Page 1
HP P2000 G3 MSA System
Event Descriptions Reference Guide
Part number: 591224-005
First edition: February 2012
Page 2
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.
Page 3
Contents
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
HP P2000 G3 MSA System Event Descriptions Reference Guide 3
Page 4
4Contents
Page 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.
HP P2000 G3 MSA System Event Descriptions Reference Guide 5
Page 6
Document conventions and symbols
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)
Bold font • Key names
Italics font Text emphasis
Monospace font • File and directory names
Monospace, italic font
Monospace, bold font Emphasis of file and directory names, system output, code, and text
Web site addresses
• 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
• System output
• Code
• Text typed at the command-line
• Code variables
• Command-line variables
typed at the command line
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.
.
6 About this guide
Page 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
storagedocs.feedback@hp.com. All submissions become the property of HP.
HP P2000 G3 MSA System Event Descriptions Reference Guide 7
Page 8
8 About this guide
Page 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.
Event code
Severity
Event description.
Recommended actions
• If the event indicates a problem, actions to take to resolve the problem.
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
your product or at http://www.hp.com
product, see
download drivers, firmware, and software, see
For a summary of storage events and corresponding SMI-S indications, see Events sent as indications to
SMI-S clients on page 62.
http://www.hp.com/go/p2000 or http://www.hp.com/go/msa. For product support and to
/go/p2000/manuals. For links to additional information about your
on the Software Support/Documentation DVD shipped with
http://www.hp.com/support.
HP P2000 G3 MSA System Event Descriptions Reference Guide 9
Page 10
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.
10 Event descriptions
Recommended actions
• No action is required.
Page 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.
HP P2000 G3 MSA System Event Descriptions Reference Guide 11
Page 12
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.
12 Event descriptions
Page 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.
HP P2000 G3 MSA System Event Descriptions Reference Guide 13
Page 14
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.
14 Event descriptions
Page 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.
HP P2000 G3 MSA System Event Descriptions Reference Guide 15
Page 16
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.
16 Event descriptions
Page 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.
HP P2000 G3 MSA System Event Descriptions Reference Guide 17
Page 18
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.
18 Event descriptions
Page 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.
HP P2000 G3 MSA System Event Descriptions Reference Guide 19
Page 20
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.
20 Event descriptions
Page 21
11 0
Info. Ownership of the indicated vdisk has been given to the other controller.
Recommended actions
• No action is required.
111
Info. The link for the indicated host port is up.
This event indicates that a problem reported by event 112 is resolved. For a system with FC ports, this event
also appears after loop initialization.
Recommended actions
• No action is required.
11 2
Warning The link for the indicated host port has unexpectedly gone down.
Recommended actions
• Look for corresponding event 111 and monitor excessive transitions indicating a host-connectivity or
switch problem. If this event occurs more than 8 times per hour, it should be investigated.
• This event is probably caused by equipment outside of the storage system, such as faulty cabling or a
faulty switch.
• If the problem is not outside of the storage system, replace the controller module that logged this event.
11 2
Info. The link for the indicated host port has gone down because the controller is starting up.
Recommended actions
• No action is required.
11 4
Info. The link for the indicated disk-channel port is down. Note that events 114 and 211 are logged whenever a
user-requested rescan occurs and do not indicate an error.
Recommended actions
• Look for corresponding event 211 and monitor excessive transitions indicating disk problems. If more
than 8 transitions occur per hour, 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.
11 6
Error After a recovery, the partner controller was killed while mirroring write-back cache data to the current
controller that logged this event. The controller that logged this event restarted to avoid losing the data in
the partner controller’s cache, but if the other controller does not restart successfully, the data will be lost.
Recommended actions
• To determine if data might have been lost, check whether this event was immediately followed by event
56, closely followed by event 71; the failover indicates that the restart did not succeed.
11 8
Info. Cache parameters have been changed for the indicated volume.
Recommended actions
• No action is required.
HP P2000 G3 MSA System Event Descriptions Reference Guide 21
Page 22
12 7
Warning The controller has detected an invalid disk dual-port connection. This event indicates that a controller host
port is connected to an expansion port instead of to a port on a host or a switch.
Recommended actions
• Disconnect the host port and expansion port from each other and connect them to the proper devices.
13 6
Warning Errors detected on the indicated disk channel have caused the controller to mark the channel as degraded.
Recommended actions
• Determine the source of the errors on the indicated disk channel and replace the faulty hardware.
When the problem is resolved, event 189 is logged.
13 9
Info. The Management Controller (MC) has powered up or restarted.
Recommended actions
• No action is required.
140
Info. The Management Controller is about to restart.
Recommended actions
• No action is required.
141
Info. This event is logged when the IP address used for management of the system has been changed by a user
or by a DHCP server (if DHCP is enabled). This event is also logged during power up or failover recovery,
even when the address has not changed.
Recommended actions
• No action is required.
22 Event descriptions
Page 23
152
Warning The Management Controller has not communicated with the Storage Controller (SC) for 15 minutes and
may have failed.
This event is initially logged as Informational severity. If the problem persists, this event is logged a second
time as Warning severity and the MC is automatically restarted in an attempt to recover from the problem.
Event 156 is then logged.
Recommended actions
• If this event is logged only one time as Warning severity, no action is required.
• If this event is logged more than one time as Warning severity, do the following:
• If you are now able to access the management interfaces of the controller that logged this event, do
the following:
• Check the version of the controller firmware and update to the latest firmware if needed.
• If the latest firmware is already installed, the controller module that logged this event probably
has a hardware fault. Replace the module.
•If you are not able to access the management interfaces of the controller that logged this event, do
the following:
• Shut down that controller and reseat the module.
• If you are then able to access the management interfaces, check the version of the controller
firmware and update to the latest firmware if needed.
• If the problem recurs, replace the module.
Info. The Management Controller has not communicated with the Storage Controller for 160 seconds.
If communication is restored in less than 15 minutes, event 153 is logged. If the problem persists, this event
is logged a second time as Warning severity.
NOTE: It is normal for this event to be logged as Informational severity during firmware update.
Recommended actions
• Check the version of the controller firmware and update to the latest firmware if needed.
• If the latest firmware is already installed, no action is required.
153
Info. The Management Controller has re-established communication with the Storage Controller.
Recommended actions
• No action is required.
15 4
Info. New firmware has been loaded on the Management Controller (MC).
Recommended actions
• No action is required.
155
Info. New loader firmware has been loaded on the Management Controller (MC).
Recommended actions
• No action is required.
HP P2000 G3 MSA System Event Descriptions Reference Guide 23
Page 24
156
Warning The Management Controller has been restarted from the Storage Controller for the purpose of error
recovery.
Recommended actions
• See the recommended actions for event 152, which is logged at approximately the same time.
Info. The Management Controller has been restarted from the Storage Controller in a normal case, such as
when initiated by a user.
Recommended actions
• No action is required.
157
Error A failure occurred when trying to write to the Storage Controller flash chip.
Recommended actions
• Replace the controller module that logged this event.
15 8
Info. A correctable ECC error occurred in the CPU memory.
Recommended actions
• No action is required.
161
Info. One or more enclosures do not have a valid path to an enclosure management processor (EMP).
All enclosure EMPs are disabled.
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.
162
Warning The host WWNs (node and port) previously presented by this controller module are unknown. In a
dual-controller system this event has two possible causes:
• One or both controller modules have been replaced or moved while the system was powered off.
• One or both controller modules have had their flash configuration cleared (this is where the previously
used WWNs are stored).
The controller module recovers from this situation by generating a WWN based on its own serial number.
Recommended actions
• If the controller was replaced or someone reprogrammed its FRU ID data, verify the WWN information
for this controller module on all hosts that access it.
24 Event descriptions
Page 25
163
Warning The host WWNs (node and port) previously presented by the partner controller module, which is currently
offline, are unknown.
This event has two possible causes:
• The online controller module reporting the event was replaced or moved while the system was powered
off.
• The online controller module had its flash configuration (where previously used WWNs are stored)
cleared.
The online controller module recovers from this situation by generating a WWN based on its own serial
number for the other controller module.
Recommended actions
• If the controller was replaced or someone reprogrammed its FRU ID data, verify the WWN information
for the other controller module on all hosts that access it.
166
Warning The RAID metadata level of the two controllers does not match.
Usually, the controller at the higher firmware level can read metadata written by a controller at a lower
firmware level. The reverse is typically not true. Therefore, if the controller at the higher firmware level
failed, the surviving controller at the lower firmware level cannot read the metadata on disks that have
failed over.
Recommended actions
• If this occurs after a firmware update, it indicates that the metadata format changed, which is rare.
Update the controller with the lower firmware level to match the firmware level on the other controller.
167
Warning A diagnostic test at controller bootup detected an abnormal operation, which might require a power cycle
to correct.
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.
HP P2000 G3 MSA System Event Descriptions Reference Guide 25
Page 26
168
Error The indicated SES alert condition was detected in the indicated enclosure. This event is logged as Error
severity when one of the power supplies in an enclosure has no power supplied to it or when a hardware
failure is detected.
Recommended actions
• Check that all modules in the enclosure are properly seated in their slots and that their latches are
locked.
• If the reported problem is with a power supply, perform these checks:
• Check that each power supply module with a switch has that switch turned on.
• Check that each power cable is firmly plugged into both the power supply and a functional
electrical outlet.
• If the reported problem is with a temperature sensor or fan or power supply, perform these checks:
• Check that all of the enclosure's fans are running.
• Check that the ambient temperature is not too warm. The enclosure operating range is 5–40C
(41–104F).
• Check for any obstructions to the airflow.
• Check that there is a module in every module slot in the enclosure.
• If none of the above resolve the issue, the indicated FRU has probably failed and should be replaced.
The failed FRU will probably have an amber LED lit.
When the problem is resolved, event 169 is logged.
Warning The indicated SES alert condition was detected in the indicated enclosure.
Recommended actions
• Check that all modules in the enclosure are properly seated in their slots and that their latches are
locked.
• If the reported problem is with a power supply, perform these checks:
• Check that each power supply module has its switch turned on.
• Check that each power cable is firmly plugged into both the power supply and a functional
electrical outlet.
• If the reported problem is with a temperature sensor or fan or power supply, perform these checks:
• Check that all of the enclosure's fans are running.
• Check that the ambient temperature is not too warm. The enclosure operating range is 5–40C
(41–104F).
• Check for any obstructions to the airflow.
• Check that there is a module or blank plate in every module slot in the enclosure.
• If none of the above resolve the issue, the indicated FRU has probably failed and should be replaced.
The failed FRU will probably have an amber LED lit.
When the problem is resolved, event 169 is logged.
Info. The indicated SES alert condition was detected in the indicated enclosure.
Recommended actions
• No action is required.
169
Info. The indicated SES alert condition has been cleared in the indicated enclosure. This event indicates that a
problem reported by event 168 is resolved.
Recommended actions
• No action is required.
26 Event descriptions
Page 27
170
Info. The last rescan detected that the indicated enclosure was added to the system.
Recommended actions
• No action is required.
171
Info. The last rescan detected that the indicated enclosure was removed from the system.
Recommended actions
• No action is required.
172
Warning The indicated vdisk has been quarantined because not all of its disks are available. There are not enough
disks to be fault tolerant. The partial vdisk will be held in quarantine until it becomes fault tolerant.
Recommended actions
• Ensure that all disks are latched into their slots and have power.
• During quarantine, the vdisk is not visible to the host. If after latching disks into their slots and powering
up the vdisk, the vdisk is still quarantined, you can manually remove the vdisk from quarantine so that
the host can see the vdisk. The vdisk is still critical.
• If disks have failed, replace them.
When the vdisk has been removed from quarantine, event 173 is logged.
173
Info. The indicated vdisk has been removed from quarantine.
Recommended actions
• No action is required.
174
Info. Enclosure or disk firmware update has succeeded, been aborted by a user, or failed.
If the firmware update fails, the user will be notified about the problem immediately and should take care
of the problem at that time, so even when there is a failure, this event is logged as Informational severity.
Recommended actions
• No action is required.
175
Info. An Ethernet link has changed status (up/down).
Recommended actions
• Monitor the error trend. If this event occurs more than 8 times per hour, it should be investigated
• This event is probably caused by equipment outside of the storage system, such as faulty cabling or a
faulty Ethernet switch.
• If this event is being logged by only one controller in a dual-controller system, swap the Ethernet cables
between the two controllers. This will show whether the problem is outside or inside the storage system.
• If the problem is not outside of the storage system, replace the controller module that logged this event.
176
Info. The error statistics for the indicated disk have been reset.
Recommended actions
• No action is required.
HP P2000 G3 MSA System Event Descriptions Reference Guide 27
Page 28
177
Info. Cache data were purged for the indicated missing volume.
Recommended actions
• No action is required.
181
Info. One or more configuration parameters associated with the Management Controller have been changed,
such as configuration for SNMP, SMI-S, email notification, and system strings (system name, system
location, etc.).
Recommended actions
• No action is required.
182
Info. All disk channels have been paused. I/O will not be performed on the disks until all channels are
unpaused.
Recommended actions
• If this event occurs in relation to disk firmware update, no action is required. When the condition is
cleared, event 183 is logged.
• If this event occurs and you are not performing disk firmware update, 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.
183
Info. All disk channels have been unpaused, meaning that I/O can resume. An unpause initiates a rescan,
which when complete is logged as event 19.
This event indicates that the pause reported by event 182 has ended.
Recommended actions
• No action is required.
185
Info. An enclosure management processor (EMP) write command has completed.
Recommended actions
• No action is required.
186
Info. Enclosure parameters have been changed by a user.
Recommended actions
• No action is required.
187
Info. The write-back cache has been enabled.
Event 188 is the corresponding event that is logged when write-back cash is disabled.
Recommended actions
• No action is required.
28 Event descriptions
Page 29
188
Info. Write-back cache has been disabled.
Event 187 is the corresponding even that is logged when write-back cache is disabled.
Recommended actions
• No action is required.
189
Info. A disk channel that was previously degraded or failed is now healthy.
Recommended actions
• No action is required.
190
Info The controller module's super-capacitor pack has started charging.
This change met a condition to trigger the auto-write-through feature, which has disabled write-back cache
and put the system in write-through mode. When the fault is resolved, event 191 is logged to indicate that
write-back mode has been restored.
Recommended Actions:
• If event 191 is not logged within 5 minutes after this event, the super-capacitor has probably failed and
the controller module should be replaced.
191
Info The auto-write-through trigger event that caused event 190 to be logged has been resolved.
Recommended Actions:
• No action is required.
192
Info The controller module's temperature has exceeded the normal operating range.
This change met a condition to trigger the auto-write-through feature, which has disabled write-back cache
and put the system in write-through mode. When the fault is resolved, event 193 is logged to indicate that
write-back mode has been restored.
Recommended Actions:
• If event 193 has not been logged since this event was logged, the over-temperature condition probably
still exists and should be investigated. Another over-temperature event was probably logged at
approximately the same time as this event (such as event 39, 40, 168, 307, 469, 476, or 477); see the
recommended actions for that event.
193
Info The auto-write-through trigger event that caused event 192 to be logged has been resolved.
Recommended Actions:
• No action is required.
HP P2000 G3 MSA System Event Descriptions Reference Guide 29
Page 30
194
Info The Storage Controller in the partner controller module is not up.
This indicates that a trigger condition has occurred that has caused the auto-write-through feature to
disable write-back cache and put the system in write-through mode. When the fault is resolved, event 195
is logged to indicate that write-back mode has been restored.
Recommended Actions:
• If event 195 has not been logged since this event was logged, the other Storage Controller is probably
still down and the cause should be investigated. Other events were probably logged at approximately
the same time as this event; see the recommended actions for those events.
195
Info The auto-write-through trigger event that caused event 194 to be logged has been resolved.
Recommended Actions:
• No action is required.
198
Info A power supply has failed.
This indicates that a trigger condition has occurred that has caused the auto-write-through feature to
disable write-back cache and put the system in write-through mode. When the fault is resolved, event 199
is logged to indicate that write-back mode has been restored.
Recommended Actions:
• If event 199 has not been logged since this event was logged, the power supply probably does not
have a health of OK and the cause should be investigated. Another power-supply event was probably
logged at approximately the same time as this event (such as event 168); see the recommended actions
for that event.
199
Info The auto-write-through trigger event that caused event 198 to be logged has been resolved.
Recommended Actions:
• No action is required.
200
Info A fan has failed.
This indicates that a trigger condition has occurred that has caused the auto-write-through feature to
disable write-back cache and put the system in write-through mode. When the fault is resolved, event 201
is logged to indicate that write-back mode has been restored.
Recommended Actions:
• If event 201 has not been logged since this event was logged, the fan probably does not have a health
of OK and the cause should be investigated. Another fan event was probably logged at approximately
the same time as this event (such as event 168); see the recommended actions for that event.
201
Info The auto-write-through trigger event that caused event 200 to be logged has been resolved.
Recommended Actions:
• No action is required.
30 Event descriptions
Page 31
202
Info. An auto-write-through trigger condition has been cleared, causing write-back cache to be re-enabled. The
environmental change is also logged at approximately the same time as this event (event 191, 193, 195,
199, 201, a nd 241.)
Recommended actions
• No action is required.
203
Warning An environmental change occurred that allows write-back cache to be enabled, but the auto-write-back
preference is not set. The environmental change is also logged at approximately the same time as this
eve n t (ev e nt 191, 193 , 195 , 199, 2 01, o r 241) .
Recommended actions
• Manually enable write-back cache.
204
Error This event is generated by the hardware-flush firmware when the boot-processing firmware needs to inform
the user about something.
The CompactFlash card is used for backing up unwritten cache data when a controller goes down
unexpectedly, such as when a power failure occurs. This event is generated when the Storage Controller
detects a problem with the CompactFlash as it is booting up.
Recommended actions
• If this event is logged again, shut down the Storage Controller, remove the controller module from the
enclosure, replace the CompactFlash card (which is accessible from the rear of the controller module,
as shown in your product's User Guide), and reinstall the controller module.
• If this event is then logged again, replace the controller module.
Warning This event is generated by the hardware-flush firmware when the boot-processing firmware needs to inform
the user about something.
The CompactFlash card is used for backing up unwritten cache data when a controller goes down
unexpectedly, such as when a power failure occurs. This event is generated when the Storage Controller
detects a problem with the CompactFlash as it is booting up.
Recommended actions
• If this event is logged again, shut down the Storage Controller, remove the controller module from the
enclosure, replace the CompactFlash card (which is accessible from the rear of the controller module,
as shown in your product's User Guide), and reinstall the controller module.
• If this event is then logged again, replace the controller module.
Info. This event is generated by the hardware-flush firmware when the boot-processing firmware needs to inform
the user about something.
When logged as Informational severity, this event contains information that is primarily of interest to
engineers.
Recommended actions
• No action is required.
205
Info. The indicated volume has been mapped or unmapped.
Recommended actions
• No action is required.
HP P2000 G3 MSA System Event Descriptions Reference Guide 31
Page 32
206
Info. Vdisk scrub has started.
The scrub checks disks in the vdisk for the following types of errors:
• Data parity errors for a RAID 3, 5, 6, or 50 vdisk
• Mirror verify errors for a RAID 1 or RAID 10 vdisk
• Media errors for all RAID levels including RAID 0 and non-RAID vdisk
When errors are detected, they are automatically corrected.
When the scrub is complete, event 207 is logged.
Recommended actions
• No action is required.
207
Error Vdisk scrub completed and found an excessive number of errors in the indicated vdisk.
This event is logged as Error severity when more than 100 parity or mirror mismatches are found and
corrected during a scrub or when 1 to 99 parity or mirror mismatches are found and corrected during
each of 10 separate scrubs of the same vdisk.
For non-redundant RAID levels (RAID 0 and non-RAID), media errors may indicate loss of data.
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.
Warning Vdisk scrub 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 scrub completed or was aborted by a user.
This event is logged as Informational severity when fewer than 100 parity or mirror mismatches are found
and corrected during a scrub.
For non-redundant RAID levels (RAID 0 and non-RAID), media errors may indicate loss of data.
Recommended actions
• No action is required.
32 Event descriptions
Page 33
208
Info. A scrub-disk job has started for the indicated disk. The result will be logged with event 209.
Recommended actions
• No action is required.
209
Error A scrub-disk job logged with event 208 has completed and found one or more media errors, SMART
events, or hard (non-media) errors. If this disk is used in a non-fault-tolerant vdisk, data may have been lost.
Recommended actions
• Replace the indicated disk.
Warning A scrub-disk job logged with event 208 has been aborted by a user, or has reassigned a disk block. These
bad-block replacements are reported as "other errors". If this disk is used in a non-fault-tolerant vdisk, data
may have been lost.
Recommended actions
• Monitor the error trend and whether the number of errors approaches the total number of bad-block
replacements available.
Info. A scrub-disk job logged with event 208 has completed and found no errors, or a disk being scrubbed (with
no errors found) has been added to a vdisk, or a user has aborted the job.
Recommended actions
• No action is required.
210
Info. All snapshots have been deleted for the indicated master volume or snap pool.
Recommended actions
• No action is required.
211
Warning SAS topology has changed; no elements are detected in the SAS map. The message specifies the number
of elements in the SAS map, the number of expanders detected, the number of expansion levels on the
native (local controller) side and on the partner (partner controller) side, and the number of device PHYs.
Recommended actions
• Perform a rescan to repopulate the SAS map.
• If a rescan does not resolve the problem, then shut down and restart both controllers.
• If the problem persists, 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. SAS topology has changed; the number of SAS expanders has increased or decreased. The message
specifies the number of elements in the SAS map, the number of expanders detected, the number of
expansion levels on the native (local controller) side and on the partner (partner controller) side, and the
number of device PHYs.
Recommended actions
• No action is required.
212
Info. All master volumes have been deleted for the indicated snap pool.
Recommended actions
• No action is required.
HP P2000 G3 MSA System Event Descriptions Reference Guide 33
Page 34
213
Info. The indicated standard volume has been converted to a master volume, or the indicated master volume has
been converted to a standard volume.
Recommended actions
• No action is required.
214
Info. The creation of snapshots is complete. The number of snapshots is indicated.
Additional events give more information for each snapshot.
Recommended actions
• No action is required.
215
Info. A previously created batch of snapshots is now committed and ready for use. The number of snapshots is
indicated.
Additional events give more information for each snapshot.
Recommended actions
• No action is required.
217
Error A super-capacitor failure occurred on the controller.
Recommended actions
• Replace the controller module that logged this event.
218
Warning The super-capacitor pack is near end of life.
Recommended actions
• Replace the controller module reporting this event.
219
Info. Utility priority has been changed by a user.
Recommended actions
• No action is required.
220
Info. Rollback of data in the indicated master volume to data in the indicated snapshot has been started by a
user.
Recommended actions
• No action is required.
221
Info. Snapshot reset has completed.
Recommended actions
• No action is required.
34 Event descriptions
Page 35
222
Info. The policy for the snap pool has been changed by a user. A policy specifies the action for the system to
automatically take when the snap pool reaches the associated threshold level.
Recommended actions
• No action is required.
223
Info. The threshold level for the snap pool has been changed by a user. Each snap pool has three threshold
levels that notify you when the snap pool is reaching decreasing capacity. Each threshold level has an
associated policy that specifies system behavior when the threshold is reached.
Recommended actions
• No action is required.
224
Info. Background rollback of data in the indicated master volume to data in the indicated snapshot has
completed.
Recommended actions
• No action is required.
225
Error A copy-on-write failure occurred when copying data from the indicated master volume to a snapshot.
Due to a problem accessing the snap pool, the write operation could not be completed to the disk. Data
are left in cache.
Recommended actions
• Delete all snapshots for the master volume and then convert the master volume to a standard volume.
226
Error Background rollback for the indicated master volume failed to start due to inability to initialize the snap
pool.
The rollback is in a suspended state.
Recommended actions
• Make sure the snap pool and the vdisk on which this volume exists are online. Restart the rollback
operation.
227
Error Failed to execute rollback for a particular LBA (logical block address) range of the indicated master
volume.
Recommended actions
• Restart the rollback operation.
228
Error Background rollback for the indicated master volume failed to end due to inability to initialize the snap
pool.
The rollback is in a suspended state.
Recommended actions
• Make sure the snap pool and the vdisk on which this volume exists are online. Restart the rollback
operation.
HP P2000 G3 MSA System Event Descriptions Reference Guide 35
Page 36
229
Warning The indicated snap pool has reached its warning threshold.
Recommended actions
• You can expand the snap pool or delete snapshots.
230
Warning The indicated snap pool has reached its error threshold.
When the error threshold is reached, the system automatically takes the action set in the policy for this
threshold level. The default policy for the error threshold is to auto-expand the snap pool.
Recommended actions
• You can expand the snap pool or delete snapshots.
231
Warning The indicated snap pool has reached its critical threshold.
When the critical threshold is reached, the system automatically takes the action set in the policy for this
threshold level. The default policy for the critical threshold is to delete all snapshots in the snap pool.
Recommended actions
• If the policy is to halt writes, then you must free up space in the snap pool by deleting snapshots.
• For other policies, no action is required.
232
Warning The maximum number of enclosures allowed for the current configuration has been exceeded.
The platform does not support the number of enclosures that are configured. The enclosure indicated by
this event has been removed from the configuration.
Recommended actions
• Reconfigure the system.
233
Warning The indicated disk type is invalid and is not allowed in the current configuration.
All disks of the unsupported type have been removed from the configuration.
Recommended actions
• Replace the unsupported disks with ones that are supported.
234
Error The indicated snap pool is unrecoverable and can therefore no longer be used.
Recommended actions
• All the snapshots associated with this snap pool are invalid and you may want to delete them.
However, the data on the master volume can be recovered by converting it to a standard volume.
235
Error An enclosure management processor (EMP) detected a serious error.
Recommended actions
• Replace the indicated controller module or expansion module.
Info. An enclosure management processor reported an event.
Recommended actions
• No action is required.
36 Event descriptions
Page 37
236
Info. A special shutdown operation has started. These special shutdown types are used as part of the
firmware-update process.
Recommended actions
• No action is required.
237
Info. A firmware update has started and is in progress. This event provides details of the steps in a
firmware-update operation that may be of interest if you have problems updating firmware.
Recommended actions
• No action is required.
238
Warning An attempt to install a licensed feature failed due to an invalid license.
Recommended actions
• Check the license for what is allowed for the platform, make corrections as appropriate, and reinstall. If
the license is invalid, the write will fail.
239
Warning A timeout occurred while flushing the CompactFlash.
Recommended actions
• Restart the Storage Controller that logged this event.
• If this event is logged again, shut down the Storage Controller, remove the controller module from the
enclosure, replace the CompactFlash card (which is accessible from the rear of the controller module,
as shown in your product's User Guide), and reinstall the controller module.
• If this event is then logged again, replace the controller module.
240
Warning A failure occurred while flushing the CompactFlash.
Recommended actions
• Restart the Storage Controller that logged this event.
• If this event is logged again, shut down the Storage Controller, remove the controller module from the
enclosure, replace the CompactFlash card (which is accessible from the rear of the controller module,
as shown in your product's User Guide), and reinstall the controller module.
• If this event is then logged again, replace the controller module.
241
Info. The auto-write-through trigger event that caused event 242 to be logged has been resolved.
Recommended actions
• No action is required.
HP P2000 G3 MSA System Event Descriptions Reference Guide 37
Page 38
242
Error The controller module's CompactFlash card has failed.
This change met a condition to trigger the auto-write-through feature, which has disabled write-back cache
and put the system in write-through mode. When the fault is resolved, event 141 is logged to indicate that
write-back mode has been restored.
Recommended actions
• If event 241 has not been logged since this event was logged, the CompactFlash probably does not
have health of OK and the cause should be investigated. Another CompactFlash event was probably
logged at approximately the same time as this event (such as event 239, 240, or 481); see the
recommended actions for that event.
243
Info. A new controller enclosure has been detected. This happens when a controller module is moved from one
enclosure to another and the controller detects that the midplane WWN is different from the WWN it has
in its local flash.
Recommended actions
• No action is required.
245
Info. An existing disk channel target device is not responding to SCSI discovery commands.
Recommended actions
• Check the indicated target device for bad hardware or bad cable, then initiate a rescan.
246
Warning The coin battery is not present or is not properly seated or has reached end-of-life.
The battery provides backup power for the real-time (date/time) clock. In the event of a power failure, the
date and time will revert to January 1, 1970 00:00:00.
Recommended actions
• Replace the controller module that logged this event.
247
Warning The FRU ID SEEPROM for the indicated field replaceable unit (FRU) cannot be read; FRU ID data might not
be programmed.
FRU ID data includes the worldwide name, serial numbers, firmware and hardware versions, branding
information, etc. This event is logged once each time a Storage Controller is started for each FRU that is not
programmed.
Recommended actions
• Return the FRU to have its FRU ID data reprogrammed.
248
Info. A valid feature license was successfully installed. See event 249 for details about each licensed feature.
Recommended actions
• No action is required.
38 Event descriptions
Page 39
249
Info. After a valid license is installed, this event is logged for each licensed feature to show the new license
value for that feature. The event specifies whether the feature is licensed, whether the license is temporary,
and whether the temporary license is expired.
Recommended actions
• No action is required.
250
Warning A license could not be installed.
The license is invalid or specifies a feature that is not supported on your product.
Recommended actions
• Review the readme file that came with the license. Verify that you are trying to install the license on the
system that the license was generated for.
251
Info. A volume-copy operation has started for the indicated source volume.
If the source volume is a master volume, you can remount it.
If the source volume is a snapshot, do not remount it until the copy is complete (as indicated by event 268).
Recommended actions
• No action is required.
252
Info. Data written to the indicated snapshot after it was created has been deleted. The snapshot now represents
the state of the master volume when the snapshot was created.
Recommended actions
• No action is required.
253
Info. A license was uninstalled.
Recommended actions
• No action is required.
255
Info. The PBCs across controllers do not match as PBC from controller A and PBC from controller B are from
different vendors. This may limit the available configurations.
Recommended actions
• No action is required.
256
Info. The indicated snapshot has been prepared but is not yet committed.
This can occur when a snapshot has been prepared but is not yet committed. This can occur when a
snapshot is taken by an application, such as the VSS hardware provider, that is timing-sensitive and needs
to take a snapshot in two stages.
After the snapshot is committed and event 258 is logged, the snapshot can be used.
Recommended actions
• No action is required.
HP P2000 G3 MSA System Event Descriptions Reference Guide 39
Page 40
257
Info. The indicated snapshot has been prepared and committed and is ready for use.
Recommended actions
• No action is required.
258
Info. The indicated snapshot has been committed and is ready for use.
Recommended actions
• No action is required.
259
Info. In-band CAPI commands have been disabled.
Recommended actions
• No action is required.
260
Info. In-band CAPI commands have been enabled.
Recommended actions
• No action is required.
261
Info. In-band SES commands have been disabled.
Recommended actions
• No action is required.
262
Info. In-band SES commands have been enabled.
Recommended actions
• No action is required.
263
Warning The indicated disk spare is missing. Either it was removed or it is not responding.
Recommended actions
• Replace the indicated disk.
264
Info. The link speed of the port bypass circuit and interconnect mode has been set to the default.
Recommended actions
• No action is required.
265
Info. Port bypass circuits currently use the service port, which may limit the link speed or interconnect mode
support.
Recommended actions
• No action is required.
40 Event descriptions
Page 41
266
Info. A volume-copy operation for the indicated master volume has been aborted.
Recommended actions
• No action is required.
267
Error While cleaning up resources in metadata at the end of a background volume copy process, the firmware
found at least one error and suspended the process for the indicated volume.
Recommended actions
• Make sure that disks and vdisks associated with the volume copy do not have problems (health OK,
status FTOL or UP) and then retry the volume copy.
268
Info. A background volume-copy operation for the indicated master volume has completed.
Recommended actions
• No action is required.
269
Info. A partner firmware update operation has started. This operation is used to copy firmware from one
controller to the other to bring both controllers up to the same version of firmware.
Recommended actions
• No action is required.
270
Warning Either there was a problem reading or writing the persistent IP data from the FRU ID SEEPROM, or invalid
data were read from the FRU ID SEEPROM.
Recommended actions
• Check the IP settings (including iSCSI host channel IP settings for an iSCSI system), and update them if
they are incorrect.
271
Info. The storage system could not get a valid serial number from the controller’s FRU ID SEEPROM, either
because it couldn’t read the FRU ID data, or because the data on it are not valid or have not been
programmed. Therefore, the MAC address is derived by using the controller’s serial number from flash. This
event is only logged one time during bootup.
Recommended actions
• No action is required.
272
Info. Expansion of the indicated snap pool has started.
Recommended actions
• No action is required.
273
Info. PHY fault isolation has been enabled or disabled by a user for the indicated enclosure and controller
module.
Recommended actions
• No action is required.
HP P2000 G3 MSA System Event Descriptions Reference Guide 41
Page 42
274
Warning The indicated PHY has been disabled, either automatically or by a user. Drive PHYs are automatically
disabled for empty disk slots or if a problem is detected. The following reasons indicate a likely hardware
fault:
• Disabled because of error count interrupts
• Disabled because of excessive PHY change counts
• PHY is ready but did not pass COMINIT
Recommended actions
• If none of the reasons listed above, no action is required.
• If any of the reasons listed under above is indicated and the event occurs shortly after the storage
system is powered up, do the following:
• Shut down the controllers. Then turn off the power for the indicated enclosure. For enclosures without
a power switch, disconnect AC power cord from the rack power source. Wait a few seconds, and
turn it back on. For enclosures without a power switch, connect the AC power cord to the rack
power source.
• If the problem recurs and the event message identifies a disk slot, replace the disk in that slot.
• If the problem recurs and the event message identifies a module, do the following:
• If the indicated PHY type is Egress, replace the cable in the module's egress port.
• If the indicated PHY type is Ingress, replace the cable in the module's ingress port.
• For other indicated PHY types or if replacing the cable does not fix the problem, replace the
indicated module.
• If the problem persists, check for other events that may indicate faulty hardware, such as an event
indicating an over-temperature condition or power supply fault, and follow the recommended
actions for those events.
• If the problem still persists, the fault may be in the enclosure midplane. Replace the
chassis-and-midplane FRU.
• If any of the reasons listed above is indicated and this event is logged shortly after a failover,
user-initiated rescan, or restart, do the following:
• If the event message identifies a disk slot, reseat the disk in that slot.
• If the problem persists after reseating the disk, replace the disk.
• If the event message identifies a module, do the following:
• If the indicated PHY type is Egress, replace the cable in the module's egress port.
• If the indicated PHY type is Ingress, replace the cable in the module's ingress port.
• For other indicated PHY types or if replacing the cable does not fix the problem, replace the
indicated module.
• If the problem persists, check for other events that may indicate faulty hardware, such as an event
indicating an over-temperature condition or power supply fault, and follow the recommended
actions for those events.
• If the problem still persists, the fault may be in the enclosure midplane. Replace the
chassis-and-midplane FRU.
275
Info. The indicated PHY has been enabled.
Recommended actions
• No action is required.
42 Event descriptions
Page 43
298
Warning The controller's real-time clock (RTC) settings might be invalid after an unexpected power loss.
This event will most commonly occur after an unexpected power loss.
Recommended actions
• Check the system date and time. If either is incorrect, set them to the correct date and time.
• Also look for event 246 and take appropriate action.
When the problem is resolved, event 299 is logged.
299
Info. The controller's RTC settings were recovered after an unexpected power loss.
This event will most commonly occur after an unexpected power loss.
Recommended actions
• No action is required, but if event 246 is also logged, take the action recommended for that event.
300
Info. CPU frequency has changed to high.
Recommended actions
• No action is required.
301
Info. CPU frequency has changed to low.
Recommended actions
• No action is required.
302
Info. DDR memory clock frequency has changed to high.
Recommended actions
• No action is required.
303
Info. DDR memory clock frequency has changed to low.
Recommended actions
• No action is required.
304
Info. The controller has detected I
2
C errors that may have been fully recovered.
Recommended actions
• No action is required.
305
Info. A serial number in Storage Controller flash memory was found to be invalid when compared to the serial
number in the controller-module or midplane FRU ID SEEPROM. The valid serial number has been
recovered automatically.
Recommended actions
• No action is required.
HP P2000 G3 MSA System Event Descriptions Reference Guide 43
Page 44
306
Info. The controller-module serial number in Storage Controller flash memory was found to be invalid when
compared to the serial number in the controller-module FRU ID SEEPROM. The valid serial number has
been recovered automatically.
Recommended actions
• No action is required.
307
Critical A temperature sensor on a controller FRU detected an over-temperature condition that caused the controller
to shut down.
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 C–40 C
(41 F–104 F).
• Check for any obstructions to the airflow.
• 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 logged the error.
308
Info. The default host port speed has changed from 4 Gbit/sec to 2 Gbit/sec because the controller module’s
HIM has a Broadcom PBC.
Recommended actions
• No action is required.
309
Info. Normally when the Management Controller is started, the IP data are obtained from the midplane FRU ID
SEEPROM where it is persisted. If the system is unable to write it to the SEEPROM the last time it changed,
a flag is set in flash memory. This flag is checked during startup, and if set, this event is logged and the IP
data that is in flash memory is used. The only time that this would not be the correct IP data would be if the
controller module was swapped and then whatever data are in the controller’s flash memory is used.
Recommended actions
• No action is required.
310
Info. After a rescan, back-end discovery and initialization of data for at least one EMP (Enclosure Management
Processor) has completed. This event is not logged again when processing completes for other EMPs in the
system.
Recommended actions
• No action is required.
311
Info. This event is logged when a user initiates a ping of a host via the iSCSI interface.
Recommended actions
• If the ping operation failed, check connectivity between the storage system and the remote host.
44 Event descriptions
Page 45
312
Info. This event is used by email messages and SNMP traps when testing notification settings. This event is not
recorded in the event log.
Recommended actions
• No action is required.
313
Error The indicated controller module has failed. This event can be ignored for a single-controller configuration.
Recommended actions
• It this is a dual-controller system, replace the failed controller module. The module’s Fault/Service
Required LED will be illuminated (not blinking).
314
Error The indicated FRU has failed or is not operating correctly. This event follows some other FRU-specific event
indicating a problem.
Recommended actions
• To determine whether the FRU needs to be replaced, see the topic about verifying component failure in
the component's replacement instructions document.
315
Critical The controller module is incompatible with the enclosure.
The controller will automatically shut down. If two incompatible controllers are inserted at the same time or
booted at the same time, one controller will crash and the other will hang. This behavior is expected and
prevents data loss.
Recommended actions
• Move the controller module to a compatible enclosure.
316
Warning The temporary license for a feature has expired.
Any components created with the feature remain accessible but new components cannot be created.
Recommended actions
• To continue using the feature, purchase a permanent license.
Info. The temporary license for a feature will expire in 10 days. Any components created with the feature will
remain accessible but new components cannot be created.
Recommended actions
• To continue using the feature after the trial period, purchase a permanent license.
317
Error A serious error has been detected on the Storage Controller's disk interface. The controller will be killed by
its partner.
Recommended actions
• Visually trace the cabling between the controller modules and expansion modules.
• If the cabling is OK, replace the controller module that logged this event.
• If the problem recurs, replace the expansion module that is connected to the controller module.
• See Resources for diagnosing and resolving problems on page 9.
HP P2000 G3 MSA System Event Descriptions Reference Guide 45
Page 46
318
Error A hardware failure occurred: XOR error.
Recommended actions
• Replace the controller module reporting the event.
319
Warning The indicated available disk has failed.
Recommended actions
• Replace the failed disk.
322
Warning The controller has an older Storage Controller version than the version used to create the CHAP
authentication database in the controller’s flash memory.
The CHAP database cannot be read or updated. However, new records can be added, which will replace
the existing database with a new database using the latest known version number.
Recommended actions
• Upgrade the controller firmware to a version whose SC is compatible with the indicated database
version.
• If no records were added, the database becomes accessible and remains intact.
• If records were added, the database becomes accessible but contains only the new records.
352
Info. Expander Controller (EC) assert data or stack-dump data are available.
Recommended actions
• No action is required.
353
Info. Expander Controller (EC) assert data and stack-dump data have been cleared.
Recommended actions
• No action is required.
354
Warning SAS topology has changed on a host port; at least one PHY has gone down. For example, the SAS cable
connecting a controller host port to a host has been disconnected.
Recommended actions
• Check the cable connection between the indicated port and the host.
• Monitor the log to see if the problem persists.
Info. SAS topology has changed on a host port; at least one PHY has gone up. For example, the SAS cable
connecting a controller host port to a host has been connected.
Recommended actions
• No action is required.
355
Warning The controller module's debug button was found to be stuck in the On position during boot up.
Recommended actions
• If the button remains stuck, replace the controller module.
46 Event descriptions
Page 47
356
Warning This event can only result from tests that are run in the manufacturing environment.
Recommended actions
• Follow the manufacturing process.
357
Warning This event can only result from tests that are run in the manufacturing environment.
Recommended actions
• Follow the manufacturing process.
358
Critical All PHYs are down for the indicated disk channel. The system is degraded and is not fault-tolerant because
all disks are in a single-ported state.
Recommended actions
• Turn off the power for the controller enclosure, wait a few seconds, and turn it back on.
• If the condition doesn't persist (that is, if event 359 has been logged for the indicated channel), no
further action is required.
• If the condition persists, this indicates a hardware problem in one of the controller modules or in the
controller enclosure midplane. For help identifying which FRU to replace, 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.
Warning Some, but not all, PHYs are down for the indicated disk channel.
Recommended actions
• Monitor the log to see whether the condition persists.
• If the condition doesn't persist (that is, if event 359 has been logged for the indicated channel), no
further action is required.
• If the condition persists, this indicates a hardware problem in one of the controller modules or in the
controller enclosure midplane. For help identifying which FRU to replace, 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.
359
Info. All PHYs that were down for the indicated disk channel have recovered and are now up.
Recommended actions
• No action is required.
360
Info. The speed of the indicated disk PHY was renegotiated.
Recommended actions
• No action is required.
HP P2000 G3 MSA System Event Descriptions Reference Guide 47
Page 48
361
Critical,
Error, or
Warning
Info. A scheduled task was initiated.
The scheduler experienced a problem with the indicated schedule.
Recommended actions
• Take appropriate action based on the indicated problem.
Recommended actions
• No action is required.
362
Critical,
Error, or
Warning
Info. The scheduler experienced a problem with the indicated task.
The scheduler experienced a problem with the indicated task.
Recommended actions
• Take appropriate action based on the indicated problem.
Recommended actions
• No action is required.
363
Error When the Management Controller is restarted, firmware versions that are currently installed are compared
against those in the bundle that was most recently installed. When firmware is updated, it is important that
all components are successfully updated or the system may not work correctly. Components checked
include the CPLD, Expander Controller (EC), Storage Controller (SC), and MC.
Recommended actions
• Reinstall the firmware bundle.
Info. When the Management Controller is restarted, firmware versions that are currently installed are compared
against those in the bundle that was most recently installed. If the versions match, this event is logged as
Informational severity. Components checked include the CPLD, Expander Controller (EC), Storage
Controller (SC), and MC.
Recommended actions
• No action is required.
400
Info. The indicated log has filled to a level at which it needs to be transferred to a log-collection system.
Recommended actions
• No action is required.
401
Warning The indicated log has filled to a level at which diagnostic data will be lost if not transferred to a
log-collection system.
Recommended actions
• Transfer the log file to the log-collection system.
402
Error The indicated log has wrapped and has started to overwrite its oldest diagnostic data.
Recommended actions
• Investigate why the log-collection system is not transferring the logs before they are overwritten. For
example, you might have enabled managed logs without configuring a destination to send logs to.
48 Event descriptions
Page 49
412
Warning One disk in the indicated RAID-6 vdisk failed. The vdisk is on line but has a status of FTDN (fault tolerant
with a down disk).
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 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.
• Otherwise, 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 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.
413
Info. Created a replication set with the indicated primary volume.
Recommended actions
• No action is required.
414
Error Failed to create the indicated replication set for the indicated volume.
This operation is not permitted if the specified volume is already in a replication set or is not a master
volume.
Recommended actions
• If the volume is a master volume and is not in a replication set, retry the operation.
415
Info. Deleted the indicated replication set.
Recommended actions
• No action is required.
416
Error Failed to delete the indicated replication set.
This can occur if an invalid identifier was specified for the replication set, or if the specified primary volume
is not on the local system.
Recommended actions
• Repeat the deletion using a valid replication-set identifier, or on the local system for the primary volume.
HP P2000 G3 MSA System Event Descriptions Reference Guide 49
Page 50
417
Info. Automatically deleted the indicated snapshot to make space for a new snapshot or for a remote snapshot
proxy volume, or while changing the secondary volume to be the primary volume.
The indicated snapshot was automatically deleted, as determined by the snap pool’s policy.
Recommended actions
• No action is required.
418
Warning A replication operation cannot complete because it needs to create a proxy volume or a replication
snapshot in the secondary vdisk, but the maximum number of volumes exists for that vdisk or its owning
controller and the vdisk contains no suitable snapshot to automatically delete.
This event is logged on the secondary volume’s system only.
Recommended actions
• To enable the replication operation to continue, delete at least one unneeded volume from the
destination vdisk or from another vdisk owned by the same controller.
• After performing the above action, if the replication fails for the same reason and becomes suspended,
events 431 and 418 will be logged. Repeat the above action and resume the replication.
419
Info. Started to add the indicated secondary volume to the indicated replication set.
Recommended actions
• No action is required.
420
Error Failed to add the indicated secondary volume to the indicated replication set.
This can occur for several reasons, such as:
• The volume is already a replication volume.
• The volume is not local to the system.
• The communication link is busy or experienced an error.
• The volume is not the same size as the existing volume or is no longer in the set.
• The volume record is not up to date.
• Replication is not licensed or the license limit would be exceeded.
Recommended actions
• If any of the above problems exist, resolve them. Then repeat the add operation with a valid volume.
421
Info. Completed adding the indicated secondary volume to the indicated replication set.
Recommended actions
• No action is required.
422
Info. Completed removing the indicated secondary volume from the indicated replication set.
Recommended actions
• No action is required.
50 Event descriptions
Page 51
423
Error Failed to remove the indicated volume from the indicated replication set. This can occur for several
reasons, such as:
• The volume record is not found.
• The volume record is not yet available.
• A primary volume conflict exists.
• You cannot delete the volume from a remote system.
• You cannot remove the volume because it is the primary volume.
Recommended actions
• If any of the above problems exist, resolve them. Then repeat the remove operation with a valid volume.
424
Info. Completed modifying parameters for the indicated secondary volume in the indicated replication set.
Recommended actions
• No action is required.
425
Info. Started a replication to the indicated secondary volume.
Recommended actions
• No action is required.
426
Info. Completed a replication to the indicated secondary volume.
Recommended actions
• No action is required.
427
Warning A communication error occurred when sending information between storage systems.
Recommended actions
• Check your network or fabric for abnormally high congestion or connectivity issues.
428
Info. A user suspended a replication to the indicated secondary volume.
Recommended actions
• No action is required.
429
Info. A user resumed a replication to the indicated secondary volume.
Recommended actions
• No action is required.
430
Info. A user aborted a replication to the indicated secondary volume.
Recommended actions
• No action is required.
HP P2000 G3 MSA System Event Descriptions Reference Guide 51
Page 52
431
Error Replication to the indicated secondary volume has suspended due to an error on that volume. User
intervention is required to resume replication. This can occur for several reasons, such as:
• The cache request was aborted.
• The cache detected that the source or target volume is offline.
• The cache detected a media error.
• The snap pool is full.
• The communication link is busy or experienced an error.
• The snapshot being used for the replication is invalid.
• There was a problem establishing proxy communication.
Recommended actions
• Resolve the error and then resume the replication.
432
Error Aborted a replication due to an error on the indicated secondary volume.
Recommended actions
• Verify that the secondary volume is valid and that the system where the volume resides is accessible.
433
Info. Skipped a replication to the indicated secondary volume.
Recommended actions
• No action is required.
434
Warning A replication collided with an ongoing replication to the indicated secondary volume.
A replication was in progress for the replication set when a new replication was requested. The new
replication has been queued.
Recommended actions
• This can be a normal operation, but in some cases this can indicate a problem. Ensure that: there are
no network issues; there is sufficient bandwidth between the primary and secondary systems; the
interval between replications is set to a sufficient amount of time to allow replications to complete.
Having too many replications queued can result in some replications not completing.
435
Warning Failed to initialize the indicated replication set.
This can occur because:
• Firmware in the remote system is incompatible with firmware in the local system.
• The primary volume and secondary volume involved in replication cannot communicate.
Recommended actions
• Update the firmware on one or both systems so they are running the same version.
• Check your network or fabric for abnormally high congestion or connectivity issues.
436
Warning Firmware in the remote system is incompatible with firmware in the local system so they cannot
communicate with each other to perform replication operations.
Recommended actions
• Update the firmware on one or both systems so they are running the same version.
52 Event descriptions
Page 53
437
Info. Started to change the primary volume for the indicated replication set to the indicated volume.
Recommended actions
• No action is required.
438
Info. Completed changing the primary volume for the indicated replication set to the indicated volume.
Recommended actions
• No action is required.
439
Error Failed to change the primary volume to the indicated volume for the indicated replication set. This can
occur for several reasons, such as:
• The volume is not in the replication set.
• Configuration tag or configuration data not found.
• The retry limit has been reached.
Recommended actions
• Verify that the specified volume is part of the replication set.
• Verify that there are no network issues preventing communication between the local and remote storage
systems.
440
Warning Retrying a replication due to an error on the indicated secondary volume.
This can occur for several reasons, such as:
• The cache request was aborted.
• The cache detected that the source or target volume is offline.
• The cache detected a media error.
• The snap pool is full.
• The communication link is busy or experienced an error.
• The snapshot being used for the replication is invalid.
• There was a problem establishing proxy communication.
The replication is being automatically retried according to policies in place. If the issue is resolved before
retries are exhausted, the replication will continue on its own; otherwise, it will go into a suspended state
unless the policy is set up to retry forever.
Recommended actions
• If any of the above problems exist, resolve them.
441
Error Failed to forward an add-volume request for a volume in a replication set. The secondary volume cannot
be fully added to the replication set.
Recommended actions
• Remove the indicated secondary volume from the replication set.
HP P2000 G3 MSA System Event Descriptions Reference Guide 53
Page 54
442
Warning Power-On Self Test (POST) diagnostics detected a hardware error in a UART chip in either or both of the
controllers.
Recommended actions
• Replace the controller module that logged this event.
443
Warning A firmware version mismatch has been detected in an MSA70 or D2700 enclosure. The enclosure should
be updated to the latest supported version of firmware as soon as possible.
Recommended actions
• In the enclosure, all FRUs must be at a combined proper firmware recipe. The two expansion modules
must be at equal firmware versions. Any replaced MSA70 FRUs might have older firmware that does
not match an internally defined recipe. Update the indicated enclosure to the latest firmware version to
ensure all FRUs are at the proper firmware level.
444
Warning A snap pool reached a capacity threshold and the associated Auto Expand policy failed because there is
not enough available space in the vdisk.
Recommended actions
• Increase the available space in the vdisk either by expanding the vdisk or by removing any unneeded
volumes.
Info. A snap pool reached a capacity threshold and the associated policy completed successfully; for example,
the snap pool was expanded successfully, or the oldest snapshot was deleted, or all snapshots were
deleted. If the policy is Delete Oldest Snapshot, the serial number of the deleted snapshot is reported.
Recommended actions
• No action is required.
449
Info. Rollback was aborted for the indicated master volume.
This can occur if a rollback is in progress and a user selects to roll back a different volume, which will abort
the first rollback and start a new rollback. A user can't explicitly abort a rollback because that would
corrupt the master volume.
Recommended actions
• No action is required.
450
Warning A remote volume’s status changed from online to offline.
This can occur for several reasons, such as:
• The communication link is busy or experienced an error.
• The local initiator experienced an error.
Recommended actions
• Verify that there are no network issues preventing communication between the local and remote storage
systems.
54 Event descriptions
Page 55
451
Info. A remote volume’s status changed from offline to online.
Recommended actions
• No action is required.
452
Info. The indicated volume has been detached from the indicated replication set.
The volume can now be physically moved to another storage system.
Recommended actions
• No action is required.
453
Info. The indicated volume has been reattached to the indicated replication set.
Recommended actions
• No action is required.
454
Info. A user changed the drive-spin-down delay for the indicated vdisk to the indicated value.
Recommended actions
• No action is required.
455
Warning The controller detected that the configured host-port link speed exceeded the capability of an FC SFP. The
speed has been automatically reduced to the maximum value supported by all hardware components in
the data path.
Recommended actions
• Replace the SFP in the indicated port with an SFP that supports a higher speed.
456
Warning The system's IQN was generated from the default OUI because the controllers could not read the OUI from
the midplane FRU ID data during startup. If the IQN is wrong for the system's branding, iSCSI hosts might
be unable to access the system.
Recommended actions
• If event 270 with status code 0 is logged at approximately the same time, restart the controllers.
464
Warning A user inserted an unsupported cable or SFP into the indicated controller host port.
Recommended actions
• Replace the cable or SFP with a supported type, as specified in your product’s User Guide.
465
Info. A user removed an unsupported cable or SFP from the indicated controller host port.
Recommended actions
• No action is required.
HP P2000 G3 MSA System Event Descriptions Reference Guide 55
Page 56
468
Info. FPGA temperature has returned to the normal operating range and the speed of buses connecting the
FPGA to downstream adapters has been restored. The speed was reduced to compensate for an FPGA
over-temperature condition.
This event indicates that a problem reported by event 469 is resolved.
Recommended actions
• No action is required.
469
Warning The speed of buses connecting the FPGA to downstream adapters has been reduced to compensate for an
FPGA over-temperature condition.
The storage system is operational but I/O performance is reduced.
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
F–104F).
(41
• Check for any obstructions to the airflow.
• 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 logged the error.
• When the problem is resolved, event 468 is logged.
C–40C
471
Info. A replication was queued because the indicated secondary volume is detached from the replication set.
Recommended actions
• No action is required.
• To enable the replication to proceed, reattach the secondary volume and then resume the replication.
472
Error A replication failed to start on the indicated secondary volume.
This can occur when the secondary system is not licensed for replication (for example, a temporary license
expired).
Recommended actions
• To perform replication, ensure that the secondary system has a valid replication license.
475
Info. A replication was queued because the indicated secondary volume is offline.
Recommended actions
• No action is required.
• To enable the replication to proceed, reattach the secondary volume and then resume the replication.
56 Event descriptions
Page 57
476
Warning The storage system is operational but I/O performance is reduced.
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
F–104F).
(41
• Check for any obstructions to the airflow.
• 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 logged the error.
When the problem is resolved, event 478 is logged.
477
Warning The storage system is operational but I/O performance is reduced.
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
F104F).
(41
• Check for any obstructions to the airflow.
• 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 logged the error.
C–40C
C–40C
When the problem is resolved, event 478 is logged.
478
Info. A problem reported by event 476 or 477 is resolved.
Recommended actions:
• No action is required.
479
Error The controller reporting this event was unable to flush data to or restore data from non-volatile memory.
This mostly likely indicates a CompactFlash failure, but it could be caused by some other problem with the
controller module. The Storage Controller that logged this event will be killed by its partner controller,
which will use its own copy of the data to perform the flush or restore operation.
Recommended actions
• If this is the first time this event has been logged, restart the killed Storage Controller.
• If this event is logged again, remove the killed controller module from the enclosure, replace the
CompactFlash card, and reinstall the controller module.
• If this event is then logged again, replace the controller module.
480
Error An IP address conflict was detected for the indicated iSCSI port of the storage system. The indicated IP
address is already in use.
Recommended actions
• Contact your data-network administrator to help resolve the IP address conflict.
HP P2000 G3 MSA System Event Descriptions Reference Guide 57
Page 58
481
Error The periodic monitor of CompactFlash hardware detected an error. The controller was put in write-through
mode, which reduces I/O performance.
Recommended actions
• Restart the Storage Controller that logged this event.
• If this event is logged again, shut down the Storage Controller, remove the controller module from the
enclosure, replace the CompactFlash card (which is accessible from the rear of the controller module,
as shown in your product's User Guide), and reinstall the controller module.
• If this event is then logged again, replace the controller module.
Recommended actions:
Replace the controller module that logged this event.
483
Error An invalid expansion-module connection was detected for the indicated disk channel. An egress port is
connected to an egress port, or an ingress port is connected to an egress port.
Recommended actions
• Visually trace the cabling between enclosures and correct the cabling.
484
Warning No compatible spares are available to reconstruct this vdisk if it experiences a disk failure. Only vdisks
that have dedicated spares will start reconstruction automatically.
This situation puts data at increased risk because it will require user action to configure a disk as a
dedicated or global spare before reconstruction can begin on the indicated vdisk if a disk in that vdisk
fails in the future.
If the last global spare has been deleted or used for reconstruction, all vdisks that do not have at least one
dedicated spare are at increased risk. Note that even though there may be global spares still available,
they cannot be used for reconstruction of a vdisk if that vdisk uses larger-capacity disks or a different type
of disk; so this event may be logged even when there are unused global spares. If the dynamic spares
feature is enabled, this event will be logged even if there is an available disk that may be used for
reconstruction.
Recommended actions
• Configure disks as dedicated spares or global spares.
• For a dedicated spare, the disk must be of the same type as the other disks in the vdisk and at least as
large and should have the same or better performance.
• For a global spare, it is best to choose a disk that is as big as or bigger than the largest disk of its type
in the system and of equal or greater performance. If the system contains a mix of disk types (SATA,
SAS, SSD, for example), there should be at least one global spare of each type (unless dedicated
spares are used to protect every vdisk of a given type).
58 Event descriptions
Page 59
485
Warning The indicated vdisk was quarantined to prevent writing invalid data that may exist on the controller that
logged this event.
This event is logged to report that the indicated vdisk has been put in the quarantined offline state (status of
QTOF) to prevent loss of data. The controller that logged this event has detected (via information saved in
the vdisk metadata) that it may contain outdated data that should not be written to the vdisk. Data may be
lost if you do not follow the recommended actions carefully. This situation is typically caused by removal of
a controller module without shutting it down first, then inserting a different controller module in its place. To
avoid having this problem occur in the future, always shut down the Storage Controller in a controller
module before removing it.
Recommended actions
• If event 486 is not logged at approximately the same time, reinsert the removed controller module, shut
it down, then remove it again.
• If events 485 and 486 are both logged at approximately the same time, wait at least 5 minutes for the
automatic recovery process to complete. Then sign in and confirm that both controller modules are
operational. (You can determine if the controllers are operational with the show redundancy-mode
CLI command or the System Redundancy table in the System Overview panel of the SMU.) In most
cases, the system will come back up and no further action is required. If both controller modules do not
become operational in 5 minutes, data may have been lost. If both controllers are not operational,
follow this recovery process:
• Remove the controller module that first logged event 486.
• Turn off the power for the controller enclosure, wait a few seconds, then turn it back on.
• Wait for the controller module to restart, then sign in again.
• Check the status of the vdisks. If any of the vdisks have a status of quarantined offline (QTOF),
dequarantine those vdisks.
• Reinsert the previously removed controller module. It should now restart successfully.
486
Info. A recovery process was initiated to prevent writing invalid data that may exist on the controller that logged
this event.
The controller that logged this event has detected (via information saved in the vdisk metadata) that it may
contain outdated data that should not be written to the vdisks. The controller will log this event, restart the
partner controller, wait 10 seconds, then kill itself. The partner controller will then unkill this controller and
mirror the correct cache data to it. This procedure will, in most cases, allow all data to be correctly written
without any loss of data and without writing any outdated data.
Recommended actions
• Wait at least 5 minutes for the automatic recovery process to complete. Then sign in and confirm that
both controller modules are operational. (You can determine if the controllers are operational with the
show redundancy-mode CLI command or the System Redundancy table in the System Overview
panel of the SMU.) In most cases, the system will come back up and no action is required.
• If both controller modules do not become operational in 5 minutes, see the recommended actions for
event 485, which will be logged at approximately the same time.
487
Info. Historical performance statistics were reset.
Recommended actions
• No action is required.
HP P2000 G3 MSA System Event Descriptions Reference Guide 59
Page 60
495
Warning The algorithm for best-path routing selected the alternate path to the indicated disk because the I/O error
count on the primary path reached its threshold.
The controller that logs this event indicates which channel (path) has the problem. For example, if the B
controller logs the problem, the problem is in the chain of cables and expansion modules connected to the
B controller module.
Recommended actions
• If this event is consistently logged for only one disk in an enclosure, perform the following actions:
•Replace the disk.
• If that does not resolve the problem, the fault is probably in the enclosure midplane. Replace the
chassis-and-midplane FRU for the indicated enclosure.
• If this event is logged for more than one disk in an enclosure or disks in multiple enclosures, perform the
following actions:
• Check for disconnected SAS cables in the bad path. If no cables are disconnected, replace the
cable connecting to the ingress port in the most-upstream enclosure with reported failures. If that
does not resolve the problem, replace other cables in the bad path, one at a time until the problem
is resolved.
• If that does not resolve the problem, replace the expansion modules that are in the bad path. Begin
with the most-upstream module that is in an enclosure with reported failures. If that does not resolve
the problem, replace other expansion modules (and the controller module) upstream of the affected
enclosure(s), one at a time until the problem is resolved.
• If that does not resolve the problem, the fault is probably in the enclosure midplane. Replace the
chassis-and-midplane FRU of the most-upstream enclosure with reported failures. If that does not
resolve the problem and there is more than one enclosure with reported failures, replace the
chassis-and-midplane FRU of the other enclosures with reported failures until the problem is
resolved.
Troubleshooting steps for leftover disk drives
HP MSA2000/P2000 arrays use metadata on hard drives to identify vdisk members and identify other
disk members of the vdisk.
Hard drives enter a Leftover state for several reasons:
• Drive spin up was not completed before a controller polled the drive. When the controller queries the
drive and finds the drive is not in a ready state, the controller may place the drive into a Leftover state.
• Improper power-on sequences.
• Firmware upgrade (due to a timing issue).
• Failover taking longer than expected.
• The drive is swapped from another MSA system, or removed and reinserted in the array.
Metadata on a disk identifies the disk as being a member of a vdisk. Improperly clearing the metadata
from a disk may cause permanent data loss.
CAUTION: Clearing metadata from a leftover drive should be done with extreme care. Only clear
metadata without looking at logs if you are certain the drive has never been associated with a vdisk in this
MSA system or contains no data. This situation most often occurs when inserting a previously used hard
drive into a live system or moving a drive between two systems.
Never clear metadata from a drive if any vdisk in the array is in an Offline, Quarantined, or inaccessible
state. Do not clear metadata from a drive if you are unsure this is the correct step to take. Clearing
metadata from a drive permanently clears all data from the drive. In these types of situations, a backup of
data should be done if possible.
60 Event descriptions
Page 61
Using the trust command
The CLI trust command should only be used as a last step in a disaster recovery situation. This command
has the potential to cause permanent data loss and unstable operation of the vdisk. If a vdisk with a single
disk is in a leftover or failed condition, the trust command should never be used. The trust command
should only be used if the vdisk is in an Offline state.
If a single disk in a vdisk has failed or been placed into a Leftover state due to UREs, Smart Trip, Sense
Key, or other errors, reintegrating the disk into the same or a different vdisk has the potential to cause data
loss. A hard drive that has failed or been placed into a Leftover state due to multiple errors should be
replaced with a new hard drive. Assign the new hard drive back to the vdisk as a spare and allow
reconstruction to complete in order to return the vdisk to a fault tolerant state
The trust command attempts to resynchronize leftover disks in order to make any leftover disk an active
member of the vdisk again. The user might need to take this step when a vdisk is offline because there is
no data backup, or as a last attempt to try to recover the data on a vdisk. In this case, trust may work,
but only as long as the leftover disk continues to operate. When the "trusted" vdisk is back online, backup
all data on the vdisk and verify all data to ensure it is valid. The user then needs to delete the trusted vdisk,
create a new vdisk, and restore data from the backup to the new vdisk.
IMPORTANT: Using trust on a vdisk is only a disaster-recovery measure; the vdisk has no tolerance for
additional failures and should never be put back into a production environment.
CAUTION: Before trusting a vdisk, carefully read the cautions and procedures for using the trust
command in the CLI Reference Guide and online help.
Once the trust command has been issued on a vdisk, further troubleshooting steps may be limited
towards disaster recovery. If you are unsure of the correct action to take, contact HP Support for further
assistance.
HP P2000 G3 MSA System Event Descriptions Reference Guide 61
Page 62
Power supply faults and recommended actions
Table 2 Power supply faults and recommended actions
Fault Recommended action
Power supply fan warning or failure, or power
supply warning or failure. Event code 168.
Power supply module status is listed as failed or
you receive a voltage event notification. Event code
16 8 .
Power LED is off. Same as above.
Voltage/Fan Fault/Service Required LED is on. Replace the power supply module.
• Check that all of the fans are working using
SMU.
• Make sure that no slots are left open for more
than two minutes. If you need to replace a
module, leave the old module in place until you
have the replacement, or use a blank cover to
close the slot. Leaving a slot open negatively
affects the airflow and might cause the unit to
overheat.
• Make sure that the
pr
operly seated in their slots and that their
latches are locked.
• For each power supply module with a switch,
check that the switch is turned on.
• Check that the power cables are firmly plugged
into both power supply and into an appropriate
and functional electrical outlet.
• Replace the power supply module.
power supply modules are
Events sent as indications to SMI-S clients
If the storage system’s SMI-S interface is enabled, the system will send events as indications to SMI-S clients
so that SMI-S clients can monitor system performance. For information about enabling the SMI-S interface,
see the chapter about configuring the system in the SMU Reference Guide.
The event categories below pertain to FRU assemblies and certain FRU components.
Table 3 Events and corresponding SMI-S indications
FRU/Event category Corresponding SMI-S class Operation status values that would trigger alert
conditions
Controller HP_Controller Down, Not Installed, OK
Hard Disk Drive HP_DiskDrive Unknown, Missing, Error, Degraded, OK
Fan HP_PSUFan Error, Stopped, OK
Power Supply HP_PSU Unknown, Error, Other, Stressed, Degraded, OK
Temperature Sensor HP_OverallTempSensor Unknown, Other, Error, Non-Recoverable Error,
Degraded, OK
Battery/SuperCap HP_SuperCap Unknown, Error, OK
FC Port HP_FCPort Stopped, OK
SAS Port HP_SASTargetPort Stopped, OK
ISCSI Port HP_ISCSIEthernetPort Stopped, OK
62 Event descriptions
Page 63
Resolving scrub errors
Background scrub procedures have been improved in recent controller firmware, including the ability to
automatically correct scrub errors, so the best solution to scrub errors is to upgrade to J202, J212, J302,
M113, or TS240. If upgrading firmware is not an option, follow the steps below.
NOTE: Disks that have logged SMART events or Unrecoverable Read Errors are candidates for
replacement.
Preliminary steps
1. Ensure that the storage system’s firmware version is one of the following or newer:
J200P39, J210P19, J300P20, M110R21
2. Ensure that the storage system’s hardware is healthy and stable.
3. Create a full backup of all data in the vdisk. HP recommends enabling all available verification
options. Verify the data integrity of the backup.
4. Correct any hardware issues.
Fixing consistency errors reported by the scrub utility
In this procedure, use the CLI verify vdisk command with its fix parameter, hereafter referred to as
“verify-fix.” Verify-fix corrects parity based on the data in the stripe at the present time and makes mirror
halves match by copying contents from the first drive in the mirror vdisk to the second drive.
NOTE:
• For parity disks, verify-fix recalculates parity for the failed stripe.
• For mirrored vdisks, verify-fix copies the data from the first disk in the vdisk to the second disk in the
vdisk.
• In either case, if the data are incorrect, verify-fix makes the consistency data (parity or the mirror copy)
match the incorrect data.
1. Complete the steps in Preliminary steps above.
2. Save the current logs from the storage system in a safe location:
a. Log in to the system’s FTP interface.
b. Enter:
get logs
3. Disable background scrub:
a. Log in to the CLI.
b. Enter:
set job-parameters background-scrub off
4. Verify that scrub is not running on the affected vdisk. If scrub is running on the vdisk, either:
• Wait for it to complete.
• Manually abort the scrub by logging in to the CLI and entering:
abort scrub vdisk
5. Run verify-fix by entering:
verify vdisk
• Allow 24 hours for this process to complete.
•Run show vdisk to ensure verify-fix is complete.
file-name
vdisk
fix yes
.zip
vdisk
HP P2000 G3 MSA System Event Descriptions Reference Guide 63
Page 64
6. When verify-fix has completed, re-enable background scrub:
a. Log in to the CLI.
b. Enter:
set job-parameters background-scrub on
7. Create a full backup of all data in the vdisk. HP recommends enabling all available verification
options. Compare with the original backup.
If errors occur during this procedure, or if the parity errors were not corrected or are seen again within a
short period of time, place a call with HP support. To help expedite your case, provide logs gathered at the
beginning of this procedure to HP support and a current copy of the logs.
64 Event descriptions
Page 65
Glossary
CAPI Configuration Application Programming Interface. The proprietary protocol used for
communication between the Storage Controller and the Management Controller in a
controller module. CAPI is always enabled.
CHAP Challenge-Handshake Authentication Protocol.
chunk size The amount of contiguous data that is written to a vdisk member before moving to the next
member of the vdisk.
compatible disk A disk that has enough capacity to replace a failed disk and is the same type (SAS or
SATA).
dedicated spare A disk that is reserved for use by a specific vdisk to replace a failed disk. See compatible
disk.
default mapping Host-access settings that are configured when a volume is created, and that apply to all
hosts that are not explicitly mapped to that volume using different settings. See also explicit
mapping and masking.
drive spin down (DSD) A power-saving feature that monitors disk activity in the storage system and spins down
inactive SAS and SATA disks, based on user-selectable policies.
DRM Disaster recovery management. Storage-system firmware features that, when the Site
Replication Adapter (SRA) feature is enabled, support the use of VMware’s Site Recovery
Manager to automate disaster-recovery failover and failback tasks. See also SRA.
dual-port disk A disk that is connected to both controllers so its data path is fault-tolerant.
dynamic spare An available compatible disk that is automatically assigned, if the dynamic spares option is
enabled, to replace a failed disk in a redundant vdisk. See compatible disk.
EC Expander Controller. The processor (located in the SAS expander in each controller module
and expansion module) that controls the SAS expander and provides SES functionality. See
also EMP.
EMP Enclosure management processor. An EC subsystem that provides SES data such as
temperature, power supply and fan status, and the presence or absence of disks.
explicit mapping Access settings for a host to a volume that override the volume’s default mapping. See also
default mapping and masking.
FC Fibre Channel interface protocol.
FRU Field-replaceable unit.
global spare A disk that is reserved for use by any redundant vdisk to replace a failed disk. See
compatible disk.
host An external port that the storage system is attached to. The external port may be a port in
an I/O adapter in a server, or a port in a network switch.
image ID A globally unique serial number that identifies the point-in-time image source for a volume.
All volumes that have identical image IDs have identical data content, whether they be
snapshots or stand-alone volumes.
IOM Input/output module, which can be either a controller module or an expansion module.
IQN iSCSI Qualified Name.
iSCSI Internet SCSI interface protocol.
iSNS Internet Storage Name Service.
jumbo frame In an iSCSI network, a frame that can contain 9000 bytes for large data transfers. A
normal frame can contain 1500 bytes.
leftover The state of a disk that has been automatically excluded from a vdisk, and is no longer
needed by the vdisk after the vdisk is reconstructed.
loop Fibre Channel Arbitrated Loop (FC-AL) topology.
HP P2000 G3 MSA System Event Descriptions Reference Guide 65
Page 66
masking Volume-mapping settings that specify no access to that volume by hosts. See also default
mapping and explicit mapping.
master volume A volume that is enabled for snapshots and has an associated snap pool.
MC Management Controller. The processor (located in a controller module) that is responsible
for human-computer interface and computer-computer interface functions, and interacts with
the SC.
metadata Data in the first sectors of a disk drive that stores all disk, vdisk, and volume specific
information including vdisk membership or spare identification, vdisk ownership, volumes
and snapshots in the vdisk, host mapping of volumes, and results of the last media scrub.
network port The Ethernet port on a controller module through which its Management Controller is
connected to the network.
point-to-point Fibre Channel Point-to-Point topology.
primary volume The volume that is the source of data in a replication set and that can be mapped to hosts.
For disaster recovery purposes, if the primary volume goes offline, a secondary volume can
be designated as the primary volume. The primary volume exists in a primary vdisk in the
primary (or local) storage system.
proxy volume A virtual volume in the local system that represents a volume in a remote system. Proxy
volumes are used internally by the controllers to perform actions such as transferring
replication data.
remote replication Asynchronous (batch) replication of block-level data from a volume in a primary system to a
volume in one or more secondary systems by creating a replication snapshot of the primary
volume and copying the snapshot data to the secondary systems via Fibre Channel or iSCSI
links. The capability to perform remote replication is a licensed feature (Remote Snap).
replication image A conceptual term for replication snapshots that have the same image ID in primary and
secondary systems. These synchronized snapshots contain identical data and can be used
for disaster recovery.
replication set Associated primary and secondary volumes that are enabled for replication and that
typically reside in two physically or geographically separate storage systems. See primary
volume and secondary volume.
replication snapshot A special type of snapshot, created by the remote replication feature, that preserves the
state of data of a replication set's primary volume as it existed when the snapshot was
created. For a primary volume, the replication process creates a replication snapshot on
both the primary system and, when the replication of primary-volume data to the secondary
volume is complete, on the secondary system. Replication snapshots are unmappable and
are not counted toward a license limit, although they are counted toward the system's
maximum number of volumes. A replication snapshot can be exported to a regular,
licensed snapshot. See also replication sync point.
replication sync point The state of a replication snapshot whose corresponding primary or secondary snapshot
exists and contains identical data. For a replication set, four types of sync point are
identified: the only replication snapshot that is copy-complete on any secondary system is
the “only sync point”; the latest replication snapshot that is copy-complete on any
secondary system is the “current sync point”; the latest replication snapshot that is
copy-complete on all secondary systems is the “common sync point”; a common sync point
that has been superseded by a new common sync point is an “old common sync point.”
SAS Serial Attached SCSI interface protocol or disk-drive architecture.
SATA Serial ATA disk-drive architecture.
SC Storage Controller. The processor (located in a controller module) that is responsible for
RAID controller functions. The SC is also referred to as the RAID controller.
66 Glossary
Page 67
secondary volume The volume that is the destination for data in a replication set and that is not accessible to
hosts. For disaster recovery purposes, if the primary volume goes offline, a secondary
volume can be designated as the primary volume. The secondary volume exists in a
secondary vdisk in a secondary (or remote) storage system.
The contents of a secondary volume are in a constant state of flux and are not in a
consistent state while a replication is in process. Only snapshots that are associated with a
secondary volume are data consistent.
secret For use with CHAP, a password that is shared between an initiator and a target to enable
authentication.
SES SCSI Enclosure Services.
single-port disk A disk that is connected to both controllers so its data path is not fault-tolerant. Single-port
disk types are identified with the suffix -S.
snap pool A volume that stores data that is specific to snapshots of an associated master volume,
including copy-on-write data and data written explicitly to the snapshots. A snap pool
cannot be mapped.
snapshot A “virtual” volume that preserves the state of a master volume’s data as it existed when the
snapshot was created. Data associated with a snapshot is recorded in both the master
volume and in its associated snap pool. A snapshot can be mapped and written to. The
capability to create snapshots is a licensed feature. Snapshots that can be mapped to hosts
are counted against the snapshot-license limit, whereas transient and unmappable
snapshots are not.
SRA Storage Replication Adapter. A host-based software component that allows VMware’s Site
Recovery Manager to manage the storage-system firmware’s disaster recovery management
(DRM) features, automating disaster-recovery failover and failback tasks. The SRA uses the
CLI XML API to control the storage system. See also DRM.
ULP Unified LUN Presentation. A RAID controller feature that enables a host to access mapped
volumes through any controller host port. ULP incorporates Asymmetric Logical Unit Access
(ALUA) extensions.
unwritable cache data Cache data that has not been written to disk and is associated with a volume that no longer
exists or whose disks are not online. If the data is needed, the volume’s disks must be
brought online. If the data is not needed it can be cleared, in which case it will be lost and
data will differ between the host and disk. Unwritable cache is also called orphan data.
vdisk A “virtual” disk comprising the capacity of one or more disks. The number of disks that a
vdisk can contain is determined by its RAID level.
volume A portion of the capacity of a vdisk that can be presented as a storage device to a host.
volume copy An independent copy (clone) of the data in a volume. The capability to create volume
copies makes use of snapshot functionality.
WWN World Wide Name. A globally unique 64-bit number that identifies a node process or
node port.
WWNN World Wide Node Name. A globally unique 64-bit number that identifies a node process.
WWPN World Wide Port Name. A globally unique 64-bit number that identifies a node port.
HP P2000 G3 MSA System Event Descriptions Reference Guide 67
Page 68
68 Glossary
Loading...