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)
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
By default, you connect to the server's SP using the out-of-band NET MGT port. The Oracle ILOM sideband management feature enables you to select either the NET MGT port or one of the server's Gigabit Ethernet ports (named NETn), which are in-band ports, to send and receive Oracle ILOM commands to and from the server SP. In-band ports are also called sideband ports.
The advantage of using a sideband management port to manage the server's SP is that one fewer cable connection and one fewer network switch port are needed. In configurations where numerous servers are being managed, such as data centers, sideband management can represent a significant savings in hardware and network utilization.
When sideband management is enabled in Oracle ILOM, the following conditions might occur:
Connectivity to the server SP might be lost when the SP management port configuration is changed while you are connected to the SP using a network connection, such as SSH, web, or Oracle ILOM Remote Console.
In-chip connectivity between the SP and the host operating system might not be supported by the on-board host Gigabit Ethernet controller. If this condition occurs, use a different port or route to transmit traffic between the source and destination targets instead of using L2 bridging or switching.
Server host power cycles might cause a brief interruption of network connectivity for server Gigabit Ethernet ports that are configured for sideband management. If this condition occurs, configure the adjacent switch or bridge ports as host ports.