Recently I had received several inquiries asking on how to configure nested ESXi (Nested Virtualization) to function in a VXLAN environment. I have written several articles in the past on configuring nested ESXi in a regular
vSphere and
vCloud Director environment, but with the use of a VXLAN backed network, there are a few additional steps that are required. These steps include additional configurations of the vCloud Network & Security Manager (previously known as vShield Manager) which ensures that both the required
promiscuous mode and
forged transmits are automatically enabled for the VXLAN virtual wires (vWires) as they are managed exclusive by the vCNS Manager.
In this article, I will walk you through the configurations that is required when using VXLAN in both a vSphere only environment as well as a vCloud Director environment. If you would like to learn more about how VXLAN works, be sure to check out the multi-part VXLAN series (
Part 1/
Part 2) by Venky
Deshpande.Disclaimer: This is not officially supported by VMware, please use at your own risk.
Configurations for VXLAN in vSphere Environment
Step 1 - Deploy vCNS Manager and configure it to point to your vCenter Server (do not enable or prepare VXLAN, this must be done after the configurations)
Step 2 - You will need to identify the VDS MoRef ID in your vCenter Server which will be used in the next step. Since the configuration is applied at the VDS level, you may want to consider having a separate VDS serving Nested Virtualization traffic since both promiscuous mode & forged transmits will automatically be enabled for all vWires. To locate the VDS MoRef ID, login to the vSphere Web Client and select the summary view for the VDS.
The VDS MoRef ID will be towards the end of the URL link and it should start with dvs-X where X is some arbitrary number. Record this value down for the next step
Step 3 - Download the
enablePromForVDS.sh shell script which will be used to prepare the VDS within the vCNS Manager. The script basically performs a POST to the REST API to the vCNS Manager using cURL and it accepts three input parameters:
vCNS Manager IP Address/Hostname,
VDS MoRef ID and
VDS MTU. The username/password is hard coded in the script to use the default which is admin/default. If you have modified the default password like any good admin, you will want to change the password before running the script. If you take a look at the request body, you will notice only promiscuous mode is enabled to true, but this will also automatically enable forged transmits as well.
In my lab enviroment, I have the vCNS Manager IP to be
172.30.0.196, VDS MoRef ID to be
dvs-13 and VDS MTU to be
9000. So the syntax to run the script would be:
./enablePromForVDS.sh 172.30.0.196 dvs-13 9000
Here is a screenshot of executing the script, you should see a response back with 200 to indicate successful execution of the script.
Step 4 - Now, we will proceed with the VXLAN preparation. Start off by logging into the vCNS Manager and selecting the vSphere Datacenter which you wish to enable VXLAN. On the right you should see a tab called "
Network Virtualization" go ahead and click on that and then click on the sub-tab called "
Preparation". Click on edit and then select the vSphere Cluster and proceed through the wizard based on your environment configuration.
Step 5 - Once the VXLAN preparation has completed, click on the "
Segment ID" and configure that based on your environment.
Step 6 - Next, click on "
Network Scopes" and you will create a network scope and specify the set of vSphere Clusters the VXLAN network will span.
Step 7 - Lastly, click on "
Networks" and this is where you will create your vWires and ensure it the proper network scope is selected.
Step 8 - To confirm that everything has been configured properly. We now log back into our vSphere Web Client and heading over to the VDS settings page. You should now see a new vWire portgroup that is created, if we take a look at it's settings we should see that both promiscuous mode and forged transmits is enabled.
You are now done with the VXLAN configurations in the vCNS Manager and can proceed to the regular instructions for enabling
Nested ESXi for vSphere.
Note: If you have already prepared VXLAN in your environment, you can still configure the above without having to un-prepare your VXLAN configurations. You just need to login to the vCNS Manager via the REST API and perform a DELETE on the VDS switch (Please refer to page 153 of the
vCNS API Programming Guide) which will just delete the mapping from vCNS but will not destroy any of your VDS configuration. Once that is done, you will be able to use the script to configure the VDS with the proper settings.
Configurations for VXLAN in vCloud Director Environment
A VXLAN network pool is automatically created for you when using vCloud Director 5.1, so the steps for preparing Nested Virtualization for vCloud Director is extremely simple compared to the vSphere only environment.
Note: VXLAN is only supported in vCloud Director 5.1, for previous versions you have the choice of using a VCD-NI or vSphere backed network and the configurations for that can be found
here.
Step 1 - Please follow the steps 1-5 from above in the vSphere only environment and then you are done. If you would like a more detailed walk through for configuring VXLAN for a vCloud Director environment, check out this
article by Rawlinson Rivera who takes you through the process step by step.
Step 2 - Proceed to the regular instructions for enabling
Nested ESXi for vCloud Director.
Step 3 - Lastly, you will go through the vCloud Director setup which is to attach your vCenter Server & vCNS Manager, create a Provider VDC, create an Organization and assign resources to your Organization VDC and ensure that the OrgVDC is consuming the VXLAN network pool that is automatically created for you when you create the Provider VDC. Once that is done, when you deploy your vApp, you will see a vWire that automatically created for you. If we login to the vSphere Web Client and go to the VDS settings, you will see the vWire has both promiscuous mode and forged transmits automatically enabled.
Additional Resources:
