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

x1e1, 0x1e2, 0x1e3, 0x1e4, 0x1e5, 0x1e6, 0x1e7, 0x1e8, 0x1e9, 0x1ea, 0x1eb, 0x1ec, 0x1ed, 0x1ee,

Page 23 highlights

Event Number (dec/hex) Event Name Predictive Maintenance Implication Suspected Components Description Logged? Mfg Fail? EH 481/0x1e1 LCC_JEM_DELETE_PENDI Y NG_EH LCC/ESD 482/0x1e2 TWSI bus retry 483/0x1e3 Keyswitch error Y Ignore, unless Controller, occurring midplane, frequently. power supply, battery Y Keyswitch circuitry 484/0x1e4 Power-on reset Y 485/0x1e5 Hot plug reset Y 486/0x1e6 Heartbeat timeout reset Y 487/0x1e7 software fault reset Y 488/0x1e8 hardware fault reset Y controller controller controller controller controller 489/0x1e9 abterm reset Y 490/0x1ea front panel reset Y 491/0x1eb host reset Y 492/0x1ec firmware download reset Y controller controller controller controller 493/0x1ed controller failover reset 494/0x1ee 495/0x1ef memory error reset dual controller comm failure 496/0x1f0 Controller Removed Y replace the failed controller controller Y controller Y Ignore unless a controller dual controller system is in a communication failure state Y controller 497/0x1f1 reset requested by other Y controller 498/0x1f2 Shared-memory error reset Y 499/0x1f3 500/0x1f4 501/0x1f5 Controller reset Y Current mode parameters were Y saved Unsupported mode parameter Y region revision controller controller controller controller controller 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 intercontroller 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 hotremoved 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

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27

Event
Number
(dec/hex)
Event
Name
Logged?
Predictive
Maintenance
Implication
Suspected
Components
Mfg Fail?
Description
EH
The JEM object has completed its deletion.
481/0x1e1
LCC_JEM_DELETE_PENDI
NG_EH
Y
LCC/ESD
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.
482/0x1e2
TWSI bus retry
Y
Ignore, unless
occurring
frequently.
Controller,
midplane,
power supply,
battery
N
A transaction on the two-wire serial bus failed and
was retried.
483/0x1e3
Keyswitch error
Y
Keyswitch
circuitry
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.
484/0x1e4
Power-on reset
Y
controller
N
This event code indicates that a controller went
through a power-on reset. This is a normal power-on
condition.
485/0x1e5
Hot plug reset
Y
controller
N
This event code indicates that a controller reset was
initiated due to a controller insertion or removal.
486/0x1e6
Heartbeat timeout reset
Y
controller
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.
487/0x1e7
software fault reset
Y
controller
N
This event code indicates that the firmware
performed an illegal action which resulted in a
software fault and reset.
488/0x1e8
hardware fault reset
Y
controller
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.
489/0x1e9
abterm reset
Y
controller
N
This event code indicates that the controller reset
due to an abnormal termination in the firmware.
490/0x1ea
front panel reset
Y
controller
N
This event code indicates that the controller reset
due to a request through the front panel.
491/0x1eb
host reset
Y
controller
N
This event code indicates that the controller reset
due to a request from the host.
492/0x1ec
firmware download reset
Y
controller
N
This event code indicates that the controller reset
due to the completion of a successful firmware
download.
493/0x1ed
controller failover reset
Y
replace the failed
controller
controller
Y
This event code indicates that the controller reset
due to the failure of the other controller in the
enclosure.
494/0x1ee
memory error reset
Y
controller
N
This event code indicates that the controller reset
due to a memory error.
495/0x1ef
dual controller comm failure
Y
Ignore unless a
dual controller
system is in a
communication
failure state
controller
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.
496/0x1f0
Controller Removed
Y
controller
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.
497/0x1f1
reset requested by other
controller
Y
controller
N
This event code indicates that the controller reset
due to a reset request from the other controller.
498/0x1f2
Shared-memory error reset
Y
controller
N
This event code indicates that the controller reset in
order to recover from an error detected in shared
memory.
499/0x1f3
Controller reset
Y
controller
N
This event code indicates that the controller reset for
an unknown reason.
500/0x1f4
Current mode parameters were
saved
Y
controller
N
This event code indicates that the current mode
parameters were saved to the saved mode
parameters without changing them.
501/0x1f5
Unsupported mode parameter
region revision
Y
controller
N
An access to the mode parameter region of the
chassis NV memory found data with a format