epmmis
asked on
Site Recovery Manager Site changing IP address
In my previous post I asked about changing the vCenter server and ESX hosts IP address. I did not ask about the SRM service. Below are the procedures I will be using to change the vCenter and ESX IP addresses.
1. Should I break the connection between each site before changing the IP addresses?
2. How / when should SRM be included in the change?
Move vCenter Server to new network
Move ESX servers to new network.
1. Should I break the connection between each site before changing the IP addresses?
2. How / when should SRM be included in the change?
Move vCenter Server to new network
Shutdown all VMs.
Put each ESX server in Maintenance mode.
Put each ESX server in Maintenance mode.
Change the vMotion IP on each ESX server.
Configuration / Networking / Distributed Virtual Switch
Manage Virtual Adapters
Select VMK0 / Click Edit
Assign New IP Address.
Configuration / Networking / Distributed Virtual Switch
Manage Virtual Adapters
Select VMK0 / Click Edit
Assign New IP Address.
Remove each ESX server from DR Cluster.
Change vCenter server's IP address.
Reboot vCenter server.
Change vCenter server's IP address.
Reboot vCenter server.
Move ESX servers to new network.
Logon to the console as root.
Enter esxcfg-vswif -l to display the IP address.
Enter esxcfg-vswif -i <192.168.145.10> -n <255.255.255.0> vswif0
Enter esxcfg-vswif -l to display the change.
Change gateway - vi /etc/sysconfig/network.
Update Hosts file.
Reboot server
Begin the next ESX server IP address change.
Log back on to each server after it reboots to test connection. ping 192.168.145.20
Restore ESX servers to DR clusterEnter esxcfg-vswif -l to display the IP address.
Enter esxcfg-vswif -i <192.168.145.10> -n <255.255.255.0> vswif0
Enter esxcfg-vswif -l to display the change.
Change gateway - vi /etc/sysconfig/network.
Update Hosts file.
Reboot server
Begin the next ESX server IP address change.
Log back on to each server after it reboots to test connection. ping 192.168.145.20
Update ESX’s DNS records.
Start vCenter Console.
Right mouse click on DR cluster.
Add Host
Update VM IP addressesStart vCenter Console.
Right mouse click on DR cluster.
Add Host
Start each VM.
Access VM via the Console.
Update the IP address.
Access VM via the Console.
Update the IP address.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I stand corrected. The repair install of the SRM is necessary. Below is an extract of an e-maill from VMware technical support describing the steps to be taken.
The re-configuration of SRM basically requires a complete re-configure. You should first remove recovery plans on the existing DR site. Next you will want to remove protection groups followed by breaking the site pairing inside SRM.
At this point you can do the IP configuration changes to the DR site. Once you have completed these changes you will have to do a repair install of SRM on the DR site giving it the new IP address for the vCenter server on the DR site.
Finally you will have to go through the site pairing process, creation of protection groups, inventory mapping and finally creation of recovery plans. After all of this do a test failover and all should be well.
The re-configuration of SRM basically requires a complete re-configure. You should first remove recovery plans on the existing DR site. Next you will want to remove protection groups followed by breaking the site pairing inside SRM.
At this point you can do the IP configuration changes to the DR site. Once you have completed these changes you will have to do a repair install of SRM on the DR site giving it the new IP address for the vCenter server on the DR site.
Finally you will have to go through the site pairing process, creation of protection groups, inventory mapping and finally creation of recovery plans. After all of this do a test failover and all should be well.
ASKER
I do not think a repair installtion is appropriate.