I have an internal restriction from our networking team that does not allow bridging between racks of the datacenter. A server in one rack needs to route to communicate with a server in another physical rack. Is it viable to setup a static route within the ESX4i kernel to route vMotion traffic to another vMotion subnet? Will this design cause any difficulties with DRS and/or HA?
Thanks in advance for any guidance on this issue.
•The source and destination VMware ESX servers must have a private VMware VMotion network on the same IP subnet and broadcast domain.
As far as I can remember, they cannot be on different subnets since its a broadcast based.
Guess all ESX servers are going into the same rack (unless they will let you run a seperate switch with no external connectivity (since that vlan never needs to go anywhere and no one else should ever get on it)
It will cause problems, yes. Thats a stupid restriction - would love to hear their justification for that!
--Matt
VCP, vExpert, Unix Geek
Cisco have developed a solution that is supported by VMWare - long distance vmotion.
See link.
http://www.networkworld.com/news/2009/090209-vmworld-cisco-vmotion.html
http://erikzandboer.wordpress.com/2009/09/03/long-distance-vmotion-a-fact/
Just realised - you have a local problem - ignore and i will go back to sleep .