SNMP HP System Health - Disk Controller Status Alerts

Hello there, we appreciate your KB-Post.

The observed behavior is expected. Please note that as some other channels from this sensor, it uses the "prtg.standardlookups.hp.status" lookup-file for status-evaluation:

      <SingleInt state="None" value="1">Other</SingleInt>
      <SingleInt state="Ok" value="2">OK</SingleInt>
      <SingleInt state="Warning" value="3">Degraded</SingleInt>
      <SingleInt state="Error" value="4">Failed</SingleInt>

PRTG is receiving the value 3 as the result from an SNMP Query, the prtg.standardlookups.hp.status lookup-file is responsible to translate theses integer values to a PRTG-compatible status.

Performing the suggested change should be simple, please refer to these instructions:

• 1. Head to the sensor's overview, click on the mentioned channel Disk Controller Status and check the Value Lookup field. It will most likely be set to prtg.standardlookups.hp.status
• 2. In the server were your PRTG Core Server runs, head to C:\Program Files (x86)\PRTG Network Monitor\lookups\ and locate the file called prtg.standardlookups.hp.status.ovl.
• 3. Copy said file to the \custom\ sub-folder. This prevents the file from being overwritten when you update PRTG.
• 4. Edit the file and modify the lookup, so that the line that refers to the "Degraded" status looks like the following:

      <SingleInt state="Error" value="3">Degraded</SingleInt>

• 5. Head back to PRTG's web-interface, within Setup > Administrative Tools perform a Re-Load Lookups.
• 6. The sensor will re-evaluate it's lookups on the next scanning interval, on which it should swich from Warning to Down(Error).
  
  These instructions are generic and apply to any sensor that uses lookups (SNMP printer, SSL Security Check, ...).

Important Notes

• Please beware that modifying the prtg.standardlookups.hp.status will affect the behavior of ALL sensors and channels that use this lookup. You may want to create a different lookup only for a specific set of sensors and channels, please refer to this guide instead.
• The Re-load Lookups is mandatory for PRTG to parse and reload any lookups modified since the last restart. If there's a syntax error in the lookup-file, you should get a PRTG Ticket telling you about it.
• Sometimes when importing a MIB File lookups will be generated automatically, but their status will always be green and the gauge will be grey. Lookups created by SNMP Library sensors have to be adjusted after their creation, their default status is "None":

<?xml version="1.0" encoding="UTF-8"?>
  <ValueLookup id="oid.ups-mib.upsconfig.upsconfigaudiblestatus" desiredValue="1" undefinedState="olsNone">
    <Lookups>
      <SingleInt state="None" value="1">disabled</SingleInt>
      <SingleInt state="None" value="2">enabled</SingleInt>
      <SingleInt state="None" value="3">muted</SingleInt>
    </Lookups>
  </ValueLookup>

More

For further understanding of lookups, please refer to the following:

• KB: Value interpretation (aka Lookups)
• KB: Monitor and "Lookup" a SNMP String value
• PRTG Manual: Define Lookups
• KB: Range-based lookup(example)
• Video: How to Configure Lookups in PRTG Network Monitor

Best Regards,
Luciano Lingnau [Paessler Support]