Documentation, Support, and Training
Sun SPARC Enterprise T5120 and T5220 Servers Site Planning Guide
Minimum Clearance for Service Access
Agency Compliance Specifications
Operating Environment Requirements
Input Power Information and Precautions
Optional Component Installation
Configuring the Service Processor
Cabling Notes for Both Servers
Port, Connector, and LED Locations for Both Servers
Slide Rail Assembly Notes for Both Servers
Cable Management Notes for Both Servers
Installing the SPARC Enterprise T5120 and T5220 Servers
Installing the Servers in a Rack
Installing the Cable Management Arm for Both Servers
Connecting the Server Cables for Both Servers
Powering On the System for the First Time
Enabling the Service Processor Network Management Port
Logging Into the Service Processor
Using the Service Processor for Common Operations
Perform a Normal System Initialization
Devices in the OpenBoot Device Tree
Boot the Solaris Operating System
Avoid Booting the Solaris Operating System at Startup
Verifying System Functionality
Installing the Servers With the Express Rail Rackmounting Kit
Slide Rail Assembly Notes for the Express Rail Rackmounting Kit
Installing the Servers in a Rack With Express Rails
Installing the Cable Management Arm
Assembling and Installing DC Power Cables for the Sun SPARC Enterprise T5120 Server
Requirements for Servers With DC Input Power
DC Supply and Ground Conductor Requirements
Overcurrent Protection Requirements
Assembling and Installing the DC Input Power Cables
Connecting the DC Input Power Cords to the Server
Assembling and Installing DC Power Cables for the Sun SPARC Enterprise T5220 Server
Requirements for Servers With DC Input Power
Assembling and Installing the DC Input Power Cables
Creating Hardware RAID Volumes
Devices and Device Identifiers
Sun SPARC Enterprise T5x20 Device Tree
Managing Logical Domains Software
Logical Domains Software Overview
View OpenBoot Configuration Variables
OpenBoot Configuration Variables on the SCC
Understanding ILOM 3.0 for the Sun SPARC Enterprise T5120 and T5220 Servers
Platform-Specific ILOM Features
Viewing and Configuring Host Control Information
Managing System User Interactions
Managing the Service Processor
Change Console Escape Characters (CLI)
Changing Configuration Policy Settings
ILOM Information Stored on the SCC
Managing Virtual Keyswitch Settings
Discover IPMI Sensors and Indicators
Sensors on Sun SPARC Enterprise T5120 and T5220 Servers
Indicators on Oracle's Sun SPARC Enterprise T5120 and T5220 Servers
Discover ALOM Compatibility Information
Event Messages Available Through the ALOM Compatibility Shell
SPARC: Infrastructure Boards in Sun SPARC Enterprise T5120 Servers
SPARC: Infrastructure Boards in Sun SPARC Enterprise T5220 Servers
Internal System Cables for Sun SPARC Enterprise T5120 Servers
Internal System Cables for Sun SPARC Enterprise T5220 Servers
Front Panel Controls and Indicators on Sun SPARC Enterprise T5120 Servers
Rear Panel Components and Indicators on Sun SPARC Enterprise T5120 Servers
Front Panel Controls and Indicators on Sun SPARC Enterprise T5220 Servers
Rear Panel Components and Indicators on Sun SPARC Enterprise T5220 Servers
Status LEDs for Ethernet Ports and Network Management Port
Diagnostics Tools Quick Reference
Service-Related ILOM Command Summary
Faults Displayed by show faulty
Display FRU Information With the show Command
ILOM Properties that Affect POST Behavior
Managing Faults Using the PSH Feature
PSH-Detected Fault Console Message
Identify PSH-Detected Faults With fmdump
View the System Message Log Files
Managing Components With Automatic System Recovery Commands
Detecting Faults Using SunVTS Software
Preparing to Service the System
Find the Chassis Serial Number
Removing Power From the System
Positioning the System for Servicing
Four-Drive Capable Backplane Configuration Reference
Eight-Drive Capable Backplane Configuration Reference
Sixteen-Drive Capable Backplane Configuration Reference
Servicing Motherboard Components
Servicing the Motherboard Assembly
Power Supply Configuration Reference
Servicing Boards and Components
Servicing the Hard Drive Backplane
Servicing Front Control Panel Light Pipe Assemblies
Servicing Power Distribution Boards
Servicing Power Supply Backplanes (Sun SPARC Enterprise T5220 Servers)
Returning the Server to Operation
Reinstall the Server in the Rack
Return the Server to the Normal Rack Position
Connect Power Cords to the Server
Power On the Server Using the poweron Command
Power On the Server Using the Front Panel Power Button
Identifying FRUs in SPARC Enterprise T5120 Servers
Motherboard Components in T5120 Servers
I/O Components in SPARC Enterprise T5120 Servers
Power Distribution/Fan Module Components in SPARC Enterprise T5120 Servers
Internal Cables for Onboard SAS Controller Cards in SPARC Enterprise T5120 Servers
Identifying FRUs in Sun SPARC Enterprise T5220 Servers
Motherboard Components in T5220 Servers
I/O Components in Sun SPARC Enterprise T5220 Servers
Power Distribution/Fan Module Components in Sun SPARC Enterprise T5220 Servers
Internal Cables for Onboard SAS Controller Cards in Sun SPARC Enterprise T5220 Servers
HDD Data Cable Routing for SAS RAID Controller Cards in Sun SPARC Enterprise T5220 Servers
ILOM enables you to remotely run diagnostics such as power-on self-test (POST), that would otherwise require physical proximity to the server’s serial port. You can also configure ILOM to send email alerts of hardware failures, hardware warnings, and other events related to the server or to ILOM.
The service processor runs independently of the server, using the server’s standby power. Therefore, ILOM firmware and software continue to function when the server OS goes offline or when the server is powered off.
Faults detected by ILOM, POST, and the Solaris Predictive Self-Healing (PSH) technology are forwarded to ILOM for fault handling.
Figure 56 Fault Reporting Through the ILOM Fault Manager
In the event of a system fault, ILOM ensures that the Service Required LED is turned on, FRUID PROMs are updated, the fault is logged, and alerts are displayed. Faulty FRUs are identified in fault messages using the FRU name.
The service processor can detect when a fault is no longer present. When this happens, it clears the fault state in the FRU PROM and extinguishes the Service Required LED.
A fault condition can be removed in two ways:
Unaided recovery – Faults caused by environmental conditions can clear automatically if the condition responsible for the fault improves over time.
Repaired fault – When a fault is repaired by human intervention, such as a FRU replacement, the service processor will usually detect the repair automatically and extinguish the Service Required LED.
Many environmental faults can automatically recover. For example, a temporary condition may cause the computer room temperature to rise above the maximum threshold, producing an overtemperature fault in the server. If the computer room temperature then returns to the normal range and the server’s internal temperature also drops back to an acceptable level, the service processor will detect the new fault-free condition. It will extinguish the Service Required LED and clear the fault state from the FRU PROM.
Note - No ILOM command is needed to manually repair an environmental fault.
The service processor can automatically detect when a FRU is removed. In many cases, it does this even if the FRU is removed while the service processor is not running.
Note - If the service processor does not automatically clear a fault state after the fault is corrected, you must perform these tasks manually. The procedure for clearing faults manually is described in Clear FRU Faults Manually.
Note - ILOM does not automatically detect hard drive replacement.
The Solaris Predictive Self-Healing technology does not monitor hard drives for faults. As a result, the service processor does not recognize hard drive faults and will not light the fault LEDs on either the chassis or the hard drive itself. Use the Solaris message files to view hard drive faults.
For general information about ILOM, see the Oracle Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide.
For detailed information about ILOM features that are specific to this server, see the Oracle Integrated Lights Out Manager (ILOM) 3.0 Supplement for SPARC Enterprise T5120 and T5220 Servers.
Before you can run ILOM commands, you must connect to the service processor. You can do this using either of the following methods:
Connect an ASCII terminal directly to the serial management port.
Use the ssh command to connect to service processor through an Ethernet connection on the network management port.
Note - Refer to the Oracle Integrated Lights Out Manager (ILOM) 3.0 Supplement for SPARC Enterprise T5120 and T5220 Servers for instructions on configuring and connecting to ILOM.
The following example shows the character sequence (hash-period) used to change from the system console to the service processor:
ok #.
The following example showiest ILOM command for changing from the service processor to the system console:
-> start /SP/console
If you are connected to the service processor using the ALOM CMT shell, use the following command to change to the system console:
sc> console