PRTG Manual: SNMP HPE ProLiant System Health Sensor
The SNMP HPE ProLiant System Health sensor monitors the system health of an HPE ProLiant server via the Simple Network Management Protocol (SNMP).
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- Dutch: SNMP HPE ProLiant Systeemstatus
- French: HPE ProLiant état du système (SNMP)
- German: SNMP HPE ProLiant Systemzustand
- Japanese: SNMP HPE ProLiant システム正常性
- Portuguese: Saúde do sistema HPE ProLiant (SNMP)
- Russian: Работоспособность системы HPE ProLiant по SNMP
- Simplified Chinese: SNMP HPE ProLiant 系统健康状况
- Spanish: Salud de sistema HPE ProLiant (SNMP)
- For Gen10 servers: Use the HPE Integrated Lights Out (iLO) interface as the parent device.
- For Gen9 servers or earlier: This sensor requires HPE Insight Management Agents and HPE Insight Management WBEM Providers on the target system.
- This sensor supports iLO as of iLO 3. We recommend that you use at least iLO 4.
- This sensor supports IPv6.
- This sensor has a low performance impact.
- This sensor uses lookups to determine the status values of one or more channels.
- This sensor has predefined limits for temperatures and broken frames.
- Redundant array of independent disks (RAID) controllers that have no hard disks assigned might cause the Down status. In this case, deactivate the respective controllers in the HPE ProLiant BIOS to avoid sensor errors.
Requirement |
Description |
---|---|
For Gen9 servers or earlier, this sensor requires a specific HPE system management tool to be installed on the target system to report data via SNMP: HPE Insight Management Agents. To receive SNMP data from redundant array of independent disks (RAID) controllers, the sensor also requires HPE Insight Management Agents. For Gen10 servers, this sensor no longer requires HPE system management tools. For more information and download links, see the Knowledge Base: Monitor HP ProLiant via SNMP? For Gen9 servers or earlier, some of the HPE object identifiers (OID) that this sensor uses are only accessible via the iLO interface. If this sensor throws an error that it cannot find "such device types", create a device that points to the address of the HPE iLO interface (if available) and add the sensor to this device. We recommend that you use the Agentless Management feature with configured SNMP. You can set this up in the iLO configuration interface under Administration | Management | SNMP Settings. For Gen10 servers, use the HPE iLO interface as parent device for this sensor. |
Setting |
Description |
---|---|
Sensor Name |
Enter a name to identify the sensor. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets. If the name contains angle brackets (<>), PRTG replaces them with braces ({}) for security reasons. For more information, see the Knowledge Base: What security features does PRTG include? |
Parent Tags |
The tags that the sensor inherits from its parent device, parent group, and parent probe. This setting is for your information only. You cannot change it. |
Tags |
Enter one or more tags. Confirm each tag with the Spacebar key, a comma, or the Enter key. You can use tags to group objects and use tag-filtered views later on. Tags are not case-sensitive. Tags are automatically inherited. It is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>). For performance reasons, it can take some minutes until you can filter for new tags that you added. The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
|
Priority |
Select a priority for the sensor. This setting determines the position of the sensor in lists. The highest priority is at the top of a list. Choose from the lowest priority () to the highest priority (). |
Setting |
Description |
---|---|
Primary Channel |
Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel is always displayed below the sensor's name. The available options depend on what channels are available for this sensor. You can set a different primary channel later by clicking below a channel gauge on the sensor's Overview tab. |
Graph Type |
Define how different channels are shown for this sensor:
|
Stack Unit |
This setting is only visible if you select Stack channels on top of each other above. Select a unit from the list. All channels with this unit are stacked on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so. |
By default, all of these settings are inherited from objects that are higher in the hierarchy. We recommend that you change them centrally in the root group settings if necessary. To change a setting for this object only, click under the corresponding setting name to disable the inheritance and to display its options.
For more information, see section Inheritance of Settings.
For more information, see section Root Group Settings, section Scanning Interval.
Schedules, Dependencies, and Maintenance Window
You cannot interrupt the inheritance for schedules, dependencies, and maintenance windows. The corresponding settings from the parent objects are always active. However, you can define additional schedules, dependencies, and maintenance windows. They are active at the same time as the parent objects' settings.
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window (default).
For more information, see section Root Group Settings, section Access Rights.
Which channel units are available depends on the sensor type and the available parameters. If no configurable channels are available, this field shows No configurable channels.
For more information, see section Root Group Settings, section Channel Unit Configuration.
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
Channel |
Description |
---|---|
CPU Fan Status |
The CPU fan status
|
Disk Controller Status |
The disk controller status
|
Downtime |
In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status |
Fans Broken |
The number of broken fans This channel has a default limit
|
Fans Running |
The number of running fans |
Fault Tolerant Fans Broken |
The number of fault-tolerant broken fans This channel has a default limit
|
Fault Tolerant Fans Running |
The number of fault-tolerant running fans |
Overall Status |
The overall status
This channel is the primary channel by default. |
Power Consumption [#] |
The power consumption |
Power Consumption [#] (%) |
The power consumption (%) |
Power Supply [#] Condition |
The power supply condition
|
Power Supply [#] Status |
The power supply status
|
System Fan Status |
The system fan status
|
Temperature [#] ([Component]) |
The temperature of the component |
Thermal Status |
The thermal status
|
KNOWLEDGE BASE
Monitor HP ProLiant via SNMP?
What security features does PRTG include?
Why is my SNMP HPE ProLiant System Health sensor in the error status after updating PRTG?
My SNMP sensors don’t work. What can I do?