Number Severity Description/Recommended actions
All enclosure EMPs are disabled.
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.
162 Warning The host WWNs (node and port) previously presented by this controller module are unknown. In a dual-
controller system this event has two possible causes:
• One or both controller modules have been replaced or moved while the system was powered o.
• One or both controller modules have had their ash conguration cleared (this is where the previously
used WWNs are stored).
The controller module recovers from this situation by generating a WWN based on its own serial number.
Recommended actions:
• If the controller module was replaced or someone reprogrammed its FRU ID data, verify the WWN
information for this controller module on all hosts that access it.
163 Warning The host WWNs (node and port) previously presented by the partner controller module, which is currently
oine, are unknown.
This event has two possible causes:
• The online controller module reporting the event was replaced or moved while the system was powered
o.
• The online controller module had its ash conguration (where previously used WWNs are stored) cleared.
The online controller module recovers from this situation by generating a WWN based on its own serial number
for the other controller module.
Recommended actions:
• If the controller module was replaced or someone reprogrammed its FRU ID data, verify the WWN
information for the other controller module on all hosts that access it.
166 Warning The RAID metadata level of the two controllers does not match, which indicates that the controllers have
dierent rmware levels.
Usually, the controller at the higher rmware level can read metadata written by a controller at a lower
rmware level. The reverse is typically not true. Therefore, if the controller at the higher rmware level failed,
the surviving controller at the lower rmware level cannot read the metadata in disks that have failed over.
Recommended actions:
• If this occurs after a rmware update, it indicates that the metadata format changed, which is rare. Update
the controller with the lower rmware level to match the rmware level in the other controller.
167 Warning A diagnostic test at controller bootup detected an abnormal operation, which might require a power cycle to
correct.
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.
170 Info. The last rescan detected that the indicated enclosure was added to the system.
Recommended actions:
• No action is required.
171 Info. The last rescan detected that the indicated enclosure was removed from the system.
Events and event messages 95