IBM Storwize V7000 Unified Problem Determination Manual page 172

Procedure
1. Attempt to open an SSH connection to the service IP of the file module with
2. If the connection is successful, verify that the management service is not
3. Attempt to stop and restart the management services. Wait for the commands
4. Once command execution is complete:
5. Open an SSH connection to the service IP and port of the file module with the
6. Verify the management service status by running the CLI command lsnode. If
7. Run the CLI command startmgtsrv. This starts the management services on
8. Once command execution is complete:
152
Storwize V7000 Unified: Problem Determination Guide 2073-720
the active management node role. Refer to . Was the connection successful?
v Yes - proceed to step 2
v No - proceed to step 5
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 150.
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.
to complete.
a. Run the CLI command stopmgtsrv.
b. Run the CLI command startmgtsrv. This restarts the management services.
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.
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.
Attention: Perform the following steps only if the active management node is
not responding properly. These steps initiate a startup and failover of the
management services on the file module hosting the passive management node
role.
passive management node role. Refer to "Determining the service IP for the
management node roles" on page 149.
the file file module responds that the management service is not running,
proceed to the next step.
the passive node.
a. Verify that the management service is running by again executing the CLI
command lsnode.