68
Info.
The controller that logged this event is shut down, or both controllers are shut down.
Recommended actions
•
No action required.
71
Info.
The controller has started or completed failing over.
Recommended actions
•
No action required.
72
Info.
After failover, recovery has either started or completed.
Recommended actions
•
No action required.
73
Info.
The two controllers are communicating with each other and cache redundancy is enabled.
Recommended actions
•
No action 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 required.
75
Info.
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
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.
77
Info.
The cache was initialized as a result of power up or failover.
Recommended actions
•
No action required.
10