IBM Storwize V7000 Unified Problem Determination Manual page 213

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: You need a CLI user with SystemAdmin privilege to perform this
procedure. 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.
Procedure
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 186
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
185
Chapter 4. File module