2.0.0p9 CEE - SNMP scan not detecting Cisco SLAs on Cisco 4k series router

[rdm (Robert Masters)]

CMK version : 2.0.0p9 CEE
OS version : RHEL 7.9

Description of the problem : When performing an inventory on a Cisco 4k series router, we are not seeing any SLA entries. This was previously reported under 1.6.9p18. Following the upgrade, the same problem exists.
Example:
cmk --no-cache -vvIn rtr2404
(extensive results)
[piggyback] No persisted sections loaded
[piggyback] Execute data source
No piggyback files for ‘rtr2404’. Skip processing.
No piggyback files for ‘172.17.50.126’. Skip processing.
Loading autochecks from /omd/sites/bunnings_env/var/check_mk/autochecks/rtr2404.mk

• EXECUTING DISCOVERY PLUGINS (34)
  Trying discovery with: cisco_temperature, if_brocade, cisco_hsrp, rmon_stats, if64, ucd_cpu_util, cisco_cpu_multiitem, cisco_temp, if, cisco_temp_sensor, cisco_power, cisco_fantray, ucd_cpu_load, cisco_temp_perf, snmp_uptime, if64adm, cisco_qos, cisco_mem_asa64, ifoperstatus, cisco_fan, cisco_redundancy, cisco_mem_asa, if_fortigate, cisco_fru_power, ucd_processes, if64_tplink, cisco_mem, cisco_temperature.dom, cisco_fru_module_status, if_lancom, ucd_mem, ucd_disk, cisco_fru_powerusage, snmp_info
  Try aquire lock on /omd/sites/bunnings_env/var/check_mk/autochecks/rtr2404.mk
  Got lock on /omd/sites/bunnings_env/var/check_mk/autochecks/rtr2404.mk
  Releasing lock on /omd/sites/bunnings_env/var/check_mk/autochecks/rtr2404.mk
  Released lock on /omd/sites/bunnings_env/var/check_mk/autochecks/rtr2404.mk
  SUCCESS - Found no new services, no new host labels

Rule is defined as:
Host name is rtr2404||RTT type:|echo||Treshold:|5000 ms/us||State:|active||Store Router RTT Echo SLA|

I have tried turning off and on bulkwalks, forcing the external SNMP client, and checking the output of a manual snmpwalk. I have also tried performing ‘full’ discoveries. The manual walk reports the SLA OIDs.

Any suggestions?

Thanks
Rob

[andreas-doehler (Andreas)]

Can you take a look the the OID “.1.3.6.1.2.1.1.2.0” on your device. What value do you get there from the device?
The SLA check expects there
“.1.3.6.1.4.1.9.1.2068”
or
“.1.3.6.1.4.1.9.1.1858”
If your device outputs something else then the check needs to be modified if your device provides the information needed for the check.

[rdm (Robert Masters)]

Looking at the results, I’m not seeing anything below “.1.3.6.1.4.1.9.1”.
The router is reporting “Cisco IOS Software [Everest], ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 16.6.7, RELEASE SOFTWARE (fc2)” as the software version.

I am following up with our Network engineer about what the correct feature OID is. The data OIDs appear to be correct.

[andreas-doehler (Andreas)]

Important is only the content of this OID “.1.3.6.1.2.1.1.2.0”
This is used by the check to determine if the device has the SLA data.

[thl-cmk]

I had a short look at the scan function of the cisco_ip_sla check. At the moment it looks only for exactly two types of cisco devices.

  "snmp_scan_function": lambda oid: oid(".1.3.6.1.2.1.1.2.0")
   in [
       ".1.3.6.1.4.1.9.1.2068",  # ciscoISR4331
       ".1.3.6.1.4.1.9.1.1858",  # ciscoC891FK9
  ]

so you can extend this list with the contents of the OID “.1.3.6.1.2.1.1.2.0” from your device like this:

    "snmp_scan_function": lambda oid: oid(".1.3.6.1.2.1.1.2.0")
    in [
        ".1.3.6.1.4.1.9.1.2068",  # ciscoISR4331
        ".1.3.6.1.4.1.9.1.1858",  # ciscoC891FK9
        ".1.3.6.1.4.1.9.1.1318",  # cat3560cG8TC
    ],

or change the scan function at all like this:

    "snmp_scan_function": lambda oid: "cisco" in oid(".1.3.6.1.2.1.1.1.0").lower()
                                      and "ios" in oid(".1.3.6.1.2.1.1.1.0").lower()
                                      and oid(".1.3.6.1.4.1.9.9.42.1.2.2.1.37.*"),

this looks for all Cisco IOS(-XE) devices with IP SLA MIB. I would prefer the second option.

[rdm (Robert Masters)]

I have tried out @thl-cmk 's second suggestion, and it works perfectly on our units.

This looks like a viable fix.