<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: SNMP HPE ProLiant Physical Disk Sensor
The SNMP HPE ProLiant Physical Disk sensor monitors a physical disk in an HPE server via the Simple Network Management Protocol (SNMP).
SNMP HPE ProLiant Physical Disk Sensor
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
Sensor in Other Languages
- Dutch: SNMP HPE ProLiant Fysieke Schijf
- French: HPE ProLiant disque physique (SNMP)
- German: SNMP HPE ProLiant Physikalischer Datenträger
- Japanese: SNMP HPE ProLiant 物理ディスク
- Portuguese: Disco físico HPE ProLiant (SNMP)
- Russian: Физический диск HPE ProLiant по SNMP
- Simplified Chinese: SNMP HPE ProLiant 物理磁盘
- Spanish: Disco físico HPE ProLiant (SNMP)
Remarks
Detailed Requirements
|
|
HPE system management tools
|
For Gen9 servers or earlier, this sensor needs a specific HPE system management tool to be installed on the target device to report data via SNMP: HPE Insight Management Agents. To receive SNMP data from redundant array of independent disks (RAID) controllers, you additionally need HPE Insight Management Agents. For Gen10 servers, this sensor no longer requires HPE system management tools. Instead, the sensor needs the HPE Agentless Management Service to be installed on the target device.
For more details 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.
|
Add Sensor
The Add Sensor dialog appears when you manually add a new sensor to a device. It only shows the settings that are required to create the sensor. You can change nearly all settings on the sensor's Settings tab after creation.
The settings that you select in the Add Sensor dialog are valid for all sensors that you create when you finish the dialog.
HPE ProLiant Physical Disk Settings
|
|
Disk
|
Select the physical disks that you want to monitor. PRTG creates one sensor for each physical disk that you select.
Enable check boxes in front of the respective lines to select the items. Use the check box in the table header to select all items or to cancel the selection. In large tables, use the search function in the upper-right corner.
|
Basic Sensor Settings
Click the Settings tab of a sensor to change its settings.
Basic Sensor Settings
|
|
Sensor Name
|
Enter a name to identify the sensor.
|
Parent Tags
|
Shows 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:
- snmphpephysicaldisksensor
- physicaldisk
- snmphpe
- hpe
|
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 ().
|
Usually, a sensor connects to the IP Address/DNS Name of the parent device. See the device settings for details. For some sensors, you can explicitly define the monitoring target in the sensor settings.
HPE ProLiant Physical Disk Settings
HPE ProLiant Physical Disk Settings
|
|
Disk
|
Shows the ID of the physical disk that this sensor monitors.
PRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.
|
Sensor Display
Sensor Display
|
|
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:
- Show channels independently (default): Show a graph for each channel.
- Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic.
You cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings).
|
Stack Unit
|
This setting is only visible if you enable Stack channels on top of each other as Graph Type. 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.
|
Inherited Settings
By default, all of the following 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.
Scanning Interval
Click to interrupt the inheritance.
Scanning Interval
|
|
Scanning Interval
|
Select a scanning interval from the dropdown list. The scanning interval determines the amount of time that the sensor waits between two scans. Choose from:
- 30 seconds
- 60 seconds
- 5 minutes
- 10 minutes
- 15 minutes
- 30 minutes
- 1 hour
- 4 hours
- 6 hours
- 12 hours
- 24 hours
You can change the available intervals in the system administration of PRTG Network Monitor.
|
If a Sensor Query Fails
|
Select the number of scanning intervals that the sensor has time to reach and to check a device again if a sensor query fails. Depending on the option that you select, the sensor can try to reach and to check a device again several times before the sensor shows the Down status. This can avoid false alarms if the monitored device only has temporary issues. For previous scanning intervals with failed requests, the sensor shows the Warning status. Choose from:
- Set sensor to down immediately: Set the sensor to the Down status immediately after the first request fails.
- Set sensor to warning for 1 interval, then set to down (recommended): Set the sensor to the Warning status after the first request fails. If the second request also fails, the sensor shows the Down status.
- Set sensor to warning for 2 intervals, then set to down: Set the sensor to the Down status only after the third request fails.
- Set sensor to warning for 3 intervals, then set to down: Set the sensor to the Down status only after the fourth request fails.
- Set sensor to warning for 4 intervals, then set to down: Set the sensor to the Down status only after the fifth request fails.
- Set sensor to warning for 5 intervals, then set to down: Set the sensor to the Down status only after the sixth request fails.
Sensors that monitor via Windows Management Instrumentation (WMI) always wait at least one scanning interval before they show the Down status. It is not possible to immediately set a WMI sensor to the Down status, so the first option does not apply to these sensors. All other options can apply.
If you define error limits for a sensor's channels, the sensor immediately shows the Down status. None of the interval options apply.
If a channel uses lookup values, the sensor immediately shows the Down status. None of the interval options apply.
|
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.
Schedules, Dependencies, and Maintenance Window
|
|
Schedule
|
Select a schedule from the list. You can use schedules to monitor during a certain time span (days or hours) every week. Choose from:
- None
- Saturdays
- Sundays
- Weekdays
- Weekdays Eight-To-Eight (08:00 - 20:00)
- Weekdays Nights (17:00 - 09:00)
- Weekdays Nights (20:00 - 08:00)
- Weekdays Nine-To-Five (09:00 - 17:00)
- Weekends
You can create schedules, edit schedules, or pause monitoring for a specific time span. For more information, see section Schedules.
|
Maintenance Window
|
Select if you want to set up a one-time maintenance window. During a maintenance window, monitoring stops for the selected object and all child objects. They show the Paused status instead. Choose between:
- Do not set up a one-time maintenance window: Do not set up a one-time maintenance window. Monitoring is always active.
- Set up a one-time maintenance window: Set up a one-time maintenance window and pause monitoring. You can define a time span for the pause below.
To terminate an active maintenance window before the defined end date, change the time entry in Maintenance Ends to a date in the past.
|
Maintenance Begins
|
This setting is only visible if you enable Set up a one-time maintenance window above. Use the date time picker to enter the start date and time of the one-time maintenance window.
|
Maintenance Ends
|
This setting is only visible if you enable Set up a one-time maintenance window above. Use the date time picker to enter the end date and time of the one-time maintenance window.
|
Dependency Type
|
Select a dependency type. You can use dependencies to pause monitoring for an object depending on the status of a different object. You can choose from:
- Use parent: Use the dependency type of the parent object.
- Select a sensor: Use the dependency type of the parent object. Additionally, pause the current object if a specific sensor is in the Down status or in the Paused status because of another dependency.
- Master sensor for parent: Make this sensor the master object for its parent device. The sensor influences the behavior of its parent device: If the sensor is in the Down status, the device is paused. For example, it is a good idea to make a Ping sensor the master object for its parent device to pause monitoring for all other sensors on the device in case the device cannot even be pinged. Additionally, the sensor is paused if the parent group is paused by another dependency.
To test your dependencies, select Simulate Error Status from the context menu of an object that other objects depend on. A few seconds later, all dependent objects are paused. You can check all dependencies under Devices | Dependencies in the main menu bar.
|
Dependency
|
This setting is only visible if you enable Select a sensor above. Click and use the object selector to select a sensor on which the current object will depend.
|
Dependency Delay (Sec.)
|
This setting is only visible if you select Select a sensor above. Define a time span in seconds for the dependency delay.
After the master sensor for this dependency returns to the Up status, PRTG additionally delays the monitoring of the dependent objects by the time span you define. This can prevent false alarms, for example, after a server restart or to give systems more time for all services to start. Enter an integer value.
This setting is not available if you set this sensor to Use parent or to be the Master sensor for parent. In this case, define delays in the parent device settings or in its parent group settings.
|
Access Rights
Click to interrupt the inheritance.
Access Rights
|
|
User Group Access
|
Define the user groups that have access to the sensor. You see a table with user groups and group access rights. The table contains all user groups in your setup. For each user group, you can choose from the following group access rights:
- Inherited: Inherit the access rights settings of the parent object.
- No access: Users in this user group cannot see or edit the sensor. The sensor neither shows up in lists nor in the device tree.
- Read access: Users in this group can see the sensor and view its monitoring results. They cannot edit any settings.
- Write access: Users in this group can see the sensor, view its monitoring results, and edit its settings. They cannot edit its access rights settings.
- Full access: Users in this group can see the sensor, view its monitoring results, edit its settings, and edit its access rights settings.
For more details on access rights, see section Access Rights Management.
|
Channel Unit Configuration
Click to interrupt the inheritance.
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.
Channel Unit Configuration
|
|
Channel Unit Types
|
For each type of channel, select the unit in which PRTG displays the data. If you define this setting on probe, group, or device level, you can inherit these settings to all sensors underneath. You can set units for the following channel types (if available):
- Bandwidth
- Memory
- Disk
- File
- Custom
Custom channel types are only available on sensor level.
|
Channel List
Which channels the sensor actually shows might depend on the monitored device, the available components, and the sensor setup.
|
|
Corrected Read Errors
|
The corrected read errors per second
|
Corrected Write Errors
|
The corrected write errors per second
|
Disk Status
|
The overall disk status
- Up status: OK
- Warning status: Erase Done, Erase Queued, Erasing, Not Authenticated, Predictive Failure
- Down status: Failed, SSD Wear Out
- Unknown status: Other
This channel is the primary channel by default.
|
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 in percent.
|
Drive Condition
|
The drive condition
- Up status: OK
- Warning status: Degraded
- Down status: Failed
- Unknown status: Other
|
Hard Read Errors
|
The number of hard read errors per second
|
Hard Write Errors
|
The number of hard write errors per second
|
S.M.A.R.T. Status
|
The Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.) status
- Up status: OK
- Warning status: Replace Drive
- Unknown status: Other
|
Sectors Read
|
The number of sectors read per second
|
Sectors Written
|
The number of sectors written per second
|
Threshold Passed
|
If the threshold is passed
- Up status: No
- Down status: Yes
|
More
Knowledge Base
SNMP HPE ProLiant Physical Disk sensor not showing all information
Monitor HP ProLiant via SNMP?
What security features does PRTG include?
What SNMP sensors does PRTG offer?
My SNMP sensors don’t work. What can I do?
Sensor Settings Overview
For more information about sensor settings, see the following sections: