iDRAC10: VoltageProbeStatus, TableEntry, StatusProbeEnum OID have Integer Status 2, Unknown

Summary: When SNMPwalk is run against OID .1.3.6.1.4.1.674.10892.5.4.600.20.1.5.1 on iDRAC10, a status code of 2 (Unknown) on firmware version 1.20.25.00 and 1.20.50.50 is returned.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

When SNMPwalk is run against OID .1.3.6.1.4.1.674.10892.5.4.600.20.1.5.1 on iDRAC10, a status code of 2 (Unknown) on firmware version 1.20.25.00 and 1.20.50.50 is returned.

SNMPwalk on the same OID run against an iDRAC9 device results in correct information.

Error output:

snmpwalk -v 2c -c public <IP_ADDRESS> .1.3.6.1.4.1.674.10892.5.4.600.20.1.5.1 -O n
.1.3.6.1.4.1.674.10892.5.4.600.20.1.5.1.1 = INTEGER: ok(3)
.1.3.6.1.4.1.674.10892.5.4.600.20.1.5.1.2 = INTEGER: ok(3)
.1.3.6.1.4.1.674.10892.5.4.600.20.1.5.1.3 = INTEGER: ok(3)
.1.3.6.1.4.1.674.10892.5.4.600.20.1.5.1.4 = INTEGER: ok(3)
.1.3.6.1.4.1.674.10892.5.4.600.20.1.5.1.5 = INTEGER: ok(3)
.1.3.6.1.4.1.674.10892.5.4.600.20.1.5.1.6 = INTEGER: ok(3)
.1.3.6.1.4.1.674.10892.5.4.600.20.1.5.1.7 = INTEGER: ok(3)
.1.3.6.1.4.1.674.10892.5.4.600.20.1.5.1.8 = INTEGER: ok(3)
.1.3.6.1.4.1.674.10892.5.4.600.20.1.5.1.9 = INTEGER: ok(3)
.1.3.6.1.4.1.674.10892.5.4.600.20.1.5.1.10 = INTEGER: ok(3)
.1.3.6.1.4.1.674.10892.5.4.600.20.1.5.1.11 = INTEGER: ok(3)
.1.3.6.1.4.1.674.10892.5.4.600.20.1.5.1.12 = INTEGER: ok(3)
.1.3.6.1.4.1.674.10892.5.4.600.20.1.5.1.13 = INTEGER: unknown(2)
.1.3.6.1.4.1.674.10892.5.4.600.20.1.5.1.14 = INTEGER: unknown(2)
.1.3.6.1.4.1.674.10892.5.4.600.20.1.5.1.15 = INTEGER: unknown(2)
.1.3.6.1.4.1.674.10892.5.4.600.20.1.5.1.16 = INTEGER: unknown(2)
.1.3.6.1.4.1.674.10892.5.4.600.20.1.5.1.17 = INTEGER: unknown(2)
.1.3.6.1.4.1.674.10892.5.4.600.20.1.5.1.18 = INTEGER: unknown(2)
.1.3.6.1.4.1.674.10892.5.4.600.20.1.5.1.19 = INTEGER: unknown(2)
.1.3.6.1.4.1.674.10892.5.4.600.20.1.5.1.20 = INTEGER: unknown(2)

Steps on how to figure out what is the textual convention of the result from the MIB file:

  • From the iDRAC MIB files, you can see that voltageProbeTableEntry .1.3.6.1.4.1.674.10892.5.4.600.20.1.5 has voltageProbeStatus as the OBEJECT-TYPE
voltageProbeStatus                              OBJECT-TYPE
    SYNTAX      StatusProbeEnum
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "0600.0020.0001.0005 This attribute defines the probe status of the
        voltage probe."
    ::= { voltageProbeTableEntry 5 }
  • voltageProbeStatusTableEntry has the SEQUENCE as StatusProbeEnum
VoltageProbeTableEntry                          ::= SEQUENCE {
    voltageProbechassisIndex                    ObjectRange,
    voltageProbeIndex                           ObjectRange,
    voltageProbeStateCapabilities               StateCapabilitiesFlags,
    voltageProbeStateSettings                   StateSettingsFlags,
    voltageProbeStatus                       StatusProbeEnum,
    voltageProbeReading                         Signed32BitRange,
    voltageProbeType                            VoltageTypeEnum,
    voltageProbeLocationName                    String64,
    voltageProbeUpperNonRecoverableThreshold    Signed32BitRange,
    voltageProbeUpperCriticalThreshold          Signed32BitRange,
    voltageProbeUpperNonCriticalThreshold       Signed32BitRange,
    voltageProbeLowerNonCriticalThreshold       Signed32BitRange,
    voltageProbeLowerCriticalThreshold          Signed32BitRange,
    voltageProbeLowerNonRecoverableThreshold    Signed32BitRange,
    voltageProbeProbeCapabilities               ProbeCapabilitiesFlags,
    voltageProbeDiscreteReading                 VoltageDiscreteReadingEnum
  • The Textual Convention for all valid parameters for StatusProbeEnum is given below. Status 2 is for Unknown.
STATUS current
    DESCRIPTION
        "Probe Status enum."
    SYNTAX              INTEGER {
    other(1),               -- probe status is not one of the following:
    unknown(2),            -- probe status is unknown (not known or monitored)
    ok(3),                  -- probe is reporting a value within the thresholds
    nonCriticalUpper(4),    -- probe has crossed upper noncritical threshold
    criticalUpper(5),       -- probe has crossed upper critical threshold
    nonRecoverableUpper(6), -- probe has crossed upper non-recoverable threshold
    nonCriticalLower(7),    -- probe has crossed lower noncritical threshold
    criticalLower(8),       -- probe has crossed lower critical threshold
    nonRecoverableLower(9), -- probe has crossed lower non-recoverable threshold
    failed(10)              -- probe is not functional
}

Cause

There is a discrete sensor which was not refreshing the ProbeStatus and hence, the incorrect data that was getting populated. This has now been fixed in a later version of iDRAC10 after which the correct data has started to flow in.

Resolution

iDRAC Engineering has root caused the issue, and the fix is available in iDRAC10 version 1.20.70.50.

Affected Products

iDRAC10 - 1.20.xx Series
Article Properties
Article Number: 000358598
Article Type: Solution
Last Modified: 02 Oct 2025
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.