HP StorageWorks Virtual Array 7100 Appendix A. Disk Array Controller Log - Page 12

FC-SCSI Interface SpecificationDescribes the IceCube SCSI interface. Targetted as part of OEM manual.Disk Array Con Error! No text of specified style in document. Event Number (dec/hex) Event Name Predictive Maintenance Implication Suspected Components Description Logged? Mfg Fail? 286/0x11e 287/0x11f 288/0x120 289/0x121 290/0x122 291/0x123 292/0x124 293/0x125 294/0x126 295/0x127 296/0x128 297/0x129 Memory Compare Error Controller Data Bus Microprocessor Access Parity Error Internal Data Bus Error Volume Set Full Reset Warm Boot IO Expander Fault Disk Set Detached Microprocessor Software Fault Microprocessor Hardware Fault Disk Interface Event Insufficient RAM For Image Upload Disk Interface Queueing Disabled Disk Disconnects Disabled Y Ingore - See SDRAM, accompanying controller, errors midplane Y > 1 in 6 months Controller Y > 1 in 6 months Controller, SIMM Y Ignore - see None accompanying errors Y Ignore if Controller recovered by power cycle Y Ignore - None Operator/Host activity Y > 1 in 1 month Controller Y > 1 in 1 month Controller Y Ignore, unless Disk, occurring controller, disk frequently interface Y Ignore - Operator None error or accompanying errors Y Immediate Disk Performance Problem - Unsupported Disk Y Immediate Disk Performance in the queue have been processed, the subsystem will undergo a short reset at which time the correctable error will be permanently corrected. Y This error code indicates that the system experienced a compare error between the redundant shared memory copies. The two word queue entry found in the shared-memory controller error queue will be placed in the event extended info area. After all entries currently in the queue have been processed, the subsystem will undergo a short reset, at which time an attempt will be made to sync the two copies of memory (if available) to see if the error was transient. If the error is permanent, nonvolatile memory must be invalidated. Single miscompare can be recovered by selecting one of the two versions of the data and syncing both sides to that version. N This event code indicates that the a reset was initiated due to excessive errors on the microprocessor local bus. N This error code indicates that the system experienced a parity error during a DMA Operation. N This error code indicates that an inconsistancy was detected in one of the volume set clusters seed values, fsb or rbtables. The migration bypassed this cluster. This could be the result of a r6 restore consistency posting temporary data to the cluster, the data in the cluster will remain bad until the data is reposted by the cache. In the mean time all reads for data will be satisfied by the cache. After the cache repost the data may then be successfully migrated. Y This error code indicates that the IO Expander containing the warm boot bit did not power-on in the correct default condition or that attempts to set the warm boot bit in the IO Expander failed. N This is a system change event posted to the log when shutdown has completed sucessfully; i.e., the volume set is no longer attacheddevice number field in log record is volume set number (system change event) N This is an error detected by the processor which caused the processor to vector to the software fault isr. The controller always resets following this log entry. This error is caused by illegal instruction fetches, divide by zero, or other illegal processor activity. N This is an error detected by the processor which caused the processor to vector to the hardware fault isr. The controller always resets following this log entry. This error occurs when the microprocessor attempts an illegal interrupt vector. N An error occurred on the disk interface. These may occur during disk hotplug. More detailed status is available in the event expanded information. N This is an error detected by the startupSystem when the current RAM config is not large enough to hold the NV image stored on disk. Since we do not support shrinking RAM, this fails the upload process and causes a new VS to be created. System state is NO_MAPS. N An attached disk could not be configured for command queueing. Command queueing and disconnects are disabled for this interface. N This event indicates that the firmware could not configure the drive to disable disconnects during