Sun Fire [TM] V880 OBP and DPM firmware mismatch may cause false obdiag onboard fcal controller failures

Asset ID:	1-72-1008187.1
Update Date:	2018-02-15
Keywords:

Solution Type Problem Resolution Sure

Solution 1008187.1 : Sun Fire [TM] V880 OBP and DPM firmware mismatch may cause false obdiag onboard fcal controller failures

Applies to:

Sun Fire V880 Server - Version Not Applicable to Not Applicable [Release N/A]
Sun Fire V880z Visualization Server - Version Not Applicable to Not Applicable [Release N/A]
All Platforms

Symptoms

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community - SPARC Legacy Servers

Sun Fire[TM] V880 systems with older DPM firmware, 9228 or earlier, may see false obdiag failures when they upgrade to 4.18.x OBP or later.

When running obdiag with diag-level set to MAX you may see the onboard fcal controller "/pci@8,600000/SUNW,qlc@2" fail incorrectly with this mismatch. When the false failure takes place this causes the system to become unbootable as the onboard fcal controller will be ASR'd out of the system. See example below:

obdiag> test 1
Hit the spacebar to interrupt testing
Testing /pci@8,600000/SUNW,qlc@2
Subtest pci-config-regs-tests
Subtest pci-registers-walk1
Subtest test-mbox-reg
Subtest test-risc-ram
Subtest mats-test
>> Testing RISC RAM (this may take a while)..........
Subtest loop-tests
>> Firmware copied
>> Waiting for loop to come up.
>> Waiting for firmware ready state
Subtest loop-tests:lip-test
Subtest loop-tests:lip-map-test
>> FCAL device count = 0xd
>> Found device with loop ID 0x7d (AL_PA = 0x1 )
>> Found device with loop ID 0x0 (AL_PA = 0xef )
>> Found device with loop ID 0x1 (AL_PA = 0xe8 )
>> Found device with loop ID 0x6 (AL_PA = 0xdc )
>> Found device with loop ID 0x3 (AL_PA = 0xe2 )
>> Found device with loop ID 0x44 (AL_PA = 0x6c )
>> Found device with loop ID 0x5 (AL_PA = 0xe0 )
>> Found device with loop ID 0x8 (AL_PA = 0xd9 )
>> Found device with loop ID 0x9 (AL_PA = 0xd6 )
>> Found device with loop ID 0xa (AL_PA = 0xd5 )
>> Found device with loop ID 0xb (AL_PA = 0xd4 )
>> Found device with loop ID 0xc (AL_PA = 0xd3 )
>> Found device with loop ID 0xd (AL_PA = 0xd2 )
Subtest loop-tests:inquiry-test
>> ISP2200 found at loop ID 0x7d
Subtest loop-tests:inquiry-test:ses-test
>> Enclosure services device found at loopid 0x6
Subtest loop-tests:inquiry-test:ses-test:ses-alpa-map-test
Subtest loop-tests:inquiry-test:ses-test:loop-empty-tests
Subtest loop-tests:inquiry-test:ses-test:loop-empty-tests:ses-lip-test
Subtest loop-tests:inquiry-test:ses-test:loop-empty-tests:fibre-frame-loopback-test
Subtest loop-tests:inquiry-test:ses-test:loop-empty-tests:ses-lip-test
Subtest loop-tests:inquiry-test:ses-test:ses-alpa-map-test
Subtest loop-tests:inquiry-test:ses-test:fibre-frame-loopback-test
ERROR : ISP2200 RISC engine did not generate expected interrupt.
DEVICE : /pci@8,600000/SUNW,qlc@2
SUBTEST : selftest:loop-tests:inquiry-test:ses-test:fibre-frame-loopback-test
CALLERS : (f0120b1c)
MACHINE : Sun Fire 880
SERIAL# : 51045419
DATE : 01/29/2007 20:29:10 GMT
CONTR0LS: diag-level=max test-args=verbose,subtests,error=5
Error: /pci@8,600000/SUNW,qlc@2 selftest failed, return code = 1
Selftest at /pci@8,600000/SUNW,qlc@2 (errors=1) ....................... failed
Pass:1 (of 1) Errors:1 (of 1) Tests Failed:1 Elapsed Time: 0:0:1:8

Cause

OBP and DPM firmware mismatch

4493252 WRONG PACKET error seen by dpmtest's loopback subtest

Solution

To resolve the problem the customer just needs to upgrade the DPM firmware to 922A or later so that the OBP/DPM firmware mismatch will no longer exist.

<sunpatch 117814-01> Sun Fire 880 & 890 Fibre-Channel Backplane Firmware patch

Current OBP firmware is available here:

How to Download Firmware for Oracle Systems and Storage Doc ID 1342226.1

Relief/Workaround

This will allow the system to boot normally until the DPM firmware can be properly upgraded during the next scheduled maintenance window. See example below of a passing obdiag run:

obdiag> test 1
Hit the spacebar to interrupt testing
Testing /pci@8,600000/SUNW,qlc@2
Subtest pci-config-regs-tests
Subtest test-mbox-reg
Subtest loop-tests
>> Firmware copied
>> Waiting for loop to come up.
>> Waiting for firmware ready state
Subtest loop-tests:lip-test
Subtest loop-tests:lip-map-test
>> FCAL device count = 0xd
>> Found device with loop ID 0x7d (AL_PA = 0x1 )
>> Found device with loop ID 0x0 (AL_PA = 0xef )
>> Found device with loop ID 0x1 (AL_PA = 0xe8 )
>> Found device with loop ID 0x6 (AL_PA = 0xdc )
>> Found device with loop ID 0x3 (AL_PA = 0xe2 )
>> Found device with loop ID 0x44 (AL_PA = 0x6c )
>> Found device with loop ID 0x5 (AL_PA = 0xe0 )
>> Found device with loop ID 0x8 (AL_PA = 0xd9 )
>> Found device with loop ID 0x9 (AL_PA = 0xd6 )
>> Found device with loop ID 0xa (AL_PA = 0xd5 )
>> Found device with loop ID 0xb (AL_PA = 0xd4 )
>> Found device with loop ID 0xc (AL_PA = 0xd3 )
>> Found device with loop ID 0xd (AL_PA = 0xd2 )
Selftest at /pci@8,600000/SUNW,qlc@2 .................................. passed
Pass:1 (of 1) Errors:0 (of 0) Tests Failed:0 Elapsed Time: 0:0:0:1

Additional Information
Please make note that you should only see this problem on V880 systems. V890 systems should not see the problem because they are shipped with the DPM firmware already at the 922A revision. A V890 system could only see the problem if someone physically downgraded the DPM firmware to an older version 9228 or earlier.

obdiag, v880, v890, DPM, firmware, OBP
Previously Published As
88604

References

Attachments

This solution has no attachment