- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- Re: VLAN Tagging on Trunk
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО01-19-2017 07:55 PM
тАО01-19-2017 07:55 PM
When we create Trunk between two procurve switches and we need to Tag vlans on that trunk to extend Vlan to another switch, do we have to assign a ip adress to Vlan on both switches or just only one switch.?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2017 08:12 PM
тАО01-19-2017 08:12 PM
Re: VLAN Tagging on Trunk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2017 11:01 PM - edited тАО01-19-2017 11:26 PM
тАО01-19-2017 11:01 PM - edited тАО01-19-2017 11:26 PM
Re: VLAN Tagging on Trunk
A Layer-3 Instance has nothing to do with a Layer-2 vlan. you do not need an SVI. You just have to ensure that the vlans exists on both switches, either manually create them on your second switch or use GVRP to distribute your VLANS across your switches. Ensure also that the interface for interconnection is transmitting the vlan.
ex. switch A 4 ports prepared as uplink trunk to interconnect other switches via port 21-24
vlan 11 name "marketing" tagged 21-24 exit vlan 12 name "supp" tagged 21-24 exit vlan 13 name "WLAN" tagged 21-24
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2017 03:05 AM
тАО01-20-2017 03:05 AM
Re: VLAN Tagging on Trunk
You only need an IP address for the Vlans if you are going to do L3 stuff like routing or DHCP server/relay.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2017 06:18 AM
тАО01-20-2017 06:18 AM
Re: VLAN Tagging on Trunk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-23-2017 07:13 AM - edited тАО01-23-2017 07:14 AM
тАО01-23-2017 07:13 AM - edited тАО01-23-2017 07:14 AM
SolutionNO
you do not have to...
your traffic is switched and transported in Layer-2, if you only want to "leave" your vlan on side-A (route) thats fine.
If you a speaking of 2-port trunk than that is link-aggregation via static or LACP (802.3ad) as long as you have on both sides
vlan A tagged trk<X> exit vlan B tagged trk <x> ... ... vlan N tagged trk<X>
sending all your needed vlans into the trunk
The term trunk is different interpreted between vendors some mean with it an 802.1q trunk (vlan tagging)
others refer to is as 802.3ad trunk (link aggregation of ports) either static or with the LACProtocol