What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

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 Dell PowerEdge System Health sensor show a power unit status error after iDRAC update?



After updating the iDRAC firmware on our Dell servers, the SNMP Dell System Health PowerEdge sensor now shows an error message

Error by lookup value ‘Other’ in Power Status

Why does this error suddenly appear? Does PRTG have a problem with iDRAC version What can I do to solve this?

dell dell-power-edge error idrac lookups poweredge prtg snmp

Created on Jan 23, 2017 2:38:27 PM by  Brandy Greger [Paessler Support]

Last change on Jan 24, 2017 11:08:55 AM by  Brandy Greger [Paessler Support]

5 Replies

Accepted Answer



This article applies as of PRTG 22

SNMP Dell PowerEdge System Health sensor and the error in power status after iDRAC firmware update

Following an update to your iDRAC firmware to, your SNMP Dell PowerEdge System Health sensor may report the following error:

Error by lookup value 'Other' in Power Unit Status

For some reason (we are not sure at this point, most likely it is a bug in the firmware), Power Units previously reported as 3 (OK) are now being reported as 1 (Other). The standard lookup that PRTG uses maps this value to the Down status. This Other status is only reported via SNMP and not visible or apparent in the OMSA.

The standard lookup (prtg.standardlookups.dell.dellstatus) that this channel or sensor uses is based on the ObjectStatusEnum referenced by the relevant OID from the IDRAC-MIB below:

0200.0010.0001.0042 This attribute defines the combined status of all power units of this chassis.ObjectStatusEnum

This is the latest version of the MIB that is publicly available:

systemStatePowerUnitStatusCombined              OBJECT-TYPE
    SYNTAX      ObjectStatusEnum
    MAX-ACCESS  read-only
    STATUS      current
        "0200.0010.0001.0042 This attribute defines the combined status
        of all power units of this chassis."
    ::= { systemStateTableEntry 42 }

ObjectStatusEnum        ::= TEXTUAL-CONVENTION
    STATUS current
        "Status of an object."
    SYNTAX              INTEGER {
    other(1),          -- the status of the object is not one of the
                        --  following:
    unknown(2),        -- the status of the object is unknown
                        --  (not known or monitored)
    ok(3),              -- the status of the object is ok
    nonCritical(4),    -- the status of the object is warning, non-critical
    critical(5),        -- the status of the object is critical (failure)
    nonRecoverable(6)  -- the status of the object is non-recoverable (dead)

This MIB is dated July 7, 2015. Dell has not yet updated their MIBs, which also leads us to believe that this is a bug and not a change in the MIB. Please contact Dell and report the issue as they are in position to fix or adjust their SNMP agent.

PRTG is behaving correctly and displaying the status exactly as the iDRAC reports it via SNMP.

Check the correctness of the value with SNMP Tester

To confirm the value reported by your iDRAC/Server, we recommend that you download our latest SNMP Tester and follow the instructions below. If you already know that the value is correct, see Workaround: Change the sensor's behavior below.

  1. Run SNMP Tester on the PRTG host (or host of the remote probe).
  2. Set the Device IP/Port, SNMP Version and Community exactly as set in PRTG.
  3. Select Walk as the Request Type.
    • Use the OID:
  4. Check the output. An affected server looks like the following:
----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 Computername: MYPROBE Interface:
01/02/2017 09:58:49 (2 ms) : Device: MYTARGETSERVERIDRAC
01/02/2017 09:58:49 (3 ms) : SNMP V2c
01/02/2017 09:58:49 (4 ms) : Walk
01/02/2017 09:58:49 (5 ms) : = "1" [ASN_INTEGER]

If this error is not displayed in the OMSA/iDRAC web interface, but reported as 1 (Other) via SNMP, you are affected. In this case, we advise you to report this discrepancy to Dell to allow them to fix the issue. Refer to Workaround: Change the sensor's behavior below if you wish to modify the alerting behavior of PRTG in the meantime.

Workaround: Change the sensor's behavior

To solve this issue, redefine the sensor behavior in the lookup file that is used for the affected channel.

Warning: With the following instructions, you configure your Dell PowerEdge sensors to ignore the Other status, which applies to all channels and sensors that use this lookup. You may also not be alerted when something goes wrong because you are no longer using the standard status mapping in PRTG.

  1. Go to the \lookups folder in the PRTG program directory and copy the file prtg.standardlookups.dell.dellstatus.ovl into the \custom subfolder. This is good practice because the lookups in the \custom subfolder are not overwritten when you update PRTG.
  2. Open your copy from the \custom subfolder in a text editor.
  3. In the lookup definition, go to line 4:
    <SingleInt state="Error" value="1">
    and change it to
    <SingleInt state="OK" value="1">
  4. Save your changes.
  5. In PRTG, reload the lookup files: Open Setup | System Administration | Administrative Tools | Load Lookups and click Go!.
  6. Starting from the next sensor scan, PRTG reports the value of 1 (Other) on any Dell equipment that uses the ObjectStatusEnum (in PRTG, prtg.standardlookups.dell.dellstatus) as OK (no alerts).

Once the issue has been addressed by Dell and the status of the Power Units is once again reported as OK, simply delete the lookup in the \custom subfolder. Then reload the lookup files from the PRTG web interface. This way, you revert to the original lookup. For more details, see PRTG Manual: Define Lookups, section Customizing Lookups.

Note: If you are familiar with lookups, it is also possible to give a new name and ID to the prtg.standardlookups.dell.dellstatus, for example prtg.standardlookups.dell.dellstatus.psbug, then perform the modification. This requires you to additionally configure the Power Unit Status channel of any affected sensor to use this lookup instead. However, it also allows you to modify the behavior ONLY for the affected channel and not for all sensors and channels that use the prtg.standardlookups.dell.dellstatus.


Created on Jan 24, 2017 11:09:56 AM by  Brandy Greger [Paessler Support]

Last change on Sep 18, 2023 9:16:43 AM by  Jacqueline Conforti [Paessler Support]



Solution from Dell Support:

  1. Login to iDRAC
  2. Check Power / Thermal -> Power Configuration -> Power Supply Options -> Redundancy Policy
  3. Change Redundancy Policy to Input Power Redundant

Created on Jun 23, 2017 1:23:06 PM

Last change on Jun 23, 2017 1:45:18 PM by  Luciano Lingnau [Paessler]



From my experience, the solution provided by Dell (as per above) does not work. Also the problem still seems to exist in iDRAC version

Created on Oct 3, 2017 2:57:42 AM



Florian's response was the fix for mine! I had to update the Controller Driver version to 6.803.21.00 using the .exe provided by MS in addition to changing redundancy to Input Power Redundant. All Green now.

iDRAC Version here.

Created on Nov 6, 2017 6:41:43 PM



Thanks Florian! This worked for me too.

PowerEdge R720
BIOS Version 2.5.4
iDRAC 7 Hardware Version 0.01
iDRAC 7 Firmware Version

FYI - this is from the Help in iDRAC:

Redundancy Policy

  • Not Redundant — In this mode, failure of a single PSU can power off the system.
  • Input Power Redundant — In this mode, the system is functional in the event of failure of a PSU input circuit, provided the PSUs are connected to different input circuits. This is also called AC redundancy.
  • PSU Redundant — Only available on systems with four PSUs. This is also called DC redundancy. This is only valid in a 2+1 PSU configuration. In this mode, the system is functional in the event of failure of a single PSU.

Created on Nov 7, 2017 7:47:17 PM

Last change on Nov 8, 2017 7:41:45 AM by  Luciano Lingnau [Paessler]

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.