SPARC Enterprise(R) M3000/M4000/M5000/M8000/M9000 Servers: ASR: SCF-8005-PX - XSCF has Detect a Solaris Domain has Panic'ed

Asset ID:	1-79-1542111.1
Update Date:	2017-04-27
Keywords:

Solution Type Predictive Self-Healing Sure

Solution 1542111.1 : SPARC Enterprise(R) M3000/M4000/M5000/M8000/M9000 Servers: ASR: SCF-8005-PX - XSCF has Detect a Solaris Domain has Panic'ed

Applies to:

Sun SPARC Enterprise M9000-64 Server - Version Not Applicable and later
Sun SPARC Enterprise M4000 Server - Version Not Applicable and later
Sun SPARC Enterprise M5000 Server - Version Not Applicable and later
Sun SPARC Enterprise M3000 Server - Version Not Applicable and later
Sun SPARC Enterprise M8000 Server - Version Not Applicable and later
Information in this document applies to any platform.

Purpose

This article describes activities required by a System Administrator to promote a DraftSR to a formal Service Request when an XSCF detects a domain panic.

Scope

This document is intended for System Administrators and support personnel.

Details

Auto Service Request (ASR) provides automatic failure detection and SR creation for Oracle SPARC systems. See http://www.oracle.com/us/asr/index.html for more information on ASR. This particular ASR event has created a Draft Service Request (DraftSR). DraftSRs require manual verification in order to determine whether further action by Oracle Service is required.

Description of the ASR Event: A Solaris domain has panic'ed.

Step 1: Please review and follow the steps recommended in document: SCF-8005-PX - The XSCF has detected that a Solaris domain has panic'ed. (Doc ID 1021931.1)

Step 2: If the panic's root cause does not need to be investigated by Oracle, no further action is required. The DraftSR will automatically expire 30 days from the sending of the notification. If the failure has been verified as requiring an investigation by Oracle, proceed with the steps to promote the DraftSR into a formal Service Request:

Log into My Oracle Support
Click on "Service Requests" in the menu area
In the "Draft Service Requests" section, click on Service Request Number <<DraftSR Number>>
Step 1 of the SR Create process will already have the Problem Summary, Problem Details and information pertaining to the Product and Configuration pre-populated. Validate that everything is accurate and all required fields are input.
Select Next.
Select "Unexpected, reboot,crash,panic" from the pull down menu then select the sub-category selection of "Solaris Operating System Panic".
You will then be prompted to upload an explorer and snapshot for further analysis by Oracle Service.
Select Next
Validate the SR severity, your contact information, and the Ship-To Address.
Click Submit to complete the SR create process and an Oracle Support Engineer will be assigned the SR to provide further assistance.

Example Alarm:

Hostname: <hostname>
Product Type: SUN SPARC ENTERPRISE M4000 SERVER
Summary:ASR:A hard-to-diagnose problem was detected by OpenBoot PROM.

A hard-to-diagnose problem was detected by OpenBoot PROM.event UUID = a659a6b1-5452-41ee-bced-1fe46ab31b92

Attachments

This solution has no attachment