Troubleshooting Guide HP StorageWorks HSG60 and HSG80 Array Controller and Array Controller Software Product Version: 8.8-1 Third Edition (March 2005) Part Number: EK-G80TS-SA.C01 This guide provides troubleshooting instructions for HSG60 and HSG80 array controllers running Array Controller Software (ACS) Versions 8.8L, 8.8F, 8.8G, 8.8P, and 8.8S. This guide contains information on various utilities, software templates, and event reporting codes.
© Copyright 2000–2005 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
contents Contents About this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Intended audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Caching techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Read caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Read-ahead caching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Write-through caching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Writeback caching .
Contents Host Ports Statistics screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Resource Statistics screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Remote Status screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Interpreting VTDPY screen information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Screen header. . . . . . . .
Contents Device Services Nontransfer Error Event Sense Data Response template (Template 41). . Disk Transfer Error Event Sense Data Response template (Template 51). . . . . . . . . . . . . . Data Replication Manager Services Event Sense Response template (Template 90) . . . . . Connection Table Full Event Error template (Template A0) . . . . . . . . . . . . . . . . . . . . . . . . 153 155 157 159 4 ASC, ASCQ, Repair Action, and Component Identifier Codes . . . . . . . . . . . . . . . . .
Contents Figures 1 OCP pattern display showing %FLL formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 2 Sample Last Failure report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 3 Sample Spontaneous Event logs showing %EVL formatting . . . . . . . . . . . . . . . . . . . . . 40 4 Sample CLI Event report showing %CER formatting. . . . . . . . . . . . . . . . . . . . . . . . . . . 41 5 SHOW THIS CLI sample screen display. . . . . .
Contents 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 DWD Status Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 EC Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Event Code Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 45 Template 41—Device Services Non-Transfer Error Event Sense Data Response Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Template 51—Disk Transfer Error Event Sense Data Response Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Template 90—Data Replication Manager Services Event Sense Data Response Format for ACS V8.
Contents 10 HSG60 and HSG80 Array Controller and Array Controller Software Troubleshooting Guide
about this guide About this Guide This troubleshooting guide provides information to help you troubleshoot problems with HP StorageWorks HSG60 and HSG80 array controllers.
About this Guide Intended audience This document for users who are experienced with the following: ■ HSG60 and HSG80 array controllers ■ HP StorageWorks Array Controller Software (ACS) ■ HP StorageWorks BA370 enclosure and enclosure components ■ HP StorageWorks M2100 and M2200 enclosures and enclosure components Prerequisites Before you complete procedures in this document, consider the following items: ■ Know what version of ACS is currently in use.
About this Guide Table 1: Related Documentation (Continued) Item Document Name Document Part Number 4. HP StorageWorks Replacing a Gigabit Link Module (GLM) in an HSG60 or HSG80 Array Controller Installation Instructions EK-80GLM-TE. D01 5. HP StorageWorks Replacing DIMMs in an HSG60 or HSG80 Cache Module Installation Instructions EK-80DIM-IM. E01 6. HP StorageWorks Replacing an HSG60 or HSG80 Cache Module Installation Instructions EK-80CAH-IM. F01 7.
About this Guide Table 1: Related Documentation (Continued) Item Document Name Document Part Number 19. HP StorageWorks HSG80 ACS Solution Software Version 8.8 for Sun Solaris Installation and Configuration Guide AA- RV1RA -TE 20. HP StorageWorks HSG80 Enterprise/Modular Storage RAID Array Fibre Channel Solution Software Version 8.8 for Sun Solaris Release Notes AA- RV1SA -TE 21. HP StorageWorks Command Console Version 2.4 Release Notes AV- RV1TA -TE 22.
About this Guide Conventions Conventions consist of the following: ■ Document conventions ■ Text symbols ■ Equipment symbols Document conventions This document follows the conventions in Table 2.
About this Guide Tip: Text in a tip provides additional help to readers by providing nonessential or optional techniques, procedures, or shortcuts. Note: Text set off in this manner presents commentary, sidelights, or interesting points of information. Equipment symbols The following equipment symbols may be found on hardware for which this guide pertains.
About this Guide Power supplies or systems marked with these symbols indicate the presence of multiple sources of power. WARNING: To reduce the risk of personal injury from electrical shock, remove all power cords to completely disconnect power from the power supplies and systems. Any product or assembly marked with these symbols indicates that the component exceeds the recommended weight for one individual to handle safely.
About this Guide Getting help If you still have a question after reading this document, contact an HP authorized service provider or access our website: http://www.hp.com. HP technical support Telephone numbers for worldwide technical support are listed on the following HP website: http://www.hp.com/support/. From this website, select the country of origin. Note: For continuous quality improvement, calls may be recorded or monitored.
Troubleshooting Information 1 This chapter provides guidelines for troubleshooting the controller, cache module, and external cache battery (ECB).
Troubleshooting Information Typical installation problem identification checklist and troubleshooting guidelines The following checklist identifies problems that occur in a typical installation. After identifying a problem, use Table 4 on page 22 to confirm the diagnosis and fix the problem. If an initial diagnosis points to several possible causes, use the tools described in this chapter and then those in the “Utilities and Exercisers” chapter that starts on page 67 to further refine the diagnosis.
Troubleshooting Information Table 3: Installation Problem Identification Checklist (Continued) Item 7. Troubleshooting Task Done (W) Use the Fault Management Utility (FMU) for last failure or memory system failure entries. Show these codes and translate the Last Failure Codes they contain. For more information, see the “Utilities and Exercisers” chapter on page 67, “Displaying last failure entries” section that starts on page 68, and “Translating event codes” section that starts on page 70.
Troubleshooting Information After identifying a problem, use Table 4 to resolve the problem. Table 4: Troubleshooting Guidelines (Sheet 1 of 9) Symptom Possible Cause Investigation Remedy Check power to subsystem and power supplies on controller enclosure. Replace cord or (BA370 enclosure only) AC input box. BA370 enclosure only: Ensure that all cooling fans are installed. If one or more fans are missing or all are inoperative for more than 8 minutes, the EMU shuts down the subsystem.
Troubleshooting Information Table 4: Troubleshooting Guidelines (Sheet 2 of 9) Symptom Possible Cause Investigation Remedy Incorrect command syntax. See the controller CLI reference guide for the SET FAILOVER command. Use the correct command syntax. Different software versions on controllers. Check software versions on both controllers. Update one or both controllers so that both use the same software version. Incompatible hardware. Check hardware versions.
Troubleshooting Information Table 4: Troubleshooting Guidelines (Sheet 3 of 9) Symptom Possible Cause Investigation Node ID is all zeros. SHOW_THIS to see if node ID is all zeros. Remedy Set node ID by using the node ID (bar code) that is located on the frame in which the controller sits. Refer to SET THIS_CONTROLLER NODE_ID in the controller CLI reference guide. Also, be sure to copy in the right direction. If cabled to the new controller, use SET FAILOVER COPY= OTHER_CONTROLLER.
Troubleshooting Information Table 4: Troubleshooting Guidelines (Sheet 4 of 9) Symptom Possible Cause Investigation Mirrored cache: "this controller" reports DIMM 3 or 4 failed in Cache A or B. Mirrored cache: controller reports battery not present. Mirrored cache: controller reports cache or mirrored cache has failed. Remedy Improperly installed DIMM in "other controller" cache module. Remove cache module and ensure that the DIMMs are installed properly. Reseat DIMM.
Troubleshooting Information Table 4: Troubleshooting Guidelines (Sheet 5 of 9) Symptom Possible Cause Investigation Invalid cache. 26 Mirrored-cache mode discrepancy. This discrepancy can occur after installing a new controller. The existing cache module is set for mirrored caching, but the new controller is set for unmirrored caching. This discrepancy can also occur if the new controller is set for mirrored caching, but the existing cache module is not. SHOW THIS_CONTROLLER indicates invalid cache.
Troubleshooting Information Table 4: Troubleshooting Guidelines (Sheet 6 of 9) Symptom Possible Cause Investigation Cache module can erroneously contain unflushed writeback data. This can occur after installing a new controller. The existing cache module might indicate that the cache module contains unflushed writeback data, but the new controller expects to find no data in the existing cache module.
Troubleshooting Information Table 4: Troubleshooting Guidelines (Sheet 7 of 9) Symptom Possible Cause Investigation Cannot add device. 28 Remedy Illegal device. See product-specific release notes that accompanied the software release for the most recent list of supported devices. Replace device. Device not properly installed in enclosure. Ensure that the device is fully seated. Firmly press the device into the bay. Failed device. Check for presence of device LEDs.
Troubleshooting Information Table 4: Troubleshooting Guidelines (Sheet 8 of 9) Symptom Possible Cause Investigation Remedy Incorrect command syntax. See the controller CLI reference guide for the appropriate ADD command. Reconfigure storageset with correct command syntax. Exceeded maximum number of storagesets. Use the SHOW STORAGESETS command to count the number of storagesets configured on the controller. Delete unused storagesets. Failed battery on ECB.
Troubleshooting Information Table 4: Troubleshooting Guidelines (Sheet 9 of 9) Symptom Possible Cause Investigation Host cannot access unit. Host files or device drivers not properly installed or configured. Check for the required device special files. Configure device special files as described in the installation and configuration guide that accompanied the software release. Invalid Cache. See the description for the invalid cache symptom on page 26.
Troubleshooting Information Significant event reporting The controller fault management software reports information about significant events that occur. These events are reported by: ■ Maintenance terminal displays. ■ Host error logs. ■ OCP LEDs. Some events cause controller operation to halt; others allow the controller to remain operable. Both types of events are detailed in the following sections.
Troubleshooting Information Flashing OCP pattern display reporting Certain events can cause a flashing display of the OCP LEDs. Each event and the resulting pattern are described in Table 5. Note: Remember that a solid black pattern represents a flashing display. A white pattern indicates off. All LEDs flash at the same time and at the same rate. Table 5: Flashing OCP Pattern Displays and Repair Actions OCP Code Error nmmmmml 1 Program card EDC error. Replace program card.
Troubleshooting Information Table 5: Flashing OCP Pattern Displays and Repair Actions (Continued) Pattern OCP Code Error Repair Action nmlmmlm 12 Controller module memory addressing is malfunctioning. Replace controller. nmlmmll 13 Controller module memory parity is not working. Replace controller. nmlmlmm 14 Controller module memory controller timer has failed. Replace controller. nmllmml 15 Controller module memory controller interrupt handler has failed. Replace controller.
Troubleshooting Information Table 5: Flashing OCP Pattern Displays and Repair Actions (Continued) Pattern OCP Code Error Repair Action nllllmm 3C An unexpected fault occurred during initialization. Replace controller. nllllml 3D An unexpected maskable interrupt occurred during initialization. Replace controller. nlllllm 3E An unexpected NMI occurred during initialization. Replace controller. nllllll 3F An invalid process ran during initialization. Replace controller.
Troubleshooting Information Table 6: Solid OCP Pattern Displays and Repair Actions (Sheet 1 of 5) Pattern OCP Code Error Repair Action ommmmmm 0 Catastrophic controller or power failure occurred. Check power. If good, reset controller. If problem persists, reseat controller module and reset controller. If problem is still evident, replace controller module. nmmmmmm 0 No program card detected or kill asserted by OTHER CONTROLLER.
Troubleshooting Information Table 6: Solid OCP Pattern Displays and Repair Actions (Sheet 2 of 5) Pattern nlmlmml OCP Code 29 Error EMU protocol version incompatible. The microcode in the EMU and the software in the controller are not compatible. nlmlmlm 2A All enclosure I/O modules are not of the same type. Enclosure I/O modules are a combination of single-ended and differential. nlmlmll 2B Jumpers, not terminators, found on backplane.
Troubleshooting Information Table 6: Solid OCP Pattern Displays and Repair Actions (Sheet 3 of 5) Pattern nlmlllm OCP Code 2E Error Multiple enclosures have the same SCSI ID. More than one enclosure has the same SCSI ID. Repair Action Reconfigure the PVA ID to uniquely identify each enclosure in the subsystem. The enclosure with the controllers must be set to PVA ID 0; additional enclosures must use PVA IDs 2 and 3.
Troubleshooting Information Table 6: Solid OCP Pattern Displays and Repair Actions (Sheet 4 of 5) Pattern nllmlml OCP Code 35 Error An unexpected bugcheck occurred during Last Failure processing. Repair Action Reset controller. Last failure processing interrupted by another last failure event. nllmllm 36 Hardware-induced controller reset expected and failed. Replace controller. nllmlll 37 Software-induced controller reset expected and failed. Replace controller.
Troubleshooting Information Table 6: Solid OCP Pattern Displays and Repair Actions (Sheet 5 of 5) Pattern nllllmm OCP Code 3C Error NVPM write loop hang occurred. Repair Action Replace controller. Attempt to write data to NVPM failed. nllllml 3D NVPM structure revision is higher than image. NVPM structure revision number is higher than the one that can be handled by the software version attempting to execute. nllllll 3F DAEMON diagnostic failed hard in non-fault tolerant mode.
Troubleshooting Information Last Failures are also reported to the host error log on Template 01, following a restart of the controller. For a detailed explanation of this template, see the “ASC, ASCQ, Repair Action, and Component Identifier Codes” chapter that starts on page 161.
Troubleshooting Information Spontaneous Event logs are reported to the Host Error log on SCSI Sense Data Templates 01, 04, 05, 11, 12, 13, 14, 41, 51, and 90. See the “Event Reporting Templates” chapter on page 135 for a detailed explanation of templates.
Troubleshooting Information ECB charging diagnostics After restarting the controller, the diagnostic routines automatically check the charge of each ECB battery. If the battery is fully charged, the controller reports the battery as good and rechecks the battery every 24 hours. If the battery is charging, the controller rechecks the battery every 4 minutes. A battery is reported as being either above or below 50 percent capacity. A battery below 50 percent capacity is referred to as low.
Troubleshooting Information UPS used for backup power If a UPS is used for backup power and the controllers are set to DATACENTER_WIDE, the controllers check the battery and indicate if a battery failure exists, but they do not take any action (see Figure 5 for an example of the screen display after issuing the SHOW THIS CLI command): HSG> SHOW THIS Controller: HSG80 ZG93413884 Software V88.
Troubleshooting Information Caching techniques The cache module supports the following caching techniques to increase subsystem read and write performance: ■ Read caching ■ Read-ahead caching ■ Write-through caching ■ Writeback caching Read caching If the controller receives a read request from the host, the controller reads the data from the disk drives, delivers the data to the host, and stores the data in the supporting cache module.
Troubleshooting Information Write-through caching After the controller receives a write request from the host, the controller places the data in the supporting cache module, writes the data to the disk drives, and then notifies the host that the write operation is complete. This process is called write-through caching because the data actually passes through—and is stored in—the cache memory along the way to the disk drives.
Troubleshooting Information Nonvolatile memory The controller provides writeback caching for storage units as long as the controller cache memory is connected to a nonvolatile backup power source, such as an ECB. The cache module must be nonvolatile to preserve unwritten cache data during a power failure. If the cache memory is not connected to a backup power supply, this unwritten data is lost during a power failure.
Troubleshooting Information Note: Disaster-tolerant mirrorsets are not subject to this requirement. By default, the controller expects to use an ECB as the backup power source for the supporting cache module.
Troubleshooting Information Table 8: Cache Policies—Cache Module Status (Continued) Cache Module Status Cache Policy Cache A Cache B Multibit cache memory failure. Good. Unmirrored Cache Mirrored Cache Data loss: Forced error and loss of writeback data for which the multibit error occurred. Controller A detects and reports the lost blocks. Data loss: None. Controller A recovers lost writeback data from the mirrored copy on Cache B. Cache policy: Both controllers support writeback caching.
Troubleshooting Information Table 8: Cache Policies—Cache Module Status (Continued) Cache Module Status Cache A Cache B DIMM or cache memory controller chip failure. Good. Cache Policy Unmirrored Cache Data loss: Writeback data that was not written to media when failure occurred was not recovered. Cache policy: Controller A supports write-through caching only; Controller B supports writeback caching. ■ Failover: In Transparent Failover, all units fail over to Controller B.
Troubleshooting Information Table 8: Cache Policies—Cache Module Status (Continued) Cache Module Status Cache Policy Cache A Cache B Cache board failure. Good. Unmirrored Cache Mirrored Cache Same as for DIMM failure (see page 49). Data loss: Controller A recovers all of writeback data from the mirrored copy on Cache B. Cache policy: Both controllers support write-through caching only. Controller B cannot execute mirrored writes because Cache A cannot mirror Controller B unwritten data.
Troubleshooting Information Table 9: Resulting Cache Policies—ECB Status (Continued) ECB Status Cache A Cache B Less than 50% charged. At least 50% charged. Cache Policy Unmirrored Cache Mirrored Cache Data loss: None. Data loss: None. Cache policy: Controller A supports write-through caching only; Controller B supports writeback caching. Cache policy: Both controllers continue to support writeback caching. Failover: In Transparent Failover, all units fail over to Controller B. Failover: None.
Troubleshooting Information Table 9: Resulting Cache Policies—ECB Status (Continued) ECB Status Cache Policy Cache A Cache B Less than 50% charged. Less than 50% charged. Failed. Less than 50% charged. Unmirrored Cache Mirrored Cache Data loss: None. Data loss: None. Cache policy: Both controllers support write-through caching only. Cache policy: Both controllers support write-through caching only. Failover: None. Failover: None. Data loss: None. Data loss: None.
Troubleshooting Information Dual external cache battery failures The array controller cache policy provides for proper handling of a single ECB failure as described in this guide. For dual ECB failures, it states that no failover occurs. If a dual ECB failure is detected, both controllers are restarted.
Troubleshooting Information %EVL--hsg80_bot> --08-JUN-2004 11:37:26-- Instance Code: 03D04002 Template: 65.(41) Occurred on 08-JUN-2004 at 11:37:11 Power On Time: 2. Years, 79. Days, 13. Hours, 34. Minutes, 26. Seconds Controller Model: HSG80 Serial Number: ZG95114377 Hardware Version: E11(29) Software Version: V88F-0(FF) Port: 1. Target: 3. ASC: (3F) ASCQ: (85) OP|KEY: x0004 1 1 2 3 2 3 ST: x17 EC: 9. 5 4 Test unit ready or read capacity command 4 failed (refer to Table 48 on page 162).
Troubleshooting Information Table 10: DWD Status Codes (Continued) Code Description 0x09 Short record. 0x0a Long record. 0x0b Tape flow interlocked condition. 0x0c Some of the data is missing. 0x0d Data is good, command retried. 0x0e Data is good, device retried. 0x0f Device reported media error. 0x10 From device sense data. 0x11 Device reported media error. 0x12 Device reported write protect. 0x13 Disk reported ILI, FM or EOM. 0x14 Device reported. 0x15 See sense data for error.
Troubleshooting Information Table 11 explains the Error Codes (EC). Table 11: EC Codes Code Description 0 Spin failed on drive. 1 Pub device type does not match NVMEM. 2 Unknown device type. 3 Block size not 512 bytes. 4 Exhausted all command retries. 5 Unsupported capacity (too large). 1 6 Blank check from drive. 7 Illegal operation code or field in operation code. 8 Vendor unique problem. 9 Drive is not responding to us. 10 Error with the media. 11 Drive is not functioning.
Troubleshooting Information hsg80_bot> show elevation Nindy is currently OFF Time: 05-JUN-2004 12:00:21 ************************************************************** Power On Time: 0. Years, 0. Days, 0. Hours, 5. Other Minutes, 24. Seconds controller information in full (SHOW OTHER FULL). ************************************************************** ************************************************************** Controller: This controller information in full (SHOW THIS FULL).
Troubleshooting Information ************************************************************** Information of all connections in full (SHOW CONNECTION FULL). ************************************************************** Connection Name Offset Unit Controller ************************************************************** Port Address Status Management information (SHOW MANAGER).
Troubleshooting Information # 001a 4 000e fffe fffe fffe Dv 5:1:0 PUB c0487cac Type 00 Pub st 6 ri 3 BLOX: vaso 17769177, vabbro 17769177, vafediro 17769179, vafeo 17769181 vaconfo 17773521, vaid1 17773522, vsilbnsiz 17769177, vsicontsiz 0 mdatav 11, nodest 0, prev_online 0, size_val 1, id0_gd 0, id1_gd 0, save_c 0, parted 1, sc-dis 0 fe_directory[0]=C01FA100, fe_directory[1]=C0FFCB80 BLOX: vaso 17769177, vabbro 17769177, vafediro 17769179, vafeo 17769181 vaconfo Nv St Up Us Dn Ds 17773521, vaid1 17773522,
Troubleshooting Information Nv St Up Us Dn Ds ------------------------------# 0026 2 fffe fffe fffe fffe Dv 5:8:0 PUB c0486314 Type 00 Pub st 6 BLOX: vaso 17769177, vabbro 17769177, vafediro 17769179, vafeo 17769181 vaconfo 17773521, vaid1 17773522, vsilbnsiz 17769177, disk 0, id1_gd 0, 1 8 0 vsicontsiz 0 mdatav 11, nodest 0, prev_online 0, DISK10800 size_val 1, id0_gd save_c 0, parted 0, sc-dis 0 fe_directory[0]=C01FA100, fe_directory[1]=C0FFCB80 COMPAQ BD009122BA 3B08 Switches: Nv St Up Us Dn Ds NOTRANSP
Troubleshooting Information ************************************************************** Information of all storage sets in full (SHOW STORAGE FULL).
Troubleshooting Information S3 stripeset DISK10300 DISK30300 DISK50300 D110 D120 D130 D140 D150 ************************************************************** Information of all units in full (SHOW UNITS FULL).
Troubleshooting Information D4 D5 D6 D7 S1 (partition) LUN ID: 6000-1FE1-0001-E200-0001-1234-5678-02B6 IDENTIFIER = 4 Switches: RUN NOWRITE_PROTECT Access:READ_CACHE READAHEAD_CACHE WRITEBACK_CACHE ALL MAX_READ_CACHED_TRANSFER_SIZE = 32 State: MAX_WRITE_CACHED_TRANSFER_SIZE = 32 ONLINE to the other controller Access: PREFERRED_PATH = OTHER_CONTROLLER ALL Size: 10661371 blocks State: Geometry (C/H/S): ( 3155 / 20 / 169 ) ONLINE to the other controller NOHOST_REDUNDANT PREFERRED_PATH = OTHER_CONTROLLER D
Troubleshooting Information D110 D120 D130 D140 64 S3 (partition) LUN ID: 6000-1FE1-0001-E200-0001-1234-5678-02C7 IDENTIFIER = 110 Switches: RUN NOWRITE_PROTECT READ_CACHE READAHEAD_CACHE WRITEBACK_CACHE MAX_READ_CACHED_TRANSFER_SIZE = 32 MAX_WRITE_CACHED_TRANSFER_SIZE = 32 MAX_READ_CACHED_TRANSFER_SIZE = 32 Access: MAX_WRITE_CACHED_TRANSFER_SIZE = 32 ALL Access: State: ALL ONLINE to this controller State: Not reserved ONLINE to this controller PREFERRED_PATH = THIS_CONTROLLER Not reserved Size: 10661
Troubleshooting Information State: ONLINE to this controller Not reserved PREFERRED_PATH = THIS_CONTROLLER Size: 10661371 blocks Geometry (C/H/S): ( 3155 / 20 / 169 ) NOHOST_REDUNDANT D180 D190 D199 Access: ALL State: S4 (partition) ONLINE to this controller LUN ID: 6000-1FE1-0001-E200-0001-1234-5678-02D3Not reserved IDENTIFIER = 180 PREFERRED_PATH = THIS_CONTROLLER Switches: Size: 10661371 blocks RUN NOWRITE_PROTECT READ_CACHE Geometry (C/H/S): ( 3155 / 20 / 169 ) READAHEAD_CACHE WRITEBACK_CACHE NOHOS
Troubleshooting Information 66 HSG60 and HSG80 Array Controller and Array Controller Software Troubleshooting Guide
Utilities and Exercisers 2 This chapter describes the utilities and exercisers available to help troubleshoot and maintain the controllers, cache modules, and ECBs.
Utilities and Exercisers Fault Management Utility (FMU) FMU provides a limited interface to the controller fault management software. Use FMU to: ■ Display the last failure and memory-system failure entries that the fault management software stores in the controller nonvolatile memory. ■ Translate many of the code values contained in event messages (for example, entries might contain code values that indicate the cause of the event, the software component that reported the event, or the repair action).
Utilities and Exercisers 3. Show one or more of the entries with the following command: SHOW event_type entry# FULL where: is LAST_FAILURE or MEMORY_SYSTEM_FAILURE. ■ event-type ■ entry# ■ FULL displays is ALL, MOST_RECENT, or 1 through 16. additional information, such as the Intel® i960 stack and hardware component register sets (for example, the memory controller, FX, host port, device ports, and so forth). 4.
Utilities and Exercisers Translating event codes To translate the event codes in the fault management reports for spontaneous events and failures: 1. Connect a PC or a local terminal to the controller maintenance port. 2. Start FMU with the following command: RUN FMU 3. Show one or more of the entries with the following command: DESCRIBE code_type code# where: ■ code_type ■ code# is one of those listed in Table 12. is the alphanumeric value displayed in the entry. Table 12: Event Code Types Item 1.
Utilities and Exercisers Figure 8 shows an example of a FMU translation of a Last Failure Code and an Instance Code. FMU>DESCRIBE LAST_FAILURE_CODE 206C0020 Last Failure Code: 206C0020 Description: Controller was forced to restart in order for new controller code image to take effect. Reporting Component: 32.(20) Description: Command Line interface Reporting component's event number: 108.(6C) Restart Type: 2.
Utilities and Exercisers Table 13: FMU SET Commands Command SET EVENT_LOGGING SET NOEVENT_LOGGING Result Enables and disables the spontaneous display of significant events to the local terminal; preceded by %EVL (see example in the section, “Spontaneous Event log,” that starts on page 40). By default, logging is enabled (SET EVENT_LOGGING). If logging is enabled, the controller spontaneously displays information about the events on the local terminal.
Utilities and Exercisers Table 13: FMU SET Commands (Continued) Command Result SET PROMPT SET NOPROMPT Enables and disables the display of the CLI prompt string following the log identifier %EVL, %LFL, or %FLL. This command is useful if the CLI prompt string is used to identify the controllers in a dual-redundant configuration (refer to the CLI reference guide for instructions to set the CLI command string for a controller).
Utilities and Exercisers Table 13: FMU SET Commands (Continued) Command SET FAULT_LED_LOGGING SET NOFAULT_LED_LOGGING Result Enables and disables the solid fault LED Event log display on the local terminal; preceded by %FLL. By default, logging is enabled (SET FAULT_LED_LOGGING). If enabled and a solid fault pattern is displayed in the OCP LEDs, the fault pattern and its meaning are displayed on the maintenance terminal.
Utilities and Exercisers SHOW RESERVATION command The SHOW RESERVATION command allows full visibility of the reservation and persistent reservation status and displays which connections or hosts exist for units. This command is primarily used by service support resources to obtain a better understanding of the circumstances of a system failure.
Utilities and Exercisers FMU> sho reservations all Unit D0 is reserved, exclusive access to host[0] MVQ621_A0. Unit D1 is reserved, exclusive access to host[1] MVQ621_A1. Unit D2 is reserved, exclusive access to host[0] MVQ621_A0. Unit D3 is reserved, exclusive access to host[1] MVQ621_A1. Unit D4 is reserved, exclusive access to host[0] MVQ621_A0. Unit D5 is reserved, exclusive access to host[1] MVQ621_A1. Unit D6 is reserved, exclusive access to host[0] MVQ621_A0.
Utilities and Exercisers FMU> Show Reservation Unit D1 has a persistent reservation. Host[0] TDRUM00 : R Host[1] SHENG03 : R W Host[2] SHENG02 : R W Host[3] TDRUM02 : R Host[4] SHENG01 : R W Host[6] SHENG00 : R W Unit D1 is registered by Host[1] SHENG03 with key 0x3523000000000010. Unit D1 is registered by Host[2] SHENG02 with key 0x3523000000000010. Unit D1 is registered by Host[4] SHENG01 with key 0x3523000000000010. Unit D1 is registered by Host[6] SHENG00 with key 0x3523000000000010.
Utilities and Exercisers Device Information and Error Utilities Device Information and Error Utilities provide specific system and device error information. ■ The SHOW DEVICE_INFORMATION unit and SHOW DEVICE_INFORMATION ALL FMU commands provide information for every device in the system. ■ The SHOW DEVICE_ERRORS and CLEAR DEVICE_ERRORS unit FMU commands capture and clear device errors, and store them in an Event log.
Utilities and Exercisers FMU> show device_info all P T Model FW Vers S/N on Media FL Metadata vers/SC 06 04 RZ1BB-CS (C) DEC 0844 JEC8849802LX5T 0 9/D 02 01 AD009322C5 A019 93078715 0008 0 11/N 02 04 BD018635C4 B012 79003718 0017 3 9/I 06 01 RZ1BB-CS (C) DEC 0844 JEC8825208T40G 0 11/U 06 03 RZ1BB-CS (C) DEC 0844 JEC880890KC33W 0 11/U 06 05 RZ1BB-CS (C) DEC 0844 JEC883640KC37H 0 11/U FL – Device Flags: Sum of: 1 = Advanced support; 2 = Fairness Support SC - S
Utilities and Exercisers Table 14: Disk Device Information (Sheet 1 of 4) Info Displayed PT Description Port#, Target#. The controller only supports sub-LUN 00; therefore, the sub-LUN is not portrayed. For example, disk40300 would be displayed as follows: Example of output: P T ----04 03 Model Device Model ID. This unique drive model number is assigned by HP and written into the device firmware by the disk drive vendor.
Utilities and Exercisers Table 14: Disk Device Information (Sheet 2 of 4) Info Displayed FW Vers Description Firmware Version. The version of drive firmware is part of the device inquiry string response. Each disk drive vendor specifies content of this string and the disk drive generally increments the string for each new device firmware version. Example of output: FW Vers ---3B05 S/N on Media Serial Number on Media. This 32-character alphanumeric string is unique to each device.
Utilities and Exercisers Table 14: Disk Device Information (Sheet 3 of 4) Info Displayed FL Description Device Flags. The controllers interpretation of the SCSI device characteristics. Example of output: FL --3 FL – Device Flags: Sum of: 1 = Advanced support; 2 = Fairness Support Advanced Support: Devices support certain controller advanced operations such as Automated Read Retry Enabled (ARRE). In the previous example, the value 3 denotes that the device supports advanced support and fairness.
Utilities and Exercisers Table 14: Disk Device Information (Sheet 4 of 4) Info Displayed Metadata Version/SC Description Disk Container Metadata Version and Status of SAVE_CONFIGURATION. If a disk drive is introduced to a controller, and it is not initialized in Transparent Failover mode (refer to CLI reference guide), it is assigned a metadata version number.
Utilities and Exercisers SHOW DEVICE_ERRORS and CLEAR DEVICE_ERRORS unit command SHOW DEVICE_ERRORS command The SHOW DEVICE_ERRORS command captures disk device events and stores a log of events in the controller non-volatile memory (NVMEM). Because each controller stores its own events, each controller log has different entries. As you look for device errors, examine the device error log for each controller. Entries in the log do not always indicate an error. Even healthy drives have logged events.
Utilities and Exercisers Interpreting Event log fields The Event log is listed in reverse chronological order, from most recent to oldest entry. Each event starts with DSEVT followed by the controller date and time of the event. Figure 14 explains the information in the Event log.
Utilities and Exercisers Table 15: Event log interpretation legend Item Description 1 Number of logging events that have occurred since the log was last cleared. 2 Number of event buffers (total). 3 Device SCSI port and target ID. 4 For internal HP use. If Init DWD equals yes, the failed command involves device configuration following a bus reset or controller restart. 5 Logged event code (see the “Common event descriptions” section on page 87). 6 Variable fields depending on the event code.
Utilities and Exercisers Common event descriptions Table 16 contains descriptions for common events. Table 16: Common Event Descriptions Event Description DS_EVENT_PORT_STATUS A general event not decoded to more detail. This does not always indicate a problem but may be relevant in relation to other events. DS_EVENT_SCSI_ERROR A general event not decoded to more detail. This does not always indicate a problem but may be relevant in relation to other events.
Utilities and Exercisers Table 16: Common Event Descriptions (Continued) Event Description The command completed with an error, detailed by the sense key, ASC, and ASCQ. DS_EVENT_UA Note: It is normal to see a series of DS_EVENT_UA, sk:06, asc:29, ascq:02 on each device on that port following a bus reset. Note: It is normal to see DS_EVENT_UA entries with a code sk:05, asc:24, ascq:00, depending on the support level of the drives in the system.
Utilities and Exercisers Video Terminal Display (VTDPY) utility The VTDPY utility, through various screens, displays configuration and performance information for HSG60 and HSG80 storage subsystems, and is used to check the subsystem for communication problems. Information displayed includes: ■ Processor utilization. ■ Virtual storage unit activity and configuration. ■ Cache performance. ■ Device activity and configuration. ■ Host port activity and configuration.
Utilities and Exercisers 2. Set the terminal to Nowrap mode to prevent the top line of the display from scrolling off of the screen. 3. Press Enter or Return to display the CLI prompt. 4. Start VTDPY with the following command: RUN VTDPY Use the key sequences and commands listed in Table 17 to control VTDPY.
Utilities and Exercisers For example, if DISP ? (DISP?) is entered, the utility lists Cache, Default, and other possibilities. Upon successfully executing a command—other than HELP—VTDPY exits Command mode. Pressing Enter or Return without a command also causes VTDPY to exit Command mode. VTDPY help Enter HELP at the VTDPY prompt (VTDPY>) to display information about VTDPY commands and keyboard shortcuts. See Figure 15. Note: The ^ symbol denotes the Ctrl key on the keyboard.
Utilities and Exercisers VTDPY screens VTDPY displays storage subsystem information by using the following display screens: ■ Display Default screen ■ Controller Status screen ■ Cache Performance screen ■ Device Performance screen ■ Host Ports Statistics screen ■ Resource Statistics screen ■ Remote Status screen Display any of the screens by entering DISPLAY at the VTDPY prompt, followed by the screen name.
Utilities and Exercisers VTDPY> DISPLAY DEFAULT HSG80 S/N: ZG92712820 SW: V88P 0.0% Idle Pr Name Stk/ Max 0 NULL 0/ 0 Typ Sta Rn HW: E-01 0 KB/S CPU% 0 Rq/S Target 0.0 111111 Up: 0 22:10.
Utilities and Exercisers VTDPY>DISPLAY STATUS HSG80 0.0% Idle S/N: ZG92712934 SW: V88P HW: E-01 18093 KB/S Pr Name Stk/ Max 0 NULL 0/ 0 Typ 3165 Rq/S Sta Rn Up: 19 5:02:22 CPU% Unit AS WC KB/S Unit ASWC KB/S 100.
Utilities and Exercisers Cache Performance screen The Cache Performance screen, shown in Figure 18, consists of the following sections: ■ Screen header, which includes: — Controller ID data — Subsystem performance — Controller uptime ■ Unit status ■ Unit I/O activity VTDPY>DISPLAY CACHE HSG80 S/N: ZG92712820 58.
Utilities and Exercisers Device Performance screen The Device Performance screen shown in Figure 19 on page 97 consists of the following sections: ■ Screen header, which includes: — Controller ID data — Subsystem performance — Controller uptime 96 ■ Device port configuration (upper left) ■ Device performance (upper right) ■ Device port performance (lower left) HSG60 and HSG80 Array Controller and Array Controller Software Troubleshooting Guide
Utilities and Exercisers VTDPY>DISPLAY DEVICE HSG80 S/N: ZG92712820 99.
Utilities and Exercisers Host Ports Statistics screen The Host Ports Statistics screen shown in Figure 20 on page 99 consists of the following sections: ■ Screen header, which includes: — Controller ID data — Subsystem performance — Controller uptime ■ Known hosts ■ Host port 1 configuration and link error counters ■ Host port 2 configuration and link error counters Note: Figure 20 on page 99 applies to “this controller” only.
Utilities and Exercisers VTDPY>DISPLAY HOST FIBRE CHANNEL HOST STATUS DISPLAY ********* KNOWN HOSTS ********** ****** PORT 1 ****** ****** PORT 2 ****** BB FrSz ID/ALPA P S Topology : FAB RIC Topology : FAB RIC BONK2P2 7 2048 210113 2 N Current Status : FAB RIC Current Status : FAB RIC 10 !NEWCON35 7 2048 210213 2 N Current ID/ALPA : 210 313 Current ID/ALPA : 210 413 11 DADRA11 7 2048 210213 1 N Tachyon Status : ff Tachyon Status : ff 12 BONK1P1 7 2048 21011
Utilities and Exercisers Resource Statistics screen The Resource Statistics screen shown in Figure 21 on page 101 consists of the following sections: ■ Screen header, which includes: — Controller ID data — Subsystem performance — Controller uptime 100 ■ Physical resource name fields ■ Cache memory requirement fields (Free, Need, and Wait) ■ Full unit performance ■ Resource status fields (Wait Flush, wait FX, Nodes, Dirty, and Flush) HSG60 and HSG80 Array Controller and Array Controller Software
Utilities and Exercisers HSG80 S/N: ZG12345678 SW: V88F HW: 00-00 100.
Utilities and Exercisers Remote Status screen The Remote Status screen (ACS V8.
Utilities and Exercisers Screen header The screen header is the first line of data on every display screen.
Utilities and Exercisers Common data fields Some VTDPY displays contain common data fields, such as the Default, Status, and Device screens. Table 18 provides a description of common data fields on Default and Status screens. Table 18: VTDPY—Common Data Fields Column Definitions: Part 1 Column Contents Pr Name Stk/Max Typ Sta CPU% Thread priority. Thread name or NULL (idle). Allocated stack size in 512 byte pages and maximum number of stack pages actually used. Thread type: FNC = Functional thread.
Utilities and Exercisers Table 19: VTDPY—Common Data Fields Column Definitions: Part 2 Column Port Target Contents SCSI ports 1 through 6. SCSI targets 0 through 15. Single controllers occupy 7; dual-redundant controllers occupy 6 and 7. D = Disk drive or CD-ROM drive. F = Foreign device. H = “This controller.” h = “Other controller” in dual-redundant configurations. P = Passthrough device. ? = Unknown device type. (space) = No device at this port and target location.
Utilities and Exercisers Table 20: VTDPY—Unit Performance Data Fields Column Definitions Column Unit A S W 106 Contents Kind of unit and unit number. Unit types include: D = Disk drive or CD-ROM drive. I = Invisible device. P = Passthrough device. ? = Unknown device type. Availability of the unit: a = Available to “other controller.” d = Offline, unit disabled for servicing. e = Online, unit mounted for exclusive access by a user. f = Offline, media format error.
Utilities and Exercisers Table 20: VTDPY—Unit Performance Data Fields Column Definitions (Continued) Column C Contents Caching state of the device: a = Read, writeback, and read-ahead caching enabled. b = Read and writeback caching enabled. c = Read and read-ahead caching enabled. p = Read-ahead caching enabled. r = Read caching only. w = Writeback caching enabled. space = Caching disabled.
Utilities and Exercisers Device Performance data fields VTDPY displays up to 42 devices in the Device Performance region (see Figure 19, upper right on page 97) of the Device screen only. See Table 21 for a description of each field. Table 21: VTDPY—Device Performance Data Fields Column Definitions Column Contents PTL A S W F 108 Type of device and the device port-target-LUN (PTL) address: D = Disk drive. P = Passthrough device. ? = Unknown device type.
Utilities and Exercisers Table 21: VTDPY—Device Performance Data Fields Column Definitions (Continued) Column Contents Rq/S Average I/O request rate for the device during the last update interval. Requests can be up to 32 KB, and generated by host requests or cache flush activity. RdKB/S Average read data transfer rate to the device in KB/s during the previous update interval. WrKB/S Average write data transfer rate to the device in KB/s during the previous update interval.
Utilities and Exercisers Host port configuration VTDPY displays host port configuration information in a block of tabular data in the Host screen only. The data is displayed for both host port 1 and host port 2 independently, although the format is the same for both. Use the CLEAR command to clear the host display link error counters. Table 23 outlines the Known Hosts portion of the Fibre Channel Host Status display.
Utilities and Exercisers Table 24: Fibre Channel Host Status Display—Port Status (Continued) Field Label Description Queue Depth Shows the instantaneous number of commands at the controller port. Busy/QFull Rsp Represents the total number of QFull/Busy responses sent by the port. Table 25: Fibre Channel Host Status Display—Link Error Counters Field Label Description Link Downs Refers to the total number of link down and up transitions. Soft Inits Number of loop initializations caused by this port.
Utilities and Exercisers Table 25: Fibre Channel Host Status Display—Link Error Counters (Continued) Field Label Description Elastic Errors Reveals the timing difference between the receive and transmits clocks and usually indicates cable pulls. Sfs Buff Warns Indicates the number of SFS buffer warning interruptions that occurred. A rapidly increasing value could indicate that the controller is running out of SFS buffer resources due to high host I/O command traffic.
Utilities and Exercisers Runtime Status of Remote Copy Sets screen Use the Runtime Status of Remote Copy Sets screen to check the runtime status of all remote copy sets. Table 28 provides a description of the Remote screen column headings and possible entries under each column. Note: This feature is only supported in the P variant of ACS. Table 28: Remote Display Column Definitions—ACS P Variant Only Column Contents COPY SET TARGET C INIT U Kb/s ASSOC SET U Kb/s Remote copy set name.
Utilities and Exercisers Table 28: Remote Display Column Definitions—ACS P Variant Only (Continued) Column Contents LS Log state: LG = Logging. MG = Merging. CP = Copying. NR = Normal. NZ = Normalizing. %MRG Percentage of merge process completed. %CPY Percent of copy process completed. Device port configuration VTDPY displays device port configuration information in a block of tabular data in the Default and device screens only.
Utilities and Exercisers Table 29: Device Map Column Definitions Column Contents Port SCSI ports 1 through 6. Target SCSI targets 0 through 15. Single controllers occupy 7; dual-redundant controllers occupy 6 and 7. D = Disk drive or CD-ROM drive. F = Foreign device. H = “This controller.” h = “Other controller” in dual-redundant configurations. P = Passthrough device. ? = Unknown device type. (space) = No device at this port and target location.
Utilities and Exercisers Table 30: Controller and Processor Utilization Definitions (Continued) Column Contents Sta CPU% Current thread state: Bl = The thread is blocked waiting for timer expiration, resources, or a synchronization event. Io = A DUP local program is blocked waiting for terminal I/O completion. Rn = The thread is currently executable. Shows the percentage of execution time credited to each thread since the last screen update.
Utilities and Exercisers Table 31: VTDPY Thread Descriptions (Continued) Thread Description MDATA Thread that processes metadata for nontransportable disks. NULL Process that is scheduled if no other process can be run. NVFOC Thread that initiates state change requests for the “other controller” in a dual-controller configuration. REMOTE Thread that manages state changes initiated by the “other controller” in a dual-controller configuration. RMGR Thread that manages the data buffer pool.
Utilities and Exercisers Table 32: Resource Performance Statistics Definitions (Continued) Column Contents 118 XBUFs Number of XOR buffers used by the FX chip for XOR operations. ZBUFs Number of zeroed XBUFs used by the FX chip for XOR operations. Disk Read DWDs Number of device work descriptors that process work requests for disk reads. Disk Write DWDs Number of device work descriptors that process work requests for disk writes.
Utilities and Exercisers Disk Inline Exerciser (DILX) Use DILX to check the data transfer capability of a unit (which may be composed of one or more disk drives). Checking for unit problems DILX generates intense read and write loads to the unit while monitoring drive performance and status. Run DILX on as many units as desired; however, since this utility creates substantial I/O loads on the controller, HP recommends stopping host-based I/O activity during the test.
Utilities and Exercisers 3. Run DILX with the following command: RUN DILX The system displays the following prompt: It is recommended that DILX only be run when there is no host activity present on the controller. Do you want to continue (y/n)[n]? 4. Enter Y(es) to accept. Note: Use the auto configure option to test the read and write capabilities of every unit in the subsystem. 5. Enter N(o) to decline the auto configure option and to allow testing of a specific unit. 6.
Utilities and Exercisers Testing the read and write capabilities of a unit Run a DILX Basic Function test to test the read and write capability of a unit. During the Basic Function test, DILX runs the following four tests: Note: DILX repeats the last three tests until the time entered in step 7 on page 123 expires. ■ Write test—Writes specific patterns of data to the unit (see Table 34). DILX does not repeat this test.
Utilities and Exercisers Table 34: Data Patterns for Phase 1: Write Test (Continued) Pattern Pattern in Hexadecimal Numbers 10 DB6C 11 2D2D, 2D2D, 2D2D, D2D2, D2D2, D2D2, 2D2D, 2D2D, D2D2, D2D2, 2D2D, D2D2, 2D2D, D2D2, 2D2D, D2D2 12 DB6D, B6DB, 6DB6, DB6D, B6DB, 6DB6, DB6D, B6DB, 6DB6, DB6D, B6DB, 6DB6, DB6D 13, ripple 1 0001, 0002, 0004, 0008, 0010, 0020, 0040, 0080, 0100, 0200, 0400, 0800, 1000, 2000, 4000, 8000 14, ripple 0 FIE, FFFD, FFFB, FFF7, FFEF, FFDF, FFBF, FF7F, FEFF, FDFF, FBFF, F7FF,
Utilities and Exercisers To test the read and write capabilities of a specific unit: Caution: Running this test on the unit erases all data on the unit. Ensure that the units used do not contain customer data. 1. From a host console, dismount the logical unit that contains the unit to be tested. 2. Connect a terminal to the controller maintenance port that accesses the unit being tested. 3.
Utilities and Exercisers 12. Press Enter or Return to accept the hard-error limit default. 13. Press Enter or Return to accept the soft-error limit default. 14. Press Enter or Return to accept the queue depth default. 15. Enter 1 to run the Basic Function test option. 16. Enter Y(es) to enable phase 1, the write test. 17. Enter Y(es) to accept the default percentage of requests that DILX issues as read requests during phase 2, the random I/O test. DILX issues the balance as write requests. 18.
Utilities and Exercisers Table 35: DILX Error Codes (Continued) Error Code Message and Explanation 2 No write buffers correspond to data pattern. Explanation: DILX read a legal data pattern from the unit, but because no write buffers correspond to the pattern, the data must be considered corrupt. 3 Read data does not match write buffer. Explanation: DILX compared the read and write data and discovered that they did not correspond. 4 Compare host data should have reported a compare error but did not.
Utilities and Exercisers Format and device code load utility (HSUTIL) Use the HSUTIL utility to upgrade the firmware on disk drives in the subsystem and to format disk drives. While formatting disk drives or installing new firmware, HSUTIL might produce one or more of the messages shown in Table 36 (many of the self-explanatory messages have been omitted from the table). Note: Disk format times are approximate.
Utilities and Exercisers Table 36: HSUTIL Messages and Inquiries (Continued) Message Description What BUFFER SIZE (in BYTES) does the drive require (2048, 4096, 8192) [8192]? HSUTIL detects that an unsupported device is selected as the target device and the firmware image requires multiple SCSI Write Buffer commands. Specify the number of bytes to be sent in each Write Buffer command. The default buffer size is 8192 bytes.
Utilities and Exercisers Configuration (CONFIG) utility Use the CONFIG utility to add one or more storage devices to the subsystem. This utility checks the device ports for new disk drives, adds them to the controller configuration, and automatically names them. Refer to the controller installation and configuration guide for more information about the CONFIG utility.
Utilities and Exercisers Code Load and Code Patch (CLCP) utility Use the CLCP utility to upgrade the controller software and the EMU software. Also use CLCP to patch the controller software. To successfully install a new controller, the correct (or current) software version and patch numbers must be available.
Utilities and Exercisers Note: Only HP authorized service providers can upload EMU microcode updates. Contact HP technical support for directions to obtain the appropriate EMU microcode and installation guide.
Utilities and Exercisers CLONE utility Use the CLONE utility to duplicate the data on any unpartitioned single-disk unit, stripeset, mirrorset, or striped mirrorset. Back up the cloned data while the actual storageset remains online. After the cloning operation is done, back up the clones rather than the storageset or single-disk unit, which can continue to service the I/O load. After cloning a mirrorset, the CLONE utility does not need to create a temporary mirrorset.
Utilities and Exercisers Field Replacement Utility (FRUTIL) Use FRUTIL to replace a failed controller, cache module, or ECB, in a dual-redundant controller configuration, without shutting down the subsystem. Refer to the controller maintenance and service guide for a more detailed explanation of how FRUTIL is used during the replacement process. Note: FRUTIL cannot run in remote copy set environments while I/O is in progress to the target side due to host write and normalization (ACS V8.8P only).
Utilities and Exercisers Change Volume Serial Number (CHVSN) utility Use the CHVSN utility to generate a new volume serial number (called VSN) for the specified device and to write the VSN on the media. The CHVSN utility is used to eliminate duplicate volume serial numbers and to rename duplicates with different volume serial numbers. Note: Only HP authorized service providers can use this utility.
Utilities and Exercisers 134 HSG60 and HSG80 Array Controller and Array Controller Software Troubleshooting Guide
Event Reporting Templates 3 This chapter describes the event codes the fault management software provides for spontaneous events and last failure events.
Event Reporting Templates The array controller uses the following codes to report different types of events.
Event Reporting Templates Passthrough Device Reset Event Sense Data Response template Events reported by passthrough devices during host and device operations are conveyed directly to the host system without intervention or interpretation by the array controllers, with the exception of device sense data that is truncated to 160 bytes if it exceeds 160 bytes.
Event Reporting Templates Last Failure Event Sense Data Response template (Template 01) Unrecoverable conditions detected by either software or hardware, and certain operator-initiated conditions, terminate controller operation. In most cases, following such a termination, the controller attempts to restart with hardware components and software data structures initialized to the states necessary to perform normal operations (see Table 38).
Event Reporting Templates Table 38: Template 01—Last Failure Event Sense Data Response Format (Continued) ↓ bit offset → 7 6 5 4 3 2 1 0 36 Template 37 Template flags 38–53 Reserved 54–69 Controller board serial number 70–73 Controller software revision level 74 Reserved or patch version (TM2) 75 Reserved 76 LUN status 77–103 Reserved 104–107 LFC 108–111 Last failure parameter [0] 112–115 Last failure parameter [1] 116–119 Last failure parameter [2] 120–123 Last failure parameter [3] 124–127 Last failure p
Event Reporting Templates Multiple-Bus Failover Event Sense Data Response template (Template 04) The controller SCSI host interconnect services software component reports Multiple-bus failover events through the Multiple-Bus Failover Event Sense Data Response (see Table 39). The error or condition is signaled to all host systems on all logical units. ■ ASC and ASCQ codes (byte offsets 12 and 13) are detailed in the “ASC, ASCQ, Repair Action, and Component Identifier Codes” chapter that starts on page 161.
Event Reporting Templates Table 39: Template 04—Multiple-Bus Failover Event Sense Data Response Format (Sheet 2 of 2) ↓ bit offset → 7 6 5 4 3 2 1 0 75 Reserved 76 LUN status 77–103 Reserved 104–131 Affected LUNs Extension (TM0) 132–159 Reserved HSG60 and HSG80 Array Controller and Array Controller Software Troubleshooting Guide 141
Event Reporting Templates Failover Event Sense Data Response template (Template 05) The controller failover control software component reports errors, and other conditions encountered during redundant controller communications and failover operation through the Failover Event Sense Data Response (see Table 40). The error or condition is signaled to all host systems on all logical units.
Event Reporting Templates Table 40: Template 05—Failover Event Sense Data Response Format (Continued) ↓ bit offset → 7 6 5 4 3 2 1 0 77–103 Reserved 104–107 LFC 108–111 Last failure parameter [0] 112–115 Last failure parameter [1] 116–119 Last failure parameter [2] 120–123 Last failure parameter [3] 124–127 Last failure parameter [4] 128–131 Last failure parameter [5] 132–135 Last failure parameter [6] 136–139 Last failure parameter [7] 140–159 Reserved HSG60 and HSG80 Array Controller and Array Controlle
Event Reporting Templates Device Discovery Error Sense Data Response template (Template 06) This template format is used internally to construct FMU output data for CLI output and cannot be exported through reporting mechanisms external to the host.
Event Reporting Templates Nonvolatile Parameter Memory Component Event Sense Data Response template (Template 11) The controller executive software component reports errors detected while accessing a nonvolatile parameter memory component through the Nonvolatile Parameter Memory Component Event Sense Data Response (see Table 41). Errors are signaled to all host systems on all logical units.
Event Reporting Templates Table 41: Template 11—Nonvolatile Parameter Memory Component Event Sense Data Response Format (Continued) ↓ bit offset → 7 6 5 4 3 2 1 0 77–103 Reserved 104–107 Memory address 108–111 Byte count 112–114 Number of times written 115 Undefined 116–159 Reserved 146 HSG60 and HSG80 Array Controller and Array Controller Software Troubleshooting Guide
Event Reporting Templates Backup Battery Failure Event Sense Data Response template (Template 12) The controller value-added services software component reports backup battery failure conditions for the various hardware components that use a battery to maintain state during power failures through the Backup Battery Failure Event Sense Data Response (see Table 42). The failure condition is signaled to all host systems on all logical units.
Event Reporting Templates Table 42: Template 12—Backup Battery Failure Event Sense Data Response Format ↓ bit offset → 7 6 5 4 3 2 1 0 77–103 Reserved 104–107 Memory address 108–159 Reserved 148 HSG60 and HSG80 Array Controller and Array Controller Software Troubleshooting Guide
Event Reporting Templates Subsystem Built-In Self-Test Failure Event Sense Data Response template (Template 13) The controller subsystem built-in self-test software component reports errors detected during test execution through the Subsystem Built-In Self-Test Failure Event Sense Data Response (see Table 43). Errors are signaled to all host systems on all logical units.
Event Reporting Templates Table 43: Template 13—Subsystem Built-In Self Test Failure Event Sense Data Response Format (Continued) ↓ bit offset → 7 6 5 4 3 2 1 0 77–103 Reserved 104–105 Undefined 106 Header type 107 Header flags 108 TE 109 Test number 110 Test command 111 Test flags 112–113 Error code 114–115 Return Code 116–119 Address of error 120–123 Expected error data 124–127 Actual error data 128–131 Extra status 1 132–135 Extra status 2 136–139 Extra status 3 140–159 Reserved 150 HSG60 and HSG80 Ar
Event Reporting Templates Memory System Failure Event Sense Data Response template (Template 14) The controller memory controller event analyzer software component and the Cache Manager, part of the Value-added (VA) software component, report the occurrence of memory errors through the Memory System Failure Event Sense Data Response (see Table 44). Errors are signaled to all host systems on all logical units.
Event Reporting Templates Table 44: Template 14—Memory System Failure Event Sense Data Response format (Continued) ↓ bit offset → 7 6 5 4 3 2 1 0 44–47 Reserved or FXCSR (TM1) 48–51 Reserved or FXCCSR (TM1) 52–53 Reserved 54–69 Controller board serial number 70–73 Controller software revision level 74 Reserved or patch version (TM2) 75 Reserved 76 LUN status 77–79 Reserved 80–83 Reserved or FXPAEC (TM1) 84–87 Reserved or FXCAEC (TM1) 88–91 Reserved or FXPAEP (TM1) 92–95 Reserved or CHC (TM0) or FXCAEP (TM1
Event Reporting Templates Device Services Nontransfer Error Event Sense Data Response template (Template 41) The controller device services software component reports errors detected while performing nontransfer work-related functions to disk (including CD-ROM and optical memory) device operations through the Device Services Nontransfer Event Sense Data Response (see Table 45).
Event Reporting Templates Table 45: Template 41—Device Services Non-Transfer Error Event Sense Data Response Format (Continued) ↓ bit offset → 7 6 5 4 3 2 1 0 75 Reserved 76 LUN status 77–103 Reserved 104 Associated port 105 Associated target 106 Associated ASC 107 Associated ASC qualifier 108–159 Reserved 154 HSG60 and HSG80 Array Controller and Array Controller Software Troubleshooting Guide
Event Reporting Templates Disk Transfer Error Event Sense Data Response template (Template 51) The controller device services and value-added services software components report errors detected while performing work related to disk (including CD-ROM and optical memory) device transfer operations through the Disk Transfer Error Event Sense Data Response (see Table 46).
Event Reporting Templates Table 46: Template 51—Disk Transfer Error Event Sense Data Response Format (Continued) ↓ bit offset → 7 6 5 4 3 2 1 74 Reserved or patch version (TM2) 75 Reserved 76 LUN status 77–78 Reserved 79–82 Device firmware revision level 83–98 Device product ID 99–100 Reserved 101 Device type 102–103 Reserved 104–121 Device sense data 122–159 Reserved 156 0 HSG60 and HSG80 Array Controller and Array Controller Software Troubleshooting Guide
Event Reporting Templates Data Replication Manager Services Event Sense Response template (Template 90) This section applies only to ACS V8.8P. The controller Data Replication Manager services software component reports events through the Data Replication Manager Services Event Sense Data Response. With Data Replication Manager, fault management events are reported on Template 90, shown in Table 47.
Event Reporting Templates Table 47: Template 90—Data Replication Manager Services Event Sense Data Response Format for ACS V8.
Event Reporting Templates Connection Table Full Event Error template (Template A0) This template format is used internally to construct FMU output data for CLI output and cannot be exported through reporting mechanisms external to the host.
Event Reporting Templates 160 HSG60 and HSG80 Array Controller and Array Controller Software Troubleshooting Guide
ASC, ASCQ, Repair Action, and Component Identifier Codes 4 This chapter describes ASC and ASCQ codes, recommended Repair Action Codes, and Component Identifier (ID) Codes found in the various templates.
ASC, ASCQ, Repair Action, and Component Identifier Codes Vendor-specific SCSI ASC and ASCQ codes Table 48 lists HSG60 and HSG80 controller vendor-specific SCSI ASC and ASCQ codes. These codes are also template-specific and appear at byte offsets 12 and 13. Note: Additional codes that are common to all SCSI devices can be found in the Small Computer System Interface-2 (SCSI-2) specification. Table 48: ASC and ASCQ Code Descriptions (Sheet 1 of 5) ASC ASCQ Code Code Description .
ASC, ASCQ, Repair Action, and Component Identifier Codes Table 48: ASC and ASCQ Code Descriptions (Sheet 2 of 5) ASC ASCQ Code Code Description 91 00 Mode select errors. 91 01 LUN exist; cannot add LUN. 91 02 LUN does not exist; cannot replace LUN. 91 03 Drive already exists; cannot add drive. 91 04 Drive does not exist; cannot do requested drive function. 91 05 Cannot delete drive; it is part of a LUN. 91 06 Cannot fail drive; format in progress.
ASC, ASCQ, Repair Action, and Component Identifier Codes Table 48: ASC and ASCQ Code Descriptions (Sheet 3 of 5) ASC ASCQ Code Code Description 164 91 1A First defined sub-LUN not formatted, second sub-LUN is illegal. 91 1B Non sub-LUN drive already owned by another LUN. 91 1C Sub-LUN drive already owned by a non sub-LUN. 91 1D Drive type differs from others in LUN. 91 1E Drive cannot be added to rank because rank is full. 91 1F Ranks have different number of disks defined.
ASC, ASCQ, Repair Action, and Component Identifier Codes Table 48: ASC and ASCQ Code Descriptions (Sheet 4 of 5) ASC ASCQ Code Code Description A1 00 Shelf OK is not properly asserted. A1 01 Unable to clear swap interrupt. Interrupt disabled. A1 02 Swap interrupt re-enabled. A1 03 Asynchronous swap detected. A1 04 Controller shelf OK is not properly asserted. A1 0A EMU fault: power supplies not OK. A1 0B EMU fault: fans not OK. A1 0C EMU fault: temperature not OK.
ASC, ASCQ, Repair Action, and Component Identifier Codes Table 48: ASC and ASCQ Code Descriptions (Sheet 5 of 5) ASC ASCQ Code Code Description 166 D1 09 Unexpected tag message. D1 0A Channel busy. D1 0B Device initialization failure. Device sense data available. D2 00 Miscellaneous SCSI driver error. D2 03 Device services had to reset the bus. D3 00 Drive SCSI chip reported gross error. D4 00 Non-SCSI bus parity error. D5 02 Message reject received on a valid message.
ASC, ASCQ, Repair Action, and Component Identifier Codes Recommended Repair Action Codes Recommended Repair Action Codes are embedded in Instance and Last Failure Codes. For a more detailed description of the relationship between these codes, see the “Instance Codes” chapter that starts on page 177 and the “Last Failure Codes” chapter that starts on page 211. Table 49 contains the Repair Action Codes assigned to each significant event in the system.
ASC, ASCQ, Repair Action, and Component Identifier Codes Table 49: Recommended Repair Action Codes (Sheet 2 of 8) Code Description 0B The “other controller” in a dual-redundant configuration was reset with the kill line by the controller that reported the event. To restart the non-operational controller, enter the CLI command, RESTART OTHER, on the surviving controller, and then depress the (//) Reset button on the non-operational controller.
ASC, ASCQ, Repair Action, and Component Identifier Codes Table 49: Recommended Repair Action Codes (Sheet 3 of 8) Code Description 20 Repair Action Code 20 failures are bus-related failures and the indicated modules reside on the PCI Data or Address Line (PDAL) bus. Follow these steps to determine what caused the failure: 1. Replace the controller with a known good controller. 2. Replace the cache module associated with “this controller” with a known good module. 3.
ASC, ASCQ, Repair Action, and Component Identifier Codes Table 49: Recommended Repair Action Codes (Sheet 4 of 8) Code Description 39 Check that the cache memory DIMMs are properly configured. 3A This error applies to the mirrored cache for “this controller.” Since the mirrored cache is physically located on the “other controller” cache module, replace the “other controller“ cache module or the appropriate memory DIMMs on the “other controller“ cache module.
ASC, ASCQ, Repair Action, and Component Identifier Codes Table 49: Recommended Repair Action Codes (Sheet 5 of 8) Code Description 51 The mirrorset is inoperative for one of the following reasons: ■ ■ ■ 52 The last Normal member has malfunctioned. Perform repair actions 55 and 59. The last Normal member is missing. Perform Repair Action 58. The members have been moved around and the consistency checks show mismatched members. Perform Repair Action 58.
ASC, ASCQ, Repair Action, and Component Identifier Codes Table 49: Recommended Repair Action Codes (Sheet 6 of 8) Code Description 5C The mirrorset has at least one local Normal or Normalizing member and one remote Normal or Normalizing member. Failsafe Error mode can now be enabled by entering the CLI command: SET unit-number ERROR_MODE=FAILSAFE 5D The last member of the spareset was removed. Add new drives to the spareset.
ASC, ASCQ, Repair Action, and Component Identifier Codes Table 49: Recommended Repair Action Codes (Sheet 7 of 8) Code Description 83 ■ ■ ■ ■ ■ ■ 88 An EMU is unavailable. This EMU (and associated cabinet) may have been removed from the subsystem; no action is required. The cabinet has lost power. Restore power to the cabinet. The EMU-to-EMU communications bus cable is disconnected or broken. Replace or reconnect the cable to reestablish communications. The specified EMU is broken.
ASC, ASCQ, Repair Action, and Component Identifier Codes Table 49: Recommended Repair Action Codes (Sheet 8 of 8) Code Description 8D Not safe to present the Worldwide LUN ID (WWLID) to the host because a site failover may have taken place, but cannot confirm with the remote controller. Perform one of the following repair actions: ■ ■ 8E Follow Repair Action 8B. If a site failover took place and you do not plan to perform a future site failback, delete the remote copy set on “this controller.
ASC, ASCQ, Repair Action, and Component Identifier Codes Component ID Codes Component ID Codes are embedded in Instance and Last Failure Codes. For a more detailed description of the relationship between these codes, see the “Instance Codes” chapter that starts on page 177 and the “Last Failure Codes” chapter that starts on page 211. Table 50 lists the Component ID Codes.
ASC, ASCQ, Repair Action, and Component Identifier Codes Table 50: Component ID Codes (Continued) Code Description 176 85 Format and Device Code Load Utility (HSUTIL) 86 Code Load/Code Patch Utility (CLCP) 8A Field Replacement Utility (FRUTIL) 8B Periodic Diagnostics (PDIAG) HSG60 and HSG80 Array Controller and Array Controller Software Troubleshooting Guide
Instance Codes 5 This chapter explains Instance Codes. An Instance Code is a number that uniquely identifies an event being reported.
Instance Codes Instance Code structure Figure 25 shows the structure of an Instance Code. By fully understanding this structure, each code can be translated without using FMU.
Instance Codes Instance Code format The format of an Instance Code as displayed in Sense Data Responses is shown in Table 51. Table 51: Instance Code Format bit offset → 7 6 {8}32 {9}33 {10}34 {11}35 5 4 3 NR threshold Repair action Event number Component ID 2 1 0 Note: The offset values enclosed in braces ( { } ) apply only to the Passthrough Device Reset Event Sense Data Response format (see Table 37 on page 137).
Instance Codes Table 52: Event Notification and Recovery (NR) Threshold Classifications (Continued) Threshold Value Classification Description 0A Soft 64 Informational Indicates either an unexpected condition detected by a controller software component (for example, protocol violations, host buffer access errors, internal inconsistencies, uninterpreted device errors, and so forth) or an intentional restart or shutdown of controller operation.
Instance Codes Table 53 contains the numerous Instance Codes, in ascending order, that might be issued by the controller fault management software. Table 53: Instance Codes and Repair Action Codes (Sheet 1 of 30) Instance Code Description Template Repair Action Code 01010302 An unrecoverable hardware-detected fault occurred. 01 03 0102030A An unrecoverable software inconsistency was detected or an intentional restart or shutdown of controller operation was requested.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 2 of 30) Instance Code Description Template Repair Action Code 02090064 A data compare error was detected during the execution of a compare modified read or write command. 51 00 020B2201 Failed read test of a writeback metadata page residing in cache. Dirty writeback cached data exists and cannot be flushed to media. The dirty data is lost. The Memory Address field contains the starting physical address of the Cache A0 memory.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 3 of 30) Description Template Repair Action Code 02110064 Disk bad block replacement attempt completed for a read within the user data area of the disk. Due to the way bad block replacement is performed on SCSI disk drives, information on the actual replacement blocks is not available to the controller and is, therefore, not included in the event report.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 4 of 30) Description Template Repair Action Code 022C0064 The device, specified in the Device Locator field, has transitioned from Copying or Normalizing state to the Normal state. 51 00 022E0064 The device, specified in the Device Locator field, was converted to a mirrorset associated with the logical unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 5 of 30) Description Template Repair Action Code 02402301 The cache backup battery covering the mirror cache was declared bad. Either the battery failed testing performed by the cache diagnostics during system startup or the battery was low (insufficiently charged) for longer than the expected duration. The Memory Address field contains the starting physical address of the Cache B1 memory.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 6 of 30) Instance Code Description Template Repair Action Code 024B2401 Writeback caching is disabled either due to a cache or battery-related problem. The exact nature of the problem is reported by other Instance Codes. In this instance, the Memory Address, Byte Count, FX Chip Register, Memory Controller Register, and Diagnostic Register fields are undefined.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 7 of 30) Instance Code Description Template Repair Action Code 0257000A An attempt to reassign a bad disk block failed. The contents of the disk block are lost. The Information field of the device sense data contains the block number of the first block in error. 51 00 0258000A This command was aborted prior to completion. The Information field of the device sense data contains the block number of the first block in error.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 8 of 30) Description Template Repair Action Code 025F2201 Memory diagnostics performed during controller initialization detected an excessive number of memory errors (512 pages or more) on the primary cache memory. Diagnostics have not declared the cache failed, due to the isolated bad memory regions, but this is a warning to replace the cache as soon as possible in case of further degradation.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 9 of 30) Description Template Repair Action Code 0268530A The device, specified in the Device Locator field, failed to be added to the RAIDset associated with the logical unit. The device remains in the spareset. 51 53 02695401 The device, specified in the Device Locator field, failed to be added to the RAIDset associated with the logical unit. The failed device was moved to the failedset.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 10 of 30) Description Template Repair Action Code 02730001 The device, specified in the Device Locator field, had a read error that was repaired with data from another mirrorset member. 51 00 02745A0A The device, specified in the Device Locator field, had a read error. Attempts to repair the error with data from another mirrorset member failed due to lack of an alternate error-free data source.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 11 of 30) Description Template Repair Action Code 027B2201 The Cache B1 memory controller failed cache diagnostics testing performed on the other cache during a cache failover attempt. The Memory Address field contains the starting physical address of the Cache B1 memory. 14 22 027C2201 The Cache B0 and Cache B1 memory controllers failed cache diagnostics testing performed on the other cache during a cache failover attempt.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 12 of 30) Instance Code Description Template Repair Action Code 02892301 The cache backup battery is near end of life. The Memory Address field contains the starting physical address of the Cache A0 memory. 12 23 028A2301 The cache backup battery covering the mirror cache is near end-of-life. The Memory Address field contains the starting physical address of the Cache B1 memory.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 13 of 30) Description Template Repair Action Code 02925D01 The device, specified in the Device Locator field, was removed from the spareset into the failedset; there are no devices left in the spareset. The new nominal number of members for the spareset is specified in the device sense data Information field. 51 5D 02931101 The UPS signaled a TMW before signaling an AC line failure.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 14 of 30) Description Template Repair Action Code 03044402 SCSI bus errors during disk operation. In this instance, the associated ASC and associated ASCQ fields are undefined. 41 44 03052002 Device port SCSI chip reported gross error during disk operation. In this instance, the associated ASC and associated ASCQ fields are undefined. 41 20 03062002 Non-SCSI bus parity error during disk operation.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 15 of 30) Instance Code Description Template Repair Action Code 03154002 Data returned from drive is invalid. 51 40 03164002 REQUEST SENSE command to drive failed. 51 40 03170064 Illegal command for Passthrough mode. 51 00 03180064 Data transfer request error. 51 00 03194002 Premature completion of a drive command. 51 40 031A4002 Command timeout. 51 40 031B0101 Watchdog timer timeout.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 16 of 30) Instance Code Description Template Repair Action Code 03354002 During device initialization, a TEST UNIT READY command or a READ CAPACITY command to the device failed. Passthrough 40 03364002 During device initialization, the device reported a deferred error. Passthrough 40 03374002 During device initialization, the maximum number of errors for a data transfer operation was exceeded.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 17 of 30) Description Template Repair Action Code 03BF0D01 The EMU for the cabinet, indicated by the Associated Port field, powered down the cabinet because the temperature has reached the allowable maximum. In this instance, the Associated Target, Associated ASC, and Associated ASCQ fields are undefined.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 18 of 30) Description Template Repair Action Code 03CA4002 A byte transfer timeout occurred during operation to a device that is unknown to the controller. In this instance, the associated ASC and associated ASCQ fields are undefined. 41 40 03CB0101 A miscellaneous SCSI port driver coding error was detected during operation to a device that is unknown to the controller.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 19 of 30) Instance Code Description Template Repair Action Code 03D14002 The identification of a device does not match the configuration information. The actual device type is unknown to the controller. In this instance, the associated ASC, and associated ASCQ fields are undefined. 41 40 03D24402 SCSI bus errors occurred during device operation. The device type is unknown to the controller.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 20 of 30) Description Template Repair Action Code 03D6450A During device initialization, the device reported the SCSI sense key, medium error. This condition indicates that the command stopped with a nonrecovered error condition that was probably caused by a flaw in the medium or an error in the recorded data.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 21 of 30) Description Template Repair Action Code 03DA450A During device initialization, the device reported the SCSI sense key, data project. This condition indicates that a command that reads or writes the medium was attempted on a block that is protected from this operation. The read or write operation is not performed. 41 45 03DB450A During device initialization, the device reported the SCSI sense key, blank check.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 22 of 30) Description Template Repair Action Code 03E0450A During device initialization, the device reported the SCSI sense key, volume overflow. This condition indicates that a buffered peripheral device has reached the end-of-partition and data not written to the medium may remain in the buffer. RECOVERED BUFFER DATA commands may be issued to read the unwritten data from the buffer.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 23 of 30) Description Template Repair Action Code 03F10502 The swap interrupt from the device port, indicated by the Associated Port field, cannot be cleared. All swap interrupts from all ports are disabled until corrective action is taken. If swap interrupts are disabled, neither controller front panel button presses nor removal or insertion of devices are detected by the controller.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 24 of 30) Instance Code 03F70401 Description The shelf, indicated by the Associated Port field, is reporting a problem. This condition could mean one or both of the following: ■ ■ Template Repair Action Code 41 04 If the shelf uses dual power supplies, one power supply failed. One of the shelf cooling fans failed. In this instance, the Associated Target, Associated ASC, and Associated ASCQ fields are undefined.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 25 of 30) Instance Code Description Template Repair Action Code 03FF0F01 The EMU-detected external air sense fault is now fixed. In this instance, the Associated Target, Associated ASC, and Associated ASCQ fields are undefined. 41 0F 07030B0A The failover control detected a receive packet sequence number mismatch. The controllers are out of synchronization with each other and are unable to communicate.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 26 of 30) Description Template Repair Action Code 07090064 The failover control received a code load message from the “other controller” indicating that a new program image is being written onto the “other controller” PCMCIA card. During this process, communication does not occur between the controllers to keep them operative; however, “this controller” does not make the “other controller” inoperative.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 27 of 30) Instance Code Description Template Repair Action Code 0C323F02 The quadrant 2 memory controller (cache B0) detected a multibit ECC error. 14 3F 0C333F02 The quadrant 3 memory controller (cache B1) detected a multibit ECC error. 14 3F 0C403E02 The quadrant 0 memory controller (cache A0) detected a firewall error. 14 3E 0C413E02 The quadrant 1 memory controller (cache A1) detected a firewall error.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 28 of 30) Instance Code Description Template Repair Action Code 0E088864 The remote copy set, specified by the Remote Copy Set Name field, has just had a membership change such that Disaster Tolerance Failsafe Error mode can now be enabled if desired. 90 88 0E098901 The remote copy set, specified by the Remote Copy Set Name field, is inoperative due to a disaster tolerance failsafe locked condition.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
Instance Codes Table 53: Instance Codes and Repair Action Codes (Sheet 29 of 30) Instance Code Description Template Repair Action Code 0E1E8C01 The asynchronous merge was terminated due to a read failure on the initiator unit. 90 8C 0E1F8B01 The asynchronous merge was terminated due to a write failure on the target unit.
