VMware Cloud Foundation 4.x Management Domain Implementation with VLAN-Backed Networks

Products

• VMware Cloud Foundation

Issue/Introduction

By default, the VMware Validated Design Solution Extensions for VMware Cloud Foundation use NSX-T backed virtual network segments and dynamic routing using the Border Gateway Protocol (BGP), when deploying the vRealize Suite components.

This procedure outlines how to deploy the vRealize Suite components without dynamic routing and BGP. The attached documentation provides step-by-step instructions required to deploy the vRealize Suite using VLAN backed networks in a VMware Cloud Foundation instance.

Symptoms:

You are unable to deploy vRealize Suite Lifecycle Manager to a VLAN backed network using VMware Cloud Foundation SDDC Manager.

Environment

VMware Cloud Foundation 4.1
VMware Cloud Foundation 4.2.x

Resolution

NOTE: This is not applicable from VCF 4.3 and above.
Please do not run this script on SDDC Manager 4.3 and above.

Greenfield VMware Cloud Foundation 4.x Deployment

1. Download the attached config.ini and avn-ingestion.py and copy to SDDC Manager using an SCP utility such as WinSCP.
2. Follow the steps in the attached PDF to create and then ingest the required VLAN backed networks to the SDDC Manager inventory to support deploying the vRealize Suite & Workspace ONE Access to VLAN backed networks.

Upgrading to VMware Cloud Foundation 4.x from VMware Cloud Foundation 4.0.x

1. Download the attached config.ini and avn-ingestion.py and copy to SDDC Manager using an SCP utility such as WinSCP.
2. Follow the steps in the attached PDF to ingest the required VLAN backed networks to the SDDC Manager inventory to support deploying the vRealize Suite & Workspace ONE Access to VLAN backed networks. Refer to the section Ingest VLAN Backed Network Details to SDDC Manager.

Updates to avn-ingestion-v2.py Script

• Config file must be specified using the --config option.
• A new option --dryrun has been introduced which allows for verification of the config.ini file and the commands executed on the SDDC Manager without committing changes.
• A new option --erase has been introduced which cleans up the AVN data from SDDC Manager. 
• The --dryrun option can be used with both --config and --erase options.
• The script now generates a log file by the name avn-ingestion.log which records all the details of the script execution and is stored in the same location where the script resides.

Additional Information

Impact/Risks:
Prior to proceeding, it is recommended to take an offline snapshot of SDDC Manager.  Please remember to remove the snapshot within ~72hours if the procedure is successful.