Notice Safety Notices :DUQLQJ Weight Exceeds 100 lbs. (45 kg.) Do NOT lift unassisted. Use a lift device or two people. Trademark Information...
Page 3
Format Conventions WARNING Caution Note this font Printing History...
Page 4
Service Manual Revision History Change Page Added Disk Module Behavior When Moving Disks to describe the disk module behavior change introduced with firmware release HP03. Added list of supported UPS models. Change Page Added Figure 87 to clarify operation of the write cache flush thresholds. Added note regarding the impact of LUN binding on performance.
Page 5
Change Page Updated ioscan output example to include UTM. Added information on reading older log files after installing the HP08 firmware and updated AM60 software. Change Page Removed all references to HP08 to reflect the decision to roll supported Multiple controller firmware rolled back to HP03.
Page 6
Change Page Updated information on battery life and warnings. Added section Replacing a Failed BCC Without Powering Off the Array Added instructions for verifying NVSRAM version after replacing a controller. Add section Serial Port Troubleshooting Changed battery expiration date to 38 months. Add information on waiting 5 minutes after performing a syswipe before issuing other commands.
Page 7
Change Page Added note on need to retry ammgr -b command to reset battery age. Added Healthcheck diagnostic tool. Added section Troubleshooting Sub-LUNs. Change Page Updated BBU information.
About This Book Chapter 1, Product Description Describes the features, controls, and operation of the disk array. Chapter 2, Topology and Array Planning Guidelines for designing the disk array configuration that best meets your needs. Chapter 3, Installation Instruction for moving the disk array. Chapter 4, Managing the Disk Array on Complete instructions for managing your disk array HP-UX...
Page 9
Related Documents and Information ¤ ¤ ¤ ¤ ¤ ¤ ¤ ¤...
Page 30
BCC Modules Power Supply Modules Fan Modules Disk Modules Chassis (and Backplane) (Front Door Not Shown)
Page 33
WARNING Touching exposed circuits on the disk module can damage the disk drive inside. To avoid damage, always handle disks carefully and use ESD precautions.
Page 41
Power Supply Fan Module Power Supply Module 2 Controller Chassis Controller Fan Power Supply Module 1 Controller Mo dule A Controller Mo dule B (Front Cover Not Shown)
Page 58
Note Condition 1 - Power On of Fully Charged BBU PCB# 348-0040099 Full Charge LED - OFF for approximately 15 minutes, and then ON solid PCB# 348-0038395 Full Charge LED - BLINKING for approximately 15 minutes, and then ON solid. PCB# 348-0041453 Full Charge LED - BLINKING for approximately 15 minutes, and then ON solid.
Page 59
Condition 3 - Power On of Faulted BBU (Powered on and then fault detected.) PCB# 348-0040099 Full Charge LED - Will follow conditions 1 or 2, then OFF when fault detected. PCB# 348-0038395 Full Charge LED - Will follow conditions 1 or 2, then OFF when fault detected.
Page 70
Note Handle multiple disk RAID Level Disk Striping Mirroring Parity failures? RAID 0 No. RAID 0 offers no data redundancy or protection against disk failure. RAID 0 should only be used for non- critical data. The failure of a single disk in a RAID 0 LUN will result in the loss of all data on the LUN.
Page 71
RAID Level Storage Efficiency RAID 0 100%. All disk space is use for data storage. RAID 1 and 0/1 50%. All data is duplicated, requiring twice the disk storage for a given amount of data capacity. RAID 3 and 5 One disk’s worth of capacity from each LUN is required to store parity data.
Page 72
RAID Level General Performance Characteristics RAID 0 – Simultaneous access to multiple disks increases I/O performance. In general, the greater the number of mirrored pairs, the greater the increase in performance. RAID 1 – A RAID 1 mirrored pair requires one I/O operation for a read and two I/O operations for a write, one to each disk in the pair.
Page 73
RAID level Application and I/O Pattern Performance RAID 0 RAID 0 is a good choice in the following situations: – Data protection is not critical. RAID 0 provides no data redundancy for protection against disk failure. – Useful for scratch files or other temporary data whose loss will not seriously impact system operation.
Page 76
Data and parity from the remaining disks are used to rebuild the contents of disk 3 on the hot spare disk. The information on the hot spare is copied to the replaced disk, and the hot spare is again available to protect against another disk failure.
Page 120
Failing Continue component after failure What happens and how to recover Disk module Applications continue to run on all supported RAID levels (RAID- 1, 0/1, and 5). The system administrator or service provider hot- swaps the failed disk module. Controller The disk array fails.
Page 121
Failing Continue component after failure What happens and how to recover Fibre No on path to I/O operations fail along the path through the failed cable. If the Channel failed cable; host has two Fibre Channel adapters connected to a dual- cable Yes if array has controller module disk array, the array can be accessed through...
Page 125
Failing Continue component after failure What happens and how to recover Disk module Applications continue to run on all supported RAID levels (RAID- 1, 0/1, and 5). The system administrator or service provider hot- swaps the failed disk module. Controller The disk array fails.
Page 126
Failing Continue component after failure What happens and how to recover Fibre No on path to I/O operations fail along the path through the failed adapter. If the Channel I/O failed adapter; host has two Fibre Channel adapters connected to a dual- adapter Yes if array has controller module disk array, the array can be accessed through...
Page 130
Failing Continue component after failure What happens and how to recover Disk module Applications continue to run on all supported RAID levels (RAID-1, 0/1, and 5). The system administrator or service provider hot- swaps the failed disk module. Controller No on path to Ownership of the failed controller module’s LUNs can transfer modules failed controller...
Page 131
Failing Continue component after failure What happens and how to recover Fibre No on path to I/O operations fail along the path through the failed cable. If the Channel failed cable; host has two Fibre Channel adapters connected to a dual-controller cable Yes if array has module disk array, the array can be accessed through the...
Page 135
Failing Continue component after failure What happens and how to recover Disk module Applications continue to run on all supported RAID levels (RAID- 0/1, and 5). The system administrator or service provider hot- swaps the failed disk module. Controller No on path to Ownership of the failed controller module’s LUNs can transfer modules failed controller...
Page 136
Failing Continue component after failure What happens and how to recover Fibre Channel No on path to I/O operations fail along the path through the failed cable. If the cable failed cable; host has two Fibre Channel adapters connected to a dual- Yes if array has controller module disk array, the array can be accessed through dual controller...
Page 139
Failing Continue component after failure What happens and how to recover Disk module Applications continue to run on all supported RAID levels (RAID-1, 0/1, and 5). The system administrator or service provider hot-swaps the failed disk module. Controller No on path to Ownership of the failed controller module’s LUNs can transfer module failed controller...
Page 140
Failing Continue component after failure What happens and how to recover Fibre Channel No on path to I/O operations fail along the path through the failed cable. If the host cable failed cable; has two Fibre Channel adapters connected to a dual-controller module Yes if array has disk array, the array can be accessed through the operational path if dual controller...
Page 158
Boot Support on Supported Host HP-UX 11.x? Fibre Channel I/O Adapter C-class A5158A on HP-UX 11.x A3740A on HP-UX 10.20 A4xx-A5xx class A5158A...
Page 160
Operating Operating In-Rush Current Current Power @ 110v @ 220v Current Cords Controller w/ 6 Disk Enclosures 41.3A 20.4A 124A Controller w/ 5 Disk Enclosures 34.8A 17.2A 104A Controller w/ 4 Disk Enclosures 28.3A 14.0A Controller w/ 3 Disk Enclosures 21.8A 10.8A Controller w/ 2 Disk Enclosures...
Page 161
Measurement Value Voltage – Range 220-240V 100 - 127V – Frequency 50-60Hz Current – Typical 2.9 - 3.2A Maximum Operating – 100 - 120 V 2.6 - 3.2A – 200 - 240 V 5.3 - 6.7A – Maximum In-rush Number of Breaker Components Rating...
Page 163
Number of Components 1.1-meter (21 U) Rack 1.6-meter (32 U) Rack 2.0-meter (41 U) Rack 1 – 4 Two 3-foot/16-amp PDUs* Two 5-foot/16-amp PDUs* Two 19-inch/16-amp PDUs Two 19-inch/16-amp PDUs 5 – 8 NA** Two 19-inch/30-amp PDRUs 9 – 10 NA** NA** Four 19-inch/30-amp PDRUs...
Page 164
UPS Product Disk Array Configuration Number Output Power Package Controller enclosure and up A2998B 3.0 kVA (3.0 kW) Rackmount to two disk enclosures Controller enclosure and up A3589B 5.5 kVA (5.5 kW) Rackmount to four disk enclosures Controller enclosure and up A1350A 8.0 kVA (8.0 kW) Standalone...
Page 165
PDU 16 Amp or PDU 16 Amp or PDRU 30 Amp PDRU 30 Amp...
Page 168
Component Measure (EIA Units) Legacy Cabinets (1 EIA Unit = 1.75”) 1.1 Meter Cabinet 21 EIA Units, Total Available 1.6 Meter Cabinet 32 EIA Units, Total Available 2.0 Meter Cabinet 41 EIA Units, Total Available Controller Enclosure FC60 5 EIA Units Used (includes 1/2 rail space below and remaining 1/2 EIA unit above enclosure) Disk Enclosure SC10 4 EIA Units Used (3.5 disk enclosure plus 1/2 rail space)
Installing the Disk Enclosures Figure Label Part (part number) Disk Enclosure (with power supplies, fans, and BCC modules) Rail kit (A5251A) for System/E cabinets Rail kit (A5250A) for legacy cabinets, 1 ea. Rack filler panel, 1/2 EIA Unit, 1 ea. Disks or fillers (A5234A or A5235A), pack of 10 SCSI terminators, 2 ea.
Page 174
AUTION WARNING Do not attempt to lift the disk enclosure without the help of another person or a lift device. Even without power supplies and disk drives, it weighs 50 pounds.
Page 175
A Front Mounting Ears C Rail B Chassis D Rail clamp...
Page 190
Setting Switch Operation Full-Bus Mode 1 - Full-/Split Bus Mode Split-Bus Mode 2 - Stand-Alone/Array Mode Always set to Off (Array Mode) 3 - Bus Reset on Power Fail Must be set to 0 4 - High/Low Bus Addressing Set to 0 (Low addressing) 5 - Not Used Not used;...
Page 191
Physical Disk Slot #s Full-Bus Mode SCSI IDs BCC A (or B) Split-Bus Mode SCSI IDs BCC-A (Even Slots) BCC-B (Odd Slots)
Attaching SCSI Cables and Configuring the Disk Enclosure Switches NOTE! It is critical that all SCSI cables be tightened securely. Use the following steps to ensure the cable connectors are seated properly. 1. Connect the cable to the enclosure connector and tighten the mounting screws finger tight.
Page 213
Module Normal State Front Enclosure System Fault System Power On (green) Disk Activity Flashing (green) when disk is being accessed. Disk Fault LED Power Supply Power Supply On (green) BCC Module Term. Power On (green) Full Bus Off (if split bus) On (green - if single bus) BCC Fault Bus Active On (green bus is available for use)
Page 214
A System fault LED B System power LED C Disk activity LED D Disk fault LED E Power On LED F Term. Pwr. LED G Full Bus LED H BCC Fault LED I Bus Active LED J LVD LED K Fan Fault LED...
Page 215
Module Normal State Controller Power On On (green) Enclosure Power Fault Fan Fault Controller Fault Fast Write Cache On (green) while data is in cache Controller Controller Power On (green) Controller Fault Heartbeat Blink (green) Status Green There are 8 status LEDs. The number and pattern of these LEDs depend on how your system is configured.
Page 216
A Power On LED B Power Fault LED C Fan Fault LED D Controller Fault LED E Fast Write Cache LED F Controller Power LED G Controller Fault LED H Heartbeat LED I Status LEDs J Fault B LED K Full Charge B LED L Fault A LED M Full Charge A LED N Power 1 LED...
Page 219
Class H/W Path Driver State H/W Type Description ============================================================================ target 8/8.8.0.4.0.0 CLAIMED DEVICE disk 8/8.8.0.4.0.0.0 sdisk CLAIMED DEVICE HP A5277A /dev/dsk/c0t0d0 /dev/rdsk/c0t0d0 disk 8/8.8.0.4.0.0.1 sdisk CLAIMED DEVICE HP A5277A /dev/dsk/c0t0d1 /dev/rdsk/c0t0d1 disk 8/8.8.0.4.0.1.0 sdisk CLAIMED DEVICE HP A5277A /dev/dsk/c0t1d0 /dev/rdsk/c0t1d0 disk 8/8.8.0.4.0.2.0 sdisk...
Page 220
sctl Peripheral Device Addressing (PDA) Hardware Path 8/12.8.0.255.1.2.0 Not Used (LUN - Logical Unit Number of disk) Target (Lower 4 bits of the loop ID) Bus (Upper 4 bits of the loop ID) Port (255 = the target connected directly to the FC) Area (0 = point-to-point or private loop) Protocol Type (8 = mass storage) Adapter...
Page 221
0 0 0 1 0 0 1 0 sdisk Volume Set Addressing (VSA) Hardware Path 8/12.8.0.6.0.1.3 Volume Number bits 0 - 2 (LUN number 0 - 7) Volume Number bits 3 - 6 (virtual SCSI bus 0 - 3) Volume Number bits 7 - 13 (always 0 for the FC60) Loop ID of controller module Area (0 = point-to-point or private loop) Protocol Type (8 = mass storage)
Installing the Disk Array FC60 Software (HP-UX Only) Hardware platform HP 9000 Series, K-class, D-class, V-class, N-class, T-600 HP-UX version HP-UX 11.0, 11.11, and 10.20...
Page 226
HP-UX myhost B.11.0.0 C 9000/750 1234567890 n-user license Note http://us-support2.external.hp.com/index.html/ (External web site) ftp://hpatlse.atl.hp.com/hp-ux_patches/ (Internal web site)
Page 251
MANAGING THE DISK ARRAY ON HP-UX Installing the Array Manager 60 Software ....... . . 254 Managing Disk Array Capacity .
Page 252
Tools for Managing the Disk Array FC60 Note...
Page 253
Task Tool Array Manager 60 Checking disk array status Yes (amdsp) Managing LUNs Yes (amcfg) Managing global hot spares Yes (ammgr) Assigning an alias to the disk array Yes (ammgr) Managing cache memory Yes (ammgr) Managing the rebuild process Yes (amutil) Changing controller state Yes (ammgr) Synchronizing controller date and time...
Page 264
Note RAID level Setting: Function: Sets the RAID level used by the LUN. Performance Impact: The RAID level selected impacts the entire performance profile for the LUN. Read I/O and write I/O performance are directly influenced by the RAID level. See "RAID Level Comparisons"...
Page 265
Cache flush threshold (default 80%) Setting: Function: Sets the level at which the disk array controller begins flushing write cache content to disk media. The setting is specified as the percentage of total available cache that can contain write data before flushing begins. The cache flush threshold can be set independently for each controller.
Page 266
Cache flush limit (default 100%) Setting: Function: Determines how much data will remain in write cache when flushing stops. It is expressed as a percentage of the cache flush threshold. For optimum performance this value is set to 100% by default. This ensures that the entire amount of cache specified by the cache flush threshold will contain write cache data, increasing the number of write cache hits.
Page 269
Note insf -e AUTION Note Can I move a disk module within the array with power on?
Page 271
Moving this to a slot previously results in this behavior. type of disk…. occupied by this type of disk…. None or Unassigned Disk remains part of its original LUN. If disk was moved from another array, the receiving array will try to create a new LUN to accommodate the disk.
Page 272
Moving this type to a slot previously results in this behavior. of disk…. occupied by this type of disk…. None or Unassigned Disk becomes unassigned. All data on disk is lost. Global Hot Spare Disk becomes a global hot spare. All data on disk is lost.
Page 273
Moving this to a slot previously results in this behavior. type of disk…. occupied by this type of disk…. None or Unassigned Disk remains part of its original LUN. If disk was moved from another array, the receiving array will try to create a new LUN to accommodate the disk.
Page 274
Moving this to a slot previously occupied type of disk…. by this type of disk…. results in this behavior. None or Unassigned Disk remains part of its original LUN. If disk was moved from another array, the receiving array will try to create a new LUN to accommodate the disk.
Upgrading Controller Cache to 512 Mbytes AUTION...
Page 279
Initial controller configuration Cache Upgrade Kit(s) Dual controllers, each with two 128 MB Two A5279A kits DIMMs Dual controllers, each with one 256 MB One A5279A kit DIMM Single controller with two 128 MB DIMMs One A5279A kit Single controller with one 256 MB DIMM One A5279A kit (only one of the DIMMs will be used)
Page 284
Green The component is functioning normally. On a disk it also indicates that the disk is part of a LUN. The component has failed or is not installed. Blue Used only for disks, indicates the disk is functioning normally and is a member of the hot spare disk group.
Managing the Disk Array Using Array Manager 60 Note Task Command Capacity Management Binding a LUN amcfg -L <cntrlrID>:<LUN> -d <channel:ID>,<channel:ID>..-r <RAIDlevel> <options> <ArrayID> Unbinding a LUN amcfg -D <LUN> [-force] <ArrayID> Calculating LUN Capacity amcfg -C -d channel:ID,channel:ID... -r <RAIDlevel>...
Page 297
Task Command Disk Array Status Displaying Status Information amdsp <option> <ArrayID> Listing Disk Array IDs amdsp -i Rescanning for Disk Arrays amdsp -R Disk Array Configuration Assigning an Alias to the Disk ammgr -D <ArrayAlias> <ArrayID> Array Setting Cache Page Size ammgr -p {4 | 16} <ArrayID>...
Page 299
Command Tasks amcfg Binding a LUN Unbinding a LUN Changing LUN Ownership Replacing a LUN Calculating LUN Capacity ammgr Adding a Global Hot Spare Removing a Global Hot Spare Assigning an Alias to the Disk Array Setting Cache Page Size Setting the Cache Flush Threshold Setting the Cache Flush Limit Changing the Controller Operating State...
Page 300
Symbol Meaning < > Indicates a variable that must be entered by the user. Only one of the listed parameters can be used (exclusive OR). Values enclosed in these braces are optional. Values enclosed in these braces are required.
Page 302
Command parameter Description ArrayID Identifies the disk array. The ArrayID may be either the disk array ID (its S/N), or an alias name assigned to the array. Each disk array must have a unique ArrayID. The disk array S/N and alias can be determined using the amdsp -i command.
Page 304
Option Status Information Displayed none General array information. This includes disk capacity usage. Sample output is shown in -l [LUN] LUN status. Status for all LUNs on the disk array will be displayed, unless a specific LUN is specified using the LUN option. If UTM is enabled, it will be displayed in the LUN output.
Page 305
Option Status Information Displayed All status. This option displays all the information returned by the preceding options. -p <devicefile> Hardware path information. Displays hardware path information for the controller corresponding to the specified device file. Rebuild status. Display the progress of any rebuilds occurring on the disk array.
Page 306
Vendor ID = HP Product ID = A5277A Array ID = 000A00A0B80673A6 Array alias = Array1 ----------------------------------------- Array State = READY Server name = speedy Array type Mfg. Product Code = 348-0040789 --- Disk space usage -------------------- Total physical = 271.4 GB Allocated to LUNs = 135.4 GB Used as Hot spare...
Page 307
Vendor ID = HP Product ID = A5277A Array ID = 000A00A0B80673A6 Array alias = Array1 ----------------------------------------- SCSI Channel:ID = 1:0 Enclosure Slot Disk State = OPTIMAL Disk Group and Type = 060E86000238C6360F LUN Capacity = 17.0 GB Manufacturer and Model = SEAGATE ST318203LC Serial Number = LRB61150 Firmware Revision...
Page 308
Information for Controller A - 000A00A0B80673A6: Controller Status = GOOD Controller Mode = ACTIVE Vendor ID = HP Product ID = A5277A Serial Number = 1T00310110 Firmware Revision = 04000311 Boot Revision = 04000301 HP Revision = HP10 Loop ID AL_PA = 0xE0 Preferred AL_PA...
Page 309
Vendor ID = HP Product ID = A5277A Array ID = 000A00A0B80673A6 Array alias = Array1 ----------------------------------------- Overall State of Array = READY Array configuration: Cache Block Size = 4 KB / 4 KB Cache Flush Threshold = 80 % / 80 % Cache Flush Limit = 100 % / 100 % Cache Size...
Page 313
Option Description Default -c capacity Specifies the capacity of the LUN. Capacity If not specified, the LUN capacity can be specified in megabytes (M) or will equal the total available gigabytes (G) by appending the appropriate capacity of the specified disks. letter to the capacity value.
Page 315
AUTION Unbinding a LUN will have the same impact on the host as removing a disk.
Page 327
Note Default Cache Parameter Value Description Write Cache Enabled (WCE) Enables write caching for the specified LUN, and all other LUNs also owned by the controller that owns the LUN.
Page 328
Default Cache Parameter Value Description Read Cache Disabled (RCD) Disables read caching for the specified LUN, and all other LUNs also owned by the controller that owns the LUN. Cache Mirroring Enabled (CME) Enables cache mirroring for the specified LUN only.
Page 330
Option Description -f channel:ID Fault Flash the LED on the specified disk. A disk is identified by both channel (1- 6) and SCSI ID (0 - 4, 8 - 12). Fault Flash the LEDs on all the disks in the disk array. Fault Stop flashing the disk LEDs.
Page 339
Option Description -C <cntrlrID> Change the state of the specified disk array controller (A or B) to FAIL. The controller is failed by holding it in a reset state. NOTE! Before failing a controller, you must transfer ownership of all LUNs to the other controller. This command will fail if the controller you attempting to fail still owns any LUNs.
Page 342
Note Major event log for Subsystem 001100A0B8060166 at Wed Nov 29 17:38:27 2000 Sequence Number = 14 Time Stamp = Wed Nov 29 17:38:19 2000 Event Type = Global Hot Spare Not Large Enough (224F) Event Category = Notification Component Type = Disk Enclosure Slot (0-based)
Page 343
Controller log sense for Subsystem 001100A0B8060166 at Mon Dec 12:51:34 2000 Controller Time Stamp = 032307 083318 FRU Code = 0x08 FRU Code Qualifier = 0x8142 Sense Key = 0x06 Additional Sense Code = 0x3F Add Sense Code Qual = 0xC7 Decoded Field Replaceable Unit Information: FRU Group = Sub-Enclosure Group...
Page 346
AUTION Note amdload Option Description -D all Download firmware to all disks on the disk array. -D channel:ID, channel:ID,... Download firmware to the specified disks on the disk array. A disk is identified by channel and SCSI ID. Multiple disks can be specified. -C all Download firmware to both disk array controllers.
Page 347
Option Description -S all Download firmware to all disk system BCC modules on the disk array. -S channel, channel,... Download firmware to the specified disk system BCC modules. A disk system is identified by the channel it is connected to (1-6). Multiple disk system can be specified. Firmware is downloaded to both BCC modules in the disk system.
Page 348
Note File Name Firmware Release Description filename.bwd bootware code filename.apd appware code filename.dl NVSRAM code filename.dlp Package firmware files. The appware and HP03 and later bootware are combined in a single package file, and the NVSRAM is included in a separate package file.
Page 350
Enhancement Description RAID 0 RAID 0 provides improved performance but without data protection. RAID 0 provides no data redundancy and should only be used for non-critical data. The loss of a single disk in a RAID 0 LUN causes the loss of all data in the LUN. Major event logging Provides greater depth of information on disk array events.
Page 352
Note Note Starting the firmware update. The download will take up to 2 minutes for each controller. Downloading code to controller A... Waiting for controller to reset... Downloading code to controller B... Waiting for controller to reset... ----- ARRAY CONTROLLER REVISION INFORMATION ----- Controller HPRev Firmware Bootware Ctrlr A...
Page 353
Note Starting the firmware update. The download will take up to 2 minutes for each controller. Downloading code to controller A... Waiting for controller to reset... Downloading code to controller B... Waiting for controller to reset... ----- ARRAY CONTROLLER REVISION INFORMATION ----- Controller HPRev Firmware Bootware Ctrlr A...
Status Conditions and Sense Code Information Status Definition/Action AM60: OPTIMAL The LUN is operating normally. STM: OPTIMAL No action is required. AM60: OPTIMAL--PARITY SCAN A parity scan is in progress on the disk array. IN PROGRESS No action is required. STM: OPTIMAL AM60: OPTIMAL-REDUNDANCY A background parity sync operation is in progress on this...
Page 362
Status Definition/Action AM60: DEGRADED--REPLACED A rebuild is in progress on the LUN. DISK BEING REBUILT No action is required. STM: DEGRADED - 2 AM60: DEAD--MORE DISK Multiple, simultaneous disk failures have occurred on the FAILURES THAN REDUNDANT LUN, causing data to be inaccessible. On a RAID 5 LUN, DISKS losing more than one disk will cause this status.
Page 363
Status Definition/Action AM60: OPTIMAL The disk is operating normally. STM: OPTIMAL (OPT) No action is required. AM60: NON-EXISTENT The disk array controller has no knowledge of a disk in this STM: No Disk (NIN) slot. This may be caused by no disk being installed, or a disk that never responds to a SCSI command from the controller.
Page 364
Status Definition/Action AM60: READ FAILED The disk array could not read from the disk. STM: FLT - 19 Replace the failed disk. AM60: WRONG BLOCK SIZE The disk uses an incompatible block size (not 512 bytes). STM: OFF - 22 Replace with a supported disk.
Page 365
Status Description AM60: Good The component is operating normally. STM: Optimal AM60: Non-critical A component or condition such as temperature or voltage STM: Fault - 3 has exceeded warning limits. Although immediate action is not required, the cause of the non-critical status should be investigated and corrected if necessary.
Page 366
FRU Code Value Group Description 0x01 Host Channel Group - comprises the host SCSI bus, its SCSI interface chip, and all initiators and other targets connected to the bus. 0x02 Controller Drive Interface Group - comprises the SCSI interface chips on the controller which connect to the drive buses.
Page 367
FRU Code Value Group Description 0x08 Disk Enclosure Group - comprises attached disk enclosures. This group includes the power supplies, environmental monitor, and other components in the disk enclosure. See "Disk Enclosure Group FRU Code Qualifier" on page 370 for information on identifying component and status.
Page 368
Status & Component ID Byte FRU Code Qualifier: Field Component Status Component ID Component Status Value Status Optimal Warning Failed Missing...
Page 369
Component ID Value Component Unspecified Device Power Supply Cooling Element Temperature Sensors Audible Alarm Environmental Services Electronics Controller Electronics Nonvolatile Cache Uninterruptible Power Supply 0x0C - 0x13 Reserved 0x14 SCSI Target Port 0x15 SCSI Initiator Port...
Page 370
Status & Component ID Byte Disk Enclosure ID Byte (See Controller Enclosure group for values) FRU Code Qualifier: Field Reserved Disk Enclosure ID TIE Value Disk Enclosure ID When TIE (Tray Identifier Enable) is set to 0, the Disk Enclosure ID field indicates both the channel and enclosure as follows: Enclosure #1 Enclosure #2...
Page 371
Additional Additional Sense Sense Code Code Qualifier Interpretation No Additional Sense Information The controller has no sense data available for the requesting host and addressed logical unit combination. Logical Unit is in the Process of Becoming Ready The controller is executing its initialization functions on the addressed logical unit.
Page 372
Additional Additional Sense Sense Code Code Qualifier Interpretation If the accompanying sense key = 4, error is interrupted as follows: Unrecovered Write Error Data could not be written to media due to an unrecoverable RAM, battery or drive error. If the accompanying sense key = 6, error is interrupted as follows: Caching Disabled Data caching has been disabled due to loss of mirroring capa-...
Page 373
Additional Additional Sense Sense Code Code Qualifier Interpretation Unrecovered Read Error An unrecovered read operation to a drive occurred and the con- troller has no redundancy to recover the error (RAID 0, degraded RAID 1, degraded mode RAID 3, or degraded RAID Miscorrected Data Error - Due to Failed Drive Read A media error has occurred on a read operation during a recon- figuration operation,...
Page 374
Additional Additional Sense Sense Code Code Qualifier Interpretation Logical Block Address Out of Range The controller received a command that requested an operation at a logical block address beyond the capacity of the logical unit. This error could be in response to a request with an illegal starting address or a request that started at a valid logical block address and the number of blocks requested extended beyond the logical unit capacity.
Page 375
Additional Additional Sense Sense Code Code Qualifier Interpretation Device Internal Reset The controller has reset itself due to an internal error condition. Default Configuration has been Created The controller has completed the process of creating a default logical unit. There is now an accessible logical unit that did not exist previously.
Page 376
Additional Additional Sense Sense Code Code Qualifier Interpretation Commands Cleared by Another Initiator The controller received a Clear Queue message from another initiator. This error is to notify the current initiator that the con- troller cleared the current initiators commands if it had any out- standing.
Page 377
Additional Additional Sense Sense Code Code Qualifier Interpretation Drive No Longer Usable. The controller has set a drive to a state that prohibits use of the drive. The value of N in the ASCQ indicates the reason why the drive cannot be used. 0 - The controller set the drive state to "Failed - Write failure"...
Page 378
Additional Additional Sense Sense Code Code Qualifier Interpretation The controller has detected a drive with Mode Select parame- ters that are not recommended or which could not be changed. Currently this indicates the QErr bit is set incorrectly on the drive specified in the FRU field of the Request Sense data.
Page 379
Additional Additional Sense Sense Code Code Qualifier Interpretation Write Back Cache Battery Has Been Discharged The controller’s battery management has indicated that the cache battery has been discharged. Write Back Cache Battery Charge Has Completed The controller’s battery management has indicated that the cache battery is operational.
Page 380
Additional Additional Sense Sense Code Code Qualifier Interpretation Diagnostic Failure on Component NN (0x80 - 0xFF) The controller has detected the failure of an internal controller component. This failure may have been detected during opera- tion as well as during an on-board diagnostic routine. The val- ues of NN supported in this release of the software are listed below.
Page 381
Additional Additional Sense Sense Code Code Qualifier Interpretation Internal Target Failure The controller has detected a hardware or software condition that does not allow the requested command to be completed. If the accompanying sense key is 0x04: Indicates a hardware failure. The controller has detected what it believes is a fatal hardware or software failure and it is unlikely that a retry would be successful.
Page 382
Additional Additional Sense Sense Code Code Qualifier Interpretation Drive Reported Reservation Conflict A drive returned a status of reservation conflict. Data Phase Error The controller encountered an error while transferring data to/ from the initiator or to/ from one of the drives. Overlapped Commands Attempted The controller received a tagged command while it had an untagged command pending from the same initiator or it...
Page 383
Additional Additional Sense Sense Code Code Qualifier Interpretation Drive IO Request Aborted IO Issued to Failed or Missing drive due to recently failed removed drive. This error can occur as a result of I/Os in progress at the time of a failed or removed drive. Microcode Download Error The controller detected an error while downloading microcode and storing it in non-volatile memory.
Page 384
Additional Additional Sense Sense Code Code Qualifier Interpretation Quiescence Is In Progress or Has Been Achieved Quiescence Could Not Be Achieved Within the Quiescence Timeout Period Quiescence Is Not Allowed A Parity/ Data Mismatch was Detected The controller detected inconsistent parity/data during a parity verification.
Page 385
Additional Additional Sense Sense Code Code Qualifier Interpretation Command Lock Violation The controller received a Write Buffer Download Microcode, Send Diagnostic, or Mode Select command, but only one such command is allowed at a time and there was another such com- mand active.
Page 386
Additional Additional Sense Sense Code Code Qualifier Interpretation Controller Removal/Replacement Detected or Alternate Con- troller Released from Reset The controller detected the activation of the signal/signals used to indicate that the alternate controller has been removed or replaced. The controller has determined that there are multiple sub-enclo- sures with the same ID value selected.
Page 387
Additional Additional Sense Sense Code Code Qualifier Interpretation Recovered processor memory failure The controller has detected and corrected a recoverable error in processor memory. Recovered data buffer memory error The controller has detected and corrected a recoverable error in the data buffer memory. Sense bytes 34-36 will contain the count of errors encountered and recovered The Inter-controller Communications Have Failed...
Page 388
Additional Additional Sense Sense Code Code Qualifier Interpretation 20/21 Fibre Channel Destination Channel Error ASCQ = 20: Indicates redundant path is not available to devices ASCQ = 21: Indicates destination drive channels are connected to each other Sense byte 26 will contain the Tray ID Sense byte 27 will contain the Channel ID...
Major Event Log Entries Event Number Event Description Priority Category Component 0x1001 Channel Failure: Logged when the Informational Failure Chip (0XC) parallel SCSI destination driver detects (0x0) (0x2) a channel failure 0x1007 Memory Allocation Failed: Logged Informational Error (0x1) Controller when memory allocation failed (0x0) (0x8)
Page 390
0x1010 Disk SMART Event: The logged Informational Error (0x1) Drive (0x1) device generated a PFA condition (0x0) 0x1012 Destination Driver Unrecovered Informational Error (0x1) Controller Error: Logged when the destination (0x0) (0x8) driver has an unrecovered error from the drive. 0x1013 Destination Diagnostic Failure: Informational...
Page 391
Event Number Event Description Priority Category Component 0x1101 SCSI Chip Exception Condition: Informational Error (0x1) Controller Logged when the SRC driver detects (0x0) (0x8) an exception condition from the SCSI chip 0x1102 Host SCSI Bus Reset: Logged when Informational Notification Controller the source SCSI driver asserts the (0x0)
Page 392
Event Number Event Description Priority Category Component 0x1201 LIP Reset Received: Logged when a Informational Error (0x1) Controller selective LIP reset is received. (0x0) (0x8) 0x1202 Target Reset Received: Logged Informational Error (0x1) Controller when a Target Reset if received. (0x0) (0x8) 0x1203...
Page 393
Event Number Event Description Priority Category Component 0x1500 HW or Internal Structure Init Error: Informational Error (0x1) Controller Logged when a controller is unable to (0x0) (0x8) initialize hardware or an internal structure. 0x1501 Device Reset Primitive Sent: Informational Error (0x1) Controller Logged when a device reset primitive (0x0)
Page 394
Event Number Event Description Priority Category Component 0x2001 Repair LUN Begin: Logged when a Informational Notification Volume (0xD) repair operation is started for the (0x0) (0x4) specified unit. 0x2005 LUN Internally Failed: Logged when Informational Failure Volume (0xD) the specified LUN is internally failed. (0x0) (0x2) 0x200A...
Page 395
0x2015 Uncompleted Write Detected in Informational Notification Controller NVSRAM: Logged at start-of-day (0x0) (0x4) (0x8) when uncompleted writes are detected in NVSRAM 0x2016 Interrupted Writes Processed by Informational Notification Controller VDD: Logged when vdd processes (0x0) (0x4) (0x8) interrupted writes for the specified unit 0x2017 Interrupted Writes Logged by VDD: Informational...
Page 396
0x201F VDD Repair End: Logged at the end Informational Notification Controller of a repair operation (0x0) (0x4) (0x8) 0x2020 Piece Failed During Interrupted Informational Notification Controller Write: Logged when a piece is failed (0x0) (0x4) (0x8) during an interrupted write operation 0x2021 Vdisk Failed During Interrupted Informational...
Page 397
0x202A Reconfiguration Resume: Logged Informational Notification Drive (0x1) when reconfiguration operations are (0x0) (0x4) resumed for the specified unit. 0x202B Parity Scan Begin: Logged when Informational Notification Controller parity scan operations are started for (0x0) (0x4) (0x8) the specified unit. 0x202C Parity Scan End: Logged when Informational...
Page 398
Event Number Event Description Priority Category Component 0x2101 Alternate Controller Late Check In: Informational Notification Controller Logged when the alternate controller (0x0) (0x4) (0x8) check in late 0x2102 Controller Cache Mirroring Not Informational Notification Controller Synchronized: The mirror is out of (0x0) (0x4) (0x8)
Page 399
0x210B Cache Synchronize Failed: Cache Informational Notification Controller synchronization between the (0x0) (0x4) (0x8) controllers failed. The ASC/ASCQ value of 0x2A/0x01 is also logged with this event. 0x210C Cache Battery Failure: Cache Informational Notification Controller battery has failed. ASC/ASCQ of (0x0) (0x4) (0x8)
Page 400
0x2117 Controller Cache Manager Error Informational Notification Controller Cleared: On occasion CCM may log (0x0) (0x4) (0x8) an error prematurely and then clear it later. For example errors may be logged when the alternate controller is removed from the subsystem. If the controller is replaced before a write is done CCM will cancel the errors logged since the controller is replaced...
Page 401
Event Number Event Description Priority Category Component 0x2202 LUN Added: Logged when a LUN is Informational Notification Volume (0xD) added to the subsystem. (0x0) (0x4) 0x2203 Volume Group or LUN Deleted: Informational Notification Volume (0xD) Logged when the specified virtual disk (0x0) (0x4) is deleted.
Page 402
0x220A Copyback Start: Logged when copy Informational Notification Volume (0xD) task is started (0x0) (0x4) 0x220B Copyback Restart: Logged when Informational Notification Volume (0xD) copy task is restarted (0x0) (0x4) 0x220C Disk or LUN Failed on Interrupted Informational Notification Unknown Write: Logged when the specified (0x0) (0x4)
Page 403
0x2214 One or More Sundry Disks Created: Informational Notification Unknown Logged when configuration manager (0x0) (0x4) (0x0) creates 1 or more sundry drives. 0x2215 UA/AEN Posted for Failed Disk: Informational Notification Unknown Logged when configuration manager (0x0) (0x4) (0x0) posts a UA/AEN for a failed drive. 0x2216 LUN Piece Out of Service (OOS): Informational...
Page 404
0x221F Immediate Availability LUN Informational Notification Volume (0xD) Initialized: Logged when an (0x0) (0x4) immediate availability LUN has been initialized. 0x2220 Global Hot Spare Added: Logged Informational Notification Drive (0x1) when a drive is to the global hot spare (0x0) (0x4) list 0x2221...
Page 405
0x2229 Failed Disk Internally: Logged when Informational Notification Drive (0x1) the configuration manager internally (0x0) (0x4) fails the device. 0x222A Unassigned Disk Specified as Informational Notification Drive (0x1) GHS: Logged when an unassigned (0x0) (0x4) drive is specified as a global hot spare 0x222B Disk Cold Replaced: Logged when Informational...
Page 406
0x2230 Configuration Manager Call to Fail Informational Notification Drive (0x1) Disk: Logged when the configuration (0x0) (0x4) manager state machine has been called to fail the device. This is an additional event that indicates the configuration manager has determined that processing has to be done in order to fail the device.
Page 407
0x2236 Copy Completed on Global Hot Informational Notification Drive (0x1) Spare Disk: Logged by the (0x0) (0x4) configuration manager state machine when a copy operation has completed on a global hot spare drive. 0x2237 Replaced Disk Rebuild Complete: Informational Notification Drive (0x1) Copy Done: Logged when a replaced (0x0)
Page 408
0x223F Optimal Disk Marked Operational Informational Notification Drive (0x1) w/o Rebuild: Logged when a optimal (0x0) (0x4) drive that hasn’t completed reconstruction is marked operational. 0x2240 Unassigned Disk or GHS Has No Informational Notification Drive (0x1) DACSTORE: Logged when an (0x0) (0x4) unassigned drive or unassigned...
Page 409
0x2247 Unrecovered Interrupted Write: Critical (0x1) Notification Volume (0xD) Logged when a LUN is marked DEAD (0x4) due to a media error failure during SOD. An error occurred during Interrupted Write processing causing the LUN to transition to the DEAD State.
Page 410
0x224D No Response From Disk: Logged Critical Notification Drive (0x1) when the configuration manager (0x1) (0x4) posts and UA/AEN of ASC/ASCQ = 0x3F/0x85 indicating the controller set the drive state to “Failed – No Response”. 0x224E Replaced Disk Failed: Logged when Critical Failure Drive (0x1)
Page 411
0x2253 LUN Created, Deleted or Changed Informational Notification Volume (0xD) Owner: Logged when the (0x0) (0x4) configuration manager posts and UA/AEN of ASC/ASCQ = 0x3F/0x0E indicating that previous LUN data reported via a Report LUNs command has changed (due to LUN creation/deletion or controller hot swap.
Page 412
Event Number Event Description Priority Category Component 0x2400 Hot Swap Monitor Detected Disk Informational Notification Drive (0x1) Removed: Logged in the system log (0x0) (0x4) when the hot swap monitor detects that a drive has been removed from the system. 0x2401 Hot Swap Monitor Detected Disk Informational...
Page 413
Event Number Event Description Priority Category Component 0x2600 ACS Download Start: Logged when Informational Notification Controller an ACS Download is started (0x0) (0x4) (0x8) 0x2601 ACS Download Completed: Logged Informational Notification Controller after the controller has been rebooted (0x0) (0x4) (0x8) after auto code synchronization has been preformed.
Page 414
0x2703 Recovered Processor DRAM Error: Informational Notification Controller Logged when the controller has (0x0) (0x4) (0x8) encountered recoverable processor DRAM ECC errors (below the maximum threshold) Event Number Event Description Priority Category Component 0x2800 Power Supply State Changed: Informational Notification Power Supply Logged when a power supply (0x0)
Page 415
0x2806 Disk Enclosure Device State Informational Notification ESM (0x7) Change: Logged when SSM has (0x0) (0x4) detected a change in an enclosure device, other than a drive status. 0x2808 Sub-Enclosure ID Not Unique: Informational Notification ESM (0x7) Logged when the controller (0x0) (0x4) determines that there are multiple...
Page 417
Event Number Event Description Priority Category Component 0x3000 Format LUN: Logged when the Informational Command Volume (0xD) controller processes a format (0x0) (0x3) command. The LUN value indicates the LUN that the controller is formatting. 0x3001 Quiesce: Logged for the quiescence Informational Command Controller...
Page 418
0x3007 Mode Select 0x01--Read-Write Informational Command Volume (0xD) Recovery Page: Logged when Mode (0x0) (0x3) Select for Page 0x01 is received and the Post Error bit value has changed from the value stored in NVSRAM. 0x3008 Mode Select 0x02--Disconnect- Informational Command Volume (0xD) Reconnect Page: Logged when...
Page 419
0x3010 Mode Select 0x3A--Global Hot Informational Command Controller Spare Page: Logged when Mode (0x0) (0x3) (0x8) Select Page 0x3A (The global hot spare page) is received. 0x3012 Write Buffer Received: Logged Informational Command Controller when Write Buffer is received to the (0x0) (0x3) (0x8)
Page 420
0x30!D ESM Firmware Download Fail: Informational Command ESM (0x7) Logged when ESM firmware (0x0) (0x3) download has failed. 0x301E ESM Firmware Download Informational Command ESM (0x7) Complete: Logged when ESM (0x0) (0x3) firmware download has successfully completed. Event Number Event Description Priority Category Component...
Page 421
Event Number Event Description Priority Category Component 0x4000 Shell SysWipe Controller: Logged Informational Notification Controller when a syswipe request is sent to the (0x0) (0x4) (0x8) controller. This routine is not called by the controller SW or FW currently. If logged it means the command was entered through the shell interface.
Page 422
0x4003 NVSRAM Clear Received from Alt Informational Notification Controller Controller: Logged when an (0x0) (0x4) (0x8) NVSRAM clear message is received from the alternate controller. No additional data is logged. The companion entry of MEL_EV_ICON_NV_CLR should also be seen in the event log along with this entry.
Page 423
0x400C Alternate Controller Reset Hold: Critical (0x1) Notification Controller Logged when the controller (0x4) (0x8) successfully puts the alternate controller in the reset/hold state. 0x400D Alternate Controller Reset Release: Informational Notification Controller Logged when the controller (0x0) (0x4) (0x8) successfully releases the alternate controller from the reset/failed state.
Page 424
Event Number Event Description Priority Category Component 0x5000 Assign Volume Group Ownership: Informational Command Volume Logged on entry to (0x0) (0x3) Group (0xE) assignVolumeGroupOwnership_1. 0x5001 Create Hotspare: Logged on entry to Informational Command Unknown assignDriveAsHotSpares_1. (0x0) (0x3) (0x0) 0x5003 Delete Hotspare: Logged on entry to Informational Command Unknown...
Page 425
0x500D Set Volume Group Online: Logged Informational Command Volume on entry to (0x0) (0x3) Group (0xE) setVolumeGroupToOnline_1 0x500E Start Disk Rebuild: Logged on entry Informational Command Drive (0x1) to startDriveReconstruction_1 (0x0) (0x3) 0x500F Start Volume Group Defragment: Informational Command Volume Logged on entry to (0x0) (0x3)
Page 426
0x5018 Set Volume Cache Parameters: Informational Command Volume (0xD) Logged on entry to (0x0) (0x3) setVolumeCacheParams_1 0x5019 Set Volume Parameters: Logged on Informational Command Volume (0xD) entry to setVolumeParams_1 (0x0) (0x3) 0x501A Set Volume User Label: Logged on Informational Command Volume (0xD) entry to setVolumeUserLable_1 (0x0)
Page 427
0x5023 Controller Function Call Return: Informational Command Unknown Logged on the return from RPC (0x0) (0x3) (0x0) function returning ReturnCode 0x5024 Write Download Checkpoint: Informational Command Controller Logged whenever the download (0x0) (0x3) (0x8) checkpoint is updated 0x5025 Controller Firmware Download Informational Command Controller...
Page 428
Event Number Event Description Priority Category Component 0x5200 Create Cluster: Logged on entry to Informational Command Unknown spmCreateCluster (0x0) (0x3) (0x0) 0x5201 Delete Cluster: Logged on entry to Informational Command Unknown spmDeleteCluster (0x0) (0x3) (0x0) 0x5202 Rename Cluster: Logged on entry to Informational Command Unknown...
Page 429
0x520C Create Storage Array Port Group: Informational Command Unknown Logged on entry to (0x0) (0x3) (0x0) spmCreateSAPortGroup 0x520D Delete Storage Array Port Group: Informational Command Unknown Logged on entry to (0x0) (0x3) (0x0) spmDeleteSAPortGroup 0x520E Move Storage Array Port: Logged Informational Command Unknown...
Page 430
Event Number Event Description Priority Category Component 0x5400 Feature Enabled: Logged when a Informational Notification Unknown feature is successfully enabled. (0x0) (0x4) (0x0) 0x5401 Feature Disabled: Logged when a Informational Notification Unknown feature is successfully disabled. (0x0) (0x4) (0x0) 0x5402 Non-Compliance: Logged when Informational Notification...
Page 432
Constant Data Fields (MSB) Sequence Number - (byte swapped) (LSB) 8-11 (MSB) Event Number - (byte swapped) (LSB) 12-15 (MSB) Timestamp - (byte swapped) (LSB) 16-19 (MSB) Location Information - (byte swapped) (Channel & Device or Tray & Slot Number) (LSB) 20-23 (MSB)
Page 433
The Sequence Number field is a 64 bit incrementing value starting from the time the sys- tem log was created or last initialized. Resetting the log does not affect this value. The Event Number is a 4 byte encoded value that includes bits for drive and controller inclusion, event priority and the event value.
Page 434
Log Group Value System Event Controller Event Drive Event Priority Value Informational Critical Reserved 0x2 - 0xF...
Page 435
Category Value Unknown Error Failure Command Notify State Host General Reserved 0x8-0xF...
Page 436
Component Value Unknown/Unspecified Device Power Supply Cooling Element Minihub Reserved Reserved Environmental Services Electronics Controller Electronics Nonvolatile Cache (RPA Cache Battery) Enclosure Uninterruptible Power Supply Chip - I/O or Memory Volume Volume Group I/O Port CRU...
Page 437
Logging of data for this field is optional and is zero when not specified. Value Definition Active Host Write Cache Hot Spare Other Internal...
Page 438
Value Definition 0x00 Controller w/Drive side SCSI ID 6 (normally the bottom controller in the subsystem) 0x01 Controller w/Drive side SCSI ID 7 (normally the top controller in the subsystem) Data Length (L) Data Field Type Data …...
Page 440
Major event log for Subsystem 001100A0B8060166 at Tue Nov 28 11:35:03 2000 Sequence Number = 76061 Time Stamp = Mon Nov 27 12:04:57 2000 Event Type = AEN Posted for Recently Logged Event (3101) Event Category = Notification Component Type = Controller Slot Event Priority...
Page 451
Note Tool type Description Information Provides detailed configuration and status information for all disk arrays components. Expert Provides capability to perform common disk array management tasks. Advanced options available with an HP Only license provide access to more advanced capabilities. Firmware Update Provides the capability of downloading new firmware to the disk array components...
Page 458
Menu Option Property Description Logs View Event Log Displays selected event log entries Tests Parity Scan Perform a parity scan on a LUN. Utilities Bind LUN Bind selected disk modules into a LUN with a specified RAID level. Unbind LUNs Unbind a LUN.
Page 463
Menu Item Option Description List Current Revisions Lists controller microcode and disk module firmware revisions currently in use. Instructions Lists basic instructions for Firmware Update Tool use. Update Perform Disk Downloads firmware to the specified disk type. Download Perform Controller Downloads firmware to the disk array controllers.
AR60DIAG Offline Diagnostic Command Description BIND Binds a LUN CHANNEL Sets the channel address environment variable CLRLOG Clears the internal logs of a controller or disk CONFIG Sets both controllers to active mode CONTROLLER Sets the controller address environment variable CNTRLTEST Tests a controller DESCRIBE...
Page 465
Command Description DISPMAP Displays the operational disk arrays connected to the host DOWNLOAD Downloads firmware to the specified controller, BCC, or disk IDENTIFY Flashes the LEDs on specified disk PARITYSCAN Performs real-time data integrity checking on specified LUN READLOG Displays internal hardware logs for specified component REVISION Displays controller, disks, and software revisions SHOWENV...
Page 467
Note DISPMAP SHOWENV controller n channel n disk n...
Page 468
bind controller # LUN # AR60DIAG> bind controller 1 lun 2 Enter Raid level (1:5) Enter ’q’ to quit Raid level 1 should have even number of drives Enter the number of drives to be bound Enter q to quit Data for drive # 0 Enter channel number Data for drive # 1...
Page 469
Drives to be bound to this lun are: Channel : 1 disk : 0 Channel : 2 disk : 1 Do you want to continue[y/n] Lun 2 is created and initializing !!
Page 470
Note channel channel # AR60DIAG> channel Channel is set to 3 AR60DIAG> channel 5 Channel is set to 5...
Page 471
clrlog controller # clrlog controller # channel # disk # AR60DIAG> clrlog controller 0 Proceed with Clear Log ? Continue [y/n] ? y Controller Logs Successfully Cleared ! AR60DIAG> clrlog controller 0 channel 1 disk 1 Proceed with Clear Log ? Continue [y/n] ? y Disk Logs Successfully Cleared !
Page 472
config RDAC AR60DIAG> config RDAC Controllers set to active...
Page 473
controller controller # AR60DIAG> controller Controller is set to device 1 AR60DIAG> controller 2 Controller is set to device 2...
Page 474
Test Level Testing Performed Test hardware components on the selected controller Level 0 tests, plus – Issue a Write Buffer and Read Buffer to each disk owned by the controller, – Issue an Inquiry command to each disk not owned by the controller. Level 1 tests, plus –...
Page 476
AR60DIAG> describe controller 0 status FC LOOP ID (ALPA) = 0x0 Controller date ..Wed Apr 21 11:14:18 1999 A single controller configuration has been detected. Controller 0 Controller 1 =================================================================== Address 8/8.8.0.6.0.0.0 State ACTIVE PASSIVE Luns NONE Display SES configuration information? Continue ([y]/n)? DISK DEVICES...
Page 482
Enable default cache mirroring SET Default cache Block sizeReserved Enable subsystem cache LED SET 0x2c 0x00 Drive negotiation Options..Negotiate for WIDE NOT SET Negotiate for Synchronous Xfer Set for maximum rate 0x2d 0x00 Cache Battery Life Expiration Age.
Page 483
Defect List: Controller 0 Channel 1 Disk 2 ------------------------------------------------ G list has 0 entries P list has 1263 entries AR60DIAG> describe controller 0 lun 0 The controller reports 1 lun ================= LUN 0 configuration ================= Raid Level = 0 Lun Type = Sub-Lun MaxLBA = 2047999 Current LUN state = Operational Approximate capacity = 100 MBytes...
Page 484
Note disk disk # AR60DIAG> disk Disk is set to 1 AR60DIAG> disk 4 Disk is set to 4...
Page 485
dispconf dispconf controller # AR60DIAG > dispconf Controller 0 Controller 1 =================================================================== Address 10/8.8.0.255.0.7.0 State PASSIVE ACTIVE Luns UNKNOWN =============== JBOD connected to channel 1 =============== Drv in slot 0 (ScsiAdd 0 ) ..OK Drv in slot 1 (ScsiAdd 8 ) .
Page 486
Supply #2 ....ON AND OK =============== JBOD connected to channel 2 =============== Drv in slot 0 (ScsiAdd 0 ) ..OK Drv in slot 1 (ScsiAdd 8 ) .
Page 487
dispfiles AR60DIAG> dispfiles File Name Intended Product Size Note nvsram_G HP A5277A NVSRAM bootware_07 HP A5277A 532116 Bootware firmware_45 HP A5277A 1559728 Application firmware alp.frm HP A5272A 230596 BCC firmware HP02.frm 303360 Disk firmware...
Page 488
Note dispmap AR60DIAG> dispmap Test Disk Path Product String Size ---- --------------- ----------------------- ----- ------- 8/8.8.0.6.0.0 HP A5277A 9301 8/8.8.0.7.0.0 HP A5277A 9301...
Page 489
WARNING This command is destructive, and downloading an incorrect firmware file could render your disk drive inoperative. Also, do not switch anything on or off on the host while a download operation is in process! download download controller # download controller # channel # download controller # channel # disk #...
Page 490
AR60DIAG> download controller 0 channel 2 disk 3 Enter the firmware file name [’?’ displays the files. Default quits]: ? File Name Intended Product Size Note nvsram_G HP A5277A NVSRAM bootware_07 HP A5277A 532116 Bootware firmware_45 HP A5277A 1559728 Application firmware alp.frm HP A5272A 230596...
Page 492
identify controller # channel # disk # <on|off> AR60DIAG> identify controller 1 channel 3 disk 2 Flashing LEDs for controller 1 channel 3 disk 2 on The LED for Controller 1 Channel 3 Disk 2 is ON...
Page 494
readlog readlog controller # readlog controller # channel # disk # AR60DIAG> readlog controller 0 Last n Deferred Errors or Asynchronous Events --------------------------------------------------------------- Event Number <1> Format Block -------------------------------------------- Sense Key ....Information .
Page 495
ASC/ASCQ Stack ....Error Detection Point ... 137363456 Host ID ....Array Software Revision Level .
Page 496
Total Errors Corrected By Applying Retries = Total Errors Corrected 10343 Total Times Correction Algorithm Processed = 10343 Total Bytes Processed (0x00000034cb6a8800) Total Uncorrected Errors Verify Errors ------------------------------------------ Errors Corrected Without Substantial Delay = Errors Corrected With Possible Delays Total Errors Corrected By Applying Retries = Total Errors Corrected Total Times Correction Algorithm Processed = Total Bytes Processed...
Page 502
unbind controller # LUN # AR60DIAG> unbind controller 1 lun 2 ******************************************************************* ******** ***** ***** ***** W A R N I N G W A R N I N G W A R N I N G ***** ***** ***** ***** UNBIND is a destructive command.
Page 504
File Description File Description healthcheck.zip The zip file for a complete first installation. readmefirst.doc The complete installation guide. updateinfo.doc Update info concerning script, program and database. HealthCheck.jar The java program that will be updated as needed. Check The Unix script used to collect data from the system. database.jar This is the device database file.
Page 507
TROUBLESHOOTING Introduction ............508 Installation Problem Solving Checklist .
Page 509
Customer Field Replaceable Units Replaceable Swappable Unit Modules Disk Enclosure Disk Modules BCC (Bus Controller Card) Modules – Note - disk enclosure should be powered down when replacing the BCC. Power Supply Modules Disk Fan Modules Disk Carrier Assembly Power Button Assembly Midplane/Mezzanine Assembly Controller Enclosure Controller Modules...
Page 511
Critical An event that causes host system downtime, or other loss of service. Host system operation will be affected if the disk system continues to be used without correction of the problem. Immediate action is required. Serious An event that may cause, host system downtime, or other loss of service if left uncorrected.
Page 512
Notification Time: Thu Aug 6 15:18:03 1998 yourserver sent Event Monitor notification information: /peripherals/events/mass_storage/LVD/enclosure/10_12.8.0.255.0.10.0 is !=1. Its current value is CRITICAL(5) Event data from monitor: Event Time: Thu Aug 6 15:18:03 1998 Hostname: yourserver.rose.hp.com IP Address: 15.43.212.175 Event ID: 0x0035ca2b9b00000002 Monitor: dm_ses_enclosure Event # : 101 Event Class: I/O...
Page 520
A Power On LED B Power Fault LED C Fan Fault LED D Controller Fault LED E Fast Write Cache LED F Controller Power LED G Controller Fault LED H Heartbeat LED I Status LEDs J Fault B LED K Full Charge B LED L Fault A LED M Full Charge A LED N Power 1 LED...
Page 521
Module Normal State Controller Power On On (green) Enclosure Power Fault Fan Fault Controller Fault Fast Write Cache On (green) while data is in cache Controller Controller Power On (green) Controller Fault Heartbeat Blink (green) Status Green There are 8 status LEDs. The number and pattern of these LEDs depend on how your system is configured.
Page 523
l indicates the LED is ON or Flashing. Note that a Note...
Page 524
Note l indicates the LED is ON or Flashing. Note that a Note...
Page 525
Note Note l indicates the LED is On or Flashing. Note that a Note 0x01 0x03 0x07 0x0F 0x1F...
Page 526
0x3F 0x7F 0xFF 0x7F 0x3F 0x1F 0x0F 0x07 0x03 0x01 0x03, etc... l indicates the LED is On or Flashing. Note that a Note Description LED Pattern In-between programming steps 0x80 Erasing boot flash segments 0x81 Writing boot flash segments 0x82 Verifying erase of boot segments 0x83...
Page 527
Verifying erase of file flash segments 0x8B Verifying write of file flash segments 0x8C...
Page 531
l indicates the LED is On or Flashing. Note that a Note Error LED Pattern Download file is lacking header record. 0x61 Download file header fails checksum test. 0x64 Download file header contains unexpected download type. 0x65 The user should attempt to download a known good file. 0x67 Intermodule error call to flash function passed bad flash type.
Page 532
Kernel missing, or kernel CRC mismatch. The user must download a 0xE7 matching combination of controller Bootware and controller Application Firmware. Application Firmware missing, or Application CRC mismatch. The user 0xE8 must download a version of controller Application Firmware that matches the currently loaded controller Bootware.
Page 533
l indicates the LED is On or Flashing. Note that a Note Code Description Comments Cause / Solution 0x20 Kernel Start Kernel Init. status Controller module / reseat or replace 0x21 Kernel cache initialization 0x22 Kernel IDT set-up 0x23 Kernel hardware initialization 0x24 Kernel initialization 0x25...
Page 534
Code Description Comments Cause / Solution 0x36 Processor DRAM diagnostics HW Diag. status Controller module / 0x00 running reseat or replace 0x37 RPA DRAM diagnostics running 0x00 0x38 Processor Level 2 Cache 0x00 diagnostics running 0x44 CDC diagnostics running 0x01 0x44 SIO diagnostics running 0x02...
Page 537
Code Description Comments Cause / Solution 0x91 Intermodule error call to flash Firmware file is bad / Download Firmware function passed bad flash type with a good file. Attempt to download Firmware again. If the problem persists, replace the controller module. 0x92 Invalid address in flash device Firmware file is bad / Download Firmware...
Page 538
Code Description Comments Cause / Solution 0xAC Load Boot Menu Boot Funct. Status Controller module / reseat or replace 0xAD Invoke Boot Menu 0xAE Exit Boot Menu 0xAF Test Diagnostics Manager Memory problem / memory reseat or replace 0xB0 Load Diagnostics Manager Controller module / reseat or replace 0xB1...
Page 539
Code Description Comments Cause / Solution 0xE6 Software load failure Firmware file is bad / Download Firmware 0x66 RPA parity error with a good file. 0xE7 Kernel missing, or kernel CRC mismatch 0xE8 Application Firmware missing, or Application CRC mismatch 0xEA Swapped controller Controller is in wrong...
Page 545
Table 67 Controller Enclosure Troubleshooting Flowchart (Sheet 1 of 5) Start Look at the Array Controller’s Power LED on? FRONT PANEL LEDs Array Enclosure Power Problem Check for: 1. Power Cords Power is being 2. Power Switch applied to the Array 3.
Page 546
Table 67 Controller Enclosure Troubleshooting Flowchart (Sheet 2 of 5) Is the Go to FRONT PANEL Controller Fault LED Controller Subsystem FAULT. Open door and look at each Controller module for: Contact the - Power LED - Fault LED Response - 8 Status LEDs Center THIS Controller is unseated...
Page 547
Table 67 Controller Enclosure Troubleshooting Flowchart (Sheet 3 of 5) Is the FRONT COVER Fan Fault LED on? Go To Subsystem FAULT. Bad Power Supply Fan Power Supply Fan module. Replace the Fault LED on? power supply fan module. Reseat the Power Front Cover Supply fan Module Fan Fault?
Page 548
Table 67 Controller Enclosure Troubleshooting Flowchart (Sheet 4 of 5) Is the FRONT COVER Power Supply Fault LED Inspect both power supply module power LEDs. Is the FRONT COVER power supply Fault LED on? Power Supply A power LED on? Go to Possible Causes: 1.
Page 549
Table 67 Controller Enclosure Troubleshooting Flowchart (Sheet 5 of 5) Go to Is the Fault-A Has the new The BBU has failed. or Fault-B BBU BBU fully charged Replace the BBU LED on? in 7 hours? Full Charge-A Has the BBU Wait 7 hours been charging for for BBU to fully...
Page 550
Symptom Possible Cause Procedure Controller LED (front A Controller missing or Check the Power LEDs on both controller cover) is ON and the unplugged modules. If one Power LED is off, make fan LED is off. sure that the module is plugged in correctly and its handles are locked in place.
Page 551
Controller Slots Controller Midplane 5 Volt Connectors 12 Volt Connector Battery Connector SCSI Drive Fibre Host Connectors Connectors Fibre Host ID Switches...
Page 553
Symptom Possible Cause Procedure Power LEDs (front and A Other FRUs are missing – Check all FRUs in the controller power supply FRUs) or not installed correctly. enclosure and make sure they are are ON but all other installed securely. If this does not fix the Power LEDs are off problem, go to cause B.
Page 554
Symptom Possible Cause Procedure Software errors occur A Software function or – Check the appropriate software and when attempting to configuration problems documentation to make sure the system access controller or is set up correctly or that the proper disks command was executed.
Page 555
Controller Fan CRU Ventilation Holes Power Supply Fan CRU...
Page 561
Symptom Possible Cause Procedure Fan Fault LED is on One or both of the fans in Replace the controller fan module. the controller fan module has failed. The power supply fan 1. Make sure the power supply fan module module is unplugged or is plugged in correctly.
Page 568
Symptom Possible Cause Procedure Fault-A or Fault-B LED A Left or right battery bank – Replace the is on has failed. Full Charge-A or Full A Left or right battery bank – Turn on the power and allow controller Charge-B LED is off is not yet fully charged.
Page 573
Symptom Possible Cause Procedure No power to the controller Power switches are turned Turn on both power switches on the module (all Power LEDs off. controller enclosure. off) Turn on the main circuit breakers in the rack, if applicable. Power cords unplugged. Make sure all power cords are plugged in securely.
Page 588
Table 73 Symptom Possible Cause Procedure Controller Controller LED (front A Controller missing or Check the power LEDs on both controller cover) is on and the unplugged modules. If a Power LED is off, make sure Fan Fault LED is off. that the module is plugged in correctly and its handles are locked in place.
Page 589
Table 73 (cont’d) Symptom Possible Cause Procedure Controller enclosure Controller enclosure fan 1. Stop all activity to the controller module and Fan Fault LED failure caused one or both and turn off the power. (front cover) are on controller(s) to overheat 2.
Page 590
Table 73 (cont’d) Symptom Possible Cause Procedure Software errors occur A Software function or Check the appropriate software and when attempting to configuration problems documentation to make sure the system is access controller or set up correctly or that the proper command disks was executed.
Page 591
Table 73 (cont’d) Symptom Possible Cause Procedure Controller Fan Module Fan Fault LED is on One or both of the fans in Replace the controller fan module. the controller fan module has failed. The power supply fan 1. Make sure the power supply fan module module is unplugged or is plugged in correctly.
Page 592
Table 73 (cont’d) Symptom Possible Cause Procedure “Battery Low” error Power turned OFF for Turn ON the power and allow controller issued by software extended period and module to run 7 hours to recharge the drained battery power. batteries. If after 7 hours, the battery low error persists, replace the BBU.
Page 593
Table 73 (cont’d) Symptom Possible Cause Procedure One Power Supply LED A Power supply module is Plug in the power cord and turn ON the (FRU) is ON and the turned OFF or power switch. If the LED remains off, go to other is off unplugged.
SureStore E Disk System SC10 Troubleshooting AUTION...
Page 595
A System fault LED B System power LED C Disk activity LED D Disk fault LED E Power On LED F Term. Pwr. LED G Full Bus LED H BCC Fault LED I Bus Active LED J LVD LED K Fan Fault LED State Indication System Power...
Page 596
State Indication BCC Fault Amber Self-test / Fault Normal operation Flashing Peer BCC DIP switch settings do not match Green Bus operating in LVD mode Bus operating in single-ended mode Term. Pwr. Green Termination power is available from the host. Normal operation.
Page 597
Note Fans, Power Component/Status Disks BCCs Supplies Sensors AM60: Good Component is installed and no error conditions are known. STM: Optimal AM60: Critical Hardware has failed. Voltage/temperature STM: Fault - 2 exceeds critical limit. AM60: Non-critical BCC A and B Voltage/temperature STM: Fault - 3 have different...
Page 598
Problem HW Event Description Category LED State Status Probable Cause/Solution The disk none System none – Neither power cord is plugged in. enclosure does Power LED – The power switch is not pressed. not power on – AC breaker is tripped. –...
Page 599
Problem HW Event Description Category LED State Status Probable Cause/Solution Power Supply Critical Amber Critical – An incompatible or defective LED is amber component caused a temporary fault. – Power supply hardware is faulty. Unplug the power cord and wait for the LED to turn off.
Page 600
Problem HW Event Description Category LED State Status Probable Cause/Solution Peer BCC status, Major none Both BCCs: Firmware on BCC A and BCC B are temperature and Warning Non-critical different versions. voltage are Not none Internal bus is faulty. Contact HP Available Available technical support to replace...
Page 609
Customer Field Replaceable Units Hot swappable Replaceable Disk Enclosure Disk & Filler Modules Disk Fan Modules Power Supply Modules BCC (Bus Controller Card) Modules Disk Enclosure (from rack) Front Cover Door Top Cover (Enclosure) Power Button Assembly Backplane/Mezzanine Assembly Disk Carrier Assembly Controller Enclosure Front Cover Controller Fan Module...
Page 612
Note AUTION WARNING To avoid electric shock hazard, do not touch the backplane or adjacent drive electronics when removing and inserting disks. Note...
Page 630
WARNING The disk enclosure weighs approximately 80 lbs. (36 kgs.) without disks. If you choose to remove the disk enclosure from the rack, use two people or a lift device.
Page 648
To Remove: Loosen captive screw, pull firmly on handle, and remove CRU. To Install: Push controller fan CRU firmly into slot and tighten captive screw.
Page 689
Option Description Controller Options (must order one option) Single controller module with 256 Mbyte cache, one Media Interface Adaptor, and one controller slot filler module. Configured with HP-UX firmware. Two controller modules with 256 Mbyte cache and two Media Interface Adaptors. Configured with HP-UX firmware.
Page 690
Number of A5294A/AZ Number of SCSI cables per A5277A/AZ per A5294A/AZ 1,2, or 3 4, 5, or 6...
Page 691
Option Description Delete one 2m cable included in A5294A product and add one 5m VHDCI SCSI cable for connection of A5277A to A5294A in a different rack Option Description Note: All disk enclosures ordered with a single A5277A/AZ must have identical Storage Capacity Options. 4, 9-Gbyte 10K rpm disk drives 8, 9-Gbyte 10K rpm disk drives 10, 9-Gbyte 10K rpm disk drives...
Page 692
Order No. Description A5276A 9.1-Gbyte disk drive module 10K rpm Ultra 2 LVD A5282A 18.2-Gbyte disk drive module 10K rpm Ultra 2 LVD A5633A 18.2-Gbyte disk drive module 15K rpm Ultra 2 LVD A5595A 36.4-Gbyte disk drive module 10K rpm Ultra 2 LVD A5622A 73.4-Gbyte disk drive module 10K rpm Ultra 2 LVD A5278A...
Replaceable Parts Exchange Part Number Field Replaceable Units Part # A5278-60001 A5278-69001 HP-UX Controller Module (5v model ) w/32 MB SIMM (no cache DIMMs) This part has been replaced by the A5278- 60006. A5278-60006 A5278-69006 HP-UX Controller Module (3.5v model ) w/32 MB SIMM (no cache DIMMs) A5635-60002...
Page 695
Exchange Part Number Field Replaceable Units Part # A5277-60004 Power Supply Modules A5277-60002 Power Supply Fan Module A5277-60001 Front Door Assembly 5021-1121 Terminator, SCSI, 68 pin, LVD 5064-2464 Media Interface Adapter (MIA) 348-0038143 +5v Power Harness 348-0038144 +12v Power harness 348-0038145 Battery Harness 348-0038942...
Page 696
Replacement Part Exchange Part Order No. Part Description Order No. A5272-67003 Backplane and mezzanine assy. A5236-60021 Mezzanine board A5272-67004 Bus Control Card (BCC) A5272-69004 J1525-60001 Half-U rack filler panel A5250-60001 Rail kit, E3660 series A5251-60001 Rail kit, Rack System/E A5635-60001 Rail kit, Rittal 9000 racks A5236-60009 Disk filler assembly...
A5277A/AZ Controller Enclosure Specifications Height Width Depth 6.75 inches (17.1 cm) 17.5 inches (44.5 cm) 24 inches (61 cm) Weight of Each Component (lbs) Quantity Subtotal (lbs) Controller modules 13.2 Controller Fan Battery 21.4 21.4 Power Supply Power Supply Fan Front Cover Chassis 31.6...
Page 698
Voltage Typical Maximum In-Rush Current Operating Operating Current Current 100 - 127 VAC 1.5 A 2.3 A 21.7 A 220 - 240 VAC 0.8 A 1.2 A 42.9 A Incoming Voltage AC RMS Typical Power Consumption 100- 127 VAC 180 watts 200 - 240 VAC 180 watts...
A5294A/AZ Disk Enclosure Specifications Height Width Depth 5.91 in. (15.0 cm) 18.9 in. (48.0 cm) 27.2 in. (69.1 cm) Component Weight of Each (lbs) Quantity Subtotal (lbs) Disk Drive (HH) 3 .3 Power Supply 10.6 Midplane-Mezzanine Door Chassis Total, Approx. 110 lbs.
Page 702
Voltage Typical Current Maximum Current 100 - 127 VAC 4.8 a 6.5 a 220 - 240 VAC 2.4 a 3.2 a 50-60 Hz , single phase, power factor corrected Incoming Voltage AC RMS Typical Power Consumption 100- 127 VAC 347 watts 200 - 240 VAC 347 watts...
Warranty and License Information Replacement Parts HP replacement parts assume the remaining warranty of the parts they replace. Warranty life of a part is not extended by means of Warranty replacement. Items Not Covered Your HP SureStore E Disk Array FC60 warranty does not cover the following: –...
Page 706
Ninety-Day Limited Software Warranty. Removable Media (if supplied). Notice of Warranty Claims.
Page 707
Limitation of liability and Remedies. TO THE EXTENT ALLOWED BY LOCAL LAW, THE REMEDIES IN THIS WAR-...
Page 708
RANTY STATEMENT ARE CUSTOMER’S SOLE AND EXCLUSIVE REMEDIES. EXCEPT AS INDICATED ABOVE, IN NO EVENT WILL HP OR ITS SUPPLIERS BE LIABLE FOR LOSS OF DATA OR FOR DIRECT, SPECIAL, INCIDENTAL, CONSE- QUENTIAL (INCLUDING LOST PROFIT OR DATA), OR OTHER DAMAGE, WHETHER BASED IN CONTRACT, TORT, OR OTHERWISE.
Page 716
1.)This product was tested with Hewlett-Packard Unix server host computer system. Boise Idaho U.S.A., 03/22/99 Dan T. Michauld / QA Manager European Contact: Your local Hewlett-Packard Sales and Service office or Hewlett-Packard GmbH, Department HQ-TRE, Herrenberger Straße 130, D-71034 Boblingen (FAX +49-7031-14-3143)
Need help?
Do you have a question about the Surestore Disk Array 12h - And FC60 and is the answer not in the manual?
Questions and answers