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)
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)
A variety of features play a role in how the memory subsystem is configured and how memory faults are handled. Understanding the underlying features helps you identify and repair memory problems. This topic describes how the server module deals with memory faults.
The following server module features independently manage memory faults:
POST – Based on Oracle ILOM configuration variables, POST runs when the server module is powered on.
For correctable memory errors (sometimes called CEs), POST forwards the error to the Oracle Solaris PSH daemon for error handling.
If an incorrect memory fault is detected, POST displays the fault with the device name of the faulty DIMMs, and logs the fault. POST then disables the faulty DIMMs. Depending on the memory configuration and the location of the faulty DIMM, POST disables half of physical memory in the server module, or half the physical memory and half the processor threads. When the offlining process occurs in normal operation, you must replace the faulty DIMMs based on the fault message and then enable the disabled DIMMs. See Clear the Fault and Verify the Functionality of the Replacement DIMM.
PSH – A feature of the Oracle Solaris OS, PSH uses the fault manager daemon (fmd) to watch for various kinds of faults. When a fault occurs, the fault is assigned a UUID and logged. PSH reports the fault and suggests a replacement for the DIMMs associated with the fault.
If you suspect that the server module has a memory problem, follow the Diagnostics Process. The flowchart helps you determine if the memory problem was detected by POST or by PSH.
Once you identify which DIMMs you want to replace, see Locate a Faulty DIMM. After replacing a faulty DIMM, you must perform the instructions in Clear the Fault and Verify the Functionality of the Replacement DIMM.