IBM Storwize V7000, Problem Determination Manual

Page: 184 / 314

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.
5. Open an SSH connection to the service IP and port of the file module with the
passive management node role. Refer to “Determining the service IP for the
management node roles” on page 157.
6. Verify the management service status by running the CLI command lsnode . If
the file file module responds that the management service is not running,
proceed to the next step.
7. Run the CLI command
startmgtsrv
. This starts the management services on
the passive node.
8.
Once command execution is complete:
a. Verify that the management service is running by again executing the CLI
command
lsnode
.
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 lsnode output reports that the management service is still not
running, contact IBM support.
9. Using the GUI event log, follow the troubleshooting documentation against the
file module with the failed management node role to isolate the software or
hardware problem that might have caused this issue.
Checking CTDB health
Use this information for checking system health with the clustered trivial database
(CTDB).
CTDB checks the health status of the Storwize V7000 Unified file modules,
scanning elements such as storage access, General Parallel File System (GPFS),
networking, Common Internet File System (CIFS), and Network File System (NFS).
An unhealthy file module cannot serve public Internet Protocol (IP) addresses and
must be fixed. However, the high availability features of the Storwize V7000
Unified system can mask the unhealthy status from its clients by failing over IP
addresses from an unhealthy file module to a healthy file module.
If your file modules are in an unhealthy state, your clients lose IP access. In the
management graphical user interface (GUI), select
Monitoring > System and check
the health status for errors and degraded events.
To check the status using either the GUI or the command-line interface (CLI),
complete this procedure:
1. To check the CTDB status:
v With the Storwize V7000 Unified GUI, use the following method:
Select Monitoring > System Details > Interface Nodes > mgmt001st001 >
NAS Services . In the CTDB state row, a healthy status is displayed as
“Active” and an unhealthy status is displayed as “unhealthy”.
Review the status of both file modules,
1
mgmt001st001 and
2
mgmt002st001, as shown in Figure 46 on page 161.
160
Storwize V7000 Unified: Problem Determination Guide Version