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-8005-Q2

Details

Predictive Self-Healing Article
The XSB could not be successfully configured into a domain.

Type

Upset

  upset.chassis.domain.config

Severity

Major

Description

The XSB could not be successfully configured into a domain.

Automated Response

Nothing is deconfigured.

Impact

XSB is not successfully configured into a domain.

Suggested Action for System Administrator

The platform administrator should investigate why the XSB could not be configured into the domain. Please consult the detail section of the knowledge article for additional information.

Details

The XSB could not be successfully configured into a domain.

The reason why the XSB could not be configured into the domain can be determined
from the ereport class of the associated ereport. The possible reasons are:

   no-mem
   Either the XSB has no memory or all the memory in the XSB has been deconfigured due to a prior fault.

   no-cpu
   Either the XSB has no CPU chip or all the CPU chips in the XSB have been deconfigured due to a prior fault.

   faulty-component
   A component in the XSB has been diagnosed as faulty and the configuration rules for this domain don't allow    
   XSB's with faulty components.


The system administrator should:

   Verify that sufficient memory or CPU chips are populated on the XSB;
 
   Verify that no memory or CPU chips were deconfigured as a result of a previous fault;

   Examine output displayed to the XSCF console and XSCF logs files to identify if a fault had occurred;

       XSCF> fmdump -m
       XSCF> fmdump -v
   
   Refer to the document "SPARC Enterprise M4000/M5000/M8000/M9000 Servers Administration Guide"
   for the procedures to set up and manage domains with XSCF firmware.


   If the problem persists, proceed with the steps outlined below.


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


   Single-line fault message displayed on the XSCF console:

   Mar 20 21:41:04 san-ff2-21-0 fmd: SOURCE: sde, REV: 1.12, CSN: 7860000772  
   EVENT-ID: 352c2c49-9227-4e6a-8264-e3bc4574f905
   Refer to http://www.sun.com/msg/SCF-8005-Q2 for detailed information.


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

   MSG-ID: SCF-8005-Q2, TYPE: Upset, VER: 1, SEVERITY: Major
   EVENT-TIME: Tue Mar 20 21:41:04 UTC 2007
   PLATFORM: SPARC-Enterprise, CSN: 7860000772, HOSTNAME: san-ff2-21-0
   SOURCE: sde, REV: 1.12
   EVENT-ID: 352c2c49-9227-4e6a-8264-e3bc4574f905
   DESC: The XSB could not be successfully configured into a domain.
   Refer to http://www.sun.com/msg/SCF-8005-Q2 for more information.
   AUTO-RESPONSE: Nothing is deconfigured.
   IMPACT: XSB is not successfully configured into a domain.
   REC-ACTION: The platform administrator should investigate why the XSB could not be configured
   into the domain. 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 352c2c49-9227-4e6a-8264-e3bc4574f905

         TIME                 UUID                                 MSG-ID
         Mar 20 21:41:04.1409 352c2c49-9227-4e6a-8264-e3bc4574f905 SCF-8005-Q2
           100%  upset.chassis.domain.config

                 Problem in: hc:///chassis=0/cmu=0/xsb=0
                    Affects: -
                        FRU: hc://:product-id=SPARC-Enterprise:chassis-id=7860000772:
                             server-id=san-ff2-21-0:
                             part=CA20393-B50X 001AA:revision=0101/component=/MBU_B


Step 3. Contact your Authorized Service Provider.


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

This solution has no attachment