Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.
Solved
difference between trunk and tagged vlans...
Posted on 2010-11-24
I know the cisco concept of trunk and access ports, i wanna know the difference between tagged ports and untagged ports in other vendor implementations like foundry etc...
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
2
-
2
5 Comments
you can see each vlan as a channel or frequency. In an access-port you have only one channel (vlan) and therefore each packet doesnt need to be marked individually.
In a trunk, because you send traffic from different vlans in the same carrier, each packet needs to be marked (tagged), otherwise the remote end doesnt know which vlan each received packet belongs to.
Ok. So in a trunk, each packet is marked. But what if I (the switch) receive a NOT marked packet in a trunk? A packet that is not tagged belongs to what in Cisco-terms is called native vlan. This is by default vlan1 but can be configured differently.
In Cisco-terms we talk about trunks and which vlans that belongs to a specific port. But other vendors see it differently. For example HP Procurve where you configure this tagging per vlan and not per port. If you have a trunk port in a HP-switch you can add additional vlans as tagged to that port (tagged port) but only one vlan can be untagged on that port.
If you have an access-port (in cisco-terms) which means that you have 0 tagged vlans and 1 tagged vlan, that is how the other end needs to be configured aswell.
If you in HP (or other vendors) add a previously unused switchport as tagged to a vlan, that means that this is (in cisco terms) a trunk that contains one single vlan, and that is tagged. This is in Cisco-switches configured as follows:
int gi0/x
switchport mode trunk
switchport trunk allowed vlan 123
switchport trunk native vlan 1 (or whatever, except for 123)
!
Does this make sense?
/Kvistofta
In a trunk, because you send traffic from different vlans in the same carrier, each packet needs to be marked (tagged), otherwise the remote end doesnt know which vlan each received packet belongs to.
Ok. So in a trunk, each packet is marked. But what if I (the switch) receive a NOT marked packet in a trunk? A packet that is not tagged belongs to what in Cisco-terms is called native vlan. This is by default vlan1 but can be configured differently.
In Cisco-terms we talk about trunks and which vlans that belongs to a specific port. But other vendors see it differently. For example HP Procurve where you configure this tagging per vlan and not per port. If you have a trunk port in a HP-switch you can add additional vlans as tagged to that port (tagged port) but only one vlan can be untagged on that port.
If you have an access-port (in cisco-terms) which means that you have 0 tagged vlans and 1 tagged vlan, that is how the other end needs to be configured aswell.
If you in HP (or other vendors) add a previously unused switchport as tagged to a vlan, that means that this is (in cisco terms) a trunk that contains one single vlan, and that is tagged. This is in Cisco-switches configured as follows:
int gi0/x
switchport mode trunk
switchport trunk allowed vlan 123
switchport trunk native vlan 1 (or whatever, except for 123)
!
Does this make sense?
/Kvistofta
your explanation was quite good,
but i dont understand
' If you have a trunk port in a HP-switch you can add additional vlans as tagged to that port (tagged port) but only one vlan can be untagged on that port'
What i know from cisco is a trunk port can carry traffic of multiple vlan's whereas an access port only belongs to one vlan .
but i dont understand
' If you have a trunk port in a HP-switch you can add additional vlans as tagged to that port (tagged port) but only one vlan can be untagged on that port'
What i know from cisco is a trunk port can carry traffic of multiple vlan's whereas an access port only belongs to one vlan .
Yes, you are right and there is no contradiction in what I wrote and what you are saying.
The technology is the same, no matter brand. The difference is the way to configure it. In HP you add ports to vlan, in Cisco you add vlans to ports.
What I say (that you quoted) is that in a trunk you can only have one untagged vlan. You cannot send multiple vlans as untagged. In the HP-world you configure vlan/ports by saying "add vlan x to port y as (un)tagged". If port y already was configured with an untagged vlan z, that vlan z will be removed from the port and vlan x will be the untagged (native) vlan instead.
/Kvistofta
The technology is the same, no matter brand. The difference is the way to configure it. In HP you add ports to vlan, in Cisco you add vlans to ports.
What I say (that you quoted) is that in a trunk you can only have one untagged vlan. You cannot send multiple vlans as untagged. In the HP-world you configure vlan/ports by saying "add vlan x to port y as (un)tagged". If port y already was configured with an untagged vlan z, that vlan z will be removed from the port and vlan x will be the untagged (native) vlan instead.
/Kvistofta
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
If you’re involved with your company’s wide area network (WAN), you’ve probably heard about SD-WANs. They’re the “boy wonder” of networking, ostensibly allowing companies to replace expensive MPLS lines with low-cost Internet access. But, are they …
WARNING:
If you follow the instructions here, you will wipe out your VTP and VLAN configurations. Make sure you have backed up your switch!!!
I recently had some issues with a few low-end Cisco routers (RV325) and I opened a case with Cisco TA…
Viewers will learn how to connect to a wireless network using the network security key. They will also learn how to access the IP address and DNS server for connections that must be done manually.
After setting up a router, find the network security…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
Suggested Courses
Course of the Month9 days, 16 hours left to enroll
722 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.