Confirming Server and Site Specifications
Install Mounting Brackets on Server
Attach Slide Rail Assemblies to Rack
Connecting Data and Management Cables
Secure Cables to CMA (Optional)
Powering On the Server for the First Time
Connect a Terminal or Emulator to the SER MGT Port
Power on the System for the First Time
Oracle Solaris OS Configuration Parameters
Assigning a Static IP Address to the SP
Assign a Static IP Address to the NET MGT Port
Understanding System Administration Resources
Platform-Specific Oracle ILOM Features
Oracle VM Server for SPARC Overview
Hardware Management Pack Overview
Source for Downloading Hardware Management Pack Software
Hardware Management Pack Documentation
Display the Oracle ILOM -> Prompt
Power On the Server (Oracle ILOM)
Power Off the Server (Oracle ILOM)
Reset the Server (Oracle Solaris OS)
Reset the Server (Oracle ILOM)
Reset the SP to Default Values
Important Hardware RAID Guidelines
Prepare to Use the FCode Utility
Hot Spare Drives in RAID Volumes (LSI)
Determining If a Drive Has Failed
RAID Drive Replacement Strategies
Changing Server Identification Information
Change Customer Data on FRU PROMs
Change System Identifier Information
Restore the Host Power State at Restart
Specify the Host Power State at Restart
Disable or Re-Enable the Host Power-On Delay
Specify Parallel Boot of the SP and Host
Configure Host Behavior (Keyswitch State)
Disable or Re-Enable Network Access to the SP
Display the DHCP Server IP Address
Display the IP Address of the SP
Using an In-band Connection to the SP
Configure the Host Boot Mode (Oracle VM Server for SPARC)
Change the Host Boot Mode Behavior at Reset
Manage the Host Boot Mode Script
Display Host Boot Mode Expiration Date
Override OBP Settings to Reset the Server
Configuring Server Behavior at Restart
Specify Behavior When the Host Resets
Specify Behavior When the Host Stops Running
Specify Behavior at Boot Timeout
Specify Behavior if Restart Fails
Specify Maximum Restart Attempts
Enabling Automatic System Recovery
Identifying WWN-Designated SAS2 Devices
Mapping WWN Values to Hard Drives (OBP probe-scsi-all Command)
Identify a Disk Slot Using prtconf (Oracle Solaris OS)
WWN Syntax in an OS Installation on an Individual Drive
WWN Syntax in an OS Installation on a RAID Volume
Infrastructure Boards in the Server
Front and Rear Panel System Controls and LEDs
Ethernet and Network Management Port LEDs
Oracle ILOM Troubleshooting Overview
Display FRU Information (show Command)
Check for Faults (show faulty Command)
Check for Faults (fmadm faulty Command)
Clear Faults (clear_fault_action Property)
Understanding Fault Managment Command Examples
Service-Related Oracle ILOM Commands
Interpreting Log Files and System Messages
Checking if Oracle VTS Is Installed
Check if Oracle VTS Software Is Installed
Oracle ILOM Properties that Affect POST Behavior
Understanding Component Replacement Categories
Removing Power From the Server
Positioning the System for Servicing
Attaching Devices to the Server
Verify Fan Module Functionality
Verify Power Supply Functionality
Servicing Memory Risers and DIMMs
Locate a Faulty DIMM (DIMM Fault Remind Button)
Locate a Faulty DIMM (show faulty Command)
Increase Server Memory With Additional DIMMs
Increase Server Memory with Additional DIMMs (16 Gbyte Configurations)
Remove a Memory Riser Filler Panel
Install a Memory Riser Filler Panel
DIMM Configuration Error Messages
Remove a DVD Drive or Filler Panel
Install a DVD Drive or Filler Panel
Servicing the System Lithium Battery
Servicing Expansion (PCIe) Cards
Remove a PCIe Card Filler Panel
Cable an Internal SAS HBA PCIe Card
Install a PCIe Card Filler Panel
Verify Fan Board Functionality
Verify Motherboard Functionality
Verify Drive Backplane Functionality
Servicing the Power Supply Backplane
Remove the Power Supply Backplane
Install the Power Supply Backplane
Verify Power Supply Backplane Functionality
Returning the Server to Operation
Return the Server to the Normal Rack Position
Power On the Server (Oracle ILOM)
POST error messages use the following syntax where n =the node number, c = the core number, s = the strand number:
n:c:s > ERROR: TEST = failing-test n:c:s > H/W under test = FRU n:c:s > Repair Instructions: Replace items in order listed by H/W under test above n:c:s > MSG = test-error-message n:c:s > END_ERROR
Warning messages use the following syntax:
WARNING: message
Informational messages use the following syntax:
INFO: message
In the following example, POST reports an uncorrectable memory error affecting DIMM locations /SYS/MB/CMP0/MR0/B0B0/CH0/D0 and /SYS/MB/CMP0/B0B1/CH0/D0. The error was detected by POST running on node 0, core 7, strand 2.
2010-07-03 18:44:13.359 0:7:2>Decode of Disrupting Error Status Reg (DESR HW Corrected) bits 00300000.00000000 2010-07-03 18:44:13.517 0:7:2> 1 DESR_SOCSRE: SOC (non-local) sw_recoverable_error. 2010-07-03 18:44:13.638 0:7:2> 1 DESR_SOCHCCE: SOC (non-local) hw_corrected_and_cleared_error. 2010-07-03 18:44:13.773 0:7:2> 2010-07-03 18:44:13.836 0:7:2>Decode of NCU Error Status Reg bits 00000000.22000000 2010-07-03 18:44:13.958 0:7:2> 1 NESR_MCU1SRE: MCU1 issued a Software Recoverable Error Request 2010-07-03 18:44:14.095 0:7:2> 1 NESR_MCU1HCCE: MCU1 issued a Hardware Corrected-and-Cleared Error Request 2010-07-03 18:44:14.248 0:7:2> 2010-07-03 18:44:14.296 0:7:2>Decode of Mem Error Status Reg Branch 1 bits 33044000.00000000 2010-07-03 18:44:14.427 0:7:2> 1 MEU 61 R/W1C Set to 1 on an UE if VEU = 1, or VEF = 1, or higher priority error in same cycle. 2010-07-03 18:44:14.614 0:7:2> 1 MEC 60 R/W1C Set to 1 on a CE if VEC = 1, or VEU = 1, or VEF = 1, or another error in same cycle. 2010-07-03 18:44:14.804 0:7:2> 1 VEU 57 R/W1C Set to 1 on an UE, if VEF = 0 and no fatal error is detected in same cycle. 2010-07-03 18:44:14.983 0:7:2> 1 VEC 56 R/W1C Set to 1 on a CE, if VEF = VEU = 0 and no fatal or UE is detected in same cycle. 2010-07-03 18:44:15.169 0:7:2> 1 DAU 50 R/W1C Set to 1 if the error was a DRAM access UE. 2010-07-03 18:44:15.304 0:7:2> 1 DAC 46 R/W1C Set to 1 if the error was a DRAM access CE. 2010-07-03 18:44:15.440 0:7:2> 2010-07-03 18:44:15.486 0:7:2> DRAM Error Address Reg for Branch 1 = 00000034.8647d2e0 2010-07-03 18:44:15.614 0:7:2> Physical Address is 00000005.d21bc0c0 2010-07-03 18:44:15.715 0:7:2> DRAM Error Location Reg for Branch 1 = 00000000.00000800 2010-07-03 18:44:15.842 0:7:2> DRAM Error Syndrome Reg for Branch 1 = dd1676ac.8c18c045 2010-07-03 18:44:15.967 0:7:2> DRAM Error Retry Reg for Branch 1 = 00000000.00000004 2010-07-03 18:44:16.086 0:7:2> DRAM Error RetrySyndrome 1 Reg for Branch 1 = a8a5f81e.f6411b5a 2010-07-03 18:44:16.218 0:7:2> DRAM Error Retry Syndrome 2 Reg for Branch 1 = a8a5f81e.f6411b5a 2010-07-03 18:44:16.351 0:7:2> DRAM Failover Location 0 for Branch 1 = 00000000.00000000 2010-07-03 18:44:16.475 0:7:2> DRAM Failover Location 1 for Branch 1 = 00000000.00000000 2010-07-03 18:44:16.604 0:7:2> 2010-07-03 18:44:16.648 0:7:2>ERROR: POST terminated prematurely. Not all system components tested. 2010-07-03 18:44:16.786 0:7:2>POST: Return to VBSC 2010-07-03 18:44:16.795 0:7:2>ERROR: 2010-07-03 18:44:16.839 0:7:2> POST toplevel status has the following failures: 2010-07-03 18:44:16.952 0:7:2> Node 0 ------------------------------- 2010-07-03 18:44:17.051 0:7:2> /SYS/MB/CMP0/MR0/BOB0/CH1/D0 (J1001) 2010-07-03 18:44:17.145 0:7:2> /SYS/MB/CMP0/MR0/BOB1/CH1/D0 (J3001) 2010-07-03 18:44:17.241 0:7:2>END_ERROR