Hi,
I wonder if anyone could shine any light on why vmotion fails to occur between an ESXi host that has just been restarted, in order to test HA. I have the following setup:
3 x ESXi5 DL360 G7s with two 4 way NICs
VSphere Vcenter 5
1 x Cluster configured for HA DRS
2 x Procurve 2910-24G
The switches are not connected to each other.
Both switches are configured as such:
All ports are untagged. NO STP, no routing
Each hosts vMotion vSwitch is connected to both switches by 1 x 1Gb nic
I have configured a vswitch on each host for vMotion. There are two vmkernel ports with two ip addresses in the same subnet. There are two vmnics attached to the vSwitch. On each port, one Vmic is set to be active whilst the other is set to unused. I have enabled jumbo frames both on the vSwitch and the 2910 switches. A vlan has been configured on both 2910 swicthes for vmotion with jumbo frames and traffic set to ‘untagged’. I can successfully vmkping all vmotion ip’s on all ESXi hosts. However, when I test HA by shutting down an ESXi host, when I restart the ESXi host I am unable to vmotion to that ESXi host. When I test vmkping I find that the restarted host can only vmkping itself and no other host can vmkping it. The attempted vmotion fails on 9% and errors with the source host cannot connect to the destination host. If I restart both the 2910 switches I can then carry out a vMotion and the vmkping is successful.
Please help?
Thanks