Hi Lex,
We've had report messages returned by SecureSnmpContext.HandleDiscovery() where the EngineTime exceeds the max int value of 2147483647; so our network devices do not complete the discovery process and we stop receiving messages from them.
As the value is based on Environment.TickCount we can workaround the problem by rebooting the server, however it's not ideal.
Thanks,
Stuart
Comments: Hi Lex, We're hosting the pipeline ourselves in our own process, basically as a trap receiver (although the issue is with informs rather than traps, obviously). It's working well, other than this issue. Kind regards, Stuart
We've had report messages returned by SecureSnmpContext.HandleDiscovery() where the EngineTime exceeds the max int value of 2147483647; so our network devices do not complete the discovery process and we stop receiving messages from them.
As the value is based on Environment.TickCount we can workaround the problem by rebooting the server, however it's not ideal.
Thanks,
Stuart
Comments: Hi Lex, We're hosting the pipeline ourselves in our own process, basically as a trap receiver (although the issue is with informs rather than traps, obviously). It's working well, other than this issue. Kind regards, Stuart