PRTG Manual: SSH SAN Physical Disk Sensor
The SSH SAN Physical Disk sensor monitors a physical disk on a storage area network (SAN) via Secure Shell (SSH).
The SAN must provide a command-line interface (CLI) for this purpose.
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- Dutch: SSH SAN Fysieke Schijf
- French: SAN disque physique (SSH)
- German: SSH SAN Physikalisches Laufwerk
- Japanese: SSH SAN 物理ディスク
- Portuguese: Disco físico SAN (SSH)
- Russian: Физический диск SAN по SSH
- Simplified Chinese: SSH SAN 物理磁盘
- Spanish: Disco físico SAN (SSH)
- This sensor requires credentials for Linux/Solaris/macOS (SSH/WBEM) systems in the settings of the parent device.
- This sensor does not support every SAN, even if it provides a CLI. This sensor only works with specific devices, for example, the HPE P2000.
- If the controller of the target system breaks down, increase the scanning interval to discharge the controller and try again.
- After a firmware update of the target system, this sensor might show incorrect channel values. Add this sensor anew in this case.
- This sensor has a medium performance impact.
- This sensor only supports IPv4.
- This sensor uses lookups to determine the status values of one or more channels.
- Sometimes the devices you monitor with this sensor return status values that are not officially documented so that the shown sensor status in PRTG differs from the "real" device status. For more information, see the Knowledge Base: Why does my SSH SAN sensor show a wrong status?
- Knowledge Base: Which encryption algorithms do PRTG SSH sensors support?
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.
|
Parent Tags |
The tags that the sensor inherits from its parent device, parent group, and parent probe.
|
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.
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 ( |
Setting |
Description |
---|---|
Connection Timeout (Sec.) |
Define a timeout in seconds for the connection. This is the time that the sensor waits to establish a connection to the host. Keep this value as low as possible. Enter an integer.
|
Shell Timeout (Sec.) |
Define a timeout in seconds for the shell response. This is the time in seconds the sensor waits for the shell to return a response after it has sent its specific command (for example, cat /proc/loadavg). The maximum value is 300 seconds (5 minutes). Enter an integer.
|
SSH Port |
Define which port this sensor uses for the SSH connection:
|
Use Port Number |
This setting is only visible if you select Enter custom port number above. Enter the port number (between 1 and 65535) that this sensor uses for the SSH connection. Enter an integer. |
SSH Engine |
Select the SSH engine that you want to use to access data with this SSH sensor. Choose between:
|
Result Handling |
Define what PRTG does with the sensor result:
|
SSH SAN Physical Disk Settings
Setting |
Description |
---|---|
Disk |
The physical disk that this sensor monitors. |
Name |
The name of the physical disk that this sensor monitors. |
Size |
The size of the physical disk that this sensor monitors. |
Command Mode |
Define the command set that the sensor uses on the device to get monitoring data:
|
Request Mode |
Define the which type of data the sensor requests:
|
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.
|
Graph Type |
Define how different channels are shown for this sensor:
|
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. |
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.
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 |
---|---|
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 |
Health |
The disk heath status
|
Total IOs |
The total number of I/O operations |
Transferred |
The data transferred |
KNOWLEDGE BASE
Which encryption algorithms do PRTG SSH sensors support?
Why does my SSH SAN sensor show a wrong status?
What security features does PRTG include?