Owners Manual

Table 27. Event descriptions and recommended actions (continued)
Number Severity Description/Recommended actions
● For variant 5: The controller modules should be updated to the latest version of firmware.
Info. A partner firmware update operation has started. This operation is used to copy firmware from
one controller to the other to bring both controllers up to the same version of firmware.
Recommended actions:
● No action is required.
270 Warning Either there was a problem reading or writing the persistent IP data from the FRU ID SEEPROM,
or invalid data were read from the FRU ID SEEPROM.
Recommended actions:
● Check the IP settings (including iSCSI host-port IP settings for an iSCSI system), and update
them if they are incorrect.
271 Info. The storage system could not get a valid serial number from the FRU ID SEEPROM on the
controller, either because it could not read the FRU ID data, or because the data in it is not valid
or has not been programmed. Therefore, the MAC address is derived by using the controller
serial number from flash. This event is only logged one time during bootup.
Recommended actions:
● No action is required.
272 Info. A snap pool was expanded due to a policy trigger.
Recommended actions:
● No action is required.
273 Info. PHY fault isolation has been enabled or disabled by a user for the indicated enclosure and
controller module.
Recommended actions:
● No action is required.
274 Warning The indicated PHY has been disabled, either automatically or by a user. Drive PHYs are
automatically disabled for empty disk slots or if a problem is detected. The following reasons
indicate a likely hardware fault:
● Disabled because of error count interrupts
● Disabled because of excessive PHY change counts
● PHY is ready but did not pass COMINIT
Recommended actions:
● If none of the preceding reasons apply, no action is required.
● If any of the preceding reasons are indicated and the event occurs shortly after the storage
system is powered up, do the following:
○ Shut down the Storage Controllers. Then turn off the power for the indicated enclosure
wait a few seconds, and turn it back on.
○ If the problem recurs and the event message identifies a disk slot, replace the disk in that
slot.
○ If the problem recurs and the event message identifies a module, do the following:
￭ If the indicated PHY type is Egress, replace the cable in the module's egress port
￭ If the indicated PHY type is Ingress, replace the cable in the module's ingress port
￭ For other indicated PHY types or if replacing the cable does not fix the problem,
replace the indicated module.
○ If the problem persists, check for other events that may indicate faulty hardware, such as
an event indicating an over-temperature condition or power supply fault, and follow the
recommended actions for those events.
○ If the problem persists, the fault may be in the enclosure midplane. Replace the chassis
FRU.
● If any of the preceding reasons are indicated and this event is logged shortly after a failover,
user-initiated rescan, or restart, do the following:
Events and event messages
101