-----BEGIN PGP SIGNED MESSAGE-----
Content-Type: text/plain; charset=us-ascii
> 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).
tcpdump was useful. It looks like it's a timeout/retransmission problem.
The ProCurve is quite slow to create VLANs, though it seems to respond to
everything else promptly (including all my other set requests, which was
confusing the issue nicely!). It hadn't occured to me that tnm would get
bored waiting by default and would retransmit the createAndGo three or
four times. When the ProCurve is done with the first copy, and has sent
its reponse, it processes the second, third and ... copies and sends error
responses back for them, which tnm then queues up to hand on to my program
the next time it tries to send anything to the ProCurve.
I'll try tuning -timeout and -retries to see if that fixes it.
Dr George D M Ross, Division of Informatics, University of Edinburgh
Kings Buildings, Mayfield Road, Edinburgh, Scotland, EH9 3JZ
Mail: email@example.com Voice: +44 131 650 5147 Fax: +44 131 667 7209
PGP: 1024/B74A4F7D 14 E8 B3 00 20 04 68 F8 95 40 CB 36 A4 D4 FA 90
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
-----END PGP SIGNATURE-----
-- !! 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