[network::cisco::standard::snmp::plugin] --mode=configuration: wrong calculation after reboot / sysuptime not considered

[joschi99]

Latest plugins
monitoring the Cisco configuration status is not working correctly and every reboot of the device will result in a CRITICAL service, because the sysuptime needs to be subtracted from the ccmHistoryRunningLastChanged.

https://community.cisco.com/t5/network-management/check-running-configuration-update-via-snmp/td-p/2322074
lausser/check_nwc_health#118

(2490)

[joschi99]

I would like to ask if there are any question on this ticket or if we can help with additional informations to fix this problem. Any updates available?

[joschi99]

Are there any news on this? It's still not working correctly.

[lucie-dubrunfaut]

Hello :)

Can you show me a debug output return? I want to inspect the contain of $oid_ccmHistoryRunningLastChanged = '.1.3.6.1.4.1.9.9.43.1.1.1.0'

[joschi99]

.1.3.6.1.4.1.9.9.43.1.1.1.0 = 3514985460
.1.3.6.1.4.1.9.9.43.1.1.2.0 = 3514975520
.1.3.6.1.4.1.9.9.43.1.1.3.0 = 3376052894

[lucie-dubrunfaut]

Ok my bad I've see the right OID

Because by default critical-status trigger when
%{running_last_changed} > %{running_last_saved}

and

running_last_changed => $self->{results}->{$oid_ccmHistoryRunningLastChanged} / 100,
running_last_saved => $self->{results}->{$oid_ccmHistoryRunningLastSaved} / 100,

[joschi99]

The problem is that it is not enough considering this OID, but you need also to consider sysuptime: https://community.cisco.com/t5/network-management/check-running-configuration-update-via-snmp/td-p/2322074

[lucie-dubrunfaut]

Hello :)

I understand the situation and the development ticket had been added in our backlog. We'll discuss for a solution in development team refinement.

[joschi99]

I send you a snmpwalk where you can reproduce the problem

[joschi99]

hi @lucie-dubrunfaut,
did you have any news on this?

[lucie-dubrunfaut]

Hello :)

This development is scheduled for team discussion at this week's refinement session. Depending on his assessment, we will be able to provide a solution as soon as possible.

[joschi99]

Hi Lucie,
the problem will also apear if the uptime counter is resetting after 497 days and this will generate a false positive. I send you for this a snmpwalk by mail.

[garnier-quentin]

#5282

[lucie-dubrunfaut]

Hello @joschi99

Were you able to check whether the solution proposed by @garnier-quentin solved your issue?

[joschi99]

I can confirm that the solution from @garnier-quentin works