What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Why does my SSH SAN sensor show a wrong status?

Votes:

0

Your Vote:

Up

Down

The SSH SAN sensors show me a status in PRTG that is different to the real status of my SAN. For example, when monitoring my HP P2000 with the SSH SAN System Health sensor, PRTG shows a warning status for all channels although the real status is OK.

Why does the status of the SSH SAN sensor differ from the real status of my SAN device? How can I fix this so that PRTG shows the correct status?

lookups prtg san sensor ssh ssh-san status wrong-status

Created on Apr 2, 2014 2:20:02 PM by  Gerald Schoch [Paessler Support]

Last change on Sep 13, 2019 8:28:02 AM by  Brandy Greger [Paessler Support]



1 Reply

Votes:

0

Your Vote:

Up

Down

This article applies as of PRTG 22

Correcting the status of SSH SAN sensors

The sensors

use lookups to determine the particular sensor status. When using lookups, PRTG generally maps status values as returned by the monitored device (usually integers) into informative text messages and corresponding sensor statuses.

Sensors that use lookups (like the SSH SAN sensors) determine the sensor status via the officially documented return values of the device as provided by the vendor. The HP P2000, for example, usually returns the status value 3 for the Warning status.

However, sometimes the returned status values differ from the standard status definitions and are not officially documented. If the values are not documented, PRTG does not know which value to use for which status. For example, the HP P2000 sometimes uses the value 3 for the OK status instead of the Warning status, and the value 1 for the Warning status instead of the OK status.

This means that PRTG cannot guarantee that it shows a real warning value as the Warning status. The same applies for the Error and None statuses.

If you encounter SSH SAN sensor states in PRTG that do not match the real statuses of your devices, you can customize the lookup file of these sensors and adjust it accordingly.

Changing the sensor status in lookup files

You can find all standard lookup files of your sensors in the \lookups subfolder of the PRTG program directory. To find the lookup files for specific sensors, open a channel that uses lookups and look at the section Lookup. This field shows the lookup ID that is shown in the ValueLookup tag of the lookup file. This file contains all lookup definitions for this channel.

Follow the sample description for Customizing Lookups to adjust the lookups to your needs.

  • SSH SAN System Health sensor: edit the file prtg.standardlookups.sshcli.status.ovl.
  • SSH SAN disk sensors: edit the file prtg.standardlookups.sshsan.status.ovl.

The following definition shows a customized lookup for the SSH SAN System Health sensor. In this code, the meaning of the status values 1 and 3 is swapped so that the return value 1 trigger the Warning status and the return value 3 triggers the OK status.

<?xml version="1.0" encoding="UTF-8"?> <ValueLookup id="prtg.standardlookups.sshsan.statuscustom" desiredValue="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PaeValueLookup.xsd"> <Lookups> <SingleInt state="None" value="0"> Unsupported </SingleInt> <SingleInt state="Warning" value="1"> Warning </SingleInt> <SingleInt state="Error" value="2"> Error </SingleInt> <SingleInt state="OK" value="3"> OK </SingleInt> <SingleInt state="Error" value="4"> Unrecoverable </SingleInt> <SingleInt state="None" value="5"> Not Installed </SingleInt> <SingleInt state="Error" value="6"> Unknown </SingleInt> <SingleInt state="Error" value="7"> Unavailable </SingleInt> </Lookups> </ValueLookup>


Note: We provide you with this customized lookup definition because we already had customers who reported this exact behavior of their HP P2000 devices. If this status definition also applies to your SAN device, either follow the instructions below or copy the original file into the custom folder and edit it accordingly while keeping the original ID. You can adjust any lookup file this way.

Important: If you use this modified lookup, note that we do not know if problems or errors are recognized correctly with this definition because we do not know how systems that do not use the standard definition handle an error case. We cannot provide any guarantee that this customized lookup works correctly in your use case. If it does not, you must modify the lookup definition differently.

  1. Copy the code.
  2. Paste the code into a text editor.
  3. Save the file into the \lookups\custom subfolder (for example, use the lookup ID with the ending .ovl as file name).
  4. Reload lookups: In the main menu bar, select Setup | System Administration | Administrative Tools and click the corresponding Go! button.
  5. For all channels of your SSH SAN System Health sensor, choose prtg.standardlookups.sshsan.statuscustom in section Lookup in the channel settings.

Your SSH SAN System Health sensor now uses the adjusted lookup definition and shows the Warning status for the return value 1.

Created on Apr 2, 2014 2:23:29 PM by  Gerald Schoch [Paessler Support]

Last change on Jun 29, 2022 12:45:30 PM by  Brandy Greger [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.