Number
Severity
Description/Recommended actions
109
Info.
The statistics for the indicated volume have been reset.
Recommended actions:
•
No action is required.
110
Info.
Ownership of the indicated disk group 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.
112
Warning
The link for the indicated host port has unexpectedly gone down. This can affect host mappings.
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.
Info.
The link for the indicated host port has gone down because the controller is starting up.
Recommended actions:
•
No action is required.
114
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
.
116
Error
After a recovery, the partner controller was killed while mirroring write-back cache data to the 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 (Storage Controller booted up), closely followed by event 71 (failover started). The failover indicates
that the restart did not succeed.
117
Warning
This controller module detected or generated an error on the indicated host channel.
Recommended actions:
•
Restart the Storage Controller that logged this event.
•
If more errors are detected, check the connectivity between the controller and the attached host.
•
If more errors are generated, shut down the Storage Controller and replace the controller module.
118
Info.
Cache parameters have been changed for the indicated volume.
92
Events and event messages