Skip to main content

VLAN Tagging VST, EST & VGT on VMWare vSphere

VLAN Tagging in ESX (VST,EST & VGT)
I am getting lot of questions on different types of VLAN tagging and how it works and how to configure it and they are even wondering that there is no specific setting named “VLAN tagging” in vsphere host network settings. Let’s cover from the basics..
There are 3 types of VLAN tagging avaliable in Vsphere.

1.Virtual Switch Tagging (VST)
2.External Switch Tagging (EST)
3.Virtual Guest Tagging (VGT)
There is no specific settings named “VLAN Tagging” is avialable in the vpshre host network settings. VLAN tagging is  determined by the VLAN value specified at the port group and it tells the vswitch or Phyiscal switch or Virtual machines to how to handle the VLAN tagging.
1. Virtual Switch Tagging (VST)
1.1 VST uses 802.1q VLAN trunks and tagged traffic.
1.2 VLAN tagging for all packets is performed by the Virtual Switch before leaving the ESX/ESXI host
1.3 Port groups on the Virtual switch of ESX server should be configured with VLAN ID (1-4094)
1.4 vSwitch responsibilty is  to strip off the vlan tag and send packet to virtual machine in corresponding port group.
1.5 Reduces the number of Physical nics on the server by running all the VLANs over one physical nic. Better solution would be keep 2 nics for redundancy.
1.6 Reduces number of cables from ESX server to physical switch.
1.7 The physical switch port connecting the uplink from the ESX should be configured as Trunk port.
1.8 virtual machine network Packet is delivered to vSwitch and before it is sent to physical switch the packet is tagged with vlan id according to the port group memebership of originating virtual machine.


2.External Switch Tagging (EST)
2.1  In EST, ESX host doesn’t see any vlan tags and does not handle any VLAN tagging.
2.2  All the tagging operation is done by physical switch and virtual switch is not aware about that.
2.3  Number of physical nics = no of VLANs connected to ESX
2.4  Port groups on the Virtual switch of ESX server need not to be configured with the VLAN number or configure VLAN ID 0 (if it is not native VLAN)
2.5  Count of NICS and cable connected to ESX is more as compared to VST approach.
2.6  The physical switch port connecting the uplink from the ESX should be configured as Access port assigned to specific VLAN.
2.7  virtual machine network Packet is delivered to physical switch without any tagging operation performed by the virtual switch.
3. Virtual Guest Tagging (VGT)
3.1 you must install 8021.Q VLAN trunking driver instide virtual machine guest opearting system.
3.2 All the VLAN tagging is performed by the virtual machine with use of trunking driver in the guest.
3.3 VLAN tags are understandable only between the virtual machine and external switch when frames are passed to/from virtual switches.
3.4 Virtual Switch will not be involved or aware of this operation. Vswitch only forwards the packets from Virtual machine to physical switch and will not perform any operation.
3.5 Port group of the virtual machine should be configured with VLAN ID 4095
3.6 The physical switch port connecting the uplink from the ESX should be configured as Trunk port
Below is comparison table for the people want a comparison under single table
I hope it will be helpful to understand the concept of VLAN Tagging with the simple language. Happy reading…..!!!!!!!

Comments

Popular posts from this blog

Quick Guide to VCF Automation for VCD Administrators

  Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been  released  and with it comes brand new Cloud Management Platform –  VCF Automation (VCFA)  which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...
  Issue with Aria Automation Custom form Multi Value Picker and Data Grid https://knowledge.broadcom.com/external/article?articleNumber=345960 Products VMware Aria Suite Issue/Introduction Symptoms: Getting  error " Expected Type String but was Object ", w hen trying to use Complex Types in MultiValue Picker on the Aria for Automation Custom Form. Environment VMware vRealize Automation 8.x Cause This issue has been identified where the problem appears when a single column Multi Value Picker or Data Grid is used. Resolution This is a known issue. There is a workaround.  Workaround: As a workaround, try adding one empty column in the Multivalue picker without filling the options. So we can add one more column without filling the value which will be hidden(there is a button in the designer page that will hide the column). This way the end user will receive the same view.  
  "Cloud zone insights not available yet, please check after some time" message on Aria Automation https://knowledge.broadcom.com/external/article?articleNumber=314894 Products VMware Aria Suite Issue/Introduction Symptoms: The certificate for Aria operations has been replaced since it was initially added to Aria Automation as an integration. When accessing the Insights pane under  Cloud Assembly  ->  Infrastructure  ->  Cloud Zone  ->  Insights  the following message is displayed:   "Cloud zone insights not available yet, please check after some time." The  /var/log/services-logs/prelude/hcmp-service-app/file-logs/hcmp-service-app.log  file contains ssl errors similar to:   2022-08-25T20:06:43.989Z ERROR hcmp-service [host='hcmp-service-app-xxxxxxx-xxxx' thread='Thread-56' user='' org='<org_id>' trace='<trace_id>' parent='<parent_id>' span='<span_id>'] c.v.a.h.a.common.AlertEnu...