HPE Servers shows only a few physical disks even though the server contains many more in SolarWinds Platform

2/18/2026 3:19 PM

2/18/2026 4:12 PM

The issue happens on the following environment:

• Node is an HPE ProLiant / Apollo Gen10 server polled via SNMP (SnmpHP).

• Current Hardware Health (Disks category) shows only a small subset of disks, typically:

  • OS/system disks on the onboard controller (for example, E208i).

• Additional data/backup disks (for example, on a P408i PCIe controller) are not listed in Hardware Health.

• Hardware Health logs contain an error like in LogFiles\Logs_Agent\HardwareHealth\HardwareHealth.Collector.Jobs_<JobID>.log:

INFO  SolarWinds.Orion.Pollers.Framework.PollerBase - Polling of Primary Disk OID failed. [NodeID = 136, PollingMethod = SnmpHP]
(System.Exception: Can't find member for value '10' in enum 'HPPhysicalDriveStatus'. 
   at SolarWinds.HardwareHealth.Contract.EnumHelper.GetAttribute[TEnum,TAttribute](TEnum enumValue)
   at SolarWinds.HardwareHealth.Pollers.HardwareHealth.SNMP.HardwareHealthSnmpPoller.SetOrionStatus[T](HardwareHealthSensorInfo sensorInfo, T sensorStatus)
   at SolarWinds.HardwareHealth.Pollers.HardwareHealth.SNMP.SAM.HPHardwareHealthSnmpPoller.PollSecondaryDiskTable(List`1 sensors)
   at SolarWinds.HardwareHealth.Pollers.HardwareHealth.SNMP.SAM.HPHardwareHealthSnmpPoller.PollSensor(...))

Orion Platform

This is caused by the device returning an unsupported status value (10) for cpqDaPhyDrvStatus, which interrupts disk polling and prevents the rest of the disks from being processed.

1. HPE disk status OID and expected values

SolarWinds uses the HPE/Compaq disk MIB cpqDaPhyDrvTable under:

• 1.3.6.1.4.1.232.3.2.5.1.1 (cpqDaPhyDrv* columns)

• Disk status column:
  cpqDaPhyDrvStatus = 1.3.6.1.4.1.232.3.2.5.1.1.6

According to the documented MIB for cpqDaPhyDrvStatus, only the following values are valid:

1 = other
2 = ok
3 = failed
4 = predictiveFailure
5 = erasing
6 = eraseDone
7 = eraseQueued
8 = ssdWearOut
9 = notAuthenticated

2. Device returns an unsupported status 10

On the affected servers, at least one physical drive reports:

.1.3.6.1.4.1.232.3.2.5.1.1.6.x.y = INTEGER: 10

10 is not defined in the MIB’s cpqDaPhyDrvStatus (https://oid-base.com/get/1.3.6.1.4.1.232.3.2.5.1.1.6) enumeration. The Hardware Health poller attempts to map the SNMP value into the internal enum HPPhysicalDriveStatus. Because there is no member for value 10, the mapping throws:

Can't find member for value '10' in enum 'HPPhysicalDriveStatus'.

This exception occurs inside PollSecondaryDiskTable, and disk polling is aborted for that cycle:

• Disks processed before the bad row (for example, OS disks on controller 0) are already collected and displayed.

• Disks processed after the bad row (typically the data/backup disks) are skipped for that poll, so they never appear as Hardware Health sensors.

The problem is not the controller index being 2 itself; the issue is the unexpected status value 10 that breaks the enum mapping and interrupts polling.

Resolution / Workarounds

1. Update HPE firmware / agents

Because 10 is outside the documented range for cpqDaPhyDrvStatus, the first remediation should be on the device side:

1. Update to the latest supported versions on the affected server:

   • iLO firmware

   • Smart Array controller firmware (E208i, P408i, etc.)

   • Any HPE SNMP/AMS/agentless management packages in use.

2. Re-run the SNMP walk for 1.3.6.1.4.1.232.3.2.5.1.1.6 and confirm all values are now in the 1–9 range (especially 2 = ok).

3. After the next few poll cycles, verify that:

   • The Hardware Health log no longer shows the HPPhysicalDriveStatus error.

   • Additional disks (for example, those on the P408i) begin to appear under Current Hardware Health → Disks.

If the device still returns 10 after a full firmware/agent update, collect:

• Fresh SNMP walk for the cpqDaPhyDrv* subtree (at least 1.3.6.1.4.1.232.3.2.5.1.1).

• Vendor documentation (if available) that explains what status 10 is supposed to mean.

Then open a case with HPE indicating:

The server returns cpqDaPhyDrvStatus = 10 for some drives, but the published MIB for cpqDaPhyDrvStatus (1.3.6.1.4.1.232.3.2.5.1.1.6) only documents values 1–9.