IBM Storwize V7000 Unified Problem Determination Manual page 171

Procedure
1. Open an SSH connection to the service IP of the file module hosting the passive
management node role.
Refer to "Determining the service IP for the management node roles" on page
149, if necessary.
2. To initiate the management services on the passive node and perform the
switchover from the active management node, run the startmgtsrv command.
Note: If you run the startmgtsrv command from the node that is becoming
active, you first need to run the setcluster command to set the cluster
environment variable. If you see the following error message when running the
command, wait until the initialization has completed before running
setcluster again:
IBM SONAS management service is starting up
EFSSG0654I The Management Service is starting up.
After you run the startmgtsrv command, the system displays information that
is similar to the following example:
[yourlogon@yourmachine.mgmt002st001 ~]# startmgtsrv
Other node is reachable and its management state is active.
Are you sure? (Y/N)Y
EFSSG0717I Takeover initiated by root - this may take a few minutes
EFSSG0544I Takeover of the management functions from the active
node was successful
Results
Once complete, the file module that previously hosted the active management
node role now hosts the passive management node role. The file module that
previously hosted the passive management node role now hosts the active
management node role.
Performing management node role failover procedures for failure
conditions
Use this topic to isolate and perform file module failover for failed conditions.
About this task
"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.
151
Chapter 4. File module