Changing Control Station (CS) and Service Processor (SP) IP addresses on 7.0.35.3 VNX Unified systems

Need to change IP addresses on VNX Unified components

This solution describes the steps to follow when changing the IP addresses on the VNX Unified system. There are two scenarios for changing IP addresses, which depend on whether the address change is on the same network or to a new and different network.

CAUTION:  Please note that in the case of multiple systems joined or managed in a multi-domain environment, the system that requires the IP address change needs to first be removed from the Domain so that it is a stand-alone VNX system.

IMPORTANT! This solution applies only to FILE OE versions at 7.0.35 and later:  Refer to 77094 for the IP address change procedures for File OE versions 7.0.12.0 - 7.0.14.0

For a video demonstration of how-to for both of the following IP address change procedures (to a new network and within the same network) search for   media44409 at   EMC Online Support.

EMC customers can download documentation or software from EMC Online Support.  From the EMC Support home page menu bar, select Support by Product, search for the product using "Find a Product". The product page provides one-stop access to technical and support-related information by EMC product for downloads, documentation, tools and additional content.

Scenario I.  Changing network address from one network to a new and different network (See Scenario II if only changing IP address within the same network):

1. Connect to CS0 serial console using a serial cable connection and Putty:
   Note:  When viewed from the back of the Control Station, the serial connection is located on the right-hand side of the system
   
   a)  Launch Putty, click on Serial, configure the connection using Speed 19200, Data bits 8, Stop bits 1, Parity None, and Flow Control None
   b)  Log in as user nasadmin, then $ su to root user
    
2. Stop the Proxy ARP service to return the SPs to the default internal address scheme:

# /nas/sbin/clariion_mgmt -stop  (Let this command run to completion, then check SP IPs with ping)
# ping 128.221.252.200 [SPA]
# ping 128.221.253.201 [SPB]

3. Change CS0 IP address and verify:
   
   a)  Change the IP address on CS0 to the new network address and verify:
   
   # nas_cs -set -ip4address 10.240.210.110 -ip4netmask 255.255.255.0 -ip4gateway 10.240.210.1
   OK
   # nas_cel -list
   id    name          owner mount_dev  channel    net_path            CMU
   0     c250          0                           10.240.210.110      FNM001046001132007
   # grep  /etc/hosts
   10.240.210.110   c250.emc.com       c250
   
   b)  Wait 5-15 minutes for the new CS0 IP address to be updated with the domain by using the following commands:
   
   # /nas/sbin/navicli -h 128.221.252.200 domain -list
   # /nas/sbin/navicli -h 128.221.253.201 domain -list
   
   Note:  Should eventually see the new IP address referenced for CS0 in the output from both SPs.
   
   c)  Move CS0's management LAN cable to the new network switch (as required).
   
   d)  For single Control Station systems,  skip to Step 6.  For dual Control Station systems, continue with Step 4 below.

4. Failover to CS1, check that CS1 IP is updated in the domain, then change CS1 IP to the new network address:
   
   a)  From CS0, failover to CS1:
   
   # /nas/sbin/cs_standby -failover
   The system will reboot, do you wish to continue? [yes or no]: yes
   Failing over from Primary Control Station...
   
   b)  Connect to the serial console on CS1, log in, and verify that CS1 took over the role as "primary control station" as follows:
   
   Note:  You may need to wait 10-15 minutes for NAS Services to properly start and for the domain -list to update with the new IP address of CS1.
   
   # /nas/sbin/getreason
   11 - slot_0 secondary control station
   10 - slot_1 primary control station   -->This output shows that CS1 is serving the role as "Primary"
    5 - slot_2 contacted
    5 - slot_3 contacted
   # ps -ef |grep "boxm"
   # ps -ef |grep "nas_m"
   # /nas/sbin/navicli -h 128.221.252.200 domain -list
   # /nas/sbin/navicli -h 128.221.253.201 domain -list
   
   c)  Change CS1 IP to the new network address, verify, and wait for the domain -list to update:
   # nas_cs -set -ip4address 10.240.210.111 -ip4netmask 255.255.255.0 -ip4gateway 10.240.210.1
   OK
   # nas_cel -list
   # /nas/sbin/navicli -h 128.221.252.200 domain -list
   # /nas/sbin/navicli -h 128.221.253.201 domain -list
   Note:  Look for CS1's new IP address to update in the domain -list output for both SPs
   # grep /etc/hosts
   10.240.210.111   cs1_250.localdomain     cs1_250
   
   d)  Move CS1's LAN Management cable to the new network (as required).
   
   e)  Failback to CS0 from CS1, verify that CS0 IP is updated in domain -list, log in to Unisphere to verify system integrity:
   
   # /nas/sbin/cs_standby -failover
   The system will reboot, do you wish to continue? [yes or no]: yes
   Failing over from Primary Control Station...

5. Connect to the serial console on CS0, login, wait for NAS Services to start and the domain -list to update with CS0 IP:
   
   # ps -ef |grep "boxm"
   # ps -ef |grep "nas_m"
   # /nas/sbin/getreason
   10 - slot_0 primary control station
   11 - slot_1 secondary control station
   # /nas/sbin/navicli -h 128.221.252.200 domain -list
   # /nas/sbin/navicli -h 128.221.253.201 domain -list

6. Start the Proxy ARP service, specifying the new IP addresses for the SPs, and verify the changes:
   Note:  Starting the Proxy ARP service, assigning the IP addresses to the SPs, and updating the domain information, may take up to 15 minutes
   
   # /nas/sbin/clariion_mgmt -start -spa_ip 10.240.210.112 -spb_ip 10.240.210.113
   # /nas/sbin/getreason
   # nas_storage -c -a
   # ping 10.240.210.112
   # ping 10.240.210.113
   # /nas/sbin/navicli -h 10.240.210.112 domain -list
   # /nas/sbin/navicli -h 10.240.210.113 domain -list

Scenario II.  Changing network address within the same network:

1. Connect to Unisphere and log in.
   
   Note:  If the Unisphere login fails, the File domain may have been damaged during the IP address change process.  Check for the presence of the File domain files in the /nas/http/domain directory.  If the domain files are missing, you may need to contact your Service Provider for assistance in repairing the domain.
   
   # ls -la /nas/http/domain  -->the following files are representative of normal output
   -rw-r--r--  1 apache apache   67 Oct 21 06:30 domain_list
   -rw-r--r--  1 root   root    933 Oct 20 15:12 domain_log
   -rw-r--r--  1 apache apache  129 Oct 21 06:30 domain_master
   -rw-r--r--  1 apache apache 6418 Oct 21 06:30 domain_provider_xml
   -rw-------  1 apache apache  227 Oct 21 06:30 domain_users
   -rw-r--r--  1 apache apache    0 Sep 30 12:15 lock_file

2. Change the IP addresses of the SPs by using the following and verify that the changes succeeded:
   
   # /nas/sbin/clariion_mgmt -modify -spa_ip 10.240.200.52 -spb_ip 10.240.200.53
   # ping 10.240.200.52
   # ping 10.240.200.53
   # tail /etc/hosts
   10.240.200.52 A_FNM00104600113 SPA # CLARiiON SP
   10.240.200.53 B_FNM00104600113 SPB # CLARiiON SP
   # nas_storage -c -a
   Discovering storage on c250 (may take several minutes)
   done
   # /nas/sbin/navicli -h 10.240.200.52 domain -list
   # /nas/sbin/navicli -h 10.240.200.53 domain -list
    
3.  Change the IP address on CS0 and then verify that CS0's IP address is properly updated to the domain:
   
   # nas_cs -set -ip4address 10.240.200.50 -ip4netmask 255.255.255.0 -ip4gateway 10.240.200.1 
   OK
   # nas_cel -list
   id    name          owner mount_dev  channel    net_path          CMU
   0     c250          0                           10.240.200.50     FNM001046001132007
   # /nas/sbin/navicli -h 10.240.200.52 domain -list
   # /nas/sbin/navicli -h 10.240.200.53 domain -list
   # grep /etc/hosts
   10.240.200.50  c250.emc.com      c250
    
4. For dual Control Station systems, failover to CS1, change CS1's IP address, wait for CS1's IP address to update in the domain:
   
   a)  Failover to CS1
   
   # /nas/sbin/cs_standby -failover
   
   b)  Log in to CS1 and verify that CS1 is running as the "primary control station"
   
   Note:  It may take 10-15 minutes for NAS services to properly transition and startup on CS1
   
   # /nas/sbin/getreason
   11 - slot_0 secondary control station
   10 - slot_1 primary control station
    5 - slot_2 contacted
    5 - slot_3 contacted
   
   c)  Change the IP address on CS1:
   
   # nas_cs -set -ip4address 10.240.200.51 -ip4netmask 255.255.255.0 -ip4gateway 10.240.200.1
   OK
   # nas_cel -list
   # grep /etc/hosts
   10.240.200.51   cs1_250.localdomain     cs1_250
   
   d)  Verify that CS1's IP address has been updated to the domain before continuing
   
   # /nas/sbin/navicli -h 10.240.200.52 domain -list
   # /nas/sbin/navicli -h 10.240.200.53 domain -list

5. Failback to CS0, wait for CS0's IP address to update, then verify system management using Unisphere
   
   a)  Failback from CS1 to CS0
   
   # /nas/sbin/cs_standby -failover
   
   b)  Log in to CS0 and verify that CS0 is the "primary" Control Station.
   
   Note:  It may take 10-15 minutes for NAS services to properly start
   
   # /nas/sbin/getreason
   11 - slot_0 primary control station
   10 - slot_1 secondary control station
    5 - slot_2 contacted
    5 - slot_3 contacted
   
   c)  Verify that CS0's IP address has properly updated in the domain
   
   # /nas/sbin/navicli -h 10.240.200.52 domain -list
   # /nas/sbin/navicli -h 10.240.200.53 domain -list
   
   d)  Launch Unisphere, log in to either the CS or SP IP address, and then verify domain management functions.