IBM Storwize V7000 Unified Series Problem Determination Manual page 183

Management node role failover procedures for failure conditions
Use this topic to isolate and perform file module failover for failed conditions.
"Failed conditions" exist when the active management node has failed and is not
responding. This failure is exposed by the inability to access the file module, run
CLI commands, and/or access the GUI.
Note: If the management IP is accessible and you can establish an SSH connection
and run CLI tasks, do not perform a management failover. Refer to .
Complete the following procedure to address this issue.
Important: Performing this procedure does not repair a problem that caused the
current system condition. This procedure provides for system access and
troubleshooting to restart the management services or to failover the management
service from a failed file module to the passive management node on the other file
module. Once you complete this procedure, follow the appropriate troubleshooting
documentation to isolate and repair the core problem that caused this condition.
1. Attempt to open an SSH connection to the service IP of the file module with
the active management node role. Refer to . Was the connection successful?
v Yes - proceed to step 2
v No - proceed to step 5 on page 160
2. If the connection is successful, verify that the management service is not
running by executing the CLI command lsnode and then reviewing the output.
v If the system responds with output for the lsnode command, then the
management services are already running. If you still cannot access the GUI,
refer to . If the GUI is accessible, then the management services are properly
running on the active management node and no failover is needed. If you
want to initiate a failover, refer to "Performing management node role
failover on a "good" system" on page 158.
v If the system responds that the management service is not running, proceed
to the next step.
Note: For a management service that is not running, the system displays
information similar to the following example:
[yourlogon@yourmachine.mgmt002st001 ~]# lsnode
EFSSG0026I Cannot execute commands because Management Service is stopped.
Use startmgtsrv to restart the service.
3. Attempt to stop and restart the management services. Wait for the commands
to complete.
a. Run the CLI command stopmgtsrv.
b. Run the CLI command startmgtsrv. This restarts the management services.
4. Once command execution is complete:
a. Verify that the management service is running by again executing the CLI
command lsnode. If the system responds that the management service is
not running, proceed to step 5 on page 160.
b. If the lsnode output provides system configuration information, verify that
you can access and log in to the GUI. If you still have trouble with
accessing the GUI, refer to .
c. If the problem appears to be resolved, DO NOT perform steps 5-9. Instead,
using the GUI event log, follow the troubleshooting documentation to
isolate the software or hardware problem that might have caused this issue.
159
Chapter 4. File module