When you are planning for a vCF deployment, you need lot and lot of IP’s and DNS records.
In my environment I have an AD integrated DNS running on MS 2012 R2.
If you are only planning on deploying the Management Workload Domain in your environment you only need to create the forward and reverse lookup records for Management Workload Domain. If Virtual Infrastructure Workload Domain will be introduced in future then you need to plan the DNS records accordingly.
Note: Please see this article for comprehensive list of DNS requirement for vCF deployment.
Below is the list of DNS records that I created in my environment:
|Workload Domain||Hostname||IP Address|
|NA||vcf (cloud builder appliance)||172.20.31.100|
Note: If you are planning to deploy vRealize and Horizon infrastructure using vCF, you need to create additional records as per product DNS requirement.
IP pools are needed to configure vMotion network, vSAN network etc during SDDC bring up process. Typically you need to have pool of IP’s reserved for following:
- vMotion pool for Esxi hosts in Management Domain and VI Workload Domain.
- vSAN pool for Esxi hosts in Management Domain and VI Workload Domain.
- NSX controller pool in Management Domain and VI Workload Domain.
Here is how the IP pools looks like in my environment:
|Pool Type||Pool Start Address||Pool End Address|
|NSX-CTLR Pool (Mgmt)||172.20.31.114||172.20.31.116|
|NSX-CTLR Pool (WLD)||172.20.31.175||172.20.31.177|
Note: Ideally its better to have your mgmt, vMotion, vSAN networks backed by different VLAN’s. In my lab I had some issues when trying to use IP’s from different VLAN’s, so I put everything on same L2 network.
I hope you enjoyed reading this post. Feel free to share this on social media if it is worth sharing