cisco_monitor probe is not inserting some QOS metrics into the database

Document ID : KB000033960
Last Modified Date : 14/02/2018
Show Technical Document Details
Problem:

cisco_monitor probe is not inserting some QOS metrics into the database

Symptoms:
I recently noticed that some metrics are not being inserted into the DB for cisco_monitor. So far I've only noticed it for a new client. I've ran DrNimbus and it looks like the QOS_MESSAGES make it to our primary hub but must be dropped by data_engine.

Upon examination of the probe GUI, we saw that there were valid values being collected by the probe for various metrics including CPU, Memory and Power Supply but NOT Fan State.

MIB variable: CiscoEnvMonFanState
instance:? .1007

.1.3.6.1.4.1.9.9.13.1.4.1.3.1007 and other OIDs

Fan State and values show up for all other devices for customers except this one customer.

no Fan State (<value>) targets show up in the data_engine log at loglevel 3 or 5.

Switch Model:
Cisco Catalyst Switch: 1.3.6.1.4.1.9.9.13.1.4.1.3.1007 (1=On, 0=Off) (Counter Mode: Delta)

1 = normal

The probe log shows the OID and values are being collected.

QOS Object

QOS_CISCO_ENVIRONMENT

Fan

In DrNimBUS, the target only shows Power supply state and values

For testing purposes, we used snmpget to walk the MIB which showed everything was working as expected and the MIB variables and OIDs and expected MIBs were present.

After checking everything we tried a redeployment of the probe but to no avail.

Finally, I suspected that perhaps the profile was somehow corrupted so we deleted and recreated it, and then lo and behold, the Fan State target values started populating as we could see in DrNimBUS sniffer output.

This appeared to be caused by Copy/Paste operation. Copying from one profile to another from within the probe GUI, e.g., SNMP community string can adversely affect the outcome and we saw target values not being populated - though you cannot see any bad/special characters when you do a Ctrl-C and Ctrl-V to paste it into a new profile or when viewing the .cfg file in Notepad++. Nevertheless, the outcome is predictable as we could recreate the small but strange problem.

Environment:

Windows 2008 R2
Robot 7.80
cisco_monitor 3.36
Robot 7.80

Resolution:
Copy and paste the community string into Notepad then copy it from notepad and paste it into the GUI. The problem no longer occurred. We also retested it.




keywords: cisco_monitor NO no fan state missing metrics OID MIB