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

Update the Firmware

Selecting a Boot Device

Select a Boot Device

Administration

Basic Administrative Tasks

Initial System Setup

Communicating With the System

Performing Common Tasks

Manage Disk Volumes

Hardware RAID Support

Creating RAID Volumes

Removing Hardware RAID Volumes

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

Service

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

Index

Update the Firmware

  1. Ensure that the ILOM service processor network management port is configured.

    This configuration is required to access the new flash image over the network. See Configure the Service Processor Network Management Port.

  2. Open an SSH session to connect to the service processor.
    % ssh root@xx.xxx.xx.x 
    ...
    Are you sure you want to continue connecting (yes/no)? yes 
    ...
    Password: password (nothing displayed) 
    Waiting for daemons to initialize... 
     
    Daemons ready 
     
    Integrated Lights Out Manager 
     
    Version 2.0.0.0 
     
    Copyright 2007 Sun Microsystems, Inc. All rights reserved. 
    Use is subject to license terms. 
     
    -> 
  3. Verify that the host is powered off.

    If the host is not powered off, type the stop /SYS command.

    -> stop /SYS
  4. Verify that the keyswitch_state parameter is set to normal.
    -> set /SYS keyswitch_state=normal
  5. Type the load command.

    The load command updates the service processor flash image and the host firmware. The load command requires the following information:

    • IP address of a TFTP server on the network that can access the flash image

    • Full path name to the flash image that the IP address can access

      The command usage is as follows:

    load [-script] -source tftp://xxx.xxx.xx.xx/pathname

    where:

    • -script – Does not prompt for confirmation and acts as if yes was specified
    • -source Specifies the IP address and full path name (URI) to the flash image
      -> load -source tftp://xxx.xxx.xx.xx/pathname 
       NOTE: A firmware upgrade will cause the server and ILOM to 
             be reset. It is recommended that a clean shutdown of 
             the server be done prior to the upgrade procedure. 
             An upgrade takes about 6 minutes to complete. ILOM 
             will enter a special mode to load new firmware. No 
             other tasks can be performed in ILOM until the 
             firmware upgrade is complete and ILOM is reset. 
       
      Are you sure you want to load the specified file (y/n)? y 
      Do you want to preserve the configuration (y/n)? y 
      ...............................................................
       
      Firmware update is complete. 
      ILOM will now be restarted with the new firmware.
      Update complete. Reset device to use new image. 
       
      -> 

      After the flash image has been updated, the system will automatically reset.

      The service processor resets, runs diagnostics, and returns to the login prompt (on the serial console), similar to the following example.

      U-Boot 1.1.1 (May 23 2007 - 21:30:12)
      ...
      POST cpu PASSED
      POST ethernet PASSED
      Hit any key to stop autoboot:  0
      ## Booting image at fe080000 ...
       
      IP Protocols: ICMP, UDP, TCP, IGMP
       
      Checking all file systems...
      fsck 1.37 (21-Mar-2005)
      Setting kernel variables ... 
      ... done. 
      Mounting local filesystems... 
      Cleaning /tmp /var/run /var/lock. 
       
      Identifying DOC Device Type(G3/G4/H3) ... 
      OK 
       
      Configuring network interfaces...Internet Systems Consortium DHCP 
      Client V3.0.1 
      Copyright 2007 Internet Systems Consortium. 
      All rights reserved. 
      For info, please visit http://www.isc.org/products/DHCP 
       
      eth0: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX. 
      Listening on LPF/eth0/00:14:4f:3f:8c:af 
      Sending on   LPF/eth0/00:14:4f:3f:8c:af 
      Sending on   Socket/fallback 
      DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 
      eth0: link up, 100 Mbps Full Duplex, auto-negotiation complete. 
      DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 
      Hostname: hostname. 
      Starting portmap daemon: portmap. 
      Initializing random number generator...done. 
      INIT: Entering runlevel: 3 
      Starting system log daemon: syslogd and klogd. 
      Starting periodic command scheduler: cron. 
      Starting IPMI Stack...... Done. 
      Starting OpenBSD Secure Shell server: sshd. 
      Starting Servicetags listener: stlistener. 
      Starting FRU update program: frutool. 
       
      hostname login: