>>>>> George Ross writes:
George> It's intended to create a new VLAN on a ProCurve 4000, and
George> indeed it does appear to do so.
George> However, the next snmp# operation of any kind that I do
George> appears to reuse the same vbl instead of the one I give it,
George> and then fails because of that createAndGo.
George> First time around:
George> Looks OK. Second time around:
George> Seems OK before, but the after value is still what it was the
George> first time around.
George> Any suggestions? Tnm snapshot 99-08-12 (because I can't
George> easily upgrade tcl on this machine).
Try to figure out what actually goes into the SNMP messages. Either
turn 'snmp watch on' and look at the varbinds (just to make sure the
problem is really on scotty's part). An alternative is to run tcpdump
which produces more human readable output (the latest version on
www.tcpdump.org is able to load MIBs using libsmi).
Once you have proven that the problem lies within scotty, try to
figure out whether you can create simpler example (e.g. one which only
modifies sysLocation.0) since the problem should not depend on what
you are trying to set.
-- Juergen Schoenwaelder Technical University Braunschweig <email@example.com> Dept. Operating Systems & Computer Networks Phone: +49 531 391 3289 Bueltenweg 74/75, 38106 Braunschweig, Germany Fax: +49 531 391 5936 <URL:http://www.ibr.cs.tu-bs.de/~schoenw/>
-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <firstname.lastname@example.org>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.
This archive was generated by hypermail 2b29 : Mon Jan 08 2001 - 15:27:40 MET