HP P2000 G3 User manual

Part number: 591224-005
First edition: February 2012
HP P2000 G3 MSA System
Event Descriptions Reference Guide

Legal and notice information
© Copyright 2012 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and
12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are
licensed to the U.S. Government under vendor’s standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth
in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting
an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Acknowledgements
Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.
UNIX is a registered trademark of The Open Group.

HP P2000 G3 MSA System Event Descriptions Reference Guide 3
About this guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
HP technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Product warranties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Subscription service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
HP web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Documentation feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Event descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Events and event messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Event format in this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Resources for diagnosing and resolving problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Event descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Troubleshooting steps for leftover disk drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Using the trust command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Power supply faults and recommended actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Events sent as indications to SMI-S clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Resolving scrub errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Preliminary steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Fixing consistency errors reported by the scrub utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Contents

4Contents

HP P2000 G3 MSA System Event Descriptions Reference Guide 5
About this guide
This guide describes events that the HP P2000 G3 MSA System may report and recommended actions to
take in response to those events. It also gives more details for troubleshooting leftover disks, using the scrub
utility, and warnings for usage of the trust command.
Intended audience
This guide is intended for storage system administrators and service personnel.
Prerequisites
Prerequisites for using this product include knowledge of:
•Network administration
•Storage system configuration
•Storage area network (SAN) management and direct attach storage (DAS)
•Fibre Channel, Serial Attached SCSI (SAS), Internet SCSI (iSCSI), and Ethernet protocols
•RAID technology
Before you begin to follow procedures in this guide, you must have already installed enclosures and
learned of any late-breaking information related to system operation, as described in the User Guide for
your product and in Release Notes.
Related documentation
In addition to this guide, please refer to online help and the following documents for this product:
•HP MSA System Racking Instructions
•HP P2000 G3 MSA Systems Installation Instructions
•HP P2000 G3 MSA System Cable Configuration Guide
•HP P2000 G3 FC MSA System User Guide
•HP P2000 G3 FC/iSCSI MSA System User Guide
•HP P2000 G3 SAS MSA System User Guide
•HP P2000 G3 iSCSI MSA System User Guide
•HP P2000 G3 MSA System SMU Reference Guide
•HP P2000 G3 MSA System CLI Reference Guide
You can find these documents from the Manuals page of the HP Business Support Center web site:
http://www.hp.com/go/p2000/manuals.

6 About this guide
Document conventions and symbols
CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.
IMPORTANT: Provides clarifying information or specific instructions.
NOTE: Provides additional information.
TIP: Provides helpful hints and shortcuts.
HP technical support
Telephone numbers for worldwide technical support are listed on the HP support web site:
http://www.hp.com/support/.
Collect the following information before calling:
•Technical support registration number (if applicable)
•Product serial numbers
•Product model names and numbers
•Applicable error messages
•Operating system type and revision level
•Detailed, specific questions
For continuous quality improvement, calls may be recorded or monitored.
Table 1 Document conventions
Convention Element
Medium blue text: Figure 1 Cross-reference links and e-mail addresses
Medium blue, underlined text
(http://www.hp.com)
Web site addresses
Bold font •Key names
•Text typed into a GUI element, such as into a box
•GUI elements that are clicked or selected, such as menu and list
items, buttons, and check boxes
Italics font Text emphasis
Monospace font •File and directory names
•System output
•Code
•Text typed at the command-line
Monospace, italic font •Code variables
•Command-line variables
Monospace, bold font Emphasis of file and directory names, system output, code, and text
typed at the command line

HP P2000 G3 MSA System Event Descriptions Reference Guide 7
Product warranties
For information about HP product warranties, see the warranty information website:
http://www.hp.com/go/storagewarranty
Subscription service
HP strongly recommends that customers sign up online using the Subscriber’s choice web site:
http://www.hp.com/go/e-updates.
•Subscribing to this service provides you with e-mail updates on the latest product enhancements, newest
versions of drivers, and firmware documentation updates as well as instant access to numerous other
product resources.
•After signing up, you can quickly locate your products by selecting Business support and then Storage
under Product Category.
HP web sites
For other product information, see the following HP web sites:
•http://www.hp.com
•http://www.hp.com/go/storage
•http://www.hp.com/go/p2000/manuals
•http://www.hp.com/support/downloads
•http://www.hp.com/storage/whitepapers
•http://www.hp.com/go/p2000
Documentation feedback
HP welcomes your feedback.
To make comments and suggestions about product documentation, please send a message to
[e-mail]. All submissions become the property of HP.

8 About this guide

HP P2000 G3 MSA System Event Descriptions Reference Guide 9
Event descriptions
Introduction
This guide is for reference by storage administrators to help troubleshoot storage-system issues. It describes
event messages that may be reported during system operation and specifies any actions recommended in
response to an event.
Events and event messages
When an event occurs in a storage system, an event message is recorded in the system’s event log and,
depending on the system’s event notification settings, may also be sent to users (using email) and
host-based applications (via SNMP or SMI-S).
Each event has a numeric code that identifies the type of event that occurred, and has one of the following
severities:
•Critical: A failure occurred that may cause a controller to shut down. Correct the problem immediately.
•Error: A failure occurred that may affect data integrity or system stability. Correct the problem as soon
as possible.
•Warning: A problem occurred that may affect system stability but not data integrity. Evaluate the
problem and correct it if necessary.
•Informational: A configuration or state change occurred, or a problem occurred that the system
corrected. No immediate action is required. In this guide, this severity is abbreviated as “Info.”
An event message may specify an associated error code or reason code. Error codes and reason codes
are outside the scope of this guide.
Event format in this guide
This guide lists events by event code and severity, where the most severe form of an event is described first.
Events are listed in the following format. Events that do not apply to P2000 G3 MSA System products are
not listed.
Resources for diagnosing and resolving problems
For further information about diagnosing and resolving problems, see:
•The troubleshooting chapter and the LED descriptions appendix in your product’s User Guide
•The topic about verifying component failure in the component’s replacement instructions document
These and other HP documents can be found on the Software Support/Documentation DVD shipped with
your product or at http://www.hp.com/go/p2000/manuals. For links to additional information about your
product, see http://www.hp.com/go/p2000 or http://www.hp.com/go/msa. For product support and to
download drivers, firmware, and software, see http://www.hp.com/support.
For a summary of storage events and corresponding SMI-S indications, see Events sent as indications to
SMI-S clients on page 62.
Event code
Severity Event description.
Recommended actions
•If the event indicates a problem, actions to take to resolve the problem.

10 Event descriptions
Event descriptions
1
Warning If the indicated vdisk is RAID 6, it is operating with degraded health due to the failure of two disks.
If the indicated vdisk is not RAID 6, it is operating with degraded health due to the failure of one disk.
The vdisk is online but cannot tolerate another disk failure.
If a dedicated spare or global spare of the proper type and size is present, that spare is used to
automatically reconstruct the vdisk; events 9 and 37 are logged to indicate this. If no usable spare disk is
present, but an available disk of the proper type and size is present and the dynamic spares feature is
enabled, that disk is used to automatically reconstruct the vdisk; event 37 is logged.
Recommended actions
•If a spare of the proper type and size is present, or if the dynamic spares feature is enabled,
reconstruction automatically starts and event 37 is logged. Replace the failed disk and configure the
replacement as a dedicated or global spare for future use.
•If no spare is present and the dynamic spares feature is disabled (that is, event 37 is NOT logged),
configure an available disk as a dedicated spare for the vdisk or replace the failed disk and configure
the new disk as a dedicated spare for the vdisk. That spare is used to automatically reconstruct the
vdisk; confirm this by checking that events 9 and 37 are logged.
•If the replacement disk was previously used in another vdisk and has a status of leftover (LEFTOVR),
clear the disk's metadata so you can assign the disk as a spare.
•Confirm that all failed disks have been replaced and that there are sufficient spare disks configured for
future use.
3
Error The indicated vdisk went offline.
One disk failed for RAID 0 or NRAID, three disks failed for RAID 6, or two disks failed for other RAID
levels. The vdisk cannot be reconstructed.
Recommended actions
•The CLI trust command may be able to recover some or all of the data on the vdisk
4
Info. The indicated disk had an uncorrectable error and the controller reassigned the indicated block.
Recommended actions
•Monitor the error trend and whether the number of errors approaches the total number of bad-block
replacements available.
6
Warning Vdisk creation failed during initialization.
Recommended actions
•Compare the vdisk count with the configuration limit for the maximum number of vdisks.
• If you reached this limit, either purchase additional storage or remove unneeded vdisks.
• If you have not reached the limit, see “Resources for diagnosing and resolving problems” in the
SMU help for the System Events panel, or the CLI help for the show events command.
Info. Recommended actions
•No action is required.

HP P2000 G3 MSA System Event Descriptions Reference Guide 11
7
Error In a testing environment, a controller diagnostic failed and reports a product-specific diagnostic code.
Recommended actions
•Perform failure analysis.
8
Warning The indicated disk in the indicated vdisk failed and the vdisk changed to a status of critical (CRIT) or offline
(OFFL). If a spare is present the controller automatically uses the spare to reconstruct the vdisk. Subsequent
events indicate the changes which happen to the vdisk.
Recommended actions
•If the indicated disk failed because of excessive media errors, imminent disk failure, possible hardware
failure, or a disk that is not supported, replace the disk.
•If the indicated disk failed because a user forced the disk out of the vdisk, or for an unknown reason,
see Troubleshooting steps for leftover disk drives on page 60.
•If the indicated disk failed because a previously detected disk is no longer present, reinsert the disk or insert a
replacement disk. If the disk then has a status of leftover (LEFTOVR), see Troubleshooting steps for leftover disk
drives on page 60.
•No action is required if the condition that caused the indicated disk failure is that RAID-6 initialization
failed. This disk is now a spare for the vdisk and reconstruction will start.
When the problem is resolved, event 9 is logged.
9
Info. The indicated spare disk has been used in the indicated critical vdisk to bring it back to a fault-tolerant
status.
Vdisk reconstruction starts automatically. This event indicates that a problem reported by event 8 is
resolved.
Recommended actions
•No action is required.
16
Info. The indicated disk has been designated a global spare.
Recommended actions
•No action is required.
18
Warning Vdisk reconstruction failed.
Recommended actions
•Determine whether the reconstruction failed due to a disk failure and whether replacing that disk will
enable reconstruction to start and complete without further errors. To determine this, look for another
event logged at approximately the same time that indicates a disk failure such as event 55, 58, or 412.
Follow the recommended action for that event.
Info. Vdisk reconstruction succeeded.
Recommended actions
•No action is required.

12 Event descriptions
19
Info. A rescan has completed.
Recommended actions
•No action is required.
20
Info. Storage Controller firmware update has completed.
Recommended actions
•No action is required.
21
Error Vdisk verification completed. Errors were found but not corrected.
Recommended actions
•Perform a vdisk scrub to find and correct the errors.
Warning Vdisk verification did not complete because of an internally detected condition such as a failed disk.
If a disk fails, data may be at risk.
Recommended actions
•Resolve any non-disk hardware problems, such as a cooling problem or a faulty controller module,
expansion module, or power supply.
•Check whether any disks in the vdisk have logged SMART events or unrecoverable read errors.
• If so, and the vdisk is a non-redundant RAID level (RAID 0 or non-RAID), copy the data to a different
vdisk and replace the faulty disks.
• If so, and the vdisk is a redundant RAID level, replace the faulty disks. Before replacing a disk,
confirm that a reconstruction is not currently running on the vdisk. It is also recommended to make a
full backup of all the data on the vdisk before replacing disks. If more than one disk in the vdisk has
errors, replace the disks one at a time and allow reconstruction to complete after each disk is
replaced.
Info. Vdisk verification failed immediately, was aborted by a user, or succeeded.
Recommended actions
•No action is required.
23
Info. Vdisk creation has started.
Recommended actions
•No action is required.
25
Info. The statistics for the indicated vdisk have been reset.
Recommended actions
•No action is required.
27
Info. Cache parameters have been changed for the indicated vdisk.
Recommended actions
•No action is required.

HP P2000 G3 MSA System Event Descriptions Reference Guide 13
28
Info. Controller parameters have been changed.
This event is logged when general configuration changes are made; for example, utility priority, remote
notification settings, user interface passwords, and management port IP values. This event is not logged
when changes are made to vdisk or volume configuration.
Recommended actions
•No action is required.
31
Info. The indicated disk is no longer a global or dedicated spare.
Recommended actions
•No action is required.
32
Info. Vdisk verification has started.
Recommended actions
•No action is required.
33
Info. Controller time/date has been changed.
This event is logged before the change happens, so the timestamp of the event shows the old time. This
event may occur often if NTP is enabled
Recommended actions
•No action is required.
34
Info. Controller has been restored to factory defaults.
Recommended actions
•For an FC controller, restart it to make the default loop ID take effect.
37
Info. Vdisk reconstruction has started. When complete, event 18 is logged.
Recommended actions
•No action is required.
39
Warning The sensors monitored a temperature or voltage in the warning range.
Recommended actions
•Check that the storage system’s fans are running.
•Check that the ambient temperature is not too warm. The enclosure operating range is 5–40C
(41F–104F).
•Check that there is a module or blank plate in every module slot in the enclosure.
•If none of the above explanations apply, replace the controller module that reported the error.
When the problem is fixed, event 47 is logged.

14 Event descriptions
40
Error The sensors monitored a temperature or voltage in the failure range.
Recommended actions
•Check that the storage system’s fans are running.
•Check that the ambient temperature is not too warm. The enclosure operating range is 5–40C
(41F–104F).
•Check that there is a module or blank plate in every module slot in the enclosure.
•If none of the above explanations apply, replace the controller module that reported the error.
When the problem is fixed, event 47 is logged.
41
Info. The indicated disk has been designated a spare for the indicated vdisk.
Recommended actions
•No action is required.
43
Info. The indicated vdisk has been deleted.
Recommended actions
•No action is required.
44
Warning The controller contains cache data for the indicated volume but the corresponding vdisk is not online.
Recommended actions
•Determine the reason why the disks comprising the vdisk are not online.
•If an enclosure is down, determine corrective action.
•If the vdisk is no longer needed, you can clear the orphan data; this will result in lost data.
•If the volume is missing and was not intentionally removed, see “Resources for diagnosing and
resolving problems” in the SMU help for the System Events panel, or the CLI help for the show events
command.
47
Info. An error detected by the sensors has been cleared. This event indicates that a problem reported by event
39 or 40 is resolved.
Recommended actions
•No action is required.
48
Info. The indicated vdisk has been renamed.
Recommended actions
•No action is required.
49
Info. A lengthy SCSI maintenance command has completed. Output indicates whether it completed successfully
or a failure occurred. (This typically occurs during disk firmware update.)
Recommended actions
•No action is required.

HP P2000 G3 MSA System Event Descriptions Reference Guide 15
50
Info. A correctable ECC error occurred in buffer memory.
Recommended actions
•No action is required.
51
Error An uncorrectable ECC error occurred in buffer memory.
Recommended actions
•If the event occurs more than once, replace the controller reporting the event.
52
Info. Vdisk expansion has started.
This operation can take days, or weeks in some cases, to complete. Allow adequate time for the expansion
to complete.
When complete, event 53 is logged.
Recommended actions
•No action is required.
53
Warning Too many errors occurred during vdisk expansion to allow the expansion to continue.
Recommended actions
•If the expansion failed because of a disk problem, replace the disk; if vdisk reconstruction starts, wait
for it to complete and then retry the expansion.
Info. Vdisk expansion either completed, failed immediately, or was aborted by a user.
Recommended actions
•If the expansion failed because of a disk problem, replace the disk; if vdisk reconstruction starts, wait
for it to complete and then retry the expansion.
55
Warning The indicated disk reported a SMART event.
A SMART event indicates impending disk failure.
Recommended actions
•Resolve any non-disk hardware problems, especially a cooling problem or a faulty power supply.
•If the disk is in a vdisk that uses a non-redundant RAID level (RAID 0 or non-RAID), copy the data to a
different vdisk and replace the faulty disk.
•If the disk is in a vdisk that uses a redundant RAID level, replace the faulty disk. Before replacing the
disk, confirm that a reconstruction is not currently running on the vdisk. It is also recommended to make
a full backup of all the data on the vdisk before replacing disks. If more than one disk in the vdisk has
reported SMART events, replace the disks one at a time and allow reconstruction to complete after
each disk is replaced.
56
Info. A controller has powered up or restarted.
Recommended actions
•No action is required.

16 Event descriptions
58
Error A disk drive detected a serious error, such as a parity error or disk hardware failure.
Recommended actions
•Replace the failed disk.
Warning A disk drive reset itself due to an internal logic error.
Recommended actions
•The first time this event is logged with Warning severity, if the indicated disk is not running the latest
firmware, update the disk firmware.
•If this event is logged with Warning severity for the same disk more than five times in one week, and
the indicated disk is running the latest firmware, replace the disk.
Info. A disk drive reported an event.
Recommended actions
•No action is required.
59
Warning The controller detected a parity event while communicating with the indicated SCSI device. The event was
detected by the controller, not the disk.
Recommended actions
•If the event indicates that a disk or an expansion module is bad, replace the indicated device.
Info. The controller detected a non-parity error while communicating with the indicated SCSI device. The error
was detected by the controller, not the disk.
Recommended actions
•No action is required.
61
Error The controller reset the indicated disk channel to recover from a communication error. This event is logged
to identify an error trend over time.
Recommended actions
•If the controller recovers, no action is required.
•View other logged events to determine other action to take.
62
Warning The indicated global or dedicated spare disk has failed.
Recommended actions
•Replace the failed disk.
•If the failed disk was a global spare, configure the new disk as a global spare.
•If the failed disk was a dedicated spare, configure the new disk as a dedicated spare for the same
vdisk.
65
Error An uncorrectable ECC error occurred on the buffer memory on startup.
The controller is automatically restarted and its cache data are restored from the partner controller’s cache.
Recommended actions
•Replace the controller module that logged this event.

HP P2000 G3 MSA System Event Descriptions Reference Guide 17
67
Info. The controller has identified a new disk or group of disks that constitute a vdisk and has taken ownership
of the vdisk. This can happen when disks containing data have been inserted from another enclosure. This
event only applies to non-Active-Active controllers.
Recommended actions
•You may need to clear the disks’ metadata if you want to reuse them in one or more new vdisks.
68
Info. The controller that logged this event is shut down, or both controllers are shut down.
Recommended actions
•No action is required.
71
Info. The controller has started or completed failing over.
Recommended actions
•No action is required.
72
Info. After failover, recovery has either started or completed.
Recommended actions
•No action is required.
73
Info. The two controllers are communicating with each other and cache redundancy is enabled.
Recommended actions
•No action is required.
74
Info. The FC loop ID for the indicated vdisk was changed to be consistent with the IDs of other vdisks. This can
occur when disks containing a vdisk are inserted from an enclosure having a different FC loop ID.
This event is also logged by the new owning controller after vdisk ownership is changed.
Recommended actions
•No action is required.
75
Info. The indicated volume’s LUN (logical unit number) has been unassigned because it conflicts with LUNs
assigned to other volumes. This can happen when disks containing data for a mapped volume have been
moved from one storage system to another.
Recommended actions
•If you want hosts to access the volume data on the inserted disks, map the volume with a different LUN.
76
Info. The controller is using default configuration settings. This event occurs on the first power up, and might
occur after a firmware update.
Recommended actions
•If you have just performed a firmware update and your system requires special configuration settings,
you must make those configuration changes before your system will operate as before.

18 Event descriptions
77
Info. The cache was initialized as a result of power up or failover.
Recommended actions
•No action is required.
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 disk in the vdisk fails, there is no dedicated spare available and all global spares are
too small or; if the dynamic spares feature is enabled, all global spares and available disks are too small.
Recommended actions
•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
Info. A trust operation has completed for the indicated vdisk.
Recommended actions
•Be sure to complete the trust procedure as documented in the CLI help for the trust command.
80
Info. The controller enabled or disabled the indicated parameters for one or more disks.
Recommended actions
•No action is required.
81
Info. The current controller has unkilled the partner controller. The other controller will restart.
Recommended actions
•No action is required.
83
Info. The partner controller is changing state (shutting down or restarting).
Recommended actions
•No action is required.
84
Warning The current controller that logged this event forced the partner controller to fail over.
Recommended actions
•See “Resources for diagnosing and resolving problems” in the SMU help for the System Events panel,
or the CLI help for the show events command.
86
Info. Host-port or disk-channel parameters have been changed.
Recommended actions
•No action is required.

HP P2000 G3 MSA System Event Descriptions Reference Guide 19
87
Warning The mirrored configuration retrieved by this controller from the partner controller has a bad cyclic
redundancy check (CRC). The local flash configuration will be used instead.
Recommended actions
•Restore the default configuration by using the restore defaults command, as described in the CLI
Reference Guide.
88
Warning The mirrored configuration retrieved by this controller from the partner controller is corrupt. The local flash
configuration will be used instead.
Recommended actions
•Restore the default configuration by using the restore defaults command, as described in the CLI
Reference Guide.
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.
Recommended actions
•The current controller that logged this event probably has down-level firmware. Update the firmware on
the down-level controller. Both controllers should have the same firmware versions.
When the problem is resolved, event 20 is logged.
90
Info. 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 changed.
Recommended actions
•No action is required.
91
Error In a testing environment, the diagnostic that checks hardware reset signals between controllers in
Active-Active mode failed.
Recommended actions
•Perform failure analysis.
95
Error 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.
Recommended actions
•Remove one of the controller modules and insert a replacement, then return the removed module to be
reprogrammed.

20 Event descriptions
96
Info. Pending configuration changes that take effect at startup were ignored because customer data might be
present in cache.
Recommended actions
•If the requested configuration changes did not occur, make the changes again and then use a
user-interface command to shut down or restart the controller.
103
Info. The name has been changed for the indicated volume.
Recommended actions
•No action is required.
104
Info. The size has been changed for the indicated volume.
Recommended actions
•No action is required.
105
Info. The default LUN for changed for the indicated volume has changed.
Recommended actions
•No action is required.
106
Info. The indicated volume has been added to the indicated vdisk.
Recommended actions
•No action is required.
107
Error The controller detected a serious error. In a single-controller configuration, the controller will restart
automatically. In an Active-Active configuration, the partner controller will kill the controller that
experienced the error.
Recommended actions
•See “Resources for diagnosing and resolving problems” in the SMU help for the System Events panel,
or the CLI help for the show events command.
108
Info. The indicated volume has been deleted from the indicated vdisk.
Recommended actions
•No action is required.
109
Info. The statistics for the indicated volume have been reset.
Recommended actions
•No action is required.