Confirming Server and Site Specifications
Overcurrent Protection Requirements
DC Power Source, Power Connection, and Grounding Requirements
Stabilize the Rack for Installation
Mounting the Server Into a 4-Post Rack
Mounting the Server Into a 2-Post Rack
Connecting Data and Management Cables
Powering On the Server for the First Time
Connect a Terminal or Emulator to the SER MGT Port
Power On the Server for the First Time
Oracle Solaris OS Configuration Parameters
Assign a Static IP Address to the SP
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)
probe-scsi-all WWN Mapping Overview
probe-scsi-all WWN Mapping Example (SPARC T4-1)
probe-scsi-all WWN Mapping Example (Netra SPARC T4-1)
probe-scsi-all WWN Mapping Example (SPARC T4-2)
probe-scsi-all WWN Mapping Example (Netra SPARC T4-2)
probe-scsi-all WWN Mapping Example (SPARC T4-4 With Four CPUs)
probe-scsi-all WWN Mapping Example (SPARC T4-4 With Two CPUs)
probe-scsi-all WWN Mapping Example (SPARC T4-1B and Netra SPARC T4-1B)
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
Power Supply, Hard Drive, and Fan Module Locations
Top Cover, Filter Tray, and DVD Tray Locations
Motherboard, DIMMs, and PCI Board Locations
Understanding Fault Management Commands
Interpreting Log Files and System Messages
Checking if Oracle VTS Is Installed
Component Service Task Reference
Removing Power From the Server
Determine if the Hard Drive Fan Is Faulty
Servicing the Hard Drive Backplane
Determine if the Hard Drive Backplane Is Faulty
Remove the Hard Drive Backplane
Install the Hard Drive Backplane
Verify the Hard Drive Backplane
Servicing the Power Distribution Board
Determine if the Power Distribution Board Is Faulty
Remove the Power Distribution Board
Install the Power Distribution Board
Verify the Power Distribution Board
Determine if the DVD Drive Is Faulty
Determine if the LED Board Is Faulty
Determine if the Fan Board Is Faulty
Servicing the PCIe2 Mezzanine Board
Determine if the PCIe2 Mezzanine Board Is Faulty
Remove the PCIe2 Mezzanine Board
Install the PCIe2 Mezzanine Board
Verify the PCIe2 Mezzanine Board
Locate a Faulty PCIe2 Riser Card
Remove a PCIe2 Card From the PCIe2 Mezzanine Board
Remove a PCIe2 Card From the PCIe2 Riser Card
Install a PCIe2 Card Into the PCIe2 Mezzanine Board
Install a PCIe2 Card Into the PCIe2 Riser Card
Install SAS Cable for Sun Storage 6 Gb SAS PCIe RAID HBA, Internal
Servicing the Signal Interface Board
Determine if the Signal Interface Board Is Faulty
Remove the Signal Interface Board
Install the Signal Interface Board
Verify the Signal Interface Board
Determine if the Battery Is Faulty
Determine if the ID PROM Is Faulty
Determine if the Motherboard Is Faulty
Returning the Server to Operation
Power On the Server (Oracle ILOM)
The Oracle Solaris OS uses the World Wide Name (WWN) syntax in place of the locally unique tn (target ID) field in logical device names. This change affects how device names can be mapped to specific SCSI devices. The following points are key to understanding the impact of this change:
Before the change to WWN nomenclature, the Oracle Solaris OS would ordinarily identify the default boot device as c0t0d0.
With the change, the device identifier for the default boot device is now referred to as c0tWWNd0, where WWN is a hexadecimal value that is unique to this device throughout the world.
This WWN value is assigned by the manufacturer of the device and, therefore, has a random relationship to the server's device tree structure.
Because WWN values do not conform to the traditional logical device name structure, you cannot directly identify a target device from its c#tWWNd# value. Instead, you can use one of the following alternative methods to map WWN-based device names to physical devices.
One method consists of analyzing the output of the OBP command probe-scsi-all. You use this method when the OS is not running. See Mapping WWN Values to Hard Drives (OBP probe-scsi-all Command) for more information.
Note - For example, you would analyze probe-scsi-all output when you want to identify a boot device.
When the OS is running, you can analyze the output of the command prtconf -v. See Identify a Disk Slot Using prtconf (Oracle Solaris OS) for more information.