HP StorageWorks 7110 Appendix A. Disk Array Controller Log - Page 18

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? controller 372/0x174 Download failed on the master Y controller 373/0x175 Unused error code N 374/0x176 TWSI Event Y 375/0x177 TWSI Bus Failure Y 376/0x178 Frontend Fibre Channel Event Y 377/0x179 Frontend Services Event Y 378/0x17a Recovered Dual Comm Failure Y 379/0x17b Reflection ECC single-bit error Y overflow 380/0x17c processor MCP or TEA Y machine check error N.A. N.A. ignore, unless occurring frequently Ignore Ignore download is sent to one of the controllers. This controller becomes the master of the download process. The other controller becomes the secondary controller (or the controler that just executes the download and reports back to the master.) This error will result if an error occurs on the secondary controller. Y In a dual controller environment the command to download is sent to one of the controllers. This controller becomes the master of the download process. The other controller becomes the secondary controller. If it is a single controller environment then the download process see the single controller as the master controller for the download regardless of the slot it exists in. If the download fails on this controller this error will result. N This error code value is unused. Controller, N This error code indicates that a transaction on one of power-supply, the two-wire serial buses did not complete battery, successfully. The bus, target device, and fail code midplane will be placed in the extended info area. The bus, controller slot, device address, and fail code will also be placed in the enclosureID, slot, component, and subcomponent fields of the CompID structure respectively. Y This error code indicates that one of the two-wire serial buses has failed. This log entry should always be preceded by several entries. The bus that failed will be identified in the extended info of the log entry. None N This error code indicates that the Front End Fibre Channel port had an event that it has logged. Specific information about the event is placed in the extended info area of the log. None N This error code indicates that a Front End Services (FES) event has occurred and has been logged. Specific information about the event is placed in the extended info area of the log. N This error code indicates that a controller was reset due to a dual-controller communication failure (one in which the two controllers failed to sync) and that the controllers successfully synced after the reset. The comm failure would result from either a transient hardware failure in the shared-memory controller, TWSI, or TSWI SRAM or from a situation where the controllers were not resetting within two seconds of each other. Processor Y This error code indicates that the number of single- DRAM bit ecc errors found in processor memory has exceeded the threshold. This threshold is half the number set up in the ECC Single-Bit Trigger register. The idea is to catch a high error rate, log, reset and reload processor memory in hopes of correcting any soft memory errors. If errors are occurring so fast that the count in ECC Single-Bit Trigger reg is exceeded before a periodic scan can discover and log this overflow, a Machine Check will result. The first byte of extended info is the ECC Single-Bit Counter register and the second byte is the ECC Single-Bit Trigger register. Processor, proc Y This error code indicates that a processor MCP or memory bus TEA fault resulted in a machine check. Information component was dumped into nvsram when the error occured and this log entry was generated during the next successful reset. The first four bytes of extended info is the 60x PCI Error Addr. The fifth byte is ErrEnR1. The sixth byte is ErrDR1. The ninth byte