Sun Fire V20z Compute Grid Rack System
 
Sun Fire V20z Server
 
Sun Fire V40z Server
 

GCS>Sun Microsystems>Servers>x64 Servers
 

Applies to:

Purpose

Last Review Date

Instructions for the Reader

Troubleshooting Details

Step 1. Verify system power

Power can be verified either visually (if you have access to the platform) or remotely using the ILOM commands.

Refer to DocID: 1008399.1 “How to verify power on a Sun Fire v20z/40z System”

The above technical instruction makes reference to the v20z/v40z Troubleshooting guide, which will assist in troubleshooting in the event that the server powered down unexpectedly. For example, in the event of a Thermal Trip Event, advice is given on correcting airflow blockages.

If you still have a problem, raise a service request as outlined in Step 6

Step 2. Verify SP connectivity

Be clear about how you are trying to contact your server.

If you are trying to connect via the service processor, refer to the Sun Fire V20z and Sun Fire V40z Servers--Server Management Guide, Part No: 817-5249

Available at: Sun Fire V20z and Sun Fire V40z Servers Documentation.

If you are trying to contact the server via the platform network, go to step 4

NOTE: If after checking your SP connectivity you still have a problem, contact Sun Support. as outlined in step 4 below

Step 3. Check for any errors on the system

• Check for platform events

Identify any reported system faults on the Service Processor with command:

sp get events -v

or one of the other methods described in the Troubleshooting: System Events section of the Sun Fire? V20z and Sun Fire V40z Servers Troubleshooting Techniques and Diagnostics Guide, Part No 817-7184

Available at:  Sun Fire V20z and Sun Fire V40z Servers Documentation.

• Visually check of system LEDs

System LEDs and the LCD panel can indicate certain fault conditions.

Refer to “Lights, LCD, LED” section of the Sun Fire V20z and Sun Fire V40z Servers Troubleshooting Techniques and Diagnostics Guide, Part No 817-7184

Any abnormal conditions, raise a a service request as outlined in Step 6.

Step 4. Verify network connectivity

The commands to follow to check your network are outlined in the following document:

DocID: 1005533.1 "How to verify network connectivity on an x64 platform"

Step 5. Check your platform has not hung

If all the above check out, your platform may be hung (although if you can run the commands in Step 4, you can't be hung...)

Here are some documents which will be helpful if you are still unsure about whether you have hung:

• DocID: 1008401.1 "Handling System hangs on an x64 Solaris System"

• DocID: 1007053.1 "Analyzing System hangs on x64 Linux systems"

• DocID: 1017776.1 "What to do on System hangs on an x64 Windows Systems"

Step 6. Raise a Service request

At this point, if you have validated that each troubleshooting step above is true for your environment, and the issue still exists, further troubleshooting is required. For additional support contact Sun Support.

NOTE: Since you can't contact your server, the amount of data you can gather is limited. For example, if you are running solaris, you will not be able to complete an explorer data capture. However, in the event you can get the data (maybe you have problems contacting on one ethernet port only), the link below will show you how.

The following link references support documents assists in the gathering of information from your platform:

• DocID: 1018748.1 "How to Run Sun[TM] Explorer and Forward the Data to a Sun Engineer".

A full description of the Sun Explorer package and release notes are available at the:

Sun Explorer Product Information Center (Doc ID 1312847.1)

• DocID: 1010057.1 "How to gather information on SuSE Linux Enterprise"

• DocID: 1010058.1 "How to gather information on Red Hat Enterprise Linux"

At this point, if you have validated that each troubleshooting step above is true for your environment, and the issue still exists, further troubleshooting is required. For additional support contact Oracle Support.

This solution has no attachment