ICP ICP9014RO, ICP9024RO Installation And User Manual

INSTALLATION AND USER’S GUIDE

ICP VORTEX RAID CONTROLLER

ICP9014RO/ICP9024RO

Copyright

©2005 ICP vortex. All rights reserved. No part of this publication may be
reproduced, stored in a retrieval system, or transmitted in any form or by any
means, electronic, mechanical, photocopying, recording or otherwise, without the
prior written consent of ICP vortex Computersysteme GmbH, Konrad-Zuse-Str.9,
74172 Neckarsulm, Germany.

Trademarks

ICP vortex, the ICP vortex logo, and ICP Storage Manager, are trademarks of ICP
vortex. Adaptec and the Adaptec logo are trademarks of Adaptec, Inc.,which may
be registered in some jurisdictions.

Microsoft, Windows, and Windows NT are registered trademarks of Microsoft
Corporation in the US and other countries, used under license.

All other trademarks are the property of their respective owners.

Changes

The material in this document is for information only and is subject to change
without notice. While reasonable efforts have been made in the preparation of this
document to assure its accuracy, ICP vortex assumes no liability resulting from
errors or omissions in this document, or from the use of the information contained
herein.

Adaptec reserves the right to make changes in the product design without
reservation and without notification to its users.

Disclaimer

IF THIS PRODUCT DIRECTS YOU TO COPY MATERIALS, YOU MUST HAVE
PERMISSION FROM THE COPYRIGHT OWNER OF THE MATERIALS TO
AVOID VIOLATING THE LAW WHICH COULD RESULT IN DAMAGES OR
OTHER REMEDIES.

ii

ICP vortex Customer Support

If you have questions about installing or using your ICP product, check this
document first
further assistance, use the support options listed below.

Support Options

■ For support via Email or phone, contact the ICP Technical Support Specialists at

[e-mail], [phone].

■ For sales information via Email or phone, contact the ICP sales department at

[e-mail], [phone].

Mailing Address

ICP vortex Computersysteme GmbH
Konrad-Zuse-Str.9
74172 Neckarsulm
Germany

Phone

Phone: [phone]

Fax: [phone]

Websites

http://www.icp-vortex.com

http://www.vortex.de

—you will find answers to most of your questions here. If you need

iii

Limited 3-Year Hardware Warranty

1. ICP vortex (“ICP”) warrants to the purchaser of this product that it will be free from defects
in material and workmanship for a period of three (3) years from the date of purchase. If the
product should become defective within the warranty period, ICP, at its option, will repair
or replace the product, or refund the purchaser’s purchase price for the product, provided it
is delivered at the purchaser’s expense to an authorized ICP service facility or to ICP.

2. Repair or replacement parts or products will be furnished on an exchange basis and will
either be new or reconditioned. All replaced parts or products shall become the property of
ICP. This warranty shall not apply if the product has been damaged by accident, misuse,
abuse or as a result of unauthorized service or parts.

3. Warranty service is available to the purchaser by delivering the product during the warranty
period to an authorized ICP service facility or to ICP and providing proof of purchase price
and date. The purchaser shall bear all shipping, packing and insurance costs and all other
costs, excluding labor and parts, necessary to effectuate repair, replacement or refund under
this warranty.

4. For more information on how to obtain warranty service, write or telephone ICP at
Konrad-Zuse-Str. 9, D-74172 Neckarsulm, Germany, [phone].

5. THIS LIMITED WARRANTY DOES NOT EXTEND TO ANY PRODUCT WHICH HAS
BEEN DAMAGED AS A RESULT OF ACCIDENT, MISUSE, ABUSE, OR AS A RESULT OF
UNAUTHORIZED SERVICE OR PARTS.

6. THIS WARRANTY IS IN LIEU OF ALL OTHER EXPRESS WARRANTIES WHICH NOW
OR HEREAFTER MIGHT OTHERWISE ARISE RESPECT TO THIS PRODUCT. IMPLIED
WARRANTIES, INCLUDING THOSE OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NON-INFRINGEMENT SHALL (A) HAVE NO GREATER
DURATION THAN 3 YEARS FROM THE DATE OF PURCHASE, (B) TERMINATE
AUTOMATICALLY AT THE EXPIRATION OF SUCH PERIOD AND (C) TO THE EXTENT
PERMITTED BY LAW BE EXCLUDED. IN THE EVENT THIS PRODUCT BECOMES
DEFECTIVE DURING THE WARRANTY PERIOD, THE PURCHASER’S EXCLUSIVE
REMEDY SHALL BE REPAIR, REPLACEMENT OR REFUND AS PROVIDED ABOVE.
INCIDENTAL OR CONSEQUENTIAL DAMAGES, INCLUDING WITHOUT LIMITATION
LOSS OF DATA, ARISING FROM BREACH OF ANY EXPRESS OR IMPLIED WARRANTY
ARE NOT THE RESPONSIBILITY OF ICP AND, TO THE EXTENT PERMITTED BY LAW,
ARE HEREBY EXCLUDED BOTH FOR PROPERTY DAMAGE, AND TO THE EXTENT
NOT UNCONSCIONABLE, FOR PERSONAL INJURY DAMAGE.

7. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL
OR CONSEQUENTIAL DAMAGES FOR CONSUMER PRODUCTS, AND SOME STATES
DO NOT ALLOW LIMITATIONS ON HOW LONG AN IMPLIED WARRANTY LASTS, SO
THE ABOVE LIMITATION OR EXCLUSIONS MAY NOT APPLY TO YOU.

8. This warranty gives you specific legal rights, and you may also have other rights which vary
from state to state.

iv

Regulatory Compliance Statements

Federal Communications Commission Radio Frequency Interference Statement

WARNING: Changes or modifications to this unit not expressly approved by the party
responsible for compliance could void the user’s authority to operate the equipment.

This equipment has been tested and found to comply with the limits for a Class B digital device,
pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection
against harmful interference in a residential installation. This equipment generates, uses, and
can radiate radio frequency energy, and if not installed and used in accordance with the
instruction manual, may cause harmful interference to radio communications. However, there is
no guarantee that interference will not occur in a particular installation. However, if this
equipment does cause interference to radio or television equipment reception, which can be
determined by turning the equipment off and on, the user is encouraged to try to correct the
interference by one or more of the following measures:

■ Reorient or relocate the receiving antenna.

■ Increase the separation between equipment and receiver.

■ Connect the equipment to an outlet on a circuit different from that to which the receiver is

connected.

■ Consult the dealer or an experienced radio/television technician for help.

■ Use a shielded and properly grounded I/O cable and power cable to ensure compliance of

this unit to the specified limits of the rules.

This device complies with part 15 of the FCC rules. Operation is subject to the following two
conditions: (1) this device may not cause harmful interference and (2) this device must accept
any interference received, including interference that may cause undesired operation.

ICP vortex ICP9014RO/ICP9024RO

Tes ted t o Comp ly
With FCC St an dard s

FOR HOME OR OFFICE USE

European Union Compliance Statement

This Information Technology Equipment has been tested and found to comply with
EMC Directive 89/336/EEC, as amended by 92/31/EEC and 93/68/EEC, in
accordance with:

■ EN55022 (1998) Emissions

■ EN55024 (1998) Immunity:

– EN61000-4-2 (1998) Electrostatic discharge: ±4 kV contact, ±8 kV air
– EN61000-4-3 (1998) Radiated immunity
– EN61000-4-4 (1995) Electrical fast transients/burst: ±1 kV AC, ±0.5 kV I/O
– EN61000-4-5 (1995) Surges ±1 kV differential mode, ±2 kV common mode
– EN61000-4-6 (1996) Conducted immunity: 3 V
– EN61000-4-11 (1994) Supply dips and variation: 30% and 100%

In addition, all equipment requiring U.L. listing has been found to comply with EMC
Directive 73/23/EEC as amended by 93/68/EEC in accordance with EN60950 with
amendments A1, A2, A3, A4, A11.

Australian/New Zealand Compliance Statement

This device has been tested and found to comply with the limits for a Class B digital
device, pursuant to the Australian/New Zealand standard AS/NZS 3548 set out by
the Spectrum Management Agency.

v

Canadian Compliance Statement

This Class B digital apparatus meets all requirements of the Canadian Interference­Causing Equipment Regulations.

Cet appareil numérique de la classe B respecte toutes les exigences du Règlement sur
le matériel brouilleur du Canada.

Japanese Compliance (Voluntary Control Council Initiative)

This equipment complies to class B Information Technology equipment based on
VCCI (Voluntary Control Council for Interface). This equipment is designed for home
use but it may causes radio frequency interference problem if used too near to a
television or radio. Please handle it correctly per this documentation.

vi

1 Introduction

Overview 1-1
Kit Contents 1-2
Overview of the Installation Process 1-2
System Requirements and Compatibility 1-3

Drive Requirements 1-3
Hardware Requirements 1-3
Operating System Compatibility 1-4

Controller Features 1-4

Features Overview 1-4
Features Summary 1-6

Advanced Features 1-6
About the Documentation 1-9
Using the Installation CD 1-9

Booting from the CD With No Operating System 1-10

Using the CD Autorun in Windows 1-10

Browsing the CD 1-11
Installing the Adobe Acrobat Reader 1-11
Software Tools Overview 1-12
Safety Information 1-13

Electrostatic Discharge (ESD) 1-13

Contents

2 Installing the Controller and Drives

Installing the Controller and Drives 2-2
Determining the Boot Controller 2-3
Creating a Bootable RAID 5 Array 2-4

Using the ICP RAID Configuration Utility 2-4

Using the Installation CD 2-6

vii

3 Installing the Driver

Overview of the Driver Installation Process 3-2
Creating a Driver Disk 3-2
Installing the Windows Driver 3-3

Installing the Driver When You Install Windows 3-3

Installing the Driver in an Existing Windows System 3-4
Installing the Linux Module 3-5

Installing the Module When You Install Red Hat or

SuSE 3-5

Installing the Module in an Existing Linux System 3-6
Installing the Unix Driver 3-6

OpenServer 3-6

UnixWare and OpenUNIX 3-8
Installing the NetWare Driver 3-9

Installing the Driver When You Install NetWare 3-9

Installing the Driver in an Existing NetWare System 3-10

Loading NetWare Drivers During Server Restart 3-11

4 Installing and Starting ICP Storage Manager

Installing ICP Storage Manager on Windows 4-2
Installing ICP Storage Manager on Linux 4-3
Installing ICP Storage Manager on OpenServer 4-4
Installing ICP Storage Manager on UnixWare/OpenUNIX

4-5
Installing ICP Storage Manager on NetWare 4-6
Starting ICP Storage Manager 4-7

Windows Operating Systems 4-7
Linux Operating Systems 4-9
OpenServer UnixWare and OpenUNIX Operating

Systems 4-10
NetWare Operating System 4-10

Logging into Remote Systems 4-10

Contents

viii

5 Understanding ICP Storage Manager

Introduction 5-1

Features 5-1

Overview 5-2

Physical Devices View 5-3

Logical Devices View 5-3
Changing How Drives are Displayed 5-4
Collapsed and Expanded Views 5-4
Component Views 5-5

A ICP RAID Configuration Utility

Overview A-1
Using the ACU A-2

Creating Arrays A-2

Managing Arrays A-5

Initializing Drives A-8

Rescanning Drives A-9
Using SCSI

Controller Configuration Options A-10

SCSI Configuration Options A-12
Using Disk Utilities A-14
Viewing the Event Log A-15

Select A-9

Contents

B ACU for DOS

Introduction B-1
Creating the ACU Utility Disk B-1
Running the ACU Interactively B-2
Running the ACU Using Scripts B-3

Playback Mode B-4

Record Mode B-4

Creating the Script File Manually B-5

Array Definition Block Keywords B-6

Channel Definition Block Keywords – SCSI only B-12

ACU Error Codes B-13

Example – Running the ACU with a Script B-14

ix

Contents

C ICP Flash Utility (IFU)

Introduction C-1

System Requirements C-2

Compatibility C-2
Creating the Firmware Floppy Disks C-3
Running the IFU from the GUI C-4
Running the IFU from the Command Line C-5

Command Summary C-5

IFU Command Line – Step-by-Step C-9

D Installing and Using the Command Line Utility

Introduction D-2
Installing ARCCONF D-2

Installing ARCCONF for Windows D-2

Installing ARCCONF for NetWare D-3

Installing ARCCONF for Linux D-4
Starting ARCCONF D-5
Using ARCCONF D-5

Status Functions D-6

RAID Configuration Functions D-7

E About RAID

Simple Volume E-1
Spanned Volume E-2
RAID 0 E-2
RAID 1 E-2
RAID 5 E-3
RAID 10 E-4
RAID 50 E-5

F About SCSI

SCSI Device Support F-1
Setting SCSI IDs F-2
Changing SCSI Termination on the Controller F-2
Enabling CD Drive Support F-3
Mixing SE Devices with LVD Devices F-3

x

G Controller Reset Procedures

Mode 0 Flash G-2

Create a bootable floppy disk G-2

Mode 0 flash Procedures G-2

H Controller Illustrations

LED Function H-2

I Specifications

Glossary

Index

Contents

xi

1

Introduction

In this Chapter...

Overview 1-1
Kit Contents 1-2
Overview of the Installation Process 1-2
System Requirements and Compatibility 1-3
Controller Features 1-4
About the Documentation 1-9
Using the Installation CD 1-9
Installing the Adobe Acrobat Reader 1-11
Software Tools Overview 1-12
Safety Information 1-13

Overview

The ICP9014RO and ICP9024RO are advanced-featured Ultra320
SCSI RAID single-channel and dual-channel controllers. Both are
64-bit/133 MHz controllers with PCI/PCI-X compatibility and
demonstrate unprecedented performance and RAID flexibility. For
a description of features for your ICP controllers, see Controller

Features on page 1-4.

1-1

Introduction

Kit Contents

Your controller kit includes:

■ ICP9014RO or ICP9024RO RAID controller (illustrated in

Appendix H)

■ Installation CD

■ Low-profile bracket

■ Quick Installation Guide

Overview of the Installation Process

This section provides an overview of how to install and configure
the controller:

1 Install and configure the controller and hard disk drives, as

described in Chapter 2, Installing the Controller and Drives.

2 Your next steps depend on your system:

In a system without an operating system (fresh install)...

a Build the bootable array, as described in Creating a Bootable

RAID 5 Array on page 2-4.

b Install the driver at the beginning of the operating system

installation, as described in Chapter 3.

c Install ICP Storage Manager

d View, manage, and build additional arrays, as needed, using

ICP Storage Manager. For an overview, see Chapter 5. For
details, refer to the ICP Storage Manager online Help.

In an existing system that already has an operating system...

a Install the driver.

b Install ICP Storage Manager as described in Chapter 4.

c Build the array using ICP Storage Manager. View, manage,

and build additional arrays, as needed. For an overview, see

Chapter 5. For details, refer to the ICP Storage Manager

online Help.



as described in Chapter 4.

1-2

Introduction

System Requirements and Compatibility

This section summarizes the following system requirements:

■ Drive Requirements

■ Hardware Requirements

■ Operating System Compatibility

Drive Requirements

You need to have enough drives available for the RAID array level
you want to build. For details, see Appendix E, About RAID.

Note: Arrays work best when all array members (drives) are
identical.

Hardware Requirements

The following list summarizes the hardware requirements:

■ Intel Pentium, or equivalent, processor

■ A motherboard that meets the following compatibility

requirements:

– Complies with the PCI Local Bus Specification, Revision 2.2

and higher.

– Supports multifunction devices where one of the devices is a

PCI bridge.

– Provides large memory-mapped address ranges.

Refer to the

Readme file on the installation CD for additional

motherboard compatibility information.

■ At least 128 MB of RAM

■ An available 3.3 Volt 32- or 64-bit PCI or PCI-X slot

■ 20 MB of free drive space

■ 16-bit SVGA color monitor with a resolution of at least 800 x 600

■ CD drive

1-3

Operating System Compatibility

The following operating systems are supported:

■ Windows 2003 Server—Standard and Advanced

■ Windows 2000—Server, Advanced Server, Professional

■ Windows XP—Home Edition and Pro

■ Red Hat Linux—Advanced Server 3.0

■ SuSE Linux—Professional 9.1, and Enterprise Server 9

Note: For the latest on Linux support, or to download
driver sources, visit www.icp-vortex.com.

■

SCO—

– UnixWare 7.13

– OpenServer 5.06a and 5.07

■ Novell—NetWare 6.x

Controller Features

This section contains the following subsections:

Introduction

■ Features Overview

■ Features Summary

■ Advanced Features

Features Overview

The ICP9014RO or ICP9024RO RAID controllers offer the
following features:

■

Supports
support the

■ 64-bit, 66-MHz 3.3V PCI interface compatible with

32-bit/33-MHz 3.3V PCI slots.

■ At least 256 MB of on-board RAM. Some controllers are

available with more RAM.

■ Operating system independent configuration and RAID

creation using the ICP RAID Configuration utility.

PCI Local Bus Specification

PCI-X Addendum

, Revision 1.0a. See page 1-6.

, Revision 2.2. Some models also

1-4

Introduction

■ Flash ROM for easy updates of controller firmware, BIOS, and

ICP RAID Configuration utility. For details on updating the
flash, see Appendix C.

■ Centralized management across all ICP host-based RAID

products using ICP Storage
console access, ICP Storage

Manager

Manager

. In addition to local

provides remote
configuration and management of RAID subsystems through
password-protected access.

■ Event logging and broadcasting, including messaging for

alphanumeric pagers.

■ Optional battery backup module available. For details, see

page 1-9.

1-5

Introduction

Features Summary

The following tables summarizes the features of the ICP SCSI RAID
controllers.

ICP9014RO

Form factor Low-profile Low-profile

PCI compatibility PCI/

PCI bus width (max) 64-bit 64-bit

PCI bus speed (max) 133 MHz 133 MHz

Cache, standard 256 MB 256 MB

Channels 1 2

Devices per channel 15 15

Total dev i c e s 15 30

Connectors, internal (high density) 1 2

Connectors, external

RAID levels 0, 1, 5, 10, 50 0, 1, 5, 10, 50

Simple volume Yes Yes

Spanned volume Yes Yes

Hotspares Yes Yes

Automatic failover Yes Yes

Audible alarm Yes Yes

Battery module option (sold separately)

(VHDCI) 12

PCI-X

ABM-400 ABM-400

ICP9024RO

PCI/
PCI-X

Advanced Features

The ICP9014RO or ICP9024RO RAID controllers
following advanced features:

■

Optimized Disk Utilization

of all your drives, even if drive sizes vary.

■

SCSI Disk Hot Plug

—Allows you to add and remove disks

without shutting down your system.

■ Online Capacity Expansion

■ Array Level Migration

—Allows you to use the full capacity

support the

1-6

Introduction

■ Drive Enclosures

■ Hotspares

■ Audible Alarm

■ Automatic Failover

■ Battery Backup Module Support

Online Capacity Expansion

The ICP9014RO or ICP9024RO RAID controllers support Online
Capacity Expansion (OCE) of existing arrays. With OCE, you can
add new members to increase the capacity of an array without
losing any data. For details, refer to the ICP Storage Manager
online Help.

Windows OCE allows you to use the additional capacity without
restarting the system. For details, refer to your Windows
documentation.

Array Level Migration

The ICP9014RO or ICP9024RO RAID controllers

allow you to
migrate from one array type to another. The migration possibilities
are:

Current Array Type New Array Type

RAID 0 RAID 5 or 10

RAID 1 RAID 0, 5 or 10

RAID 5 RAID 0 or 10

RAID 10 RAID 0 or 5

RAID 50 RAID 0 or 5

For details on how to migrate from one array type to another, refer
to the ICP Storage Manager online Help.

Drive Enclosures

The ICP9014RO or ICP9024RO RAID controllers support drive
enclosures that include SAF-TE enclosure management hardware
per the SAF-TE specification.

1-7

Introduction

Hotspares

The ICP9014RO or ICP9024RO RAID controllers support
hotspares—drives that are reserved to replace a failing drive in a
redundant array. If a drive fails, the hotspare will replace it and the
array is automatically rebuilt. Two types of hotspares can be used:

■ Global—Protects every array that the drive has enough

available capacity to protect.

■ Dedicated—Protects only the array that it has been assigned to

protect.

Audible Alarm

The ICP9014RO or ICP9024RO RAID controllers are equipped with
an audible alarm that alerts you to situations that affect safety of
your data.

Sounding the Alarm

The alarm sounds under the following circumstances:

■ When the controller is running, and a drive fails. For example, if

a drive becomes unplugged, the alarm sounds.

■ When restarting the system, if an array is degraded. For

example, if a drive is missing from a three-drive RAID 5, the
alarms sounds.

■ If an array can’t be configured. For example, if a drive is missing

from a RAID 0, or if two drives are missing from a RAID-5, the
alarm sounds.

Silencing the Alarm

The alarm continues to sound until one of the following actions is
taken:

■ The array with the failed member is deleted.

■ If the array is redundant, a rebuild begins.

The alarm feature can be disabled using SCSISelect or ICP Storage
Manager. For details on disabling it throug SCSISelect, see

page A-11. Also refer to the ICP Storage Manager online Help.

1-8

Introduction

Automatic Failover

The ICP9014RO or ICP9024RO RAID controllers can automatically
rebuild an array when a failed drive is replaced with a new drive.
This feature applies only to redundant arrays in SES- or SAF-TE­enabled drive enclosures. See page A-10 for details.

Battery Backup Module Support

To see the battery module connector location for your controller,
see Appendix H.

About the Documentation

The documentation set for the ICP RAID controllers includes:

■ Quick Installation Guide—Printed guide that summarizes

how to install the controller and create a bootable array.

■ Readme Text File—Contains late-breaking technical

information.

■ Installation and User’s Guide (this book)—PDF file on the

installation CD with complete information on how to install
and configure your controller and attach devices.

■ Online Help—ICP Storage Manager includes an embedded

online Help system that provides details on how to use ICP
Storage Manager to create and manage arrays.

To view the PDF documents, use Acrobat Reader or Viewer. For
details, see Installing the Adobe Acrobat Reader on page 1-11.

For details on using the installation CD, see Using the Installation

CD on page 1-9.

Using the Installation CD

The installation CD contains software, drivers, and documentation.
You can use the CD in the following ways:

■ Booting from the CD With No Operating System

■ Using the CD Autorun in Windows

■ Browsing the CD

1-9

Introduction

Booting from the CD With No Operating System

The installation CD is bootable. You can use it to start a computer that
has no operating system and configure an array.

Note: To use the bootable CD, verify that your computer
supports bootable CDs. To do so, enter system Setup and
check the settings.

Using the CD Autorun in Windows

To use the Autorun executable, autorun.exe, start Windows and
insert the installation CD. Your computer automatically reads the
CD (provided it has been set up to do so).

Note: If your computer does not automatically read the CD,
you can prompt it to read the CD by clicking on
from the CD’s root directory.

The CD presents the following options:

■ Install ICP Storage Manager—Installs the management

software. For details, see Chapter 4.

autorun.exe

■

Install Adobe Acrobat Reader

—Installs Adobe Acrobat Reader
for Windows to let you view the ICP documentation in PDF
format. Versions of Acrobat Reader for other platforms are also
included, see

■ View Release Notes—Displays the Readme file containing the

Installing the Adobe Acrobat Reader

on page 1-11.

latest information for ICP RAID products and software.

■ View Documentation—Provides quick access to the PDF files.

■ Create Driver Diskette—Allows you to create a driver disk for

any supported operating system.

1-10

Introduction

Browsing the CD

If your installation process requires you to directly access files on the
installation CD, you can save time by limiting your browsing to the
following files and folders, available at the root level:

■ Autorun executable—In Windows, click on autorun.exe if your

computer does not automatically execute it when you insert the
CD in the drive.

■

Readme text file

—Contains additional technical information

about device compatibility, operating system support, and drivers.

■ DOCS folder—Contains the user documentation PDF files.

■ PACKAGES folder (and subfolders)—Contains the

management software and device drivers.

■ SOURCES folder (and subfolders)—Contains driver source

files and other components developed under the GNU General
Public License (GPL) agreement.

Installing the Adobe Acrobat Reader

Both Adobe Acrobat Reader and Viewer are provided on the
installation CD. These applications allow you to view PDF files.
Acrobat Reader is also available from Adobe as a free download at

www.adobe.com

.

How you use Reader or Viewer depends on your operating system,
as described below:

■

Windows

—To install Acrobat Reader, choose the appropriate

option from the CD Autorun menu.

■ Linux—Acrobat Reader is located on the installation CD at

mount-point/packages/Linux/RedHat/apps/adobe. Use the full path

name to access this location. If the path gets truncated, you may
not see the correct location.

■ UNIX—Use Acrobat Viewer because Reader is not available for

all operating systems. Your system must have Java Runtime
Environment (JVE) 1.1.7B from April 11, 2000 or later (you can
download it from
installation

java.sun.com). The Viewer is

CD at

mount-point

/Acrobat_Reader

located on the

.

1-11

Introduction

■ NetWare—Acrobat Reader and Viewer are not available for this

operating system or any DOS environment. You need to use a
computer that supports Acrobat Reader or Acrobat Viewer.

Software Tools Overview

The ICP9014RO or ICP9024RO RAID controllers support the
following tools:

■ ICP Storage Manager—Storage management application with

a graphical user interface (GUI). Use this tool to create,
configure, and manage arrays in an environment in which you
have an operating system installed. For details, see Chapters 4
and 5.

■ ICP RAID Configuration Utility—BIOS-based utility that

contains the following components:

– Array Configuration Utility (ACU)—Storage management

utility. Use this BIOS-based utility to create, configure, and
manage arrays on a fresh system on which the operating
system has not yet been installed. Also available as a
DOS-based executable (see next bullet). For details on using
the ACU, see Appendix A. For details on using the DOS­based ACU, see Appendix B.

– SCSISelect—Device management utility. Used to verify the

hardware configuration of the controller and the drives. For
details, see page A-9.

– Disk Utilities—Drive management utility. Used to format

and verify drives. For details, see page A-14.

■ Array Configuration Utility (ACU) for DOS—DOS utility used

to create, configure, and manage arrays. Also available as part
of the BIOS-based ICP RAID Configuration utility. For details,
see Appendix B.

■

ICP Flash Utility (IFU)

—DOS utility used to update, save, or
verify the controller firmware, BIOS, and ICP RAID
Configuration

■ ARCCONF Command Line Program—Allows you to create

utility

versions. For details, see Appendix C.

and manage arrays with ICP RAID Configuration-based ICP
Storage Manager controllers. For details, see Appendix D.

1-12

Introduction

Safety Information

To ensure your personal safety, as well as the safety of you
equipment:

■

Keep your work area and the computer clean and clear of debris.

■ Before opening the system cabinet, unplug the power cord.

■ Observe the safety information of the host system/disk cabinet.

Electrostatic Discharge (ESD)

Caution: ESD is produced by materials that accumulate and

!

retain electrical charges and is transferred to people or other
objects upon contact. It can damage electronic components
when they are improperly handled and can result in total or
intermittent failures. Follow ESD-prevention procedures
when removing and replacing components.

To prevent ESD damage:

■ Use an ESD wrist or ankle strap and ensure that it makes skin

contact. Connect the equipment end of the strap to an
unpainted metal surface on the chassis. If a wrist strap is not
available, ground yourself by touching the metal chassis before
handling the controller or any other part of the computer.

■ Avoid touching the controller against your clothing. The wrist

strap protects components from ESD voltages present on the
body only. ESD voltages on clothing can still cause damage.

■ Handle your controller by its bracket or edges only. Avoid

touching the printed circuit board or the connectors.

■ Place your controller only on an antistatic surface, such as the

bag supplied in your kit.

■ If you plan to return the controller, put it back in its antistatic

bag immediately.

1-13

2

Installing the Controller and Drives

In this Chapter...

Installing the Controller and Drives 2-2
Determining the Boot Controller 2-3
Creating a Bootable RAID 5 Array 2-4

2-1

Installing the Controller and Drives

Installing the Controller and Drives

Use only the latest Ultra320 hard
quality Ultra320-rated cables with multimode terminators for all
drives that share a channel with Ultra320 drives.

To install the controller and drives:

Caution: Take appropriate action to prevent ESD damage. See

!

Safety Information on page 1-13.

1 If you have a low-profile computer cabinet, replace the original

full-height bracket with the low-profile bracket.

2 Turn off your computer.

3 Unplug the power cord.

4 Open the system cabinet.

5 Remove the cover from an available 3.3V PCI or PCI-X slot that

is 2.2 or higher compliant.

Note: You’ll get better performance if you use a 64-bit slot.

6 Install the controller in the PCI (or PCI-X) slot and secure the

controller bracket to the chassis.

7 Install and connect any internal drives using the appropriate

cable.

disk

drives in arrays and only high-

Note: To build a RAID 5, as described in Creating a Bootable

RAID 5 Array on page 2-4, you must install at least three

drives.

8 Close the computer cabinet.

2-2

Installing the Controller and Drives

9 Connect any external cables and drives to the controller.

Notes:

■ Do not attach a cable to the controller unless the other

end of the cable is attached to a proper termination.
Doing so can cause unstable operation.

■ Use high quality cables. Poor quality cables may

degrade system reliability. Avoid cables not rated for
Ultra320 operation.

■ Observe the maximum cable lengths/cable loads for

Ultra320.

■ Use device adapters as needed to connect any single-

ended (SE) drives (avoid mixing old SE and LVD
devices on the same SCSI bus).

■ For additional considerations about installing SCSI

drives, see Appendix F, About SCSI.

Determining the Boot Controller

Note: If your system will contain two or more bootable

controllers, read this section. Otherwise, skip this section.

The ICP9014RO or ICP9024RO RAID controller

s support bootable
drives and arrays. The controller’s default setting and your system
setup usually allow you to install and boot from either a hard disk
drive connected to the motherboard, or from a drive or array
connected to the controller.

If you already have an operating system installed on a hard disk
drive connected to the motherboard and you want to boot a second
operating system from the RAID controller, follow these steps:

1 Enter the system setup.

2 Navigate to the hard disk drive boot sequence.

3 Move the boot controller to the top of the list.

2-3

Installing the Controller and Drives

Creating a Bootable RAID 5 Array

Note: To install an operating system on a drive or array

connected to your ICP9014RO or ICP9024RO RAID
controller, read this section. Otherwise, skip to Chapter 3 to
install the driver in an existing operating system.

This section describes how to create a bootable RAID 5 array with
at least three drives.

Choose one of the following methods:

■ Using the ICP RAID Configuration Utility—Use this method if

you prefer a text-based approach.

■ Using the Installation CD—Use this method if you prefer a

GUI-based approach.

Why build a RAID 5?

This array level provides a versatile combination of performance
and redundancy on a minimum of three drives. Because RAID 5
uses parity, it is the safest, and most recoverable, of all RAID levels.

What if I prefer a different RAID level?

That’s no problem. Once you build your array and install your
operating system, you can change array levels (see Array Level

Migration on page 1-7) or expand the capacity of the array (see
Online Capacity Expansion on page 1-7) to suit your needs.

Using the ICP RAID Configuration Utility

To build a bootable RAID 5 array using the ICP RAID
Configuration utility:

1 Install the controller and drives, as described in Installing the

Controller and Drives on page 2-2.

Note: For a RAID 5, you need at least 3 drives.

2

Turn on the computer, then press
Configuration utility.

The first screen shows all installed ICP RAID controllers.

Ctrl+A

to enter the ICP RAID

2-4

Installing the Controller and Drives

3 Use the arrow keys to highlight the controller you want to use,

then press Enter.

The Menu Options screen is displayed.

4 Highlight Array Configuration Utility, then press Enter.

The ACU Menu is displayed.

5 Highlight Initialize Drives, then press Enter.

6 Highlight at least three drives to be used for the array and press

Insert for each highlighted drive.

The utility displays the selected drives.

7 Press Enter.

A warning message appears—this is normal.

Note: During initialization, all data is deleted from the
disk. Before proceeding, back up any data you want to
keep.

8 Press Y.

The selected drives are initialized, then the ACU Menu is
displayed again.

9 Highlight Create Array, then press Enter.

10

Highlight the three dirves you just initialized for the array, then
press

Insert

for each highlighted drive.

11 Press Enter.

12 On the Array Properties screen, respond as follows to accept

the defaults (shown in parentheses):

Property Line Displayed Entry or Selection

Array Type Select RAID 5, then press Enter

Array Label Type a name, then press Enter.

Array Size Press Enter, then press Enter again to

use the default granularity of GB.

Stripe Size Press Enter (256KB).

Read Caching Press Enter (Yes).

2-5

Installing the Controller and Drives

Property Line Displayed Entry or Selection

Wri t e C aching Press Enter (Enable always).

Create RAID via Press Enter (Build/Verify).

[Done] Press Enter.

13 A cache warning message is displayed. Type Y.

A Creating Array window appears.

14 Once the array is created, a message displays telling you that

the array can now be used. Press any key to return to the ACU
Menu.

Note:

Although you can start using the array immediately,

performance is reduced until the build process is complete.

15 Press Esc until the Exit Utility window appears.

16 Highlight Yes, then press Enter.

The computer restarts.

17

Install the driver as described in Chapter 3.

Using the Installation CD

Note: You cannot create the RAID using a CD drive connected

to the RAID controller.

To build a bootable RAID 5 array using the installation CD:

1 Install the controller and drives, as described in Installing the

Controller and Drives on page 2-2.

2 Start or restart the computer.

3 Insert the installation CD.

Note: If the installation CD does not start automatically,

you may need to enter system setup and enable booting
from the CD. For details, refer to your computer’s
documentation.

2-6

Installing the Controller and Drives

4 Select the appropriate language on the Language screen, then

press Enter. Read the Licenses screen, then press Enter again.

The installation CD main menu is displayed.

5 Select Launch Configuration Utility.

The system launches ICP Storage Manager. The ICP Storage
Manager screen appears similar to the following.

6 Click Create.

7 In the configuration wizard, select Custom.

8 Click the RAID 5 button, then click Next.

9 Click at least three drives to be used in your array.

Each drive you select is marked with a check.

10 Click Next.

11 Type the name you want to assign to the RAID 5 you are

creating, then click Apply.

The system creates the array. The display refreshes to show the
newly-created RAID 5 on the right side of the display. You can
use the array immediately. However, if you want to make the
array bootable you must allow the array to finish building
before restarting the system.

12 When you are ready to continue, close all windows.

The Main Menu is active.

13 Click Reboot to restart your system.

14 Remove the installation CD.

15 If you want to make the array bootable, do so now using the

ICP RAID Configuration Utility. For details, see page A-6.

2-7

3

Installing the Driver

In this Chapter...

Overview of the Driver Installation Process 3-2
Creating a Driver Disk 3-2
Installing the Windows Driver 3-3
Installing the Linux Module 3-5
Installing the Unix Driver 3-6
Installing the NetWare Driver 3-9

3-1

Installing the Driver

Overview of the Driver Installation Process

The following process is recommended to install the driver:

1 Create a driver disk. See Creating a Driver Disk on page 3-2 for

details.

2 Identify the appropriate installation procedure for your

computer.

You need to know the operating system and whether you are
installing the driver while also installing the operating system,
or installing the driver onto a system that already has the
operating system installed.

3 Familiarize yourself with the supported RAID levels. You will

need to select a RAID level during driver installation. See

Appendix E for a summary of the various RAID levels.

Note: If you don’t like your initial RAID level selection, you
can change it later using Array Level Migration. See page

1-7 for RAID levels and the ICP Storage Manager online

Help for details.

4 Read and understand the entire installation procedure.

5 Proceed with the installation.

Creating a Driver Disk

Note:

If you are adding the controller to an existing Linux

system, you do not need to create a driver disk; skip this section.

Before installing the driver, create the driver disk:

1 Set your system BIOS so that your computer boots from the CD

drive.

2 Insert the controller installation CD and turn on the computer.

3 Respond to the on-screen instructions as necessary to get to the

Start Menu.

3-2

Installing the Driver

4 Click Create Driver Disk, then select the appropriate operating

system.

5 If you selected Linux, you must also select the architecture:

– i386—For Intel 386 or 486 computers
– i586—For Pentium I or II computers
– i686—For Pentium III, IV, or AMD K-6 computers
– Athlon—AMD Athlon computers

6 Select the appropriate floppy disk drive letter, then choose the

appropriate format. A full format is required only if the disk has
never been formatted or if it contains bad sectors.

7 Insert a floppy disk, then click OK. The system creates the

driver disk.

8 Remove and label the driver disk.

Now that you have created your driver disk, proceed with the
appropriate driver installation procedure.

Installing the Windows Driver

This section contains the following procedures:

■ Installing the Driver When You Install Windows

■ Installing the Driver in an Existing Windows System

Installing the Driver When You Install Windows

To install the driver while also installing the Windows operating
system, follow these steps:

1 Install and configure the controller and hard disk drives, as

described on page 2-2.

2 Create the bootable array, as described on page 2-4.

3 Create the driver disk, as described on page 3-2. When finished,

remove the driver disk.

4 Insert the Windows setup CD and restart the computer to begin

the Windows installation.

3-3

Installing the Driver

5 When prompted to install a third-party driver, press F6.

Note: When F6 is active, a prompt appears at the bottom of

the screen for only 5 seconds. If you miss your chance to
press F6, restart the computer.

6 Insert the driver disk and wait until prompted to install the

driver. Press S to specify that the driver is on the floppy disk,
then press Enter. The computer reads the disk.

7 When the driver is found, press Enter. Respond to the on-screen

instructions to complete the installation.

Installing the Driver in an Existing Windows System

To install the driver in an existing Windows system:

1 Install and configure the controller and hard disk drives, as

described in Chapter 2.

2 Create the driver disk, as described on page 3-2. When finished,

remove the driver disk.

3 Start Windows. Windows launches the Found New Hardware

Wizard, which searches for the driver.

4 Insert the driver disk, select the floppy drive as the source, then

click Next.

5 Click Next in the two subsequent windows and follow the

on-screen instructions to complete the driver installation.

6 Remove the driver disk and restart the computer.

3-4

Installing the Driver

Installing the Linux Module

This section contains the following procedures:

■ Installing the Module When You Install Red Hat or SuSE

■ Installing the Module in an Existing Linux System

Note: For the most up-to-date information on ICP’s support of
Linux, visit www.icp-vortex.com.

Installing the Module When You Install Red Hat or SuSE

To install the module during a fresh install of Red Hat or SuSE:

1 Install and configure the controller and hard disk drives, as

described on page 2-2.

2 Create the bootable array, as described on page 2-4.

3 Create the driver disk, as described on page 3-2. When finished,

remove the driver disk.

4 Insert the first Red Hat or SuSE installation CD.

5 Restart the computer.

6 When the Red Hat Welcome screen appears, type

Boot: prompt.

expert

at the

7 When prompted, insert the driver disk, then select OK.

8 Follow the prompts to set up your preferred environment.

9 If you are installing other third-party devices, proceed with the

installation of those devices. Otherwise, select Done.

10 Proceed with the Linux installation according to the Red Hat or

SuSE instructions.

3-5

Installing the Driver

Installing the Module in an Existing Linux System

To install the module in an existing Red Hat or SuSE Linux system:

1 Insert and mount the controller installation CD.

2 Install the module RPM by typing:

rpm -Uvh mount-point/xxx/yyy.rpm

where
system,

mount-point

xxx

is the driver path, and

is the specific mount point on the Linux

yyy.rpm

is the rpm file.

3 Run

fdisk, mkfs, and create mount points for any new drives.

Installing the Unix Driver

This section discusses the following systems:

■ OpenServer

■ UnixWare and OpenUNIX

OpenServer

This section contains procedures for installing the driver in
OpenServer systems.

Installing the Driver When You Install OpenServer

To install the driver when installing OpenServer:

1 Install and configure the controller and hard disk drives, as

described in page 2-2.

2 Create the bootable array, as described on page 2-4.

3 Create the driver disk, as described on page 3-2. When finished,

remove the driver disk.

4

Insert the OpenServer installation CD and restart the computer.

The system starts loading from the CD and displays a Boot:
prompt.

5 When you see the

defbootstr link=aacraid

Boot: prompt, insert the driver disk and type

.

6 Follow the OpenServer instructions to complete the installation.

3-6

Installing the Driver

7 When the installation is complete, remove the driver disk and

restart the computer.

8 Insert and mount the controller installation CD.

9 To enable RAID management software and utilities, type the

following commands:

cd mount-point/openserv/arc/driver/aacraid/reloc/tmp/aacraid/scripts
cp ./aacaifd /usr/sbin
cp ./S98aacaifd /etc/rc2.d
chmod 755 /usr/sbin/aacaifd /etc/rc2.d/S98aacaifd

Installing the Driver in an Existing OpenServer System

To install the driver in an existing OpenServer system:

1 Install and configure your ICP RAID controller and hard disk

drives, as described in page 2-2.

2 Create the driver disk, as described on page 3-2. When finished,

remove the driver disk.

3 Boot the server.

4 Insert the driver disk.

5 To run t he

the

installpkg

installpkg utility, open a terminal window and type

command.

OpenServer reads the disk and performs the installation.

6 Rebuild the kernel.

7 Install the new kernel by typing

y

when prompted to make it

the default kernel.

8 Restart the computer.

9 Add devices created on the RAID controller to the operating

system. For details, refer to your OpenServer documentation.

10 Insert and mount the controller installation CD.

11 To enable RAID management software and utilities, type the

following commands:

cd mount-point/openserv/arc/driver/aacraid/reloc/tmp/aacraid/scripts
cp ./aacaifd /usr/sbin
cp ./S98aacaifd /etc/rc2.d
chmod 755 /usr/sbin/aacaifd /etc/rc2.d/S98aacaifd

3-7

Installing the Driver

UnixWare and OpenUNIX

This section contains the following procedures:

■ Installing the Driver When You Install UnixWare or OpenUNIX

■

Installing the Driver in an Existing UnixWare or OpenUNIX System

Note: Although the driver disk you create for UnixWare and
OpenUNIX differ, the installation procedures for these
operating systems are the same.

Installing the Driver When You Install UnixWare or OpenUNIX

To install the driver when installing UnixWare or OpenUNIX:

1 Install and configure the controller and hard disk drives, as

described on page 2-2.

2 Create the bootable array, as described on page 2-4.

3 Create the driver disk, as described on page 3-2. When finished,

remove the driver disk.

4 Insert the Unix installation CD and start the operating system

installation.

5 When you see the prompt, insert the driver disk, select Install

HBA diskette, and then press F10.

The computer loads the driver from the driver disk and
displays the HBA screen.

6 Select Proceed with Installation, then press F10.

7 Complete the installation as appropriate.

8 When the installation is finished, remove the driver disk and

restart the computer.

Installing the Driver in an Existing UnixWare or OpenUNIX System

To install the driver in an existing UnixWare or OpenUNIX system:

1 Shut down the computer. Install and configure the controller

and hard disk drives, as described in Chapter 2.

2 Create the driver disk, as described on page 3-2. When finished,

remove the driver disk.

3 Turn on the computer, then insert the driver disk.

3-8

Installing the Driver

4 To run t he pkgadd utility, type

pkgadd -d diskette1

and then

press Enter. UNIX reads the disk and package information.

5 Press Enter.

6

Restart the computer. The system rebuilds the kernel
automatically.

7 Add devices created on the RAID controller to the operating

system. For details, refer to your OpenServer documentation.

Installing the NetWare Driver

This section contains the following procedures:

■ Installing the Driver When You Install NetWare on page 3-9

■ Installing the Driver in an Existing NetWare System on page 3-10

■ Loading NetWare Drivers During Server Restart on page 3-11

Installing the Driver When You Install NetWare

To install the driver when installing NetWare:

1 Install and configure the controller and hard disk drives, as

described on page 2-2.

2 Create the driver disk, as described on page 3-2. When finished,

remove the driver disk.

3

Restart the computer, then press

Ctrl+A

when prompted to access
the ICP RAID Configuration utility. Use the ICP RAID
Configuration utility to create the RAID. For details, see

ICP RAID Configuration Utility

on page 2-4.

4 Install and configure a secondary controller, if any.

5 Install the operating system according to the NetWare

documentation. Verify that the files

aacraid.ham and aacraid.ddi

are available on the driver disk that you created in Step 2.

During the first part of the installation select Manual install
mode instead of Default to be able to load additional drivers
later. To load additional drivers:

Using the

3-9

Installing the Driver

a select Modify when the Storage adapters are displayed.

b Select Storage adapters and press the Ins key to add an

unlisted driver from the floppy disk.

6 When the Device Types screen appears, check the Storage

adapters list and select Modify to add another driver.

7 Select Storage adapters, then press Enter.

All recognized controllers are displayed.

8 If

AACRAID is detected, delete it.

9 Press Insert to add another driver. The available drivers are

displayed.

10 Insert the driver disk.

11 Press the Enter key to scan the floppy disk drive.

Once the driver is selected, the parameter screen is displayed.

12 Verify the loaded drivers. From the lower window menu, select

Continue, then press Enter.

Note: If the driver installation process fails, the server
console is displayed so you can see the cause of the failure.

Now that you have installed the drivers, refer to your NetWare
documentation to modify disk partitions, apply hot fixes, or
perform volume maintenance. Also see Loading NetWare Drivers

During Server Restart on page 3-11 for a summary of array

management options in NetWare.

Installing the Driver in an Existing NetWare System

To install the driver in an existing NetWare system:

1 Upgrade your NetWare server to the minimum patch level

specified by Novell.

2 Create the driver disk, as described on page 3-2. When finished,

remove the driver disk.

3 Shut down the server.

4 Install and configure the controller as a secondary controller, as

described in Chapter 2.

3-10

5 Start the server.

Installing the Driver

6 At the NetWare server console prompt, type

nwconfig.nlm

and press Enter.

load

7 Select Driver Options and press Enter.

8

Select

Configure disk and storage device drivers

and press

Enter

9 Select Select an additional driver and press Enter.

10 Insert the driver disk, then press the Insert key.

All available drivers are displayed.

11 Press the Insert key again to access additional drivers.

12 Press Enter to scan for the drivers.

13 Select ICP Advanced RAID Controller and press Enter.

The aacraid parameters screen is displayed.

14 Select Select/Modify driver Parameters and press Enter.

15 Select Save parameters and load driver.

16 When prompted to select an additional driver, select No.

17 Press Esc to exit the

Nwconfig utility.

18 Create arrays using the ICP RAID Configuration utility (see

Using the ACU on page A-2) or remotely using ICP Storage

Manager (refer the online Help). Alternatively, you can create
arrays using the ARCCONF Command Line program. ( see

Appendix D, Installing and Using the Command Line Utility).

Now that you have installed the drivers, refer to your NetWare
documentation to modify disk partitions, apply hot fixes, or
perform volume maintenance. See also Loading NetWare Drivers

During Server Restart.

.

Loading NetWare Drivers During Server Restart

To automatically load the aacraid.ham driver during server restart,
the

startup.ncf file (usually located in your server's startup

directory) must contain a load command line that specifies the
location of the driver and any appropriate command line options.

3-11

Installing the Driver

The syntax to load the driver is:

load [pathname]aacraid.ham slot=number [options]

For example, the command to load the driver from the c:\nwserver

directory, with the verbose= option

ON is:

load c:\nwserver\aacraid.ham slot=2 verbose=y

Notes:

■ Command line options are not case sensitive.

■ Placing commas between command line options is

optional.

To mo d ify t he

startup.ncf file:

1 At the server console prompt, type load nwconfig and press

Enter.

2 Select the NCF File Options menu, then press Enter.

3 Select the Modify Startup.ncf option, then press Enter.

4 Make the necessary changes. When you are done, press Esc.

Note: You can also use your DOS text editor to modify the

startup.ncf file, it resides on the DOS partition.

For additional information on the

startup.ncf file, refer to your

NetWare documentation.

3-12

4

Installing and Starting ICP Storage Manager

In this Chapter...

Installing ICP Storage Manager on Windows 4-2
Installing ICP Storage Manager on Linux 4-3
Installing ICP Storage Manager on OpenServer 4-4
Installing ICP Storage Manager on UnixWare/OpenUNIX 4-5
Installing ICP Storage Manager on NetWare 4-6
Starting ICP Storage Manager 4-7
Logging into Remote Systems 4-10

After you have installed the ICP9014RO or ICP9024RO RAID
controller and its driver, you are ready to install and use ICP
Storage Manager—a user-friendly GUI that makes it easy for you
to create and manage arrays without having to restart the
computer and use the BIOS utility.

Note: You need administrator or root privileges to install ICP
Storage Manager. For details on verifying privileges, refer to
your operating system documentation.

4-1

Installing and Starting ICP Storage Manager

Installing ICP Storage Manager on Windows

Notes:

■ On Windows, ICP Storage Manager supports up to 16 ICP

RAID controllers.

■ If a previous version of ICP Storage Manager is installed,

you must remove it before upgrading. To remove ICP
Storage Manager, use the Add/Remove Programs option
in your Windows Control Panel.

To install ICP Storage Manager:

1 Insert the controller installation CD and wait for the

Autorun

executable to start the installation. If this does not occur, browse
the CD and click Autorun.

2 When the installation wizard starts, follow the instructions on

the screen to complete the installation.

Note:

When prompted to install SNMP (Simple Network

Management Protocol), accept the default (

do not install

)
unless you have a specific requirement for ICP Storage
Manager to work with SNMP gets and traps.

4-2

Installing and Starting ICP Storage Manager

Installing ICP Storage Manager on Linux

Notes:

■ With Linux, ICP Storage Manager can be used to manage

up to 12 ICP RAID controllers.

■ ICP Storage Manager includes the JRE.

■ Remove any previous version of ICP Storage Manager.

Any customization files you created when you used the
previous version are saved and used in the upgrade. To
remove ICP Storage Manager, type the

rpm --erase StorMan command.

■ For the latest on ICP’s support of Linux, visit

www.icp-vortex.com.

To install ICP Storage Manager:

1 Insert the controller installation CD.

2 Mount the controller installation CD:

for Red Hat mount /dev/cdrom /mnt/cdrom
for SuSE mount /dev/cdrom /media/cdrom

3 Change to the cdrom directory:

for Red Hat cd /mnt/cdrom/linux/manager
for SuSE cd /media/cdrom/linux/manager

4 Extract the RPM package and install it:

rpm --install ./StorMan*.rpm

5 Unmount the controller installation CD:

for Red Hat umount /mnt/cdr om
for SuSE umount /media/cdrom

4-3

Installing and Starting ICP Storage Manager

Installing ICP Storage Manager on OpenServer

Notes:

■ With OpenServer, ICP Storage Manager can be used to

manage up to 12 ICP RAID controllers.

■

You need either the Java Development Kit (JDK) for SCO or
the JRE for SCO, version 1.3.1. To download these, visit

www.thescog roup.com

■

OpenServer 5.06 only

urwfonts and package set OSR-compatible Version 8.0.1 or
higher, both available on the maintenance CD; OSS643A for
socket driver supplement from the
Release Supplement 5.06a is helpful but not required.

■

If a previous version of ICP Storage Manager is installed,
you must remove it before upgrading. Any customization
files you created when you used the previous version are
saved and used in the upgrade.
Manager, type

To install ICP Storage Manager:

1 Insert the controller installation CD.

2 Mount the controller installation CD:

mount -r -f HS,lower /dev/cd0 /mnt

.

—Requires the following packages:

www.thescog roup.com

To rem o ve I CP St ora g e

pkgrm RaidMan

.

.

3 Install using pkgadd:

pkgadd –a /mnt/openserv/manager/RaidMan.adm –d /mnt/

openserv/manager/RaidMan.ds

4 Follow the instructions on the screen to complete the

installation. When the installation is complete, change to the
root directory:

cd /

5 Unmount the CD drive:

umount /mnt

4-4

Installing and Starting ICP Storage Manager

6 To start RAID Agent, type the following case-sensitive

command:

sh /opt/RaidMan/RaidAgnt.sh

When successful, a copyright message is displayed.

If you want RAID Agent to run at startup all the time, add the
following line to the

nfra:12346:once:sh /opt/RaidMan/RaidAgnt.sh

/etc/inittab and /etc/conf/init.d/kernel files:

Installing ICP Storage Manager on UnixWare/ OpenUNIX

Notes:

■ With UnixWare and OpenUNIX, ICP Storage Manager can

be used to manage up to 12 ICP RAID controllers.

■ You need root privileges to install ICP Storage Manager.

■

You need either the Java Development Kit (JDK) for SCO or
the JRE for SCO, version 1.3.1. To download these, visit

www.thescog roup.com

■ If a previous version of ICP Storage Manager is installed,

you must remove it before upgrading. Any customization
files you created when you used the previous version are
saved and used in the upgrade.
Manager, type

■ If a previous version of ICP Storage Manager is installed,

you must remove it before upgrading. Any customization
files you created when you used the previous version are
saved and used in the upgrade.
Manager, type

.

pkgrm RaidMan

pkgrm RaidMan

To rem o ve I CP St ora g e

.

To rem o ve I CP St ora g e

.

To install ICP Storage Manager on UnixWare or OpenUNIX:

1 Insert the controller installation CD.

2 Mount the controller installation CD:

mount -r -F cdfs /dev/cdrom/cdromdevicefile /mnt

where cdromdevicefile is the device file, for example,

c0b0t010, for the CD-ROM block device. To determine the

actual filename, look in the

/dev/cdrom directory.

4-5

Installing and Starting ICP Storage Manager

3 Use pkgadd to install ICP Storage Manager:

pkgadd -d /mnt/unixware/manager/RaidMan.ds

4

Follow the instructions on the screen to complete the installation.

5 Unmount the CD drive:

umount /mnt

6 UnixWare Only—To start RAID Agent, type the following case-

sensitive command:

sh /opt/RaidMan/RaidAgnt.sh

When successful, a copyright message is displayed in the
terminal window.

If you want RAID Agent to run at startup all the time, add the
following line to the

nfra:12346:once:sh /opt/RaidMan/RaidAgnt.sh

/etc/inittab and /etc/conf/init.d/kernel files:

Installing ICP Storage Manager on NetWare

Notes:

■ With NetWare, ICP Storage Manager can be used to

manage up to 16 ICP RAID controllers.

■

You need the latest Support Pack for your operating system
so you can run the supported Java Virtual Machine (JVM).

■ You need JVM version 1.3 or later. To check your JVM

version, load JVM, type

■ For the latest updates from Novell, visit www.no vell.com.

JAVA -VERSION.

To install ICP Storage Manager on Netware:

1 Insert the controller installation CD.

2 From the command prompt, type

load cdrom and press Enter

if the CD is not mounted automatically.

4-6

Installing and Starting ICP Storage Manager

3 From the command prompt, type:

xx_yy_zz:\netware\manager\install

where xx is the product CD, yy is the version number, and zz is
the release number. For example:

adptcd_v2_01

The installation program starts.

4 Follow the instructions on the screen to complete the

installation.

Starting ICP Storage Manager

Note: You need root privileges to run ICP Storage Manager.

To start ICP Storage Manager, use the following procedures for
your operating system.

Windows Operating Systems

1 To run ICP Storage Manager as a standalone application, click

Start > Programs > ICP Storage Manager.

2 The application flash screen appears briefly. Then the ICP

Storage Manager window opens with a login dialog box
superimposed. Enter a valid user name and password for a user
on the system, and click Connect.

4-7

Installing and Starting ICP Storage Manager

Notes: ICP Storage Manager permissions vary according to
your operating system permisssions:

■ Administrator: Logging in as an Administrator allows you

to view and modify the RAID configuration. You can
create and delete logical drives, verify logical drives,
perform migrations, and add and remove hotspare drives.
To log in as an Administrator, enter a valid user name and
password for the Administrator or an Administrative User
on the system.

The Administrative User is any member of the local
Administrators group, which can (in a Domain
configuration) include Domain Administrators.

■ User: Logging in as a User allows you to view the RAID

configuration, verify logical drives, and add and remove
hotspares. You cannot create or delete logical drives or
perform migrations. To log in as a User, use your normal
network user name and password.

■ Guest: Logging in as a Guest allows you to view the RAID

configuration only. You cannot change or modify any
information. To log in as a Guest, click Cancel on the
Login window.

4-8

Installing and Starting ICP Storage Manager

Linux Operating Systems

1 Change to the ICP Storage Manager installation directory by

typing:

cd /usr/StorMan.

2 Type the following command and press Enter:

sh StorMan.sh

3 The application flash screen appears briefly. Then the ICP

Storage Manager window opens with a login dialog box
superimposed. Enter a valid user name and password for a user
on the system, and click Connect.

Notes: ICP Storage Manager permissions vary according to
your operating permisssions:

■ Administrator: Logging in as an Administrator allows you

to view and modify the RAID configuration. You can
create and delete logical drives, verify logical drives,
perform migrations, and add and remove hotspare drives.
To log in as an Administrator, enter
name and enter the root password.

■ User: Logging in as a User allows you to view the RAID

configuration, verify logical drives, and add and remove
hotspares. You cannot create or delete logical drives or
perform migrations. To log in as a User, use your normal
network user name and password.

■ Guest: Logging in as a Guest allows you to view the RAID

configuration only. You cannot make any changes. To log
in as Guest, click Cancel at the login window.

root for the user

4-9

Installing and Starting ICP Storage Manager

OpenServer UnixWare and OpenUNIX Operating Systems

1 Change to the ICP Storage Manager installation directory by

typing:

cd /opt/RaidMan.

2 Type the following command and press Enter:

sh RaidMan.sh

NetWare Operating System

To start ICP Storage Manager on NetWare, type the LOAD RAIDMAN
command.

Logging into Remote Systems

To log into a remote system:

1 From the menu bar of the ICP Storage Manager main menu,

click Remote > Add Remote System.

The ICP Storage Manager displays the Add Remote system
screen:

2 Enter the IP address.

The default
you.

System startup port number, 34571, is supplied for

4-10

Installing and Starting ICP Storage Manager

3 For Username, enter admin
4 For Password, enter ICP

Note: The username and password are case sensitive.

When you are logged in for the first time, you can add new
accounts and change account passwords. For details, refer to the
online Help.

4-11

5

Understanding ICP Storage Manager

In this Chapter...

Introduction 5-1
Overview 5-2
Changing How Drives are Displayed 5-4
Collapsed and Expanded Views 5-4
Component Views 5-5

Introduction

This chapter provides an overview of ICP Storage Manager, the
user-friendly GUI that you use to create, change, and manage
arrays. For more details on using ICP Storage Manager, refer to its
embedded online Help system.

Features

You can use ICP Storage Manager to:

■ Create and delete arrays

■ Verify arrays

■ Migrate arrays

■ Add and remove hotspares

■ Change RAID level

5-1

Understanding ICP Storage Manager

■ View the RAID configuration

■ View information about managed systems and subsystems

such as arrays, logical drives, hotspare drives, and physical
drives

■ Notify systems of all events occurring on the local system

■ Increase logical device size

■ Manage scheduled tasks such as Verify or Migrate

■ Add or remove a remote system

■ Configure, administer, and monitor controllers that are

installed locally or remotely in your servers or external storage

■ Fine tune controller settings for optimal performance

Note: Some of these features may not be available for your
controller.

Overview

ICP Storage Manager

provides an expandable tree view of the
controllers you are managing. You can perform most configuration
and management tasks by selecting a controller from the tree and
working with related objects. The figure below shows how

ICP
Storage Manager displays information about Physical and Logical
devices

.

5-2

Understanding ICP Storage Manager

Using the buttons in the Physical devices and Logical devices
views, you can:

■ Change how drives are displayed

■ Collapse and expand a view

■ Identify components of a logical device

■ Create and delete hotspares

Physical Devices View

This view displays information about the drives, enclosures, and
other physical devices attached to the controller. The devices are
organized numerically. The display for each channel or port
includes information on maximum speed, the number of the
channels on the controller, and the number of devices attached to
the controller.

Indicators, next to the controller name, report status of the fan and
temperature modules on SAF-TE (enclosure management) devices and
other devices that monitor these conditions. The indicator colors are:

■ Blue—Normal

■ Yel low—Warning

■ Red—Error

■ Gray—Not applicable to the devices.

For example, the fan indicator changes to yellow when one fan
fails; it changes to red when a second fan fails and cooling is no
longer adequate.

Logical Devices View

This view displays information about the logical devices created
using the physical devices, including the number of logical devices,
the RAID level of each device, and whether a logical device is
protected by a hotspare.

You can create and delete logical devices in the Logical devices
view by selecting the Create option and using the Create wizard.

5-3

Understanding ICP Storage Manager

Changing How Drives are Displayed

You can choose how information is displayed in the Physical
devices view by clicking one of the following buttons in the Logical
devices view.

Displays physical device information in text format. This is the
default view.

Displays physical device information in full size capacity format.
A full-length bar is displayed for each drive, regardless of
capacity. A small segment on each drive is reserved for the

signature

Note:

; this area is indicated by a gray

cap

at the end of each bar.

A drive shaded in light blue is not part of any disk group.

Displays physical device information in relative size capacity
format. A full-length bar is displayed for the largest drive;
proportionally shorter bars are displayed for other drives.

RAID

Collapsed and Expanded Views

You can display a collapsed or expanded view of the system
configuration. Initially, ICP Storage Manager displays a collapsed
textual view of the configuration information in both the Logical
devices and Physical devices views.

In the Logical devices view...

Click to expand and collapse information about disk groups and
logical devices. The expanded display shows the following
information about each logical device:

■ Disk group name and capacity (if available)

■ Logical device size

■ Logical device state

■ Build progress

In the Physical devices view...

Click to expand and collapse information about physical drives.
The expanded display shows the following information about
each drive:

■ Capacity of the drive

■ Drive ID

■ Drive state

5-4

Understanding ICP Storage Manager

Component Views

When you click a physical or logical device in the device views, the
related components are highlighted in the other view.

■ When you click a logical device in the Logical devices view, the

physical drives that make up the logical device are highlighted
in the Physical devices view, and vice-versa.

■ When you click a hotspare, the logical devices protected by that

spare are highlighted.

■ In the graphical views, if the logical device uses only part of the

available storage, only those segments are highlighted (in dark
blue).

5-5

A

ICP RAID Configuration Utility

In this Appendix...

Overview A-1
Using the ACU A-2
Using SCSISelect A-9
Using Disk Utilities A-14
Viewing the Event Log A-15

Overview

The ICP RAID Configuration utility is a BIOS-based utility that
includes:

■ Array Configuration Utility (ACU)—Used to create, configure,

and manage arrays, and make arrays bootable. Also used to
initialize and rescan drives. (Also available as a stand-alone
DOS utility as described in Appendix B, ACU for DOS.)

■ SCSISelect—Used to change device and controller settings.

■ Disk Utilities—Used to format or verify media.

To run the ICP RAID Configuration utility, press Ctrl+A when
prompted by the following message during system startup:

Press <Ctrl><A> for ICP RAID Configuration Utility

A-1

ICP RAID Configuration Utility

The ICP RAID Controller menu is displayed, showing the following
available options:

■ Array Configuration Utility

■ SCSISelect Utility

■ Disk Utilities

To select a menu option in the ICP RAID Configuration utility, use
the arrow keys to highlight the menu option you want, then press
Enter. Sometimes, selecting an option displays another menu. To
return to the previous menu at any time, press Esc.

The following sections detail each of the ICP RAID Configuration
utility menu options.

Using the ACU

The Array Configuration Utility (ACU) allows you to perform the
following tasks:

■ Creating Arrays

■ Managing Arrays

■ Initializing Drives

■ Rescanning Drives

Creating Arrays

To create an array:

1 For systems with RAID enclosures—Power up any enclosures.

Note: The ACU may not find disks or enclosures that were

powered up after system power-up. Therefore, power up
enclosures prior to powering up the computer.

A-2

ICP RAID Configuration Utility

2 Shut down and restart the computer.

Note: After you install a controller in a system and start it

for the first time, the BIOS may display a configuration
that does not match your system’s configuration. This is
normal. Proceed with array creation.

3 Press Ctrl+A when prompted to access the ICP RAID

Configuration utility.

4 From the ICP RAID Configuration utility menu, select Array

Configuration Utility.

5 From the ACU menu, select Create Array.

6 Select a channel.

7 Select the disks for the new array, then press Insert. To deselect

a disk, highlight the disk, then press Delete.

ACU displays the largest usable space available for each disk. You
can use available space from multiple disks for the new array.

Note: Disks containing MS-DOS partitions, disks with no
usable space, or disks that are not initialized appear
dimmed and cannot be used in a new array. For
information on how to initialize a drive, see page A-8.

8 When you are finished selecting disks, press Enter.

The Array Properties menu is displayed.

Assigning Array Properties

Note: You can use ACU to assign array properties only if the

array has not yet been built. After the array is built, you must
use ICP Storage Manager to assign properties.

A-3

ICP RAID Configuration Utility

To assign properties to the new array:

1 In the Array Properties menu, select an array type, then press

Enter.

The display shows only the array types available for the
number of drives selected.

The maximum number of drives allowed and minimum
number of drives required depends on the RAID level. For
details, see Appendix E, About RAID.

2 Optional: Type a label for the array, then press Enter.

3 Enter the desired array size.

The maximum array size available based on the partitions you
selected is displayed automatically. If you want to designate a
different array size, type the desired array size and select MB
(megabytes), GB (gigabytes), or TB (terabytes) from the drop­down list. If the available space from the selected partitions is
greater than the size you specify, the remaining space can be
used in other arrays.

4 Select the desired stripe size.

The allowable stripe sizes are 16, 32, 64, 128, 256 KB (the
default), and 512. The default stripe size provides the best
overall performance in most network environments.

5 Specify whether you want to enable read and write caching for

the array.

Caution: Enabling caching optimizes performance.

!

However, when caching is Enabled, there is a risk of data
loss or corruption during a power failure. Therefore, you
should enable caching unless your data is highly sensitive,
or your application performs completely reads, which is
unlikely.

6 When you are finished, select Done.

The array build starts.

A-4

ICP RAID Configuration Utility

Managing Arrays

With the Manage Arrays option, you can perform the following tasks:

■ Viewing Array Properties

■ Making an Array Bootable

■ Deleting Arrays

■ Managing Failover Drive Assignments

Viewing Array Properties

To view the properties of an existing array:

1 From the ACU main menu, select Manage Arrays.

2 From the List of Arrays dialog box, select the array you want to

view, then press Enter.

To view properties related to the array’s physical disks:

– RAID 0, 1, 5 (Single-Level Arrays)—View the Array

Properties dialog box.

– RAID 10, 50 (Dual-Level Arrays)—Highlight the array

member you want to view, then press Enter to display the
second level. Press Enter again to display the physical disks
associated with the array.

Note: Failed drives are displayed in a different color.

3 Press Esc to return to the previous menu.

A-5

ICP RAID Configuration Utility

Making an Array Bootable

Notes:

■

If the controller is not bootable, you can disable its runtime
BIOS. (For details, see the table on page A-10.) When the BIOS
is disabled, it does not occupy any of the expansion ROM
region of the system’s memory map. In a system with several
expansion ROMs, disabling the BIOS may be helpful.

■

The controller always uses the lowest numbered array as its
bootable array. If you delete Array 00, the next lowest
numbered array becomes the bootable array.

■ You cannot make a non-00 array bootable while the array

is in a build/verify or rebuild process.

■ You may need to change the system BIOS to modify the

boot order. For more information, refer to the system
documentation.

You can make an array bootable so that the system boots from the
array instead of from a stand-alone (single) disk. To make an array
bootable:

1 From the ACU main menu, select Manage Arrays.

2 Select the array you want to make bootable, then press Ctrl+B.

This changes the selected array’s number to 00, making it the
controller’s boot array.

3 Restart the computer.

Deleting Arrays

Caution: When you delete an array, you delete all the data

!

from the array. Before proceeding, back up any data you want
to keep.

To delete an existing array:

1 From the ACU main menu, select Manage Arrays.

2 Select the array you want to delete, then press Delete.

A-6

ICP RAID Configuration Utility

3 In the Array Properties dialog box, press Delete, then press

Enter. A warning message appears.

4 Select Yes to delete the array, or No to return to the previous

menu. At the Array Properties dialog box, select Delete again,
then press Enter.

5 Press Esc to return to the previous menu.

Managing Failover Drive Assignments

To assign a hotspare to an array:

1 Select Manage Arrays from the main menu.

2 From the List of Arrays dialog box, select the array to which

you want to assign a hotspare, then press Ctrl+S. The Hotspare
Management for Array dialog box is displayed, which shows
the drives that can be assigned as hotspares.

3 Select a drive, then press Insert to assign the drive as a hotspare.

The specified drive is displayed in the Assigned Hotspares
drives list.

4 Press Enter to save the hotspare assignment.

5 If you are finished managing hotspares, press Y (for yes) when

prompted to return to the main menu.

To remove an assigned hotspare from an array:

1 Select Manage Arrays from the main menu.

2

From the
want to remove the assigned hotspare, then press

List of Arrays

dialog box, select the array from which you

Ctrl+S

. The
Hotspare Management for Array dialog box is displayed, which
shows drives that can be assigned as hotspares and drives that are
already assigned as hotspares.

3 From the Assigned Hotspares drives list, select the drive to be

removed, then press Delete. The specified drive is displayed in
the Select Hotspares drives list.

4 Press Enter to save the removed hotspare assignment.

5 If you are finished managing hotspares, press Y (for yes) when

prompted to return to the main menu.

A-7

ICP RAID Configuration Utility

Initializing Drives

If a correctly installed disk does not appear in the disk selection list
for creating a new array, or it appears grayed out, you need to
initialize it.

Caution:

!

■ During initialization, all data is deleted from the disk.

Before proceeding, back up any data you want to keep.

■ If the drive is already used in an array, initialization may

make the array unusable.

■ Do not initialize a disk that is part of a boot array. The boot

array is the lowest numbered array (normally 00) in the
List of Arrays dialog box. For information on determining
which disks are associated with a particular array, see

Viewing Array Properties on page A-5.

To initialize drives:

1 Restart the computer, then press Ctrl+A when prompted to

access the ICP RAID Configuration utility.

2 From the ICP RAID Configuration utility menu, select Array

Configuration Utility.

3 Select Initialize Drives.

4 Select a channel.

5 Highlight the disk you want to initialize, then press Insert.

6 Repeat Step 5 until all the drives to be initialized are selected.

7 Press Enter.

8 Read the warning message, ensure that you have selected the

correct drives to initialize, and then press Y to continue.

A-8

ICP RAID Configuration Utility

Rescanning Drives

To rescan the drives connected to the controller:

1 Restart the computer, then press Ctrl+A when prompted to

access the ICP RAID Configuration utility.

2 From the ICP RAID Configuration utility menu, select Array

Configuration Utility.

3 Select Rescan Drives.

Using SCSISelect

The SCSISelect Utility allows you to change controller and device
settings without opening the computer cabinet or handling the
controller. To access this utility:

1 Restart the computer, then press Ctrl+A when prompted to

access the ICP RAID Configuration utility.

2 If multiple controllers are installed, select the controller you

want to configure, then press Enter.

3 From the ICP RAID Configuration utility menu, select

SCSISelect Utility.

To select a menu option, highlight it using the arrow keys, then
press Enter. In some cases, selecting an option displays another
menu. To return to the previous menu, press Esc.

To restore the original default values, return to Configure/View
Host Adapter Settings, then press F6.

4 To exit the utility, press Esc until a message prompts you to exit.

If you changed any settings, you are prompted to save the
changes before you exit. Choose Yes to exit and restart the
computer. Any changes you made take effect after restart.

A-9

ICP RAID Configuration Utility

Controller Configuration Options

The Controller Configuration options are described in the table
below.

Models

Option Default

Drives Write
Cache

Runtime BIOS

Automatic
Failover

Array
Background
Consistency
Check

BBS Support Enabled

Drive's
Default

Enabled

Enabled All When

Disabled

Affected

All When

All When

All When

See
note

Description

enabled, providing maximum drive
performance. When
write cache is used on the drive. By
default, the drive’s setting is used.

Caution

slight possibility (less than with
controller cache) of data loss or
corruption during a power failure.

allows the controller to act as a
bootable device. Disabling the BIOS
allows another suitable controller to
act as the boot device.

automatically rebuilds an array
when the failed drive is replaced.
When disabled, the array must be
rebuilt manually.

constantly performs a verification
on a redundant array to data
integrity. In the case of RAID 1 or 10,
consistency checks assure that the
data between like blocks match. In
the case of a RAID 5 or a RAID 50,
consistency checks assure that data
in the stripe and the calculated
parity for the stripe match.
Consistency checking processes
reduce performance. For a RAID 5
or a RAID 50, the performance
reduction is significant.

When

1

support BBS, controller is presented
as a bootable device in the host
system's BIOS for boot device
selection.

Enabled

, write cache is

—When

Enabled

Enabled

Enabled

Enabled

Enabled

, the controller BIOS

, the controller

, the controller

in systems that

Disabled

, there is a

, no

A-10

Models

Option Default

Array-based
BBS Support

Physical
Drives Display
during POST

CD-ROM Boot
Support

Removable
Media Devices
Support

Alarm Control

1. BBS systems containing SCSI controllers only.

Disabled

Disabled

Enabled

Enabled

Enabled

Affected

All When

All When

SCSI
only

SCSI
only

All When

Description

support BBS, the controller presents
attached bootable devices up to the
host system's BIOS for boot device
selection. This is relevant for logical
arrays.

devices are displayed during system
POST. Displaying the devices adds a
few seconds to the overall POST
time.

When
booted from a bootable CD.

When
devices, such as CD drives and Zip
drives, are supported.

ICP RAID Configuration Utility

Enabled

in systems that

Enabled

, attached physical

Enabled

, the system can be

Enabled

, removable media

Enabled

, the alarm sounds.

A-11

ICP RAID Configuration Utility

SCSI Configuration Options

To access the SCSI Device Configuration options, select SCSI
Configuration.

SCSI Channel Interface Definitions

The SCSI Channel Interface Definitions are described in the
following table.

Option Default Description

Controller SCSI
Channel ID

SCSI Parity
Checking

Controller SCSI
Channel
Te rm in a ti on

7

Enabled

Auto
Mode

Sets the controller’s SCSI ID. ICP
recommends that you leave the controller set
to the default, which gives it the highest
priority on the SCSI channel.

Determines whether the controller verifies
the accuracy of data transfer on the SCSI
channel. You should only disable SCSI Parity
Checking on the controller and all SCSI
devices if any SCSI device supported by the
controller does not support SCSI parity;
otherwise, retain the default. Most SCSI
devices do support SCSI parity. If you are not
sure whether a device supports SCSI parity,
consult the documentation for the device.

Sets termination on the controller. ICP
recommends that you retain the default
setting.

A-12

ICP RAID Configuration Utility

SCSI Device Configuration Options

The SCSI device settings allow you to configure certain parameters
for each device on the SCSI channel. To configure settings for a
specific device, you must know the SCSI ID assigned to that device.
If you are not sure of the SCSI ID, see Using Disk Utilities on

page A-14.

To access the SCSI Device Configuration options, select SCSI
Configuration, then select Additional Options. The SCSI Device
Configuration options are described in the table below.

Note: For maximum performance, retain the default settings.

SCSI Device Configuration Options

Option Default Description

Maximum
Trans f e r R ate

Enable
Disconnection

Initiate Wide
Negotiation

QAS No Determines whether QAS (Quick Arbitration

Packetized Yes Determines whether SCSI packetization

N/A Determines the maximum data transfer rate

Yes Determines whether the SCSI channel allows

Yes Determines whether the SCSI channel attempts

that the SCSI channel supports. The maximum
effective data transfer rate is doubled when

Initiate Wide Negotiation

devices are attached. (
has no effect with 8-bit devices.)

the SCSI device to disconnect from the SCSI
channel (sometimes called Disconnect/
Reconnect or Reselection).

16-bit data transfer instead of 8-bit data transfer.
The effective data transfer rate is doubled when
16-bit data transfer is used.

and Selection) is used to eliminate overhead
and speed up data transfers on the SCSI bus.

If you are using an enclosure that contains
Ultra320 expander ICs, it is recommended that
you do not enable QAS.

(encapsulation) is used to reduce overhead and
speed data transfer. The packetized SCSI
protocol provides a method for transferring
command and status information at the
maximum rate.

is set to

Initiate Wide Negotiation

Ye s

and 16-bit

A-13

ICP RAID Configuration Utility

Using Disk Utilities

Use Disk Utilities to low-level format or verify the media of the
hard disk drives. To access Disk Utilities:

1 Restart the computer, then press Ctrl+A when prompted to

access the ICP RAID Configuration utility.

2 If multiple controllers are installed, select the controller you

want to configure, then press Enter.

3 From the ICP RAID Configuration utility menu, select Disk

Utilities.

4 Select the desired disk, then press Enter.

Choose either Format Disk or Verify Disk Media:

■ Format Disk—The functionality depends on the controller

type, as described below:

– SATA Controllers—Simulates a format of the hard disk

drive by removing the file system and writing zeros to
the entire disk.

– SCSI Controllers—Performs a low-level format.

Most drives are formatted at the factory and do not need to be
formatted again.

Caution: During formatting, all data is deleted. Before

!

proceeding, back up any data you want to keep.

■ Verify Disk Media—Scans the media for defects and

corrects any errors that are found.

A-14

ICP RAID Configuration Utility

Viewing the Event Log

The BIOS-based event log stores all firmware events (configuration
changes, array creation, boot activity, and so on).

The event log has a fixed size. Once full, old events are deleted as
new events are stored. Also, the log is cleared when the system is
restarted.

To access the event log:

1 Restart the computer, then press Ctrl+A when prompted to

access the ICP RAID Configuration utility.

2 If multiple controllers are installed, select the controller you

want to display events for, then press Enter.

3 From the ICP RAID Configuration utility menu, press Ctrl+P.

The Controller Service menu appears.

4 Select Controller Log Information, then press Enter. The

current log is displayed.

A-15

B

ACU for DOS

In this Appendix...

Introduction B-1
Creating the ACU Utility Disk B-1
Running the ACU Interactively B-2
Running the ACU Using Scripts B-3

Introduction

The ACU allows you to create, configure, and manage arrays.

Creating the ACU Utility Disk

The DOS version of this utility runs from a floppy disk that you
need to create using the following procedure:

1 To find the ACU executable,

controller installation CD that relates to your controller model.

ICP Model Path

ICP9014RO packages/firmware/ICP9014RO
ICP9024RO

2 Insert a bootable floppy disk and copy

packages/firmware/ICP9024RO

acu.exe, browse to the folder on the

acu.exe

to it.

B-1

ACU for DOS

Running the ACU Interactively

To run the ACU interactively:

1 Insert the ACU utility disk you created in Creating the ACU

Utility Disk.

2 Start or restart your computer.

The computer boots to the DOS command line.

3 Ty pe

ACU

on the command line, then press Enter.

To select ACU options, highlight the options using the arrow keys
and the Tab key, then press Enter. You can select from the
following tasks:

■ Creating Arrays

■ Managing Arrays

■ Initializing Drives

■ Rescanning Drives

Note: To return to the previous menu at any time, press Esc.

For details on using the ACU, see Using the ACU on page A-2.

B-2

Running the ACU Using Scripts

ACU for DOS

To use the ACU scripting features, use the

ACU

command, specify a

script file (see Creating the Script File Manually on page B-5), and
specify one (but not both) of the required switches listed in the table
below. You may also add one or both of the optional switches listed
in the table.

Note: Command line syntax is not case sensitive.

Switch Type Description

/P <file>

/R <file>

/L <file>

/C <number>

Required

Required

Optional

Optional

Playback Mode—In this mode, the ACU reads
the contents of the specified script file and creates
arrays and configures channel settings based on
the keywords defined in the script. For more
details, see Playback Mode on page B-4.

Note:

The ACU exits with an error if you do not

include either the

Record Mode—The ACU writes a controller’s
existing array configuration to a specified script
file, enabling you to create the same configuration
by running the ACU in playback mode (/P
switch) with the resulting script. For more details,
see Record Mode on page B-4.

Note:

The ACU exits with an error if you do not

include either the

Optional Log Filename Switch—If you include
this switch, the ACU records its activity and any
errors it encounters in the log file. If you do not
include this switch, the ACU displays any status
and errors on the screen.
The

file is a standard MS-DOS file, which can

include a drive, directory, filename, and extension.
Only the filename and extension (
required. If no drive or directory is specified, the
file is placed in the location of the ACU executable.

Optional Controller Number Switch—In
systems with more than one controller, this switch
specifies which controller to change, where
<number> is the controller number. The default
controller number is 0.

Note:

The number assigned to a particular controller
depends on the controller’s physical PCI slot and the
order in which your system scans its PCI slots.

/P

or the /R switch (but not both).

/P

or the /R switch (but not both).

.LOG

) are

B-3

ACU for DOS

Playback Mode

In this mode, the ACU reads the contents of the specified script file
and creates arrays based on the keywords specified in the script.

The syntax is ACU /P <file> where file is the parameter
specifying name of the script file. The file parameter can include
a drive, directory, filename, and extension. If no drive or directory
is specified, the file is placed in the location of the ACU executable.

Note: The script file syntax allows only a single hotspare to be
assigned to any given array. Therefore, when recording a
RAID 10, the ACU cannot map hotspares assigned to the
individual mirror sets in the resulting script file. Instead, the
ACU creates a single

HotspareDrives

list for all hotspares

assigned to the RAID 10. For details, see the Method Keyword

on page B-9.

Record Mode

There are two methods available for creating a script file:

■ Use Record Mode.

■ Create the script manually. (See page B-5.)

Regardless of which method you use to create the script, you need
to use Playback Mode (/P) to use the script.

In Record Mode, the ACU writes a controller’s existing array
configuration to a specified script file, enabling you to create the
same configuration by running the ACU in Playback Mode (/P
switch) with the resulting script.

The syntax is ACU /R <file> where file is the parameter
specifying name of the script file. The file parameter can include
a drive, directory, filename, and extension, but only the filename
and extension are required. If no drive or directory is specified, the
file is placed in the location of the ACU executable.

B-4

Notes:

■ Record Mode can be used to record only one controller at a

time. Therefore, if you want to record multiple controllers,
record them separately using separate script files.

■ Because the ACU supports only a subset of array types

available, it cannot record all the possible array
configurations. If the ACU encounters an array that it
cannot create, it displays a warning (or, if the /L switch is
used, records the warning in the log file) and does not
record any keywords for that array in its script file.

■ When recording an array, the ACU uses the default Wait

setting (equivalent to
file and include

Wait=No

Wait=Yes

) unless you edit the script

in the array’s definition block.

For details, see the Wait Keyword on page B-11

Creating the Script File Manually

Script files contain the following structures, or blocks:

■ Array Definition Block Keywords

■ Channel Definition Block Keywords – SCSI only (optional)

ACU for DOS

The rules for syntax are as follows:

■ Each keyword must start its own line.

■ The syntax is not case sensitive.

Comments

To enter a comment in the script file, start with a pound character (#).
You can start anywhere on a line. For a sample script that includes
comments, see

Example – Running the ACU with a Script

on page B-14.

B-5

ACU for DOS

Array Definition Block Keywords

The array definition block always begins with the keyword
and ends with the keyword

End

. The other required array definition

keywords are Drives and Type. The array definition keywords
are listed alphabetically in the following table.

Default

Keyword

Array

Drives Yes None Specifies the devices used in

End Yes None Indicates the end of an array

HotspareDrives

InitializeAll

Method Ye s Build Indicates the method (Build/

ReadCache No Yes Indicates whether read

Size No

StripeSize No 64

Type Yes None Indicates the type of array to

Wait No Yes

WriteCache No Yes Indicates whether write cach-

Required

?

Value Description

Yes None Indicates the start of an array

No None Specifies the hotspares to

No No Indicates whether to initialize

Maximum

definition block. See page B-7).

creating the array. See

page B-7).

definition block. See page B-7
for details.

assign to the array. See

page B-8).

all the drives connected to the
controller. See page B-8).

Verify, Clear, or Quick Init) to
use when creating a redundant
array (see page B-9.

caching is enabled for this
array (see page B-10).

Specifies the size of the array
(see page B-10).

Specifies the size of contiguous
I/O, in bytes (see page B-10).

create (see

Indicates whether the ACU
should wait for the new array’s
build/verify or clear to com­plete before continuing (see

page B-11).

ing is enabled for this array
(see page B-11).

page B-11

Array

).

B-6

ACU for DOS

The keywords are described in detail in the sections following
sections.

Array Keyword

Array

is a required keyword, indicating the start of an array

definition block. The syntax is Array=<label>, where label is
an optional alphanumeric string.

Examples

Array
Array=MyData

Drives Keyword

Drives

creating the array. There is no default value.

A drive is identified by its channel number, ID (target), and LUN,
separated by colons; for example,
multiple drive identifiers with commas.

Prior to creating any new arrays, the ACU initializes any drives
specified by the Drives keyword. If a drive is specified in more
than one array definition block in a script, it is initialized only once.

Caution: Any drive specified within the script file is initialized,

!

which destroys any data on that drive.

Examples

Drives=0:0:0
Drives=0:0:0,0:1:0,0:2:0

is a required keyword, specifying the devices to use in

0:0:0

or

0:1:0

. Separate

End Keyword

End

is a required keyword, indicating the end of the block.

Example

End

B-7

ACU for DOS

HotspareDrives Keyword

HotspareDrives

is an optional keyword, specifying the hotspares

to assign to the array. The syntax for listing hotspares is the same as
the Drives Keyword on page B-7. If

HotspareDrives

is not specified,

no hotspares are assigned to the array.

Notes:

■

HotspareDrives

creates only dedicated hotspares. If the
same drive is assigned to protect multiple arrays, only the
last array that drive is assigned to is protected.

■

HotspareDrives

does not verify that the available space
on the specified hotspares is sufficient to serve as failover
for the array.

■ When assigning hotspares to a multilevel array,

HotspareDrives

assigns all the hotspares in the list to all
arrays within the multilevel array.

Example

HotspareDrives=0:0:0,0:1:0

InitializeAll Keyword

If you want the ACU to initialize all drives connected to the
controller and delete any existing arrays before any new arrays are
created, even those that are not specified in any

Drives

keyword

definition, specify InitializeAll=yes. Otherwise, the ACU
initializes only those drives specified by the

Drives

keyword.

Caution: Initializing a drive automatically deletes any existing

!

arrays with that drive as their member.

B-8

ACU for DOS

Notes:

■

InitializeAll

is a global keyword that you need to

specify only once.

■

InitializeAll

is always performed prior to array

creation regardless of its position in the script.

■ If both

specified in the same script file,

InitializeAll=Yes

and

InitializeAll=No

InitializeAll=Yes

are

is

always the overriding value.

■ If an array is deleted during a build/verify process, the

process is automatically terminated.

Possible values are as follows:

■ Yes —Initialize all drives.

■ No (the default)—Do not initialize all drives; only those drives

specified with the

Examples

Drives

keyword are initialized.

Type=Volume
Type=RAID1

Method Keyword

Method

is an optional keyword, indicating which method to use
when creating a redundant (RAID 1, 5, and 10) array. Possible
values are:

■

Build

(the

default

)—Perform a build/verify process on the array.

Take s lon g er t han

Clear

, but allows you to begin using the array

immediately.

■ Clear—Clear the array. Faster than a build/verify process, but

you have to wait for the operation to be completed before you
can begin using the array.

■

Quick Init

—Makes the array available immediately, but does not
accomplish a build/verify. Parity and mirror information is created
as data is written to the drive (called full-stripe write mode), which
reduces overall array performance. Maximum performance is
achieved by starting and completing a build/verify.

Example

Method=Build

B-9

ACU for DOS

ReadCache Keyword

ReadCache

indicates whether the array uses read caching.

Possible values are:

■ Yes (the default)—Enable read caching.

■ No—Disable read caching.

Example

ReadCache=Yes

Size Keyword

The

Size

keyword specifies the size of the array. Specify

Maximum

(the default) to create an array using the maximum available space,
based on the array type and drives selected. Otherwise, specify the
size as an integer or a decimal number, followed by the unit
keyword MB (megabytes), GB (gigabytes), or TB (terabytes).

Note: A unit keyword is required with a numeric size value. If
no unit keyword is specified, the ACU exits with an error.

Examples

Size=2.5GB
Size=300MB
Size=Maximum

StripeSize Keyword

Note: This keyword does not support RAID 50 arrays because

RAID 50 arrays support only a stripe size of 64 KB.

The

StripeSize

keyword specifies the stripe size (in MB) written

to each member of a striped (RAID 0, RAID 5, RAID 10) array.

The possible values for

StripeSize

are 16, 32, 64, 128, 256 KB (the

default), 512.

Example

StripeSize=256

B-10

ACU for DOS

Type Keyword

Type

is a required keyword, indicating the array type. There is no

default value. The

■ Volume ■ RAID5

■ RAID0 ■ RAID10

■ RAID1 ■ RAID50

Type

keyword values are:

Note: For information about which array types your controller
supports, see Controller Features on page 1-4.

Wait Keyword

Wait

is an optional keyword that you can use to tell the ACU to

allow the ACU to continue while the build/verify or clear
completes in the background; specify wait=no. Otherwise, the
ACU waits by default.

Note: If the host is powered off before the build/verify or clear
process completes and is then restarted, the process resumes
without any user intervention.

Examples

Wait=Yes
Wait=No

WriteCache Keyword

The

WriteCache

keyword indicates whether write caching is used
for this array if write caching is supported for the system. Possible
values are as follows:

■ Yes (the default)—Enable the write cache.

■ No—Disable the write cache.

Note: Setting an array’s

WriteCache

keyword to

Yes

might

result in data loss or corruption during a power failure.

Example

WriteCache=Yes

B-11

ACU for DOS

Channel Definition Block Keywords – SCSI only

The channel definition block is optional. If used, it always begins
with the keyword
channel definition block keywords are listed alphabetically in the
following table.

Keyword Description

Channel Used to identify the channel.
ControllerID Changes the SCSI ID of the controller.
End Indicates the end of a channel definition block.

Channel Keyword

Channel is an optional keyword that begins a channel definition
block and specifies the channel number to which the channel
keywords apply. Channels are numbered from zero to the
maximum number of channels on the controller minus one.

You can include multiple channel definition blocks within a script file,
each beginning with a

Example

Channel=0

Channel and ends with the keyword

Channel

keyword and value.

End

. The

ControllerID Keyword

ConrollerID is an optional keyword to change the SCSI ID of the
controller. Normally, the SCSI controller is assigned SCSI ID 7 on
each of its channels. You can specify any ID value between 0 and 7.

Caution: Do not change the SCSI ID of the controller unless

!

directed to do so by ICP Technical Support.

Example

ControllerID=7

End Keyword

End

is a required keyword, indicating the end of the block.

Example

End

B-12

ACU for DOS

ACU Error Codes

When the ACU detects an error, it reports the error and exits
immediately. If a log file is specified, the ACU writes the error code
to the log file. Otherwise, it displays the error code on the screen.

The possible error messages returned by the ACU are listed in the
table below.

ACU Error Codes

Code Description

0 ACU ran without changes—The ACU exited with no errors

(success) and no report is required.

1 No controller found—The ACU did not detect any controllers in the

system.

2 Syntax or logical error in the script file—The ACU encountered an

3 Unable to open file—The ACU was unable to open the specified

4 Error in the

5 Unable to read system configuration—The ACU was unable to get

6 No drives detected—The ACU did not detect any devices attached

7 Specified drive not found in system—The device you specified

8 Specified array size too small—You specified an array size that is

9 Specified array size too big—You specified an array size that is

10 Number of drives do not match the array type—The number of

11 Unable to initialize drive—The ACU was unable to initialize one or

12 Error occurred while creating array—The ACU encountered an

13 Too many spare drives assigned—You attempted to assign more

command or keyword in the specified script file.

invalid

script or log file.

command line parameters—You passed an invalid

command line switch to the ACU. (See Running the ACU Using

Scripts on page B-3 for the list of valid

the configuration information from the specified controller.

to the selected controller.

does not exist on the selected controller.

smaller than the minimum size allowed for this array.

larger than the maximum size allowed for this array.

drives you selected is invalid for the type of array specified.

more devices.

error creating an array.

than the maximum number of hotspares allowed for the specified
array.

command line switches.)

B-13

ACU for DOS

ACU Error Codes "Continued"

Code Description

14 Insufficient memory to run the application—There is not enough

memory to run the ACU.

15 Incorrect controller number—The controller number you specified

is invalid or out-of-range.

16 Controller not responding—The controller has stopped responding

to the ACU.

17 Build/Verify/Clear failed—The build/verify or clear operation for

one or more arrays has failed.

100 You ran ACU and made changes—The ACU exited with no errors

(success) and you must restart the computer.

Example – Running the ACU with a Script

The following MS-DOS command invokes the ACU and creates
arrays on controller 1 based on the array keywords defined in the
script file
log of the operation in the log file

A:\RAID.ACU

. It also configures Channel 0 and saves a

C:\RAID.LOG

A:\> ACU /P A:\RAID.ACU /L C:\RAID.LOG /C1

.

The following sample script file is a sample

RAID.ACU

script as
referred to in the previous ACU command. This script creates the
following arrays—a 500 MB, single-disk volume, and a 2 GB,
two-drive RAID 1 with a hotspare:

# Script to create volume, mirror, and RAID 5 arrays
# Create a 500MB volume labeled ‘MySystem’
Array=MySystem
Type=Volume
Size=500MB
Drives=0:0:0

End
# Create a 2GB mirror labeled ‘MyMirror’

Array=MyMirror
Type=RAID1
Size=2GB
# Use drives 1 and 2
Drives=0:1:0,0:2:0
# Disable write cache
WriteCache=No
# Assign 1 spare drive
HotspareDrives=0:3:0
End

B-14

The following sample script file creates a maximum size
three-drive RAID 5.

# Create a maximum size RAID 5 labeled ‘MyData’
Array=MyData
Type=RAID5
Size=Maximum

# Use the maximum stripe size
StripeSize=64

# Clear the array (don’t build/verify it)
Method=Clear

# Don’t wait for clear to complete
Wait=No

# Use drives 0, 1, 2
Drives=0:0:0, 0:1:0, 0:2:0

End

ACU for DOS

B-15

C

ICP Flash Utility (IFU)

In this Appendix...

Introduction C-1
Creating the Firmware Floppy Disks C-3
Running the IFU from the GUI C-4
Running the IFU from the Command Line C-5

Introduction

The ICP Flash Utility (IFU) is a DOS utility used to update, save, or
verify the RAID controller’s firmware BIOS, and NVRAM.

Caution: The IFU is easy to use and contains safeguards to

!

prevent you from accidentally damaging the controller’s flash
contents. Still, you must be careful to use the IFU correctly,
otherwise, you could render the controller inoperable.

Note:

If you are updating multiple controllers in the same
system, first update the boot controller’s flash, and then update
the flash for the remaining controllers.

C-1

ICP Flash Utility (IFU)

The IFU is used to:

■ Update—Updates all the flash components on a controller with

the flash image data from a User Flash Image (UFI) file.

The IFU updates the controller’s flash by reading UFI files and
writing them to the controller’s flash components.

Note: The UFI includes the controller’s type, thereby
ensuring that the IFU uses the correct file.

■

Save

—Reads the contents of a controller’s flash components and
saves the data to a UFI file. This allows you to later restore a
controller’s flash to its previous contents should the need arise.

■ Verify—Reads the contents of a controller’s flash components

and compares it to the contents of the specified UFI file.

■ Ve rs i on —Displays version information about a controller’s

flash components.

■ List—Lists all supported controllers detected in your system.

System Requirements

The requirements for IFU are as follows:

■ MS–DOS version 5.0 or later. It cannot run from a DOS

command prompt window under any version of Windows.

■ At least 8 MB of extended memory.

Note:

You cannot create the bootable floppy using Windows 2000.

Compatibility

The IFU has the following compatibility issues:

■ Supports HIMEM.SYS; compatible with other DOS drivers

running under HIMEM.SYS
SETVER.SYS).

■ Does not support DOS extenders installed in memory, such as

EMM386.SYS and DOS4GW.

(for example, SMARTDRV.SYS and

C-2

ICP Flash Utility (IFU)

Creating the Firmware Floppy Disks

Controller firmware is available two ways:

■ From the controller installation CD—The CD includes the IFU

executable,
multiple UFI files.

You can locate the necessary files on the controller installation
CD at the locations listed below.

ICP Model Path

ICP9014RO /packages/firmware/ICP9014RO

ICP9024RO /packages/firmware/ICP9024RO

■ From the ICP Web site—When you download a new firmware

file, you usually get the most recent version of IFU.

To create the firmware floppy disks:

1 Create a bootable MS–DOS floppy disk and copy the following

files to this disk:

–IFU.exe
–AAxxx01.ufi

IFU.exe. The flash image may be comprised of

where xxx is the model number of your controller.

2 Create additional bootable MS–DOS floppy disks and copy each

additional

AAxxx0x.ufi files to a separate disk. (Some controllers

have two UFI files; others have four.)

3 Start the IFU as described in Running the IFU from the GUI on

page C-4 and follow the prompts.

C-3

ICP Flash Utility (IFU)

Running the IFU from the GUI

The easy way to run the IFU is to use its GUI. If you prefer to run
the IFU from the command line, see page C-5.

To access the IFU:

1 Create the firmware floppy disks, as described in Creating the

Firmware Floppy Disks on page C-3.

2 Shut down your operating system and reboot to DOS from a

bootable MS-DOS floppy disk or from a DOS partition on a
bootable drive. You can use the drive connected to the controller
you are updating.

Note: When updating the controller flash, I/O is not
possible. Before you can use the controller again, complete
the flash operation and restart the computer.

3 At the DOS command prompt (typically

arguments.

The IFU’s main menu is displayed.

4

Select

Select Controllers

5 Select Select an Operation.

6 Select any available IFU function and follow the on-screen

instructions.

and select the controllers to be flashed.

A:\>), type

IFU

with no

C-4

ICP Flash Utility (IFU)

Running the IFU from the Command Line

At the DOS command prompt (typically A:\>), type IFU followed
by a command and any switches. The IFU processes the command,
prompts you to insert additional floppy disks as needed, exits, and
reports success or an error message code.

Command Summary

This section describes each IFU command (in alphabetical order).

HELP

The HELP command displays a summary of IFU functions and
command switches.

Examples

The following are examples of commands you can use to display
help information:

A:\> IFU HELP
A:\> IFU /?

LIST

The LIST command displays the IFU-supported controllers
installed on your computer. Use this command to see which
controllers are installed, or to identify the ID numbers assigned to
each physical controller.

You do not have to restart the computer after completing this
command.

Example

The following example shows a typical response to a

LIST

command.

A:\> IFU LIST
ICP Flash Utility V4.0-0 B5749
(c)ICP Inc. 1999–2002. All Rights Reserved.
Controllers Detected and Recognized:
Controller #0 (03:05:00) ICP 2410

C-5

ICP Flash Utility (IFU)

SAVE

The

SAVE

command saves the contents of a controller’s flash in a
UFI file. The name of the UFI file is based on the controller type
and cannot be changed.

You must restart the computer following a

Command Syntax

The command syntax for the

IFU SAVE [/C<Controller ID>] [/D <UFI File Path>]

Command Switches

SAVE

command is as follows:

SAVE

command.

The following switches are available:

■

/C <Controller ID>

is one or more controller IDs representing
the set of controllers on which to perform the specified
command. The default is 0, which means that if the computer
has

multiple controllers, the IFU defaults to controller 0 unless you

specify otherwise.

You can specify a single controller ID, for example:

/C 0

multiple IDs separated by commas, for example:

/C 0,2
or ALL to indicate all controllers.

Note:

If you are using multiple controllers, you must specify

the controller you want by using the

/C

switch; otherwise, the

IFU displays an error message and exits.

■

/D <UFI File Path>

specifies the path (drive and directory)
where the UFI files are located. If you do not specify the
switch, the IFU looks for, or creates, its UFI files in the default
location.

Note:

You cannot specify the name of a UFI file, only its path.

UFI filenames are predefined, based on controller type.

/D

C-6

ICP Flash Utility (IFU)

Examples

In the following example, the IFU saves flash contents from
controller 0 to a UFI file in the current default drive and directory:

A:\> IFU SAVE /C 0

In the following example, the IFU saves flash contents from
controller 1 to a UFI file in

A:\> IFU SAVE /C 1 /D C:\UFI_FILES

C:\UFI_FILES

.

UPDATE

The

UPDATE

from the flash image data in a UFI file. You can use the

command updates a controller’s flash components

UPDATE

command to update a single controller’s flash components or to
update multiple controllers on your computer.

You must restart the computer following an

Command Syntax

The command syntax for the

IFU UPDATE [/C<Controller ID>] [/D <UFI File Path>]

Command Switches

UPDATE

command is as follows:

UPDATE

command.

For details on the /C and /D switches, see the SAVE command on

page C-6.

Example

The following example shows a typical system response after an
update has been performed.

A:\> IFU UPDATE /C 0
ICP Flash Utility V4.0-0 B5749
(c)ICP Inc. 1999–2005. All Rights Reserved.
Updating Controller 0 (ICP9024RO)
Reading flash image file (Build 5749)
IFU is about to update firmware on controllers ICP 2410
***PLEASE DO NOT REBOOT THE SYSTEM DURING THE UPDATE***
This might take a few minutes.
Writing ICP9024RO (4MB) Flash Image to controller 0...OK.
Verifying...OK
Please restart the computer to allow firmware changes to take
effect.

C-7

ICP Flash Utility (IFU)

VERIFY

The

VERIFY

command compares the contents of each of the flash
components on a controller to the corresponding image in a UFI
file and indicates whether they match. Use this command to
determine whether a controller’s flash components are up-to-date
when compared to a specific UFI file.

After using the

Command Syntax

The command syntax for the

IFU VERIFY [/C<Controller ID>] [/D <UFI File Path>]

Command Switches

VERIFY

command, you must restart the computer.

VERIFY

command is as follows:

For details on the /C and /D switches, see the SAVE command on

page C-6.

Example

The following example shows a typical system response after a
verify command has been performed.

A:\> IFU VERIFY /C 0
ICP Flash Utility V4.0-0 B5749
(c)ICP Inc. 1999–2005. All Rights Reserved.
Reading flash image file (Build 5748)
Controller #0: ICP9024RO
ROM: Checksum: 797B [VALID] (Build 5748)
File: Checksum: 797B [VALID] (Build 5748)

Image Compares Correctly

VERSION

The

VERSION

command displays version information about the

flash components on a controller.

After using the

VERSION

command, you must restart the computer.

Command Syntax

The command syntax for the

IFU VERSION [/C<Controller ID>]

Command Switches

VERSION

command is as follows:

For details on the /C switch, see the SAVE command on page C-6.

C-8

ICP Flash Utility (IFU)

Example

The following example displays version information about all
supported controllers.

A:\> IFU VERSION /C 0
ICP Flash Utility V4.0-0 B5749
(c)ICP Inc. 1999–2005. All Rights Reserved.
Version Information for Controller #0 (ICP9024RO)
ROM: Build 5748 [VALID] Fri Sep 27 13:28:40 EDT 2002
A:\> IFU VERSION /C ALL

IFU Command Line – Step-by-Step

This section provides step-by step instructions for updating the
flash.

To update the flash using the IFU command line:

1 Create the firmware floppy disks, as described in Creating the

Firmware Floppy Disks on page C-3.

2 Shut down the computer.

3 Insert the bootable disk that contains the IFU utility.

4 Turn on the computer.

5 Enter the system setup utility and verify that your computer is

set up to boot from the bootable disk.

6 If you have multiple controllers only—At the DOS prompt, type

ifu list

and press Enter.

This command displays the ICP RAID controllers in your
system. Note the controller number for the controller you want
to update; you may need it in Step 7 to perform the update.

7 You can update the flash using any of the following

alternatives:

a Updating the Flash on a Single Controller—To flash the

firmware on a single controller, type:

ifu update /C <

Where <

controller_number

controller_number

>

> is the number of the controller

whose firmware you are updating. For example, to upgrade
controller 0, type:

ifu update /C 0

C-9

ICP Flash Utility (IFU)

b Updating the Flash on Multiple Controllers—To flash the

firmware on multiple controllers, type:

ifu update /C <

controller_number_a

>,<

controller_number_b

>

Where

<controller_number_a>

and

<controller_number_b>

is the number of one of the controllers whose firmware you
are updating.

To upgrade controllers 0, 2, and 3 for example, type:

ifu update /C 0, 2, 3

c Updating the Flash on All Controllers Simultaneously—To

flash the firmware on all controllers, type:

ifu update /C all

Note: The UFI file identifies the appropriate controllers,

so you do not have to worry about flashing the wrong

controller.

8 The IFU prompts you to insert the first firmware disk.

When it detects that the disk is in the drive, the IFU reads the
firmware image contained on the first disk.

9 When prompted, remove the first firmware disk and insert the

second firmware disk.

10 If necessary, repeat Step 9 until the process is complete.

C-10

D

Installing and Using the Command Line Utility

In this Appendix...

Introduction D-2
Installing ARCCONF D-2
Starting ARCCONF D-5
Using ARCCONF D-5

D-1