Unable to discover QoS elements on a Cisco device (Legacy KB ID CNC TS5784 )

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

Run the following command to determine if the CISCO-CLASS-BASED-QOS-MIB is available on the device:


nhSnmpTool -n -o 1.3.6.1.4.1.9.9.166 -c <comm> <ip>



If it fails, it will return:

nhSnmpTool -n -o 1.3.6.1.4.1.9.9.166 -c public 10.150.100.194
# 10.150.100.194:1.3.6.1.4.1.9.9.166

The MIB objects from cbQoSIfIndex ( 1.3.6.1.4.1.9.9.166.1.1.1.1.4 ) will determine the relationship between service policies and (sub)interfaces.  This table will return the ifIndex of the (sub)interface configured with the specific service policy, if a given interface is not listed in this table, eHealth will NOT discover QoS elements for this (sub)interface.

In this case you need to enable the MIB for QOS or contact Cisco TAC.
If it passes then the whole tree will be displayed. Provide the output to Concord Support.

Please contact Concord Technical Support for further assistance.

To manage QOS-enabled devices, you must purchase the Network Health product set and an eHealth ? QoS license. In Releases 5.0 and above , eHealth can discover QOS elements only on Cisco routers that support "IP-based quality of service" and the CISCO-CLASS-BASED-QOS-MIB.

Related Issues/Questions:
QoS discover issue
QoS: No MIB support for this agent
Cannot discover QoS elements
No QoS elements discovered
Unable to discover QoS elements on a Cisco device

Problem Environment:
eHealth
Cisco QoS

Causes of this problem:
Cisco CatOS firmware does not support 'CISCO-CLASS-BASED-QOS-MIB', and there is no plan of adding this MIB to the CatOS firmware.

 

Unless QoS is configured in layer 3 or IOS firmware, it cannot be discovered.


The CISCO-CLASS-BASED-QOS-MIB table starts at OID is 1.3.6.1.4.1.9.9.166. If it does not exist in the MIB then eHealth will not be able to discover QoS elements.


(Legacy KB ID CNC TS5784 )