Firmware 3.06 and drive OIDS

[winadm]

Good day!

We have recently updated the firmware on a couple of our servers to 3.06 and now we get strange values of used OIDs, that we can't find in any mibs:

cpqDaCntlrBoardStatus returns 8

cpqDaPhyDrvStatus returns 10

Also very strange behavior of cpqDaPhyDrvConfigurationStatus - returns 3, that indicates "notConfigured" in old mibs, which is very strange since the drive is configured as spare drive.

Can anyone provide the fresh mib for first two OIDs and explain why the status returns 3 for spare drive?

[Suman_1978]

Hi,

It would be helpful if you could mention which firmware you updated and what is the server model.

For your reference, please check these links for SNMP Alerts.
https://support.hpe.com/hpesc/public/docDisplay?docId=c05315472
https://support.hpe.com/hpesc/public/docDisplay?docId=c04131162
https://support.hpe.com/hpesc/public/docDisplay?docId=sd00003116en_us&page=GUID-F0AAC44A-BE05-4016-95AA-D5368D857D43.html

Thank You!
I work with HPE but opinions expressed here are mine.

[BPSingh]

Greetings!

Have you tried downgrading the iLO firmware to the working revision?

[winadm]

Hm, no, we haven't tried to downgrade. It sounds quite strange to downgrade the firmware because we don't have full information for some SNMP oids.

[winadm]

Server model is  HP(E) ProLiant DL360 Gen10 Plus. The firmware was 3.01, we have updated to 3.06.

Unfortunately, I didn't manage to find the answers for questions in the provided links. Looks like it is not mentioned cpqDaPhyDrvStatus OID with value 10 anywhere. Maybe we have outdated CPQIDA-MIB?

snmpwalk -v3  -l authPriv -u  -a SHA -A  -x AES -X  server 1.3.6.1.4.1.232.3.2.5.1.1.6
iso.3.6.1.4.1.232.3.2.5.1.1.6.12.0 = INTEGER: 2
iso.3.6.1.4.1.232.3.2.5.1.1.6.12.1 = INTEGER: 2
iso.3.6.1.4.1.232.3.2.5.1.1.6.12.2 = INTEGER: 2
iso.3.6.1.4.1.232.3.2.5.1.1.6.12.3 = INTEGER: 10

and for cpqDaCntlrBoardStatus

snmpwalk -v3  -l authPriv -u  -a SHA -A  -x AES -X  server 1.3.6.1.4.1.232.3.2.2.1.1.10
iso.3.6.1.4.1.232.3.2.2.1.1.10.12 = INTEGER: 8

[BPSingh]

Please ensure, you are using latest MIB KIT. 

Windows:
https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-UNITY_C7843&tab=Fixes&softwareId=MTX_672861d3159d42f4bef2607803

and then
https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_a85af317be96442da0e72c2d93

The Document -- https://www.hpe.com/psnow/doc/a50006146enw , has all the supported MIB details.

[winadm]

Great!

Mibs pack from the second link contains the fresh cpqida.mib, which contains all the new statuses. One question left - is status notConfigured forcpqDaPhyDrvConfigurationStatus on hotspare disk, which sounds not critical at all.

snmpwalk -v3  -l authPriv -u -a SHA -A  -x AES -X server 1.3.6.1.4.1.232.3.2.5.1.1.58
iso.3.6.1.4.1.232.3.2.5.1.1.58.12.0 = INTEGER: 2
iso.3.6.1.4.1.232.3.2.5.1.1.58.12.1 = INTEGER: 2
iso.3.6.1.4.1.232.3.2.5.1.1.58.12.2 = INTEGER: 2
iso.3.6.1.4.1.232.3.2.5.1.1.58.12.3 = INTEGER: 3

[BPSingh]

What is the return value that you see for cpqDaPhyDrvStatus on the spare drive?

[winadm]

@BPSingh 

snmpwalk -v3  -l authPriv -u  -a SHA -A -x AES -X  server 1.3.6.1.4.1.232.3.2.5.1.1.6
iso.3.6.1.4.1.232.3.2.5.1.1.6.12.0 = INTEGER: 2
iso.3.6.1.4.1.232.3.2.5.1.1.6.12.1 = INTEGER: 2
iso.3.6.1.4.1.232.3.2.5.1.1.6.12.2 = INTEGER: 2
iso.3.6.1.4.1.232.3.2.5.1.1.6.12.3 = INTEGER: 10

Thats exactly "Hotspare" in the fresh mibs.

     cpqDaPhyDrvStatus OBJECT-TYPE
        SYNTAX  INTEGER
        {
            other(1),
            ok(2),
            failed(3),
            predictiveFailure(4),
            erasing(5),
            eraseDone(6),
            eraseQueued(7),
            ssdWearOut(8),
            notAuthenticated(9),
			Hotspare(10)
        }

[BPSingh]

Starting from iLO5 version 3.04, the return value for a spare disk has been updated to Hotspare(10). This is working as per design.