Chaparral Rio User Guide

RFF244/RFF288
External RAID Subsystem
Users Guide
Copyright
2001, 2002 Chaparral Network Storage, Inc. Document Number: 07-0096-001 This document covers the RFF244 and RFF288. All rights reserved. No part of this publication may be reproduced without the prior written consent of Chaparral Network Storage, Inc. 7420 E. Dry Creek Parkway Longmont, Colorado 80503 http://www.chaparralnet.com
Trademarks
Windows is a registered trademark and Windows NT is a trademark of Microsoft Corporation in the U.S. and other countries, used under license. All other trademarks are the property of their respective companies.
Changes
The material in this document is subject to change without notice. While reasonable efforts have been made to ensure the accuracy of this document, Chaparral Network Storage, Inc. assumes no liability resulting from errors or omissions in this publication, or from the use of the information contained herein. If you would like to provide comments or suggestions on the quality and/or accuracy of this manual, please contact Chaparral at http://www.chaparralnet.com/manuals. Chaparral reserves the right to make changes in the product design without reservation and without notification to its users. Comments and suggestions can be sent to the address listed above.
Technical Support
If after reviewing this users guide, you still have questions about installing or using your Chaparral product, please contact us at (303) 845-3200 or by e-mail at support@chaparralnet.com.
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 users authority to operate the equipment. This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC rules. 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.
iii
Canadian Compliance Statement

This Class A digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations. Cet appareil numrique de la classe A respecte toutes les exigences du Rglement sur le matrial brouilleur du Canada.
iv
Contents
Contents
1 Introduction
About This Guide ..............................................................................................1-2 Conventions ................................................................................................1-2 Safety .................................................................................................................1-3 Electrical Surges .........................................................................................1-3 EU Declaration of Conformity ...................................................................1-3 UL Approvals .............................................................................................1-3 Reference Documents ........................................................................................1-4 External Documents ....................................................................................1-4 Chaparral Documents .................................................................................1-4
Hardware Installation
Unpacking the RIO Subsystem .........................................................................2-1 Understanding the RFF244 and RFF288 ....................................................2-2 Connecting the Battery ......................................................................................2-5 Installing the RIO Subsystem ............................................................................2-7 Front-Mounting the RIO Subsystem ...........................................................2-7 Rear-Mounting the RIO Subsystem ............................................................2-8 Connecting the RIO Subsystem ......................................................................2-10 Connecting to the RS-232 Port ................................................................. 2-11 Connecting to the Ethernet Port ................................................................2-12 Connecting the Power Cables ...................................................................2-13 Connecting to the Fibre Channel Host and Disk Ports .............................2-13 Connecting to the Fibre Channel Host Ports ............................................2-19 Connecting to the FC Disk Ports .............................................................2-19 Understanding the LED Status Lights .............................................................2-20 Understanding How the Data Managers Work Together ................................2-24 Replacing Modules ..........................................................................................2-25 Removing a Module ..................................................................................2-26 Removing a Power Port ............................................................................2-28 Installing a Module ...................................................................................2-29 Installing a Power Port ..............................................................................2-30 Upgrading or Replacing the Memory DIMMs ................................................2-32
RFF244/RFF288 Users Guide
Accessing the Disk Array Administrator Software

Accessing the Disk Array Administrator Using the RS-232 Serial Port ...........3-2 Accessing the Disk Array Administrator Using the Ethernet Port ....................3-4 Using the Ethernet Port for the First Time .................................................3-4 Accessing the Disk Array Software Using the Ethernet Port .....................3-4 Navigating the Disk Array Administrator Software ..........................................3-7 Changing the Screen Display ......................................................................3-7 Disk Array Administrator Menu Tree ........................................................3-8
Creating and Managing Arrays and Partitions

Creating Arrays .................................................................................................4-1 Creating a Single-Partition Array ...............................................................4-2 Creating a Multiple-Partition Array ............................................................4-7 Managing Arrays .............................................................................................4-12 Viewing Array and Drive Status Information ...........................................4-12 Viewing Array Status ............................................................................4-12 Viewing Drive Status .............................................................................4-14 Stopping the Array Initialization Process .................................................4-15 Adding a Partition .....................................................................................4-15 Verifying an Array ....................................................................................4-18 Viewing Verification Status ...................................................................4-19 Stopping the Verification .......................................................................4-19 Reconstructing an Array ...........................................................................4-20 Expanding Array Capacity ........................................................................4-21 Viewing Expand Status ..........................................................................4-23 Changing an Array Name .........................................................................4-23 Changing Array Ownership ......................................................................4-24 Trusting an Array ......................................................................................4-25 Deleting an Array ......................................................................................4-26 Managing Partitions ........................................................................................4-27 Understanding Partitions ...........................................................................4-27 Viewing Partition Status Information .......................................................4-28 Viewing Partition Status ........................................................................4-28 Viewing Partition Statistics ....................................................................4-30 Resetting Partition Statistics ...................................................................4-32 Expanding a Partition ................................................................................4-34 Changing a Partition Name .......................................................................4-35 Changing a Partition LUN .......................................................................4-36 Changing the Read-Ahead Size ................................................................4-36 Controlling Partition Access .....................................................................4-38
Contents
Viewing Known WWNs ........................................................................4-39 Creating Names (Aliases) for Host WWNs ..............................................4-40 Configuring InfoShield ..........................................................................4-41 Changing All Partitions to Include All Hosts ...........................................4-44
Deleting a Partition ...................................................................................4-44
Monitoring System Status

Displaying the Event Log ..................................................................................5-2 Viewing the Most Recent Event .................................................................5-3 Viewing One Event at a Time .....................................................................5-3 Viewing a Whole Screen of Events ............................................................5-4 Capturing the Event Log .............................................................................5-5 Displaying Module Status Information .............................................................5-5 Displaying Hardware and Configuration Information ......................................5-6 Capturing the Event Log, Hardware, and Configuration Information ............5-10 Displaying Drive Errors and Resetting Error Statistics ................................... 5-11 Displaying Overall Statistics ...........................................................................5-12 Resetting Overall Statistics .......................................................................5-13
Managing Spares
Managing Dedicated Spares ..............................................................................6-2 Adding a Dedicated Spare ..........................................................................6-2 Deleting a Dedicated Spare .........................................................................6-3 Enabling Dynamic Spares .................................................................................6-3 Managing the Spare Pool ..................................................................................6-4 Adding a Spare to the Spare Pool ...............................................................6-5 Deleting a Spare from the Spare Pool .........................................................6-5 Displaying the Spare Pool ...........................................................................6-6
Configuring the RIO Subsystem

Shutting Down and Restarting the Data Managers or Data Gates ...................7-1 Shutting Down and Restarting the Current Data Manager .........................7-2 Shutting Down the Other Data Manager ....................................................7-3 Shutting Down Both Data Managers ..........................................................7-4 Putting a Data Manager or Data Gate Offline ............................................7-4 Putting a Data Manager or Data Gate Online .............................................7-6 Forcing a Data Manager or Data Gate Offline ...........................................7-6 Changing the Date and Time .............................................................................7-7 Configuring the Host Channels .........................................................................7-8
Configuring the Internal Host Port Hubs ..................................................7-10 Understanding LUNs and Viewing LUN Information ....................................7-12 Viewing LUN Information .......................................................................7-13 Configuring the FC Disk Channels .................................................................7-14 Configuring the Data Gates .............................................................................7-16 Changing the Alarm Mute Setting ...................................................................7-16 Locking the Cache Setting ..............................................................................7-18 Enabling and Disabling the Battery .................................................................7-19 Changing the Utility Priority ...........................................................................7-21 Rescanning All Channels ................................................................................7-21 Pausing I/O ......................................................................................................7-22 Restoring Default Settings ...............................................................................7-23 Upgrading Firmware .......................................................................................7-24 Upgrading the Data Managers and Memory Controllers Firmware ......7-24 Upgrading LAN Firmware ........................................................................7-25
Managing Disk Drives and Enclosures

Managing Disk Drives .......................................................................................8-1 Displaying Drive Information .....................................................................8-1 Displaying All Drives ..............................................................................8-2 Viewing Drive Status ...............................................................................8-3 Displaying Drive Errors and Resetting Error Statistics ...............................8-4 Clearing Metadata from a Drive .................................................................8-4 Enabling and Disabling Write-back Cache .................................................8-5 Displaying Disk Cache Status .....................................................................8-7 Enabling and Disabling SMART Changes .................................................8-8 Blinking a Drive LED .................................................................................8-9 Taking Down a Drive .................................................................................8-9 Testing a Drive ..........................................................................................8-10 Managing Enclosures ......................................................................................8-10 Setting the EMP LUN ............................................................................... 8-11 Changing the Additional EMP Settings ....................................................8-13
Troubleshooting
Chaparral Technical Support .............................................................................9-1 AC Power Problems ..........................................................................................9-1 Terminal Emulator and COM Port Problems ....................................................9-1 Host Fibre Channel Problems ............................................................................9-2 Array Problems ..................................................................................................9-3
Contents
Problems During Startup ...................................................................................9-4 RIO Subsystem Problems ..................................................................................9-4 Warning and Error Events .................................................................................9-5 Warnings .....................................................................................................9-5 Errors ..........................................................................................................9-7 Setting Up Debug Logging ................................................................................9-8 Using the Loader Diagnostics Menu .................................................................9-9 Using the Loader Utility Menu .........................................................................9-9 Understanding Disk-related Errors ....................................................................9-9 Disk Errors ..................................................................................................9-9 Disk Channel Errors ..................................................................................9-10 Voltage and Temperature Errors and Warnings ....................................... 9-11
Array Basics
Array Types ...................................................................................................... A-2 RAID 0 (Striped Disks) ............................................................................. A-2 RAID 1, RAID 10 (Mirrored Disks) .......................................................... A-2 RAID 3 ....................................................................................................... A-2 RAID 4 ....................................................................................................... A-3 RAID 5 ....................................................................................................... A-3 RAID 50 ..................................................................................................... A-3 Volume Sets ............................................................................................... A-4 Comparing RAID Levels .................................................................................. A-4 Mixing Disks from Different Manufacturers or with Different Capacities ...... A-5
Features and Specifications

Temperature and Voltage Monitoring ....................................................... B-4
LAN Configuration
Configuring the Data Manager for TCP/IP ...................................................... C-1 Using Address Resolution Protocol (ARP) ............................................... C-2 Configuring the LAN Settings ......................................................................... C-3 Configuring the IP Settings ........................................................................ C-3 Configuring the FTP Settings .................................................................... C-4 Configuring the Telnet Settings ................................................................. C-4 Configuring the SNMP Settings ................................................................ C-5 Configuring the Contact Settings ............................................................... C-6 Resetting the LAN Subsystem .................................................................. C-7
Theory of Operation
How the Data Managers Communicate ............................................................ D-1 How the Data Managers Present Their LUNs .................................................. D-3 Understanding Mirrored Configuration ............................................................ D-5 World Wide Name Impersonation ................................................................... D-5
Glossary Index
10
1
Introduction
This Users Guide explains how to install and use the Chaparral RIO Fibre-to-Fibre RAID solutions, models RFF244 and RFF288. They are designed as RAID subsystems to be used with a host system or storage area network (SAN) with a Fibre Channel (FC) connection and FC disk drives to provide a powerful storage subsystem. The RIO subsystems are fault-tolerant RAID systems that let you configure FC disk drives as fault-tolerant arrays. The arrays are presented as logical units to one or two host channels. The RIO subsystems also have write-back cache memory that is backed up by a battery in each Data Manager. The RIO subsystems have either four (RFF244) or eight (RFF288) FC host ports that support 1-Gbit and 2-Gbit speeds and either two (RFF244) or four (RFF288) FC disk channels. The RIO subsystems include the following features:
! ! ! ! ! !
Fully fault-tolerant, modular design Sequential data transfers from disk arrays at nearly 800 MB/sec sustained Greater than 50,000 I/O operations per second (IOPS) capability Operating system independentno special software or drivers required Four or eight 1-Gbit/2-Gbit Fibre Channel host ports Fibre Channel host interface supporting Fibre Channel-Arbitrated Loop (FC-AL), point-to-point, and switched fabric Two or four redundant 1-Gbit/2-Gbit FC disk channels Support for up to 248 FC devices organized in up to 32 arrays, 16 partitions per array up to a total of 128 logical unit numbers (LUNs) Configuration and management using a local area network (LAN) (10/100baseT) connection Support for cache memory of 512 MB using standard double data rate (DDR; DDR 266 supported) Dual Inline Memory Modules (DIMMs). DIMMs must be qualified by Chaparral; you can find the current list on the Chaparral Technical Support Web site, http://www.chaparralnet.com/ and click Support. Redundant power, AC, and cooling Built to fit into 1U high (1.75"), 19" rack Support for RAID levels 0, 1, 3, 4, 5, 10, 50, and just a bunch of disks (JBOD) Online capacity expansion allowing reconfiguration without interruptions
! !
! ! ! !
1-1
! !
Advanced disk utilities, array verification and recovery, and spare pooling Embedded Configuration Application Programming Interface (CAPI) for programmatic configuration and management of a Chaparral product Replacement of major system modules during online operation Firmware can be upgraded either in-band over FC or out-of-band using RS-232 or Ethernet Continuous runtime monitoring for warnings for out-of-spec temperatures and voltages, battery failures, fan failures, and internal errors
! !
For additional features and detailed specifications, see Appendix B, Features and Specifications.
About This Guide

This Users Guide describes how to install and configure your Chaparral RFF244 and RFF288 RAID subsystems. It assumes that you are familiar with the basic functions of your computer system. It also assumes that you are familiar with Fibre Channel configurations and basic network administration terminology.
Conventions
This Guide uses several typographical conventions to help explain how to use the RIO subsystem.
Convention Bold CTRL-R Definition Words in bold indicate items to select such as menu items or command buttons. Keys you press simultaneously. In this example, hold down the Ctrl key and press the r key. Tips give you information that can help you improve the performance of your system. Notes give you important information that may affect how you decide to set up your system.
Cautions warn you about actions that may permanently delete data or cause damage to your system.
1-2
Introduction
Safety
Electrical Surges
A powerful electrical surge (2,000 volts), primarily associated with a lightning strike, may cause a Data Manager to go offline or restart. You may have to manually put the Data Manager back online. Review the event log to determine the Data Managers status (see Displaying the Event Log on page 5-2) and take the appropriate action based on its status. For information about restarting a Data Manager, see Shutting Down and Restarting the Current Data Manager on page 7-2. For information about putting a Data Manager online, see Putting a Data Manager or Data Gate Online on page 7-6. Tests show that electrical surges up to 2000 volts coming through the AC connection will not damage the RIO subsystem hardware.
EU Declaration of Conformity
The RFF244 and RFF288 comply with the following Directives and European Norms issued by the Commission of the European Community:
! !
89/336/EECEU Electromagnetic Compatibility Directive EN 60950: 1999, 3rd editionSafety of Information Technology Equipment, Including Electrical Business Equipment CB Report to EN 60950: 1999, 3rd edition EN 55024CISPR 24Immunity EN55022: 1998Limits and Methods of Measurement of Radio Interference Characteristics of Information Technology Equipment, Class A EN 6100-3-2 1995Harmonic Emission EN 6100-3-3: 1995Voltage Flicker
! ! !
! !
UL Approvals
! !
UL approved cUL approved
1-3
Reference Documents
External Documents
! !
FC standards documents available from www.t11.org. The RAID Book: A Storage System Technology Handbook by Paul Massiglia, ISBN 1879936-90-9
Chaparral Documents
!
Chaparral Configuration Application Programming Interface (CAPI) Functional Specification is available for software engineers who need to develop a programmed interface for managing the RIO subsystem.
1-4
2
This chapter explains how to install and connect the RIO subsystem. The installation, configuration, and use of the RFF244 and RFF288 RAID subsystems in all but the most basic of environments requires certain expertise on the part of the user. Because there are many connections and configuration options involving host platforms, host bus adapters (HBAs), storage enclosures, disk drive devices, and applications, only general guidelines are included in this document. No in-depth discussion of integration of the RFF244 and RFF288 is included here due to the high level of expertise required on the part of the integrator and the level of support that may be needed from Chaparral. For more information about connectivity options, see Appendix D, Theory of Operation. You can mount the RIO subsystem in a standard 19" rack. Be sure that the operating environment meets the requirements found in Appendix B, Features and Specifications. To install the RIO subsystem, you need to complete the following tasks in sequence:
1 Unpack the RIO subsystem. See page 2-1. 2 Connect the battery. See page 2-5. 3 Install the RIO subsystem. See page 2-7. 4 Connect the RS-232. See page 2-11. 5 Connect the Ethernet port. See page 2-12. 6 Connect the power cables. See page 2-13. 7 Connect the Fibre Channel host and disk ports. See page 2-13.
Unpacking the RIO Subsystem
!
! ! ! !
Caution: You should use a suitable antistatic wrist or ankle strap and observe all conventional electrostatic discharge (ESD) precautions when handling modules.
Carefully unpack the RIO subsystem and ensure that you have all the parts specified below: RIO subsystem Power cables (2) RS-232 cables and DB-9 adapters (2) Ferrite cores (2)
2-1
! !
CD with Users Guide and additional documentation Rear-mounting kit (4 Phillips screws, 2 Kep nuts, two long side rails, two short side rails, and two receiver side rails)
To unpack the RIO subsystem:
1 Place the shipping container on a flat, clean, stable surface. 2 Carefully remove the RIO subsystem and verify the contents against the packing list. 3 Remove the foam from the sides of the RIO subsystem and remove it from the plastic
bag. Save the original shipping container and packing materials in case future reshipment is necessary.
4 Visually inspect the RIO subsystem and notify your freight carrier immediately of
any damage. You are now ready to connect the battery.
Understanding the RFF244 and RFF288

The RIO series of RAID products is fully fault-tolerant and modular in design. The RFF244 and RFF288 have four types of redundant modules:
!
Two Data ManagersEach includes a RAID controller processor, management interface, and the cache memory DDR DIMM (see Figure 2-1). Two Power ManagersEach contains a power supply and two cooling fans (see Figure 2-1). Two (RFF244) or four (RFF288) Data GatesEach includes two FC host ports and two FC disk sockets (see Figure 2-2). Two Power PortsEach provides AC power entry for one Power Manager and two cooling fans (see Figure 2-2).
2-2
Each pair of modules provides the redundancy for the functions listed above.
Power Manager A
Data Manager A
Data Manager B
Power Manager B
Figure 2-1. Front view
Power Port B
Data Gate 2
Data Gate 1
Power Port A
Figure 2-2. Rear view of the RFF244; Data Gates must be in the top two slots
2-3
Power Port A
Power Port B Data Gate 4
Data Gate 2 Data Gate 3
Data Gate 1
Figure 2-3. Rear view of the RFF288
You can hot swap each module as long as the other module of the pair is operating properly.
Caution: Do not leave any slots open on the RIO family of products. If you need to replace a module, leave the old module in place until you have the replacement. Leaving a slot open negatively affects the airflow and may cause the unit to overheat.
2-4
Connecting the Battery

Before you install the RIO subsystem, you must connect the battery inside each Data Manager. If you send a Data Manager back to your authorized dealer for repair, you should disconnect the battery.
! ! !
Caution: If the RIO subsystem is powered on, do not remove a module until you have the replacement module and are ready to install it. Leaving a slot open negatively affects the airflow and may cause the RIO subsystem to overheat. Caution: When you replace a module with the RIO subsystem powered on, install the new module within two minutes of removing the old module. The RIO subsystem may overheat if you take more than two minutes.
To connect the battery:
1 Press the latch of each handle of the Data Manager.

If the RIO subsystem is already powered on, do not pull the handles yet; only press the latches. The handle unlocks and takes the Data Manager offline.
Latches to push
2 If the RIO subsystem is already powered on, see if the STATUS LED on the module
turned red. Caution: If the LED did not turn red, do not proceed with removing the Data Manager. Check that the other Data Manager is online (see Displaying Module Status Information on page 5-5). If you must remove the only working Data Manager partner, be aware that removing it will cause users to lose access to data and disrupt the flow of data.
2-5
3 If the LED turned red, pull the handles outward to start sliding the module out.
4 Slide the module most of the way out of the slot. 5 Record the Media Access Control (MAC) address that is on the label of the Data
Manager for use in configuring LAN access. The label is on the top side of the Data Manager toward the back of the module.
6 Slide the Data Manager back in far enough to still see the battery connector and
receptacle.
Battery connector and receptacle Push wires down
7 Connect the battery cable to the receptacle as shown above. 8 Bend the wires over the side of the receptacle to permit the Data Manager to slide
into the slot.
2-6
9 Pushing the Data Managers handles, slide the Data Manager back into the slot until
the handles lock. You hear a click and the handles go into the locked position. Locking the handles makes the connection.
Push the handles in the direction of the arrows to lock them in place
10 Repeat steps 1 through 9 on the other Data Manager.
Installing the RIO Subsystem

You can install the RIO subsystem in a standard 1U high, 19" rack. You can either front- or rear-mount the RIO subsystem. Rear-mounting uses the rear-mounting kit.
Front-Mounting the RIO Subsystem

To front-mount the RIO subsystem, you must place it on top of a tray or another component in your rack and secure the brackets on the front of the RIO subsystem to the front of the rack. Note: Ensure that the RIO subsystem has adequate clearance for the fan, air intake vents (front, rear, and sides), and access to all connections. The RIO subsystem requires airflow clearance on all sides, except the bottom and top. While one person can install the RIO subsystem, we recommend using two people to ensure that you properly support the RIO subsystem during installation. Recommended tools and parts for this procedure:
! !
#2 Phillips screwdriver Four mounting screws that came with the rack
2-7
To front-mount the RIO subsystem in a rack:
1 Determine where in the rack you want to mount the RIO subsystem. 2 Using four mounting screws, attach the RIO subsystem to the front of the rack.
Use the screws that came with the rack. Install in the 19" rack according to the racks instructions.
3 Make sure the RIO subsystem is securely mounted and resting on top of a tray or
another component.
Rear-Mounting the RIO Subsystem

While one person can install the RIO subsystem, we recommend using two people to ensure that you properly support the RIO subsystem during installation. The rear-mount kit lets you mount the RIO subsystem at the rear of a rack, letting you free-mount the RIO subsystem without the support of a tray. The rear-mount kit includes (shown in Figure 2-4 and Figure 2-5):
! ! ! ! !
Two short side rails Two long side rails Two receiver side rails Four side-rail mounting screws (6-32 countersink) Two nuts (8-32 Kep)
Short side rail (long side rail not shown) Side-rail mounting screws
Figure 2-4. Rear-mounting side rail and screws
2-8
Short side rail (long side rail not shown)
Mounting screw (fixed in place) and nut Receiver side rail
Figure 2-5. Rear-mounting rails
Recommended tools for this procedure:

! ! !
#2 Phillips screwdriver Socket wrench for a #8 nut Four mounting screws that came with the rack
To install the RIO subsystem using the rear-mount kit:
1 Determine where in the rack you want to mount the RIO subsystem. 2 Determine whether you need to use the long or short side rails. 3 Using two of the side-rail mounting screws that came with the RIO subsystem,
connect the short or long side rails to the rear of each side of the RIO subsystem. See Figure 2-4.
4 Using two mounting screws from your rack on each side, connect the receiver side
rails to the rack. See Figure 2-5.
5 Lifting the RIO subsystem, slide the side rails on the RIO subsystem into the receiver
rails on the rack.
6 Screw on one mounting nut on each side and tighten the nuts securely.
See Figure 2-5.
7 Make sure the RIO subsystem is securely mounted.
2-9
Connecting the RIO Subsystem

The RIO subsystem has several types of data connections:
!
RS-232 serialfor configuration and management of the RIO subsystem (see Figure 2-6 and Connecting to the RS-232 Port on page 2-11). Ethernet (10/100BaseT)to connect to your local area network (LAN) to permit configuration and management of the RIO subsystem (see Figure 2-6 and Connecting to the Ethernet Port on page 2-12). Four or eight FC disk socketspermitting the connection of up to 248 disks (see Figure 2-7 and Connecting to the FC Disk Ports on page 2-19). Four or eight FC host socketspermitting connection to FC hosts, typically through an arbitrated loop or SAN with fabric (see Figure 2-7 and Connecting to the Fibre Channel Host and Disk Ports on page 2-13).
RS-232 serial ports
Shielded cable or ferrite core required
Ethernet ports
Figure 2-6. Front view showing connections
FC host sockets (ports 1 and 2 on each Data Gate)
FC disk sockets (ports 3 and 4 on each Data Gate)
SFP or cable with integrated SFP connector required for all FC ports
Figure 2-7. Rear view showing connections (RFF288 with four Data Gates shown; RFF244 has two Data Gates)
2-10
Connecting to the RS-232 Port

You use the RS-232 port to update the firmware, configure, and monitor the RIO subsystem using a computer with a VT-100 or ANSI terminal emulator. You can connect to the RS-232 port on each Data Manager. For more information about the configuration and management capabilities, see the chapters that follow in this manual. You must use the RS-232 cable that came with the RIO subsystem or one configured like it. The RS-232 cable is a standard 6-conductor, flatline cable with an RJ-11 to DB-9 adapter. The DB-9 pinout is as follows:
Table 2-1. DB-9 pinout Pin 2 3 5 Function Transmit Receive Ground
The RJ-11 cable pinout is straight through (not null modem) as follows:
Table 2-2. RJ-11 pinout Pin 1 2 3 4 5 6 Function No connection No connection Receive (RX) Transmit (TX) Ground No connection
Configure the RS-232 port in your terminal emulator software using the following settings:
!
Baud rate: 9600, 19200, 38400, 57600, or 115200; 115200 is the RIO subsystems default and the best for downloading firmware upgrades Data Bits: 8 Stop Bits: 1 Parity: None Flow Control: None or software XON/XOFF
! ! ! !
To connect to the RS-232 port:
1 Be sure the RIO subsystem is turned off. 2 Using the RS-232 cable that came with the RIO subsystem, connect the RJ-11 end of
the cable to the RS-232 serial port on one of the Data Managers. See Figure 2-6 on page 2-10.
3 Connect the DB-9 adapter to the serial (COM) port on the computer that will monitor
and configure the RIO subsystem.
2-11
4 Connect the other end of the RS-232 cable to the DB-9 adapter. 5 Repeat steps 2 through 4 on the other Data Manager.
You are now ready to connect the Ethernet port, if you plan to use it, or you can continue with connecting the power cables.
Connecting to the Ethernet Port

You use the Ethernet (10/100BaseT) port to configure and manage the RIO subsystem. You use this configuration option when you need to manage the RIO subsystem from a remote computer that is connected to your LAN. The RIO subsystems default IP address is 10.0.0.1. To comply with radiated emissions requirements, you must use one of the following options for the Ethernet connections:
!
Use a shielded Ethernet cable that has a properly terminated connection on the end that connects to your network (the RIO connector is properly terminated). Use the external, snap-on, ferrite cores that came with the RIO on an unshielded Ethernet cable.
To connect to the Ethernet port:
1 Be sure the RIO subsystem is turned off. 2 Connect one end of the Ethernet cable (RJ-45) to the Ethernet port on one of the Data
Managers. See Figure 2-6 on page 2-10.
3 If you are using unshielded cable, connect the snap-on, ferrite core to the cable about
1/2" from the RIO subsystem. To connect the ferrite core, create a loop with the Ethernet cable, open the ferrite core, snap the ferrite core onto the cable loop as shown below, and close the ferrite core.
4 Connect the other end of the Ethernet cable to a network hub, controller, or other
network connection. For information about configuring the RIO subsystem to use the Ethernet port, see Using the Ethernet Port for the First Time on page 3-4.
2-12

You are now ready to connect the power cables.
Connecting the Power Cables
Caution: Connect the Power Port to a power source only when the Power Port is fully installed in the RIO subsystem slot. Touching internal parts of the Power Port when it is connected to a power source will cause a dangerous electrical shock.
1 Attach the power cables to the Power Ports on the back of the RIO subsystem.
See Figure 2-3 on page 2-4.
2 Plug the power cables into a power source. 3 Power up the RIO subsystem (power switches on both Power Ports in the up
position) and allow it to come ready. The STATUS lights on all modules should be a steady green after the initial startup. For more information about the LEDs, see Understanding the LED Status Lights on page 2-20.
4 Verify that the RIO subsystem starts properly and that you see the initial screen of the
Disk Array Administrator. For more information, see Accessing the Disk Array Administrator Using the RS-232 Serial Port on page 3-2 and Accessing the Disk Array Administrator Using the Ethernet Port on page 3-4. You are now ready to connect the hosts to the FC host and disk ports.
Connecting to the Fibre Channel Host and Disk Ports

You can connect the RIO subsystem directly to one or more FC HBAs or to a FC switch or hub. Each Data Gate has two FC host ports that are looped together by default. You can disable the internal loop. For more information, see Configuring the Internal Host Port Hubs on page 7-10. You can attach FC disk drives to all of the RIO subsystems FC disk ports. You can connect up to 124 FC devices to the RFF244 and up to 248 devices to the RFF288.
2-13
You must use proper FC modules (for example, small form-factor pluggables [SFPs] and FC cable, either optical or copper). You must purchase standard 3.3-volt SFPs through your distributor. Go to the Chaparral Web site (http://www.chaparralnet.com) for a list of approved 2-Gbit SFPs. The SFP connector is available in two versions:
! !
Copper Optical
Figure 2-8 through Figure 2-13 show examples, using the Xyratex RS-1600-FC-FFX storage subsystem, of most of the host and disk connection options available. Each horizontal pair of Data Gates provides redundant paths (dual port connections) to the hosts and disk enclosures. Figure 2-8 shows the recommended configuration if you have one dual ported host and one disk enclosure to connect.
Figure 2-8. RFF244 connected to one host and one FC disk enclosure (internal Data Gate host hubs enabled)
2-14
Figure 2-9 shows the recommended configuration if you have two dual ported hosts and two disk enclosures to connect.
Figure 2-9. RFF244 connected to two hosts and two FC disk enclosures (internal Data Gate host hubs enabled)
Figure 2-10 shows the recommended configuration if you are using two switches with multiple hosts and have two disk enclosures to connect.
Figure 2-10. RFF244 connected to two hosts and two FC disk enclosures (internal Data Gate host hubs disabled)
2-15
Figure 2-11 shows the recommended configuration if you have four dual ported hosts and four disk enclosures to connect to an RFF288.
Figure 2-11. RFF288 connected to four hosts and four FC disk enclosures (internal Data Gate host hubs enabled)
2-16
Figure 2-12 shows the recommended configuration if you are using four switches with multiple hosts and have four disk enclosures to connect to an RFF288.
Figure 2-12. RFF288 connected to four hosts, four switches, and four FC disk enclosures (internal Data Gate host hubs disabled)
If you have an RFF288, you can continue to connect disk enclosures to your other two Data Gates. Once you use all of the disk channels, you can connect additional disk enclosures by daisy-chaining them. Figure 2-13 shows the recommended configuration if you are have four dual ported hosts and have 16 disk enclosures (the maximum you can connect) to connect to an RFF288.
2-17
Figure 2-13. RFF288 connected to four hosts and 16 FC disk enclosures (internal Data Gate host hubs disabled)
2-18
Connecting to the Fibre Channel Host Ports

Each Data Gate on the RFF244 and RFF288 has two FC host sockets (ports 1 and 2) that are looped together by default. You can disable the internal loop. For more information, see Configuring the Internal Host Port Hubs on page 7-10. To connect to the Fibre Channel host ports:
1 Insert an SFP into each Fibre Channel host port.

See Figure 2-7 on page 2-10. The SFP is keyed and can only go in one way. Be sure that the SFP locks into place.
2 Connect one end of the Fibre Channel cable to the SFP.

See Figure 2-7 on page 2-10. Also see the configuration diagrams on page 2-14 through page 2-18.
3 Connect the other end of the Fibre Channel cable to the hosts HBA or to a FC hub or
switch. See Figure 2-7 on page 2-10. Also see the configuration diagrams on page 2-14 through page 2-18.
4 Power up the connected hosts, hubs, or switches on the network if necessary.

You are now ready to connect the FC disk drives to the FC disk ports.
Connecting to the FC Disk Ports

Each Data Gate on the RFF244 and RFF288 has two FC disk sockets: ports 3 and 4. Sockets 3 and 4 are looped together on each Data Gate. To ensure redundant access to your disks, you should connect the FC disk cables to two different Data Gates. To connect disks to the FC disk channels:
1 Insert an SFP into each Fibre Channel disk socket or use integrated passive SFP
copper cables. See Figure 2-7 on page 2-10. The SFP is keyed and can only go in one way. Be sure that the SFP locks into place.
2 Connect one end of a FC cable to FC port 3 of one Data Gate on the back of the RIO
subsystem. See Figure 2-7 on page 2-10. Also see the configuration diagrams on page 2-14 through page 2-18.
3 Connect the other end of the FC cable to the FC disk drive or enclosure. 4 Connect one end of another FC cable to FC port 3 of a different Data Gate on the
back of the RIO subsystem. See Figure 2-7 on page 2-10. Also see the configuration diagrams on page 2-14 through page 2-18.
5 Connect the other end of the FC cable to the FC disk drive or enclosure. 6 Power up the FC disk drives or enclosure.
2-19
The RIO subsystem recognizes all FC disks connected to the FC disk ports and assigns any existing arrays a unique LUN address, which will be mapped as part of a unique FC address. You can configure the RIO subsystem to assign itself a LUN for in-band management. You have now completed the hardware installation steps. You can now set up the arrays for use from your operating system. For more information, see Creating Arrays on page 4-1.
Understanding the LED Status Lights

LED status lights are on the front and rear of the RIO subsystem. For more information about troubleshooting problems indicated by the status lights, see Chapter 9, Troubleshooting.
Power Manager A Fault Data Manager A Battery Data Manager A Status Data Manager A Ethernet Activity Data Manager A Ethernet Link Power Manager B Status
Power Manager A Status
Data Manager B Status
Data Manager B Battery
Data Manager B Ethernet Link
Data Manager B Ethernet Activity
Power Manager B Fault
Figure 2-14. Front LED status lights
2-20
Data Gate 2, FC Host Port 1 Activity Power Port B Status Power Port B Fault
Data Gate 2, FC Host Port 2 Activity
Data Gate 2, FC Disk Port 3 Activity
Data Gate 2, FC Disk Port 4 Activity Power Port A Fault Power Port A Status
Data Gate 2 Status
Data Gate 2, FC Host Port 1 Link
Data Gate 2, FC Host Port 2 Link
Data Gate 2, FC Disk Port 3 Link
Data Gate 2, FC Disk Port 4 Link
Figure 2-15. Rear LED status lights
2-21
Table 2-3 and Table 2-4 describe the meaning of the LED status lights located on the front and rear of the RIO subsystem. For information about determining the cause of an amber or red LED, see Chapter 5, Monitoring System Status.
Table 2-3. Front LED status lights Module Data Manager LED label STATUS Description Data Manager Status Color Green Amber Red Function Solid when RIO subsystem is on and this Data Manager has no fault Flashing when initializing Solid if LAN subsystem or battery has a fault Solid when RIO subsystem is on and this module has a fault (is offline): ! Latch not fully closed ! Temperature or voltage in failure range Solid when RIO subsystem is on and battery is working properly Flashing when RIO subsystem is powered off and data in the battery-backed cache is valid. If the Data Manager is not gracefully shutdown, also flashes amber, whether there is data in the write-back cache or not. Solid when RIO subsystem is on and write-back cache is disabled Solid when RIO subsystem is on and battery is not working properly Flashing or solid when 10/100BaseT link is active or busy Solid when Ethernet link is detected When Ethernet link is not detected Solid when LAN subsystem of Data Manager has a fault Solid when RIO subsystem is on and module has no faults Solid when RIO subsystem is on and module has a fault: Overvoltage, overload, or temperature in failure range ! DC failure of internal power supply ! Fan failure
!
BATT
Battery
Green Amber
Red ACT LNK Ethernet activity Ethernet link status Green Green Off Amber or Red Power Manager STATUS FAULT Power Manager status Power Manager fault Green Red
2-22
Table 2-4. Rear LED status lights Module Data Gate LED label STATUS Description Data Gate Status Color Green Amber Red Function Solid when RIO subsystem is on and this Data Gate has no fault Flashing when RIO subsystem is initializing Solid when RIO subsystem is on and this module has a fault (is offline): ! Latch not fully closed ! Internal onboard temperature in failure range Solid on when FC link is active Off when no I/O activity Solid on when FC link is up and detects a valid receive signal on SFP input Off when external FC link is disconnected or not established Solid on when FC link is active Solid off when no I/O activity Solid on when FC link is up and detects a valid receive signal on SFP input Off when external FC link is disconnected or not established Solid on when FC link is active Solid off when no I/O activity Solid on when FC link is up and detects a valid receive signal on SFP input Off when external FC link is disconnected or not established Solid on when FC link is active Solid off when no I/O activity Solid on when FC link is up and detects a valid receive signal on SFP input Off when external FC link is disconnected or not established Solid when RIO subsystem is on and module has no faults Solid when RIO subsystem is on and module has a fault: Loss of alternating current (AC) power or blown AC fuse ! Fan failure
!
ACT 1
FC host activity for host port 1 FC host link status for host port 1 FC host activity for host port 2 FC host link status for host port 2 FC disk activity for disk port 3 FC disk link status for disk port 3 FC disk activity for disk port 4 FC disk link status for disk port 4 Power Port status Power Port fault
Green
LNK 1
Green
ACT 2
Green
LNK 2
Green
ACT 3
Green
LNK 3
Green
ACT 4
Green
LNK 4
Green
Power Port
STATUS FAULT
Green Red
2-23
Understanding How the Data Managers Work Together

Below are terms associated with how the pair of Data Managers work together:
!
Data Manager A and BOne Data Manager is designated as Data Manager A and the other is designated as Data Manager B. The Data Managers identity displays continuously at the bottom of the Disk Array Administrator screens. FailbackThe act of returning ownership of Data Manager resources from a surviving Data Manager to a previously failed or offline (but now active) Data Manager. The resources include disk arrays, cache data, and host ID information. FailoverThe act of temporarily transferring ownership of Data Manager resources from a failed or offline Data Manager to the surviving Data Manager. The resources include disk arrays, cache data, and host ID information. Force offlineOne Data Manager can force the other Data Manager offline by resetting it and taking it offline. OtherThe opposite Data Manager from the one currently being used (that is, not the local Data Manager). OwnershipA single Data Manager has ownership of the following resources: arrays and dedicated spares. When a Data Manager fails, the other Data Manager assumes temporary ownership of its resources. Put offlineWhen you either press the latch on a Data Manager handle or use the Disk Array Administrator software to gracefully take a Data Manager offline. Put onlineWhen a surviving Data Manager removes the reset from the other Data Manager, it puts it back online. The other Data Manager will restart and attempt to come online. Dual StartWhen both Data Managers start at the same time, they exchange information related to their current configuration and the ownership of resources. The time and date of Data Manager B is synchronized with that of Data Manager A. Add ArrayWhen a Data Manager adds an array, that Data Manager is owner of the array, as well as any dedicated spare drives. Arrays and dedicated spares are not visible to the other Data Manager when both Data Managers are online. Delete ArrayA Data Manager may only delete arrays that it owns. Pool Spare ConfigurationPool spares are visible to both Data Managers when both Data Managers are online. FailoverWhen a failover occurs, the surviving Data Manager displays FAILED OVER in the Disk Array Administrator, in the area between the board temperature and date. At this point, the arrays and dedicated spares of the failed or offline Data Manager now belong to the surviving Data Manager. Resources from the failed Data Manager are tagged with (FO).
You should understand how the Data Managers act in different scenarios.
!
! !
2-24
FailbackWhen a failback occurs, the Data Manager coming online regains control of its arrays and dedicated spares from the other Data Manager.
For more information, see Appendix D, Theory of Operation.
Replacing Modules
You can replace each module in the RFF244 or RFF288 without powering down the system. You only need to power down the system when you plan to shut down the whole system for maintenance, repair, or a move. You know that a module needs replacement by:
! ! !
LED status lights (see Understanding the LED Status Lights on page 2-20) Alarms (see Changing the Alarm Mute Setting on page 7-16) Events in the Disk Array Administrator software (see Displaying the Event Log on page 5-2).
2-25
Removing a Module
As long as the other module of the type you are removing remains active, you can remove a module without powering down the system. For an RFF288, you must have one working Data Gate in each horizontal pair.
! ! !
Caution: Do not remove a module until you have the replacement module and are ready to install it. Leaving a slot open negatively affects the airflow and may cause the RFF244 or RFF288 to overheat.
Caution: When you replace a module with the RIO subsystem powered on, install the new module within two minutes of removing the old module. The RIO subsystem may overheat if you take more than two minutes.
The steps below apply to removing a Data Manager, Data Gate, or Power Manager. The steps for removing a Power Port are different. See Removing a Power Port on page 2-28. To remove a Data Manager, Data Gate, or Power Manager:
1 Press the latch of each handle of the module you want to remove.
Do not pull the handles yet; only press the latches.
Latches to push
2-26
Latches to push
The handle unlocks and takes the module offline. Power Managers have only one handle.
2 If you are removing a Data Manager or Data Gate, see if the STATUS LED on the
module turned red. Caution: If the LED did not turn red, do not proceed with removing the Data Manager. Check that the other Data Manager is online (see Displaying Module Status Information on page 5-5). If you must remove the only working Data Manager partner, be aware that removing it will cause users to lose access to data and disrupt the flow of data.
3 If the LED turned red, pull the handles outward to start sliding the module out.
Power Managers have only one handle.
4 Slide the module all the way out of the slot.
2-27
Removing a Power Port

As long as one Power Port remains active, you can remove the other Power Port without powering down the system.
! ! !
Caution: Do not remove a module until you have the replacement module and are ready to install it. Leaving a slot open negatively affects the airflow and may cause the RFF244 or RFF288 to overheat.
Caution: When you replace a module with the RIO subsystem powered on, install the new module within two minutes of removing the old module. The RIO subsystem may overheat if you take more than two minutes. Caution: Connect the Power Port to a power source only when the Power Port is fully installed in the RIO subsystem slot. Touching internal parts of the Power Port when it is connected to a power source will cause a dangerous electrical shock.
The steps below apply to removing a Power Port. The steps for removing a Data Manager, Data Gate, or Power Manager are different. See Removing a Module on page 2-26. To remove a Power Port:
1 Turn off the power to the power port you are removing. 2 Unplug the power cable. 3 Lift up the handle of the Power Port.
The Power Port starts to slide out of its slot.
4 Slide the Power Port out of the slot.
2-28
Installing a Module
You can install any module without powering down the system. Caution: When you replace a module with the RIO subsystem powered on, install the new module within two minutes of removing the old module. The RIO subsystem may overheat if you take more than two minutes.
! !
The steps below apply to installing a Data Manager, Data Gate, or Power Manager. The steps for installing a Power Port are different. See Installing a Power Port on page 2-30. To install a Data Manager, Data Gate, or Power Manager:
1 Insert the module part of the way into the appropriate slot.
For Data Managers (shown below) and Data Gates, you must make sure the rails on both sides of the module slide into the card guide on both sides of the slot. For Power Managers, the left Power Manager goes in with the component side facing down. Always make sure that the Power Manager LEDs are toward the outside of the RIO subsystem and the Power Manager handle is next to the Data Manager handles.
Card guide
Card guide
rail
2-29
2 Pushing the handles in, slide the module the rest of the way into the slot until the
handles lock. You hear a click and the handles go into the locked position. Locking the handles makes sure the module is connected properly. Power Managers have only one handle.
Push the handles in the direction of the arrows to lock them in place
On a Data Manager or Data Gate, the STATUS LED should flash amber as it initializes and turn solid green to show that the module is online. If the STATUS LED turns red, the module has not gone online and likely failed its self-test. Try to put the module online (see Putting a Data Manager or Data Gate Online on page 7-6) or check the errors that were generated (Displaying the Event Log on page 5-2). For additional information, see Chapter 9, Troubleshooting.
Installing a Power Port

The steps below apply to installing a Power Port. The steps for installing a Data Manager, Data Gate, or Power Manager are different. See Installing a Module on page 2-29.
Caution: When you replace a module with the RIO subsystem powered on, install the new module within two minutes of removing the old module. The RIO subsystem may overheat if you take more than two minutes.
2-30
! !
Caution: Do not plug the power cable into the Power Port until the Power Port is properly installed in the enclosure.
Caution: Connect the Power Port to a power source only when the Power Port is fully installed in the RIO subsystem slot. Touching internal parts of the Power Port when it is connected to a power source will cause a dangerous electrical shock.
To install a Power Port:
1 Be sure that you have the correct Power Port.

The right and left Power Ports are different and are not interchangeable. The LEDs are always at the top of the Power Port and the power cable connector is toward the outside of the RIO subsystem.
2 Lift up the handle on the Power Port. 3 Holding the handle up, slide the Power Port part way into the slot until it stops. 4 Push the handle down to engage the Power Port and slide it the rest of the way into
the slot until the handle is all the way down.
5 Attach the power cable and turn on the switch.
2-31
Upgrading or Replacing the Memory DIMMs

Each Data Manager has a CPU synchronous dynamic random access memory (SDRAM) DIMM for CPU memory and a double data rate (DDR) DIMM for cache memory. You can upgrade or replace both memory DIMMs on each Data Manager. DIMMs must be qualified by Chaparral. You can find the current list on the Chaparral Technical Support Web site, http://www.chaparralnet.com/ and click Support. Note: The RIO subsystem will be unavailable when you upgrade the cache memory on one Data Manager until after you upgrade the DIMMs on both Data Managers and reinstall both Data Managers. The RIO subsystem will not work with different types of cache memory installed in each Data Manager. To replace a memory DIMM:
1 Remove one Data Manager.

For information about removing a Data Manager, see Removing a Module on page 2-26.
2 Pull the memory DIMM clips apart as shown below.

The cache memory DIMM has two clips. The CPU memory DIMM has only one clip
Clip CPU memory DIMM Clip Cache memory DIMM Clip
2-32
3 Slide the DIMM straight out toward the center of the Data Manager as shown below.
4 Install the new memory DIMM by sliding it straight into the slot and pushing firmly
until the you hear and feel the clips click into place. The CPU memory DIMM has only one clip.
5 Install the Data Manager in the RIO subsystem.

For information about installing a Data Manager, see Installing a Module on page 2-29.
6 Repeat steps 1 through 5 for the other Data Manager.
2-33
2-34
3
You can display and change a variety of settings using the Disk Array Administrator software. Using the Disk Array Administrator, you can:
!
Create and manage arrays (see Chapter 4, Creating and Managing Arrays and Partitions) Monitor system status (see Chapter 5, Monitoring System Status) Manage spares (see Chapter 6, Managing Spares) Configure the RIO subsystem (see Chapter 7, Configuring the controllerRIO Subsystem) Manage disk drives and enclosures (see Chapter 8, Managing Disk Drives and Enclosures)
! ! !
You can access the Disk Array Administrator software using the RS-232 serial port or the Ethernet port connections on the Data Managers. You must connect a computer with terminal emulator software to the serial or Ethernet port according to Chapter 2, Hardware Installation. Each Data Manager has one RS-232 and one Ethernet port. You have access to all host and disk ports on all installed Data Gates from either Data Manager. However, you can only manage arrays and dedicated spares from the Data Manager where the array was created, that is, each Data Manager can only see its own arrays and dedicated spares. Each Data Manager can see all pool spares and available drives (drives not used in an array or as a dedicated spare). You must perform some configuration functions from the Data Manager where you want the change to take place:
! ! !
Upgrading firmware (see page 7-80) Configuring LAN settings (see page C-3) Creating and managing arrays, partitions, and dedicated spares (see Chapter 4, Creating and Managing Arrays and Partitions and Managing Dedicated Spares on page 6-2)
You can perform other configuration functions from either Data Manager and have the same changes made automatically on the other Data Manager:
! !
Managing pool spares (see page 6-4) Configuring host channels (see page 7-15)
3-1
! !
Configuring disk channels (see page 7-36) Configuring the following RIO subsystem settings: Alarm mute (see page 7-56) Lock cache (see page 7-60) Configuring the following disk settings: Write-back cache (see page 8-5) SMART (see page 8-8) Enclosure management processor (EMP) (see page 8-10)
Accessing the Disk Array Administrator Using the RS-232 Serial Port
You can access the Disk Array Administrator software using the RS-232 serial port. You must use a straight-through serial cable. You cannot use a null modem cable. Configure the RS-232 port in your terminal emulator software using the following settings:
Setting Terminal Emulation Font Translations Columns Value VT-100 or ANSI (for color support) Terminal None 80
Set the communications parameters for the terminal program as follows:

Setting Baud Rate Data Bits Stop Bits Parity Flow Control Connector Value 115,200 8 1 None Software (XON/XOFF) or None COM1 (typically)
3-2
To access the Disk Array Administrator software using the RS-232 serial port:
1 From the computer connected to the RIO subsystem, start your terminal emulation
software. Be sure that your terminal emulation software is set to use the correct COM port on your computer. See Terminal Emulator and COM Port Problems on page 9-1 for more details on how the RIO subsystem can auto-detect the baud rate.
2 Press CTRL-R.
This refreshes the screen. The initial Chaparral Disk Array Administrator screen displays. If any events have occurred, each event displays. Informational events scroll by automatically. Warning events (yellow text on a black background) and error events (white text on a red background) display until you press Enter or Esc. Once all the events display, the initial screen displays. The initial screen alternates between displaying the date, time, and temperature and the model number of your RIO subsystem. You can bypass all events by pressing Tab. However, events provide valuable information about the status of your RIO subsystem and you should review them. All events are also stored in the event log (see Displaying the Event Log on page 5-2).
3 Press Enter.
The System Menu displays.
3-3
You can now perform all of the functions described in the following chapters. All steps start from the System Menu.
Accessing the Disk Array Administrator Using the Ethernet Port

You can access the Disk Array Administrator software using the Ethernet port and Telnet. Windows users may want to obtain a terminal emulator program such as HyperTerminal Private Edition from Hilgraeve that supports both Telnet protocol and serial port protocol. In addition, such programs support the color display from the Disk Array Administrator. You can configure a variety of settings for the Ethernet connection. For more information, see Configuring the LAN Settings on page C-3.
Using the Ethernet Port for the First Time

Before you can access the Disk Array Administrator software, you must set the IP address and subnet mask for the Data Manager. The default IP address is 10.0.0.1 and the default port number is 23. You can do this one of three ways:
!
Setting up your computer with an IP address that is compatible with the Data Manager default of 10.0.0.1, such as 10.0.0.42. Using address resolution protocol (ARP) to set the address. See Using Address Resolution Protocol (ARP) on page C-2. Using the serial connection to the Data Manager and setting the address. See Configuring the IP Settings on page C-3.
Once you set the IP address and subnet mask, you can use the steps in the next section to access the Disk Array Administrator software.
Accessing the Disk Array Software Using the Ethernet Port

Note: You can use the RS-232 and Telnet connections at the same time. If a Telnet session is active, you can see the activity through the RS-232 connection, and you can make changes to the configuration using the RS232 connection. You can configure a variety of settings for the Ethernet connection. For more information, see Configuring the LAN Settings on page C-3.
3-4
To access the Disk Array Administrator software using the Ethernet port and the Telnet utility:
1 Set up the IP address and subnet mask as described in Using the Ethernet Port for the
First Time on page 3-4.
2 At the DOS or UNIX prompt, enter telnet and press Enter.

The exact steps for your Telnet program may be different. The remaining steps work for HyperTerminal Private Edition.
3 Using the Terminal menu, select Preferences. 4 Select VT100 Arrows option, VT-100/ANSI emulation, and Terminal font. Click
OK. If you are using Windows and Telnet, you must configure the preferences and font from the Terminal menu each time as shown below.
Click Font to set the font as shown here.
5 Enter the IP address or, using the Connect menu, select the Data Manager IP address
from the menu (if present) and press Enter. If needed, enter the port number. The default port is 23. The Enter Password screen displays.
3-5
6 Enter your password and press Enter.

There is no default password. If you have not set up a password, just press Enter. The initial Chaparral Disk Array Administrator screen displays. If any events have occurred, each event displays. Informational events scroll by automatically. Warning events (yellow text on a black background) and error events (white text on a red background) display until you press Enter or Esc. Once all the events display, the initial screen displays. The initial screen alternates between displaying the date, time, and temperature and the model number of your RIO subsystem. You can bypass all events by pressing Tab. However, events provide valuable information about the status of your RIO subsystem and you should review them. All events are also stored in the event log (see Displaying the Event Log on page 5-2).
7 Press Enter.
The System Menu displays.
You can now perform all of the functions described in the following chapters. All steps start from the System Menu.
3-6
Navigating the Disk Array Administrator Software

You can navigate the Disk Array Administrator software using your keyboard. Table 3-1 describes the primary navigation and selection methods.
Table 3-1. Disk Array Administrator navigation To Select a menu item Do this Press the or and press Enter. or Press the letter that is a different color (or highlighted) in a menu item (hot key). Press Esc, CTRL-Z, or . Press the or . Press Tab
Return to the previous menu or screen without saving your changes Scroll through the available choices for a setting Bypass the list of recent events
Note: After four minutes of inactivity, the Disk Array Administrator software times out and returns to the initial screen.
Changing the Screen Display

After you have accessed the Disk Array Administrator software, you can change the screen display using a combination of keystrokes, as shown on the System Menu. Table 3-2 lists the keystrokes required to change various screen displays.
Table 3-2. Changing screen displays Select Ctrl-A Ctrl-B Ctrl-E Ctrl-H Ctrl-R Ctrl-Z, Esc, or Function Toggles between ANSI and VT100 character sets (use VT100 for legacy systems) Toggles between black and white and color Toggles between the event log, hardware information, and configuration information screens Toggles between the Help screen and list of shortcut keys Refreshes screen Escapes or quits the current menu
3-7
Disk Array Administrator Menu Tree

Figure 3-1 on page 3-8 and Figure 3-2 on page 3-9 describe the complete Disk Array Administrator menu hierarchy. In the Disk Array Administrator, menu options that are not accessible appear gray. For example, the Array Menu is not accessible unless one or more arrays exist.
Figure 3-1. Menu tree
3-8
Figure 3-2. Menu tree (continued)
3-9
3-10
4
Using the Disk Array Administrator, you can create and manage arrays and partitions. You can perform the following array-related functions:
! ! !
Create arrays (see page 4-1) Manage arrays (see page 4-12) Manage partitions (see page 4-27) manger
Creating Arrays
You can create an array anytime. You can create arrays from either Data Manager A or Data Manager B. Arrays you create from one Data Manager are not visible through the RS-232 or Ethernet port of the other Data Manager. However, all unused disk drives connected to all Data Gates and all pool spares are available to both Data Managers. For more information about how the Data Managers work together see Understanding How the Data Managers Work Together on page 2-24 and Appendix D, Theory of Operation. The maximum size for any array is 2 TB. Table 4-1 describes the drive requirements for each RAID level.
Table 4-1. Drive requirements by RAID level Minimum number of drives 1 2 2 3 3 3 6 Maximum number of drives 1 16 16 16 16 16 32
RAID level Volume Set RAID 0 RAID 1 (Mirrored) RAID 3 RAID 4 RAID 5 RAID 50
Note: Before you create more than one array, you must be sure that your host operating system supports multiple logical unit numbers (LUNs). Most operating systems do, or have an option you can enable to support multiple LUNs. If your operating system does not support multiple LUNs, the host will only be able to see one array at LUN 0.
4-1
Before you create an array, you must decide whether you want to partition the array. You can create an array one of two ways:
!
As a single-partition arrayan array that stores all data in a single partition and is accessed by a single LUN (see page 4-2). As a multiple-partition arrayan array that can have one or more partitions, with each partition assigned its own LUN (see page 4-7).
For more information about partitions, see Understanding Partitions on page 4-27.
Creating a Single-Partition Array

You can create an array that has just one partition. Once you create a single-partition array, you cannot add more partitions. Single-partition arrays work well in environments that need one large, fault-tolerant storage space for data on one server. A large database accessed by users on a single server that is used only for that application is an example. To create a single-partition array:
1 From the System Menu, select Add an Array and press Enter.
The Enter Array Name screen displays.
2 Enter a name for the array and press Enter.

You can use up to 20 characters. You can include any characters in the name, including spaces. If you do not want to name the array, you can just press Enter. You can add or change the name later. The system asks if you want to create one partition now for the entire array.
4-2
3 Select Yes to create a single-partition array and press Enter.

If you want to create a multiple-partition array, see Creating a Multiple-Partition Array on page 4-7. The LUN screen displays.
4 Select the LUN for the array and press Enter.

The LUN that displays is the suggested default LUN assignment. Note: Most UNIX, Linux, and Macintosh operating systems require that the CAPI LUN, which is the LUN assigned to each Data Manager, be set to a higher value than all array LUNs. Before creating your first array, change the CAPI LUN to a higher value. If you are using a custom software application to configure and manage the controller (this application uses CAPI to communicate with the Data Manager), you must have a CAPI LUN. If you are not using a custom application, and therefore are not using CAPI, select NONE as the CAPI LUN. This allows your first array to be seen at LUN 0. The system warns you about the LUN for UNIX and Macintosh, as above, the first time you create an array. Press Enter and the system asks if you want to be warned again. Select No to avoid receiving this warning again or select Yes to be warned the next time you create an array. The RAID Type screen displays.
4-3
5 Select the RAID type: RAID0, RAID3, RAID4, RAID5, RAID50, VOLUME (a
single drive similar to just a bunch of disks [JBOD] except that it includes metadata), or MIRRORED and press Enter. Note: A RAID 10 array is created when there are more than two drives in a mirrored array. See Appendix A, Array Basics, for more information. If you selected RAID 50 as the array type, the Select RAID 50 Array Size screen displays (not shown) with all possible configurations for the array and drive combinations. Select the configuration you want, press Enter, and skip to step 7. If you selected any array type other than RAID 50, the Number of Drives screen displays.
4-4
6 Enter the number of drives (excluding spares) you want in the array and press Enter.
The Select Drives screen displays. The list includes all available drives, that is, drives that are not members of an array and are not assigned as a dedicated or pool spare, on either Data Manager. The screen includes the following information for each drive: DG:ID (Data Gate and loop ID for each channel; ------ shows a single ported drive) Size Vendor Model or serial number or node and WWN (press T to toggle the display) Rev (firmware revision) Usage Drive usage
7 Select the drives you want to use for the array and press Enter.
You select a drive by highlighting it and pressing Enter. Each selected drive turns gray in the drive list. After you press Enter for the number of drives you entered previously, the system automatically goes to the next screen. To skip a drive, use the or key. You may want to select drives from different disk channels (Data Gates), which keeps the array online even if one channel becomes unavailable. If the array is mirrored, RAID 3, RAID 4, RAID 5, or RAID 50 and you have one or more drives left, the Number of Spares screen displays.
8 If the Number of Spares screen displays, enter the number of spares you want to add
and press Enter. This creates dedicated spares that can only be used by this array. A dedicated spare drive will not be available for any other use. For more information about spares, see Chapter 6, Managing Spares. If you do not want a dedicated spare, enter 0. The Select Drives screen displays.
4-5
9 If the Select Drives screen displays, select the drive you want to use as a dedicated
spare and press Enter. Only available drives, that is, drives that are not members of an array and are not assigned as dedicated or pool spares, display. You can delete a dedicated spare from the array at any time. For more information, see Deleting a Dedicated Spare on page 6-3. You select a drive by highlighting it and pressing Enter. Each selected drive turns gray in the drive list. After you press Enter for the number of drives you entered previously, the system automatically goes to the next screen. To skip a drive, use the or key. To toggle the display between the drive model number, serial number, and the node and WWN, press T. If the array you are creating is a RAID 0, RAID 3, RAID 4, RAID 5, RAID 10, or RAID 50, the Chunk Size screen displays.
10 If the Chunk Size screen displays, select the chunk size and press Enter.
The chunk size is the amount of contiguous data that is written to an array member before moving to the next member of the array. To determine the appropriate chunk size, refer to your operating system documentation. For example, the default chunk size for Windows NT and many other operating systems is 64 KB. If you are using the array for a database with very small records, you may want to use a smaller chunk size. If the array you are creating is a RAID 3, RAID 4, RAID 5, RAID 50, or Mirrored, the Array Init Options screen displays. The current option has an * next to it.
11 If the Array Init Options screen displays, select the option you want and press Enter.
Offline InitializationUsing this option means you must wait for the array initialization process to finish before using the array. It uses the zero method to create the array, which is faster than the verify method. Online InitializationUsing this option lets you begin using the array immediately after creating it, while the array initialization process runs. It uses the verify method to create the array, which takes longer than the zero method. The system confirms that you want to create the array.
4-6
12 Select Yes and press Enter.

A message notifies you that the array is being created and shows the progress of the initialization process. The array initialization process takes from several minutes to more than an hour depending on the array type (volume, RAID 0, and RAID 1 are the fastest), array size, drive speed, and other processes running on the RIO subsystem. You can press Esc to return to the Disk Array Administrator menus and perform other functions. To check the progress of the array initialization, select Array Menu from the System Menu. The status of the initialization displays in the list of arrays. If you find that you need to change the disks or some other array configuration, you can stop the array initialization process. See Stopping the Array Initialization Process on page 4-15. Note: Most operating systems, such as Windows NT 4.0, require you to restart the host system to see a new LUN. Windows 2000 can recognize new LUNs by selecting Refresh from the Computer Management Window. NetWare v3.12 and later can recognize new devices by typing the command SCAN FOR NEW DEVICES at the console prompt. Other operating systems might have similar features.
Creating a Multiple-Partition Array

You can create an array that is set up for more than one partition. Note: Once you create a multiple-partition array, you must create at least one partition before you can use the array. See Adding a Partition on page 4-15. Multiple-partition arrays work well when you have very large disk drives and you want to make the most efficient use of disk space for fault tolerance (parity and spares). For more information, see Understanding Partitions on page 4-27. To create a multiple-partition array:
1 From the System Menu, select Add an Array and press Enter.
The Enter Array Name screen displays.
4-7
2 Enter a name for the array and press Enter.

You can use up to 20 characters. You can include any characters in the name, including spaces. If you do not want to name the array, you can just press Enter. You can add or change the name later. The system asks if you want to create one partition now for the entire array.
3 Select No to create a multiple-partition array and press Enter.

If you want to create a single-partition array, see Creating a Single-Partition Array on page 4-2. The RAID Type screen displays.
4 Select the RAID type: RAID0, RAID3, RAID4, RAID5, RAID50, VOLUME (a
single drive similar to just a bunch of disks (JBOD) except that it includes metadata), or MIRRORED and press Enter. Note: A RAID 10 array is created when there are more than two drives in a mirrored array. See Appendix A, Array Basics, for more information. If you selected RAID 50 as the array type, the Select RAID 50 Array Size screen displays (not shown) with all possible configurations for the array and drive combinations. Select the configuration you want, press Enter, and skip to step 7.
4-8
If you selected any array type other than RAID 50, the Number of Drives screen displays.
5 Enter the number of drives (excluding spares) you want in the array and press Enter.
The Select Drives screen displays (shown below). The list includes all available drives, that is, drives that are not members of an array and are not assigned as a dedicated or pool spare, on either Data Manager. The list includes the following information for each drive: DG:ID (Data Gate and loop ID for each channel; ----- shows a single ported drive) Size Vendor Model, serial number, or node and WWN (press T to toggle the display) Rev (firmware revision) Usage
4-9
6 Select the drives you want to use for the array and press Enter.
You select a drive by highlighting it and pressing Enter. Each selected drive turns gray in the drive list. After you press Enter for the number of drives you entered previously, the system automatically goes to the next screen. To skip a drive, use the or key. You may want to select drives from different disk channels (Data Gates), which keeps the array online even if one channel becomes unavailable. If the array is mirrored, RAID 3, RAID 4, RAID 5, or RAID 50 and you have one or more drives left, the Number of Spares screen displays.
7 If the Number of Spares screen displays, enter the number of spares you want to add
and press Enter. This creates dedicated spares that can only be used by this array. A dedicated spare drive will not be available for any other use. For more information about spares, see Chapter 6, Managing Spares. If you do not want a dedicated spare, enter 0. The Select Drives screen displays.
8 If the Select Drives screen displays, select the drive you want to use as a dedicated
spare and press Enter. Only available drives, that is, drives that are not members of an array and are not assigned as a dedicated or pool spares, display. You can delete a dedicated spare from the array at any time. For more information, see Deleting a Dedicated Spare on page 6-3. You select a drive by highlighting it and pressing Enter. Each selected drive turns gray in the drive list. After you press Enter for the number of drives you entered previously, the system automatically goes to the next screen. To skip a drive, use the or key. To toggle the display between the drive model number, serial number, and the node and WWN, press T. If the array you are creating is a RAID 3, RAID 4, RAID 5, RAID 10, or RAID 50, the Chunk Size screen displays.
4-10
9 If the Chunk Size screen displays, select the chunk size and press Enter.
The chunk size is the amount of contiguous data that is written to an array member before moving to the next member of the array. To determine the appropriate chunk size, refer to your operating system documentation. For example, the default chunk size for Windows NT and many other operating systems is 64 KB. If you are using the array for a database with very small records, you may want to use a smaller chunk size. If the array you are creating is a RAID 3, RAID 4, RAID 5, RAID 50, or Mirrored array, the Array Init Options screen displays. The current option has an * next to it.
10 If the Array Init Options screen displays, select the option you want and press Enter.
Offline InitializationUsing this option means you must wait for the array initialization process to finish before using the array. It uses the zero method to create the array, which is faster than the verify method. Online InitializationUsing this option lets you begin using the array immediately after creating it, while the array initialization process runs. It uses the verify method to create the array, which takes longer than the zero method. The system confirms that you want to create the array.

A message notifies you that the array is being created and shows the progress of the initialization process. The array initialization process takes from several minutes to more than an hour depending on the array type (volume, RAID 0, and RAID 1 are the fastest), array size, drive speed, and other processes running on the RIO subsystem. You can press Esc to return to the Disk Array Administrator menus and perform other functions. To check the progress of the array initialization, select Array Menu from the System Menu. The status of the initialization displays in the list of arrays. If you find that you need to change the disks or some other array configuration, you can stop the array initialization process. See Stopping the Array Initialization Process on page 4-15. You must create at least one partition before you can use the array. See Adding a Partition on page 4-15. Note: Most operating systems, such as Windows NT 4.0, require you to restart the host system to see the new array. Windows 2000 can recognize new LUNs by selecting Refresh from the Computer Management Window. NetWare v3.12 and later can recognize new devices by typing the command SCAN FOR NEW DEVICES at the console prompt. Other operating systems might have similar features.
4-11
Managing Arrays
The Disk Array Administrator software lets you manage your arrays in a variety of ways. You can:
! ! ! ! ! ! ! ! !
View array and drive status (see page 4-12) Stop the initialization process (see page 4-15) Verify an array (see page 4-18) Reconstruct an array (see page 4-20) Expand array capacity (see page 4-21) Change the array name (see page 4-23) Change array ownership (see page 4-24) Trust an array (see page 4-25) Delete an array (see page 4-26)
Viewing Array and Drive Status Information

Array and drive status information is available in two ways:
! !
View array status (see page 4-12) View drive status (see page 4-14)
Viewing Array Status

You can view the status of an array, including the following information:
! ! ! !
StateOnline, Offline, Critical, or Fault-tolerant. Serial numberUnique number the RIO subsystem assigns to each array. NameName you give to the array. RAID levelArray type (0, 3, 4, 5, 50, Volume, or Mirrored). The term mirrored is used for both RAID 1 and RAID 10 arrays. Number of drivesNumber of drives in the array when fault-tolerant. For example, if a three-drive RAID 5 array loses one drive, the number will still display 3. Number of drives per subarrayFor RAID 50 only; number of drives in each underlying RAID 5 array. Number of spare drivesNumber of spare drives dedicated to this array. SizeSize of the entire array (expressed in MB or GB for arrays larger than 10 GB). Chunk sizeArrays chunk size. Date createdDate the array was created. UtilityUtility running (None, Verify, Reconstruct, Expand, or Initialize).
! ! ! ! !
4-12
! !
Number of partitionsNumber of partitions created on the array. Free partition totalAmount of free space (no partition) on the array.
To view the status of an array:
1 From the System Menu, select Array Menu and press Enter.
The Select Array screen displays with a list of existing arrays.
2 Select the array you want and press Enter.

The array menu displays.
3 Select Array Status and press Enter.

The status screen displays showing the status of the array you selected.
4 Press Esc to return to the Array Menu.

4-13
Viewing Drive Status

You can view the status of the drives in an array, including the following information:
! ! ! ! ! ! !
Drive numberThe drives sequential position in the RIO subsystems drive list. Drive statusWhether the drive is up or down. SpareSPR identifies the drive as a dedicated spare. Channel numberBack-end disk bus number. Data Gate:ID SizeSize of the drive in MB. UsageIf part of an array, this displays the array name and member number. If a spare, this displays the type of spare. If unused, this displays Available. If the drive was part of an array that no longer exists, this displays Leftover.
Note: If a drive has failed or malfunctioned, it may not be listed.
To view drive status:

3 Select Drive Status and press Enter.

The drive status screen displays showing the drives that are members of the array and that are assigned as dedicated spares.
Use the or key to scroll through the drives. These are the drives that are currently members of the array.
4 Press Esc to return to the Array Menu.
4-14
Stopping the Array Initialization Process

If you find that you need to change the disks or some other array configuration, you can stop the array initialization process.
Caution: If you stop the initialization process, the array goes offline and its data is not available to users.
You must delete the array before you can use the drives in another array. To stop the array initialization process:

3 Select Abort Initialization and press Enter.

The system confirms that you want to stop the initialization process.
Adding a Partition
If you created a multiple-partition array, you must create at least one partition on the array before you can use the array. You can create partitions on a multiple-partition array until you use all of the free space. For more information about partitions, see Understanding Partitions on page 4-27. To add a partition:
2 Select the multiple-partition array you want and press Enter.

4-15
3 Select Add a Partition and press Enter.

The Select Free Partition screen displays with a list of free partitions. A free partition is free space that has not yet been partitioned or space that had a partition that was deleted.
4 Select the free partition you want to use.

The partition size screen displays.
5 Enter the size you want to make the partition and press Enter.
The Partition Name screen displays.
4-16
6 Enter a name for the partition and press Enter.

You can use up to 20 characters. You can include any characters in the name, including spaces. If you do not want to name the partition, you can just press Enter. You can add or change the name later. The LUN screen displays.
7 Select the LUN for the partition and press Enter.

The LUN that displays is the suggested default LUN assignment. Note: Most UNIX, Linux, and Macintosh operating systems require that the CAPI LUN, which is the LUN assigned to each Data Manager, be set to a higher value than all array LUNs. Before creating your first array, change the CAPI LUN to a higher value. If you are using a custom software application to configure and manage the Data Manager (this application uses CAPI to communicate with the Data Manager), you must have a CAPI LUN. If you are not using a custom application, and therefore are not using CAPI, select NONE as the CAPI LUN. This allows your first array to be seen at LUN 0. The system warns you about the LUN for UNIX and Macintosh, as above, the first time you create a partition. Press Enter and the system asks if you want to be warned again. Select No to avoid receiving this warning again, otherwise select Yes to be warned the next time you create a partition. The system confirms that you want to make the change.
4-17
Verifying an Array
The Verify function allows you to verify the data on the specified array (RAID 3, RAID 4, RAID 5, RAID 50, and mirrored arrays only):
!
RAID 3, RAID 4, RAID 5, and RAID 50Verifies all parity blocks in the selected array and corrects any bad parity. MirroredCompares the primary and secondary drives. If a mismatch occurs, the primary is copied to the secondary.
You may want to verify an array when you suspect there is a problem. To verify an array:

3 Select Verify Function and press Enter.

The verify menu displays.
4-18
4 Select Start Verify and press Enter.

Verification begins and the percentage of verification completed displays. You can continue to use the array during verification.
To return to the verification menu, press Esc. To check the progress of the array verification, you can use the verification status described below or select Array Menu from the System Menu. The status of the verification displays in the list of arrays.
Viewing Verification Status

You can view the status of the verification process while it is running. To view verification status:


4 Select View Verify Status and press Enter.

The Verify Status screen displays.
5 Press Esc to return to the verify menu. Stopping the Verification

You can stop the verification process. Normally, you want to let the verification finish, although stopping it does not cause any damage to your data. You may want to stop the verification if you want to improve performance of the RIO subsystem for another application.
4-19
To stop the verification process:


4 Select Abort Verify and press Enter.

The system confirms that you want to stop the verification process.
Reconstructing an Array
The RIO subsystem automatically reconstructs redundant arrays (RAID 3, RAID 4, RAID 5, RAID 50, and mirrored) if an array becomes critical and a properly sized spare drive is available. An array becomes critical when one or more member drives fail. If a reconstruct does not start automatically, it means that no valid spares are available. To start a reconstruct, replace the failed drive, and add the new drive as a dedicated spare (see Adding a Dedicated Spare on page 6-2 and Enabling Dynamic Spares on page 6-3) or as a pool spare (see Adding a Spare to the Spare Pool on page 6-5). Remember that any pool spares added might be used by any critical array, not necessarily the array you want.
4-20
Expanding Array Capacity

You can expand array capacity without stopping I/O activity, so you can continue using the array while the expansion process runs. You can only expand one array at a time. Note: Expanding an array here does not change the size of the host operating system partitions that reside on the array, because the RAID controller is working at the block level not the file system level of the operating system. To use the new space, you must create a new operating system partition using the newly added space or use a third-party application specific to the operating system to change the partition size. How you create a new partition or resize an existing one depends upon the operating system. Most operating systems cannot resize an existing partition. Refer to your operating system documentation. The number of drives you can add to an array depends upon the RAID level as shown in Table 4-2. You also cannot exceed the maximum number of drives for each RAID level. See Creating Arrays on page 4-1.
Table 4-2. Drive additions by RAID level RAID level RAID 0 RAID 1 (Mirrored) Volume Set RAID 10 RAID 3, 4, or 5 RAID 50 Number of drives you can add 1 to 4 at a time up to the maximum Cannot expand Cannot expand 2 or 4 at a time up to the maximum 1 to 4 at a time up to the maximum You can expand the array, one RAID 5 array at a time up to the maximum number of drives. All RAID 5 arrays must contain the same number of drives. Maximum number of drives 16 N/A N/A 16 16 32
If you are expanding a multiple-partition array, you add free space at the end of the array. For more information about partitions, see Understanding Partitions on page 4-27. Note: Once you start expanding array capacity, you cannot stop it. The expand function may take an hour or more to complete, depending on the array type, array size, drive speed, and other processes running on the RIO subsystem.
4-21
To expand an array:

3 Select Expand Function and press Enter.

The expand menu displays.
4 Select Start Expand and press Enter.

The Number of Drives screen displays.
5 Enter the number of drives you want to add and press Enter.
The Select Drives screen displays.
4-22
6 Select the drives you want to add from the list of available drives and press Enter.
Only available drives, that is, drives that are not members of an array and are not assigned as dedicated or pool spares, display. You select a drive by highlighting it and pressing Enter. Each selected drive turns gray in the drive list. After you press Enter for the number of drives you entered previously, the system automatically begins the expansion. To skip a drive, use the or key. To toggle the display between the drive model number, serial number, and the node and WWN, press T. Expansion begins and the percentage completed displays. to return to the array menu, press Esc. To check the progress of the expansion, you can use the expand status described below or select Array Menu from the System Menu. The status of the expansion displays in the list of arrays.
Viewing Expand Status

You can view the status of the expansion process while it is running. To view expand status:

3 Select Expand Function and press Enter.

The expand menu displays.
4 Select View Expand Status and press Enter.

The Expand Status screen displays.
5 Press Esc to return to the expand menu.
Changing an Array Name

You can change the name of an array. This does not affect the target ID or LUN values of the array. The RIO subsystem does not allow you to change an array name when a utility is running. To change an array name:

3 Select Change Array Name and press Enter.

The Enter New Name screen displays.
4-23
4 Enter the name you want to use and press Enter.

You can use up to 20 characters. You can include any characters in the name, including spaces. The system confirms that you want to make the change.
Changing Array Ownership

You can change the ownership of any array between the Data Managers. For more information about how the Data Managers work together, see Understanding How the Data Managers Work Together on page 2-24. You might want to change ownership if you plan to replace or repair one Data Manager. Changing ownership lets you continue using an array without interruption and makes the array visible on the Data Manager you change it to. You can no longer see the array on the original Data Manager. Note: When you change the ownership of an array, the LUNs assigned to the arrays partitions become invalid. After changing ownership, you must assign a new LUN to each array partition. To change array ownership:

3 Select Switch Array Owner and press Enter.

The system confirms that you want to make the change.
4 Select Yes and press Enter. 5 Assign a new LUN to each array partition.
See Changing a Partition LUN on page 4-36.
4-24
Trusting an Array
You can use the Trust Array function to bring an array back online by resynchronizing the time and date stamp and any other metadata on a bad disk. This makes the disk an active member of the array again. You might need to do this when:
!
One or more disks of an array start up more slowly or were powered on after the rest of the disks in the array. This causes the date and time stamps to differ, which the RIO subsystem interprets as a problem with the late disks. In this case, the array will function normally after using Trust Array. An array is offline because a drive is failing, you have no data backup, and you want to try to recover the data from the array. In this case, the Trust Array function may work, but only as long as the failing drive continues to operate.
Before you can use this function, you must enable it in the Option Configuration menu.
Caution: The Trust Array feature can cause unstable operation and data loss if used improperly. This feature is intended for disaster recovery.
To trust an array:
1 From the System Menu, select Configuration Menu and press Enter.
The Configuration Menu displays.
2 Select Option Configuration and press Enter.

The Option Configuration Menu displays.
3 Select Enable Trust Array and press Enter.

The Enable Trust Array screen displays.
4 Select Enable and press Enter.

The option is only enabled until you use it. After you trust an array, the option reverts back to being disabled.
5 Press Esc twice to return to the System Menu. 6 Select Array Menu and press Enter.

4-25
8 Select Trust Array and press Enter.

The system confirms that you want to trust the array.

The array will be back online. Note: If the array does not come back online, it may be that too many members are offline or the array may have additional failures on the bus or enclosure that Trust Array cannot fix.
Deleting an Array
You can delete an array when you no longer need the array or you need the drives for another use.
Caution: Deleting an array deletes all partitions and data contained in the array.
Note: You cannot delete an array while any utility (Initialize, Verify, Expand, or Reconstruct) is running on the array. You must stop the utility, if allowed, or let it finish before you can delete the array. To delete an array:
1 From the System Menu, select Delete an Array and press Enter.
The Select Array screen displays.
2 Select the array you want to delete and press Enter.

The system asks you to confirm the deletion.
4-26
Managing Partitions
The Disk Array Administrator software lets you manage partitions in a variety of ways. You can:
! ! ! ! ! ! ! !
View partition status information (see page 4-28) Add a partition (see page 4-15) Expand a partition (see page 4-34) Change a partition name (see page 4-35) Change a partition LUN (see page 4-36) Change a partitions read-ahead setting (see page 4-36) Control partition access (see page 4-38) Delete a partition (see page 4-44)
Understanding Partitions
The partitions discussed here are logical subdivisions of an array to which you can assign a LUN. You can add, expand, rename, change the LUN, and delete partitions using the RAID controllers software. This type of partition is not the same as a partition you create with your operating system or third party tools. When you create an array, you can choose to make the array all one partition or set up the array for multiple partitions. Using multiple partitions lets you create one very large array making efficient use of your disk drives. For example, you could create one very large RAID 5 array and assign one dedicated spare to the array. This minimizes the amount of disk space allocated to parity and spares compared to the space required if you created five or six smaller RAID 5 arrays. Once you set up an array for multiple partitions, you must create each partition by setting the partition size and assigning the partition a LUN. You can also give each partition a name. We recommend assigning names that indicate how the partition will be used. For example, if the first partition will be used to store your customer database, give it a name like: cust database. When you first create an array set up for multiple partitions, all of the space on the array is designated as free space as shown in Figure 4-1.
Free space Figure 4-1. Array set up for multiple partitions before creating partitions
When you create a partition, you set how large you want the partition to be in MB. Figure 4-2 shows a single partition.
Partition 1 Free space Figure 4-2. Array after creating one partition
4-27
The Disk Array Administrator assigns each partition a unique serial number and sequence number. It assigns sequence numbers in the order the partitions are created, so the first partition on an array is number 1, the second is 2, and so on. Once you create one or more partitions on an array, you can create additional partitions in the remaining free space or you can expand a partition with some limitations. You can only expand a partition into contiguous, following, free space. In Figure 4-2, you can expand partition 1 or you can create additional partitions in the free space. After you partition all of the free space, you can expand the size of a partition only by deleting a partition that follows (has a higher number than) the one you want to expand. In Figure 4-3, you can delete partition 3 and then expand partition 2 to use some or all of partition 3s space.
Partition 1 Partition 2 Partition 3 Partition 4 Partition 5
Figure 4-3. Array after creating five partitions
Caution: If you delete a partition, you also delete all data stored in the partition. Be sure that you back up all data before deleting a partition.
When you expand an array, you add free space at the end of the array as shown in Figure 4-4. For more information about expanding an array, see Expanding Array Capacity on page 4-21.
Partition 1 Partition 2 Partition 3 Partition 4 Partition 5 Free space
Figure 4-4. Array with five partitions after expanding the array
After expanding an array, you can either add a partition or expand the last partition to use the new free space. You can also delete one or more partitions and expand a partition into the space.
Viewing Partition Status Information

You can perform three functions related to partition status information:
! ! !
View partition status (see page 4-28) View partition statistics (see page 4-30) Reset partition statistics (see page 4-32)
Viewing Partition Status

You can view the status of a partition, including the following information:
! !
Array stateOnline, Offline, Critical, or Fault-tolerant. Array typeRAID level (0, 3, 4, 5, 50, Volume, or Mirrored). The term mirrored is used for both RAID 1 and RAID 10 arrays. Array drivesNumber of drives in the array when fault-tolerant. For example, if a three-drive RAID 5 array loses one drive, the number will still display 3.
4-28
! ! ! ! !
NameName you give to the partition. Serial numberUnique number the RIO subsystem assigns to each partition. Target ID:LUNTarget ID and LUN presented to the host system. Partition sizeSize of the partition (expressed in MB). Percentage of total arrayThe percentage of the total array that this partition represents. Write-back cachingStatus of the write-back cache (enabled or disabled) for this array. InfoShield TypeType of InfoShield set up on the partition. See Controlling Partition Access on page 4-38.
To view the status of a partition:
1 Display the partition menu.

From the Array Menu
1 From the System Menu, select Array
From the All Partitions Menu

1 From the System Menu, select All
Menu and press Enter. The Select Array screen displays with a list of existing arrays.
2 Select the array you want and press
Partitions Menu and press Enter. The Select Partition or Free Area screen displays with a list of existing partitions and free space.
2 Select the partition you want and press
Enter. The array menu displays.

3 Select Partition Menu and press Enter.
Enter. The partition menu displays.
The Select Partition screen displays with a list of existing partitions for the current array.
4-29
2 Select Partition Status and press Enter.

The status screen displays showing the status of the partition you selected.
3 Press Esc to return to the partition menu. Viewing Partition Statistics

You can view the current partition statistics. The following statistics are available:
! ! ! ! ! !
ReadTotal number of host read requests directed to the partition WriteTotal number of host write requests directed to the partition SecRdTotal number of sectors read from the partition SecWtTotal number of sectors written to the partition Queue DepthCurrent number of commands from the host that are queued up I/O SizeLast host I/O block size request in 512-byte sectors
Similar statistics are also available on an aggregate basis for all partition LUNs. For more information, see Displaying Overall Statistics on page 5-12.
4-30
To view the partition statistics:

From the Array Menu

2 Select the array you want and press
Enter. The array menu displays.

2 Select Partition Statistics and press Enter.

The statistics menu displays.
4-31
3 Select View Statistics and press Enter.

The statistics screen displays showing the statistics of the partition you selected.
4 Press Esc to return to the statistics menu. Resetting Partition Statistics

You can reset the following partition statistics to zero:
! ! ! ! !
Read Write SecRd SecWt I/O Size Note: Resetting statistics here also resets the statistics for this partition that are included in the aggregate statistics. See Displaying Overall Statistics on page 5-12.
You may want to reset the statistics if you are monitoring performance or doing benchmark testing. You may also want to reset statistics when you change how you are using the partition. Note: You cannot reset the queue depth value. It always reflects the current I/O queue depth.
4-32
To reset partition statistics:

From the Array Menu

2 Select the partition you want and

press Enter. The partition menu displays.
2 Select Partition Statistics and press Enter.

The statistics menu displays.
3 Select Reset Statistics and press Enter.


The system confirms that the statistics have been cleared and returns to the statistics menu.
4-33
Expanding a Partition
You can expand an existing partition, with some limitations. You can only expand a partition into contiguous, following, free space. For more information about partitions, see Understanding Partitions on page 4-27. To expand a partition:

From the Array Menu


2 Select Expand Partition and press Enter.

The Expand Partition screen displays.
3 Enter the size you want to make the partition and press Enter.
You can only expand a partition into contiguous free space that follows the partition. For more information, see Understanding Partitions on page 4-27. The system confirms that you want to make the change.
4-34
Changing a Partition Name

You can change the name of a partition. This does not affect the target ID or LUN values of the partition. The RIO subsystem does not allow you to change a partition name when a utility is running. To change a partition name:

From the Array Menu


2 Select Change Partition Name and press Enter.

The Enter New Name screen displays.
3 Enter the name you want to use and press Enter.

You can use up to 20 characters. You can include any characters in the name, including spaces. The system confirms that you want to make the change.
4-35
Changing a Partition LUN

You can change the LUN assigned to a partition, as it appears under the RIO subsystems target ID from the host systems point of view. The change takes place immediately, however, you may need to restart the host system to see the partition at the new LUN. Note: You cannot change the partitions LUN to one that is already in use. If you want to use a LUN that is already in use, you must first reassign the LUN in use. For more information about LUNs and your RIO subsystem, see Understanding LUNs and Viewing LUN Information on page 7-12. To change a partition LUN:

From the Array Menu
1 From the System Menu, select Array Menu

and press Enter. The Select Array screen displays with a list of existing arrays.

2 Select Change LUN and press Enter.

The New LUN screen displays.
3 Enter the LUN you want to use and press Enter.

Changing the Read-Ahead Size

You can change the read-ahead setting for each partition. This setting controls how much data the Data Manager reads ahead and stores in its cache memory during sequential reads. If you want to change this size, you should be prepared to monitor the system performance using the array statistics and adjust the size until you find the optimal size for your application.
4-36
The default setting is one chunk for the first access in a sequential read and one stripe for all subsequent accesses. The size of the chunk is based on the chunk size used when you created the array (default is 64 KB). The Data Managers treat volumes and mirrored arrays (RAID 1) internally as if they have a stripe size of 64 KB, even though they are not striped. If you specify a read-ahead cache size, that amount of data is read first, and the same amount is read for all read-ahead accesses. Read-ahead is triggered by two back-to-back accesses to consecutive logical block address (LBA) ranges. Read-head can be forward (that is, increasing LBAs) or reverse (that is, decreasing LBAs). Setting the read-ahead size to 0 turns off read-ahead cache. This is useful if the host is triggering read-ahead for what are random accesses. This can happen if the host breaks up the random I/O into two smaller reads, triggering read-ahead. You can use the partition statistics read histogram to determine what size accesses the host is doing. Setting the read-ahead size to a very large size (say four to five stripes worth) can help improve the performance of multiple (three or more) sequential read streams, in some cases improving performance by three times. This would be useful for providing multiple video streams, for example. To change the read-ahead size:

From the Array Menu
1 From the System Menu, select Array Menu

and press Enter. The Select Array screen displays with a list of existing arrays.

4-37
2 Select Change Read-Ahead Size and press Enter.

The Read-Ahead Size screen displays.
3 Select the amount of data you want the Data Manager to read ahead for this partition
and press Enter.
Controlling Partition Access

The RIO subsystems InfoShield capability lets you specify which hosts can access each partition. This gives you complete control of array access based on your specific needs. Figure 4-5 shows an example of how you can use InfoShield.
Engineering Web server
Accounting HR
Array A, partition 1 accessed by Accounting
Array C (single-partition array) accessed by all hosts
Array A, partition 2 accessed by HR
Array B, partition 1 accessed by Engineering
Array B, partition 2 accessed by HR and Accounting
Array B, partition 3 accessed by all hosts, except Web server
Figure 4-5. InfoShield example
4-38
Before you set up InfoShield, you should know the World Wide Name (WWN) for each host that you want to set up. Your SAN administrator should know the WWNs for your network. You can display a list of the last 16 WWNs that the RIO subsystem is aware of on the SAN, and you can give each WWN a name (alias) of your own. This makes working with the InfoShield feature faster and easier. You set up InfoShield by either excluding or including hosts on a list for each partition LUN. The list can include or exclude up to 16 specific hosts or all hosts for each partition LUN. For example, in Figure 4-5, Array A has two partitions. Partition 1 has an include list that contains only Accounting, so only the Accounting server can access partition 1. Array B, partition 3 has an exclude list that contains only the Web server, so all hosts except the Web server can access the partition. Array C uses the default setting, Include All Hosts, which permits all hosts to access the array.
Viewing Known WWNs

You can view a list of 16 host WWNs that the RIO subsystem is aware of on your SAN. The RIO subsystem will be aware of any host that was started since the RIO subsystem was last restarted. Typically, hosts scan for devices during their start process. When this happens, the RIO subsystem saves the WWN information for the host and retains the information even after you restart the RIO subsystem. The list includes the last 16 hosts that started or that you named. You can determine which WWN is for which host by starting one host at a time or scanning for devices from a host, and then viewing the WWN list. The host that scanned for devices most recently is first on the list. You can then give the hosts names you recognize, for example you can use the computer name that has already been assigned to each host, to make InfoShield easier to manage. To view known WWNs:
2 Select General InfoShield and press Enter.

The General InfoShield screen displays.
4-39
3 Select Display Host List and press Enter.

The Display Host List screen displays showing the last 16 WWNs known to the RIO subsystem. The WWNs are listed according to when they scanned for devices. The host that scanned for devices most recently is listed first.
Note: A hosts WWN is placed at the top of the known hosts list whenever the host performs a device discovery or bus scanning type of operation.
4 Press Esc to return to the previous menu. Creating Names (Aliases) for Host WWNs
You can give the hosts on your SAN names (aliases) that you can easily recognize to make InfoShield easier to manage. For example, you can use the computer name that has already been assigned to each host. You can determine which WWN is for which host by starting one host at a time or scanning for devices from a host, and then viewing the WWN list. The host that scanned for devices most recently is first on the list. You can name up to 63 hosts, but you can only view the last 16 hosts that started or that you named. The list of 16 changes as you name hosts or as hosts restart. The names are stored on the RIO subsystem, so if you change RIO subsystems, you have to rename the hosts. To create or change names for WWNs:

4-40
3 Select Add or Name Host and press Enter.

The Add or Name Host screen displays the last 16 known WWNs and host names that you have set up. If you want to change the name (alias), enter the new name in Step 5. For more information, see Viewing Known WWNs on page 4-39. If the RIO subsystem is not aware of any WWNs, the list is empty and the system asks you to enter a host WWN. Select Enter New Host to enter a name a new host.
Note: If you have not manually assigned a WWN an alias, the RIO subsystem will attempt to give the WWN a default name. The default name, if available, is the name of the manufacturer of the hosts host bus adapter (HBA), enclosed in angle brackets. For example, a QLogic HBA will have a default name of <Qlogic>.
4 Select the WWN you want to name and press Enter.

The Enter Host Name screen displays.
5 Enter the name (alias) you want and press Enter.

You can enter up to 16 characters. You can use any combination of characters and spaces.
Configuring InfoShield
Once you set up host names (aliases), you can easily set up your InfoShield. This is where you determine which hosts can access each partition LUN. You set up InfoShield by either excluding or including hosts on a list for each partition LUN. The list can include or exclude up to 16 specific hosts or all hosts for each partition LUN. The InfoShield information is stored as part of the arrays metadata using the WWN for each host. If you install a new RIO subsystem, the array partitions InfoShield will remain. The InfoShield will also remain if you change the partitions LUN.
4-41
Note: Changes to InfoShield take effect immediately, therefore, you should make changes that limit access to partitions when the partitions are not in use. To set up InfoShield:

From the Array Menu

1 From the System Menu, select All Partitions Menu and press Enter.
The Select Partition or Free Area screen displays with a list of existing partitions and free space.

2 Select InfoShield and press Enter.

The InfoShield menu displays and shows the current InfoShield type at the top. The default setting for each partition LUN is Include All Hosts. This results in all hosts being able to access all partitions. You can change the list type using the Change InfoShield Type option. See the next step.
4-42
3 Select the option you want and press Enter.

Display Host ListDisplays a list of the hosts currently on the include or exclude list for the selected partition. This option only displays hosts if you have already used Add Host to List and added one or more WWNs to an include or exclude list. Add Host to ListDisplays the Enter Host WWN screen where you enter the WWN or name (alias) or select the host you want to add to the current list for the selected partition. The list of WWNs and names that displays contains only the last 16 hosts that started or that you named. If you know other WWNs or names, you can enter the WWN or name. Enter the WWN or name or select the host from the list and press Enter. Remove Host from ListDisplays the Remove Host from List screen, which contains a list of the hosts currently on the include or exclude list for the selected partition. Select the WWN of the host you want to remove from the list and press Enter. Change InfoShield TypeDisplays the Change InfoShield Type screen where you can change the InfoShield type to one of four options described below. Changing the InfoShield type does not add or remove any hosts in previously created lists. Include All HostsPermits all hosts on the network to access the selected array. This is the default InfoShield type. This results in all hosts being able to access all partitions. If you have already created an include or exclude list, you can use this option to override the list. Your existing list is retained and you can display, add, or remove hosts from the list. Include Listed HostsLets you enter or select the WWNs of the specific hosts you want to be able to access the selected partition. The list of WWNs and names that displays contains only the last 16 hosts that started or that you named. If you know other WWNs or names, you can enter the WWN or name. Exclude All HostsPermits no hosts on the network to access the selected partition. If you have already created an include or exclude list, you can use this option to override the list. Your existing list is retained and you can display, add, or remove hosts from the list. Exclude Listed HostsLets you enter or select the WWNs or names (aliases) of the specific hosts you do not want to be able to access the selected partition. The list of WWNs and names that displays contains only the last 16 hosts that started or that you named. If you know other WWNs or names, you can enter the WWN or name. Whether you use an include or exclude list depends on your needs. You may want to determine which list would be shorter and create the shorter list. If you have changed the InfoShield, the system confirms that you want to make the change.
4 Select Yes and press Enter to make the changes.

The system confirms that the changes are made.
5 Press Esc to return to the InfoShield screen.

4-43
Changing All Partitions to Include All Hosts

You can change all partitions to include all hosts from the General InfoShield menu. This lets you quickly change the InfoShield setting for all partitions at once to permit all hosts to see all partitions, overriding the existing setting for each partition. However, the RIO subsystem retains all existing include and exclude lists. If you use this option and later need to change back to your previous InfoShield settings, you must do so by changing the setting for each partition individually. See Configuring InfoShield on page 4-41. To change all partitions to include all hosts:

3 Select Include All Hosts and press Enter.

The system confirms that the changes are made.
4 Press Esc to return to the General InfoShield screen.
Deleting a Partition
You can delete a partition when you no longer need it and you want to use the space for another purpose.
Caution: Deleting a partition deletes all data contained in the partition.
Note: You cannot delete a partition while any utility (Initialize, Verify, Expand, or Reconstruct) is running on the array. You must stop the utility, if allowed, or let it finish before you can delete the partition.
4-44
To delete a partition:

From the Array Menu


2 Select Delete This Partition and press Enter.

The system asks you to confirm the deletion.

The Delete Partition option is also available from the Array Menu.
4-45
4-46
5
You should monitor your system regularly to ensure that the RIO subsystem, disks, and arrays are working properly. The RIO subsystem and Disk Array Administrator software let you monitor the status several ways:
!
RIO subsystem LEDs (see Understanding the LED Status Lights on page 2-20 and Chapter 9, Troubleshooting) Event log (see Displaying the Event Log on page 5-2) Module status screens (see Displaying Module Status Information on page 5-5) Hardware and configuration information screens (see Displaying Hardware and Configuration Information on page 5-6) Complete event, hardware, and configuration capture (see Capturing the Event Log, Hardware, and Configuration Information on page 5-10) Drive error statistics (see Displaying Drive Errors and Resetting Error Statistics on page 5-11) Overall Statistics screen (see Displaying Overall Statistics on page 5-12) Array status screen (see Viewing Array and Drive Status Information on page 4-12) Disk status screen (see Viewing Drive Status on page 4-14) Power On Self-Test (POST) (see Problems During Startup on page 9-4) Debug log (see Setting Up Debug Logging on page 9-8)
! ! !
! ! ! ! !
5-1
Displaying the Event Log

The Data Managers event log contains important information about the status of the Data Manager, disks, and arrays. You should check it regularly for each Data Manager to monitor the status of your system. For more information about specific warning and error events, see Warning and Error Events on page 9-5. For information about specific disk and channel errors, see Understanding Disk-related Errors on page 9-9. Below is a list of some of the key warning and failure events included in the event log during operation:
! ! ! ! ! ! ! ! ! ! !
Disk detected error Disk channel error Battery failure Drive down Power up Array critical Array offline Temperature warning Temperature failure (this leads to a shutdown which is also logged) Voltage warning Voltage failure (this leads to a shutdown which is also logged)
The event log stores the most recent 400 events. Events have a time stamp next to them with one-second granularity. Note: If you are having a problem with the RIO subsystem or an array, check the event log before calling technical support. Event messages may let you resolve the problem without calling. You should also check Chapter 9, Troubleshooting. You can view the event information three ways:
! ! !
Most recent event One event at a time, most recent event first Full screen of events at a time
You can also capture the event log to a file. See Capturing the Event Log on page 5-5.
5-2
Viewing the Most Recent Event

When you first access the Disk Array Administrator software, any events that have occurred display. Informational events scroll by automatically. Warning events (yellow text on a black background) and error events (white text on a red background) display until you press Enter or Esc. Once all the events display, the initial screen displays. The initial screen alternates between displaying the date, time, and temperature and the model number of your hardware. You can bypass all events by pressing Tab.
Viewing One Event at a Time

You can view a Data Managers events one at a time. The events display in reverse chronological order, that is, the most recent event is first. If an event displays several parameters, you can see all of them when you view the log one event at a time. When you view a whole screen of events, some parameters may be truncated. To view one event at a time:
1 From the System Menu, select Event Log Menu and press Enter.
The Event Log Menu displays.
5-3
2 Select View Event Log and press Enter.

The event log screen displays the last event that occurred.
3 Press to see the previous event.

You can continue to view earlier events by pressing .
4 Press Esc to return to the Event Log Menu.
Viewing a Whole Screen of Events

You can also view a Data Managers events from the log file a whole screen at a time. This lets you quickly review all recent events. The events display in chronological order, that is, the most recent event is last. When you view a whole screen of events, some parameters may be truncated. If an event displays several parameters, you can see all of them when you view the log one event at a time. To view a whole screen of events:
1 From anywhere in the Disk Array Administrator software, press CTRL-E until the
Event Log screen displays. The first screen of events from the event log displays.
2 Press U to page up or D to page down in the log or use the other keys as listed at the
bottom of the screen to navigate within the event log.
5-4
3 Keep pressing CTRL-E to page through the other information screens and return to
the menu.
Capturing the Event Log

You can also capture a Data Managers entire event log, which saves it to a file on your hard drive. This is useful if you want to print the log or attach it to an e-mail message. The steps below use HyperTerminal as the terminal emulator software. If you use a different terminal emulator, your procedure may be different. To capture the event log file:
1 With HyperTerminal up and running as your RS-232 interface terminal, press

CTRL-E until the event log displays.
2 From the Transfer menu in HyperTerminal, select Capture Text.

The Capture Text window displays.
3 Enter the path and file name you want to use to store the log file contents.
Save the file with a .txt file extension.
4 Click Start. 5 Press P on the keyboard to begin the transfer. 6 From the Transfer menu in HyperTerminal, select Capture Text, then select Stop. 7 To capture the event log for other Data Manager, repeat steps 1 through 6 from the
computer connected to the other Data Manager.
Displaying Module Status Information

You can display status information about each of the modules in your RIO subsystem:
! ! ! !
Data Managers (two) Data Gates (two or four) Power Managers (two) Power Ports (two)
To display module status information:
1 From the System Menu, select Manage Modules and press Enter.
The Manage Modules screen displays.
2 Select the module whose status you want and press Enter.
The manage module menu displays.
5-5
3 Select Module Status and press Enter.

The module status information screen displays.
4 Press Esc to return to the manage module menu.
Displaying Hardware and Configuration Information

You can display the RIO subsystems hardware and configuration information. This is where you can see what version of the firmware you have. Chaparral technical support personnel may request this information. You can display the hardware and configuration information two ways:
! !
Hardware information only Hardware and configuration information
Table 5-1 lists the configuration information that is available.

Table 5-1. Configuration information Group
HOST 0 HOST 1 HOST 2 HOST 3 DG1.1&2 DG2.1&2 DG3.1&2 DG4.1&2
Field
Active Channel
What displays
Speed1 Gb/s or 2 Gb/s as set in the Disk Array Administrator software.
Field
What displays
Topology
Loop, Point-to-Point, or Auto Detection as set in the Disk Array Administrator software. FC World Wide Name for node. FC World Wide Name for port.
Node WWN Port WWN
5-6
Table 5-1. Configuration information (Continued) Group Field

Loop ID
What displays
SOFT or a specific number as set in the Disk Array Administrator software. 24-bit FC address or None if the FC link is not active. NONE or specific number as set in the Disk Array Administrator software. Status of disk channel based on whether a disk enclosure is connected and can be: Good, Down (not online) Probation (had errors but now has a time limit before it gets back to good status or failure for some reason), Degraded (had some errors but link has not failed), Failed (excessive errors causing link to fail), Unknown (status cannot be determined). Lists disk drive loop IDs in the order discovered on the loop. Always Active-Active. 2 or 4 as set in Disk Array Administrator software. Current status of the Data Manager (Not Failed Over or Failed Over). Version of the active-active software. Percentage set in Disk Array Administrator software (1% is the default and recommended value). ON or OFF as set in Disk Array Administrator software. ON or OFF as set in Disk Array Administrator software.
Field
Current Loop ID AL_PA
What displays
Currently assigned value or Inactive if the FC link is not active. Currently assigned value or None if the FC link is not active.
FC Addr
CAPI LUN
DISK 0 DISK 1 DISK 2 DISK 3
Online or Offline Health
Speed
1 or 2 Gbit/sec as set in Disk Array Administrator software.
DG1.3&4 DG2.3&4 DG3.3&4 DG4.3&4 DATAMGR
Loop map
Operating Mode DG Config A-A Status
A-A Version Backoff
Utility Pri
HIGH, MED, or LOW utility priority as set in Disk Array Administrator software. ENABLED or DISABLED as set in Disk Array Administrator software. ON or OFF as set in Disk Array Administrator software.
Alarm Mute
Battery
Cache Lock
Dyn. Spare
5-7
Table 5-1. Configuration information (Continued) Group

DISK
Field
WBCache
What displays
ENABLED, DISABLED, or NO MODIFY as set in Disk Array Administrator software. Internal hubs Enabled or Disabled as set in Disk Array Administrator software. Version of the Configuration Application Programming Interface. Version of the FC software. Number of seconds as set in the Disk Array Administrator software. ON or OFF as set in Disk Array Administrator software.
Field
SMART
What displays
ENABLED, DISABLED, or NO MODIFY as set in Disk Array Administrator software.
ENCLOS
Features
CAPI
Version
FC LIB EMP
Version Poll Rate
Temperature
ON or OFF as set in Disk Array Administrator software. ON or OFF as set in Disk Array Administrator software.
Slot flags
Global Flags
To display hardware information only:
1 From the System Menu, select Utilities Menu and press Enter.
The Utilities Menu displays.
5-8
2 Select Hardware Information and press Enter.

The Hardware Information screen displays.
3 Press Esc to return to the Utilities Menu.

To display hardware and configuration information:
1 From anywhere in the Disk Array Administrator software, press CTRL-E until the
HW Info screen displays. The HW Info screen displays. Press U to page up or D to page down in the screen or use the other keys as listed at the bottom of the screen to navigate within the HW Info screen.
5-9
2 Press CTRL-E again.

The CFG Info screen displays. Press U to page up or D to page down in the screen or use the other keys as listed at the bottom of the screen to navigate within the CFG screen.
3 Press CTRL-E to display the next screen of configuration information or Esc to

return to where you started from.
Capturing the Event Log, Hardware, and Configuration Information

You can capture and save the following information to a file on your hard drive:
! ! ! !
Entire event log All hardware information All configuration information All debug information that is turned on (see Setting Up Debug Logging on page 9-8)
This is useful if you want to print all of this information or attach it to an e-mail message. The steps below use HyperTerminal as the terminal emulator software. If you use a different terminal emulator, your procedure may be different. To capture the event log, hardware, and configuration information:
1 With HyperTerminal up and running as your RS-232 interface terminal, from the
System Menu, select Utilities Menu and press Enter. The Utilities Menu displays.
2 From the Transfer menu in HyperTerminal, select Capture Text.

The Capture Text window displays.
5-10
3 Enter the path and file name you want to use to store the log file contents.
Save the file with a .txt file extension.
4 Click Start. 5 Select Dump Debug Info and press Enter. 6 From the Transfer menu in HyperTerminal, select Capture Text, then select Stop. 7 To capture the same information for the other Data Manager, repeat steps 1 through 6
from the computer connected to the other Data Manager.
Displaying Drive Errors and Resetting Error Statistics

You can display drive errors for a specific drive. You know a drive has errors when you see the letter E in the first column of the Display Drives screen. To display drive errors:
1 From the System Menu, select Display Drives and press Enter.
The Display Drives screen displays.
2 If a drive has an E next to it, select the drive and press Enter to display the error
information. Some errors are primarily for information purposes to help you diagnose drive and enclosure problems. For more information about SMART errors, refer to the drive manufacturers specifications. For more information about FC errors, refer to: www.t11.org, click Drafts, find the FC-FS 1.6 T11/02-018v0 dpANS - Fibre Channel Framing and Signaling Interface document, and go to section 21. To reset the error statistics, select Reset drive error statistics and press Enter.
3 Press Esc to return to the list of drives.
5-11
Displaying Overall Statistics

You can display two types of aggregate statistics for all partition LUNs:
!
General statistics (Similar statistics are also available for individual partition LUNs. For more information, see Viewing Partition Statistics on page 4-30.) I/O operations per second (IOPS) Bandwidth (in millions of bytes per second) Number of read operations Number of write operations Total sectors (512 bytes) read Total sectors written Total current command queue depth across all LUNs Host read/write histogram that shows how many host reads and writes fell into a particular size range. The I/O ranges are based on powers of two: 1 Sector 23 Sectors 47 Sectors 815 Sectors 1631 Sectors 3263 Sectors 64127 Sectors 128255 Sectors 256511 Sectors 5121023 Sectors 10242047 Sectors 2048 (and larger) Sectors Tip: This information may be helpful in interpreting performance based on individual system configuration such as HBA, driver configuration, SAN configuration, and host operating system configuration. The statistical information can be useful to profile applications and their usage of a partition, which could be used to determine if additional arrays would increase performance and what type of RAID level is applicable to your needs. You may want to analyze the performance of the same application using different RAID levels to determine which level gives you the best performance. See Appendix A, Array Basics for more details on RAID levels.
5-12
Note: The statistics are provided as general information for your use, however, they are not intended for benchmarking purposes. To access the general array statistics:
2 Select Overall Statistics and press Enter.

The Overall Statistics screen displays.
3 Select View Statistics and press Enter.

The View Statistics screen displays.
4 Press Esc to return to the Overall Statistics screen.

To access the read/write histogram:

3 Select View R/W Histogram and press Enter.

The View R/W Histogram screen displays.
4 Press Esc to return to the Overall Statistics screen.
Resetting Overall Statistics

You can also reset all of the overall statistics back to zero. You may want to reset the statistics if you are monitoring performance or doing benchmark testing. Note: Resetting statistics here also resets the statistics for each individual partition. See Resetting Partition Statistics on page 4-32. To reset overall statistics:

5-13
3 Select Reset All Statistics and press Enter.


The system confirms that the statistics have been cleared and returns to the Overall Statistics screen.
5-14
6
Managing Spares
Chaparral RAID controllers automatically reconstruct redundant (fault-tolerant) arrays (RAID 3, RAID 4, RAID 5, RAID 50, and mirrored) if an array becomes critical and a properly sized spare drive is available. An array becomes critical when one or more member drives fails. You can set up two types of spare drives:
! !
DedicatedAvailable drive that is assigned to a specific array (see page 6-2). PoolAvailable drive that is assigned to the pool, which can provide a spare for any failed drive in any redundant array. Pool spares are available to both Data Managers. If a drive in an array on either Data Manager fails, the Data Manager can use a pool spare to reconstruct the array (see page 6-4).
In addition, if you enable the Dynamic Spares option and a drive fails, you can replace the drive and the Data Manager will rescan the bus, find the new disk drive, and automatically start reconstruction of the array (see page 6-3). The Data Manager looks for a dedicated spare first. If it does not find a properly sized dedicated spare, it looks for a pool spare. If a reconstruct does not start automatically, it means that no valid spares are available. To start a reconstruct, you must:
1 Replace the failed drive, if no other drive is available. 2 Add the new drive or another available drive as a dedicated spare to the array or as a
pool spare. Remember that any pool spares added might be used by any critical array, not necessarily the array you want.
6-1
Managing Dedicated Spares

Dedicated spares are unused disk drives that you assign as a spare to a specific array. The disk must be as large as the smallest member of the array. You cannot use a dedicated spare drive as a member of an array or as a pool spare. Although using a dedicated spare is the most secure way to provide spares for your arrays, it is also expensive to keep an idle drive assigned to each array. An alternative method is to assign one or more idle drives to the spare pool. See Managing the Spare Pool on page 6-4.
Adding a Dedicated Spare

You assign dedicated spare drives to a specific array. If a member drive in the array fails, the RIO subsystem uses a dedicated spare drive to automatically reconstruct the array. You can add dedicated spare drives to mirrored (RAID 1 and RAID 10) and parity (RAID 3, RAID 4, RAID 5, and RAID 50) arrays when you create the array or afterward. You can assign up to four dedicated spare drives to an array. For more information about assigning spares when you create an array, see Creating Arrays on page 4-1. Note: You cannot add a spare that does not have enough capacity to replace the smallest member in the array. To add a dedicated spare:

3 Select Add Spare and press Enter.

The list of drives screen displays listing the available drives. Note: If a drive was a member of an array and was removed from the array, you cannot use it as a spare until you clear the drives metadata. For more information, see Clearing Metadata from a Drive on page 8-4. To toggle the display between the drive model number, serial number, and the node and WWN, press T.
4 Select the drive you want to add as a spare and press Enter.
The system confirms the change.
6-2
Managing Spares
Deleting a Dedicated Spare

You can delete a dedicated spare drive from an array at any time. To delete a dedicated spare:

3 Select Delete Spare and press Enter. 4 Select the spare drive you want to delete and press Enter.
The system confirms the deletion.
5 Select Yes and press Enter to delete the spare.

The drive is now available for use in an array or as a spare.
Enabling Dynamic Spares

The Dynamic Spares option lets you use all of your disk drives in redundant arrays, without assigning one as a spare. For example, if you enable Dynamic Spares and a drive fails, you can replace the drive and the RIO subsystem will rescan the bus, find the new disk drive, and automatically start reconstruction of the array. The RIO subsystem automatically finds the new drive and reconstructs the array. With Dynamic Spares enabled, if you have spares or available drives, the RIO subsystem first looks for a dedicated or spare pool drive for the reconstruction. If none is found, it uses an available drive, which the RIO subsystem automatically assigns as a spare and starts reconstruction. You must make sure that the new or available drive has enough capacity to replace the smallest member in the array and does not contain metadata (see Clearing Metadata from a Drive on page 8-4). A change to this setting on either Data Manager is automatically updated on the other Data Manager. Note: Performance in systems without an enclosure management processor (EMP) will decrease if an array becomes critical with this option enabled and there are no available drives to start reconstruction. To minimize the performance impact, increase the RIO subsystem rescan rate as described in the steps below.
6-3
To enable dynamic spares:

The Option Configuration screen displays.
3 Select Dynamic Spare Configuration and press Enter.

The Dynamic Spare Config screen displays. The current setting is marked with an * next to it.
4 Select Enabled and press Enter.

The Rescan Rate screen displays.
5 Enter the rescan rate in minutes.

This tells the RIO subsystem how often it should look for an available drive by rescanning the bus. Rescanning the bus frequently can affect performance. If you have an EMP, the dynamic spare configuration will not rescan the bus. The EMP will detect the new drive and tell the RIO subsystem to rescan; the rescan rate you set here will not affect the system. The system confirms the change.
Managing the Spare Pool

The spare pool lets you have one or more disk drives available for the reconstruction of redundant arrays (mirrored [RAID 1 and RAID 10] and parity [RAID 3, RAID 4, RAID 5, and RAID 50]). Once you assign a drive to the spare pool, it is not available for use as an array member or as a dedicated spare. Pool spares are available to both Data Managers. If a drive in an array on either Data Manager fails, the Data Manager can use a pool spare to reconstruct the array. If a pool spare is too small (smaller than an individual member in an array), the Data Manager cannot use it.
6-4
Managing Spares
Adding a Spare to the Spare Pool

You can add up to eight drives to the spare pool to reconstruct any critical array on the RIO subsystem. After an array has started using a pool spare, other critical arrays are prevented from using it. For a pool spare to be used, it must be at least as large as the smallest drive in the array. To add a pool spare:
1 From the System Menu, select Pool Spare Menu and press Enter.
The Pool Spare Menu displays.
2 Select Add Pool Spare and press Enter.

The Select Drives screen displays. To blink the selected drive, press B. The blink function is a toggle. Press B again to stop the blinking. You can also blink more than one drive by selecting each drive and pressing B. To toggle the display between the drive model number, serial number, and the node and WWN, press T.
3 Select each spare drive you want to add and press Enter.
Deleting a Spare from the Spare Pool

You can delete a spare from the spare pool at any time. To delete a spare from the spare pool:
2 Select Delete Pool Spare and press Enter.

The Delete Pool Spare screen displays listing the drives assigned to the spare pool.
3 Select the pool spare you want to delete and press Enter.
6-5
Displaying the Spare Pool

You can display a list of all of the pool spares. To display the spare pool:
2 Select Display Pool Spares and press Enter.

The Display Pool Spare screen displays listing all disk drives assigned to the spare pool.
3 Press Esc to return to the Pool Spare Menu.
6-6
7
The Disk Array Administrator lets you configure settings and perform a variety of functions on the RIO subsystem. You can:
! ! ! ! ! ! ! ! ! ! ! ! ! ! !
Shut down and restart the Data Managers and Data Gates (see page 7-1) Change the date and time (see page 7-7) Configure the host channels (see page 7-8) View LUN information (see page 7-12) Configure the FC disk channels (see page 7-14) Configure the Data Gates (see page 7-16) Change the alarm mute setting (see page 7-16) Change the read-ahead cache setting (see page 7-16) Lock the cache setting (see page 7-18) Enable or disable the battery (see page 7-19) Change the utility priority (see page 7-21) Rescan all channels (see page 7-21) Pause I/O (see page 7-22) Restore the default settings (see page 7-23) Upgrade the firmware (see page 7-24)
Shutting Down and Restarting the Data Managers or Data Gates

You have five options when you need to shut down or restart a Data Manager and two options for a Data Gate:
!
Shut down and restart the current Data ManagerGracefully shuts down and restarts the Data Manager you are currently accessing using the Disk Array Administrator software (as shown at the bottom of each screen). Use this option when you have changed a configuration that requires restarting (the procedures say when you need to do this) or when you need to replace the Data Manager. (See page 7-2.)
7-1
Shut down the other Data ManagerGracefully shuts down the other Data Manager (the one you are not currently accessing using the Disk Array Administrator software). Use this option when you need to replace the other Data Manager or to perform maintenance. (See page 7-3.) Shut down both Data ManagersGracefully shuts down both Data Managers. Use this option when you need to power down the whole system for maintenance, repair, or a move. (See page 7-4.) Put a Data Manager or Data Gate offlineGracefully shuts down the selected module. For a Data Manager, this is the same as shutting down. For a Data Gate, use this option when you need to replace the Data Gate. (See page 7-4.) Put a Data Manager or Data Gate onlineRestarts the selected module. Use this option after you replace a Data Manager or Data Gate to put the new module online. (See page 7-4.) Force a Data Manager or Data Gate offlineShuts down the selected module when using Put Offline does not work. Using this option may cause users to lose access to data. (See page 7-6.)
Shutting Down and Restarting the Current Data Manager

You may need to shut down and restart a Data Manager after making certain configuration changes. The procedures say when you need to do this. You should shut down a Data Manager before you remove it. This shut down is the same as unlocking the handles on the Data Manager hardware to remove it. For more information, see Removing a Module on page 2-26. Using the shutdown from the Disk Array Administrator lets you see any messages related to the shut down. You cannot see the messages when you unlock the hardware handles. You should shut down both Data Managers when you need to power down the whole system for maintenance, repair, or a move. For more information, see Shutting Down Both Data Managers on page 7-4. We strongly recommend that you shut down a Data Manager gracefully and do not just turn off the power. A normal shutdown ensures that the write-back cache has been flushed to the disk.
7-2
To shut down and restart the current Data Manager:
1 From the System Menu, select Shutdown Menu and press Enter.
The Shutdown Menu displays.
2 Select Shutdown/Restart and press Enter

The system confirms that you want to shut down.

The system confirms that it has shut down. To restart the Data Manager, press Enter to restart. The system performs its self-test. When you see the Disk Array Administrator initial screen, the Data Manager is ready.
Shutting Down the Other Data Manager

You should shut down the other Data Manager when you need to remove the other Data Manager. This shut down is the same as unlocking the handles on the Data Manager hardware to remove it. For more information, see Removing a Module on page 2-26. Using the shutdown from the Disk Array Administrator lets you see any messages related to the shut down. You cannot see the messages when you unlock the hardware handles. You should shut down both Data Managers when you need to power down the whole system for maintenance, repair, or a move. For more information, see Shutting Down Both Data Managers on page 7-4. We strongly recommend that you shut down the Data Manager gracefully and do not turn off the power. A normal shutdown ensures that the write-back cache is flushed to the disk. To shut down the other Data Manager:
2 Select Shutdown Other and press Enter


The system confirms that it has shut down.
7-3
Shutting Down Both Data Managers

You can simultaneously and gracefully shut down both Data Managers. Use this in preparation to power down the whole system for maintenance, repair, or a move.
Caution: Shutting down both Data Managers will cause users to lose access to data and will interrupt the flow of data.
To shut down both Data Managers:
2 Select Shutdown Both and press Enter


Both Data Managers shut down. To restart both Data Managers, press Enter at the same time on both Data Managers.
Putting a Data Manager or Data Gate Offline

You may need to put a Data Manager or Data Gate offline. This option gracefully shuts down the selected module. For a Data Manager, this is the same as shutting down. For a Data Gate, use this option when you need to replace the Data Gate. This function is the same as unlocking the handles on the Data Manager or Data Gate hardware to remove it. For more information, see Removing a Module on page 2-26. Using this function from the Disk Array Administrator lets you see any messages related to the put offline. You cannot see the messages when you unlock the hardware handles.
Caution: If the Data Manager or Data Gate is the only one working of the redundant pair, putting it offline will cause users to lose access to data and will interrupt the flow of data.
After replacing the Data Manager or Data Gate, you can use the Put Online option to start the new module if it does not come online automatically.
7-4
To put a Data Manager or Data Gate offline:
2 Select the module you want to put offline and press Enter.
3 Select Put Offline and press Enter.

The system confirms that you want to put the module offline.

The module goes offline.
7-5
Putting a Data Manager or Data Gate Online

If you used the Put Offline function for a Data Manager or Data Gate and did not remove that module, you can put the module back online. You can also use the Put Online function when a Data Manager or Data Gate is offline for any reason. To put a Data Manager or Data Gate online:
2 Select the module you want to put online and press Enter.
3 Select Put Online and press Enter.

The system confirms that you want to put the module online.

The module goes online.
Forcing a Data Manager or Data Gate Offline

You may need to force a Data Manager or Data Gate offline. This option forces the selected module to shut down. Use the Force Offline option only when the Put Offline command does not work and you must take a module offline.
Caution: If the Data Manager or Data Gate is the only one working of the redundant pair, forcing it offline will cause users to lose access to data and will interrupt the flow of data.
To force a Data Manager or Data Gate offline:
2 Select the module you want to put offline and press Enter.
3 Select Force Offline and press Enter.

The system confirms that you want to force the module offline.

The module goes offline.
7-6
Changing the Date and Time

You can change the date and time on either Data Manager. A change to this setting on either Data Manager is automatically updated on the other Data Manager. To set a Data Managers date:
2 Select Set Date/Time and press Enter.

The Set Date/Time screen displays.
3 Select Set Date and press Enter.

The Set Date screen displays.
4 Enter the date you want and press Enter.

Enter the date in the following format: MM/DD/YYYY. The system confirms that you want to make the change.
5 Select Yes and press Enter to make the change.

The system confirms that the change is made.
6 Press Esc to return to the Configuration Menu.
7-7
To set a Data Managers time:
2 Select Set Date/Time and press Enter.

The Set Date/Time screen displays.
3 Select Set Time and press Enter.

The Set Time screen displays.
4 Enter the time you want and press Enter.

Enter the time using a 24-hour clock in the following format: hh:mm:ss. The system confirms that you want to make the change.

6 Press Esc to return to the Configuration Menu.
Configuring the Host Channels

You can configure several settings for each host channel independently. For information about configuring the internal host port hubs, see Configuring the Internal Host Port Hubs on page 7-10.
7-8
Table 7-1 lists the host channel settings and what they do.
Table 7-1. Host channel settings Host channel setting Topology Description You should be sure that the topology setting is correct for your configuration. You can set the topology to: ! LOOPUse this option for all configurations except when the Data Gate is connected to a switch F-port. You must use this option if the internal hubs are enabled. For more information, see Configuring the Internal Host Port Hubs on page 7-10. ! POINT-TO-POINTUse this option only when you connect the Data Gate to a switch F-port. If you change from Loop to Point to Point mode after already establishing a public loop connection, the switch may ignore subsequent attempts to perform point to point initialization. To resolve this, see Problem: The FC host port and switch or HBA do not establish a link. on page 9-3. ! Auto DetectionAutomatically detects the configuration based on the loop initialization process or port address of switch or fabric. Use this option when you do not know what topology you are using or when you plan to change the configuration as you might during testing of the RIO subsystem. Note: You should not set a host port topology to Auto Detection if the HBA, switch, or hub that the Data Gate is connected to is also set to auto detect. You can set the speed to: 1 GB or 2 GB. When you change the link speed, the other host channel on this Data Gate changes speed to match. FC Loop IDYou may need to change the FC Loop ID if you want the Data Manager to be at a specific address or if your system checks addresses in reverse order (lowest address first). You have two options: ! SOFTUse this setting if you do not care whether the Data Managers Loop ID changes when you power down and power up. This setting lets the FC loop initialization process determine the Loop ID. ! Any number between 0 and 125Select a specific number if you want the Loop ID to stay the same after you power down and power up. The Disk Array Administrator software cannot tell you which Loop IDs are available. To be sure that you have successfully assigned the Loop ID you want, check the Loop ID after you restart the Data Manager. If the Data Manager cannot get the specified Loop ID during the loop initialization process, it will try to get a soft address. Each Data Manager has one LUN that you can change when you configure the host channels. You only need to assign a CAPI LUN if you are using CAPI to configure the RIO subsystem over a host channel via SCSI protocol extensions. If you are not using CAPI, you can set the CAPI LUN to NONE. If you are using CAPI, you can set it to a value of 0-63. You have two options for setting the LUN: ! NONEUse this setting if you are not using CAPI to configure the RIO subsystem. ! Any number between 0 and 63Select a specific number if you want the CAPI LUN to stay the same when you restart (this change takes effect immediately unless the CAPI LUN is currently in use).
Link Speed Target ID
CAPI LUN For more information about LUNs, see Understanding LUNs and Viewing LUN Information on page 7-12.
7-9
To configure the host channels:
2 Select Host Configuration and press Enter.

The Channel screen displays.
3 Select the host channel you want to configure and press Enter.
The Enable/Disable screen displays. An * displays next to the current setting.

The Topology screen displays. An * displays next to the current setting.

The Link Speed screen displays. An * displays next to the current setting.

The Target ID screen displays.
7 Select the option or number you want and press Enter.

The CAPI LUN screen displays.
8 Select the option or number you want to use.

There is just one CAPI LUN for each Data Manager. The system confirms that you want to make the change.
Configuring the Internal Host Port Hubs

You can configure the internal host hub in the Data Gates. This option lets you configure the hub as a single loop, which connects host ports 1 and 2 on each Data Gate. This configuration, the default, presents all LUNs from both Data Managers on both ports 1 and 2 of each Data Gate as shown in Figure 7-1.
7-10
Figure 7-1. Internal hubs enabled
When you disable the single loop of the hub, each Data Gate presents Data Manager As LUNs on only one port and Data Manager Bs LUNs only on the other port as shown in Figure 7-2. You may want to use this option when you connect to redundant switches or point-to-point switches.
Figure 7-2. Internal hubs disabled
To configure the internal hubs:

3 Select Enclosure Features and press Enter.

The Enclosure Features screen displays.

Config Internal HubsThis option to configures the hub to enable or disable the RIO subsystems internal FC hubs. Select Enable or Disable and press Enter.
7-11
Understanding LUNs and Viewing LUN Information

Each Data Manager supports up to 64 FC logical unit numbers (LUNs) , or 128 after a failover, that are numbered zero through 63. There are three different types of LUNs: CAPI, EMP, and partition. You can view information about each LUN. See Viewing LUN Information on page 7-13. The three types of LUNs have the following characteristics:
!
CAPI LUNAllows CAPI to configure the Data Manager. Each Data Manager can have a CAPI LUN. You only need to assign a CAPI LUN if you are using CAPI to configure the Data Manager over a host channel using SCSI protocol extensions. If you are not using CAPI, you can set the CAPI LUN to NONE. If you are using CAPI, you can set it to a value of 0-63. Note: Most UNIX, Linux, and Macintosh operating systems require that the CAPI LUN be set to a higher value than all array LUNs. Before creating your first array, change the CAPI LUN to a higher value. If you are using a custom software application to configure and manage the controller (this application uses CAPI to communicate with the controller), you must have a CAPI LUN. If you are not using a custom application, and therefore are not using CAPI, select NONE as the CAPI LUN. This allows your first array to be seen at LUN 0.
EMP LUNsAllow access to EMPs. You can set an EMP LUN to a value of 0-63 or NONE. NONE means that the EMP cannot be accessed via a LUN. For information about changing the EMP LUN, see Setting the EMP LUN on page 8-11. Partition LUNsAllow access to partitions on the Data Manager can set partition LUNs to any numeric value from 0-63. For information about changing the partition LUN, see Changing a Partition LUN on page 4-36.
7-12
Viewing LUN Information

You can view information for each existing LUN. To view LUN information:
2 Select LUN information and press Enter.

The LUN Information screen displays.
3 Press Esc to return to the Utilities Menu.
7-13
Configuring the FC Disk Channels

You can change two configuration options for each FC disk channel:
!
Link speedThis is the maximum speed the RIO subsystem will attempt to negotiate. You can set the speed to: 1 GB/second or 2 GB/second. Initiator ID assigned to each channelThe RIO subsystem assigns each of its FC disk channels one of the FC loop IDs (initiator IDs). You can change the initiator ID assigned to each channel. You may need to do this if the default ID, 125, conflicts with an EMP ID. You have two options: SOFTUse this setting if you do not care whether the channels initiator ID changes when you power down and power up. This setting lets the FC loop initialization process determine the initiator ID. Any number between 0 and 125Select a specific number if you want the initiator ID to stay the same after you power down and power up. The Disk Array Administrator software cannot tell you which IDs are available. To be sure that you have successfully assigned the ID you want, check the ID after you restart the RIO subsystem. If the RIO subsystem cannot get the specified Loop ID during the loop initialization process, it will try to get a soft address.
To configure the FC disk channels:
2 Select Channel Configuration and press Enter.

The Select Disk Channel screen displays.
7-14
3 Select the channel you want and press Enter.

The Link Speed screen displays. The current setting has an * next to it.
4 Select the setting you want and press Enter.

The Initiator ID screen displays showing the current initiator ID.
5 Select the initiator ID you want and press Enter.

The system confirms that you want to make the changes.
6 Select Yes and press Enter to make the changes. 7 Press Esc to return to the Configuration Menu.
7-15
Configuring the Data Gates

You can configure the number of Data Gates the RIO subsystem uses to be two or four. You need to change this setting if you have been using four Data Gates and are removing two Data Gates. The RIO subsystem will work if you do not change this setting, but you will receive a number of error messages because the RIO subsystem expects to see four Data Gates installed. Be sure that the Data Gates are installed in the correct slots if you are only using two. For more information, see Understanding the RFF244 and RFF288 on page 2-2. To configure the Data Gates:

The Option Configuration Menu displays.
3 Select Number of Data Gates and press Enter.

The Number of Data Gates screen displays. The current setting has an * next to it.
4 Select the setting you want and press Enter.

The system confirms that you want to make the changes.
5 Select Yes and press Enter to make the changes. 6 Press Esc to return to the Option Configuration Menu.
Changing the Alarm Mute Setting

You can enable or disable the audible alarm that sounds when the RIO subsystem becomes too hot, detects low or high voltage, or an array becomes critical or offline. Changing the mute setting lets you turn off the alarm when it is sounding. You should turn it back on after resolving the problem. You can also use the Mute button on the Data Manager to turn off the alarm when it sounds.
7-16
The alarm sounds for temperature or voltage conditions (events). Warning events are generated when the temperature or voltage enters the warning range. Shutdown events are generated when the temperature or voltage enters the shutdown range. After reaching the shutdown range, the RIO subsystem will not function. You must resolve the problem and restart the RIO subsystem. If the problem is not resolved, it will shut down again. Alarm conditions trigger an event message that displays in the Disk Array Administrator software window and in the event log. See Displaying the Event Log on page 5-2. A change to this setting on either Data Manager is automatically updated on the other Data Manager. Table 7-2 shows the temperature and voltage thresholds for each alarm and what to do to resolve the problem.
Table 7-2. Alarm thresholds Alarm threshold Data Manager internal temperature ! Warning0C to 4C and 66C to 70C ! Shutdown<0C and >70C What to do when the alarm sounds
!
Check the Disk Array Administrator software to confirm what the alarm means. See Displaying the Event Log on page 5-2. Check the ambient temperature and lower it, if needed. Ambient temperature should be less than 45C. Check that the RIO subsystem has good airflow clearance. The RIO subsystem requires airflow clearance on all sides, except the bottom and top. Check that the internal fans are running. The fans are in the Power Managers. Same as above.
Data Manager CPU temperature ! Warning0C to 4C and 91C to 100C ! Shutdown<0C and >100C Data Gate internal temperature ! Warning0C to 4C and 66C to 70C ! Shutdown<0C and >70C VCC voltage ! Warning5 V -10% to -8% and +8% to +10% ! Shutdown5 V <-10% and >+10%
Same as above.
Check the Disk Array Administrator software to confirm what the alarm means. See Displaying the Event Log on page 5-2. If it is a warning alarm, let the RIO subsystem continue to operate. If it is a shutdown alarm, see which Data Manager is showing the alarm. If only one Data Manager shows the alarm, replace that Data Manager. If it is both, you must troubleshoot the Power Managers. Same as above for the VCC voltage.
12V voltage ! Warning12 V -20% to -10% and +10% to +20% ! Shutdown12 V <-20% and >+20%
7-17
Table 7-2. Alarm thresholds Alarm threshold 2.5 V voltage ! Warning2.5 V -10% to -8% and +8% to +10% ! ShutdownN/A What to do when the alarm sounds
!
Same as above for the VCC voltage.
To enable or disable the alarm:
2 Select Alarm Mute and press Enter.

The Alarm Mute screen displays. The current setting is marked with an * next to it.
Locking the Cache Setting

You can prevent host systems from using SCSI mode-select commands to change the Data Managers write-back cache setting. Some operating systems disable write cache. If cache lock is enabled, the host cannot modify the cache setting. The default setting is disabled. This option is useful in some environments where the host system disables the Data Managers write-back cache, resulting in degraded performance. A change to this setting on either Data Manager is automatically updated on the other Data Manager
7-18
To lock the cache setting:

3 Select Cache Lock and press Enter.

The Cache Lock screen displays. The current setting is marked with an * next to it.
Enabling and Disabling the Battery

If you are not using a battery in your RIO subsystem, the RIO subsystem will sound an alarm. To eliminate the alarm, you can disable the battery. The default setting is battery enabled. Note: You should only disable the battery if you are running the RIO subsystem with an uninterruptable power supply (UPS), so that you will not lose power to the RIO subsystem.
7-19
If you disable the battery, the RIO subsystem will not give any warnings, nor will it disable the write-back cache. If you change this setting, you must restart the RIO subsystem for the change to take effect. To change the battery setting:

3 Select Battery and press Enter.

The Battery screen displays. The current setting is marked with an * next to it.
4 Select the option you want and press Enter. 5 Restart to have your changes take effect.
See Shutting Down and Restarting the Data Managers or Data Gates on page 7-1.
7-20
Changing the Utility Priority

You can change the priority at which all utilities (Verify, Reconstruct, Expand, Initialize, etc.) run when there are active I/O operations competing for the Data Managers CPU. The choices are:
! ! !
High (default) Medium Low
For example, select High if your highest priority is to get the array back to a fully faulttolerant state. This causes heavy I/O with the host to be slower than normal. Select Low priority if streaming data without interruption, such as for a Web server, is more important than data redundancy. This allows the Reconstruct or other utility to run at a slower rate with minimal effects on host I/O. To change the utility priority:
2 Select Utility Priority and press Enter.

The Utility Priority screen displays. The current setting is marked with an * next to it.
Rescanning All Channels

You can tell the Data Manager to scan all disk channels for new or removed disk drives. You can use this option when you install or remove drives. The rescan temporarily pauses all I/O processes and then resumes normal operation. If you are using an enclosure with an EMP, the Data Manager will perform a rescan automatically. With an EMP, the EMP detects the change in drive status and updates the Data Manager about removed drives almost immediately; however, installed drives will be detected after a three-minute delay. This delay is to allow the new drives to spin up.
7-21
To rescan all channels:
2 Select Rescan and press Enter.
Pausing I/O
Most drive enclosures allow you to remove and replace drives while FC disk channel activity continues. However, you may still want to pause I/O if you are replacing more than one disk drive. The Hot Swap Pause option suspends activity on all device channels used in the RIO subsystem, thereby ensuring data integrity on the connected drives and arrays.
Caution: Pausing I/O halts active I/O to the host.
Note: If you are not sure that your enclosure supports hot swapping, use the Hot Swap Pause option before you remove or replace any drives in an array.
7-22
To pause I/O:
2 Select Hot Swap Pause and press Enter.

The Bus Paused screen displays.
3 When you have replaced the drive, resume back end activity by pressing Esc.
Caution: Do not stay in the Hot Swap Pause mode for too long; otherwise, an operating system time-out may occur (the time varies according to the operating system). For example, in Windows NT, the default limitation during I/O activity is 10 seconds.
Restoring Default Settings

You can restore all of the Data Manager default settings. You may want to do this if the Data Manager is not working properly and you cannot determine why. This lets you then change the settings that are critical to your configuration. To restore the default settings:
2 Select Restore Defaults and press Enter.

The Restore Defaults screen displays. The system confirms that you want to make the change.

4 Press Enter to return to the Configuration Menu.
7-23
Upgrading Firmware
You can upgrade three types of firmware:
! ! !
Data Manager Memory controller LAN subsystem
Information regarding the latest release of firmware and firmware updates is available from the Chaparral Web site (www.chaparralnet.com/ and click Support). You can also contact Chaparral technical support for firmware updates at (303) 845-3200 or send e-mail to support@chaparralnet.com
Upgrading the Data Managers and Memory Controllers Firmware

You use the Flash Utility to download new firmware (.fla file) for your Data Managers, memory controller, and the storage controller loader. The Flash Utility is resident in the embedded firmware of the Data Managers. You can access the Flash Utility using either your RS-232 or Ethernet connection to the Data Manager. If you want to use the Ethernet connection, your Telnet utility must support either the Kermit or Xmodem protocol. For information about accessing the Disk Array Administrator software, see Chapter 3, Accessing the Disk Array Administrator Software. Follow the procedure below for both Data Managers to make sure that both have the updated firmware. To upgrade the Data Managers and memory controllers firmware:
1 Call Chaparral technical support for information about downloading the firmware
updates. See Chaparral Technical Support on page 9-1.
2 From the computer connected to the Data Manager, access the Disk Array
Administrator software. See Chapter 3, Accessing the Disk Array Administrator Software.
4 Select Shutdown/Restart and press Enter.


The system confirms that it has shut down.
6 Press Enter to restart.
7-24
7 While the Data Manager restarts, hold down the spacebar on your keyboard.
The Flash Utility screen displays.
8 Press the number on your keyboard that corresponds to the protocol you want to use
to transfer the firmware upgrade file from your computer to the Data Manager. We recommend using the KERMIT protocol. The system shows that it is ready to use KERMIT.
9 Using your terminal emulator software, send the .fla file using KERMIT.
If you are using HyperTerminal, select Transfer > Send File, navigate to where the firmware update file is located, select it, and click Open. Select the same Protocol from the drop-down list that you selected from the Flash Utility screen. Click Send. The file transfers. The system displays messages showing that it is flashing the code and restarting the Data Manager.
Caution: Do not interrupt the power when transferring the new firmware.
Upgrading LAN Firmware

You can also update the firmware for the LAN subsystem inside the Data Managers and the LAN subsystem loader. The firmware is contained in a .bfl file. Upgrading the LAN firmware works best from a system that is not running Windows 95 or 98. When using Windows 95 or 98, you received a timeout message even though the ftp process is continuing. If you upgrade the LAN firmware from other operating systems, such as Windows NT or Windows 2000, you do not receive this message.
7-25
To upgrade the LAN subsystems firmware:
1 Check the version of LAN firmware you have now by pressing CTRL-E until the
configuration information screen with that information displays.
2 Call Chaparral technical support for information about downloading the firmware
updates. See Chaparral Technical Support on page 9-1.
3 From the computer connected to the Data Manager, access the DOS window. 4 At the DOS prompt change to the directory where you downloaded
the .bfl file.
5 Enter:
ftp [Data Managers IP address]
6 At the User prompt enter:

flash
7 At the Password prompt enter:

flash
8 At the FTP prompt enter:

bin
9 At the FTP prompt enter:

put [.bfl file name] flash If you are using Windows 95 or 98, you will see a timeout message (Connection closed by remote host), but the ftp process is continuing. You can ignore the timeout message. Wait a few minutes and check the firmware version. If you are using another operating systems, you will see the downloading progress displayed on the screen.
10 When you see the restarting message, wait 60 seconds. 11 Check the version of LAN firmware you have now to make sure the firmware update
worked by pressing CTRL-E until the configuration information screen with that information displays.
7-26
8
The Disk Array Administrator software lets you control a variety of functions related to disk drives and enclosure management processor (EMP) enclosures connected to your RIO subsystem.
!
For drives, you can: Display drive information (see page 8-1) Clear metadata from a drive (see page 8-4) Enable/disable write-back cache (see page 8-5) Display disk cache status (see page 8-7) Enable/disable changes to SMART (see page 8-8) Blink a drive LED (see page 8-9) Take down a drive (see page 8-9) Test a drive (see page 8-10) For EMP enclosures, you can: Change the EMP LUN (see page 8-11) Change additional EMP settings (see page 8-13)
Managing Disk Drives

The Disk Array Administrator software lets you control a variety of functions related to disk drives. You should also refer to your disk drive or enclosure documentation for information about related functions.
Displaying Drive Information

You can display three types of information about disk drives:
! ! !
A list of all drives connected to the RIO subsystem The status of all drives in an array Errors on a specific drive and reset error statistics
8-1
Displaying All Drives

You can display a list of all connected drives. The information includes:
! ! ! ! ! ! !
Data Gate ID:Loop ID Size Vendor Model number (toggles with node WWN and serial number by pressing T) Node WWN (toggles with model number and serial number by pressing T) Serial number (toggles with node WWN and model number by pressing T) Drive firmware revision Utility runningExpand, Verify, etc. Array numberThe arrays sequential position in the RIO subsystems array list Member numberThe drives sequential position in the array
If any of the drives are members of an array, the following information may also display:
! ! !
Drives that are not members of any array are listed as Available. Drives that contain leftover metadata from a previous array are listed as Leftover. This situation can arise if drives are removed and reinserted or the drives failed temporarily and are not operating again. To clear leftover metadata, use the Clear Metadata function. See Clearing Metadata from a Drive on page 8-4. You can also perform two functions from the list of drives:
! !
View drive errors Blink the selected drive
To display all drives:
If a drive has an E in the first column, select the drive and press Enter to display the error. To reset the error statistics, select Reset drive error statistics and press Enter.
8-2
To blink the selected drive, press B. The blink function is a toggle. Press B again to stop the blinking. You can also blink more than one drive by selecting each drive and pressing B. To toggle the display between the drive model number, serial number, and the node and WWN, press M.
2 Press Esc to return to the System Menu. Viewing Drive Status

You can view the status of the drives in an array, including the following information:
! ! ! ! !
Drive numberThe drives sequential position in the RIO subsystems drive list Drive statusWhether the drive is up or down SpareDisplays SPR if the drive is a dedicated spare for the current array Channel numberBack-end disk bus number Data Gate:Loop IDID for the Data Gate the drive is connected to and the loop ID for the FC disk port SizeSize of the drive in MB UsageIf a member of an array, this displays the array name and member number. If a spare, this displays the type of spare. If unused, this displays Available. If the drive was part of an array that no longer exists, this displays Leftover.
! !
Note: If a drive has failed or malfunctioned, it may not be listed.
To view drive status:

8-3
3 Select Drive Status and press Enter.

The drive status screen displays showing the drives that are members of the array and that are assigned as spares.
Use the or key to scroll through the drives.
4 Press Esc to return to the Array Menu. Displaying Drive Errors and Resetting Error Statistics
You can display drive errors for a specific drive. You know a drive has errors when you see the letter E in the first column of the Display Drives screen. To display drive errors:
2 If a drive has an E next to it, select the drive and press Enter to display the error
information. Some errors are primarily for information purposes to help you diagnose drive and enclosure problems. For more information about SMART errors, refer to the drive manufacturers specifications. For more information about FC errors, refer to: www.t11.org, click Drafts, find the FC-FS 1.6 T11/02-018v0 dpANS - Fibre Channel Framing and Signaling Interface document, and go to section 21. To reset the error statistics, select Reset drive error statistics and press Enter.
3 Press Esc to return to the list of drives.
Clearing Metadata from a Drive

All of the member drives in an array contain metadata in the first sectors of the drive. The RIO subsystem uses the metadata to identify array members after restarting or replacing RIO subsystems. You can clear the metadata from a drive if you have a drive that was previously a member of an array. Drives in this state display Leftover in the Display Drives screen. After you clear the metadata, you can use the drive in an array or as a spare.
8-4
To clear metadata from a drive:
2 Select Drive Utilities Menu and press Enter.

The Drive Utilities Menu displays.
3 Select Clear Metadata and press Enter.

The Select Drive screen displays showing drives that are not array members.
4 Select the drive you want and press Enter.

You can now use this drive in an array or as a spare.
Enabling and Disabling Write-back Cache

You can control the write-back cache setting for all of your disk drives at once. Changes take effect after the next rescan or restart. A change to this setting on either Data Manager is automatically updated on the other Data Manager. This can be set to ENABLE, DISABLE, or DONT MODIFY (which means the RIO subsystem should not change any drives write-back cache settings). The default setting is DISABLE. Typically, if your drives are part of an array, you do not want to turn on write-back cache on the drives. The RIO subsystem is already using write-back cache to improve performance. Turning on write-back cache on the disk drive may improve performance in some cases, depending on the type of array and how you are using it. Any disk drives with write-back cache enabled should be connected to an uninterruptable power supply (UPS) in case of power failure. If the drives are not on a UPS and power is lost during disk writes, the array will lose any data in the disks write-back cache.
Caution: We recommend that you disable disk write-back cache. Some drives delete their write-back cache if they encounter an internal error, resulting in lost data.
8-5
To change the write-back cache setting:
2 Select Disk Configuration and press Enter.

The Disk Configuration screen displays.
3 Select Write-back Cache and press Enter.

The Write-back Cache screen displays. The current setting is marked with an * next to it.
4 Select the option you want and press Enter. 5 Restart or rescan to have your changes take effect.
See Shutting Down and Restarting the Data Managers or Data Gates on page 7-1 or Rescanning All Channels on page 7-21.
8-6
Displaying Disk Cache Status

You can display the cache status of each disk drive. Any disk drives with write-back cache enabled should be connected to a UPS in case of power failure. If the drives are not on a UPS and power is lost during disk writes, the array will lose any data in the disks writeback cache. To display disk cache status:

3 Select Display Drive Cache and press Enter.

The Select Drives screen displays.
4 Select a drive and press Enter.

The cache status screen displays showing the status of the read and write cache.
5 Press Esc to return to the Drive Utilities Menu.
8-7
Enabling and Disabling SMART Changes

You can enable or disable the ability to change the Self-Monitoring, Analysis and Reporting Technology (SMART) settings for all drives connected to the RIO subsystem. This can be set to ENABLE, DISABLE, or DONT MODIFY (which means the RIO subsystem should not change any drives SMART settings). The default setting is DONT MODIFY. When you enable SMART, the SMART events are recorded in the event log, which lets you monitor your disk drives or analyze why a drive failed. For more information, see Displaying the Event Log on page 5-2. On most drives, SMART is disabled by default by the manufacturer. A change to this setting on either Data Manager is automatically updated on the other Data Manager. To enable or disable SMART changes:
2 Select Disk Configuration and press Enter.

The Disk Configuration screen displays.
3 Select SMART and press Enter.

The SMART screen displays. The current setting is marked with an * next to it.
4 Select the option you want and press Enter. 5 Restart or rescan to have your changes take effect.
See Shutting Down and Restarting the Data Managers or Data Gates on page 7-1 or Rescanning All Channels on page 7-21.
8-8
Blinking a Drive LED

You can blink the LED on a specific drive one of two ways:
! !
From the Drive Utilities Menu (only works for a single drive; see below) From the Display Drives list when you add a pool spare or display all drives (works for multiple drives). Select the drive and press B. Press B again to stop the blinking.
To blink a drive LED from the Drive Utilities Menu:

3 Select Blink Drive LED and press Enter.

The Select Drive screen displays.

The drive continues blinking its LED until you do one of the following: Press Esc before the Disk Array Administrator times out. Repeat the blink LED command, which toggles the blink LED command off.
5 Press Esc to stop blinking the LED.
Taking Down a Drive
Caution: This function is only for testing and could result in data loss. It should not be used in normal operation.
The Down Drive function sets the status of a drive in a fault-tolerant array to down. This forces the RIO subsystem to remove it from the array and marks the array as critical. At this point, you will be unable to take down any additional drives in the array. If you have a properly sized dedicated or pool spare, this will cause a reconstruct on the affected array. For more information, see Reconstructing an Array on page 4-20. To take down a drive:

8-9
3 Select Down Drive and press Enter.

The Select Drive screen displays showing drives that are array members.


To make the drive display again, you must use Rescan. See Rescanning All Channels on page 7-21. After you rescan, you must clear the metadata from the drive before you can use it in an array or as a spare. See Clearing Metadata from a Drive on page 8-4.
Testing a Drive
This function issues a Test Unit Ready (TUR) command to the selected disk. This just tells you that the drive can respond, but it still may not be functioning properly. To test a drive:

3 Select Test Unit Ready and press Enter.

The Select Drive screen displays.

If the TUR was successful, TUR STATUS OK displays. If the TUR was not successful, a failure message displays.
5 Press Esc to return to the Drive Utilities Menu.
Managing Enclosures
An enclosure management processor (EMP) is a device in the enclosure from which the RIO subsystem can inquire about the enclosures environmental conditions such as temperature, power supply and fan status, and the presence or absence of disk drives. The RIO subsystem can also tell the EMP about RAID activities such as drive rebuilds and failed disk drives. If you have only one EMP, the configuration settings are automatically enabled when the RIO subsystem is installed. No changes are required to the default configuration settings to support EMP. If you have more than one EMP, you must set up the EMP LUNs as described in the next section.
8-10
You may want to enable the Global Flags option to allow the RIO subsystem to set the EMPs global bits. In most enclosures, this allows the RIO subsystem to set the enclosures audible alarm when errors occur. To enable this option, see Changing the Additional EMP Settings on page 8-13. You can control the following functions for EMPs:
! !
Set the EMP LUN (see page 8-11) Change additional EMP settings (see page 8-13): Polling interval Temperature sensor status Slot update status Enclosure update status
Setting the EMP LUN

If you have only one EMP, the configuration settings are automatically enabled when the RIO subsystem is installed. If you have more than one EMP, you must set up the EMP LUNs as described in this section. The RIO subsystem allows in-band access to the EMP in the disk enclosure under the RIO subsystems target ID using direct EMP commands. You can set an EMP LUN to any value between 0 and 63, except where it would conflict with a previously assigned LUN (EMP, array, or CAPI [Data Manager]). You can also set it to NONE, which tells the RIO subsystem not to present a LUN for this EMP under the RIO subsystems target ID. You can set LUNs for EMPs that you plan to add by assigning a LUN to the EMP ID you want to use. The RIO subsystem assigns EMP IDs sequentially each time it starts. Note: EMP LUN settings have no effect on the CAPI interface, which always allows communication with all of the EMPs connected to the RIO subsystem You may want to change the EMP LUN if it conflicts with the LUN of another device.
8-11
To change the EMP LUN:
2 Select EMP Configuration and press Enter.

The EMP Configuration screen displays.
3 Select EMP LUNs and press Enter.

The EMP LUNs screen displays.
8-12
4 Select the EMP ID you want and press Enter.

The EMP ID can be any number from 015. The RIO subsystem assigns EMP IDs sequentially when it starts. The EMP LUN screen displays.
5 Select the option or number you want to use.

To Not assign the EMP a LUN Keep the same LUN for the EMP at all times Do this
!
Select NONE and press Enter. Select the [LUN] you want to use and press Enter. This can be any number from 0 to 63 that is not already in use.
Changing the Additional EMP Settings

You can change four additional EMP settings:
!
Polling intervalThis is the interval, in seconds, that the RIO subsystem polls the EMPs for status changes. If the polling rate is set to zero, the RIO subsystem does not communicate with the EMP. Only use this setting if you suspect you are having communication problems with the EMP. The default setting is five seconds. A change to this setting on either Data Manager is automatically updated on the other Data Manager Temperature sensor statusThis controls whether the RIO subsystems onboard temperature sensor provides temperature information to the host along with the enclosures temperature detected by the EMP. The default setting is OFF, which means that only the enclosures temperature is reported. Slot update status (Slot Flags)This controls whether the RIO subsystem sends commands to the EMP to update the status of each enclosure slot. The default setting is ON, which means that the RIO subsystem will update the Device Slot Status flags.
8-13
Enclosure update status (Global Flags)This controls whether the RIO subsystem polls the EMP to get updated status of the overall enclosure. The default setting is OFF, which means that the RIO subsystem does not update the enclosures Global Flags. A change to this setting on either Data Manager is automatically updated on the other Data Manager
To change the EMP settings:
2 Select EMP Configuration and press Enter.

The EMP Configuration screen displays.
3 Select EMP Settings and press Enter.

The Poll Rate screen displays.
4 Enter the poll rate you want, in seconds, and press Enter.
The Temperature screen displays. The current setting is marked with an * next to it.
8-14
5 Select whether you want to include the RIO subsystems temperature and press
Enter. The Slot Flags screen displays. The current setting is marked with an * next to it.
6 Select whether you want the RIO subsystem to send slot status updates to the EMP
and press Enter. The Global Flags screen displays. The current setting is marked with an * next to it.
7 Select whether you want the RIO subsystem to send enclosure status updates to the
EMP and press Enter. The system confirms that you want to make the changes.
8-15
8-16
9
Troubleshooting
Chaparral Technical Support
For assistance configuring and using your Chaparral product, contact your authorized distributor or Chaparral technical support at: support@chaparralnet.com. Solutions to common problems you may encounter are described in the following sections.
AC Power Problems
Problem: Power Port status is listed as Failed or an AC Fail event displays in the Disk Array Administrator software.
Try each of the following until the problem is solved:
1 Check that the Power Port switches are both turned on. 2 Check that the power cables are firmly plugged into both Power Ports and into an
appropriate electrical outlet.
3 Replace the Power Port. 4 Replace the Power Manager.

Problem: A Power Port or Power Manager Fault LED is solid red and the alarm is sounding.
Power Ports do not have any user-replaceable parts. Replace the Power Port.
Terminal Emulator and COM Port Problems

Problem: Screen continuously puts out garbage characters.
The likely cause of this problem is a baud rate mismatch between the terminal emulator and the RIO subsystem. The default baud rate is 115,200. Follow these steps if you set your terminal emulator to this rate and still get garbage characters:
1 If you are able, shut down both Data Managers.

See Shutting Down and Restarting the Data Managers or Data Gates on page 7-1. If you are unable to shut down the RIO subsystem, continue with step 2.
2 Turn off the power on both Power Ports. 3 Press and hold down the spacebar of your terminal emulator.
9-1
4 Turn on the power while continuing to press the spacebar. This will allow the RIO
subsystem to auto-detect the baud rate setting.
5 When the Flash Utility appears, select option 5 to continue to start the Data Manager.
Note: Some terminal emulators do not immediately change to the new baud rate settings, and you have to exit and restart the emulator to use the new settings.
Problem: Nothing is displayed on the terminal emulator screen.
The probable cause of this problem is a bad RS-232 cable connection or swapped transmit/receive lines. If the cable is properly connected on both ends, try a null modem adapter that will reverse the RS-232 transmit and receive signals. The need for a null modem adapter depends on the RS-232 cable you are using.
Problem: Screen is updated, but will not respond to keystrokes.
Be sure you are using a straight-through serial cable or try using a null modem adapter. Disable hardware flow control on the terminal or terminal emulator. The RIO subsystem supports XON/XOFF flow control and works properly in most cases with no flow control.
Problem: Screen looks correct, but clock is not being updated.
Check to be sure that the RIO subsystem is still powered on. If you are using XON/XOFF, press the CTRL key and Q key simultaneously to start data flowing.
Problem: Screen is updated and menus appear correctly, but boxes around menus look incorrect.
Try a different font in your terminal emulator program, such as Terminal.
Host Fibre Channel Problems

Problem: The host system does not see the RIO subsystem.
Verify in the CTRL-E CFG Info screen that there is a Host Channel FC World Wide Name that is valid. Verify that the port ID is active and a valid arbitrated loop port address (AL_PA) is assigned. Verify the array LUN numbers are configured correctly and not overlapping.
Problem: The LNK LED (FC host port) is not lit.
The problem may be incorrect settings for the FC host port. Verify the type of connection you have and change the topology accordingly. For hub use Loop and for fabric or switch use Point to Point topology, if required by the switch. Check the link speed setting and make sure that it correct.
Problem: The LNK LED (FC host port) goes on and off repeatedly when connecting to a fabric switch.
The problem may be that the FC host port topology is set to Loop and the fabric switch requires Point to Point, or the FC host port topology is set to Point to Point and the fabric switch requires Loop. Make sure that your FC host port and the switch topologies match.
9-2
Troubleshooting
Problem: The LNK LED (FC host port) is lit and the host sees the arrays, but the performance is very slow.
It is possible to have a link but have a bad FC cable. Try replacing the cable or SFP.
Problem: The FC host port and switch or HBA do not establish a link.
The problem may be that both the HBA and FC host port are set to Auto. Disconnect the FC cable and try changing the FC host port topology to Loop or Point to Point according to your host and reconnect the cable. When changing from Loop to Point to Point mode after already establishing a public loop connection, the switch may ignore subsequent attempts to perform point-to-point initialization. Take one of the following actions to establish the point to point connection:
! ! !
Physically unplug and plug the FC cable. Configure the switch port to force point-to-point mode. Change the link speed for that port on RIO and then change it back. The switch recognizes the change from loop to point to point due to the disruption caused when going to the other link speed (useful if RIO is being remotely managed). See Configuring the Host Channels on page 7-8. Restart both Data Managers. See Shutting Down and Restarting the Data Managers or Data Gates on page 7-1.
Array Problems
Problem: Array is much smaller than it should be.
The backoff percent may be set higher than 1%, which is causing the array to be much smaller than the full size of its member disks.
Note: We strongly recommend that you leave the backoff percent at 1%.
Setting the backoff percent backs off or reduces the capacity of the array by the given percentage. The backoff percentage helps when you assign spares by compensating for the minor capacity differences that occur between vendors. For example, two 18-GB drives from two different vendors may differ in capacity by 100 MB. With a backoff of 0%, you would not be able to replace an array members slightly larger 18-GB drive with a smaller 18-GB drive. If you intend to only use identical drives from the same vendor, you can use a backoff of 0%. The default setting is 1% backoff. This default allows you to easily work with drives that have the same nominal capacity, but different actual capacities. The backoff percentage affects all arrays created on the RIO subsystem after you set the percentage. If the drives in an array are not equal in size, the array capacity in a RAID 5 array is based on the smallest members capacity. The backoff percentage is then taken off the capacity from that amount.
9-3
A change to this setting on either Data Manager is automatically updated on the other Data Manager To change the backoff percentage:
2 Select Backoff Percent and press Enter.

The Backoff Percent screen displays.
3 Enter the backoff percent you want to use and press Enter.
Enter the percentage as three digits using the following format: 00.0%. The default is 01.0%.
Problems During Startup

The following sections describe problems you might encounter during Power On Self-Test (POST) or during startup and explain how to resolve those problems. POST shows problems related to the processor, logic, and memory.
Problem: RIO subsystem failed the onboard memory test.
When this failure occurs, it means the internal CPU memory failed. Replace the CPU memory SDRAM DIMM. See Upgrading or Replacing the Memory DIMMs on page 2-32. If replacing the CPU memory did not solve the problem, replace the Data Manager to correct the problem.
Problem: System hangs at Loading Bridge during BFLU Loader Menu.
Update the firmware to ensure you are using the latest version. See Upgrading Firmware on page 7-24. If you cannot update the firmware or if the updated firmware does not correct the problem, replace the Data Manager.
Problem: One of the POST diagnostic tests failed.
Contact Chaparral technical support.

Problem: The system hangs at CT_srv starting.
Follow these steps to resolve the problem:
1 Check the disk and host channels to make sure they are properly connected and that
the Data Gate LNK LEDs are on.
2 Check the enclosure to make sure everything is properly connected. 3 If the enclosure and the drive work properly, replace the Data Manager or Data Gate.
9-4
Troubleshooting
RIO Subsystem Problems

Problem: The Data Managers STATUS LED does not turn on.
Check that the Data Manager is properly seated in the slot and the handles are closed and locked. Check the Disk Array Administrator for outstanding events and for RS-232 interface for power-on initialization and diagnostics errors.
Problem: The Data Managers STATUS LED is on, but there is no RS-232 display.
Check that the RS-232 cable is the correct type (straight-through). Check that the terminal emulation utility on the computer system is properly configured. See Accessing the Disk Array Administrator Using the RS-232 Serial Port on page 3-2.
Problem: The RIO subsystem reports an SDRAM memory error.
Check that the cache memory DDR DIMM is fully seated in the connector and the clips are fully engaged into the DIMM notches. Check that the DIMM is from the Chaparralapproved vendor list. Refer to the Chaparral technical support Web site for the latest updated information.
Warning and Error Events

There are a number of conditions that trigger warning or error events, activate the alarm, and may affect the state of the STATUS and FAULT LEDs. The alarm or buzzer sounds mainly when the Disk Array Administrator displays a warning or error event. The alarm will silence when you acknowledge the event by pressing Esc. The events in these categories are listed below.
Warnings
Warning events let you know that something related to the RIO subsystem or an array has a problem. You should correct the problem as soon as possible. Table 9-1 defines each warning event and recommends the action you should take.
Table 9-1. Warning events Event ARRAY CRITICAL Definition One or more drives are down and the array is online, but is no longer fault tolerant. Recommended Action Add a spare to the array or the spare pool. Then replace the bad drives. See Adding a Dedicated Spare on page 6-2 or Adding a Spare to the Spare Pool on page 6-5. Replace the bad drive and restore the data from backup.
ARRAY OFFLINE
More than one drive in a RAID 0 or volume set went down bringing the array to an offline state. This array is no longer accessible by the host. A warning condition in the battery pack or charging interface has been detected.
BATT FAIL INFO
Replace the Data Manager. You cannot replace the Lithium-Ion battery.
9-5
Table 9-1. Warning events (Continued) Event BOOT ONLINE FAIL Definition During startup, the system attempted to put the specified module online. This operation failed. Recommended Action The event gives a reason why the Put Online failed. Examine this reason and take the appropriate action. If the reason is DIAGNOSTIC FAIL, a hardware problem was found with the module. In this case, try replacing the module with a different one. Determine the source of the errors on the specified disk channel and replace the faulty hardware. Add a spare to the array or the spare pool. Then replace the bad drive. See Adding a Dedicated Spare on page 6-2 or Adding a Spare to the Spare Pool on page 6-5. If the event indicates that the module has failed or is not present, install a new module. See Replacing Modules on page 2-25. Examine the specified Fibre Channel connection and make changes so that the drives are connected to two Data Gate partners (that is, Data Gate 1 and Data Gate 2, or Data Gate 3 and Data Gate 4) as shown in Figure 2-8 on page 2-14 through Figure 2-13 on page 2-18.
DISK CHAN DEGRAD
Errors detected on one of the disk channels have caused the RIO subsystem to mark the channel as degraded. An error occurred with the drive and it was downed, removing it from the active array.
DRIVE DOWN
HW STATUS CHANGE
A Data Manager has detected a significant change in the status of one of the power modules. Invalid dual port Fibre Channel drive connection. The RIO subsystem has detected a single physical disk drive port connected to more than one RIO subsystem port. This is invalid, because it would present the appearance of a dual ported drive connection, without the fault-tolerance benefits. Failure of the disk drive port would cause loss of access to the drive. The battery is approaching its fouryear life span. A correctable single-bit cache memory ECC error occurred.
INVALID DP CONN
REPLACE BATTERY SDRAM CORR ECC
Replace the Data Manager. You cannot replace the Lithium-Ion battery yourself. If this error occurs frequently, replace the cache memory. See Upgrading or Replacing the Memory DIMMs on page 2-32 Clear the metadata from the spare drive. See Clearing Metadata from a Drive on page 8-4.
SPARE UNUSABLE
The drive still contains metadata that must be cleared.
9-6
Troubleshooting
Table 9-1. Warning events (Continued) Event SMART EVENT Definition A disk drive informational exceptions page control (IEPC) predictive failure message was received. No actions by the RIO subsystem are taken on the drive for these events. The system attempted to use Put Offline on a module, but the request was rejected, probably because availability to the hosts would have been affected. The system attempted to Put Online a newly inserted module, however the Put Online request failed. Recommended Action Run diagnostics available from your operating system on the affected drive. Replace the drive, if necessary.
SYS OFFLINE FAIL
This Put Offline request may occur when you press one of the module latches to remove the module. In this case, we recommend that you do not take the module offline. The event gives a reason why the Put Online failed. Examine this reason and take the appropriate action. If the reason is DIAGNOSTIC FAIL, a hardware problem was found with the module. In this case, try replacing the module with a different one. Either determine which drives are missing and reinstall them, or select Yes when asked if you want to discard this data. Check that the RIO subsystems fans are running. Check that the ambient temperature is not too warm. Check for any obstructions to the air flow. See Appendix B, Features and Specifications.
SYS ONLINE FAIL
UNWRITABLE CACHE
The SDRAM cache has battery backed-up data, and the arrays assigned to this data are not present. The analog-to-digital convertor monitored a temperature or voltage in the warning range.
VOLT/TEMP WARN
Errors
Error events let you know that something related to the RIO subsystem, module, or disk drives has failed and requires immediate attention. Table 9-2 defines each error event and recommends the action you should take.
Table 9-2. Error events Event ARRAY CRITICAL Definition One drive in the specified array failed and the array is running in degraded mode (not fault tolerant). Recommended Action Replace the failed drive and add it as a spare to the critical array. If you have dynamic spares enabled, you only need to replace the drive. The system will automatically reconstruct the array.
9-7
Table 9-2. Error events (Continued) Event BATTERY FAILED Definition A failure in the battery pack or charging interface has been detected. Recommended Action Check that the battery is firmly connected to the Data Manager. See Connecting the Battery on page 2-5. Replace the Data Manager. You cannot replace the Lithium-Ion battery yourself. Check the cables on the channel.
DISK CHAN FAILED NO ONLINE DG'S
An error has occurred in communicating on the disk channel. During startup, the system was unable to bring any Data Gates online. Because Data Gates are used for communication between Data Managers, both Data Managers cannot execute together in this environment. To bring both Data Managers online, at least one Data Gate must be online. A noncorrectable multiple-bit cache memory ECC error occurred.
Put Online all available Data Gates. Note that the system will not put online Data Gates at start time that the user put or forced offline. It may be a matter of putting those Data Gates back online. If Data Gates are missing or have failed, install new ones. See Replacing Modules on page 2-25. Reseat the cache memory. Check that the memory installed is on the approved list (http://www.chaparralnet.com and click Support). If the problem continues, replace the memory. See Upgrading or Replacing the Memory DIMMs on page 2-32 Check that the RIO subsystems fans are running. Check that the ambient temperature is not too warm. If the Power Ports and Power Managers have no errors, replace the module (Data Manager or Data Gate) where the error occurred. See Appendix B, Features and Specifications.
SDRAM UNCORR ECC
VOLT/TEMP FAIL
The analog-to-digital convertor monitored a temperature or voltage in the failure range.
Setting Up Debug Logging

You can view a debug log by pressing Ctrl-E. Pressing Ctrl-E toggles you through the event log, debug log, hardware information, and configuration information screens. You can set up additional logging when instructed by Chaparrals technical support personnel. To set up debug logging:
9-8
Troubleshooting
2 Select Debug Log Enable and press Enter.

The Debug Log Enable screen displays.
3 Select each logging item that you want to turn on and press Enter. 4 Select Save Changes and press Enter.
Using the Loader Diagnostics Menu

If you have any diagnostic errors, contact Chaparral technical support.
Using the Loader Utility Menu

If you have any diagnostic errors, contact Chaparral technical support.
Understanding Disk-related Errors

The event log includes errors reported by EMPs and disk drives on your system. If you see these errors in the event log, the information below may assist you. For more information about viewing the event log, see Displaying the Event Log on page 5-2.
Disk Errors
If a disk detects an error, it reports the error, which is recorded in the event log. Figure 9-1 shows an example of a disk-detected error.
Data Gate.port:loop ID Command, logical block address (LBA), transfer size Array serial number Sense key, sense code, sense qualifier Sense information
Figure 9-1. Disk-detected error example
Table 9-3 lists some of the most common SCSI sense key descriptions (in hexadecimal). Table 9-4 lists the descriptions for the most common sense codes (ASC) and sense code qualifiers (ASCQ), all in hexadecimal. Refer to the SCSI Primary Commands - 2 (SPC-2) Specification for a complete list of ASC and ASCQ descriptions.
Table 9-3. Common sense key descriptions Sense Key 0h 1h 2h Description No sense Recovered error Not ready
9-9
Table 9-3. Common sense key descriptions (Continued) Sense Key 3h 4h 5h 6h 7h 8h 9h Ah Bh Ch Dh Eh Fh Description Medium error Hardware error Illegal request Unit attention Data protect Blank check Vendor-specific Copy aborted Aborted command Obsolete Volume overflow Miscompare Reserved
Table 9-4. ?Common ASC and ASCQ descriptions ASC 0C 0C 11 11 11 11 11 11 11 47 48 ASCQ 02 03 00 01 02 03 04 0B 0C 00/01 00 Descriptions Write errorauto-reallocation failed Write errorrecommend reassignment Unrecovered read error Read retries exhausted Error too long to correct Multiple read errors Unrecovered read errorauto-reallocation failed Unrecovered read errorrecommend reassignment Unrecovered read errorrecommend rewrite the data FC CRC error Initiator-detected error message received
Disk Channel Errors

Disk channel errors are similar to disk-detected errors, except they are detected by the RIO subsystem, instead of the disk drive. Some disk channel errors are displayed as text strings, others are displayed as hexadecimal codes. Figure 9-2 shows a disk channel error displaying the hexadecimal code. Table 9-5 lists the error code descriptions. Most disk channel errors are informational because the RIO
9-10
Troubleshooting
subsystem issues retries to correct any problem. Errors that cannot be corrected with retries will result in another critical event describing the affected array (if any).
Data Gate.port:loop ID Logical block address (LBA)
Error code
Figure 9-2. Disk channel error example
Table 9-5. Disk channel error codes Error Code Abort LkDn CRC Error Dev Busy Dn/Ov Run IOTimeout Link Down LIP No Respon Port Fail PrtcolError QueueFull Stat: 04 Stat: 05 Stat: 32 Stat: 42 Stat: 44 Stat: 45 Stat: 46 Description I/O request was aborted because of third-party loop initialization procedure (LIP). CRC error on data was received from a target. Target reported busy status. Data overrun or underrun has been detected. RIO subsystem aborted an I/O request to this target because it timed out. Link down while communication in progress. I/O request was aborted because of a channel reset. No response from target. Disk channel hardware failure. This may be the result of bad cabling. RIO subsystem detected an unrecoverable protocol error on the part of the target. Target reported queue full status. Data overrun or underrun occurred while getting sense data. Request for sense data failed. Target has been reserved by another initiator. I/O request was aborted because of RIO subsystems decision to reset the channel. RIO subsystem decided to abort I/O request for reasons other than bus or target reset. I/O request was aborted because of target reset requested by RIO subsystem . Target did not respond properly to abort sequence.
Voltage and Temperature Errors and Warnings

Most voltage and temperature errors and warnings relate to the Power Port or Power Manager modules. Check the following to resolve these errors or warnings:
1 Check that all of the fans are working by making sure all of the RIO subsystems
LEDs are green or using the Hardware Information or Module Status screens in the Disk Array Administrator software.
9-11
See Displaying Hardware and Configuration Information on page 5-6 and Displaying Module Status Information on page 5-5.
2 Make sure that the Data Managers and Data Gates are properly seated in their slots
and that their handles are locked.
3 Make sure that no slots are left open for more than two minutes.
If you need to replace a module, leave the old module in place until you have the replacement or use a blank cover to close the slot. Leaving a slot open negatively affects the airflow and may cause the unit to overheat.
4 Try replacing each Power Port and Power Manager, one at a time. 5 Replace the Data Gates and Data Managers, one at a time.
9-12
A
Array Basics
Chaparrals RAID controllers let you set up and manage disk arrays. A disk array (array) is a group of disks that appears to the system as a single virtual disk. This is accomplished through software resident in the RAID controller. RAID (Redundant Array of Independent Disks) refers to disk arrays in which part of the array storage capacity may be used to store redundant information. The redundant information lets you restore user data if a disk in the array fails. The host system views the RIO subsystem as a single FC disk drive. It is actually an array of physical disks behind a RAID controller. The RIO subsystem is managed by software to appear as a single, very large physical disk. Depending on the array type, the virtual disk has advantages in fault-tolerance, cost, performance, or a combination of these. This section explains the different array types and the disk requirements for each type. Tip: Choosing the right RAID level for your needs will improve performance. The following are examples of storage needs and appropriate RAID level. Chaparral RAID controllers also provide methods of tracking statistical data to aid in the process. See Chapter 5, Monitoring System Status. Table A-6 shows some example applications and RAID levels.
.
Table A-6. Example applications and RAID levels Application Testing multiple operating systems or software development (where redundancy is not an issue) Fast temporary storage or scratch disks for graphics, page layout, and image rendering Workgroup servers Video editing and production Network operating system, databases, high availability applications, workgroup servers Very large databases, Web server, video on demand RAID level Volume RAID 0 RAID 1, 10 RAID 3 or 4 RAID 5 RAID 50
A-1
Array Types
Array types are defined by their RAID level, a number from 0 through 5 (a higher RAID level does not necessarily indicate a higher level of performance or fault tolerance). Chaparrals RAID controllers let you create the types of arrays that have proven to be the most useful for RAID applications: RAID 0, 1, 10 (also known as mirrored), 3, 4, 5, 50, and volume sets. For more detailed information about array types, refer to The RAID Book: A Storage System Technology Handbook by Paul Massiglia, ISBN 1-879936-90-9.
RAID 0 (Striped Disks)

In a RAID 0 array, data is distributed, or striped, across the disks in the array. The array appears to the server as one large disk with a capacity approximately equal to the combined capacity of the physical disks. Because multiple reads and writes can be handled in parallel, the I/O performance of the array is much better than that of a single physical disk. RAID 0 arrays do not store redundant data, so they are not true RAID applications. If one disk fails, the entire array fails and all array data is lost. The fault tolerance of a RAID 0 array, therefore, is less than that of any single disk in the array. The term RAID 0 is widely used for these arrays, however, because they are conceptually similar to true RAID applications.
RAID 1, RAID 10 (Mirrored Disks)

In RAID 1 and RAID 10 arrays (commonly called mirrored arrays) disks are paired, with both disks in a pair containing the same data. When data is written to a mirrored array, it is written twiceonce to each disk in the pair. A RAID 1 array has only one set of paired disks. A RAID 10 array has multiple pairs, across which data is striped. The read performance of RAID 1 arrays can be much better than that of a single disk, while the write performance is slightly lower. In RAID 10 arrays, both read performance and write performance are better than those of a single disk. A mirrored array is also highly reliable, because both disks in a pair must fail for the array to fail. In an array with five pairs of mirrored disks, for example, the array can maintain its integrity even if five disks failas long as each pair is left with one good disk. The main disadvantage of a mirrored array is its cost. Because all disks must have a twin, you must use twice the number of disks that actually contribute to the array capacity. In an eightdisk array, for example, you have only four disks of usable capacity.
RAID 3
RAID 3 arrays contain redundant information in the form of parity data, which is calculated block-by-block for all user data. The user data is distributed across all but one of the disks in the array. The parity data is written exclusively to the parity disk (also known as the check disk). In the event of a disk failure, the data can be reconstructed from corresponding data stripes on the remaining disks in the array.
A-2
Array Basics
RAID 3 provides excellent I/O performance for applications that require high data transfer rates such as image processing, video processing, scientific data collection, batch data processing, or sequential reads and writes. RAID 3 is not well suited for transaction processing or other applications that require simultaneous reads and writes.
RAID 4
RAID 4 is similar to RAID 3 in that the redundant information is achieved in the form of parity data. The user data is distributed across all but one of the disks. The RIO subsystem uses a single, dedicated parity drive for data protection. The main difference is that RAID 3 usually synchronizes writes to its disks, while RAID 4 can send data to its disk independently. RAID 4 is best suited for transaction processing applications that require high read requests, but not write requests such as inquires rather than updates. RAID 4 is not recommended for I/O-intensive applications that require high data transfer rates.
RAID 5
RAID 5 arrays contain redundant information in the form of parity data, which is calculated block-by-block for all user data. The parity information is distributed across the disks in the array and occupies the equivalent capacity of approximately one disk. Data is interspersed with the parity information. If one disk in the array fails, the data on the failed disk can be reconstructed from the parity data and user data on the remaining disks. Two disks must fail before the entire array fails. The read performance of a RAID 5 array is excellentcomparable to that of a RAID 0 array. Write performance is lower than that of a RAID 0 array, because write operations involve calculating and writing new parity data as well as writing the new user data.
RAID 50
RAID 50 arrays are made up of two or more RAID 5 arrays, across which data is striped. RAID 50 arrays contain redundant information in the form of parity data, which is calculated block-by-block for all user data. As in a RAID 5 array, the parity information is distributed across the disks in the array and occupies the equivalent capacity of one disk per RAID 5. Data is interspersed with the parity information. If one disk in the array fails, the data on the failed disk can be reconstructed from the parity data and user data on the remaining disks. Two disks in one RAID 5 subset must fail before the entire array fails. The read performance of a RAID 50 array is excellentbetter than a RAID 5 array along with better data protection. Write performance is lower than that of a RAID 0 array, because write operations involve calculating and writing new parity data as well as writing the new user data.
A-3
Volume Sets
A volume set provides the ability to create a host-accessible LUN that maps to a single disk in the array, similar to JBOD. Volume sets are nonredundant and have a capacity slightly less than the physical disk they are created from. Volume sets are useful if you have a single disk available and you do not want to use it as a spare. Note: For more information on RAID levels, see The RAIDbook: A Source Book for RAID Technology, published by the RAID Advisory Board (St. Peter, Minnesota, February, 1996).
Comparing RAID Levels

Table A-1 illustrates the differences between the different RAID levels.
Table A-1. Comparing RAID levels RAID Level RAID 0 RAID 1 Min No. of Drives 2 2
Description Data striping without redundancy Disk mirroring
Strengths Highest performance Very high: Performance Data protection Minimal penalty on write performance Previously used for RAM error environments correction (known as Hamming Code) and in disk drives before the use of embedded error correction Excellent performance for large, sequential data requests
Weaknesses No data protectionone drive fails, all data is lost High redundancy cost overheadbecause all data is duplicated, twice the storage capacity is required No practical usesame performance can be achieved by RAID 3 at lower cost
RAID 2
N/A
No practical use
RAID 3
Block-level data striping with dedicated parity drive
Not well-suited for transactionoriented network applications; single parity drive does not support multiple, concurrent write requests Write requests suffer from same single parity-drive bottleneck as RAID 3; RAID 5 offers equal data protection and better performance at same cost
RAID 4 (Not widely used)
Block-level data striping with dedicated parity drive
Data striping supports multiple simultaneous read requests
A-4
Array Basics
Table A-1. Comparing RAID levels (Continued) RAID Level RAID 5 Min No. of Drives 3
Description Block-level data striping with distributed parity
Strengths Best cost/performance for transaction-oriented networks; very high performance and data protection; supports multiple simultaneous reads and writes; can also be optimized for large, sequential requests Better random performance and data protection than RAID 5; supports more drives than RAID 5 Highest performance and data protection (can tolerate multiple drive failures) Ability to use a single drive to store additional data
Weaknesses Write performance is slower than RAID 0 or RAID 1
RAID 50
Combination of RAID 0 (data striping) and RAID 5 with distributed parity Combination of RAID 0 (data striping) and RAID 1 (mirroring)
Lower storage capacity than RAID 5
RAID 10 (Also known as mirrored) Volume Sets
High redundancy cost overhead; because all data is duplicated, twice the storage capacity is required; requires minimum of four drives Not protected, lower performance (not striped)
Non-RAID, nonstriped mapping to a single drive (similar to JBOD)
Mixing Disks from Different Manufacturers or with Different Capacities

An array can contain different models of FC disks, even disks with different capacities; for example, an array can include a 36-GB disk and a 72-GB disk. If you mix disks with different capacities, the smallest disk determines the logical capacity of all other disks in the array, regardless of RAID level. For example, if a RAID 0 array contains one 36-GB disk and four 72-GB disks, the capacity of the array is equivalent to approximately five 36-GB disks. To maximize disk capacity, use disks of similar size.
A-5
A-6
B
RIO subsystems are Fibre Channel-to-Fibre Channel RAID subsystems designed for mission-critical applications requiring the highest performance with uncompromised data reliability, such as mid-range and enterprise server storage. The RIO subsystems maintain exceptionally high throughput and are ideally suited for high-bandwidth, data-intensive applications such as electronic commerce, digital video, CAD, seismic research, digital prepress, and 3-D imaging. Table B-1 summarizes the specific technical features of the RFF244 and RFF288.
Table B-1. RFF244 and RFF288 features Onboard CPU Host data rate Host interface channels FC protocol Device interface channels Device data rate Advanced processing features (Data Manager) Mobile Pentium III 850 MHz, 32-KB on-chip L1 cache, 256-KB on-chip L2 cache 200 MB/sec per Fibre Channel connection (400 MB/sec per host channel, full duplex)
Four (RFF244) or eight (RFF-288) 1-Gbit/2-Gbit Fibre Channel ports

FC-AL, point-to-point, and switched fabric support Four (RFF244) or eight (RFF-288) 1-Gbit/2-Gbit Fibre Channel ports (configured as two or four loops) 200 MB/sec per Fibre Channel loop
!
! ! !
Mobile Pentium III 850 MHz, 32-KB on-chip L1 cache, 256-KB on-chip L2 cache Third generation advanced dual port Peripheral Component Interconnect Extended (PCI-X), Double Data Rate (DDR) memory controller, with hardware accelerated RAID exclusive or (XOR) 72-bit, 100-MHz storage controller CPU memory supporting 64 MB default, PC-100/133 compatible synchronous dynamic random access memory (SDRAM) DIMM, error checking and correcting (ECC) protected 72-bit cache memory supporting 128-512 MB, double data rate (DDR) DIMM, ECC protected. DIMMs must be qualified by Chaparral; you can find the current list on the Chaparral Technical Support Web site, http://www.chaparralnet.com/ and click Support. Integrated Lithium-Ion battery backup interface for DDR write-back cache memory, 50 hours minimum backup time with unbuffered 512-MB DIMM 32-bit, 66 MHz management controller CPU memory, integrated SDRAM 4-MB onboard flash for upgradeable storage controller firmware 4-MB onboard flash for upgradeable management controller firmware
B-1
Table B-1. RFF244 and RFF288 features (Continued) Advanced management controller processing features
! ! ! !
5x86 100 MHz Elan integrated processor 16-MB, 64-bit / 66-MHz on-board SDRAM memory 4 MB on-board flash for upgradeable management controller firmware 10/100baseT Ethernet controller, 32-bit / 33-MHz PCI interface to the Elan processor Shielded RJ-45 connector receptacle Quad channel, embedded, multitasking reduced instruction set computer (RISC) protocol engines 1-Gbit/sec or 2-Gbit/sec Fibre Channel arbitrated loop and switched fabric (host) support Full duplex send and receive payload buffers capable of 1 and 2 Gbit/sec speed Class 3 connection with FC protocol (FCP)-SCSI protocols Up to 128 simultaneous FCP connections (initiators and targets) Greater than 64 command queue depth per FC port Copper and optical interface support using modular small form-factor pluggable (SFP) transceivers Internal configurable mini-hub support for host configuration options Passive multiple PCI-X bus backplane True PCI-X hot plug module support on Data Managers and Data Gates for high-availability, redundant operation Dedicated Data Manager intermodule communication links (failover reset, interrupt messaging, and I2C [inter-IC]) Hardware mechanical sensing for Data Manager and Data Gate front panel handle and latch engagement Nonvolatile memory store for Data Manager configuration history and tracking Menu-based text interface over RS-232 using external RJ-11 connection Local area network (LAN) 10/100BaseT Ethernet interface using external RJ45 connection External LED indicators on all redundant modules External alarm mute button on Data Manager module Voltage, temperature, battery, fan, and power supply monitoring and event logging
Advanced Fibre Channel features (Data Gate)
! ! ! ! !
Advanced hardware availability features
! !
Configuration and management
! !
! ! !
B-2
Table B-1 shows the physical and environmental specifications of the RFF244 and RFF288.
Table B-7. Product specifications Item Physical Specification
!
! !
1U (1.75") height, standard 19"-rack form factor Width17.606" +/- 0.020" (447.2 mm +/- 0.5 mm), excluding rear mounting hardware Width17.702" +/- 0.020" (449.6 mm +/- 0.5 mm), including rear mounting hardware Height1.710" +/- 0.020" (43.4 mm +/- 0.5 mm) Depth20.840" (530 mm), excluding module latch handles and rear mounting hardware Rack mount with permanently attached EIC-978-compliant rack ears Front and rear mounting in 19"-rack Less than 40 lbs approximate weight (includes all internal modules, excludes FC SFP transceivers) Dual redundant internal AC-to-DC 150-Watt power supplies with 5 V/12 V DC load sharing Hot pluggable, redundant power/cooling modules (Power Manager) contain power supply and two DC fans for front intake cooling Hot pluggable, redundant AC entry/cooling modules (Power Port) contain two DC fans for rear exhaust cooling Integrated EMI filter AC entry module and power switch in each Power Port module Universal 90 to 241.3 VAC input voltage range, 49.35 to 60.65 Hz input frequency, 3.0 A RMS @ 120 VAC, 1.5 A RMS @ 230 VAC input current Independent redundant AC entry and AC switch per power supply Internal power supply EN61000-3-2, -4-2/6 compliant Overvoltage, overcurrent, overtemperature internally protected Internal shared +5.0 VDC, 30.0A max current output per supply Internal shared +12.0 VDC, 2.0A max current output per supply (fans only) DC fail and AC fail monitor outputs per supply
Power and cooling (Power Manager and Power Port)
Power
! ! ! ! !
Battery backup Air flow
Single-cell Lithium Ion (Li-Ion) battery pack, with integrated thermistor and overcurrent/overvoltage protection circuit.
!
! ! !
15.0 cubic-ft/min. (CFM) redundant fans located in Power Manager and Power Port modules Rotation detection monitor output per fan Nonobstructed front intake and rear exhaust Nonobstructed side intake/exhaust
B-3
Table B-7. Product specifications (Continued) Item Environmental Specification

!
! ! ! ! !
+5oC to +40oC external ambient, normal operating range (at front of RIO subsystem) 0C to +70C internal ambient, operating range -20oC to +100oC nonoperating/storage 10% to 85% humidity normal operating, noncondensing 5% to 90% humidity nonoperating, noncondensing 90 to 241.3 VAC, 49.35 to 60.65 Hz, autoranging power supply
Temperature and Voltage Monitoring

Table B-8 shows the temperature and voltage normal, warning, and failure thresholds.
Table B-8. Temperature and voltage thresholds Signal Data Manager external temperature sensor Data Manager internal temperature Data Manager CPU temperature sensor Data Gate internal temperature sensor VCC Normal range 0C to 40C Warning range None Failure threshold None
5C to 65C 5C to 90C 5C to 65C -8.0% to +8.0% (4.60V to 5.40V)
0C to 4C and 66C to 70C 0C to 4C and 91C to 100C 0C to 4C and 66C to 70C low warning range: ! -10.0% to <-8.0% ! (4.50V to <4.60V) high warning range: ! >8.0% to 10.0% ! (>5.40V to 5.50V) low warning range: ! - 20.0% to < -10.0% ! (9.6V to < 10.8V) high warning range: ! >10.0% to 20.0% ! (>13.2V to 14.4V)
!
<0C and >70C <0C and >100C <0C and >70C <-10.0% and >+10.0% (<4.50V and >5.50V)
12V
-10.0% to +10.0% (10.8V to 13.2V)
<-20% and >+20% (<9.6V and >14.4V)
2.5VB
-8.0% to +8.0% (2.30V to 2.70V)
< -8.0% and >8.0% (< 2.30V and >2.70V)
No failure event
B-4
Battery temperature monitoring notes:

! ! !
Internal thermocouple in battery pack monitored. Warning issued if pack outside temperature range (5C to 40C). Write-back cache remains enabled in the event of a battery thermal warning.
External ambient temperature: monitors and displays air temperature coming into the RIO subsystem.
B-5
B-6
C
LAN Configuration
Before you can access the Disk Array Administrator software using the Ethernet port, you must set up each Data Manager for TCP/IP. The following sections describe the TCP/IP setup. A Data Manager that is part of a TCP/IP network requires three basic IP configuration elements: IP address, subnet mask, and default gateway IP address. The Data Managers IP address must be unique to the network in which the Data Manager resides. If the Data Manager is part of a publicly routed network (that is, attached to the Internet), the address must be globally unique. This appendix describes how to configure the TCP/IP settings for the first time starting from the factory-set defaults.
Configuring the Data Manager for TCP/IP

Before you can access the Disk Array Administrator software using the Ethernet port, you must set the IP address and subnet mask for the Data Manager. The default IP address is 10.0.0.1. You can do this one of three ways:
!
Setting up your computer with an IP address that is compatible with the Data Manager default of 10.0.0.1, such as 10.0.0.42. Using address resolution protocol (ARP) to set the address. See Using Address Resolution Protocol (ARP) on page C-2. Using the serial connection to the Data Manager and setting the address. See Configuring the IP Settings on page C-3.
C-1
Using Address Resolution Protocol (ARP)

The ARP configuration method requires no IP address reconfiguration of any computer on the LAN. The ARP command is available in various forms and sometimes with varying syntax in UNIX and Windows systems. All Data Managers ship with a unique Media Access Control (MAC) hardware address (sometimes referred to as a physical address). Chaparral Network Storage MAC addresses have the format 00-50-13-fx-xx-xx, where x-xx-xx is unique to each Data Manager. The Data Manager MAC address can be found on a label on the top side, toward the back of the Data Manager. Note: TCP/IP protocol requires that all devices in a subnet have the same octets, typically for the first three octets. For example, to use the default Chaparral IP address of 10.0.0.1, other computers on the subnet must be 10.0.0.X, where X is the value between 2 and 254. ARP is useful because you can temporarily assign a compatible IP address to the Data Manager. To use ARP to resolve addresses in Windows:
1 You must first place the MAC address of the Data Manager being set up into your
computers ARP cache using the following command at the DOS prompt: arp -s [IP address] 00:50:13:fx-xx-xx. In this command, 00-50-13-fx-xx-xx is the Data Managers unique MAC address and IP address is the IP address you or your LAN system administrator have chosen to use as the IP address for the Data Manager. This ARP command adds a static MAC-to-IP address binding to your computer. For example, if you wanted to bind the Data Manager with the factory MAC address of 00-50-13-f0-10-00 to the IP address 169.205.7.22, you should type arp s 169.205.7.22 00-50-13-f0-10-00.
Note: UNIX users see MAN pages for ARP in your OS.
2 After entering the MAC address-to-IP address mapping into your computers ARP
cache, you can issue the ping command (for example, ping 169.205.7.22) to send a request to the Data Manager. If the Data Manager addressed by the ping command does not respond, check the LAN connection on the Data Manager.
3 If the ping command addressed to the Data Manager was successful, use Telnet to
access the Data Manager using the IP address you just configured (for example, 169.205.7.22).
4 Access the TCP/IP Configuration screen in the Disk Array Administrator and enter
the permanent IP address for the Data Manager. See Configuring the IP Settings on page C-3.
C-2
LAN Configuration
Configuring the LAN Settings

You can configure several LAN settings for each Data Manager using the Disk Array Administrator software:
! ! ! ! ! ! ! !
IP settings (see page C-3) FTP settings (see page C-4) Telnet settings (see page C-4) SNMP settings (see page C-5) Contact settings (see page C-6) HTTP settings (see page C-6) Security options (see page C-6) Reset LAN subsystem (see page C-8)
Configuring the IP Settings

You can set three IP-related settings:
! ! !
IP AddressInternet Protocol address of the Data Manager. Default is 10.0.0.1. IP MaskSubnet mask. Default is 255.255.255.0. GatewayDefault is 0.0.0.0. See your LAN administrator for more information.
If you are not sure what IP address, subnet mask, and gateway to use, contact your LAN administrator. To set the IP address, subnet mask, or gateway:
2 Select LAN Configuration and press Enter.

The LAN Configuration screen displays.
3 Select IP Settings and press Enter.

The IP Settings screen displays.

The screen displays related to the option you selected.
5 Enter the IP address, subnet mask, or gateway you want and press Enter.

The system makes the change.
C-3
Configuring the FTP Settings

You can set three FTP-related settings:
!
LoginLogin name for FTP access to the Data Manager. You can use FTP to download firmware updates. You can enter up to 15 characters. Default is flash. PasswordPassword for FTP access to the Data Manager. You can enter up to 15 characters. Default is flash.
Changes to any of these settings on either Data Manager are automatically updated on the other Data Manager. To set the FTP settings:

3 Select FTP Settings and press Enter.

The FTP Settings screen displays.

5 Enter or select the option you want and press Enter.


Configuring the Telnet Settings

You can set two Telnet-related settings:
!
PasswordPassword for accessing the Data Manager using the Ethernet port and Telnet. You can enter up to 32 characters. Default is null (press Enter). TimeoutNumber of idle minutes before the Telnet session times out. Default is no timeout, which is shown as 0 minutes in the Disk Array Administrator.
Changes to any of these settings on either Data Manager are automatically updated on the other Data Manager.
C-4
LAN Configuration
To set the Telnet settings:

3 Select Telnet Settings and press Enter.

The Telnet Settings screen displays.



Configuring the SNMP Settings

You can set six Simple Network Management Protocol (SNMP)-related settings:
!
Trap HostHost computers IP address that is set up to receive SNMP traps. Default is 0.0.0.0. Traps EnableOn or off toggle to enable SNMP traps. Default is No (disabled). Read CommunitySNMP read password. Default is Public. Write CommunitySNMP write password. Default is Private. Event FilterInformational, Warning, or Error. Default is Warning. Trap FilterInformational, Warning, or Error. Default is Warning.
! ! ! ! !
Changes to any of these settings on either Data Manager are automatically updated on the other Data Manager. To set the SNMP settings:

3 Select SNMP Settings and press Enter.

The SNMP Settings screen displays.

C-5


Configuring the Contact Settings

You can set four contact settings:
!
System NameName of the RIO subsystem as seen by other systems on the LAN. You can enter up to 80 characters. Default is Uninitialized Name. System ContactName of a contact person responsible for the Data Manager. You can enter up to 80 characters. System LocationLocation of the Data Manager. You can enter up to 32 characters. System InformationRead-only screen with information about the system.
! !
Changes to any of these settings on either Data Manager are automatically updated on the other Data Manager. To set the Contact settings:

3 Select Contact Settings and press Enter.

The Contact Settings screen displays.



Configuring the HTTP Settings

You can set up the passwords for RAIDar, the browser-based interface to be part of the next release. If you want access to a preproduction demo of RAIDar, contact your sales representative or beta coordinator.
C-6
LAN Configuration
Configuring the Security Options

You can enable or disable the following LAN-related functions:
!
TelnetControls access to the Data Managers using Telnet, which permits you to manage the Data Managers using your LAN. Default is enabled. FTPControls access to the Data Managers using file transfer protocol (FTP), which permits you to upgrade the Data Managers LAN subsystem firmware. Default is enabled. HTTPControls access to the Data Managers using hypertext transfer protocol (HTTP), which permits you to manage the Data Managers using RAIDar. If you want access to a preproduction demo of RAIDar, contact your sales representative or beta coordinator. Default is enabled. SNMPControls the availability of SNMP, which permits remote monitoring of the Data Manager using your LAN. Default is enabled. Internet DebugUsed for diagnosing problems during the technical support process. We recommend that this remain disabled unless support personnel tell you to enable it. Default is disabled.
Changes to any of these settings on either Data Manager are automatically updated on the other Data Manager. To change any of the security options:

3 Select Security Options and press Enter.

The Security Options screen displays.

The screen displays related to the option you selected. The current option has an * next to it.
5 Select Enable or Disable and press Enter.

C-7
Resetting the LAN Subsystem

If you are having difficulty communicating with the Data Manager using the Ethernet connection, you can reset the LAN subsystem in the Data Manager. To reset the LAN subsystem:
2 Select Reset LAN Subsystem and press Enter.

The system confirms that you want to reset the LAN subsystem.

The system resets the LAN subsystem.
C-8
D
Theory of Operation
The RIO family of RAID subsystems provides complete redundancy of each module. This section describes how the two Data Managers (DMs) that provide the RAID capabilities work together. If one Data Manager fails, the remaining Data Manager will take over the failed Data Managers functionality. In normal operation, you can access arrays (LUNs) for configuration purposes only from the Data Manager that currently owns them. One Data Manager will have no visibility to the other Data Managers arrays. If a Data Manager fails, the surviving Data Manager will take ownership of all arrays. Pool spares and unassigned disks are always visible to both Data Managers. Because of the way LUNs are owned by a specific Data Manager and the way LUNs are presented when a Data Manager fails, there are certain rules that you should follow when making Fibre Channel connections:
!
Connect dual-ported Fibre Channel hosts with one link to each Data Gate host port in a horizontal pair of Data Gates. There are two horizontal pairs of Data Gates: Data Gates 1 and 2 and Data Gates 3 and 4 (if you have an RFF288). Each horizontal pair of Data Gates is referred to as Data Gate partners. Connecting to each Data Gate partner ensures that a host can still see all LUNs when a Data Manager fails. The RIO subsystem also protects against accidentally putting both Data Gate partners offline. Connect dual-ported Fibre Channel disk drives with one link to each Data Gate disk port on Data Gate partners. When connecting hosts directly to the Data Gates, enable the internal hubs. When connecting hosts through switches that are connected to the Data Gates, disable the internal hubs. For more information, see Configuring the Internal Host Port Hubs on page 7-10.
How the Data Managers Communicate

The two Data Managers communicate using internal disk FC connections. Although many different message types are sent between the two Data Managers, the majority of the data is write cache data. In the default write-back caching mode, any data that the host writes to a Data Manager is copied to the other Data Manager before good status is returned to the host. By mirroring the data, if a Data Manager fails, the surviving Data Manager will have a copy of all data that has not been written to the disk. Each Data Manager also sends heartbeat messages to its partner Data Manager. If a Data Manager does not receive a heartbeat message within a set timeout period, it will force the other Data Manager offline assuming that it has malfunctioned. After forcing the other
D-1
Data Manager offline, it will take ownership of all arrays and will change half of its host ports to present the failed Data Managers identity. In this failed-over configuration, the Data Manager will present its native identity and LUNs on half of the host ports and the failed Data Managers identity and LUNs on the other host ports. The Data Managers host interface impersonates the others World Wide Name (WWN) identifier and other identifiers as appropriate to the current FC topology. After a Data Manager has failed, you can replace the failed Data Manager with a new Data Manager. The arrays will fail back to the new Data Manager without intervention. If you want to retry the failed Data Manager, you must put the Data Manager online. For more information, see Putting a Data Manager or Data Gate Online on page 7-6. If you replace a failed Data Manager with a new Data Manager, the new Data Manager will attempt to retrieve its configuration (called the mirrored configuration; see Understanding Mirrored Configuration on page D-9) from the surviving Data Manager. This means that the replacement Data Manager will start up with the same configuration as the Data Manager it replaced. If the surviving Data Manager for some reason does not contain a valid mirrored configuration, you must manually configure the replacement Data Manager. The redundant Data Manager system makes some assumptions about the host operating systems SCSI command processing. Specifically, the host must retry incomplete commands after a timeout period. Modern operating systems, including Microsoft Windows NT, do this. This retry is necessary because a host may issue a command to a Data Manager, the Data Manager fails over, and the new Data Manager does not have a copy of the command. Only write command data (in write-back cache mode) is mirrored on the other Data Manager just before sending a good status to the host.
D-2
Theory of Operation
How the Data Managers Present Their LUNs

Each Data Manager presents the LUNs it owns on all Data Gates (DGs), giving the hosts dual-ported Fibre Channel access. However, with an RFF244, when a Data Manager fails, the surviving Data Manager presents its LUNs on one Data Gate and the LUNs of the failed Data Manager on the other Data Gate. With an RFF288, when a Data Manager fails, the surviving Data Manager presents its LUNs on one vertical pair of Data Gates and the LUNs of the failed Data Manager on the other vertical pair of Data Gates. Note that enabling the internal Data Gate Fibre Channel hubs affects how LUNs are presented on ports 1 and 2 of a Data Gate. Table D-1 describes how the Data Managers present LUNs to the host when internal hubs are enabled. Table D-2 describes how the Data Managers present LUNs to the host when internal hubs are disabled. This is also depicted in Figure 7-1 on page 7-11 and Figure 7-2 on page 7-11.
Table D-1. Presentation of LUNs on Data Gate ports when internal hubs are enabled RFF288 Only DM status Both DMs online DM-A failed DM-B failed DG 1 Port 1 All LUNs DM-As LUNs DM-As LUNs DG 1 Port 2 All LUNs DM-As LUNs DM-As LUNs DG 2 Port 1 All LUNs DM-Bs LUNs DM-Bs LUNs DG 2 Port 2 All LUNs DM-Bs LUNs DM-Bs LUNs DG 3 Port 1 All LUNs DM-As LUNs DM-As LUNs DG 3 Port 2 All LUNs DM-As LUNs DM-As LUNs DG 4 Port 1 All LUNs DM-Bs LUNs DM-Bs LUNs DG 4 Port 2 All LUNs DM-Bs LUNs DM-Bs LUNs
Table D-2. Presentation of LUNs on Data Gate ports when internal hubs are disabled RFF288 Only DM status Both DMs online DG 1 Port 1 DM-As LUNs No LUNs DM-As LUNs DG 1 Port 2 DM-Bs LUNs DM-As LUNs No LUNs DG 2 Port 1 DM-Bs LUNs DM-Bs LUNs No LUNs DG 2 Port 2 DMAs LUNs No LUNs DM-Bs LUNs DG 3 Port 1 DM-Bs LUNs DM-As LUNs No LUNs DG 3 Port 2 DM-As LUNs No LUNs DM-As LUNs DG 4 Port 1 DM-As LUNs No LUNs DM-Bs LUNs DG 4 Port 2 DM-Bs LUNs DM-Bs LUNs No LUNs
DM-A failed DM-B failed
D-3
Figure D-1 through Figure D-3 represent the physical layout of the Data Gate ports. Note: The host port hubs are shown in these diagrams, but they may be optionally disabled. The disk port hubs are always enabled.
DG-2 DM-B (Host 0)

Port 1
DG-1 DM-A (Disk 1)

Port 4
DM-A (Host 1)
DM-B (Disk 1)
DM-A (Host 0)
Port 1
DM-B (Host 1)
DM-A (Disk 0)
DM-B (Disk 0)
Port 4
Port 2 Port 3
Port 2 Port 3
DG-4 (RFF288 Only) DM-A (Host 3)

Port 1
DG-3 (RFF288 Only) DM-B (Disk 3)

Port 4
DM-B (Host 2)
DM-A (Disk 3)
DM-B (Host 3)
Port 1
DM-A (Host 2)
DM-B (Disk 2)
DM-A (Disk 2)
Port 4
Port 2 Port 3
Port 2 Port 3
Figure D-1. Port assignment when both Data Managers are online
DG-2 DM-B (Host 0)

Port 1
DG-1 Bypassed
Port 4
Bypassed
DM-B (Disk 1)
Bypassed
Port 1
DM-A (Host 0)
Bypassed
DM-B (Disk 0)
Port 4
Port 2 Port 3
Port 2 Port 3
DG-4 (RFF288 Only) Bypassed

Port 1
DG-3 (RFF288 Only) DM-B (Disk 3)

Port 4
DM-B (Host 2)
Bypassed
DM-A (Host 2)
Port 1
Bypassed
DM-B (Disk 2)
Bypassed
Port 4
Port 2 Port 3
Port 2 Port 3
Figure D-2. Port assignment when Data Manager A is offline
DG-2 Bypassed
Port 1
DG-1 DM-A (Disk 1)

Port 4
DM-B (Host 0)
Bypassed
DM-A (Host 0)
Port 1
Bypassed
DM-A (Disk 0)
Bypassed
Port 4
Port 2 Port 3
Port 2 Port 3
DG-4 (RFF288 Only) DM-B (Host 2)

Port 1
DG-3 (RFF288 Only) Bypassed

Port 4
Bypassed
DM-A (Disk 3)
Bypassed
Port 1
DM-A (Host 2)
Bypassed
DM-A (Disk 2)
Port 4
Port 2 Port 3
Port 2 Port 3
Figure D-3. Port assignment when Data Manager B is offline
D-4
Theory of Operation
LUN Presentation: Two Host Loops and Two Disk Loops

Figure D-4 shows a RIO subsystem with two Data Gates (RFF244). The Data Gates are configured so that the FC port chips controlled by each Data Manager are connected together with internal loops. This results in two FC loops on the host side and two FC loops on the disk side. LUNs and resources owned by Data Manager A are shown in blue. Those owned by Data Manager B are shown in red. Note that the FC disks are dual-ported, so disk accesses can take advantage of the bandwidth of two loops. Both Data Managers have dual-ported access to all disks, so loss of one disk port or even an entire disk loop does not cause a failure.
Figure D-4. RIO subsystem with two Data Gates configured with two host loops and two disk loops
D-5
LUN Presentation: After a Data Manager Failure

Figure D-5 shows a RIO subsystem with two Data Gates (RFF244) configured with two host loops and two disk loops after Data Manager A has failed. In this situation, the Data Gate Fibre Channel ports owned by Data Manager A are now unused. Note that Data Manager B now presents Data Manager As LUNs on Data Gate 2s host port, so that the hosts still have access to both As and Bs LUNs. Disk access is essentially unchanged, since Data Manager B already had access to both FC disk loops before Data Manager A failed.
Figure D-5. RIO subsystem after Data Manager A fails
D-6
Theory of Operation
LUN Presentation: After a Data Gate Failure

Figure D-6 shows a RIO subsystem with two Data Gates (RFF244) configured with two host loops and two disk loops after Data Gate 1 has failed. In this situation, dual-ported host access to the RIO subsystem is lost. In addition, the RIO loses dual-ported access to its Fibre Channel disks. This type of Data Gate failure is one that affects the entire Data Gate. An examples is a Data Gate on-board power failure. Partial Data Gate failures that cause a Data Manager to crash are handled as Data Manager failures (see LUN Presentation: After a Data Manager Failure on page D-6).
Figure D-6. RIO subsystem after Data Gate 1 fails
D-7
LUN Presentation: Four Direct-Connect Host Ports and Two Disk Loops
Figure D-7 shows a RIO subsystem with two Data Gates (RFF244) configured so that their host Fibre Channel ports are directly connected to the Data Gates external SFP connectors (that is, the internal Data Gate hubs are disabled). Each Data Gates disk FC ports are still looped together. This results in four directly connected FC loops on the host side and two FC loops on the disk side.
Figure D-7. RIO subsystem with four direct-connect host ports and two disk loops
Four Data Gate RIO Configurations

With four Data Gates (RFF288), two disk-side dual-loops can be supported, allowing the connection of two strings of dual-ported Fibre Channel disks. The LUNs display the same as described in the previous sections for each horizontal Data Gate pair.
D-8
Theory of Operation
Understanding Mirrored Configuration

The mirrored configuration feature causes configuration changes to be mirrored to the other Data Manager. The mirrored configuration is stored in the other Data Managers Flash. If a Data Manager fails and is replaced, then on startup, it attempts to retrieve its configuration from the other Data Managers flash. The intent is that you will not need to reconfigure a new Data Manager when it is used as a replacement. If a replacement Data Manager uses its mirrored configuration, you will see a message during startup (saying its using the mirrored configuration), and then it will restart (restarting is necessary for the mirrored configuration to take effect). Heres how the mirrored configuration works in different scenarios:
!
Both Data Managers are operating normallyEach Data Manager uses its own local configuration. One Data Manager starts and the other Data Manager does not start due to some problemThe Data Manager that starts uses its local configuration. One Data Manager is up when a new, replacement Data Manager startsThe new Data Manager attempts to get its mirrored configuration from the other Data Manager. If it is not available, it will try to use its local configuration. If that is not available, it will use the defaults.
World Wide Name Impersonation

This feature allows a replacement Data Manager to assume the WWN of the Data Manager it replaced. This continues indefinitely until you start both Data Managers, in which case the native (that is, Data Manager serial number derived) WWNs are used. A warning event is posted indicating whenever a non-native WWN is used. When you start both Data Managers after replacing one, both Data Managers use their own native WWN and a different warning event is also posted. The event lets you know that hosts may not recognize the replacement Data Manager because it is no longer using the WWN of the Data Manager it replaced. You can restart the hosts to have them recognized the Data Managers new WWN. The CTRL-E CFG Info screen shows the current and native WWNs for the local and other Data Manager. Also, the serial number string returned by a SCSI Inquiry command returns the node WWN value instead of the actual serial number. This allows a replacement Data Manager to also impersonate the failed Data Managers serial number, so it appears unchanged from the host (display of Data Manager serial numbers is not affected).
D-9
With a single Data Manager started and if the other Data Manager is down and the Data Manager that is up does not know the serial number of the down Data Manager, the surviving Data Manager fabricates a unique WWN for the other Data Manager, based on its own serial number. If the down Data Manager is later repaired, it will assume this fabricated (and therefore non-native) WWN when it starts up. Note: You will see events in the event log when a Data Manager starts using a non-native WWN. You should note that this has happened. If some subsequent catastrophic event (such a power loss) occurs that causes both Data Managers to restart (and the servers or hosts do not restart), then the WWNs will change (that is, the native WWNs will be used). When the WWNs change, the host may be unable to find the Data Managers. You must update the configuration on the hosts with the new WWNs.
D-10
Glossary
addressAn address is a data structure or logical convention used to identify a unique entity, such as a particular process or network device. arbitrated loop physical address (AL_PA)An AL_PA is a 1-byte value used in an arbitrated loop topology. This value is used to identify L_Ports. The value then becomes the last byte of the address identifier for each public L_Port on the loop. busSee Channel. channelA channel is a common physical path composed of wires or other media, across which signals are sent from one part of a computer to another. A channel is a means of transferring data between modules and adapters, or between an adapter and SCSI or Fibre Channel devices. A channel topology network consists of a single cable trunk that connects one workstation to the next in a daisy-chain configuration. All nodes share the same medium, and only one node can broadcast messages at a time. controller AIn a redundant controller environment, one controller is designated as controller A and the other controller is designated as the controller B. Controller identity is determined by enclosure hardware. The controllers identity displays continuously at the bottom of the Disk Array Administrator screens. Data GateOne module in the RIO family of RAID products. Data Gates contain all of the host and disk I/O hardware. Data ManagerOne module in the RIO family of RAID products. Data Managers contain the RAID controller hardware not associated with primary I/O. Data Manager AIn the RIO family of products, one Data Manager is designated as Data Manager A (DM-A) and the other Data Manager is designated as the Data Manager B (DM-B). The Data Managers identity displays continuously at the bottom of the Disk Array Administrator screens. fabricFabric refers to a switched topology, which is one of the three FC topologies. Fabric elements, which are responsible for frame routing, interconnect various N_Ports or NL_Ports. Depending on vendor support, fabric switches may be interconnected to support up to 16 million N_Ports on a single network. failbackIn Active-Active mode, failback is the act of returning ownership of controller resources from a surviving controller to a previously failed (but now active) controller. The resources include disk arrays, cache data, and host ID information. failoverIn Active-Active mode, failover is the act of temporarily transferring ownership of controller resources from a failed controller to a surviving controller. The resources include disk arrays, cache data, and host ID information. FC adapterAn FC adapter is a printed circuit assembly that translates data between the FC host processors internal bus and FC link. FC Arbitrated Loop (FC-AL)FC-AL is one of three FC topologies in which ports use arbitration to establish a point-to-point circuit. Arbitrated loops allow multiple ports to
G-1
be connected serially in a single loop. Up to 126 NL_Ports and 1 FL_Port can be configured in a unidirectional loop. Ports arbitrate for access to the loop based on their AL_PA. Ports with lower AL_PAs have higher priority than ports with higher AL_PAs. FC deviceA device that uses FC communications is referred to as an FC device. FC portAn FC port is the opening at the back of a router that provides a fiber optic connection between the FC adapter and FC host. FC protocol for SCSI (FCP)FCP defines an FC mapping layer (FC-4) that uses FCPH services to transmit SCSI command, data, and status information between a SCSI initiator and SCSI target. FCP enables transmission and receipt of SCSI commands, data, and status across the FC using standard FC frame and sequence formats. FibreFibre is a generic FC term that refers to all transmission media types specified in the FC Physical Layer standard (FC-PH), such as optical fiber, copper twisted pair, and copper coaxial cable. Fibre Channel (FC)FC is a bidirectional, point-to-point serial data channel, structured for high-performance capability. In the physical sense, an FC is an interconnection of multiple communication points, called N_Ports, by a switching network (fabric). FC transports incoming data from devices by reading the buffer information, packaging it, and sending the information across the fabric. Although FC is a generalized transport mechanism that has no protocol of its own or native I/O command set, it can transport any existing upper-level protocol such as SCSI and IP. FC offers highspeed data transfer rates. FC is most commonly used to connect clustered servers to storage systems. ANSI has developed standards for FC. gigabit interface converter (GBIC)A GBIC, also referred to as a Physical Link Module, is a physical component that manages functions of the FC-0 layer. This layer consists of the physical characteristics of the media and interface, including drivers, transceivers, connectors, and cables. A GBIC attaches to an FC adapter and connects a router to an FC host. high voltage differential (HVD)HVD is a differential SCSI scheme with terminators that run on 5 volts. host bus adapter (HBA)An HBA is the critical link between a host server or workstation and a storage subsystem, integrating computing platforms, operating systems, and I/O protocols to ensure proper interoperability and functionality. The bus adapter provides direct storage connectivity from the system to data within the storage subsystem and enables stable, high-speed transmission of information and files. HBAs manage the controller-specific aspects of handling a storage driver interface device implemented as a target driver, which supports mass storage peripheral devices such as disks and tapes. A storage driver interface is used to implement SCSI and other storage device drivers. An HBA connects to the storage subsystem to the host computer and uses either fiber or copper media. initiatorAn initiator is an FC or SCSI device that contains application clients that originate service requests and task management functions for processing by a target FC or SCSI device. initiator modeInitiator mode is the configuration mode of a device in which an FC or SCSI initiator requests operations to be performed by an FC or SCSI target device.
G-2
Glossary
KillIn Active-Active mode, one controller can kill the other controller by resetting it and taking it offline. logical unit number or logical unit (LUN)A LUN is a subdivision of a SCSI target. For SCSI-3, each SCSI target supports up to 128 LUNs. An FC host using LUNs can address multiple peripheral devices that may share a common controller. loop addressLoop address is an FC term that indicates the unique ID of a node in FC loop topology. A loop address is sometimes referred to as a Loop ID. low voltage differential (LVD)LVD is a method of powering SCSI cables that will be formalized in the SCSI-3 specifications. LVD uses less power than the current differential drive (HVD), is less expensive, and allows for higher speeds such as those of Ultra2 SCSI. LVD requires 3.3 volts (versus 5 volts for HVD). management information base (MIB)A MIB is a database of managed objects accessed by network management protocols. An SNMP MIB is a set of parameters that an SNMP management station can query or set in the SNMP agent of a network device (for example, a router). Mapping tableA mapping table is a table indexed by sequential LUN values. The values indicate select bus:target:LUN devices. Mapping tables are used by some routers to perform FC-to-SCSI operations by default. other controller or Data ManagerThe opposite controller or Data Manager from the one currently being used (that is, not the local controller or Data Manager) is referred to as the other. ownershipIn an active-active configuration, a single controller has ownership of the following resources: arrays and dedicated spares. When a controller fails, the other controller assumes temporary ownership of its resources. partitionA partition is a logical subdivision of an array to which you can assign a LUN. You can add, expand, rename, change the LUN, and delete partitions using the RAID controllers software. This type of partition is not the same as a partition you create with your operating system or third party tools. point to pointA point-to-point connection is a communication link between two end systems. Chaparral uses this term to refer to a link between the controller or router (Nport) and the F-port on a switch. The point-to-point topology is one of three FC topologies, in which two ports are directly connected by a link; there are no fabric, loop, or switching elements present. Power ManagerOne module in the RIO family of RAID products. Power Managers contain the power supply and two cooling fans. Power PortOne module in the RIO family of RAID products. Power Ports contain the ac entry, switch, fuse, filtering as well as a cooling fan. RouterA router is a device that enables connectivity between SCSI devices and FC networks. It routes each data command to the appropriate SCSI channel based on the address it is intended for. SCSI adapter A SCSI adapter is a 16-bit fast/wide or 8-bit narrow, single-ended or differential physical connection between a router and SCSI devices. Each SCSI adapter supports up to 16 (fast/wide) or 8 (narrow) SCSI devices, including itself.
G-3
SCSI addressingEach device supported by a SCSI adapter has its own unique SCSI address, which dictates the devices priority when arbitrating for access to the SCSI bus. A SCSI address of 7 has the highest priority. For a fast/wide SCSI adapter that supports up to 16 devices, the next highest priority address is 6, then 5, 4, 3, 2, 1, 0, 15, 14, 13, 12, 11, 10, 9, and 8. A narrow SCSI adapter supports up to eight devices, including itself. The SCSI address 7 has the highest priority, followed by 6, 5, 4, 3, 2, 1, and 0. SCSI busA SCSI bus provides a means of transferring data between SCSI devices. A SCSI bus is either an 8- or 16-bit bus that supports up to 8 or 16 devices, including itself. The bus can consist of any mix of initiators and targets, with the requirement that at least one initiator and one target must be present. SCSI deviceA SCSI device is a single unit on a SCSI bus that originates or services SCSI commands. A SCSI device is identified by a unique SCSI address. SCSI devices can act as initiators or targets. SCSI portA SCSI port is an opening at the back of a router that provides connection between the SCSI adapter and SCSI bus. Simple Network Management Protocol (SNMP) SNMP is the Internet standard protocol, defined in STD 15, RFC 1157, developed to manage nodes on an Internet Protocol (IP) network. small computer system interface (SCSI) SCSI is an industry standard for connecting peripheral devices and their controllers to an initiator. Storage devices are daisy-chained together and connected to a host adapter. The host adapter provides a shared bus that attached peripherals use to pass data to and from the host system. Examples of devices attached to the adapter include disk drives, CD-ROM discs, optical disks, and tape drives. In theory, any SCSI device can be plugged into any SCSI controller. small form-factor pluggable (SFP)Type of connector. speedSpeed is a status type in the FC Status Menu that shows the speed of the FC port interface. storage area network (SAN)SAN refers to the network behind servers that links one or more servers to one or more storage systems. Each storage system could be RAID, tape backup, tape library, CD-ROM library, or JBOD. SANs operate with both SCSI and networking (IP) protocols. Servers and workstations use the FC network for shared access to the same storage device or system. Legacy SCSI systems are interfaced using an FC-toSCSI bridge. targetA target is a device (peripheral) that responds to an operation requested by an initiator (host system). Although peripherals are generally targets, a peripheral may be required to act temporarily as an initiator for some commands (for example, SCSI EXTENDED COPY command). terminator block/terminationA terminator block (or termination) refers to the electrical connection at each end of a SCSI bus. The terminator block is composed of a set of resistors, or possibly other components. The function of a terminator block is to provide a pull-up for open collector drivers on the bus, and also impedance matching to prevent signal reflections at the ends of the cable. SCSI buses require that a terminator be placed on the 68-pin high-density SCSI connector on the last SCSI peripheral. Data errors may occur in a SCSI bus that is not terminated.
G-4
Glossary
topologyA network topology refers to the physical layout of nodes on a network. Topologies range from local network topologies to WAN topologies. FC topologies include point-to-point, FC-AL, and fabric. trapIn the context of SNMP, a trap is an unsolicited message sent by an agent to a management station. The purpose is to notify the management station of some unusual event. unkillIn Active-Active mode, when a surviving controller removes the reset from the other controller, it unkills it. The other controller will reboot and attempt to come online.
G-5
G-6
Index
A
Abort Initialization 4-15 Abort Verify 4-20 access to partitions, controlling 4-38 accessing the Disk Array Administrator software 3-1 ACT light 2-22 ACT lights 2-23, 2-24 Add a Partition 4-16 Add an Array 4-2, 4-7 Add Host to List 4-43 Add or Name Host 4-41 Add or Name Host screen 4-41 Add Pool Spare 6-5 Add Spare 6-2 adding arrays 4-1 dedicated spares 6-2 partitions 4-15 pool spares 6-5 Address Resolution Protocol, using to resolve IP address C-2 alarm temperature thresholds for 7-17, B-4 turning on or off for the RIO subsystem 7-16 voltage thresholds for 7-17, B-4 Alarm Mute 7-18 Alarm Mute screen 7-18 aliases, giving to WWNs 4-40 ARP, using to resolve IP address C-2 Array Status 4-13 array types defined A-2 maximum number of drives 4-1 minimum number of drives 4-1 arrays adding 4-1 adding a partition to 4-15 bringing back online 4-25 changing names of 4-23 changing ownership of 4-24 creating 4-1 creating a multiple-partition 4-7 creating a single-partition 4-2 deleting 4-26 expanding capacity of 4-21 managing 4-12 mixing disks A-5 reconstructing 4-20, 6-1 resetting aggregate statistics 5-13 status of expanding 4-23 status of verifying 4-19 stopping the initialization process 4-15 stopping the verify process 4-19 trusting 4-25 verifying 4-18 viewing aggregate statistics for all 5-12 viewing read/write histogram 5-12 viewing status of 4-12 viewing status of drives in 4-14, 8-3 Auto Detection topology setting 7-9
B
Backoff percentage 9-3 BATT light 2-22 battery connecting 2-5 disabling 7-19 enabling 7-19 Battery screen 7-20 Blink Drive LED 8-9 blinking, LED of disk drive 8-9 Bus Paused screen 7-23
C
cache disabling for disk drives 8-5 enabling for disk drives 8-5 locking setting on RIO subsystem 7-18 Cache Lock screen 7-19
I-1
capacity expanding for arrays 4-21 expanding for partitions 4-28, 4-34 CAPI LUN changing 7-9 CAPI LUN for 7-12 capturing complete event, hardware, and configuration information 5-10 configuration information 5-10 hardware information 5-10 the event log file 5-5, 5-10 Change Array Name 4-23 Change InfoShield Type 4-43 Change LUN 4-36 Change Read-Ahead Size 4-38 changing array names 4-23 array ownership 4-24 EMP polling interval 8-13 EMP slot update status setting 8-13 EMP temperature status setting 8-13 EMP update status setting for the enclosure 8-13 partition LUNs 4-36 partition names 4-35 the CAPI LUN 7-9 the internal host port hub configuration 7-10 utility priority on RIO subsystem 7-21 channels changing FC loop ID 7-14 changing link speed 7-14 configuring host 7-8 problems with host 9-2 rescanning 7-21 selecting the link speed 7-9 selecting the topology 7-9 Chaparral technical support 9-1 Chunk Size screen 4-6, 4-10 Clear Metadata 8-5 communications parameters 3-2 Config Internal Hubs 7-11 configuration information capturing 5-10 displaying 5-6 Configuration Information screen 5-10 configuration software, accessing 3-1
configuring Data Gates 7-16 disk channels 7-14 host channels 7-8 the RIO subsystem 7-1 connecting the battery 2-5 to the Ethernet Port 2-12 to the FC disk channels 2-19 to the FC host ports 2-13, 2-19 to the RS-232 port 2-11 contact settings C-6 conventions 1-2 creating arrays 4-1 multiple-partition arrays 4-7 single-partition arrays 4-2 customer support 9-1
D
data status of verifying 4-19 stopping verify process 4-19 verifying 4-18 Data Gate shutting down 7-1 Data Gates configuring 7-16 forcing offline 7-6 installing 2-29 putting offline 7-4 putting online 7-6 removing 2-26 replacing 2-25 viewing status of 5-5 Data Manager restarting 7-1 Data Manager A, defined 2-24 Data Manager B, defined 2-24 Data Managers changing LUN for 7-9 connecting the battery 2-5 forcing offline 7-6 how they present LUNs D-3 installing 2-29
I-2
Index
LUNs 7-12 putting offline 7-4 putting online 7-6 removing 2-26 replacing 2-25 shutting down 7-2 shutting down both 7-4 shutting down the other 7-2, 7-3 understanding how they work together 2-24 viewing status of 5-5 date, setting 7-7 dedicated spares adding 6-2 defined 6-1 deleting 6-3 default settings, restoring 7-23 Delete an Array 4-26 Delete Spare 6-3 Delete This Partition 4-45 deleting arrays 4-26 dedicated spares 6-3 partitions 4-44 pool spares 6-5 DIMMs upgrading 2-32 disabling SMART changes 8-8 write-back cache changes 8-5 Disk Array Administrator accessing 3-1 changing the screen display 3-7 initial screen 3-3, 3-6 menu tree 3-8 navigating in 3-7 System Menu 3-3, 3-6 disk array See arrays disk channels changing FC loop ID of 7-14 changing link speed 7-14 configuring 7-14 Disk Configuration screen 8-6 disk drives blinking LED of 8-9 clearing metadata from 8-4 disabling SMART changes 8-8
disabling write-back cache 8-5 displaying 8-2 enabling SMART changes 8-8 enabling write-back cache 8-5 maximum by array type 4-1 minimum by array type 4-1 taking down 8-9 testing 8-10 using disks from different manufacturers A-5 using disks with different capacities A-5 viewing cache status 8-7 viewing status of 4-14, 8-3 Display Drive Cache 8-7 Display Drives screen 5-11, 8-2, 8-4 Display Host List 4-40, 4-43 Display Host List screen 4-40 Display Pool Spares 6-6 displaying array status 4-12 cache status for disk drives 8-7 configuration information 5-6 disk drives 8-2 events 5-2 hardware information 5-6 partition status 4-28 pool spares 6-6 Down Drive 8-9 Drive Status 4-14 Drive Status screen 8-4 drives blinking LED of 8-9 clearing metadata from 8-4 disabling SMART changes 8-8 disabling write-back cache 8-5 displaying 8-2 enabling SMART changes 8-8 enabling write-back cache 8-5 maximum by array type 4-1 minimum by array type 4-1 taking down 8-9 testing 8-10 using disks from different manufacturers A-5 using disks with different capacities A-5 viewing cache status cache 8-7 viewing status of 4-14, 8-3 Dynamic Spare Configuration 6-4
I-3
dynamic spares, enabling 6-3
E
EMP Configuration screen 8-12 EMP LUNs screen 8-12 EMPs changing LUNs for 8-11 changing the enclosure status setting 8-13 changing the polling interval 8-13 changing the slot status setting 8-13 changing the temperature status setting 8-13 LUNs for 7-12 Enable Trust Array 4-25 Enable Trust Array screen 4-25 enabling SMART changes 8-8 write-back cache changes 8-5 Enclosure Features 7-11 enclosures changing LUNs 8-11 changing the enclosure status setting 8-13 changing the polling interval 8-13 changing the slot status setting 8-13 changing the temperature status setting 8-13 Enter Array Name screen 4-2, 4-7 Enter New Name 4-23, 4-35 error events 9-7 error messages 9-5, 9-7 Ethernet card See LAN subsystem Ethernet port accessing the Disk Array Administrator software 3-4, C-1 connecting to 2-12 event log capturing 5-5, 5-10 displaying 5-2 Event Log Menu 5-3 Event Log screen 5-4 events capturing the log file 5-5, 5-10 displaying 5-2 error 9-7 viewing most recent 5-3 viewing one at a time 5-3 viewing whole screen of 5-4
warning 9-5 Exclude All Hosts 4-43 Exclude Listed Hosts 4-43 Expand Function 4-22, 4-23 Expand Partition 4-34 Expand Status screen 4-23 expanding array capacity 4-21 partition capacity 4-28, 4-34 status of 4-23
F
failback, defined 2-24 failover, defined 2-24 FAULT light 2-23, 2-24 FC disk channels changing FC loop ID 7-14 changing speed of 7-14 configuring 7-14 connecting to 2-19 FC host ports connecting to 2-13, 2-19 FC loop IDs, changing for disk channels 7-14 FC port problems with 9-2 features 1-1, B-1 firmware upgrading for the Data Manager 7-24 upgrading for the LAN subsystem 7-25 upgrading for the memory controller 7-24 Flash Utility screen 7-25 Force Offline 7-6 force offline, defined 2-24 forcing a Data Gate offline 7-6 a Data Manager offline 7-6 FTP settings C-4
G
General InfoShield 4-39, 4-44 General InfoShield screen 4-39, 4-44 Global Flags screen 8-15 Global Flags, defined 8-14
I-4
Index
H
Hardware Information 5-9 hardware information capturing 5-10 Hardware Information screen 5-9 hardware information, displaying 5-6 histogram, viewing for reads and writes 5-12 host channels configuring 7-8 problems with 9-2 selecting the link speed 7-9 selecting the topology for 7-9 host ports changing the internal hub configuration 7-10 connecting to 2-13, 2-19 hosts controlling access to partitions 4-41 giving access to all partitions 4-44 giving names to 4-40 Hot Swap Pause 7-23 hot swapping 7-22 HTTP settings C-3 hub configuration, changing for host ports 7-10
resolving using ARP C-2 setting C-3
L
LAN configuring FTP settings C-4 configuring the contact settings C-6 configuring the SNMP settings C-5 configuring the Telnet settings C-4 setting the IP Address C-3 setting up to access Disk Array Administrator software C-1 setting up to access RIO subsystem software 3-4 LAN subsystem resetting C-7 upgrading firmware 7-24 upgrading firmware for 7-25 LEDs blinking for disk drives 8-9 on the RIO subsystem 2-20 leftover drives, clearing metadata from 8-4 lights blinking LEDs for disk drives 8-9 RIO subsystem LED status lights 2-20 Link Speed screen 7-15 link speed, selecting 7-9 LNK light 2-22 LNK lights 2-23, 2-24 log file capturing 5-5, 5-10 viewing 5-2 LOOP topology setting 7-9 LUN information 7-13 LUN Information screen 7-13 LUN screen 4-3, 4-17 LUNs CAPI 7-12 changing for Data Managers 7-9 changing for EMPs 8-11 changing for partitions 4-36 for each Data Manager 7-12 for EMPs 7-12 for partitions 7-12 how presented D-3 understanding 7-12
I
I/O pausing 7-22 resuming 7-23 Include All Hosts 4-43, 4-44 Include Listed Hosts 4-43 InfoShield 4-42 configuring 4-41 naming WWNs 4-40 overview 4-38 setting to include all hosts 4-44 viewing known WWNs 4-39 initial Disk Array Administrator screen 3-3, 3-6 initialization process, stopping for arrays 4-15 Initiator ID screen 7-15 initiator ID, changing 7-14 installing disk and host connection methods 2-14 modules 2-29, 2-30 the RIO subsystem 2-1 IP addresses
I-5
viewing information 7-13
O
offline forcing a Data Gate 7-6 forcing a Data Manager 7-6 putting a Data Gate 7-4 putting a Data Manager 7-4 online putting a Data Gate 7-6 putting a Data Manager 7-6 other Data Manager changing array ownership to 4-24 other, defined 2-24 Overall Statistics 5-13 Overall Statistics screen 5-13 ownership changing for arrays 4-24 defined 2-24
M
MAC hardware address C-2 manage module menu 5-5 Manage Modules screen 5-5 managing arrays 4-12 partitions 4-27 memory upgrading 2-32 menu tree 3-8 metadata, clearing from disk drives 8-4 mirrored disks A-2 mixing disks on arrays A-5 Module Status screen 5-6 modules installing 2-29, 2-30 removing 2-26, 2-28 replacing 2-25 viewing status of 5-5 Mute button 7-16 muting the RIO subsystem alarm 7-16
P
packing list 2-1 parity disk A-2 Partition Name screen 4-16 Partition Statistics 4-31, 4-33 Partition Status 4-30 partitions adding 4-15 changing LUNs for 4-36 changing names of 4-35 controlling access to 4-38, 4-41 creating array with multiple 4-7 creating array with one 4-2 deleting 4-44 expanding capacity of 4-28, 4-34 giving access to all 4-44 LUNs for 7-12 managing 4-27 resetting statistics 4-32 understanding 4-27 viewing statistics 4-30 viewing status of 4-28 pausing I/O 7-22 permissions, setting for partitions 4-38 POINT-TO-POINT topology setting 7-9 Poll Rate screen 8-14 polling interval, changing for enclosures 8-13
N
names changing for arrays 4-23 changing for partitions 4-35 creating for WWNs 4-40 navigating in the Disk Array Administrator software 3-7 network configuring FTP settings C-4 configuring the contact settings C-6 configuring the SNMP settings C-5 configuring the Telnet settings C-4 resetting the LAN subsystem C-7 setting the IP address, IP mask, and gateway C-3 setting up to access Disk Array Administrator software C-1 setting up to access RIO subsystem software 3-4 network interface card See LAN subsystem New LUN screen 4-36 Number of Data Gates 7-16 Number of Drives screen 4-4, 4-9 Number of Spares screen 4-5, 4-10
I-6
Index
Pool Spare Menu 6-5, 6-6 pool spares adding 6-5 defined 6-1 deleting 6-5 displaying 6-6 Power Managers installing 2-29 removing 2-26 replacing 2-25 viewing status of 5-5 Power Ports installing 2-30 removing 2-28 replacing 2-25 viewing status of 5-5 priority, changing for RIO subsystem utilities 7-21 problems with host channels 9-2 terminal screen 9-1 the RIO subsystem 9-4 Put Offline 7-5 put offline, defined 2-25 Put Online 7-6 put online, defined 2-25 putting a Data Gate offline 7-4, 7-6 a Data Manager offline 7-4 a Data Manager online 7-6
R
RAID levels compared A-4 described A-2 RAID reference information A-4 RAID Type screen 4-3, 4-8 rebooting a Data Manager 7-1 reconstructing arrays 4-20, 6-1 Remove Host from List 4-43 removing modules 2-26, 2-28 replacing modules 2-25 Rescan 7-22 rescanning channels 7-21
Reset LAN Subsystem C-7 Reset Statistics 4-33 resetting aggregate statistics for all arrays 5-13 partition statistics 4-32 the LAN subsystem C-7 resolving IP addresses using ARP C-2 restarting a Data Manager 7-1 the LAN subsystem C-7 the RIO subsystem 7-1 Restore Defaults screen 7-23 restoring default settings 7-23 resuming I/O 7-23 RIO subsystem changing utility priority 7-21 changing which owns an array 4-24 configuring 7-1 connecting to the Ethernet port 2-12 connecting to the FC disk channels 2-19 connecting to the FC host ports 2-13, 2-19 connecting to the RS-232 port 2-11 disabling the battery 7-19 displaying configuration information 5-6 displaying events 5-2 displaying hardware information 5-6 enabling the battery 7-19 features 1-1, B-1 installing 2-1 locking the cache setting 7-18 monitoring status of 5-1 problems with 9-4 rescanning channels 7-21 restarting 7-1 restoring defaults 7-23 selecting the link speed 7-9 selecting the topology 7-9 setting the date and time 7-7 shutting down 7-1 specifications B-1 turning the alarm on or off 7-16 understanding LUNs for 7-12 unpacking 2-1 upgrading firmware 7-24 RS-232 port
I-7
connecting to 2-11 settings for 2-11, 3-2
S
screen, changing the display of 3-7 security settings C-3 Select Disk Channel screen 7-14 Select Free Partition screen 4-16 serial port connecting to 2-11 settings for 2-11, 3-2 servers controlling access to partitions 4-41 giving access to all partitions 4-44 giving names to 4-40 Set Date screen 7-7 Set Date/Time 7-7, 7-8 Set Date/Time screen 7-7 Set Time screen 7-8 settings for the RS-232 port 2-11 SFPs, compatible types of 2-14 Shutdown Both menu option 7-4 Shutdown Menu 7-3, 7-4 Shutdown Other 7-3 Shutdown/Restart 7-3, 7-4 shutting down a Data Gate 7-1 a Data Manager 7-1 both Data Managers 7-4 the current Data Manager 7-2 the other Data Manager 7-2, 7-3 the RIO subsystem 7-1 size expanding for arrays 4-21 expanding for partitions 4-28, 4-34 Slot Flags screen 8-15 Slot Flags, defined 8-13 slot status setting, changing for enclosures 8-13 SMART disabling changes to 8-8 enabling changes to 8-8 SMART screen 8-8 SNMP settings C-5 software accessing to configure the RIO subsystem 3-1
menu tree 3-8 navigating in 3-7 spares adding dedicated 6-2 adding pool 6-5 defined 6-1 deleting dedicated 6-3 deleting pool 6-5 displaying pool 6-6 enabling automatic 6-3 enabling dynamic 6-3 use in reconstructing 6-1 specifications B-1 speed changing for FC disk channels 7-14 changing for host channels 7-9 Start Expand 4-22 Start Verify 4-19 statistics resetting aggregate for all arrays 5-13 resetting for partitions 4-32 viewing aggregate for all arrays 5-12 viewing for partitions 4-30 viewing read/write histogram 5-12 status monitoring for system 5-1 of expanding 4-23 viewing for arrays 4-12 viewing for disk drive cache 8-7 viewing for drives 4-14, 8-3 viewing for modules 5-5 viewing for partitions 4-28 STATUS light 2-22, 2-23, 2-24 striped disks A-2 support 9-1 Switch Array Owner 4-24 System Menu 3-3, 3-6 system, monitoring status of 5-1
T
Target ID 7-9 TCP/IP setting up to access Disk Array Administrator software C-1 setting up to access RIO subsystem software 3-4
I-8
Index
using ARP to set up C-2 technical support 9-1 Telnet settings C-4 temperature alarm thresholds for 7-17, B-4 monitoring B-4 Temperature screen 8-14 temperature status setting, changing for enclosures 8-13 terminal emulator software 3-1 terminal screen problems 9-1 Test Unit Ready 8-10 testing disk drives 8-10 theory of operation D-1 time, setting 7-7 topology Auto Detection setting 7-9 LOOP setting 7-9 POINT-TO-POINT setting 7-9 selecting 7-9 troubleshooting 9-1 trusting arrays 4-25 typographic conventions 1-2
viewing aggregate statistics for all arrays 5-12 array status 4-12 cache status for disk drives 8-7 disk drives 8-2 drive status 4-14, 8-3 events 5-2 known WWNs 4-39 LUN information 7-13 partition statistics 4-30 partition status 4-28 pool spares 6-6 read/write histogram 5-12 status for drives 8-7 voltage alarm thresholds for 7-17, B-4 monitoring B-4
W
warning events 9-5 World Wide Names impersonation of D-5 naming 4-40 viewing known 4-39 write-back cache disabling for disk drives 8-5 enabling for disk drives 8-5 locking setting on RIO subsystem 7-18 viewing for disk drives 8-7 WWNs giving names to 4-40 impersonation of D-5 viewing known 4-39
U
unpacking the RIO subsystem 2-1 upgrading DIMMs 2-32 LAN subsystem firmware 7-25 memory controller firmware 7-24 utilities, changing priority of 7-21 Utility Priority screen 7-21
V
Verify Function 4-18, 4-19, 4-20 Verify Status screen 4-19 verifying data 4-18 status of 4-19 stopping process 4-19 View Event Log 5-4 View Expand Status 4-23 View R/W Histogram 5-13 View R/W Histogram screen 5-13 View Statistics 4-32, 5-13 View Statistics screen 5-13 View Verify Status 4-19
I-9
I-10
Chaparral Network Storage, Inc.

7420 E. Dry Creek Parkway
Longmont, CO 80503 2002 Chaparral Network Storage, Inc. All rights reserved. 05/02 Document Number: 07-0096-001

Chaparral Rio User Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chaparral Rio User Guide

Uploaded by

Copyright:

Available Formats

RFF244/RFF288

External RAID Subsystem

Federal Communications Commission Radio Frequency Interference Statement

Canadian Compliance Statement

RFF244/RFF288 Users Guide

Accessing the Disk Array Administrator Software

Creating and Managing Arrays and Partitions

Deleting a Partition ...................................................................................4-44

Monitoring System Status

Configuring the RIO Subsystem

RFF244/RFF288 Users Guide

Managing Disk Drives and Enclosures

Features and Specifications

RFF244/RFF288 Users Guide

RFF244/RFF288 Users Guide

About This Guide

UL approved cUL approved

RFF244/RFF288 Users Guide

Unpacking the RIO Subsystem

RFF244/RFF288 Users Guide

To unpack the RIO subsystem:

Understanding the RFF244 and RFF288

Figure 2-1. Front view

RFF244/RFF288 Users Guide

Power Port B Data Gate 4

Data Gate 2 Data Gate 3

Figure 2-3. Rear view of the RFF288

Connecting the Battery

To connect the battery:

1 Press the latch of each handle of the Data Manager.

RFF244/RFF288 Users Guide

Battery connector and receptacle Push wires down

10 Repeat steps 1 through 9 on the other Data Manager.

Installing the RIO Subsystem

Front-Mounting the RIO Subsystem

RFF244/RFF288 Users Guide

To front-mount the RIO subsystem in a rack:

Rear-Mounting the RIO Subsystem

Figure 2-4. Rear-mounting side rail and screws

Short side rail (long side rail not shown)

Mounting screw (fixed in place) and nut Receiver side rail

Figure 2-5. Rear-mounting rails

Recommended tools for this procedure:

To install the RIO subsystem using the rear-mount kit:

7 Make sure the RIO subsystem is securely mounted.

RFF244/RFF288 Users Guide

Connecting the RIO Subsystem

RS-232 serial ports

Shielded cable or ferrite core required

Figure 2-6. Front view showing connections

FC host sockets (ports 1 and 2 on each Data Gate)

FC disk sockets (ports 3 and 4 on each Data Gate)

Connecting to the RS-232 Port

To connect to the RS-232 port:

RFF244/RFF288 Users Guide

Connecting to the Ethernet Port

To connect to the Ethernet port:

5 Repeat steps 2 through 4 on the other Data Manager.

Connecting the Power Cables

Connecting to the Fibre Channel Host and Disk Ports

RFF244/RFF288 Users Guide

RFF244/RFF288 Users Guide

RFF244/RFF288 Users Guide

Connecting to the Fibre Channel Host Ports