1. 15 Jun, 2005 1 commit
  2. 10 Nov, 2004 1 commit
  3. 22 Oct, 2003 1 commit
    • Robert Ricci's avatar
      Change the way the switch modules for snmpit get their configuration · c069a419
      Robert Ricci authored
      information. Rather than pass it all in, which was getting very
      cumbersome, and inconsistent between Cisco and Intel switches, the
      modules query the database themselves (via a new function in
      Also in this commit are two new options for switch stacks - the
      ability to specify minimum and maximum VLAN number to use.
  4. 28 Apr, 2003 1 commit
  5. 12 Feb, 2003 1 commit
  6. 10 Jan, 2003 1 commit
  7. 07 Jul, 2002 1 commit
  8. 17 Jun, 2002 1 commit
    • Robert Ricci's avatar
      Made some functions that previously took only a single port or VLAN · 13381879
      Robert Ricci authored
      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
      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.
  9. 23 Jan, 2002 1 commit
    • Robert Ricci's avatar
      Some minor API changes to increase effieciency for Intels. · 9bd1dded
      Robert Ricci authored
      First, the stack-level createVlan() function no longer takes as an
      argument a list of devices the VLAN exists on, since it looks like
      this will never be needed.
      In it's place, createVlan() now takes a list of ports, so that it can
      (if so desired) put the ports in the VLAN without a seperate lock and
      The snmpit_intel module now uses its 'nested locking' feature to avoid
      additional locking in these cases. Note though, that the way that this
      is done is not safe for multiple switches in a stack. If we ever have
      to support multiple Intels (looks doubtful), this will have to be
      removed, or locking will need to be moved a level up to
      snmpit_intel_stack . Yuck.
      For Intels, the removeVlan() function calls removePortsFromVlan()
      itself, again to save locking overhead. The Cisco behavior, however,
      is unchanged, as locking is not expensive, and this would be too
  10. 17 Jan, 2002 1 commit
  11. 14 Jan, 2002 1 commit
    • Robert Ricci's avatar
      Intel support is now fully functional. This mostly invovled making the · 223fff16
      Robert Ricci authored
      snmpit_intel module conform to the same API as snmpit_cisco.
      Intels VLANs are now done per port rather than per MAC. This should give
      experimenters more flexibility on the experimental net, and is more consistent
      with the way that VLANs are done on other switches.
      snmpit_intel_stack will need to undergo minor work to support stacks of
      multiple switches.
  12. 07 Jan, 2002 1 commit
  13. 03 Jan, 2002 1 commit
  14. 28 Dec, 2001 1 commit
    • Robert Ricci's avatar
      Initial version of the stack-level abstraction for Intel switches. For not, · e30b66aa
      Robert Ricci authored
      it's mostly just a wrapper around snmpit_intel - this is because, when doing
      MAC-based VLANs, you never have to talk to more than one switch. When we switch
      to doing port-based VLANs with Intels (something we should do soon, but will
      take some experimenting), it will likely become a more full-fledged layer.
      Not at all debugged yet - won't be able to do that until we have the
      mini-testbed more funcitonal.