Deployment Guide

22 VCF on VxRail Multirack Deployment using BGP EVPN
5 Planning and preparation
Before creating the IP underlay that drives the SDDC, it is essential to plan out the networks, IP subnets, and
external services required. Also, planning of the prerequisites on all required switching hardware is
recommended.
5.1 VLAN IDs and IP subnets
VCF on VxRail requires that specific VLAN IDs and IP subnets for the traffic types in the SDDC are defined
ahead of time. Table 2 shows the values that are used in this document. The NSX-V TEP VLAN is configured
to use the VLAN ID in each rack while the IP subnet is changed based on the rack. For example,
172.25.101.0/24 represents Rack 1 with a gateway of 172.25.101.253.
VLAN and IP subnet configuration
Cluster
VLAN function
VLAN ID
VNI
Subnet
Gateway
Workload cluster
ESXi Management
1641
1641
172.16.41.0/24
172.16.41.253
vSphere vMotion
1642
1642
172.16.42.0/24
172.16.42.253
vSAN
1643
1643
172.16.43.0/24
172.16.43.253
VxRail management
3939
3939
-
-
NSX-T TEPs
2500
-
172.25.n.0/24
172.25.n.253
NSX-T Uplink01
1647
-
172.16.47.0/24
-
NSX-T Uplink02
1648
-
172.16.48.0/24
-
Note: Use these VLAN IDs and IP subnets as samples. Configure the VLAN IDs and IP subnets according to
the environment.
5.2 External services
In this section, the following are discussed, along with the guidelines on placement:
• DNS
• NTP
• DHCP