Strange behavior after receiving notInTimeWindows report
Fuoco Emilio Francesco <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <[email protected]> |
Hi to all, I have a strange behavior in my code that cyclically sends SNMP-GET to a remote device every 5 minutes. Following what happens... (closed by brackets you can find the msgAuthEngTIME). I added 1 second of network delay... Everything is OK. 13:04:02.411515000 SNMP-GET sent to device (11088965) 13:04:02.680255000 Received response (11088966) 1 second of network delay... Everything is OK. 13:09:02.433468000 SNMP-GET sent to device (11089265) 13:09:02.640451000 Received response (11089266) I added 155 seconds of network delay... Device answer is notInTimeWindows report - behavior is as expected 13:14:02.460844000 SNMP-GET sent to device (11089565) 13:16:37.562737000 Received notInTimeWindows report from device (11089721) Now the strange behavior... 13:16:37.563430000 Another SNMP-GET sent to device (11089721) There is no evidence of this GET sent from my source code. The msgAuthEngTIME is the same of the notInTimeWindows report. It seems that net-snmp automatically sends another GET after receiving notInTimeWindows report. Anyone can confirm this behavior? If yes, is there a way to prevent "automatic" sending of GET? Thanks to all for your help. Emilio ------------------------------------------------------------------------------ The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users