Owners Manual

Table 27. Event descriptions and recommended actions (continued)
Number Severity Description/Recommended actions
● No action is required.
84 Warning The current controller that logged this event forced the partner controller to fail over.
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.
86 Info. Host-port or disk-channel parameters have been changed.
Recommended actions:
● No action is required.
87 Warning The mirrored configuration retrieved by this controller from the partner controller has a bad
cyclic redundancy check (CRC). The local flash configuration will be used instead.
Recommended actions:
● Restore the default configuration by using the restore defaults command, as described
in the CLI Reference Guide.
88 Warning The mirrored configuration retrieved by this controller from the partner controller is corrupt. The
local flash configuration will be used instead.
Recommended actions:
● Restore the default configuration by using the restore defaults command, as described
in the CLI Reference Guide.
89 Warning The mirrored configuration retrieved by this controller from the partner controller has a
configuration level that is too high for the firmware in this controller to process. The local flash
configuration will be used instead.
Recommended actions:
● The current controller that logged this event probably has down-level firmware. Update the
firmware in the down-level controller. Both controllers should have the same firmware
versions.
When the problem is resolved, event 20 is logged.
90 Info. The partner controller does not have a mirrored configuration image for the current controller,
so the current controller's local flash configuration is being used.
This event is expected if the other controller is new or its configuration has been changed.
Recommended actions:
● No action is required.
91 Error In a testing environment, the diagnostic that checks hardware reset signals between controllers
in Active-Active mode failed.
Recommended actions:
● Perform failure analysis.
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.
Events and event messages 85