IBM ServeRAID 4Lx Ultra160 Hardware Maintenance Manual

Download

ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers

Hardw are Maintenance M anual

򔻐򗗠򙳰

ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers

Hardw are Maintenance M anual

򔻐򗗠򙳰

Note

Before using this information and the product it supports, be sure to read “Notices” on page 160.

Third Edition (July 2002) The following paragraph does not apply to the United Kingdom or any country where such provisions are

inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM

may make

improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time. This publication was developed for products and services offered in the United States of America. IBM may not offer

the products, services, or features discussed in this document in other countries, and the information is subject to change without notice. Consult your local IBM representative for information on the products, services, and features available in your area.

Requests for technical information about IBM products should be made to your IBM reseller or IBM marketing representative.

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

About this manual

This manual contains diagnostic information, a Symptom-to-FRU index, service information, error codes, error messages, and configuration information for the IBM ServeRAID

Note: The IBM ServeRAID product can be either a controller on an adapter or a

Important: This manual is intended for trained servicers who are familiar with IBM

Important safety information

Be sure to read all caution and danger statements in this book before performing any of the instructions. See “Safety information” on page 127.

Leia todas as instruções de cuidado e perigo antes de executar qualquer operação.

™

-4x Ultra160 and ServeRAID-5i Ultra320 controllers.

controller on the system board of the server. For consistency in this manual, the ServeRAID product is referred to as a ServeRAID controller, unless it is specifically noted otherwise.

To install device drivers and utility programs for an IBM ServeRAID controller that comes as a standard feature on an IBM system board, see the installation instructions and CDs provided with the server for instructions.

server products.

Online support

Prenez connaissance de toutes les consignes de type Attention et Danger avant de procéder aux opérations décrites par les instructions.

Lesen Sie alle Sicherheitshinweise, bevor Sie eine Anweisung ausführen.

Accertarsi di leggere tutti gli avvisi di attenzione e di pericolo prima di effettuare qualsiasi operazione.

Lea atentamente todas las declaraciones de precaución y peligro ante de llevar a cabo cualquier operación.

You can download the most current diagnostic, BIOS flash, and device driver files from http://www.ibm.com/pc/support on the World Wide Web.

iv ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

About this manual .......................iii

Important safety information ....................iii

Online support .........................iv

General checkout ........................1

General information .......................3

Notices that are used in this book ..................3

IBM ServeRAID Support CD ....................3

ServeRAID ROM Update Wizard ..................3

Device drivers.........................4

ServeRAID Manager program ...................4

IPSSEND command-line program .................4

Diskette images ........................4

ServeRAID files needed to install Microsoft Cluster Server (MSCS) .....5

ServeRAID publications .....................5

Supported operating systems ....................6

Controller features ........................6

Connector locations .......................7

ServeRAID-4H controller .....................7

ServeRAID-4L controller .....................9

ServeRAID-4Lx controller ....................10

ServeRAID-4M controller ....................11

ServeRAID-4Mx controller ....................13

ServeRAID-5i controller .....................15

Installing and configuring ServeRAID controllers ...........17

Using a ServeRAID-4x controller in a server with Active PCI features .....17

Using Windows NT 4.0 with Active PCI features............17

Using Windows 2000 with Active PCI features ............18

Using NetWare with Active PCI features...............18

Installing the ServeRAID-4x controller ................18

Installing the ServeRAID-5i controller .................21

Preparing for installation ....................21

Installing the ServeRAID-5i controller ................22

Replacing the battery pack on the ServeRAID-5i Ultra320 controller ....24

Installing the ServeRAID-5i controller 2-U bracket ...........25

IBM Director support for the ServeRAID-5i controller ..........27

Connecting external devices to a ServeRAID-4 controller .........27

Configuring the ServeRAID controller.................28

Using ServeRAID Manager ...................29

Using Express configuration ..................30

Using Custom configuration ..................31

Fine-tuning your configuration ..................36

Changing the stripe-unit size ..................36

Write-cache mode ......................36

Viewing your configuration.....................36

Getting assistance .......................37

Using utility programs .....................41

Using the ServeRAID Mini-Configuration program ............41

Accessing the Mini-Configuration program ..............41

Viewing the controller status ...................41

Viewing the configuration ....................42

Using the advanced configuration functions .............42

Using the IPSSEND command-line program ..............43

Starting the IPSSEND command-line program ............43

Starting IPSSEND from Windows, NetWare, OS/2, Linux, OpenServer,

UnixWare, or Open UNIX ..................44

Starting IPSSEND from DOS..................44

Using the IPSSEND command-line program .............44

Server roll-out functions ...................45

Error-recovery functions ...................45

Problem-isolation and debug functions ..............46

RAID configuration functions ..................48

Using the IPSMON command-line program (NetWare only) ........50

IBM ServeRAID cluster solution ..................53

ServeRAID considerations.....................55

Hardware considerations ....................55

Controller considerations ....................55

Array or logical drive considerations ................55

Monitoring and updating an IBM ServeRAID cluster solution ......57

Checking the ownership of a physical drive ..............57

Adding logical drives to a cluster ..................58

Validating a cluster .......................59

Viewing merge-group numbers and other cluster information ........60

Maintenance and troubleshooting .................61

Obtaining ServeRAID updates ...................61

Updating BIOS and firmware code..................61

Upgrading a ServeRAID controller ..................62

Updating device drivers, BIOS and firmware code, and utility programs . . . 62

Replacing the old controller ...................63

Symptom-to-FRU index .....................65

Parts listing..........................67

Recovery procedures ......................69

IBM ServeRAID Support CD warning message while starting ........69

Recovering from problems starting the ServeRAID Manager ........69

Recovering from an incomplete format of a physical drive .........70

Channel troubleshooting procedures .................71

Dead channel service procedure ..................71

Drive replacement (rebuilding a defunct drive) .............73

Recovering from defunct drives ..................73

Rebuilding a hot-swap drive ...................74

Recovering from multiple physical drive failures (Windows only) .......75

Capturing the ServeRAID logs ..................76

Isolating and removing the failed physical drive ............76

Checking the hardware connections ................77

Setting defunct drives to the online state ..............77

Accessing the critical logical drives ................77

Finishing the procedure.....................78

Troubleshooting .......................78

Poor signal quality across the SCSI bus .............78

Isolating hardware problems ..................79

vi ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Locating the startup device (SCO OpenServer only) ...........80

Solving problems in a failover environment ..............80

Recovering from a failure in a failover environment ..........80

Replacing a controller of a failover pair in a non-hot-plug PCI slot ....80

Replacing a controller of a failover pair in a hot-plug PCI slot ......81

Recovering from a failed physical drive in a RAID level-5E environment . . . 82

Recovering from a power failure during a failover ...........82

Troubleshooting an IBM ServeRAID Cluster Solution ...........82

Recovering from a failed ServeRAID server .............82

Recovering from a failed ServeRAID controller ............83

Obtaining the current configuration information ...........84

Replacing a ServeRAID controller ................84

Recovering from a failover in a Microsoft Cluster Server server ......86

Recovering from a failed physical drive in a RAID level-5E environment . . . 86

Recovering from a failed server in a ServeRAID cluster .........86

Troubleshooting ServeRAID subsystems in a cluster environment .....86

Creating ServeRAID diskettes ...................89

Creating diskettes on Windows ..................90

Creating diskettes on IBM OS/2..................90

Creating diskettes on Linux or UNIX ................91

Error codes and procedures ...................93

ServeRAID startup (POST) messages ................93

POST (ISPR) error procedures ...................93

BCS and ECS register codes ...................95

Channel record table......................101

Reference information .....................103

Understanding RAID technology ..................103

Stripe-unit size .......................103

Selecting a RAID level and tuning performance ...........104

Supported RAID levels ....................104

Understanding RAID level-0..................105

Understanding RAID level-1..................106

Understanding RAID level-1 Enhanced .............107

Understanding RAID level-5..................108

Understanding RAID level-5 Enhanced..............110

Understanding RAID level-x0 .................112

Drive state descriptions ....................113

Physical drive state descriptions ................113

Logical drive state descriptions ................114

Device drivers .......................114

Miscellaneous programs ...................115

Using ServeRAID Controllers to avoid data loss ..........115

Drive failures .......................115

Drive protection features ...................116

Device Event Table .....................117

Acronyms, terms, and definitions ..................122

Related service information ...................127

Safety information .......................127

General safety .......................127

Electrical safety .......................128

Safety inspection guide ....................129

Handling electrostatic discharge-sensitive devices ..........130

Contents vii

Grounding requirements ....................131

Safety notices (multi-lingual translations) ..............131

Problem determination tips ....................160

Notices ...........................160

Trademarks..........................161

viii ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

General checkout

The following general checkout procedures are for the system boards containing integrated ServeRAID controllers.

Attention: The drives in the system you are servicing might have been rearranged or the drive startup sequence changed. Be extremely careful during write operations such as copying, saving, or formatting. Data or programs can be overwritten if you choose an incorrect drive.

Diagnostic error messages appear when a test program finds a problem with a hardware option. For the test programs to determine if a test Passed, Failed,or Aborted properly, the test programs check the error-return code at test completion.

General error messages appear if a problem or conflict is found by an application program, the operating system, or both. For an explanation of these messages, refer to the information supplied with that software package.

For systems that are part of a shared DASD cluster, run one test at a time in looped mode. Do not run all tests in looped mode, as this could enable the DASD diagnostic tests.

Note: A failed system might be part of a shared DASD cluster (two or more

systems sharing the same external storage device(s)). Prior to running diagnostics, verify that the failing system is not part of a shared DASD cluster.

A system might be part of a cluster if:

v The customer identifies the system as part of a cluster. v One or more external storage units are attached to the system and at least one

of the attached storage units is additionally attached to another system or unidentifiable source.

v One or more systems are located near the failing system.

If the failing system is suspected to be part of a shared DASD cluster, all diagnostic tests can be run except diagnostic tests that test either the storage unit (DASD residing in the storage unit), or the storage controller attached to the storage unit.

Notes:

1. Before replacing any FRUs, ensure the latest level of system BIOS is installed

on the system. Also, ensure that the latest level or customer-approved level of the ServeRAID controller BIOS and firmware are installed. Down-level BIOS or firmware might cause false errors and unnecessary replacement of the controller.

2. If multiple error codes are displayed, diagnose the first error code displayed.

3. If an installed device is not recognized by the diagnostics program, that device

might be defective.

The following steps list the general checkout procedures.

001 IS THE SYSTEM PART OF A CLUSTER?

YES: Schedule maintenance with the customer. Shut down all

systems related to the cluster. Run the hard disk test of the server diagnostics on the shared storage.

NO: Go to step 2.

002 DO THE FOLLOWING:

v Power-off the server and all external enclosures. v Check all cables and power cords. v Set all display controls to the middle position. v Power-on all external enclosures. v Boot the machine and watch for the ServeRAID controller BIOS

screen.

003 DID THE BIOS SCREEN APPEAR?

YES: Go to Step 4. NO: Try to download the ServeRAID Firmware and BIOS to the

controller and reboot. If unsuccessful, replace the ServeRAID controller. To download relevant files, see “Obtaining ServeRAID updates” on page 61.

004 NOTE THE STATUS OF THE SERVERAID POWER-ON

SELF-TEST (POST). DID THE POST INDICATE A PASSED STATUS?

YES: Go to Step 5. NO: Refer to the “Symptom-to-FRU index” on page 65.

005 NOTE THE DRIVE CONFIGURATION STATUS. DID THE DRIVE

CONFIGURATION STATUS INDICATE A PASSED STATUS? YES: Controller is OK. NO: Refer to the drive configuration conflict resolution procedures

for the controller in “BCS and ECS register codes” on page 95.

2 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

General information

This Hardware Maintenance Manual provides information for configuring an IBM ServeRAID controller and using the ServeRAID utility programs and the IBM ServeRAID Cluster Solution, and troubleshooting errors.

Note: The IBM ServeRAID product can be either a controller on an adapter, such

as the one in this option package, or a controller on the system board of your server. For consistency in this manual, the ServeRAID product is referred to as a ServeRAID controller, unless it is specifically noted otherwise.

Notices that are used in this book

This book contains the following notices designed to highlight key information:

v Notes: These notices provide important tips, guidance, or advice. v Important: These notices provide information or advice that might help you avoid

inconvenient or difficult situations.

v Attention: These notices indicate possible damage to programs, devices, or

data. An attention notice is placed just before the instruction or situation in which damage could occur.

v Caution: These statements indicate situations that can be potentially hazardous

to you. A caution statement is placed just before the description of a potentially hazardous procedure step or situation.

v Danger: These statements indicate situations that can be potentially lethal or

extremely hazardous to you. A danger statement is placed just before the description of a potentially lethal or extremely hazardous procedure step or situation.

IBM ServeRAID Support CD

The IBM ServeRAID Support CD is shipped with the controller and contains the following:

v ServeRAID ROM Update Wizard v Device drivers v ServeRAID Manager program v IPSSEND command-line program v Diskette images v ServeRAID files needed to install Microsoft v ServeRAID publications

ServeRAID support information is also available at http://www.ibm.com/pc/support/.

ServeRAID ROM Update Wizard

The IBM ServeRAID ROM (read-only memory) Update Wizard is a program designed to automatically identify and scan each ServeRAID controller installed in your server. If the BIOS and firmware code need updating, the wizard will give you the opportunity to do so.

Cluster Server (MSCS)

Device drivers

The device drivers are located in the following directory on the IBM ServeRAID Support CD:

e:/operatingsystem/DRIVER

where e is the CD-ROM drive and operatingsystem is the specific operating system used in the ServeRAID installation.

The device drivers are also located on the operating-system-specific IBM ServeRAID Support diskettes.

ServeRAID Manager program

Use this program to configure arrays and logical drives using ServeRAID controllers. ServeRAID Manager operates in two ways: in startable-CD mode and as an installed program. In startable-CD mode, you can configure your ServeRAID adapter before you install an operating system.

This program is available in the following directory:

e:/operatingsystem/MANAGER

where e is the CD-ROM drive and operatingsystem is the specific operating system used in the ServeRAID installation.

IPSSEND command-line program

Use this program to configure and manage your ServeRAID controllers. This program is available on both the IBM ServeRAID Support CD and the operating-system-specific IBM ServeRAID Support diskettes.

Diskette images

Use these images to create the ServeRAID diskettes. These diskettes include the following:

v IBM ServeRAID BIOS and Firmware Update (1 of 3) diskette v IBM ServeRAID BIOS and Firmware Update (2 of 3) diskette v IBM ServeRAID BIOS and Firmware Update (3 of 3) diskette

v IBM ServeRAID Failover Support for Windows NT

diskette

v IBM ServeRAID Cluster Solution for Windows NT 4.0 and Windows 2000 diskette v IBM ServeRAID Support for Windows 2000 Server diskette v IBM ServeRAID Support for Windows (Professional Editions) diskette v IBM ServeRAID Support for Windows NT 4.0 diskette

v IBM ServeRAID Support for IBM OS/2 v IBM ServeRAID Support for Novell NetWare diskette

v IBM ServeRAID Support for Caldera UnixWare and Open UNIX v IBM ServeRAID Support for SCO OpenServer diskette v IBM ServeRAID Support for Red Hat Linux (1 of 2) diskette v IBM ServeRAID Support for Red Hat Linux (2 of 2) diskette v IBM ServeRAID Support for Caldera OpenLinux (1 of 2) diskette v IBM ServeRAID Support for Caldera OpenLinux (2 of 2) diskette

diskette

4.0 and Windows®2000

diskette

4 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

v IBM ServeRAID Support for SuSE Linux diskette v IBM ServeRAID Support for Turbolinux diskette v IBM ServeRAID Support for DOS diskette

These files are available in the e:/DISKETTE directory, where e is the CD-ROM drive.

For instructions on creating the diskettes, see “Creating ServeRAID diskettes” on page 89.

ServeRAID files needed to install Microsoft Cluster Server (MSCS)

Note: The IBM ServeRAID Cluster Solution requires either Windows 2000 or

Windows NT 4.0.

These files are available in the following directory:

e:/operatingsystem/CLUSTER

where e is the CD-ROM drive and operatingsystem is the specific operating system used in the ServeRAID installation.

ServeRAID publications

The following books are available in Portable Document Format (PDF) on the IBM ServeRAID Support CD in the /BOOKS directory:

v IBM ServeRAID User’s Reference, Version 5.10 (SRAID51.PDF) v IBM ServeRAID Device Driver Installation Instructions (DEVDRV51.PDF)

The following booklets are extracted from the IBM ServeRAID User’s Reference, Version 5.10 and are available on the IBM ServeRAID Support CD in the /BOOKS

directory:

v IBM ServeRAID-4 Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers

Installation Guide (INSTAL51.PDF)

v Configuring IBM ServeRAID Controllers for Failover (FAILOV51.PDF) v Installing the IBM ServeRAID Cluster Solution (CLUSTE51.PDF) v Understanding IBM ServeRAID Technology (TECHNO51.PDF)

Note: Use Adobe Acrobat Reader to view these files. The IBM ServeRAID Support

CD contains the Acrobat Readers for Microsoft Windows, IBM OS/2, and

Linux

in the /BOOKS/READERS directory.

If you are installing the IBM ServeRAID Cluster Solution, you might need to refer to the IBM Shared Disk Clustering Hardware Reference. This book provides general information about planning and configuring a shared-disk cluster using IBM server products. It contains illustrations, descriptions, and parts listings for various high-availability, shared-disk cluster examples.

Note: You can obtain this publication from the IBM Support Web site. See

“Obtaining ServeRAID updates” on page 61 for additional information.

™

In addition, the following IBM Redbooks

v Implementing Netfinity

Disk Subsystems: ServeRAID SCSI, Fibre Channel, and

might be of interest:

SSA

General information 5

v Tuning Netfinity Servers for Performance: Getting the most out of Windows 2000

and Windows NT 4.0

v Netfinity Director: Integration and Tools

v Netfinity Clustering Planning Guide

You can download these books from the IBM Web site at http://www.ibm.com/redbooks/.

Supported operating systems

The following operating systems are supported with ServeRAID-4 and ServeRAID-5i controllers:

v Microsoft XP Professional (ServeRAID-4Lx controller only) v Microsoft Windows 2000 Advanced Server, Datacenter, and Server v Microsoft Windows 2000 Professional (ServeRAID-4Lx controller only) v Microsoft Windows NT 4.0 Enterprise Edition and Server v Novell NetWare (versions 5.x and 6.0) v IBM OS/2 WARP v Red Hat Linux (versions 6.2, 7.0, 7.1, 7.2, and 7.3) v SuSE Linux (versions 7.1, 7.2, 7.3, and 8.0) v Caldera OpenLinux (versions 3.1 and 3.1.1) v Turbolinux (versions 6.5 and 7.0) v SCO OpenServer 5.0.6a v Caldera UnixWare 7.1.1 v Caldera Open UNIX 8.0

Server for e-business

Controller features

The standard features of the ServeRAID controllers are listed in the section for the individual controllers.

The features of ServeRAID software and utility programs supported by ServeRAID controllers are listed in the following table.

ServeRAID features ServeRAID controller

-5i -4Mx -4M -4Lx -4L -4H

ServeRAID ROM Update Wizard Yes Yes Yes Yes Yes Yes ServeRAID Manager Yes Yes Yes Yes Yes Yes ServeRAID Mini-Configuration program Yes Yes Yes Yes Yes Yes IPSSEND Yes Yes Yes Yes Yes Yes

™

IPSSEND FlashCopy XP Professional, Windows 2000, and Windows NT only)

IPSMON (NetWare only) Yes Yes Yes Yes Yes Yes Clustering (Windows NT and Windows

2000 only) Failover (Windows NT and Windows 2000

only)

function (Windows

No Yes Ye s Yes Ye s Yes

6 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Connector locations

This section provides illustrations of the SCSI channel connectors and cable connectors for the ServeRAID-4H, ServeRAID-4L, ServeRAID-4Lx, ServeRAID-4M, ServeRAID-4Mx, and ServeRAID-5i controllers.

Note: You cannot attach internal and external SCSI devices to the same channel.

For example, you cannot attach devices to both external Channel 1 and internal Channel 1. The ServeRAID-4 controllers do not support configurations that use both the internal and external connectors on the same channel concurrently.

The light-emitting diodes (LEDs) on the controllers indicate activity on the SCSI channels and provide diagnostic information for trained service technicians.

ServeRAID-4H controller

Standard features of the ServeRAID-4H controller are as follows.

Feature ServeRAID-4H

Arrays (max.) 8 Battery-backup cache Yes Cache memory 128 MB Hard disk drives (max.) 60 Logical drives (max.) 8 Microprocessor 266 MHz SCSI channels 4 SCSI transfer speed (max.) 160 MB per sec. Supported RAID levels 0, 1, 5, Enhanced-1 (1E), and Enhanced-5 (5E), 00, 10,

System PCI data bus 64 bit at 33 MHz

1E0, 50

The ServeRAID-4H controller has four independent SCSI channel connectors: Channel 1, Channel 2, Channel 3, and Channel 4. Each of these SCSI channels supports up to 15 physical devices.

Note: In the event of a power outage or failure, the battery-backup cache protects

the data stored in the ServeRAID cache memory when using the write-back setting of the write-cache mode.

General information 7

Internal Channel 2

Internal Channel 1

Battery for Backup Cache

External Channel 1

External Channel 2

External Channel 3

External Channel 4

Figure 1. ServeRAID-4H controller

You can attach internal SCSI devices to the internal Channel 1 and Channel 2 connectors. You can attach external SCSI devices to the external Channel 1, Channel 2, Channel 3, and Channel 4 connectors.

Note: The ServeRAID-4H controller uses the module (P/N 38L3386) containing a

lithium battery.

Statement 2

CAUTION:

When replacing the lithium battery, use only IBM Part Number 38L3386 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.

8 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

ServeRAID-4L controller

Standard features of the ServeRAID-4L controller are as follows.

Feature ServeRAID-4L

Arrays (max.) 8 Battery-backup cache No Cache memory 16 MB Hard disk drives (max.) 15 Logical drives (max.) 8 Microprocessor 100 MHz SCSI channels 1 SCSI transfer speed (max.) 160 MB per sec. Supported RAID levels 0, 1, 5, Enhanced-1 (1E), and Enhanced-5 (5E), 00, 10, 1E0,

System PCI data bus 64 bit at 33 MHz

The ServeRAID-4L controller has one independent SCSI channel connector: Channel 1. This SCSI channel supports up to 15 physical devices.

Internal Channel 1

External Channel 1

Figure 2. ServeRAID-4L controller

You can attach internal SCSI devices to the internal Channel 1 connector. You can attach external SCSI devices to the external Channel 1 connector.

Note: The ServeRAID-4L controller uses the module (P/N 38L3386) containing a

lithium battery.

General information 9

Statement 2

CAUTION:

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.

ServeRAID-4Lx controller

Standard features of the ServeRAID-4Lx controller are as follows.

Feature ServeRAID-4Lx

Arrays (max.) 8 Battery-backup cache No Cache memory 32 MB Hard disk drives (max.) 15 Logical drives (max.) 8 Microprocessor 100 MHz SCSI channels 1 SCSI transfer speed (max.) 160 MB per sec. Supported RAID levels 0, 1, 5, Enhanced-1 (1E), and Enhanced-5 (5E), 00, 10, 1E0,

System PCI data bus 64 bit at 33-66 MHz

The ServeRAID-4Lx controller has one independent SCSI channel connector, Channel 1. This SCSI channel supports up to 15 physical devices.

10 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Internal Channel 1

External Channel 1

Figure 3. ServeRAID-4Lx controller

You can attach internal SCSI devices to the internal Channel 1 connector. You can attach external SCSI devices to the external Channel 1 connector.

Note: The ServeRAID-4Lx controller uses the module (P/N 38L3386) containing a

lithium battery.

Statement 2

CAUTION:

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.

ServeRAID-4M controller

Standard features of the ServeRAID-4M controller are as follows.

Feature ServeRAID-4M

Arrays (max.) 8 Battery-backup cache Yes Cache memory 64 MB Hard disk drives (max.) 30

General information 11

Feature ServeRAID-4M

Logical drives (max.) 8 Microprocessor 100 MHz SCSI channels 2 SCSI transfer speed (max.) 160 MB per sec. Supported RAID levels 0, 1, 5, Enhanced-1 (1E), and Enhanced-5 (5E), 00, 10, 1E0,

System PCI data bus 64 bit at 33 MHz

The ServeRAID-4M controller has two independent SCSI channel connectors: Channel 1 and Channel 2. Each of these SCSI channels supports up to 15 physical devices.

Internal Channel 1

Internal Channel 2

External Channel 2

Battery

External Channel 1

Figure 4. ServeRAID-4M controller

You can attach internal SCSI devices to the internal Channel 1 and Channel 2 connectors. You can attach external SCSI devices to the external Channel 1 and Channel 2 connectors.

Note: The ServeRAID-4M controller uses the module (P/N 38L3386) containing a

lithium battery.

12 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Statement 2

CAUTION:

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.

ServeRAID-4Mx controller

Standard features of the ServeRAID-4Mx controller are as follows.

Feature ServeRAID-4Mx

Arrays (max.) 8 Battery-backup cache Yes Cache memory 64 MB Hard disk drives (max.) 30 Logical drives (max.) 8 Microprocessor 100 MHz SCSI channels 2 SCSI transfer speed (max.) 160 MB per sec. Supported RAID levels 0, 1, 5, Enhanced-1 (1E), and Enhanced-5 (5E), 00, 10, 1E0,

System PCI data bus 64 bit at 33-66 MHz

The ServeRAID-4Mx controller has two independent SCSI channel connectors: Channel 1 and Channel 2. Each of these SCSI channels supports up to 15 physical devices.

Note: In the event of a power outage or failure, the battery-backup cache protects

the data stored in the ServeRAID cache memory when using the write-back setting of the write-cache mode.

General information 13

Internal Channel 1

Internal Channel 2

External Channel 2

Battery for Backup Cache

External Channel 1

Figure 5. ServeRAID-4Mx controller

You can attach internal SCSI devices to the internal Channel 1 and Channel 2 connectors. You can attach external SCSI devices to the external Channel 1 and Channel 2 connectors..

Note: The ServeRAID-4Mx controller uses the module (P/N 38L3386) containing a

lithium battery.

Statement 2

CAUTION:

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.

14 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

ServeRAID-5i controller

Standard features of the ServeRAID-5i controller are as follows.

Feature ServeRAID-5i

Arrays (max.) 8 Battery-backup cache Yes Cache memory 128 MB Hard disk drives (max.) 30 Logical drives (max.) 8 Microprocessor 100 MHz SCSI channels 0 SCSI transfer speed (max.) 320 MB per sec. Supported RAID levels 0, 1, 5, Enhanced-1 (1E), and 00, 10, 1E0, 50 System PCI data bus 64 bit at 66 MHz

The ServeRAID-5i controller has no independent SCSI channel connectors. It must be used with an IBM xSeries

™

server that contains an integrated RAID controller. It comes with both a 2-U and 3-U I/O bracket; the 3-U bracket is mounted on the controller. You can connect devices to this controller using the integrated RAID controller’s connectors.

Battery for Backup Cache

Figure 6. ServeRAID-5i controller

Note: The ServeRAID-5i controller uses the module (P/N 38L3386) containing a

lithium battery.

General information 15

Statement 2

CAUTION:

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.

16 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Installing and configuring ServeRAID controllers

This section provides installation, cabling and configuration information for the ServeRAID-4H, -4L, -4Lx, -4M, -4Mx Ultra160 SCSI controllers and ServeRAID-5i Ultra320 SCSI controller (hereafter sometimes referred to as IBM ServeRAID-4x controllers and the IBM ServeRAID-5i Ultra320 SCSI controller).

For information on ServeRAID updates, see “Obtaining ServeRAID updates” on page 61. For information on BIOS code, see “Updating BIOS and firmware code” on page 61.

Using a ServeRAID-4x controller in a server with Active PCI features

Note: The ServeRAID-5i controller does not support (Active) hot-plug features.

Some IBM servers support Active PCI (also called hot-plug PCI) features. The ServeRAID-3 and ServeRAID-4 controllers support Active PCI features on Windows NT 4.0, Windows 2000, and Novell NetWare. The following table summarizes which operating systems support specific Active PCI functions:

Feature Windows NT 4.0 Windows 2000 NetWare 5.x NetWare 6.0 Hot add Yes Yes Ye s Yes Hot remove No Yes Yes Yes Hot replace Yes No No No

You can use the Active PCI features to install, remove, or replace PCI controllers without turning off the server.

v Use the hot-add feature to add a controller to a running server, thus expanding

its capacity.

v Use the hot-remove feature to remove a controller from a running server. v Use the hot-replace feature to replace a controller with an identical controller.

Note: When you use the hot-replace feature, some parameters (such as rebuild

rate) are not restored. If you have previously saved the controller configuration, refer to it for information.

Attention: Do not attempt a hot-replace operation on Windows 2000 or NetWare by hot-removing a failed controller and then hot-adding a new controller. Loss of data can occur. If a controller fails on these operating systems, you must shut down the server to replace the controller.

Using Windows NT 4.0 with Active PCI features

To use Active PCI with Windows NT 4.0 and a ServeRAID controller, you must install the following software components in this order:

1. DMI Service provider. A free version is included on the IBM ServeRAID Support

CD in the following directory: e:\WINNT\DMISP\setup.exe where e is the CD-ROM drive.

Note: This version is sufficient for most users’ needs, but a Y2K compliant

version is available at http://www.enablers.com/.

2. IBM Hot Plug for Windows NT 4.0 Package, version 4.2 or later. This package is available from the IBM Support Web site. See “Obtaining ServeRAID updates”

on page 61 for additional information.

Note: Be sure to read the instructions and restrictions for this software

program.

3. ServeRAID Active PCI DMI component. This is an optional component that you can install during the ServeRAID Manager installation.

To perform a hot-replace operation, start the IBM ServeRAID Hot Replace Wizard. You can start this program from within either the IBM Hot Plug for Windows NT 4.0 program or the ServeRAID Manager program. You can use the ServeRAID Manager program to start the wizard either on the server with the failed controller, or across the network from a remote installation of the ServeRAID Manager.

Note: It is useful to start the IBM ServeRAID Hot Replace Wizard from a remote

installation when the server with the failed controller does not have a monitor.

Using Windows 2000 with Active PCI features

To use Active PCI with Windows 2000, you must install the IBM Active PCI Software for Windows 2000. This software is available from the IBM Support Web site. See “Obtaining ServeRAID updates” on page 61 for additional information.

Note: Be sure to read the instructions and restrictions for this software program.

Using NetWare with Active PCI features

To use Active PCI with NetWare, you must install the IBM PCI Hot-Plug Controller Driver for NetWare. This software is available from the IBM Support Web site. See “Obtaining ServeRAID updates” on page 61 for additional information.

Note: Be sure to read the instructions and restrictions for this software program.

Installing the ServeRAID-4x controller

During the installation, you might need a small, flat-blade screwdriver and the documentation that comes with your server.

Complete the following steps to install the ServeRAID-4 controller:

1. Review “Safety information” on page 127 and the Safety Information book provided with your server.

Note: Some IBM servers support Active PCI features, which enable you to

install or remove PCI controllers without turning off the server. If your server model provides Active PCI support and you are using Windows 2000, Windows NT 4.0, NetWare 5.0, or NetWare 6.0, you do not need to turn off your server to install this controller. This operation is referred to as a hot-add operation. Before performing this operation, complete the following tasks:

v Review the information provided with your server to determine

whether your model supports these features.

18 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

v Review the documentation provided with your operating system for

information concerning using these features.

v See “Using a ServeRAID-4x controller in a server with Active PCI

features” on page 17.

2. If your server model does not support Active PCI, turn off the server and disconnect all power cords and cables from the server.

Statement 5

CAUTION: The power control button on the device and the power switch on the power supply do not turn off the electrical current supplied to the device. The device also might have more than one power cord. To remove all electrical current from the device, ensure that all power cords are disconnected from the power source.

2 1

3. Remove the server cover and locate an empty PCI expansion slot for the controller. Choose a slot that is farthest from other installed components, such as the microprocessor. If necessary, see your server documentation for more detailed information about the expansion slots.

Note: Some server models require that you install the ServeRAID controller in

a specific PCI slot. See the documentation that came with your server for more information.

4. Remove the expansion-slot cover, if applicable.

5. Touch the static-protective package containing the controller to an unpainted metal expansion-slot cover on the server. This discharges any static electricity from the package and your body.

6. Holding the controller by the edges, remove it from the static-protective package. Do not touch any exposed components on the controller.

7. Insert the controller into the PCI expansion slot. Press the controller firmly into the slot so that it is fully seated.

Note: The illustrations in this section depict the ServeRAID-4H controller.

Other IBM ServeRAID controllers will have a slightly different appearance.

Installing and configuring ServeRAID controllers 19

Figure 7. Inserting a ServeRAID-4H controller into the PCI expansion slot

8. Secure the controller by either tightening the expansion-slot screw on the top of the controller or closing the latch, depending on your server.

9. Connect the SCSI cables to the controller. If you intend to attach external devices only, go to step 13 on page 21. Otherwise, go to step 10.

10. Connect one end of a 68-pin standard cable (separately purchased or already in your server) to the internal channel connector on the ServeRAID controller.

Note: For the channel connector locations, refer to the controller locations for

the specific ServeRAID model, earlier in this chapter.

20 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Figure 8. Connecting a ServeRAID-4H controller internal channel connector

11. Connect the other end of the SCSI cable to the SCSI backplane or to a SCSI device in the server. (See your server documentation or the system label inside the server cover for the location of the SCSI connector on the backplane.)

12. If you have physical drives to install, install them now. See your server documentation for drive installation instructions.

13. Install the server cover.

14. If you disconnected the cables and power cords in step 2 on page 19, reconnect the cables and cords. See your server documentation if you need detailed instructions.

15. If you want to attach an external SCSI device to the ServeRAID controller, go to “Connecting external devices to a ServeRAID-4 controller” on page 27. Otherwise, go to “Understanding RAID technology” on page 103.

Installing the ServeRAID-5i controller

Attention: If you plan to install a ServeRAID-5i controller into a server that

contains data, back up the data first. When the ServeRAID-5i controller is installed, you will lose access to any data or applications on physical drives connected to the integrated RAID controller.

Preparing for installation

Before you begin the installation procedure, see the documentation that comes with your server. You need to determine the following:

v The PCI expansion slot into which you will install the controller

Installing and configuring ServeRAID controllers 21

v Whether you need to install the low-profile 2-U bracket

Complete the following steps to install the 2-U bracket. You will need a small, flat-blade screwdriver.

1. Holding the controller by the edges, remove it from the static-protective package. Do not touch any exposed components on the controller.

2. Set the controller battery-side down on a nonconductive, static-protected surface. Do not place the controller on your server cover or on a metal table.

3. Using a small, flat-blade screwdriver, remove the screw from the battery pack.

4. To remove the battery, gently press the tab up and lift the battery away from the controller.

Figure 9. Removing the battery from a ServeRAID-5i controller

5. Remove the two bracket screws. Set them aside.

6. Remove the 3-U bracket.

7. Align the two screw holes in the 2-U bracket with the two screw holes on the controller. Using the two screws you removed in step 5, secure the bracket to the controller.

8. Gently snap the battery back into place.

9. Using the screw you removed in step 3, secure the battery to the controller.

10. Return the controller to the static-protective package.

Installing the ServeRAID-5i controller

During the installation, you might need a small, flat-blade screwdriver and the documentation that comes with your server.

Complete the following steps to install the ServeRAID-5i controller:

1. Review “Safety information” on page 127 and the Safety Information book provided with your server.

2. Turn off the server and disconnect all power cords and cables from the server.

Statement 5

22 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Statement 5

2 1

3. Remove the server cover and locate the PCI expansion slot.

Notes:

a. The ServeRAID-5i controller must be installed in an extended PCI

expansion slot. If you have not already done so, see the documentation that comes with your server to determine the correct PCI expansion slot for the ServeRAID-5i controller.

b. If another controller is already installed in the extended PCI expansion slot

designed for the ServeRAID-5i controller, you must remove the controller before installing the ServeRAID-5i controller.

4. Remove the expansion-slot cover, if applicable.

5. Touch the static-protective package containing the controller to an unpainted metal expansion-slot cover on the server. This discharges any static electricity from the package and your body.

6. Holding the controller by the edges, remove it from the static-protective package. Do not touch any exposed components on the controller.

7. Insert the controller into the PCI expansion slot. Press the controller firmly into the slot so that it is fully seated.

Figure 10. Inserting a ServeRAID-5i controller into the PCI expansion slot

Installing and configuring ServeRAID controllers 23

8. Secure the controller by either tightening the expansion-slot screw on the top of the controller or closing the latch, depending on your server.

9. If you have physical drives to install, install them now. See your server documentation for drive installation instructions.

10. Install the server cover.

11. Reconnect the cables and cords. See your server documentation if you need detailed instructions.

Replacing the battery pack on the ServeRAID-5i Ultra320 controller

The IBM ServeRAID-5i Ultra320 SCSI controller has a replaceable battery pack for the backup cache. If your controller requires a new battery pack, you must use the following instructions to replace the battery pack.

Attention: Failure to follow these instructions might damage the ServeRAID-5i controller.

Complete the following steps to replace the battery pack. You will need a small, flat-blade screwdriver.

1. Review “Safety information” on page 127, “Handling electrostatic

discharge-sensitive devices” on page 130, and the Safety Information book provided with your server.

2. Set the controller battery-side down on a nonconductive, static-protected

surface. Do not place the controller on your server cover or on a metal table.

3. Using a small, flat-blade screwdriver, remove the screw from the battery pack.

4. To remove the battery, gently press the tab up and lift the battery away from the

controller.

Ta b

Alignment pin

Battery

5. Remove the new battery pack from its packaging.

24 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Attention: Attention Follow steps 6 and 7 carefully. Failure to do so might

damage the controller.

6. Carefully position the new battery pack on the controller. Be sure that the alignment pin and the two tabs are properly aligned.

Tabs

Alignment pin

Battery

7. Press gently on the center of the battery pack to snap the battery pack into place. Be sure to apply pressure evenly with both hands and to hold the controller as shown in the figure below. Also, make sure that the tab is properly latched on the controller.

8. Using the screw you removed in step 3 on page 24, secure the battery to the controller.

9. The battery pack contains a nickel metal hydride battery. Be sure to recycle or dispose of the discarded battery pack properly. Recycling facilities might not be available in your area.

Installing the ServeRAID-5i controller 2-U bracket

The IBM ServeRAID.-5i Ultra320 SCSI controller has a 3-U bracket. If your server requires a low-profile 2-U bracket, you must use the following instructions to install the 2-U bracket.

Attention: Failure to follow these instructions might damage the ServeRAID-5i controller.

Complete the following steps to install the 2-U bracket. You will need a small, flat-blade screwdriver.

1. Review “Safety information” on page 127, “Handling electrostatic discharge-sensitive devices” on page 130, and the Safety Information book provided with your server.

2. Holding the controller by the edges, remove it from the static-protective package.

Installing and configuring ServeRAID controllers 25

3. Set the controller battery-side down on a nonconductive, static-protected surface. Do not place the controller on your server cover or on a metal table.

4. Using a small, flat-blade screwdriver, remove the screw from the battery pack.

5. To remove the battery, gently press the tab up and lift the battery away from the controller.

Ta b

Alignment pin

Battery

6. Remove the two bracket screws. Set them aside.

7. Remove the 3-U bracket.

8. Align the two screw holes in the 2-U bracket with the two screw holes on the controller. Using the two screws you removed in step 6, secure the bracket to the controller. The screws enter the screw holes on the battery side of the controller and then go through the bracket screw holes.

Attention: Follow steps 9 and 10 on page 27. carefully. Failure to do so might damage the controller.

9. Carefully reposition the battery pack on the controller. Be sure that the alignment pin and the two tabs are properly aligned.

Tabs

Alignment pin

Battery

26 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

10. Press gently on the center of the battery pack to snap the battery pack into place. Be sure to apply pressure evenly with both hands and to hold the controller as shown in the figure below. Also, make sure that the tab is properly latched on the controller.

11. Using the screw you removed in step 4 on page 26, secure the battery to the controller.

IBM Director support for the ServeRAID-5i controller

If you want to use IBM Director to monitor and manage the IBM ServeRAID-5i Ultra320 SCSI controller, you must use IBM Director Version 3.1 with Service Pack 1, or later.

Notes:

1. IBM plans to release IBM Director 3.1 with Service Pack 1 by the beginning of

August, 2002.

2. If you do not use IBM Director, you can use the ServeRAID Manager program

to configure, manage, and monitor your ServeRAID-5i controller. This program is on the IBM ServeRAID Support CD that came with your ServeRAID-5i controller.

Complete the following steps to download IBM Director 3.1 with Service Pack 1:

1. Go to the IBM Systems Management - Director Version 3.1 Package page at

www.pc.ibm.com/qtechinfo/MIGR-40738.html

2. Scroll down the page to the File Details section.

3. For each file that you want to download, right-mouse click the file and click your

browser action to save the file to your hard disk drive (for example, click Save Target As).

4. Install the IBM Director Service Pack according to the instructions in the IBM

Director Version 3.1 with Service Pack 1 README file.

Connecting external devices to a ServeRAID-4 controller

Note: You cannot attach internal and external SCSI devices to the same channel.

same channel concurrently. Complete the following steps to attach SCSI devices to an external channel connector on the ServeRAID-4 controller:

1. Connect one end of a 68-pin very-high-density connector interface (VHDCI)

SCSI cable to an external channel connector on the ServeRAID controller.

Installing and configuring ServeRAID controllers 27

Note: For connector locations, refer to the controller locations for the specific

ServeRAID model, earlier in this chapter.

Figure 11. Connecting a ServeRAID-4H controller external channel connector

2. Connect the other end of the SCSI cable to the external SCSI device.

3. Go to “Updating BIOS and firmware code” on page 61.

Configuring the ServeRAID controller

This section provides information about starting and using the ServeRAID Manager program. You can use the ServeRAID Manager program to configure your ServeRAID controllers, view the ServeRAID configurations and associated devices, change controller settings, monitor your controllers, and more.

The information in this section is an overview of the ServeRAID Manager program and its capabilities. For instructions on specific processes using the ServeRAID Manager program, refer to the ServeRAID Manager online help.

If you are configuring an integrated RAID controller, see the instructions in the Installation Guide provided with your server.

Important: If you intend to use your ServeRAID-4 controllers in a Microsoft

Windows failover or clustering environment, do the following:

v For failover, see the IBM ServeRAID User’s Reference . v For clustering, go to “IBM ServeRAID cluster solution” on page 53.

28 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Using ServeRAID Manager

The ServeRAID Manager program operates in two ways:

v Startable-CD mode v As an installed software program

When you run the ServeRAID Manager program from the startable IBM ServeRAID Support CD, you are using startable-CD mode. Startable-CD mode lets you to

configure your controller before you install your operating system. After you have configured the controller and installed the operating system, you also can use startable-CD mode to change specific controller settings. For additional information, see “Viewing your configuration” on page 36.

To run the ServeRAID Manager program in startable-CD mode, turn on the server; then, insert the IBM ServeRAID Support CD (or the CD that contains the ServeRAID Manager program that came with your server) into the CD-ROM drive.

If the ServeRAID Manager program detects unconfigured controllers and ready drives, the program automatically starts the Configuration wizard, and a window similar to that shown in Figure 12 opens.

Figure 12. “Configuration wizard” window

You can use the Configuration wizard to create up to eight arrays and up to eight logical drives for each ServeRAID controller. The Configuration wizard provides two configuration options: Express and Custom. Express configuration automatically configures your ServeRAID controller, and you can use Custom configuration to configure your controller manually. If you want to use RAID level-1E, RAID-level-5E, or RAID level-x0, you must use Custom configuration. For more information about RAID levels, see “Understanding RAID technology” on page 103.

Installing and configuring ServeRAID controllers 29

Using Express configuration

Express configuration automatically configures your ServeRAID controller. This feature does the following:

v Creates arrays by grouping together same-sized physical drives. v Creates one logical drive per array. v Assigns a RAID level based on the number of physical drives in an array:

– An array with a single physical drive is assigned RAID level-0. – An array with two physical drives is assigned RAID level-1. – An array with three or more physical drives is assigned RAID level-5.

v Designates a hot-spare drive for the controller. If one or more arrays has four or

more physical drives, the largest-sized drive from those arrays is designated the hot-spare drive.

Complete the following steps to use Express configuration:

1. In the ServeRAID Manager tree, click the ServeRAID controller that you want to configure.

2. Click Express configuration.

3. Click Next. The “Configuration summary” window opens.

4. Review the information that is displayed in the “Configuration summary” window. To change the configuration, click Modify arrays or Modify logical drives.

Figure 13. “Configuration summary” window (Express Configuration)

Note: Some operating systems have size limitations for logical drives. Before

you save the configuration, verify that the size of the logical drive is appropriate for your operating system.

5. Click Apply; then, click Yes when asked if you want to apply the new configuration. The configuration is saved in the ServeRAID controller and in the physical drives.

6. If you have multiple controllers, do the following:

30 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

a. Click the ServeRAID controller that you want to configure.

b. From the toolbar, click

(Configure RAID).

c. Repeat steps 2 on page 30 through 6 on page 30 for each controller.

7. When you have completed configuring your controllers, you can change certain controller settings. See “Fine-tuning your configuration” on page 36 for more information. If you do not want to change any settings, exit from the ServeRAID Manager program, and remove the CD from the CD-ROM drive.

8. Restart the server.

9. Continue by installing ServeRAID device drivers (see the IBM ServeRAID User’s Reference for more information).

Note: If you are configuring your startup (boot) ServeRAID controller, you must

install the device driver while installing the operating system.

Using Custom configuration

Select Custom configuration to configure your controller manually. Complete the following steps to use Custom configuration:

1. In the ServeRAID Manager tree, click the ServeRAID controller that you want to configure.

2. Click Custom configuration.

3. Click Next. The “Create arrays” window opens. If you want to create spanned arrays, go to step 2 of “Creating spanned arrays” on page 34.

Figure 14. “Create arrays” window

4. Click the appropriate tab in the right pane; then, from the list of ready drives, select the drives you want to move to the array.

5. Click Add selected drives to add the drives to the array. Click Add all drives to move all ready drives to an array.

Installing and configuring ServeRAID controllers 31

6. Repeat steps 4 on page 31 and 5 on page 31 for each additional array or hot-spare drive that you want to configure.

7. After you select the ready drives for your arrays and hot-spare drive, click Next. The “Create logical drives” window opens.

Figure 15. “Create logical drives” window

8. Click the appropriate Array tab.

9. Select a RAID level from the drop-down list. (For more information, see “Supported RAID levels” on page 104.)

Notes:

a. RAID level-5E allows only one logical drive per array. b. If you are configuring a spanned array, you can set the RAID level only for

the first logical drive you create.

10. If you do not want to use the maximum size for the logical drive, type the size

in the Data (MB) field.

Notes:

a. You can define up to eight logical drives per controller. There are two

exceptions:

v If an array contains a logical drive assigned RAID level-5E v If you want to use the logical-drive migration feature

In these cases, one logical drive slot must be left free; therefore, you cannot define more than seven logical drives.

b. Some operating systems have size limitations for logical drives. Before you

save the configuration, verify that the size of the logical drive is appropriate

for your operating system. c. A logical drive cannot exceed 2048 GB. d. Typically, the first logical drive defined on the first ServeRAID controller

found by system BIOS during startup will be your startup (boot) drive.

32 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

11. If you have free space available and want to create additional logical drives,

click Create new logical drive.

Figure 16. “Adding another logical drive” window

12. Repeat steps 9 through 11 for each logical drive that you want to define in this array.

13. Repeat steps 8 on page 32 through 12 for each additional array you want to configure.

14. Click Next. The “Configuration summary” window opens.

Installing and configuring ServeRAID controllers 33

Figure 17. “Configuration summary” window (Custom Configuration)

15. Review the information that is displayed in the “Configuration summary”

window. To change the configuration, click Back.

16. Click Apply; then, click Yes when asked if you want to apply the new

configuration. The configuration is saved in the ServeRAID controller and in the physical drives.

17. If you have multiple controllers, do the following: a. Click the ServeRAID controller that you want to configure.

b. From the toolbar, click

(Configure RAID).

c. Repeat steps 2 on page 31 through 17b for each controller.

18. When you have completed configuring your controllers, you can change certain controller settings. See “Fine-tuning your configuration” on page 36 for more information. If you do not want to change any settings, exit from the ServeRAID Manager program, and remove the CD from the CD-ROM drive.

19. Restart the server.

20. Continue by installing ServeRAID device drivers (see the IBM ServeRAID User’s Reference for more information).

Note: If you are configuring your startup (boot) ServeRAID controller, you

must install the device driver while installing the operating system.

Creating spanned arrays: If you want to assign RAID level-x0 to an array, you must create a spanned array. For more information about spanned arrays, see “Understanding RAID level-x0” on page 112.

Notes:

1. Spanned arrays are supported only by ServeRAID-4 and ServeRAID-5i

controllers.

34 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

2. A logical drive cannot exceed 2048 GB.

Complete the following steps to create one or more spanned arrays:

1. If you have not completed steps 1 to 3 in “Using Custom configuration” on page 31, do so now.

2. Create identical arrays by doing the following: a. Click the Array tab in the right panel; then, from the list of ready drives,

select the drives you want to move to the array.

b. Click Add selected drives to add the drives to the array. c. Repeat steps 2a and 2b for each additional array that you want to configure.

Note: To create a spanned array, the arrays to be spanned must be

identical (that is, they must have the same number of physical drives).

d. Select the Span arrays check box; then, click Next. The “Create spanned

arrays” window opens.

Figure 18. “Create spanned arrays” window

3. Create spanned arrays by doing the following: a. In the list of arrays, click the arrays that you want to add to your spanned

array.

b. Click

can click

(Add selected arrays) to add the arrays to the spanned array. You

(Add all arrays) to move all arrays to the spanned array.

c. To create additional spanned arrays, click the New spanned array tab in the

right pane; then, repeat steps 3a and 3b.

4. Click Next; the “Create logical drives” window opens. Continue with step 8 of “Using Custom configuration” on page 31.

Installing and configuring ServeRAID controllers 35

Fine-tuning your configuration

Before you store data on the controller, you will need to determine the correct stripe-unit size for your configuration and set the write-cache mode, if necessary.

Changing the stripe-unit size

The new controller stripe-unit size is set at the factory to 8 KB. If you need to change this setting, you must change the stripe-unit size before you store data in the logical drives. After you store data in the logical drives, you cannot change the stripe-unit size without destroying data in the logical drives.

Complete the following steps to change the stripe-unit size:

1. In the ServeRAID Manager tree, click the new controller to select it.

2. Click Actions → Change stripe-unit size.

3. Select the new stripe-unit size for your installation.

Note: Consider your server application environment when you select the

controller stripe-unit size setting.

Environment Stripe-unit size

Groupware (such as Lotus Notes Transaction processing database 16 KB Decision support database 16 KB Thin client environments 8 KB File server (Windows 2000, Windows NT 4.0, Novell NetWare) 16 KB File server (other) 8 KB Web server 8 KB Other 8 KB

®®

or Exchange) 16 KB

Write-cache mode

If you are preparing to install Novell NetWare 5.x from the startable Novell NetWare

5.x CD, set the write-cache mode to write through for the logical drive to which you

will install the operating system. To accomplish this, complete the following steps:

1. In the ServeRAID Manager tree, click the logical drive.

2. Click Actions → Change write-cache mode to write through.

Viewing your configuration

You can use ServeRAID Manager to view information about RAID controllers and the RAID subsystem (such as arrays, logical drives, hot-spare drives, and physical drives).

To view information, expand the ServeRAID Manager tree; then, click the relevant tree object. Detailed information about the selected device appears in the right pane.

36 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Figure 19. ServeRAID Manager window

To display available actions for an item, click the item in the ServeRAID Manager tree and click Actions.

Getting assistance

For more information about ServeRAID Manager, see the online help system. To start the help system, select an item from the Help menu.

Installing and configuring ServeRAID controllers 37

Figure 20. ServeRAID Manager help menu

The help system (ServeRAID Assist) will open within the ServeRAID Manager interface.

To learn more about the ServeRAID Manager tree objects and the actions that apply to them, select a tree object and click Actions → Hints and tips. ServeRAID Assist will start, and information about the tree object will appear in the right pane of ServeRAID Manager.

38 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Figure 21. Hints and tips feature

Installing and configuring ServeRAID controllers 39

40 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Using utility programs

This section provides the information that is needed to start and use the ServeRAID Mini-Configuration program, and the IPSSEND and IPSMON command-line programs.

Using the ServeRAID Mini-Configuration program

This chapter provides the information needed to start and use the ServeRAID Mini-Configuration program.

The ServeRAID Mini-Configuration program provides a quick way to display the current settings for a ServeRAID controller. You also can use this program to perform a limited set of the configuration functions without using the IBM ServeRAID Support CD.

Accessing the Mini-Configuration program

Complete the following steps to access the Mini-Configuration program:

1. Turn on the server. If the server already is running, shut down the operating system; then, restart the server.

2. When the following message appears, promptly press Ctrl+I:

Press Ctrl+I to access the Mini-Configuration Program

3. If your server contains more than one ServeRAID controller, a selection screen appears. To continue, do the following: a. Use the Up Arrow (↑) or Down Arrow (↓) key to select a controller. b. Press Enter.

If your server contains only one ServeRAID controller, or after you select a ServeRAID controller, the main menu appears.

The following choices are available from the main menu: v View Controller Status shows the current status of the ServeRAID

controller. (See “Viewing the controller status” for more information.)

v View Configuration shows the current configuration information for the

ServeRAID controller. (See “Viewing the configuration” on page 42 for more information.)

v Advanced Functions is used to restore the controller to the factory-default

settings, import configuration from drives, configure BIOS settings, and view the controller and PCI information. (See “Viewing the configuration” on page 42 for more information.)

4. Use the Up Arrow (↑) or Down Arrow (↓) key to highlight your choice; then, press Enter.

5. Follow the instructions that appear on the screen.

6. Click Exit. If your server contains more than one ServeRAID controller, the controller selection screen appears. Otherwise, the Mini-Configuration program closes.

Viewing the controller status

When you select View Controller Status from the main menu, the following information appears on the screen:

v All physical drives and their states

v Unattend shows the current state of the unattended mode.

– When this option is set to Off and a startup error occurs, the system stops at

the recovery option screen and waits for you to choose the recovery method.

– When this option is set to On and a startup error occurs, the system stops at

the recovery option screen and waits 30 seconds for you to respond. Then, the BIOS automatically selects an appropriate option and continues the system startup process.

v ReadAhead shows the current state of the read-ahead cache mode. v CompMode shows the current state of BIOS-compatibility mapping. Off indicates

8 GB (Extended); On indicates 2 GB (Limited).

v Clustered shows the current state for clustering. v BBC shows the cache size of the battery-backup cache, if it is installed (8 = 8

MB or 32 = 32 MB) or No if there is no battery-backup cache installed.

v Boot Blk shows the version number of the startable microcode (or firmware)

loaded for the ServeRAID controller.

v Code Blk shows the current version number of the microcode (or firmware)

loaded for the ServeRAID controller.

v Rebuild Rate shows the current speed setting for rebuilds: High, Medium, or

Low.

v Number of Defunct drives shows the current number of defunct physical drives. v Number of Offline drives shows the current number of offline logical drives. v Number of Critical drives shows the current number of critical logical drives. v Config Updates shows the number of times that the configuration has been

changed since it was initialized. When you initialize the configuration, the Config Updates resets to 0.

v Bad Stripe, Locked Stripe, or Blocked Drive identifies the logical drives that

are affected. – Bad Stripe Drives indicates logical drives that have inaccessible areas. – Locked Stripe Drives is a reserved field. – Blocked Drives indicates the logical drives that are blocked. You must

unblock a blocked drive before you can use it. See “Logical drive state descriptions” on page 114 for more information.

Viewing the configuration

You can select View Configuration from the main menu to display the number, size, RAID level, state, stripe-unit size, write-cache mode, read-ahead cache mode, and creation date for each logical drive.

Using the advanced configuration functions

You can select the Advanced Functions to restore the controller configuration to factory-default settings, copy the configuration to the controller from the connected physical drives, configure BIOS settings, and view the controller and PCI information.

When you select the Advanced Functions from the main menu, the following choices are displayed.

Attention: Be careful when making selections from this menu. If you change the configuration, you might lose data.

42 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

v Restore to Factory Default Settings restores all parameters in the configuration

to the factory-default settings. When you reset the configuration, any data or programs stored on the logical drives attached to the selected ServeRAID controller will become inaccessible.

This choice deletes the existing configuration information; that is, it deletes all logical drives defined for the controller and sets all functional physical drives attached to the controller to the ready state.

v Copy the Configuration from Drives to Controller reads the most common

configuration from the drives in the server and copies it to the ServeRAID controller.

v Configure BIOS Settings is used to modify the following BIOS settings for the

ServeRAID controller: – BIOS support for startable CDROM – BIOS support for INT13 extensions – BIOS support for reading partition tables – Bypass read/verify operations – BIOS compatibility mapping – Override temporary write through – Load ServeRAID BIOS default settings – Save configuration to the ServeRAID controller

v View Controller and PCI Information shows the ServeRAID controller hardware

and PCI register information.

v Exit is used to exit from the current menu to the previous menu.

Using the IPSSEND command-line program

This chapter provides the information needed to start and use the IPSSEND command-line program.

IPSSEND is an advanced command-line program that you can use to configure and manage your ServeRAID controllers. This utility program is provided on the IBM ServeRAID Support diskettes and the IBM ServeRAID Support CD.

Starting the IPSSEND command-line program

The IPSSEND command-line program provides a number of functions. Some of these functions are useful as diagnostic or error-recovery tools. This manual addresses only these diagnostic and error-recovery functions. Descriptions of the other functions of the IPSSEND command-line program can be found in the documentation that shipped with the controller.

When you run IPSSEND with no parameters, a list of available functions and their specific parameters appears. The available functions and their parameters are described in the sections that follow.

To run the IPSSEND program with no parameters: v If you are using Windows NT 4.0, Windows 2000, or OS/2:

1. Type:

c:\ipsadm\ipssend

where c is the drive letter of the drive where Windows NT 4.0, Windows 2000, or OS/2 is installed.

2. Press Enter.

Using utility programs 43

v If you are using NetWare:

1. From the console, type:

load ipssend

2. Press Enter.

v If you are using Linux, OpenServer, or UnixWare:

1. Type:

/usr/bin/ipssend

2. Press Enter.

v If you are using DOS:

1. Insert the startable IPSSEND diskette into diskette drive A; then type:

a:\ipssend

where a is the drive letter of the diskette drive.

2. Press Enter.

You can run IPSSEND either from your operating system or by using the startable (bootable) IBM ServeRAID Support for DOS diskette. When you run IPSSEND without parameters, a list of available functions and their specific parameters is displayed.

Starting IPSSEND from Windows, NetWare, OS/2, Linux, OpenServer, UnixWare, or Open UNIX

To start and run IPSSEND without parameters, type one of the following and press Enter:

For Windows and OS/2

For NetWare

For Linux, OpenServer, UnixWare, and Open UNIX

where c is the drive letter of the drive where the operating system is installed.

Starting IPSSEND from DOS

Complete the following steps to start IPSSEND:

1. Insert the IBM ServeRAID Support for DOS diskette into the diskette drive.

2. Restart the server.

3. Type the following and press Enter:

a:\ipssend

where a is the diskette drive letter.

Using the IPSSEND command-line program

The syntax conventions are as follows:

v Commands are shown in uppercase letters. v Variables are shown in italics and explained immediately afterward. v Optional commands or variables are enclosed in brackets. v Where you must type one of several commands, the values are separated by

slashes.

v Default values are underlined.

c:\ipsadm\ipssend

load ipssend

/usr/bin/ipssend

44 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

v Repeatable parameters are enclosed in braces, and the maximum number of

repetitions is specified.

Server roll-out functions

Server roll-out functions are for server roll-out and building systems only; these functions are not for restoring systems. Do not use these commands for servicing systems.

The following lists the IPSSEND server roll-out functions:

v autosync v backup v copyId v init v restore v synch

Error-recovery functions

The following table describes the IPSSEND error-recovery functions.

Function What it does Command and supported operating systems getstatus This function displays information about

the most recent rebuild, synchronization, logical drive migration, or FlashCopy. The information includes the type of operation, status, logical drive number, logical drive size, and percentage of the operation completed.

rebuild This function rebuilds a defunct physical

drive. You can use this function for arrays that contain one or more logical drives in the critical state.

IPSSEND GETSTATUS controller

where controller is the ServeRAID controller number (1–12).

Supported operating systems: Windows, NetWare, OS/2, Linux, OpenServer, UnixWare, Open UNIX, and DOS

IPSSEND REBUILD controller dch dsid nch nsid

where:

v controller is the ServeRAID controller number (1–12) v dch is the channel number for the defunct drive (1–4) v dsid is the SCSI ID for the defunct drive (0–15) v nch is the channel number for the new drive (1–4) v nsid is the SCSI ID for the new drive (0–15)

Supported operating systems: Windows, NetWare, OS/2, Linux, OpenServer, UnixWare, Open UNIX, and DOS

Using utility programs 45

Function What it does Command and supported operating systems setstate This function changes the state of a

physical drive.

Attention: Be very careful when using this function. For example, you might lose data if you change a physical drive from the defunct to online state without first performing a rebuild operation.

unblock This function provides access to a blocked

RAID level-0 logical drive.

Important: The logical drive might contain damaged data. You must recreate or restore the data.

IPSSEND SETSTATE controller channel sid newstate

where:

v controller is the ServeRAID controller number (1–12) v channel is the channel number for the drive (1–4) v sid is the SCSI ID for the drive (0–15) v newstate is the new state for the drive. Valid states

are: – EMP for Empty – RDY for Ready – HSP for Hot spare – SHS for Standby hot spare – DDD for Defunct disk drive – DHS for Defunct hot spare – RBL for Rebuild – SBY for Standby – ONL for Online

Supported operating systems: Windows, NetWare, OS/2, Linux, OpenServer, UnixWare, Open UNIX, and DOS

IPSSEND UNBLOCK controller logicaldrive

where:

v controller is the ServeRAID controller number (1–12) v logicaldrive is the logical drive number (1–8)

Supported operating systems: Windows, NetWare, OS/2, Linux, OpenServer, UnixWare, Open UNIX, and DOS

Problem-isolation and debug functions

The following table describes the IPSSEND problem-isolation and debug functions.

Function What it does Command and supported operating systems certify This function verifies the media of a

physical drive. If IPSSEND finds errors, it reassigns the sectors. Once the procedure is complete, IPSSEND summarizes the reassignments and Predictive Failure Analysis

eraseevent This function clears all entries in the

designated event logs. (See getevent for descriptions of the ServeRAID controller device event, soft event, and hard event logs).

(PFA) errors.

IPSSEND CERTIFY controller channel sid

where:

v controller is the ServeRAID controller number (1–12) v channel is the channel number for the device (1–4) v sid is the SCSI ID for the device (0–15)

Supported operating system: DOS IPSSEND ERASEEVENT controller

DEVICE/SOFT/HARD/ALL

where:

v controller is the ServeRAID controller number (1–12) v DEVICE is the device event log v SOFT is the ServeRAID controller soft event log v HARD is the ServeRAID controller hard event log v ALL is the ServeRAID controller device event, soft

event, and hard event logs

Supported operating systems: Windows, NetWare, OS/2, Linux, OpenServer, UnixWare, Open UNIX, and DOS

46 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Function What it does Command and supported operating systems format This function performs a low-level format of

IPSSEND FORMAT controller options NOPROMPT

a physical drive, erasing all data.

where:

Attention: After issuing the format command, do not stop the formatting process. If you stop the process, the physical drive will not respond to anything except the format function. To recover the drive, see “Recovering from an incomplete format of a physical drive” on page 70.

v controller is the ServeRAID controller number (1 to

12)

v options is composed of one of three choices:

– [<Channel> <SCSI ID>]

When this option is selected:

- Channel is the channel number for the device (1 to 4)

- SCSI ID is the SCSI ID of the device (0 to 15)

– ALL

- When ALL is selected, all hard disk drives in the READY state will be formatted.

– CHANNEL <Channel>

- When CHANNEL is selected, all READY drives for the specified channel will be formatted.

Format command errors indicate that the specified hard disk drive is not present or there is some other hard disk drive problem.

If a previous format command to a hard disk drive was interrupted, this drive may respond only to a format command. In this situation, the hard disk drive will not appear in the controller’s configuration. The user can attempt to format the drive using the FORMAT command to make it available for use.

getevent This function displays the contents of the

designated event logs.

IPSSEND GETEVENT controller DEVICE/SOFT/HARD/ALL

getversion This function lists the versions of BIOS,

cluster DLL, device driver, and firmware for every ServeRAID controller in the server.

identify This function flashes the LEDs on a

designated physical or logical drive. To stop the LEDs from flashing, press any key.

where:

event, and hard event logs

Supported operating systems: Windows, NetWare, OS/2, Linux, OpenServer, UnixWare, Open UNIX, and DOS

IPSSEND GETVERSION

Supported operating systems: Windows, NetWare, OS/2, Linux, OpenServer, UnixWare, Open UNIX, and DOS

IPSSEND IDENTIFY controller PHYSICALDRIVE/LOGICALDRIVE options

where:

v controller is the ServeRAID controller number (1–12) v PHYSICALDRIVE is the designated physical drive v LOGICALDRIVE is the designated logical drive v options is one of the following:

– If PHYSICAL DRIVE, the channel ID and SCSI ID – If LOGICALDRIVE, the logical drive number (1-8)

Supported operating systems: Windows, NetWare, OS/2, Linux, OpenServer, UnixWare, Open UNIX, and DOS

Using utility programs 47

Function What it does Command and supported operating systems selftest This function directs a controller or physical

drive to perform its self-test. You must restart the server after the self-test is completed.

IPSSEND SELFTEST controller options AD/PD channel

sid

where:

v controller is the ServeRAID controller number (1–12) v AD is the ServeRAID controller self-test v PD is the physical drive self-test v (If PD) channel is the drive channel (1–4), and sid is

the SCSI ID for the device (0–15).

Supported operating system: DOS

RAID configuration functions

The following table describes the IPSSEND RAID configuration functions.

Function What it does Command and supported operating systems create This function create logical drives on

either an existing or a new array. To define a new array, you must type the channel and SCSI ID of the physical drives. Note: You cannot create RAID level-x0 logical drives with this function.

After the logical drive is created, a quick initialization is done. The quick initialization process initializes the first 1024 sectors of the logical drive.

If you assign the logical drive RAID level-5 or RAID level-5E and the ServeRAID controller supports auto-synchronization, the logical drive automatically synchronizes in the background. If the controller does not support the auto-synchronization feature, you can use the IPSSEND synch function to synchronize the RAID level-5 or RAID level-5E logical drives. After synchronization, the logical drives are available for storing data.

delete This function deletes an array. You will

lose all the data contained in logical drives defined in the array.

Note: You cannot delete spanned arrays (RAID level-x0 logical drives) with this function.

IPSSEND CREATE controller LOGICALDRIVE NEWARRAY/ARRAYID size raidlevel {channel sid} [NOPROMPT]

where:

v controller is the ServeRAID controller number (1–12) v NEWARRAY indicates that you are creating a new

array and logical drive

v ARRAYID is the Array ID (A–H) of the existing array

on which you want to create a logical drive

v size is one of the following:

– The size in MB of the logical drive – MAX indicates that you want to use all available

space in the array.

v raidlevel is the RAID level for the logical drive (0, 1,

1E, 5, or 5E)

v If NEWARRAY, channel is the channel number for the

device (1– 4), and sid is the SCSI ID for the device (0–15). The maximum number of repetitions of {channel sid} is 16.

v NOPROMPT is an optional parameter that overrides

the user prompt.

Supported operating systems: Windows, NetWare, OS/2, Linux, OpenServer, UnixWare, Open UNIX, and DOS

IPSSEND DELETE controller ARRAY arrayID

where

v controller is the ServeRAID controller number (1–12) v arrayID is the array identifier (A-H) of an existing array

Supported operating systems: Windows, NetWare, OS/2, Linux, OpenServer, UnixWare, Open UNIX, and DOS

48 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Function What it does Command and supported operating systems devinfo This function lists the state and size of a

IPSSEND DEVINFO controller channel sid

physical drive.

where:

v controller is the ServeRAID controller number (1–12) v channel is the channel number for the device (1– 4) v sid is the SCSI ID for the device (0–15)

Supported operating systems: Windows, NetWare, OS/2, Linux, OpenServer, UnixWare, Open UNIX, and DOS

drivever This function lists the vendor ID, firmware

IPSSEND DRIVEVER controller channel sid version, and serial number of a designated physical drive. IPPSEND retrieves this information directly from the physical drive.

where:

v controller is the ServeRAID controller number (1–12)

v channel is the channel number for the device (1– 4)

v sid is the SCSI ID for the device (0–15)

Supported operating systems: Windows, NetWare, OS/2,

Linux, OpenServer, UnixWare, Open UNIX, and DOS

getconfig This function lists information about a

IPSSEND GETCONFIG controller AD/LD/PD/AL controller, logical drive, or physical drive. This information potentially includes (but is not limited to) the following:

v Controller type v BIOS, boot block, device driver, and

firmware versions

v Logical drive status, RAID level, and

size

v Physical drive type, SCSI ID, presence

of PFA

where:

v controller is the ServeRAID controller number (1–12)

v AD specifies the controller information.

v LD specifies the logical drive information.

v PD specifies the physical device information.

v AL specifies all information.

Supported operating systems: Windows, NetWare, OS/2,

Linux, OpenServer, UnixWare, Open UNIX, and DOS v Physical drive state

hsrebuild This function enables the hot-swap rebuild

IPSSEND HSREBUILD controller ON feature.

where controller is the ServeRAID controller number

(1–12)

readahead This function enables, disables, or sets

the read-ahead cache mode to “Adaptive.”

scandrives This function scans all SCSI channel on a

controller for the following:

v Physical drives that have been added v Ready drives that have been removed

Supported operating systems: Windows, NetWare, OS/2,

Linux, OpenServer, UnixWare, Open UNIX, and DOS

IPSSEND READAHEAD controller ON/OFF/ADAPTIVE

where:

v controller is the ServeRAID controller number (1–12)

v ON enables the read-ahead cache mode

v OFF disables the read-ahead cache mode

v ADAPTIVE indicates that the controller will determine

the best mode to use at any given time.

Supported operating system: DOS

IPSSEND SCANDRIVES controller

where controller is the ServeRAID controller number

(1–12)

Supported operating systems: Windows, NetWare, OS/2,

Linux, OpenServer, UnixWare, Open UNIX, and DOS

Using utility programs 49

Function What it does Command and supported operating systems setconfig This function modifies the controller

configuration. You can either restore the controller to the factory-default settings, or you can copy the configuration from physical drives attached to a controller.

unattended This function enables or disables

unattended mode. This controller setting determines how the BIOS handles failures during system startup.

IPSSEND SETCONFIG controller DEFAULT/IMPORTDRIVE [NOPROMPT]

where:

v controller is the ServeRAID controller number (1–12) v DEFAULT restores the controller to the factory-default

settings. All logical drives that are currently defined will be deleted.

v IMPORTDRIVE copies the configuration from the

drives attached to the controller. To import from a specific physical drive, type the channel number and the SCSI ID; otherwise, the controller selects the drive from which to import the configuration. This option is useful when you are replacing a controller and reestablishing the original configuration on the new controller.

v NOPROMPT is an optional parameter that overrides

the user prompt.

Supported operating systems: Windows, NetWare, OS/2, Linux, OpenServer, UnixWare, Open UNIX, and DOS

IPSSEND UNATTENDED controller ON/OFF

where:

v controller is the ServeRAID controller number (1–12) v ON enables the feature v OFF disables the feature

Supported operating systems: Windows, NetWare, OS/2, Linux, OpenServer, UnixWare, Open UNIX, and DOS

Using the IPSMON command-line program (NetWare only)

This chapter provides the information about starting and using the IPSMON command-line program.

You can use the IPSMON program to monitor a ServeRAID controller for defunct drives, Predictive Failure Analysis (PFA) warnings, rebuild operations, FlashCopy operations, synchronizations, logical-drive migrations, and RAID level-5E compressions. Whenever activities occur, this program can log a message to the screen, to a file, or to both the screen and a file.

You can use the IPSMON program with Novell NetWare 5.x only.

This utility program is provided on the IBM ServeRAID Support for Novell NetWare diskette.

Complete the following steps to run the IPSMON program:

1. From the console, type the following:

load ipsmon

2. Press Enter.

When you start IPSMON, it immediately begins polling all ServeRAID controllers for specific conditions. If a condition is found, this program logs a message to the screen, to a file, or to both the screen and a file.

50 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Note: IPSMON continuously polls the ServeRAID controllers until you type unload

ipsmon at the system console.

Command: ipsmon options

where options is one of the following optional parameters: v -F:filename to specify the name of the file in which to record messages. The

default file name is IPSMON.LOG.

v -S to display messages on the standard output (usually the screen). v -? to obtain a current list of valid parameters.

Note: If you start this program without any command-line parameters, the IPSMON

program will log the messages to the IPSMON.LOG file, and the messages will not be displayed on the screen.

During operation, IPSMON logs various messages. Each message contains an alert code and a location specifier.

v The alert code begins with the message type and number:

– INF (information) followed by the message number – WRN (warning) followed by the message number – CRT (critical) followed by the message number

v The location specifier comes after the alert code:

– A followed by the controller number – C followed by the channel number (if required) – SID followed by the SCSI ID (if required)

For example, a message of CRTxxx:A2C3SID04 signifies that a Critical condition (CRTxxx) was found on Controller 2 (A2), Channel 3 (C3), SCSI ID 4 (SID04).

The IPSMON program can log the following messages, based on the condition being monitored and errors detected.

Information Messages:

<Date and Time> INF000:A1C-SID-- (no errors detected) <Date and Time> INF001:A1C-SID-- (rebuild started) <Date and Time> INF002:A1C-SID-- (rebuild completed) <Date and Time> INF003:A1C-SID-- (synchronization started) <Date and Time> INF004:A1C-SID-- (synchronization completed) <Date and Time> INF005:A1C-SID-- (migration started) <Date and Time> INF006:A1C-SID-- (migration completed)

Warning Messages:

<Date and Time> WRN001:A2C3SID12 (PFA error detected)

Critical Messages:

<Date and Time> CRT001:A3C2SID04 (dead drive detected) <Date and Time> CRT002:A1C-SID-- (controller is not responding to

commands)

Using utility programs 51

52 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

IBM ServeRAID cluster solution

A cluster is a group of independent computer systems that work together as a single logical system. A client interacts with a cluster as though it is a single server. In other words, a cluster is a group of computers linked together in such a way that they share and manage a set of resources that can support a number of users at the same time.

This high-availability clustering solution is based on a two-server cluster, where both servers can access the same storage devices, but only one server at a time controls the storage devices shared by both servers. If one of the two running servers fails, the remaining server automatically assumes control of the shared resources managed by the failed server while still controlling its own resources at the same time. Then, the failed server can be repaired offline without the loss of time or work efficiency, because the shared data and applications earlier managed by the failed server are still online to the clients.

When the failed server is operational again, it can be placed back into the cluster; the resources are reallocated between the two servers and the cluster resumes normal operation.

A controller is a device that coordinates and controls the operation of one or more input and output devices, such as workstations, and synchronizes the operation of such devices with the operation of a system as a whole.

The IBM ServeRAID Cluster Solution, as discussed in this book, uses one of the following controllers:

v IBM ServeRAID-4H Ultra160 SCSI controller v IBM ServeRAID-4M Ultra160 SCSI controller v IBM ServeRAID-4Mx Ultra160 SCSI controller v IBM ServeRAID-4L Ultra160 SCSI controller v IBM ServeRAID-4Lx Ultra160 SCSI controller

The IBM ServeRAID Cluster Solution also uses IBM expansion enclosures, such as the following:

v IBM Netfinity EXP15 Rack Storage Enclosure v IBM Netfinity EXP200 Rack Storage Enclosure v IBM Netfinity EXP300 Rack Storage Enclosure

Note: You can configure only 13 physical drives in an EXP300 enclosure.

You can install the IBM ServeRAID Cluster Solution by using one of the following software applications:

v Microsoft Cluster Server, which is part of Windows NT Server Enterprise Edition v Microsoft Cluster Server, which is part of Windows 2000 Advanced Server

Edition.

The following figures show an example of a simple high-availability clustering solution. The first figure shows a high-level view of a cluster; the second figure shows a more detailed view of a cluster.

Clients

Public Network

Crossover

Cable

(Heartbeat)

SCSI Bus

Server A Server B

Expansion Enclosure

Figure 22. A high-level view of a cluster

Server A

Drive

Array A

233 MHz

6 4

SCSI IDs

Channel 2

EtherJet ServeRAID

See Note A See Note B

Power Cord Power Cord

Crossover Cable (Heartbeat)

Channel 1 Channel 1

Repeater

Arrays

UPS

Server A

CD-ROM

RAID - 1

Integrated

Ethernet

Controller

Figure 23. A detailed view of a cluster

Note A: Server A

v Shared Channel 1 - SCSI ID 6 v Non-shared Channel 2 - SCSI ID 7

Public Network

B0B1B

HSP

_ _

345

CCC

HSP

_ _

1112 13

3518 Enclosure

UPS

Expansion

Server B

Unit

SCSI IDs

Repeater

Server B

6 4 3

Channel 2

EtherJet

ServeRAID

233

MHz

CD-ROM

Drive

RAID - 1

Array A

Integrated

Ethernet

Controller

Note B: Server B

v Shared Channel 1 - SCSI ID 7 v Non-shared Channel 2 - SCSI ID 7

54 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

The solution you use for your installation depends on your specific requirements. For more information about requirements and types of installations, see the IBM Shared Disk Clustering Hardware Reference. You can obtain this publication from the IBM Support Web site. See “Obtaining ServeRAID updates” on page 61 for additional information.

ServeRAID considerations

It is important to understand the following ServeRAID considerations before you set up your high-availability cluster solution.

Hardware considerations

v You must cable the SCSI channels in a controller pair so that the controllers

share the same channels.

v You must connect all disks that will be shared to the shared channels. This

includes hot-spare drives, as well as data drives.

v Each shared physical drive must be part of a logical drive or defined as a hot

spare to one or the other servers. You must remove all other physical drives from the shared disk enclosure to ensure proper operation.

v Do not connect nondisk devices, such as CD-ROM or tape drives, to shared

channels. These devices will be accessible to both servers, and conflicts might arise.

Controller considerations

v Controller pair is a term that refers to two controllers, one in each system, that

are connected to each other through the same SCSI bus.

v Each ServeRAID controller must have a different SCSI initiator ID assigned to

the shared channels. For example, set one server, Server A, to ID 6, and set the other server, Server B, to ID 7. The setup instructions describe this in more detail.

v You must set the stripe-unit size of each ServeRAID controller in a pair to the

same value (8 KB, 16 KB, 32 KB, or 64 KB).

v Each ServeRAID controller must have a unique controller name assigned. v Do not change the controller name on both ServeRAID controllers in a pair at the

same time. Doing so can cause problems and might require that you restart the server.

v You cannot share hot-spare drives between controllers in a cluster pairing. If you

want hot-spare protection, each ServeRAID controller must have a hot-spare drive defined. You must connect hot-spare drives only to shared channels. Both servers must be able to access their uniquely-defined hot-spare drives in case a failover occurs after a hot-spare drive replaces a failed shared drive.

v Physical drives that are configured by one controller in the pair must appear as

ready drives to the other controller in the pair. Be sure to verify this criterion when you add drives. Restart both servers, or scan for new devices using the ServeRAID Manager program on both servers, to make sure the added physical drives appear as ready drives on both servers before creating logical drives.

Array or logical drive considerations

v Create only one logical drive for each array. v Every logical drive that is shared by the two servers must have its write-cache

mode set to write through; this will help ensure that data integrity is maintained.

IBM ServeRAID cluster solution 55

For logical drives that are not shared between the two servers, set the write-cache mode to write back; this will improve performance.

v You must assign merge-group numbers in the range 1–8 to each logical drive

that will be shared. Merge-group numbers must be unique for each shared logical drive in the cluster. You must assign merge-group numbers 206 or 207 to the non-shared logical drives.

v If you are starting (booting) the operating system from a shared controller, define

the first logical drive as the startup drive and assign a merge-group number for a non-shared drive, for example, 206 for Server A.

v The total number of logical drives per controller must be eight or less before or

after a failover. If you exceed this number, a failover will not be completed.

v The following logical drives will not failover:

– Logical drives currently undergoing Logical Drive Migration (LDM) operations – RAID level-5E logical drives undergoing compression or decompression – RAID level-5 or level-5E logical drives in a critical state

However, all other logical drives will failover if necessary.

v The ServeRAID controller does not permit the failover of RAID level-5 or level-5E

logical drives that are in a critical state. For this reason, do not use RAID level-5 or level-5E for the quorum drive. You must configure the quorum drive as a RAID level-1 logical drive.

Note: Define hot-spare drives in your array to minimize the time that logical

drives remain in critical state.

v If a failover occurs while a critical RAID level-1, level-1E, level-10 or level-1E0

logical drive is rebuilding to a spare disk, the rebuild operation automatically restarts.

v The cluster support software will initiate a synchronization of all RAID level

logical drives except for the following: – RAID level-0 logical drives – Any critical or offline logical drives.

If a drive fails before this synchronization is complete, logical drive access is blocked and is no longer accessible.

v When a logical drive spans multiple SCSI channels and a failure within the drive

subsystem occurs that is unique to a channel (for example, a disconnected cable), the entire physical array will be identified as failed even though access from the surviving server can occur. Therefore, if you have small arrays, consider not spanning multiple channels.

56 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Monitoring and updating an IBM ServeRAID cluster solution

You can use the ServeRAID Manager program to check the ownership of a physical drive on another server or to add or remove a logical drive in the cluster. The ServeRAID Manager program supports three features for cluster functions:

v View shared drives v Validate cluster v Configure for clustering

Note: Make sure that you installed the ServeRAID Manager program on your

server. For instructions, see the IBM ServeRAID User’s Guide.

Checking the ownership of a physical drive

A physical drive that is owned (and configured) on Server B will appear in the ready or defunct state on Server A. Complete the following steps to determine whether a ready drive is owned by the other server:

1. In the ServeRAID Manager tree, click the controller that contains the ready drives. A window similar to the following opens.

Figure 24. ServeRAID Manager window

2. Click Actions → Clustering actions → View shared drives. The “View shared drives” window opens.

3. Click Enable view shared drives.

4. Select the SCSI channel and SCSI ID of a physical drive on a shared channel.

5. Click OK. Physical drives that are available for use are labeled Ready in the

tree. If the physical drive is not available for use (that is, it is owned by the other server), the drive is labeled Reserved in the tree.

Important: Hot-spare drives owned by the other server are not labeled

Reserved. Be sure you do not inadvertently use a hot-spare drive in both servers.

Adding logical drives to a cluster

Complete the following steps to add logical drives to a cluster:

1. Install the hard disk drives in the server or shared expansion enclosure. For installation information, see the documentation that is included with the hard disk drive and the server.

Important: Physical drives that are configured by one controller in the pair

must appear as ready drives to the other controller in the pair. Be sure to verify this status when you add drives after the servers are started. Before creating logical drives, restart both servers, or scan for new drives using the ServeRAID Manager program on both servers, to make sure the added physical drives appear as ready drives on both servers. For more information, see “ServeRAID considerations” on page 55.

2. Using the ServeRAID Manager program, configure the physical drives for the ServeRAID controller. For instructions, see “Configuring the ServeRAID controller” on page 28.

Note: If the drives will be shared, define only one logical drive per array.

3. In the ServeRAID Manager tree, click the controller for the cluster.

4. Click Configure for clustering on the toolbar. A window similar to the following opens.

Figure 25. “Configure for clustering” window

5. Click Shared or Non-shared for the logical drive you have just defined.

6. Select the merge-group number that you want to use for the logical drive you just defined.

58 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

7. Click OK.

8. If you are using Windows NT 4.0, continue by creating additional ServeRAID disk resources on a Windows NT 4.0 ServeRAID cluster (see the IBM ServeRAID User’s Guide for more information).

If you are using Windows 2000, continue by continue by creating additional ServeRAID disk resources on a Windows 2000 ServeRAID cluster (see the IBM ServeRAID User’s Guide for more information).

Validating a cluster

Use the Validate cluster feature to determine whether your cluster is configured correctly.

Note: You must have the ServeRAID Manager program installed and running on all

Complete the following steps to validate a cluster:

1. In the ServeRAID Manager tree, click a server in the cluster.

2. Click Actions → Validate cluster. A window similar to the following opens.

servers in the cluster for this feature to work.

Figure 26. “ServeRAID cluster validation” window

The server you selected in step 1 is listed in the Node A field.

Note: You cannot change the Node A system in the “ServeRAID cluster

validation” window. To select a different system, click Cancel to return to the ServeRAID Manager tree.

3. From the Node B menu, select your second server.

Monitoring and updating an IBM ServeRAID cluster solution 59

Note: The Node B system defaults to the first system in the tree other than the

Node A system. If there are no remote systems in the tree, click Cancel to return to the tree and add a remote system. You can also type the Node B name.

4. Click Start. The ServeRAID Manager program scans both systems to verify the

ServeRAID cluster configuration. The progress indicator reports the progress of the validation.

5. If you want to stop the validation before it is completed, click Cancel.

Otherwise, if the ServeRAID Manager program finds problems with the ServeRAID cluster configuration, it reports the problems in the Problems found message field. If there are no problems with the ServeRAID cluster configuration, the message field reports only the cluster pairings found.

6. To view the problem report events in an easy-to-read window, double-click an

event in the Problems found message field.

7. To save the contents of the Problems found message field, click Save. A “Save as” window opens. Specify the file name for the message field log and click OK.

8. Click Done to exit the “ServeRAID cluster validation” window. If the ServeRAID cluster configuration has problems, fix the problems; then, use Validate cluster again.

Viewing merge-group numbers and other cluster information

Complete the following steps to view the merge-group numbers and other cluster information:

1. In the ServeRAID Manager tree, click the controller you are using for the cluster.

2. Click Configure for clustering on the toolbar. A window similar to the following opens.

Figure 27. “Configure controller for clustering” window

Note: In this case, you can view this information only. You cannot change the

information.

60 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Maintenance and troubleshooting

Obtaining ServeRAID updates

IBM periodically makes updated versions of the ServeRAID software available from the IBM Support page on the World Wide Web.

Complete the following steps to locate files:

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

2. In the Search field at the top of the page, type ServeRAID; then, press Enter.

Note: If you download ServeRAID software, you must download and install all

ServeRAID software at the same time. This will ensure that all levels of the software are compatible. The ServeRAID software includes the following:

v BIOS and firmware code v Device drivers v ServeRAID Manager program v Command-line programs

If you do not have access to the World Wide Web, contact your place of purchase, your IBM reseller, or your IBM marketing representative for replacement CDs.

Updating BIOS and firmware code

Before configuring the ServeRAID controller, you must have the latest BIOS and firmware code installed on your server. Complete the following steps to update the levels of BIOS and firmware code:

1. Insert the IBM ServeRAID Support CD into the server CD-ROM drive, and turn on the server.

The IBM ServeRAID ROM Update Wizard automatically starts. The IBM ServeRAID ROM (read-only memory) Update Wizard is a program that updates the BIOS and firmware code on ServeRAID controllers. The wizard automatically identifies and scans each ServeRAID controller.

If the BIOS and firmware code do not require updating, the wizard automatically stops and the ServeRAID Manager program starts. Continue with “Configuring the ServeRAID controller” on page 28.

If the BIOS and firmware code require updating, a report screen opens with the following information:

v Controller types found. v Controller slot number, if known. v Firmware version. v BIOS version. v Update status. If a controller has outdated BIOS or firmware code, the IBM

ServeRAID ROM Update Wizard marks the controller as a candidate for update.

The IBM ServeRAID ROM Update Wizard asks if you want to update. You decide whether to update, but you must update all or none of the controllers in your server; you cannot selectively update.

2. If you want to update your ServeRAID controllers, click Update. If the wizard detects an error, an error message appears and you are prompted to insert a diskette into your diskette drive. The wizard saves details about the error to a file on the diskette.

If you do not want to update your ServeRAID controllers, click Cancel.

3. When all updates are completed, scroll through the Features window. This window reports the changes that the IBM ServeRAID ROM Update Wizard applied to your ServeRAID controllers.

4. Leave the IBM ServeRAID Support CD in the CD-ROM drive; shut down and restart the server.

Upgrading a ServeRAID controller

This section contains instructions for upgrading a ServeRAID controller. The following table displays possible upgrade scenarios.

Existing controller Upgrade to

ServeRAID-II ServeRAID-II Yes Yes Yes ServeRAID-3 No Yes Yes ServeRAID-4 No No Yes ServeRAID-5i No No No

Upgrade to ServeRAID-3

Upgrade to ServeRAID-4

Backward compatibility is not supported. In addition, you must usually upgrade to a controller with the same or greater number of channels; upgrading to a controller with fewer number of channels is possible only if the new controller contains as many or more channels than those actually used on the original controller.

You must select a ServeRAID controller that meets the conditions outlined above. After updating the device driver, BIOS and firmware code, and utility programs, you can replace the older controller with the new controller and copy the configuration from the physical drives.

Notes:

1. When upgrading an existing system, you must update the device driver before flashing the controller with the new BIOS and firmware code.

2. This procedure assumes that you are replacing an existing ServeRAID controller in a fully functioning system.

Updating device drivers, BIOS and firmware code, and utility programs

Complete the following steps to upgrade the device driver, BIOS and firmware code, and utility programs:

1. Install the device driver for the new ServeRAID controller. For more information, see the IBM ServeRAID Device Driver Installation Instructions (DEVDRV51.PDF) on the IBM ServeRAID Support CD.

2. Update the BIOS and firmware code for your existing ServeRAID controller, using the IBM ServeRAID Support CD that came with the new controller. For more information, see “Updating BIOS and firmware code” on page 61.

3. If the IPSSEND command-line program is currently installed on the server, upgrade to the latest version. For more information, see the IBM ServeRAID User’s Guide.

4. Upgrade or install the ServeRAID Manager program. For more information, see the IBM ServeRAID User’s Guide.

5. Ensure that the server is functioning properly before continuing to “Replacing the old controller” on page 63.

62 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Replacing the old controller

Complete the following steps to replace the old controller:

1. Shut down the server.

2. If the controller is a ServeRAID-4x: a. Make note of which SCSI cables were attached to specific channels. b. Remove any cables from the old controller; remove the controller. c. Insert the new controller into a PCI slot. If possible, use the PCI slot in

which the old controller was inserted.

d. Attach the SCSI cables to the new controller.

Note: If the new controller has the same number of channels as the old

controller, attach storage devices to the same channels as used previously.

3. If the controller is a ServeRAID-5i:

a. Remove the ServeRAID-5i controller. b. Insert the new ServeRAID-5i controller in the same extended PCI slot as the

one that was just removed.

4. Insert the IBM ServeRAID Support CD into the server CD-ROM drive, and turn

on the server. The IBM ServeRAID ROM Update Wizard automatically starts. If the BIOS and firmware code do not require updating, the wizard automatically

stops, and the ServeRAID Manager starts. Go to step 5. If necessary, update the BIOS and firmware code for the new controller. Leave

the IBM ServeRAID Support CD in the CD-ROM drive; shut down and start the server.

5. After the ServeRAID Manager program starts, click the new controller in the left

pane.

6. Click Actions → Restore to factory-default settings.

7. Click Actions → Copy configuration from drives.

8. Shut down the server, and remove the IBM ServeRAID Support CD from the

CD-ROM drive.

9. Restart the server.

Maintenance and troubleshooting 63

64 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Symptom-to-FRU index

This index supports ServeRAID-4H, -4L, -4Lx, -4M and-4Mx Ultra 160 SCSI controllers, and ServeRAID-5i Ultra 320SCSI controllers.

The Symptom-to-FRU index lists symptoms, errors, and the possible causes.

The purpose of this index is to allow the servicer to determine which FRUs may need to be replaced at the conclusion of troubleshooting procedures.

Note: Do not replace any FRU until you have followed the POST (ISPR) Error

Procedures (see “POST (ISPR) error procedures” on page 93). Only replace a ServeRAID-4H, -4L, -4Lx, -4M, -4Mx or -5i controller if indicated to do so in the POST (ISPR) Error Procedures.

xxx in the following table is used as a placeholder and may be any letter or number in an actual error message.

Error FRU/action

1xxx (Microcode checksum error)

2xxx (Code DRAM error)

3000-31XX (Code DRAM error)

3200 (Code DRAM error)

3300 (ServeRAID-5i only)

3E20 (ServeRAID-5i only)

3E2x

4xxx thru 5xxx (Code DRAM error)

1. ServeRAID controller

1. Install download jumpers, flash latest level BIOS and firmware for controller. Remove jumpers.

2. ServeRAID controller.

1. Install download jumpers, flash latest level BIOS and firmware for controller. Remove jumpers.

2. ServeRAID controller.

1. Install download jumpers, flash latest level BIOS code and firmware for controller. Remove jumpers.

2. ServeRAID controller.

1. Install ServeRAID-5i controller in an extended PCI expansion slot. See the documentation that came with the server for more information.

1. Remove the ServeRAID-5i controller from its slot and install it in the proper PCI option slot.

2. Verify that the ServeRAID-5i controller is supported in this server.

3. ServeRAID-5i controller.

4. System board (refer to the Hardware Maintenance Manual for your system).

1. Reseat the ServeRAID controller.

2. Flash latest level of BIOS code and firmware for controller.

3. ServeRAID-5i controller.

4. Integrated RAID controller on server (refer to the Hardware Maintenance Manual for your system).

1. Install download jumpers, flash latest level BIOS code and firmware for controller. Remove jumpers.

2. ServeRAID controller.

Error FRU/action

6xxx (Cache DRAM error) (ServeRAID-4H only)

7xxx thru 8xxx (Host/local PCI bus interface error)

9003

9xxx thru BZxx (SCSI bus error caused by cables, termination, defective drives, etc.). Z refers to the specific channel or channels that cause the error. See “Drive state descriptions” on page 113.

EFFE (Firmware code corrupt or download jumpers are in place)

FFFF or other code not listed

1. Reseat daughter card.

2. Install download jumpers, flash latest level BIOS code and firmware for controller. Remove jumpers.

3. ServeRAID controller.

1. Flash latest level of BIOS code and firmware for controller.

2. If ServeRAID-4x controller, replace controller.

3. If ServeRAID-5i controller, integrated RAID controller on the server (refer to the Hardware Maintenance Manual for your system).

1. Flash latest level of BIOS code and firmware for controller.

2. Confirm that this controller is a supported option for this system.

3. ServeRAID controller.

4. Integrated RAID controller on the server (refer to the Hardware Maintenance Manual for your system).

1. Follow indications at “POST (ISPR) error procedures”

on page 93. Follow those instructions before

continuing with the next steps listed in this index.

2. SCSI cable.

3. SCSI backplane.

4. Hard drive.

5. ServeRAID controller.

1. Flash latest level BIOS and firmware for controller. Remove jumpers.

2. ServeRAID controller.

1. Follow indications at “POST (ISPR) error procedures”

on page 93.

2. SCSI cable.

3. SCSI backplane.

4. Hard disk drive.

5. ServeRAID controller.

66 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Parts listing

The following table lists the ServeRAID-4x and 5i controller parts and provides the FRU number.

Table 1. Part name and FRU for ServeRAID-4H

Part name FRU P/N

Base card assembly 37L6892 Daughter card assembly (Japan only) 19K0561 Daughter card assembly 37L6902 Battery (Japan only) 00N9561 Battery 37L6903 ServeRAID Support CD 19K0577 ServeRAID Support CD (Japan) 19K0578

Table 2. Part name and FRU for ServeRAID-4L

Part name FRU P/N

Card assembly 09N9540 ServeRAID Support CD 19K0579 ServeRAID Support CD (Japan) 19K0580

Table 3. Part name and FRU for ServeRAID-4Lx

Part name FRU P/N

Card assembly 06P5741 ServeRAID Support CD 19K6131 ServeRAID Support CD (Japan) 24P2925

Table 4. Part name and FRU for ServeRAID-4M

Part name FRU P/N

Card assembly 37L7258 Card assembly (Japan only) 00N9543 Battery 37L6903 Battery (Japan only) 00N9561 ServeRAID Support CD 19K0579 ServeRAID Support CD (Japan) 19K0580

Table 5. Part name and FRU for ServeRAID-4Mx

Part name FRU P/N

Card assembly 06P5737 Card assembly (Japan only) 06P5739 Battery 37L6903 Battery (Japan only) 00N9561 ServeRAID Support CD 19K6131

Table 5. Part name and FRU for ServeRAID-4Mx (continued)

Part name FRU P/N

ServeRAID Support CD (Japan) 24P2925

Table 6. Part name and FRU for ServeRAID-5i

Part name FRU P/N

Card assembly 32P0016 Battery 25P3482 ServeRAID Support CD 33P2640

68 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Recovery procedures

This section includes information on the recovering from certain problems.

IBM ServeRAID Support CD warning message while starting

If you start a server with the IBM ServeRAID Support CD in the CD-ROM drive, the following warning message might be displayed:

You passed an undefined mode number. Press <RETURN> to see video modes available, <SPACE> to continue or wait 30 secs

Press the Spacebar to continue starting the IBM ServeRAID Support CD. The following message appears, and the CD starts:

Uncompressing Linux... Ok, booting the kernel.

Recovering from problems starting the ServeRAID Manager

Problem Explanation Action

The ServeRAID Manager program hangs on the splash screen.

When starting the ServeRAID Manager, the following error message is displayed:

Unable to find load file RAIDMAN

When starting the ServeRAID Manager, the following error message is displayed:

-autounload is an invalid parameter

When starting the ServeRAID Manager, the following error message is displayed:

ERROR: Unable to find Java

You might be using an old version of the ServeRAID device driver.

The ServeRAID Manager program was not installed to the root directory of the SYS volume.

You are using an old version of the Novell Java Virtual machine (JVM).

The Novell Java Virtual machine (JVM) is not installed on your server.

™

Upgrade the ServeRAID device driver to the latest version. More information about installing ServeRAID device drivers is available in the IBM ServeRAID User’s Guide.

Reinstall the ServeRAID Manager. If the installation is completed properly, there will be a directory called RAIDMAN under the root directory of the SYS volume.

Download and install the latest JVM from the Novell Web site: http://developer.novell.com/ndk/download.htm

Problem Explanation Action

The ServeRAID Manager program fails to start, and the following error message is displayed:

Can’t find class com.ibm.sysmgt.raidmgr.mgtGUI. Launch

Your TCP/IP hosts file is not configured for the local server hostname.

Configure your TCP/IP hosts file for the local server hostname.

1. Open the /etc/hosts file.

2. If TCP/IP networking is configured, complete the following steps:

a. If the hostname of the server is

b. On a new line, type the IP address of

c. Press the Tab key to the second

d. Press the Tab key to the third column

3. If TCP/IP networking is not configured, type the server name in the third column of the line that starts with 127.0.0.1. Note: The following is an example of a completed line:

127.0.0.1 localhost matrix

identified on the line starting with

127.0.0.1, remove the hostname from this line.

the server.

column and type the fully qualified hostname.

and type the nickname for the server. Note: The following is an example of a completed line:

1.1.1.1 matrix.localdomain matrix

where 1.1.1.1 is the IP address of the server and matrix is the hostname of the server.

where matrix is the server name.

4. Restart the server for these changes to take effect.

Recovering from an incomplete format of a physical drive

During formatting of a physical drive, if the format process is stopped by a system reset, system shutdown, power outage, or by some other means, the physical drive becomes inoperable.

Complete the following steps to enable the physical drive to communicate with the ServeRAID controller again:

1. Note the channel of the ServeRAID controller to which the physical drive is connected.

2. Note the SCSI ID of the physical drive.

3. Use the ipssend format function to restart the format of the physical drive. The syntax is: ipssend format controller channel sid

where:

v controller is the ServeRAID controller number (1–12) v channel is the channel number for the device (1–4) v sid is the SCSI ID for the device (0–15)

70 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

After the format process is complete, the ServeRAID controller will be able to recognize the drive again.

Channel troubleshooting procedures

Note: The ServeRAID-5i controller does not have any physical channel connectors;

it uses the system’s onboard integrated controller’s channel connectors. All references to channels in these troubleshooting procedures are in regard to the integrated controller physical connectors for the ServeRAID-5i only. Logically, these channels are the same as the other ServeRAID controllers.

This procedure should be used when there is a problem on the SCSI channel outboard of the controller that prevents the controller from communicating with the devices attached to that channel.

1. For non-hot-swap systems, check termination of identified channel.

2. Check for proper cabling configuration in systems that use DASD status cables.

3. To determine if a single drive is causing the failure, disconnect one drive at a time and reboot the system each time. Continue until you have disconnected all the drives, or the failure has disappeared.

4. Replace SCSI cable.

5. Replace SCSI backplane.

6. If the controller is a ServeRAID-4x, replace the controller.

7. If the controller is a ServeRAID-5i, refer to your system’s Hardware Maintenance Manual or User’s Guide.

Dead channel service procedure

Use this procedure when, on one or more channels, all configured (ONL/HSP) drives are shown as DDD, and all RDY/SBY/DHS devices are shown as EMP.

Before continuing, verify that the hard drive enclosure is powered on. If the drives in the enclosure have been marked DDD because the enclosure was powered off, power-on the enclosure, then import the configuration from the drives by performing the following actions:

1. Press CTRL+I during POST to enter the Mini-Configuration program.

2. Choose Advanced Functions.

3. Choose Import Configuration.

The dead channel service procedure is listed in the following steps:

001 IS THIS A SERVERAID-5i CONTROLLER?

YES: Follow “Channel troubleshooting procedures”. NO: Go to step 002

002 DOES THIS SERVERAID CONTROLLER HAVE MORE THAN

ONE CHANNEL? YES: Go to step 003. NO:

v Follow the channel trouble shooting procedure. See “Channel

record table” on page 101.

Recovery procedures 71

v If serveRAID controller has only one channel and it is failing,

move controller to a different PCI slot. If problem persists, replace the controller.

003 DO THE OTHER CHANNELS ON THE SERVERAID

CONTROLLER HAVE ANY DEVICES CONNECTED? YES: Go to step 004. NO:

v Do not press F5, since this changes the customer’s

configuration.

v Connect the failing channel cable to one of the other channel

connectors on the controller and reboot.

You should get new error messages now for the moved channel in the form of “Following drives not responding...”, and “Following drives found in new location...” If you get “...drives not responding...” and do not get the “...drives in new location...”, there is a problem on the SCSI channel outboard of the controller that prevents the controller from communicating with the devices attached to that channel. Go to “Channel record table” on page 101 to resolve the problem. If you get “...drives not responding...” and “...drives in new location...”, reconnect the cable to the original channel connector and reboot. If original message appears, the original channel on the controller is defective. Replace controller.

004 DOES THE STATUS FOR THESE DRIVES APPEAR CORRECT?

YES: Do not press F5, since this changes the customer’s

configuration. v Disconnect one of the correctly-operating channel connectors at

the controller and connect it to the failing controller channel.

v Reboot the system.

You should get new error messages now for the moved channel in the form of “Following drives not responding...”, referring to original and moved channels, and “Following drives found in new location...”.

If you get the message “...not responding...”, referring to original and moved channels, and do not get the “Following drives found in new location...” message, this channel on the controller is defective. Replace controller. If you get “...new location...”, this channel on the controller is working correctly.

v Connect the original failing channel cable to the connector from

which the working channel was removed and reboot.

If you get the “...drives not responding” message, and do not get the “Following drives found in new location...”, there is a problem on the SCSI channel outboard of the controller that prevents the controller from communicating with the devices attached to that channel. Go to “Channel record table” on page 101 to resolve the problem. If you get the “...drives in new location...” message, the problem has apparently resolved itself. Restore the channel

72 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

connections to original locations and reboot. If the original problem persists, suspect a problem in the mating of the cable and controller connectors.

NO: Status is incorrect for multiple channels. v Verify that devices on channel are powered up and properly

connected.

v Move controller to a different PCI slot.

If problem persists, replace the controller.

Drive replacement (rebuilding a defunct drive)

A physical drive is marked defunct when there is a loss of communication between the controller and the physical drive. This can be caused by any of the following:

v An improperly connected cable, physical drive, or controller v Loss of power to a drive v An improperly assembled SCSI channel in an unsupported configuration v A defective cable, backplane, physical drive, or controller v Connecting unsupported SCSI devices (such as tape drives or CD-ROM drives)

to the same SCSI channel used for an array

In each case, after the communication problem is resolved, a rebuild operation is required to reconstruct the data for the device in its disk array. The ServeRAID controllers can reconstruct RAID level-1, level-1E, level-5, level-5E, level-10, level-1E0, and level-50 logical drives. They cannot, however, reconstruct data stored in RAID level-0 logical drives because RAID level-0 is not redundant. If an array contains only RAID level-0 logical drives, the logical drives in the array are marked offline and the logical drives contain damaged data. You cannot rebuild the logical drives. You must correct the cause of the failure or replace the physical drives; then, you must restore your data.

To prevent data-integrity problems, the ServeRAID controllers set the RAID level-0 logical drives in the affected array to blocked status during the rebuild operation for RAID level-1 or RAID level-5. After the rebuild operation is completed, you can unblock the RAID level-0 logical drives and access them once again. Remember, however, that the RAID level-0 logical drives contain damaged data.

Note: For logical drives in an IBM ServeRAID Cluster Solution:

v Because shared logical drives can have only one logical drive for each

array, blocking a RAID level-0 logical drive during a rebuild operation does not apply to shared logical drives.

v Because non-shared logical drives can have more than one logical drive

for each array, blocking a RAID level-0 logical drive during a rebuild operation does apply to non-shared logical drives.

Recovering from defunct drives

When a physical drive is marked as defunct and it is not part of an array, it has been replaced in the array that it had formerly belonged to with a new physical drive. Run the ServeRAID diagnostics that can be started from the server’s diagnostics by starting the server and pressing the F2 key when prompted. If the diagnostics do not log an error for the physical drive, set the drive to the ″ready″ state using the IPSSEND programs SETSTATE command (see “Error-recovery

Recovery procedures 73

functions” on page 45). If successful, it can now be made part of a new array or set up as a hot spare drive using that same command.

If a physical drive fails in an array or multiple physical drives fail in separate arrays (one physical drive per array), complete the following steps:

1. Replace each defunct physical drive. The ServeRAID controller starts the rebuild operation when it detects the removal and reinsertion of a drive that is part of an array.

Note: (For a configuration that contains a hot-spare drive) If you replace a

failed physical drive, it is not necessary to position the new physical drive on the same SCSI channel and SCSI ID as the original hot-spare drive. The replacement physical drive is automatically incorporated into the configuration as a hot-spare drive. Here is an example of how this works:

a. The original configuration consists of a RAID level-5 logical drive

composed of four physical drives. The physical drives are connected to SCSI channel 1; they are assigned SCSI IDs 0, 1, 2, and 3. SCSI ID 3 is a hot-spare drive.

b. The physical drive at Channel 1, SCSI ID 2, fails; the logical drive

enters the critical state. c. The hot-spare drive at Channel 1, SCSI ID 3, is rebuilt into the array. d. You remove the failed physical drive at Channel 1, SCSI ID 2, and

replace it with a new physical drive. The new physical drive at

Channel 1, SCSI ID 2, is automatically assigned to be a hot-spare

drive.

2. If a rebuild operation is in progress, wait until the rebuild is complete. Otherwise, go to step 3.

Note: If you are replacing multiple defunct drives, you must wait for each

rebuild operation to complete before starting subsequent rebuild operations.

3. Verify the cables, physical drives, and controllers are installed properly.

4. Attempt to rebuild the defunct physical drive by performing a hot-swap rebuild. See “Rebuilding a hot-swap drive” for instructions.

5. If the hot-swap rebuild fails, use the system diagnostics to test the ServeRAID subsystem. Press F2 to start diagnostics. If the diagnostics fail, refer to the Hardware Maintenance Manual for the server and find the error codes to determine which component is to be replaced.

Note: Be sure to use the most recent diagnostic tests available for the server.

Rebuilding a hot-swap drive

A hot-swap rebuild refers to a rebuild operation that is started by the ServeRAID controller when it detects that a drive that is part of an array and in the defunct state has been removed and reinserted on the SCSI cable or backplane. The reinsertion of the physical drive, whether it is the same drive or a new drive, will trigger the ServeRAID controller to start the rebuild operation. During the rebuild operation, the drive being rebuilt is in the rebuild state, and the logical drive remains critical until the rebuild operation has been successfully completed.

On IBM servers, when a hot-spare drive is available, the rebuild operation begins automatically without the need to replace the failed drive. If more than one drive fails within the same array, no rebuild takes place. If multiple drives fail in separate

74 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

arrays (one physical drive per array), the controller initiates a rebuild operation for the logical drives within the array containing the first failed physical drive. This rebuild operation is performed on the first hot-spare drive of sufficient size to become a valid member of the array.

Complete the following steps to start a hot-swap rebuild:

1. Without removing the drive completely, gently remove the physical drive from the server, using the handle of the hot-swap tray. If necessary, see the documentation that comes with your server for information about removing a physical drive.

Attention: When power is removed from a hot-swap drive, the drive immediately parks the heads, locks the actuator in the “landing zone,” and begins spinning down. However, the spinning down of the disk might require up to 20 seconds after power is removed. Do not move the drive while it is spinning down. Moving the drive while it is spinning down might damage the drive.

2. Wait 20 seconds to allow the physical drive to completely stop spinning.

3. If you are certain there is nothing wrong with the physical drive you removed, gently reinstall the drive into the server. Make sure the drive is completely installed in the backplane connector.

Otherwise, replace the physical drive with a new drive that is the same size (or larger) and continue with the rebuild operation.

Notes:

a. If multiple drives fail in separate arrays (one physical drive per array),

replace each defunct physical drive. If multiple physical drives fail at the same time within the same array, see “Recovering from multiple physical drive failures (Windows only)”.

b. Although it is possible to rebuild a defunct physical drive to an online

physical drive that is defective, avoid doing so.

Recovering from multiple physical drive failures (Windows only)

Important:

v There is no guarantee that this procedure will recover data. v This procedure requires a ServeRAID-3 or ServeRAID-4 controller with BIOS and

firmware at version 4.x or later installed prior to the physical drive failures.

v Repeat this procedure for each array that contains multiple physical drives

marked defunct.

The ServeRAID controller is designed to tolerate a single physical drive failure in an array. Although there is no guarantee that intact data can be recovered after a multiple physical drive failure in an array, the following procedure offers the possibility of a successful recovery in the event that multiple physical drives are marked defunct within the same array.

You will need the following:

v An IBM ServeRAID Support CD, version 4.80 or later. v A diskette containing the IPSSEND command-line program. This can be either

downloaded from the IBM Web site or created using the IBM ServeRAID Support CD.

Recovery procedures 75

v A version of DUMPLOG and CLEARLOG appropriate for your operating system.

You can download both programs from the IBM Support Web site at http://www.ibm.com/pc/support

Notes:

1. If you have downloaded a newer version of the IBM ServeRAID Support CD, do not upgrade the BIOS and firmware until you have completed this procedure.

2. The following procedures rely upon logging functions introduced in version 4.0 of the IBM ServeRAID Support CD. The ServeRAID controller must have had BIOS and firmware version 4.x or later installed prior to the multiple physical drive failure.

This procedure involves the following steps:

1. Capturing the ServeRAID logs

2. Isolating and removing the failed physical drive

3. Checking the hardware connections

4. Setting defunct drives to the online state

5. Accessing the critical logical drives

6. Finishing the procedure

Capturing the ServeRAID logs

Complete the following steps to capture the ServeRAID logs:

1. Run DUMPLOG.BAT to capture the ServeRAID logs. Do one of the following: v If the operating system is located on the failed logical drive, complete the

following steps: a. Copy the DUMPLOG.BAT and CLEARLOG.BAT files to the root of the

ServeRAID diskette. b. Start the server from the ServeRAID command-line diskette. c. At the prompt, type the following:

DUMPLOG filename controller

where filename is the name of the text file and controller is the ServeRAID controller number (1-12)

v If the operating system is accessible, complete the following tasks:

a. Copy or extract the DUMPLOG utility appropriate for your operating

system to a local directory or folder. b. Run the DUMPLOG command appropriate for the operating system and

save the output to a text file.

2. Trained service technicians can refer to the logsfor root-cause analysis. The logs provide the best evidence for determining the cause of the failure.

Isolating and removing the failed physical drive

To use ServeRAID Manager to determine the order in which drives were marked defunct, complete the following steps:

1. Start ServeRAID Manager in startable-CD mode.

2. In the ServeRAID Manager tree, right-click Local system.

3. Click Save printable configuration and event logs; then, press Enter. A window opens, listing the name and location of the log file.

4. Click OK.

76 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

5. Open the log file in a text editor. The ServeRAID defunct drive event log lists all physical drives marked defunct; the most recent failure is shown at the bottom of the list.

6. Review the list to determine which physical drive failed first. If you cannot determine which drive failed first, go to step 7 on page 78 of “Accessing the critical logical drives.″

Notes:

a. The ServeRAID defunct drive event log might contain entries from earlier

incidents of defunct drives. Review the list of defunct drives carefully, and use the date and time stamps to identify the first drives associated with this incident.

b. In certain circumstances, the ServeRAID defunct drive event log does not

list the drives in the exact order that the drives failed. For example, when an array spans multiple ServeRAID channels, the ServeRAID controller issues parallel I/O requests to devices on each channel. In the event of a catastrophic failure, physical drives might be marked defunct at the same time.

7. Remove the first physical drive marked defunct from the backplane or disconnect the SCSI cable from the drive.

8. Exit ServeRAID Manager; then, shut down the server.

Checking the hardware connections

While the server is turned off, complete the following tasks:

1. Reseat the ServeRAID controllers.

2. Reseat the SCSI cables and the disks against the backplanes.

3. Reseat the power cables to the backplane and SCSI backplane repeater options, if they are present.

As you are reseating the components, visually inspect each piece for bent pins, nicks, crimps, pinches, or other signs of damage. Take extra time to ensure that each component snaps or clicks into place properly.

Setting defunct drives to the online state

Complete the following steps to set the defunct drives to the online state:

1. Start the server.

2. Insert the IBM ServeRAID Support CD into the CD-ROM drive.

3. Use ServeRAID Manager to delete all hot-spare and standby-hot-spare drives. This will prevent a rebuild operation from starting.

4. Set each defunct physical drive in the failed array to the online state. The failed logical drives should change to a critical state. If there are problems bringing physical drives online, or if a physical drive initially goes online and then fails to a defunct state soon after, see “Troubleshooting” on page 78. The logical drives must be in a critical state before you proceed.

Accessing the critical logical drives

Complete the following steps to attempt to access the critical logical drives:

1. If you are still in ServeRAID Manager, exit and restart the server.

2. Attempt to start the operating system. If you are prompted to perform any file-system integrity tests, skip the tests.

Recovery procedures 77

3. If the operating system starts, run the IPSSEND getbst command on each logical drive. This will determine if the bad stripe table has incremented on a logical drive. If there are one or more bad stripes, data is lost or damaged.

4. Run a read-only, file-system integrity check on each logical drive.

5. Using application-specific tools, run more intensive integrity tests on each logical drive.

6. If all tests pass, you can assume that the data is good. Go to “Finishing the procedure”. Otherwise, weigh the results of the file-integrity tests and determine how best to proceed. Your options include the following:

v Use a recent backup to restore damaged files. v Use a recent backup to restore damaged files; schedule a planned outage to

rebuild the data at a later date.

v Restore or rebuild the data.

7. Restore or rebuild the missing data on each critical logical drive if any of the following problems persists:

v The critical logical drive remains inaccessible. v Data errors are found on the critical logical drives. v The operating system continuously fails to start properly. v Partition information on the critical logical drives is unknown.

Finishing the procedure

Complete the following steps:

1. Initiate a backup of the data.

2. After the backup is completed, replace the physical drive that was removed in step 7 on page 77. The new physical drive must be equal to or greater in size than the original drive. An auto-rebuild operation will start.

3. If necessary, redefine the hot-spare drives.

4. Using DUMPLOG, capture another set of ServeRAID logs.

5. Clear the ServeRAID logs using the following CLEARLOG.BAT command available on the DUMPLOG Web site:

CLEARLOG controller

where controller is the ServeRAID controller number (1-12).

6. Using DUMPLOG, capture the ServeRAID logs after two to three days of normal activity. Trained service technicians can refer to the logs to determine whether the ServeRAID controller and SCSI bus activities are operating properly.

Troubleshooting

If you continue to experience problems, review the following information. It might help you identify the configuration or hardware problem.

Poor signal quality across the SCSI bus

The most common cause of multiple physical drive failures is poor signal quality across the SCSI bus. As the SCSI protocol tries to recover, the overhead increases. As the system becomes busier and demand for data increases, the corrective actions of the SCSI protocol increase, and the SCSI bus moves toward saturation. This overhead will eventually limit the normal device communication bandwidth. If left unchecked, one or more SCSI physical drives might not respond to the ServeRAID controller in a timely way, which will result in the ServeRAID controller marking the physical drives defunct.

78 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Poor signal quality problems can be caused by any of the following:

v Improper installation of the ServeRAID controller in a PCI slot v Poor cable connections v Poor seating of hot-swap drives against the SCSI backplane v Improper installation or seating of backplane repeaters v Improper SCSI bus termination

Isolating hardware problems

You can use the following techniques to isolate most hardware problems: v Check error codes within the ServeRAID Manager when a physical drive fails to

respond to a command. Research these codes in the Hardware Maintenance Manual and Troubleshooting Guide for your server.

v In non-hot swap systems, make sure the physical drives are properly attached to

the cable connectors. Start with the connector closest to the SCSI terminator and work your way forward to the connector closest to the controller. Examine each SCSI device and ensure that it has the proper jumper settings.

v While the server is turned off, reseat the ServeRAID controller in its PCI slot and

all cables and disk devices on the SCSI bus.

v Examine the cables for bent or missing pins, nicks, crimps, pinches, or

over-stretching.

v Temporarily attach the physical drives to an integrated SCSI controller, if

available. Start the BIOS. As the BIOS POST runs, review the status of the physical drives and the negotiated data rates. Determine if it is correct.

From the BIOS, choose an option which will list all the devices attached to the controller. Select one of the physical drives and initiate a media test. This will test the device and the entire SCSI bus. If you see errors on the integrated SCSI controller, try to determine if it is the physical drive or the cable by initiating a media test on other physical drives. Test both online and defunct physical drives to determine if the test results are consistent with the drive states on the ServeRAID controller. You can also move hot-swap physical drives to a different position on the backplane and retest to see if the results change.

If the problem persists, swap out the SCSI cable and run a media test again on the physical drives. If the physical drives pass the test, the previous cable is bad. This is a valuable technique for isolating a failing component in the SCSI path.

Note: Depending on the rate at which it negotiates data with low-voltage

differential (LVD) SCSI devices, an integrated controller might produce different results than the ServeRAID controller.

v Use the system diagnostics to test the ServeRAID subsystem. Press F2 to start

diagnostics. If the subsystem fails the test, disconnect the physical drives from the ServeRAID controller; then, reset the controller to the factory-default settings. Run the diagnostic tests again. If the subsystem passes the diagnostics test, then attach the disks to the ServeRAID controller, one channel at a time, and run the tests again to isolate the channel of the failing component. If the controller continues to fail diagnostic tests, refer to the Hardware Maintenance Manual for the server and find the error codes that determine which component is to be replaced.

Note: Be sure to use the most recent diagnostic tests available for the server.

v Disconnect the first physical drive marked defunct from the cable or backplane.

Restore the ServeRAID controller to the factory-default setting. Attempt to import the RAID configuration from the physical drives. Depending on how the failure

Recovery procedures 79

occurred, this technique might have mixed results. There is a reasonable chance that all physical drives will return to an online state, except for the physical drive that is disconnected.

v Move the ServeRAID controller into a different PCI slot or PCI bus and retest.

Notes:

1. When attaching an LVD ServeRAID controller to storage enclosures, set the data rate for the channel to the data rate supported by the enclosure.

2. Mixing LVD SCSI devices with single-ended SCSI devices on the same SCSI bus will switch all devices on the channel to single-ended mode and data rates.

v Trained service technicians can refer to the ServeRAID logs captured on the

system for interpretation to isolate a failing component.

Locating the startup device (SCO OpenServer only)

After installing a ServeRAID controller, SCO OpenServer might fail to find the startup (boot) device.

This problem occurs when your server locates a startup device before coming to the ServeRAID controller on which OpenServer is installed. To solve this problem, consult the documentation that came with your server to determine the PCI slot scan order; then, specify the startup device.

Complete the following steps to specify the startup device:

1. Restart the server.

2. From the prompt, type the following and press Enter:

boot: defbootstr Sdsk=ips(x,0,0,0)

where x is the number of startup devices installed before the ServeRAID controller on which OpenServer is installed.

Solving problems in a failover environment

Use these procedures to recover from problems in a failover environment. Also, you can find hints and tips to help you solve problems on the IBM Support Web site. See “Obtaining ServeRAID updates” on page 61 for additional information.

Recovering from a failure in a failover environment

In a failover environment, when the ServeRAID device driver is unable to send a command to the active controller and the active controller does not respond to a reset command, the device driver attempts to failover to the passive controller.

Note: Loose cables or defective physical drives will not cause a failover to occur.

Replacing a controller of a failover pair in a non-hot-plug PCI slot

Important: Before replacing the failed controller, ensure that you have the latest

device drivers, BIOS, and firmware code installed in your server. Follow the instructions in “Updating device drivers, BIOS and firmware code, and utility programs” on page 62

If a failed controller is not in a hot-plug PCI slot, complete the following steps:

80 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

1. Shut down the server.

2. Replace the failed controller.

Note: Do not attach the SCSI cables to the new controller.

3. Insert the IBM ServeRAID Support CD into the CD-ROM drive; then, turn on the server. The ServeRAID Manager program starts.

4. Select the controller that you just inserted, and click Actions → Restore to factory-default settings.

5. If a confirmation window opens, click Yes. When the operation is complete, a message appears at the bottom of the window indicating that the ServeRAID Manager has successfully restored the configuration to the factory-default settings.

6. Configure the new controller for failover. Click Configure for clustering on the toolbar. The “Configure controller for clustering” window opens.

Figure 28. “Configure controller for clustering” window

7. Type the controller name, partner name, and SCSI initiator IDs that you used for the controller you are replacing.

8. Click OK.

9. Shut down the server.

Important:

When connecting the cables, you must connect the same channel connectors on both ServeRAID controllers to the enclosure. For example, if you connect the cable from Channel 1 on the first ServeRAID controller to the enclosure, you must connect the cable from Channel 1 on the second ServeRAID controller to the enclosure.

10. Connect the enclosure to the new ServeRAID controller.

11. Remove the IBM ServeRAID Support CD from the CD-ROM drive; then, turn on the server.

12. Start the ServeRAID Manager program that is installed on the server; then, confirm that the ServeRAID controllers are correctly configured for failover.

Replacing a controller of a failover pair in a hot-plug PCI slot

If the failed controller is in a hot-plug slot, see the documentation that comes with the server for instructions for replacing the controller.

Note: Windows 2000 does not support the hot-replace feature. For more

information, see “Replacing a controller of a failover pair in a non-hot-plug PCI slot” on page 80.

Recovery procedures 81

For Windows NT 4.0, use the following software to replace the controller. Follow the on-screen directions:

v IBM Netfinity PCI Hot Plug for Windows NT 4.0 Package, version 4.1 or later v (For the ServeRAID-4M, ServeRAID-4Mx, ServeRAID-4L, and ServeRAID-4Lx

controllers only) IBM PCI Hot Plug Adapter Update, version 1.0, for the IBM Netfinity PCI Hot Plug for Windows NT 4.0

v IBM ServeRAID Manager program v IBM ServeRAID Hot Replace Wizard

Recovering from a failed physical drive in a RAID level-5E environment

If a RAID level-5E logical drive undergoes compression as the result of a failed physical drive, the failed drive will be marked defunct hot spare (DHS). Replace the defunct physical drive or remove the defunct drive from the enclosure as soon as possible. If a DHS drive is present, the RAID level-5E logical drive might not failover.

Recovering from a power failure during a failover

If a power failure occurs during a failover, the two controllers in the active-passive pair might have the following problems: v Some logical drives are configured on one controller and some logical drives are

configured on the other controller.

v A logical drive does not appear on either controller.

Complete the following steps to recover from a power failure:

1. Run ipssend merge for every merge-group number configured on the active

controller.

Note: If ipssend merge fails, run ipssend merge partner for every

merge-group number configured on the active controller.

2. Run ipssend unmerge for every merge-group number configured on the

passive controller.

3. Shut down and restart the server. Windows 2000 and Windows NT 4.0 pairs the controllers again.

Troubleshooting an IBM ServeRAID Cluster Solution

There is the possibility that one of the servers, one of the ServeRAID controllers, or one of the hard disk drives in a cluster might fail. This section presents procedures you can take to recover from these potential problems. If you still have problems after following these procedures, see “Symptom-to-FRU index” on page 65. Also, you can find hints and tips to help you solve problems on the IBM Support Web site. See “Obtaining ServeRAID updates” on page 61 for additional information.

Recovering from a failed ServeRAID server

When replacing a failed server in a high-availability configuration, you might not need to replace the ServeRAID controller. However, if you replace your ServeRAID controller, you must reconfigure the controller after installing your new server.

Important: The following procedure requires specific configuration settings for the

ServeRAID controller. If the server and controller that are being replaced are functional, you can obtain these settings from the controller. However, if the controller or the server is not functional, you will need a record of the settings, such as one created when the

82 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

controller was previously configured. If you are replacing your ServeRAID controller at the same time as your server, you must have correct configuration information to complete this procedure.

Complete the following steps to recover from a failed server:

1. Shut down the failed server.

2. Remove all local physical drives from the failed server. As you remove your physical drives, be sure to note the bay in which each drive

was installed. If you are replacing your failed server with an identical server, you can reinstall the drives in an identical configuration and get your server up and running quickly.

3. If the ServeRAID controller is functional, remove it from the failed server. As you remove the controller from the failed server, be sure to note the following: v Which SCSI cables are connected to the SCSI channel connectors on the

controller

v Which PCI slot has the controller installed

4. Install all the local physical drives into the new server, using the location

information you recorded in step 2. For information on how to install a physical drive, see the documentation that

comes with your server. If you are replacing the failed server with an identical server, install each physical drive in the same bay as the one it was removed from in the failed server.

5. If the ServeRAID controller in the failed server is not functional, or if you are not

sure, continue with “Recovering from a failed ServeRAID controller”. Otherwise, perform the following steps with the functional ServeRAID controller: a. Install the controller in the new server. b. Reinstall the cables as they were in the failed server. c. Start the server.

Recovering from a failed ServeRAID controller

You must have the following configuration information to configure your new ServeRAID controller:

v SCSI initiator IDs

The SCSI initiator IDs for a non-shared SCSI channel are set to 7. For shared SCSI channels, the SCSI initiator IDs must be 7 or 6; they must be different from the SCSI initiator IDs for the corresponding SCSI channels of the cluster partner controller. Therefore, if you can obtain the SCSI initiator IDs for the corresponding cluster partner system, you know the correct SCSI initiator IDs for this system. For example, if the cluster partner system-shared SCSI initiator IDs were set to 7, the controller you are replacing would need to have its SCSI initiator IDs set to 6 for the shared channels.

v Controller and partner name

You can also determine the names for the controller being replaced by reading the settings from the cluster partner system.

v Stripe-unit size

The stripe-unit size must be the same on both controllers in a high-availability cluster.

v Unattended mode setting

This setting is configured automatically as Enabled when a controller is set up for clustering.

Recovery procedures 83

If the ServeRAID controller you are replacing is functional, you can obtain the above configuration information by starting your server with the IBM ServeRAID Support CD in the CD-ROM drive and using the ServeRAID Manager program.

Note: The configuration information is also available in the printable configuration

file you might have saved when configuring the ServeRAID controllers for clustering.

If the ServeRAID controller is not functional, you will need to refer to a record of the settings that was made when the controller was previously configured. If you do not have a record of the configuration information, see “Obtaining the current configuration information” for information that might help you to assign the proper values.

Obtaining the current configuration information

To obtain the SCSI initiator IDs, controller name, partner name, and stripe-unit size from the corresponding cluster partner controller, complete the following steps:

1. Click Start → ServeRAID Manager.

Start the cluster partner system with the IBM ServeRAID Support CD in the CD-ROM drive. The ServeRAID Manager program starts.

2. In the ServeRAID Manager tree, click the cluster partner controller.

3. Click Configure for clustering on the toolbar. The “Configure controller for

clustering” window opens.

Figure 29. “Configure controller for clustering” window

4. Note the settings in the fields.

5. To determine stripe-unit size, refer to the information displayed in the right pane of ServeRAID Manager.

Replacing a ServeRAID controller

Complete the following steps to replace a failed ServeRAID controller in your high-availability configuration:

1. Shut down the server.

2. Note which SCSI cables are connected to which SCSI channel connectors on the controller.

84 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

3. Note which PCI slot has the controller installed.

4. Remove the failed ServeRAID controller. For instructions on how to remove and install the ServeRAID controller, see

the installation guide that came with your ServeRAID controller.

5. Install the new ServeRAID controller. Be sure to install the controller in the same PCI slot from which you removed the failed ServeRAID controller.

Important: Observe the following precautions:

v Do not reconnect the SCSI channel cables to the controller at

this time.

v You must ensure that you have the same level of ServeRAID

BIOS and firmware on both controllers in the cluster. The software is available on the IBM Support Web site. See

“Obtaining ServeRAID updates” on page 61 for additional information.

6. Start the system with the IBM ServeRAID Support CD (version 4.0, or later) in the CD-ROM drive. The ServeRAID Manager program starts.

7. In the ServeRAID Manager tree, click the new controller.

8. Click Actions → Restore to factory-default settings. The ServeRAID Manager program initializes the controller configuration.

9. With the new controller still selected in the tree, click Configure for clustering on the toolbar. The “Configure controller for clustering” window opens.

Figure 30. “Configure controller for clustering” window

10. Using the settings that were assigned to the previous ServeRAID controller (that is, the controller you are replacing), complete each of the following fields:

v SCSI initiator IDs v Controller name v Partner name

11. Click OK. The new controller stripe-unit size setting defaults to 8 KB. If you need to change this setting to match the partner controller, go to step 12. Otherwise, go to step 15.

12. In the ServeRAID Manager tree, click the new controller.

13. Click Actions → Change stripe-unit size.

14. Click the new stripe-unit size for your installation.

15. Shut down and turn off the server.

16. Reconnect the SCSI channel cables to the controller.

Recovery procedures 85

Note: Be sure to connect the cables to the correct SCSI channels as noted in

step 2 on page 84.

17. If the ServeRAID controller being replaced is attached to the server startup disk array or other non-shared disk arrays, start the system with the IBM ServeRAID Support CD (version 4.0, or later) in the CD-ROM drive. The ServeRAID Manager program starts.

If the ServeRAID controller being replaced is not attached to any of these items, go to step 21.

18. In the ServeRAID Manager tree, click the new controller.

19. Click Actions → Copy configuration from drives.

20. Click the merge-group number for the non-shared logical drives (that is, 206 or

207).

Note: The last number in the merge-group number is the shared SCSI initiator

ID. That is, if the merge-group number is 206, the SCSI initiator ID is 6.

21. Remove the IBM ServeRAID Support CD from the CD-ROM drive.

22. Restart your server.

Note: If the controller you replaced is the startup controller, the system will

now start the operating system properly.

Recovering from a failover in a Microsoft Cluster Server server

After a failover occurs in a Microsoft Cluster Server server, the red drive lights in external expansion enclosures might turn on for physical drives that are online. There is no hardware problem; the lights turn off within an hour.

Recovering from a failed physical drive in a RAID level-5E environment

Recovering from a failed server in a ServeRAID cluster

Contact IBM technical support for assistance.

Troubleshooting ServeRAID subsystems in a cluster environment

Following is a series of common problems and solutions that can help you troubleshoot your IBM ServeRAID Cluster Solution.

86 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Problem Action

The ServeRAID Manager program shows physical drives in defunct state.

1. Enable the View shared drives feature in the ServeRAID

Manager program. Doing so will display a drive as reserved, instead of defunct, in the following situations:

v A drive has been moved. v A drive has failed-over to the other server in the cluster.

Note: It is normal for drives in the above situations to be displayed as defunct if you have not enabled the View shared drives feature. In this case, the drives shown in the defunct state are not really defective.

2. Check RAID level-1 and RAID level-5 arrays to make sure they are not in critical state. If they are in critical state, replace the failed drive and perform a rebuild operation.

ServeRAID shared logical drives do not failover properly.

1. Ensure that the resource type of each ServeRAID controller shared disk resource is IBM ServeRAID logical disk.

If the resource type is shown as “physical drive,” the localquorum option was not specified properly when MSCS under Windows NT 4.0 was installed.

To correct this problem, you must reinstall the high-availability cluster solution using Microsoft Windows NT.

2. Ensure that shared SCSI buses on the ServeRAID controller pair are connected in the same way that corresponding SCSI channels are connected. For example, SCSI channel 1 on the controller in the first cluster server is connected to SCSI channel 1 on the controller in the second cluster server, channel 2 is connected to channel 2, and so forth.

3. Ensure that the physical SCSI drives that contain logical drives are all connected to shared SCSI channels.

4. Ensure that there are no more than eight shared logical drives defined per pair of ServeRAID controllers.

5. Make sure each shared logical drive has a unique merge-group number assigned. Shared merge-group numbers must be in the range 1–8.

6. Make sure each ServeRAID controller has been assigned a unique controller name and that each ServeRAID controller has its partner name assigned properly to correspond to the ServeRAID controller in the other cluster server that is attached to the shared SCSI buses.

7. Check for loose shared SCSI bus cables.

8. Ensure that the physical drives that are expected to be moved or to failover show up in a ready or reserved state on the server that is attempting to take control of these drives.

Recovery procedures 87

Problem Action

RAID level-5 logical drives cannot be accessed by the operating system after a failover.

If one of the cluster servers fails and the surviving server takes over the cluster resources, occasionally one or more of the IP address resources will stay in the online pending state for several minutes after they are moved over to the surviving server. After this, the resource will go to the failed state, and the following error message will be displayed in the surviving server system log (as viewed with the Event viewer).

Use the ServeRAID Manager program to check the state of the logical drive to ensure that it is not blocked. Using this program, select the logical drive and look for Blocked state Yes. If the logical drive is blocked, make sure all physical drives that are part of the logical drive are in the online state. If all physical drives are not in the online state, a drive might have failed during one of the following situations:

v A failover v A resynchronization process after a failover

Data integrity cannot be guaranteed in this case and the logical drive has been blocked to prevent the possibility of incorrect data being read from the logical drive.

Unblock, reinitialize, and synchronize the logical drive and restore the data from a backup source. Depending on the type of data contained on the logical drive and the availability of a recent backup copy, you can do one of the following:

v Unblock the drive and continue normal operation. v Replace and rebuild one or more defunct drives.

However, if you do not reinitialize, synchronize, and restore the drive, be aware that some data could be lost or damaged.

Complete the following steps:

1. Right-click the IP resource in the Cluster Administrator.

2. From the General page, click Properties.

3. Select Run this resource in a separate Resource Monitor

check box. A message appears stating that the resource must be restarted for the change to take effect.

Note: Placing IPSHA disk resources into their own Resource Monitor can decrease failover time.

For example, the Windows NT Event Log Message:

Date: ??? Event ID: 1069 Time: ??? Source: ClusSvc User: N/A Type: Error Computer: ??? Category: (4)

Description:

Cluster resource ’ip address resource name’ failed

88 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

Problem Action

After one of the cluster servers has been shut down normally and the surviving server takes over the cluster resources, occasionally one or more of the IBM ServeRAID logical drive resources will stay in the online-pending state for several minutes, after they are moved over to the surviving server (when viewed with the Cluster Administrator). After this, the resource will go to the Failed state and the following error message will be displayed in the surviving server system log (as viewed with the Event viewer).

For example, the Windows NT Event Log Message:

Date: ??? Event ID: 1069 Time: ??? Source: ClusSvc User: N/A Type: Error Computer: ??? Category: (4)

Description:

Cluster resource ’IBM ServeRAID Logical Disk name’ failed.

If a previous version of IBM ServeRAID Cluster Solution has been uninstalled, a message is incorrectly displayed prompting you to perform an upgrade when you attempt to reinstall the ServeRAID Windows NT Cluster Solution.

Array identifiers and logical drive numbers might change during a failover condition.

No action is necessary to bring the resource online after the failover. MSCS will bring this resource online on the surviving server within approximately 4 minutes.

You must delete the C3E76E53-F841-11D0-BFA1-08005AB8ED05 registry key. Complete the following steps to delete the registry key:

1. From the Start menu, click Run.

2. Type: REGEDIT and click OK. The Registry Editor window opens.

3. Select HKEY_CLASSES_ROOT\CLSID and delete C3E76E53-F841-11D0-BFA1-08005AB8ED05.

4. Reinstall the ServeRAID Windows NT Cluster Solution. For more information about configuring ServeRAID controllers for clustering, see the IBM ServeRAID User’s Guide.

By design, the array identifiers and logical drive numbers might change during a failover condition. Consistency between the merge-group numbers and Windows NT or Windows 2000 permanent (sticky) drive letters is maintained, while the ordering process during a failover condition is controlled by the Microsoft Cluster Server software and the available array identifiers on the surviving server.

Creating ServeRAID diskettes

Images for the following diskettes are in the \DISKETTE directory of the IBM ServeRAID Support CD. Each of the operating-system specific diskettes contains

device drivers and the IPSSEND utility.

Note: The IPSMON utility is available only on the IBM ServeRAID Support for

Novell NetWare diskette.

Diskette image Diskette

biosfw1.img IBM BIOS and Firmware Update (1 of 3) for the ServeRAID-5i controller biosfw2.img IBM BIOS and Firmware Update (2 of 3) for the ServeRAID-4H,

ServeRAID-II, ServeRAID on-board, and the ServeRAID controllers

Recovery procedures 89

Diskette image Diskette

biosfw3.img IBM BIOS and Firmware Update (3 of 3) for the ServeRAID-4M,

ServeRAID-4Mx, ServeRAID-4L, ServeRAID-4Lx, ServeRAID-3H, and

ServeRAID-3L controllers failover.img IBM ServeRAID Failover Support for Windows NT and Windows 2000 clusnt.img IBM ServeRAID Cluster Solution for Windows NT and Windows 2000 winsrv.img IBM ServeRAID Support for Windows 2000 Server winpro.img IBM ServeRAID Support for Windows (Professional Editions) for

Microsoft Windows XP Professional and Microsoft Windows 2000

Professional os2.img IBM ServeRAID Support for OS/2 winnt.img IBM ServeRAID Support for Windows NT 4.0 netware.img IBM ServeRAID Support for Novell NetWare openunix.img IBM ServeRAID Support for Caldera UnixWare and Open UNIX openserv.img IBM ServeRAID Support for SCO OpenServer redhat1.img IBM ServeRAID Support for Red Hat Linux (1 of 2) for Red Hat Linux,

versions 6.2 and 7.0 redhat2.img IBM ServeRAID Support for Red Hat Linux (2 of 2) for Red Hat Linux,

versions 7.1, 7.2, and 7.3 caldera1.img IBM ServeRAID Support for Caldera OpenLinux (1 of 2) for Caldera

OpenLinux, version 3.1 caldera2.img IBM ServeRAID Support for Caldera OpenLinux (2 of 2) for Caldera

OpenLinux, version 3.1.1 suse.img IBM ServeRAID Support for SuSE Linux turbo.img IBM ServeRAID Support for Turbolinux dos.img IBM ServeRAID Support for DOS

Creating diskettes on Windows

Complete the following steps to create a diskette:

1. Insert the IBM ServeRAID Support CD into the CD-ROM drive.

2. Insert a blank diskette into the diskette drive.

3. At the DOS or command prompt, type the following and press Enter:

e:\diskette\tools\dsk4w32 e:\diskette\disketteimage a:

where

v e is the drive letter for the CD-ROM drive. v disketteimage is the name of the diskette image. v a is the drive letter for the diskette drive.

4. Remove the IBM ServeRAID Support CD from the CD-ROM drive.

5. Remove the diskette from the diskette drive and label the diskette appropriately.

Creating diskettes on IBM OS/2

Complete the following steps to create a diskette:

1. Insert the IBM ServeRAID Support CD into the CD-ROM drive.

2. Insert a blank diskette into the diskette drive.

3. At the OS/2 command prompt, type the following and Press Enter:

90 ServeRAID-4x Ultra160 and ServeRAID-5i Ultra320 SCSI Controllers: Hardware Maintenance Manual

IBM ServeRAID 4Lx Ultra160 Hardware Maintenance Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

About this manual

Important safety information

Online support

Contents

General checkout

General information

Notices that are used in this book

IBM ServeRAID Support CD

ServeRAID ROM Update Wizard

Device drivers

ServeRAID Manager program

IPSSEND command-line program

Diskette images

ServeRAID files needed to install Microsoft Cluster Server (MSCS)

ServeRAID publications

Supported operating systems

Controller features

Connector locations

ServeRAID-4H controller

ServeRAID-4L controller

ServeRAID-4Lx controller

ServeRAID-4M controller

ServeRAID-4Mx controller

ServeRAID-5i controller

Installing and configuring ServeRAID controllers

Using a ServeRAID-4x controller in a server with Active PCI features

Using Windows NT 4.0 with Active PCI features

Using Windows 2000 with Active PCI features

Using NetWare with Active PCI features

Installing the ServeRAID-4x controller

Installing the ServeRAID-5i controller

Preparing for installation

Installing the ServeRAID-5i controller

Replacing the battery pack on the ServeRAID-5i Ultra320 controller

Installing the ServeRAID-5i controller 2-U bracket

IBM Director support for the ServeRAID-5i controller

Connecting external devices to a ServeRAID-4 controller

Configuring the ServeRAID controller

Using ServeRAID Manager

Using Express configuration

Using Custom configuration

Fine-tuning your configuration

Changing the stripe-unit size

Write-cache mode

Viewing your configuration

Getting assistance

Using utility programs

Using the ServeRAID Mini-Configuration program

Accessing the Mini-Configuration program

Viewing the controller status

Viewing the configuration

Using the advanced configuration functions

Using the IPSSEND command-line program

Starting the IPSSEND command-line program

Starting IPSSEND from Windows, NetWare, OS/2, Linux, OpenServer, UnixWare, or Open UNIX

Starting IPSSEND from DOS

Using the IPSSEND command-line program

Server roll-out functions

Error-recovery functions

Problem-isolation and debug functions

RAID configuration functions

Using the IPSMON command-line program (NetWare only)

IBM ServeRAID cluster solution

ServeRAID considerations

Hardware considerations

Controller considerations

Array or logical drive considerations

Monitoring and updating an IBM ServeRAID cluster solution

Checking the ownership of a physical drive

Adding logical drives to a cluster

Validating a cluster

Viewing merge-group numbers and other cluster information

Maintenance and troubleshooting

Obtaining ServeRAID updates

Updating BIOS and firmware code

Upgrading a ServeRAID controller