Mobility Group Creation fails with error "Not all networks are configured"

Products

• VMware HCX

Issue/Introduction

• You are unable to migrate VMs attached to certain vSphere port groups.
• The VMs are powered-on but their NIC is in the disconnected state.
• The selected VMs only have 1 network adapter assigned and configured but the HCX Mobility Group UI shows 2, one of which has no network label.
• This behavior is also seen when utilizing HCX CMDLETs bundled in PowerCli V13.3 to create mobility groups. 
• When proceeding with Mobility Group validation you receive an error: "Not all networks are configured"
  
  
  
  
• The following lines can be seen from HCX-MGR logfile at /common/logs/admin/web.log :
  

  2025-05-28 17:18:27.317 UTC [https-jsse-nio-127.0.0.1-8443-exec-1, Ent: HybridityAdmin, , TxId: TxId: ########-####-####-####-############] WARN c.v.v.h.a.m.c.MobilityIntentUtil- Value for networkParams.srcNetworkId can not be empty for migrationId:

   

• When using HCX 4.11 PowerShell cmdlets, RAV migrations fail during the vMotion phase with the error "vMotion failed. Could not do mapping networks for the source network mac ##:##:##:##.##.##"
  • NetworkMappings that are created and validated in PowerShell will fail during the vMotion phase of the RAV migration. Does not affect bulk migration type when initiated via PowerShell.
    
    
• When viewing the error presented on the Power-Shell created Mobility-Group via the UI shows:
  

Environment

HCX 4.11

Cause

The HCX UI is incorrectly computing the network parameters on DVS that have been exported then re-imported, causing it to mistakenly reject migrations of disconnected VMs.

Resolution

• This issue is resolved in HCX 4.11.1
• If using PowerCli V13.3, the below workaround still applies. PCLI 13.3 is still susceptible to this issue. This KB will be updated with the PCLI version this issue is fixed in. 

Workaround:

• Use the legacy UI view in HCX when creating mobility groups for VMs whose networks are impacted by this issue: 
• For PowerCli users experiencing this issue, please open the created mobility group using the legacy UI.