that are being removed.

setting port speed and duplex. Well, they probably do, in some MIB,
but not in the one we use on CatOS, and these features aren't actually
very important right now.

Also, make snmpit itself handle unsupported port operations.

VLAN domain. This means that we have to create and delete VLANs on
all switches, instead of just the 'leader'. This behavior is
controlled through the new single_domain column in the
switch_stack_types table.

Most snmpit_cisco functions now take Cisco-specific VLAN numbers,
rather than testbed VLAN ids.

This is an intermediate step in removing dependance on VTP.

As a nice side-effect, this saves another 25% of the time to
operate on topologies for large experiments.

for large experiments. Not as much of an improvement as I had hoped,
but further improvement will probably take a lot more rearranging.

printed incorrectly.

    Accept [switch.]<module>/<port> format for ports, so that we can
	deal with ports not in the database (mostly for my own
	debugging sanity.)
    A -n option that prevents assign from changing hardware settings
    	(though, unlike TESTMODE, does read some information from
	the switches)
    Private VLAN support, through the -x,-y, and -z switches. There
	are only 5 letters of the alphabet left, so I've given up on
	memnonic switches.
    Worked a bit on making VLAN deletion more efficient, but with
    	little sucess

Private VLANs work like so:
Make a primary private VLAN with:
snmpit -m myvlan-primary -y primary
Attach a community VLAN to it like so:
snmpit -m myvlan-community -y community -x myvlan-primary -z cisco2.1/15
Put some ports into the community VLAN:
snmpit -m myvlan-community pc1:0 pc2:0

set of MIBs, and index some of the tables differently.

This requires some more information to be passed when switch and stack objects
are created.

Also, make the SNMP community to use overridable in the defs file.

Re-worked the snmpitGet functions slightly to make them more
convenient and to work around some ickiness in the SNMP library.

time in between retries.  This should help out when we have dozens
of experiments swapping in and out at once.

(and so, has been renamed setVlansOnTrunk). Part of the work necessary
to get the stack-level setVlanOnTrunks function to accept multiple
VLANs in one call.

take more than one. This can increase efficiency, since, for example,
we now only have to lock the VLAN edit buffer once when tearing down
an experiment, instead of once per VLAN. There are still other
functions (setVlanOnTrunks comes to mind) that could benefit from this
treatment.

These optimization have been made only for Ciscos - minimal changes
necessary to keep Intel support working were made, but they will still
have the same old slow behavior.

return value on VLAN creation. If it reports success, we look for the
VLAN with findVlan(), to make sure it's really there. We retry a
couple times if it didn't work. This will add a small (sub-second)
time penalty per VLAN created.

We ran into one instance, that we've noticed, where the switch
reported that VLAN creation succeeded, but the VLAN did not actually
get created on the switch.

OID from the CISCO-VLAN-MEMBERSHIP MIB. But, this MIB does not seem
to be supported by all Cisco switches. So, we now use vlanPortVlan
from the CISCO-STACK MIB.

So, we no longer need CISCO-VLAN-MEMBERSHIP-MIB at all, which should make
snmpit usable on a wider variety of Ciscos.

information about a large number of ports in bulk.

Also added the RMON MIB.

When dealing with trunks, since they may be EtherChannels, we have to
make another lookup on the switch to get the ifIndex for the whole
channel - can't just use the ifIndex of one of the ports like you
can from the Cisco CLI.

These changes make snmpit slightly slower - it now has to get more information
from the switches when it's going to create or delete VLANs. However, this
is on the order of fractions of seconds, so it shouldn't be too noticable.

As much of it as possible switch-independant, and put in snmpit_lib.
Should work for arbitrarily complicated switch toplogies, as long as
there are not multiple trunks between two switches. (Multiple ports
combined into one trunk are fine, however.)

As a result of this, VLAN creations and deletions now need to operate
on all switches, not just on the ones that have ports in the VLAN.
This is because the traffic may have to traverse switches that have no
ports in the VLAN to reach other switches that do.

Not called yet. I've done simple testing, but need to do more, as this
could get us into major trouble if it has bugs.

things from getting cleaned up on failure.

account for the time it may take for changes made at the master to
propagate to the slaves. Added a paramter to override this, as sometimes,
we know that we're talking to the master so the delay does not come into
play.

This should improve the running time of snmpit by about 10 seconds per VLAN
created, since we can tell right away if the VLAN already exists or not.

standardize on using /usr/bin/perl instead of /usr/local/bin/perl (most already
did.)

creation to propogate. So, we retry up to 10 times with 1-second sleeps in
between.

Made this number more easily tweakable: just set $max_tries in vlanLock().
Also, only prints out every 5th failure, and in a form that should make it
more clear that it's a transient, recoverable, error.

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

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

Make snmpit fail loudly when it can't get the vlan edit buffer. Usually this fails for one of three reasons: a) The community strings are wrong on the switch, b) some previous snmpit run left the buffer taken when it unexpectedly was killed, or c) someone else really is using the buffer.

VLANs it is to operate on. This is only a temporary multi-switch solution, as
it only picks one switch to operate on.

Also, added a sanity check in snmpit_cisco.pm. Now checks every port that
it controls, to make sure it's on the right switch. If this sanity check
fails, dies to prevent any damage to existing switch configuration.

Changes to snmpit to stop creation/renaming of vlans that already exist, in preparation for vlansync, among other things. Also added vlansync, and made a small change to vlandiff.