Stretching cluster fails for host having different nic-VDS mapping
Article ID: 323369
Updated On:
Products
VMware Cloud Foundation
Issue/Introduction
Symptoms:
Trying to add a new host to the secondary fault domain using vmnic0 and vmnic1 fails. Primary fault domain hosts have been configured with vmnic0 and vmnic2.
Getting the following error messages:
Error: INVALID FAULT DOMAIN NAMES
Error: Failed to validate stretch spec [SPEC_ERROR_VMNIC_DOES_NOT_EXIST: ESXi host vmnicx does not contain specified pnic {a} (has {b})]
Trying to add a new host to the secondary fault domain using vmnic0 and vmnic1 fails. Primary fault domain hosts have been configured with vmnic0 and vmnic2.
Getting the following error messages:
Error: INVALID FAULT DOMAIN NAMES
Error: Failed to validate stretch spec [SPEC_ERROR_VMNIC_DOES_NOT_EXIST: ESXi host vmnicx does not contain specified pnic {a} (has {b})]
Environment
Vmware Cloud Foundation 4.5
Cause
In 4.5 additional validations were introduced to ensure cluster homogeneity hence nic-vds mapping of AZ1 and AZ2 should match
Resolution
Input spec should have same nic-vds mapping of AZ1 hosts.
Feedback
Yes
No
Powered by
