just recently my colleague shown me a bug when Cisco Content switch exceeds 828 days of uptime it can cause network connectivity problems. So we need to monitor all affected devices for uptime. I decided to use Thold plugin for this and discover that Cacti is showing wrong uptime under Console / Management / devices and when i choose device Cacti it queries a device and shows uptime in left upper corner. It showed me 22 days. But colleague told me that uptime he is seeing on the device is more than 500 days.
So I digg a bit around and found that Cacti [0.8.7g] uses SNMPv2-MIB::sysUpTime, but this is only for the SNMP daemon uptime, no the system update. So when i open device properties it shows me actually wrong value. Shouldnt it use HOST-RESOURCES-MIB::hrSystemUptime for system update? Could be a bug / possibly old because my Cacti is a bit outdated. I am also unable to query device for hrSystemUptime:
Code: Select all
snmpget -v 2c -c my-community device_ip .1.3.6.1.2.1.1.3.0
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (186136482) 21 days, 13:02:44.82
snmptranslate .1.3.6.1.2.1.1.3.0
DISMAN-EVENT-MIB::sysUpTimeInstance
snmptranslate .1.3.6.1.2.1.25.1.1.0
HOST-RESOURCES-MIB::hrSystemUptime.0
snmpget -v 2c -c my-community device_ip .1.3.6.1.2.1.25.1.1.0
HOST-RESOURCES-MIB::hrSystemUptime.0 = No Such Object available on this agent at this OID
But actually i need to monitor tresholds and setup warning e-mail, so I looked under treshold templates and i can see there:
Code: Select all
ucd_hrSystemUptime [ucd_hrSystemUptime]
ucd_sysUptime [ucd_sysUptime]
Thx
Regards