IBM Storwize V7000 Unified Problem Determination Manual page 170

Table of Contents

Advertisement

Procedure
1. Attempt to open an SSH connection to the root IP of one of the file modules
[root@kq186wx.mgmt002st001 ~]# lsnode
EFSSG0026I Cannot execute commands because Management Service is stopped.
Use startmgtsrv to restart the service.
2. Determine the service IP addresses for the file modules hosting a management
Table 33. Hostname and service IP reference
Host name
mgmt001st001
mgmt002st001
Performing management node role failover on a "good" system
Use this procedure to complete a failover process when both file modules appear
to be operating correctly.
About this task
If both file modules are operating correctly with regard to management services,
perform the following procedure to failover the active management node to the
passive management node.
150
Storwize V7000 Unified: Problem Determination Guide 2073-720
hosting a management node role.
Note: Run the CLI command lsnode.
v If you get output from lsnode that shows the system configuration (as in
Example 1), proceed to step 2.
v If you get a message that the management service is stopped or is not
running (as in Example 2), attempt to log out and log in to the other file
module hosting a management node role. If the other file module is not
responding, refer to "Performing management node role failover procedures
for failure conditions" on page 151.
Example 1: System configuration output from lsnode displays similar to the
following example:
[root@kq186wx.mgmt001st001 ~]# lsnode
Hostname
IP
Description
mgmt001st001 172.31.8.2 active management node management,interface,storage
mgmt002st001 172.31.8.3 passive management node management,interface,storage
Product version Connection status GPFS status CTDB status Last updated
1.3.0.0-50a
OK
1.3.0.0-50a
OK
EFSSG1000I The command completed successfully.
[root@kq186wx.mgmt001st001 ~]#
Example 2: Output for lsnode for a management service that is not running is
similar to the following example:
node role by running the CLI command lsnwmgt. Output that is similar to the
following example is displayed:
[root@kq186wx.mgmt001st001 ~]# lsnwmgt
Interface Service IP Node1 Service IP Node2
ethX0
9.11.137.128
Management IP Network
9.11.137.127 255.255.254.0 9.11.136.1
EFSSG1000I The command completed successfully.
The following table describes the nodes that are identified by the command:
Role
active
active
8/30/11 8:36 PM
active
active
8/30/11 8:36 PM
9.11.137.129
Gateway
VLAN ID
Corresponding Service IP reference
Service IP Node1
Service IP Node2

Advertisement

Table of Contents
loading

Table of Contents