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

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

Advertisement

Table 6-14 Most Common Microcode Panic Codes (Continued)
Value
Description
0x00A00006
Retry stamp panic. On very large "no disconnect transfers" (>512 blocks) the
microcode would panic. Fixed in microcode revision 7.61.
0x00A00016
SCSI errors. SCSI errors on the host SCSI bus might cause the microcode to panic
with a 0x00A00016 or 0x00A00047 code. Fixed in microcode revision 7.61.
0x00A0001C
Register bit reset incorrectly. A flaw on the SEL line of the host SCSI bus would
cause the NCR 720 SCSI controller on the SP to invalidate its onboard SSID register.
During the validation the microcode examined the register, found a bit reset, and
panicked. Fixed in microcode revision 7.61.
0x00A0002F
Bad information passed. Occurred if an SP had just cleared its queue and was
responding to a transfer request. These codes are part of the SCSI bus synchronous
and wide transfer negotiation handshake. Fixed in microcode revision 7.61.
0x00A00043
I/O SCSI command. Occurred when executing an I/O SCSI command from the host
during a SCSI bus reset condition. Fixed in microcode revisions 8.26, 8.58, and 9.04.
0x00A00047
SCSI errors. SCSI errors on the host SCSI bus might cause the microcode to panic
with a 0x00A00016 or 0x00A00047 code. Fixed in microcode revision 7.61.
0x00A00081
Bad hardware. Resets the backend SCSI bus indicating a possible hardware
problem. Check the SP SCSI I/O adapter, and all cabling connections.
0x00A000B0
SCSI initiator problems. Initiator was not responding. Fixed in microcode revision
8.15.
Panics 0x00A000B0, 0x00240010, and 0x00220050 occurred in SCSI environments
that had severe SCSI protocol problems due to malfunctioning initiators or noisy
conditions. Fixed in microcode revisions 8.27, 8.58, and 9.04.
0x00A02003
Target mode addressing used with NCR 53C825 SCSI IC. Occurs if a command is
issued with target mode addressing enabled with the NCR 53C825 SCSI processor
used for the host SCSI interface in the array. revision A of this IC resolves this
problem. Microcode revision 8.17 has been modified to not allow target mode
addressing to be enabled unless a 53C825 SCSI processor is installed in the array.
If running on a Windows NT system and target mode addressing is used, a bound
unit 7 might conflict with the controller ID of 7. Under target mode addressing, the
LUN stays at 0 and the individual devices (targets) are addressed. Windows NT only
allows for eight devices, 0-6 for disks, and 7 for the initiator (SP). If this exists, the
target disk 7 will have to be unbound.
Unsolicited Event Log
6-61

Advertisement

Table of Contents
loading

This manual is also suitable for:

30/fc

Table of Contents