Error: Input vmnics and vds mapping is not same as that of existing cluster host

Products

• VMware SDDC Manager

Issue/Introduction

• When adding a host to a cluster via SDDC Manager, an error message is received in the UI:
  
  Input vmnics and vds mapping is not same as that of existing cluster host
 
• Checking the domainmanager.log, the following event is logged:
  
  YYYY-MM-DDThh:mm:ss.079+0000 WARN  [vcf_dm,################################,####] [c.v.v.h.c.v.HostVmnicConfigurationValidator,dm-exec-7]  Input vmnics ({vmnic0=<VDS_NAME>, vmnic3=<VDS_NAME>, vmnic2=<VDS_NAME>, vmnic1=<VDS_NAME>}) and existing cluster host vmnics ({vmnic0=<VDS_NAME>, vmnic3=<VDS_NAME>}) don't match.
   

Environment

8.0

Cause

The hosts in the cluster are expected to be homogenous. However, the definition for the vmnics being passed as input parameters does not align with what is currently configured in the cluster.

Resolution

1. Update the input JSON such that the configuration matches what is expected of the cluster. You can use the domainmanager.log event as a reference:
   
   YYYY-MM-DDThh:mm:ss.079+0000 WARN  [vcf_dm,################################,####] [c.v.v.h.c.v.HostVmnicConfigurationValidator,dm-exec-7]  Input vmnics ({vmnic0=<VDS_NAME>, vmnic3=<VDS_NAME>, vmnic2=<VDS_NAME>, vmnic1=<VDS_NAME>}) and existing cluster host vmnics ({vmnic0=<VDS_NAME>, vmnic3=<VDS_NAME>}) don't match.
   
   You can see the input vmnics has vmnic0, vmnic3, vmnic2, vmnic1 defined, while the existing cluster host vmnics list only vmnic0 and vmnic3. In this scenario, the input JSON should define only vmnic0 and vmnic3.
   
   
2. Once the input parameters have been updated, retry the host addition via SDDC Manager.