User manual HP STORAGEWORKS 7100 VIRTUAL ARRAY APPENDIX A. DISK ARRAY CONTROLLER LOG

[. . . ] Disk Array Controller Log The array controller continually monitors all components of the disk array, and logs any information that may be of helpful in evaluating the performance and operation of the array. All aspects of array operation are logged, including: · changes to the operating status of the array · changes to the configuration of the array · performance data · port error statistics Table 1 lists all event codes that can appear in the controller log event pages. The table also includes events that are not logged, but can still generate SCSI sense data. Appropriate corrective action is included for all events that require it. [. . . ] This message is logged when NV-SDRAM is found to be invalid at boot and must be initialized. This should not cause concern if memory was purposely invalidated or a new board or new memory has just been installed. This error code indicates that a battery has failed the long discharge test. This test occurs following power on and every 30 days thereafter. The test takes about 36 hours to complete. This error code indicates that a fan has failed. This error code indicates that a power supply has failed. This error code indicates that the Background N N N N N N N N N N N N N Logged?Event Number (dec/hex) Event Name Predictive Maintenance Implication Suspected Components Description 314/0x13a Drive Missing At Power On Y Ignore unless no Operator activity Disk Drive, Controller, Back End FC Link 315/0x13b RAM Image Upload Failed Y Single Occurrance 316/0x13c Old Cache Configuration Used Y Ignore - See errors associated with shut down Disk Drives, Controller, Back End FC Link None 317/0x13d Incompatible RAM Image Content Y Ignore - Operator error None 318/0x13e Disk Interface Underrun Event Y 319/0x13f Disk Interface Overrun Event Y 320/0x140 Disk Interface Timeout Event Y 321/0x141 Controller ECC Miscorrection Y Single Occurrance not with other entries Single Occurrance not with other entries > 2 occurrances per hot plug insert or removal Single Occurrance Single Occurrance Disk, controller, disk interface Disk, controller, disk interface Disk, controller, disk interface SIMM, Controller Controller 322/0x142 Controller Data Bus Microprocessor Access Error Y 323/0x143 Incompatible Address Table In RAM Image Y Ignore - Operator error None 324/0x144 Non-Volatile Memory Initialized Y Ignore unless no operator activity SDRAM DIMM, Controller 325/0x145 Battery Failed Discharge Test Y Single Occurrance Battery 326/0x146 327/0x147 Fan Failed Power Supply Failed Y Y Single Occurrance Single Occurrance Single 328/0x148 Power Down Due To Fan Y Fan, Controller, Backplane Power Supply, Controller, Backplane Fans, Failure Occurrance Controller, Backplane Mfg Fail?N N N N Manager (BGM) has discovered that there are not enough good fans to cool the system. The BGM is shuttingThe NVRAM is not posted to disk, so it is critical to repair the system quickly. This error code indicates that the BGM has started timing that a fan is missing from the enclosure. The total length of time a fan has been missing will be checked periodically and if it exceeds TIME_FAN_MISSING_ALLOWED_BGM (approx. 10 minutes) the BGM will shut off the power supply. This error code indicates that the BGM is shutting off the power supply because a fan has been missing from the enclosure for too long (approx. This error code indicates that the batteries have failed a discharge test or have dropped below an acceptable voltage level. Attempting to shrink write cache with valid writes still in cache. This error code indicates that a controller was discovered to be bad during the poweron process This can be caused by the controller having difficulty in establishing communication. Ignore if recovered by power cycle or reset. This error code indicates that a SIMM was discovered to be bad during the poweron process. A backend SCSI channel was held reset longer than the time allowed for a drive hotplug. Probably caused by a partially inserted drive module, a failing drive, a failing controller, or a bent pin on a connector. [. . . ] Check the extended event information for more information. A PDM, during instantiation, came up with different basic information. One possible cause is downloading unsupported mech FW that doesn't conform to the required capacity point for drive category. The midplane EEPROM mode parameters region contains a revision that is older than the revision expected by current firmware. [. . . ]