Re: [j-nsp] MX VPLS Trunk with VLAN rewriting
* Humair Ali humair.s@gmail.com [2011-12-23 16:41]: Sebastian, you should be able to achieve what you want by using Virtual Switch Routing instance instead of VPLS routing instance. you can confirgure a Virtual Switch instance with protocol VPLS in it , and create a bridge-domains to allow all vlans , that should allow you to be able to create a trunk in VPLS, and allowing all vlans FYI: I asked the people I know at Juniper the same question and they also told me to use virtual-switch. But this only works with interface-type trunk, and I need single units because 1 physical interface has multiple VLANs which must be added to different VPLS instances or other services on a per-unit basis. instance-type virtual-switch; ## ## Warning: Only interface with 'interface-mode' is allowed in a virtual-switch ## The other option was to use one VPLS instance per VLAN which seems to be the only option available to us. Regards Sebastian -- GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE) 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE. -- Terry Pratchett, The Fifth Elephant ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX VPLS Trunk with VLAN rewriting
Hi thanks for your feedback, just to clarify , you want to use specific unit for specific vpls instance ? if you need specfic range of vlan per unit for multiple VPLS instance ,can you try the following below, this is not what we have in production , but it should work, or work around it set interfaces xe-1/1/0 flexible-ethernet-services set interfaces xe-1/1/0 unit 10 encapsulation vlan-bridge set interfaces xe-1/1/0 unit 10 family bridge interface-mode trunk set interfaces xe-1/1/0 unit 10 family bridge vlan-id-list 100-500 set interfaces xe-1/1/0 unit 20 encapsulation vlan-bridge set interfaces xe-1/1/0 unit 20 family bridge interface-mode trunk set interfaces xe-1/1/0 unit 20 family bridge vlan-id-list 540-4094 then you can apply xe-1/1/0.10 to vpls-instance A and xe-1/1/0.20 to vpls instance B let me know if it works , i would be interested to know thanks On 10 January 2012 15:57, Sebastian Wiesinger juniper-...@ml.karotte.org wrote: * Humair Ali humair.s@gmail.com [2011-12-23 16:41]: Sebastian, you should be able to achieve what you want by using Virtual Switch Routing instance instead of VPLS routing instance. you can confirgure a Virtual Switch instance with protocol VPLS in it , and create a bridge-domains to allow all vlans , that should allow you to be able to create a trunk in VPLS, and allowing all vlans FYI: I asked the people I know at Juniper the same question and they also told me to use virtual-switch. But this only works with interface-type trunk, and I need single units because 1 physical interface has multiple VLANs which must be added to different VPLS instances or other services on a per-unit basis. instance-type virtual-switch; ## ## Warning: Only interface with 'interface-mode' is allowed in a virtual-switch ## The other option was to use one VPLS instance per VLAN which seems to be the only option available to us. Regards Sebastian -- GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE) 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE. -- Terry Pratchett, The Fifth Elephant ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp -- Humair ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX VPLS Trunk with VLAN rewriting
On Friday, December 23, 2011 12:04:34 AM Derick Winkworth wrote: There really ought to be an entire book *just* about this topic. Written in a tutorial fashion. Covering Q-in-Q, VPLS, PBB, VLAN tag manipulation, bridging features, etc. All on the MX specifically. It needs to cover the various encapsulation types, family bridge, etc. The MX solution guide isn't making it happen. I would say not just for the MX, but also for the M- and T- series routers, particularly spending lots of time on which PIC's can support what features. Many times this isn't really known, and it's hard to sometimes know what improvements/fixes, if any, a PIC-E has over a regular PIC, or what a PIC-2E has over a PIC-E, particularly when it comes to 802.1ad and friends. I wish there was a way for Juniper to abstract this so that I didn't care so much about which PIC's I bought. It's annoying. Mark. signature.asc Description: This is a digitally signed message part. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX VPLS Trunk with VLAN rewriting
hi Sebastian, did you try to remove the vlan-id statement at all (I mean, no vlan-id none but no vlan-id at all)? Massimo. On Thu, Dec 22, 2011 at 10:20 PM, Sebastian Wiesinger juniper-...@ml.karotte.org wrote: * Serge Vautour sergevaut...@yahoo.ca [2011-12-22 17:28]: Hello, Have you tried building this up from a very simple setup that works and adding complexity as you go? I've done something like this with the vlan-id all before but not with the VLAN tag manipulations at the same time. Hi, yes I begun with a simple setup where I just connected two sites with one vlan on each site and vlan-id none. The VLAN manipulation is the only thing that doesn't seem to work. The first thing that looks odd to me is the input-vlan map. Why do you need it? Swap on egress should be enough. Another thing I'm not sure about is both sub-interfaces in the same site. I'd put them in separate sites. I need the input-vlan-map to rewrite the vlan tag so that it is the same in the vpls instance on both sites. The subinterfaces are on the same L2 switch, why should I put them in different sites? What if I have 100 subinterfaces, I can't (or don't want to) make 100 sites for that on every PE. Try making this work by using the same VLAN on both ends, then add the VLAN manipulation. I've got something that looks almost exactly the same as this in my lab and it works: If I have the same VLAN on both sites it works, but I don't have that in the production setup so that's not an option. :( Regards Sebastian -- New GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE) Old GPG Key-ID: 0x76B79F20 (0x1B6034F476B79F20) 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE. -- Terry Pratchett, The Fifth Elephant ___ 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] MX VPLS Trunk with VLAN rewriting
It's coming.
On 12/22/11 8:04 AM, Derick Winkworth dwinkwo...@att.net wrote:
I don't have the answer immediately for you, so I apologize.
But I wanted to chime in with a THIS IS WHAT I'M TALKING ABOUT comment.
The MX is super flexible and has loads of features with respect to
VLANs/BRIDGING/VPLS/PBB etc, but its confusing as shit and the
documentation is not the greatest.
There really ought to be an entire book *just* about this topic. Written
in a tutorial fashion. Covering Q-in-Q, VPLS, PBB, VLAN tag
manipulation, bridging features, etc. All on the MX specifically. It
needs to cover the various encapsulation types, family bridge, etc.
The MX solution guide isn't making it happen.
Still, I heart the MX immensely. Especially now that we are finally
seeing quality code on it... or better quality code anyway.
Derick Winkworth
CCIE #15672 (RS, SP), JNCIE-M #721
http://packetpushers.net/author/dwinkworth/
From: Sebastian Wiesinger juniper-...@ml.karotte.org
To: Juniper NSP juniper-nsp@puck.nether.net
Sent: Thursday, December 22, 2011 8:34 AM
Subject: [j-nsp] MX VPLS Trunk with VLAN rewriting
Hi,
I'm trying to setup a VLPS Trunk (many VLANs - one VPLS instance) on
MX960 (Trio MPC) where each site has different local VLAN-IDs which
should be bridged over VPLS.
Example:
Site 1 VPLS Site 2
LAN1: vl100 vl10vl200
LAN2: vl301 vl11vl201
I did the following config:
Site1:
interfaces {
ae2 {
unit 100 {
encapsulation vlan-vpls;
vlan-id 100;
input-vlan-map {
swap;
vlan-id 10;
}
output-vlan-map swap;
}
unit 301 {
encapsulation vlan-vpls;
vlan-id 301;
input-vlan-map {
swap;
vlan-id 11;
}
output-vlan-map swap;
}
}
routing-instances {
test-service {
instance-type vpls;
vlan-id all;
interface ae2.100;
interface ae2.301;
vrf-target target:65000:10003;
protocols {
vpls {
no-tunnel-services;
site local-ce {
site-identifier 1;
interface ae2.100;
interface ae2.301;
}
mac-flush {
any-interface;
}
}
}
}
}
Site2:
interfaces {
ae2 {
unit 200 {
encapsulation vlan-vpls;
vlan-id 200;
input-vlan-map {
swap;
vlan-id 10;
}
output-vlan-map swap;
}
unit 201 {
encapsulation vlan-vpls;
vlan-id 201;
input-vlan-map {
swap;
vlan-id 11;
}
output-vlan-map swap;
}
}
routing-instances {
test-service {
instance-type vpls;
vlan-id all;
interface ae2.200;
interface ae2.201;
vrf-target target:65000:10003;
protocols {
vpls {
no-tunnel-services;
site local-ce {
site-identifier 2;
interface ae2.200;
interface ae2.201;
}
mac-flush {
any-interface;
}
}
}
}
}
When I try to commit this config I get an error:
[edit routing-instances test-service interface]
'ae2.100'
interface with input/output vlan-maps cannot be added to a
routing-instance with a vlan-id/vlan-tags configured
JunOS version is 11.2R4
When I remove vlan-id all from the VPLS instance the config commits
but no bridge is formed, the clients on each site cannot reach each
other.
Any idea what to do? Our Juniper consultant said it would be possible
to do this.
Regards
Sebastian
--
New GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0
B9CE)
Old GPG Key-ID: 0x76B79F20 (0x1B6034F476B79F20)
'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE
SCYTHE.
-- Terry Pratchett, The Fifth Elephant
___
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
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX VPLS Trunk with VLAN rewriting
Sebastian,
you should be able to achieve what you want by using Virtual Switch Routing
instance instead of VPLS routing instance.
you can confirgure a Virtual Switch instance with protocol VPLS in it , and
create a bridge-domains to allow all vlans , that should allow you to be
able to create a trunk in VPLS, and allowing all vlans
HTH
On 23 December 2011 15:18, Doug Hanks dha...@juniper.net wrote:
It's coming.
On 12/22/11 8:04 AM, Derick Winkworth dwinkwo...@att.net wrote:
I don't have the answer immediately for you, so I apologize.
But I wanted to chime in with a THIS IS WHAT I'M TALKING ABOUT comment.
The MX is super flexible and has loads of features with respect to
VLANs/BRIDGING/VPLS/PBB etc, but its confusing as shit and the
documentation is not the greatest.
There really ought to be an entire book *just* about this topic. Written
in a tutorial fashion. Covering Q-in-Q, VPLS, PBB, VLAN tag
manipulation, bridging features, etc. All on the MX specifically. It
needs to cover the various encapsulation types, family bridge, etc.
The MX solution guide isn't making it happen.
Still, I heart the MX immensely. Especially now that we are finally
seeing quality code on it... or better quality code anyway.
Derick Winkworth
CCIE #15672 (RS, SP), JNCIE-M #721
http://packetpushers.net/author/dwinkworth/
From: Sebastian Wiesinger juniper-...@ml.karotte.org
To: Juniper NSP juniper-nsp@puck.nether.net
Sent: Thursday, December 22, 2011 8:34 AM
Subject: [j-nsp] MX VPLS Trunk with VLAN rewriting
Hi,
I'm trying to setup a VLPS Trunk (many VLANs - one VPLS instance) on
MX960 (Trio MPC) where each site has different local VLAN-IDs which
should be bridged over VPLS.
Example:
Site 1 VPLS Site 2
LAN1: vl100 vl10vl200
LAN2: vl301 vl11vl201
I did the following config:
Site1:
interfaces {
ae2 {
unit 100 {
encapsulation vlan-vpls;
vlan-id 100;
input-vlan-map {
swap;
vlan-id 10;
}
output-vlan-map swap;
}
unit 301 {
encapsulation vlan-vpls;
vlan-id 301;
input-vlan-map {
swap;
vlan-id 11;
}
output-vlan-map swap;
}
}
routing-instances {
test-service {
instance-type vpls;
vlan-id all;
interface ae2.100;
interface ae2.301;
vrf-target target:65000:10003;
protocols {
vpls {
no-tunnel-services;
site local-ce {
site-identifier 1;
interface ae2.100;
interface ae2.301;
}
mac-flush {
any-interface;
}
}
}
}
}
Site2:
interfaces {
ae2 {
unit 200 {
encapsulation vlan-vpls;
vlan-id 200;
input-vlan-map {
swap;
vlan-id 10;
}
output-vlan-map swap;
}
unit 201 {
encapsulation vlan-vpls;
vlan-id 201;
input-vlan-map {
swap;
vlan-id 11;
}
output-vlan-map swap;
}
}
routing-instances {
test-service {
instance-type vpls;
vlan-id all;
interface ae2.200;
interface ae2.201;
vrf-target target:65000:10003;
protocols {
vpls {
no-tunnel-services;
site local-ce {
site-identifier 2;
interface ae2.200;
interface ae2.201;
}
mac-flush {
any-interface;
}
}
}
}
}
When I try to commit this config I get an error:
[edit routing-instances test-service interface]
'ae2.100'
interface with input/output vlan-maps cannot be added to a
routing-instance with a vlan-id/vlan-tags configured
JunOS version is 11.2R4
When I remove vlan-id all from the VPLS instance the config commits
but no bridge is formed, the clients on each site cannot reach each
other.
Any idea what to do? Our Juniper consultant said it would be possible
to do this.
Regards
Sebastian
--
New GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0
B9CE)
Old GPG Key-ID: 0x76B79F20 (0x1B6034F476B79F20)
'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE
SCYTHE.
-- Terry Pratchett, The Fifth Elephant
___
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
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
Re: [j-nsp] MX VPLS Trunk with VLAN rewriting
* magno massimo.magn...@gmail.com [2011-12-23 15:27]: hi Sebastian, did you try to remove the vlan-id statement at all (I mean, no vlan-id none but no vlan-id at all)? Hi, yes I have that now and it's not doing anything. I see no mac-adresses in show vpls mac-table. Regards Sebastian -- New GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE) Old GPG Key-ID: 0x76B79F20 (0x1B6034F476B79F20) 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE. -- Terry Pratchett, The Fifth Elephant ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX VPLS Trunk with VLAN rewriting
I don't have the answer immediately for you, so I apologize.
But I wanted to chime in with a THIS IS WHAT I'M TALKING ABOUT comment. The
MX is super flexible and has loads of features with respect to
VLANs/BRIDGING/VPLS/PBB etc, but its confusing as shit and the documentation is
not the greatest.
There really ought to be an entire book *just* about this topic. Written in a
tutorial fashion. Covering Q-in-Q, VPLS, PBB, VLAN tag manipulation, bridging
features, etc. All on the MX specifically. It needs to cover the various
encapsulation types, family bridge, etc.
The MX solution guide isn't making it happen.
Still, I heart the MX immensely. Especially now that we are finally seeing
quality code on it... or better quality code anyway.
Derick Winkworth
CCIE #15672 (RS, SP), JNCIE-M #721
http://packetpushers.net/author/dwinkworth/
From: Sebastian Wiesinger juniper-...@ml.karotte.org
To: Juniper NSP juniper-nsp@puck.nether.net
Sent: Thursday, December 22, 2011 8:34 AM
Subject: [j-nsp] MX VPLS Trunk with VLAN rewriting
Hi,
I'm trying to setup a VLPS Trunk (many VLANs - one VPLS instance) on
MX960 (Trio MPC) where each site has different local VLAN-IDs which
should be bridged over VPLS.
Example:
Site 1 VPLS Site 2
LAN1: vl100 vl10 vl200
LAN2: vl301 vl11 vl201
I did the following config:
Site1:
interfaces {
ae2 {
unit 100 {
encapsulation vlan-vpls;
vlan-id 100;
input-vlan-map {
swap;
vlan-id 10;
}
output-vlan-map swap;
}
unit 301 {
encapsulation vlan-vpls;
vlan-id 301;
input-vlan-map {
swap;
vlan-id 11;
}
output-vlan-map swap;
}
}
routing-instances {
test-service {
instance-type vpls;
vlan-id all;
interface ae2.100;
interface ae2.301;
vrf-target target:65000:10003;
protocols {
vpls {
no-tunnel-services;
site local-ce {
site-identifier 1;
interface ae2.100;
interface ae2.301;
}
mac-flush {
any-interface;
}
}
}
}
}
Site2:
interfaces {
ae2 {
unit 200 {
encapsulation vlan-vpls;
vlan-id 200;
input-vlan-map {
swap;
vlan-id 10;
}
output-vlan-map swap;
}
unit 201 {
encapsulation vlan-vpls;
vlan-id 201;
input-vlan-map {
swap;
vlan-id 11;
}
output-vlan-map swap;
}
}
routing-instances {
test-service {
instance-type vpls;
vlan-id all;
interface ae2.200;
interface ae2.201;
vrf-target target:65000:10003;
protocols {
vpls {
no-tunnel-services;
site local-ce {
site-identifier 2;
interface ae2.200;
interface ae2.201;
}
mac-flush {
any-interface;
}
}
}
}
}
When I try to commit this config I get an error:
[edit routing-instances test-service interface]
'ae2.100'
interface with input/output vlan-maps cannot be added to a routing-instance
with a vlan-id/vlan-tags configured
JunOS version is 11.2R4
When I remove vlan-id all from the VPLS instance the config commits
but no bridge is formed, the clients on each site cannot reach each
other.
Any idea what to do? Our Juniper consultant said it would be possible
to do this.
Regards
Sebastian
--
New GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE)
Old GPG Key-ID: 0x76B79F20 (0x1B6034F476B79F20)
'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE.
-- Terry Pratchett, The Fifth Elephant
___
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] MX VPLS Trunk with VLAN rewriting
Hello,
Have you tried building this up from a very simple setup that works and adding
complexity as you go? I've done something like this with the vlan-id all
before but not with the VLAN tag manipulations at the same time.
The first thing that looks odd to me is the input-vlan map. Why do you need it?
Swap on egress should be enough. Another thing I'm not sure about is both
sub-interfaces in the same site. I'd put them in separate sites.
Try making this work by using the same VLAN on both ends, then add the VLAN
manipulation. I've got something that looks almost exactly the same as this in
my lab and it works:
interfaces {
ae2 {
unit 100 {
encapsulation vlan-vpls;
vlan-id 100;
}
unit 301 {
encapsulation vlan-vpls;
vlan-id 301;
}
}
routing-instances {
test-service {
instance-type vpls;
vlan-id all;
interface ae2.100;
interface ae2.301;
vrf-target target:65000:10003;
protocols {
vpls {
no-tunnel-services;
site vlan100 {
site-identifier 1;
interface ae2.100;
}
site vlan301 {
site-identifier 2;
interface ae2.301;
}
}
}
}
}
Use the same config on both ends, update the site-IDs to make all 4 unique.
If you get this working, start adding the egress swap. I am having trouble
reasoning how it will work. The box needs a way to know what traffic to
associate to which sub-interface. I don't think it can do that in this case.
I hope that helps.
Serge
From: Sebastian Wiesinger juniper-...@ml.karotte.org
To: Juniper NSP juniper-nsp@puck.nether.net
Sent: Thursday, December 22, 2011 10:34:43 AM
Subject: [j-nsp] MX VPLS Trunk with VLAN rewriting
Hi,
I'm trying to setup a VLPS Trunk (many VLANs - one VPLS instance) on
MX960 (Trio MPC) where each site has different local VLAN-IDs which
should be bridged over VPLS.
Example:
Site 1 VPLS Site 2
LAN1: vl100 vl10 vl200
LAN2: vl301 vl11 vl201
I did the following config:
Site1:
interfaces {
ae2 {
unit 100 {
encapsulation vlan-vpls;
vlan-id 100;
input-vlan-map {
swap;
vlan-id 10;
}
output-vlan-map swap;
}
unit 301 {
encapsulation vlan-vpls;
vlan-id 301;
input-vlan-map {
swap;
vlan-id 11;
}
output-vlan-map swap;
}
}
routing-instances {
test-service {
instance-type vpls;
vlan-id all;
interface ae2.100;
interface ae2.301;
vrf-target target:65000:10003;
protocols {
vpls {
no-tunnel-services;
site local-ce {
site-identifier 1;
interface ae2.100;
interface ae2.301;
}
mac-flush {
any-interface;
}
}
}
}
}
Site2:
interfaces {
ae2 {
unit 200 {
encapsulation vlan-vpls;
vlan-id 200;
input-vlan-map {
swap;
vlan-id 10;
}
output-vlan-map swap;
}
unit 201 {
encapsulation vlan-vpls;
vlan-id 201;
input-vlan-map {
swap;
vlan-id 11;
}
output-vlan-map swap;
}
}
routing-instances {
test-service {
instance-type vpls;
vlan-id all;
interface ae2.200;
interface ae2.201;
vrf-target target:65000:10003;
protocols {
vpls {
no-tunnel-services;
site local-ce {
site-identifier 2;
interface ae2.200;
interface ae2.201;
}
mac-flush {
any-interface;
}
}
}
}
}
When I try to commit this config I get an error:
[edit routing-instances test-service interface]
'ae2.100'
interface with input/output vlan-maps cannot be added to a routing-instance
with a vlan-id/vlan-tags configured
JunOS version is 11.2R4
When I remove vlan-id all from the VPLS instance the config commits
but no bridge is formed, the clients on each site cannot reach each
other.
Any idea what to do? Our Juniper consultant said it would be possible
to do this.
Regards
Sebastian
--
New GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE)
Old GPG Key-ID: 0x76B79F20 (0x1B6034F476B79F20)
'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE.
-- Terry Pratchett, The Fifth Elephant
___
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] MX VPLS Trunk with VLAN rewriting
* Serge Vautour sergevaut...@yahoo.ca [2011-12-22 17:28]: Hello, Have you tried building this up from a very simple setup that works and adding complexity as you go? I've done something like this with the vlan-id all before but not with the VLAN tag manipulations at the same time. Hi, yes I begun with a simple setup where I just connected two sites with one vlan on each site and vlan-id none. The VLAN manipulation is the only thing that doesn't seem to work. The first thing that looks odd to me is the input-vlan map. Why do you need it? Swap on egress should be enough. Another thing I'm not sure about is both sub-interfaces in the same site. I'd put them in separate sites. I need the input-vlan-map to rewrite the vlan tag so that it is the same in the vpls instance on both sites. The subinterfaces are on the same L2 switch, why should I put them in different sites? What if I have 100 subinterfaces, I can't (or don't want to) make 100 sites for that on every PE. Try making this work by using the same VLAN on both ends, then add the VLAN manipulation. I've got something that looks almost exactly the same as this in my lab and it works: If I have the same VLAN on both sites it works, but I don't have that in the production setup so that's not an option. :( Regards Sebastian -- New GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE) Old GPG Key-ID: 0x76B79F20 (0x1B6034F476B79F20) 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE. -- Terry Pratchett, The Fifth Elephant ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
