9.1 VCF Installer fails on "vMotion Network Connectivity" check and/or "vSAN Network Connectivity"

Products

• VMware SDDC Manager / VCF Installer

Issue/Introduction

Gateway 192.168.x.x for VMOTION network is not responding from host.example.com

ESX Host 'host.example.com' -> '192.168.x.x' VLAN '####' with MTU 900 fail to vmkping


A similar error is observed in the VCF Installer's domainmanager.log

/var/log/vmware/vcf/domainmanager/domainmanager.log
======================================================================================
2026-04-06T17:58:12.788+0000 DEBUG [vcf_dm,0000000000000000,0000] [c.v.e.s.c.v.util.ResponseUtil,dm-exec-680]  Build validation response: {"errorCode":"NOT_RESPONDING_GATEWAY_FROM.warning","arguments":["192.168.x.x","VMOTION","host.example"],"context":{"severity":"WARNING","bundleName":"com.vmware.evo.sddc.common.validation.er
rors.messages"},"message":"Gateway 192.168.x.x for VMOTION network is not responding from host.example","remediationMessage":"Verify the gateway is reachable and properly configured on the network"}
2026-04-06T17:58:12.790+0000 DEBUG [vcf_dm,69d3f3fe3afbbc14de93c54de91dbb6b,49a8] [c.v.e.s.c.v.util.ResponseUtil,dm-exec-679]  Build validation response: {"errorCode":"SINGLE_PORTGROUP_VALIDATIONS.error","arguments":["VMOTION"],"context":{"severity":"ERROR","bundleName":"com.vmware.evo.sddc.common.validation.errors.messages","validation.taskId"
:"0a1203fd-9d5e-12f5-819d-63eaab640188"},"message":"Failed to validate connectivity of VMOTION network","remediationMessage":"Check input parameters for VMOTION network andverify hosts have connectivity on this network"}

Environment

VMware Cloud Foundation 9.0

VMware Cloud Foundation 9.1

Cause

The VCF Installer is not honoring the standby uplink and if the active vmnic is already in use by the VSS(vSwitch0), then the validation will fail.

Resolution

Workaround 1: Edit the domainmanager service application.properties file.

• Take a snapshot of SDDC Manager VM

• SSH to the SDDC Manager with the 'vcf' user and then type 'su -'.

•  Update the application properties file of the domain manager service:
  
  echo "validation.disable.network.connectivity.check=true" >> /etc/vmware/vcf/domainmanager/application.properties
  
  
• Restart the Domain Manager service:
  
  systemctl restart domainmanager
  
  
• Re-run the validation checks

 

Workaround 2: Update deployment json and set both vmnics to ACTIVE/ACTIVE.