Table 28. Event descriptions and recommended actions (continued)
Number Severity Description/Recommended actions
95 Error Both controllers in an Active-Active configuration have the same serial number. Non-unique
serial numbers can cause system problems. For example, 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.
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 the Storage Controller and then restart it.
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 (logical unit number) has been changed for the indicated volume.
Recommended actions:
● No action is required.
106 Info. The indicated volume has been added to the indicated pool.
Recommended actions:
● No action is required.
107 Error A serious error has been detected by the controller. 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:
● Download the debug logs from your storage system and contact technical support. A service
technician can use the debug logs to determine the problem.
108 Info. The indicated volume has been deleted from the indicated pool.
Recommended actions:
● No action is required.
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.
Events and event messages 83