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-PX

Scope

Details

Predictive Self-Healing Article
The XSCF has detected that a Solaris domain has panic'ed.

Type

Upset

  upset.chassis.domain.panic

Severity

Major

Description

The XSCF has detected that a Solaris domain has panic'ed.

Automated Response

No action is taken due to this fault.

Impact

The Solaris domain has panic'ed.

Suggested Action for System Administrator

The administrator should look at the domain's console to identify the cause of the panic. Please consult the detail section of the knowledge article for additional information.

Details

The XSCF has detected that a Solaris domain has panic'ed.

The reason for the domain panic is unknown by XSCF software.

*** THERE IS NO DIAGNOSIS PERFORMED BY THE XSCF ***

The domain panic could be due to either a hardware or software problem.

The domain will attempt to save the error telemetry and then perform diagnosis on system reboot.

In the event the system is unable to save the error telemetry or produce an automated diagnosis,
then the information from the system console may be useful in attempting to manually diagnose the domain panic.

The system administrator should examine output displayed to the XSCF console, domain's console,
domain logs files (/var/adm/messages, fmdump -v) and XSCF logs files (fmdump -m, fmdump -v) to
gain a further understanding of the problem.

  If there is no explanation why the domain panic'ed,  then proceed with the steps outlined below.

1. Collect diagnostics data:
   1. In most cases a snapshot from the main XSCFU will be required to quickly and accurately identify the issue. 
      See Document 1533993.1 - Gathering diagnostic data for SPARC Enterprise M3000/M4000/M5000/M8000/M9000 (OPL) Servers.
   2. In the event of a software panic and some hardware panics a domain explorer will also be needed.
   3. Corefiles generated from the panic should be saved and may need to be uploaded ( See Document 1020199.1 ).
      
      
2. Gather the snapshot and explorer data bundles and contact your Authorized Service Provider. 
   
   1. See Document 1010911.1 - What Should I Send to Oracle After a Solaris Panic or Unexpected Reboot?
      
      

This solution has no attachment