Sun Enterprise[TM] 3x00-6x00 servers: Data collection advice for unplanned system reboots (Doc ID 1008923.1)

Last updated on MARCH 29, 2017

Applies to:

Sun Enterprise 3500 Server
Sun Enterprise 4500 Server
Sun Enterprise 5500 Server
Sun Enterprise 6500 Server
Sun Enterprise 3000 Server - Version: Not Applicable to Not Applicable   [Release: N/A to N/A]
All Platforms

Goal

The goal of this document is to provide suggestions for what type of data needs to be collected if a Sun Enterprise 3x00, 4x00, 5x00, or 6x00 system encounters an unplanned system reboot.  Unplanned refers to any number of ways one might describe the system suddenly resetting (so you might refer to this as a crash, panic, reset, or some other name). 
Each of these names actually has different technical meanings.  The whole point of this article is to set expectations on the data needs that are required to determine root cause to the event that was encountered.  This article will not describe the actual resolution to the event - just how and what data is needed in order to allow the support engineer to perform the diagnosis.
Background:
Sun Enterprise 3x00-6x00 servers may experience unplanned reboots for different reasons. Basic failure analysis methodology might entail the need to transfer large core files for analysis, but this is not necessary in some cases.   While this document will NOT completely eliminate the need for core file analysis, the goal is to reduce diagnosis time of certain failures where errors are sufficient, and transfer of large core files is unnecessary.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms