Front and Rear Panel Components
Plan Communication With the Server Module During Installation
Optional Component Installation
Modular System Chassis Preparation
Insert the Server Module Into the Chassis
Communicating With the Server Module During Startup
Monitor the Diagnostic Messages
Powering On the Server Module for the First Time
Initial Power-On Task Overview
Power On the System for the First Time
Install Oracle Solaris Software From the Network
Oracle Solaris Configuration Settings
Assign a Static IP Address to the Service Processor
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
Reset the Server From the Oracle Solaris OS
Reset the Server From Oracle ILOM
Reset the SP to Default Values
Important Hardware RAID Guidelines
Disk Zones for SPARC T3-1 Servers With Sixteen-Disk Backplanes
Displaying Disk Zone Information
Enabling and Disabling Disk Zoning In the Field
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 FRUdata Information
Change System Identifier Information
Restore Host Power State at Restart
Specify Host Power State at Restart
Disable or Re-Enable Power-On Delay
Specify Parallel Boot of the SP and Host
Configure Host Behavior With the Keyswitch State
Disable or Re-Enable Network Access to the SP
Display the DHCP Server IP Address
Using an In-band Connection to the SP
Configure the Host Boot Mode of 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 OpenBoot PROM 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
probe-scsi-all Output Example (SPARC T3-1, Eight-Disk Backplane)
probe-scsi-all Output Example (SPARC T3-1, Sixteen-Disk Backplane)
probe-scsi-all Output Example (SPARC T3-4)
Identify a Disk Slot Using probe-scsi-all (OBP)
Identify a Disk Slot Using prtconf (Oracle Solaris, Onboard Controllers)
Identify a Disk Slot Using prtconf (Oracle Solaris, Single Initiator)
WWN Syntax in an OS Installation on a Specific Device
WWN Syntax in an OS Installation on a RAID Volume
Front and Rear Panel Components
Interpreting Log Files and System Messages
Managing Faults (Oracle Solaris PSH)
Managing Components (ASR Commands)
Checking if Oracle VTS Software Is Installed
Find the Modular System Serial Number
Find the Server Module Serial Number
Removing the Server Module From the Modular System for Service
Clear the Fault and Verify the Functionality of the Replacement DIMM
Servicing a Service Processor Card
Remove the Service Processor Card
Install the Service Processor Card
Replacing the Server Module Enclosure Assembly
Transfer Components to Another Enclosure Assembly
Returning the Server Module to Operation
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 server module uses advanced ECC technology that corrects up to 4 bits in error on nibble boundaries, as long as the bits are all in the same DRAM. On some DIMMs, if a DRAM fails, the DIMM continues to function.
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 uncorrectable 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 system, 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.
Oracle Solaris PSH technology – A feature of the 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 the PSH technology.
Once you identify which DIMMs you want to replace, see Locate a Faulty DIMM (LEDs). After replacing a faulty DIMM, You must perform the instructions in Clear the Fault and Verify the Functionality of the Replacement DIMM.