- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: Trunk or Tagged Port
Switches, Hubs, and Modems
1753737
Members
4353
Online
108799
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-25-2007 12:09 AM
тАО05-25-2007 12:09 AM
I am wondering if anyone can clarify an instance when I tagged port would used as opposed to a Trunk (port aggregation)?
It is my understanding that tagged ports are for interconectivty b/t two 802.1Q compliant switches. I am not sure if a trunk could also be used in this same instance.
Any clarification provided will be greatly appreciated.
It is my understanding that tagged ports are for interconectivty b/t two 802.1Q compliant switches. I am not sure if a trunk could also be used in this same instance.
Any clarification provided will be greatly appreciated.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-25-2007 01:58 AM
тАО05-25-2007 01:58 AM
Solution
Tagging and trunks are really two different animals.
A trunk is a link aggregation of some type using two or more physical interfaces to create a logical interface for increased performance and fault tolerance. Trunk groups can be used between switches or from switches to hosts. There are several proprietary protocols for interswitch trunking, varying from vendor to vendor. The standard protocol is now is IEEE 802.3ad, otherwise known as LACP -- Link Aggregation Control Protocol.
Tagging is whether or not to add an 802.1Q header on to an ethernet packet. The 802.1Q header is used for two purposes, VLAN and 802.1p prioritization. Tagging is used almost exclusively between switches. You would use tagging if you were in an environment using VLANs or VoIP that required prioritization.
If you required increased bandwidth between switches, you could create a trunk group. (Assuming the switches supported a common protocol.) If the switches needed to pass tagged packets before, they will still need to pass tagged packets over the trunk group. Setting up a trunk group does not alter or elimiate the requirement for passing tagged packets.
However, setting up a trunk group can alter the configuration of packet tagging. Depending on the switch vendor, model, and protocol, some may require setting tagging on each port, while others may just require it on the trunk group as a whole.
A trunk is a link aggregation of some type using two or more physical interfaces to create a logical interface for increased performance and fault tolerance. Trunk groups can be used between switches or from switches to hosts. There are several proprietary protocols for interswitch trunking, varying from vendor to vendor. The standard protocol is now is IEEE 802.3ad, otherwise known as LACP -- Link Aggregation Control Protocol.
Tagging is whether or not to add an 802.1Q header on to an ethernet packet. The 802.1Q header is used for two purposes, VLAN and 802.1p prioritization. Tagging is used almost exclusively between switches. You would use tagging if you were in an environment using VLANs or VoIP that required prioritization.
If you required increased bandwidth between switches, you could create a trunk group. (Assuming the switches supported a common protocol.) If the switches needed to pass tagged packets before, they will still need to pass tagged packets over the trunk group. Setting up a trunk group does not alter or elimiate the requirement for passing tagged packets.
However, setting up a trunk group can alter the configuration of packet tagging. Depending on the switch vendor, model, and protocol, some may require setting tagging on each port, while others may just require it on the trunk group as a whole.
Trust me, I know what I'm doing
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-25-2007 02:55 AM
тАО05-25-2007 02:55 AM
Re: Trunk or Tagged Port
Thank you providing such a concise and clear explanation.
Your response is greatly appreciated.
Your response is greatly appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-25-2007 02:56 AM
тАО05-25-2007 02:56 AM
Re: Trunk or Tagged Port
thank you for your response
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP