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
Create a Hardware Mirrored Volume of the Default Boot Device
Create a Hardware Striped Volume
Configure a Hardware RAID Volume for the Solaris OS
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
Managing Faults Using the PSH Feature
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
# raidctl Controller: 1 Disk: 0.0.0 Disk: 0.1.0 Disk: 0.2.0 Disk: 0.3.0 Disk: 0.4.0 Disk: 0.5.0 Disk: 0.6.0 Disk: 0.7.0
See Disk Slot Numbers.
The preceding example indicates that no RAID volume exists. In another case:
# raidctl Controller: 1 Volume:c1t0d0 Disk: 0.0.0 Disk: 0.1.0 Disk: 0.2.0 Disk: 0.3.0 Disk: 0.4.0 Disk: 0.5.0 Disk: 0.6.0 Disk: 0.7.0
In this example, a single volume (c1t0d0) has been enabled.
The Sun SPARC Enterprise T5120 or T5220 server’s on-board SAS controller can configure as many as two RAID volumes. Prior to volume creation, ensure that the member disks are available and that there are not two volumes already created.
The RAID status might be:
OPTIMAL – Indicating that the RAID volume is online and fully synchronized.
SYNC – Indicating that the data between the primary and secondary member disks in an IM are still synchronizing.
DEGRADED – Indicating that a member disk is failed or otherwise offline.
FAILED – Indicating that volume should be deleted and reinitialized. This failure can occur when any member disk in an IS volume is lost, or when both disks are lost in an IM volume.
The Disk Status column displays the status of each physical disk. Each member disk might be GOOD, indicating that it is online and functioning properly, or it might be FAILED, indicating that the disk has hardware or configuration issues that need to be addressed.
For example, an IM with a secondary disk that has been removed from the chassis appears as:
# raidctl -l c1t0d0 Volume Size Stripe Status Cache RAID Sub Size Level Disk ---------------------------------------------------------------- c1t0d0 136.6G N/A DEGRADED OFF RAID1 0.1.0 136.6G GOOD N/A 136.6G FAILED
See the raidctl(1M) man page for additional details regarding volume and disk status.
Note - The logical device names might appear differently on your system, depending on the number and type of add-on disk controllers installed.
# raidctl -c primary secondary
The creation of the RAID volume is interactive, by default. For example:
# raidctl -c c1t0d0 c1t1d0 Creating RAID volume c1t0d0 will destroy all data on member disks, proceed (yes/no)? yes ... Volume c1t0d0 is created successfully! #
As an alternative, you can use the –f option to force the creation if you are sure of the member disks and sure that the data on both member disks can be lost. For example:
# raidctl -f -c c1t0d0 c1t1d0 Volume c1t0d0 is created successfully! #
When you create a RAID mirror, the secondary drive (in this case, c1t1d0) disappears from the Solaris device tree.
# raidctl -l c1t0d0 Volume Size Stripe Status Cache RAID Sub Size Level Disk ---------------------------------------------------------------- c1t0d0 136.6G N/A SYNC OFF RAID1 0.0.0 136.6G GOOD 0.1.0 136.6G GOOD
The preceding example indicates that the RAID mirror is still resynchronizing with the backup drive.
The following example shows that the RAID mirror is synchronized and online.
# raidctl -l c1t0d0 Volume Size Stripe Status Cache RAID Sub Size Level Disk ---------------------------------------------------------------- c1t0d0 136.6G N/A OPTIMAL OFF RAID1 0.0.0 136.6G GOOD 0.1.0 136.6G GOOD
The disk controller synchronizes IM volumes one at a time. If you create a second IM volume before the first IM volume completes its synchronization, the first volume’s RAID status will indicate SYNC, and the second volume’s RAID status will indicate OPTIMAL. Once the first volume has completed, its RAID status changes to OPTIMAL, and the second volume automatically starts synchronizing, with a RAID status of SYNC.
Under RAID 1 (disk mirroring), all data is duplicated on both drives. If a disk fails, replace it with a working drive and restore the mirror. For instructions, see Delete a Hardware RAID Volume.
For more information about the raidctl utility, see the raidctl(1M) man page.