IBM Storwize V7000, Problem Determination Manual

Page: 45 / 314

of the Easy Setup Wizard and restart Easy Setup Wizard again. You have to key in
all fields for each step again. Once all steps are completed the system runs the
configuration and restarts.
GUI access issues
This topic provides assistance in isolating and resolving problems with the GUI.
This section covers GUI access issues that allow you to isolate and resolve GUI
problems. This section extends beyond the GUI in the case where a file module is
not responding and requires a management switchover to the other file module.
Accessing the GUI is critical to isolating and resolving system problems.
1. Does the GUI launch and are there problems logging into the system?
v
Yes : Check that the user ID being used was set up to access the GUI. Refer to
“Authentication basic concepts” in the IBM Storwize V7000 Unified Information
Center .
v
No : Proceed to next question.
2. Does the GUI launch and are there problems logging into the system?
v
Yes : Verify that you are using a supported browser and the browser settings
are correct. Refer to “Checking your web browser settings for the
management GUI” in the
IBM Storwize V7000 Unified Information Center .
v No : Proceed to next question.
Note:
If the GUI does not load complete these steps.
3. Are you able to initiate an ssh connection to either file node and log in to
either file node?
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 157.
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:
[root@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.
Chapter 3. Getting started troubleshooting
21