IBM BladeCenter S SAS RAID Controller Module Installation And User Manual

Download



IBM SAS RAID Controller Module

Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module



IBM SAS RAID Controller Module

Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

Note

Before using this information and the product it supports, read the information in the “Notices” on page 191 section.

Fourteenth Edition (July 2013)

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Tables ...............vii

Chapter 1. Introduction ........1

Product description and package contents ....2

System requirements...........3

Interface choices and functions .......3

Workflow notes ...........4

Documentation notes ..........4

Preinstallation safety information .......5

Handling static-sensitive devices........8

Hardware features and specifications ......9

Component illustrations .........10

Logical identifiers and physical location codes . . 11

Option package contents .........11

Tables

1. Interfaces and functions .........3

2. Important notes ...........4

3. Features ..............9

4. Battery Backup Unit part number .....13

5. RAID levels and characteristics ......36

6. Drive configurations per RAID level ....37

7. Service mode conditions ........74

8. Tape devices supported by the IBM BladeCenter S SAS RAID Controller Module . 95

9. Light path diagnostics LED details .....98

10. Alert types generated by the RAID Controller 106

11. Alert Attribute descriptions .......107

12. Configuration and Log Files ......151

13. Limits for particulates and gases .....193

viii IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

Chapter 1. Introduction

The IBM BladeCenter S SAS RAID Controller Module provides a fully-integrated shared storage solution in an IBM BladeCenter S chassis. This guide contains instructions for the installation of the IBM BladeCenter S SAS RAID Controller Modules (SAS RAID Modules) into an IBM BladeCenter S chassis. This guide also contains information about the interfaces you can use to configure and maintain your SAS RAID Modules and other associated components you might be using.

Data storage subsystems

Two subsystems are involved in IBM BladeCenter S data storage: the Disk Storage Module (DSM), and SAS RAID Module. The Disk Storage Module (DSM) is an enclosure holding up to six Disk Drive Modules (DDMs). There are a maximum of two DSMs installed in an IBM BladeCenter S chassis.

SAS RAID Module subsystems

The SAS RAID Module includes two subsystems: a RAID Controller subsystem, and a SAS Switch subsystem. The SAS RAID Modules provide a connection between the Blade servers and the DSMs that allow you to design storage configurations and volumes for your data.

In addition, a SAS Expansion Card must be installed in each blade server for the blades to connect to the RAID Data Storage subsystem and modules.

Firmware updates

The DDM, DSM, RAID Controller, and SAS Switch require firmware updates. Two methods of updating the firmware are as follows:

v IBM Storage Configuration Manager (SCM)

The IBM Storage Configuration Manager is a web-based system management application that you can use to update firmware on the IBM BladeCenter S SAS RAID Controller Module, DSM, and DDM, as well as manage and configure

BladeCenter®devices.

IBM

Note:

1. Firmware update and Raid configuration through IBM Storage Configuration Manager is NOT supported for DSM_SFF (DSM-12) configuration or mix configuration (DSM_LFF (DSM-6) combined with DSM_SFF).

2. Install IBM Storage Configuration Manager on an Ethernet connected workstation or laptop. For installation and configuration instructions, refer to the IBM Storage Configuration Manager documentation.

v SAS RAID Controller Firmware Update Package

The SAS RAID Controller Firmware Update Package is a CLI- based application package that you can use to update the IBM BladeCenter S SAS RAID Controller Module, DSM and DDM firmware. You can also write scripts automating firmware updates of single or multiple IBM BladeCenter S units.

Note: Install the SAS RAID Controller Firmware Update Package on an Ethernet connected workstation or laptop running a Windows or Linux operating system.

For more information about the RAID controller card, search for the RAID Expansion Card Installation and User's Guide at http://www.ibm.com/systems/ support/.

For additional information about other BladeCenter components, see the instructions in your BladeCenter documentation.

Product description and package contents

The IBM BladeCenter S SAS RAID Controller Module provides fully-integrated RAID Storage Area Network (SAN) functionality, inside your IBM BladeCenter S chassis. Each IBM BladeCenter S SAS RAID Controller Module ships with the following:

v 43W3584 IBM BladeCenter S SAS RAID Controller Module Option v 46C8000 Publication Package v 90Y5612 Quick Start Manual v 90Y5570 Support CD v 90Y5611 Flyer v 17P8568 L1 for Battery Backup Unit v 22R6649 Top Level Assembly Battery Backup Unit v 43W3604 L1 for IBM BladeCenter S SAS RAID Controller Module v 17P9375 Aristos EULA v 17P9277 Top Level Assembly IBM BladeCenter S SAS RAID Controller Module

The IBM BladeCenter S SAS RAID Controller Module consists of an integrated SAS Switch combined with a RAID Controller which provides an embedded RAID storage solution with advanced SAN features to the IBM BladeCenter S chassis. Your IBM BladeCenter S SAS RAID Controller Module features the IBM Storage Configuration Manager which provides end-to-end storage management:

v Fast and easy set up with the Initial Setup wizard v System health monitoring v Storage configuration (creates pools, defines volumes, and maps to hosts) v SAS RAID Module maintenance including firmware updates and device user

management

v Troubleshooting

Supported operating systems and drives

The IBM BladeCenter Interoperability guide provides a listing of the interoperability between operating systems, drive types, and other components supported for use with the IBM BladeCenter S SAS RAID Controller Module. This guide is updated periodically, so check this location for the latest copy: https://www.ibm.com/ systems/support/supportsite.wss/docdisplay?lndocid=MIGR-5073016 &brandind=5000020.

2 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

System requirements

The IBM BladeCenter S SAS RAID Controller Module functions only within the IBM BladeCenter S chassis. The following are also required:

v One or two IBM BladeCenter S SAS RAID Controller Modules. If you install two

SAS RAID Modules, you must install them in I/O module bay 3 and I/O module bay 4. If you install one SAS RAID Module, you must install it in I/O module bay 3.

v One Battery Backup Unit for each IBM BladeCenter S SAS RAID Controller

Module

v At least two hard disk drives for RAID configurations 0 and 1 or three hard disk

drives for RAID 5

v An Advanced Management Module v 2 power supplies per Disk Storage Module (DSM) v A supported Ethernet switch

– Nortel 1/10Gb Uplink Ethernet Switch Module (GbESM-1-10U) firmware

(1.0.1.0)

Interface choices and functions

After you install the IBM BladeCenter S SAS RAID Controller Module, you can manage and configure it using the following interfaces:

Table 1. Interfaces and functions

Interface Manage and configure

Use the Advanced Management Module Web interface to manage and configure:

v IBM BladeCenter S SAS RAID Controller

Module IP addresses

v SAS Switch IP addresses

Use the IBM Storage Configuration Manager to:

Use the RAID Controller command line interface to:

Use the SAS Switch command line interface to :

Use the SAS Switch Web interface to:

You can also use the Advanced Management Module to monitor the status of your IBM BladeCenter S chassis and related components

v Create storage configuration v Grant host access to storage v Assign storage to hosts v Monitor controller status v Update controller code v Update SAS Switch firmware

v Create storage configuration v Grant host access to storage v Assign storage to hosts v Monitor controller status v Update controller code using SAS RAID

Controller Firmware Update Package

v Monitor SAS Switch status v Update SAS Switch firmware

v Monitor SAS Switch components

Chapter 1. Introduction 3

Workflow notes

There are several different tools and utilities that impact the way you begin using your IBM BladeCenter S SAS RAID Controller Module.

For example, if you are using the IBM Storage Configuration Manager application to configure your storage and data redundancies and maintain your firmware, the steps you take to accomplish this are more automated than if you are using the RAID Controller command line interface and, or the SAS RAID Controller Firmware Update Package to do these things. However, despite the manner in which you choose to accomplish your system storage configurations and maintenance, the IBM BladeCenter S SAS RAID Controller Module enables you configure your integrated storage solutions by performing the following:

v Create storage pools v Define volumes for those pools v Receive Logical Unit Numbers (LUNs) for those volumes v Map those LUNs to hosts (servers) contained in the IBM BladeCenter S chassis.

Important: Before you begin the process of storage configuration, use the RAID Controller command line interface to set up your email to receive system alerts and log output.

Documentation notes

Table 2. Important notes

Summary

Throughout this document, the user name is also known as the login name, user identifier, or user ID for logging into one or more of the following interfaces or programs:

v Telnet interface v Web browser interface v Advanced management module Web interface v IBM Storage Configuration Manager Web interface

Note: The IBM Storage Configuration Manager has two login screens: One to the server and the other to the RAID Controller.

v RAID Controller command line interface v SAS Switch command line interface v SAS Switch Web interface

Requirement: Install two SAS RAID Modules in an IBM BladeCenter S chassis. Requirement: To use the SAS RAID Modules, Battery Backup Units must be installed in

bay 1 and bay 2 of the media tray. You can obtain up-to-date information about the SAS RAID Modules and other IBM

products at http://www.ibm.com/systems/support/

4 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

Table 2. Important notes (continued)

Summary

The controller module has the following labels:

1. Safety certification label

2. Product name label

3. Serial number label

4. Media access control (MAC) address label

5. SAS ID

The major components topic contains an illustration that shows the location of the SAS RAID Modules labels.

Note: This information is required when you register the SAS RAID Modules with IBM.

Preinstallation safety information

This topic contains important safety information. Read before installing this product.

Before installing this product, read the safety information (statements)

Antes de instalar este produto, leia as Informações de Segurança.

Læs sikkerhedsforskrifterne, før du installerer dette produkt.

Lees voordat u dit product installeert eerst de veiligheidsvoorschriften.

Ennen kuin asennat tämän tuotteen, lue turvaohjeet kohdasta Safety Information.

Avant d'installer ce produit, lisez les consignes de sécurité.

Vor der Installation dieses Produkts die Sicherheitshinweise lesen.

Chapter 1. Introduction 5

Prima di installare questo prodotto, leggere le Informazioni sulla Sicurezza.

Les sikkerhetsinformasjonen (Safety Information) før du installerer dette produktet.

Antes de instalar este produto, leia as Informações sobre Segurança.

Antes de instalar este producto, lea la información de seguridad.

Läs säkerhetsinformationen innan du installerar den här produkten.

Statement 1

6 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

DANGER

Electrical current from power, telephone, and communication cables is hazardous.

To avoid a shock hazard:

v Do not connect or disconnect any cables or perform installation,

maintenance, or reconfiguration of this product during an electrical storm.

v Connect all power cords to a properly wired and grounded electrical outlet.

v Connect to properly wired outlets any equipment that will be attached to

this product.

v When possible, use one hand only to connect or disconnect signal cables.

v Never turn on any equipment when there is evidence of fire, water, or

structural damage.

v Disconnect the attached power cords, telecommunications systems,

networks, and modems before you open the device covers, unless instructed otherwise in the installation and configuration procedures.

v Connect and disconnect cables as described in the following table when

installing, moving, or opening covers on this product or attached devices.

To Connect: To Disconnect:

1. Turn everything OFF.

2. First, attach all cables to devices.

3. Attach signal cables to connectors.

4. Attach power cords to outlet.

5. Turn device ON.

1. Turn everything OFF.

2. First, remove power cords from outlet.

3. Remove signal cables from connectors.

4. Remove all cables from devices.

Statement 2

CAUTION: When replacing the lithium battery, use only IBM Part Number 33F8354 or an equivalent type battery recommended by the manufacturer. If your system has a module containing a lithium battery, replace it only with the same module type made by the same manufacturer. The battery contains lithium and can explode if not properly used, handled, or disposed of.

Do not:

v Throw or immerse into water

v Heat to more than 100°C (212°F)

v Repair or disassemble

Dispose of the battery as required by local ordinances or regulations.

Chapter 1. Introduction 7

Statement 21

CAUTION: Hazardous energy is present when the blade is connected to the power source. Always replace the blade cover before installing the blade.

Handling static-sensitive devices

Static electricity can damage electronic devices, including your blade server. To avoid damage, keep static-sensitive devices in their static-protective packages until you are ready to install them.

To reduce the possibility of damage from electrostatic discharge, observe the following precautions:

v When you work on a IBM BladeCenter S chassis that has an electrostatic

discharge (ESD) connector, use a wrist strap when you handle modules, optional devices, or blade servers. To work correctly, the wrist strap must have a good contact on both ends. It should touch your skin at one end and firmly connected to the ESD connector on the front or back of the IBM BladeCenter S chassis.

v Limit your movement. Movement can cause static electricity to build up around

you.

v Handle the device carefully: holding it by its edges or its frame. v Do not touch solder joints, pins, or exposed circuitry. v Do not leave the device where others can handle and damage it. v While the device is still in its static-protective package, touch it to any

unpainted metal surface of the IBM BladeCenter S chassis or any unpainted metal surface on any other grounded component in the rack you are installing the device in for at least 2 seconds. (This drains static electricity from the package and from your body.)

v Remove the device from its package and install it directly into the blade server

without setting down the device. If it is necessary to set down the device, place it back into its static-protective package. Do not place the device on your blade server cover or on a metal surface.

v Take additional care when handling devices during cold weather. Heating

reduces indoor humidity and increases static electricity.

8 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

Hardware features and specifications

This section provides a summary of the features and specifications for the IBM BladeCenter S SAS RAID Controller Module.

The SAS RAID Modules support the following features:

v 6 internal 1X SAS 3.0 Gb host connectivity to 6 blade slots v 2 internal 4X SAS 3.0Gb to 2 disk storage module (DSM) systems v 1.0 Gb Ethernet for RAID management v 10/100 Ethernet for Switch management v Serial SAS Protocol v Serial Management Protocol (SMP) as defined in the SAS specification v Fourteen internal x1 links to Blade servers

The IBM BladeCenter S chassis takes advantage of the features of the IBM BladeCenter S SAS RAID Controller Module.

The following are standard features of the IBM BladeCenter S chassis:

v An Advanced Management Module v Two or more power modules v Four fan modules v A media tray

You might receive additional features depending on what you ordered.

Table 3. Features

SAS RAID Module

SAS RAID Module features

v SAS RAID Module and

SAS expander

v Vitesse 7157

Environmental: Fabric management –

maintainability

v Diagnostics: Power-on

self-test (POST) is performed on all functional components. Port operational tests include internal, external, and online tests.

v User interface:

Light-emitting diode (LED) indicators

methods:

SAS RAID Module electrical specifications:

v Power source loading: 2

amps maximum at 12 V dc

v Heat output: 24 watts

maximum

v Operating voltage: 12 V dc v Circuit protection:

Internally fused

Dimensions

Chapter 1. Introduction 9

Table 3. Features (continued)

SAS RAID Module features

SAS RAID Module maintainability

SAS RAID Module electrical specifications:

v Temperature and altitude:

– Operating:

- 10°C to 52°C (50°F to

126°F) at an altitude of0to914m(0to2 998 ft)

- 10°C to 49°C (50°F to

120°F) at an altitude of0to3000m(0to

9 843 ft) – Non-operating: – -40°C to 65°C (-40°F to

149°F) at an altitude of 0to12000m(0to39 370 ft)

v Humidity:

– Operating: 8% to 80%,

noncondensing

– Non-operating: 5% to

80%, noncondensing

Component illustrations

The following illustrations show the front and rear views of an IBM BladeCenter S chassis. Your hardware might have labels not shown in the following illustrations.

v Advanced Management

Module interface

v IBM Storage Configuration

Manager interface

v Telnet and command line

interface (CLI)

v Web-browser interface v SAS connectivity module

simple network management protocol (SNMP) agent

The SNMP agent enables a network management workstation to receive configuration values and SAS link data through SNMP and the Ethernet interface.

SAS RAID Module

v Width: 112 mm (4.41 in.) v Height: 29 mm (1.14 in.) v Depth: 260 mm (10.25 in.) v Weight: 2 lb (.91 kg)

Battery Backup Unit dimensions

v Depth: 16.3 in [414.08 mm] v Width: 3.10 in [78.65 mm] v Height: 0.88 in [22.4 mm] v Weight: 1.32 Kg (2.91 lbs)

Figure 1. Front view of an IBM BladeCenter S chassis

10 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

Figure 2. Back view of an IBM BladeCenter S chassis

Logical identifiers and physical location codes

You can use logical identifiers and physical location codes to locate resources in your system.

Use logical identifiers to identify a specific resource for commands, status, and messages. Use physical location codes to identify a specific resource in the physical world; this helps identify the exact location of a resource when you remove or replace them.

You can see logical identifiers and physical location codes in IBM Storage Configuration Manager by performing the following steps:

1. From the IBM Storage Configuration Manager navigation panel, select Health >

Physical View. The Physical View page displays a graphical representation of

the devices on your server.

2. Hover the mouse cursor over the resources that appear in the Physical View

page to display the logical identifiers and physical location codes.

Option package contents

This topic describes the contents of the option package.

The connectivity module option package contains the following items:

v One IBM BladeCenter S SAS RAID Controller Module v One Battery Backup Unit (45W5002) is bundled with each IBM BladeCenter S

SAS RAID Controller Module.

v The RAID Controller Getting Started Guide v The Support CD, which includes:

– The RAID Controller and SAS Expansion Card Installation and User’s Guide – The RAID Controller and SAS Expansion Card Getting Started Guide – IBM BladeCenter Storage Configuration Manager Planning, Installation, and

Configuration Guide

– SAS Expansion Card applications – MIB files

Chapter 1. Introduction 11

– Readme file – Multilingual Safety Information

Chapter 2. Prerequisite hardware

The section highlights the prerequisite hardware required to operate the IBM BladeCenter S SAS RAID Controller Module.

The IBM BladeCenter S chassis requires one Battery Backup Unit, FRU part number 45W5002, for each SAS RAID Module to function.

Understanding Battery Backup Units

Battery Backup Units (BBUs) can provide enough reserve power to store data in your IBM BladeCenter S SAS RAID Controller Module memory cache for 72 hours in the event of an interruption of power.

Battery Backup Units automatically recharge once they are inserted into the IBM BladeCenter S chassis.

Note: Like all batteries, Battery Backup Units degrade over time. You should install Battery Backup Units within 90 days of the date of purchase so that they can begin recharging, and do not take them out of the IBM BladeCenter S chassis for extended periods of time.

The first battery expiration notification is made 90 days before the expiration date listed. Subsequent notifications are made at 30 and 15 days. You must replace the Battery Backup Units before the final expiration date occurs. If the Battery Backup Units expire, the RAID Controller enters into a cache write-through mode until you install new Battery Backup Units. This causes a significant delay in processing speed.

IBM consumable parts

Consumable parts (parts that are purchased separately) are not covered by the IBM Statement of Limited Warranty. The following consumable parts are available for purchase from the retail store.

Table 4. Battery Backup Unit part number

Description FRU Part number

Battery Backup Unit 45W5002

To order a consumable part, complete the following steps:

1. Go to http://www.ibm.com.

2. From the Products menu, click Upgrades, accessories & parts

3. Click Obtain maintenance parts

4. Follow the instructions to order the component from the retail store

If you need help with your order, call the toll-free number that is listed on the retail parts page, or contact your local IBM representative for assistance.

Environmental considerations

Follow the laws and guidelines for battery and other hazardous waste disposal in your area.

Quick facts about Battery Backup Units

Battery backup units provide backup for SAS RAID controller modules cache.

Battery Backup Units are installed in the battery backup unit bays located in the media tray when you install SAS RAID controller modules. The Battery Backup Unit in battery backup bay 1 provides backup support for the SAS RAID controller module in I/O module bay 3; the Battery Backup Unit in battery backup bay 2 provides backup support for the SAS RAID controller module in I/O module bay

Note: Both Battery Backup Units are required when you install two SAS RAID controller modules.

Controls and indicators

The Battery Backup Units provides the following indicators:

Power Lit (green). Power is being supplied to the Battery Backup Units.

Charging

Lit (green). The Battery Backup Units is being charged. Off.

Fault Lit (amber). The Battery Backup Units has a failure. If the Fault LED is lit,

replace the Battery Backup Units.

14 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

Installing the Battery Backup Unit

To install the Battery Backup Unit, slide the unit into the media tray and close the release handle.

About this task

This topic shows the mechanics of performing a physical installation of the Battery Backup Units. The Replacing a battery section of this document details the steps to take to prepare the IBM BladeCenter S SAS RAID Controller Module for a battery replacement.

Battery Backup Unit installation into the front of the BladeCenter S chassis

Procedure

1. Open the release handle (rotate the handle down).

2. Slide the battery backup unit into the media tray.

3. Close the release handle (rotate the handle up)

Removing the Battery Backup Unit hardware

To remove the Battery Backup Unit, open the release handle on the Battery Backup Unit and slide the bBattery Backup Unit out of the media tray.

About this task

Important: If you are removing one or both Battery backup units from a BladeCenter S chassis that contains SAS RAID controller modules, refer to the IBM BladeCenter SAS RAID Controller Installation and User's Guide for additional steps that might need to be performed.

Chapter 2. Prerequisite hardware 15

Procedure

1. Open the release handle (rotate the handle down)

2. Slide the battery backup unit out of the media tray.

16 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

Chapter 3. Understanding the Telnet interface

You can establish a Telnet session to retrieve information or to configure settings using the command line interface.

You can perform a variety of installation and connectivity management tasks through an Ethernet connection using this interface.

You can access the Telnet interface in one of two ways:

v Advanced Management Module v Use the Command Line Interface on a network management workstation

Establishing a Telnet session to RAID Controller

You can establish a Telnet session using various methods. This topic describes how to establish a Telnet session to the RAID Controller using the Advanced Management Module.

Before you begin

About this task

To establish a Telnet session to the RAID Controller using the Advanced Management Module complete the following steps:

Procedure

1. Point your browser to http://xxx.xxx.xxx.xxx, where xxx.xxx.xxx.xxx is the IP address of the Advanced Management Module interface. The Enter Network Password window opens.

If you have the Advanced Management Module connected to your network, log in using the network IP assigned to it. If you are using the default IP address your management system (the computer you are using to manage your IBM BladeCenter S components) must be physically connected through an Ethernet cable to the Advanced Management Module .

Note: The default IP address for the Advanced Management Module is

192.168.70.125.

2. Enter the initial default user ID, USERID for the User Name. The user ID and password are case sensitive.

3. Enter the initial default password, PASSW0RD (the sixth character is a zero) for the Password and click OK. The Welcome window opens.

4. Select the timeout value of this Web session for the Inactive session timeout value and click Continue. The Advanced Management Module window

opens.

5. Select I/O Module Tasks > Configuration. The I/O Module Configuration window opens.

6. Click the link for either the connectivity module in I/O module bay 3 or in I/O module bay 4.

7. From the Current IP Configuration for RAID Controller Subsystem section, click Advanced Configuration. he Advanced Configuration window opens.

8. To start a Telnet session, click Start Telnet Session. The Login screen opens.

9. At the Login prompt, type the initial default user ID, USERID and press Enter.

The user ID and password are case sensitive. The Password prompt displays.

10. At the Password prompt, type the initial default password, PASSW0RD (the sixth character is a zero).

11. Click OK. The Command Line Interface Shell screen opens.

18 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

Chapter 4. Installing the IBM BladeCenter S SAS RAID Controller Module

This topic details the IBM BladeCenter S SAS RAID Controller Module installation and setup procedures.

Before you begin

Before you begin, do the following:

1. Install a SAS Expansion Card (CFFv) for IBM BladeCenter (Part Number 39Y9190) into each Blade server that you want to communicate with the RAID Controller. For detailed installation instructions, see The SAS Expansion Card (CFFv) for IBM BladeCenter Installation and Users Guide located in the Support directory on the support CD.

2. If you are upgrading ensure that your previously installed Advanced Management Module has the level of firmware that supports the RAID Controller. You can check your firmware level at: www.ibm.com/systems/ support/documentation/.

Note: If you log into the Advanced Management Module using the default IP (192.168.70.125), your management system (the computer you are using to manage your IBM BladeCenter S components) must be physically connected through an Ethernet cable to the Advanced Management Module.

3. As part of the setup procedure, obtain four unused IP Addresses on the same subnet from your network administrator.

v 2 IP Address for the RAID Subsystem v 2 IP Address for the SAS Switches

4. Remove the SAS RAID Modules from their shipping packages.

Remember: Follow the guidelines for handling static sensitive devices.

About this task

Once you have finished the prerequisite steps perform the following tasks:

Installation and setup

Procedure

1. Install one Battery Backup Unit in bay 1 of the media tray, and the second Battery Backup Unit in bay 2 of the media tray.

2. Install the first SAS RAID Module in I/O module bay 3, and the second SAS RAID Module in I/O module bay 4.

After you have physically installed the modules, you can configure them in the following ways:

IBM BladeCenter Start Now Advisor

A guided configuration using the IBM BladeCenter Start Now Advisor CD included with your IBM BladeCenter S chassis.

Insert the CD into the laptop or PC you are using for your installation and follow the prompts given.

Advanced Management Module

A non-guided manual configuration using a direct connection to the Advanced Management Module.

Log into the Advanced Management Module and perform the rest of the setup tasks.

20 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

Note: You will still need to configure integrated storage using the IBM

BladeCenter Start Now Advisor, IBM Storage Configuration Manager, or RAID Controller command line interface.

The IBM BladeCenter Start Now Advisor method

About this task

After installation, you can configure the SAS RAID Modules using the IBM BladeCenter Start Now Advisor shipped with IBM BladeCenter S chassis. The Start Now Advisor is a configuration tool that helps you quickly connect to and configure components of the IBM BladeCenter S chassis. It provides step-by-step instructions and enables you to quickly and easily configure the Advanced Management Module and SAS RAID Modules, including setting storage options. To use the IBM BladeCenter Start Now Advisor:

Procedure

1. Insert the IBM BladeCenter Start Now Advisor CD on a workstation that can communicate with the Advanced Management Module, and follow the instructions in the wizard. You must have the Advanced Management Module IP address and IP addresses for the RAID Controller and SAS Switch components of each IBM BladeCenter S SAS RAID Controller Module to complete IBM BladeCenter Start Now Advisor installation.

Note: You must have the Advanced Management Module IP address and IP addresses for the RAID Controller and SAS Switch components of eachIBM BladeCenter S SAS RAID Controller Module to complete the IBM BladeCenter Start Now Advisor installation.

2. After connecting to and doing initial inventory of the IBM BladeCenter S chassis, choose a configuration method to complete the setup. It is recommended that you use the Express configuration method. This gets you up and running quickest using intelligent defaults for many settings. You can optionally choose the Launch method which prompts you to launch additional consoles to complete the configuration process or the Import method, which allows you to import a configuration saved in another IBM BladeCenter Start Now Advisor session.

The Advanced Management Module method

About this task

After you install the IBM BladeCenter S SAS RAID Controller Module, you can log into the Advanced Management Module and set the parameters of the modules so that you can begin configuring your integrated storage.

Note: Before you enter the POST and Ethernet switch parameters for your IBM BladeCenter S SAS RAID Controller Module, ensure that if you are running a storage configuration using spares, that spare matches the capacity, speed and type of the drives in the array for which it is used.

Procedure

1. To log into the Advanced Management Module perform the following: a. Enter the IP address of the Advanced Management Module into the Web

browser URL field.

Chapter 4. Installing the IBM BladeCenter S SAS RAID Controller Module 21

Note: The default IP address for the Advanced Management Module is

192.168.70.125.

b. Enter the username and password.

v The default username is: USERID v The default password is: PASSW0RD (the sixth position is the numeral

zero)

c. When prompted for the Inactive session timeout value, select no timeout.

Note: Remember to log out when you have completed your session. If you

do not log out, the system shows an error the next time you try to log in.

2. Click Continue.

3. From the I/O Module Tasks menu, click Configuration.

4. From the I/O Module Configuration section, click Bay 3

5. Enter the IP settings for the SAS Switch, and RAID Controller.

6. Save the settings.

7. If you have two SAS RAID Modules, repeat these steps to configure the IP

settings for the SAS Switch, and RAID Controller in Bay 4 as well.

8. Verify the IP settings are listed before proceeding to the next step.

9. Enable Fast POST and ensure that External ports are disabled for each RAID

Controller.

Note: The disabled ports are SAS ports, not Ethernet ports.

a. From the I/O Module Tasks menu, click Admin/Power/Restart. b. Scroll down to the I/O Module Advanced Setup section and from the

Select a module menu, select I/O module 3.

c. Select Enabled from the menu for Fast POST and Disabled for External

ports.

d. Click Save.

10. If you have two SAS RAID Modules, repeat these steps to enable Fast POST

and ensure that the External ports are disabled for the RAID Controller installed in I/O module 4 as well.

What to do next

If you experience any problems with setting these parameters, review the advanced verification procedures in the Troubleshooting section of this document.

22 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

Installing IBM Storage Configuration Manager

After completing initial configuration of your IBM BladeCenter S SAS RAID Controller Modules, you should install the IBM Storage Configuration Manager. IBM Storage Configuration Manager provides advanced support for management and monitoring of IBM BladeCenter storage. It also provides system health monitoring, device user management, and troubleshooting functions.

About this task

The following is a summary and not meant to be used as primary installation instructions. For complete instructions and important compatibility notices, refer to the IBM Storage Configuration Manager Planning, Installation and Configuration Guide.

Procedure

1. Navigate to http://www.ibm.com/systems/management/director/ downloads.html.

2. From the Choose Software list, select IBM Storage Configuration Manager and download the installer file.

3. Unpack the .ZIP or .TAR installation file to a temporary directory or burn the ISO image to a CD.

4. Launch the installer and follow the on screen prompts.

5. When prompted to choose an install type, select SCM Full Install for all

devices.

6. After you install the IBM Storage Configuration Manager, you are prompted to restart your workstation. TheIBM Storage Configuration Manager service starts automatically upon restart.

7. From the Start menu, launch the IBM Storage Configuration Manager.

8. Log in and select Initial Configuration Wizard and follow the on screen

prompts.

Important: If you apply a new storage configuration using the IBM Storage Configuration Manager, existing configuration and all data stored on the disks is deleted before new configuration is applied.

User ID and password requirements

The SAS RAID Module has two separate default user IDs and passwords. The first default user, USERID, and default password, PASSW0RD (the sixth character is a zero), is used to access the RAID Controller command line interface. The second default user, USERID1, and default password, PASSW0RD (the sixth character is a zero), is used by the IBM Storage Configuration Manager.

The default user IDs cannot be changed. However, you can change the password for either USERID or USERID1 using the chpassword command in the RAID Controller command line interface (see “chpasswd” on page 61). The following rules apply to new passwords:

v Password must contain at least 8 characters v Password must not exceed 16 characters. v Password must contain at least one digit (0–9) v Password must contain at least one alpha character (a-z,A-Z).

Chapter 4. Installing the IBM BladeCenter S SAS RAID Controller Module 23

If the firmware level of your RAID controllers is older than 1.2.x.xxx, you need to change the password on both SAS RAID Modules at the same time. If the firmware level of your RAID controllers is 1.2.x.xxx or newer, then changing the password on one SAS RAID Module automatically changes the password on the other SAS RAID Module.

Resetting the passwords on an SAS RAID Module

Before you begin

Before resetting the SAS RAID Module passwords, you must end all application I/O processes and shut down any active Blade servers in accordance with the recommended non-concurrent practices. Then, use the reset to factory defaults function within Advanced Management Module to reset the passwords.

To reset the passwords on one SAS RAID Module, you must power off both SAS RAID Modules. Perform the following steps to reset the passwords on the SAS RAID Module in bay 3.

Procedure

1. Stop all host I/O applications and power off the Blade servers.

2. Use the Advanced Management Module to reset the passwords. a. Log into the Advanced Management Module. b. Select I/O Module Tasks > Admin/Power/Restart. c. Select the checkboxes next to bay 3 and bay 4. d. From the Available actions menu, select Power Off Module(s). e. Click Perform action. f. Wait until both SAS RAID Modules are powered off. The Off message will

be displayed in the Pwr column.

g. Select I/O Module Tasks > Configuration. h. In the I/O Module Configuration section, select Bay 3. i. In the Bay 3 section that displays, select Advanced Configuration. j. In the Advanced Configuration for I/O Module 3 section, select Restore

Factory Defaults.

k. Select Restore Defaults. l. Select OK. m. The SAS RAID Module in bay 3 will power on. Wait until the SAS RAID

Module in bay 3 successfully powers on. The On message will display in the Pwr column, and the message POST results available: Module completed POST successfully will display in POST Status column.

3. Power on the SAS RAID Module in bay 4. a. Select I/O Module Tasks > Admin/Power/Restart. b. Select the checkbox next to bay 4. c. From the Available actions menu, select Power On Module(s). d. Click Perform action. e. The SAS RAID Module in bay 4 will power on. Wait until the SAS RAID

Module in bay 4 successfully powers on. The On message will be displayed in the Pwr column, and the message POST results available: Module

completed POST successfully will display in POST Status column.

24 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

What to do next

To reset the passwords for the SAS RAID Module in bay 4, repeat these steps, substituting the opposite bay numbers where appropriate.

Note: Performing the steps to reset the factory defaults does not affect any logical configuration data on the SAS RAID Modules.

Configuring storage through the CLI

Advanced users can also configure their storage through the RAID Controller command line interface – “Using the command line to configure storage” on page

90.

Upgrading from a single to a dual controller configuration

Upgrading from a single RAID Controller configuration to a dual RAID Controller configuration is supported using the RAID Controller command line interface. Perform the following steps to concurrently upgrade from a single to dual controller configuration.

1. Log into the CLI of the RAID Controller.

2. At the <CLI> prompt, enter list controller and press Enter to verify the

controller is operating in a single controller configuration.

<CLI> list controller _______________________________________________________________________ | Ctlr# | Controller | Status | Ports | LUNs | |_____________|________________|____________________|_________|_________| | 0 | Ctlr0| STANDALONE| 1| 10| | 1 | Ctlr1| NOT_PRESENT| -| --| |_____________|________________|____________________|_________|_________|

3. At the <CLI> prompt, enter host –get and press Enter to query the list of host servers.

<CLI> host -get

HostWWN 500062b00007e568, HostName Blade_Bay_1 :

LUNs Mapped :

___________________________________________________________ | LUN | Permission | Volume | |_________|_____________________|___________________________| | 0| ACCESS_READWRITE| Raid10_Pool:r10_vol_1| | 4| ACCESS_READWRITE| Raid10_Pool:r10_vol_10| | 3| ACCESS_READWRITE| Raid10_Pool:r10_vol_4| | 2| ACCESS_READWRITE| Raid10_Pool:r10_vol_3| | 1| ACCESS_READWRITE| Raid10_Pool:r10_vol_2| | 5| ACCESS_READWRITE| Raid10_Pool:r10_vol_9| | 6| ACCESS_READWRITE| Raid10_Pool:r10_vol_8| | 7| ACCESS_READWRITE| Raid10_Pool:r10_vol_7| | 8| ACCESS_READWRITE| Raid10_Pool:r10_vol_6| | 9| ACCESS_READWRITE| Raid10_Pool:r10_vol_5| |_________|_____________________|___________________________|

4. Insert the new RAID Controller into I/O bay 4. a. Open the release handle by rotating the handle down. b. Slide the RAID Controller into the module bay until it stops. c. Close the release handle by rotating the handle up. d. Connect all cables to the module.

Chapter 4. Installing the IBM BladeCenter S SAS RAID Controller Module 25

5. At the <CLI> prompt, enter alert –get and press Enter. Verify the configuration changed from a single to dual controller by querying the active alert list for alert 706. Alert 706 is automatically cleared from the active alert list after two minutes.

<CLI> alert -get

Existing Alerts :

__________________________________________________________________________________________ |AlertCode| Id | Time | SlotID | Severity | WWN | Ackable |MaskState| |==========================================================================================| | 706 | 61| 20100219232029 | 0 | Info | 5005076b07441aff | 1 | Masked| |------------------------------------------------------------------------------------------| | Msg: Controller changed from Single to Dual Controller Mode (SCFG set to 2) | |==========================================================================================|

6. At the <CLI> prompt, enter list controller and press Enter. Verify the controllers are operating in a dual primary-secondary configuration .

<CLI> list controller _______________________________________________________________________ | Ctlr# | Controller | Status | Ports | LUNs | |_____________|________________|____________________|_________|_________| | 0 | Ctlr0| PRIMARY| 1| 10| | 1 | Ctlr1| SECONDARY| 1| 10| |_____________|________________|____________________|_________|_________|

7. At the <CLI> prompt, enter alert -get and press Enter to query the active alert list for alert 5600. Record the host port WWN to create host-LUN mappings.

<CLI> alert -get Current Machine Local Time: 02/19/2010 11:20:36 PM

Existing Alerts :

__________________________________________________________________________________________ |AlertCode| Id | Time | SlotID | Severity | WWN | Ackable |MaskState| |==========================================================================================| | 5600 | 9 | 20100219162030 | 1 | Info | 5005076b07441aff | 1 | Masked | |------------------------------------------------------------------------------------------| | Msg: Illegal host 0x500062b00007e569 access attempted | |==========================================================================================|

8. At the <CLI> prompt, enter host –add <WWN> and press Enter to add the host WWN to the list of host.

<CLI> host -add 500062b00007e569 Host added with WWN 500062b00007e569 and Name CliHost1

9. At the <CLI> prompt, enter host –get and press Enter to verify the new host was added to the list of host servers.

<CLI> host -get

HostWWN 500062b00007e568, HostName Blade_Bay_1 :

LUNs Mapped :

26 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

| 9| ACCESS_READWRITE| Raid10_Pool:r10_vol_5| |_________|_____________________|___________________________|

HostWWN 500062b00007e569, HostName CliHost1 :

No LUNs Mapped

10. At the <CLI> prompt, enter hostlun –map –volume <POOLNAME:VOLNAME>

-PERMISSION <RW> -wwn <WWN> -name <HOSTNAME> -lun <LUNNUMBER> and press

Enter to map the host to the LUNs using the WWN of the host port . The LUN, volume number, and permissions must be the same.

<CLI> hostlun -map -volume Raid10_Pool:r10_vol_1 -permission rw -wwn 500062b00007e569

-name CliHost1 -lun 0

Working ...

Host LUN 0 for host 500062b00007e569 and host name CliHost1 mapped to volume ’r10_vol_1’ in ’Raid10_Pool’

<CLI> hostlun -map -volume Raid10_Pool:r10_vol_2 -permission rw -wwn 500062b00007e569

-name CliHost1 -lun 1

Working ...

Host LUN 1 for host 500062b00007e569 and host name CliHost1 mapped to volume ’r10_vol_2’ in ’Raid10_Pool’

<CLI> hostlun -map -volume Raid10_Pool:r10_vol_3 -permission rw -wwn 500062b00007e569

-name CliHost1 -lun 2

Working ...

Host LUN 2 for host 500062b00007e569 and host name CliHost1 mapped to volume ’r10_vol_3’ in ’Raid10_Pool’

<CLI> hostlun -map -volume Raid10_Pool:r10_vol_4 -permission rw -wwn 500062b00007e569

-name CliHost1 -lun 3

Working ...

Host LUN 3 for host 500062b00007e569 and host name CliHost1 mapped to volume ’r10_vol_4’ in ’Raid10_Pool’

<CLI> hostlun -map -volume Raid10_Pool:r10_vol_10 -permission rw -wwn 500062b00007e569

-name CliHost1 -lun 4

Working ...

Host LUN 4 for host 500062b00007e569 and host name CliHost1 mapped to volume ’r10_vol_10’ in ’Raid10_Pool’

<CLI> hostlun -map -volume Raid10_Pool:r10_vol_9 -permission rw -wwn 500062b00007e569

-name CliHost1 -lun 5

Working ...

Host LUN 5 for host 500062b00007e569 and host name CliHost1 mapped to volume ’r10_vol_9’ in ’Raid10_Pool’

<CLI> hostlun -map -volume Raid10_Pool:r10_vol_8 -permission rw -wwn 500062b00007e569

-name CliHost1 -lun 6

Working ...

Host LUN 6 for host 500062b00007e569 and host name CliHost1 mapped to volume ’r10_vol_8’ in ’Raid10_Pool’

Chapter 4. Installing the IBM BladeCenter S SAS RAID Controller Module 27

<CLI> hostlun -map -volume Raid10_Pool:r10_vol_7 -permission rw -wwn 500062b00007e569

-name CliHost1 -lun 7

Working ...

Host LUN 7 for host 500062b00007e569 and host name CliHost1 mapped to volume ’r10_vol_7’ in ’Raid10_Pool’

<CLI> hostlun -map -volume Raid10_Pool:r10_vol_6 -permission rw -wwn 500062b00007e569

-name CliHost1 -lun 8

Working ...

Host LUN 8 for host 500062b00007e569 and host name CliHost1 mapped to volume ’r10_vol_6’ in ’Raid10_Pool’

<CLI> hostlun -map -volume Raid10_Pool:r10_vol_5 -permission rw -wwn 500062b00007e569

-name CliHost1 -lun 9

Working ...

Host LUN 9 for host 500062b00007e569 and host name CliHost1 mapped to volume ’r10_vol_5’ in ’Raid10_Pool’

11. Log into the host server and scan for hardware changes to allow for the host to recognized the second path.

12. Log into the host server and verify the second path is operational.

13. At the <CLI> prompt, enter host –get and press Enter to verify the host

mappings of the second WWN.

<CLI> host -get

HostWWN 500062b00007e568, HostName Blade_Bay_1 :

LUNs Mapped :

HostWWN 500062b00007e569, HostName CliHost1 :

LUNs Mapped :

___________________________________________________________ | LUN | Permission | Volume | |_________|_____________________|___________________________| | 0| ACCESS_READWRITE| Raid10_Pool:r10_vol_1| | 1| ACCESS_READWRITE| Raid10_Pool:r10_vol_2| | 2| ACCESS_READWRITE| Raid10_Pool:r10_vol_3| | 3| ACCESS_READWRITE| Raid10_Pool:r10_vol_4| | 4| ACCESS_READWRITE| Raid10_Pool:r10_vol_10| | 5| ACCESS_READWRITE| Raid10_Pool:r10_vol_9| | 6| ACCESS_READWRITE| Raid10_Pool:r10_vol_8|

28 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

| 7| ACCESS_READWRITE| Raid10_Pool:r10_vol_7| | 8| ACCESS_READWRITE| Raid10_Pool:r10_vol_6| | 9| ACCESS_READWRITE| Raid10_Pool:r10_vol_5| |_________|_____________________|___________________________|

If the upgrade did not complete successfully, collect the logs and contact IBM.

Chapter 4. Installing the IBM BladeCenter S SAS RAID Controller Module 29

30 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

Chapter 5. Disconnecting power to the BladeCenter unit

This section describes the power-off sequence for the BladeCenter S chassis with IBM BladeCenter S SAS RAID Controller Module installed.

About this task

If you are disconnecting power from the BladeCenter chassis for more than 72 hours, you must turn off IBM BladeCenter S SAS RAID Controller Module as part of the chassis power-off procedure. This allows the RAID Controller to save the cached data on the disk drives.

Disconnect power from the BladeCenter S chassis by shutting down all blade servers and components and disconnecting the BladeCenter S chassis from all power sources.

Note: A 9401 alert event is logged in the system if one of the following occurs: v The IBM BladeCenter S SAS RAID Controller Module is not turned off and the

chassis is disconnected from the power source for more than 72 hours

v You remove both SAS RAID Controller Modules, both backup battery modules,

or the media tray without performing a proper power-off procedure

If the IBM BladeCenter S SAS RAID Controller Module is not turned off and the BladeCenter chassis is disconnected from the power source for more than 72 hours, the backup battery units require a period of charging time before they can provide power for the RAID Controller memory cache. During this charging period, the RAID Controller enters into a cache write-through mode. This causes a significant delay in processing speed.

Before you install or remove any components in the chassis, review and resolve any active alerts for the components. Refer to the related sections in “Non-concurrent repair procedures” on page 154 and “Concurrent repair procedures” on page 164 for more information on repair procedures.

To turn off the BladeCenter S chassis, complete the following steps:

Procedure

1. Turn off the blade servers: a. Stop all blade server I/O applications and shut down the operating

systems. See the documentation that comes with your blade server for information about shutting down the operating system on the blade server.

b. Log on the Advanced Management Module (AMM). c. Select Blade Tasks > Power/Restart. d. Select all blade servers. e. From the Available actions list, select Power Off Blade and click Perform

action.

f. Make sure that all blade servers are Off.

2. Turn off the SAS RAID Controller Modules: a. In the AMM, select I/O Module Tasks > Admin/Power/Restart. b. Select the bays in which the SAS RAID Controller Modules are installed.

c. From the Available actions list, select Power Off Module(s) and click

Perform action.

d. Make sure that both SAS RAID Controller Modules are Off.

Note: It may take up to 8 minutes to fully turn off the SAS RAID Controller

Modules. If power to the chassis is disconnected before the I/O modules are in the Off state and you turn on the chassis after 72 hours, a 9401 alert event will be logged in the system.

3. Disconnect power from the chassis: a. Remove all power cords from the power modules. b. Verify that all LEDs are off.

Note: After you disconnect the BladeCenter S chassis from power, wait at least 30 seconds before you connect the BladeCenter S chassis to power again.

32 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

Chapter 6. Updating firmware

Several components, including the IBM BladeCenter S SAS RAID Controller Module, require regular firmware updates. This section explains how to find and install the most recent updates.

Note: When replacing BladeCenter components, consider updating the firmware for the Advanced Management Module and any other components to the latest version of firmware.

The SAS RAID Controller Firmware Update Package is a Command Line Interface (CLI) based application package that allows you to automatically upgrade the firmware associated with the IBM BladeCenter S SAS RAID Controller Module and its components. The application must be installed on a computer using Windows or Linux with a network connection to the IBM BladeCenter S SAS RAID Controller Module and the Advanced Management Module.

After completing the installation procedures, check the current firmware level shipped on the IBM BladeCenter S SAS RAID Controller Module and visit the IBM BladeCenter support Web site to ensure that it is operating with the latest version of firmware.

To download the latest firmware update package:

1. Point your browser to http://www.ibm.com/systems/support/.

2. From the Product Support section, click the BladeCenter link.

3. From the Popular links section, select Software and device drivers.

4. From the IBM BladeCenter software and device drivers Web site, select

BladeCenter S.

5. From the matrix of downloadable files, select the blade servers and other devices that are installed in your BladeCenter S chassis to download the firmware and device drivers for them.

Product documentation for the BladeCenter S system is available at:

http://www.ibm.com/systems/support/

From the BladeCenter support page, in the Support & downloads section, select Documentation.

Note: For information on updating firmware through IBM Storage Configuration

Manager, see the IBM Storage Configuration Manager online help.

Note: When updating the RAID Controller firmware from 1.0.x.x to 1.2.x.x, pre-verifying the RAID Subsystem is not supported.

Subscribing to notifications

About this task

My Notifications is a service that can automatically email you when new information or code is available for your IBM BladeCenter product. To subscribe, start at the IBM BladeCenter Support web page: http://www.ibm.com/systems/ support/.

Procedure

1. Locate the Stay Informed section of the page and click Subscribe today.

2. Click BladeCenter

3. From the BladeCenter section of the Support Subscriptions page click

BladeCenter notifications.

Note: Log in with your IBM ID and password. If you don't yet have an IBM

ID, you can register using your email address. You are prompted to create a password, a password hint and to provide your country of residence.

4. At the My subscriptions page, select BladeCenter S and click Submit

5. From within the Notify me by area, select the following: email, weekly, html.

6. From within the Type area select the machine type of the BladeCenter S

(typically 8886).

7. From within the Operating System area, select the operating system you use with the BladeCenter SAS RAID Controller Module.

8. From within the Selections area, select Troubleshooting, Download, and Install, or other items of interest to you.

Installing and configuring firmware updates

To obtain the latest IBM BladeCenter S SAS RAID Controller Module firmware update configuration and installation instructions, visit the IBM Support website at http://www.ibm.com/support/. Follow the instructions attached to the code package to install and configure firmware updates.

34 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

Chapter 7. Working with storage pools and volumes

You can divide your available storage into storage pools and volumes to customize your configuration.

Understanding storage pools

A storage pool is a collection of disk drives that become a logical entity. When you create a storage pool, you assign a RAID level to it which will provide a redundancy level.

You can create a storage pool using IBM Storage Configuration Manager or by using the create pool command in the RAID Controller command line interface (see “create pool” on page 80).

Notes

v You should determine the size of your storage pool by the amount of space

v All disk drives in a storage pool must be the same type. v A disk drive can only belong to one storage pool. v If you use global spares to protect storage pools, ensure that any spare matches

required by your application. Once you have determined whatever constraints are put in place by the application, then you can weigh the performance enhancement versus cost to determine the RAID level to use.

the capacity, speed and type of the drives in the storage pool for which it is used.

Understanding volumes

After you create storage pools, you need to break the storage pools into discrete areas of storage, which are called volumes. Volumes are the basic unit of storage that are exposed to the Blade server and are created from the available space in a storage pool. A volume is completely contained within a single storage pool, however a storage pool can contain multiple volumes. After you create volumes, you must map them to each individual Blade server. Each Blade server can access one or more of these volumes.

Volumes are typically defined as either data volumes, which are used to store application date, or boot volumes, which are used to store the operating system image. For each volume, you need to determine the following characteristics:

v The size (in GBs) v The blade server or servers that will have access to the volume v Any applications on the blade servers that need access to the volume

You define volumes using IBM Storage Configuration Manager or by using the create volume command in the RAID Controller command line interface (see “create volume” on page 81).

Notes:

v The minimum size of a volume is 1 MB. The maximum size of a volume is the

maximum size of the storage pool in which the volume resides.

v Defining large volumes may take several minutes to complete. An IBM

BladeCenter S takes approximately 10 minutes to define an 11 TB volume, and may take longer if the system is performing other tasks.

v The maximum number of volumes on a system is 128. The maximum number of

volumes on a host is 16.

v Multiple blade servers can be mapped to a single volume if clustering is

configured. See “Configuring blades for Microsoft Cluster Service” on page 40 for more information.

v Mapping a single volume to multiple blade servers can be done using the

hostlun command through the RAID Controller command line interface. See “hostlun” on page 85 for more information.

Understanding RAID levels

This topic details RAID level characteristics as they relate to the IBM BladeCenter S SAS RAID Controller Module.

A Redundant Arrays of Independent Disks (RAID) is a collection of two or more disk drives that present an image of one or more logical disk drives. In the event of a disk failure, the data can be read or regenerated from the other disk drives in the array due to data redundancy. There are several considerations in deciding which RAID level to choose for your configuration: the amount of storage you have at your disposal, cost, and security requirements.

The IBM BladeCenter S SAS RAID Controller Module supports the following RAID levels:

Table 5. RAID levels and characteristics

RAID levels Characteristics

0 Striping 1 Mirroring 5 Striping with Distributed Parity 10 Striping across mirrors

RAID 0 uses a process called striping, which is the splitting of data across more than one disk. A RAID 0 configuration adds no redundancy and the loss of any one disk in a stripe causes the failure of all the disks in that stripe.

RAID 1 uses a process called mirroring. In a RAID 1 configuration, all of the data on a disk is replicated onto a second peer-level disk. If one of the disks in the pair fails, the other continues running unaffected. RAID 1 requires a two-disk configuration.

RAID 5 uses a process called striped parity. This process writes data and parity information in stripes along three or more drives. If a drive in the array fails, you do have to replace it, but the array is not destroyed by a single drive failure. If a drive failure occurs, subsequent reads are calculated from the distributed parity. The first predefined configuration file (CannedConfig_RSSM.cfg) sets up a RAID 5 array using six available drives. RAID 5 requires a minimum 3 disk configuration.

RAID 10 uses a process called striping across mirrors. This process requires a set of even numbered disks, with four disks being the minimum number required. The

36 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

data is organized as stripes across the disks and the striped disk sets are mirrored. This configuration provides fault tolerance and improved performance.

Drive configurations per RAID level

The following table shows the possible drive configurations for each RAID level.

Table 6. Drive configurations per RAID level

RAID level

RAID 0 Striping 2 12 1 TB ~11 TB RAID 1 Mirroring 2 12 1 TB ~1 TB RAID 5 Striping with

RAID 10 Striping across

RAID characteristics

Distributed Parity

mirrors

Minimum drives

3 12 1 TB ~9.5 TB

4. Drives must be added in pairs. (4,6,8,10,12 drives).

Maximum drives

12 1 TB ~5.5 TB

Understanding the predefined storage configuration

Maximum size of each disk drive

Maximum storage pool capacity

When you install your IBM BladeCenter S SAS RAID Controller Module, a predefined configuration is available to get you started. This topic details the specifics of that predefined configuration.

Canned configuration

The predefined configuration packaged with IBM BladeCenter S SAS RAID Controller Module is referred to as a canned config within the interface itself. The name of the configuration file is CannedConfig_RSSM.cfg, and the names of the configurations created contain the word canned in them. You can use the predefined configuration if you meet the minimum storage requirements for it.

You can load the predefined or canned configuration from the command line interface by running the following command at the RAID Controller command line interface prompt:

controller config -load CannedConfig_RSSM.cfg

The controller config command uses the predefined configuration to create one pool at a RAID 5 level, using port 0, called CannedDG1.

The following example shows a command set that is equivalent to the function of the controller config command. The create pool command uses five drives in the first storage module to create a RAID 5 array, and the global spare command uses another drive to create one global spare. The create volume commands then create six volumes of 20 GB in the pool labeled CannedDG1.

Example: Contents of a pool created using the predefined configuration

<CLI> create pool -drives 1:3 1:5 1:2 1:1 1:4 -raidtype 5 -port 0 -name CannedDG1 create volume -name CannedDG1:vol1 -size 20480MB -seqpostreadcmdsize 0 -seqreadaheadmargin 1 -writecachepolicy on create volume -name CannedDG1:vol2 -size 20480MB -seqpostreadcmdsize 0 -seqreadaheadmargin 1 -writecachepolicy on create volume -name CannedDG1:vol3 -size 20480MB -seqpostreadcmdsize 0 -seqreadaheadmargin 1 -writecachepolicy on

Chapter 7. Working with storage pools and volumes 37

create volume -name CannedDG1:vol4 -size 20480MB -seqpostreadcmdsize 0 -seqreadaheadmargin 1 -writecachepolicy on create volume -name CannedDG1:vol5 -size 20480MB -seqpostreadcmdsize 0 -seqreadaheadmargin 1 -writecachepolicy on create volume -name CannedDG1:vol6 -size 20480MB -seqpostreadcmdsize 0 -seqreadaheadmargin 1 -writecachepolicy on global spare -add -slot 1:6 -autocopyback off event log -setlevel -tlc 2622232552222200000066000 -alsal 3363333363333633383333 -arts 333333333353353333333 datascrub -set -auto off

Note: The autocopyback feature allows you to copy the data from a source drive of a virtual drive to a destination drive that is not part of the virtual drive. Autocopyback is often used to create or to restore a specific physical configuration for a drive group (for example, a specific arrangement of the drive group members on the device I/O buses). In general, when a drive fails or is expected to fail, the data is rebuilt on a global spare. After the failed drive is replaced by a new hard disk drive, the data is copied from the global spare to the new drive, and the global spare reverts from a rebuild drive to its original global spare status. The autocopyback operation runs as a background activity, while the virtual drive is still available online to the host.

For more information on the controller config command, see “controller config” on page 65

After you issue the command that loads the predefined configuration, define the hosts and the volumes that require access to them.

Configuring volumes for use with VMware

This topic describes the steps to configure volumes for use with the VMware operating system.

To properly failover the VI client, perform the following steps to set multipath configuration settings for the VMware:

1. Check the controller states and the preferred path from the RAID Controller command line interface (CLI) or IBM Storage Configuration Manager (SCM).

Using the RAID Controller command line interface (CLI)

a. Run the list controller command to ensure the controllers are in the

bound state.

<CLI> list controller Current Machine Local Time: 10/02/2009 09:11:55 AM

_______________________________________________ | Ctlr# | Controller | Status | Ports | LUNs | |_______|____________|___________|_______|______| | 0 | Ctlr0 | PRIMARY | 1 | 186 | | 1 | Ctlr1 | SECONDARY | 1 | 186 | |_______|____________|___________|_______|______|

b. Run the list pool command to check your preferred path. In the following

example, the raid1 pool has a preferred path set to controller 1 as indicated by slot 1. All volumes belonging to raid1 will have a preferred path to controller 1. Similarly, the raid5 pool has a preferred path set to controller 0 as indicated by slot 0.

<CLI> list pool Current Machine Local Time: 10/02/2009 09:12:01 AM

_________________________________________________________________________ |Pool#|ID| Name|RaidType|OwnerCtlr|TotalCap|AvailCap|Status|State|Degraded| |_____|__|_____|________|_________|_______ |_______ |______|_____|________| | 0 | 2|raid5| 5 | Slot 0 | 3832GB| 366GB|Viable| ONV | No | | 1 | 1|raid1| 1 | Slot 1 | 279GB| 247GB|Viable| ONV | No | |____ |__|_____|________|_________|________|________|______|_____|________|

Using IBM Storage Configuration Manager (SCM)

38 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

a. From the SCM navigation panel, select Health > Physical View, then select

the Controllers tab. Select each controller and ensure both controllers have a status of Normal (Online).

b. From the SCM navigation panel, select Configuration > Storage, then select

the Storage Pools tab. Select a storage pool that you plan to use with VMware, then select Properties from the More Actions list. From the General tab, note the Primary Controller which displays the preferred path. All volumes belonging to a storage pool will have the same preferred path as the storage pool.

2. Now that you have identified the preferred path for your volumes, perform the following steps to change the multipath setting within VMware.

a. Open the VMware Infrastructure Client. b. In the left panel, select the host that you want to change. c. In the right panel, click the Configuration tab. d. In the Configuration window, click the Properties link next to the Details

field to open the Datastore properties window.

e. Click Manage Paths to open the Manage Paths window. f. Near the top of the Policy section, click Change to open the Manage Paths -

Selection Policy window.

g. Select Fixed and click OK. h. Close any windows you opened to return to the main menu. Repeat these

steps for all hosts that you want to have this setting.

3. Configure the volumes within the VMware Operating System (OS) configuration to properly failover through the VI client.

a. Open the VMware Infrastructure Client. b. Select the blades with access to the SAS RAID Modules. c. Under Configuration, select Storage from the side panel and select the

volume to be changed.

d. Click Properties, then select Manage paths.

There are two paths in the Manage Paths window. The lower numbered path represents controller 0 and the higher numbered path represents controller 1. If the preferred path is same as indicated by the preferred path you investigated in step #1 through CLI or SCM, no action is required. If the preferred path is different from what is indicated in the CLI or SCM display, proceed to the next step.

e. Select the device path that you want to change then click Change. f. Under preference, select Preferred and click OK.

Repeat steps 3a through 3f for each of the volumes.

Note: If you change your pool ownership after completing these steps, you may need to re-modify your VMWare configuration.

Chapter 7. Working with storage pools and volumes 39

Configuring blades for Microsoft Cluster Service

This topic describes the steps to configure the SAS Expansion Card (CFFv) for IBM BladeCenter and the SAS Connectivity Card (CIOv) for IBM BladeCenter to support blades that are configured for Microsoft Cluster Service.

If you are configuring a server blade as a node in a Microsoft Windows 2003 clustering environment, you need to configure the SAS Expansion Card or the Onboard SAS Controller BIOS (for configurations with the SAS Connectivity Card) to support blades that are configured for Microsoft Cluster Service. If the SAS Expansion Card and the Onboard SAS Controller BIOS configuration is not set, nodes added to the cluster may fail to boot or hang with the console output as shown in Figure 3.

Figure 3. Example of a hung boot screen

Important: For blades that have the SAS Expansion Card or a boot disk connected through the SAS Expansion Card, you must apply Microsoft Hotfix 886569 for Microsoft Cluster Service to be able to manage the storage volumes. You can download Microsoft Hotfix 886569 at http://support.microsoft.com/kb/886569.

The steps you need to perform to configure the SAS Expansion Card and the Onboard SAS Controller BIOS depend on your boot disk type and external adapter type. Determine which steps you need to follow based on the boot option and the type of external SAS interface card you have installed:

v “Configuring blades with an internal boot disk and SAS Expansion Card” v “Configuring blades with a boot disk connected through the SAS Expansion

Card” on page 42

v “Configuring blades with the SAS Connectivity Card” on page 44

Configuring blades with an internal boot disk and SAS Expansion Card

Follow these steps when the SAS RAID Module is configured so that only data drives are presented to the blade host, and the host blade uses separate adapters for the internal boot drive and the SAS RAID Module data drives.

1. When the <<<Press Ctrl-C to start LSI Logic Configuration Utility>>> prompt displays during system boot, press Ctrl+C to enter the LSI Logic Configuration Utility. For blades with an enabled Onboard SAS Controller and the SAS Expansion Card, the Adapter List screen will be similar to Figure 4 on page 41. In Figure 4 on page 41, the SAS Expansion Card is shown as the first entry SAS3020XD. The adapter name may vary depending on the particular blade model and SAS Expansion Card version. To determine which entry is the SAS Expansion Card, you can temporarily disable the Onboard SAS Controller by pressing F1 during the boot; this removes the Onboard SAS Controller from

40 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

the Adapter List screen and the remaining entry will be the SAS Expansion Card. HS20 and LS20 blade types will have a single SAS entry by default as the internal hard drive is connected using SCSI.

Figure 4. Adapter List screen showing Onboard SAS Controller and SAS Expansion Card

2. Use the arrow keys to select the SAS Expansion Card then press Enter to display the Adapter Properties screen. Ensure that Boot Support is set to [Disabled], as shown in Figure 5. When the boot support is disabled, the LSI Adapter BIOS will not scan the data drives for boot devices.

Figure 5. Disabling boot support for the SAS Expansion Card

3. Press Esc to exit the Adapter Properties screen until the utility asks you to save the configuration as shown in Figure 6. Use the arrow keys to select Save changes then exit this menu, then press Enter. Back on the Adapter List screen, the Status of the external adapter now displays as [Disabled].

Figure 6. Saving configuration changes for the SAS Expansion Card

4. Change the boot order so that the Onboard SAS Controller is boot device 0. Use the arrow keys to select the Boot Order fields, then press Insert and Delete to change the boot order so that the Onboard SAS Controller is set to 0. Figure 7 on page 42 shows the correct boot order.

Chapter 7. Working with storage pools and volumes 41

Figure 7. Setting boot order to 0 for Onboard SAS Controller

5. Press Esc to exit the Adapter List screen. Use the arrow keys to select Exit the Configuration Utility and Reboot, then press Enter.

Figure 8. Saving the BIOS setting and rebooting

The blade now boots from the internal disk and will not scan the external drives during the boot. The first boot device is the Onboard SAS Controller.

Configuring blades with a boot disk connected through the SAS Expansion Card

Follow these steps when the SAS RAID Module is configured to boot the host blade, and also for data drives.

Note: The boot drive must be mapped to LUN0, and the data drive mapping can be any drive starting at LUN1. The boot drive must not be shared with other hosts blades on the SAS RAID Module.

1. During the blade boot, press F1 to disable the Onboard SAS Controller. The Devices and I/O Ports screen displays.

Figure 9. Devices and I/O Ports screen

2. Press Esc to exit the Devices and I/O Ports screen.

42 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

3. When the <<<Press Ctrl-C to start LSI Logic Configuration Utility>>> prompt displays during system boot, press Ctrl+C to enter the LSI Logic Configuration Utility. The Adapter List screen displays, similar to Figure 10.

Figure 10. Adapter List screen showing SAS Expansion Card

4. Use the arrow keys to select the external SAS adapter then press Enter to display the Adapter Properties screen. Ensure that Boot Support is set to [Enabled BIOS & OS].

Figure 11. Adapter Properties screen showing enabled BIOS and OS boot support for the SAS Expansion Card

5. Use the arrow keys to select Advanced Adapter Properties, then press Enter. The Advanced Adapter Properties screen displays as shown in Figure 12.

Figure 12. Advanced Adapter Properties screen

6. Use the arrow keys to select Advanced Device Properties, then press Enter. The Advanced Device Properties screen displays as shown in Figure 13 on page

44.

Chapter 7. Working with storage pools and volumes 43

Figure 13. Advanced Device Properties screen

7. Use the arrow keys to navigate to LUNs to Scan for Block Devices and set it to [Lun 0 Only].

8. Press Esc to exit the Adapter Properties screen until the utility asks you to save the configuration as shown in Figure 14. Use the arrow keys to select Save changes then exit this menu, then press Enter.

Figure 14. Saving configuration changes for the SAS Expansion Card

9. Press Esc to exit the Adapter List screen. Use the arrow keys to select Exit the Configuration Utility and Reboot, then press Enter.

Figure 15. Saving the BIOS setting and rebooting

Configuring blades with the SAS Connectivity Card

Follow these steps for blades that have the SAS Connectivity Card instead of an SAS Expansion Card. For configurations with the SAS Connectivity Card, the internal hard drive and external drives are on the same storage bus. To configure the blade to operate the SAS Connectivity Card, the Onboard SAS Controller BIOS must be set to scan LUN0 only during the boot and the external drives must be mapped with numbers higher then 0.

Note: If you map drives to the host through the RAID Controller command line interface, you must start the drive mapping with LUN1 or higher. If you start the drive mapping at LUN0, a boot delay will occur.

44 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

For blades that have the SAS Connectivity Card and are configured to be booted from an external SAS drive, the internal hard drive must be removed. Except for the requirements to remove the internal disk and to map a boot volume to the blade, the configuration for internal hard drive boot and external SAS boot is identical.

1. When the <<<Press Ctrl-C to start LSI Logic Configuration Utility>>> prompt displays during system boot, press Ctrl+C to enter the LSI Logic Configuration Utility. The Adapter List screen displays, similar to Figure 16.

Figure 16. Adapter List screen showing the Onboard SAS Controller.

2. Use the arrow keys to select the Onboard SAS Controller then press Enter to display the Adapter Properties screen.

Figure 17. Adapter Properties screen for the Onboard SAS Controller

3. Ensure that Boot Support is set to [Enabled BIOS & OS].

4. Use the arrow keys to select Advanced Adapter Properties, then press Enter.

The Advanced Adapter Properties screen displays as shown in Figure 18.

Figure 18. Advanced Adapter Properties screen

5. Use the arrow keys to select Advanced Device Properties, then press Enter. The Advanced Device Properties screen displays as shown in Figure 19 on page

46.

Chapter 7. Working with storage pools and volumes 45

Figure 19. Advanced Device Properties screen

6. Use the arrow keys to navigate to LUNs to Scan for Block Devices and set it to [Lun 0 Only].

7. Press Esc to exit the Adapter Properties screen until the utility asks you to save the configuration as shown in Figure 20.

Figure 20. Saving configuration changes for the Onboard SAS Controller

8. Use the arrow keys to select Save changes then exit this menu, then press Enter. The Adapter List screen displays again.

9. Press Esc to exit the Adapter List screen. Use the arrow keys to select Exit the Configuration Utility and Reboot, then press Enter.

Figure 21. Saving the BIOS setting and rebooting

Disabling IGMP snooping

Internet Group Management Protocol (IGMP) snooping is the process of listening to IGMP network traffic. In a cluster configuration, you should disable IGMP snooping to prevent node failover issues. Perform the following steps to disable IGMP snooping.

Disabling IGMP snooping through Telnet

1. Log into the Advanced Management Module: a. Enter the IP address of the Advanced Management Module into the Web

browser URL field. If you have the Advanced Management Module connected to your network, log in using the network IP assigned to it. If

46 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

you are using the default IP address your management system (the computer you are using to manage your IBM BladeCenter S components) must be physically connected through an Ethernet cable to the Advanced Management Module .

Note: The default IP address for the Advanced Management Module is

192.168.70.125.

b. Enter the username and password.

v The default username is: USERID v The default password is: PASSW0RD (the sixth position is the numeral

zero)

c. When prompted for the Inactive session timeout value, select no timeout.

Note: Remember to log out when you have completed your session. If you

do not log out, the system shows an error the next time you try to log in.

2. From the main menu, select the Ethernet module and choose Advanced Configuration.

3. Select Start Telnet Session.

4. Type cfg and press Enter to open the configuration menu.

5. Type group and press Enter to open the group menu.

6. Select the appropriate group number at the prompt

7. Type igmp at the selected group menu to change the IGMP setting.

>> Group 1# igmp Current Enable/Disable IGMP snooping on current group: enabled Enter new Enable/Disable IGMP snooping on current group [d/e]:

8. Press d to disable IGMP snooping.

Disabling IGMP snooping through a web session

1. Log into the Advanced Management Module: a. Enter the IP address of the Advanced Management Module into the Web

browser URL field. If you have the Advanced Management Module connected to your network, log in using the network IP assigned to it. If you are using the default IP address your management system (the computer you are using to manage your IBM BladeCenter S components) must be physically connected through an Ethernet cable to the Advanced Management Module .

Note: The default IP address for the Advanced Management Module is

192.168.70.125.

b. Enter the username and password.

v The default username is: USERID v The default password is: PASSW0RD (the sixth position is the numeral

zero)

c. When prompted for the Inactive session timeout value, select no timeout.

Note: Remember to log out when you have completed your session. If you

do not log out, the system shows an error the next time you try to log in.

2. From the main menu, select the Ethernet module from the Advanced Management Module and select Advanced Configuration.

3. Select Start Web Session.

4. From the navigation panel, select Miscellaneous settings > Uplink/Group.

Chapter 7. Working with storage pools and volumes 47

5. For IGMP settings, select Disable from the list of options.

48 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

Chapter 8. Using the RAID Controller command line interface

This section provides an overview and highlights some of the commands used in the RAID Controller command line interface.

The RAID Controller command line interface (CLI) is an independent program that you can use to operate the RAID controller. You must log in to a Telnet/ssh session using your user ID and password. The RAID Controller command line interface program starts automatically, and a <CLI> prompt appears. When you exit from the RAID Controller command line interface program, the Telnet/ssh session ends simultaneously.

Example of a user ID login:

> telnet controllerip

(none)login: USERID password:

Linux(none) 2.4.20_mv131-alc Rel H-2.4.20.12 Wed Jun 17 15:03:32 PDT 2009 ppc unknown

MontaVista(R) Linux(R) Professional Edition 3.1

<CLI>

List of commands

Use the commands defined by the RAID Controller command line interface to configuration and maintain the RAID controller. The commands are categorized into the following categories:

1. Display Commands

2. Volume Management

3. Volume Services

4. System Control and Configuration

Size reporting through the CLI

The RAID Controller command line interface (CLI) reports the precision of volume, storage pool, and disk drive sizing to the nearest gigabyte. When adding fractions of a gigabyte, the CLI rounds the result to the nearest gigabyte.

Display help for commands

If any <CLI> command is issued with the -help option, a contextual help page is displayed. Type help at the <CLI> command prompt to display the list of available commands.

Display commands

Use the SAS Switch command line interface for the RAID controller to perform administrative tasks for the device. This topic details the commands that you can use to display information.

detail controller

The detail controller command creates output detailing information about the controller selected.

Command arguments:

<CLI> detail controller –ctlr [0|1]

Where:

v [0|1] - Allows selection of the controller.

Example:

<CLI>detail controller –ctlr [0|1]

Current Machine Local Time: 07/26/2012 00:35:24 AM

Controller Information :

UltraSlice Version : ALC3300 Software version : H-2.1.2.4 Uboot Version : H-1.1.4.6 OS version : H-2.4.20.12 SES version : 0107 BMC version : S0BT10A 0121 02/08/2010 FPGA version : 01.07 CPLD version : S0CP00A C00A 01/01/2000 SAS switch version : S0SW01D R107 12/17/2009 Chassis Serial Number : KQWZZN1 WWN : 5005076b07402cff

Chassis Machine Type/Model : 8886AC1 SAS RAID Controller Module Part Number : 43W3605 SAS RAID Controller Module FRU Part Number : 43W3630 SAS RAID Controller Module Serial Number : YK101279B016 Machine Signature SAS RAID Controller Module Location : IO Bay 3 Manufacturer ID : IBM SAS RAID Controller Module Hardware Revision ID : 2 SAS RAID Controller Module Hardware Product ID : 00a5 MAC Address (upto 8) : 00:1A:64:9E:00:61 Target port WWN : 5005076b07402ca0 Target port protocol : SAS Target port speed : 3Gbps

Current Status : SECONDARY System Hardware Configuration Mode : Dual

BBU State : 1 (Working) BBU Fault Code : 0 (None) BBU Part Number : 45W4439 BBU Serial Number : YK10MY2810D2 BBU FRU Number : 45W5002 BBU Firmware Revision : 58.0 BBU Expiration Date : Sat Jul 23 12:00:00 2016 Charging state information BBU Charging : False BBU Capacity (Hours) : 72+

50 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

Associated Volumes currently serviced by this controller:

_____________________________________________________________________________ | Vol# | VolumeName | Cap | RaidType | Status | |______|_______________________|_________|___________|_______________________| | 0| p1r10:p1r10_V01| 1000GB| 10| VBL INI| | 1| p1r10:p1r10_V02| 2000GB| 10| VBL INI TRN| | 2| p1r10:p1r10_V03| 100GB| 10| VBL INI TRN| |______|_______________________|_________|___________|_______________________|

Usage: VBL=Viable DEG=Degraded INI=Inited

detail drive

The detail drive command creates output detailing information about the drive specified by the bay position.

When the drive is specified by a number, that number refers to the sequence number that appears on the list displayed when issuing the list drive command. Issue the list drive command before you issue detail drive with the –number option, so that there is an internal reference list. If you do not issue the list drive command first, an error displays.

Command arguments:

<CLI> detail drive [ -slot | -number [REFNUM] ]

Where:

v [REFNUM] - Refers to the sequence number on the list displayed when you issue

the list drive command.

Example:

<CLI> detail drive -slot 1:1

_____________________________________________________________________________ | Drive#| E:T | SerialNo | Cap | Pool | Usage | State | |_______|_______|_______________________|_______|_____________|_______|_______| | 0| 1:1 | 9QK0SWLM| 698GB| raid10pool| GRP| OK| |_______|_______|_______________________|_______|_____________|_______|_______|

NVBL=Non-Viable TRN=In-Transition

________________________________________ | Mount State |Ctl0|Ctl1| RPM |FW level| |_____________|____|____|_______|________| | Online| 1| 1| 7200| BC1D| |_____________|____|____|_______|________|

Drive SAS Address : 5000c5000d218b73 Vendor / Manufacturer ID : IBM-ESXS IBM Option Number : 42D0546 IBM FRU Number : 42D0548 IBM Part Number : 42C0279 Interface Type : SAS Disk Speed : 7200 Serial Number : 9QK0SWLM Code Level : BC1D Product Master ID : 41Y8468 Product Family ID : ST3750630SS

__________________________________________ | Volume | RaidType | Size | |___________________|____________|_________| |raid10pool:rd10vol1| 10| 174GB|

Chapter 8. Using the RAID Controller command line interface 51

|raid10pool:rd10vol3| 10| 174GB| |raid10pool:rd10vol5| 10| 174GB| |raid10pool:rd10vol4| 10| 174GB| |raid10pool:rd10vol2| 10| 174GB| |raid10pool:rd10vol6| 10| 174GB| |raid10pool:rd10vol8| 10| 174GB| |raid10pool:rd10vol7| 10| 174GB| |___________________|____________|_________|

detail pool

The detail pool command provides detailed information about any pool. The pool can be specified by a name or number. The -name option uses the pool name as input.

Command arguments:

<CLI> detail pool [–name poolname | -number number]

Where:

v poolname - Defines the name of the pool. v number - Refers to the sequence number on the list displayed when you issue the

list pool command.

Example:

<CLI> detail pool -name pool1 _____________________________________________________________________________________________ | ID | Name |RaidType|OwnerCtlr|TotalCap|AvailCap| Status | State | Degraded | |____|___________|________|_________|________|________|_____________|__________|____________| | 2| DG2| 1| IO 3| 33GB| 28GB| Viable| MV| No| |____|___________|________|_________|________|________|_____________|__________|____________|

When the pool is specified by a number, that number refers to the sequence number that appears on the list displayed when issuing the list pool command. Issue the list pool command before you issue detail pool with the –number option, so that there is an internal reference list. If you do not issue the list pool command first, an error displays.

Any volume service currently running on this pool also displays in the status.

The state definitions are:

v UN - Unmounted, Non-viable v MF - Mounted, Failed v UF - Unmounted, Failed v DN - Dismounted, Non-viable v DF - Dismounted, Failed v UV - Unmounted, Viable v DV - Dismounted, Viable v MV - Mounted, Viable v MN - Mounted, Non-viable

Note: One or more drives are missing in this pool. You must acknowledge an alert pertaining to this state. If the missing drive comes back to make the pool viable, the state automatically changes to MV. When you acknowledge the alert, the state of the pool becomes UN.

52 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

Information about a drive in the primary section is as follows:

__________________________________________________________________________________________ | Slot | SerialNo | Cap | Grp | Usage | State | Mount State | Ctl0 | Ctl1 | |________|______________ ___|_______|________|_______|_______|_____________|______|______| | 1:5| DQR9P6C00D3F| 33GB| DG2| GRP| OK| Mounted| 1| 1| |________|__ _______________|_______|________|_______|_______|_____________|______|______|

Information about a drive in the secondary section is as follows:

_________________________________________________________________________________________ | Slot | SerialNo | Cap | Grp | Usage | State | Mount State | Ctl0 | Ctl1 | |________|___________________|_______|_______|_______|_______|_____________|______|______| | 2:6| DQR9P6C00D8S| 33GB| DG2| GRP| OK| Mounted| 1| 1| |________|___________________|_______|_______|_______|_______|_____________|______|______|

Information about existing volumes is as follows:

__________________________________________________________________________________ | Volumes | Cap | GrpName | RaidType | Status | |_______________________|__________|_____________|__________|____________________ _| | DG2:Vol5| 690MB| DG2| 10| Viable Inited | | DG2:Vol6| 1GB| DG2| 10| Viable Inited | | DG2:Vol7| 1GB| DG2| 10| Viable Inited | | DG2:Vol8| 1GB| DG2| 10| Viable Inited | |_______________________|__________|_____________|__________|______________________|

detail volume

The detail volume command creates output detailing information about any volume. The volume can be specified by name or number. The name is specified as a poolName:volumeName combination.

When the volume is specified by a number, that number refers to the sequence number that appears on the list displayed when issuing the list volume command. Issue the list volume command before you issue detail volume with the –number option, so that there is an internal reference list. If you do not issue the list volume command first, an error displays.

The state definitions are:

Information about contributing drives is as follows:

_____________________________________________________________________________________________ | Drive# | Slot# | SerialNo | Cap | Pool | Usage | State | Mount State | Ctl0 | Ctl1 | |________|_______|______________|_______|________|_______|_______|_____________|______|______|

Chapter 8. Using the RAID Controller command line interface 53

| 0| 1:5 | DQR9P6C00D3F| 33GB| DG2| GRP| OK| Mounted| 1| 1| | 1| 2:6 | DQR9P6C00D8S| 33GB| DG2| GRP| OK| Mounted| 1| 1| |________|_______|______________|_______|________|_______|_______|_____________|______|______|

Information about an associated controller is as follows:

_________________________________________________________ | Controller | Status | Ports | LUNs | |________________|____________________|_________|_________| | Ctrl0| MASTERBOUND| 1| 1| |________________|____________________|_________|_________|

Command arguments:

<CLI> detail volume [–name poolname:volumename| –number number]

Where:

v poolname:volumename - Allows selection of the volume name as a combination of

poolname and volumename.

v number - Refers to the sequence number on the list displayed when you issue the

list volume command.

Example:

<CLI> detail volume -name pool1:vol1

View Volume Info vol1

_________________________________________________________________ | VolumeName | Cap | RaidType | Status | |___________________________|_________|___________|_______________| | pool1:vol1| 4GB| 0| Viable| |___________________________|_________|___________|_______________|

HostLUNs mapped:

___________________________________________________ | HostWWN | LUN | Permission | |_____________________|___________|__________________| | 784875485454| 3| READWRITE| |_____________________|___________|__________________|

Pool information: ___________________________________________________________________________________________ | ID | Name |RaidType|OwnerCtlr|TotalCap|AvailCap| Status | State | Degraded | |____|___________|________|_________|________|________|____________|__________|____________| | 1| pool1| 0| IO 3| 33GB| 28GB| Viable| MF| No| |____|___________|________|_________|________|________|____________|__________|____________|

54 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

detail volume verbose

The detail volume verbose command creates output detailing information about all of the Logical Unit Numbers (LUNs). A LUN is a number assigned to a logical unit.

Command arguments:

<CLI> detail volume verbose

Example:

<CLI> detail volume verbose ______________________________________________________________________ | Name |RaidType| HostWWN | LUN | Size | Status | |__________________|________|_________________|______|_______|________| | pool1:vol1| 0| 784875485454| 3| 4GB| Viable| |__________________|________|_________________|______|_______|________|

list controller

The list controller command creates output providing summary information about each controller. The status of a controller is the actual running state of the controller.

Command arguments:

<CLI> list controller

____________________________________________________________________ | Ctlr# | Controller | Status | Ports | LUNs | |_____________|________________|_________________|_________|_________| | 0 | Ctrl0| MASTERBOUND| 1| 1| | 1 | Ctrl1| SLAVEBOUND| 1| 1| |_____________|________________|_________________|_________|_________|

Examples:

<CLI> list controller

_____________________________________________________________________ | Ctlr# | Controller | Status | Ports | LUNs | |_____________|________________|_________________|_________|_________| | 0 | Ctrl0| STARTING| 1| 1| | 1 | Ctrl1| SHUTDOWN| 1| 1| |_____________|________________|_________________|_________|_________|

Chapter 8. Using the RAID Controller command line interface 55

list drive

The list drive command creates output providing summary information about each drive.

The drive bay number is E:T. E:T stands for [Enclosure]:[Tray], where E is the enclosure number and T is the position of the hard drive. These positions/locations begin with 1 and 1 is the uppermost drive.

The usage definitions are:

v UNA - UnAssigned v GRP/SGR - Current/Stale Group Member v FOR - Foreign v GLS/SGS - Current/Stale Global Spare v NQ - Non-qualified v LCS/SLS - Current/Stale Local Spare v CBL/SCL - Current/Stale Auto-copy-back Local Spare v CBG/SCG - Current/Stale Auto-copy-back Global Spare

The state definitions are:

v OK - Healthy v M - Missing v P - Predicted Failure (PFA) v U - Unreliable

Note: M P U states can be combined.

v PM - Path Missing v UP - UnReliable PFA v MP - Missing PFA v MUP - Missing UnReliable PFA v MU - Missing UnReliable v INI - Initialized v UNS - Unsupported (non-IBM device). v PM - Path Missing The drive is OK, but one or more paths are not usable. v IMD - Incompatible metadata The metadata on the drive is incompatible with

the firmware version. Assimilate the drive or upgrade the firmware.

v UNF - Unsupported drive firmware version

Important: Drive assimilation a destructive procedure causing complete data loss. Use this command only if your intention is to irrevocably erase all disk data.

Command arguments:

<CLI> list drive

Example:

<CLI> list drive

________________________________________________________________________________________________ |Drive# | E:T | SerialNo | Cap | Pool | Usage | State | Mount State | Ctl1 | Ctl2 | RPM | |_______|______|______________|_______|______|_______|_______|_____________|______|______|______|

56 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

| 0| 1:4| DQR9P6C00D1H| 33GB| --| UNA| U| Dismounted| 1| 1| 0| | 1| 1:5| DQR9P6C00D3F| 33GB| DG2| GRP| OK| Mounted| 1| 1| 0| | 2| 2:6| DQR9P6C00D8S| 33GB| DG2| GRP| OK| Mounted| 1| 1| 0| | 3| 2:2| DQR9P6C00D8U| 33GB| --| UNA| OK| Mounted| 1| 1| 0| | 4| 2:1| DQR9P6C00D8V| 33GB| --| UNA| OK| Mounted| 1| 1| 0| | 5| 2:3| DQR9P6C00D9A| 33GB| --| UNA| OK| Mounted| 1| 1| 0| | 6| 1:6| DQR9P6C00DBK| 33GB| --| UNA| OK| Mounted| 1| 1| 0| | 7| 1:3| J3XU3MVK| 33GB| --| UNA| OK| Mounted| 1| 1| 0| | 8| 1:1| J3XU3R0K| 33GB| --| UNA| OK| Mounted| 1| 1| 0| | 9| 1:2| J3Y564BK| 33GB| --| UNA| OK| Mounted| 1| 1| 0| | 10| 2:4| J3Y8DVLK| 33GB| --| UNA| OK| Mounted| 1| 1| 0| | 11| 2:5| J3YWKMKJ| 33GB| --| UNA| OK| Mounted| 1| 1| 0| |_______|______|______________|_______|______|_______|_______|_____________|______|______|______|

list pool

The list pool command creates output providing summary information, including the status, about each pool. Any volume service currently running on a pool is also shown in the status. Size displayed is total and available capacity.

The state definitions are:

Command arguments:

<CLI> list pool

Example:

<CLI> list pool

_____________________________________________________________________________________________ |Pool#| ID | Name |RaidType|OwnerCtlr|TotalCap|AvailCap| Status |State |Degraded| |_____|____|______|________|_________|________|________|_____________________|______|________| | 0| 1| DG1| 5| IO 3| 267GB| 117GB|Degraded-InTransition| MV| Yes| |_____|____|______|________|_________|________|________|_____________________|______|________|

Chapter 8. Using the RAID Controller command line interface 57

list volume

The list volume command creates output providing summary information about all volumes. The volume name displays as poolname:volumename.

The possible states of a volume are:

v Viable v Degraded v InTransition v Inited

An Inited state indicates that the volume has been initialized.

Command arguments:

<CLI> list volume

Example:

<CLI> list volume

________________________________________________________________________ | vol# | VolumeName | Cap | RaidType | Status | |______|___________________________|_________|___________|_______________| | 0| pool1:vol1| 4GB| 0| Viable| | 1| Group0:vol1| 183GB| 5| Viable| | 2| ADMIN:v2| 197GB| 10| Degraded | | 3| MyData:MyVolume| 4GB| 0| Inited| | 4| pl23:volume0| 44GB| 0| InTransition| |______|___________________________|_________|___________|_______________|

System control and configuration commands

Use the RAID Controller command line interface to perform administrative tasks for the device. This topic details commands about system control and configuration.

alert

The alert command displays system alerts, changes the state of system alerts, and creates a generic alert. Use the -get option to display alerts generated in the system at any given point. To change the state of the alerts specified by the alert code and alert id, use the -mask, -unmask,or-ack option. Use the -create option to create a generic alert with the alert code specified by the –code option.

Note: Refer to the Troubleshooting section for description and details on the alerts and codes.

Command arguments:

-help option

Usage : alert [ -get | [-create|-clear] -code genericAlertCode | -savehistory |

[-get] : Displays the alerts generated in the system at any given point. [-mask] : When this command is used with mask/unmask or ack options, it can be used to

[-savehistory] : Saves alert history into a file.

-code : alert code of the alert you want to take action on.

-[ mask | unmask | ack ] -code AlertCode -id Id -ctlr SlotID ]

change the state of the alerts in the system specified by the alert code and alert id.

58 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

battery

-id : id of the alert message to be taken action on .

-ctlr : slotID of the controller where you want the action to be taken place on an alert message.

[-create] : This option can be used to create a generic alert with the alert code specified

by ’-code’ option. The valid range for the alert code is between 10000-19999. The description and details of these codes can be found in RAS user guide.

[-clear] : This option can be used to clear a generic alert with the alert code specified

by ’-code’ option. The valid range for the alert code is between 10000-19999.

Example:

<CLI> alert -get Current Machine Local Time: 04/02/2009 11:24:34 AM

Existing Alerts :

__________________________________________________________________________________________ |AlertCode| Id | Time |SlotID| Severity | WWN | Ackable | MaskState | |==========================================================================================| | 5600 | 2 |20090325124508| 0| Info |5005076b074059ff| 1 | Masked | |------------------------------------------------------------------------------------------| | Msg: Illegal host 0x500062b00007ccc0 access attempted | |==========================================================================================|

Use this command to manage the Battery Backup Units.

Command arguments:

<CLI> battery -ctlr [0|1] -get

Where:

v [0|1] - Allows you to select controller 0 or 1.

When you issue this command with the -get option, the current status of the battery is displayed:

Example:

<CLI> battery -ctlr 0 -get

Controller 0

Basic battery type and status BBU State : 1 (Working) BBU Fault Code : 0 (None)

Part Number : 45W4439 Serial Number : YK10MY2810D2 FRU Number : 45W5002 FirmwareRev : 58.0 Expiration Date : Sat Jul 23 12:00:00 2016

Charging state information Charging : False Capacity (Hours) : 72+

<CLI>

Chapter 8. Using the RAID Controller command line interface 59

cache settings

Use this command to specify the cache settings.

Command arguments:

<CLI> cache -[get | set [-volumesetting -seqpostreadcmdsize [SIZE]

-seqreadaheadmargin [MARGIN] -writecachepolicy [off|on|default] [-systemdefault] [-volumename [POOL:VOLUME]] | ctlrsetting

-writecachepolicy [on|off] ]

Where:

v [SIZE] - Indicates maximum sector count of single predictive read ahead. v [MARGIN] - Defines number of sectors in read ahead buffer. v [off|on|default] - Allows you to turn -writecachepolicy offoronortouse

with default settings.

v [POOL:VOLUME] - Indicates pool name and volume name. If pool name not

specified, all system volume settings are modified; if pool name specified but volume name is not specified, cache settings are applied to all volumes in pool.

v [on|off] - Allows you to turn -writecachepolicy on or off when –ctlrsetting

option is specified.

The maximum sector count of a single predictive read ahead is seqpostreadcmdsize. A value of 0 disables predictive read for this volume. A value of 1-128 overrides the previous setting and represents a command transfer size that is a multiple of 16Kb. A value of (0xFFFF) causes the default value to be used. The number of sectors in the read ahead buffer is seqreadaheadmargin. This parameter is ignored if the seqpostreadcmdsize is zero. The valid range is 1 to 0x7FFF. A value of (0xFFFF) causes the default value to be used. The firmware sets the writecachepolicy to specify the write cache policy. If none of the cache options are provided, the current system default settings are used.

If you do not specify the -poolname, all volumes in the system will have their settings modified. If you specify the -poolname but do not specify the -volumename, the cache settings will be applied to all the volumes in the pool.

If you specify the –systemdefault option, the setting is used to change the system default. System default is used to set the cache policy for a new volume that was created with the cache policy set to default.

If you specify the –get option, the system default setting is displayed.

If you specify the –ctlrsetting option, the write cache settings for the controller are set.

60 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

chpasswd

Use this command to change the password for the selected user on an SAS RAID Module. If the firmware level of your RAID controllers is older than 1.2.x.xxx, you need to change the password on both SAS RAID Modules at the same time. If the firmware level of your RAID controllers is 1.2.x.xxx or newer, then changing the password on one SAS RAID Module automatically changes the password on the other SAS RAID Module.

Command arguments:

<CLI> chpasswd -[cli | mgmtInterface ] -oldpasswd [OLDPWD] -newpasswd [NEWPWD]

-help option

Usage : chpasswd -[cli | mgmtInterface ] -oldpasswd [OLDPWD] -newpasswd [NEWPWD]

-cli : change the password for the CLI user

-mgmtInterface : change the password for the management interface OLDPWD : old password for the user NEWPWD : new password for the user - it should be minimum of 8, maximum of 16 characters

clilog

The clilog command prints the log of all CLI commands issued and their timestamps. If you specify the -save option with a filename, the log is saved to the file.

There should be at least one alphabet and one numeric character in the password Please use a combination of upper and lower case letters and numbers for the password

Command arguments:

<CLI> clilog [–save file]

Where:

v file - Names the file where the log is saved.

Example:

<CLI> clilog –save clilogfile

commparams

The commparams command is issued by the system administrator to set or display the communication parameter settings. Communication is with outside agencies by using Telnet or one or more Ethernet communication links, and the serial port provided on the microprocessor.

Command arguments:

<CLI> commparams -[get -ctlr [0|1] -port [0|1] -ip i.j.k.l -gateway i.j.k.l

-netmask -i.j.k.l [-vlan n -vlaninsert [on|off]]]

Where:

v [0|1] - Allows selection of the controller or port. v i.j.k.l - Allows selection of the IP address , gateway, or netmask. v n - Allows selection of the VLAN tag. v [on|off] - Allows selection of the VLAN tag insert.

Example:

Chapter 8. Using the RAID Controller command line interface 61

<CLI> commparams –get

Ctlr0 Port0 Port1

IP ADDRESS 192.168.75.16 192.168.75.17

GATEWAY 192.168.75.1 192.168.75.1 NETMASK 255.255.255.0 255.255.255.0

VLAN tag insert 0d 0d

Ctlr1 Port0 Port1

VLAN tag insert 0d 0d

Switch Ip Address Information :

Switch Ip Address1 : Switch Ip Address2 :

VLAN tag 0d 0d

IP ADDRESS 192.168.75.18 192.168.75.19

GATEWAY 192.168.75.1 192.168.75.1 NETMASK 255.255.255.0 255.255.255.0

VLAN tag 0d 0d

configure access

Use the configure access command to set or display configurable access protocols (SSH and Telnet).

An error occurs if you issue the -set option while the list is empty.

Note: If you disable both SSH and Telnet access protocols, you must reset the RAID controller back to the factory defaults to re-enable both access protocols. For instructions on resetting the RAID controller, see“How to reset the SAS RAID controllers to the factory defaults” on page 183.

Command argument:

configure access -[get | set -enable|disable [SSH|TELNET] | help]

Examples:

<CLI> configure access -get Current Machine Local Time: 09/16/2011 04:28:38 AM _____________________________________________ | Access Protocol | Status | |____________________|_______________________| | TELNET| ENABLED| | SSH| ENABLED| |____________________|_______________________|

<CLI> configure access -set -disable telnet <CLI> configure access -get _____________________________________________ | Access Protocol | Status | |____________________|_______________________| | TELNET| DISABLED| | SSH| ENABLED| |____________________|_______________________|

62 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

configure alert

The configure alert command selects the alert messages to send by email. Previously configured messages display as configured and can be cleared.

Use the -get option to display the list of alerts and to build a local list of system alerts before using the –set option to configure the alerts. Use the -set option to clear the list. An error appears if you issue the –set option while the list is empty.

Command arguments:

<CLI> configure alert [ -get | -set | -setgenericalerttemplate ]

-help option

Usage : configure alert -[get | set [-email | -initiallymasked]

[-get] : Displays the email and initiallymasked properties of alerts

[-set] : Enables the user to set the email and initiallymasked attribute

[-setgenericalerttemplate] : Enables the user to create or replace an entry in alertTemplates

on : Sets the attribute to ’on’ for the alertCode specified by RefNum. off : Sets the attribute to ’off’ for the alertCode specified by RefNum. email : When email attribute is set for an alert, an email is generated

initiallymasked : When this attribute is set for an alert, initiallymasked LED is

type : Defines the type of alert for generic alert being specified. severity : Defines the severity of alert for generic alert being specified. msg : Defines the message for the generic alert. The string should be

-on <RefNum RefNum...> -off <RefNum RefNum...> | setgenericalerttemplate -code <genericAlertCode>

-type [persistent|ackable] -initiallymasked [on|off]

-email [on|off] -severity [critical|warning|info]

-msg "DesiredAlertStringInQuotes"]

currently defined in alertTemplates.

for any email.

for generic alerts.

every time that alert is created in the system.When this attribute is set, email is only generated for future events and not for existing alerts.

lighted every time that alert is created in the system.When this attribute is set, LED is lighted for future events and not for existing alerts.

specified within quotes for this command. The string is saved in the alertTemplates without the quotes.

Where:

v number - Defines the reference number of the alert displayed by using the -get

option.

Examples:

<CLI> configure alert -get Current Machine Local Time: 04/08/2009 09:47:11 AM

Ref# Code EmailOn InitialMask AlertMsg

---- ----- ------- ----------- --------

1 0 On Unmasked TestAlert %s 2 2 Off Masked Compatible drive enclosure %<EnclosureId> found 3 3 Off Masked Drive enclosure %<EnclosureId> removed 4 4 Off Masked Drive enclosure %<EnclosureId> firmware updated 5 100 On Masked Controller firmware updated 6 101 Off Masked Disorderly shutdown detected - System restored from battery

7 102 On Unmasked Controller in survivor mode - Redundant controller

8 103 Off Masked New controller recognized 9 104 Off Masked Replacement media tray %<BackplaneId> detected

State State

backup

%<ControllerId> is offline

Chapter 8. Using the RAID Controller command line interface 63

10 105 Off Masked ArtsTime %<AltString:1=initialized:2=updated> - previous value

11 110 Off Masked API requested %<AltString:1=ctlr1:2=ctlr2:3=ctlrs 1&2> to

configure pool

The configure pool command allows of user to change the owner controller for a group from CLI. This command must be run on a survivor controller. The other controller must be in service mode.

Command arguments:

<CLI> configure pool -name [POOLNAME] -changeowner

-help option

COMMAND-HELP: configure pool

This command is used to change the owner controller for a group from CLI.

This command must be run on a survivor controller. The other controller must be in service mode.

Usage : configure pool -name [POOLNAME] -changeowner. POOLNAME : Name of the pool that needs to change the owner controller.

Examples:

<CLI> configure pool -name p1r5 -changeowner Current Machine Local Time: 02/07/2013 11:04:44 AM Error : Change pool ownership command failed Reason: Controller state is not valid for this request

was %<TimeDate>

shutdown and %<AltString:1=power off:2=enter service mode>

Note: One of controller must be in survivor mode.

<CLI> shutdown -ctlr 1 -state servicemode Current Machine Local Time: 03/04/2013 01:22:51 PM Shutdown Command accepted

<CLI>configure pool -name p1r5 -changeowner Current Machine Local Time: 03/04/2013 01:45:45 PM Change pool ownership command successful

configure timeout

The configure timeout command displays and sets the session timeout for the command line interface. When the configured timeout period is reached, the system automatically closes the CLI session.

By default, CLI session timeout is disabled. The minimum timeout period is two minutes (120 seconds). To disable CLI session timeout after you have configured it, use the -set option and specify "00" for HR, MIN, and SEC.

An error appears if you issue the -set option while the list is empty or if the timeout value is invalid.

Command arguments:

<CLI> configure timeout -[get | set <HR:MIN:SEC> | help]

-help option

64 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

<CLI> configure timeout -[get | set <HR:MIN:SEC> | help] Usage : configure timeout -[get | set <HR:MIN:SEC> | help] [-get] : Displays the CLI session timeout settings [-set] : Sets the CLI session timeout period. HR : Number of hours. The number must be less than two digits. MIN : Number of minites. The number must be less than two digits. SEC : Number of seconds. The number must be less than two digits.

Examples:

<CLI> configure timeout -set 00:01:30 Current Machine Local Time: 09/16/2011 03:54:33 AM Error : configure timeout command failed

Note: The timeout period is less than two minutes.

<CLI> configure timeout -set 00:02:30 Current Machine Local Time: 11/16/2011 05:07:08 PM CLI Session Timeout is set to 150 seconds

<CLI> configure timeout -set 00:00:00 Current Machine Local Time: 11/16/2011 05:07:21 PM CLI Session Timeout is set to DISABLED

controller config

The controller config command is used for controller configuration. When this command is issued, a config file is generated where settings are stored or retrieved.

The two sections of the config file are: v System configuration - Contains drive pool, volume, spares, and host

configurations.

v Controller settings - Contains read write and read only fields. The read write

fields contain cache settings (read and write cache enables), redundant mode, port speeds, topology, and IP address/net mask. The read only fields contain the controller World Wide Name (WWN), a unique 64-bit address used for identification.

Issue this command with the -load option for the following: v Restore factory settings - This restores the factory default to the controller. Use a

file that contains factory settings as the config file. The factory settings are in the Controller settings section of the file.

v Canned Config - This quickly prepares a system for operation based on

predetermined settings. Use a file with a valid server and host configuration as the config file.

v Clone system - This uses the saved config file to program another system.

Issue this command with the -save option for the following:

v Clone system - This uses the saved config file to program another system. v Print configuration - This prints the configuration of the system to the config file.

You can read and edit the config file.

Issue this command with the -get option to print the config file information on the screen for all config files.

Command arguments:

<CLI> controller config [ -save | -load | -get | -delete | -deleteall]

Chapter 8. Using the RAID Controller command line interface 65

Where:

[-save] : Prints the configuration of a system out to a file and

be read/edited by user.

[-load] : By issuing this command with -load. option, following

FILENAME : The filename specifies the name of the file where the

[-get] : Executing this command with ’-get’ option prints the

[-delete] : Deletes the user generated configuration file(s)

[-deleteall] : Deletes all the user generated configuration file(s).

could be accomplished:

1. Restore factory settings: A file with factory settings could be given as input filename which restores the factory default to the controller. This path is mostly used for restoring factory defaults for controller settings (second part of the config file)

2. Canned Config: A file with a valid back-end and host configuration can be provided to prepare a system for operation based on a pre-decided settings quickly.

3. Clone system: A file coming from a configured system (generated using

[controller configuration -save filename])command can be used to program another system.

settings are stored or retrieved "-" is an invalid character and should not be included in the filename.

config file’s header information on the screen for all config files.

specified.

Example: none

email alert

The email alert command selects and sends critical alerts to the your users by email. It allows you to enter an email address configuration and save it. You can do this for up to five email addresses added one at a time. The host name, port number and sender setting overwrites existing settings. The email that is sent out has following format:

Alert Code:1300 Drive 3:5000c500003cd4ff failure detected - Previous drive status was spare Controller WWN: 327654ABE76DD67C Controller SerialNumber : 123abfe56dd

Use the -test option to configure and send a test communication to a specified email account.

Command arguments:

<CLI> email alert –[get | delete –email email| set [-test] –email email –smtpserver server

-help option

<CLI> email alert –[get | delete –email email| set [-test] –email email –smtpserver server

[-set] : Enables the user to enter an email address configuration and save it. [-test] : If this option is selected along with [-set] option, the email is configured

[-get] : Displays the current email configuration with emailId , smtp server ,smtp port [-delete] : Deletes specific email id EMAIL : EmailId of the person who wants to get the alerts. SERVER : IP address of the SMTP server .

–smtpport port -smtpsender [SENDER]]

and a test mail is sent. If this option is selected without any other option, the command sends a test alert to the email already configured

66 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

PORT : Port number on which SMTP server listens . SENDER : Sender’s full IP address. SMTP domain name is extracted from it so it must be

valid for email to work.The format of this input should be in user@domain format.

enclosure reporting

Use this command to get type, version, and status data on enclosures (Disk Storage Modules).

Command arguments:

<CLI> list enclosure

_______________________________________________________ | Encl# | Enclosure | Type| Version |Status | |_________|____________|___________|_________|________| | 0 | Encl0 | Controller| 0004 | Good | | 1 | Encl1 | DSM | 0.42 | Good | | 2 | Encl2 | DSM | 0.42 | Good | |________ |____________|___________|_________|________|

<CLI> detail enclosure -encl 0 Enclosure Information:

Enclosure Type : Controller

Package Version : 0100

SES version : 0100

Part No : PN

FRU No : FN

Serial Number : SN

Slot # : 4294967295

Controller 1 :

Voltage : 11.85 Volts

Controller 2 :

Voltage : 11.80 Volts

Status : Good

<CLI> detail enclosure -encl 1 Enclosure Information:

Enclosure Type : DSM

Package Version : 0.98 SES version : 0.98 Enclosure Processor Version : 0.98 Power Controller Version : 1.13 Part No : FRU No :

Serial Number : Slot # : 0 Status : Good

<CLI> detail enclosure -encl 2 Enclosure Information:

Enclosure Type : DSM

Package Version : 0.98 SES version : 0.98 Enclosure Processor Version : 0.98 Power Controller Version : 1.13 Part No : FRU No :

Chapter 8. Using the RAID Controller command line interface 67

Serial Number : Slot # : 0 Status : Good

event log

The event log command detects and analyzes errors by using a trace capability. Trace information is captured in a file in the controller which the system administrator can browse. Information is displayed or stored for ALSAL, ARTS, or TLC modules. Information can also be displayed or stored for all modules.

Use this command with the -show option to display the event log captured by the system for one or all of the modules.

Use this command with the -save option to store the event log captured by the system for one or all of the modules. Information is saved to a file named

EVENTLOG_timestamp. A maximum of three files remains in the system. If you issue

-save when three files exist in the system, the oldest file is deleted before the new

one can be saved. You can retrieve the deleted file with a getFile mechanism defined and implemented in external software by using the gSoap protocol. You can also retrieve other dump information, such as cdump and controller log,inthe same way.

Command arguments:

locate

Where:

v [all|arts|alsal|tlc] - Allows selection of all modules or one module.

Examples:

<CLI> event log –show all

.. .. ..

<CLI> event log –save arts Traces saved to file named EVENTLOG_03312008123456.trace

The locate command illuminates the information LEDs on the drives corresponding to the objects you select.

Command argument:

<CLI> locate

Please select one of this options Usage : [ -off | -getobject | -setobject ]

COMMAND-HELP: locate object

[-setobject [ -drive [ slot | all] | -pool poolname | -volume poolname:volumename |

-ctlr [0|1] | -bbu [0|1] | -enclosure [0|1|2] | -number objectnumber] ]

This command lights up the LED on the drives corresponding to the objects selected. If only drive object is selected, [-setobject] : This command lights up the LED on the selected objects.

If the selected object is a drive, the LED on that drive is litup. If the selected object is a pool or a volume, LEDs on all the drives making up that

68 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

object light up. The object can be specified using either the name or sequence number in the list returned by ’-getobject’ command.

[-getobject] : This command with ’-getobject’ option is used to get a list of all the objects

[-off] : Turns off the LEDs on all components Examples: <CLI> locate -setobject -pool group1

<CLI> locate -setobject -drive 1:1

<CLI> locate -setobject -bbu 0

<CLI> locate -setobject -ctlr 1

<CLI> locate -setobject -encl 0

<CLI> locate -setobject -volume pool1:volume1

<CLI> locate -setobject -drive all

<CLI> locate -getobject -volume <CLI> locate -setobject -number 2

of that type.

The locate command lights up the LED on these objects:

v drive v pool v volume v controller v bbu v enclosure

If any of the objects are not supplied, this error returns: cannot find object, name is ambiguous

Use the -off option to turn off the LEDs on all objects.

Use the -getobject option to list all of a specified object. Specify the object by using either the identifier of that object or the sequence number in the list returned by the –getobject option.

Use the –drive option to specify the selected object as a drive and to locate a drive. If the selected object is a drive, the LED on that drive is lit up.

Use the -pool option to specify the selected object as a pool and to locate a pool by its name. If the selected object is a pool, the LEDs on all the drives making up that pool are lit up.

Use the -volume option to specify the selected object as a volume and to locate drives that belong to a volume by its name. If the selected object is a volume, the LEDs on all the drives making up that volume are lit up.

Use –bbu, –controller, and –enclosure options to identify these objects by their number.

Use the -setobject option to turn on the LEDs of the drives indicated by the objects. You can issue the –setobject option with the -number option to clear a

Chapter 8. Using the RAID Controller command line interface 69

local list of objects. If you issue the –setobject option with the -number option while the list is empty, an error generates.

Use the -number option only after you have issued the –getobject option, which builds a local list of objects.

Command arguments:

-bbu [0|1] | -tray traylocation | -enclosure [0|1|2] | -number object] ]

Where:

v [E:T|all] - Locates a specific drive by name when issued with –drive E:T.

Locates all drives when issued with –drive all.

v poolname - Locates a pool by its name when issued with -pool poolname. v pool:volume - Locates drives belonging to a volume by its name when issued

with -volume pool:volume.

v [0|1] - Locates a controller and Battery Backup Unit by their number. v [0|1|2] - Locates a enclosure by its number. v object - Allows selection of the number displayed in the list output.

Examples:

<CLI> locate –off <CLI> locate –getobject –volume

vol# VolumeName Cap RaidType Status

0 pool1:vol1 4GB 0 Viable

1 pool1:vol2 2GB 0 Viable

<CLI> locate –setobject –pool group1 <CLI> locate –setobject –drive 0:6 <CLI> locate –setobject –bbu 0 <CLI> locate –setobject –ctlr 1 <CLI> locate –setobject –enclosure 0 <CLI> locate –setobject –volume pool1:volume1 <CLI> locate –setobject –drive all

<CLI> locate –getobject –volume

Vol# VolName# GrpName# Capacity# HostLUN# Host-WWN 0 testVol0 Grp1 1024 0 23abcd 1 testVol1 Grp2 3590 0 abdef3

<CLI> locate –setobject –number 2

70 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

list features

Use this command to display currently enabled feature fields.

Command arguments:

<CLI> list features

Example:

<CLI> list features Current Machine Local Time: 08/26/2008 03:25:34 PM

____________________________________________________ | S.No | Features | Availability | |______|_________________________|___________________| | 0| Base Features | Enabled | | 1| Bound Mode | Enabled | | 2| Volume Copy | Disabled | | 3| Snapshot Copy | Disabled | | 4| Max Drives Supported | 12 | | 5| Max Hosts Supported | 6 | |______|_________________________|___________________|

mountpolicy

Use this command to set and display the mount policy.

Command arguments:

<CLI> mountpolicy –[get | set [-automount [on|off]]]

Where:

v -get displays the current mount policy v -set sets a new mount policy. -automount is required with the -set parameter.

Example:

<CLI> mountpolicy –get

<CLI> mountpolicy –set –automount on

mountstate

Use this command to query the mount states of drives, pools, batteries, media trays, and enclosures (Disk Storage Modules) in the system.

Command arguments:

-setobject -[mount [-drive <<E:T><E:T> ...> | -bbu [0|1] | -mediatray 0 |

-enclosure <<num><num> ...>]|dismount [-drive <<E:T> <E:T> ...> |

-pool <<poolname> <poolname> ...> | -bbu [0|1] | -mediatray 0 |

-enclosure <<num> <num> ...> [-okdegradded]]] ]

Where:

v -getobject queries the mount state of the selected object v -setobject set the mount state of the selected object

The mount or dismount state of a component tells you if that component is available or unavailable. When querying a system component, some -get options are available but it is important to keep note of the following:

Chapter 8. Using the RAID Controller command line interface 71

v When pool is the selected object, you can set the –oknonviable option while

mounting a nonviable pool.

v If the –reportonly option is specified while dismounting an enclosure, only the

affected LUNs are reported without actually dismounting the enclosures.

v If you do not specify the –okdegraded option while dismounting an enclosure

that might result in degraded groups, the command will fail.

Examples:

<CLI> mountstate -getobject -drive

_____________________________________________ | Drive# | E:T | State | |________|____________|_______________________| | 0| 1:4| Online| | 1| 2:3| Online| | 2| 1:6| Online| | 3| 1:2| Online| | 4| 1:1| Online| | 5| 2:6| Online| | 6| 2:2| Online| | 7| 2:4| Online| | 8| 1:3| Online| | 9| 2:5| Online| | 10| 2:1| Online| |________|____________|_______________________|

<CLI> mountstate -getobject -mediatray No trays reported

<CLI> mountstate -getobject -enclosure

_____________________________________ | Enclosure# | State | |_____________|_______________________| | 0| Online| | 1| Online| | 2| Online| |_____________|_______________________|

<CLI> mountstate -getobject -bbu

_____________________________________ | CtlrId# | Battery State | |_____________|_______________________| | Ctlr 0| Service| | Ctlr 1| Service| |_____________|_______________________|

<CLI> mountstate -setobject -dismount -drive 1:1

<CLI> mountstate -setobject -mount -drive 1:1

Note: If a pool has been dismounted, is offline, or in service mode, mounting one or more of the drives will not restore the pool. A dual controller reboot is required to bring the pool back online.

<CLI> mountstate -setobject -dismount -pool my_pool

72 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

Note: Once a pool is dismounted, the pool can not be mounted using the

mountstate -setobject command. A dual controller reboot is required to bring the pool back online.

<CLI> mountstate -setobject -dismount -bbu 1

<CLI> mountstate -setobject -mount -bbu 1

<CLI> mountstate -setobject -dismount -mediatray 0

<CLI> mountstate -setobject -mount -mediatray 0

<CLI> mountstate -setobject -dismount -enclosure 2

Note: If dismounting an enclosure causes a pool to become degraded, this command will fail, unless the -okdegraded option is also provided.

<CLI> mountstate -setobject -mount -enclosure 2

Note: If a pool is completely contained in the enclosure, all drives of the pool are located in the enclosure to be mounted. The pool will not be automatically mounted. A system reboot, both controllers rebooted at the same time, is required to bring the pool online.

post result

The post result command shows the result of post.

Command arguments:

<CLI> post result

Example:

<CLI> post result All tests passed for ctlr 0. All tests passed for ctlr 1.

service mode

The service mode command displays the cause and recovery information when a RAID controller is in service mode.

Some situations and system conditions require you to place the RAID Controller in an offline condition to facilitate a system repair or preserve customer data integrity. You can use the RAID Controller command line interface to put the RAID Controller in a state associated with an offline condition, but remaining active on a level that allows you to continue an interaction. This state is known as service mode. A service mode shutdown initiates the orderly shutdown sequence but does not execute the power off phase.

The service mode command transitions a controller to service mode when various conditions listed in the following table occur. The controller returns to normal mode after a system administrator or service technician issues one of the controller actions.

Chapter 8. Using the RAID Controller command line interface 73

Table 7. Service mode conditions

Reason Description Controller action

SES_FAILURE Controller is unable to

communicate with SES device

BMC_FAILURE Controller is unable to

communicate with BMC device

VPD_NOACCESS Controller is unable to

access VPD data

HW_FAILURE Unrecoverable hardware

error

HW_RECURRING_FAILURE Recoverable hardware

error has caused multiple reboots

SW_RECURRING_FAILURE Firmware detected error

has caused multiple reboots

FORCED_NON_SURVIVOR Failover condition

occurred and other controller was better qualified to become survivor.

DRV_MSMTCH_RB Rebinder does not see the

same drives as survivor.

DRV_MSMTCH_ST On boot up (warm or

cold) both controllers discover a different set of drives and neither controller's discovered drives is a superset of the other's.

SES_ERRS The controller detected

environmental conditions unsuitable for normal operation.

INDETERMINATE_DATA_LOSS Controller is unable to

proceed with out loosing data - PROCEED AT OWN RISK

BATTERY_LOW, BATTERY_FAILED

If "Writeback mode without battery" is false, enter service mode, else report error in log and continue normally

Service Mode - Reboot or Replace

Service Mode - Reboot or Replace Error log shows controller, drive, and SES data on which basis a survivor was chosen. (Includes mirror path down, tie breaker cases, host port down, etc.)

Service Mode - Reboot or Replace

Service Mode - Reboot or Replace (Note that both controllers will be in service mode.)

Service Mode - Reboot after environmentals return to normal

Service Mode - Reboot, Replace, or Force boot with data loss

Service Mode - Reboot when battery OK

Command arguments:

<CLI> service mode –getreason Reason details : string Recovery Hints : string

74 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

Where:

v -getreason lists any appropriate recovery options.

Example:

<CLI> service mode –getreason Current Machine Local Time: 08/26/2008 03:35:15 PM

The reason for service mode is “DRV_MISMATCH_RB”. Reason details : “Rebinder does not see the same drives as survivor.” Recovery Hints : “Reboot or Replace the controller”

shellscript

The shellscript command runs a shell script in the RAID controller.

Command arguments:

<CLI> shellscript –file name [-param “ANYSTRING”]

Where:

v -file is a required parameter that specifies the file to be run. v -param is an optional parameter that is passed to the shell script. ANYSTRING must

be enclosed in quotation marks, and can contain any printable characters. If the

-param option is not specified, RAID Controller CLI passes a null string as a parameter to the shell script.

Example:

<cli> shellscript –file somefile.ext

show raid levels

The show raid levels command displays the list of currently supported raid levels in the system.

Command arguments:

<CLI> show raid levels

Example:

<CLI> show raid levels Following Raid Levels are supported by the system: RAID 0 RAID 5 RAID 1 RAID 10

Chapter 8. Using the RAID Controller command line interface 75

shutdown

The shutdown command changes the operational state of one or both RAID Controllers.

You can specify these RAID Controller states:

Servicemode

Reboot

Online

This command is used to shutdown RAID Controllers singularly or together. You can specify if the controllers being shutdown enter service mode during the shutdown process.

Note: If the controller to which you have your RAID Controller command line interface session connected is shut down, the CLI session ends. However, if only one controller is selected for servicemode, an optional switch –ensuresurvivor can be issued to ensure that the process does not result in non-availability.

With the servicemode option, –ensuresurvivor and -readytoremove options have to be selected together. -readytoremove option illuminates the service LED. A controller in service mode can be brought online by issuing this command with –state online option to the active controller.

A mode where all processes except command processes are stopped.

A mode where all processes are stopped and then started again.

A mode where all processes are active.

Command arguments:

<CLI> shutdown [–[ctlr 0| ctlr 1 ]–state [servicemode [-readytoremove] [-ensuresurvivor]

| reboot | online]] | [-system –state [servicemode |reboot]]

Where:

v [servicemode|reboot|online] - Allows selection of the state of the controller.

Example of the shutdown command with the -help option:

<CLI> shutdown -help

COMMAND-HELP: shutdown Usage : shutdown -ctlr [0|1] -state [servicemode [-readytoremove -ensuresurvivor]|

This command is used to shutdown either or both the controllers. The user can specify whether the controllers being shutdown enter service mode or shut off their power. If only one controller is selected for servicemode, an optional switch ’ensuresurvivor’ can be passed to ensure that it will not result in non-availability. With the servicemode option, ensuresurvivor and readytoremove options have to be selected together. The ’readytoremove’ option enables the service LED to be turned on. A powered off controller can be powered on by issuing this command with ’-state online’ option to the active controller. If the controller to which this CLI session is connected to is being requested to be powered off,the user will lose the CLI session.

reboot |online ] | -system -state [servicemode |reboot]

76 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

swversion

The swversion command retrieves and displays the software version.

Command arguments:

<CLI> swversion

Example:

<CLI> swversion Current Machine Local Time: 11/27/2009 11:27:09 PM

Software version : H-2.0.2.6 UBoot version : H-1.1.4.5 OS version : H-2.4.20.11 SES version : 0105 BMC version : S0BT07c 011A 06/30/2009 FPGA version : 01.06 CPLD version : S0CP00A C00A 01/01/2000 SAS switch version : S0SW01D R105 6/8/2009 BBU FirmwareRev : 53.0 Package Build No : 1.2.0.041

time

The time command sets and returns the date and time. It is issued by the system administrator for timestamps in the system, such as logs, alerts, volume creation time, and flashcopy name suffixes. The Linux operating system time is set in the factory and cannot be changed. This factory set Linux time is used for various purposes, such as scheduling tasks and monitoring. A delta is stored from the Linux time in the local flash to remember the changed time.

Command arguments:

<CLI> time –[get | set –date mm/dd/yyyy –time hh:mm:ss -[am|pm] ]

Where:

v mm - Displays the month. v dd - Displays the day. v yyyy - Displays the year. v hh - Displays the hour. v mm - Displays the minutes. v ss - Displays the seconds.

Examples:

<CLI> time –set –date mm/dd/yyyy –time hh:mm:ss –am|pm Time set to mm/dd/yyyy hh:mm:ss am

<CLI> time –get Current time is mm/dd/yyyy hh:mm:ss am

Chapter 8. Using the RAID Controller command line interface 77

validate key

The validate key command sets or displays the license key in the system.

Command arguments:

<CLI> validate key [-get | -set <192_bit_key>]

Where:

v -get - Displays the current license key. v -set - Sets a new 192–bit license key.

Example setting the key:

<cli> validate key -set 3a288d5ec2cef28c61510c11f6c64a69afae7e678f6c216f Current Machine Local Time: 08/26/2008 03:24:43 PM

License Key 3a288d5ec2cef28c61510c11f6c64a69afae7e678f6c216f has been set successfully

Example getting the current key:

<cli> validate key –get Current Machine Local Time: 08/26/2008 03:24:43 PM

License Key : 3a288d5ec2cef28c61510c11f6c64a69afae7e678f6c216f

Volume management commands

Use the RAID Controller command line interface for the RAID controller to perform administrative tasks for the device. This topic details the commands you can use to manage your storage volumes.

add mirror

Use this command to add a mirror to an existing drive pool. Mirrors can only be added to a RAID 0 pool. Drives must be added in pairs and must not have a smaller capacity than the existing drives in the RAID 0 pool.

Important: This command requires you to end all application I/O processes and shut down any active Blade servers in accordance with the recommended non-concurrent practices. The add mirror command must complete before you resume any application I/O processes. Depending on the size of the drives, add mirror may take several hours to complete. If one of the Blade servers being shut down is used as the RAID controller management node and has logical unit numbers (LUNs) mapped to it, you must use an external Blade server to manage the RAID subsystem.

Command arguments:

<CLI> add mirror -pool [POOL_NAME] -drives [ENCLOSURE]:[TRAY][ENCLOSURE]:[TRAY]..

Where:

v [POOL_NAME] - Specifies the name of the drive pool. v [ENCLOSURE]:[TRAY] - Specifies the drive bay number by enclosure number and

tray number.

Example:

<CLI> add mirror -pool Grp1 -drives 1:1 1:3

78 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

assimilate drive

Use this command with foreign drives, which are drives that were written on another system using the controller software or a system using another vendor’s software. By running this command with the -set option, you can record the information pertinent to this controller in the drive region reserved for metadata.

Important: This command produces a destructive procedure causing complete data loss. Use this command only if your intention is to irrevocably erase all disk data.

Command arguments:

<CLI> assimilate drive Please select one of the options: [-get |-set [-slot|-number]]

Where:

v E:T - Specifies the drive bay number by enclosure number and tray number. v number - Specifies the drive bay number by the sequence number that appears

on list displayed when command is run with -get option.

When you run this command with the -get option, a list of all foreign drives is displayed.

Example:

<CLI> assimilate drive –get

Drive# E:T SerialNo Cap Pool Usage State Ct10 Ct11 RPM

0 2:3 J3YWKGSJ 33GB D1 CLS OK 1 1 0

When you run the assimilate drive command with the -set option, the drive is assimilated and becomes available. Specify the drive by bay position or number. When you specify the drive by a number, that number refers to the sequence number that appears on the list displayed on running this command with the -get option. Run this command with the -get option just before running it with the

-set option to make an internal reference list. An error message is displayed if you run the assimilate drive command with the -set option without first running it with the -get option. The list is cleared after you run the command with the -set option.

Example:

<CLI> assimilate drive –set –slot 2 Drive in Enclosure 2 has been assimilated.

<CLI> assimilate drive –get

Drive# Enclosure SerialNo Cap Pool Usage State Ct10 Ct11 RPM

0 2 J3YWKGSJ 33GB D1 CLS OK 1 1 0

<CLI> assimilate drive –set –number 0 Drive is Enclosure 2.

Chapter 8. Using the RAID Controller command line interface 79

copyback

Use this command to copy the data from the source drive to the destination drive. This command can be used to drain a drive or to copy the data from the spare drive to the replaced drive.

Note: For any pool, only one copyback operation is active at a time. A new copyback request will be rejected if a copyback operation is already running in the group.

Command arguments:

<CLI> copyback copyback -source<E:T>-dest<E:T>[-convert]

Where:

v E:T - [Enclosure]:[Tray] Specifies the drive bay number by enclosure number and

tray number.

v -source - Specifies the source drive where the data being copied from. v -dest - Specifies the destination drive where the data being copied to. v -convert - Specifies the conversion of the source drive to a global spare when

the copyback operation finished.

Example:

<CLI> copyback –source 2:6 –dest 1:1 Source drive 2:6 Destination drive 1:1

Copyback operation started successfully.

create pool

This command creates a drive pool using drives specified by their bay numbers. The -help option provides more details regarding proper configuration of drives in particular RAID levels.

Example of the create pool command with the -help option

<CLI> create pool -help

COMMAND-HELP: create pool

This command is used to create drive groups. Usage : create pool -drives [DRIVE][DRIVE].. -raidtype [RAID_LEVEL] -port [PORT]

-name [POOL_NAME] DRIVE : [ENCLOSURE]:[TRAY] format for one drive.

RAID_LEVEL : Possible RAID_LEVEL values are ’0’,’1’,’5’,’10’.

0 - RAID 0, 1 - RAID 1, 5 - RAID 5, 10 - RAID 10 RAID 5 - For RAID 5 configuration, specify at least 3 drives RAID 10 - For RAID 1+0 configuration, the number of drives specified should

be a multiple of 2

RAID 1 - For RAID 1 configuration, the number of drives specified should

be 2 PORT : Port value can be either ’0’ or ’1’. POOL_NAME : Pass a unique name for this Drive Pool

Pool name is maximum of 12 characters and contains only alphanumeric and underscores.

80 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

Where:

v [ENCLOSURE]:[TRAY] - Specifies the drive bay number by enclosure number and

tray number.

v [0|1|10|5] - Allows selection of raid type. v [0|1] - Allows selection of port. v [POOL_NAME] - Defines the name of the pool.

A drive pool is a defined set of drives. Each volume that is exposed to host systems is completely contained within a drive pool. It is important to note that a drive can only be a member of one drive pool.

This command creates a pool using drives specified by their bay numbers. You can specify the -raidtype and the owner controller bay number. The pool name can be a maximum of 12 characters long and can contain alphanumeric and underscores. Make the pool name unique across the system.

Example:

<CLI> create pool –drives 1:4 1:1 1:3 –raidtype 10 –port 0 –name Group10 Drive Group created with total capacity of 46 GB.

create volume

This command creates a volume of a specified size on a particular pool.

Command arguments:

<CLI> create volume –name poolname:volumename –size number [%|MB|GB] –seqpostreadcmdsize size –seqreadaheadmargin margin

Where:

v poolname:volumename - Specifies pool name and volume name. Volume name can

be up to 12 characters long and contain alphanumeric and underscores; it must be unique across pool on which it is created.

v number - Number indicating size of the pool. v [%|MB|GB] - Allows you to specify size in percentage of total pool capacity, MB,

or GB.

v size - Specifies maximum sector count of a single predictive read ahead. v margin - Indicates number of sectors in the read ahead buffer.

create volume -help

<CLI> create volume

Too many/few parameters for -name option

COMMAND-HELP: create volume

This command is used to create a volume. Usage : create volume -name [POOLNAME]:[VOLUMENAME] -size [SIZE][UNIT]

POOLNAME : Pool’s name on which the volume is going to be created VOLUMENAME : Volume’s name to create. It has to be associated with poolname as a pool:volume

SIZE : Size may be passed in different units.

[-seqpostreadcmdsize [READCMDSIZE] -seqreadaheadmargin [MARGIN] ]

pair. Volume name is maximum of 12 characters and contains only alphanumeric and underscores.

If % is used, then SIZE value should not be more than ’100%’ .

Chapter 8. Using the RAID Controller command line interface 81

If MB or GB is used, then it should not be more than available size of Drive Group. e.g. if available size of Drive Group(DRIVEGRPNAME) is 2346MB it should be less than or equal to ’2346MB’ or ’2GB’. The SIZE specified should be whole numbers

UNIT : Unit of the size can be GB or MB or % READCMDSIZE : Sequential Post Read Command Size is the maximum sector count of a single

MARGIN : Read Ahead Margin is the number of sectors in the read ahead buffer. This parameter

i.e. 236.54MB is not a valid number.

predictive read ahead. A value of 0 disables predictive read for this volume. A value of 1-128 will override the previous setting and represents a command transfer size that is a multiple of 16Kbytes. A value of (0xFFFF) will cause the default value to be used.

is ignored if the Sequential Post Read Command Size is zero. The valid range is 1 to 0x7FFF. A value of (0xFFFF) results in the default value being used.

In other words, specify size in MB, GB or percentage of the total pool capacity. Specify the name as poolname:volumename. The volume name can be a maximum of 12 characters long and can contain alphanumeric and underscores. Make the volume name unique across the pool on which it is being created. The maximum sector count of a single predictive read ahead is seqpostreadcmdsize. A value of 0 disables predictive read for this volume. A value of 1-128 overrides the previous setting and represents a command transfer size that is a multiple of 16Kb. A value of (0xFFFF) causes the default value to be used. The number of sectors in the read ahead buffer is seqreadaheadmargin. This parameter is ignored if the seqpostreadcmdsize is zero. The valid range is 1 to 0x7FFF. A value of (0xFFFF) results in the default value.

Example:

<CLI> create volume –name Grp1:volume1 –size 10 % Volume 'volume1' created on pool 'Grp1' with capacity 15 GB.

delete pool

This command deletes a drive pool.

Command arguments:

<CLI> delete pool –name poolName

Where:

v poolName - Specifies name of pool to be deleted.

When you issue this command, the following warning is appears:

Example:

<CLI> delete pool –name Group0

All volumes in this Pool and hostluns mapped to them will be unavailable (deleted). The data for these volumes will be deleted. Do you want to continue? Type L to delete or any other key to cancel. L Pool Group0 has been deleted.

An error message is displayed if the target pool is not found.

Example:

<CLI> delete pool –name Group0 No such drive pool Please re-execute the command with valid pool name available

82 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

delete volume

This command deletes a master volume.

Command arguments:

<CLI> delete volume –name poolname:volumename

Where:

v poolname:volumename - Specifies pool name and volume name. Volume name can

be up to 12 characters long and contain alphanumeric and underscores; it must be unique across the pool on which it is created.

When you issue the delete volume command, the following warning appears:

Example:

<CLI> delete volume -name raid1:vol88 All hostluns mapped to this volume will be unavailable (deleted). The data for this volumes will be deleted. Do you want to continue? Type ’L’ to delete or any other key to cancel. L Volume vol88 on pool raid1 has been deleted

global spare

Use this command to manage global spares. Global spares are drives that can be used to rebuild a degraded pool that has no local spares.

Command arguments:

<CLI> global spare –[add -slot E:T | get | delete –[slot E:T |number number]]

Where:

v E:T - Specifies the drive bay number by enclosure number and drive position. v number - Specifies the drive bay number by the sequence number that appears

on list displayed when command is run with -get option.

You can use a drive from the global spares to rebuild a degraded pool that has no local spares, but can only add global spares to the global spare pool if their state is unassigned. Run the list drive command defined earlier to obtain a list of unassigned drives. If a drive being deleted from the global spare pool has already been chosen for a rebuild, it will produce and error.

Running the global spare command with the -get option returns a list of all the global spares in the system.

Example:

<CLI> global spare –get

Drive# Slot SerialNo Cap Pool Usage State Ct10 Ct11 RPM

1 1:5 3LM269P3 279GB -- GLS online 1 1 0

Running this command with the -add option adds a global spare.

Example:

<CLI> global spare –add –slot 1:5 Global spare added

Chapter 8. Using the RAID Controller command line interface 83

host

Running the global spare command with the -delete option deletes a global spare. Specify the drive by bay position or number. When you specify the drive by a number, that number refers to the sequence number that appears on the list displayed on running this command with the -get option. Run this command with the -get option just before running it with the -delete number option to make an internal reference list. An error message is displayed if you run the global spare command with the -delete option without first running it with the -get option.

Example:

<CLI> global spare –delete –slot 1 Global spare deleted from Controller Enclosure 1.

<CLI> global spare –get

Drive# Enclosure SerialNo Cap Pool Usage State Ct10 Ct11 RPM

0 2 J3YWKGSJ 33GB -- GLS OK 1 1 0 1 1 J3YXDVJJ 33GB -- GLS OK 1 1 0 2 1 JBV1HE7J 33GB -- GLS OK 1 1 0

<CLI> global spare –delete –number 2 Global spare deleted from Controller Enclosure 1.

Use this command to add a host World Wide Name (WWN) to the controller list of hosts or to get the list of hosts added to the controller .

Command arguments:

<CLI>host –[add WWN| get]

Where:

v WWN - Specifies host WWN to add to controller list of hosts or host WWN for

which logical unit numbers (LUNs) will be mapped.

Examples:

<CLI> host –add 1234567890abcdef Host added with WWN 1234567890abcdef.

<CLI> host –get HostWWN 784875485454 : LUNs Mapped

LUN Permission Volume

3 ACCESS_READWRITE pool1:vol1

HostWWN 123456789abcdef0 : No LUNs Mapped HostWWN 123456789abcdef1 : No LUNs Mapped

84 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

hostlun

Use this command to map or unmap a volume to a host using the specified LUN number or to get a list of all host LUNs.

Important: When using this command with the -unmap argument to unmap a volume to a host, the command requires you to end all application I/O processes on the LUN that is being unmapped and to shut down any active Blade servers in accordance with the recommended non-concurrent practices.

Command arguments:

<CLI> hostlun –[get –wwn WWN | map –volume poolname:volumeName –permission [ro/rw] –wwn WWN –lun number | unmap –wwn WWN –lun number] CLI> host Please select one of the below options Usage : [ -add | -delete |-get ]

COMMAND-HELP: host Usage : host -[get |delete WWN | add WWN] This command is used to add/delete a host WWN to/from the controller list of hosts or get the list of hosts added to the controller. WWN : The WWN name of the host (16 hexadecimal digits).

Where:

v WWN - Specifies host World Wide Name for which LUNs will be mapped or

unmapped.

v poolname:volumeName - Specifies pool name and volume name. Volume name can

be up to 12 characters long and contain alphanumeric and underscores; it must be unique across pool on which it is created.

v [ro/rw] - Specifies whether permission is read only or read-write. v number - Specifies LUN number to be mapped or unmapped.

Running the hostlun command with the -map option maps any volume to any host using the specified LUN number. This command adds the host if it has not already been added. It returns an error message if the specified volume is already mapped to the specified host.

Example:

<CLI> hostlun –map -volume Grp1:vol1 –permission RW –wwn 500062b00008ace9 –lun 6 Host Lun 6 for host 500062b00008ace9 mapped to volume 'vol1' in pool 'Grp1'.

Running this command with the -get option returns a list of all host LUNs.

Example:

<CLI> hostlun -get -wwn 500062b00008ace9

HostWWN 500062b00008ace9 : LUNs Mapped

___________________________________________________________ | LUN | Permission | Volume | |_________|_____________________|___________________________| | 2| ACCESS_READWRITE| raid1_1:vol01| | 3| ACCESS_READWRITE| raid1_1:vol02| | 0| ACCESS_READWRITE| raid0_0:vol01| | 1| ACCESS_READWRITE| raid0_0:vol02| | 6| ACCESS_READWRITE| raid10_1:vol01| | 7| ACCESS_READWRITE| raid10_1:vol02|

Chapter 8. Using the RAID Controller command line interface 85

| 4| ACCESS_READWRITE| raid5_0:vol01| | 5| ACCESS_READWRITE| raid5_0:vol02| |_________|_____________________|___________________________|

Running this command with the -unmap option unmaps the host LUN from a volume.

Example:

<CLI> hostlun –unmap –wwn 500062b00008ace9 –lun 4 Lun 4 for host 500062b00008ace9 unmapped.

Volume services commands

Use the SAS Switch command line interface for the RAID controller to perform administrative tasks for the device. This topic details commands related to volume services.

add capacity

The add capacity command expands the capacity of a drive pool by adding a new unassigned drive or drives to the pool. The number of drives you add to the pool is dependant on the RAID level configured on your system. For RAID levels 1 and 10, you add two drives to the pool at a time. If you are operating a RAID level of 0 or 5, you add one at a time. If the capacity of the new drive is less than the capacity of the smallest drive in the pool, the system generates an error. However, if the capacity of the new drive is more than the capacity of the smallest drive in the pool, the system generates a warning.

Command arguments:

<CLI> add capacity –pool name –drivelist <[ENCLOSURE]:[TRAY]> <[ENCLOSURE]:[TRAY]> .. <[ENCLOSURE]:[TRAY]>

Where:

v name - Defines the pool name. v [ENCLOSURE]:[TRAY] - Specifies the drive bay number by enclosure number and

drive position (tray) number. You can add one or more drives to the pool.

Example:

<CLI> add capacity –pool Group0 –drivelist 1:3 Capacity added successfully

86 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

datascrub

The datascrub command views or sets the datascrub policy.

The -auto flag specifies whether background scrub should be enabled. If a problem is found, the policy to fix it or create bad blocks is defined in the flash configuration file.

Command arguments:

<CLI> datascrub –[get | set –auto [on|off]

Where:

v [on|off] - Enables or disables data scrubbing.

Example:

<CLI> datascrub -get Data Scrub Policy is off

delete all

Important: This command produces a destructive procedure causing complete data loss. Use this command only if your intention is to irrevocably erase all disk data. The delete all command deletes all pools, volumes, and host LUNs in a bound controller system. Use this command to delete an existing configuration before loading a new configuration manually or from a configuration script.

Command arguments:

<CLI> delete all

Example:

<CLI> delete all All volumes in the system and hostluns mapped to them will be unavailable (deleted). The data for these volumes will be deleted. Do you want to continue? Type 'L’ to delete or any other key to cancel. L Started deleting all... Delete All Successful

expand -volume

Use the expand -volume command to expand the capacity of a volume. The new capacity of a volume is equal to the added capacity increment plus the old volume. The incremental capacity can be defined in MB, GB or the percentage (%) of the total remaining drive pool capacity.

Note: If the remaining capacity on the pool is less than the requested expansion, an error occurs.

Command arguments:

<CLI> expand -volume poolname:volumename -add capacityIncrement [MB|GB|%]

Where:

v poolname:volumename - Allows selection of the volume name as a combination of

poolname and volumename.

v capacityIncrement - Specifies the number for the incremental capacity.

Chapter 8. Using the RAID Controller command line interface 87

v [MB|GB|%] - Defines incremental capacity in MB, GB, or as % of total remaining

Example:

<CLI> expand –volume Grp1:vol1 –add 10% Volume 'vol1’ on pool 'Grp1’ has been expanded. The new capacity is 34 GB.

initialize

The initialize command performs a task that overwrites and formats the metadata area on the drive before removing the drive from the system.

Important: This command produces a destructive procedure causing complete data loss. Use this command only if your intention is to irrevocably erase all disk data.

Command arguments:

<CLI> initialize –drive slotnumber

Where:

v slotnumber - Specifies the drive bay by enclosure number.

Example:

<CLI> initialize –drive 1:3

drive pool capacity.

list killedpaths

The list killedpaths command displays the killed drive paths information from the persistent memory. If both paths to a drive are killed, the drive will not show up in the list drive response.

Command arguments:

<CLI> list killedpaths [-ctlr [0|1]]

Where:

v -ctlr specifies the path to act on. The default is both the ctlr 0and ctlr 1

paths.

Example:

<cli> list killedpaths [-ctlr [0|1]] Current Machine Local Time: 08/26/2008 03:20:14 PM

_______________________________________________________________________________ | E:T:S | DriveDN | Word-Wide Node Name | Word-Wide Port Name | |_______________________________________________________________________________| | 1:2:0| 3:5000c5000a832023| 5000c5000a832021| 5000c5000a832021| | 1:4:0| 3:500000e0177202d0| 500000e0177202d2| 500000e0177202d2| | 1:3:0| 3:5000c5000a83b72f| 5000c5000a83b72d| 5000c5000a83b72d| | 1:2:0| 3:5000c5000a832023| 5000c5000a832022| 5000c5000a832022| | 1:4:0| 3:500000e0177202d0| 500000e0177202d3| 500000e0177202d3| | 1:3:0| 3:5000c5000a83b72f| 5000c5000a83b72e| 5000c5000a83b72e| |_________|_____________________|_______________________|_______________________|

88 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

synchronize volume

The synchronize volume command synchronizes a volume immediately to ensure that redundant information is valid. You can also use this command to perform a parity check on RAID 5 volumes and a mirror consistency check on mirrored volumes. Any errors found during the check are handled according to the defined datascrub policy found in the flash configuration file. The progress of datascrub is shown along with other volume services.

If the background datascrub is enabled (datascrub is disabled by default) and running when you issue synchronize volume, the background task enters into a suspended state. After synchronize volume finishes, the background task automatically resumes. The status of synchronize volume reports, but the status of the background task does not report.

Command arguments:

<CLI> synchronize volume [–name pool[:volume]]

Where:

v pool[:volume] - Defines the pool name, the volume name, or the pool name and

volume name. If the pool name is not specified, all the volumes in the system will be

synchronized. If the pool name is specified and the volume name is not specified, all the volumes in that pool will be synchronized.

Example: none

view long running tasks

The view long running tasks command displays all of the long running tasks that have been initiated and their status. The following long running tasks can have their status displayed:

v Volume based tasks:

– initialize – synchronize volume

v System level tasks:

– synchronize volume

v Pool based tasks:

– synchronize volume – addmirror – addcapacity

Command arguments:

<CLI> view long running tasks

Example:

<CLI> view long running tasks

Status of long running tasks:

Volume based tasks: Pool name Volume name Task name % complete Status

Group0 vol1 migrate 80% running Grp1 volume12 init 50% running

Chapter 8. Using the RAID Controller command line interface 89

Grp1 Volume1 init 0% scheduled

Group based tasks: Pool name Task name % complete Status Tray

Grp2 Rebuild 30% running 1:2 Group34 AddMirror 24% running N/A

System tasks: Task name % complete Status

Synchronize volume 80% running

Using the command line to configure storage

The recommend methods of configuring storage are the Start Now Advisor and the IBM Storage Configuration Manager, but storage configuration can also be done using the RAID Controller command line interface.

Example of a RAID 5 configuration

About this task

The following shows an example the commands used to create a RAID 5 configuration.

Procedure

1. Before you begin, ensure that all of your drives are in an unassigned and

online state.

2. Run the list drive command

list drive

3. Issue the commands to create your pools and a global spare (GLS)

create pool -drives 1:1 1:2 1:3 -raidtype 5 -port 0 -name A1R5 create pool -drives 2:1 2:2 2:3 2:4 2:5 -raidtype 5 -port 1 -name A2R5 global spare -add -slot 2:6

4. Verify pools and global spare

list pool list drive

5. Create your volumes

create volume -name A1R5:V1 -size 1GB create volume -name A1R5:V2 -size 1GB. create volume -name A2R5:V1 -size 4GB create volume -name A2R5:V2 -size 4GB

6. Verify your volumes

list volume

7. Map the volumes to hosts

hostlun -map -volume A1R5:V1 -permission rw -wwn 500062B000030D4C -lun 0 hostlun -map -volume A1R5:V1 -permission rw -wwn 500062B000030D4D -lun 0 hostlun -map -volume A1R5:V2 -permission rw -wwn 500062B000030D4C -lun 1 hostlun -map -volume A1R5:V2 -permission rw -wwn 500062B000030D4D -lun 1

hostlun -map -volume A2R5:V1 -permission rw -wwn 500062B00007E0D0 -lun 0 hostlun -map -volume A2R5:V1 -permission rw -wwn 500062B00007E0D1 -lun 0 hostlun -map -volume A2R5:V2 -permission rw -wwn 500062B00007E0D0 -lun 1 hostlun -map -volume A2R5:V2 -permission rw -wwn 500062B00007E0D1 -lun 1

8. Verify host mapping

90 IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module

IBM BladeCenter S SAS RAID Controller Module Installation And User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

Tables

Chapter 1. Introduction

Product description and package contents

System requirements

Interface choices and functions

Workflow notes

Documentation notes

Preinstallation safety information

Handling static-sensitive devices

Hardware features and specifications

Component illustrations

Logical identifiers and physical location codes

Option package contents

Related documentation

Chapter 2. Prerequisite hardware

Understanding Battery Backup Units

Quick facts about Battery Backup Units

Installing the Battery Backup Unit

Removing the Battery Backup Unit hardware

Chapter 3. Understanding the Telnet interface

Establishing a Telnet session to RAID Controller

Chapter 4. Installing the IBM BladeCenter S SAS RAID Controller Module

Installation and setup

The IBM BladeCenter Start Now Advisor method

The Advanced Management Module method

Installing IBM Storage Configuration Manager

User ID and password requirements

Resetting the passwords on an SAS RAID Module

Configuring storage through the CLI

Upgrading from a single to a dual controller configuration

Chapter 5. Disconnecting power to the BladeCenter unit

Chapter 6. Updating firmware

Subscribing to notifications

Installing and configuring firmware updates

Chapter 7. Working with storage pools and volumes

Understanding storage pools

Understanding volumes

Understanding RAID levels

Understanding the predefined storage configuration

Configuring volumes for use with VMware

Configuring blades for Microsoft Cluster Service

Chapter 8. Using the RAID Controller command line interface

Display commands

detail controller

detail drive

detail pool

detail volume

detail volume verbose

list controller

list drive

list pool

list volume

System control and configuration commands

alert

battery

cache settings

chpasswd

clilog

commparams

configure access

configure alert

configure pool

configure timeout

controller config

email alert

enclosure reporting

event log

locate

list features

mountpolicy

mountstate

post result

service mode

shellscript

show raid levels