All new accounts created on Gitlab now require administrator approval. If you invite any collaborators, please let Flux staff know so they can approve the accounts.

  1. 10 Jan, 2002 1 commit
    • Robert Ricci's avatar
      Most of the time, findVlan() retries up to 10 times to find a VLAN, to · 6a3140fa
      Robert Ricci authored
      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.
      6a3140fa
  2. 07 Jan, 2002 1 commit
  3. 03 Jan, 2002 1 commit
  4. 21 Nov, 2001 1 commit
  5. 02 Nov, 2001 2 commits
  6. 31 Oct, 2001 2 commits
    • Robert Ricci's avatar
      6881dc73
    • 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
      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
      7e53c10a
  7. 03 Oct, 2001 2 commits
    • Mac Newbold's avatar
      Make snmpit fail loudly when it can't get the vlan edit buffer. Usually this... · 4f140f75
      Mac Newbold authored
      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.
      4f140f75
    • 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.
      645197be
  8. 14 Aug, 2001 1 commit
  9. 19 Jul, 2001 2 commits
  10. 04 Jun, 2001 1 commit
  11. 01 Jun, 2001 1 commit
  12. 29 May, 2001 1 commit
  13. 26 May, 2001 1 commit
  14. 18 May, 2001 1 commit
  15. 17 May, 2001 1 commit