Hi,
we have two datacenter locations that use different L3 networks.
We would like to be able to migrate VMs from one DC to the other.
Networks:
sideA-mgmt (e.g. 10.10.1.0/24)
sideA-vmotion (e.g. 10.10.2.0/24)
sideB-mgmt (e.g. 10.20.1.0/24)
sideB-vmotion (e.g. 10.20.2.0/24)
My first idea would be to use one combined vmkernel adapter for vmotion (hot) and provisioning (cold migration) traffic and set a route on both datacenter sides.
I tested this solution and it worked but then I found this ~7 year old KB article that suggests routes for vmotion (and probably provisioning too?) are not official supported on default stack: https://kb.vmware.com/s/article/2108823
Is this still the case and I have to use own stacks for routeablity of vMotion/prov?
My backup idea would be to create two vmkernel adapter one for vmotion and one for provisioning with their own stacks and then just put a default route into these own stacks / routing tables.
(I would then need two IP addresses from the respective vMotion network, one for vmotion and one for prov. The gateway remains the same. Have not yet checked whether this makes problems with the routing table assignment. In the worst case I would need a third network per location.)
Are both ways supported or only the own stack variant?
Are routes ESXi (minor/major) upgrade safe?
Regards,
Robért