We have 4 esxi5 hosts and we have been asked to modify the SC ip's from a 10.x to a 192.x and no routing exists between these subnets. The vmotion subnet is separate and will not change.
My plan
vmotion all VM's off host one. Login to the SC, remove the host from the cluster and change its ip to the new range. Reboot thwe host and re add it to the cluster. I would then repeat this process by vmotioning the the VM's on host 2 to the new host1 and then changing the ip on host 2...
Is the SC ip required to be reachable to allow vmotion? Is there some other flaw in this plan that would result in downtime to any of the VM's or affect HA in some way? Should I enable routing between the 10.x and the 192.x subnets for the duration of this work?
thanks
stuart