[j-nsp] MX VPLS Trunk with VLAN rewriting

[Sebastian Wiesinger]

* Serge Vautour <sergevautour at 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