HP StorageWorks 2000fc HP StorageWorks P2000 G3 MSA System Event Description R - Page 10

If you want hosts to access the volume data on the inserted disks, map the volume with a different

Get HP StorageWorks 2000fc - G2 Modular Smart Array PDF manuals and user guides View all HP StorageWorks 2000fc manuals
Add to My Manuals
Save this manual to your list of manuals

Page 10 highlights

67 Informational 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 Informational The controller that logged this event is shut down, or both controllers are shut down. Recommended actions • No action required. 71 Informational The controller has started or completed failing over. Recommended actions • No action required. 72 Informational After failover, recovery has either started or completed. Recommended actions • No action required. 73 Informational The two controllers are communicating with each other and cache redundancy is enabled. Recommended actions • No action required. 74 Informational 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 required. 75 Informational The indicated volume's LUN 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 inserted from another enclosure. Recommended actions • If you want hosts to access the volume data on the inserted disks, map the volume with a different LUN. 76 Informational 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. 77 Informational The cache was initialized as a result of power up or failover. Recommended actions • No action required. 10

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
10
67
Informational
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
Informational
The controller that logged this event is shut down, or both controllers are shut down.
Recommended actions
•
No action required.
71
Informational
The controller has started or completed failing over.
Recommended actions
•
No action required.
72
Informational
After failover, recovery has either started or completed.
Recommended actions
•
No action required.
73
Informational
The two controllers are communicating with each other and cache redundancy is enabled.
Recommended actions
•
No action required.
74
Informational
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 required.
75
Informational
The indicated volume’s LUN 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 inserted from
another enclosure.
Recommended actions
•
If you want hosts to access the volume data on the inserted disks, map the volume with a different LUN.
76
Informational
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.
77
Informational
The cache was initialized as a result of power up or failover.
Recommended actions
•
No action required.