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

PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: Mx000
 

In this Document

Purpose

Scope

Details

Applies to:

Purpose

 This article describes activity required by a System Administrator to verify whether a System Reset is transient (ignorable) or actionable. If actionable, instructions will be provided as to how to proceed.

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:

An externally initiated reset has occurred on a domain.

These resets can be from a variety of sources and an additional check needs to performed in order to verify if this is an actual fault. If an actionable failure has occurred the DraftSR needs to be promoted into a formal Service Request and if possible an explorer and snapshot need to be provided to diagnose the issue.

Please find an example ASR alarm at the bottom of this document.

Step 1: Identify the system for which this event with corresponding ASR Alarm has occurred.

To view information on which of your systems is reporting the error condition

1. Log into My Oracle Support
2. Click on "Service Requests" in the menu area
3. In the "Draft Service Requests" section, click on Service Request Number <<DraftSR Number>> The affected Product, Serial Number, and Asset Name will be displayed on the same row as the Draft SR ID.

Step 2: Verify the system wasn't purposefully reset as part of regular maintenance. This is frequently caused by the System Administrator manually resetting the domain. To verify this is an actionable ( needs to be analyzed and fixed ) fault:

1. Ask the Systems Administrator.
2. Run the viewaudit command on the XSCF and review the output for the "reset" command, if present then the domain was manually reset and may not need to be promoted.
   
   • If the root cause for having to reset the domain needs to be analyzed, the details of the situation leading to the reset should be included in "Problem Details" below ( Step 3 ).

• Example command output://
  viewaudit -D <yyyymmdd> -c ACS_DOMAIN ( <yyyymmdd> is the date of when the issue occurred example 20080612 )
  .................
  header,87,1,command - console,192.168.1.1,2008-06-12 18:27:31.134 -06:00
  subject,2,platadm,normal,console
  command,console,-d0
  platform access,granted
  domain access,granted,0
  text,Connect to DomainID 0?y
  return,0
  header,106,1,command - reset,192.168.1.1,2008-06-12 18:27:39.307 -06:00
  subject,2,platadm,normal,console
  command,reset,-d0,xir
  platform access,granted
  domain access,granted,0
  text,DomainID to reset:00^JContinue? [y|n] :y^J
  return,0
  header,87,1,command - console,192.168.1.1,2008-06-12 18:27:49.435 -06:00
  subject,2,platadm,normal,console
  command,console,-d0
  platform access,granted
  domain access,granted,0
  text,Connect to DomainID 0?y
  return,0
  .................

Step 3: If a failure is not a valid problem, no further action is required. The DraftSR will automatically expire. If the failure has been verified as actionable, proceed with the steps to promote the DraftSR into a formal Service Request:

1. Log into My Oracle Support
2. Click on "Service Requests" in the menu area
3. In the "Draft Service Requests" section, click on Service Request Number <<DraftSR Number>>
4. 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. Click Next.
5. Select "Hardware Errors or Suspected Failures" from the pull down menu then select the sub-category selection of "Other Issues".
   You will then be prompted to upload an explorer and snapshot for further analysis by Oracle Service.
   Click Next
6. Validate the SR severity, your contact information, and the Ship-To Address. Cick Submit to complete the SR create process and an Oracle Support Engineer will be assigned the SR to provide further assistance.

Example Alarm:

Hostname: bob-sys
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

This solution has no attachment