Sun Fire V240 Server
 
Sun Fire V440 Server
 
Sun Fire V480 Server
 
Sun Fire V210 Server
 
Sun Fire V890 Server
 
Sun Fire V880 Server
 
Sun Fire V490 Server
 

GCS>Sun Microsystems>Servers>Entry-Level Servers
 

Symptoms:

Purpose/Scope:

When these reboots happen, there are no apparent signs of an error at the OS level. The system reboots with no panic, core file or any messages logged to the /var/adm/messages file. The error messages and all output will appear only on the system console (will be in the console logs).

This document will assist the user in resolving issues related to  unexplained  reboots on entry-level and mid-range VSP Servers, such as: Sun Fire[TM] 280R, Sun Fire[TM] V440, Sun Fire[TM] V210/240, Sun Fire[TM] V480/490, Sun Fire[TM] V880/890.

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 system wasn't brought down by user command (or user error). Check the /var/adm/messages file for messages, such as  rebooted by root  and  going down on signal 15 :

Nov 10 15:55:44 v890-b reboot: [ID 662345 auth.crit] rebooted by root
Nov 10 15:55:44 v890-b syslogd: going down on signal 15

For the 'sun4u' platforms the latest reboot/reset reason can also be checked from the 'prtconf -vp' output. Here is an example for a reboot caused by user:

v890-b# prtconf -vp |grep reset
reset-reason:  'SPOR Software/User'

2. Verify the reboot is not due to fatal reset errors. Refer to <Document: 1008390.1>

3. Verify there are no Red State Exception (RSE) errors. To verify the the reboot is not due to RSE errors refer to <Document: 1008390.1>

4. Verify the console logging via the system serial console is enabled and system is prepared to collect the data necessary to analyze the 'unexplained reboots'. 

Refer to <Document: 1004222.1>

In case you need to collect the data via the RSC console,  the system console should be redirected to RSC. Refer to <Document: 1011888.1>

5. At this point, if the user has validated that each troubleshooting step above is true for the environment, and the issue still exists, further troubleshooting is required. Gather the needed data from the console logs and by running explorer. For further assistance you may contact   My Oracle Support.

To notify content owners of a knowledge gap contained in this
document, and/or prior to updating this document, please contact
the domain engineers that are managing this document via the
"Document Feedback" alias(es) listed below:

Normalization Lead: Jim Robbins

Domain Engineer/Lead : Josh Freeman

[email protected]

REFERENCES:

Internal Tool: Fatal Reset Decoder

Internal Tool: RED State Exception Decoder

Internal Tool: US3iAFAR Decoder

Sun Alert <Document: 1000380.1> Sun Systems Equipped With
Schizo ASICs Version 2.3 or Higher May Experience Either Domain
Stop (Dstop), Domain Pause or FATAL RESET Under Heavy I/O

FCO AO226-1 V480 Fatal Resets with specific
network and I/O configurations

Sun Alert <Document: 1000884.1> Sun Fire V440 and Netra 440
Systems Using a Specific Networking Configuration may Unexpectedly
Reset

<Document: 1012214.1> Troubleshooting Red
State Exception Memory Errors

<Document: 1006524.1>  Sun Fire V880 FATAL Resets

<Document: 1006530.1>  Troubleshooting Sun Fire V880 RED
STATE EXCEPTION

<Document: 1004903.1>  Event Messages for
UltraSPARC-III[R], UltraSPARC-III+[R], UltraSPARC-IIIi[R],
UltraSPARC-IV[R] and UltraSPARC-IV+[R] CPU Modules .

This solution has no attachment