v With the CLI, log in as an admin user, then open the CLI and issue the
lsnode -r command to determine whether CTDB is active on all nodes.
The system displays information similar to the following:
[yourlogon@yourmachine]$ lsnode -r
EFSSG0015I Refreshing data.
Hostname IP Description Role
mgmt001st001 10.254.8.2 active management node management,interface,storage
mgmt002st001 10.254.8.3 passive management node management,interface,storage
Product version Connection status GPFS status CTDB status Last updated
1.3.0.0-55c OK active active
1.3.0.0-55c OK active unhealthy
EFSSG1000I The command completed successfully.
In the CTDB Status column, “active” indicates a healthy status and “unhealthy”
indicates an error status.
2. If the CTDB status for a file module is “unhealthy”, perform one or more of the
following procedures:
v Review the health status for any potential network problems. A network
failure between a file module and the customer can result in an
“UNHEALTHY” CTDB status. Follow the appropriate error code action plans
to resolve the network problems. Refer to “Checking network interface
availability” on page 166.
v If the network has been isolated without any problems being identified,
perform the procedures in “Checking the GPFS file system mount on each
file module” on page 162.
v Refer to the information in “Troubleshooting the System x3650” in the IBM
Storwize V7000 Unified Information Center to determine if any additional
hardware problems might be causing the “unhealthy” CTDB status.
v Perform a reboot of the unhealthy file module. Refer to “Resuming services
on a suspended file module” in the IBM Storwize V7000 Unified Information
Center.
1
2
Figure 46. Management GUI showing CTDB status for both file modules
Chapter 4. File module 161
To Next Page
Need help?
General
