Table of Contents
Advertisement
Action
Diagnostic Action
No.
8
Determine if the fault
was detected by POST.
9
Contact Sun for
Support.
1.2.1
Memory Configuration and Fault Handling
A variety of features play a role in how the memory subsystem is configured and how memory
faults are handled. Understanding the underlying features helps you identify and repair memory
problems. This section describes how the memory is configured and how the server deals with
memory faults.
1.2.1.1
Memory Configuration
In the server memory there are 16 slots that hold DDR-2 memory FB-DIMMs in the following
FB-DIMM sizes:
1 Gbyte (maximum of 32 Gbyte)
■
2 Gbyte (maximum of 64 Gbyte)
■
4 Gbyte (maximum of 128 Gbyte)
■
8 Gbyte (maximum of 256 Gbyte)
■
FB-DIMMs are installed in groups of 8, called ranks (ranks 0 and 1). At minimum, rank 0 must
be fully populated with eight FB-DIMMs of the same capacity. A second rank of FB-DIMMs of
the same capacity can be added to fill rank 1.
See
"4.9 Servicing FB-DIMMs" on page 100
server.
Resulting Action
After replacing the FRU, perform the procedure to clear PSH
detected faults.
POST performs basic tests of the server components and reports
faulty FRUs. When POST detects a faulty FRU, it logs the fault
and if possible, takes the FRU offline. POST detected FRUs
display the following text in the fault message:
FRU-name deemed faulty and disabled
In this case, replace the FRU and run the procedure to clear
POST detected faults.
The majority of hardware faults are detected by the server's
diagnostics. In rare cases, a problem might require additional
troubleshooting. If you are unable to determine the cause of the
problem, contact Sun for support.
1.2 Server Diagnostics Overview
Additional Information
"1.5 Running
POST" on page 32
"Clearing POST Detected
Faults" on page 39
Sun Support information:
//www.sun.com/support
"1.10 Obtaining the Chassis
Serial Number" on page 54
for instructions about adding memory to a
Chapter 1 • Server Diagnostics
http:
15
Advertisement
Table of Contents
