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

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? 460/0x1cc TWSI Write Failure Y 461/0x1cd TWSI transmit Failure Y 462/0x1ce EEPROM now present Y 463/0x1cf EEPROM new status Y 464/0x1d0 EEPROM Selftest Passed Y 465/0x1d1 EEPROM Selftest Failed Y 466/0x1d2 EEPROM Read Failed Y 467/0x1d3 EEPROM Write Failed Y 468/0x1d4 EEPROM not mirrored Y 469/0x1d5 EEPROM can not get wwn Y 470/0x1d6 Firmware clone complete Y 471/0x1d7 Firmware clone failed. Y 472/0x1d8 VSC7130_INT_DISABLE_EH Y 473/0x1d9 LCC_DEVICE_STATE_INV Y ALID_EH 474/0x1da 475/0x1db 476/0x1dc 477/0x1dd 478/0x1de 479/0x1df 480/0x1e0 LCC_EVENT_EH Y LCC_DATA_LENGTH_ERR Y OR_EH LCC_NOT_SUPPORTED_ER Y ROR_EH LCC_RETRIES_EXCEEDED Y _EH LCC_ELEMENT_EXCEEDE Y D_MAX_EH LCC_STORAGE_EXCEEDE Y D_EH LCC_JEM_DELETE_DONE_ Y Controller or midplane Controller, battery, powersupply, midplane Controller, battery, power supply, midplane Midplane Midplane Midplane Midplane Midplane Midplane N.A. N.A. VSC7130 Signal Detect / Port Bypass Control chip LCC/ESD LCC/ESD LCC/ESD LCC/ESD LCC/ESD LCC/ESD LCC/ESD LCC/ESD Y The two-wire serial bus module retried the write and was either not able to get a response from the device, the transaction failed, or the bus failed. In the case of a bus failure, the bus was good at the time the read request was made. Now it has failed. Y The two-wire serial bus module retried the transmit and was either not able to get a response from the device, the transaction failed, or the bus failed. In the case of a bus failure, the bus was good at the time the read request was made. Now it has failed. N The eeprom was marked as not present because of "no hardware" status from the TWSI module. Upon further attempts to communicate, the device is now responding. N The status (GOOD, NOT_PRESENT, FAILED, CRITICAL) has changed. N The eeprom selftest was able to verify that the midplane eeproms are mirrored. Y The selftest of the mirrored eeproms detected the data was not identical between the pair. An attempt to fix this inconsistancy failed. Y The firmware was not able to read correctly from either of the mirrored midplane eeproms. Y The firmware was not able to read correctly from either of the mirrored midplane eeproms. Y The firmware was not able to read or write correctly from one of the mirrored midplane eeproms. The system is no longer fully redundant. Y During a request for a new lun WWN, the firmware was not able to read from either of the midplane eeproms. This is can be due to a variety of TWSI failures or the eeprom failing. The eeprom can only create 2,000 trillion (2 quadrillion) LUN's. If this limit has been exceeded, the midplane must be replaced. N Cloning of firmware to the other controller has completed. N Cloning of firmware to the other controller has failed. Y We've exceeded the maximum number of retries in attempting to clear a VSC7130 signal detect interrupt. The interrupt is being disabled to allow other TWS devices sharing the interrupt line to be able to generate interrupts. When this condition exists, the controller will not be able to respond to JBOD cable insertion and removal instantaneously, instead it will take up to five seconds to recognize the state change. This condition generally indicates bad FC conditions or a problem with the 7130. N Happens when a JEM is no longer allowed to send requests to an LCC its retries are zeroed. The current outstanding I/O may complete but no additional I/O will be started. N Status of elements as well as information on the LCC. N The amount of data sent by the LCC was not what was expected or calculated. N Data that was received from the LCC was not supported. e.g. LCC F/W not supported or a NEW element type is not supported by the array F/W. N The retries for an I/O have been exceeded. N The number of elements ,for a specific element type, exceeded the maximum allowed. (e.g. Disk element type reports 60 drives in a single JBOD) N Exceeded element or status storage space. N Topology Manager requested a delete of a JEM.