was preventing VLANs from being cleared out before they were delted.

document.

interface for this node.

control interface for this node.

operate on, but it turns out this can happen during normal operations. For
example, an experiment with no VLANs.

hold separate values for each of the two pipes. This allows us to
treat the links asymmetrically with respect to the delay node
configuration. Changes to tmcd to return the expanded info, and rework
(completely) delay_config to allow user to change the duplex
characteristics (just like before), or just simplex characteristics by
specifying the pipe number. By convention (I invented) pipe 0 is
traffic coming in on iface0. Of course, none of the front end stuff
has been changed, so the changing a single pipe does not cause
anything in virt_lans to be changed, so those changes will be lost at
swapout. Also get rid of all the ssh'ed pipe config stuff in
delay_config. Instead, add a client side script called update_delays
to /etc/testbed on the experiment nodes. After updating the delays
table, just ssh over and run that script, which calls the existing
code. Less distribution of knowledge.

we can now handle cross-switch links.

Now supports multiple switches and multiple stacks. To do this, the existing
snmpit_cisco module had to be modified to behave as a true object, and its
interface changed.

A new layer of abstraction has been added: the stack. This is to hide the
details of how things such as VLAN creation occur across multiple devices. For
example, in Cisco stacks, you always contact the stack leader (VTP server) to
create/delete VLANs. Other switches may have different semantics, such as
having to contact every switch to create the VLAN.

Now uses libdb for database access and permissions checks.

Hardware details are hidden as much as possible in the user interface. For
example, the creation and deletion commands now take VLAN identifiers, and
snmpit transparently turns these into device-specific VLAN numbers.

snmpit.in has been re-written from scratch. The new version uses three basic
steps:
1) Process command line options and determine operation to run
2) Determine which devices, ports, and VLANs will be involved and make
   the appropriate objects
3) Actually perform the operation
   when TESTMODE is set, does only steps 1 and 2

Some command-line options have changed. This is because we now use getopt,
rather than a home-grown parser, to parse the command line. As a result of the
large number of options, and an attempt to mimic old options as much as
possible, the options are no longer very mnemonic.

Uses a new table called switch_stacks to figure out which switches belong to
which stacks. A stack is defined as a set of switches that share VLANs.

All snmpit scripts and modules now run with 'use strict' to help catch certain
programming errors.

VLAN listing now prints out the pid/eid and vname for VLANs, if possible.

A few things have bitrotted due to these changes:
* snmpit_intel will need to be re-tooled to use the new interface, and to
  behave as a proper object
* vlansync, vlandiff, and resetvlans depend on the output of snmpit, and will
  need to be updated to understand its new output format

that relative links work. This old way:

	<a href="docwrapper.php3?docname=tutorial/nscommands.html">

throws off relative links cause the actual file (docwrapper.php3) is
in a different dir than the file loaded. Instead, do this:

	<a href="tutorial/docwrapper.php3?docname=nscommands.html">

So loading tutorial/docwrapper.php3 sets the current directory
properly, and then loads the specified file.

run from a testbed style daemon so that we can more easily get word
of failure.

snmpit.

pages now show the lastlogin info that is gathered from sshd syslog
reporting to users. That info is parsed by security/genlastlog.c, and
entered into the DB in the nodeuidlastlogin and uidnodelastlogin
tables. If not obvious from the names, for each user we want the last time
they logged in anyplace, and for each node we want the last time anyone
logged into it. The latter is obviously more useful for scheduling
purposes. All of the various images have new /etc/syslog.conf files,
and the 6.2 got new sshd_configs (all cvsup'ed with kill -HUP). There
is an entry in boss:/etc/crontab and users:/etc/syslog.conf. All of
this is decribed in greater detail in security/genlastlog.c.

to ptopgen to use just one switch, and pass that from assign. Only
until new snmpit is ready.

checks. Some functions in here (such as getting the outlet for a node) could
probably stand to be moved to libdb.

Also now uses the snmpit_apc library directly, so that it does not need to
make external calls to snmpit.