Finding a bad CPU in a Sun Enterprise[TM] 450 server

Asset ID:	1-72-1004624.1
Update Date:	2009-02-24
Keywords:

Solution Type Problem Resolution Sure

Solution 1004624.1 : Finding a bad CPU in a Sun Enterprise[TM] 450 server

Related Items


Sun Enterprise 450 Server

Related Categories


GCS>Sun Microsystems>Servers>Entry-Level Servers

PreviouslyPublishedAs
206412

Symptoms
This document helps to understand the CPU number scheme in
a Sun Enterprise[TM] 450 server, and to find a bad CPU, if
the system fails reboot.

A bad cpu may cause a RED STATE EXCEPTION panic.

Resolution
The order of CPU installation, is not the same as the way
Solaris[TM] Operating System(OS) numbers the CPUs.

Solaris OS, probes the UPA slots from top to
bottom(UPA slot 1=TOP 4=BOTTOM).

UPA slot 1 = CPU 0 J0101
UPA slot 2 = CPU 1 J0201
UPA slot 3 = CPU 2 J0301
UPA slot 4 = CPU 3 J0401

If the system panics on bootup, or keeps rebooting, with
RED STATE EXCEPTION errors, and a CPU is suspected, disable
one CPU at a time.

At the ok prompt:
ok setenv upa-port-skip-list <CPU#>
ok reset-all
ok boot

Once the Failing CPU is found, the system should boot up with
the CPU disabled. When the CPU is replaced, set the NVRAM
variable back to original setting.

ok setenv upa-port-skip-list none

Product
Sun Enterprise 450 Server

cpu, panic, RED STATE, boot up failed
Previously Published As
21220

Change History
Date: 2004-11-17
User Name: 18392
Action: Approved
Comment: Added trademarking, OS name etc. Added STM for readability. Corrected grammar, wording.
Version: 3
Date: 2004-11-17
User Name: 18392
Action: Accept
Comment:
Version: 0
Date: 2004-11-17

Attachments

This solution has no attachment