$ swlist PHCO_19571 # PHCO_19571 B.11.00.06 HP Array Manager/60 cum.patch PHCO_19571.ADMN-ENG-A-MAN B.11.00.06 HPArray Manager/60 Utilities Manual Pages PHCO_19571.ARRAY-MGMT B.11.00.06 HPArray Manager/60 Utilities
7KH LQFRUUHFW YHUVLRQ DV OLVWHG DERYH KDV WKH UHYLVLRQ % 7KH FRUUHFW YHUVLRQ KDV WKH UHYLVLRQ % 7KH +3 SDWFK GDWDEDVH DQG IWS VLWHV KDYH WKH FRUUHFW YHUVLRQ RI WKLV SDWFK 7KH LQFRUUHFW YHUVLRQ LV RQO\ IRXQG RQ WKH +38; 6XSSRUW 3OXV 'HFHPEHU ,W LV UHFRPPHQGHG WKDW \RX UHPRYH WKH LQFRUUHFW YHUVLRQ RI 3+&2B DQG LQVWDOO WKH FRUUHFW YHUVLRQ 7KH LQFRUUHFW YHUVLRQ RI 3+&2B LV IRXQG LQ WKH IROORZLQJ EXQGOH

December 1999:

;6:+:&5 %
The correct version of PHCO_19571 is found in the following bundles: March 2000:
;6:*5 % ;6:+:&5 %'HFHPEHU ;6:+:&5 %

Data Parity

Data parity is a second technique used to achieve data redundancy. If a disk fails or becomes inaccessible, the parity data can be combined with data on the remaining disks in the LUN to reconstruct the data on the failed disk. Data parity is used for RAID 3 and RAID 5 LUNs. To ensure high availability, each disk in the LUN should be in a separate enclosure. Parity cannot be used to reconstruct data if more than one disk in the LUN is unavailable. Parity is calculated on each write I/O by doing a serial binary exclusive OR (XOR) of the data segments in the stripe written to the data disks in the LUN. The exclusive OR algorithm requires an even number of binary 1s to create a result of 0. Figure 17 illustrates the process for calculating parity on a five-disk LUN. The data written on the first disk is XORd with the data written on the second disk. The result is XORd with the data on the third disk, which is XORd with the data on the fourth disk. The result, which is the parity, is written to the fifth disk. If any bit changes state, the parity also changes to maintain a result of 0.

Data 1

If this bit is now written as 1.

Parity

This bit will also be changed to a 1 so the total still equals 0.
Figure 17 Calculating Data Parity

Data Striping

Data striping, which is used on RAID 0, 0/1, 3 and 5 LUNs, is the performance-enhancing technique of reading and writing data to uniformly sized segments on all disks in a LUN simultaneously. Collectively, the segments comprise a stripe of data on the LUN. Data striping enhances performance by allowing multiple sets of read/write heads to execute the same I/O transaction simultaneously. The amount of information simultaneously read from or written to each disk is the stripe segment size. The stripe segment size is configurable to provide optimum performance under varying sizes of I/O transactions. Stripe segment size is specified in 512-byte blocks of data. Stripe segment size can affect disk array performance. The smaller the stripe segment size, the more efficient the distribution of data read or written across the stripes in the LUN. However, if the stripe segment is too small for a single I/O operation, the operation requires access to two stripes. Called a stripe boundary crossing, this action may negatively impact performance. The optimum stripe segment size is the smallest size that will rarely force I/Os to a second stripe. For example, assume your application uses a typical I/O size of 64 KB. If you are

Settings that give a higher priority to the rebuild process will cause the rebuild to complete sooner, but at the expense of I/O performance. Lower rebuild priority settings favors host I/Os, which will maintain I/O performance but delay the completion of the rebuild. The rebuild priority settings selected reflect the importance of performance versus data availability. The LUN being rebuilt is vulnerable to another disk failure while the rebuild is in progress. The longer the rebuild takes, the greater the chance of another disk failure. The following sequence occurs following a disk failure and replacement. Figure 23 illustrates the process. A 5-disk RAID 5 LUN is used for this example. 1. Disk 3 in the RAID 5 LUN fails. 2. The disk array locates an available global hot spare and begins recreating on it the information that was on the failed disk. The data and parity on the remaining four disks in the LUN are used to recreate the information. 3. When the rebuild finishes, the global hot spare is part of the LUN, which fulfills the roll of disk 3. 4. When disk 3 is replaced, the disk array begins copying all the information from the former global hot spare to the replacement disk. 5. When copying completes, the LUN is restored to its original configuration. The former global hot spare is returned to the global hot spare disk group and is available to protect against another data disk failure. Note Can a lower capacity disk serve as a hot spare for a larger disk? It is possible for a lower capacity disk to be used as a global hot spare when a larger disk fails. When a disk failure occurs, the disk array controller looks for a global hot spare that is large enough to store the data on the failed disk, not for a disk that matches the capacity of the failed disk. For example, if an 18 Gbyte disk fails but there is only 6 Gbytes of data stored on the disk, a 9 Gbyte global hot spare could be used. Although this feature is available, it is recommended that you always select the largest disks in the array to serve as global hot spares. This will ensure that any disk in the array is protected, regardless of how much data is stored on it.
Data and parity from the remaining disks are used to rebuild the contents of disk 3 on the hot spare disk.
The information on the hot spare is copied to the replaced disk, and the hot spare is again available to protect against another disk failure.
Figure 23 Rebuild Process on a RAID 5 LUN (or Volume Group)
Primary and Alternate I/O Paths
There are two I/O paths to each LUN on the disk array - one through controller A and one through controller B. Logical Volume Manager (LVM) is used to establish the primary path and the alternate path to a LUN. The primary path becomes the path for all host I/Os to that LUN. If a failure occurs in the primary path, LVM automatically switches to the alternate path to access the LUN. The first time an I/O is performed to the LUN using the alternate path, the disk array switches ownership of the LUN to the controller on the alternate path. Once the problem with the primary path is corrected, ownership of the LUN should be switched back to the original I/O path to maintain proper load balancing. The primary path established using LVM defines the owning controller for the LUN. This may override the controller ownership defined when the LUN was bound. For example, if controller A was identified as the owning controller when the LUN was bound, and LVM subsequently established the primary path to the LUN through controller B, controller B becomes the owning controller.

Because each HP Fibre Channel-AL Hub has ten ports, either two host adapters and eight controller modules or four host adapters and six controller modules can attach to each HP Fibre Channel-AL Hub. If any hardware component (controller module, host Fibre Channel I/O adapter, HP Fibre Channel-AL Hub, or fibre optic cable) fails in one Fibre Channel-AL, the I/O communication between hosts and disk arrays can continue through the other Fibre Channel-AL. Supported cable lengths for each segment of the Fibre Channel-AL include 2 m, 16 m, 50 m, 100 m, and 500 m. The maximum combined cable lengths for all segments, that is, the total length of the Fibre Channel-AL should not exceed 5000 m because performance can degrade due to propagation delay. Because of this it is recommended that the total cable length of the Fibre Channel-AL be as short as possible. Fibre optic cables in lengths of 2 m, 16 m, 50 m, and 100 m cables can be ordered from Hewlett-Packard (see chapter 8 for part numbers). Fibre optic cables longer than 100 m must be custom-fabricated for each implementation.
Figure 39 High Availability Topology
Table 10 High Availability Topology Error Recovery
Failing component Disk module Continue after failure Yes What happens and how to recover Applications continue to run on all supported RAID levels (RAID-1, 0/1, and 5). The system administrator or service provider hotswaps the failed disk module. Ownership of the failed controller modules LUNs can transfer automatically to the remaining operational controller module if primary and alternate paths have been configured in LVM. If so, LVM switches automatically and transparently to the alternate path. The system administrator or service provider hot-swaps the failed controller module.

Controller modules

No on path to failed controller module; Yes on alternate path through second controller module Yes

Fan module

Applications continue to run. The system administrator or service provider hot-swaps the fan module. Availability are present, applications continue to run when one power supply module fails. The system administrator or service provider hot-swaps the failed power supply module. I/O operations fail along the path to the failed HP Fibre Channel-AL Hub. I/O operations can transfer automatically to the other HP Fibre Channel-AL Hub if primary and alternate paths have been configured in LVM. If so, LVM switches automatically and transparently to the alternate path. The authorized service provider hot-swaps the failed HP Fibre Channel-AL Hub. I/O operations fail along the path through the failed adapter. If the host has two Fibre Channel adapters connected to a dual-controller module disk array, the array can be accessed through the path to the operational adapter and controller module if primary and alternate paths have been configured in LVM. If so, LVM switches automatically and transparently to the alternate path. The authorized service provider replaces the failed adapter and the system administrator restarts the operating system and applications.

Step 8. Bind LUNs

If a LUN structure has been created on the disk array either at the factory (A5277AZ) or by a reseller, it may not be necessary to perform this step. If no LUN structure has been created, only LUN 0 will exist. When performing this step, consult with the customer to ensure that the desired LUN configuration is created on the disk array. To bind a LUN, type:
amcfg -L <cntrlr>:<LUN> -d <channel:ID>,<channel:ID>,.. -r <RAIDlevel> <options> <ArrayID> For example, the following command creates LUN 1 as RAID 5 using six disks:
amcfg -L A:1 -d 1:1,2:10,3:10,4:1,5:1,6:1 -r 5 <options> <ArrayID> For more information, see "Binding a LUN" on page 289 To use SAM, see "Binding a LUN" on page 267
Step 9. Add Global Hot Spares (Optional)
Hot spares provide an additional level of data protection. A hot spare automatically replaces a failed disk, restoring redundancy and protecting against a second disk failure. For maximum protection against disk failure, it is recommended that one hot spare be created per channel. To add a global hot spare, type: ammgr -h channel:ID <ArrayID> For example, the following command creates a global hot spare: ammgr -h 4:3 <ArrayID>
For more information, see "Adding a Global Hot Spare" on page 296 To use SAM, see "Adding a Global Hot Spare" on page 273
Step 10. Install Special Device Files
After binding LUNs, you must install special device files on the LUNs. This makes the LUNs usable by the operating system. To install the special device files, type: insf -e
Step 11. Check Disk Array Status
The final step is to display the disk array status to ensure that all features are enabled and that the array is working properly. To display disk array status, type: amdsp -a <ArrayID> See Figure 88 on page 284 for a sample status display output that identifies the important fields and the normal values.
Perform the following steps to configure the disk for operation on a Windows NT or Windows 2000 host. Refer to the HP Storage Manager 60 Users Guide for detailed instructions on performing each of these tasks. 1. 2. 3. 4. 5. Add the disk array to the SM60 management topology. Set up any alert notifications. Rename the disk array. Create the desired volume structure. Replace the default 10 Mbyte volume if necessary. Add hot spares as required.

Step 1. Plan the Expanded Configuration
Your expansion strategy will be dictated by the amount of capacity you are adding to the disk array. This includes both the number of new enclosures you are adding, and the number of new disk modules. Careful planning will help ensure that the expansion is performed successfully. 1. Identify the original disk array configuration by performing the following tasks: a. Create a detailed diagram of the existing Disk Array FC60 layout. b. Attach a label to each Fiber Channel cable attached to the disk array, identifying the host interface and disk array controller port it connects. c. Identify the disks comprising each LUN on the disk array. Then attach a label to each disk in the LUN, identifying its LUN number and channel:ID. For example, LUN 0, 4:0. The channel and ID assigned to each disk are a function of the enclosure and slot the disk is installed in. d. Identify all global hot spare disks in the disk array. Then attach a label to each global hot spare disk, identifying the channel:ID of the disk. Note A global hot spare disk should not be moved. If you intend to move a hot spare disk that is not in use, the disk must be removed from the hot spare group. This will change its role to Unassigned. After the disk has been moved to its new location, it can again be assigned the role as a global hot spare.
Identify the expanded disk array layout by performing the following tasks: a. Create a detailed diagram of the expanded HP FC60 array layout. Include all Fibre Channel and SCSI cabling connections. This diagram will serve as your configuration guide as you add the new enclosures. The Capacity Expansion Map on page 235 should assist you in identifying where disk will be moved in the new configuration. b. Attach a second label to each disk that is part of a LUN, identifying the disk enclosure and slot the disk will occupy in the new configuration. The disk should be moved to the enclosure and slot that corresponds to the original channel:ID of the disk.
Step 2. Backup All Disk Array Data
CAUTION It is critical that you perform this step. Protection of user data is essential if a problem occurs during the expansion process.

1. 2. 3.

Stop all I/O activity to the disk array. Backup all data on the Disk Array FC60. Label and store the backup media in a safe place.
Step 3. Prepare the Disk Array for Shut Down
1. Determine if any LUNs in the disk array are using a global hot spare as a result of a disk failure. If any hot spares are in use, perform the following steps: a. Identify and replace the failed disk that caused the use of the global hot spare. b. Wait for the disk array to complete the process of copying data from the hot spare to the replacement disk. c. Verify that the LUN is now in the OPTIMAL state. 2. Verify that the status of each LUN on the disk array is OPTIMAL. All LUNs must be in the optimal state before continuing.

Segment ------4 4

Disks ----1:0 LUN Information - the 3:0 status of each LUN should 2:0 be OPTIMAL 4:0
LUN 31 is the default UTM LUN. GOOD status indicates the UTM is enabled and operating normally. See note on page 283.
WCA --X X RCA --X X CMA --X X
LUN WCE RCD --- --- --0 X 1 X. Total capacity of Total capacity of Total capacity of
Cache Status for each LUN - all LUNs should have the status values shown
LUNs on controller A = 84.6 GB LUNs on controller B = 50.8 GB all configured LUNs = 135.4 GB
LUNs should typically be distributed between both controllers for best performance. LUN ownership can be reassigned to balance LUN usage.
Vendor ID = HP Product ID = A5277A Array ID = 000A00A0B80673A6 Array alias = Array1 ----------------------------------------SCSI Channel:ID = 1:0 Enclosure = 0 Slot = 0 Disk State = OPTIMAL Disk Information - the status of each disk should be Optimal for each disk Disk Group and Type = 060E86000238C6360F LUN assigned to a LUN. Capacity = 17.0 GB Manufacturer and Model = SEAGATE ST318203LC Serial Number = LRB61150 Firmware Revision = HP01. Total capacity of all installed physical disks = 271.4 GB Hot Spare Activity -------------------None Vendor ID = HP Product ID = A5277A Array ID = 000A00A0B80673A6 Array alias = Array1 ----------------------------------------Disk Group 060E86000738C6395B: Disk Group Type = LUN Disk Group Information - this is another Number of LUNs = 1 representation of the LUN information LUN(s) = 6 Remaining Capacity = 0.0 MB RAID Level = 1 Segment Size = 4 KB Disks: 1:3 3:3. Total remaining capacity for LUN disk groups = 0.0 MB
Information for Controller A - 000A00A0B80673A6: Controller Status = GOOD Controller Mode = ACTIVE Vendor ID = HP Product ID = A5277A Serial Number = 1T00310110 Controller Information - make sure the Firmware Revision = 04000304 following conditions are met: Boot Revision = 04000200 - Both controllers should be ACTIVE HP Revision = HP08 Loop ID = 5 - The Loop ID must be unique for each AL_PA = 0xE0 controller Preferred AL_PA = 0xE0 - The three levels of firmware revisions must Controller Date = 05/08/2000 be identical for each controller Controller Time = 13:38:53 Cache Battery Age = 0 to 89 days NVSRAM Checksum = 0x353181DF Information for Controller B - 000A00A0B80673A6: Controller Status = GOOD Controller Mode = ACTIVE Vendor ID = HP Product ID = A5277A Serial Number = 1T90510188 Firmware Revision = 04000304 Boot Revision = 04000200 HP Revision = HP08 Loop ID = 4 AL_PA = 0xE1 Preferred AL_PA = 0xE1 Controller Date = 05/08/2000 Controller Time = 13:38:54 Cache Battery Age = 0 to 89 days NVSRAM Checksum = 0x353181DF Information for Disk System SCSI Channel = Thumbwheel Setting = Controller Status = Vendor ID = Product ID = Serial Number = Firmware Revision = Information for Disk System SCSI Channel = Thumbwheel Setting = Controller Status = Vendor ID = Product ID = Serial Number = i i i 1 (USSA02010592), Controller B: Disk Enclosure Information 2 make sure the following 0 conditions are met: GOOD - The status of both controllers HP (BCCs) should be GOOD A5294A USSA02010649 - The Thumbwheel Setting HP04 must be the same for each 1 (USSA02010592), Controller A:controller 1 - The Thumbwheel Setting 0 should correspond to the GOOD enclosure position in the rack. HP Uppermost enclosure set to 0, A5294A next one down set to 1, etc. USSA02010592

The following is a sample of an Asynchronous Event Log entry:
Controller log sense for Subsystem 001100A0B8060166 at Mon Dec 12:51:Controller Time Stamp = FRU Code = 0x08 FRU Code Qualifier = 0x8142 Sense Key = 0x06 Additional Sense Code = 0x3F Add Sense Code Qual = 0xC7 Decoded Field Replaceable Unit Information: FRU Group = Sub-Enclosure Group FRU ID Setting = 1 FRU Type = Power Supply 4
FRU State = Failed Decoded SCSI Sense: Non-media Component Failure Reporting LUN = 0
For information on interpreting SCSI sense codes, see "SCSI Sense Codes" on page 327.
Flushing Disk Array Log Contents
Array Manager 60 automatically retrieves the contents of the disk array controller log at regular intervals, typically 15 minutes. However, if necessary you can manually flush (retrieve) the contents of the disk array log to the host. This may be useful if you suspect a very recent event has not yet been retrieved. To flush the contents of the disk array log, type: amutil -l <ArrayID> A message is displayed indicating that the log file has been flushed. The log contents can now be displayed using the amlog command as described above.

Purging Controller Logs

The controller logs are retrieved at regular intervals and stored on the host. Over time, these logs may grow quite large. Major event logging in particular generates very large log files. To reduce the space consumed by the logs, the oldest log file can be purged from the log file directory.
To purge the oldest log file in the host directory, type: amutil -p Note Always use the amutil -p command to purge the controller logs. This command maintains the catalog pointers used to access the log files. Using a system command such as rm to remove the log files will cause log catalog errors. Management of the log files can be automated by creating a script that purges the oldest log files at regular intervals using amutil -p. This technique can be used to ensure that the log files dont grow to a size that may cause the ?var file system to overflow.

Resetting Battery Age

The battery age should be reset to zero when the battery is replaced. This ensures an accurate indication of the age of the battery To reset the battery age to zero, type: ammgr -b <ArrayID>
Installing Updated Patches
The following HP-UX patches are required when upgrading to HP08 firmware. The patches must be installed before upgraidng the contoller firmware to HP08. If the patches are not installed, the upgrade will fail. HP-UX 10.20: PHCO_22627 and PHSS_22846 HP-UX 11.0: PHCO_22628 and PHSS_22847 The required patches can be downloaded from the following web sites: http://us-support2.external.hp.com/index.html/ (External web site) ftp://hpatlse.atl.hp.com/hp-ux_patches/ (Internal web site)
The patches are not currently included on the HP-UX Support Plus CD-ROM. They must be downloaded from the indicated web sites.

Upgrading Disk Firmware

The firmware on each disk can be upgraded individually. Because different disks require different firmeware files, it may be necessary to
Managing the Disk Array Using STM
STM is an online diagnostic tool, but it can be used to perform some of the common tasks involved in managing the disk array. The tasks described here are available to all users and do not require the purchase of a license. See "Support Tools Manager" on page 347 for more information on using this tool.
Checking Disk Array Status Information
The STM Information Tool displays disk array status information. See "Using the STM Information Tool" on page 352 for more information on running and using this tool.
STM Tool xstm, mstm Action Select: Tools > Information Tool > Run
The STM Expert Tool can be used to bind a LUN. See "Using the STM Expert Tool" on page 355 for more information on running and using this tool.
STM Tool xstm, mstm Action Select: Tools > Expert Tool > Run Select: Utilities > Bind LUN
The STM Expert Tool can be used to unbind a LUN. See "Using the STM Expert Tool" on page 355 for more information on running and using this tool.
STM Tool xstm, mstm Action Select: Tools > Expert Tool > Run Select: Utilities > Unbind LUN
The STM Expert Tool can be used to add a global hot spare. See "Using the STM Expert Tool" on page 355 for more information on running and using this tool.
STM Tool xstm, mstm Action Select: Tools > Expert Tool > Run Select: Utilities > Hot Spares > Create
The STM Expert Tool can be used to remove a global hot spare. See "Using the STM Expert Tool" on page 355 for more information on running and using this tool.
STM Tool xstm, mstm Action Select: Tools > Expert Tool > Run Select: Utilities > Hot Spares > Delete
The STM Expert Tool can be used to locate disk modules. to aid in identification. The LEDs on the disk array components are flashed to aid in identification. See "Using the STM Expert Tool" on page 355 for more information on running and using this tool.

When a disk module is replaced, the new disk inherits the group properties of the original disk. For example, if you replace a disk that was part of LUN 1, the replacement will also become part of LUN 1. If the disk is a replacement for a global hot spare or an unassigned disk, the replacement will become a global hot spare or an unassigned disk.
A special feature called drive lockout prevents unsupported disk drives from being used in the disk array. If an unsupported disk drive is installed in the disk array, the drive will be failed. Locked out drives will be indicated with a special drive status (0x1B).
Removing a Disk Module or Filler Module
1. 2. 3. Unlock and open the disk enclosure door. If removing a disk module, insert the plug end of your ESD wrist strap in the disk enclosure ESD socket (A in Figure 94). Release the module by squeezing the latch tab (B in Figure 94) and sliding the module part way out of the enclosure. While the disk is spinning, it is vulnerable to damage. Wait for the disk to stop spinning (about 15 seconds) before fully removing the module from the enclosure.
To avoid electric shock hazard, do not touch the backplane or adjacent drive electronics when removing and inserting disks.
Slide the module out of the slot until you can grasp the handle (C). Support the disk module with your other hand around the enclosed side. When removing adjacent disk modules, removing them from right to left improves access to successive modules.
A ESD plug-in B cam latch C handle
Figure 94 Disk Module Removal
Installing a Disk Module or Filler Module
CAUTION Touching the disk circuit board can cause high energy discharge and damage the disk. Disks modules are fragile and should be handled carefully.
If the disk module you are installing has been removed from another Disk Array FC60, you should ensure that the module has a status of Unassigned. This is done by unbinding the LUN the disk module was a part of in the original disk array. See "Moving Disks from One Disk Array to Another" on page 255.
Remove the replacement disk from its ESD bag, being careful to grasp the disk by its handle (A in Figure 96). Pull the cam latch (B) away from the disk module. Mark the slot number that the disk is being installed into on the Slot Location Map on the top of the disk module. See Figure 95. This facilitates reinstalling the disk module in the correct slot.

Mark Slot

Figure 95 Disk Slot Identification Label
Use both hands to hold the disk one on the handle and the other on the carrier frame.
Slide the disk module into the slot with capacity label up (C in Figure 96).
Close the cam latch to seat the module firmly into the backplane. An audible click indicates the latch is closed properly. Check the LEDs (D in Figure 96) above the disk module for the following behavior: Both LEDs should turn on briefly. The amber Fault LED should turn off. The green disk Activity LED should blink for a few seconds and then go out. If the host begins to access the disk, the Activity LED will flash. If this behavior does not occur, refer to chapter 6, Troubleshooting, for information on identifying and solving the problem.

Number of A5294A/AZ per A5277A/AZ 1,2, or 3 4, 5, or 6 Number of SCSI cables per A5294A/AZ 2 1
Both models include the following components (except as indicated):
Table 55 A5294A Custom Cabling Option
Option 701 Description Delete one 2m cable included in A5294A product and add one 5m VHDCI SCSI cable for connection of A5277A to A5294A in a different rack
Table 56 A5294A/AZ Storage Capacity Options

Option Description

Note: All disk enclosures ordered with a single A5277A/AZ must have identical Storage Capacity Options. Reference / Legal / Regulatory 4, 9-Gbyte 10K rpm disk drives 8, 9-Gbyte 10K rpm disk drives 10, 9-Gbyte 10K rpm disk drives 4, 18-Gbyte 10K rpm disk drives 8, 18-Gbyte 10K rpm disk drives 10, 18-Gbyte 10K rpm disk drives 4, 36-Gbyte 10K rpm disk drives 8, 36-Gbyte 10K rpm disk drives 10, 36-Gbyte 10K rpm disk drives 4, 18-Gbyte 15K rpm disk drives 8, 18-Gbyte 15K rpm disk drives 10, 18-Gbyte 15K rpm disk drives
Table 57 Supporting Software (CD ROMS)
Product B6191A A5628A Description IPR Distribution CD-ROM

HP Storage Manager 60

Disk Array FC60 Upgrade and Add-On Products
Order the following parts to expand or reconfigure your original purchase: Table 58 Upgrade Products
Order No. A5276A A5282A A5633A A5595A A5622A A5278A 002 A5279A A5306A A5307A A5308A A5250A A5251A A5672A A3583A A3531A A3735A A3736A A5296A A5649A Description 9.1-Gbyte disk drive module 10K rpm Ultra 2 LVD 18.2-Gbyte disk drive module 10K rpm Ultra 2 LVD 18.2-Gbyte disk drive module 15K rpm Ultra 2 LVD 36.4-Gbyte disk drive module 10K rpm Ultra 2 LVD 73.4-Gbyte disk drive module 10K rpm Ultra 2 LVD Add-on controller, includes Media Interface Adaptor (MIA) Must also order Option 002 for 256 Mbytes of cache 256 Mbyte cache option for A5278A Controller cache 512-Mbyte upgrade kit. Includes two 256-Mbyte DIMMs 2 m, VHDCI to VHDCI SCSI Cable, M/M 5 m, VHDCI to VHDCI SCSI Cable, M/M 10 m, VHDCI to VHDCI SCSI Cable, M/M Rail kit for HP legacy cabinets: C2785A, C2786A, C2787A, A1896A, and A1897A Rail kit for HP Rack System/E: HP A4900A, A4901A, A4902A, J1500A, J1501A, J1502A Rail kit for Rittal 9000 racks 2-meter Fibre Channel cable 16-meter Fibre Channel cable 50-meter Fibre Channel cable 100-meter Fibre Channel cable VHDCI SCSI terminator (LVD/SE) Storage Partition Support (up to 8 partitions)

The environmental limits in a nonoperating state (shipping and storage) are wider:
Temperature: Maximum gradient: Relative humidity: Altitude:
-40 C to 70 C (-40 F to 158 F) 24 C per hour (43.2 F per hour) 15% to 90% noncondensing 4600 m (15,000 ft)
Sound power: 6.4 Bels Sound pressure at operators position: 56.2 dB(A)
Warranty and License Information
Hewlett-Packard Hardware Limited Warranty
HP warrants to you, the end-user Customer, that HP SureStore E Disk Array FC60 hardware components and supplies will be free from defects in material and workmanship under normal use after the date of purchase for three years. If HP or Authorized Reseller receives notice of such defects during the warranty period, HP or Authorized Reseller will, at its option, either repair or replace products that prove to be defective. Replacement parts may be new or equivalent in performance to new. Should HP or Authorized Reseller be unable to repair or replace the hardware or accessory within a reasonable amount of time, Customer's alternate remedy will be a refund of the purchase price upon return of the HP SureStore E Disk Array FC60.
Replacement Parts Warranty
HP replacement parts assume the remaining warranty of the parts they replace. Warranty life of a part is not extended by means of replacement. Your HP SureStore E Disk Array FC60 warranty does not cover the following: Products purchased from anyone other than HP or an authorized HP reseller Non-HP products installed by unauthorized entities Consumables, such as batteries Customer-installed third-party software Routine cleaning, or normal cosmetic and mechanical wear Damage caused by misuse, abuse, or neglect Damage caused by parts that were not manufactured or sold by HP Damage caused when warranted parts were repaired or replaced by an organization other than HP or by a service provider not authorized by HP

Items Not Covered

Software Product Limited Warranty
The HP Software Product Limited Warranty will apply to all Software that is provided to you by HP as part of the HP SureStore E Disk Array FC60 for the NINETY (90) day period specified below. This HP Software Product Limited Warranty will supersede any non-HP software warranty terms that may be found in any documentation or other materials contained in the computer product packaging with respect to covered Software. Ninety-Day Limited Software Warranty. HP warrants for a period of NINETY (90) DAYS from the date of the purchase that the Software will execute its programming instructions when all files are properly installed. HP does not warrant that the software will be uninterrupted or error free. In the event that this software product fails to execute its programming instructions during the warranty period, Customers remedy will be a refund or replacement. Should HP be unable to replace the media within a reasonable amount of time, Customers alternate remedy will be a refund of the purchase price (license fee) upon return of the product and all copies. Removable Media (if supplied). HP warrants the removable media, if supplied, upon which this product is recorded to be free from defects in materials and workmanship under normal use for a period of NINETY (90) DAYS from the date of purchase. In the event the media proves to be defective during the warranty period, Customers remedy will be to return the media to HP for replacement. Should HP be unable to replace the media with a reasonable amount of time, Customers alternate remedy will be a refund of the purchase price upon return of the product and destruction of all other non-removable media copies of the software product. Note that removable media does not include hot-swap hard drives, which are warranted under the HP Hardware Limited Warranty. Notice of Warranty Claims. All warranty claims must be made during the applicable warranty period or within thirty (30) days after the expiration of the applicable warranty period. Any claim made after that time will not be eligible for warranty service but may be service under a separate HP support contract covering the product.

AM60Srvr starting 241 AM60Srvr daemon 241 amcfg binding a LUN 289 changing LUN ownership 293 unbinding a LUN 292 amdsp checking rebuild progress 305 listing disk arrays 292 amlog viewing logs 309 ammgr adding hot spare 296 assigning an alias 297 displaying parity scan status 307 halting parity scan 307 performing a parity scan 306 removing hot spare 296 resetting battery age 312 setting cache flush limit 301 setting cache flush threshold 300 setting cache page size 300 setting controller date and time 297 amutil changing rebuild priority settings 305 flushing disk array log 311 locating disk modules 304 managing the UTM 298 AR60Diag using to create a boot device 222 Array Manager adding a global hot spare 296 assigning an alias 297 binding a LUN 289
calculating LUN capacity 292 changing LUN ownership 293 changing rebuild priority settings 305 checking disk array status 282 checking rebuild progress 305 command summary 278 described 238 displaying parity scan status 307 flushing disk array log 311 halting parity scan 307 identifying disk modules 292 installing 240, 241 listing all disk arrays 288 locating disk modules 304 managing disk array logs 309 managing log files 307 performing a parity scan 306 removing a global hot spare 296 replacing a LUN 294 rescanning for disk arrays 288 resetting battery age 312 running 241 setting cache flush limit 301 setting cache flush threshold 300 setting cache page size 300 synchronizing controller date and time 297 unbinding a LUN 293 array See disk array ArrayID 280 listing for all arrays 288 assigning LUN ownership 247 B backplane controller card. See BCC module basic topology 102, 103 error recovery 108 batteries See battery backup module battery age resetting 312 battery backup module cache protection 46 described 45
life expectancy 46 removal and replacement 400 battery charger See battery backup module BCC module described 29 troubleshooting 380 binding a LUN using Array Manager using SAM 267 using STM 314 boot support 222 C cabinets supported 18 cable installation Fibre Channel 196 SCSI 187 cables FC-AL supported lengths 110 length performance degradation 116 cache upgrading to 512 MB 258 cache flush limit impact on performance 252 setting 301 cache flush threshold impact on performance 251 setting 300 cache page size impact on performance 252 setting 300 caching 66 read I/O 66 write I/O 66 calculating LUN capacity 292 campus topology 102, 125 capacity adding 254 expanding with disk enclosures 224 managing 242
maximum 75 changing LUN ownership 293 channel number disk module 244 channel:ID described 280 checking disk array status using Array Manager using SAM 260 using STM 314 circuit breakers, European 149 cntrlrID described 280 command summary Array Manager command-based interface See cstm component status conditions 321 configuration management software 216 switches 176 configuring LUNs 242 controller date synchronizing with host 297 controller enclosure acoustics 423 dimensions 420 environmental 422 front cover 37 host ID 39 installation 170, 173 LED locations 204 models 412 power down 43 power supply fan module described 43 power supply modules described 42 specifications 420 voltage 421 weight 420 controller enclosure modules described 34

primary LUN path 64 drive lockout 387 drivers system 146 E electrical requirements 147 EMC compliance 434 EMS hardware event monitoring 21, 362 enabling disk WCE 303 enclosure number 245 environmental requirements disk enclosure electrical requirements 149 electrical 147 power distribution units (PDUs/ PDRUs) 150 recommended European circuit breakers 149 recommended PDU/PDRU for HP System/E racks 151 site 147 environmental specifications 422, 426 ESD strap part number 160 evaluating performance 250 event messages, contents of 363 event notification on HP-UX 363 expanding storage capacity adding disk enclosures 224 overview 75 Expert Tool 355 menu options 356 using menu mode 356 using X Windows 355 F factory default configurations See
troubleshooting 380 fan module, disk enclosure described 31 fault detection 31 removal and replacement 392 fast write cache LED 40 FC-AL, See Fibre Channel Arbitrated Loop Fibre Channel controller modules 39 host connections 39 hub connection 71 IO adapters and drivers 146 throughput 71 Fibre Channel Arbitrated Loop 102, 131 Fibre Channel cable installation 196 Fibre Channel connection 71 Fibre Channel host ID addressing 179 filler module adding or replacing 386 installation 166 removal Firmware Update Tool 357 firmware, BCC troubleshooting 382 flushing disk array log 311 front cover, controller enclosure 37 removal and replacement 397 FRU codes 322 full-bus mode setting 178 switch 178 G global hot spare adding using Array Manager adding using SAM 273 adding using STM 315 removing using Array Manager removing using SAM 275 removing using STM 315
recommended array configurations
fan troubleshooting 381 fan module
tips for selecting disks 62 global hot spare disks described 61 H hardware event monitoring See EMS
hardware event monitoring
hardware path interpreting 208 peripheral device addressing 208 sample ioscan 207 volume set addressing (VSA) 209 heat output controller enclosure 421 disk enclosure 425 high availability features 21, 47 planning 73 high availability topology 102 error recovery 118 hardware components 115 redundant HP FC-AL Hubs 115 high availability, distance, and capacity topology 102, 120123 error recovery 123 host connections 39 host adapters 146 host ID controller modules 39 hot spare See global hot spare hot swappable modules 18 disk enclosure 27 HP Fibre Channel Arbitrated Loop Hub 102 campus topology 125 cascading 120 high availability topology 115 high availability, distance and capacity topology 120 single-system distance topology 110 HP-UX boot device 222