I am getting an error when running Get requests on a device and need to know what the error indicates. If I do a Walk using a MIB browser after I get this issue I can get all the data. It is only #SNMP that has an issue.
Details:
I am calling Messenger.Get using SNMP V1 and I am querying 24 SNMP objects.
Exception:
{"wrong response sequence: expected -1986527, received 14790689"}
StackTrace:
at Lextm.SharpSnmpLib.Messaging.SnmpMessageExtension.GetResponse(ISnmpMessage request, Int32 timeout, IPEndPoint receiver, UserRegistry registry, Socket udpSocket) in c:\sharpsnmplib\SharpSnmpLib\Messaging\SnmpMessageExtension.cs:line 440
at Lextm.SharpSnmpLib.Messaging.SnmpMessageExtension.GetResponse(ISnmpMessage request, Int32 timeout, IPEndPoint receiver, Socket udpSocket) in c:\sharpsnmplib\SharpSnmpLib\Messaging\SnmpMessageExtension.cs:line 355
at Lextm.SharpSnmpLib.Messaging.SnmpMessageExtension.GetResponse(ISnmpMessage request, Int32 timeout, IPEndPoint receiver) in c:\sharpsnmplib\SharpSnmpLib\Messaging\SnmpMessageExtension.cs:line 320
at Lextm.SharpSnmpLib.Messaging.Messenger.Get(VersionCode version, IPEndPoint endpoint, OctetString community, IList`1 variables, Int32 timeout) in c:\sharpsnmplib\SharpSnmpLib\Messaging\Messenger.cs:line 96
at Comms.Snmp.SharpSNMPDevice.ProcessSnmpGets() in z:\Projects\SES Astra\2400 Program\Software\Source\SESAstraServer\SESAstraServer\Comms\Snmp\SharpSNMPDevice.cs:line 892
Please advise.
Comments: Meanwhile, if you do use `Manager.Get` as the exception call stack shows, you might switch to the latest release (where each call to `Get` will create a new `Socket` object). Some very old releases do not do that. Make sure `timeout` value is large enough, or there might be `TimeoutException` raised when you send a lot of requests to a single agent and it could not respond all of them quickly enough.
Details:
I am calling Messenger.Get using SNMP V1 and I am querying 24 SNMP objects.
Exception:
{"wrong response sequence: expected -1986527, received 14790689"}
StackTrace:
at Lextm.SharpSnmpLib.Messaging.SnmpMessageExtension.GetResponse(ISnmpMessage request, Int32 timeout, IPEndPoint receiver, UserRegistry registry, Socket udpSocket) in c:\sharpsnmplib\SharpSnmpLib\Messaging\SnmpMessageExtension.cs:line 440
at Lextm.SharpSnmpLib.Messaging.SnmpMessageExtension.GetResponse(ISnmpMessage request, Int32 timeout, IPEndPoint receiver, Socket udpSocket) in c:\sharpsnmplib\SharpSnmpLib\Messaging\SnmpMessageExtension.cs:line 355
at Lextm.SharpSnmpLib.Messaging.SnmpMessageExtension.GetResponse(ISnmpMessage request, Int32 timeout, IPEndPoint receiver) in c:\sharpsnmplib\SharpSnmpLib\Messaging\SnmpMessageExtension.cs:line 320
at Lextm.SharpSnmpLib.Messaging.Messenger.Get(VersionCode version, IPEndPoint endpoint, OctetString community, IList`1 variables, Int32 timeout) in c:\sharpsnmplib\SharpSnmpLib\Messaging\Messenger.cs:line 96
at Comms.Snmp.SharpSNMPDevice.ProcessSnmpGets() in z:\Projects\SES Astra\2400 Program\Software\Source\SESAstraServer\SESAstraServer\Comms\Snmp\SharpSNMPDevice.cs:line 892
Please advise.
Comments: Meanwhile, if you do use `Manager.Get` as the exception call stack shows, you might switch to the latest release (where each call to `Get` will create a new `Socket` object). Some very old releases do not do that. Make sure `timeout` value is large enough, or there might be `TimeoutException` raised when you send a lot of requests to a single agent and it could not respond all of them quickly enough.