Owners Manual

Table 27. Event descriptions and recommended actions (continued)
Number Severity Description/Recommended actions
● No action is required.
157 Error A failure occurred when trying to write to the Storage Controller (SC) flash chip.
Recommended actions:
● Replace the controller module that logged this event.
158 Error A correctable ECC error occurred in Storage Controller CPU memory more than once during a
12-hour period, indicating a probable hardware fault.
Recommended actions:
● Replace the controller module that logged this event.
Warning A correctable ECC error occurred in Storage Controller CPU memory.
This event is logged with Warning severity to provide information that may be useful to technical
support, but no action is required now. It will be logged with Error severity if it is necessary to
replace the controller module.
Recommended actions:
● No action is required.
161 Info. One or more enclosures do not have a valid path to an enclosure management processor (EMP).
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
off.
● One or both controller modules have had their flash configuration 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 offline, are unknown.
This event has two possible causes:\
● The online controller module reporting the event was replaced or moved while the system
was powered off.
● The online controller module had its flash configuration (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 different firmware levels.
Events and event messages 89