Documentation, Support, and Training
SPARC Enterprise T5440 Site Planning Guide
Minimum Clearance for Service Access
Agency Compliance Specifications
Operating Environment Requirements
About the SPARC Enterprise T5440 Server
About the Cable Management Arm
Rack Compatibility Requirements
Installing the SPARC Enterprise T5440 Server
Installing the Rack Slide Assembly
Installing the Server Into the Cabinet
Installing the Cable Management Arm (CMA)
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
Booting the Solaris Operating System
Updating Service Processor and Server Firmware
Create a Hardware Mirrored Volume
Create a Hardware Striped Volume
Configure and Label a Hardware RAID Volume for Use in the Solaris Operating System
Removing Hardware RAID Volumes
Understanding Logical Domains Software
Operating the Solaris OS With Logical Domains
ALOM-to-ILOM Command Reference
ILOM and ALOM CMT Command Comparison Tables
Understanding ILOM for the Sun SPARC Enterprise T5440 Server
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
Managing Virtual Keyswitch Settings
Sensors on Sun SPARC Enterprise T5440 Server
Indicators on the Sun SPARC Enterprise T5440 Server Server
Limits to Backward Compatibility
Create an ALOM CMT Compatibility Shell
ILOM and ALOM CMT Command Comparison
Event Messages Available Through the ALOM Compatibility Shell
Service Processor Usage Event Messages
Environmental Monitoring Event Messages
Host Monitoring Event Messages
Infrastructure Boards and Cables
Understanding Fault Handling Options
Connecting to the Service Processor
Displaying FRU Information With Oracle ILOM
Oracle ILOM-to-ALOM CMT Command Reference
Preparing to Service the System
Obtain the Chassis Serial Number
Obtain the Chassis Serial Number Remotely
Extending the Server to the Maintenance Position
Remove the Server From the Rack
Perform Electrostatic Discharge – Antistatic Prevention Measures
Servicing Customer-Replaceable Units
Hot-Pluggable and Hot‐Swappable Devices
Servicing Field-Replaceable Units
Servicing the Service Processor
Servicing the Power Distribution Board
Servicing the Fan Tray Carriage
Servicing the Hard Drive Backplane
Servicing the Flex Cable Assembly
Servicing the Front Control Panel
Returning the Server to Operation
Install the Server Into the Rack
Slide the Server Into the Rack
Connect the Power Cords to the Server
Performing Node Reconfiguration
I/O Connections to CMP/Memory Modules
Recovering From a Failed CMP/Memory Module
I/O Fabric in 2P Configuration
I/O Fabric in 4P Configuration
Serial Management Port Connector Pinouts
Network Management Port Connector Pinouts
Before You Begin
Due to the volume initialization that occurs on the disk controller when a new volume is created, the volume must be configured and labeled using the format(1M)utility prior to use with the Solaris OS. See Configure and Label a Hardware RAID Volume for Use in the Solaris Operating System.
Because of this limitation, raidctl(1M) blocks the creation of a hardware RAID volume if any of the member disks currently have a file system mounted.
This section describes the procedure required to create a hardware RAID volume containing the default boot device. Since the boot device always has a mounted file system when booted, an alternate boot medium must be employed, and the volume created in that environment. One alternate medium is a network installation image in single-user mode (refer to the Solaris 10 Installation Guide for more information about configuring and using network-based installations).
From the OpenBoot ok prompt, type the printenv command, and if necessary, the devalias command, to identify the default boot device. For example:
ok printenv boot-device boot-device = disk ok devalias disk disk /pci@0/pci@0/pci@2/scsi@0/disk@0,0
ok boot net -s
See Create a Hardware Mirrored Volume.
# raidctl -c -r 1 c0t0d0 c0t1d0 Creating RAID volume c0t0d0 will destroy all data on member disks, proceed (yes/no) ? yes Volume c0t0d0 created #
The hardware RAID volume c0t0d0 appears as a disk to the Solaris installation program.
Note - The logical device names might appear differently on your system, depending on the number and type of add-on disk controllers installed.