[j-nsp] MX VPLS Trunk with VLAN rewriting

[Humair Ali]

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 <dhanks at juniper.net> wrote:

> It's coming.
>
> On 12/22/11 8:04 AM, "Derick Winkworth" <dwinkworth at 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-nsp at ml.karotte.org>
> >To: Juniper NSP <juniper-nsp at 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 at puck.nether.net
> >https://puck.nether.net/mailman/listinfo/juniper-nsp
> >_______________________________________________
> >juniper-nsp mailing list juniper-nsp at puck.nether.net
> >https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>



-- 
Humair