HP A7143A RAID160 SA Controller Support Guide

Transcription

1 HP A7143A RAID160 SA Controller Support Guide Installation and Administration of the HP A7143A PCI 4-Channel RAID160 SA SCSI Controller HP-UX Manufacturing Part Number : J E0512 Printed in the US Copyright 2005 Hewlett-Packard Development Company L.P.

2 Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Warranty A copy of the specific warranty terms applicable to your Hewlett-Packard product and replacement parts can be obtained from your local Sales and Service Office. U.S. Government License Proprietary computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Trademark Notices UNIX is a registered trademark in the United States and other countries, licensed exclusively through The Open Group. 2

3 Contents Preface: About This Document 7 1. RAID Technology Overview What is RAID? The RAID Concept Logical Drives and Arrays HP RAID160 SA Controller Supported RAID Configurations RAID 0 No Fault Tolerance Advantages Disadvantages RAID 1 Disk Drive Mirroring Advantages Disadvantages RAID 1+0 Disk Drive Mirroring and Striping Advantages Disadvantages RAID 5 Distributed Data Guarding Advantages Disadvantages RAID ADG Advanced Data Guarding Advantages Disadvantages Summary of RAID Methods Choosing a RAID Method RAID160 SA Controller Overview Board Components and Features Overview of Controller Features Overview of Array Accelerator Features Batteries PCI System Interface SCSI Support Fault Management Features Installation Overview Overview of Installation Steps Planning Disk Configurations RAID160 SA Array Configuration Guidelines

4 Contents Installation Prerequisites for the RAID160 SA Controller HP A7143A RAID160 SA Controller Support Matrix Installing the RAID160 SA Controller Locating Software for the RAID160 SA Controller Installing Software for the RAID160 SA Controller Preparing for RAID160 SA Controller Installation Installing the RAID160 SA Controller Hardware (Offline) Online Addition and Replacement Online Installation of the RAID160 SA Controller RAID160 SA Controller OLAR Error Recovery Online Addition Error Online Replacement Error OLAR Error Recovery Connecting the Cables and the StorageWorks Disk Enclosures Supported StorageWorks Disc Enclosures External Cabling for HP Servers Labeling the Cables Verifying the Installation RAID160 SA Controller Firmware Determining the RAID160 SA Device File Determining the RAID160 SA Firmware Version Updating the RAID160 SA Firmware Physical Disk Firmware Determining the RAID160 SA Device File Determining the SCSI Channel, the SCSI ID, and the Firmware Version for Physical Disks Updating Physical Disk Firmware Setting up a RAID160 SA Controller As a Boot Device Considerations Dependencies Installing HP-UX on a Logical Drive Configuring the RAID160 SA Controller Planning the RAID Configuration saconfig Configuration CLI

5 Contents Determining the RAID160 SA Device File Displaying the RAID160 SA Configuration Adding a Spare Disk Drive Deleting a Spare Disk Drive Change the Rebuild Priority of a Logical Drive Specify Percentage of Cache Used for Read Caching Auto-Fail Missing Disks At Boot Clear the Configuration Troubleshooting HP Support Tools Manager (STM) Event Monitoring Service (EMS) ODE The sautil Command Troubleshooting with sautil sautil <device_file> Logical Drive State Definitions Physical Disk State Definitions sautil <device_file> accept_media_xchg <logical_drive_number> sautil <device_file> run_startup_script A. Probability of Logical Drive Failure RAID Level and Probability of Drive Failure B. Controller Specifications RAID160 SA Controller Specifications C. Hard Drive Installation and Replacement Background General Information About Hard Drive Failure Recognizing Disk Drive Failure Compromised Fault Tolerance Automatic Data Recovery General Aspects of Disk Drive Replacement Drive Failure During Rebuild Minimizing Fatal System Errors During Rebuild

6 Contents D. Electrostatic Discharge Preventing System Damage Handling Parts Grounding E. Questions and Answers RAID160 SA Controller Q & A Glossary

7 Preface: About This Document This document describes how to install, configure, and troubleshoot the HP A7143A PCI 4-Channel RAID160 SA SCSI controller on HP-UX 11iv1 & 11i v2 64-bit platforms. The latest version of this document can be found on line at docs.hp.com. Intended Audience This document is intended for system and network administrators responsible for installing, configuring, and managing fault tolerant data storage. Administrators are expected to have knowledge of HP-UX operating system concepts, commands, and configuration. This document is not a tutorial. New and Changed Documentation in This Edition This Support Guide was published in conjunction with the initial release of the HP A7143A PCI 4-Channel RAID160 SA SCSI controller. This is the second edition of this document. Publishing History Table 1 Publishing History Details Document Manufacturing Part Number Operating Systems Supported Supported Product Versions Publication Date J i v1 (64-bit) B August 2003 J i v2 (64-bit) B December 2005 What s in This Document The HP A7173A RAID160 SA Controller Support Guide is divided into several chapters containing information about RAID in general, the RAID levels supported by the RAID160 SA controller specifically, and 7

8 installation, configuration, and troubleshooting details for the RAID160 SA controller. There are also several appendixes containing supplemental information. Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6 Appendix B Appendix C Appendix A Appendix D Appendix E RAID Technology Overview Use this chapter to learn about RAID in general, followed by specific details on the RAID levels supported by the RAID160 SA controller. RAID160 SA Controller Overview This chapter provides an overview of RAID160 SA features and functionality. Installation Overview This chapter lists RAID160 SA installation steps and installation prerequisites. Installing the RAID160 SA Controller This chapter covers all aspects of RAID160 SA installation, including online installation, hardware requirements, software requirements, firmware requirements, and setting up RAID160 SA logical drives as a boot devices. Configuring the RAID160 SA Controller This chapter includes information on planning RAID configurations and details on the use of the saconfig command to configure logical drives on the RAID160 SA controller. Troubleshooting This chapter provides information of the different troubleshooting tools available for the RAID160 SA controller including using the sautil command for troubleshooting. Controller Specifications Hard Drive Installation and Replacement Probability of Logical Drive Failure Electrostatic Discharge Questions and Answers Typographical Conventions This document uses the following conventions. Book Title The title of a book. On the web and on the Instant Information CD, it may be a hot link to the book itself. 8

9 KeyCap Emphasis Bold Bold ComputerOut UserInput Command The name of a keyboard key. Note that Return and Enter both refer to the same key. Text that is emphasized. Text that is strongly emphasized. The defined use of an important word or phrase. Text displayed by the computer. Commands and other text that you type. A command name or qualified command phrase. HP-UX Release Name and Release Identifier Each HP-UX 11i release has an associated release name and release identifier. The uname (1) command with the -r option returns the release identifier. This table shows the releases available for HP-UX 11i. Table 2 HP-UX 11i Releases Release Identifier Release Name Supported Processor Architecture B HP-UX 11i v1 (September 2005) PA-RISC B HP-UX 11i v2 (December 2005) Intel Itanium, PA-RISC Related Documents Additional information about the HP A7143A RAID160 SA controller can be found within docs.hp.com in the /O Cards and Networking Software collection under Smart Array (RAID). Other documents in this collection include: HP A7143A RAID160 SA Controller Release Notes HP A7143A RAID160 SA Controller Installation Guide 9

10 HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Please send comments to: Please include document title, manufacturing part number, and any comment, error found, or suggestion for improvement you have concerning this document. Also, please let us know if there is anything about this document that is particularly useful, so we can incorporate it into our other documents. 10

11 1 RAID Technology Overview This chapter contains the following sections providing an overview of the RAID technology and descriptions of the different RAID levels that are supported by the HP A7173A RAID160 SA controller: Chapter 1 11

12 RAID Technology Overview NOTE If you are ready to install the RAID160 SA controller and you are familiar with RAID concepts and the RAID levels supported by the RAID160 SA controller, proceed to Chapter 3, Installation Overview, on page Chapter 1

13 RAID Technology Overview What is RAID? What is RAID? The RAID concept was proposed in 1987 when A Case for Redundant Arrays of Inexpensive Disks (RAID) was published by David Patterson, Garth Gibson, and Randy Katz at the University of California, Berkeley. This study defined five different disk array configurations, or RAID levels. All of the RAID levels provided fault tolerance and each RAID level offered different feature sets and performance, to accommodate different systems administration priorities and computing environments. The idea was to combine multiple, small, inexpensive, disk drives into an array that would function as a single logical drive, but provide better performance than a single large expensive disk drive (SLED). NOTE Currently, RAID stands for Redundant Array of Independent Disks, because, in general, disks have become inexpensive. Small disk drives are lower in performance and have less capacity, when compared to large disk drives. Small drives also have lower storage density than large drives, but small drives are equal to or better than large drives in four areas: I/O per actuator (multiple I/O capability) Cost per megabyte Mean time between failures (MTBF) SCSI controller per disk drive (better cost/performance ratio) Grouping small disk drives into an array provides: High transfer rates Increased disk capacity High I/O rates The RAID study pointed out that as the number of disk drives in an array (also referred to as a stripe set) increases, the mean time between failures (MTBF) of the array decreases. At the time the RAID study was Chapter 1 13

14 RAID Technology Overview What is RAID? published, if a disk drive crashed data restoration was typically dependent on backup from a tape drive. In addition, the system would have to be taken off-line to replace the failed disk. The RAID Concept The RAID study proposed a multi-level concept for improved data input/output performance (arrays with logical drives) and improved data availability (by avoiding the impact of disk drive failures). Five original RAID configurations, or levels (RAID 1 through RAID 5), were defined to meet the needs of various computing environments. As the five original RAID configurations progress from RAID 1 through RAID 5, data redundancy increases. Each RAID configuration offers greater fault tolerance than the RAID configuration that precedes it. Overall, a RAID has three main attributes that are exploited in some way by all of the five original RAID configurations and by most of the other RAID configurations that have been defined since the RAID study was published in They are: A set of physical disk drives that can function as one or more logical drives (improved I/O) Data distribution across multiple physical disks (striping) Data recovery or reconstruction of data in the event of a physical disk failure (redundancy) One exception is RAID 0. The term RAID 0 was adopted to describe a disk array configuration that includes data block striping, but lacks redundancy. Since the publication of the RAID study, RAID 2, RAID 3 and RAID 4 have become impractical due to technological changes. There are other RAID configurations (some are proprietary) that have been defined over the years, but a detailed description of all RAID configurations is beyond the scope of this document. The RAID configurations that are supported by the HP RAID160 SA controller (0, 1+0, 5, and ADG) are detailed in HP RAID160 SA Controller Supported RAID Configurations on page Chapter 1

15 RAID Technology Overview Logical Drives and Arrays Logical Drives and Arrays Connecting extra disk drives to a system increases the total storage capacity, but has no effect on the efficiency of read/write (R/W) operations. Data can only be transferred to one physical disk at a time (see Figure 1-1). Figure 1-1 Disk Drives Added to System R/W P1 P2 P3 With an array controller installed in the system, the capacity of several physical disks can be combined into one or more virtual units called logical drives (also called logical volumes). Chapter 1 15

16 RAID Technology Overview Logical Drives and Arrays The read/write heads of all of the physical disks in a logical drive are active simultaneously, improving input/output (I/O) performance and reducing the total time required for data transfer (see Figure 1-2). Figure 1-2 Physical Disks Configured into a Logical Drive (L1) L1 P1 P2 P3 16 Chapter 1

17 RAID Technology Overview Logical Drives and Arrays Because the read/write heads for each physical disk are active simultaneously, the same amount of data is written to each disk during any given time interval. Each unit of data is called a block. The blocks form a set of data stripes spread evenly over all of the physical disks in a logical drive (see Figure 1-3). Figure 1-3 Data Striping (S1-S4) of Data Blocks B1-B12 S1 B1 B2 B3 S2 B4 B5 B6 S3 S4 B7 B10 B8 B11 B9 B12 For data in the logical drive to be readable, the data block sequence must be the same in every stripe. This sequencing process is performed by the array controller (HP RAID160 SA), which sends the data blocks to the disk drive write heads in the correct order. A natural consequence of the striping process is that each physical disk in a given logical drive will contain the same amount of data. If one physical disk has a larger capacity than other physical disks in the same logical drive, the extra capacity is wasted because it cannot be used by the logical drive. The group of physical disks containing the logical drive is called a drive array (or just array). Since all of the physical disks in an array are commonly configured into just one logical drive, the term array is also often used as a synonym for logical drive. Each logical drive is distributed over all of the physical disks within an array. A logical drive can also extend over more than one channel on the same controller, but it cannot extend over more than one controller. Chapter 1 17

18 RAID Technology Overview Logical Drives and Arrays Disk failure, although rare, is potentially catastrophic. If a physical disk fails, the logical drive it is assigned to will fail, and all of the data on that logical drive will be lost. To protect against data loss due to physical disk failure, logical drives can be configured with fault tolerance. The RAID configurations that are supported by the HP RAID160 SA controller are: RAID 0 Data Striping only (no fault tolerance) RAID 1 Data Mirroring only (fault tolerant) RAID 1+0 Drive Mirroring and Striping (fault tolerant) RAID 5 Distributed Data Guarding (fault tolerant) RAID ADG Advanced Data Guarding (fault tolerant) For any configuration except RAID 0, further protection against data loss can be achieved by assigning a physical disk as an online spare (or hot spare). Spare disk drives contain no data and must be in the same array as the logical drive they are assigned to. Multiple spare disk drives can be assigned to a logical drive, limited only by the availability of unused physical disks in the array. When a spare disk drive is assigned to a logical drive, it can only serve as a spare for the logical drive it is assigned to. When a physical disk in the array fails, the controller automatically rebuilds the information that was originally on the failed disk, onto an online spare. The system is quickly restored to full RAID-level data protection. In the unlikely event that another disk in the array fails while data is being rewritten to the spare, the logical drive may fail, depending on which RAID configuration is in use. See Appendix A, Probability of Logical Drive Failure,for details. 18 Chapter 1

19 RAID Technology Overview HP RAID160 SA Controller Supported RAID Configurations HP RAID160 SA Controller Supported RAID Configurations RAID 0 No Fault Tolerance The RAID 0 configuration enhances performance with data striping, but there is no data redundancy to protect against data loss when a physical disk fails. RAID 0 is useful for rapid storage of large amounts of non-critical data (for printing or image editing, for example), or when cost is the most important consideration (see Figure 1-4 on page 19). Figure 1-4 Data Striping (S1-S4) of Data Blocks B1-B12 S1 B1 B2 B3 S2 B4 B5 B6 S3 S4 B7 B10 B8 B11 B9 B12 Advantages Highest performance configuration for writes Lowest cost per unit of data stored All disk capacity is used to store data (none needed for fault tolerance) Disadvantages All data on the logical drive is lost if a physical disk fails Chapter 1 19

20 RAID Technology Overview HP RAID160 SA Controller Supported RAID Configurations Cannot use an online spare Can only preserve data by backing it up to external disk drives NOTE The original Berkeley RAID study only defined levels 1 through 5. RAID Level 0 was conceived later, but is not considered to be a true RAID, because it does not provide any fault tolerance. RAID 1 Disk Drive Mirroring In this configuration, only two physical disks are present in the array. Data is duplicated from one disk onto the other disk creating a mirrored pair of disk drives, but there is no striping of data (see Figure 1-5, Disk Drive Mirroring of P1 onto P2 (RAID 1), ). Figure 1-5 Disk Drive Mirroring of P1 onto P2 (RAID 1) B1 B2 B3 B4 P1 B1 B2 B3 B4 P2 Advantages No data loss or interruption of service, if a disk fails Fast read performance - data is available from either disk Disadvantages Cost is high - 50% of disk space is allocated for data protection 20 Chapter 1

21 RAID Technology Overview HP RAID160 SA Controller Supported RAID Configurations Only 50% of total disk drive capacity is usable for data storage RAID 1+0 Disk Drive Mirroring and Striping This configuration requires an array with four or more physical disks. The disks are mirrored in pairs and data blocks are striped across the mirrored pairs (see Figure 1-6, Mirroring and Striping (RAID 1+0), Figure 1-6 Mirroring and Striping (RAID 1+0) S1 S2 B1 B5 B2 B6 B3 B7 B4 B8 P1 P2 P3 P4 P5 P6 P7 P8 S1 S2 B1 B5 B2 B6 B3 B7 B4 B8 In each mirrored pair, the physical disk that is not busy answering other requests answers any read request sent to the array (this behavior is called load balancing). If a physical disk fails, the remaining disk in the mirrored pair can still provide all the necessary data. Several disks in the array can fail without incurring data loss, as long as no two failed disks belong to the same mirrored pair. This fault-tolerance method is useful when high performance and data protection are more important than the cost of physical disks. Advantages Highest read and write performance of any fault-tolerant configuration No loss of data as long as none of failed disks are mirrored to another failed disk (up to half of the physical disks in the array can fail) Chapter 1 21

22 RAID Technology Overview HP RAID160 SA Controller Supported RAID Configurations Disadvantages Expensive (many disks needed for fault tolerance) Only 50% of total disk drive capacity usable for data storage RAID 5 Distributed Data Guarding RAID 5 employs a parity data formula. With this configuration, one block in each data stripe contains parity data that is calculated for each data block in that stripe. The blocks of parity data are distributed over the physical disks that make up the logical drive, with each physical disk having only one block of parity data (see Figure 1-7, Distributed Data Guarding, Showing Parity Information (Px,y), ). When a physical disk fails, the data that was on the failed disk can be calculated from the data blocks on the remaining physical disks in the logical drive, by using the parity data for each stripe in that logical drive. This recovered data is usually written to an online spare in a process called a rebuild. This configuration is useful when cost, performance, and data availability are equally important. Figure 1-7 Distributed Data Guarding, Showing Parity Information (Px,y) S1 B1 B2 P1,2 S2 S3 S4 B3 P5,6 B7 P3,4 B5 B8 B4 B6 P7,8 Advantages High read performance No loss of data if one physical disk fails 22 Chapter 1

23 RAID Technology Overview HP RAID160 SA Controller Supported RAID Configurations More disk drive capacity usable than with RAID 1+0 parity information only requires the storage space equivalent to one physical disk on the array Disadvantages Relatively low write performance Loss of data if a second disk fails before data from the first failed disk is rebuilt RAID ADG Advanced Data Guarding RAID ADG is similar to RAID 5 in that parity data is generated (and stored) to protect against data loss caused by physical disk failure. With RAID ADG, however, two different sets of parity data are generated for each data block on a stripe, then the two parity data blocks are stored on different physical disks allowing data to be preserved even if two physical disks fail simultaneously. As can be seen in Figure 1-8, Advanced Data Guarding (RAID ADG), the two sets of parity data require as much storage capacity as the data blocks they correspond to on each stripe in a logical drive. Chapter 1 23

24 RAID Technology Overview HP RAID160 SA Controller Supported RAID Configurations This method is most useful when data loss is unacceptable, but cost must also be minimized. The probability that data loss will occur when arrays are configured with RAID ADG is less than when they are configured with RAID 5 (see Appendix A, Probability of Logical Drive Failure, on page 133). Figure 1-8 Advanced Data Guarding (RAID ADG) B1 B2 P1,2 Q1,2 B3 P3,4 Q3,4 B4 P5,6 Q5,6 B5 B6 Q7,8 B7 B8 P7,8 Advantages High read performance High data availability any two disks can fail without loss of critical data More disk drive capacity usable than with RAID 1+0 parity information requires only the storage space equivalent to two physical disks Disadvantages The only significant disadvantage of RAID ADG is a relatively low write performance (lower than RAID 5), due to the need for two sets of parity data. 24 Chapter 1

25 RAID Technology Overview Summary of RAID Methods Summary of RAID Methods Table 1-1 Table 1-1 summarizes the important features of the different RAID configurations that are supported by the HP RAID160 SA controller. The decision chart in Table 1-2 on page 26. may help with determining which option is best for your computing environment. Summary of RAID Methods RAID 0 RAID 1 RAID1+0 RAID 5 RAID ADG Alternative name Striping (no fault tolerance) Mirroring Mirroring and Striping Distributed Data Guarding Advanced Data Guarding Usable disk drive space* Usable disk drive space formula Minimum number of physical disks Tolerates failure of one physical disk? 100% 50% 50% 67% to 93% 50% to 96% n n/2 n/2 (n-1)/n (n-2)/n No Yes Yes Yes Yes Tolerates simultaneous failure of more than one physical disk? No No Only if no two failed disks are in a mirrored pair No Yes Read performance High High High High High Write performance High Medium Medium Low Low Relative cost Low High High Medium Medium *Values for usable disk drive space are calculated with these assumptions: (1) All physical disks in the array have the same capacity; (2) Online spares are not used; (3) No more than 14 physical disks are used per array for RAID 5; (4) No more than 56 disks are used with RAID ADG. Chapter 1 25

26 RAID Technology Overview Choosing a RAID Method Choosing a RAID Method Table 1-2 Choosing a RAID Method Most Important Fault tolerance Also Important Cost effectiveness Suggested RAID Level RAID ADG I/O performance RAID 1, RAID 1+0 Cost effectiveness I/O performance Fault tolerance I/O performance Cost effectiveness RAID ADG RAID 5 (RAID 0 if fault tolerance is not required) RAID 5 (RAID 0 if fault tolerance is not required) Fault tolerance RAID 1, RAID Chapter 1

27 2 RAID160 SA Controller Overview This chapter contains the following sections providing an overview of the RAID160 SA controller features and functionality: Chapter 2 27

28 RAID160 SA Controller Overview Board Components and Features Board Components and Features The RAID160 SA controller has four Wide Ultra160 SCSI channels and 256 MB of cache. Figure 2-1 HP A7143A RAID160 SA controller Table 2-1 Hardware Overview Item Description 1 Two internal 68-pin Wide SCSI connectors (channel 1 nearer the bracket, channel 2 nearer the board center). These internal connectors are not supported on the HP A7143A RAID160 SA controller. 2 Four external (VHDCI) connectors (channels 1 and 3 nearer the main board) 3 Array accelerator cache 28 Chapter 2

29 RAID160 SA Controller Overview Board Components and Features NOTE Ports 1 and 2 each have two connectors (one internal and one external). However, only one connector can be used per channel at any given time. Ports 3 and 4 can be used only for external disk drives. The internal connectors are not supported on the HP A7143A RAID160 SA controller. Figure 2-2 Array Accelerator Cache with Batteries For detailed controller board specifications, refer to Appendix B, Controller Specifications. Overview of Controller Features Four Wide Ultra160 SCSI channels, supporting up to 56 disk drives (4 channels, 14 drives per channel) Support for HP-UX 11i v1 Operating System (64-bit only) Backward compatibility with Wide Ultra2 devices Removable array accelerator 64-bit, 33/66-MHz PCI system interface Other features supported: RAID 0 (striping) RAID 1, 1+0, 5, and ADG (fault tolerant) Chapter 2 29

30 RAID160 SA Controller Overview Board Components and Features vpars (HP-UX Virtual Partitions) Ignite UX Hot-pluggable disk drives Drive movement Adjustable stripe size S.M.A.R.T. disk drives Multiple online spares per array Background initialization Overview of Array Accelerator Features The array accelerator is a high performance, battery-backed, 100-MHz SDRAM DIMM cache module. The RAID160 SA controller uses cache to store read data from the disk drives. The system can later access this read data. The controller firmware uses the read-ahead and most recently used caching algorithms. The RAID160 SA controller also uses cache to complete drive write operations more quickly. This use of the cache has further performance benefits: If the system requires data that still resides in the write cache, the controller delivers this data from the cache. This process is quicker than delivering the data from a drive. If the system writes new data to the same location, the controller overwrites the cache contents. This eliminates a drive write operation. If the system performs a RAID 1 procedure, the controller gets mirrored data from the cache instead of from host memory. If the system performs a RAID 5 procedure, the write cache collects enough data blocks from several write accesses to carry out a full stripe write to the disk drives. This operation eliminates the need to calculate and update parity information each time a data block is written to the drive. Other features of the array accelerator include: 30 Chapter 2

31 RAID160 SA Controller Overview Board Components and Features Cache capacity of 256-MB with 224-MB usable cache (32 MB of the cache is used for transfer buffer). Error checking and correcting (ECC) memory, providing single-bit data correction. Batteries The array accelerator cache has two NiMH battery packs. Figure 2-3 Battery Packs If a power outage occurs, the batteries will preserve cashed data for up to 72 hours. When power is restored to the system, an initialization process will write the preserved data to the disk drives. The batteries are continuously recharged using a trickle-charging process whenever the system power is on. Chapter 2 31

32 RAID160 SA Controller Overview Board Components and Features IMPORTANT The batteries on a new RAID160 SA controller may have a low charge when the controller board is first installed. No action is required on your part, since the internal circuitry automatically recharges the batteries and enables the cache. The recharge process takes less than four hours. The controller will function properly during this time, but without the performance advantage of the array accelerator. When the batteries are charged to an acceptable capacity, the array accelerator is automatically enabled. PCI System Interface RAID160 SA controller interfaces with the system through a high-performance 64-bit PCI bus that: Runs at 66 MHz Provides a high-speed path (up to 528 MB/s) between the system board and the controller Includes two parity protection signals The RAID160 SA controller is a PCI Bus Master device conforming to Rev. 2.2 of the PCI Local Bus Specification. As a bus master device, it takes control of the PCI bus during high-speed transfers, freeing the system processor to handle application processing or other types of tasks. For maximum performance, HP recommends that you use only 66-MHz devices on any given 66-MHz PCI bus. Combining 66-MHz and 33-MHz devices on a PCI bus will decrease the overall bandwidth to 33-MHz speeds. SCSI Support The RAID160 SA controller supports disk drives that conform to Wide Ultra160 and Wide Ultra2 standards. Although Wide Ultra2 devices operate at a different maximum speed from Wide Ultra160 devices, operating speeds are unaffected if they are connected to the same SCSI bus because they both use low voltage differential (LVD) signaling. 32 Chapter 2

33 RAID160 SA Controller Overview Board Components and Features Fault Management Features The RAID160 SA controller and the HP-UX operating system support several fault management and data reliability features that minimize the impact of disk drive defects on your system. Auto-Reliability Monitoring (ARM) is a firmware process that operates in the background scanning physical disks for bad sectors in fault-tolerant logical drives. ARM also verifies the consistency of parity data in logical drives that are using RAID 5 or RAID ADG. This process assures that you can recover all data successfully if a disk failure occurs in the future. ARM operates only when you select a fault-tolerant configuration (RAID 1 or higher). Dynamic sector repair by the RAID160 SA controller automatically remaps any sectors that have media faults (detected either during normal operation or by auto reliability monitoring). S.M.A.R.T. is an industry-standard diagnostic and failure-prediction feature of physical disks, developed by HP in collaboration with the disk drive industry. It monitors several factors that can be used to predict imminent physical disk failure due to mechanical causes. Such factors include the condition of the read/write head, the seek error rate, and the spin-up time. When a threshold value is exceeded for one of these factors, the disk sends an alert that failure is imminent. Thus, the user can back up data and replace the disk drive before failure occurs. NOTE An online spare does not become active and start rebuilding when the imminent failure alert is sent, because the degraded disk has not actually failed yet and is still online. The online spare is activated only after a disk in the array has failed. Drive failure alert features cause an alert message to be sent to Event Monitoring Services (EMS) when physical disk or logical drive failure occurs. Interim data recovery occurs if a disk fails in fault-tolerant configurations (RAID level 1 or higher). Chapter 2 33

34 RAID160 SA Controller Overview Board Components and Features If a physical disk fails in RAID 1, RAID 1+0, RAID 5, or ADG, the system will still process I/O requests, but at a reduced performance level. Replace the failed physical disk as soon as possible to restore performance and full fault tolerance for the logical drive it belongs to. The risk of continuing operations without replacing a failed physical disk varies depending on the RAID level that has been configured: RAID 1: If RAID 1 is configured, the result will be a single mirrored pair of disks. If one physical disk fails, the remaining disk in the mirrored pair can still provide all of the data. RAID 1+0: A RAID 1+0 configuration will have a minimum of 4 physical disks, and the total number of physical disks will be divisible by 2 (to support mirrored pairs). In RAID 1+0, if a physical disk fails, the remaining disk in any mirrored pair will still provide all of the data that was on the failed disk. In fact, several physical disks in an array can fail without incurring data loss, as long as no two failed physical disks belong to the same mirrored pair. RAID 5: If a physical disk fails in a RAID 5 configuration, data is recovered via a parity formula and is typically written to an on-line spare physical disk. If a second physical disk fails before the data from the initial physical disk failure has been rebuilt on the on-line spare disk, the logical drive will fail and data will be lost. ADG: Similar to RAID 5, ADG also relies on a parity scheme to rebuild data if a physical disk fails. However, in an ADG configuration the parity data is duplicated on two different physical disks. As a result, ADG can support the failure of two physical disks without data loss. For a more detailed description of the RAID levels supported by the HP A7143A RAID160 SA controller see Chapter 1, RAID Technology Overview, on page 11. For detailed information on the probability of logical drive failure, see Appendix A, Probability of Logical Drive Failure, on page 133. Recovery ROM is a redundancy feature that ensures continuous system availability by providing a backup ROM. This feature protects against corruption of a ROM image (caused, for example, by power fluctuation during ROM upgrade). If corruption occurs, the server automatically restarts using the remaining good copy of the 34 Chapter 2

35 RAID160 SA Controller Overview Board Components and Features ROM image. When you upgrade the ROM, the inactive image (the one not being used by the system) is upgraded. There is not normally any noticeable difference in operation. When you use Recovery ROM for the first time, however, both ROM images are upgraded, causing a boot delay of about 60 seconds. Chapter 2 35

36 RAID160 SA Controller Overview Board Components and Features 36 Chapter 2

37 3 Installation Overview This chapter provides information to help you plan the installation and configuration of the RAID160 SA controller. Chapter 3 45

38 Installation Overview NOTE Complete Smart Array documentation (including the Smart Array Support matrix) is available on under the I/O Cards and Networking Software section in the Smart Array (RAID) category. NOTE To view a detailed list of support accessories visit the system configuration site at: 46 Chapter 3

39 Installation Overview Overview of Installation Steps Overview of Installation Steps Installation steps for the RAID160 SA controller are as follows: Step 1. Plan your disk configurations (see Chapter 1, RAID Technology Overview, on page 11). Step 2. Check the installation prerequisites (see Installation Prerequisites for the RAID160 SA Controller on page 49). Step 3. Install the software: See Locating Software for the RAID160 SA Controller on page 52 and Installing Software for the RAID160 SA Controller on page 53. Step 4. Install the controller: See Installing the RAID160 SA Controller Hardware (Offline) on page 57 or Online Addition and Replacement on page 59. Step 5. Upgrade the controller firmware, if necessary: See RAID160 SA Controller Firmware on page 74). Step 6. Connect the JBODs (see Connecting the Cables and the StorageWorks Disk Enclosures on page 66). Step 7. Label the cables connecting the JBODs to the controller (see Labeling the Cables on page 69). Step 8. Verify the installation: See Verifying the Installation on page 71. Chapter 3 47

40 Installation Overview Planning Disk Configurations Planning Disk Configurations If you have not determined the RAID level you want to configure for your application, see Chapter 1, RAID Technology Overview, on page 11 for details on RAID160 SA supported RAID levels. RAID160 SA Array Configuration Guidelines Please keep in mind the following configuration limits for the RAID160 SA controller: The maximum number of physical disks per channel is 14. The maximum number of arrays per controller is 8. (An array is a grouping of physical disks.) The maximum number of logical drives per controller is Chapter 3

41 Installation Overview Installation Prerequisites for the RAID160 SA Controller Installation Prerequisites for the RAID160 SA Controller Before installing the RAID160 SA controller, check to make sure the following hardware and software prerequisites have been met: Read the RAID160 SA controller Release Note, so you can check for any known problems, required patches, or other information you need for installation. Plan your disk configurations (see Planning Disk Configurations on page 48). Make sure you have super-user (root) privileges. Confirm your HP-UX operating system version is supported by the RAID160 SA controller. To determine the HP-UX version you are using, enter this command: uname -a See the RAID160 SA controller Release Note or Table 3-1, HP A7143A Support Matrix, on page 50, for information about the required operating system versions. Make sure the /usr/sbin, /sbin, and /usr/bin directories are in your PATH statement. To do this, log in as root and enter this command: echo $PATH CAUTION If any data currently exists on the StorageWorks disk enclosure, back it up if you want to retain the file system and the data. Configuring logical drives will destroy any data on the disks. When you are sure you have met the installation prerequisites, go to Chapter 4, Installing the RAID160 SA Controller, on page 51. Chapter 3 49

42 Installation Overview Installation Prerequisites for the RAID160 SA Controller HP A7143A RAID160 SA Controller Support Matrix Table 3-1 HP A7143A Support Matrix Supported Systems HP-UX Release Software Bundle Name controller Firmware Level OLAR Support Boot Support rp24xx A400 A500 11i, 64-bit RAID-01 version 3.32 No Yes rp54xx Excluding: 11i, 64-bit RAID-01 version 3.32 Yes Yes L1000 (Product Number A5576A) L2000 (Product Number A5191A) rp7400 Excluding: 11i, 64-bit RAID-01 version 3.32 Yes Yes N4000 Revision A (Product Number A3639A) N4000 Revision B (Product Number A3639B) rp i, 64-bit RAID-01 version 3.32 Yes Yes 50 Chapter 3

43 4 Installing the RAID160 SA Controller This chapter contains the following sections detailing hardware, software, and firmware installation for the RAID160 SA controller: Chapter 4 51

44 Installing the RAID160 SA Controller Locating Software for the RAID160 SA Controller Locating Software for the RAID160 SA Controller The drivers, utilities and manpages for the RAID160 SA controller are located at the HP Software Depot. Go to Search for A7143A to find the pci 4-channel raid160 sa scsi controller Click on receive for free Fill out the free product registration form and click on next Look for Download Software and click on A7143A_11_11_01.depot to download the drivers, utilities and manpages for the RAID160 SA controller In the Documents column next to the Download Software column, click on Installation Instructions to download instructions for using the Software Distributor tool to install the drivers, utilities and manpages for the RAID160 SA controller 52 Chapter 4

45 Installing the RAID160 SA Controller Installing Software for the RAID160 SA Controller Installing Software for the RAID160 SA Controller The drivers, utilities and manpages for the RAID160 SA controller are contained in the RAID-01 bundle located in the pci 4-channel raid160 sa scsi controller depot, see Locating Software for the RAID160 SA Controller. They can be installed using the Software Distributor (SD). The SD is a tool for installing software on HP-UX host systems. The SD can also be used to remove software from HP-UX host systems. The instructions for using the SD to install or remove the drivers, utilities and manpages for the RAID160 SA controller can be downloaded at the HP Software Depot, see Locating Software for the RAID160 SA Controller. The RAID-01 bundle is composed of several files that will be copied to the appropriate directories on the host system. The SD will add the following files to an HP-UX host configuration: /usr/conf/lib/libciss.a This is the library of 64-bit object modules that must be linked into the HP-UX kernel /usr/conf/lib/ciss_dbg.o This is the 64-bit debug object module that must be linked into the HP-UX kernel /usr/conf/master.d/ciss This is the master file /opt/raidsa/bin/sautil This is the support tool. sautil is an abbreviation for Smart Array Support Utility Chapter 4 53

46 Installing the RAID160 SA Controller Installing Software for the RAID160 SA Controller /opt/raidsa/bin/saconfig This is the command line configuration tool. saconfig is an abbreviation for Smart Array Configuration Utility /sbin/rc2.d/s900ciss S900ciss (Run-2; start script) is a symbolic link pointing to /sbin/init.d/ciss /sbin/init.d/ciss ciss is a startup script to make a device file for RAID160 /usr/sbin/olrad.d/ciss This is the script for OLAR /usr/share/man/man1m.z The manpages for sautil and saconfig are located here /opt/raidsa/bin/maxwell332.bin This is the RAID160 SA controller firmware 54 Chapter 4

47 Installing the RAID160 SA Controller Preparing for RAID160 SA Controller Installation Preparing for RAID160 SA Controller Installation Before installing a RAID160 SA controller in a server, backup all data. This step is mandatory if the disks were not previously configured on a RAID160 SA controller, because the data format will not be recognized and the existing data will not be preserved. Also, if you are connecting non-arrayed SCSI disk drives to a RAID160 SA controller, you must backup all data, because data is not preserved when RAID controllers are connected to non-arrayed disk drives. NOTE If your server supports Online Addition and Replacement (OLAR) of the RAID160 SA controller and you plan to do an online installation, see Online Addition and Replacement on page 59. See the Table 3-1, HP A7143A Support Matrix, on page 50, to find out if your server supports OLAR. To prepare a server that does not support OLAR, or if you would prefer to install the RAID160 SA controller offline: 1. Close all applications. 2. Power down the server. 3. Power down any peripheral devices that are attached to the server. 4. Unplug the AC power cord from the outlet, and then from the server. CAUTION In systems using external data storage, be sure that the server is the first unit powered down and the last unit to be powered back up. Doing this ensures that the system will not erroneously mark the disk drives as failed. Chapter 4 55

48 Installing the RAID160 SA Controller Preparing for RAID160 SA Controller Installation WARNING To reduce the risk of personal injury or damage to the equipment, consult the safety information and user documentation provided with your server before attempting installation. Many computers are capable of producing energy levels that are considered hazardous. These computers are intended to be serviced by qualified personnel trained to deal with those hazards. Do not remove enclosures or attempt to bypass any interlocks that may be provided for the purpose of removing these hazardous conditions. CAUTION Electrostatic discharge (ESD) can damage electronic components. Be sure that you are properly grounded before continuing the installation procedure. See Appendix D, Electrostatic Discharge, on page 159, for ESD information. The RAID160 SA controller contains electronic components that can easily be damaged by small amounts of static electricity. To avoid damage, follow these guidelines: Store the controller in its antistatic plastic bag until you are ready to install it Work in a static-free area, if possible Handle the controller only by the edges. Do not touch electronic components or electrical traces If you must lay the controller down, place it on a non-conductive mat or surface Before beginning installation, and without removing the RAID160 SA controller from its antistatic bag, inspect the controller for any signs of obvious damage, such as chipped or loose components. Contact HP if the controller is damaged. 56 Chapter 4

49 Installing the RAID160 SA Controller Installing the RAID160 SA Controller Hardware (Offline) Installing the RAID160 SA Controller Hardware (Offline) 1. Disconnect any peripheral devices from the server. 2. Remove or open the access panel on the server. 3. Select an available 66-MHz PCI slot. Slots that use a 64-bit interface may provide higher performance. 4. Remove the slot cover or open the hot-plug latch. Save the retaining screw, if one is present. 5. Slide the controller board along the slot alignment guide. Figure 4-1 Installing the HP A7143A RAID160 SA controller NOTE Your server may look slightly different from the one illustrated 6. Press the controller board firmly into the slot so the contacts on the board edge are properly seated in the system board connector. 7. Secure the board in place with the hot-plug latch or retaining screw. Chapter 4 57

50 Installing the RAID160 SA Controller Installing the RAID160 SA Controller Hardware (Offline) 8. Continue by following the instructions given in Connecting the Cables and the StorageWorks Disk Enclosures on page Chapter 4

51 Installing the RAID160 SA Controller Online Addition and Replacement Online Addition and Replacement Online Addition and Replacement (OLAR) allows the RAID160 SA controller to be added online to HP-UX systems that support OLAR, without having to reboot. If the OLAR feature is used, it will not be necessary to completely shut down and then reboot the system to add or replace a RAID160 SA controller. System hardware uses per-slot power control combined with HP-UX OLAR utilities, to enable online addition or replacement of RAID160 SA controllers, without adversely affecting other system components. You can add or replace a RAID160 SA controller in an HP-UX system that supports OLAR, by using the SAM utility to invoke the OLAR script. If you are using SAM to online add or replace a controller, SAM will intervene and provide warnings to minimize the chance that you will perform an OLAR procedure that will adversely affect your HP-UX system. IMPORTANT When using OLAR to add or replace a RAID160 SA controller, it is important to pay attention to the warning messages that will be displayed. It is necessary to remove the SCSI cables from a RAID160 SA controller that is about to be online replaced, before the PCI slot is powered off. It is necessary to wait until power has been restored to the PCI slot, before the SCSI cables are connected to an add-in or replacement RAID160 SA controller. If the SCSI cables are removed, or connected, to the RAID160 SA controller while the PCI slot is powered off, the OLAR procedure will have to be repeated. See RAID160 SA Controller OLAR Error Recovery on page 62. During a RAID160 SA controller replacement operation, SAM performs a Critical Resource Analysis (CRA), which checks all channels on the target controller for critical resources that would be temporarily unavailable, while the controller is shut down. After completing the Chapter 4 59

52 Installing the RAID160 SA Controller Online Addition and Replacement CRA, SAM presents the options available to you. If critical resources will be affected by the OLAR procedure, you will have the option to replace the controller when the system is offline. IMPORTANT In many cases, other controllers (host bus adapters) and slots within the system are dependent on the target controller. For example, if the target controller has multiple-channels (the RAID160 SA controller has 4 channels), suspending or deleting drivers for the target PCI slot also suspends individual drivers for the multiple hardware paths on the controller installed in that PCI slot. For detailed instructions and information on using the OLAR feature, see, Managing PCI Cards with OLAR, which is the 2nd chapter of the Configuring HP-UX for Peripherals book, Part Number B This document can be viewed or downloaded at or a hard copy can be ordered from HP. For detailed information about using SAM, see Using System Administration Manager (SAM). This document can be viewed or downloaded at or a hard copy can be ordered from HP. 60 Chapter 4

53 Installing the RAID160 SA Controller Online Installation of the RAID160 SA Controller Online Installation of the RAID160 SA Controller If your system has one or more slots that support OLAR and you want to use OLAR to install the controller in one of those slots follow these steps: Step 1. Be sure version B or later of the ciss driver (RAID160 SA software) is installed on your system. See Locating Software for the RAID160 SA Controller on page 52. Step 2. Install the RAID160 SA controller in your HP-UX system according to the procedure described in the Managing PCI Cards with OLAR, which is the 2nd chapter of the Configuring HP-UX for Peripherals book, Part Number B This document can be viewed or downloaded at or a hard copy can be ordered from HP. TIP To improve performance, install the RAID160 SA controller in a non-shared PCI slot running at PCI 2X speed or greater. IMPORTANT When using OLAR to add or replace a RAID160 SA controller, it is important to pay attention to the warning messages that will be displayed. It is necessary to remove the SCSI cables from a RAID160 SA controller that is about to be online replaced, before the PCI slot is powered off. It is necessary to wait until power has been restored to the PCI slot, before the SCSI cables are connected to an add-in or replacement RAID160 SA controller. If the SCSI cables are removed, or connected, to the RAID160 SA controller while the PCI slot is powered off, the OLAR procedure will have to be repeated. See RAID160 SA Controller OLAR Error Recovery on page 62. Chapter 4 61

54 Installing the RAID160 SA Controller RAID160 SA Controller OLAR Error Recovery RAID160 SA Controller OLAR Error Recovery This section explains how to recover: If you are attempting an online addition of a RAID160 SA controller and the SCSI cables are connected before the PCI slot is powered on If you are attempting an online replacement of a RAID160 SA Controller and the SCSI cable(s) are not disconnected, before the PCI slot is powered off If you are attempting an online replacement of a RAID160 SA Controller and the SCSI cable(s) are reconnected, before the PCI slot is powered on again In any of these circumstances, an OLAR error message will be displayed (see Figure 4-4, First Error Message, ). Online Addition Error If you are attempting an online addition of a RAID160 SA controller and the SCSI cable(s) are connected to the add-in controller, before power is restored to the PCI slot, an OLAR error message will appear on your monitor (see Figure 4-4, First Error Message, ). Proceed to OLAR Error Recovery on page 64. Online Replacement Error A message will appear during online replacement warning you when to disconnect the SCSI cables from the A7143A adapter (RAID160 SA controller) you are replacing. See Figure 4-2, SCSI Cable Disconnect Warning, : 62 Chapter 4

55 Installing the RAID160 SA Controller RAID160 SA Controller OLAR Error Recovery Figure 4-2 SCSI Cable Disconnect Warning If you continue the online replacement according to the instructions, once the replacement controller has been installed in the PCI slot, the following message will appear (see Figure 4-3, SCSI Cable Reconnect Note, ): Figure 4-3 SCSI Cable Reconnect Note At this point you reset the RAID160 SA controller and the online replacement is complete. If the error message in Figure 4-4 appears, before the online replacement procedure is completed, proceed to the next section OLAR Error Recovery. Chapter 4 63

56 Installing the RAID160 SA Controller RAID160 SA Controller OLAR Error Recovery OLAR Error Recovery If the SCSI cables are disconnected from, or connected to, a controller after the PCI slot is powered off, the OLAR procedure will fail and the following message will appear (see Figure 4-4, First Error Message, ): Figure 4-4 First Error Message At this point the controller is suspended and will remain suspended, unless the following steps are followed: 1. Click OK on the first error message (see Figure 4-4, First Error Message, ) 2. The following message will appear (see Figure 4-5, Second Error Message, ). Figure 4-5 Second Error Message 64 Chapter 4

57 Installing the RAID160 SA Controller RAID160 SA Controller OLAR Error Recovery 3. Now, disconnect the SCSI cable(s) from the controller and click YES. The following message will be appear (see Figure 4-6, SCSI Cable Reconnect Note, ): Figure 4-6 SCSI Cable Reconnect Note 4. Now connect the SCSI cable(s) to the controller, click OK, and run sautil /dev/cissxx reset_adapter. After the reset operation is completed, the controller will be operational. Chapter 4 65

58 Installing the RAID160 SA Controller Connecting the Cables and the StorageWorks Disk Enclosures Connecting the Cables and the StorageWorks Disk Enclosures Each channel on the RAID160 SA controller supports up to 14 drives Ports 1 and 2 each have two SCSI connectors, one for external storage units and one for internal hard drives in the server The internal and external connectors on channel 1 cannot be used simultaneously The internal and external connectors on channel 2 cannot be used simultaneously Ports 3 and 4 can only be connected to external storage units NOTE Currently the internal ports on the RAID160 SA controller are not supported. Peripherals attached to any of the connectors must have a unique SCSI ID value in the range of 0 to 15 (except ID 7, which is reserved for controller use). The SCSI ID value determines the priority given to the device when it attempts to use the SCSI bus. The supported HP StorageWorks disk enclosures automatically set the SCSI IDs for the physical disks they contain. IMPORTANT To preserve an existing configuration when replacing an existing RAID160 SA controller with a different RAID160 SA controller, be certain to reconnect the SCSI cables to the same channels on the replacement controller as the channels they had been connected to on the original controller, (channel 1 to channel 1, channel 2 to channel 2, and so on). To prevent signal degradation, SCSI buses require termination on both ends. In HP servers and storage systems, the controller, SCSI cable, and backplane provide the required termination. 66 Chapter 4

59 Installing the RAID160 SA Controller Connecting the Cables and the StorageWorks Disk Enclosures Supported StorageWorks Disc Enclosures The RAID160 SA controller supports the following HP StorageWorks disc enclosures: StorageWorks 43xxT (Tower) Ships with one VHDCI to VHDCI 6-foot cable StorageWorks 4314R (Rack) Ships with one VHDCI to VHDCI 12-foot cable StorageWorks 4354R (Rack) Ships with two VHDCI to VHDCI 12-foot cables External Cabling for HP Servers All HP StorageWorks storage enclosure models include external SCSI cables. Check the connector type on your storage device to identify the cable type needed. See Figure 3-2 and Table 3-1 for details. Figure 4-7 Identifying SCSI Cable Connectors Chapter 4 67

60 Installing the RAID160 SA Controller Connecting the Cables and the StorageWorks Disk Enclosures Table 4-1 Cable Connector Descriptions (see Figure 3-2 above) Item Description 1 External 68-pin Wide 2 External offset VHDCI 3 Internal 50-pin narrow (Internal connections are not supported on the RAID160 SA controller) 4 Internal 68-pin Wide (Internal connections are not supported on the RAID160 SA controller) Table 4-2 Supported External SCSI Cables for StorageWorks Enclosures Cable Type Length Option Kit Number Cable Assembly Number External Offset VHDCI to External Offset VHDCI External Offset VHDCI to External Offset VHDCI External Offset VHDCI to External Offset VHDCI External Offset VHDCI to External Offset VHDCI External Offset VHDCI to External Wide External Offset VHDCI to External Wide 1.8 m / 6 ft B m / 12 ft B m / 24 ft B m / 39 ft B m / 6 ft B m / 12 ft B Note: If additional cables are required, order by the option kit number. 68 Chapter 4

61 Installing the RAID160 SA Controller Connecting the Cables and the StorageWorks Disk Enclosures NOTE IMPORTANT: Offset VHDCI cables must be used with the RAID160 SA controller. Early versions of the VHDCI cables do not accommodate side-by-side connection to the RAID160 SA controller. If your storage enclosure did not include the Offset VHDCI cables, you may need to order them. See Table 4-2 above, for part numbers. Up to four SCSI ports on the RAID160 SA controller are available for connection to external storage devices. 1. On the rear of the server, connect the cable to the VHDCI connector on the Smart Array controller, and then tighten the lock screws on the cable connector. 2. Attach the other end of the cable to the HP StorageWorks storage enclosure, and then tighten the lock screws on the cable connector. 3. Label the cables. See Labeling the Cables, below. 4. Replace the access panel and secure it with the thumbscrews, as required. CAUTION Do not operate the server with the access panel removed for extended periods of time. This precaution is to protect thermally sensitive components by ensuring the proper airflow through the server, and also to minimize personal contact with hazardous energy levels. In systems using external data storage, be sure that the server is the first unit powered down and the last unit to be powered back up. Doing this ensures that the system will not erroneously mark the drives as failed. Labeling the Cables If the cables connecting the RAID controllers and the disk enclosures are switched, data could be corrupted. HP strongly recommends that each cable is labeled to show the following information: The controller s slot number (this is stenciled on the system) The controller s channel number Chapter 4 69

62 Installing the RAID160 SA Controller Connecting the Cables and the StorageWorks Disk Enclosures The StorageWorks disk enclosure the cable connects to (if there are multiple disk enclosures) The SCSI bus connection ID on the I/O module in the StorageWorks disk enclosure: SCSI Bus A or SCSI Bus B 70 Chapter 4

63 Installing the RAID160 SA Controller Verifying the Installation Verifying the Installation After the system reboots, verify that the installation was successful by following these steps: Step 1. Issue the swlist command: swlist If the RAID160 SA controller is installed correctly, the generated output will look similar to this: # swlist # Initializing... # Contacting target "hpfcs681"... # # Target: hpfcs681:/ # # # Bundle(s): # B3899BA B HP C/ANSI C Developer s Bundle for HP-UX 11.i (S700) B3901BA B HP C/ANSI C Developer s Bundle for HP-UX 11.i (S800) B7609BA A Event Monitoring Service BUNDLE11i 11i, February 2001 B Required Patch Bundle for HP-UX Base-VXVM B Base VERITAS Volume Manager 3.2 for HP-UX CDE-English B English CDE Environment Chapter 4 71

64 Installing the RAID160 SA Controller Verifying the Installation FDDI-00 B PCI FDDI;Supptd HW=A3739A/A3739B;SW=J3626AA FibrChanl-00 B PCI/HSC FibreChannel;Supptd HW=A6684A,A6685A,A5158A,A6795A GOLDAPPS11i HP-UX 11i, June 2003 B Gold Applications Patches for GOLDBASE11i B Gold Base Patches for HP-UX 11i, June 2003 GigEther-00 B PCI/HSC GigEther;Supptd HW=A4926A/A4929A/A4924A/A4925A;SW=J1642AA GigEther-01 B PCI GigEther;Supptd HW=A6794A/A6825A/A6847A HPUX11i-OE B HP-UX 11i Operating Environment Component HPUXBase64 B HP-UX 64-bit Base OS HPUXBaseAux B HP-UX Base OS Auxiliary HWEnable11i HP-UX 11i, June 2003 OnlineDiag Jun 2003 B Hardware Enablement Patches for B HPUX Support Tools Bundle, RAID-00 B PCI RAID; Supptd HW=A5856A RAID-01 B %08 RAID160; Supptd HW=A7143A perl B C Perl Programming Language # # Product(s) not contained in a Bundle: # BullseyeCover HP-UX 11 LIF-LOAD B HP LIF LOAD Tools The RAID-01 bundle is highlighted for emphasis. 72 Chapter 4

65 Installing the RAID160 SA Controller Verifying the Installation Step 2. Issue the ioscan -kfn grep ciss command: # ioscan -kfn grep ciss ioscan -kfn grep ciss If the RAID160 SA controller software is installed correctly, the generated output will look similar to this: ext_bus 6 0/6/2/0 ciss CLAIMED INTERFACE PCI 4-Channel RAID160 SA SCSI controller (A7143A) /dev/ciss6 If the software is not installed correctly, re-install it using swinstall (see Installing Software for the RAID160 SA Controller on page 53). Chapter 4 73

66 Installing the RAID160 SA Controller RAID160 SA Controller Firmware RAID160 SA Controller Firmware The sautil command is used to confirm and update the firmware version that is currently installed on the RAID160 SA controller. HP recommends that the latest firmware version be installed. NOTE This section of the RAID160 Support Guide focuses on the sautil command options that are used to confirm, or change, RAID160 SA controller firmware. The other sautil command options listed in the sautil help screen and detailed in the sautil manpages, are explained in The sautil Command on page 115. You will need a superuser user ID to run the sautil command. By issuing the sautil command without any options, the sautil help screen with command options and syntax will be displayed: # sautil ****************************************************************************** **** **** **** S A U T I L S u p p o r t U t i l i t y **** **** **** **** for the HP A7143A RAID160 SA SCSI Adapter **** **** **** **** version A **** **** **** **** (c) Copyright 2003 Hewlett-Packard Development Company, L.P. **** ****************************************************************************** 74 Chapter 4

67 Installing the RAID160 SA Controller RAID160 SA Controller Firmware Usage: sautil <device_file> [-s] <device_file> download_hba_fw <fw_image> <device_file> download_dev_fw <fw_image> <ch>:<id> <device_file> reset_adapter <device_file> start_recovery <device_file> stat <device_file> clear_stat <device_file> get_trace_buf <device_file> get_fw_err_log <device_file> accept_media_xchg <logical_drive_number> run_startup_script where "<device_file>" is the adapter s device file, e.g., /dev/ciss5 "-s" (optional) displays a shorter output "<fw_image>" is the firmware image file to download "<ch>:<id>" is the physical disk to update, e.g., 4:12 Notes: - This utility requires superuser privilege. - See the sautil man page for tool details. # Before running the sautil command to confirm or update the controller firmware, you will need to know the device file for the RAID160 SA controller. Chapter 4 75

68 Installing the RAID160 SA Controller RAID160 SA Controller Firmware Determining the RAID160 SA Device File The device file for the RAID160 SA controller can be determined from the output of the ioscan -kfn command. An example of a portion of the ioscan -kfn output listing the RAID160 SA device file follows: # ioscan -kfn Class I H/W Path Driver S/W State H/W Type Description ============================================================================= root 0 root CLAIMED BUS_NEXUS ioa 0 0 sba CLAIMED BUS_NEXUS System Bus Adapter (582) ba 0 0/0 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782) lan 0 0/0/0/0 btlan CLAIMED INTERFACE HP PCI 10/100Base-TX Core /dev/diag/lan0 /dev/ether0 /dev/lan0 target 2 0/0/1/1.15 tgt CLAIMED DEVICE disk 0 0/0/1/ sdisk CLAIMED DEVICE HP 73.4GMAN3735MC /dev/dsk/c1t15d0 /dev/rdsk/c1t15d0 ext_bus 6 0/6/0/0 ciss CLAIMED INTERFACE PCI 4-Channel RAID160 SA SCSI Adapter (A7143A) /dev/ciss6 target 7 0/6/0/0.0 tgt NO_HW DEVICE target 8 0/6/0/0.7 tgt CLAIMED DEVICE The device file for the RAID160 SA controller in the example above is /dev/ciss6. Determining the RAID160 SA Firmware Version The firmware version that is in the ROM on the RAID160 SA controller can be determined by using either the sautil <device_file> command (extensive output), or the sautil <device_file> -s command (shortened output). 76 Chapter 4

69 Installing the RAID160 SA Controller RAID160 SA Controller Firmware An example of the lengthy sautil <device_file> command output is provided in The sautil Command on page 115 in the Troubleshooting chapter. Issuing the sautil <device_file> -s command provides an abbreviated listing of information for the RAID160 SA controller and all connected devices, including the firmware version currently in ROM. # sautil /dev/ciss6 -s ****************************************************************************** **** **** **** S A U T I L S u p p o r t U t i l i t y **** **** **** **** for the HP A7143A RAID160 SA SCSI Adapter **** **** **** **** version A **** **** **** **** (c) Copyright 2003 Hewlett-Packard Development Company, L.P. **** ****************************************************************************** ---- DRIVER INFORMATION Driver State... READY ---- ADAPTER INFORMATION Adapter... HP A7143A RAID160 SA SCSI Adapter Chapter 4 77

70 Installing the RAID160 SA Controller RAID160 SA Controller Firmware Hardware Path... 0/6/0/0 Serial Number... P2313ADDAOVCDK Device File... /dev/ciss6 Hardware Revision... A Firmware Revision (in ROM) # of Logical Drives... 1 # of Physical Disks Configured... 4 # of Physical Disks Detected ARRAY ACCELERATOR (CACHE) INFORMATION Array Accelerator Board Present?... yes Cache Configuration Status... cache enabled Cache Ratio... 50% Read / 50% Write Total Cache Size (MB) Battery Pack Count... 2 Battery Status (pack #1)... ok Battery Status (pack #2)... ok ---- LOGICAL DRIVE SUMMARY # RAID Size Status MB OK 78 Chapter 4

71 Installing the RAID160 SA Controller RAID160 SA Controller Firmware ---- SCSI DEVICE SUMMARY Ch ID Type Capacity Status 1 0 DISK 18.2 GB OK 1 1 DISK 18.2 GB OK 1 2 DISK 18.2 GB SPARE 1 3 DISK 18.2 GB SPARE 1 7 PROCESSOR N/A N/A ---- SCSI DEVICE 1: Channel Number... 1 SCSI ID... 0 Device Type... DISK Disk Capacity GB Device Status... OK Device Vendor ID... COMPAQ Device Product ID... BD A Device Serial Number... UFL0P14000K90117 Device Firmware Version... B016 SCSI Transfer Rate... Ultra SCSI DEVICE 1: Channel Number... 1 SCSI ID... 1 Device Type... DISK Chapter 4 79

72 Installing the RAID160 SA Controller RAID160 SA Controller Firmware Disk Capacity GB Device Status... OK Device Vendor ID... COMPAQ Device Product ID... BD A Device Serial Number... UFL0P14000KG0117 Device Firmware Version... B016 SCSI Transfer Rate... Ultra SCSI DEVICE 1: Channel Number... 1 SCSI ID... 2 Device Type... DISK Disk Capacity GB Device Status... SPARE Device Vendor ID... COMPAQ Device Product ID... BD A Device Serial Number... UFL0P140008V0117 Device Firmware Version... B016 SCSI Transfer Rate... Ultra SCSI DEVICE 1: Channel Number... 1 SCSI ID... 3 Device Type... DISK Disk Capacity GB Device Status... SPARE 80 Chapter 4

73 Installing the RAID160 SA Controller RAID160 SA Controller Firmware Device Vendor ID... COMPAQ Device Product ID... BD Device Serial Number Device Firmware Version... B20B SCSI Transfer Rate... Ultra SCSI DEVICE 1: Channel Number... 1 SCSI ID... 7 Device Type... PROCESSOR Device Vendor ID... COMPAQ Device Product ID... PROLIANT 4LEE Chapter 4 81

74 Installing the RAID160 SA Controller RAID160 SA Controller Firmware ---- DIAGRAM OF EXTERNAL CONNECTORS ON BRACKET ========---======== ULTRA-3 <--- LOOK FOR THIS LOGO / \ <- \ / * * * * * * (Ch 1)---> * * * * <--- (Ch 2) * * * * * * * * * * * * (Ch 3)---> * * * * <--- (Ch 4) * * * * * * ~ ~ ~ ~ ~ ****************************************************************************** **** End of SAUTIL Output **** ****************************************************************************** The firmware version that is in the ROM on the RAID160 SA controller (/dev/ciss6), is version Chapter 4

75 Installing the RAID160 SA Controller RAID160 SA Controller Firmware Updating the RAID160 SA Firmware The sautil command syntax for updating RAID160 SA controller firmware is: sautil <device_file> download_hba_fw <fw_image> where: <device_file> is the controller device file. The device file for the RAID160 controller can be determined by running the ioscan -kfn command as illustrated in Determining the RAID160 SA Device File on page 76. <fw_image> is the file path for the firmware version you want to install on the RAID160 SA controller. The file path for the latest RAID160 SA controller firmware file can be found in the /opt/raidsa/bin/ directory in the SW depot download bundle. See Installing Software for the RAID160 SA Controller on page 53, for the complete file path. When the sautil <device_file> download_hba_fw <fw_image> command is issued, the firmware version that is currently installed will be listed along with the firmware version you selected to replace it with. You will have the opportunity to proceed with the download or cancel: # sautil /dev/ciss6 download_hba_fw /opt/raidsa/bin/maxwell332.bin ****************************************************************************** **** **** **** S A U T I L S u p p o r t U t i l i t y **** **** **** **** for the HP A7143A RAID160 SA SCSI Adapter **** **** **** **** version A **** **** **** **** (c) Copyright 2003 Hewlett-Packard Development Company, L.P. **** ****************************************************************************** Chapter 4 83

76 Installing the RAID160 SA Controller RAID160 SA Controller Firmware ---- DRIVER INFORMATION Driver State... READY ---- ADAPTER INFORMATION Adapter... HP A7143A RAID160 SA SCSI controller Hardware Path... 0/6/2/0 Device File... /dev/ciss FIRMWARE DOWNLOAD ** You are downloading the firmware image "/opt/raidsa/bin/maxwell332.bin" ** to the adapter "/dev/ciss6". Retrieving firmware image file from disk... [Done] Validating the file s signature and size... [Done] Retrieving the firmware revision string from ROM... [Done] Retrieving the firmware revision string from the file... [Done] Current Revision (in ROM) New Revision (in file) WARNING: All I/O to this controller will be temporarily halted while the firmware is being updated. 84 Chapter 4

77 Installing the RAID160 SA Controller RAID160 SA Controller Firmware Do you want to continue (y/n)? Preparing for download (this could take up to 2 minutes)...[done] Sending the new firmware to the adapter...[done] Activating the new firmware...[done] Resetting the adapter (this could take up to 2 minutes)...[done] Retrieving the firmware revision string from ROM...[Done] Current Revision (in ROM) FIRMWARE DOWNLOAD WAS SUCCESSFUL! ****************************************************************************** **** End of SAUTIL Output **** ****************************************************************************** Chapter 4 85

78 Installing the RAID160 SA Controller Physical Disk Firmware Physical Disk Firmware The sautil command is used to confirm and update the firmware version on each of the physical disks in the SmartArray disk enclosure that the RAID160 SA controller is attached to. NOTE This section of the RAID160 Support Guide focuses on the sautil command options that are used to confirm, or change, physical disk firmware. The other sautil command options listed in the sautil help screen and detailed in the sautil manpages, are explained in The sautil Command on page 115. # sautil You will need a superuser user ID to run the sautil command. By issuing the sautil command without any options, the sautil help screen with command options and syntax will be displayed: ****************************************************************************** **** **** **** S A U T I L S u p p o r t U t i l i t y **** **** **** **** for the HP A7143A RAID160 SA SCSI Adapter **** **** **** **** version A **** **** **** **** (c) Copyright 2003 Hewlett-Packard Development Company, L.P. **** ****************************************************************************** Usage: sautil <device_file> [-s] <device_file> download_hba_fw <fw_image> <device_file> download_dev_fw <fw_image> <ch>:<id> 86 Chapter 4

79 Installing the RAID160 SA Controller Physical Disk Firmware <device_file> reset_adapter <device_file> start_recovery <device_file> stat <device_file> clear_stat <device_file> get_trace_buf <device_file> get_fw_err_log <device_file> accept_media_xchg <logical_drive_number> run_startup_script where "<device_file>" is the adapter s device file, e.g., /dev/ciss5 "-s" (optional) displays a shorter output "<fw_image>" is the firmware image file to download "<ch>:<id>" is the physical disk to update, e.g., 4:12 Notes: - This utility requires superuser privilege. - See the sautil man page for tool details. # Before running the sautil command to confirm or update physical disk firmware, you will need to know the device file for the RAID160 SA controller as well as the SCSI channel and SCSI ID for each of the physical disks attached to the RAID160 SA controller. Determining the RAID160 SA Device File The device file for the RAID160 SA controller can be determined from the output of the ioscan -kfn command. An example of a portion of the ioscan -kfn output listing the RAID160 SA device file follows: Chapter 4 87

80 Installing the RAID160 SA Controller Physical Disk Firmware # ioscan -kfn Class I H/W Path Driver S/W State H/W Type Description ============================================================================= root 0 root CLAIMED BUS_NEXUS ioa 0 0 sba CLAIMED BUS_NEXUS System Bus Adapter (582) ba 0 0/0 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782) lan 0 0/0/0/0 btlan CLAIMED INTERFACE HP PCI 10/100Base-TX Core /dev/diag/lan0 /dev/ether0 /dev/lan0 target 2 0/0/1/1.15 tgt CLAIMED DEVICE disk 0 0/0/1/ sdisk CLAIMED DEVICE HP 73.4GMAN3735MC /dev/dsk/c1t15d0 /dev/rdsk/c1t15d0 ext_bus 6 0/6/0/0 ciss CLAIMED INTERFACE PCI 4-Channel RAID160 SA SCSI Adapter (A7143A) /dev/ciss6 target 7 0/6/0/0.0 tgt NO_HW DEVICE target 8 0/6/0/0.7 tgt CLAIMED DEVICE The device file for the RAID160 SA controller in the example above is /dev/ciss6. Determining the SCSI Channel, the SCSI ID, and the Firmware Version for Physical Disks The SCSI channel, SCSI ID, and the firmware version that is installed on each of the physical disks attached to the RAID160 SA controller can be determined by using either the sautil <device_file> command (extensive output), or the sautil <device_file> -s command (shortened output). An example of the lengthy sautil <device_file> command output is provided in The sautil Command on page 115 in the Troubleshooting chapter. 88 Chapter 4

81 Installing the RAID160 SA Controller Physical Disk Firmware Issuing the sautil <device_file> -s command provides an abbreviated listing of information for the RAID160 SA controller and all connected devices including a SCSI Device Summary that lists the SCSI channel and the SCSI ID for each of the physical disks attached to the RAID160 SA controller. The firmware version currently installed on each physical disk is also included in the output of the sautil <device_file> -s command: # sautil /dev/ciss6 -s ****************************************************************************** **** **** **** S A U T I L S u p p o r t U t i l i t y **** **** **** **** for the HP A7143A RAID160 SA SCSI Adapter **** **** **** **** version A **** **** **** **** (c) Copyright 2003 Hewlett-Packard Development Company, L.P. **** ****************************************************************************** ---- DRIVER INFORMATION Driver State... READY ---- ADAPTER INFORMATION Adapter... HP A7143A RAID160 SA SCSI Adapter Chapter 4 89

82 Installing the RAID160 SA Controller Physical Disk Firmware Hardware Path... 0/6/0/0 Serial Number... P2313ADDAOVCDK Device File... /dev/ciss6 Hardware Revision... A Firmware Revision (in ROM) # of Logical Drives... 1 # of Physical Disks Configured... 4 # of Physical Disks Detected ARRAY ACCELERATOR (CACHE) INFORMATION Array Accelerator Board Present?... yes Cache Configuration Status... cache enabled Cache Ratio... 50% Read / 50% Write Total Cache Size (MB) Battery Pack Count... 2 Battery Status (pack #1)... ok Battery Status (pack #2)... ok ---- LOGICAL DRIVE SUMMARY # RAID Size Status MB OK 90 Chapter 4

83 Installing the RAID160 SA Controller Physical Disk Firmware ---- SCSI DEVICE SUMMARY Ch ID Type Capacity Status 1 0 DISK 18.2 GB OK 1 1 DISK 18.2 GB OK 1 2 DISK 18.2 GB SPARE 1 3 DISK 18.2 GB SPARE 1 7 PROCESSOR N/A N/A ---- SCSI DEVICE 1: Channel Number... 1 SCSI ID... 0 Device Type... DISK Disk Capacity GB Device Status... OK Device Vendor ID... COMPAQ Device Product ID... BD A Device Serial Number... UFL0P14000K90117 Device Firmware Version... HPB3 SCSI Transfer Rate... Ultra SCSI DEVICE 1: Channel Number... 1 SCSI ID... 1 Device Type... DISK Chapter 4 91

84 Installing the RAID160 SA Controller Physical Disk Firmware Disk Capacity GB Device Status... OK Device Vendor ID... COMPAQ Device Product ID... BD A Device Serial Number... UFL0P14000KG0117 Device Firmware Version... HPB3 SCSI Transfer Rate... Ultra SCSI DEVICE 1: Channel Number... 1 SCSI ID... 2 Device Type... DISK Disk Capacity GB Device Status... SPARE Device Vendor ID... COMPAQ Device Product ID... BD A Device Serial Number... UFL0P140008V0117 Device Firmware Version... HPB3 SCSI Transfer Rate... Ultra SCSI DEVICE 1: Channel Number... 1 SCSI ID... 3 Device Type... DISK Disk Capacity GB Device Status... SPARE 92 Chapter 4

85 Installing the RAID160 SA Controller Physical Disk Firmware Device Vendor ID... COMPAQ Device Product ID... BD Device Serial Number Device Firmware Version... HPB3 SCSI Transfer Rate... Ultra SCSI DEVICE 1: Channel Number... 1 SCSI ID... 7 Device Type... PROCESSOR Device Vendor ID... COMPAQ Device Product ID... PROLIANT 4LEE ---- DIAGRAM OF EXTERNAL CONNECTORS ON BRACKET ========---======== ULTRA-3 <--- LOOK FOR THIS LOGO / \ <- \ / * * * * * * (Ch 1)---> * * * * <--- (Ch 2) * * * * * * Chapter 4 93

86 Installing the RAID160 SA Controller Physical Disk Firmware * * * * * * (Ch 3)---> * * * * <--- (Ch 4) * * * * * * ~ ~ ~ ~ ~ ****************************************************************************** **** End of SAUTIL Output **** ****************************************************************************** In the example above, the SCSI Device Summary lists the SCSI channel and the SCSI ID for each of the physical disks attached to the RAID160 SA controller. The information provided for each of the physical disks, following the SCSI Device Summary, indicates that all of the physical disks have firmware version HPB3 installed. Updating Physical Disk Firmware The sautil physical disk firmware update command syntax is: sautil <device_file> download_dev_fw <fw_image> <ch>:<id> where: <device_file> is the controller device file. The RAID160 SA controller device file can be determined by issuing the ioscan -kfn command as illustrated in Determining the RAID160 SA Device File on page 87. <fw_image> is the file path for the firmware version you want to install on the RAID160 SA controller. You will need to contact your HP representative for access to the physical disk firmware image update file. 94 Chapter 4

87 Installing the RAID160 SA Controller Physical Disk Firmware <ch>:<id> is the SCSI channel and the SCSI ID of the physical disk you want to change the firmware on. The SCSI channel and the SCSI ID for each physical disk connected to the RAID160 SA controller can be determined from the SCSI Device Summary contained in the output of the sautil <device_file> command or the sautil <device_file> -s command as illustrated in Determining the SCSI Channel, the SCSI ID, and the Firmware Version for Physical Disks on page 88. When the sautil <device_file> download_dev_fw <fw_image> <pdev_id> command is issued, the physical disk firmware version that is currently installed will be listed along with the firmware version you selected to replace it with. You will have the opportunity to proceed with the download or cancel: NOTE This procedure will need to be repeated for each physical disk that you want to update the firmware on. # sautil /dev/ciss6 download_dev_fw HPB4d849.lod 1:0 ****************************************************************************** **** **** **** S A U T I L S u p p o r t U t i l i t y **** **** **** **** for the HP A7143A RAID160 SA SCSI Adapter **** **** **** **** version A **** **** **** **** (c) Copyright 2003 Hewlett-Packard Development Company, L.P. **** ****************************************************************************** Chapter 4 95

88 Installing the RAID160 SA Controller Physical Disk Firmware ---- DRIVER INFORMATION Driver State... READY ---- ADAPTER INFORMATION Adapter... HP A7143A RAID160 SA SCSI controller Hardware Path... 0/6/2/0 Device File... /dev/ciss FIRMWARE DOWNLOAD ** You are downloading the firmware image "HPB4d849.lod" ** to the physical disk "1:0" (channel:id) ** connected to the controller "/dev/ciss6". Verifying that the specified target disk is valid... [Done] Retrieving firmware image file from disk... [Done] Retrieving the firmware revision string from ROM... [Done] Current Revision (in ROM)... HPB3 WARNING: All I/O to this controller will be temporarily halted while the firmware is being updated. Do you want to continue (y/n)? 96 Chapter 4

89 Installing the RAID160 SA Controller Physical Disk Firmware Preparing for download (this could take up to 2 minutes)... [Done] Sending the new firmware to the disk... [Done] Resetting the adapter (this could take up to 2 minutes)... [Done] Retrieving the firmware revision string from ROM... [Done] Current Revision (in ROM)... HPB4 FIRMWARE DOWNLOAD WAS SUCCESSFUL! ****************************************************************************** **** End of SAUTIL Output **** ****************************************************************************** Chapter 4 97

90 Installing the RAID160 SA Controller Setting up a RAID160 SA Controller As a Boot Device Setting up a RAID160 SA Controller As a Boot Device The RAID160 SA controller can be set up as a boot device. To do this, you actually set up a logical drive on the controller as a boot device. On each RAID160 SA controller, any number of its logical drives can be set up as boot devices. For example, if you have two controllers in a system, and each controller has three logical drives configured on it, you could set up two logical drives on one controller as boot devices, and all three logical drives on the other controller as boot devices, giving you a total of five boot devices. Considerations Things to consider before you set up a RAID160 SA controller as a boot device: While you are using a RAID160 SA logical drive as a boot device (that is, while HP-UX is running on it), you are limited in the configuration tasks you can perform with the saconfig configuration utility. This is because saconfig sees the logical drive as being in use, so any kind of configuration changes affecting that drive are not allowed until you are no longer using it as the boot device. When you are not using a logical drive as a boot device, if you clear the controller s configuration, that logical drive will also be deleted. If you still want a logical drive to be set up as a boot device, you will need to configure a logical drive and then complete the entire boot setup process again. If you have trouble accessing your RAID boot data, only limited troubleshooting tools are available. HP recommends booting from an alternative boot media and using STM and sautil online tools. See Chapter 6 of the HP A7143A RAID160 Support Guide, for more information. Dependencies The following dependencies must be met before a RAID160 SA controller can be set up as a boot device: 98 Chapter 4

91 Installing the RAID160 SA Controller Setting up a RAID160 SA Controller As a Boot Device You must have the correct version of the product dependent code (PDC) installed. See the HP A7143A RAID160 SA Release Notes for information on the PDC versions needed for each of the supported HP-UX systems. If you do not have the correct PDC version, contact your HP representative. The RAID160 SA controller can only be connected to external disks. The internal SCSI connections cannot be used. You must have RAID160 SA controller firmware version 3.32 or later installed. HP strongly recommends having an alternate boot device available (for example, a disk that is not controlled by the RAID160 SA controller). Installing HP-UX on a Logical Drive To set up a RAID160 SA controller as a boot device, you must install HP-UX on one of the controller s logical drives. Follow this procedure: Step 1. Start Ignite-UX from the HP-UX 11i version 1 Core OS Install and Recovery Media for September The Ignite-UX Welcome screen displays: Welcome to Ignite-UX! Use the <tab> key to navigate between fields, and the arrow keys within fields. Use the <return/enter> key to select an item. Use the <return/enter> or <space-bar> to pop-up a choices list. If the menus are not clear, select the "Help" item for more information. Hardware Summary: System Model: 9000/800/A500-5X Chapter 4 99

92 Installing the RAID160 SA Controller Setting up a RAID160 SA Controller As a Boot Device [ Scan Again ] Disks: 3 (204.6GB) Floppies: 0 LAN cards: 1 CD/DVDs: 0 Tapes: 0 Memory: 4096Mb Graphics Ports: 0 IO Buses: 7 CPUs: 1 [ H/W Details ] [ Install HP-UX ] [ Run a Recovery Shell ] [ Advanced Options ] [ Reboot ] [ Help ] Step 2. Select Run a Recovery Shell. The Recovery Shell screen displays: NOTE: Creating the second RAM disc and mounting on /dev... * Generating device file for the second ramdisc... * Loading mkfs to make a file system... version 4 layout sectors, blocks of size 1024, log size 1024 blocks unlimited inodes, largefiles not supported data blocks, free data blocks 1 allocation units of blocks, data blocks last allocation unit has data blocks * Loading mount to mount/dev/ram1 file system... * Mounting /dev/ram1 file system succeeded! * Copying /dev.old files back to /dev succeeds! * Loading insf to create disk device files... * Creating disk device files... * Loading in a shell Chapter 4

93 Installing the RAID160 SA Controller Setting up a RAID160 SA Controller As a Boot Device NOTE: Pushing a shell, you will have to use "reboot" to reboot the system when done. Use the "loadfile" command to bring in more commands as you need them. # Step 3. At the recovery shell prompt, enter: loadfile -l INSTCMDS/opt/raidsa/bin/ciss_insf # loadfile -l INSTCMDS /opt/raidsa/bin/ciss_insf # Step 4. At the next prompt, enter: # /opt/raidsa/bin/ciss_insf /opt/raidsa/bin/ciss_insf and verify that the device file for the RAID160 SA controller has been created. Installing special file for RAID160 instance 5 /dev/ciss5 installed # Step 5. At the prompt enter: loadfile -l INSTCMDS /opt/raidsa/bin/saconfig # loadfile -l INSTCMDS /opt/raidsa/bin/saconfig # Step 6. Now configure the array(s) and logical drive(s) following the instructions for the saconfig configuration utility. Step 7. Once the logical drive(s) and array(s) have been configured, exit the recovery shell by entering reboot at the prompt. The system will reboot and you will be returned to the Boot Console Handler (BCH) prompt. Step 8. At the BCH prompt, start Ignite-UX from the HP-UX 11i version 1 Core OS Install and Recovery Media for September The Ignite-UX Welcome screen displays (see Step 1). Step 9. Select Install HP-UX. Chapter 4 101

94 Installing the RAID160 SA Controller Setting up a RAID160 SA Controller As a Boot Device Step 10. Select the kind of installation (Guided or Advanced) you want to do. The installation starts, and the Ignite-UX graphical interface (GUI) appears. Step 11. Under the Basic tab, select the configuration to use according to the HP-UX system you are using. Step 12. Still under the Basic tab, for the root disk for the installation, select the RAID160 SA logical drive you want to install the HP-UX operating system on. Step 13. Continue with (and finish) the installation as usual. Step 14. Once the installation has completed, you can boot from that RAID160 SA logical drive. 102 Chapter 4

95 5 Configuring the RAID160 SA Controller This chapter contains the following sections detailing the use of the saconfig command to configure the RAID160 SA controller: Chapter 5 103

96 Configuring the RAID160 SA Controller Planning the RAID Configuration Planning the RAID Configuration If you don t already know exactly how you want to configure RAID on your system, consider the following steps. Step 1. Determine the RAID level you want to use for each logical drive (see Chapter 1 of the HP A7143A RAID160 Support Guide. Step 2. Draw the physical disk configuration. You should consider these things: Consider having one or more of your logical drives spread across controller channels. This would protect against a cable disconnection and distribute the I/O load across the channels. Consider using one or more online spare disk drives. A spare drive s capacity is not available unless the spare drive takes over for a failed physical disk, however, spare drives provide extra protection if there is a disk failure that is beyond the fault tolerance protection offered by the RAID configuration. Step 3. Choose a stripe size. In most cases, the default stripe size will provide the best performance. Use a smaller size only if you know your data will always be written in smaller blocks. For RAID 0, 1 and 1+0 the default stripe size is 128 KB. For RAID 5 and ADG, the default stripe size is 16 KB. Step 4. Determine the logical drive configuration, considering: Only logical drives can be accessed by HP-UX (physical drives cannot be accessed by HP-UX). Each logical drive is seen as a very large SCSI disk. Do not include physical drives of different capacities in the same logical drive. HP-UX sees the RAID160 SA logical drives as disks, so you can use the Logical Volume Manager (LVM) to configure them as physical volumes. Then, you can partition the drive into separate logical volumes. 104 Chapter 5

97 Configuring the RAID160 SA Controller saconfig Configuration CLI saconfig Configuration CLI The saconfig command is used to: Configure Logical Drives Set the RAID level Set the stripe size on a RAID Set up on-line spare disk drives Delete logical drives Clear the configuration You will need a superuser ID to run the saconfig command. By issuing the saconfig command without any options, the saconfig help screen with command options and syntax will be displayed: # saconfig No device file specified ****************************************************************************** **** **** **** S A C O N F I G U t i l i t y **** **** **** **** for the HP A7143A RAID160 SA SCSI Adapter **** **** **** **** version A **** **** **** **** (C) Copyright Hewlett-Packard Development Company, L.P. **** ****************************************************************************** Usage: To display configuration saconfig /dev/cissx To create logical drive saconfig /dev/cissx -R <RAID level> [-S <Stripe size (KB)>] -p <Channel:Target> [-p <Channel:Target>... ] [-s <Channel:Target>] Chapter 5 105

98 Configuring the RAID160 SA Controller saconfig Configuration CLI RAID level can be 0, 1, 1+0, 5, or ADG. For RAID 0, 1, and 1+0, stripe size can be 8, 16, 32, 64, 128, or 256 (default is 128). For RAID 5 and ADG, stripe size can be 8, 16, 32, or 64 (default is 16). Channel can be 1-4. Target can be To delete logical drive saconfig /dev/cissx -D <Logical drive #> To clear configuration saconfig /dev/cissx -D all To add spare drive to existing logical drive saconfig /dev/cissx -A <Logical drive #> -s <Channel:Target> To delete a spare drive of a logical drive saconfig /dev/cissx -D <Logical drive #> -s <Channel:Target> To delete all spare drives of a logical drive saconfig /dev/cissx -D <Logical drive #> -s all To change the rebuild priority for the logical drives saconfig /dev/cissx -r <rebuild_priority> To specify the percentage of total cache size to be used for read caching saconfig /dev/cissx -C <read_caching_percentage> Read caching percentage can be 0, 25, 50, 75, or 100. To enable or disable auto-fail missing disks at boot saconfig /dev/cissx -F on off 106 Chapter 5

99 Configuring the RAID160 SA Controller saconfig Configuration CLI Issue the man saconfig command to view the saconfig manpage for more details on the saconfig command. Before running the saconfig command to configure the storage devices connected to a RAID160 SA controller, you will need to know the device file for the RAID160 SA controller. Determining the RAID160 SA Device File The device file for the RAID160 SA controller can be determined from the output of the ioscan -kfn command. An example of a portion of the ioscan -kfn output listing the RAID160 SA device file follows: # ioscan -kfn Class I H/W Path Driver S/W State H/W Type Description ============================================================================= root 0 root CLAIMED BUS_NEXUS ioa 0 0 sba CLAIMED BUS_NEXUS System Bus Adapter (582) ba 0 0/0 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782) lan 0 0/0/0/0 btlan CLAIMED INTERFACE HP PCI 10/100Base-TX Core /dev/diag/lan0 /dev/ether0 /dev/lan0 target 2 0/0/1/1.15 tgt CLAIMED DEVICE disk 0 0/0/1/ sdisk CLAIMED DEVICE HP 73.4GMAN3735MC /dev/dsk/c1t15d0 /dev/rdsk/c1t15d0 ext_bus 6 0/6/0/0 ciss CLAIMED INTERFACE PCI 4-Channel RAID160 SA SCSI Adapter (A7143A) /dev/ciss6 target 7 0/6/0/0.0 tgt NO_HW DEVICE target 8 0/6/0/0.7 tgt CLAIMED DEVICE The device file for the RAID160 SA controller in the example above is /dev/ciss6. Displaying the RAID160 SA Configuration To display the physical disks connected to a RAID160 SA controller, as well as any logical drives and spare drives that have been configured, issue the saconfig <dev_file> command, where <dev_file> represents the device file for the RAID160 SA controller. Chapter 5 107

100 Configuring the RAID160 SA Controller saconfig Configuration CLI # saconfig /dev/ciss6 The channel, SCSI ID, size, and status of each physical disk attached to the RAID160 SA controller is included in the saconfig <dev_file> output. If any logical drives have been configured on the RAID160 SA controller, a detailed description of each logical drive that has been configured will also be displayed: ******************** RAID160 Controller /dev/ciss6 ******************** PHYSICAL DRIVES Ch ID Size Status GB UNASSIGNED GB UNASSIGNED GB UNASSIGNED GB UNASSIGNED In the example above, there are 4 physical disks attached to the RAID160 SA controller (/dev/ciss6). No logical drive has been configured. Adding a Spare Disk Drive The saconfig /dev/cissx -A <Logical drive #> -s <Channel:Target> command is used to add a spare physical disk to an existing logical drive: # saconfig /dev/ciss7 -A 0 -s 1:3 Spare drive 1:3 added to Logical drive 0 You can add multiple spare physical disks to a logical drive, depending on the number of physical disks in the array that are not in use. Deleting a Spare Disk Drive The saconfig /dev/cissx -D <Logical Drive #> -s <Channel:Target> command is used to delete a spare physical disk from an existing logical drive: # saconfig /dev/ciss7 -D 0 -s 1:3 Spare drive 1:3 deleted from Logical drive 0 You can delete all the spare drives of logical drive 0 at once with the following command 108 Chapter 5

101 Configuring the RAID160 SA Controller saconfig Configuration CLI # saconfig /dev/ciss7 -D 0 -s all All spare drives are deleted from logical drive 0 Change the Rebuild Priority of a Logical Drive The saconfig /dev/cissx -r <low medium high> command is used to set the rebuild priority of logical dries unders cissx controller For example, if the rebuild priority needs to be set to high for the logical drives under controller ciss7 use the command # saconfig /dev/ciss7 -r high Specify Percentage of Cache Used for Read Caching The saconfig /dev/cissx -C <read_caching_percentage> command is used to specify a percentage of cache to be used exclusively for read caching. The <read_caching_percentage> can be: 0, 25, 50, 75, or 100 percent of the cache. # saconfig /dev/ciss7 -C 100 Read cache percentage changed to 100% Auto-Fail Missing Disks At Boot The saconfig /dev/cissx -F on off command is used to enable or disable auto-fail of missing disks at boot: # saconfig /dev/ciss7 -F on Auto-fail missing disks enabled Clear the Configuration The saconfig <dev_file> -D all command is used to clear all of the logical drives that have been configured from the physical disks attached to a RAID160 SA controller: # saconfig /dev/ciss6 -D all Are you sure you want to clear configuration on RAID160 SA controller /dev/ciss6? (y/[n]): y Logical drive 0 deleted Configuration cleared Chapter 5 109

102 Configuring the RAID160 SA Controller saconfig Configuration CLI WARNING All of the data on the logical drives and the physical disks connected to the specified RAID160 SA controller will be lost when the saconfig -D all command is issued. 110 Chapter 5

103 6 Troubleshooting This chapter contains the following sections providing troubleshooting options available for the RAID160 SA controller: Chapter 6 111

104 Troubleshooting HP Support Tools Manager (STM) HP Support Tools Manager (STM) STM is a software application that can be run from the console to obtain status and descriptive information about the RAID160 SA controller. STM can also be used to diagnose problems. STM version A.42.00, or later, must be used with the RAID160 SA controller. For detailed information on STM, go to click on Browse by Topic, then click on Diagnostics. 112 Chapter 6

105 Troubleshooting Event Monitoring Service (EMS) Event Monitoring Service (EMS) Event Monitoring Service (EMS) notifies a system administrator when an event occurs on the system. A hardware event monitor monitors the hardware for unusual behavior (known as an event) and sends a message to the Event Monitoring Service, which notifies the system administrator of the event, along with suggestions for correcting the problem. This service is available for the RAID160 SA controller. For detailed information on how hardware monitors work, go to click on Browse by topic then go to the Diagnostics section to locate EMS information. Chapter 6 113

106 Troubleshooting ODE ODE The RAID160 SA controller supports HP s Offline Diagnostics Environment (ODE). ODE is an offline support tools platform for troubleshooting systems that are running without an operating system or systems that cannot be tested using online tools. The offline environment is also useful for testing that needs to be done before a system is booted. ODE provides a user-friendly interface for diagnostics and utilities that have been developed to run in this environment. The Offline Diagnostics Environment has a distributed architecture consisting of several modules. Each module has a specific function and uses well defined protocols to communicate with the other modules. The user chooses between a command line interface, or a menu-driven interface. The command line interface allows the user to select specific tests and/or utilities to execute on a specific hardware module. The menu-driven interface allows the user to specify the hardware module to be tested, then ODE selects the appropriate tests to execute on the module. The Offline Diagnostic Environment consists of: A Test Controller - which acts as the user interface and launches the execution of the Test Modules. Test Modules - which consist of diagnostic or utility programs designed to execute within ODE. These modules exercise or diagnose user specified hardware units. A System Library (SysLib) - which consists of a set of common routines for use by both the Test Controller and the Test Modules. These routines perform I/O, string parsing, and system control. For detailed information about ODE and how to use it: 1. Go to 2. Click on Browse by Topic 3. Click on Diagnostics 4. Click on Offline Diagnostics 114 Chapter 6

107 Troubleshooting The sautil Command The sautil Command Troubleshooting with sautil NOTE Before troubleshooting with the sautil command, run STM. The diagnostic information STM provides will augment the information provided by the sautil command. See HP Support Tools Manager (STM) on page 112, for details. By issuing the sautil command without any options, the sautil help screen with command options and syntax, will be displayed: # sautil ****************************************************************************** **** **** **** S A U T I L S u p p o r t U t i l i t y **** **** **** **** for the HP A7143A RAID160 SA SCSI Adapter **** **** **** **** version A **** **** **** **** (c) Copyright 2003 Hewlett-Packard Development Company, L.P. **** ****************************************************************************** Usage: sautil <device_file> [-s] <device_file> download_hba_fw <fw_image> <device_file> download_dev_fw <fw_image> <ch>:<id> Chapter 6 115

108 Troubleshooting The sautil Command <device_file> reset_adapter <device_file> start_recovery <device_file> stat <device_file> clear_stat <device_file> get_trace_buf <device_file> get_fw_err_log <device_file> accept_media_xchg <logical_drive_number> run_startup_script where "<device_file>" is the adapter s device file, e.g., /dev/ciss5 "-s" (optional) displays a shorter output "<fw_image>" is the firmware image file to download "<ch>:<id>" is the physical disk to update, e.g., 4:12 Notes: - This utility requires superuser privilege. - See the sautil man page for tool details. This section of the RAID160 Support Guide focuses on sautil command options that are used for online troubleshooting of the RAID160 SA controller. The sautil command option that is used for updating RAID160 SA controller firmware (<device_file> download_hba_fw <fw_image>) is detailed in RAID160 SA Controller Firmware on page 74. The sautil command option that is used for updating physical disk firmware (<device_file> download_dev_fw <fw_image> <ch>:<id> ) is detailed in Physical Disk Firmware on page 86. The sautil <device_file> reset_adapter option resets the adapter. Some situations that may require an adapter reset include: 116 Chapter 6

109 Troubleshooting The sautil Command Online replacement of the RAID160 SA is performed, but the logical drives on the replacement controller are not detected A disk enclosure with an existing RAID configuration was hot - added and the logical drives on that enclosure are not detected The sautil <device_file> start_recovery option causes the RAID160 SA controller to start rebuilding any logical drives that are in READY FOR RECOVERY OPERATION state. All logical drives in this state will eventually transition to RECOVERING. Heavy I/O to the controller may delay this transition. There is no adverse impact, if this option is invoked when no logical drives are in READY FOR RECOVERY OPERATION state. The following sautil troubleshooting command options, which are included in the sautil help screen and detailed in the sautil manpages, are intended for HP support personnel. Detailed knowledge of the RAID160 SA driver and firmware is required to interpret the output: <device_file> stat <device_file> clear_stat <device_file> get_trace_buf <device_file> get_fw_err_log The sautil command options that will be useful for HP customers troubleshooting a RAID160 SA controller are: sautil <device_file> sautil <device_file> accept_media_xchg <logical_drive_number> run_startup_script Chapter 6 117

110 Troubleshooting The sautil Command sautil <device_file> The sautil <device_file> command output provides detailed information on the RAID 160 SA controller, any logical drives that have been configured, and all SCSI devices that are attached to the controller. There is a -s option for this command that provides a shorter and less detailed output. An example of the sautil <device_file> -s command output can be found in RAID160 SA Controller Firmware on page 74. For troubleshooting purposes the sautil <device_file> command, illustrated in the following example, is preferable...the Logical Drive Summary and the SCSI Device Summary, which have been highlighted for emphasis, are particularly useful for troubleshooting: # sautil /dev/ciss6 ****************************************************************************** **** **** **** S A U T I L S u p p o r t U t i l i t y **** **** **** **** for the HP A7143A RAID160 SA SCSI Adapter **** **** **** **** version A **** **** **** **** (c) Copyright 2003 Hewlett-Packard Development Company, L.P. **** ****************************************************************************** ---- DRIVER INFORMATION Driver State... READY ---- ADAPTER INFORMATION Adapter... HP A7143A RAID160 SA SCSI Adapter Hardware Path... 0/6/0/0 Serial Number... P2313ADDAOVCDK Device File... /dev/ciss6 Hardware Revision... A Boot Block Revision Firmware Revision (running) Firmware Revision (in ROM) Chapter 6

111 Troubleshooting The sautil Command Firmware Revision (inactive) # of Logical Drives... 1 # of Physical Disks Configured... 4 # of Physical Disks Detected... 4 Logical Drive Rebuild Priority (high) Array Capacity Expansion Priority... 0 (low) Auto-fail Missing Disks at Boot... enabled ---- ARRAY ACCELERATOR (CACHE) INFORMATION Array Accelerator Board Present?... yes Cache Configuration Status... cache enabled Cache Ratio... 50% Read / 50% Write Total Cache Size (MB) Read Cache Write Cache Transfer Buffer Battery Pack Count... 2 Battery Status (pack #1)... ok Battery Status (pack #2)... ok ---- LOGICAL DRIVE SUMMARY # RAID Size Status MB OK ---- SCSI DEVICE SUMMARY Ch ID Type Capacity Status 1 0 DISK 18.2 GB OK 1 1 DISK 18.2 GB OK 1 2 DISK 18.2 GB SPARE 1 3 DISK 18.2 GB SPARE 1 7 PROCESSOR N/A N/A ---- LOGICAL DRIVE Logical Device File... c6t0d0 Fault Tolerance Mode... RAID 1+0 (Disk Mirroring) Logical Drive Size MB Chapter 6 119

112 Troubleshooting The sautil Command Logical Drive Status... OK # of Participating Physical Disks... 2 Participating Physical Disk(s)... Ch:ID 1: 0 1: 1 Participating Spare Disk(s)... Ch:ID 1: 2 1: 3 Stripe Size KB Logical Drive Cache Status... cache enabled Configuration Signature... 0xA79C46BC Media Exchange Detected?... no ---- SCSI DEVICE 1: Channel Number... 1 SCSI ID... 0 Device Type... DISK Disk Capacity GB Device Status... OK Device Vendor ID... COMPAQ Device Product ID... BD A Device Serial Number... UFL0P14000K90117 Device Firmware Version... B016 SCSI Transfer Rate... Ultra 160 Reserved Area (cfg/status info) KB (0.6 MB) Block Size (bytes/sector) bytes HP Disk Stamped?... yes Last Failure Reason... none Physical Disk Flags: Disk present and operational... yes Non-disk device detected... no Wide SCSI transfer enabled... yes Synchronous (Fast/Ultra) transfer enabled... yes Narrow disk tray detected... no Wide transfer failed, reverted to narrow... no Ultra SCSI transfer enabled... yes Ultra-2 SCSI transfer enabled... yes S.M.A.R.T. supported... yes S.M.A.R.T. errors (in factory M&P data)... no 120 Chapter 6

113 Troubleshooting The sautil Command S.M.A.R.T. enabled... yes S.M.A.R.T. errors (in powerup M&P data)... no Attached to external channel... yes Configured in a logical drive... yes Configured as a spare disk... no Disk write cache enabled at spin up... no Running in DT clocking mode... yes Supports DT clocking mode only... no Supports DT and ST clocking modes... yes Running in U320 mode... no Packetized SCSI supported... no Supports redundant adapter operation... yes Disk write cache enabled in current page... no Disk write cache disabled in default page... yes QAS capable (U320 only)... no Currently running QAS (U320 only)... no ---- SCSI DEVICE 1: Channel Number... 1 SCSI ID... 1 Device Type... DISK Disk Capacity GB Device Status... OK Device Vendor ID... COMPAQ Device Product ID... BD A Device Serial Number... UFL0P14000KG0117 Device Firmware Version... B016 SCSI Transfer Rate... Ultra 160 Reserved Area (cfg/status info) KB (0.6 MB) Block Size (bytes/sector) bytes HP Disk Stamped?... yes Last Failure Reason... none Physical Disk Flags: Disk present and operational... yes Non-disk device detected... no Wide SCSI transfer enabled... yes Synchronous (Fast/Ultra) transfer enabled... yes Narrow disk tray detected... no Wide transfer failed, reverted to narrow... no Ultra SCSI transfer enabled... yes Chapter 6 121

114 Troubleshooting The sautil Command Ultra-2 SCSI transfer enabled... yes S.M.A.R.T. supported... yes S.M.A.R.T. errors (in factory M&P data)... no S.M.A.R.T. enabled... yes S.M.A.R.T. errors (in powerup M&P data)... no Attached to external channel... yes Configured in a logical drive... yes Configured as a spare disk... no Disk write cache enabled at spin up... no Running in DT clocking mode... yes Supports DT clocking mode only... no Supports DT and ST clocking modes... yes Running in U320 mode... no Packetized SCSI supported... no Supports redundant adapter operation... yes Disk write cache enabled in current page... no Disk write cache disabled in default page... yes QAS capable (U320 only)... no Currently running QAS (U320 only)... no ---- SCSI DEVICE 1: Channel Number... 1 SCSI ID... 2 Device Type... DISK Disk Capacity GB Device Status... SPARE Device Vendor ID... COMPAQ Device Product ID... BD A Device Serial Number... UFL0P140008V0117 Device Firmware Version... B016 SCSI Transfer Rate... Ultra 160 Reserved Area (cfg/status info) KB (0.6 MB) Block Size (bytes/sector) bytes HP Disk Stamped?... yes Last Failure Reason... none Physical Disk Flags: Disk present and operational... yes Non-disk device detected... no Wide SCSI transfer enabled... yes 122 Chapter 6

115 Troubleshooting The sautil Command Synchronous (Fast/Ultra) transfer enabled... yes Narrow disk tray detected... no Wide transfer failed, reverted to narrow... no Ultra SCSI transfer enabled... yes Ultra-2 SCSI transfer enabled... yes S.M.A.R.T. supported... yes S.M.A.R.T. errors (in factory M&P data)... no S.M.A.R.T. enabled... yes S.M.A.R.T. errors (in powerup M&P data)... no Attached to external channel... yes Configured in a logical drive... yes Configured as a spare disk... yes Disk write cache enabled at spin up... no Running in DT clocking mode... yes Supports DT clocking mode only... no Supports DT and ST clocking modes... yes Running in U320 mode... no Packetized SCSI supported... no Supports redundant adapter operation... yes Disk write cache enabled in current page... no Disk write cache disabled in default page... yes QAS capable (U320 only)... no Currently running QAS (U320 only)... no ---- SCSI DEVICE 1: Channel Number... 1 SCSI ID... 3 Device Type... DISK Disk Capacity GB Device Status... SPARE Device Vendor ID... COMPAQ Device Product ID... BD Device Serial Number Device Firmware Version... B20B SCSI Transfer Rate... Ultra 160 Reserved Area (cfg/status info) KB (0.6 MB) Block Size (bytes/sector) bytes HP Disk Stamped?... yes Last Failure Reason... none Chapter 6 123

116 Troubleshooting The sautil Command Physical Disk Flags: Disk present and operational... yes Non-disk device detected... no Wide SCSI transfer enabled... yes Synchronous (Fast/Ultra) transfer enabled... yes Narrow disk tray detected... no Wide transfer failed, reverted to narrow... no Ultra SCSI transfer enabled... yes Ultra-2 SCSI transfer enabled... yes S.M.A.R.T. supported... yes S.M.A.R.T. errors (in factory M&P data)... no S.M.A.R.T. enabled... yes S.M.A.R.T. errors (in powerup M&P data)... no Attached to external channel... yes Configured in a logical drive... yes Configured as a spare disk... yes Disk write cache enabled at spin up... no Running in DT clocking mode... yes Supports DT clocking mode only... no Supports DT and ST clocking modes... yes Running in U320 mode... no Packetized SCSI supported... no Supports redundant adapter operation... yes Disk write cache enabled in current page... no Disk write cache disabled in default page... yes QAS capable (U320 only)... no Currently running QAS (U320 only)... no ---- SCSI DEVICE 1: Channel Number... 1 SCSI ID... 7 Device Type... PROCESSOR Device Vendor ID... COMPAQ Device Product ID... PROLIANT 4LEE ---- DIAGRAM OF EXTERNAL CONNECTORS ON BRACKET ========---======== 124 Chapter 6

117 Troubleshooting The sautil Command ULTRA-3 <--- LOOK FOR THIS LOGO / \ <- \ / * * * * * * (Ch 1)---> * * * * <--- (Ch 2) * * * * * * * * * * * * (Ch 3)---> * * * * <--- (Ch 4) * * * * * * ~ ~ ~ ~ ~ ****************************************************************************** **** End of SAUTIL Output **** ****************************************************************************** # Logical Drive State Definitions The status column of the Logical Drive Summary in the sautil <device_file> command output example indicates the logical drive state. The logical drive state provides useful troubleshooting information. Refer to the following logical drive state definitions to interpret the logical drive status (the logical drive state definitions are also included in the sautil manpage). Logical Drive State Definitions: OK All physical disks in the logical drive are operational. FAILED Some possible causes: 1) Multiple physical disks in a fault-tolerant (RAID 1, Chapter 6 125

118 Troubleshooting The sautil Command 1+0, 5, ADG) logical drive have failed. 2) One or more disks in a RAID 0 logical drive have failed. 3) Cache data loss has occurred. 4) Array expansion was aborted. 5) The logical drive is temporarily disabled because another logical drive on the adapter had a missing disk at power-up. USING INTERIM RECOVERY MODE Also known as "degraded" state. A physical disk in a fault tolerant logical drive has failed. For RAID 1, 1+0 or 5, data loss may result if a second disk should fail. For RAID ADG, data loss may result if two additional disks should fail. READY FOR RECOVERY OPERATION A replacement disk is present, but rebuild hasn t started yet (another logical drive may be currently rebuilding). The logical drive will also return to this state if the rebuild had been aborted due to unrecoverable read errors from another disk. RECOVERING One or more physical disks in this logical drive are being rebuilt. WRONG PHYSICAL DISK WAS REPLACED While the logical drive was in a degraded state, the system was powered off and a disk other than the failed disk was replaced. Shut off the system and replace the 126 Chapter 6

119 Troubleshooting The sautil Command correct (failed) disk. PHYSICAL DISK(S) NOT PROPERLY CONNECTED While the system was off, one or more disks were removed. Note: the other logical drives are held in a temporary "failed" state when this occurs. EXPANDING The data in the logical drive is being reorganized because: 1) Physical disks have been added to the array (capacity expansion). 2) The stripe size is being changed (stripe-size migration). 3) The RAID level is being changed (RAID-level migration). NOT YET AVAILABLE A capacity expansion operation is in progress (or is queued up) that will make room on the disks for this new logical drive. Until room has been made on the physical disks, this newly configured logical drive cannot be read or written. QUEUED FOR EXPANSION The logical drive is waiting to undergo data reorganization (see EXPANDING above). Possible causes for the delay are a rebuild or expansion operation may already be in progress. Chapter 6 127

120 Troubleshooting The sautil Command Physical Disk State Definitions The status column of the SCSI Device Summary in the sautil <device_file> command output example also provides useful troubleshooting information. Refer to the following physical disk state definitions to interpret the status of physical disks (the physical disk state definitions are also included in the sautil manpage). Physical Disk State Definitions: OK The physical disk is configured in one or more logical drives and is operational. SPARE The physical disk is configured as a spare disk. UNASSIGNED The physical disk has not been configured in any logical drives. FAILED The configured physical disk has failed. 128 Chapter 6

121 Troubleshooting The sautil Command sautil <device_file> accept_media_xchg <logical_drive_number> The sautil <device_file> accept_media_xchg <logical_drive_number> command instructs the RAID160 SA controller to: 1. Set the state of the specified failed logical drive, <logical_drive_number>, to "OK" 2. Set the states of all failed physical disks that have been replaced via hot-plug exchanges to "OK" WARNING This option preserves the RAID configuration, logical drive configurations, and controller settings. If more disks failed than the RAID level is able to accommodate, data on the failed logical drive may have been compromised. If data has been compromised you will need to restore from backup media. In the following example, logical drive 0 accepts a media exchange: # sautil /dev/ciss6 accept_media_xchg 0 ****************************************************************************** **** **** **** S A U T I L S u p p o r t U t i l i t y **** **** **** **** for the HP A7143A RAID160 SA SCSI Adapter **** **** **** **** version A **** **** **** **** (c) Copyright 2003 Hewlett-Packard Development Company, L.P. **** ****************************************************************************** Chapter 6 129

122 Troubleshooting The sautil Command ---- DRIVER INFORMATION Driver State... READY ---- ADAPTER INFORMATION Adapter... HP A7143A RAID160 SA SCSI Adapter Hardware Path... 0/6/2/0 Device File... /dev/ciss ACCEPT MEDIA EXCHANGE Logical drive specified: 0 WARNING: The status of logical drive 0 will be set to "OK". The status of all physical disks that have been replaced on this logical drive will also be set to "OK". While this option preserves the RAID configuration (logical drive configurations, adapter settings, etc.), data on the failed logical drive may have already been compromised. If more disks have failed than the RAID level can accommodate, you will need to restore your data from backup media. Do you want to continue (y/n)? ****************************************************************************** **** End of SAUTIL Output **** ****************************************************************************** 130 Chapter 6

123 Troubleshooting The sautil Command sautil <device_file> run_startup_script The run_startup_script option runs the RAID160 SA controller startup script to recreate the device files (/dev/cissx). Chapter 6 131

124 Troubleshooting The sautil Command 132 Chapter 6

125 A Probability of Logical Drive Failure Appendix A 133

126 Probability of Logical Drive Failure RAID Level and Probability of Drive Failure RAID Level and Probability of Drive Failure The probability that a logical drive will fail depends on the RAID level setting. A RAID 0 logical drive fails if only one physical disk fails. For a RAID 1+0 logical drive, the failure situation is complex. The maximum number of physical disks that can fail without causing failure of the logical drive is n/2, where n is the number of physical disks in the array. This maximum is reached only if no failed disk is mirrored to any other failed disk. In practice, a logical drive usually fails before this maximum is reached. As the number of failed disks increases, it becomes increasingly unlikely that a newly failed disk is not mirrored to a previously failed disk. The failure of only two physical disks is enough to cause a logical drive to fail if the two disks happen to be mirrored to each other. The risk of this occurring decreases as the number of mirrored pairs in the array increases. A RAID 5 logical drive (with no online spare) fails if two physical disks fail. A RAID ADG logical drive (with no online spare) fails when three physical disks fail. At any given RAID level, the probability of logical drive failure increases as the number of physical disks in the logical drive increases. The graph in Figure A-1, Relative Probability of Logical Drive Failure, provides more quantitative information. The data for this graph is calculated from the mean time between failure (MTBF) value for a typical physical disk, assuming that no online spares are present. If an online spare is added to any of the fault-tolerant RAID configurations, the probability of logical drive failure is further decreased. 134 Appendix A

127 Probability of Logical Drive Failure RAID Level and Probability of Drive Failure Figure A-1 Relative Probability of Logical Drive Failure Appendix A 135

128 Probability of Logical Drive Failure RAID Level and Probability of Drive Failure 136 Appendix A

129 B Controller Specifications Appendix B 137

130 Controller Specifications RAID160 SA Controller Specifications RAID160 SA Controller Specifications Table B-1 Dimensions RAID160 SA Specifications 31.5 cm x 10.8 cm x 1.5 cm (12.4 in x 4.3 in x 0.6 in) Power Required 24.9 W (19.0 W at 3.3 V, 5.9 W at 5 V) Battery PCI Specification PCI Bus Transfer Rate Supported RAID Levels 2 NiMH battery packs, rechargeable. The RAID160 SA controller complies with PCI revision 2.2 Up to 528 MB/s 0, 1, 1+0, 5, and ADG Number of channels 4 Number of drives per channel Up to 14 Connector Type Four VHDCI External, Two 68-pin Wide Internal Termination SCSI Transfer rate Cache Size Operating Temperature Range Shipping Temperature Range Operating Relative Humidity (non-condensing) Non-Operating Relative Humidity (non-condensing) Termination is required, but it is provided automatically on the supported HP systems. Up to 160 MB/s (40 MHz) per channel 256 MB (224 MB usable, 32 MB transfer buffer) 10 to 35 C (50 to 95 F) -30 to 60 C (-22 to 140 F) 20% to 80% 5% to 90% 138 Appendix B

131 C Hard Drive Installation and Replacement Appendix C 139

132 Hard Drive Installation and Replacement Background Background Each SCSI channel on the RAID160 SA controller supports up to 14 physical disks. Disks can be of the Ultra320 or the Ultra160 type. Each physical disk on a SCSI bus must have a unique ID value in the range of 0 to 15 (except ID 7, which is typically reserved for controller use). This value is set automatically on hot-pluggable disk drives in the storage systems that are supported by the RAID160 SA controller. Do not terminate the disk drives. HP servers and internal cabling provide the required termination of the SCSI bus. Do not use disk drives of different capacity in the same array. The excess capacity of larger disk drives cannot be used by the array and is wasted. Do not use hot-pluggable disk drives on the same SCSI bus as non-hot-pluggable disk drives. 140 Appendix C

133 Hard Drive Installation and Replacement General Information About Hard Drive Failure General Information About Hard Drive Failure When a physical disk fails, the logical drive it belongs to will be affected. Each logical drive connected to a RAID160 SA controller can be configured with be a different RAID level. For this reason, each logical drive may be affected differently by a physical disk failure, depending on the fault-tolerance method (RAID level) that has been configured on it. RAID 0 configurations cannot tolerate disk drive failure. If any physical disk in the array fails, the logical drive will also fail. RAID 1 configurations, which are limited to two mirrored physical disks in an array, can tolerate one physical disk failure. RAID 1+0 configurations can tolerate multiple physical disk failures as long as no failed disks are mirrored to one another. RAID 5 configurations can tolerate one physical disk failure. RAID ADG configurations can tolerate simultaneous failure of two physical disks. If more physical disks fail than the fault-tolerance method allows, fault tolerance is compromised and the logical drive fails. In this case, all requests from the operating system will be rejected with unrecoverable errors. The Compromised Fault Tolerance section discusses possible ways to recover from this situation. Recognizing Disk Drive Failure The LEDs on the front of each disk drive are visible through the front of the StorageWorks disk enclosures. When a disk drive is configured as part of an array and attached to a powered-up controller, the status of the drive can be determined from the illumination pattern of the LEDs. Appendix C 141

134 Hard Drive Installation and Replacement General Information About Hard Drive Failure Table E-1 describes the meaning of the various LED combinations. Figure C-1 Figure E-1: Hard drive status LED indicators Table C-1 Disk Drive Status from LED Illumination Pattern (1) Activity (2) Online (3) Fault Meaning On, Off, or Flashing On or Off Flashing A predictive failure alert has been received for this disk drive. Replace the drive as soon as possible. On, Off, or Flashing On Off OK to replace the disk drive online if the array is configured for fault tolerance and all other drives in the array are online. The disk drive is online and configured as part of an array. On Flashing Off Do not remove the disk drive. Removing a drive during this process may terminate the current operation and cause data loss. The disk drive is rebuilding or undergoing capacity expansion. 142 Appendix C

135 Hard Drive Installation and Replacement General Information About Hard Drive Failure Table C-1 Disk Drive Status from LED Illumination Pattern (Continued) (1) Activity (2) Online (3) Fault Meaning On Off Off Do not remove the disk drive. Removing a drive during this process may cause data loss. The disk drive is being accessed, but (1) it is not configured as part of an array, or (2) it is a replacement drive and rebuild has not yet started. On Flashing Flashing Do not remove the disk drive. Removing a drive during this process can cause data loss in non-fault-tolerant configurations. Either (1) the drive is part of an array being selected by saconfig, or (2) sautil is upgrading the drive firmware. Off Off On OK to replace the disk drive online. The drive has failed and has been placed offline. Off Off Off OK to replace the disk drive online if the array is configured for fault tolerance and all other drives in the array are online. Either (1) the drive is not configured as part of an array; (2) the drive is configured as part of an array, but a powered-up controller is not accessing the drive; or (3) the drive is configured as an online spare. There are other ways to recognize that a hard drive has failed: The amber LED lights up on the front of supported StorageWorks disk enclosures, if failed drives are inside. (Other problems such as fan failure, redundant power supply failure, or over-temperature conditions, will also cause this LED to light up.) Event Monitoring Services (EMS) will cause an alert message to be sent when physical or logical drive failure occurs. See Event Monitoring Service (EMS) on page 113, for details. Appendix C 143

136 Hard Drive Installation and Replacement General Information About Hard Drive Failure The sautil <device_file> command, can be used to investigate undetected disks. The SCSI DEVICE SUMMARY section of the sautil <device_file> command output lists all of the disks the firmware has detected. The Participating Physical Disk(s) section of the LOGICAL DRIVE information contained in the sautil <device_file> command output lists the channel and SCSI ID of all of the physical disks that have been assigned to a logical drive. By comparing the Participating Physical Disk(s) to the SCSI DEVICE SUMMARY, you can determine if disks are missing or failed. For example, in the following sautil <device_file> command output excerpt, the physical disk on channel 1 with a SCSI ID of 1 does not show up in the SCSI Device Summary, however, it is listed as a participating physical disk in Logical Drive LOGICAL DRIVE SUMMARY # RAID Size Status MB USING INTERIM RECOVERY MODE ---- SCSI DEVICE SUMMARY Ch ID Type Capacity Status 1 0 DISK 18.2 GB OK 1 7 PROCESSOR N/A N/A ---- LOGICAL DRIVE Logical Device File... c6t0d0 Fault Tolerance Mode... RAID 1+0 (Disk Mirroring) Logical Drive Status... USING INTERIM RECOVERY MODE # of Participating Physical Disks... 2 Participating Physical Disk(s)... Ch:ID 1: 0 1: Appendix C

137 Hard Drive Installation and Replacement General Information About Hard Drive Failure Participating Spare Disk(s)... Ch:ID none Stripe Size KB Logical Drive Cache Status... cache enabled Configuration Signature... 0xA36E047E Media Exchange Detected?... no For more information on the sautil command see Troubleshooting with sautil on page 115. Appendix C 145

138 Hard Drive Installation and Replacement Compromised Fault Tolerance Compromised Fault Tolerance Compromised fault tolerance commonly occurs when more physical disks have failed than the fault-tolerance method can endure. In this case, the logical volume is failed and unrecoverable disk error messages are returned to the host. Data loss is likely to occur. An example of this situation would be an array configured with RAID 5 fault tolerance, in which one drive fails, while another drive in the same array is still being rebuilt. If the array has no online spare, the logical drive will fail. Compromised fault tolerance may also be caused by non-drive problems, such as temporary power loss to a storage system or a faulty cable. In such cases, the physical drives do not need to be replaced. However, data may still have been lost, especially if the system was busy at the time that the problem occurred. Example C-1 Procedure to Attempt Recovery When fault tolerance has been compromised, inserting replacement drives does not improve the condition of the logical volume. Instead, if your screen displays unrecoverable error messages, try the following procedure to recover data. Power down the StorageWorks disk enclosure, and then power it back up. In some cases, a marginal drive will work again for long enough to allow you to make copies of important files. Make copies of important data, if possible. Replace any failed disks. After the failed disks have been replaced, the fault tolerance may again be compromised. If so, cycle the power again. Run the sautil <device_file> accept_media_xchg <logical_drive_number> command on the affected logical drive. This will restore the logical drive s configuration. Now restore your data from backup media (see sautil <device_file> accept_media_xchg <logical_drive_number> on page 129). To minimize the risk of data loss due to compromised fault tolerance, make frequent backups of all logical volumes. 146 Appendix C

139 Hard Drive Installation and Replacement Automatic Data Recovery Automatic Data Recovery Automatic data recovery is an automatic background process that rebuilds data onto a spare or replacement disk drive when another disk drive in the array fails. This process is also called a rebuild. If a disk drive in a fault-tolerant configuration is replaced while the system power is off, a message is displayed during the next system startup. This message informs you that an automatic data recovery procedure has been initiated. When automatic data recovery has finished, the Online LED of the replacement drive stops blinking and begins to glow steadily. In general, approximately 15 minutes is required to rebuild each gigabyte. The actual rebuild time depends on: The level of rebuild priority that has been set for the logical drive (saconfig automatically sets the priority to high ) The amount of I/O activity occurring during the rebuild operation The disk drive speed The number of disks in the array (for RAID 5 and RAID ADG) For example, the rebuild time when using 9-GB Wide-Ultra disk drives in a RAID 5 configuration varies from ten minutes per gigabyte (for three drives) to 20 minutes per gigabyte (for 14 drives). Example C-2 Failure of Automatic Data Recovery If the Online LED of the replacement disk drive stops blinking during automatic data recovery, there are three possible causes: If the Online LED is glowing continuously, automatic data recovery was successful and has finished. If the amber failure LED is illuminated or other LEDs go out, the replacement disk drive has failed and is producing unrecoverable disk errors. Remove and replace the failed replacement disk drive. If the automatic data recovery process has abnormally terminated, one possible cause is a non-correctable read error on another physical disk. Locate the faulty disk, replace it, and restore data from backup. Appendix C 147

140 Hard Drive Installation and Replacement General Aspects of Disk Drive Replacement General Aspects of Disk Drive Replacement CAUTION Sometimes, a disk drive that has previously been failed by the controller may seem to be operational after the system is power-cycled, or (for a hot-pluggable drive) after the drive has been removed and reinserted. However, continued use of such marginal drives may eventually result in data loss. Replace the marginal drive as soon as possible. There are several other factors to remember when replacing a disk drive: Non-hot-pluggable drives should only be replaced while the system is powered down. Hot-pluggable drives can be removed and replaced at any time, whether the host or storage system power is on or off. When a hot-pluggable drive is inserted, all disk activity on the array pauses while the new drive is spinning up (usually 20 seconds or so). If the drive is inserted while power is on, in a fault-tolerant configuration, data recovery onto the replacement drive begins automatically (indicated by the blinking Online LED). Replacement disk drives must have a capacity no less than that of the smallest disk drive in the array. Drives of insufficient capacity will be failed immediately by the controller, before automatic data recovery can begin. CAUTION In systems using external data storage, take care that the server is the first unit to be powered down and the last to be powered back up. Doing this ensures that the system will not erroneously mark the drives as failed. The rebuild operation takes several hours, even if the system is not busy while the rebuild is in progress. System performance and fault tolerance are both affected until the rebuild has finished. Therefore, replace drives 148 Appendix C

141 Hard Drive Installation and Replacement General Aspects of Disk Drive Replacement during low activity periods whenever possible. In addition, be sure that all logical drives on the same array as the disk drive being replaced, have a current, valid backup. Appendix C 149

142 Hard Drive Installation and Replacement Drive Failure During Rebuild Drive Failure During Rebuild If another drive in the array fails while fault tolerance is unavailable during rebuild, a fatal system error may occur. If this happens, all data on the array is lost. In exceptional cases, however, failure of another drive need not lead to a fatal system error. These exceptions include: Failure after activation of a spare drive Failure of a drive that is not mirrored to any other failed drives (in a RAID 1+0 configuration) Failure of a second drive in a RAID ADG configuration Minimizing Fatal System Errors During Rebuild When a hard drive is replaced, the controller gathers fault-tolerance data from the remaining drives in the array. This data is then used to rebuild the missing data (originally on the failed drive) onto the replacement drive. If more than one drive is removed at a time, the fault-tolerance data is incomplete. The missing data cannot then be reconstructed and is likely to be permanently lost. To minimize the likelihood of fatal system errors, take these precautions when removing failed drives: Do not remove a degraded drive if any other member of the array is offline (the Online LED is off). In this condition, no other drive in the array can be removed without data loss. There are some exceptions: When RAID 1+0 is used, drives are mirrored in pairs. Several drives can be in a failed condition simultaneously (and they can all be replaced simultaneously) without data loss, as long as no two failed drives belong to the same mirrored pair. When RAID ADG is used, two drives can fail simultaneously (and be replaced simultaneously) without data loss. If an online spare has an unlit Online LED (it is offline), the degraded drive can still be replaced. 150 Appendix C

143 Hard Drive Installation and Replacement Drive Failure During Rebuild Do not remove a second drive from an array until the first failed or missing drive has been replaced and the rebuild process is complete. (When the rebuild is complete, the Online LED on the front of the drive stops blinking.) There are some exceptions: In RAID ADG configurations, any two drives in the array can be replaced simultaneously. In RAID 1+0 configurations, any drives that are not mirrored to other removed or failed drives can be simultaneously replaced offline without data loss. Appendix C 151

144 Hard Drive Installation and Replacement Drive Failure During Rebuild 152 Appendix C

145 D Electrostatic Discharge Appendix D 159

146 Electrostatic Discharge Preventing System Damage Preventing System Damage Handling Parts To prevent damaging the system, be aware of the precautions you need to follow when setting up the system or handling parts. A discharge of static electricity from a finger or other conductor may damage system boards or other static-sensitive devices. This type of damage may reduce the life expectancy of the device. To prevent electrostatic damage, observe the following precautions: Avoid hand contact by transporting and storing products in static-safe containers Keep electrostatic-sensitive parts in their containers until they arrive at static-free workstations Place parts on a grounded surface before removing them from their containers Avoid touching pins, leads, or circuitry Always be properly grounded when touching a static-sensitive component or assembly Grounding There are several methods for grounding. Use one or more of the following methods when handling or installing electrostatic-sensitive parts: Use a wrist strap connected by a ground cord to a grounded workstation or computer chassis. Wrist straps are flexible straps with a minimum of 1 megohm resistance in the ground cords. To provide proper ground, wear the strap snug against the skin. Use heel straps, toe straps, or boot straps at standing workstations. Wear the straps on both feet when standing on conductive floors or dissipating floor mats. se conductive field service tools. Use a portable field service kit with a folding static-dissipating work mat. 160 Appendix D

147 E Questions and Answers Appendix E 161

148 Questions and Answers RAID160 SA Controller Q & A RAID160 SA Controller Q & A Q:How many RAID160 SA controllers can I install in my system? A:The maximum number of controllers that you can install in your system depends on your server and several other factors specific to your configuration. Generally, the maximum number is restricted to the number of PCI slots not used for other peripherals. Another limiting factor is the power rating of your system. Each RAID160 SA controller requires 24.9 W. Your server must be capable of supplying every controller with this amount of power. Q:How many external drives can I install in my system? A:Each RAID160 SA controller has four SCSI buses. Each bus can support up to 14 drives. Q:Does the RAID160 SA controller support SCSI tape drives and CD-ROM drives? A: No. Q:What is the data transfer rate for Wide Ultra160 SCSI? A:Wide Ultra160 SCSI has a data bandwidth of 160 MB per second. Most server applications do not generally take advantage of the full Ultra160 bandwidth, so performance results will vary from customer to customer. Q:What is the difference between LVD and Ultra160 SCSI? A:Low Voltage Differential (LVD) is a signaling level for SCSI protocols. Ultra160 is a SCSI protocol that uses LVD signaling. Ultra2 also uses LVD signaling, but earlier SCSI protocols used Single-Ended (SE) signaling. Q:Are Single Ended and Low Voltage Differential SCSI compatible? A:Yes. When mixing SE drives and LVD drives on a single SCSI channel, all drives switch down to SE SCSI mode and operate under SE SCSI rules. To maintain a true LVD SCSI bus with its associated performance advantages, a LVD SCSI channel should only be connected to LVD SCSI drives. Q:I have several hard drives in my server and in an HP StorageWorks Enclosure What SCSI IDs do I assign for these drives? 162 Appendix E

149 Questions and Answers RAID160 SA Controller Q & A A:If you are using hot-pluggable drives in a StorageWorks Enclosure 4300, the SCSI IDs are set automatically according to the bay in which the drives are installed and do not need to be set manually. The IDs of devices on each SCSI bus do not have to be consecutive. However, the IDs must still be unique to each device on any given SCSI bus. Q:Can I use third-party drives (those not manufactured by HP) with the RAI160 SA controller? A:No. Q:Why do the drive activity LEDs light up on some drives when my system is idle? A:The RAID160 SA controller performs several different background activities on the drives when the controller is otherwise idle. For example, Auto-Reliability Monitoring scans fault-tolerant volumes for defects and verifies the consistency of parity data, and Drive Parameter Tracking periodically checks the performance of all drives on the controller (normally on an hourly basis). Q: What is RAID ADG? A:RAID ADG is an extension of RAID 5 that allows additional fault tolerance by using two different and independent parity schemes. Data is striped across a set of hard drives, just as with RAID 5, and the two sets of parity data are calculated and written across all the drives in the array. RAID ADG provides an extremely high level of fault tolerance and can sustain two simultaneous drive failures without downtime or data loss. This fault tolerance level is the perfect solution when data is mission critical. Appendix E 163

150 Questions and Answers RAID160 SA Controller Q & A 164 Appendix E

151 Glossary ACU (Array Configuration Utility) A configuration utility useful both for novices and for more experienced RAID users. ADU (Array Diagnostic Utility) A diagnostic tool that collects comprehensive information about the array controllers in a system and lists any problems detected. ARM (Auto-Reliability Monitoring) Also known as surface analysis. A fault management feature whereby hard drives are scanned for bad sectors, and data in the faulty sectors is remapped onto good sectors. Parity data consistency is also checked for drives in RAID 5 or RAID ADG configurations. Operates as a background process. array A set of physical drives configured into one or more logical drives. Arrayed drives have significant performance and data protection advantages over non-arrayed drives. array accelerator A component of some Smart Array controllers that dramatically improves disk read and write performance by providing a buffer. Data integrity is protected by a backup battery and ECC memory. array capacity expansion See capacity expansion. Automatic Data Recovery Also known as rebuild. A process that automatically reconstructs data from a failed drive and writes it onto a replacement drive. Rebuild time depends on several factors, but at least 15 minutes should be allowed per gigabyte. cache A high-speed memory component, used to store data temporarily for rapid access. capacity expansion Abbreviation for array capacity expansion. The addition of physical drives to a pre-existing drive array, and redistribution of existing logical drives and data over the enlarged array. The size of the logical drives does not change. capacity extension Abbreviation for logical drive capacity extension. The enlargement of a logical drive without disruption of data. There must be free space on the array before extension can occur. If necessary, create free space by deleting a logical drive or by carrying out a capacity expansion. Capacity extension can be carried out online with some operating systems. CISS Acronym for Command Interface for SCSI-3 Support Specification. controller duplexing A type of fault tolerance that requires two Smart Array controllers. Each controller has its own set of drives, and the drive sets have identical data. When one controller fails, the other automatically takes over the servicing of requests. controller duplexing is available only for some operating systems. data guarding See RAID. data striping Writing data to logical drives in interleaved chunks (by byte or by sector). This technique improves system performance. drive mirroring See RAID. ECC (error correction and checking) memory A type of memory that checks and corrects single-bit or multi-bit memory errors (depending on configuration) without causing the server to halt or corrupt data. Glossary 165

152 Glossary fault tolerance fault tolerance The ability of a server to recover from hardware problems without interrupting server performance or corrupting data. Hardware RAID is most commonly used, but there are other types of fault tolerance for example, controller duplexing and software-based RAID. flashing Updating the flash memory on a system. Flash memory is non-volatile memory that is used to hold control code such as BIOS information. It is also very fast because it can be rewritten block by block, rather than byte by byte. hot spare See online spare. interim data recovery If a drive fails in RAID 1, 1+0, 5 or ADG, the system will still process I/O requests, but at a reduced performance level. logical drive (or logical volume) A group of physical drives, or part of a group, that behaves as one storage unit. Each constituent physical drive contributes the same storage volume to the total volume of the logical drive. Has performance advantages over individual physical drives. logical drive capacity extension See capacity extension. LVD (low voltage differential) A type of SCSI signaling that allows a maximum transfer rate of either 80 MB/s or 160 MB/s, conforming to either the Wide Ultra2 or Wide Ultra160 SCSI standards respectively. online spare Also known as a hot spare, this is a drive in a fault-tolerant system that normally contains no data. When any other drive in the array fails, the controller automatically rebuilds the missing data that was on the failed drive onto the online spare. The controller constructs the missing data from the duplicate or parity data that is on the remaining drives in the array. PCI-X An enhanced PCI bus that allows operation at 133 MHz, equivalent to a data throughput of 1.0 GB/s. PCI-X is backward-compatible with PCI systems and devices, which operate at 66 MHz or 33 MHz. RAID (Redundant Array of Independent Disks) A form of fault tolerance. RAID 0 (no fault tolerance) uses data striping to distribute data evenly across all physical disks in the array, but has no redundant data. RAID 1+0 (drive mirroring) duplicates data from one drive onto a second drive. RAID 5 (distributed data guarding) distributes parity data across all drives in the array, and uses the parity data and data on remaining drives to reconstruct data from a failed drive. RAID ADG (advanced data guarding) is similar to RAID 5, but uses two independent sets of parity data. Refer to Appendix D for more details. rebuild See Automatic Data Recovery. SCSI ID A unique ID number assigned to each SCSI device connected to a SCSI bus. The ID number determines the device priority on the SCSI bus; ID 7 is the highest priority and is always assigned to the SCSI controller. SE (single-ended) A type of SCSI signaling that allows a maximum transfer rate of 40 MB/s. Conforms to the Wide-Ultra SCSI standard. Now being phased out in favor of LVD technology. 166 Glossary

153 S.M.A.R.T. (Self-Monitoring, Analysis, and Reporting Technology) Technology co-developed by HP and the hard drive industry that provides warning of imminent drive failure. This feature makes it possible for HP to offer Pre-Failure Warranty replacement of hard drives. S.M.A.R.T. supersedes the drive parameter tracking feature that was previously used for this purpose because the self-monitoring routines used in S.M.A.R.T. are more accurate than the drive parameter tracking tests. The self-monitoring routines are customized for that specific drive type and have direct access to internal performance, calibration, and error measurements. Glossary Wide-Ultra; Wide Ultra2; Wide Ultra160 SNMP (Simple Network Management Protocol) Governs network management and the monitoring of network devices and functions. spare See online spare. striping See data striping. surface analysis See ARM. VHDCI (Very High Density Cable Interconnect) A type of external SCSI connector used by Ultra SCSI controllers. Wide-Ultra; Wide Ultra2; Wide Ultra160 A set of SCSI standards that support maximum signal transfer rates of 40 MB/s, 80 MB/s, and 160 MB/s, respectively. Glossary 167

154 Glossary S.M.A.R.T. (Self-Monitoring, Analysis, and Reporting Technology) 168 Glossary