Sun Netra 210 Server
 
Sun Fire V240 Server
 
Sun Fire V210 Server
 
Sun Fire V125 Server
 
Sun Netra 240 (AC) Server
 

PLA-Support>Sun Systems>SPARC>Workgroup Servers>SN-SPARC: SF-V2x0
 

Document supporting ASR  for CPU Fan Alarms

In this Document

Purpose

Scope

Details

Description of the ASR Event:

How to verify if a CPU fan has failed:

Example alarm:

Applies to:

Purpose

• This article describes activity required by a System Administrator to verify whether a CPU Fan event 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 dertermine whether further action by Oracle Service is required.

Description of the ASR Event:

A CPU fan alarm can be transient in nature.  An additional check need to performed in order to verify whether this is a persistent hardware faultor not.  If a persistent failure has occurred the DraftSR needs to be promoted into a formal Service Request and the part needs to be replaced.

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

How to verify if a CPU fan has failed:

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: To verify that a fan has a persistent failure, perform either Step2a or Step 2b on the identified system.

Step 2a:    You can validate a Fan failure is persistent by running prtdiag -v on a V240 and it is still reporting the fan as 'failed'. 

Log in to Solaris.

Run prtdiag -v 

The following output indicates a persistent failure for a v240 reporting a failed fan in a Motherboard.

/usr/sbin/prtdiag -v
[output removed]

[output removed]

Note: F[0/1/2] are the system fans, MB/P[0/1]/F[0/1] are the CPU fans, PS[0/1] are the Power Supply fans (FRU is the PSU itself)
Note: The output can vary slightly per System firmware version, HW version and Solaris version.

Step 2b:

Run the ALOM command "showenvironment" and check following information. 

A status that is not OK or a speed below the low threshold would verify a persistent failure.

Fans (Speeds Revolution Per Minute):
----------------------------------------------------------
Sensor           Status             Speed   Warn    Low
----------------------------------------------------------
F0.RS                OK                5000        --   1000
F1.RS                OK                4891        --   1000
F2.RS                OK                5232        --   1000
MB.P0.F0.RS      OK               15340   2000   2000
MB.P0.F1.RS      OK               15697   2000   2000
MB.P1.F0.RS      OK               17307   2000   2000
MB.P1.F1.RS      OK               17307   2000   2000

Note: F[0/1/2] are the system fans, MB/P[0/1]/F[0/1] are the CPU fans.

Note: The output can vary slightly per System firmware version, HW version and Solaris version.

Step 3: If a failure is not persistent, no further action is required.  The DraftSR will automatically expire.

If the failure has been verified as persistent, 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 file for further analysis by Oracle Service.  This file is required to allow the correct part to be dispatched.

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:

=ASR Alarm=
Automatic Service Request (ASR) Alarm
Generated: 2011-10-05 10:23:47
Severity : 3
Device : AA1234567
Eventcode: 1.3.6.1.4.1.42.2.12.2.2.1.1.10.2.1.1.1.6

Event num: 1.3.6.1.4.1.42.2.12.2.2.1.1.10.2.1.1.1.6

ASR: Probable Fan failure, fan-unit: XXX
-----------------------------------
Hostname: SYSTEM1
Product Type: SUNW,SUN-FIRE-V240 SPARC SYSTEM
Summary:ASR: Probable Fan failure, fan-unit: XXX
Description:mod/Config-Readerelp/PhysicalComponents/Fan/FanTable/FanTableEntry/OperationalS

FEMS rule matched:000214 - v240_v440_v445_v245_v210_v215 - SUNMC


mod/Config-Readerelp/PhysicalComponents/Fan/FanTable/FanTableEntry/OperationalS

This solution has no attachment