1/4
Ahm source destination question

EduardoOliveira Lv1  Posted 2026-Oct-02 04:31

Hello team,

I have a customer with multiple branch offices, all managed by a single vCenter located at the headquarters.

The customer plans to deploy a Sangfor host in each branch office and migrate the VMs from the local VMware hosts to the Sangfor host at each site.

They want to use AHM (Agentless Host Migration) for the migration.

Question: During the migration, will the data traffic flow directly from the VMware host to the Sangfor host within the branch office, or will it have to pass through the vCenter at headquarters?

This matters because it determines whether the WAN link between the branches and HQ will be a bottleneck.

Newbie901019 has solved this question and earned 20 coins.

Posting a reply earns you 2 coins. An accepted reply earns you 20 coins and another 10 coins for replying within 10 minutes. (Expired) What is Coin?

Enter your mobile phone number and company name for better service. Go

No, the heavy VM disk migration traffic will NOT pass through the vCenter at Headquarters.
During an aHM (Agentless Host Migration) task, the data traffic flows directly from the local VMware ESXi host to the local Sangfor HCI host within the branch office's Local Area Network (LAN). The WAN link between the branch and HQ will only carry a negligible amount of management control traffic.
How Traffic is Split During aHM Migration
Sangfor aHM separates the migration process into two distinct traffic planes:
  • Control / Management Plane (WAN Traffic – Minimal)

    • Path: Local Sangfor Host  Headquarters vCenter Server.
    • Port: TCP 443 (vSphere Web API).
    • Role: Sangfor HCI communicates with vCenter at HQ solely to authenticate, retrieve VM inventory, issue task instructions, and trigger VMware snapshots (VADP).
    • WAN Impact: Extremely low bandwidth consumption (kilobytes per second of API metadata).


  • Data Plane / Disk Transfer (Branch LAN Traffic – Direct)

    • Path: Local VMware ESXi Host  Local Sangfor HCI Host.
    • Port: TCP 902 (NFC / VMware vSphere VDDK Data Stream).
    • Role: Once vCenter authorizes the task, the local Sangfor HCI host reads the VM's .vmdk disk data blocks directly from the local ESXi host's NFC service over TCP Port 902.
    • WAN Impact: Zero WAN usage. All heavy gigabit data streaming remains local to the branch switch infrastructure.

Requirements for Branch Deployments
  • Firewall Ports to Open:

    • Sangfor Branch Host  HQ vCenter: Open TCP Port 443 over the WAN.
    • Sangfor Branch Host  Local ESXi Host: Open TCP Port 902 over the local Branch LAN.

  • DNS Resolution: If your branch ESXi hosts are added to vCenter using FQDNs/hostnames rather than IP addresses, ensure the local Sangfor HCI node can resolve those ESXi hostnames locally.
  • aHM Concurrency Limits: aHM supports up to 2 concurrent VM migrations per task. Since each branch has its own local Sangfor host/cluster, migrations at different branch offices can run in parallel without impacting each other's performance or saturating the HQ network.
  • aHM License: VMware managed migration (AHM) requires a valid aHM license on the HCI platform.


Is this answer helpful?
Humayun Ahmed Lv4  Posted 2026-Oct-05 13:19
  
Yes. For aHM (Agentless Host Migration), the bulk VM data traffic is intended to flow directly between the Sangfor platform and the VMware ESXi host, not through the vCenter server at HQ.

Deployment Guide:
https://www.sangfor.com/sites/de ... lution-part-2-1.pdf
Prosi Lv4  Posted 2026-Oct-02 18:13
  
HI, When migrating from VMware to Sangfor HCI, there is a fundamental distinction between the control plane and the actual data transfer path (or the VM itself).

If the migration is initiated or managed via vCenter at the headquarters (HQ), this does not mean the VM data must pass through vCenter. In a typical architecture, vCenter provides management or control information, whereas migration data can flow directly between the VMware ESXi host and the Sangfor HCI host or storage, depending on the migration method and network design employed.
Newbie380273 Lv2  Posted 2026-Oct-02 15:01
  
Hi,

No, the heavy VM data will NOT go through vCenter at HQ.

aHM separates traffic into 2 planes:

**1. Control Plane (WAN - Very Low):**
Sangfor HCI Host at Branch <-> vCenter at HQ over TCP 443 (vSphere API). Only to get VM inventory, auth, and trigger migration task. Bandwidth is minimal, just KBs.

**2. Data Plane (LAN - Direct & Heavy):**
Local VMware ESXi Host -> Local Sangfor HCI Host over TCP 902 (VDDK / NFC). The actual vmdk data block transfer happens locally within the branch office LAN switch.

So your WAN link will NOT be a bottleneck. The heavy data stays local to branch. You only need to open:
- Branch HCI to HQ vCenter: TCP 443 over WAN
- Branch ESXi to Branch HCI: TCP 902 over LAN

Make sure DNS resolution works if ESXi hosts are added with FQDN, and you have valid aHM license on HCI.

You can run multiple branch migrations in parallel because data is local.

Thanks.
Newbie006434 Lv2  Posted 2026-Oct-02 12:38
  


> Hi, in aRM Agentless mode the vCenter at HQ is only for management and API calls. The real migration data plane is direct between the source ESXi host and the target Sangfor HCI host in the same branch. So the traffic will stay local inside the branch LAN and will not hairpin through HQ. Your WAN link is safe, just ensure good 10G connectivity between the two hosts locally for faster migration.
Newbie900829 Lv2  Posted 2026-Oct-02 12:35
  
Great question! For aRM Agentless migration, the actual data traffic flows directly from the source VMware host to the destination Sangfor host within the same branch office LAN. It does NOT need to go through the vCenter at HQ. The vCenter is only used for control plane and orchestration to initiate the migration, but the heavy data transfer is direct host-to-host. So your WAN link will not become a bottleneck for this. Just make sure both hosts have L2 connectivity locally for the migration network.
Humayun Ahmed Lv4  Posted 2026-Oct-02 12:03
  
Yes — the bulk migration data does not need to pass through the vCenter server itself.

Sangfor's current documentation distinguishes the management/control connection from the VM data-transfer path:

Sangfor HCI/SCP → vCenter: TCP 443 for management commands.
Sangfor HCI/SCP → VMware ESXi: TCP 902 for VM data transfer.

So for your topology:
  HQ
        ┌──────────────────┐
        │ VMware vCenter   │
        └────────┬─────────┘
                 │
              WAN │ 443
                 │
      ┌──────────┴──────────┐
      │                     │
   Branch A              Branch B
┌─────────────┐       ┌─────────────┐
│ VMware ESXi │       │ VMware ESXi │
│     VM      │       │     VM      │
└──────┬──────┘       └──────┬──────┘
       │                      │
       │  VM DATA             │ VM DATA
       │  TCP 902             │ TCP 902
       ▼                      ▼
┌─────────────┐       ┌─────────────┐
│ Sangfor HCI │       │ Sangfor HCI │
└─────────────┘       └─────────────┘

https://www.sangfor.com/blog/clo ... ta-migration-online

I Can Help:

Change

Board Leaders

George ...

Weekly Sharers

George ...

Weekly Questioners