1. 15 Aug, 2006 1 commit
  2. 04 May, 2006 1 commit
    • Kirk Webb's avatar
      · 662e924f
      Kirk Webb authored
      Fixed up vlan listing function under (apparently) new variable scoping rules
      in perl 5.8.
      662e924f
  3. 16 Feb, 2006 1 commit
  4. 19 Dec, 2005 1 commit
    • Kevin Atkinson's avatar
      · 45f997fd
      Kevin Atkinson authored
      Updates to to Error Logging API Code.
      
      You should start seeing much better error messages coming from my
      system.  Errors coming from parse.proxy and assign (the two most
      frequent sources of errors) should now be concise and to the point.
      Errors coming from libosload/libreboot (the next most frequent source
      of errors) should now also be much better, but not perfect.  Getting
      perfect errors will likely a rework of how errors are handled in
      libosload/libreboot, just adding tberror/tbwarn/tbnotice calls is not
      enough.  I can do this at a latter date if necessary.
      
      A few minor database changes.
      
      Some changes to the API.  A few bug fixes. Lots of tberror/tbwarn/tbnotice
      added to scripts.
      
      Since assign is a C program, and at this time my API is perl only, I wrote a
      second wrapper around assign, assign_wrapper2.  When assign fails errors are
      now parsed in assign_wrapper2, sent to stderr and logged.  This means that
      RunAssign() just returns when assign fails rather than echoing some of
      assign.log output and then quiting.  The output to the activity log remains
      unchanged.
      
      Since "parse.proxy" is run from ops I couldn't use my API in it, even though
      it is a perl program.  Instead I parse the errors coming form it in
      parse-ns.
      45f997fd
  5. 04 Nov, 2005 1 commit
    • Kevin Atkinson's avatar
      · a2aba279
      Kevin Atkinson authored
      Added error logging API.  See tbsetup/libtblog.pm.in and tbsetup/libtblog.sql.
      a2aba279
  6. 26 Oct, 2005 1 commit
    • Robert Ricci's avatar
      Add a new option, -N, which prints out the name of the VLAN number · 2c9ae239
      Robert Ricci authored
      assoicated with the named VLAN..
      
      Output format:
      <vlan_name> <stack> <vlan_number>
      (This is so the user can, if they want, look for more than one
      VLAN on more than one stack at a time.)
      
      This should make some of the control-net firewall code cleaner.
      
      For now, though, it's pretty inefficient, becuase it calls listVlans()
      on the whole stack, which is much more than needed. But, a more efficient
      implementation will require a change to the switch/stack API.
      2c9ae239
  7. 21 Jun, 2005 2 commits
  8. 15 Jun, 2005 1 commit
  9. 09 Jun, 2005 1 commit
  10. 24 May, 2005 1 commit
  11. 20 Apr, 2005 1 commit
  12. 23 Mar, 2005 1 commit
  13. 18 Mar, 2005 1 commit
  14. 10 Mar, 2005 1 commit
    • Robert Ricci's avatar
      Added two new options, needed for WhOL support. · b992395a
      Robert Ricci authored
      The new -b option gives you a string with the current status of a
      port (ie. if it's enabled, and which VLAN it's in). After getting
      this string, you can then modify the port (change its VLAN, enable it,
      whatever). Then, when you're done, you can pass the string -b gave you
      back into snmpit with -B, and it should restore the original status
      of the port.
      
      Make sure to put the status string in single quotes when you pass it
      on the command line. It contains some stuff that the shell won't like,
      such as semicolons.
      b992395a
  15. 09 Feb, 2005 1 commit
  16. 12 Jan, 2005 1 commit
    • Robert Ricci's avatar
      Added support for a switch being in more than one stack at a time. · e189be0a
      Robert Ricci authored
      Each switch has a 'primary' stack that it belongs to if it's specified
      with the '-i' parameter. Otherwise, it can be considered to be a part
      of any of the stacks of which it's a member.
      
      The main point of this is so that we can have switches that are on
      both the control and experimental networks.
      
      Note: Having a VLAN with the same name on two overlapping stacks is
      like crossing the streams: that would be bad. Not "all life as you
      know it stopping instantaneously" bad, but snmpit might get confused.
      e189be0a
  17. 06 Jan, 2005 1 commit
  18. 03 Dec, 2004 1 commit
  19. 02 Dec, 2004 1 commit
  20. 01 Dec, 2004 1 commit
    • Robert Ricci's avatar
      Add user-visible support for trunking. · cfdf5c00
      Robert Ricci authored
      Added support for Cisco switches to enable and disable trunking for a
      port.
      
      Added two new command-line options:
      -N <port> <vlans>
      	Enable trunking on a port, allowing the given list of VLANs to
      	cross the trunk
      
      -U <port>:
      	Disable trunking for the port
      
      This functionality is needed for Mike's firewall support.
      cfdf5c00
  21. 15 Nov, 2004 1 commit
    • Leigh B. Stoller's avatar
      A bunch of ElabInELab changes. · 10b116e0
      Leigh B. Stoller authored
      * snmpit: When ElabInELabis true, use the routines in the new
        snmpit_remote.pm library for setting up and tearing down vlans for an
        experiment. At present, only these two operations are proxied out to
        the outer emulab.
      
      * snmpit_remote.pm: A new little library that uses the XMLPRC server on
        the outer emulab to setup and destroy vlans for an inner experiment.
        This code is used from snmpit (see above).
      
      * snmpit_lib.pm: A couple of minor changes for the server side of the
        proxy operation.
      
      * snmpit.proxy.in: A new perl module that is invoked from the RPC
        server.  This proxy sets up and tears down vlans for an inner elab.
        The basic model is that the container experiment will have lots of
        vlans for various individual experiments running on the inner emulab.
      
      * swapexp: A couple of minor elabinelab hacks.
      
      * tbswap: For elabinelab experiments, reconfig/restart dhcpd when
        tearing down the experiment, and call out to new elabinelab script
        when setting up an elabinelab experiment. There is no provision for
        swapmod at this time.
      
      * elabinelab: A new script to create the inner emulab. Does all kinds of
        gross DB stuff then more gross stuff on the inner ops and boss.
      10b116e0
  22. 12 Nov, 2004 1 commit
  23. 10 Nov, 2004 1 commit
  24. 30 Mar, 2004 1 commit
  25. 09 Mar, 2004 1 commit
  26. 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
      snmpit_lib.pm).
      
      Also in this commit are two new options for switch stacks - the
      ability to specify minimum and maximum VLAN number to use.
      c069a419
  27. 04 Aug, 2003 1 commit
  28. 28 Apr, 2003 1 commit
  29. 17 Mar, 2003 1 commit
  30. 06 Mar, 2003 1 commit
  31. 07 Feb, 2003 1 commit
  32. 06 Feb, 2003 1 commit
  33. 21 Jan, 2003 1 commit
  34. 17 Jan, 2003 1 commit
    • Robert Ricci's avatar
      New features: · 2d7b6b82
      Robert Ricci authored
          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
      2d7b6b82
  35. 10 Jan, 2003 1 commit
  36. 28 Aug, 2002 1 commit
  37. 07 Jul, 2002 1 commit
  38. 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
      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.
      13381879
  39. 20 Feb, 2002 1 commit
    • Robert Ricci's avatar
      Code for picking which VLANs are allowed to go across which trunks. · 11e0ea5f
      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.
      11e0ea5f