PRTG Manual: SSH SAN Logical Disk Sensor
The SSH SAN Logical Disk sensor monitors a logical 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 Logische Schijf
- French: SAN disque logique (SSH)
- German: SSH SAN Logisches Laufwerk
- Japanese: SSH SAN 論理ディスク
- Portuguese: Disco lógico SAN (SSH)
- Russian: Логический диск SAN по SSH
- Simplified Chinese: SSH SAN 逻辑磁盘
- Spanish: Disco lógico SAN (SSH)
Consider the following remarks and requirements for this sensor:
Remark |
Description |
---|---|
Credentials |
This sensor requires credentials for Linux/Solaris/macOS (SSH/WBEM) systems in the settings of the parent device. |
SAN support |
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. |
Scanning interval |
If the controller of the target system breaks down, increase the scanning interval to discharge the controller and try again. |
Firmware update |
After a firmware update of the target system, this sensor might show incorrect channel values. Add this sensor anew in this case. |
Performance impact |
This sensor has a medium performance impact. |
IPv4 |
This sensor only supports IPv4. |
Lookups |
This sensor uses lookups to determine the status values of one or more channels. |
Device status |
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 |
Knowledge Base: Which encryption algorithms do PRTG SSH sensors support? |
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
- logicaldisk
- sshsan
- sshsanlogicaldisk
For more information about basic sensor settings, see section Sensor Settings.
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. This sensor has a fixed timeout of 300 seconds. If you change the value, it does not have an effect on the timeout. Make sure that the connection timeout is a value that is higher than the shell timeout to avoid potential errors. |
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. This sensor has a fixed timeout of 300 seconds. If you change the value, it does not have an effect on the timeout. Make sure that the shell timeout is a value that is lower than the connection timeout to avoid potential errors. |
SSH Port Inheritance |
Define which port this sensor uses for the SSH connection:
|
Custom SSH Port |
This setting is only visible if you select Do not inherit port (enter a custom SSH port) 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:
We strongly recommend that you use the default SSH engine. The option you select here overrides the selection of the SSH engine in a higher object: a parent device, group, probe, or root. |
Result Handling |
Define what PRTG does with the sensor result:
This option is not available when the sensor runs on the hosted probe of a PRTG Hosted Monitor instance. In a cluster, PRTG stores the result in the PRTG data directory of the master node. |
Setting |
Description |
---|---|
Volume |
The volume that this sensor monitors. |
Size |
The size of the volume that this sensor monitors. |
Command Mode |
Define the command set that the sensor uses on the device to get monitoring data:
|
Setting |
Description |
---|---|
Primary Channel |
Select a channel from the list to define it as the primary channel. In the device tree, PRTG displays the last value of the primary channel 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 this sensor shows different channels:
|
Stack Unit |
This setting is only visible if you select Stack channels on top of each other above. Select a unit from the list. PRTG stacks all channels with this unit 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.
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
This channel is the primary channel by default. |
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?