
上QQ阅读APP看书,第一时间看更新
How to do it...
This recipe assumes that you already have a vCenter server set up.
- From Fabric | Access Policies | Pools | VLAN, select Create VLAN Pool from the Actions menu.
- Give the pool a name and click on the plus sign to set the block range:

- Click on OK. The new range should be listed under Encap Blocks. Click on Submit. The new VLAN pool will be listed:

- From the VM Networking menu, right-click on VMware and select Create vCenter Domain.

- Fill in the details for the Virtual Switch Name, and from the dropdown, select the VLAN pool created earlier.

- Fill in the vCenter Credentials with an appropriate username and password by clicking on the plus sign.
- Create the relevant credentials. Here, we will name the controller, set the IP address (or hostname), the distributed virtual switch (DVS) version, the data center (as defined in vCenter), and the associated credential (created in step 6).

- We also need to create the Management EPG. Clicking on the dropdown arrow next to this option brings up the option to Create EPG Under Tenant mgmt. Clicking on this option brings up another window:

- We create an Application Profile by clicking on the dropdown in the previous screenshot and selecting Create Application Profile Under Tenant mgmt:

- We name the application profile and select the monitoring policy (if we have one) and add any tags or descriptions:

- Click on SUBMIT.
- Returning to the previous screen, we can name the EPG and accept the default values for the other options.

- Click on SUBMIT.
- On the final screen, click on OK.

- Click on SUBMIT.

I have set the vSwitch policy to use LLDP, which will be significant later.
Note that although we have not specified any Security Domains or Port Channel Mode, the new configuration is accepted.
- If we start drilling through the left-hand side menu, we should be able to see any virtual machines running on the ESXi hosts connected to the vCenter server:

- We can verify that the DVS is created by looking through the vCenter console:

- If we look at the properties of the vSwitch, we can see that LLDP is enabled (as per the configuration made earlier).
