1.2 Server Diagnostics Overview
1.2.1 Memory Configuration and Fault Handling
1.3 Using LEDs to Identify the State of Devices
1.3.1 Front and Rear Panel LEDs
1.4 Using the Service Processor Firmware for Diagnosis and Repair Verification
1.4.1 Interacting With the Service Processor
1.4.2 Running Service-Related Commands
1.5.1 Controlling How POST Runs
1.6 Using the Solaris Predictive Self-Healing Feature
1.6.1 Identifying PSH Detected Faults
1.7 Collecting Information From Solaris OS Files and Commands
Viewing System Message Log Files
1.8 Managing Components With Automatic System Recovery Commands
1.9 Exercising the System With SunVTS Software
Checking Whether SunVTS Software Is Installed
1.9.1 Exercising the System Using SunVTS Software
1.10 Obtaining the Chassis Serial Number
1.11 Additional Service Related Information
2.1.2 Electrostatic Discharge Safety
2.3 Prerequisite Tasks for Component Replacement
Disconnect Cables From the Server
Remove the Server From the Rack
3. Replacing Storage Components
3.2 Replacing the Optical Media Drive
Remove the Optical Media Drive
Install the Optical Media Drive
4. Replacing Motherboard Assembly Components
4.1 PCIe, PCI-X, and XAUI Card Configuration Reference
4.1.1 PCI Cards on the PCI Auxilliary Board
4.1.2 PCI Cards on the PCI Mezzanine Assembly
4.1.3 High Bandwidth PCIe Card Installation
4.2 Replacing PCI-X 0-1 and PCIe 2-3 Cards
Remove PCI-X 0-1 and PCIe 2-3 Cards
Install PCI-X 0-1 and PCIe 2-3 Cards
4.3 Replacing PCIe/XAUI Cards 4-6 and PCIe Cards 7-9
Remove PCIe/XAUI Cards 4-6 and PCIe Cards 7-9
Install PCIe/XAUI Cards 4-6 and PCIe Cards 7-9
4.4 Cabling the Sun Storage 6 Gb SAS PCIe RAID HBA, Internal
Cable the Sun Storage 6 Gb SAS PCIe RAID HBA, Internal
4.6 Replacing the PCI Mezzanine Assembly
Remove the PCI Mezzanine Assembly
Install the PCI Mezzanine Assembly
4.7 FB-DIMM Configuration Reference
4.8 Replacing the Memory Mezzanine Assembly
Remove the Memory Mezzanine Filler Tray
Install the Memory Mezzanine Assembly
Remove the Memory Mezzanine Assembly
4.12 Replacing the Motherboard Assembly
Remove the Motherboard Assembly
Install the Motherboard Assembly
4.13 Replacing the Disk Backplane Assembly
Remove the Disk Backplane Assembly
Install the Disk Backplane Assembly
4.14 Replacing the SAS Expander Assembly
Remove the SAS Expander Assembly
Install the SAS Expander Assembly
4.15 Replacing the Auxillary Board Assembly
Remove the Auxillary Board Assembly
Install the Auxillary Board Assembly
5. Replacing Chassis Components
5.3 Replacing the System Fan Assembly (Fan Tray 0)
Remove the System Fan Assembly (Fan Tray 0)
Install the System Fan Assembly (Fan Tray 0)
5.4 Replacing the Hard Drive Fan Assembly (Fan Tray 1)
Remove the Hard Drive Fan Assembly (Fan Tray 1)
Install the Hard Drive Fan Assembly (Fan Tray 1)
5.5 Replacing the FB-DIMM Fan Assembly (Fan Tray 2)
Remove the FB-DIMM Fan Assembly (Fan Tray 2)
Install the FB-DIMM Fan Assembly (Fan Tray 2)
6. Returning the Server to Operation
This section describes how to diagnose and replace faulty FB-DIMMs. If you are upgrading the system with additional FB-DIMMs, see Install Additional FB-DIMMs. For FB-DIMM configuration guidelines, see 4.7 FB-DIMM Configuration Reference.
![]() | Caution - This procedure requires that you handle components that are sensitive to static discharge. This sensitivity can cause the component to fail. To avoid this problem, ensure that you follow antistatic practices as described in Perform Antistatic Measures. |
![]() | Caution - Ensure that all power is removed from the server before removing or installing FB-DIMMs. You must disconnect the power cables before performing this procedure. |
![]() | Caution - DIMM filler cards are required in all empty slots in the memory mezzanine tray. DIMM filler cards are not required on the motherboard. |
The system Service Required LED lights if the system detects a FB-DIMM fault.
Use the showfaults command to identify faulty FB-DIMMs. See Detecting Faults.
Use the FB-DIMM fault locator button on the motherboard to identify faulty FB‐DIMMs.
Any faulty FB-DIMMs will be indicated with a corresponding amber fault LED on the motherboard.
Figure 4-20 Identifying an FB-DIMM
Tip - Make a note of the faulty FB-DIMM location so that you can install the replacement FB-DIMM in the same location.
Faulty FB-DIMMs are identified with a corresponding amber LED on the motherboard.
Note - The FB-DIMM fault LEDs remain lit only for a few minutes.
![]() | Caution - FB-DIMMs may be hot. Use caution when servicing FB-DIMMs. |
Figure 4-21 Removing FB-DIMMs

![]() | Caution - Ensure that all power is removed from the server before removing or installing FB-DIMMs or damage to the FB-DIMMs might occur. You must disconnect the power cables from the system before performing this procedure. |
Align the FB-DIMM notch with the key in the connector. This ensures that the FB-DIMM is oriented correctly.
If the FB-DIMM does not easily seat into the connector, verify that the orientation of the FB-DIMM is as shown in Inserting the FB-DIMM Into the Slot. If the orientation is reversed, damage to the FB-DIMM might occur.
Figure 4-22 Inserting the FB-DIMM Into the Slot

If you installed FB-DIMMs as part of another procedure, return to that procedure.
If you are to only install FB-DIMMs go to Step 7.
Note - If you removed the memory mezzanine, you must reinstall it. See ***
Refer to the Integrated Lights Out Manager 2.0 (ILOM 2.0) Supplement for the Sun Netra T5440 Server for instructions.
The method you use to clear a fault depends on how the fault is identified by the showfaults command.
Examples:
-> show faulty Target | Property | Value --------------------+------------------------+-------------------------------- /SP/faultmgmt/0 | fru | /SYS/MB/CMP0/BR0/CH1/D0 /SP/faultmgmt/0 | timestamp | Dec 14 22:43:59 /SP/faultmgmt/0/ | sunw-msg-id | SUN4V-8000-DX faults/0 | | /SP/faultmgmt/0/ | uuid | 3aa7c854-9667-e176-efe5-e487e520 faults/0 | | 7a8a /SP/faultmgmt/0/ | timestamp | Dec 14 22:43:59 faults/0 | |
-> show faulty Target | Property | Value --------------------+------------------------+-------------------------------- /SP/faultmgmt/0 | fru | /SYS/MB/CMP0/BR1/CH0/D0 /SP/faultmgmt/0 | timestamp | Dec 21 16:40:56 /SP/faultmgmt/0/ | timestamp | Dec 21 16:40:56 faults/0 /SP/faultmgmt/0/ | sp_detected_fault | /SYS/MB/CMP0/BR1/CH0/D0 faults/0 | | Forced fail(POST)
-> set /SYS/MB/CMP0/BR0/CH0/D0 component_state=Enabled
-> set /SYS/keyswitch_state=Diag Set ‘keyswitch_state’ to ‘Diag’
-> stop /SYS Are you sure you want to stop /SYS (y/n)? y Stopping /SYS -> start /SYS Are you sure you want to start /SYS (y/n)? y Starting /SYS
Note - The server takes about one minute to power off. Use the show /HOST command to determine when the host has been powered off. The console will display status=Powered Off.
-> start /SYS/console
Watch the POST output for possible fault messages. The following output is a sign that POST did not detect any faults:
. . . 0:0:0>INFO: 0:0:0> POST Passed all devices. 0:0:0>POST: Return to VBSC. 0:0:0>Master set ACK for vbsc runpost command and spin...
Note - Depending on the configuration of ILOM POST variables and whether POST detected faults or not, the system might boot, or the system might remain at the ok prompt. If the system is at the ok prompt, type boot.
-> set /SYS keyswitch_state=Normal Set ‘ketswitch_state’ to ‘Normal’
# fmadm faulty
No memory faults should be displayed.
If faults are reported, refer to the diagnostics flowchart in Diagnostic Flowchart for an approach to diagnose the fault.
-> show faulty Target | Property | Value --------------------+------------------------+------------------------------- /SP/faultmgmt/0 | fru | /SYS/MB/CMP0/BR0/CH1/D0 /SP/faultmgmt/0 | timestamp | Dec 14 22:43:59 /SP/faultmgmt/0/ | sunw-msg-id | SUN4V-8000-DX faults/0 | | /SP/faultmgmt/0/ | uuid | 3aa7c854-9667-e176-efe5-e487e520 faults/0 | | 7a8a /SP/faultmgmt/0/ | timestamp | Dec 14 22:43:59 faults/0 | |
-> set /SYS/MB/CMP0/BR0/CH1/D0 clear_fault_action=True Are you sure you want to clear /SYS/MB/CMP0/BR0/CH1/D0 (y/n)? y Set ’clear_fault_action’ to ’true
Use the same UUID that was displayed from the output of the ILOM show faulty command.
# fmadm repair 3aa7c854-9667-e176-efe5-e487e520
Before You Begin
Before you begin, see 4.7 FB-DIMM Configuration Reference to familiarize yourself with FB-DIMM configuration guidelines.
![]() | Caution - Ensure that all power is removed from the server before installing FB‐DIMMs or damage to the FB-DIMMs might occur. |
![]() | Caution - You must disconnect the power cables from the system before performing this procedure. |
Align the FB-DIMM notch with the key in the connector. This alignment ensures that the FB-DIMM is oriented correctly.
If the FB-DIMM does not easily seat into the connector, verify that the orientation of the FB-DIMM is as shown in Removing FB-DIMMs. If the orientation is reversed, damage to the FB-DIMM might occur.
-> set /SYS/keyswitch_state=Diag Set ‘keyswitch_state’ to ‘Diag’
-> stop /SYS Are you sure you want to stop /SYS (y/n)? y Stopping /SYS -> start /SYS Are you sure you want to start /SYS (y/n)? y Starting /SYS
Note - The server takes about one minute to power off. The ILOM console does not indicate when the system is actually powered off.
-> start /SYS/console
Watch the POST output for possible fault messages. The following output is a sign that POST did not detect any faults:
. . . 0:0:0>INFO: 0:0:0> POST Passed all devices. 0:0:0>POST: Return to VBSC. 0:0:0>Master set ACK for vbsc runpost command and spin...
Note - Depending on the configuration of ILOM POST variables and whether POST detected faults or not, the system might boot, or the system might remain at the ok prompt. If the system is at the ok prompt, type boot.
-> set /SYS keyswitch_state=Normal Set ‘ketswitch_state’ to ‘Normal’