Owners Manual

Table 27. Event descriptions and recommended actions (continued)
Number Severity Description/Recommended actions
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 disk group was changed to be consistent with the IDs of
other disk groups. This can occur when disks that constitute a disk group are inserted from an
enclosure having a different FC loop ID.
This event is also logged by the new owning controller after disk group 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 in 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 is required.
78 Warning The controller could not use an assigned spare for a disk group because the spare’s capacity is
too small.
This occurs when a disk in the disk group 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, or if there is no spare of the correct type. There may be more than one failed
disk in the system.
Recommended actions:
● Replace each failed disk with one of the same type (SSD, enterprise SAS, or midline SAS)
and the same or greater capacity. For continued optimum I/O performance, the replacement
disk should have performance that is the same as or better than the one it is replacing.
● Configure disks as dedicated spares or global spares.
82 Events and event messages