In the most part of this chapter, we will use the new vSphere Client in HTML5, but still, there is some functionality that has not been ported on it. You can find the details at https://docs.vmware.com/en/VMware-vSphere/6.5/rn/vsphere-client-65-html5-functionality-support.html.
To create a new distributed switch, using the vSphere Client, follow these steps:
- First, we will create a vDS in the networking inventory view (1). This specific inventory view is the logical container of vDS definition and configuration. Right-click on the datacenter (in this example, SDN_PRAHA) and from the contextual menu, choose the Distributed Switch menu and then the New Distributed Switch... option as shown in the following screenshot:
- The next step is to specify the name for the vDS, which in our case is Mastering_DSwitch as shown in following screenshot:
- In the next part, we must specify the version of vDS. This step is very important because each different version has different features and enhancements, but of course, newest versions are not compatible with the previous version of ESXi and vSphere. To learn more about the features and capabilities of the different versions of vDS, you can click on the small blue icon i in the vSphere Client.
In this example, we used the latest version 6.5 because we have all the hosts in the latest version:
- The next step is to configure the settings as follows:
-
- Number of uplinks: You can specify the maximum number of allowed physical connections to the distributed switch per host
- Network I/O Control: You can prioritize the access to network resources for workloads
- Default port group: You can set create now or create later
- Port group name: This is the name for the default port group
- Finally, you will have the summary with all the information related to your configuration, for the last check. At this point, you can click on the Finish button shown as follows:
OK guys, this is going to be a little bit confusing for you, but trust me at the moment vSphere 6.5 Update 1 is better used for working with vDS vSphere Web Client. Why? The easy answer coming is that this version is not fully ready for working with vDS. It will be very soon.
So, we will switch to the vSphere Web Client in order to configure all the available settings of a vDS.