- 20 Feb, 2002 1 commit
-
-
Robert Ricci authored
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.
-
- 12 Feb, 2002 1 commit
-
-
Robert Ricci authored
-
- 11 Feb, 2002 1 commit
-
-
Robert Ricci authored
getTrunks: Build a structure representing all of the trunks in the switch topolgy getTrunkPath: Find the shortest path between two switches, across the trunks found by getTrunks Note that the getTrunkPath duplicates some work done in assign. However, we don't currently have a good way to pass this information from assign to snmpit, and we need to be able to figure this out anyway, in case snmpit isn't being called as part of experiment swapin. These functions should soon be used to pick which VLANs are allowed across which trunks.
-
- 03 Jan, 2002 1 commit
-
-
Robert Ricci authored
standardize on using /usr/bin/perl instead of /usr/local/bin/perl (most already did.)
-
- 28 Dec, 2001 1 commit
-
-
Robert Ricci authored
does not yet exist (but should soon.) There is a new database table, switch_stack_types, that goes along with these code changes, to indicate which module should be used for each switch stack.
-
- 28 Nov, 2001 1 commit
-
-
Robert Ricci authored
speeds and duplexes from the database.
-
- 15 Nov, 2001 1 commit
-
-
Robert Ricci authored
Make sure experiments actually exist, for morons like me that enter 'eid pid' instead of 'pid eid' When using '-t', don't try to create VLANs if they already exist, just put ports in it (this can be used, for example, to repair damage to switch state or fix up after manually monkeying with VLANs)
-
- 31 Oct, 2001 1 commit
-
-
Robert Ricci authored
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
-
- 16 Oct, 2001 1 commit
-
-
Leigh B. Stoller authored
-
- 24 Sep, 2001 1 commit
-
-
Mac Newbold authored
-
- 23 Jul, 2001 1 commit
-
-
Mac Newbold authored
-
- 21 Jul, 2001 1 commit
-
-
Mac Newbold authored
Many changes and updates for handling new types. The db now has types like 'pc600', 'pc850', and 'dnard', and each type has a class like 'pc' or 'shark'. This updates scripts that use types to use classes where appropriate, and to handle the new types where there were hardcoded things that couldn't be eliminated right now.
-
- 07 Jun, 2001 1 commit
-
-
Mac Newbold authored
-
- 01 Jun, 2001 1 commit
-
-
Mac Newbold authored
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.
-
- 29 May, 2001 1 commit
-
-
Mac Newbold authored
-
- 25 May, 2001 1 commit
-
-
Mac Newbold authored
-
- 21 May, 2001 1 commit
-
-
Mac Newbold authored
Added full support for adding vlans based on the table in the database. Takes pid and eid and sets up the vlans. Added tableVlans to snmpit_lib to get them from the db, and updated snmpit_doc.txt.
-
- 18 May, 2001 1 commit
-
-
Mac Newbold authored
-
- 17 May, 2001 1 commit
-
-
Mac Newbold authored
-