[j-nsp] MX VPLS Trunk with VLAN rewriting

[Serge Vautour]

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-nsp at ml.karotte.org>
To: Juniper NSP <juniper-nsp at 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 at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp