If you did not utilize a DHCP server during the deployment of vCloud Foundation, one of the issues you will face is that the VRLCM VM deployment fails in the x-region network. This is because the SDDC manager is not able to reach the VRLCM VM since the Host Overlay tunnel is not established.
The parameter sheet for Host-overlay is "N/A", and this is not the case for Edge-TEP parameters. Although, the sheet does not contain any information to add static Host TEP pools we had to manually configure the IP pools as a solution.
Thanks to my colleague Faisal who was able to assist in assigning the TEP IP's that are from the NSX-T Host Overlay VLAN range using the below procedure.
a) Login to NSX-T dashboard and create a new IP static pool for the host-tep pool.
b) Assign this
newly created pool under the transport-node profile instead of DHCP.
c) Once done,
configure the NSX for the vcenter managed vsphere cluster to assign the
host-tep interfaces from the static pool.
1) Once the vCloud foundation is deployed on the NSX-T admin console, browse to Systems => Host Transport Nodes => Select your vCenter from the "Managed by" drop down and expand your vcenter and select the Management cluster. You will notice that the NSX VTEPs will be assigned a 169.254.0.0/16 IP address as shown below which is a link-local IPv4 address.These TEP IP Addresses need be to set to a range as per the VCF Deployment parameter sheet NSX-T Host Overlay network.
2) To create the IP pool,select "Networking" => " IP Address Pools" => "ADD IP ADDRESS POOL".
3) In the New Windows, select " ADD SUBNET" => IP Ranges.4) Define your IP Ranges that you would like to utilize along with the other details as per your infrastructure and click Apply. Once done, click on Save in the next screen to save the IP Pool you created.
9) Once the IPs are assigned, the SDDC manager will be able to reach the VRLCM VM and the deployment will succeed.