[j-nsp] MX Lab config for virtual-switch

[Aaron]

Hi Matthew, I wonder if this test a ran a few weeks ago will help you... probably just remove the extra tag that I have in my config and replace ea5 units with your physical interfaces you are working with...

(my notes during my test...) in this test I show how to tie 2 different customer sites top tagged with a certain service provider tag with site1 as 101 and site 2 as 102...i just felt like messing with bottom tags being different… both CE 3750's in same ip subnet where able to ping each other just fine

set interfaces ae5 unit 101 encapsulation vlan-vpls

set interfaces ae5 unit 101 vlan-tags outer 101

set interfaces ae5 unit 101 vlan-tags inner 12

set interfaces ae5 unit 101 input-vlan-map pop-pop

set interfaces ae5 unit 101 output-vlan-map push-push

set interfaces ae5 unit 101 family vpls


set interfaces ae5 unit 102 encapsulation vlan-vpls

set interfaces ae5 unit 102 vlan-tags outer 102

set interfaces ae5 unit 102 vlan-tags inner 1212

set interfaces ae5 unit 102 input-vlan-map pop-pop

set interfaces ae5 unit 102 output-vlan-map push-push

set interfaces ae5 unit 102 family vpls


set routing-instances acme instance-type vpls

set routing-instances acme interface ge-0/0/38.102

set routing-instances acme interface ae5.101

set routing-instances acme interface ae5.102

set routing-instances acme route-distinguisher 10.101.12.245:20001

set routing-instances acme l2vpn-id l2vpn-id:64512:20001

set routing-instances acme vrf-target target:64512:20001

set routing-instances acme protocols vpls interface ge-0/0/38.102

set routing-instances acme protocols vpls interface ae5.101

set routing-instances acme protocols vpls interface ae5.102

set routing-instances acme protocols vpls no-tunnel-services

- Aaron