MBU Degraded Status Cannot be Cleared on SPARC Enterprise M3000/M4000/M5000 Running XCP1114

Asset ID:	1-77-1538391.1
Update Date:	2017-11-27
Keywords:

Solution Type Sun Alert Sure

Solution 1538391.1 : MBU Degraded Status Cannot be Cleared on SPARC Enterprise M3000/M4000/M5000 Running XCP1114

Applies to:

Sun SPARC Enterprise M4000 Server
Sun SPARC Enterprise M3000 Server
Sun SPARC Enterprise M5000 Server
Sun Hardware - Generic
SPARC
_______________________________________

Date of Workaround Release: 20-Mar-2013

Date of Resolved Release: 30-Apr-2013
_______________________________________

Description

On SPARC Enterprise M3000, M4000 and M5000 systems running XCP 1114 firmware, the 'degraded' status of an MBU (Motherboard Unit) cannot be cleared even after replacing any hardware suspected of being faulty or running the 'clearfault' command. This issue may lead to unnecessary hardware replacement.

Note: Once the underlying fault has been addressed, the erroneously reported degraded MBU status will have no impact on the domain operation which can be safely started.

Occurrence

This issue can occur on the following platforms:

SPARC Platform

Sun SPARC Enterprise M3000/M4000/M5000 systems with XCP 1114 firmware and without XCP 1115 firmware

showing an MBU with a status of "degraded".

Note: Sun SPARC Enterprise M8000/M9000 systems are not impacted by this issue.

To determine the XCP firmware version on the system, run the following command at the eXtended System Control Facility (XSCFU) shell:

      XSCF> version -c xcp

XCP 1114 output will appear similar to the following:

     XSCF> version -c xcp
     XSCF#0 (Active )
     XCP0 (Reserve): 1114
     XCP1 (Current): 1114
     XSCF>

To determine whether an MBU is degraded, run the following command on the XSCFU:

     XSCF> showstatus
     MBU_A Status:Degraded;

Symptoms

Should the described issue occur, the degraded status of an MBU cannot be cleared, even after replacing any hardware suspected of being faulty or running the 'clearfault' command.

Workaround

Downgrading to an older firmware release is not recommended because it may lead to other system issues. This issue is harmless once the originally reported failure has been resolved.

This issue is addressed on the following platforms:

SPARC Platform

Sun SPARC Enterprise M3000 systems with XCP 1115 firmware as delivered in patch 16687241 or later
Sun SPARC Enterprise M4000 systems with XCP 1115 firmware as delivered in patch 16687246 or later
Sun SPARC Enterprise M5000 systems with XCP 1115 firmware as delivered in patch 16687248 or later

Note: After upgrading to XCP1115, use the clearfault command to clear the MBU degraded status. If this fails to clear the MBU degraded status, then disconnect the server from its power source, wait 30 seconds, then reconnect it.

For additional information, please see <Document:1002631.1>: "Sun SPARC[TM] Enterprise M3000, M4000, M5000, M8000, M9000 XSCF Control Package (XCP) Firmware Image Software Version Matrix Information"

Patches

<PATCH:16687241>
<PATCH:16687246>
<PATCH:16687248>

History

20-Mar-2013: Document released, status Workaround
30-Apr-2013: Updated for release of XCP 1115, issue is Resolved
11-Jun-2013: Additional Note added to Workaround/Resolution for post-upgrade instructions

This regression (BUG 16242988) was introduced by the bug 15724455 which
was delivered in XCP firmware 1114. XCP firmware 1114 has been withdrawn.

Internal <Document:1533895.1> is being used by TSC to avoid unnecessary hardware replacement:
Sun SPARC(R) Enterprise M3000/M4000/M5000 : Cannot clear the MBU "Degraded" status

Questions regarding this document should be addressed to
sunalertpublication_us_grp@oracle.com and copy the
responsible Engineer listed below.

Internal Contributor/Submitter: alex.aftandilian@oracle.com
Internal Eng Responsible Engineer: alex.aftandilian@oracle.com
Internal Knowledge Analyst: david.mariotto@oracle.com
Internal Eng Business Unit Group: Systems RPE
Internal Escalation ID: 3-6877092621, 3-6565932831,
3-6662112661, 3-6779306191, 3-6872388101

References

Attachments

This solution has no attachment