Table 13 Management Controller scenarios
Action RequiredSymptom
SC component is functioning
properly and all Host I/O are being
• Restart MC from the other controller, if possible.
• If that does not resolve the issue, restart the array.
handled correctly while the MC
component is not accepting a user
login
Log in to the Management Controller on the other storage controller and restart
the unresponsive Management Controller.
For example, an array with the following setup:
A storage controller might be
replaced or power-cycled due to
an unresponsive Management
Controller port.
Controller A—IP 15.5.224.9
Controller B—IP 15.5.224.10
Verify the network connectivity by issuing a ping to the MC IP address of the
controller. Ensure that an issue does not exist with the intranet on which the
MSA is installed.
nl
# ping 15.5.224.9
nl
Reply from 15.5.224.9 bytes=32 time60
If the ping command does not return a valid response, investigate the network
or cabling.
If controller A responds to the ping but is not enabling logins via the CLI or
SMU interface, log in to controller B via the CLI and attempt to restart the MC
on controller A.
The following example shows a login and restart of a controller through the CLI
interface:
#restart mc A
Continue? yes <enter return>
Success: MC A restarted.
Wait a few moments after the Success information is displayed for the restart
process to complete and then try to log in to controller A.
If the Management Controller remains unresponsive, shutdown and restart
controller A using the opposite controller B, then recheck the Management
Controller.
NOTE: During restart, you will briefly lose communication with the specified
management controllers:
From controller B:
#shutdown A
Wait for A to shutdown
#restart sc a < this will restart the Management Controller on controller
A as well >.
NOTE: In a single controller environment, if the CLI command is not successful,
quiesce all host I/Os before restarting the SC of the controller.
Management Controller Issue 21
To Next Page
Loading...
