Skip to ContentSkip to Footer
Start of content
- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: VLAN Tagging confusion
Switches, Hubs, and Modems
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
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
- Email to a Friend
- Report Inappropriate Content
11-19-2010 08:39 AM
11-19-2010 08:39 AM
VLAN Tagging confusion
I am working on a fairly large implementation of Procurve switches. I am having some trouble finding a clear answer to the 'no untagged' command for VLAN 1.
Should the tagged (DOT1Q uplinks) be included in the 'no untagged' statement for VLAN 1. I see that when a Trunk is setup it is part of the 'no untagged' statement. Simply put should all ports be 'no untagged' on VLAN 1 if they are either untagged in another VLAN or part of a DOT1Q tag?
Thanks
Should the tagged (DOT1Q uplinks) be included in the 'no untagged' statement for VLAN 1. I see that when a Trunk is setup it is part of the 'no untagged' statement. Simply put should all ports be 'no untagged' on VLAN 1 if they are either untagged in another VLAN or part of a DOT1Q tag?
Thanks
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-19-2010 09:13 AM
11-19-2010 09:13 AM
Re: VLAN Tagging confusion
Jason asked: "Simply put should all ports be 'no untagged' on VLAN 1 if they are either untagged in another VLAN or part of a DOT1Q tag?"
simply, yes, (and you don't control that statement being made) unless a port is part of a trunk group as you noted above.
Some port/vlan basics:
1) all ports are untagged members of vlan1 by default. (of course you know this, but I wanted to put it all down)
***
2) when a port is untagged into a different vlan, there is an automatic config line added into vlan1 of the 'no untagged x'.
***
3) when you simply tag a port into a vlan without changing its untagged state, the port remains untagged in vlan1.
4) you cannot remove that 'no untagged x' line in vlan1.
5) all ports must have a vlan home, can be untagged at most in one vlan, can be tagged multiple times, can be tagged and untagged at same time - but not in same vlan. a port does not have to be untagged in any vlan, as long as it is tagged in at least one vlan (the gotta have a home mode).
6) when a port is added into a trunk, the port loses it "individuality", it is part of the trunk now.
hth...Jeff
simply, yes, (and you don't control that statement being made) unless a port is part of a trunk group as you noted above.
Some port/vlan basics:
1) all ports are untagged members of vlan1 by default. (of course you know this, but I wanted to put it all down)
***
2) when a port is untagged into a different vlan, there is an automatic config line added into vlan1 of the 'no untagged x'.
***
3) when you simply tag a port into a vlan without changing its untagged state, the port remains untagged in vlan1.
4) you cannot remove that 'no untagged x' line in vlan1.
5) all ports must have a vlan home, can be untagged at most in one vlan, can be tagged multiple times, can be tagged and untagged at same time - but not in same vlan. a port does not have to be untagged in any vlan, as long as it is tagged in at least one vlan (the gotta have a home mode).
6) when a port is added into a trunk, the port loses it "individuality", it is part of the trunk now.
hth...Jeff
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.
End of content
United States
Hewlett Packard Enterprise International
Communities
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP