Expansion of Management vSphere Cluster is failing on VLAN based AVN

Products

• VMware Cloud Foundation

Issue/Introduction

Symptoms:

• Any expansion operations (Add Host/vSAN Stretch Cluster/Expand vSAN Stretch Cluster) executed in the Management Workload Domain fails with following error.  "Attach VLAN Transport Zone to Host Transport Nodes".
   
• The environment's network topology is VLAN-based AVN configured during VCF 3.x or 4.x Migration with MR1 and MR2 releases and/or ingested AVN as suggested in following article VMware Cloud Foundation 4.x Management Domain Implementation with VLAN-Backed Networks
  
  
• Following snippets are observed in /var/log/vmware/vcf/domainmanager/domainmanager.log

YYYY-MM-DDT<Time> ERROR [vcf_dm,9d0a4a46cfca44fa,0d6f] [c.v.v.c.f.p.n.a.NsxtAddHostVlanHeader,dm-exec-10] Error occurred while generating input for add hosts in NSX-T environment
       
java.lang.NullPointerException: null

YYYY-MM-DDT<Time> ERROR [vcf_dm,9d0a4a46cfca44fa,0d6f] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-10] [GL0M7C]                         

ERROR_OCCURRED_WHILE_GENERATING_INPUT Error occurred while generating input for add hosts in nsxt environment

com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Error occurred while generating input for add hosts in the NSX-T environment

Caused by: java.lang.NullPointerException: null at com.vmware.vcf.common.fsm.plugins.nsxt.action.NsxtAddHostVlanHeader.execute(NsxtAddHostVlanHeader.java:218)
... 18 common frames omitted

YYYY-MM-DDT<Time> DEBUG [vcf_dm,9d0a4a46cfca44fa,e5d3] [c.v.e.s.c.s.a.l.LockingServiceAdapterImpl,dm-exec-12] Execution name ADD_HOST_WORKFLOW,   execution ID 99ad7352-####-####-#
###-########06e, resource type DEPLOYMENT, resource ID null.

Environment

VMware Cloud Foundation 5.x
VMware Cloud Foundation 4.x
VMware Cloud Foundation 3.x

Cause

The association between the Management vSphere Cluster and the VLAN Transport Zone in the SDDC Manager Database is not populated.

Resolution

This issue is resolved in VCF 4.4. but in some rare circumstance's it can be presented in VCF 5.2

 

If you encounter this behaviour please reach to Broadcom Technical Support for further assistance.