UIM - snmpcollector can't reach device: has reached sysUpTime > xxx days

Article Id: 193291
Status: Published
Updated On: 18-06-2020 12:10
Products:
CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) , NIMSOFT PROBES , DX Infrastructure Management
Issue/Introduction:

I have discovered some devices with SNMPcollector however they are not polling data and I'm seeing the following entries in snmpcollector.log:

 

Jun 09 21:01:43:967 [DefaultUDPTransportMapping_0.0.0.0/0, snmpcollector] Profile : <ip_address>has reached sysUpTime > 497 days. Cleared the stale engineTime from USM
Jun 09 21:02:43:966 [DefaultUDPTransportMapping_0.0.0.0/0, snmpcollector] Profile : <ip_address>has reached sysUpTime > 497 days. Cleared the stale engineTime from USM

What could be the cause of this?

Cause:

In most of the cases if SNMPcollector logs this error, the discovered devices had duplicated Engine ID (engineid)

Environment:

Release : 8.51/ 9.x 

Component : UIM - SNMPCOLLECTOR 3.x

Resolution:

If the rediscovery is done on devices that have a duplicated engine id this issue may occur.

A network admin should be able to check if the Engine ID is the same on multiple devices.

If duplicated Engineid is found, delete the engine id and recreate it on the device where is seen as duplicated. 

Additional Information:

SNMP Engine ID (Cisco)

https://www.cisco.com/assets/sol/sb/Switches_Emulators_v2_2_015/help/nk_configuring_snmp05.html#:~:text=By%20default%20the%20Engine%20ID,The%20Engine%20ID%20Page%20opens.