How does one get the switch's management interface wrapped inside a QinQ?
For example, say I want all infrastructure nodes tagged VLAN 9 throughout the entire network, including the switches. However, I want each switch to have it's own QinQ to wrap those in.
Something like this:
Switch A (QinQ 100)
-- node 1 (vlan 9)
-- node 2 (vlan 9)
Switch B (QinQ 200)
-- node 3 (vlan 9)
-- node 4 (vlan 9)
so back at the router I have 2 interfaces: 100(9) for all infrastructure nodes on switch A, and 200(9) for all infrastructure nodes on switch B. (I know I can accomplish this with flat vlans, but the goal here is to have the same predictable vlan for all the field techs to work with while still keeping the network reasonably segregated).
But how to get the switch tagged vlan 9 and also wrapped inside it's designated QinQ tag? I would like switch A to be on interface 100(9) at the router along with nodes 1 and 2, and switch B to be on interface 200(9) along with nodes 3 and 4.
Thanks in advance for the feedback!
Management VLAN and QinQ tagging
- FuzzyDice
- Member
- Posts: 7
- Joined: Thu Jan 05, 2017 4:47 am
- Has thanked: 0 time
- Been thanked: 0 time
-
mike99 - Associate
- Posts: 837
- Joined: Tue Nov 25, 2014 10:53 am
- Location: Quebec, Canada
- Has thanked: 95 times
- Been thanked: 245 times
Re: Management VLAN and QinQ tagging
Your management vlan need to be outside of the QinQ. You could work around this by using (loosing) 2 ports, one to remove the QinQ vlan and the other one for management.
What you would need, and I'm pretty sure several WISP would find this usefull, is some kind of reverse QinQ that would encapsulate QinQ on egress an remove QinQ encapsulation on ingress.
What you would need, and I'm pretty sure several WISP would find this usefull, is some kind of reverse QinQ that would encapsulate QinQ on egress an remove QinQ encapsulation on ingress.
-
petecarlson - Experienced Member
- Posts: 107
- Joined: Thu Aug 28, 2014 7:04 pm
- Location: Baltimore, MD
- Has thanked: 15 times
- Been thanked: 10 times
Re: Management VLAN and QinQ tagging
mike99 wrote:Your management vlan need to be outside of the QinQ. You could work around this by using (loosing) 2 ports, one to remove the QinQ vlan and the other one for management.
What you would need, and I'm pretty sure several WISP would find this usefull, is some kind of reverse QinQ that would encapsulate QinQ on egress an remove QinQ encapsulation on ingress.
I've never thought of that but that would be really really useful. You would need to be able to set it as a trunk port and allow a subset of vlans and then wrap an extra 0x8100 or 0x88a8 tag.
What would be the most useful is if you could wrap with a matchlist.
-
mike99 - Associate
- Posts: 837
- Joined: Tue Nov 25, 2014 10:53 am
- Location: Quebec, Canada
- Has thanked: 95 times
- Been thanked: 245 times
Re: Management VLAN and QinQ tagging
Selective VLANs for QinQ. Some asked for it for a long time. Chris, Dave, Stephen or Eric, can we have a features request "annoncement" where feature request would be accounted in the first post just like for SFP or compatible PoE devices ?
4 posts
Page 1 of 1
Who is online
Users browsing this forum: No registered users and 55 guests