Worked this through?
The configuration of ESX Server host networking and name resolution, as well as the networking infrastructure external to ESX Server hosts (switches, routers, and firewalls) is critical to optimizing VMware HA setup. When you configure these components, use the following best practices to improve VMware HA performance.
If your switches support the PortFast (or an equivalent) setting, enable it on the physical network switches that connect servers. This helps avoid spanning tree isolation events. For more information on this option, see the documentation provided by your networking switch vendor.
Make sure that the following firewall ports are open for communication by the service console for all ESX Server 3 hosts:
Incoming port: TCP/UDP 8042-8045
Outgoing port: TCP/UDP 2050-2250
For better heartbeat reliability, configure end-to-end dual network paths between servers for service console networking. Configure shorter network paths between the servers in a cluster. Routes with too many hops can cause networking packet delays for heartbeats.
Disable VMware HA (using VirtualCenter, clear the Enable VMware HA checkbox in the Settings dialog box for the cluster) when you perform any networking maintenance that might disable all heartbeat paths between hosts.
Use DNS for name resolution rather than the error-prone method of manually editing the local /etc/hosts file on ESX Server hosts. If you do edit /etc/hosts, you must include both long and short names.
Use consistent port names on VLANs for public networks. Port names are used to reconfigure access to the network by virtual machines. If you use inconsistent names between the original server and the failover server, virtual machines are disconnected from their networks after failover.
Use valid virtual machine network labels on all servers in a VMware HA cluster. Virtual machines use these labels to reestablish network connectivity upon restart.
AWo
vExpert 2009/10/11
[:o]===[o:] [: ]o=o[ :]
= Save forests! rent firewood! =
