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 SP In-band (Sideband) Access
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
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)
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 (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.
Note - In-band connection is not recommended for server modules.
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/switching.
Server host power cycles might cause a brief interruption of network connectivity for server Gigabit Ethernet ports (NETn) that are configured for sideband management. If this condition occurs, configure the adjacent switch/bridge ports as host ports.