HP A3550A - High Availability Disk Arrays Model 20 Storage Enclosure User Manual
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Disk array system
  5. A3550A - High Availability Disk Arrays Model 20 Storage...
  6. User manual
HP A3550A - High Availability Disk Arrays Model 20 Storage Enclosure User Manual

HP A3550A - High Availability Disk Arrays Model 20 Storage Enclosure User Manual

High availability disk array
Hide thumbs Also See for A3550A - High Availability Disk Arrays Model 20 Storage Enclosure:
Table of Contents

Quick Links

See also: Installation Manual
Table of Contents
loading

Related Manuals for HP A3550A - High Availability Disk Arrays Model 20 Storage Enclosure

Summary of Contents for HP A3550A - High Availability Disk Arrays Model 20 Storage Enclosure

  • Page 5 WARNING WARNING 6à Ãqr‚‡r†ÃhÃuh“h…qÇuh‡ÃphÃphˆ†rÃr…†‚hyÃvwˆ…’ Caution Caution 6à Ãqr‚‡r†ÃhÃuh“h…qÇuh‡ÃphÃqh€htrÃr„ˆvƒ€r‡Ã‚…Ã…r†ˆy‡ÃvÃy‚†‡Ãqh‡h Caution WARNING 9‚Á‚‡Ãƒ…‚prrqÃir’‚qÃhà …à Á‚‡vprȁ‡vy҂ˆÃˆqr…†‡hqÇurÃuh“h…q‚ˆ†Ãp‚qv‡v‚†ÃhqÃuh‰rÇhxrÃ hƒƒ…‚ƒ…vh‡rƇrƒ†...
  • Page 10 *HUlXVFKHPLVVLRQ viii...
  • Page 11 WARNING There are no user maintenance or service operations or adjustments to be performed on any OLC/OLM model.
  • Page 12 The product herewith complies with the requirements of the Low Voltage Directive 73/23/EEC and the EMC Directive 89/336/EEC and carries the CE marking accordingly. This Product was tested in a typical configuration with a Hewlett-Packard 9000 K-Class Enterprise Server computer system. Roseville, May 20 .
  • Page 13 In this book Format Conventions Convention Used for this font ETURN...
  • Page 15 Contents Reference xiii...
  • Page 16 Product Description...
  • Page 17 Hardware Topologies Installation...
  • Page 18 Grid Manager...
  • Page 19 Host-Based Support Tools xvii...
  • Page 20 Troubleshooting xviii...
  • Page 21 Removal and Replacement Appendix Glossary Index...
  • Page 23 FIGURES...
  • Page 24 Â Â xxii...
  • Page 25 Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â xxiii...
  • Page 26 Â Â Â Â Â Â Â Â Â Â Â xxiv...
  • Page 28 xxvi...
  • Page 29 TABLES xxvii...
  • Page 30 xxviii...
  • Page 31 Reference Reference - 1...
  • Page 32 Features Š Reference - 2...
  • Page 33 Models, Options, and Add-on Products Models Available Options Available Storage Capacity Options Option Number of 8.8 GB Option Number of 17.8 GB LP disk modules LP disk modules Order up to six of either option to fill the array. High Availability Options Option Dual SPs with 32 MB of cache on each SP (includes BBU) Dual SPs with 64 MB of cache on each SP (includes BBU)
  • Page 34 A3661B(Z) #0Z6 A3736A 1005-0366 Fibre optic cable 100 m RS-232C Cables Cable product number Part number Description Length 24542G 24540-80011 HP RS-232C cable from array to terminal 24542M 5183-0807 HP RS-232C cable from array to MUX Upgrade and Add-on Products Reference - 4...
  • Page 35 Product Structure for the A3662B SP630/FC Controller Options Available High Availability Cache Memory Options SIMMs SIMMs for first Option Cache size on A3662B SP in A3661B 32 MB 2 x 16 MB — 64 MB 4 x 16 MB 2 x 16 MB Fibre Optic Cable Options Option Fibre optic cable...

  • Page 36: Host Adapters

    Host Adapters Fibre Channel Mass Storage I/O Adapter A3591A HSC HP 9000 D-Class Enterprise Servers A3404A HSC HP 9000 K-Class Enterprise Servers A3636A HSC HP 9000 T-Class Enterprise Servers A3740A PCI HP 9000 N-Class and V-Class Enterprise Servers A5246A PCI HP NetServers Reference - 6...

  • Page 37: Specifications

    Specifications Dimensions Height Width Depth 46.74 cm (18.4 in.) 48.2 cm (19.0 in.) 76.2 cm (30 in.) Weight Minimum configured weight Maximum configured weight Chassis with 5 disk modules, 1 SP, and 2 Chassis with 30 disk modules, 2 SPs, 3 power power supply units: 58.7 kg (130.3 lbs) supply units, and 1 BBU: 106.6 kg (235 lbs) WARNING...
  • Page 38 AC Power Input Specifications Current draw* BTU/hr K cal/hr 1100 1100 3.300 Power Consumption DC Power Specifications Environmental Specifications Operating Environment Reference - 8...
  • Page 39 Heat Output Non-Operating Environment (Shipping and Storage) Battery Disposal Reference - 9...
  • Page 40 Reference - 10...

  • Page 41: Emc Compliance

    Acoustic Levels Sound power Sound pressure (operator’s position) 67 dBA 48 dBA Safety Certifications Replacement Power Cord EMC Compliance Reference - 11...

  • Page 42: Replaceable Parts

    Replaceable Parts Customer-Replaceable Parts (CRUs) New HP part number Exchange part number Description 5063-5393 A3666-69021 4.2 GB LP disk module 5063-5335 A5169-69021 4.2 GB LP disk module 5063-5333 A5132-69021 8.8 GB LP disk module 5063-5334 A5133-69021 17.8 GB LP disk module A3231-60005 A3231-69005 A3662-60001...

  • Page 43: Product Description

    1 Product Description...
  • Page 44 About the Disk Array Figure 1-1 High Availability Fibre Channel 30-Slot Disk Array About the Disk Array...
  • Page 45 About the Disk Array...
  • Page 46 Note The disk array is supported as a boot device on the HP-UX operating system only in a non-high availability, single SP configuration. Figure 1-2 Disk Array Internal Hardware Architecture About the Disk Array...

  • Page 47: Disk Array Chassis

    Disk Array Chassis Database drives C0 D0 C3 D3 E3 A0, A3, A4, B0, C0 C1 D1 C4 D4 E4 Cache vault drives A0, B0, C0, D0, E0 C2 D2 C5 D5 E5 Figure 1-3 Front View of Disk Array Chassis with Disk Slots Identified About the Disk Array...
  • Page 48 About Disk Array Components Caution Fillers must be installed in any unused disk array slots to ensure EMI compliance and maintain proper air flow in the chassis. Do not remove any disk array component without installing a replacement component or a slot filler at the same time. Do not operate the disk array with any slot open, except while replacing a failed component.
  • Page 49 Figure 1-4 Disk Module About Disk Array Components...
  • Page 50 Note Bound drives must remain in the slots in which they were bound. Problems will occur if disk modules are moved to other slots after they are bound. About Disk Array Components...
  • Page 51 Storage-Control Processor Printed-circuit Memory board modules Service light (amber) Ready light (green) Latch Bezel Figure 1-5 SP630/FC Storage-Control Processor About Disk Array Components...
  • Page 52 1-10 About Disk Array Components...
  • Page 53 Fan Pack Replace light Release button Figure 1-6 Fan Pack About Disk Array Components 1-11...

  • Page 54: Power Supply Units

    Power Supply Units Ready light (green) Replace light (amber) Figure 1-7 Power Supply Unit 1-12 About Disk Array Components...

  • Page 55: Battery Backup Unit

    Battery Backup Unit About Disk Array Components 1-13...
  • Page 56 Figure 1-8 Battery Backup Unit 1-14 About Disk Array Components...
  • Page 57 Fibre Channel Interconnect PCA Figure 1-9 Fibre Channel Interconnect PCA About Disk Array Components 1-15...

  • Page 58: External Components

    External Components Fibre Channel I/O Adapter Fibre Channel Arbitrated Loop Hub 1-16 External Components...

  • Page 59: Raid Technology

    Disk Array High Availability Features RAID Technology Note RAID level 0 and individual disk units are not supported because they do not provide data redundancy. Disk Array High Availability Features 1-17...
  • Page 60 Disk Array Caching 1-18 Disk Array High Availability Features...
  • Page 61 Disk Array High Availability Features 1-19...
  • Page 62 Table 1-1 Caching Recommendations for Disk Configurations Disk configuration Read caching Write caching RAID-5 Recommended Highly recommended RAID-3 Not allowed Not allowed RAID-1 Recommended Acceptable RAID-1/0 Recommended Acceptable Table 1-2 Utilities for Various Cache Operations Cache operation Grid Manager Specify basic cache parameters Enable/disable storage system cache Enable/disable read and/or write...
  • Page 63 Disk Array High Availability Features 1-21...
  • Page 64 RAID General Information 1-22 RAID General Information...

  • Page 65: Disk Striping

    Caution Disk modules having different storage capacities or different model or part numbers should not be bound into the same RAID group because performance can be affected. Table 1-3 Disk Striping, Hardware Mirroring, and Parity by RAID Level Hardware RAID level Disk Striping Mirroring Parity...
  • Page 66 Mirroring 1-24 RAID General Information...
  • Page 67 Parity RAID-1 (Mirrored Pair) RAID General Information 1-25...
  • Page 68 Figure 1-10 RAID-1 (Mirrored Pair) 1-26 RAID General Information...
  • Page 69 RAID-1/0 Group (Mirrored RAID-0 Group) RAID General Information 1-27...
  • Page 70 Figure 1-11 Distribution of User Data in a RAID-1/0 Group 1-28 RAID General Information...
  • Page 71 RAID-3 Group (Parallel Access Array) Figure 1-12 Distribution of User and Parity Data in a RAID-3 Group RAID General Information 1-29...
  • Page 72 Table 1-4 RAID-3 Memory Recommendations Based on 6 MB per LUN Number of Total SIMM SP memory Total RAID-3 Unused SIMM bound RAID-3 memory used memory memory LUNs on each SP by each SP on each SP on each SP 16 MB 4 MB 6 MB...
  • Page 73 RAID General Information 1-31...
  • Page 74 RAID-5 Group (Individual Access Array) 1-32 RAID General Information...
  • Page 75 Figure 1-13 Distribution of User and Parity Data in a RAID-5 Group RAID General Information 1-33...

  • Page 76: Global Hot Spares

    Global Hot Spares 1-34 Global Hot Spares...
  • Page 77 Figure 1-14 Example of a Disk Array with Two RAID-5 Groups and One Global Hot Spare Global Hot Spares 1-35...
  • Page 78 1-36 Global Hot Spares...
  • Page 79 Planning Disk Unit Configurations Data Availability and Disk Space Use Planning Disk Unit Configurations 1-37...
  • Page 80 raiduser Figure 1-15 Disk Space Use in the Different Disk Unit Configurations 1-38 Planning Disk Unit Configurations...
  • Page 81 Guidelines for Logical Disk Unit Configurations RAID-5 Group (Individual Access Array) Planning Disk Unit Configurations 1-39...
  • Page 82 RAID-3 Group (Parallel Access Array) RAID-1/0 Group 1-40 Planning Disk Unit Configurations...
  • Page 83 Figure 1-16 Mirrored Modules in a RAID-1/0 Group RAID-1 (Mirrored Pair) Planning Disk Unit Configurations 1-41...

  • Page 84: Global Hot Spare

    Global Hot Spare RAID Performance Table 1-5 Relative Performance, Cost, and Availability Compared to an Individual Disk Relative read Relative write Relative cost Tolerance for Physical disk performance performance per MB of single disk configuration without caching without caching storage module failure? RAID-5 group with 5 Up to 5.0...
  • Page 85 Planning Disk Unit Configurations 1-43...
  • Page 86 Two SPs, Load Balancing, and Device File Name Configuration Management Worksheet 1-44 Planning Disk Unit Configurations...
  • Page 87 A0-E0 & A3-E3 A1-E1 & A4-E4 A2-E2 & A5-E5 Host Name Host Adapter Paths FC-AL Hub 1 Name FC-AL Hub 2 Name Array Name SP-A SP-B Primary Alternate RAID Volume Number Size Logical Size Path Path Level Disks Group ID Physical MBytes Volumes...
  • Page 88 Completing the Configuration Management Worksheet 1-46 Planning Disk Unit Configurations...
  • Page 89 Figure 1-18 Example of a High Availability Topology with Three Arrays, Two Hubs, and Four Hosts Planning Disk Unit Configurations 1-47...
  • Page 90 Figure 1-19 Example of a High Availability, Distance and Capacity Topology with Three Arrays, Two Pairs of Cascaded Hubs, and Four Hosts 1-48 Planning Disk Unit Configurations...
  • Page 91 Planning Disk Unit Configurations 1-49...
  • Page 92 Note Setting system cache to both read and write cache, with write cache twice the size of read cache, is recommended for RAID-5 configurations because this will provide best overall performance. 1-50 Planning Disk Unit Configurations...
  • Page 93 2 Hardware Topologies...
  • Page 94 Topologies Topologies...

  • Page 95: Basic Topology

    Basic Topology Basic Topology...
  • Page 96 Figure 2-1 Basic Topology, High Availability Version: Host with Two FC I/O Adapters Basic Topology...
  • Page 97 Figure 2-2 Basic Topology, High Availability Version: Host with Four FC I/O Adapters Basic Topology...
  • Page 98 Figure 2-3 Basic Topology, Non-High Availability Version: Host with Four FC I/O Adapters Basic Topology...
  • Page 99 Table 2-1 Basic Topology Error Recovery Failing Continue component after failure? What happens and how to recover Disk module Applications continue to run on all supported RAID levels (RAID-1, 1/0, 3, and 5). The system administrator or service provider hot- replaces the failed disk module.
  • Page 100 Single-System Distance Topology Single-System Distance Topology...
  • Page 101 Single-System Distance Topology...
  • Page 102 Figure 2-4 Single-System Distance Topology 2-10 Single-System Distance Topology...
  • Page 103 Table 2-2 Single-System Distance Topology Error Recovery Failing Continue component after failure? What happens and how to recover Disk module Applications continue to run on all supported RAID levels (RAID-1, 1/0, 3, and 5). The system administrator or service provider hot-replaces the failed disk module.
  • Page 104 High Availability Topology 2-12 High Availability Topology...
  • Page 105 Figure 2-5 High Availability Topology High Availability Topology 2-13...
  • Page 106 Table 2-3 High Availability Topology Error Recovery Failing Continue component after failure? What happens and how to recover Disk module Applications continue to run on all supported RAID levels (RAID-1, 1/0, 3, and 5). The system administrator or service provider hot-replaces the failed disk module.
  • Page 107 High Availability, Distance, and Capacity Topology High Availability, Distance, and Capacity Topology 2-15...
  • Page 108 Figure 2-6 High Availability, Distance, and Capacity Topology 2-16 High Availability, Distance, and Capacity Topology...
  • Page 109 Table 2-4 High Availability, Distance, and Capacity Topology Error Recovery Failing Continue component after failure? What happens and how to recover Disk module Applications continue to run on all supported RAID levels (RAID-1, 1/0, 3, and 5). The system administrator or service provider hot- replaces the failed disk module.
  • Page 110 Campus Topology 2-18 Campus Topology...
  • Page 111 Building 1 Building 2 Figure 2-7 Campus Topology Campus Topology 2-19...
  • Page 112 Table 2-5 Campus Topology Error Recovery Failing Continue component after failure? What happens and how to recover Disk module Applications continue to run on all supported RAID levels (RAID-1, 1/0, 3, and 5). The system administrator or service provider hot- replaces the failed disk module.

  • Page 113: Installation

    3 Installation...

  • Page 114: Overview Of Installation

    Overview of Installation Overview of Installation...

  • Page 115: Check The Operating System

    Check the Operating System Check the Operating System...
  • Page 116 Check Power Requirements Note The Hewlett-Packard Model 30/FC High Availability Disk Array uses 200 VAC to 240 VAC nominal. 110 VAC is not supported. Check Power Requirements...
  • Page 117 Table 3-1 PDU Requirements PDU part PDU product number number Description Typical application Racking restrictions E5929-63001 E5929A - Universal PDU C-19 outlet is for newer Must be racked on rails at or - Ten C-13 and one Hawk SPUs requiring a above 4 EIAs to clear the C-19 outlets 20-amp connector.
  • Page 118 Table 3-2 Currents and Durations Arrays in a cabinet In-rush (surge) currents and duration Steady state currents Up to 115 amps for 10 to 12 ms 5 amps Up to 230 amps for 10 to 12 ms 10 amps Three Up to 345 amps for 10 to 12 ms 15 amps Table 3-3 European Circuit Breakers...
  • Page 119 Make the Fibre Channel Connection to the Host Install Fibre Channel I/O Adapter Cards into the Host System Make the Fibre Channel Connection to the Host...
  • Page 120 Set Fibre Channel IDs for the SP(s) in the Disk Array Most-significant Least-significant digit of FC ID digit of FC ID SP A’s FC ID SP B’s FC ID switches switches Figure 3-1 Fibre Channel ID Switches Note Each SP requires a unique Fibre Channel address number. Make the Fibre Channel Connection to the Host...
  • Page 121 Table 3-4 Fibre Channel Addresses FC address (Loop ID) FC address (Loop ID) FC address (Loop ID) (hexadecimal) (decimal) (hexadecimal) (decimal) (hexadecimal) (decimal) Make the Fibre Channel Connection to the Host...
  • Page 122 Determine the Locations of the Fibre Channel Connectors FC address FC address switches- connectors switches- connectors SP A SP A SP B SP B interface SP-A SP-B Figure 3-2 Fibre Channel Connector Locations Connect the Disk Array to a Host System or an HP FC-AL Hub 3-10 Make the Fibre Channel Connection to the Host...
  • Page 123 Figure 3-3 Connecting a Fibre Optic Cable to a Fibre Channel Connector Make the Fibre Channel Connection to the Host 3-11...
  • Page 124 Make the RS-232C Connection to the Host System Asynchronous port Figure 3-4 SP Console Port Locations 3-12 Make the RS-232C Connection to the Host System...
  • Page 125 Direct-Connect Terminal Configure the Direct-Connect Terminal YSTEM Make the RS-232C Connection to the Host System 3-13...
  • Page 126 Note If configuring the disk array using a direct-connect terminal, it is also possible to complete any RAID configuration modifications before attaching the disk array to the host computer. If terminal emulation is used, the disk array will come up in the factory- default configuration of RAID-5 LUNs.
  • Page 127 Identify Available MUX Ports Connect the Disk Array to a MUX Port Configure the MUX Ports on the Host System Note There are port restrictions on certain computers. If using a J2085A and the MDP port of a CPU, ports 0, 1, and 7 are reserved on a K-Series CPU. cd /etc/uucp cp Devices Devices.old vi Devices...
  • Page 128 gridmgr0::101:20:The Gridmgr:/home/gridmgr0:/bin/ksh gridmgr1::101:20:The Gridmgr:/home/gridmgr1:/bin/ksh cd /home mkdir gridmgr0 mkdir gridmgr1 cd gridmgr0 vi .profile #————————————————————————————————— # @(#) $Revision: 66.1 $ #————————————————————————————————— # User .profile for Grid Manager #————————————————————————————————— # Emulate vt100 terminal. TERM=vt100 export TERM # Set up the shell environment. set -u trap “echo 'logout'”...
  • Page 129 #____________________________________________________________________ # Copy .profile to the second login directory. cd /home/gridmgr1 cp /home/gridmgr0/.profile .profile vi .profile Make the RS-232C Connection to the Host System 3-17...

  • Page 130: Connect The Power Cord

    Connect the Power Cord Note The disk array must be installed into the cabinet so that the disk array’s fan pack door can be swung open without interfering with any cables, cabinet PDU, plug on the PDU, or other devices installed in the cabinet. The PDU should be installed on the left side of the cabinet (as viewed from the back of the cabinet).
  • Page 131 Power Up the Disk Array Front of storage system POWER Back of storage system Note: Fan not shown for clarity Figure 3-6 Powering Up the Disk Array Power Up the Disk Array 3-19...
  • Page 132 Verify Array Connectivity Class H/W Path Driver S/W State H/W Type Description =================================================================== mux2 CLAIMED INTERFACE HP J2092A - 16 RS-232 MUX /dev/diag/mux2 /dev/diag/tty2p5 /dev/tty2p14 /dev/diag/tty2p0 /dev/diag/tty2p6 /dev/tty2p15 /dev/diag/tty2p1 /dev/diag/tty2p7 /dev/tty2p2 /dev/diag/tty2p10 /dev/diag/tty2p8 /dev/tty2p3 /dev/diag/tty2p11 /dev/diag/tty2p9 /dev/tty2p4 /dev/diag/tty2p12 /dev/mux2 /dev/tty2p5 /dev/diag/tty2p13 /dev/tty2p0 /dev/tty2p6...
  • Page 133 Class H/W Path Driver S/W State H/W Type Description =================================================================================== root CLAIMED BUS_NEXUS ccio CLAIMED BUS_NEXUS I/O Adapter fcT1 CLAIMED INTERFACE HP Fibre Channel Mass Storage Adapter 8/4.5 fcT1_cntl CLAIMED INTERFACE HP Fibre Channel Mass Storage Cntl /dev/fcms2 8/4.8 CLAIMED INTERFACE FCP Protocol Adapter ext_bus...
  • Page 134 /dev/diag/tty0p8 /dev/tty0p8 /dev/diag/tty0p9 /dev/tty0p9 lanmux 10/4/16 lanmux0 CLAIMED INTERFACE HP J2146A - 802.3 LAN 10/4/16.1 lan3 CLAIMED INTERFACE /dev/diag/lan0 /dev/ether0 /dev/lan0 ext_bus 10/8 c720 CLAIMED INTERFACE GSC add-on Fast/Wide SCSI Interface target 10/8.7 CLAIMED DEVICE 10/8.7.0 sctl CLAIMED DEVICE Initiator /dev/rscsi/c1t7d0 10/12 bus_adapter CLAIMED...
  • Page 135 ETURN Power Up the Disk Array 3-23...
  • Page 136 3-24 Power Up the Disk Array...
  • Page 137 4 Grid Manager...
  • Page 138 About Grid Manager About Grid Manager...
  • Page 139 Initiating Grid Manager Login: gridmgr0 ONTROL ETURN Initiating Grid Manager...
  • Page 140 Displaying the Grid Manager Main Menu ETURN Figure 4-1 Grid Manager Main Menu Displaying the Grid Manager Main Menu...
  • Page 141 Grid Manager Menu Overview ETURN Grid Manager Menus Grid Manager Menu Overview...
  • Page 142 Grid Manager Menu Overview...
  • Page 143 Grid Manager Menu Overview...
  • Page 144 Grid Manager Menu Overview...
  • Page 145 Presentation Utility Screen Figure 4-2 Typical Presentation Utility Screen SP Status SP Identifier SP Loop ID Presentation Utility Screen...

  • Page 146: System Status

    Serial Number Heartbeat ONTROL ONTROL Fault Field  System Status Microcode Revision 9.45.04 Statistics Logging 4-10 Presentation Utility Screen...
  • Page 147 Peer SP Requests Completed Cache States Disk Module Status Presentation Utility Screen 4-11...
  • Page 148 Table 4-1 Disk Module Status Codes Code Disk module status BIN n Binding – being bound into a logical disk unit (LUN). No other configuration functions can be performed while disks are being bound. ENA n Enabled (disk module is part of a bound LUN that is owned by this SP). If the disk array has another SP, this module's box is marked RDY on that SP's display.
  • Page 149 PROM Revision Power Supply Unit (VSC x) Presentation Utility Screen 4-13...
  • Page 150 , BDP , UDP 4-14 Presentation Utility Screen...
  • Page 151 Moving the Grid Cursor ETURN Table 4-2 Cursor Movement Keys Function H, h, or left arrow Moves cursor left one box. J, j, or down arrow Moves cursor down one box. K, k, or up arrow Moves cursor up one box. L, l, or right arrow Moves cursor right one box.
  • Page 152 Disabling and Enabling the SP ETURN Â Â Figure 4-3 Disabling and Enabling an SP Caution Never disable both SPs at the same time because data can be lost. 4-16 Disabling and Enabling the SP...
  • Page 153 Creating Logical Disk Units (LUNs) Preparing to Create Logical Disk Units Binding Disk Modules as Logical Disk Units Creating Logical Disk Units (LUNs) 4-17...
  • Page 154 Table 4-3 Restrictions and Recommendations for Binding Disks into LUNs Group to bind Restrictions and recommendations Any group Only unbound (UNB) disk modules can be bound. If you attempt to bind a module that is binding (BIN), Grid Manager displays an error message. All disk modules in a group must be of the same type and same capacity to use the modules’...
  • Page 155 ETURN ETURN Figure 4-4 Bind Logical Units Menu Creating Logical Disk Units (LUNs) 4-19...
  • Page 156 ETURN ETURN Figure 4-5 Grid for Binding LUNs ETURN Note To unselect a selected disk, highlight the disk and press R ETURN ETURN 4-20 Creating Logical Disk Units (LUNs)
  • Page 157 Logical Unit Number (LUN) Note The operating system recognizes LUNs 0 through 7 only. Maximum Rebuild Time Sectors per Stripe Element Enable Caches (LUN Cache) Creating Logical Disk Units (LUNs) 4-21...
  • Page 158 Note To change the disk(s) bind options, answer N to the “Confirm bind options (Y/N)?” and then reselect bind options. To reselect different disks to bind, answer Y to the question. Answering Y does not start the binding process. ETURN ETURN 4-22 Creating Logical Disk Units (LUNs)
  • Page 159 Table 4-4 Bind Options for Different Types of Logical Disk Units Logical disk unit type Bind options Recommendations RAID-5 Logical unit number Default Maximum rebuild time Default Sectors per stripe element Default Enable caches* Both RAID-3 Logical unit number Default Maximum rebuild time Default RAID-3 SP memory...
  • Page 160 Unbinding a Logical Disk Unit (LUN) Caution Unbinding a LUN destroys all information on it. An unbound disk module cannot be used until it is bound into a LUN so the operating system can access it. All data on the disk modules is lost when LUNs are unbound.
  • Page 161 Figure 4-6 Unbinding a LUN ETURN Unbinding a Logical Disk Unit (LUN) 4-25...
  • Page 162 Specifying Storage System Memory Configuration Table 4-5 Memory Configuration Values 64 MB 32 MB 16 MB 8 MB Total physical memory System buffer size 4 MB 4 MB 4 MB 4 MB Write cache size 40 MB 18 MB 8 MB 2 MB Read cache size 20 MB...
  • Page 163 Figure 4-7 Change Storage System Memory Configuration Screen (No RAID-3 LUNs Present) Specifying Storage System Memory Configuration 4-27...
  • Page 164 Configuring SP Memory for RAID-3 LUNs To Allocate SP Memory for Use by All RAID-3 Groups   4-28 Configuring SP Memory for RAID-3 LUNs...
  • Page 165 Caution If the array reboots, data on the array will be unavailable to the host system until the reboot process completes. Figure 4-8 Change Storage System Memory Configuration Screen (RAID-3 LUNs Present) Configuring SP Memory for RAID-3 LUNs 4-29...
  • Page 166 To Bind RAID-3 LUNs and Assign SP Memory to Each RAID-3 LUN ETURN ETURN ETURN ETURN ETURN 4-30 Configuring SP Memory for RAID-3 LUNs...
  • Page 167 Setting Up Disk Array Caching Table 4-6 SIMM Sizes for the Disk Array SIMM sizes 8 MB 4 x 4 MB (4 A3235A SIMMs) 16 MB 8 x 4 MB (8 A3235A SIMMs) 32 MB 4 x 16 MB (4 A3234A SIMMs) 64 MB 8 x 16 MB (8 A3234A SIMMs) Setting Up Disk Array Caching...
  • Page 168 Disabling and Enabling Disk Array Caching To Disable or Enable Disk Array Caching   Figure 4-9 Change Storage System Cache Parameters Screen – Enable 4-32 Setting Up Disk Array Caching...
  • Page 169 Setting Up Disk Array Caching 4-33...
  • Page 170 Specifying Cache Page Size and Cache Size 4-34 Setting Up Disk Array Caching...
  • Page 171 To Specify Disk Array Caching Parameters   Figure 4-10 Change Storage System Cache Parameters Screen – Disable ETURN Setting Up Disk Array Caching 4-35...
  • Page 172 4-36 Setting Up Disk Array Caching...
  • Page 173 5 Host-Based Support Tools...
  • Page 174 Overview Overview...
  • Page 175 Support Tools Manager (STM) Table 5-1 STM Interfaces Interface name Intended environment Invoking command xstm X Windows terminals and workstations /usr/sbin/xstm mstm Menu-based, for non-graphics terminals /usr/sbin/mstm cstm Command line, for use in scripts /usr/sbin/cstm Support Tools Manager (STM)
  • Page 176 xstm Interface Table 5-2 Available Support Tools Support Tool license required? Tool type Description Information Provides quick access to the most useful information. Firmware Update Updates SP microcode and disk module firmware. Expert Provides low-level access to the disk array for configuration and troubleshooting.
  • Page 177 Â Â Â Â Â Â Figure 5-1 Information Tool Menu Options Support Tools Manager (STM)
  • Page 178 Figure 5-2 Information Log Screen, Map Section Support Tools Manager (STM)
  • Page 179 Table 5-3 xstm Status Fields for the Information Log Status field values Description This SP ID, hard address, loop ID, and SP model of this SP Peer SP ID, hard address, and loop ID of peer SP Serial # Serial number of the disk array FAULT DETECTED Displayed only if the SP reports a disk array fault (the Information Tool completion status will be set to Information...
  • Page 180 Table 5-4 Disk State for the Map in the Information Log Status Field Description Values blank removed powering up unbound ready rebuilding enabled binding formatting equalizing (with a hot spare) unsupported Table 5-5 LUN Bind State for the Map in the Information Log Status Field Description Values...
  • Page 181 Figure 5-3 Information Log Screen, Configuration Section Support Tools Manager (STM)
  • Page 182 Figure 5-4 Information Log Screen, Disks Section 5-10 Support Tools Manager (STM)
  • Page 183   Figure 5-5 Activity Log Screen   Support Tools Manager (STM) 5-11...

  • Page 184: Firmware Update Tool

    Firmware Update Tool   Figure 5-6 Firmware Update Tool Top-Level Menu 5-12 Support Tools Manager (STM)
  • Page 185 Table 5-6 Firmware Update Tool Menu Items and Descriptions Menu Item Option Property Description Select File... filename Specifies the microcode or firmware file to be used. Save As... filename Saves a file using a user-specified name. File Print... Prints a file. Exit...
  • Page 186 Listing Microcode and Firmware Revisions  Figure 5-7 Current Revisions Display Updating Microcode and Firmware 5-14 Support Tools Manager (STM)
  • Page 187 SP Microcode Updates Disk Module Firmware Updates Caution Never reenable a peer SP while a disk module firmware update operation is in progress. Doing so can interrupt the operation, causing permanent disk module and/or data loss. Expert Tool   Support Tools Manager (STM) 5-15...
  • Page 188 Figure 5-8 Expert Tool Top-Level Menu 5-16 Support Tools Manager (STM)
  • Page 189 Table 5-7 Expert Tool Menus and Descriptions Menu Items Option Property Description Save As Saves the contents of main STM window to a file. File Print Prints the contents of main STM window. Exit Exits the Expert Tool. Event Codes: All Displays Unsolicited Event Log information for the SP to which the command is issued.
  • Page 190 Table 5-7 Expert Tool Menus and Descriptions (Continued) Menu Items Option Property Description Bind LUN Binds selected disk modules into a LUN with a specified RAID level. Unbind LUNs Unbinds a LUN. Auto-assign Enables or disables the auto-assign state of a LUN.
  • Page 191 Info  Capacity  Figure 5-9 Info Capacity Screen Info  Inquiry  Figure 5-10 Info Inquiry Screen Support Tools Manager (STM) 5-19...
  • Page 192 I/O  Read Disks   Figure 5-11 I/O Read Disks Screen 5-20 Support Tools Manager (STM)
  • Page 193  Figure 5-12 I/O Read Disks, Select Blocks Screen  Figure 5-13 I/O Read Disks Output Screen Support Tools Manager (STM) 5-21...
  • Page 194 I/O  Read LUNs   Figure 5-14 I/O Read LUNs Screen 5-22 Support Tools Manager (STM)
  • Page 195  Figure 5-15 I/O Read LUNs, Select Blocks Screen  Figure 5-16 I/O Read LUNs Output Screen Support Tools Manager (STM) 5-23...
  • Page 196 Tests  Test Unit Ready Figure 5-17 Test Unit Ready Screen 5-24 Support Tools Manager (STM)
  • Page 197 Tests  Verify Disks   Figure 5-18 Tests Verify Disks Screen Support Tools Manager (STM) 5-25...
  • Page 198 Â Figure 5-19 Tests Verify Disks, Select Blocks Screen 5-26 Support Tools Manager (STM)
  • Page 199 Tests  Verify LUNs   Figure 5-20 Tests Verify LUNs Screen Support Tools Manager (STM) 5-27...
  • Page 200 Â Figure 5-21 Tests Verify LUNs, Select Blocks Screen 5-28 Support Tools Manager (STM)
  • Page 201 Utilities  System Configuration  Host I/F Settings   Figure 5-22 Utilities System Configuration Host I/F Settings Screen Support Tools Manager (STM) 5-29...
  • Page 202 Utilities  System Configuration  System Cache   Figure 5-23 Utilities System Configuration System Cache Screen 5-30 Support Tools Manager (STM)
  • Page 203 Utilities  System Configuration  System Memory   Figure 5-24 Utilities System Configuration System Memory Screen mstm Interface Support Tools Manager (STM) 5-31...
  • Page 204 Table 5-8 Available Support Tools Support Tool license required? Tool type Description Information Provides quick access to the most useful information. Firmware Update Updates SP microcode and disk module firmware. Expert Provides low-level access to the disk array for configuration and troubleshooting.
  • Page 205 Â Â Â Â Â Â Figure 5-25 mstm Device Map and Menu Support Tools Manager (STM) 5-33...
  • Page 206 Figure 5-26 Information Log Screen, Map Section Table 5-9 mstm Status Fields for the Information Log Status field values Description This SP ID, hard address, loop ID, and SP model of this SP Peer SP ID, hard address, and loop ID of peer SP Serial # Serial number of the disk array FAULT DETECTED...
  • Page 207 Table 5-9 mstm Status Fields for the Information Log Status field values Description Read Physical memory reserved for reads and status Write Physical memory reserved for writes and status Firmware Rev SP firmware revision Microcode Rev SP microcode revision Prom Rev Levl PROM revision level Auto-Trespass Auto-trespass setting...
  • Page 208 Table 5-11 LUN Bind State for the Map in the Information Log Status Field Description Values blank disk is unbound disk is bound to a RAID-1 LUN disk is bound to a RAID-3 LUN disk is bound to a RAID-5 LUN R-10 disk is bound to a RAID-1/0 LUN disk is bound to a hot spare LUN...
  • Page 209 Figure 5-28 Information Log Screen, Disks Section   Support Tools Manager (STM) 5-37...
  • Page 210 Figure 5-29 Activity Log Screen   Firmware Update Tool   5-38 Support Tools Manager (STM)
  • Page 211 Figure 5-30 Firmware Update Tool Top-Level Menu Table 5-12 Firmware Update Tool Menu Items and Descriptions Menu Item Option Property Description File Select File... filename Specifies the microcode or firmware file to be used. Save As... filename Saves a file using a user-specified name. Print...
  • Page 212 Table 5-12 Firmware Update Tool Menu Items and Descriptions Menu Item Option Property Description Update Controller Download, Downloads microcode to the disk array’s database Firmware update PROM drives, burns PROM code contained in the download and restart file to the SP’s PROMs, and restarts the SP using the controllers new microcode.
  • Page 213 Listing Microcode and Firmware Revisions  Figure 5-31 Current Revisions Display Updating Microcode and Firmware Support Tools Manager (STM) 5-41...
  • Page 214 SP Microcode Updates Disk Module Firmware Updates Caution Never reenable a peer SP while a disk module firmware update operation is in progress. Doing so can interrupt the operation, causing permanent disk module and/or data loss. Exclusive access is required to download disk firmware. All file systems should be deactivated while updating disk firmware.
  • Page 215 Â Â Figure 5-32 Expert Tool Top-Level Menu Table 5-13 Expert Tool Menus and Descriptions Menu Items Option Property Description File Save As Saves the contents of main STM window to a file. Print Prints the contents of main STM window. Exit Exits the Expert Tool.
  • Page 216 Table 5-13 Expert Tool Menus and Descriptions (Continued) Menu Items Option Property Description Logs View Unsolicited Log Event Codes: All Displays Unsolicited Event Log information for the SP to which the command is issued. Event Codes >= 0x800 (Note that the log can be saved to a file, and Event Codes >= 0x900 further filtering can then be done using HP-UX commands such as grep.)
  • Page 217 Table 5-13 Expert Tool Menus and Descriptions (Continued) Menu Items Option Property Description Bind LUN Binds selected disk modules into a LUN with a specified RAID level. Unbind LUNs Unbinds a LUN. Auto-assign Enables or disables the auto-assign state of a LUN.
  • Page 218 Selected Expert Tool Screens Info  Capacity  Figure 5-33 Info Capacity Screen Info  Inquiry  Figure 5-34 Info Inquiry Screen 5-46 Support Tools Manager (STM)
  • Page 219 I/O  Read Disks   Figure 5-35 I/O Read Disks Screen Support Tools Manager (STM) 5-47...
  • Page 220  Figure 5-36 I/O Read Disks, Select Blocks Screen  Figure 5-37 I/O Read Disks Output Screen 5-48 Support Tools Manager (STM)
  • Page 221 I/O  Read LUNs   Figure 5-38 I/O Read LUNs Screen Support Tools Manager (STM) 5-49...
  • Page 222  Figure 5-39 I/O Read LUNs, Select Blocks Screen  Figure 5-40 I/O Read LUNs Output Screen 5-50 Support Tools Manager (STM)
  • Page 223 Tests  Test Unit Ready Figure 5-41 Test Unit Ready Screen Support Tools Manager (STM) 5-51...
  • Page 224 Tests  Verify Disks   Figure 5-42 Tests Verify Disks Screen 5-52 Support Tools Manager (STM)
  • Page 225 Â Figure 5-43 Tests Verify Disks, Select Blocks Screen Support Tools Manager (STM) 5-53...
  • Page 226 Tests  Verify LUNs   Figure 5-44 Tests Verify LUNs Screen 5-54 Support Tools Manager (STM)
  • Page 227  Figure 5-45 Tests Verify LUNs, Select Blocks Screen Utilities  System Configuration  Host I/F Settings   Figure 5-46 Utilities System Configuration Host I/F Settings Screen Support Tools Manager (STM) 5-55...
  • Page 228 Utilities  System Configuration  System Cache   Figure 5-47 Utilities System Configuration System Cache Screen 5-56 Support Tools Manager (STM)
  • Page 229 Utilities  System Configuration  System Memory   Figure 5-48 Utilities System Configuration System Memory Screen Support Tools Manager (STM) 5-57...
  • Page 230 System Administration Manager (SAM) The SAM Interface 5-58 System Administration Manager (SAM)
  • Page 231 Viewing Disk Array Status Figure 5-49 Disk and File Systems Screen, View More Information Selection System Administration Manager (SAM) 5-59...
  • Page 232 Figure 5-50 View Array Status Information Screen – Front Tab 5-60 System Administration Manager (SAM)
  • Page 233 Figure 5-51 View Array Status Information Screen – Back Tab System Administration Manager (SAM) 5-61...
  • Page 234 Binding a LUN Â Â Figure 5-52 Disk and File Systems Screen, Bind LUN Selection 5-62 System Administration Manager (SAM)
  • Page 235 Figure 5-53 Bind LUN Screen System Administration Manager (SAM) 5-63...
  • Page 236 Unbinding a LUN Â Â Figure 5-54 Disk and File Systems Screen, Unbind LUN Selection 5-64 System Administration Manager (SAM)
  • Page 237 Figure 5-55 Unbind LUN Confirmation Screen Creating a Volume Group with an Alternate Path LUN Ownership and Auto-Trespass Primary and Alternate Paths System Administration Manager (SAM) 5-65...
  • Page 238 Ioscan Output Note The disk array is shipped from the factory with auto-trespass enabled. Under normal operating conditions in HP-UX environments, auto-trespass should remain enabled on disk arrays with two SPs. 5-66 System Administration Manager (SAM)
  • Page 239 Figure 5-56 Ioscan Output with Auto-Trespass Enabled System Administration Manager (SAM) 5-67...
  • Page 240 Figure 5-57 Creating or Extending a Volume Group Using LVM 5-68 System Administration Manager (SAM)
  • Page 241 Enabling / Disabling LUN Cache   Figure 5-58 Disk and File Systems Screen, Change Caching Parameters Selection System Administration Manager (SAM) 5-69...
  • Page 242 Figure 5-59 Change Caching Parameters Screen 5-70 System Administration Manager (SAM)
  • Page 243 Hardware Event Monitoring http://www.docs.hp.com/hpux/systems/ Setting Up the Hardware Event Monitor Hardware Event Monitoring 5-71...
  • Page 244 High Availability Array Monitor (HARAYMON) HARAYMON Configuration # This is the configuration file for pharaymon_exec. # Set the second parameter in the three lines below to configure the specified # notification mechanism (console messages, system logs, or email, respectively # to “on” or “off”. Set the third parameter in the “mail” line to specify the # recipient of HARAYMON email.
  • Page 245 HARAYMON Messages ======================================== High Availability Array Monitor Reported on: Thu Jan 9 11:24:47 1997 ---------------------------------------- Unit Shutdown: Disk C5 Reported by: Physical Device: 8/8.8.0.255.0.0.2 Product ID: DGCC3400WDR5 ======================================== ======================================== High Availability Array Monitor Reported on: Thu Jan 9 11:26:07 1997 ---------------------------------------- BBU Removed Reported by:...
  • Page 246 Note It is important to be aware of the distinction between the occurrence of a failure and the reporting of that failure. A disk array component failure is reported immediately to the disk array. The disk array, in turn, notifies the system of this event when the next I/O is attempted to any disk array component .
  • Page 247 Running HARAYMON High Availability Array Monitor (HARAYMON) 5-75...
  • Page 248 5-76 High Availability Array Monitor (HARAYMON)

  • Page 249: Troubleshooting

    Troubleshooting...
  • Page 250 About Replaceable Components Table 6-1 Disk Array FRUs Field- Customer- replaceable replaceable Component (FRU) (CRU) Hot-replaceable Disk module Fan pack Power supply unit Yes, if three power supply units installed SIMM Yes, if dual SPs Yes, if dual SPs About Replaceable Components...
  • Page 251 Caution Because the disk array incorporates redundant design features, it does not have to be powered down while replacing disk modules, SPs, or BBUs. The fan pack and power supply units are also hot-replaceable but removal and replacement must be completed within two minutes or the disk array will report an overtemperature fault and shut down.
  • Page 252 Disk Array Chassis interface SP-A SP-B Power extender supply pack On/Off switch Figure 6-1 FRU Locations Disk Array Chassis...
  • Page 253 Disk Array Front-View LEDs Front of storage system System System power LED service LED (green) (amber) Disk module LEDs Ready LED (green) Busy LED (green) A0 B0 C0 D0 B3 C3 D3 Fault LED (amber) A1 B1 C1 D1 B4 C4 D4 A2 B2 C2 D2 B5 C5 D5 Figure 6-2 Front LED Locations...
  • Page 254 Disk Array Rear-View LEDs Back of storage system SP LEDs Ready LED (green) Service LED (amber) BBU LEDs Replace LED (amber) VSC LEDs Ready LED (green) Replace LED (amber) Fan module Figure 6-3 Rear LED Locations Disk Array Chassis...
  • Page 255 Table 6-2 Disk Array LEDs Array condition when LED is on Array condition when LED is off Array Front Panel Power supply units are operating Disk array is powered off or, if it has POWER-ON (green) and providing power to the midplane been running, has lost the +24 VDC +24 VDC bus.

  • Page 256: Power-Up Troubleshooting

    Power-Up Troubleshooting Figure 6-4 Disk Array Power-Up Screen Output Power-Up Troubleshooting...
  • Page 257 Table 6-3 Disk Array Power-Up Tests Test ID Test description Append Error Messages Mode AM79C970 Ethernet Controller (AM79C970) Tests (DIR) Clear Error Messages Configuration Editor CL1283 Parallel Interface (CL1283) Tests (DIR) CS4231 cs4231 Audio Codec (DIR) Display Errors DEC21040 Ethernet Controller (DEC21040) Tests Display Error Messages Display Pass Count Help on Tests/Commands...
  • Page 258 Table 6-3 Disk Array Power-Up Tests (Continued) Test ID Test description Quick Self Test (DIR) Random Access Memory Tests (DIR) MK48T0x Timekeeping (DIR) Serial Communication Controller (Z85C230) Tests (DIR) Stop on Error Mode SRAM Static Random Access Memory Tests (DIR) Self Test (DIR) TACH Tachyon Fibre Channel I/O Processor Tests (DIR)
  • Page 259 Table 6-4 Power-Up Troubleshooting Condition and/or symptom Solution Power-up tests fail Inserting a FRU while the power-up tests are running can cause the tests to fail. Insert all FRUs and then cycle power to rerun the power-up tests. No CRU LEDs are on and the fans are Indicates no AC power is reaching the disk array’s power not running supply unit(s).
  • Page 260 Checking the Status of the Fibre Channel Link Class H/W Path Driver S/W State H/W Type Description =============================================================== 8/4.5 fcT1_cntl CLAIMED INTERFACE HP Fibre Channel Mass Storage Cntl 8/8.5 fcT1_cntl CLAIMED INTERFACE HP Fibre Channel Mass Storage Cntl 6-12 Power-Up Troubleshooting...
  • Page 261 Local N_Port_ID is 0x000001 N_Port Node World Wide Name 0x1000080009F608B9 N_Port Port World Wide Name 0x1000080009F608B9 Topology IN_LOOP Speed 1062500000 (bps) HPA of card 0xFFB44000 EIM of card 0xFFFA000D Driver state READY Number of EDB’s in use Number of OIB’s in use Number of Active Outbound Exchanges Number of Active Login Sessions Power-Up Troubleshooting...
  • Page 262 Troubleshooting the Disk Array Disk Module Troubleshooting Overview 6-14 Troubleshooting the Disk Array...
  • Page 263 Identifying Logical Disk Units and Disk Module Failures Figure 6-5 Presentation Utility Screen Showing Disk Module Configurations ETURN Troubleshooting the Disk Array 6-15...
  • Page 264 Figure 6-6 Performance Statistics for a Failed Disk Module Table 6-5 Sense Key, Additional Sense Code, and Additional Sense Code Qualifier Values (Not a Comprehensive List) Sense key Description 0x00 - No Sense 00/00/00 There is no sense information to return at this time for this LUN. 0x01 - Recovered Error The SP is returning an Unsolicited Sense Block to the host.
  • Page 265 Table 6-5 Sense Key, Additional Sense Code, and Additional Sense Code Qualifier Values (Not a Comprehensive List) (Continued) Sense key Description 0x02 - Not Ready 02/04/00 Logical unit not ready. Cause not reportable. 02/04/01 The LUN is reporting that it is becoming ready (performing an Assign). The initiator (host) should retry after a short time interval (such as 500ms).
  • Page 266 Table 6-5 Sense Key, Additional Sense Code, and Additional Sense Code Qualifier Values (Not a Comprehensive List) (Continued) Sense key Description 05/25/01 This LUN is a global hot spare. This LUN cannot be accessed for data operations by the host. 05/26/02 A parameter was set to an invalid value, for example, a nonchangeable field was changed on a Mode Select.
  • Page 267 Table 6-5 Sense Key, Additional Sense Code, and Additional Sense Code Qualifier Values (Not a Comprehensive List) (Continued) Sense key Description 0B/4E/00 The LUN has encountered an “Incorrect Initiator Connection.” Examples include receiving two CDBs for the same I_T_L_Q nexus, or the mixing of tagged and untagged CDBs for a given I_T_L_Q nexus (with no outstanding Contingent Allegiance).
  • Page 268 Obtaining Additional Disk Failure Information with Grid Manager Global Hot Spares and Rebuilds SP Troubleshooting 6-20 Troubleshooting the Disk Array...
  • Page 269 Table 6-6 SP Troubleshooting Condition and/or symptom Solution No LEDs illuminated on SP Firmly seat the SP in the disk array chassis. SP READY LED illuminated but, no Check the SP connector for damage. Check the FC-AL hub, host response from SP Fibre Channel I/O adapter, and Fibre Channel cables for damage.
  • Page 270 SIMM Size (MB) SIMM Pair SIMM Pair Total Memory Crossover Address 0x00800000 0x02000000 0x02000000 0x02000000 6-22 Troubleshooting the Disk Array...
  • Page 271 Note Only cache sizes of 8, 16, 32, and 64 MB are supported because Hewlett-Packard does not ship any other cache sizes as an option. A cache size of 40 MB will work as long as the SIMM installation guidelines are meet.

  • Page 272: Configuring Cache

    Configuring Cache   ETURN   6-24 Configuring Cache...
  • Page 273 Â Â Â Â Configuring Cache 6-25...
  • Page 274 Configuring SP memory for RAID-3 To Allocate SP Memory for Use by All RAID-3 Groups   6-26 Configuring SP memory for RAID-3...
  • Page 275 Figure 6-7 Change Storage System Memory Configuration Screen Configuring SP memory for RAID-3 6-27...
  • Page 276 To Bind RAID-3 LUNs and Assign SP Memory to Each RAID-3 LUN NTER NTER NTER NTER NTER Caution Unbinding a LUN causes all data on all the disk modules in the LUN to be lost. 6-28 Configuring SP memory for RAID-3...

  • Page 277: Viewing Maintenance Information

    Viewing Maintenance Information Display Unsolicited Event Log  Viewing Maintenance Information 6-29...
  • Page 278 Figure 6-8 Grid Manager Unsolicited Event Log Display Faulted CRUs  6-30 Viewing Maintenance Information...
  • Page 279 Figure 6-9 Faulted CRU Display Screen Display Verify Results  Viewing Maintenance Information 6-31...
  • Page 280 Figure 6-10 First Report Page for a Unit Verify Field Description State Indicates that a Verify or Sniff is currently running. Sniffing Indicates whether this feature is Enabled or Disabled. % Complete Indicates the completion percentage of the operation (0 to 100). 6-32 Viewing Maintenance Information...
  • Page 281 Field Description Sniff Period To set the sniff period, from the Grid Manager main menu follow the menu   6. path: 5. Change Parameters 1. Change Logical Unit Parameters Change Unit Verify Configuration. Passes Indicates the total number of verify operations that have been performed. Applies only to the first and fourth page reports “Historical Totals.”...
  • Page 282 Figure 6-11 LUN Configuration Screen Action N or n Moves to the next screen (there are additional screens if there are more LUNs than will fit onto one screen). P or p Moves to the previous screen. R or r Refreshes the screen contents to reflect the current state of the disk array.
  • Page 283 Unsolicited Event Log SP A Display Unsolicited Event Log SP ALPA ID 0 Event Date Event (message) Extended Status 1. 01/26/97 13:59:10 VSCA 0x904 (VSC Shutdown/removed) 0x00 2. 01/26/97 15:01:02 0xa07 (CRU Powered down) 0x00 3. 01/26/97 15:01:23 0x906 (Unit shutdown) 0x00 4.
  • Page 284 Controlling the Display of Event Records Action N or n Scrolls to the next screen of entries. P or p Scrolls to the previous screen of entries. F or f Displays the first screen of entries. L or l Displays the last screen of entries. A or a Defines a filter to select event types by FRU or error code.
  • Page 285 To Add a Filter Figure 6-13 Apply Filters Menu ETURN Unsolicited Event Log 6-37...
  • Page 286 Note Filter(s) are active until deleted or until the disk array is powered down. If the Unsolicited Event Log listing seems short, one or more filters may be active. Try deleting all filters, as explained next. To Delete All Filters of One Type ETURN SP Event Codes 6-38...
  • Page 287 Table 6-8 Informational Codes Event code Event code name Description 0x601 SP Power Up The SP is powered up and ready for I/O. This field also shows the revision of microcode (Licensed Internal Code) and the amount of SP memory in MB, in hexadecimal. For example, (SP Powerup);...
  • Page 288 Table 6-8 Informational Codes (Continued) Event code Event code name Description 0x621 Background Verify A background check on the correctness of parity information Started has begun on the physical unit of which this drive is a member. 0x622 Background Verify A background checkpoint verification of the accuracy and Complete completeness of the parity check data in a RAID-5, RAID-3,...
  • Page 289 Table 6-8 Informational Codes (Continued) Event code Event code name Description 0x645 CRU Bound Extended status identifies unit number. This message is logged once for each CRU in a LUN at the completion of a Bind operation. 0x646 CRU Unbound Extended status identifies unit number.
  • Page 290 0x66C General Front End Fibre This event code is intended for use by development personnel Link Unsolicited in the factory. Contact your Hewlett-Packard support representative if this event code occurs. 0x66D Peer SP timed out The host SP has timed out waiting for the peer SP to reply to a request.
  • Page 291 Table 6-8 Informational Codes (Continued) Event code Event code name Description 0x689 Sector Reconstructed On a read from a RAID-1 mirrored pair, a corrupted sector was reconstructed. 0x68A Uncorrectable Parity A hard error on a parity sector could not be corrected. Sector 0x68B Uncorrectable Data...
  • Page 292 Table 6-8 Informational Codes (Continued) Event code Event code name Description 0x6E2 Front End Fibre Loop The SP’s fibre loop failed to initialize. Error 0x6E3 Fibre Channel Initiator The SP tried to communicate with an initiator that is no longer Gone responding.
  • Page 293 Table 6-9 Thresholded (Soft) Codes (Continued) Recommended Event code Event code name Description threshold 0x805 Single Bit Error The SP’s tolerance level for single bit errors in the read cache has been exceeded. 0x820 Soft Media Error The SP successfully cleared a disk Notify the user after three media defect.
  • Page 294 Table 6-10 Error Codes Event code Event code name Description 0x901 Hard SCSI Error An abnormal SCSI bus or disk drive event was detected and could not be cleared through retry operations. 0x903 Fan Removed A fan pack has been shut down or removed from the system. 0x904 VSC Removed A VSC (power supply unit) has been shut down or removed...
  • Page 295 Table 6-10 Error Codes (Continued) Event code Event code name Description 0x910 Cache Recovery Failed A nonmirrored cache recovery was attempted but failed to recover information for any cached LUNs. It does not apply to a disk array with two SPs. 0x920 Hard Media Error This disk module has reported a media defect that could not...
  • Page 296 Table 6-11 Fatal Error Codes Event code Event code name Description 0xA02 Failed SCSI Bus An internal SCSI bus failed and all disk modules on that bus are inaccessible by the SP. The CRU number displayed corresponds to the bus number. The failure resulted from a bad cable or cable connection, bad terminator, bad SCSI chip on an SP or a bad device.
  • Page 297 Decoding Extended Status Codes Unsolicited Event Log 6-49...
  • Page 298 Table 6-12 Extended Status Codes Extended Extended status code status code name Description 0x00 None No error information available. 0x01 SCSI protocol error An error was detected and retried during activity on an internal SCSI bus between the SP and the disk itself. 0x02 Device detected parity error Drive returned sense data indicating data sourced at the SCSI interface device on the SP encountered an internal parity...
  • Page 299 Table 6-12 Extended Status Codes (Continued) Extended Extended status code status code name Description 0x10 Unit attention The drive reported an unexpected unit attention with unrecognized sense data. This code should never be seen. 0x11 Device aborted command The disk did not complete a command issued by SP microcode.
  • Page 300 Table 6-12 Extended Status Codes (Continued) Extended Extended status code status code name Description 0x28 Spindle synchronization This error code should never be seen. change 0x29 Not ready/start in progress This error code should never be seen. 0x2A Transfer count not zero Too few bytes were transferred by a drive during an I/O operation.
  • Page 301 Table 6-12 Extended Status Codes (Continued) Extended Extended status code status code name Description 0x3E Media error remap failed An attempt to do a remap after a Media error failed for some reason other than one of the following: another media error, a timeout, cannot remap (no LBA provided), or bad defect list.
  • Page 302 Microcode Panics 6-54 Unsolicited Event Log...
  • Page 303 Table 6-13 Microcode Panic Categories Value Category 0x0000nnnn Kernel services 0x0010nnnn Disk management, upper level 0x0022nnnn Host read/write request management 0x0024nnnn Host nonread/write request management 0x0025nnnn Unsolicited log management 0x0026nnnn Grid Manager interface 0x0028nnnn RAID services management 0x0030nnnn Memory management 0x0040nnnn Disk management, lower level 0x0050nnnn...
  • Page 304 0x00000008 with an extended status of 0x00000003. All known causes of this panic have been fixed. If this panic occurs, obtain a memory dump and Unsolicited Event Log from both SPs and give them to your Hewlett-Packard service representative. 0x0000000A Memory exhausted.
  • Page 305 Table 6-14 Most Common Microcode Panic Codes (Continued) Value Description 0x00000015 Memory exhausted. 0x00000016 Memory exhausted. 0x00100006 Degraded LUN experiencing heavy I/O. Reported on a very large, degraded RAID-5 LUN (usually with more than eight disks) under heavy I/O conditions. Fixed in microcode revision 8.09.
  • Page 306 9.x4 and later. If this panic occurs obtain a memory dump and Unsolicited Event Logs from both SPs and give them to your Hewlett-Packard service representative for failure analysis. 6-58...
  • Page 307 Table 6-14 Most Common Microcode Panic Codes (Continued) Value Description 0x00240010 SCSI protocol problems. The microcode panics 0x00A000B0, 0x00240010, and 0x00220050 occurred in SCSI environments that have severe SCSI protocol problems due to improperly working initiators or noisy conditions. Fixed in microcode revisions 8.27, 8.58, and 9.04.
  • Page 308 PROM code flash operation. Microcode 9.x5 fixes all known occurrences of this panic. If this panic occurs with the latest release of microcode, obtain the Unsolicited Event Logs from both SPs and the memory dump, and give them to your Hewlett-Packard service representative for failure analysis. 0x0080007E Incorrect state reported by peer.
  • Page 309 Table 6-14 Most Common Microcode Panic Codes (Continued) Value Description 0x00A00006 Retry stamp panic. On very large “no disconnect transfers” (>512 blocks) the microcode would panic. Fixed in microcode revision 7.61. 0x00A00016 SCSI errors. SCSI errors on the host SCSI bus might cause the microcode to panic with a 0x00A00016 or 0x00A00047 code.
  • Page 310 Table 6-14 Most Common Microcode Panic Codes (Continued) Value Description 0x00E00000 I/O from cache and firmware timing issue. The microcode would occasionally panic with a 0x00E00000/0x00E0000C code during normal operating conditions. The panic was a result of communication problems between the two SPs in a mirrored caching array.
  • Page 311 Troubleshooting with Grid Manager Checking Disk Array Status with the Presentation Utility ETURN Figure 6-14 Typical Presentation Utility Screen Troubleshooting with Grid Manager 6-63...
  • Page 312 Bound but Not Assigned Status after Replacing an SP ETURN Figure 6-15 Disk State Looking from Owning SP 6-64 Troubleshooting with Grid Manager...
  • Page 313 Figure 6-16 Disk State Looking from Non-Owning SP Â Â ETURN Troubleshooting with Grid Manager 6-65...
  • Page 314 6-66 Troubleshooting with Grid Manager...
  • Page 315 Troubleshooting with SAM View Disk Array Status Troubleshooting with SAM 6-67...
  • Page 316 Figure 6-17 Disk and File Systems Screen, View More Information Selection 6-68 Troubleshooting with SAM...
  • Page 317 Figure 6-18 View Array Status Information Screen – Front Tab Troubleshooting with SAM 6-69...
  • Page 318 Figure 6-19. View Array Status Information Screen – Back Tab Unbinding a LUN Â Â 6-70 Troubleshooting with SAM...
  • Page 319 Figure 6-20 Disk and File Systems Screen, Unbind LUN Selection Figure 6-21 Unbind LUN Confirmation Screen Troubleshooting with SAM 6-71...

  • Page 320: Write Cache

    Caching Write Cache Read Cache Changing a LUN’s Cache Parameters 6-72 Troubleshooting with SAM...
  • Page 321 Â Â Figure 6-22 Disk and File Systems Screen, Change Caching Parameters Selection Figure 6-23 Change Caching Parameters Screen Troubleshooting with SAM 6-73...
  • Page 322 Binding a LUN Â Â Figure 6-24 Disk and File Systems Screen, Bind LUN Selection 6-74 Troubleshooting with SAM...
  • Page 323 Figure 6-25 Bind LUN Screen Troubleshooting with SAM 6-75...
  • Page 324 6-76 Troubleshooting with SAM...

  • Page 325: Removal And Replacement

    Removal and Replacement...

  • Page 326: Parts Breakdown

    Parts Breakdown Table 7-1 Customer-Replaceable Parts New HP part number Exchange part number Description 5063-5393 A3666-69021 4.2-GB LP disk module 5063-5335 A5169-69021 4.2-GB LP disk module 5063-5333 A5132-69021 8.8-GB disk module 5063-5334 A5133-69021 17.8-GB LP disk module A3231-60005 A3231-69005 A3662-60001 A3662-69101 Storage processor (SP630/FC SP) A3692-60001...
  • Page 327 Disk Module Removal and Replacement Caution NEVER remove or replace faulted disk modules when array power is OFF as data can be lost. NEVER rearrange faulted disk modules when array power is either ON or OFF as data can be lost. Handle disk modules very carefully as they can be damaged easily by shock and vibration.
  • Page 328 Note With the redundant RAID levels of RAID-5, RAID-3, RAID-1/0, and RAID-1, only one disk module should replaced at a time, and each rebuild should complete before another disk module is replaced. When using RAID-5, RAID-3, RAID-1/0, or RAID-1, a rebuild begins as soon as a disk module is replaced.
  • Page 329 Rail slot Disk module’s rail Rail slot Disk module’s ESD wrist strap rail Figure 7-2 Installing a Disk Module Disk Module Removal and Replacement...
  • Page 330 Fan Pack Removal and Replacement Caution A failed fan pack can be replaced with the disk array powered on. However, the process must be completed within two minutes to avoid a thermal shutdown of the disk array. Caution Do not lift a fan pack by its handle. Fan Pack Removal and Replacement...
  • Page 331 Replace light (amber) Lock/unlock button Figure 7-3 Fan Pack Back of storage system ac power cord Holding module at slight angle, slide it away from chassis. Be careful not to pull release power cord out of latches socket. ac power cord Figure 7-4 Removing a Fan Pack Fan Pack Removal and Replacement...
  • Page 332 Holding module at slight angle, slide it onto hinge pins. ac power cord Figure 7-5 Installing a Fan Pack Fan Pack Removal and Replacement...
  • Page 333 SP Removal and Replacement Caution Strap the ESD wrist strap to your wrist and ground it to the disk array chassis (or suitable ground). Place the SP on an ESD conductive sheet when it is removed from its carton. Use ESD kit P/N 5182-4119 (supplied with each array). SP Removal and Replacement...
  • Page 334 A. Pull both ejectors until B. Rest edge of SP on palm of they unlock and the hand, and with other hand processor board starts pull it out of chassis, making coming out of the chassis. sure not to touch any electronic components or circuits.
  • Page 335 Power Supply Unit Removal and Replacement Note The disk array will not operate with only one power supply unit. To allow hot- replacement, three power supply units must be installed. A power supply unit must be removed and replaced, and the fan pack closed again, within two minutes or the disk array will do a thermal shutdown.
  • Page 336 Fan pack removed for clarity. It is not necessary to remove the fan pack to remove the power supplies. Figure 7-8 Removing or Installing a Power Supply Unit 7-12 Power Supply Unit Removal and Replacement...
  • Page 337 BBU Removal and Replacement Caution Use caution when removing the BBU. It is very heavy. BBU Removal and Replacement 7-13...
  • Page 338 Note The BBU must be removed and installed, and the fan pack closed again, within two minutes. If the removal and replacement takes longer than two minutes, the disk array will do a thermal shutdown. Back of storage system SP B SP A Figure 7-9 Location of the BBU 7-14...
  • Page 339 Figure 7-10 Removing or Installing a BBU BBU Removal and Replacement 7-15...

  • Page 340: Battery Disposal

    Battery Disposal 7-16 BBU Removal and Replacement...
  • Page 341 In a single-SP configuration, data will be lost if the SP is not disabled and the unposted data is not written to disk before the SP is removed. In a two-SP configuration, the data is mirrored so the data is preserved. Hewlett-Packard recommends that the cache be disabled before an SP is removed.
  • Page 342 SIMM sizes 8 MB — 2 x 4 MB per SP (2 A3235A SIMMs per SP) 16 MB — 4 x 4 MB per SP (4 A3235A SIMMs per SP) 32 MB — 2 x 16 MB per SP (2 A3234A SIMMs per SP) 64 MB —...
  • Page 343 Edge of SP board Notch Pin 1 2ND PAIR connectors Memory modules in 1ST PAIR connectors Figure 7-11 SIMM Locations Locking tabs Push out on the locking tabs with your thumbs and push the module up until it is released from the tabs. Lift the module out of the connector and place it in its own anti-static packaging.
  • Page 344 A. Position memory module above connector so its notch is over connector end nearest to the SP board’s edge connector. Connector B. Insert module in connector so it angles Memory slightly toward the center of SP board. module C. Gently push top of module down until it snaps into each locking tab.
  • Page 345 Appendix Disk Array Installation/Troubleshooting Checklist Check for Physical Damage: Check Site Power: Check Site Environment: Appendix - 1...
  • Page 346 Check Fibre Optic and RS-232C Cables: Check Disk Array (Pre-Power-Up): Check Disk Array Functionality and Configuration: Appendix - 2...
  • Page 347 Required Information for Escalated Sites: Appendix - 3...
  • Page 348 Appendix - 4...
  • Page 349 Glossary Glossary - 1...
  • Page 350 Glossary - 2...
  • Page 351 Glossary - 3...
  • Page 352 Glossary - 4...
  • Page 353 Glossary - 5...
  • Page 354 Glossary - 6...
  • Page 355 Glossary - 7...
  • Page 356 Glossary - 8...
  • Page 357 Glossary - 9...
  • Page 358 Glossary - 10...
  • Page 359 Index R-11 R-3 3-10 2-13 4-14 1-10 5-65 R-4 1-3 1-15 3-12 3-17 4-2 1-50 3-13 1-2 1-10 1-18 1-49 3-12 3-17 6-24 5-18 5-45 4-14 R-2 1-10 1-20 5-18 5-45 4-32 5-69 5-18 5-45 2-2 2-3 4-32 5-69 5-18 5-45 1-3 1-5 1-6 1-20 1-13 1-14...
  • Page 360 3-13 3-19 3-23 3-15 R-12 4-28 4-30 6-26 6-28 4-21 5-45 3-12 3-15 3-10 5-59 3-11 6-14 6-22 3-10 3-18 3-12 1-22 1-24 1-25 1-40 3-13 1-5 1-6 5-17 5-19 5-44 5-46 6-20 6-49 5-15 5-42 1-34 6-15 5-17 5-19 5-44 5-46 3-19 1-8 1-10 1-36 6-21 5-17 5-20 5-44 5-47...
  • Page 361 3-22 1-12 6-63 6-66 4-24 5-72 5-75 6-12 5-73 5-73 5-75 6-12 5-71 3-10 5-71 3-10 1-24 1-26 2-19 1-16 1-44 1-46 1-15 3-8 1-20 1-17 1-36 1-15 3-8 3-10 1-3 3-10 2-14 2-12 5-12 5-15 2-12 2-14 5-38 5-42 2-15 2-17 2-17...
  • Page 362 1-3 1-16 2-2 1-50 3-10 2-18 1-17 1-22 4-21 1-16 2-15 5-65 2-12 4-17 4-23 2-15 5-62 5-18 5-45 4-18 1-20 4-21 6-72 1-20 5-17 5-19 5-44 5-46 1-44 1-32 1-39 6-15 1-17 5-17 5-19 5-44 5-46 5-11 5-32 5-38 5-65 6-39 5-17 5-21 5-23 5-44 5-48 5-50...
  • Page 363 1-24 6-16 5-75 5-3 5-31 1-22 3-15 3-20 3-18 3-14 R-11 3-15 3-15 3-12 3-15 3-14 3-20 1-3 1-5 1-6 1-12 6-2 7-11 4-13 4-13 6-10 6-11 6-13 4-15 6-63 4-10 4-11 1-10 5-65 1-50 1-29 1-40 1-8 1-10 6-21 1-17 1-22 1-25 1-29 1-32 1-37 1-43 6-22 1-25...
  • Page 364 1-24 1-49 1-50 1-44 3-14 4-2 5-2 5-58 5-70 1-22 1-29 1-40 1-22 1-35 6-74 4-30 6-28 1-20 1-37 5-65 1-39 5-69 1-9 4-28 4-30 6-26 6-28 5-69 1-40 5-58 1-25 6-67 6-75 1-23 6-70 1-22 1-32 1-39 5-64 1-37 6-67 1-32 1-39 1-3 1-5 1-9...
  • Page 365 6-2 7-9 6-20 R-11 4-32 5-18 5-30 5-45 5-56 4-26 5-18 5-31 5-45 5-57 5-45 3-22 1-8 1-35 3-14 4-2 3-12 3-14 5-2 5-3 5-57 6-21 5-18 5-45 5-18 5-45 5-17 5-23 5-44 5-50 5-18 5-45 5-18 5-45 1-22 5-18 5-45 1-20 2-2 2-3 5-45...
  • Page 366 4-24 5-64 6-70 5-18 5-45 6-35 6-38 6-37 5-17 5-44 6-20 6-36 6-38 6-46 6-49 6-48 6-36 6-38 6-54 6-55 4-13 6-15 6-38 6-38 6-44 5-17 5-44 5-15 5-42 5-15 5-42 1-13 3-4 5-17 5-25 5-44 5-52 5-17 5-26 5-28 5-44 5-53 5-55 3-22 5-65 6-72...
  • Page 367 Agree Disagree † † † † † † The manual is well organized. † † † † † † The information is technically accurate. † † † † † † Information is easy to find. † † † † † †...
  • Page 368 Fold Here Tape Please Do Not Staple Tape...
  • Page 370 *A3661-96031*...

This manual is also suitable for:

30/fc

Table of Contents