Configure: Change management server IP address

 

 

Topic

Customer Procedures

Selections

Procedures: Configure

Configure: Change management server IP address

Select cluster topology: VPLEX Metro or VPLEX Geo

 

 

Contents

Task 1:   Log in to the VPlexcli 3

Task 2:    Disable Call Home if it is enabled. 3

Task 3:   Disable Cluster Witness if it is enabled. 3

Task 4:   Change the IP address. 4

Task 5:   Configure Internet Protocol Security (IPsec) 4

Task 6:   Re-enable Cluster Witness if applicable. 5

Task 7:    Re-enable Call Home if applicable. 5

Task 8:   Close the SSH sessions. 5

Task 9:   VPLEX Metro: Update RecoverPoint splitter credentials. 5

 


 

Task 1:    Log in to the VPlexcli

                   

  1. [   ]    Using PuTTY (version 0.60 or later) or a similar SSH client, establish a connection to the current public IP address of the management server in Cluster 1, and log in as user service.

Note:  The EMC VPLEX Security Configuration Guide (available on EMC Support Online) contains the default passwords.

  2. [   ]      From the shell prompt, type the following command to connect to the VPlexcli:

Vplexcli

 

  3. [   ]    Log in with username service.

  4. [   ]     Repeat steps 1. [   ] and  2. [   ] on Cluster 2. (Leave the VPlexcli session on Cluster 1 open.)

Task 2:      Disable Call Home if it is enabled

                   

  1. [   ]      From the VPlexcli prompt on Cluster 1, type the following commands to verify the Call Home status:

cd /notifications/call-home

 

ls

 

Output example if Call Home is enabled:

Attributes:

Name     Value

----     -----

Enabled  true

 

  2. [   ]      If Call Home is enabled, type the following commands to disable it and confirm that it is disabled:

set enabled false --force

 

ls

 

Output example if Call Home is disabled:

Attributes:

Name     Value

----     -----

Enabled  false

 

  3. [   ]      Repeat steps 1. [   ] and 2. [   ] on Cluster 2.

Task 3:    Disable Cluster Witness if it is enabled

If VPLEX Witness (Cluster Witness) is enabled, perform the following steps to disable it until after you have changed the IP address:

                   

  1. [   ]      Type the following commands on Cluster 1:

cluster-witness disable –-force

 

configuration cw-vpn-reset

 

  2. [   ]      Type the following command on Cluster 2:

configuration cw-vpn-reset

 

Task 4:    Change the IP address

                   

  1. [   ]      From the VPlexcli prompt on the first or only management server whose address you are changing, type the following command:

management-server set-ip –i IP_address:netmask -g gateway_IP_address -p eth3

 

Example :

management-server set-ip –i 10.18.2.0:255.255.255.0 –g 10.18.2.2 –p eth3

 

Note:  Your SSH session to the management server now closes, and you can no longer use the old IP address to connect to the management server.

  2. [   ]    To verify that the address change was successful, establish an SSH connection to the management server’s new address, and log in as service.

  3. [   ]    If you are changing the addresses on both management servers, repeat steps 1. [   ] and 2. [   ]  on the other management server.

Task 5:    Configure Internet Protocol Security (IPsec)

                   

  1. [   ]      From the VPlexcli prompt on Cluster 1, type the following command:

version -a

 

  2. [   ]      Type the applicable commands, which depend on the Product Version in the output from step 1. [   ]:

·    If the version is 5.0 or higher:

security ipsec-configure -i remote_management_server_IP_address

 

vpn status

 

·    If the version is lower than 5.0:

Note:   The l in -l is a lowercase letter L (for local).

security ipsec-configure -l local_Cluster_IP_Seed -r remote_Cluster_IP_ Seed -i remote_management_server_IP_address -c hostCert.pem -k hostKey.pem

 

vpn status -l local_Cluster_IP_seed -n number_of_engines_in_local_cluster -c remote_Cluster_IP_Seed -e number_of_engines_in_remote_cluster -r remote_management_server_IP_address

 

Output example for GeoSynchrony 5.0:

Verifying the VPN status between the management servers...

IPSEC is UP

Remote Management Server at IP Address 10.12.147.254 is reachable

Remote Internal Gateway addresses are reachable

 

Verifying the VPN status between the management server and the cluster witness server...

IPSEC is UP

Cluster Witness Server at IP Address 128.221.254.3 is reachable

 

  3. [   ]      Repeat steps 1. [   ] and 2. [   ] on Cluster 2.

Task 6:    Re-enable Cluster Witness if applicable

If you disabled Cluster Witness earlier in this procedure, perform the following steps to re-enable it:

                   

  1. [   ]      Type the following command on Cluster 2:

configuration cw-vpn-configure public_address_of_Cluster_Witness_server

 

  2. [   ]      Type the following commands on Cluster 1:

configuration cw-vpn-configure public_address_of_Cluster_Witness_server

 

cluster-witness enable

 

Task 7:      Re-enable Call Home if applicable

If you disabled Call Home earlier in this procedure, perform the following steps to re-enable it:

                   

  1. [   ]      Type the following commands on Cluster 1 to enable Call Home and confirm that it is enabled:

set enabled true

 

ls

 

  2. [   ]      Repeat step 1. [   ] on Cluster 2.

Task 8:    Close the SSH sessions

                   

  1. [   ]       Type the following command to exit the VPlexcli on Cluster 2:

exit

 

  2. [   ]     Type the following command to exit the shell session:

exit

 

  3. [   ]       Repeat steps 1. [   ] and 2. [   ] on Cluster 1.

Task 9:    VPLEX Metro: Update RecoverPoint splitter credentials

Note:  RecoverPoint is not supported on VPLEX Geo configurations.

If RecoverPoint is deployed with this VPLEX cluster, the splitter credentials on each RecoverPoint cluster used with this VPLEX cluster must be updated, supplying the new IP address of the management server.

Before you can update the splitter credentials, you must clear the existing credentials from the RecoverPoint CLI and kill the affinity process.

                   

  1. [   ]    In the RecoverPoint CLI, type the following command to clear the splitter credentials from the RecoverPoint CLI:

clear_splitter_login_credentials

 

  2. [   ]    Type the following command to identify the affinity process on the Site Control RPA:

ps -ef | grep affinity

 

For example:

RecoverPoint_RPA2:/root# ps -ef | grep affinity

 

root      2640     1  0 Apr05 ?        00:00:00 /bin/tcsh ./vplex_affinity_loop.tcsh background

root      2660  2640  0 Apr05 ?        00:06:07 /usr/kashya/java/jre/bin/java -cp /home/kos/kashya/archive/classes/log4j-1.2.15.jar:/home/kos/kashya/archive/classes/orgjson.jar:/home/kos/kashya/archive/classes/java_mpi.jar:/home/kos/kashya/archive/classes/jni_mgmt.jar:/home/kos/kashya/archive/classes/management-client.jar:/home/kos/kashya/archive/classes/log4j-1.2.15.jar:/home/kos/kashya/archive/classes/apache-log4j-extras-1.0.jar:/home/kos/kashya/archive/classes/vplex_affinity.jar com.emc.vplex.discovery.VPLEXDiscovererMain

root     15631 15167  0 05:25 pts/0    00:00:00 grep affinity -

 

 

  3. [   ]    In the output, identify the ID of the vplex_affinity process.

  4. [   ]    Type the following command to kill the process:

kill -9 ID of the affinity process

 

Where ID of the affinity process is the ID displayed by the grep command.

CAUTION:    Do not kill the vplex_affinity_loop process.

For example:

RecoverPoint_RPA2:/root# kill -9 2660

 

  5. [   ]    After affinity process is back up, re-enter the following information:

·     Splitter credentials

·     New IP address

·     New username and password

When you have completed these steps, the system is ready for the credentials to be updated.

Refer to the RecoverPoint documentation to update the splitter credentials.