Network Management
Verify the Hardware Health Sensor status of Arista devices for NPM
This article provides information on how to verify the Hardware Health Sensor status of Arista devices.
First published date
Last published date
Overview
This article tells you how to verify the status of Hardware Health Sensors on Arista devices.
The Hardware Health Sensor status of nodes is based on their sensor value (entPhySensorValue) compared to its threshold value and not the operational status (entPhySensorOperStatus). You can find the list of different Hardware Health Sensor OIDs in this article Hardware health OIDS
The following example shows three sensors in critical status displayed in the Web Console:
The value received from the sensors needs to be checked to verify the status.
Product section
Resolution
- Run SolarWinds SNMP Walk: A new tool for collecting SNMP MIB walks on the device and get all the available OIDs.
- Locate the sensor strings in the SNMP Walk file by using the
entPhysicalDescr .1.3.6.1.2.1.47.1.1.1.1.2OID. The following strings are found based on the above example:.1.3.6.1.2.1.47.1.1.1.1.2.100305211 = STRING: " TX Bias Sensor for Ethernet5".1.3.6.1.2.1.47.1.1.1.1.2.100305212 = STRING: " TX Power Sensor for Ethernet5".1.3.6.1.2.1.47.1.1.1.1.2.100305213 = STRING: " RX Power Sensor for Ethernet5".1.3.6.1.2.1.47.1.1.1.1.2.100305202 = STRING: " Voltage Sensor for Ethernet5"
Note: The highlighted numbers can be used as a unique identifier of each sensor to easily locate the sensors. -
Locate the current value of these sensors using the
entPhySensorValue 1.3.6.1.2.1.99.1.1.1.4OID. See the following example:.1.3.6.1.2.1.99.1.1.1.4.100305211 = INTEGER: 0.1.3.6.1.2.1.99.1.1.1.4.100305212 = INTEGER: -1000000000.1.3.6.1.2.1.99.1.1.1.4.100305213 = INTEGER: -1000000000.1.3.6.1.2.1.99.1.1.1.4.100305202 = INTEGER: 331 -
Round off the Integer results to match values displayed on the Web Console. The values can be used to verify if they are beyond the threshold set by the vendor.
Additional information
To determine the unit of measurement:Use the OID for entPhySensorUnitsDisplay - 1.3.6.1.2.1.99.1.1.1.6
For example: A temperature sensor will usually have a value of "Celsius" for this OID.
These are the OIDs used by Arista with configured sensor threshold values for either below and above the warning and critical level.
| Sensor | OID |
| aristaEntSensorThresholdLowWarning | 1.3.6.1.4.1.30065.3.12.1.1.1.1 |
| aristaEntSensorThresholdLowCritical | 1.3.6.1.4.1.30065.3.12.1.1.1.2 |
| aristaEntSensorThresholdHighWarning | 1.3.6.1.4.1.30065.3.12.1.1.1.3 |
| aristaEntSensorThresholdHighCritical | 1.3.6.1.4.1.30065.3.12.1.1.1.4 |
Using the screenshot from the Web Console as an example, use the OIDs for the Critical status, not Low and High. The values based on the SNMP Walk results are as follows:
aristaEntSensorThresholdLowCritical
.1.3.6.1.4.1.30065.3.12.1.1.1.2.100305211 = INTEGER: 100
.1.3.6.1.4.1.30065.3.12.1.1.1.2.100305212 = INTEGER: 891
.1.3.6.1.4.1.30065.3.12.1.1.1.2.100305213 = INTEGER: 251
.1.3.6.1.4.1.30065.3.12.1.1.1.2.100306202 = INTEGER: 297
aristaEntSensorThresholdHighCritical
.1.3.6.1.4.1.30065.3.12.1.1.1.4.100305211 = INTEGER: 1500
.1.3.6.1.4.1.30065.3.12.1.1.1.4.100305212 = INTEGER: 14125
.1.3.6.1.4.1.30065.3.12.1.1.1.4.100305213 = INTEGER: 14125
.1.3.6.1.4.1.30065.3.12.1.1.1.4.100306202 = INTEGER: 360
The values for each sensor in entPhySensorValue can now be checked if they are within the threshold range set by the vendor. In our example, the current value of the first three sensors (TX Bias Sensor for Ethernet5, TX Power Sensor for Ethernet5, and RX Power Sensor for Ethernet5) are below the sensor's critical threshold resulting to a Critical status.The value in the fourth sensor (Voltage Sensor for Ethernet5) is within the accepted threshold.
Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.