- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: Trunk Port Tagging
Switches, Hubs, and Modems
1753628
Members
5622
Online
108797
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
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
тАО09-18-2006 06:33 PM
тАО09-18-2006 06:33 PM
Trunk Port Tagging
Hello,
I have LACP trunks between a core and two downstream switches (all 5400s).
In reading I see alternate directions to either tag all VLANs between swtiches at the trunk level or untag VLAN1 or another VLAN.
What is the proper config?
Regards,
gp
I have LACP trunks between a core and two downstream switches (all 5400s).
In reading I see alternate directions to either tag all VLANs between swtiches at the trunk level or untag VLAN1 or another VLAN.
What is the proper config?
Regards,
gp
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-18-2006 06:45 PM
тАО09-18-2006 06:45 PM
Re: Trunk Port Tagging
Hi
If you want Vlans to travel accross your switches, just tagg all Vlans on the trunks, and keep the default-vlan untagged.
Good Luck !!!
If you want Vlans to travel accross your switches, just tagg all Vlans on the trunks, and keep the default-vlan untagged.
Good Luck !!!
Science for Everyone
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2006 04:31 AM
тАО09-20-2006 04:31 AM
Re: Trunk Port Tagging
George,
> In reading I see alternate directions to
> either tag all VLANs between swtiches at
> the trunk level or untag VLAN1 or another
> VLAN.
Both are correct. In fact, almost anything that you could do might be correct. It depends on what you interface to.
> What is the proper config?
For several reasons, having one VLAN untagged on a 802.1Q link is a good idea. It defines what should happen with untagged frames entering that port, and it establishes the highest level of inter-vendor compatibility (there are platforms which can't deal with it, though). The VLAN that is left untagged is often called the "native VLAN". Using the default VLAN (VID 1) as the native VLAN is another compatibility default. It is also very helpful in cases where ProCurve hardware falls back to port default configuration, like when you change from 1000BaseT to SFP or back on a 2626 dual personality port (silly concept, I could rant about it endlessly). If you have the switch management in VID 1, you still reach a box that broke this way and can fix it.
So it's a good idea to run VID 1 untagged and the others tagged, but other schemes will work as well as long as the peer side of the ISL thinks the same way about it.
BTW, you should always allow *all* existing VLANs on an ISL if you are running single instance STP. Leaving out certain VLANs arbitrarily (because you know they are not needed at the other end) can badly fail with SSTP.
FWIW, there is absolutely nothing link aggregation specific about that tagging. It applies to any ISL, aggregated or not.
BTW, I'm desperately trying to not use the term "trunk" as it means different things for different people ;)
> In reading I see alternate directions to
> either tag all VLANs between swtiches at
> the trunk level or untag VLAN1 or another
> VLAN.
Both are correct. In fact, almost anything that you could do might be correct. It depends on what you interface to.
> What is the proper config?
For several reasons, having one VLAN untagged on a 802.1Q link is a good idea. It defines what should happen with untagged frames entering that port, and it establishes the highest level of inter-vendor compatibility (there are platforms which can't deal with it, though). The VLAN that is left untagged is often called the "native VLAN". Using the default VLAN (VID 1) as the native VLAN is another compatibility default. It is also very helpful in cases where ProCurve hardware falls back to port default configuration, like when you change from 1000BaseT to SFP or back on a 2626 dual personality port (silly concept, I could rant about it endlessly). If you have the switch management in VID 1, you still reach a box that broke this way and can fix it.
So it's a good idea to run VID 1 untagged and the others tagged, but other schemes will work as well as long as the peer side of the ISL thinks the same way about it.
BTW, you should always allow *all* existing VLANs on an ISL if you are running single instance STP. Leaving out certain VLANs arbitrarily (because you know they are not needed at the other end) can badly fail with SSTP.
FWIW, there is absolutely nothing link aggregation specific about that tagging. It applies to any ISL, aggregated or not.
BTW, I'm desperately trying to not use the term "trunk" as it means different things for different people ;)
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