VCF Installer fails validation when LACP is configured

Products

• VMware NSX
• VMware vSphere ESXi

Issue/Introduction

VCF Installer validation fails if LACP is configured on the vDS for Management and NSX is configured to use a different vDS. The following error message appears:
LAG/LACP enabled DVS, hosting management networks, in Management Domain, should be configured with NSX. Remediation: LAG/LACP enabled DVS, hosting management networks, in Management Domain, should be configured with NSX.

Environment

VCF 9.0.0 and 9.0.1

Resolution

Option 1

• The Management vDS will also need to be configured for NSX. This involves adding additional NSX configuration to the JSON specification file for the Management vDS.
  • Here is the additional content with sample values: "nsxtSwitchConfig" to be added to the JSON specification file:
    
    { "transportZones": [ { "transportType": "VLAN", "name": "###-###-vlan-tz01" } ] }, "nsxTeamings": [ { "policy": "FAILOVER_ORDER", "activeUplinks": [ "lag" ], "standByUplinks": [] } ],
    
    
    
    
  • This additional configuration will create a VLAN transport zone and add the vDS with Management traffic to the transport node profile.

Option 2

• Use the same vDS for NSX and Management traffic when LACP is configured.

Option 3

• Move the network to another DVS with no LAG.