Sun SPARC Enterprise M8000 Server
 
Sun SPARC Enterprise M4000 Server
 
Sun SPARC Enterprise M3000 Server
 
Sun SPARC Enterprise M9000-32 Server
 
Sun SPARC Enterprise M5000 Server
 
Sun SPARC Enterprise M9000-64 Server
 

PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: Sun PSH
 

Applies to:

Purpose

Provide additional information for message ID: SCF-8003-K5

Details

Predictive Self-Healing Article
Non-fatal uncorrectable error occurred on the interface between a MBC chip and the XSCF.

Type

Fault

  fault.chassis.SPARC-Enterprise.if.se-mbc-xscf

Severity

Critical

Description

A non-fatal uncorrectable error occurred on the interface between a MBC chip and the XSCF.

Automated Response

No immediate action is taken by XSCF software due to this fault. Resources associated with the faulty FRU will be deconfigured after the platform is power cycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed. This resource deconfiguration may cause the platform to become unbootable. Please consult the detail section of the knowledge article for additional information.

Impact

The non-fatal uncorrectable error trap may cause the domain to panic.

Suggested Action for System Administrator

Schedule a repair action to replace the affected Field Replaceable Unit (FRU), the identity of which can be determined using fmdump -v -u EVENT_ID. Please consult the detail section of the knowledge article for additional information.

Details

A non-fatal uncorrectable error occurred on the interface between a MBC chip and the XSCF.

No immediate action is taken by XSCF software due to this fault.
  
For non-TTY-oriented faults, the maintenance bus between the XSCF and the FRU in question is disconnected.

    This means the XSCF will:
        -lose all I2C and JTAG access to chips and devices on the FRU;
       - lose all DMA access to chips on the FRU;
       - lose all access to MBC registers;
       - lose all ability to diagnose faults on the FRU.

    If the FRU in question is a Motherboard or CMU, and this is a non-TTY-oriented fault,
    then the XSCF will:
       - lose all access to SRAM on the MBC chip;
       - lose all use of the SCF command interface using this MBC chip.


For TTY-oriented faults, the TTY interface for this MBC chip becomes unusable.


 
SPARC Enterprise M3000 platform:
 
   The XSCFU is located on the Motherboard Unit (MBU).

   If this is a TTY-oriented fault, then the domains lose access to the TTY interface and no further action is taken.
  
   If the FRU with the MBC chip is on the Motherboard, then the platform becomes unbootable.
 

SPARC Enterprise M4000 platform:

   If this is a TTY-oriented fault, then the domains lose access to the TTY interface and no further action is taken.
  
   If the FRU with the MBC chip is on the Motherboard,  then the platform will gradually become unbootable as domains try to reboot.


SPARC Enterprise M5000 platform:

   If this is a TTY-oriented fault, then if the domains using the half the Motherboard with the faulty TTY interface
   also use the other half the Motherboard, then the XSCF software will  switch the TTY interface to use the
   other half the Motherboard.   Otherwise, no immediate action is taken.

    If the FRU with the MBC chip is on the Motherboard, then the platform will gradually become unbootable as domains try to reboot.


SPARC Enterprise M8000 platform:

    If this is a TTY-oriented fault, then XSCF software will switch the TTY interface to another CMU
    that belongs to the domain (if there is a working TTY interface on another CMU in the domain).

    If there is no other CMU with a working TTY interface  in this domain,
    then the domains lose access to the TTY interface and no further action is taken.

    If this is not a TTY-oriented fault, then no immediate action is  taken.

    If the FRU with the MBC chip is a CMU, then the CMU is deconfigured as the domains using the CMU reboot.

    If the FRU with the MBC chip is an IOU, then the IOU is deconfigured after the domains using the IOU reboot.

    If the FRU with the MBC chip is a BP_A Backplane, then the platform will gradually become unbootable as domains try to reboot.


SPARC Enterprise M9000-32 platform:

    If this is a TTY-oriented fault, then XSCF software will switch the TTY interface to another CMU
    that belongs to the domain (if there is a working TTY interface on another CMU in the domain).

    If there is no other CMU with a working TTY interface  in this domain,
    then the domains lose access to the TTY interface and no further action is taken.

    If this is not a TTY-oriented fault, then no immediate action is  taken.

    If the FRU with the MBC chip is a CMU, then the CMU is deconfigured as the domains using the CMU reboot.

    If the FRU with the MBC chip is an IOU, then the IOU is deconfigured after the domains using the IOU reboot.

    If the FRU with the MBC chip is an XBU, then the crossbar way is deconfigured the next time the platform is restarted.

    If the FRU with the MBC chip is an active Clock Unit,  then the Clock Unit is deconfigured the next time the platform is restarted.    
    If the FRU with the MBC chip is a standby Clock Unit,  nothing is deconfigured.


SPARC Enterprise M9000-64 platform:

    If this is a TTY-oriented fault, then XSCF software will switch the TTY interface to another CMU
    that belongs to the domain (if there is a working TTY interface on another CMU in the domain).

    If there is no other CMU with a working TTY interface  in this domain,
    then the domains lose access to the TTY interface and no further action is taken.

    If this is not a TTY-oriented fault, then no immediate action is  taken.

    If the FRU with the MBC chip is a CMU, then the CMU is deconfigured as the domains using the CMU reboot.

    If the FRU with the MBC chip is an IOU, then the IOU is deconfigured after the domains using the IOU reboot.

    If the FRU with the MBC chip is an XBU, then the crossbar way is deconfigured the next time the platform is restarted.

    If the FRU with the MBC chip is an active Clock Unit,  then the Clock Unit is deconfigured the next time the platform is restarted.    
    If the FRU with the MBC chip is a standby Clock Unit,  nothing is deconfigured.

    If the FRU with the MBC chip is an XSCFU_C on the expansion cabinet:
       
           If there is a standby XSCFU, the XSCFU will failover to the standby XSCFU.
           If there is no standby XSCFU, then the platform becomes unbootable.



The recommended service action for this event is to schedule the replacement of the affected FRU's.


Step 1. Collect the fault message (use one of the following methods):


   Single-line fault message displayed on the XSCF console:

   Mar 20 21:21:34 san-ff2-21-0 fmd: SOURCE: sde, REV: 1.12, CSN: 7860000772  
   EVENT-ID: db9cf38c-7c65-46ea-b74d-0378a66c317e
   Refer to http://www.sun.com/msg/ SCF-8003-K5 for detailed information.


   Complete fault message using 'fmdump -m' on the XSCF console:

   MSG-ID:  SCF-8003-K5, TYPE: Fault, VER: 1, SEVERITY: Critical
   EVENT-TIME: Tue Mar 20 21:21:34 UTC 2007
   PLATFORM: SPARC-Enterprise, CSN: 7860000772, HOSTNAME: san-ff2-21-0
   SOURCE: sde, REV: 1.12
   EVENT-ID: db9cf38c-7c65-46ea-b74d-0378a66c317e
   DESC: A non-fatal uncorrectable error occurred on the interface between a MBC chip and the XSCF.
   Refer to http://www.sun.com/msg/SCF-8003-K5 for more information.
   AUTO-RESPONSE: No immediate action is taken by XSCF software due to this fault.
   Resources associated with the faulty FRU will be deconfigured after the platform is
   power cycled or after the domain reboots or after a Dynamic Reconfiguration operation
   is performed. This resource deconfiguration may cause the platform to become
   unbootable. Please consult the detail section of the knowledge article for additional information.
   IMPACT: The non-fatal uncorrectable error trap may cause the domain to panic.
   REC-ACTION: Schedule a repair action to replace the affected Field Replaceable Unit (FRU),
   the identity of which can be determined using fmdump -v -u EVENT_ID.
   Please consult the detail section of the knowledge article for additional information.


Step 2. Collect the output from the 'fmdump -v -u EVENT_ID' command


   
   SPARC Enterprise platform example:
 
   xscf> fmdump -v -u db9cf38c-7c65-46ea-b74d-0378a66c317e

         TIME                 UUID                                 MSG-ID
         Mar 20 21:21:34.3173 db9cf38c-7c65-46ea-b74d-0378a66c317e SCF-8003-K5
           66%  fault.chassis.SPARC-Enterprise.if.se-mbc-xscf

                Problem in: hc:///chassis=0/iou=0/mbc=0
                   Affects: hc:///chassis=0/iou=0
                       FRU: hc://:product-id=SPARC-Enterprise:chassis-id=7860000772:
                            server-id=san-ff2-21-0:
                            part=CA20393-B55X 001AA:revision=0101/component=/IOU#0

           33%  fault.chassis.SPARC-Enterprise.if.se-mbc-xscf

                Problem in: hc:///chassis=0/xscfu=0/mbc=0
                   Affects: hc:///chassis=0/iou=0
                       FRU: hc://:product-id=SPARC-Enterprise:chassis-id=7860000772:
                            server-id=san-ff2-21-0:
                            part=CA20393-B56X 001AA:revision=0101/component=/XSCFU


Step 3. Contact your Authorized Service Provider.



If you require additional information, please refer to Document 1002526.1.

Product
Other Server Models 1000-9999

Product_uuid
41751310-63d5-11d7-9179-89d0596b661d

This solution has no attachment