[VMC on AWS]Unable to import VM(s) while using Advanced Cross vCenter vMotion
search cancel

[VMC on AWS]Unable to import VM(s) while using Advanced Cross vCenter vMotion

book

Article ID: 314087

calendar_today

Updated On:

Products

VMware Cloud on AWS

Issue/Introduction

To troubleshoot this scenario and to be able to import VM(s) into vcenter

Symptoms:
  • While trying to import one or more VM(s), received the following error :
               "  vCenter does not support hosts of this type (). "
image.png
 


Cause

One of the following may apply:-
  1. Different versions of ESXI present on both hosts.
  2. Absence of a MGW firewall between on-prem and cloud vcenter.
  3. Absence of vmotion license in vcenter.

Resolution

One of the following may apply:-
  1. If different versions of ESXI present on both hosts: 
           It would be best to have the same version of ESXi on both hosts in order to avoid compatibility issues. 

       2.Absence of a MGW firewall between on-prem and cloud vcenter: 

          To enable traffic between an on-premise and cloud vcenter, create a MGW firewall rule between them. 
 
       3.Absence of vmotion license in vcenter: 

         To make sure ESXi is licensed for vMotion, you could check the license status:

         Log into vCenter via vSphere client > select ESXi host > click Configuration > click Licensed Features > check whether vMotion is supported. [Note: This step applies to on-prem]


Additional Information

https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-vcenter-esxi-management/GUID-ED703E35-269C-48E0-A34D-CCBB26BFD93E.html

Impact/Risks:
Customer will be unable to import one or more VMs into the vcenter