Skip to main content

VLAN Tagging in VMware ESX (VST,EST & VGT)

 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

Post a Comment

Popular posts from this blog

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.
Post a Comment
Read more

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...
Post a Comment
Read more

Recreating a VMFS-3 or VMFS-5 partition table in ESXi 5.x

For this kind of issues you need to engage VMware support on this, following any part of this article could lead to more complex situation if not ran by an expert.   Symptoms Datastore does not mount because of a lost or overwritten partition table.   Purpose When a VMFS partition is created in ESX 3.x or ESX 4.x, it has a Master Boot Record (MBR) partition map. The MBR is written to the first 512 B block (LBA0) and contains the information where the (VMFS) partition starts and ends. ESXi 5.0 introduced VMFS-5, which uses a GUID partition table (GPT) for new datastores. When a VMFS-3 partition is created in ESXi 5.x and is later updated to VMFS-5, the original partition map (MBR) is maintained. If the partition information of a VMFS datastore is deleted or overwritten (for example, by a Windows system with direct access to the same disks), it is impossible to determine if the partition map was GPT or MBR. The only time you can be sure that a GPT partition map was used is if th...
Post a Comment
Read more