HP StorageWorks 2300 Modular Smart Array reference guide (500911-001, January 2009)

HP StorageWorks 2300 Modular Smart Array reference guide 87
77 Informational The cache was initialized as a result of
power up or failover.
78 Warning The controller could not use an assigned
spare for a vdisk because the spare’s
capacity is too small. This occurs when a
vdisk’s status becomes critical and all global
spares are too small or (if dynamic spares
are enabled) all disks are too small.
Replace existing spares or add spares with
enough capacity to replace the smallest disk
in the vdisk. The vdisk size is limited by its
disk with the least capacity.
79 Informational The trust vdisk operation has completed
successfully.
80 Informational The controller has modified mode parameters
on one or more disks.
81 Informational The current controller has unkilled the partner
controller. The other controller will restart.
83 Informational The partner controller is changing state
(shutting down or restarting).
84 Warning In an active-active configuration, the current
controller has forced the partner controller to
fail over for the specified reason.
Save the log files and contact a service
technician.
86 Informational The FC host port or disk parameters have
been changed.
87 Warning The mirrored configuration retrieved by this
controller from the partner controller has bad
cyclic redundancy check (CRC). The local
flash configuration will be used instead.
The mirrored configuration is corrupted.
Configuration data on the two controllers
may be out of sync. Clear configuration may
be needed to fully recover from this.
88 Warning The mirrored configuration retrieved by this
controller from the partner controller is
corrupt. The local flash configuration will be
used instead.
The mirrored configuration is corrupted.
Configuration data on the two controllers
may be out of sync. Clear configuration may
be needed to fully recover from this.
89 Warning The mirrored configuration retrieved by this
controller from the partner controller has a
configuration level that is too high for the
firmware in this controller to process. The
local flash configuration will be used instead.
This likely indicates that the current controller
has down-level firmware. Update the
firmware on the down-level controller. Both
controllers should have the same firmware
versions.
When the problem is fixed, event 20 is
logged.
90 Informational The partner controller does not have a
mirrored configuration image for the current
controller, so the current controller’s local
flash configuration is being used. This event
is expected if the other controller is new or its
configuration has been cleared.
95 Critical Both controllers in an active-active
configuration have the same serial number.
Non-unique serial numbers can cause system
problems; for example, vdisk ownership and
WWNs are determined by serial number.
A service technician must examine both
controller serial numbers and change at least
one of them.
Table 14 Event code descriptions and recommended actions (continued)
Event
code
Event type Description Recommended action