Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-75-1012990.1
Update Date:2011-05-16
Keywords:

Solution Type  Troubleshooting Sure

Solution  1012990.1 :   Troubleshooting system crash or system down and collecting core file for Entry-level and Midrange Sun SPARC Systems  


Related Items
  • Sun Fire E6900 Server
  •  
  • Sun Fire 3800 Server
  •  
  • Sun Fire 6800 Server
  •  
  • Sun Fire E4900 Server
  •  
  • Sun Fire 4800 Server
  •  
  • Sun Fire E2900 Server
  •  
  • Sun Fire V1280 Server
  •  
  • Sun Netra 1290 Server
  •  
  • Sun Fire 4810 Server
  •  
  • Sun Fire V490 Server
  •  
Related Categories
  • GCS>Sun Microsystems>Servers>Midrange V and Netra Servers
  •  
  • GCS>Sun Microsystems>Servers>Entry-Level Servers
  •  
  • GCS>Sun Microsystems>Servers>Midrange Servers
  •  

PreviouslyPublishedAs
217788
Abstract

In this Document
  Purpose
  Last Review Date
  Instructions for the Reader
  Troubleshooting Details


Applies to:

Sun Fire E6900 Server
Sun Netra 1290 Server
Sun Fire E2900 Server
Sun Fire 4810 Server
Sun Fire V490 Server
All Platforms

Purpose

This document will assist the user with collecting a core file for analysis when a system has crashed.

It is assumed that EIS (Enterprise Installation Standards) regarding best practices have been followed and the crash was not caused by a customers application.

Last Review Date

February 28, 2011

Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details

Symptoms:

  • System is down
  • System has crashed
  • Core file has been generated

Sun Shared Shell


If you require assistance in collecting the data recommended in this article or require help in diagnosing a system issue, there is a collaborative service tool called Sun Shared Shell which allows Sun Service engineers to remotely view and diagnose customer's systems. Consider using this option to reduce the problem resolution time.




 



Steps to Follow
Please validate that each troubleshooting step below is true for your environment.
The steps will provide instructions or a link to a document, for validating the step and taking corrective action  as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step.

1.  Verify the system power cord(s) are securely connected at both ends. 

  • Make sure power supply(s) are properly seated and check all external LED's.  If it appears to be a power issue, reference the following troubleshooting documents:
    • For Entry-level SPARC systems see <Document 1018104.1> Diagnosing Why a System Will Not Power On for Entry-level and Midrange Sun SPARC Systems
    • For Sun Fire[TM] Midrange Servers, see <Document 1010053.1> Troubleshooting Complete system Power Outages on Sun Fire [TM] Serengeti or LightWeight8 Systems

2.  Verify the status of all components are OK and present.

  • Look for the wrench fault light usually located on the front of the system.
    • A solid green LED indicates no component failures while an illuminated amber wrench LED is alerting you that it has detected a general fault or failure that needs to be identified.
  • On Sun Fire[TM] Midrange servers, view the output of showenvironment if the System Controller is up and activated.
    • See <Document 1011930.1> Sun Fire[TM] (3800-6800) System Controller Application (ScApp) How To's.

3.  Verify that POST diagnostics pass and does not fail a hardware component.

  • Check the console for any error messages logged, if none then the banner should be displayed.
    • See <Document 1004222.1> How to setup console logging and obtain diagnostic data from different types of SPARC servers

4.  Verify the system is on and keyswitch is in normal or diagnostic position.

  • Check that the system key is in the normal or diagnostic position or if the system has a virtual switch, that the poweron command has been issued.
  • To verify what system used a physical keyswitch, see <Document 1011578.1> Sun SPARC(R) Systems that have interlock switch feature

5.  Verify a core file can be generated.

  • Get the system to the OK prompt. Depending on system type either with issuing a 'STOP a' or sendinging a break.  Once at the OK prompt issue the 'sync' command which will force the system to generate a core file.
  • Several references exist relating to the procedures to follow to collect this information:
    • <Document 1012913.1>  Solaris[TM] Operating System: Panics, dumps, hangs or crashes. The MOST important things you will ever need to know.
    • <Document 1004803.1> Collecting System Crash Dump Images on Solaris[TM] 7 and later
    • <Document 1003108.1> How to gather information at the OK prompt
    • <Document 1004803.1> Collecting System Crash Dump Images on Solaris[TM] 7 and later

6. Verify the boot process completes off the primary boot disk.

  • If the system can not boot off the primary or alternate boot disk, confirm the boot disk is recognized and functioning properly.
    • Entry-level SPARC servers should refer to <Document 1005531.1> Verify Disk is Present When Booting From Alternate Media
    • Sun Fire[TM] Midrange servers should refer to <Document: 1008391.1> Troubleshooting a Sun Fire[TM] E2900/3800/4800/4810/E4900/6800/E6900/V1280 and Netra[TM] 1280/1290 system that can't or won't boot

7.  Collect the following data and collaborate with the next level of support.

  • Gather the core file that was generated in Step 5 above.
  • Collect Explorer data from the system in question.
    • For most SPARC systems you will only need to see <Document 1002383.1> Explorer Data Collector
    • For Entry-level SPARC servers see the additional reference:
      • <Document 1018946.1> Using Sun[TM] Explorer on the Tx000 Series Systems.
    • For Sun Fire[TM} Midrange servers see the additional reference:
      • It is preferred that Explorer with the appropriate scextended or 1280extended option as detailed in <Document 1018748.1> em>How to run Sun data and send to Sun engineer
      • If Explorer data can not be collected for whatever reason see <Document 1003529.1> Procedure to collect Sunfire Midrange failure data manually
At this point, if the customer has validated that each troubleshooting step 
above is true for their environment, and the issue still exists, collaborate
with the next level of technical support.
            
            
To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community - Midrange Servers. 

Product
Sun Fire V490 Server
Sun Netra 1290 Server
Sun Fire V1280 Server
Sun Fire E6900 Server
Sun Fire E4900 Server
Sun Fire E2900 Server
Sun Fire 6800 Server
Sun Fire 4810 Server
Sun Fire 4800 Server
Sun Fire 3800 Server



Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback