{{ $t('productDocDetail.guideClickSwitch') }}
{{ $t('productDocDetail.know') }}
{{ $t('productDocDetail.dontRemind') }}
6.11.3
{{sendMatomoQuery("Sangfor Cloud Platform (SCP)","aHM")}}

aHM

{{ $t('productDocDetail.updateTime') }}: 2025-12-17

Issue:

The VM migration has failed.

Resolution

Here are some common troubleshooting methods:

  1. Log in SCP, go to Resources Center, find the vCenter instance and verify that the IP address, username, password, and port are correct. (The user account must have administrator privileges.)
  2. Check whether the VMware version is compatible with the HCI version. Incompatibility may lead to failures in adding to management, migration, or backup. The HCI platform supports managing vCenter versions from 5.0 to 7.0.2. Support for managing vCenter 7.x begins from HCI version 6.8.0.
  3. Verify whether the Changed Block Tracking (CBT) feature is enabled for the VMware virtual machine. If not, attempt to enable it and restart the migration.
  4. Check the network connectivity between VMware and HCI. Ensure that port 902 (TCP) from HCI to the ESXi host and port 443 from HCI to vCenter are accessible.
  5. Determine if the vCenter was added using a domain name. If so, confirm that DNS is configured on HCI and that the HCI can resolve the corresponding domain name.
  6. Check whether the VMware virtual machine configuration supports migration.

If the VMware virtual machine has undergone snapshot rollback operations, it cannot be backed up or migrated to the HCI platform.

If the VMware virtual machine is configured with an SR-IOV passthrough network adapter, the customer must change the network adapter type to a different one before migration.

If the VMware virtual machine uses RDM (Raw Device Mapping) disks, it cannot be added to management or migrated.

If the VMware virtual machine uses disks in independent mode, it cannot be added to management or migrated.