The physical switch treats the ESX Server like any other switch, tagging traffic with the appropriate VLAN tags as it moves across the trunk into the ESX Server's NICs.
The ESX Server then uses the VLAN tags to direct the traffic to the appropriate port group.
As with most other things in a VI3 implementation, the "best answer" will depend upon the organization's business needs.
In most cases, VST provides the right balance between complexity and simplicity while providing the greatest level of flexibility.
I discussed VLAN trunks, which use 802.1q encapsulation to pass tagged traffic up to the VMware ESX Server in my previous tip, Configuring VLANs in VMware Infrastructure 3 (VI3).
Virtual Switch Tagging (VST) VST uses 802.1q VLAN trunks and tagged traffic, as we've discussed already.
This means that the guest OS must be able to support VLANs and VLAN tags.
When to use VGT, EST or VST VLAN configurations Each of the different VLAN configurations has its advantages and disadvantages.
however, there might be plugins that refuse to work if they're strictly bound to a specipic host (i.e.
some plugs by cakewalk don't work, they are giving you the appropiate message when you try to load them).
also beware that, if you have waves plugins installed, these are dx plugins by nature, they'll be converted, too.
other than these minor issues this worked flawless for me.
Search for dating vst:
There are, however, three other types of VLAN configurations VI3 uses: virtual switch tagging (VST), external switch tagging (EST) and virtual guest tagging (VGT).