Re: [j-nsp] EX4200 Q-in-Q
Hi,
Actually, we have this working on 9.5R2.7... :)
You need to do the following:
Under ethernet-switching-options:
dot1q-tunneling {
ether-type 0x8100;
}
And then create the QinQ vlan:
{master:1}[edit vlans QinQvlan]
vlan-id 504;
interface {
ge-1/0/8.0; -- customer interface
xe-1/1/0.0; -- trunk interface
}
dot1q-tunneling;
You can show that it is operational:
run show vlans XXX extensive
VLAN: , Created at: Thu Dec 17 10:46:54 2009
802.1Q Tag: 504, Internal index: 39, Admin State: Enabled, Origin: Static
Dot1q Tunneling Status: Enabled
Protocol: Port Mode
Number of interfaces: Tagged 1 (Active = 1), Untagged 1 (Active = 1)
xe-1/1/0.0*, tagged, trunk
ge-1/0/8.0*, untagged, access
And in our case, xe-1/1/0 is having a lot of non QinQ vlans, so this is what
you are looking for I guess!
Best regards,
Niels
-Original Message-
From: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Derick Winkworth
Sent: maandag 28 december 2009 22:37
To: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] EX4200 Q-in-Q
This is not possible until 10.0 on the EX.
From: Kevin Wormington kw...@sofnet.com
To: juniper-nsp@puck.nether.net
Sent: Mon, December 28, 2009 2:29:15 PM
Subject: [j-nsp] EX4200 Q-in-Q
Hi All,
I'm fairly new to EX4200s and am running 9.6R1.13 on a three member stack.
Unfortunately, I already have live traffic on this so it somewhat limits my
ability to test. I would like to be able to configure a trunk port to have
some vlan members that are single-tagged and some that are double-tagged
(q-in-q). I was wondering if anyone has successfully done this?
Thanks,
Kevin
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Tenzij schriftelijk anders is overeengekomen, zijn op al onze
rechtsbetrekkingen de Algemene Voorwaarden van Intermax van toepassing. Deze
zijn middels deze directe link
http://www.intermax.nl/algemenevoorwaardenintermax.pdf in te zien en/of kunnen
op verzoek worden toegezonden. Toepasselijkheid van eventuele inkoop- of andere
voorwaarden van opdrachtgever dan wel van derden wordt dan ook uitdrukkelijk
van de hand gewezen. Nederlands recht is exclusief van toepassing.
De informatie verzonden met dit E-mail bericht is uitsluitend bestemd voor de
geadresseerde. Gebruik van deze informatie door anderen dan de geadresseerde is
verboden. Openbaarmaking, vermenigvuldiging, verspreiding en/of verstrekking
van deze informatie aan derden is niet toegestaan. Intermax staat niet in voor
de juiste en volledige overbrenging van de inhoud van een verzonden E-mail,
noch voor tijdige ontvangst daarvan.
Please consider the environment before printing this e-mail.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] EX4200 Q-in-Q
Hello,
QinQ has been implemented starting from 9.3 and Juniper has removed
the limitation of having not QinQ and QinQ vlans on the same tagged
interface in 9.4
Best regards,
Ruslan
-Original Message-
From: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Niels Ardts
Sent: Tuesday, December 29, 2009 11:04 AM
To: 'Derick Winkworth'; 'juniper-nsp@puck.nether.net'
Subject: Re: [j-nsp] EX4200 Q-in-Q
Hi,
Actually, we have this working on 9.5R2.7... :)
You need to do the following:
Under ethernet-switching-options:
dot1q-tunneling {
ether-type 0x8100;
}
And then create the QinQ vlan:
{master:1}[edit vlans QinQvlan]
vlan-id 504;
interface {
ge-1/0/8.0; -- customer interface
xe-1/1/0.0; -- trunk interface
}
dot1q-tunneling;
You can show that it is operational:
run show vlans XXX extensive
VLAN: , Created at: Thu Dec 17 10:46:54 2009
802.1Q Tag: 504, Internal index: 39, Admin State: Enabled, Origin: Static
Dot1q Tunneling Status: Enabled
Protocol: Port Mode
Number of interfaces: Tagged 1 (Active = 1), Untagged 1 (Active = 1)
xe-1/1/0.0*, tagged, trunk
ge-1/0/8.0*, untagged, access
And in our case, xe-1/1/0 is having a lot of non QinQ vlans, so this is what
you are looking for I guess!
Best regards,
Niels
-Original Message-
From: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Derick Winkworth
Sent: maandag 28 december 2009 22:37
To: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] EX4200 Q-in-Q
This is not possible until 10.0 on the EX.
From: Kevin Wormington kw...@sofnet.com
To: juniper-nsp@puck.nether.net
Sent: Mon, December 28, 2009 2:29:15 PM
Subject: [j-nsp] EX4200 Q-in-Q
Hi All,
I'm fairly new to EX4200s and am running 9.6R1.13 on a three member stack.
Unfortunately, I already have live traffic on this so it somewhat limits my
ability to test. I would like to be able to configure a trunk port to have
some vlan members that are single-tagged and some that are double-tagged
(q-in-q). I was wondering if anyone has successfully done this?
Thanks,
Kevin
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Tenzij schriftelijk anders is overeengekomen, zijn op al onze
rechtsbetrekkingen de Algemene Voorwaarden van Intermax van toepassing. Deze
zijn middels deze directe link
http://www.intermax.nl/algemenevoorwaardenintermax.pdf in te zien en/of kunnen
op verzoek worden toegezonden. Toepasselijkheid van eventuele inkoop- of andere
voorwaarden van opdrachtgever dan wel van derden wordt dan ook uitdrukkelijk
van de hand gewezen. Nederlands recht is exclusief van toepassing.
De informatie verzonden met dit E-mail bericht is uitsluitend bestemd voor de
geadresseerde. Gebruik van deze informatie door anderen dan de geadresseerde is
verboden. Openbaarmaking, vermenigvuldiging, verspreiding en/of verstrekking
van deze informatie aan derden is niet toegestaan. Intermax staat niet in voor
de juiste en volledige overbrenging van de inhoud van een verzonden E-mail,
noch voor tijdige ontvangst daarvan.
Please consider the environment before printing this e-mail.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] EX4200 Q-in-Q
Niels,
Thanks...that is exactly what we are looking to do. Thanks to others
who have replied as well.
Kevin
On Dec 29, 2009, at 2:03 AM, Niels Ardts n.ar...@intermax.nl wrote:
Hi,
Actually, we have this working on 9.5R2.7... :)
You need to do the following:
Under ethernet-switching-options:
dot1q-tunneling {
ether-type 0x8100;
}
And then create the QinQ vlan:
{master:1}[edit vlans QinQvlan]
vlan-id 504;
interface {
ge-1/0/8.0; -- customer interface
xe-1/1/0.0; -- trunk interface
}
dot1q-tunneling;
You can show that it is operational:
run show vlans XXX extensive
VLAN: , Created at: Thu Dec 17 10:46:54 2009
802.1Q Tag: 504, Internal index: 39, Admin State: Enabled, Origin:
Static
Dot1q Tunneling Status: Enabled
Protocol: Port Mode
Number of interfaces: Tagged 1 (Active = 1), Untagged 1 (Active = 1)
xe-1/1/0.0*, tagged, trunk
ge-1/0/8.0*, untagged, access
And in our case, xe-1/1/0 is having a lot of non QinQ vlans, so this
is what you are looking for I guess!
Best regards,
Niels
-Original Message-
From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-
boun...@puck.nether.net] On Behalf Of Derick Winkworth
Sent: maandag 28 december 2009 22:37
To: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] EX4200 Q-in-Q
This is not possible until 10.0 on the EX.
From: Kevin Wormington kw...@sofnet.com
To: juniper-nsp@puck.nether.net
Sent: Mon, December 28, 2009 2:29:15 PM
Subject: [j-nsp] EX4200 Q-in-Q
Hi All,
I'm fairly new to EX4200s and am running 9.6R1.13 on a three member
stack. Unfortunately, I already have live traffic on this so it
somewhat limits my ability to test. I would like to be able to
configure a trunk port to have some vlan members that are single-
tagged and some that are double-tagged (q-in-q). I was wondering if
anyone has successfully done this?
Thanks,
Kevin
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Tenzij schriftelijk anders is overeengekomen, zijn op al onze
rechtsbetrekkingen de Algemene Voorwaarden van Intermax van
toepassing. Deze zijn middels deze directe link http://www.intermax.nl/algemenevoorwaardenintermax.pdf
in te zien en/of kunnen op verzoek worden toegezonden.
Toepasselijkheid van eventuele inkoop- of andere voorwaarden van
opdrachtgever dan wel van derden wordt dan ook uitdrukkelijk van de
hand gewezen. Nederlands recht is exclusief van toepassing.
De informatie verzonden met dit E-mail bericht is uitsluitend
bestemd voor de geadresseerde. Gebruik van deze informatie door
anderen dan de geadresseerde is verboden. Openbaarmaking,
vermenigvuldiging, verspreiding en/of verstrekking van deze
informatie aan derden is niet toegestaan. Intermax staat niet in
voor de juiste en volledige overbrenging van de inhoud van een
verzonden E-mail, noch voor tijdige ontvangst daarvan.
Please consider the environment before printing this e-mail.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] EX4200 Q-in-Q
Hi All, I'm fairly new to EX4200s and am running 9.6R1.13 on a three member stack. Unfortunately, I already have live traffic on this so it somewhat limits my ability to test. I would like to be able to configure a trunk port to have some vlan members that are single-tagged and some that are double-tagged (q-in-q). I was wondering if anyone has successfully done this? Thanks, Kevin ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] EX4200 Q-in-Q
This is not possible until 10.0 on the EX. From: Kevin Wormington kw...@sofnet.com To: juniper-nsp@puck.nether.net Sent: Mon, December 28, 2009 2:29:15 PM Subject: [j-nsp] EX4200 Q-in-Q Hi All, I'm fairly new to EX4200s and am running 9.6R1.13 on a three member stack. Unfortunately, I already have live traffic on this so it somewhat limits my ability to test. I would like to be able to configure a trunk port to have some vlan members that are single-tagged and some that are double-tagged (q-in-q). I was wondering if anyone has successfully done this? Thanks, Kevin ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
