ESXi 6.0u2 - When attempting vMotion, the dialog window does not show the target host

[tigaratus]

I have seven ESXi 6.0u2 hosts.
ESX09 is just recently added.
I have checked, (1) the ESX09 has been added to the switches, (2) all datastores have been presented, and (3) the cluster EVC is set at "Ivy Bridge".

However, when attempting to vMotion a powered-off VM, I am not able to select ESX09 host.

Is there any other settings I should check?

Thank you

[VMARA]

Check the vMotion enabled in the virtual switches. what are the switches that you are using. Standard Switches or Distributed switches?

[RAJ_RAJ]

Hi ,

Please verify below Prerequisites , you will be able to identify the issue solve it .

■

Verify that you have at least two ESXi hosts that are licensed for vMotion or are in evaluation mode.

■

Verify that you have running instances of vCenter Server and the vSphere Web Client.

■

Verify that hosts have access to shared storage of a supported type, such as Fibre Channel, iSCSI, or NAS.

■

Verify that the source and destination hosts have compatible CPUs.

■

Verify that hosts have access to the same physical networks.

■

Verify that you have at least one active Gigabit Ethernet adapter on each host.

■

Virtual machine files must be on shared storage visible by the hosts.

■

Virtual machines must run a supported operating system.

■

Virtual machines must not have a connection to a virtual media device with a mounted local image.

■

Virtual machines must not have a connection to an internal vSwitch that is not connected to a physical network.

■

Virtual machines must have access to the same subnets.

■

Virtual machines must not have CPU affinity configured

[tigaratus]

1) Using distributed switch.

2) ping test confirmed connectivity of the vMotion network.

3) Configuration as below.

[VMARA]

Ping seems working I would like to see the vmkping status as well. Try this: 

Login to a different host from ssh and try "vmkping <target_host_vmk_nic_ip>"

[Stanley_]

what is the warning on each host about?

and is vMotion enabled/set on vmk1 ? (it is not visible on pictures)

[tigaratus]

1) vmkping successful

2) vMotion adapter already configured

[RajeevVCP4]

1. Put the sever on maintenance mode

2. Disconnect from Network

3. Remove from cluster

4. then add back in cluster.