Which VLAN value permits virtual machine guest tagging in vSphere 5 environment?
A.
4095
B.
1
C.
4096
D.
0
Explanation:
http://vmnomad.blogspot.com/2011/07/vlan-tagging-and-use-cases-of-vlan-id.htmlPage 14 and 15 from vsphere-esxi-vcenter-server-50-networking-guide.pdf
A VLAN ID, which restricts port group traffic to a logical Ethernet segment within the physical network, is optional. For a port group to reach port groups located on other VLANs, the VLAN ID must be set to 4095. If you use VLAN IDs, you must change the port group labels and VLAN IDs together so that the labels properly represent connectivity.
…
If you enter 0 or leave the option blank, the port group can see only untagged (non-VLAN) traffic. If you enter 4095, the port group can see traffic on any VLAN while leaving the VLAN tags intact.
So,why 0 is another answer?
If you enter 0 or leave the option blank, the port group can see only untagged (non-VLAN) traffic. If you enter 4095, the port group can see traffic on any VLAN while leaving the VLAN tags intact.
…and the number 4095 is actually undisputably logical!. The VLAN tag in the packet basically consists of 4 bytes (or octets if you like) constituting 32 bits. Only 12 bits of them are actually used to indicate the VLAN NUMBER defined. Now get out your calculator, set it to binary, enter 12 ‘ones’ and convert to decimal. TADA = 4095
Just another tidbit of useless info :-))
(but with a bit of luck you’ll never forget it again!)
Cheers