1. 15 Nov, 2001 1 commit
    • Robert Ricci's avatar
      Two fixes: · 947f73f4
      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)
  2. 14 Nov, 2001 1 commit
  3. 02 Nov, 2001 2 commits
  4. 01 Nov, 2001 1 commit
  5. 31 Oct, 2001 1 commit
    • Robert Ricci's avatar
      Major overhaul of snmpit. Highlights, in no particular order: · 7e53c10a
      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
      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
  6. 03 Oct, 2001 1 commit
    • Robert Ricci's avatar
      snmpit now discovers which switch to operate on based on the members of the · 645197be
      Robert Ricci authored
      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.
  7. 24 Aug, 2001 3 commits
  8. 14 Aug, 2001 1 commit
  9. 23 Jul, 2001 1 commit
  10. 19 Jul, 2001 1 commit
  11. 05 Jun, 2001 1 commit
  12. 04 Jun, 2001 2 commits
  13. 01 Jun, 2001 1 commit
  14. 26 May, 2001 1 commit
  15. 25 May, 2001 1 commit
  16. 24 May, 2001 1 commit
  17. 21 May, 2001 1 commit
  18. 18 May, 2001 2 commits
  19. 17 May, 2001 1 commit
  20. 11 May, 2001 1 commit
    • Mac Newbold's avatar
      Small set of changes to make snmpit work correctly for the control router. I... · 070d4a56
      Mac Newbold authored
      Small set of changes to make snmpit work correctly for the control router. I also added entries in the database for ports that are in vlans (other than the default #1) that aren't connected to a node in the database. So, from now on, when an empty port is in a vlan, we need to put an entry in the wires table that says its connected to node 'empty' on some unused port number.
  21. 20 Mar, 2001 1 commit
  22. 15 Mar, 2001 1 commit
  23. 14 Mar, 2001 1 commit
  24. 06 Feb, 2001 1 commit
  25. 27 Jan, 2001 1 commit
  26. 12 Jan, 2001 1 commit
  27. 05 Jan, 2001 1 commit
  28. 03 Jan, 2001 2 commits
  29. 17 Nov, 2000 1 commit
  30. 09 Nov, 2000 1 commit
  31. 16 Oct, 2000 1 commit
  32. 11 Oct, 2000 1 commit
  33. 09 Oct, 2000 1 commit
  34. 19 Sep, 2000 1 commit