calculation cisco config running vs startup y2k22 bug ?

[marcosjerps]

As happy users of the check_nwc_health plugin in nagios xi we're facing a strange result on a cisco Nexus9000 C9396PX Chassis

[nagiosadmin@nag2001 ~]$ /usr/local/nagios/libexec/check_nwc_health -vvv --hostname XX-XXX-XXX-dc-02.net.beeldengeluid.nl --community XXXXXXXX --mode check-config
[CONFIG]
ccmHistoryRunningLastChanged: 1633471235.92 (Wed Oct 6 00:00:35 2021)
ccmHistoryRunningLastSaved: 1599055696.47 (Wed Sep 2 16:08:16 2020)
ccmHistoryStartupLastChanged: 1599055696.46 (Wed Sep 2 16:08:16 2020)
CRITICAL - running config is ahead of startup config since 144892 minutes. changes will be lost in case of a reboot

While when looking at the switch in this case at the startup config
!Command: show startup-config
!Time: Fri Jan 14 12:58:16 2022
!Startup config saved at: Wed Jan 12 16:35:48 2022
version 7.0(3)I7(8) Bios:version 07.66

Any one facing the same issue or could you tell me howto resolve this ?

[deuntje]

same issue here with nexus 9k switches. The calculation of the 'ccmHistoryRunningXXX' values are not correct. Saw some other issues in this repo, but not found the solution.

[danjford]

Have come across a similar problem, not sure it is related to check_nwc_health though.

Querying the OIDs directly with snmpget seems to yield a similar result of the dates being super behind but show startup-config showing the correct datetimes

OIDs here:

ccmHistoryRunningLastChanged |   | .1.3.6.1.4.1.9.9.43.1.1.1
ccmHistoryRunningLastSaved |   | .1.3.6.1.4.1.9.9.43.1.1.2
ccmHistoryStartupLastChanged |   | .1.3.6.1.4.1.9.9.43.1.1.3

https://mibs.observium.org/mib/CISCO-CONFIG-MAN-MIB/