IPMI (Intelligent Platform Management Interface) monitoring enables users to seamlessly observe and manage server well-being, independent of the status of the device (the host system's CPU/firmware/operating system). Using IPMI, you can comprehensively monitor your devices' hardware health constantly. With IPMI, administrators gain the ability to receive alerts and notifications, enabling a prompt response to potential issues.
This help document includes a comprehensive list of vendors and protocols supported by OpManager for IPMI monitoring.
Currently, OpManager supports the following vendor-protocol combinations for IPMI monitoring:
These are the OIDs from the IDRAC-MIB-SMIv2.mib that are used for hardware data collection:
Category | Units | Sensor Name | Sensor Status | Sensor Value |
Fan | RPM | .1.3.6.1.4.1.674.10892.5.4.700.12.1.8 | .1.3.6.1.4.1.674.10892.5.4.700.12.1.5 | .1.3.6.1.4.1.674.10892.5.4.700.12.1.6 |
Temperature | degree C | .1.3.6.1.4.1.674.10892.5.4.700.20.1.8 | .1.3.6.1.4.1.674.10892.5.4.700.20.1.5 | .1.3.6.1.4.1.674.10892.5.4.700.20.1.6 |
Power | Watts | .1.3.6.1.4.1.674.10892.5.4.600.12.1.8 | .1.3.6.1.4.1.674.10892.5.4.600.12.1.5 | .1.3.6.1.4.1.674.10892.5.4.600.12.1.6 |
Voltage | Volts | .1.3.6.1.4.1.674.10892.5.4.600.20.1.8 | .1.3.6.1.4.1.674.10892.5.4.600.20.1.5 | NIL |
Processors | MHz | .1.3.6.1.4.1.674.10892.5.4.1100.30.1.8 | .1.3.6.1.4.1.674.10892.5.4.1100.30.1.5 | .1.3.6.1.4.1.674.10892.5.4.1100.30.1.12 |
Memory | MB | .1.3.6.1.4.1.674.10892.5.4.1100.50.1.8 | .1.3.6.1.4.1.674.10892.5.4.1100.50.1.5 | .1.3.6.1.4.1.674.10892.5.4.1100.50.1.14 |
Battery | -NA- | .1.3.6.1.4.1.674.10892.5.4.600.50.1.7 | .1.3.6.1.4.1.674.10892.5.4.600.50.1.5 | .1.3.6.1.4.1.674.10892.5.4.600.50.1.6 |
Disk array data | MB | .1.3.6.1.4.1.674.10892.5.5.1.20.130.4.1.55 | .1.3.6.1.4.1.674.10892.5.5.1.20.130.4.1.4 | .1.3.6.1.4.1.674.10892.5.5.1.20.130.4.1.17 |
The base API call used for monitoring iDrac devices is:
/redfish/v1/systems/system.embedded.1/
Based on the set of sensors that need to be monitored, the last part of the API is modified.
Category | Units | API to get sensor details |
Fan, Temperature | RPM (fan), degree C (temperature) | /redfish/v1/Chassis/System.Embedded.1/Thermal/ |
Power, Voltage | Watts (power), Volts (Voltage) | /redfish/v1/Chassis/System.Embedded.1/Power/ |
Processors | MHz | /redfish/v1/Systems/System.Embedded.1/Processors/ |
Memory | MB | /redfish/v1/Systems/System.Embedded.1/Memory/ |
Disk array data | MB | /redfish/v1/Systems/System.Embedded.1/Storage/ |
IPMI Hardware monitoring in HP iLO devices is performed using the base API call:
/redfish/v1/systems/1/
The different APIs used for hardware systems in the HP device is as listed below:
Category | Units | APIs to get Sensor Details |
Fan, Temperature | Percentage (fan), degree C (temperature) | /redfish/v1/Chassis/1/Thermal/ |
Power | Watts | /redfish/v1/Chassis/1/Power/ |
Processors | MHz | /redfish/v1/Systems/1/Processors/ |
Memory | MB | /redfish/v1/Systems/1/Memory/ |
Disk array data | MB | /redfish/v1/Systems/1/Storage/ - To get SSD details /redfish/v1/Systems/1/SmartStorage/ArrayControllers/ - To get HDD details |
The OIDs used for IPMI-based hardware monitoring under the IMM.mib are as follows:
Category | Units | Sensor Name | Sensor Status | Sensor Value |
Fan | Percentage | .1.3.6.1.4.1.2.3.51.3.1.3.2.1.2 | .1.3.6.1.4.1.2.3.51.3.1.3.2.1.10 | .1.3.6.1.4.1.2.3.51.3.1.3.2.1.3 |
Temperature | degree C | .1.3.6.1.4.1.2.3.51.3.1.1.2.1.2 | .1.3.6.1.4.1.2.3.51.3.1.1.2.1.11 | .1.3.6.1.4.1.2.3.51.3.1.1.2.1.3 |
Power | Watts | .1.3.6.1.4.1.2.3.51.3.1.11.2.1.2 | .1.3.6.1.4.1.2.3.51.3.1.11.2.1.6 | NIL |
Voltage | Volts | .1.3.6.1.4.1.2.3.51.3.1.2.2.1.2 | .1.3.6.1.4.1.2.3.51.3.1.2.2.1.11 | .1.3.6.1.4.1.2.3.51.3.1.2.2.1.3 |
Processors | Mhz | .1.3.6.1.4.1.2.3.51.3.1.5.20.1.2 | .1.3.6.1.4.1.2.3.51.3.1.5.20.1.11 | .1.3.6.1.4.1.2.3.51.3.1.5.20.1.3 |
Memory | MB | .1.3.6.1.4.1.2.3.51.3.1.5.21.1.2 | .1.3.6.1.4.1.2.3.51.3.1.5.21.1.8 | .1.3.6.1.4.1.2.3.51.3.1.5.21.1.7 |
Disk array data | MB | .1.3.6.1.4.1.2.3.51.3.1.12.2.1.2 | .1.3.6.1.4.1.2.3.51.3.1.12.2.1.3 | NIL |
SuperMicro devices are monitored by using the base call API: /redfish/v1/Systems/1
Based on the set of sensors that need to be monitored, the last part of the API is modified as follows:
Category | Units | APIs to get sensor details |
Fan, Temperature | rpm(fan), degree C(temperature) | /redfish/v1/Chassis/1/Thermal |
Power, Voltage | Watts(power), Volts(Voltage) | /redfish/v1/Chassis/1/Power |
Processors | Watts | /redfish/v1/Systems/1/Processors |
Memory | MB | /redfish/v1/Systems/1/Memory (For higher versions) /redfish/v1/Systems/1 (For lower versions) |
Disk array data | MB | /redfish/v1/Systems/1/SimpleStorage |
These are the OIDs from the HUAWEI-SERVER-IBMC-MIB.mib that are used for hardware data collection:
Category | Units | Sensor Name | Sensor Status | Sensor Value |
Fan | RPM | .1.3.6.1.4.1.2011.2.235.1.1.8.50.1.7 | .1.3.6.1.4.1.2011.2.235.1.1.8.50.1.4 | .1.3.6.1.4.1.2011.2.235.1.1.8.50.1.2 |
Temperature | degree C | .1.3.6.1.4.1.2011.2.235.1.1.26.50.1.2 | Nil | .1.3.6.1.4.1.2011.2.235.1.1.26.50.1.3 |
Power | Watts | .1.3.6.1.4.1.2011.2.235.1.1.6.50.1.13 | .1.3.6.1.4.1.2011.2.235.1.1.6.50.1.7 | .1.3.6.1.4.1.2011.2.235.1.1.6.50.1.8 |
Processors | MHz | .1.3.6.1.4.1.2011.2.235.1.1.15.50.1.10 | .1.3.6.1.4.1.2011.2.235.1.1.15.50.1.6 | .1.3.6.1.4.1.2011.2.235.1.1.15.50.1.5 |
Memory | MB | .1.3.6.1.4.1.2011.2.235.1.1.16.50.1.10 | .1.3.6.1.4.1.2011.2.235.1.1.16.50.1.6 | .1.3.6.1.4.1.2011.2.235.1.1.16.50.1.4 |
Disk array data | MB | .1.3.6.1.4.1.2011.2.235.1.1.18.50.1.6 | .1.3.6.1.4.1.2011.2.235.1.1.18.50.1.3 | .1.3.6.1.4.1.2011.2.235.1.1.18.50.1.12 |
The base API call used for monitoring Huawei devices is:
/redfish/v1/Systems/1
Based on the set of sensors that need to be monitored, the last part of the API is modified.
Category | Units | API to get sensor details |
Fan, Temperature | RPM (fan), degree C (temperature) | /redfish/v1/Chassis/1/Thermal |
Power, Voltage | Watts (power), Volts (Voltage) | /redfish/v1/Chassis/1/Power |
Processors | MHz | /redfish/v1/Systems/1/Processors |
Memory | MB | /redfish/v1/Systems/1/Memory |
The OIDs used for IPMI-based hardware monitoring under the HH3C-SERVER-AGENT-MIB are as follows:
Category | Units | Sensor Name | Sensor Status | Sensor Value |
Fan | rpm | .1.3.6.1.4.1.25506.13.1.2.1.1.10.1.1.2 | .1.3.6.1.4.1.25506.13.1.2.1.1.10.1.1.8 | .1.3.6.1.4.1.25506.13.1.2.1.1.10.1.1.5 |
Temperature | degree C | .1.3.6.1.4.1.25506.13.1.2.1.1.11.3.1.3 | .1.3.6.1.4.1.25506.13.1.2.1.1.11.3.1.6 | .1.3.6.1.4.1.25506.13.1.2.1.1.11.3.1.4 |
Power | Watts | .1.3.6.1.4.1.25506.13.1.2.1.1.7.1.1.1.14 | .1.3.6.1.4.1.25506.13.1.2.1.1.7.1.1.1.13 | .1.3.6.1.4.1.25506.13.1.2.1.1.7.1.1.1.10 |
Processors | Mhz | .1.3.6.1.4.1.25506.13.1.2.1.1.1.1.1.15 | .1.3.6.1.4.1.25506.13.1.2.1.1.1.1.1.14 | .1.3.6.1.4.1.25506.13.1.2.1.1.1.1.1.3 |
Memory | MB | .1.3.6.1.4.1.25506.13.1.2.1.1.2.2.1.4 | .1.3.6.1.4.1.25506.13.1.2.1.1.2.2.1.16 | .1.3.6.1.4.1.25506.13.1.2.1.1.2.2.1.6 |
Disk array data | MB | .1.3.6.1.4.1.25506.13.1.2.1.1.9.3.1.12 | .1.3.6.1.4.1.25506.13.1.2.1.1.9.3.1.11 | .1.3.6.1.4.1.25506.13.1.2.1.1.9.3.1.9 |
The following list covers the status codes corresponding to each vendor-protocol combination and specifies the criticality of alerts triggered based on these codes.
Disk array data:
Other sensors:
Since status messages are passed as strings in IMM, only the following criticalities can be raised in the related alerts:
HP iLO4 is the fourth generation in the iLO series and, below are the status strings that correspond to its respective memory status.
Thank you for your feedback!