Exit Print View

Sun Blade 6000 Disk Module Administration Guide

Get PDF Book Print View
 

Document Information

Preface

1.  Overview of Using Sun Blade 6000 Disk Modules With Server Modules

2.  Inserting, Moving and Replacing the Sun Blade 6000 Disk Module

3.  System Requirements

4.  Upgrading Systems

5.  Installing, Removing or Replacing Disks

6.  Multipathing and RAID

7.  How LSI Host Bus Adapters Assign Target IDs to Expanders, Disks, and RAID Volumes

8.  How Adaptec Host Bus Adapters Assign Target IDs to Expanders, Disks, and RAID Volumes

9.  Setting Up Hardware RAID Volumes With LSI and Adaptec Host Bus Adapters

10.  ILOM For the Sun Blade 6000 Disk Module

ILOM on the CMM

ILOM 2.0 Proxy CLI Program For SAS-NEMs and Disk Modules

To Start the ILOM 2.0 Proxy CLI Program

Navigation Using the CMM ILOM CLI

CMM ILOM Management and Monitoring for SAS-NEMs and Disk Modules

Upgrading CMM ILOM Firmware

To upgrade ILOM Firmware Using the CLI

To upgrade ILOM Firmware Using the ILOM Web Interface

11.  Oracle's Sun Storage Common Array Manager (CAM)

A.  Using the SIA Application to Upgrade x86 Server Blade and Host Bus Adapter Firmware

B.  Using the lsiutil Software

C.  Upgrading the Disk Module to Allow a SAS-2 Compatible Server Blade in the Chassis

Index

Chapter 10

ILOM For the Sun Blade 6000 Disk Module

This chapter contains these topics:

ILOM on the CMM

The Oracle Integrated Lights Out Manager (ILOM) on the Chassis Monitoring Module (CMM) provides minimal information for disk blades or SAS-NEMs.

The ILOM graphical user interface recognizes the presence of SAS-NEMs and disk blades but does not interact with them.

The ILOM CLI (command-line interface) can get FRU and SEEPROM information from both SAS-NEMs and disk blades, but does not provide any diagnostic information. Refer to the Sun Blade 6000 Multi-Fabric Network Express Module User’s Guide (820-1705) for details.

ILOM generates logs that record if a disk blade or SAS-NEM is inserted, removed, powered up, or powered down.

ILOM also monitors the Service LED on the Sun Blade 6000 Disk Module and SAS-NEM blades in the chassis. The Service LED is turned on for an over-temperature or over-voltage condition. If this light is turned on or off, the corresponding IPMI state sensor changes and a log entry is generated.


Note - A sudden over-temperature or over-voltage surge will power off the SAS-NEM or disk blade. When such a rapid shut down occurs, the Service LED is also turned off. However, this type of event is recorded in the log.


To see the CMM log for the SAS-NEMs and disk blades (as well as any server blades present), run this command from the CMM CLI:

-> show /CMM/logs/event/list

For ILOM version 2.0, if you want to monitor and interact with SAS-NEMs and disk blades you must use a special ILOM proxy program. ILOM 3.0 does not require a proxy program.

ILOM 2.0 Proxy CLI Program For SAS-NEMs and Disk Modules

If you are using CMM ILOM 2.0 (version 2.0.3.10 or later), you use a CLI-based proxy program to monitor and control your disk modules and SAS-NEM modules.


Note - There is no proxy CLI for ILOM 3.0.


You can connect to the ILOM CLI by either of two means:

Instructions for setting up and using ILOM are documented in the Sun Integrated Lights Out Manager 2.0 User’s Guide, available at:

http://docs.sun.com/app/docs/doc/820-1188

To Start the ILOM 2.0 Proxy CLI Program

Before You Begin

Prerequisite: To start the ILOM 2.0 proxy CLI, a SAS-NEM module must be installed in the chassis in either NEM slot 0 or NEM slot 1.

Navigation Using the CMM ILOM CLI

With the CMM ILOM CLI (either with the proxy CLI for ILOM 2.0, or the standard CLI with ILOM 3.0), you navigate through a tree consisting of all the SAS-NEMs and disk modules (called targets) in the chassis. You can use standard Linux and Unix commands such as cd or pwd to navigate through the tree.

The tree consists of all the SAS-NEMs and disk blades in the chassis.

The CLI Tree of Targets
Graphic showing CLI tree of targets.

You can use these commands to navigate through the tree:

You can use these commands on module targets (NEMx and BLx):

You can use this command on property targets:

You can use these commands at any time:

CMM ILOM Management and Monitoring for SAS-NEMs and Disk Modules

The CMM ILOM CLI (ILOM 2.0 or 3.0) allows you to do the following:

Upgrading CMM ILOM Firmware

ILOM 2.0.3.10, build 36968 for the Sun Blade 6000 System chassis is the minimum version required for use with disk blades and SAS-NEMs. This firmware can be downloaded from:

http://www.oracle.com/goto/blades

You can upgrade your ILOM firmware in two ways: by using the CLI or by using the ILOM web interface.

To upgrade ILOM Firmware Using the CLI

Use a tftp server:

  1. Put the .ima file in the /tftpboot directory.

  2. In the CLI, run this command:

    -> load -source tftp://<IPadd>/ilom.6000-2.0.3.10-r36968.ima

    where IPadd is the IP address of your tftp server.

To upgrade ILOM Firmware Using the ILOM Web Interface

  1. Log in as any user with Administrator privileges.

  2. Select Maintenance --> Firmware Upgrade.

    The Firmware Upgrade page appears.

  3. Click Enter Upgrade Mode.

    A dialog box appears asking you to confirm that you want to enter Upgrade mode.

  4. Click OK to enter Upgrade mode.

    ILOM stops its normal operation and prepares for a flash upgrade.

  5. Enter the path to the new ILOM .ima file in the Select Image File to Upload field or click Browse to locate and select the .ima file.

  6. Click Upload.

    After a short pause, a Firmware Verification screen appears that shows the current firmware version and the requested upgrade version.

  7. Click Start Upgrade.

    The process takes about 6 minutes. At the end, the service processor is reset.