epmmis
asked on
Change Network vSphere cluster is in
Our vSphere DR cluster is being moved into a new network. I am looking for advice as to the best sequence to make this happen. The DR site consists of 3 x ESX 4.0 servers, 1 vCenter server and 4 active VMs. Each server has 4 network cables connected to it for a total of 12 network cables dedicated to the cluster. There is only 1 distributed vSwitch used by all 3 ESX servers.
My tentative sequence is
1. vMotion VMs off one ESX server.
2. Put server into maintenance mode.
3. Via the vCenter server change the ESX server's IP address to new network. (vConsole will loose connection)
4. Replace old network Cat 5 cables with new network Cat 5 cables
5. Reestablish vCenter connection to ESX server.
6. Continue with 2nd and 3rd ESX server.
7. Change vCenter server's IP address to new network.
8. Change active VM's IP address to new network.
9. Rename distributed switch. The old network is part of the vSwitch's name.
10. Update DNS.
My tentative sequence is
1. vMotion VMs off one ESX server.
2. Put server into maintenance mode.
3. Via the vCenter server change the ESX server's IP address to new network. (vConsole will loose connection)
4. Replace old network Cat 5 cables with new network Cat 5 cables
5. Reestablish vCenter connection to ESX server.
6. Continue with 2nd and 3rd ESX server.
7. Change vCenter server's IP address to new network.
8. Change active VM's IP address to new network.
9. Rename distributed switch. The old network is part of the vSwitch's name.
10. Update DNS.
Danny McDaniel
I think you will be better off if you plan on removing each host from vCenter. Even though you may have registered the hosts in VC by their name, IP addresses get cached on the hosts and put into the VC's database. The hosts will go into a disconnected state when you change the VC's IP either way and you'll have to re-authenticate the hosts with the root account.
Hi
I think that is a good plan. But using what danm66 as stated, will have no problem on your plan. And you can bypass some issues that you may encounter after the IP change.
The only think that I will add is a new backup Console with a new ip for the new Network.
If the new Network and the old Network can communicate with each other, you not lose the connection from the console(but you will need to connect trough this new IP)
Hope this can help
Jail
I think that is a good plan. But using what danm66 as stated, will have no problem on your plan. And you can bypass some issues that you may encounter after the IP change.
The only think that I will add is a new backup Console with a new ip for the new Network.
If the new Network and the old Network can communicate with each other, you not lose the connection from the console(but you will need to connect trough this new IP)
Hope this can help
Jail
ASKER
I should modify the plan as follows?
3. Via the vCenter server change the ESX server's IP address to new network. (vConsole will loose connection)
4. Delete the host from DR cluster in vCenter Server.
5. Replace network cables.
6. Update DNS.
7. Add the host back into the DR cluster in the vCenter Server by its host name.
Questions -
1. Should the host be rebooted after changing the IP address and before adding it back into the cluster?
2. BestWay - I do not understand your suggestion about a backup console with a new IP. Can the backup console be on the DR vCenter server? If the vCenter server can route to the new IP, is a backup console needed?
3. How does one make a backup console?
Excellent suggestions. I am most grateful.
3. Via the vCenter server change the ESX server's IP address to new network. (vConsole will loose connection)
4. Delete the host from DR cluster in vCenter Server.
5. Replace network cables.
6. Update DNS.
7. Add the host back into the DR cluster in the vCenter Server by its host name.
Questions -
1. Should the host be rebooted after changing the IP address and before adding it back into the cluster?
2. BestWay - I do not understand your suggestion about a backup console with a new IP. Can the backup console be on the DR vCenter server? If the vCenter server can route to the new IP, is a backup console needed?
3. How does one make a backup console?
Excellent suggestions. I am most grateful.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The ESX server's web interface is disabled. I would then change the IP address from the command line.
ASKER
Thanks