v Yes:
a. Run the CLI command lsnode and determine the status of the file nodes.
b. If the lsnode reports the management service is not running, refer to
“Management node role failover procedures” on page 183.
c. If lsnode provides the system configuration information, check the
connection status under the appropriate heading. Is the status set to OK:
Note: The Sample Output shown has been adjusted in regards to spacing
and layout to accommodate this publication. It might not match exactly
what is seen on your system.
Sample Output:
[admin@kq186wx.mgmt001st001 ~]# lsnode
Product Connection GPFS CTDB
Hostname IP Description Role version status status status Last updated
mgmt001st001 172.31.8.2 active management, 1.3.0.0-51c OK active active 9/19/11 8:02 AM
management interface,
node storage
mgmt002st001 172.31.8.3 passive management, 1.3.0.0-51c OK active active 9/19/11 8:02 AM
management interface,
node storage
EFSSG1000I The command completed successfully.
– Yes: Run the CLI command lshealth. Reference the active
management node Hostname (mgmt001st001 or mgmt002st002)
obtained from the lsnode command. Ensure that HOST_STATE,
SERVICE, and NETWORK from lshealth is set to OK.
Sample Output:
mgmt001st001 HOST_STATE OK OK
SERVICE OK All services are running OK
CTDB OK CTDBSTATE_STATE_ACTIVE
GPFS OK ACTIVE
SCM OK SCM system running as expected
NETWORK ERROR Network interfaces have a degraded state
CHECKOUT OK Disk Subsystem have a online state
mgmt002st001 HOST_STATE OK OK
SERVICE OK All services are running OK
CTDB OK CTDBSTATE_STATE_ACTIVE
GPFS OK ACTIVE
SCM OK SCM system running as expected
MGMTNODE_REPL_STATE OK OK
NETWORK ERROR Network interfaces have a degraded state
V7000 CLUSTER ERROR Alert found in component cluster
ENCLOSURE ERROR Alert found in component enclosure
IO_GRP OK The component io_grp is running OK
MDISK OK The component mdisk is running OK
NODE OK The component node is running OK
PORT ERROR Alert found in component port
EFSSG1000I The command completed successfully.
– No: Perform network connectivity isolation procedures. Refer to
“Management node role failover procedures” on page 183.
No: Perform network connectivity isolation procedures. Refer to
“Management node role failover procedures” on page 183.
If none of the previous steps resolved the GUI connectivity issues, perform the
following procedure.
Network port isolation for GUI:
Chapter 3. Getting started troubleshooting 61
To Next Page
Loading...
Need help?
General
