Once Cluster preparation is completed, It time to configure the VXLAN. Virtual Extensible LAN (VXLAN) enables you to create a logical network for your virtual machines across different networks. You can create a layer 2 network on top of your layer 3 networks. VXLAN transport networks deploy a VMkernel interface for VXLAN on each host. This is the interface that will encapsulate network segments packets if it needs to reach a guest on another host. By encapsulating via a VMkernel interface the workload is totally unaware of this process occurring. As far as the workload is concerned the two guests are adjacent on the same segment when infact they could be spanning many L3 boundaries.
To configure the VXLAN, Login to the Web Client > Networking & Security > Installation > Host Preparation-> Configure . A wizard will ask for VXLAN networking configuration details. This will create a new VMkernel port on each host in the cluster as the VXLAN Tunnel Endpoint (VTEP).
Provide the below options to configure the VTEP VMkernel Port:
- Switch – Select the DvSwitch from the drop-down for attaching the new VXLAN VMkernel interface.
- VLAN – Enter the VLAN ID to use for VXLAN VMkernel interface. Enter “0″ if you’re not using a VLAN, which will pass along untagged traffic.
- MTU – The recommended minimum value of MTU is 1600, which allows for the overhead incurred by VXLAN encapsulation. It must be greater than 1550 and the underlying network must support the increased value. Ensure your distributed vSwitch (DSwitch) set MTU size more than 1600.
- VMKNic IP Addressing – You can specify either IP Pool or DHCP for IP addressing. I don’t have DHCP in my environment. Select “New IP Pool” to create a new one same as we created during NSX controller deployment. I have used a IP pool called “ VXLAN Pool”
Enter the IP Pool Name, Gateway, Prefix Length, Primary DNS,DNS Suffix and Static IP Pool range for this New IP Pool and click on Ok to create the New IP Pool.
- VMKNic Teaming Policy – This option is define the temaing policy used for bonding the vmnics (physical NICs) for use with the VTEP port group. I have left with the default Teaming policy “Static EtherChannel”
- VTEP – I left the default one and it is not even allowed to configure ,if you choose “Static EtherChannel” as your Teaming policy.
Click on Ok to create the new VXLAN vmkernel interface in the ESXi hosts.
Once the VXLAN is configured, You will be able to see the status of the VXLAN is changed to “Enabled” for that particular cluster.
As discussed in previous steps, Configure the VXLAN for other clusters in your vCenter.
You can notice the VXLAN VMkernel interface is created for the ESXi hosts in the Compute clusters. It assigns the IP address for the VXLAN VMKernel interface from the IP Pool which we have created earlier.
You can verify the same from the Networking & Security > Installation > Logical Network Preparation>VXLAN Transport.
We are done with configuring VXLAN for ESXi hosts. We will configure Segment ID and transport Zones in the upcoming posts. I hope this is informative for you. Thanks for Reading!!!. Be Social and share it in social media, if you feel worth sharing it.