Can anybody give an explanation for real function of tagged versus
untagged people in a VLAN? A genuine industry example is worthwhile. We have see the records, but it is certainly not obvious.
Into the most basic form, I regularly recall a 'Tagged' slot as an inter-switch hyperlink and an 'Untagged' port as a number slot
- All message board subject areas
- Past Topic
- Then Topic
The language of tagging try confusing without having some understanding of how process performs. Take a look and view whether this clears right up anything individually:
But anyways, an untagged interface in a VLAN was a physical member of that VLAN, ie. as soon as you put the number into that slot it's physically linked to that VLAN (often referred to as an "access interface" in Cisco language).
A tagged interface will usually hold traffic for numerous VLANs from switch to additional system systems particularly an upstream router or an edge turn (In Cisco terminology this is exactly called trunking, horsepower have no particular term because of it).
If a number should fit in with multiple VLAN, the slot ought to be TAGGED (as an example an VMware ESX Server with guests that belongs to different VLANs)
When you configure a slot as 'Tagged' you might be telling the switch to spot an 802.1q tag in the framework that will diagnose the VLAN that the frame originated in.