JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Sun SPARC Enterprise T5440 Server Topic Set
search filter icon
search icon

Document Information

Using This Documentation

Related Documentation

Documentation, Support, and Training

Site Planning

SPARC Enterprise T5440 Site Planning Guide

Physical Specifications

Minimum Clearance for Service Access

Environmental Specifications

Power Source Requirements

Acoustic Noise Emissions

Agency Compliance Specifications

Operating Environment Requirements

Installation and Setup

Preparing for Installation

About the SPARC Enterprise T5440 Server

Tools and Equipment Needed

Installation Overview

Cabling Notes

About the Slide Rail Assembly

About the Cable Management Arm

Rack Compatibility Requirements

Safety Precautions

ESD Precautions

Installing the SPARC Enterprise T5440 Server

Installing the Rack Slide Assembly

Installing the Server Into the Cabinet

Installing the Cable Management Arm (CMA)

Connecting the Server Cables

Managing Cables With the CMA

Powering On the System

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 the Firmware

Updating Service Processor and Server Firmware

Updating the Firmware

Selecting a Boot Device

Select a Boot Device


Basic Administrative Tasks

Initial System Setup

Communicating With the System

Performing Common Tasks

Manage Disk Volumes

Hardware RAID Support

Creating RAID Volumes

Create a Hardware Mirrored Volume

Create a Hardware Mirrored Volume of the Default Boot Device

Create a Hardware Striped Volume

Configure and Label a Hardware RAID Volume for Use in the Solaris Operating System

Disk Slot Numbers

Removing Hardware RAID Volumes

Delete a Hardware RAID Volume

Hot-Plug a Mirrored Disk

Hot-Plug a Nonmirrored Disk

Manage the System

Searching for Faults

Bypassing Minor Faults

Clearing Faults

Managing Devices

Use Logical Domains Software

Understanding Logical Domains Software

Operating the Solaris OS With Logical Domains

ALOM-to-ILOM Command Reference

ILOM and ALOM CMT Command Comparison Tables

Remote Management

Understanding ILOM for the Sun SPARC Enterprise T5440 Server

ILOM Overview

Platform-Specific ILOM Features

ILOM Features Not Supported

Managing the Host

Resetting the Host

Managing Host Boot Mode

Viewing and Configuring Host Control Information

Managing System User Interactions

Managing the Service Processor

Storing Customer Information

Display Console History (CLI)

Change Console Escape Characters (CLI)

Changing Configuration Policy Settings

Managing Network Access

Managing Devices

Managing Virtual Keyswitch Settings

IPMI Sensor Reference

Sensors on Sun SPARC Enterprise T5440 Server

Indicators on the Sun SPARC Enterprise T5440 Server Server

ALOM CMT Compatibility Shell

Limits to Backward Compatibility

Create an ALOM CMT Compatibility Shell

ILOM and ALOM CMT Command Comparison

ALOM CMT Variables

ALOM CMT Variable Comparison

Event Messages Available Through the ALOM Compatibility Shell

Event Message Overview

Event Severity Levels

Service Processor Usage Event Messages

Environmental Monitoring Event Messages

Host Monitoring Event Messages

SCC Backup and Restore

Information Stored on The SCC


Identifying Server Components

Infrastructure Boards and Cables

Front Panel Diagram

Front Panel LEDs

Rear Panel Diagram

Rear Panel LEDs

Ethernet Port LEDs

Managing Faults

Understanding Fault Handling Options

Connecting to the Service Processor

Displaying FRU Information With Oracle ILOM

Controlling How POST Runs

Detecting Faults

Clearing Faults

Disabling Faulty Components

Oracle ILOM-to-ALOM CMT Command Reference

Preparing to Service the System

Safety Information

Required Tools

Obtain the Chassis Serial Number

Obtain the Chassis Serial Number Remotely

Powering Off the System

Extending the Server to the Maintenance Position

Remove the Server From the Rack

Perform Electrostatic Discharge – Antistatic Prevention Measures

Remove the Top Cover

Servicing Customer-Replaceable Units

Hot-Pluggable and Hot‐Swappable Devices

Servicing Hard Drives

Servicing Fan Trays

Servicing Power Supplies

Servicing PCIe Cards

Servicing CMP/Memory Modules

Servicing FB-DIMMs

Servicing Field-Replaceable Units

Servicing the Front Bezel

Servicing the DVD-ROM Drive

Servicing the Service Processor

Servicing the IDPROM

Servicing the Battery

Servicing the Power Distribution Board

Servicing the Fan Tray Carriage

Servicing the Hard Drive Backplane

Servicing the Motherboard

Servicing the Flex Cable Assembly

Servicing the Front Control Panel

Servicing the Front I/O Board

Returning the Server to Operation

Install the Top Cover

Install the Server Into the Rack

Slide the Server Into the Rack

Connect the Power Cords to the Server

Power On the Server

Performing Node Reconfiguration

I/O Connections to CMP/Memory Modules

Recovering From a Failed CMP/Memory Module

System Bus Topology

I/O Fabric in 2P Configuration

I/O Fabric in 4P Configuration

Identifying Connector Pinouts

Serial Management Port Connector Pinouts

Network Management Port Connector Pinouts

Serial Port Connector Pinouts

USB Connector Pinouts

Gigabit Ethernet Connector Pinouts

Server Components

Customer-Replaceable Units

Field-Replaceable Units


Create a Hardware Mirrored Volume of the Default Boot Device

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).

  1. Determine which disk is the default boot device.

    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         
  2. Type the boot net -s command.
    ok boot net -s
  3. Once the system boots, use the raidctl(1M) utility to create a hardware mirrored volume, using the default boot device as the primary disk.

    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
  4. Install the volume with the Solaris OS using any supported method.

    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.

  5. To configure the volume for use with Solaris, see Configure and Label a Hardware RAID Volume for Use in the Solaris Operating System.
Related Information