Sun Fire X4200 M2 Server
 
Sun Fire X4100 M2 Server
 
Sun Fire X4600 M2 Server
 
Sun SPARC Enterprise T5440 Server
 
Sun Fire X4140 Server
 
Sun Fire X4640 Server
 
Sun Fire X4100 Server
 
Sun Fire X4240 Server
 
Sun Fire X4600 Server
 
Sun Fire X4200 Server
 
Sun Fire X4500 Server
 
Sun Fire X4540 Server
 

PLA-Support>Sun Systems>x86>Server>SN-x64: SERVER 64bit
 

This article describes activity required by a System Administrator to verify whether action has to be taken on a X86 ASR power supply alarm on an AMD based system

In this Document

Purpose

Scope

Details

Description of the ASR Event:

How to verify if there is a genuine Power Supply issue:

Example alarm:

Applies to:

Purpose

 This article describes activity required by a System Administrator to determine whether action has to be taken on a X86 ASR power supply alarm.

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 X86 systems.  See http://www.oracle.com/us/asr/index.html for more information on ASR.

Description of the ASR Event:

Power supply events can be both transient or persistent. They can be generated by external changes and actions, most notably by the removal of AC from a power supply.

Additional checks may need to performed in order to understand the cause of this ASR event.  If a persistent failure has occurred, or if a power event or events cannot

be explained by changes in the supplied power or work being carried out on the machine, then further investigation by a support engineer may be required

If the event has been been caused by changes in site power or a similar event then no action need be taken.

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

How to verify if there is a genuine Power Supply issue:

Step 1: Identify the system that experienced this ASR Alarm.

The Auto Service Request (ASR) will be logged against the serial number of the machine that generated the alarm.

The information provided by the alarm will contain the hostname of the machine or the machine's Service

Processor.

Step 2: To verify that a power supply has a persistent failure, perform either Step2a, Step 2b or Step 2c of this document.

The ASR alarm will identify the power supply number that has generated the alarm.

This power supply can be checked by using the one of the methods below:

"value = State Asserted" for PWROK indicates the power supply DC output is functioning

"value = State Asserted" for VINOK indicates the AC input to the power supply is present

If the AC input for a particular power supply is "State Deasserted" then the corresponding DC output of the power supply (PWROK) will also be  "State Deasserted" and the site infrastructure

should be checked to discover the reason for the loss of AC.

Note on a server which is powered off PWROK will be in state "Deasserted" for all power supplies.

On a system that is powered up and VINOK is Asserted (On) for a power supply but PWROK is "Deasserted" (Off) for that power supply then a support engineer should be engaged.

Step 2a

If the utility ipmitool is available then the ipmitool command "sensor" can be used to check the

incoming AC and DC output of a power supply.

eg

ipmitool -H <sp address or name> -U root sensor

<output omitted>
PS1/VINOK        | 0x2        | discrete   | 0x0200| na        | na        | na        | na        | na        | na
PS1/PWROK        | 0x2        | discrete   | 0x0200| na        | na        | na        | na        | na        | na
<output omitted>

Note "0x2 indicates "Asserted" and "0x1" indicates "Deasserted"

Step 2b

Log onto the Command Line Interface (CLI) of the server's service processor and use the command below to check the relevant power supply status under /SYS/PSx

where "x" is the power supplied implicated in the ASR alarm.

"value = State Asserted" under PWROK indicates the power supply DC output is functioning

"value = State Asserted" under VINOK indicates the AC input to the power supply is present

Note the following output will vary slightly according to the version of ILOM.

If the AC input for a particular power supply is "State Deasserted" then the corrresponding DC output of the power supply (PWROK) will also be  "State Deasserted" and the site infrastructure should be checked to discover the reason for the loss of AC.

->  show -d properties /SYS/PS0/PWROK
  /SYS/PS0/PWROK
    Properties:
        type = Power Supply
        class = Discrete Sensor
        value = State Asserted


-> show -d properties /SYS/PS0/VINOK
  /SYS/PS0/VINOK
    Properties:
        type = Power Supply
        class = Discrete Sensor
        value = State Asserted

Step 2c

Log onto the the Browser User Interface (BUI) of the ILOM

Navigate to the System Monitoring Tab > Sensor readings.

Then select "Type: Power Supply" as filter

and check the relevant /SYS/PSx/PWROK and /SYS/PWx/VINOK entries.

An example is shown below:

"value = State Asserted" for the relevant power supply's PWROK indicates the power supply DC output is functioning

"value = State Asserted" for the relevant powers supply's VINOK indicates AC to the power supply is present

 Step 3:

If a failure is not persistent, no further action is required.  The SR will close in 14 days.

If the failure has been verified as persistent or is a cause of concern, then engage a support engineer by one of the following methods

a) Update the SR - A support engineer will be assigned to assist.

b) Phone your local Oracle support number and request the SR be assigned to the next available engineer.

Example alarm:

Hostname: <failing SP Hostname>
Product Type: SUN FIRE X4600
Summary:Probable power supply failure

Probable power supply failure
sunHwTrapSystemIdentifier = 
sunHwTrapChassisId = <humber>
sunHwTrapProductName = 
sunHwTrapComponentName = /SYS/PS0/PWROK
sunHwTrapAdditionalInfo = State Deasserted
sunHwTrapAssocObjectId = .1.3.6.1.2.1.47.1.1.1.1.2.101

This solution has no attachment