What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags

View all Tags

What OIDs are used for the CISCO UCS System Health Sensor?



I am attempting to set up some sensors for a Cisco UCS server to monitor its health and check for active faults. I have tried the built in SNMP Cisco UCS System Health sensor which does give accurate results. However we would like to be able to make sensors which could act as a standalone version of the Critical Faults Count channel using a Custom SNMP Sensor. This would involve finding the OIDs which feed the values from the System Health sensor but the problem is that I cannot find any OID which gives these values in any of the Cisco MIB documentation and the ones used by the sensor are not visible from what I can see. This makes me think that these values are actually some sort of sum of different states found from other OIDs. Thus my question is: 1. What are the OIDs that are used to retrieve data for the SNMP Cisco UCS System Health sensor. 2. Is the Critical Faults Count fed directly via an OID or is it the result of some processing post retrieval?

Thanks for any help you can offer.

cisco snmp snmp-custom-sensor snmp-sensor

Created on Feb 16, 2018 5:40:44 PM

1 Reply



Dear caulanR,

please understand that we usually don't communicate how our more complex SNMP sensors work exactly. Making them was a lot of work, we don't want to give away the results of our engineering.

As for the standalone sensor, you could use the normal System Health sensor and hide the other channels both from tables and from graphs. This is a per-channel setting. Now those channels only appear in the sensor channel list on the sensor overview tab.

Created on Feb 16, 2018 6:05:03 PM by  Arne Seifert [Paessler Support]

Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.