Power Supply Faults And Power Cycle; Power Cycle - HP MSA 2040 Troubleshooting Manual

Table 14 Instances when the Management Controller becomes Unresponsive (continued)
Symptom
The following sequence of messages
appears in the array logs:
152 INFORMATIONAL The
Storage Controller is not receiving
data from the Management
Controller. (This is normal during
firmware update.)
153 INFORMATIONAL The
Storage Controller resumed
communications with the
Management Controller.
152 INFORMATIONAL The
Storage Controller is not receiving
data from the Management
Controller.
156 WARNING The Management
Controller was restarted by the
Storage Controller.
139 INFORMATIONAL The
Management Controller booted
up. MC firmware version:
XXXXXXXX (baselevel: XXXX)
153 INFORMATIONAL The
Storage Controller resumed
communications with the
Management Controller.
152 INFORMATIONAL The
Storage Controller is not receiving
data from the Management
Controller. (This is normal during
firmware update.)
153 INFORMATIONAL The
Storage Controller resumed
communications with the
Management Controller
For information on replacing the Controller Module, see HPE MSA Controller Module Replacement
Instructions Guide on the Hewlett Packard Enterprise Support Center website.

Power Supply Faults and Power Cycle

"Power Cycle" (page 23)
"Power Supply Faults and Recommended Actions" (page 25)

Power Cycle

Under normal operations because of the redundant nature of the MSA array, the system should
not require a full system power cycle. Restarting each controller independently results in the
same outcome as a full power cycle, while still maintaining host connectivity.
On the front of every MSA is an Enclosure ID LED. This LED will aid in identifying the Controller
shelf. The Controller Shelf will report as "1" and any subsequent enclosures will have higher
numbered IDs.
Cause
Management Controller and Storage
Controller are unable to
communicate.
Action Required
For systems that have a
communication error between the MC
and SC, perform any one of the
following steps:
Run the following CLI command:
#restart mc A
Continue? yes <enter
return>
Success: MC A restarted.
Restart the MC using SMU.
NOTE:
During the restart process, you will
briefly lose communication with the
specified management controllers
In some cases, if the restart function
previously noted does not clear the
MC hang issue, you might attempt
to reseat the offending controller.
Before reseating the offending
controller, you must perform a
couple of safety measures:
1. Get and verify a backup of the
data on the array.
2. If possible, quiesce the I/O to the
array.
3. Shutdown the controller, for
example, shutdown a|b|both
Alternatively, shutdown the
controller using the SMU.
Shutting down both the
controllers is an offline activity.
4. Reseating a controller with
active I/O in a dual controller
array will cause I/O failover to
the other controller. In a single
controller array, this reseating
should be scheduled during a
maintenance window.
Power Supply Faults and Power Cycle 23