Understanding System Administration Resources
Oracle VM Server for SPARC Overview
Multipathing Software Overview
Oracle Hardware Management Pack Overview
Oracle Enterprise Manager Ops Center Overview
Obtain the OpenBoot Prompt Under Various Conditions
Display the Oracle ILOM Prompt
Redirect the System Console to a Local Graphics Monitor
Powering the Server On and Off
Power On the Server (Oracle ILOM CLI)
Power Off the Server (Oracle ILOM CLI)
Power On the Server (Oracle ILOM Web Interface)
Power Off the Server (Oracle ILOM Web Interface)
Power On a Server With Multiple Active Domains (Oracle VM Server for SPARC)
Power Off a Server With Multiple Active Domains (Oracle VM Server for SPARC)
Reset the Server (Oracle Solaris)
Reset the Server (Oracle ILOM)
Booting and Shutting Down the OS
Booting and Shutting Down Oracle Solaris
Boot the OS Manually (OpenBoot)
Shut Down the OS (init Command)
Shut Down the OS (shutdown Command)
Obtain the OpenBoot Prompt (Oracle Solaris)
Obtain the OpenBoot Prompt (Oracle ILOM CLI)
Obtain the OpenBoot Prompt (Oracle ILOM Web Interface)
Configuring Boot and Restart Behavior
Change the Default Boot Device (OpenBoot)
Enable or Disable Automatic Booting (OpenBoot)
Enable or Disable Automatic Booting (Oracle Solaris)
OpenBoot Configuration Parameters
Boot Mode Overview (Oracle ILOM)
Configure the Host Boot Mode (Oracle VM Server for SPARC)
Change the Host Boot Mode Behavior at Reset (Oracle ILOM)
Manage the Host Boot Mode Script (Oracle ILOM)
Display the Host Boot Mode Expiration Date (Oracle ILOM)
Override OpenBoot Settings to Reset the Server
Server Restart Behavior Configuration (Oracle ILOM)
Changing Server Identification Information
Change Customer Data on FRU PROMs
Change Server Identifier Information
Restore the Host Power State at Restart
Specify the Host Power State at Restart
Disable or Reenable the Host Power-On Delay
Specify Parallel Boot of the SP and Host
Specify Host Virtual Keyswitch Behavior
Reset the Values in the SP to Default Values
Configuring SP and Host Network Addresses
Disable or Reenable Network Access to the SP
Display the SP Network Parameters
Connecting to the SP (In-band)
Oracle ILOM In-band (Sideband) Management
Configure SP In-band (Sideband) Access
Matching Devices to Device Names
Importance of Matching a Physical Device to a Name
Display Server Components (Oracle ILOM)
Locate Device Paths (OpenBoot)
Correlate WWN Device Names With Physical Locations (diskinfo Command)
probe-scsi-all Device Naming (OpenBoot)
Correlate WWN Device Names With Physical Locations (probe-scsi-all Command)
Identify a Disk Slot (Oracle Solaris)
WWN Syntax in an Oracle Solaris 10 Installation on an Individual Drive
WWN Syntax in an Oracle Solaris 10 Installation on a RAID Volume
RAID Capabilities in Oracle Enterprise Manager Ops Center
FCode-Based RAID Utility Commands
Prepare to Create a RAID Hardware Volume (FCode-based RAID Utility)
Hot-Spare Drives in RAID Volumes (LSI)
Determining if a Drive Has Failed
Locate Error Messages Related to Drives in a RAID Volume
Display Status (FCode-Based RAID Utility)
Display Status (sas2ircu Utility, LSI)
RAID Drive Replacement Strategies
Oracle Solaris uses the WWN (World Wide Name) 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, Oracle Solaris identified 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 cntWWNdn value. Instead, you can use one of the following alternative methods to map WWN-based device names to physical devices.
When the OS is not running, you can analyze the output of the OpenBoot command probe-scsi-all.
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 (Oracle Solaris) for more information.