Understanding the Server Module
Front and Rear Panel Components
Confirming Server Module and Site Specifications
Plan Communication With the Server Module During Installation
Prepare the Modular System and Server Module
Insert the Server Module Into the Chassis
Powering On the Server Module for the First Time
Method 1a – Power On the Host Through the CMM (Web Interface)
Method 1b – Power On the Host Through the CMM (CLI)
Method 2 – Power On the Host Through the CMM SER MGT Port (CLI)
Method 3 – Power On the Host Through the Front Panel (SP CLI)
Configuring the Oracle Solaris OS
Install Oracle Solaris Software From the Network
Oracle Solaris 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
Front and Rear Panel Components
Interpreting Log Files and System Messages
Checking if Oracle VTS Software Is Installed
Find the Modular System Chassis Serial Number
Find the Server Module Serial Number
Preparing the Server Module for Removal
Remove the Server Module From the Modular System
Clear the Fault and Verify the Functionality of the Replacement DIMM
Replacing the Server Module Enclosure Assembly (Motherboard)
Transfer Components to Another Enclosure Assembly
Returning the Server Module to Operation
Install the Server Module Into the Modular System
Power On the Host (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.