How to check why the system is powered off, on Sun Fire[TM] X2100 M2/X2200 M2 Servers

Asset ID:	1-71-1012992.1
Update Date:	2012-07-30
Keywords:

Solution Type Technical Instruction Sure

Solution 1012992.1 : How to check why the system is powered off, on Sun Fire[TM] X2100 M2/X2200 M2 Servers

Applies to:

Sun Fire X2100 M2 Server - Version Not Applicable to Not Applicable [Release N/A]
Sun Fire X2200 M2 Server - Version Not Applicable to Not Applicable [Release N/A]
All Platforms

Goal

This document describes what to check if systems appears to be powered off and you expect it to be ON via ipmitool, ELOM web GUI, Service Processor CLI and if you are local to the server.

Fix

Symptoms:

System powered off
Cannot access
Cannot boot

Steps to Follow

Instructions to gather possible reasons of the outage:
If the chassis has no power then the Service Processor will not function as it requires Standby Voltage. If this is the case then examination of the local server is required.
If you can communicate with the Service Processor then AC voltage is available to the server, so use the following to gather the status of the platform and to gather possible reasons of the outage using ipmitool, ELOM GUI, or Service Processor CLI.
There are some conditions that trigger the BMC to issue a shutdown request:

An over-temperature condition for more than 1 second.
Multiple fan failures.
CPU thermal trip

The fault conditions that will trigger a shutdown are:

All power supplies have failed or have been removed.
A power supply has been out of spec for more than 100 mS.
The hot-swap circuit has faulted.
An over-temperature condition has occurred

How to gather possible reasons of the outage using ipmitool.

Use the following common ipmitool commands to gather further data as to the possible reasons for the platform state. These would be useful if you need to report a support call:


ipmitool -I lan -H <ELOM User name> -U <ELOM User name> sel elist
ipmitool -I lan -H <ELOM User name> -U <ELOM User name> sel info
ipmitool -I lan -H <ELOM User name> -U <ELOM User name> sdr list all info
ipmitool -I lan -H <ELOM User name> -U <ELOM User name> fru print
ipmitool -I lan -H <ELOM User name> -U <ELOM User name> sensor

See <Document: 1009698.1> for further information on Intelligent Platform Management Interface (IPMI).

Refer to Chapter 7: Using IPMI, Embedded Lights Out Manager Administration Guide For the Sun Fire X2200 M2 and Sun Fire X2100 M2 Servers, Part No.: 819-6588-xx "How to gather possible reasons of the outage using ELOM web GUIOpen ELOM Service Processor GUI", to access enter https://<ELOM IP address> in a supported browser.

Depending of the ELOM version installed on your system, you will find the power status on the following pages.

After you have logged into the Service Processor:

Click "System Monitoring" -> "Event Logs" -> "View Events Logs" tab.

-or-

Click "Event Log" -> "View Events Log" tab.

Refer to the ELOM Administration Guide Supplement for Sun Fire if available for your platform at: http://www.oracle.com/technetwork/documentation/oracle-x86-servers-190077.html "How to gather possible reasons of the outage using ELOM Service Processor Command Line (CLI)"

Log in to the Service Processor using the SSH command
NOTE: You will need the IP address of the Service Processor to do this:

# ssh -l <USERNAME> <IP_ADDRESS>

Check the output for the following commands from the Service Processor:

-> show /SP/AgentInfo/SEL - This gathers the SEL event list. -> show -d properties -level all /SP/SystemInfo ? This gathers the Sensor values. How to gather possible reasons of the outage using if you are local to the server

After checking LEDs and verified that the power ok LED from the front or rear is illuminated either STEADY GREEN (ON) or SLOW BLINK GREEN (OFF), then power is available and that AC is applied.
Power on the platform by pressing the power on button
Press <F2> when prompted to enter BIOS. Note any events that might be reported
Once in BIOS navigate using the cursor keys to the tab labeled "Advanced"
Navigate down to "IPMI 2.0 Configuration", press <ENTER>
Select "View Event Log", examine for possible reasons of the outage, use <ESC> to exit

NOTE: Unless you are familiar with these events as they are in raw format, I would suggest you use ipmitool commands above as this decodes these events automatically.

As there will be events that are part of the normal process of the system powering on, decoding of these events would be required to look for issues.

The messages can also be decoded manually by accessing the following document: http://www.intel.com/design/servers/ipmi/IPMIv2_0_rev1_0_markup_2.pdf

It is beyond the scope of this document to discuss this manual process of decoding. If the system will still not power on even if AC is available on or remain on.

There could be an environmental issue that might be the reason that the server will not power on or remain on. Check environment and event logs for possible causes.

Verifying cause of NO power if you are local to the server

If the Power LED on the front or back of the system is OFF, please Ensure that an AC power cord is plugged into at least one power connector on the rear of the server and into an working AC power outlet(s).

If have still have no Power LEDs activity and the AC power cords are connected to the system, engage a qualified electrician to check the AC voltage on the power cords.

For further Information about LED states refer to Sun Fire[TM] X2100 M2 Servers Service Manual, Chapter 1.3.1 Front and Back Panels, Part No. 819-6591-xx at URL below:

http://docs.oracle.com/cd/E19121-01/sf.x2100m2/index.html

For further Information about LED states refer to Sun Fire[TM] X2200 M2 Servers Service Manual, Chapter 1.3.1 Front and Back Panels, Part No 819-6597-xx at URL below:

http://docs.oracle.com/cd/E19121-01/sf.x2200m2/index.html

Previously Published As 91543

References

Attachments

This solution has no attachment