HP StorageWorks 7100 - Virtual Array Appendix page 21

Event Event
Number Name
(dec/hex)
download mode
436/0x1b4 TWSI bus is busy
437/0x1b5 NVRAM battery not present
438/0x1b6 NVRAM battery failed
439/0x1b7
NVRAM battery not
responding
440/0x1b8 NVRAM battery
reconditioning stopped
441/0x1b9
NVRAM battery
reconditioning started
442/0x1ba Array switched to secure mode
443/0x1bb Array out of secure mode
444/0x1bc Turning on LED due to battery
failure
445/0x1bd Battery has reached end of life
446/0x1be
NVRAM battery status is
LOW
447/0x1bf NVRAM battery status is
GOOD
448/0x1c0 NVRAM battery status is
UNKNOWN
449/0x1c1 TWSI bus has been requested
by another module
450/0x1c2 Unable to communicate with
the NVRAM battery charger
451/0x1c3
NVRAM battery
reconditioning done
452/0x1c4 NVRAM battery
reconditioning status
453/0x1c5 EEPROM status is good
454/0x1c6 EEPROM status is "not
present"
455/0x1c7 EEPROM status is "failed"
456/0x1c8 EEPROM status is "unknown"
457/0x1c9
Invalid state in state machine
458/0x1ca TWSI Request Failure
459/0x1cb
TWSI Read Failure
Predictive Suspected
Maintenance Components
Implication
battery charger
Y Ignore, unless Controller
occurring
frequently
Y NVRAM
battery
Y NVRAM
battery
Y NVRAM
battery
Y NVRAM
battery charger
Y NVRAM
battery charger
Y NVRAM
battery
Y NVRAM
battery
Y Battery amber
LED
Y NVRAM
battery
Y NVRAM
battery
Y NVRAM
battery
Y NVRAM
battery
Y Ignore, unless Controller,
occurring battery, power
frequently supply
Y Controller,
battery
Y NVRAM
battery charger
Y NVRAM
battery
Y
Y
Y
Y
Y
Y Controller,
battery, power
supply,
midplane
Y Controller,
battery, power
supply,
midplane
Description
download mode to update the charger firmware
N The two-wire serial bus local to the controlle is
busy.
N The NVRAM battery charger does not detect the
presence of NVRAM battery
Y The NVRAM battery charger has declared the
NVRAM battery as failed
Y The NVRAM battery is not responding to two-wire
serial bus commands
N The NVRAM battery charger has aborted the
reconditioning of a battery
N The NVRAM battery charger has successfully
started reconditioning of a battery.
N The array has been switched to secure mode due to
the condition of the batteries
N The array has been switched out of secure mode
since the condition of the batteries do not warrant it
anymore
Y The amber LED that indicates battery failure has
been turned on due to a battery failure condition.
When this log entry is unaccompanied by the log
entry, it indicates that the battery management
firmware module was unable to communicate with
the NVRAM battery. Possible two-wire serial bus
communication error.
Y The NVRAM battery internal status indicates that
the battery has reached the end of life condition
N The status of NVRAM battery is low. This means
that the battery charge is less than a specified
threshold value
N The status of NVRAM battery is good. This means
that the battery charge is equal or higher than a
specified threshold value
N The status of the NVRAM battery is unknown. This
may be due to the firmware not being able to
communicate with the battery
N The battery management firmware has received a
request from another firmware module to use the
two-wire serial bus
Y The battery management firmware module is unable
to communicate with the NVRAM battery charger.
Possible two-wire serial bus communication error
N The NVRAM battery charger has successfully
reconditioned a battery
N The state of the controller and batteries that are
checked before a decision is taken on reconditioning
N The eeprom can be communicated with and has
valid contents.
N Communication with the eeprom has failed. The
module assumes that no hardware is present.
Y The TWSI bus may have failed, the read after a
write resulted in inconsistent data, or the crc
checksums in a device and it's mirror (if available)
are not correct.
N This can is caused when an TWSI bus command
fails. The eeprom is marked as unknown until a
retry is done or the TWSI bus reports a hard failure.
Y This is caused by an invalid state in an eeprom state
machine. If this error is found, there is a bug in the
firmware which must be fixed.
Y The two-wire serial bus module would not allow the
read or write request. This is usually due to a bus
failure.
Y The two-wire serial bus module retried the read 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.