We have several Cisco Catalyst 6807s that are in VSS configuration. Each Catalyst 6807 in the pair have a supervisor module. During maintenance on one of these VSS pair we will perform fail over between the Active and Standby so the SUPs and other line cards are being reloaded. However the whole chassis does not get rebooted so the LAST BOOT under Node Details does not update the uptime value.
I did open a case with Solarwinds support and got a response there is not a way to change which sysuptime value that is polled under Node Details. Their suggestion was to create a UNDP for a different OID. I have also searched Solarwinds Customer Portal and Thwack but have been unable to find anything specific to this situation. I am posting in the hope that someone else has come across this same scenario to see what may have been done.
We would like to be able to report off of the Uptime for control process value for Last Reboot.
Here are examples of show version output and the show redundancy output. The current processor and peer processor uptime is the accurate last boot time.
Show Version output
Uptime is 3 years, 13 weeks, 2 days, 7 hours, 51 minutes
Uptime for this control processor is 5 weeks, 12 hours, 27 minutes
Cat6807#sh redundancy
Redundant System Information :
------------------------------
Available system uptime = 3 years, 13 weeks, 2 days, 7 hours, 51 minutes
Switchovers system experienced = 2
Standby failures = 0
Last switchover reason = user forced
Current Processor Information :
-------------------------------
Active Location = slot 1/3
Current Software state = ACTIVE
Uptime in current state = 5 weeks, 12 hours, 27 minutes
Peer Processor Information :
----------------------------
Standby Location = slot 2/3
Current Software state = STANDBY HOT
Uptime in current state = 5 weeks, 11 hours, 54 minutes
Many Thanks.
