...
ASR9000 is not showing correct RSP uptime in snmp walk.
Poll the RSP Uptime data through snmp walk using below MIB. 1.3.6.1.4.1.9.9.117.1.2.1.1.8
"Process restart Invmgr" would help
SNMPv2-SMI::mib-2.47.1.1.1.1.7.8796468 = STRING: "module 0/RSP0/CPU0" SNMPv2-SMI::mib-2.47.1.1.1.1.7.38557239 = STRING: "module 0/RSP0/CPU0" SNMPv2-SMI::mib-2.47.1.1.1.1.7.56744940 = STRING: "module 0/RSP1/CPU0" SNMPv2-SMI::mib-2.47.1.1.1.1.7.5375401 = STRING: "module 0/RSP1/CPU0" (base) test-M-R06J:~ test$ snmpwalk -v2c -c test 172.18.87.100 1.3.6.1.4.1.9.9.117.1.2.1.1.8.8796468 SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.8.8796468 = Gauge32: 1590497859 <<<<<<< Showing incorrect for RSP0 (base) test-M-R06J:~ test$ snmpwalk -v2c -c test 172.18.87.100 1.3.6.1.4.1.9.9.117.1.2.1.1.8.5375401 SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.8.5375401 = Gauge32: 4637550 RP/0/RSP0/CPU0:ASR-9010-D#sh redundancy Tue May 26 13:49:57.176 UTC Redundancy information for node 0/RSP0/CPU0: ========================================== Node 0/RSP0/CPU0 is in ACTIVE role Node Redundancy Partner (0/RSP1/CPU0) is in STANDBY role Standby node in 0/RSP1/CPU0 is ready Standby node in 0/RSP1/CPU0 is NSR-not-configured Node 0/RSP0/CPU0 is in process group PRIMARY role Process Redundancy Partner (0/RSP1/CPU0) is in BACKUP role Backup node in 0/RSP1/CPU0 is ready Backup node in 0/RSP1/CPU0 is NSR-ready Group Primary Backup Status --------- --------- --------- --------- dsc 0/RSP0/CPU0 0/RSP1/CPU0 Ready dlrsc 0/RSP0/CPU0 0/RSP1/CPU0 Ready central-services 0/RSP0/CPU0 0/RSP1/CPU0 Ready v4-routing 0/RSP0/CPU0 0/RSP1/CPU0 Ready netmgmt 0/RSP0/CPU0 0/RSP1/CPU0 Ready mcast-routing 0/RSP0/CPU0 0/RSP1/CPU0 Ready v6-routing 0/RSP0/CPU0 0/RSP1/CPU0 Ready Group_10_bgp2 0/RSP0/CPU0 0/RSP1/CPU0 Ready Reload and boot info ---------------------- A9K-RSP440-TR reloaded Sat Mar 28 15:25:01 2020: 8 weeks, 2 days, 22 hours, 24 minutes ago Active node booted Sat Mar 28 15:25:01 2020: 8 weeks, 2 days, 22 hours, 24 minutes ago Standby node boot Thu Apr 2 21:46:26 2020: 7 weeks, 4 days, 16 hours, 3 minutes ago Standby node last went not ready Tue May 12 15:29:12 2020: 1 week, 6 days, 22 hours, 20 minutes ago Standby node last went ready Tue May 12 15:29:12 2020: 1 week, 6 days, 22 hours, 20 minutes ago There have been 0 switch-overs since reload Active node reload Cause: Initiating switch-over. Standby node reload "Cause: Install operation. Shutdown standby node gracefully."