One of my co-worker is writing some script in Scotty, he found that the
following async snmp requtest does not get excuted immediately in scotty
2.1.9, the command return immediately with the request ID, however, "snoop"
indicates that no packet is being send out on the SUN interface.
% $s get moduleSwVersion.1 {puts "%V"}
13574
%>
It does not matter how longer we wait (we waited for over 5 minutes) or how
many
async request we send (we send over 300), no packet was send and call back
script were not executed.
I played with the problem a bit more, here is what I found:
- scotty 2.1.5: async request alway send out immediately
- scotty 2.1.7: first 10 async request send out immediately, after that,
request get queued up
- scotty 2.1.9: async request almost always get queued up
when an SNMP request got queued up, a "snmp wait" or another synchronize snmp
command will trigger the request in the queue to be send out to the
network. It seems to me that this is a scotty bug introduced in version
2.1.7, was there any change to the way the TCL event loop handle async
event in 2.1.7?
I undersand that we should always use a "snmp wait" command to ensure all
pending SNMP request has been complete, and we are currently doing that, I
just think this may not have been the desirable behavour. Anybody have
similar experience?
/Simon
-- !! 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 <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.