During Advanced Cross vCenter vMotion (AXVM) validation step in the "3 Select a compute resource", vCenter shows a compatibility error: "vCenter does not support hosts of this type ()."
vpxd.log indicates the network error.
YYYY-MM-DDThh:mm:ss.sssZ warning vpxd[08291] ... Failed to connect; <io_obj p:0x00007fd360109ac8, h:-1, <TCP ':: : ####'>, <TCP '<VCENTER_IPADDRESS> : 443'>>, e: 104(Connection reset by peer), duration: 120007msec
YYYY-MM-DDThh:mm:ss.sssZ info vpxd[08291] ... Failed to shutdown socket; <io_obj p:0x00007fd360109ac8, h:-1, <TCP ':: : ####'>, <TCP '<VCENTER_IPADDRESS> : 443'>>, e: 9(shutdown: Bad file descriptor)
VMware vCenter Server 7U3
Network connection error between the source vCenter and the destination vCenter.
Resolve the network issue to ensure bidirectional connectivity between the source and destination vCenter servers over port 443.
When IPv4/IPv6 dual-stack is enabled on both vCenters, IPv6 traffic is prioritized. Verify that IPv6 communication is functioning correctly as well.
# Network connectivity check from source vCenter to destination vCenter
ssh root@<SOURCE_VCENTER>
curl -vkI https://<DESTINATION_VCENTER>:443
curl -6 -vkI https://<DESTINATION_VCENTER>:443 # Optional for dual-stack environment
# Network connectivity check from destination vCenter to source vCenter
ssh root@<DESTINATION_VCENTER>
curl -vkI https://<SOURCE_VCENTER>:443
curl -6 -vkI https://<SOURCE_VCENTER>:443 # Optional for dual-stack environment