HP MSA Events Description Reference Guide (762785-001, March 2014)
42 Event descriptions
305
Info. A serial number in Storage Controller (SC) flash memory was found to be invalid when compared to the
serial number in the controller-module or midplane FRU ID SEEPROM. The valid serial number has been
recovered automatically.
Recommended actions
• No action is required.
306
Info. The controller-module serial number in Storage Controller (SC) flash memory was found to be invalid
when compared to the serial number in the controller-module FRU ID SEEPROM. The valid serial number
has been recovered automatically.
Recommended actions
• No action is required.
307
Critical A temperature sensor on a controller FRU detected an over-temperature condition that caused the
controller to shut down.
Recommended actions
• Check that the storage system’s fans are running.
• Check that the ambient temperature is not too warm. The enclosure operating range is 5 C–40 C
(41 F–104 F).
• Check for any obstructions to the airflow.
• Check that there is a module or blank plate in every module slot in the enclosure.
If none of the above explanations apply, replace the controller module that logged the error.
309
Info. Normally when the Management Controller (MC) is started, the IP data is obtained from the midplane
FRU ID SEEPROM where it is persisted. If the system is unable to write it to the SEEPROM the last time it
changed, a flag is set in flash memory. This flag is checked during startup, and if set, this event is logged
and the IP data that is in flash memory is used. The only time that this would not be the correct IP data
would be if the controller module was swapped and then whatever data are in the controller’s flash
memory is used.
Recommended actions
• No action is required.
310
Info. After a rescan, back-end discovery and initialization of data for at least one EMP (Enclosure Management
Processor) has completed. This event is not logged again when processing completes for other EMPs in
the system.
Recommended actions
• No action is required.
311
Info. This event is logged when a user initiates a ping of a host via the iSCSI interface.
Recommended actions
• If the ping operation failed, check connectivity between the storage system and the remote host.