HP StorageWorks 7100 - Virtual Array Appendix page 23

Event Event
Number Name
(dec/hex)
EH
481/0x1e1 LCC_JEM_DELETE_PENDI
NG_EH
482/0x1e2 TWSI bus retry
483/0x1e3
Keyswitch error
484/0x1e4 Power-on reset
485/0x1e5
Hot plug reset
486/0x1e6 Heartbeat timeout reset
487/0x1e7 software fault reset
488/0x1e8 hardware fault reset
489/0x1e9 abterm reset
490/0x1ea
front panel reset
491/0x1eb host reset
492/0x1ec
firmware download reset
493/0x1ed controller failover reset
494/0x1ee memory error reset
495/0x1ef dual controller comm failure
496/0x1f0 Controller Removed
497/0x1f1 reset requested by other
controller
498/0x1f2 Shared-memory error reset
499/0x1f3
Controller reset
500/0x1f4 Current mode parameters were
saved
501/0x1f5 Unsupported mode parameter
region revision
Predictive Suspected
Maintenance Components
Implication
Y LCC/ESD
Y Ignore, unless Controller,
occurring midplane,
frequently. power supply,
battery
Y Keyswitch
circuitry
Y controller
Y controller
Y controller
Y controller
Y controller
Y controller
Y controller
Y controller
Y controller
Y replace the failed controller
controller
Y controller
Y Ignore unless a controller
dual controller
system is in a
communication
failure state
Y controller
Y controller
Y controller
Y controller
Y controller
Y controller
Description
The JEM object has completed its deletion.
N Topology Manager requested a delete of a JEM
when the JEM has an outstanding I/O. The deletion
is pending on the completion/failure of the
outstanding I/O. Any qued I/O would be aborted.
N A transaction on the two-wire serial bus failed and
was retried.
Y This error code indicates that a controller was
removed from the system without generating a park
interrupt to the remaining controller when inter-
controller communication was enabled. The
operating state of the logging controller is placed in
the extended info area. If the removed controller
was in use, the remaining controller will go through
a short reset after logging this error.
N This event code indicates that a controller went
through a power-on reset. This is a normal power-on
condition.
N This event code indicates that a controller reset was
initiated due to a controller insertion or removal.
N This event code indicates that a controller reset was
initiated due to a controller heartbeat timeout. One
of the controllers in the system failed to check-in
with the controller heartbeat checking module.
N This event code indicates that the firmware
performed an illegal action which resulted in a
software fault and reset.
N This event code indicates that the hardware
performed an illegal action which resulted in a
hardware fault and reset. This could mean that the
hardware generated an unrecognized interrupt vector
or that the shared-memory controller detected an
internal error.
N This event code indicates that the controller reset
due to an abnormal termination in the firmware.
N This event code indicates that the controller reset
due to a request through the front panel.
N This event code indicates that the controller reset
due to a request from the host.
N This event code indicates that the controller reset
due to the completion of a successful firmware
download.
Y This event code indicates that the controller reset
due to the failure of the other controller in the
enclosure.
N This event code indicates that the controller reset
due to a memory error.
Y This event code indicates that the controller reset
due to a dual controller communication failure. If
the controllers are able to communicate after the
reset, this error can be ignored.
N This event code indicates that the controller was
removed from the enclosure with the power on.
This is a normal entry for a controller that was hot-
removed previously.
N This event code indicates that the controller reset
due to a reset request from the other controller.
N This event code indicates that the controller reset in
order to recover from an error detected in shared
memory.
N This event code indicates that the controller reset for
an unknown reason.
N This event code indicates that the current mode
parameters were saved to the saved mode
parameters without changing them.
N An access to the mode parameter region of the
chassis NV memory found data with a format