Hi @SantoshBavkar 

Short answer is yes. Please check this link https://portal.nutanix.com/page/documents/details?targetId=AHV-Admin-Guide-v6_1:ahv-acr-l2-nw-mgmt-ovs-c.html

Virtual switches or VS are used to manage multiple bridges and uplinks. 

The VS configuration is designed to provide flexibility in configuring virtual bridge connections. A virtual switch (VS) defines a collection of AHV nodes and the uplink ports on each node. It is an aggregation of the same OVS bridge on all the compute nodes in a cluster. For example, vs0 is the default virtual switch is an aggregation of the br0 bridge and br0-up uplinks of all the nodes.

After you configure a VS, you can use the VS as reference for physical network management instead of using the bridge names as reference.

The virtual switch aggregates the same bridges on all nodes in the cluster. The bridge (for example, br1) connects to the physical port such as eth3 (Ethernet port) via the corresponding uplink (for example, br1-up). The uplink ports of the bridges are connected to the same physical network. For example, the following illustration shows that vs0 is mapped to the br0 bridge, in turn connected via uplink br0-up to various (physical) Ethernet ports on different nodes.

I suppose that you’ve been deployed br1 with manage_ovs commands, first creating the single bridge and the configuring interfaces and bond mode. If i am right, next time you can try to do it via Prism Element using the “Create VS” wizard which automatically creates bridge, bond and virtual switch. It’s faster. Here’s the link https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v6_1:wc-network-vs-create-upgrade-wc-t.html

Now your host will look similar to the image below. Yes I’m using 1G interfaces for vs0 on the lab, sadly I don’t have a 10G switch on the lab

To migrate br1 from “bridge” to “virtual switch” use this command from acli net.migrate_br_to_virtual_switch br1 vs_name=vs1 Your VLAN will migrate too. 

VLAN has no virtual switch before migration:

VLAN “moved” to vs1 after migration

Please note, when you created the VLAN on br1 you used the vswitch_name parameter which is deprecated.

Once br1 has been migrated to vs1, and if further VLANs are required you can create them directly thorough Prism Element on the desired virtual switch

To sum up>

• You should migrate bridges to virtual switches
• Virtual switches help to have all the nodes with the same network configuration
• Virtual switches allows you to create VLAN on a specific Virtual Switch without using ACLI

Long answer, hope it clarify things a bit

Regards!

Thanks for the answer