Management Node Role Failover Procedures - IBM Storwize V7000 Unified Series Problem Determination Manual

Table 36. Storwize V7000 Unified logical devices and physical port locations (continued)
Logical Ethernet
device name Device description
mgmtsl0_1 Internal connection between the file modules Port 2 - Built-In xSeries Ethernet Port
ethXsl0_0 1 Gbps Customer Network
ethXsl0_1 1 Gbps Customer Network
ethXsl1_0 10 Gbps customer network
ethXsl1_1 10 Gbps customer network

Management node role failover procedures

The following procedures either restart the management service or initiate a
management service failover from the file module hosting the active management
node role to the file module hosting the passive management node role.
Once complete, the file module that previously hosted the active management
node role now hosts the passive management node role. The file module that
previously hosted the passive management node role now hosts the active
management node role.
Note: All of these tasks require a user that is configured as a CLI admin. Other
users cannot perform these tasks.
Determining the service IP for the management node roles
Use this procedure to identify the service IP addresses for the file modules that
host the management node roles.
You need the service IP address of a file module that hosts a management node
role to perform a management failover from the file module that hosts the active
management node role to the file module that hosts the passive management node
role, when the active management node fails and the current management IP does
not respond.
1. Attempt to open an SSH connection to the root IP of one of the file modules
Physical location information
Port 3 - Built-In xSeries Ethernet Port
Port 4 - Built-In xSeries Ethernet Port
Port 1 / 10GbE Converged Network Adapter
Port 2 / 10GbE Converged Network Adapter
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 "Management node role failover procedures for failure
conditions" on page 159.
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:
Role
active active 8/30/11 8:36 PM
active active 8/30/11 8:36 PM
157
Chapter 4. File module