Advanced Cross vCenter vMotion compatibility check timeout

[RMDAUS]

Hi there, I'm having an issue when trying to do a cross-migration of some VMs from a vCenter server running version 6.5 (Cluster) to another cluster running vCenter 7.0U2. The connection between the vCenters is established and firewall rules are in place. The issue is when the destination vCenter tries to check the resource compatibility which did not complete and gives a timeout as per the attached screenshot.

Does anyone had this issue before and could share some information? 

Thanks.

Attachment(s)

XVM-Error.pdf   34 KB 1 version

[Scott Vessey]

As your post needs moving to the correct area for the product used, I have reported it to the moderators.

 

[subashv4u]

Please check the VM version, which might not support in the newer cluster

[RegisMD]

Hi Subash, the VM hardware version on the source vCenter is v13 which is compatible with vCenter 7.0 according to the VMware compatibility matrix.  I am checking all networks between the two vCenters but everything seems fine. Not sure what else could be checked. 

I can see the below on the VCSA vpxd log:

2022-11-14T10:44:42.307+10:00 info vpxd[26295] [Originator@6876 sub=SoapAdapter.HTTPService.HttpConnection] HTTP Connection read failed while waiting for further requests [N7Vmacore4Http14HttpConnectionE:0x00007f78d076b620]: N7Vmacore16TimeoutExceptionE(Operation timed out: Stream: <io_obj p:0x00007f791491b618, h:-1, <TCP '127.0.0.1 : 8085'>, <TCP '127.0.0.1 : 58264'> FD Closed>, duration: 00:00:46.667792 (hh:mm:ss.us))
--> [context]zKq7AVECAQAAAJCaGQEMdnB4ZAAAcnY0bGlidm1hY29yZS5zbwAAAaopAAmfKgBDaS8AQVUqAJn/HwCipiAA4UEgAPKdIABGBTQBh38AbGlicHRocmVhZC5zby4wAAK/NQ9saWJjLnNvLjYA[/context]

[ptarnawski]

Hey  

 

Do you have an Enterprise Plus license?

Are both vCenters Server instances in Enhanced Linked Mode? 

Are both vCenters in the same Single Sign-On domain?

Are both time-synchronized with each other for correct vCenter Single Sign-On token verification?

For migration of compute resources only, both vCenter Server instances must be connected to the shared virtual machine storage.

Check the requirements of the port: 

• 8000 and 902 for vMotion and NFC between ESXi
• 902 for NFC on the ESXi host's Management subnet in case of Cross-vCenter vMotion, or cold migration (unless there is a dedicated subnet and vmkernel port)
• 443 between both vCenter Servers
• 443 between vCenter Server and the ESXi server (this is a requirement to have the ESXi host added to vCenter Servers)

 

My blog: AngryAdmin   Twitter: @AngrySysOps Youtube: @AngryAdmin (please subscribe)

 

[RMDAUS]

Thanks for your reply ptarnawski,

The issue was a Cisco ASA Firewall in between the two vCenters, it was blocking port 902 on the ESXi subnets.

All working now.

Cheers,

[ptarnawski]

Hey  ,

 

I was right pointing to port 902, please leave a Kudos