[j-nsp] VPLS q-in-q

[Mark Tees]

I would add input-vlan-map pop and output-vlan-map push on your interface
unit and remove vlan-id from the VPLS instance.

You can see what it’s doing by showing the interface in operational mode
also.

Where maybe it’s not so explicit is when you put vlan-id on the VPLS
instance which configures input VLAN swaps that you can see on the
interface in operational output.

On Wed, 20 May 2020 at 21:18, Baldur Norddahl <baldur at gigabit.dk> wrote:

> Hello
>
> I am trying to enable transport of q-in-q double tagged frames over VPLS
> through our MX204. The remote end is a switch of another brand (ZTE) and
> it has some limitations. The outer vlan tag is not transported so I need
> the MX204 to add it back before processing. However I can not figure out
> how to do this.
>
> My test configuration:
>
> baldur at formervangen-edge1# show routing-instances poi-formervangen |
> display inheritance brief
> protocols {
>      vpls {
>          ## 'ethernet-vlan' was inherited from group 'POI-VPLS'
>          encapsulation-type ethernet-vlan;
>          ## 'no-control-word' was inherited from group 'POI-VPLS'
>          no-control-word;
>          ## 'mac-statistics' was inherited from group 'POI-VPLS'
>          mac-statistics;
>          mesh-group 1 {
>              vpls-id 424;
>              neighbor 10.9.124.0;
>          }
>      }
> }
> ## 'vpls' was inherited from group 'POI-VPLS'
> instance-type vpls;
> vlan-id 424;
> interface xe-0/1/7.424;
>
> baldur at formervangen-edge1# show interfaces xe-0/1/7
> flexible-vlan-tagging;
> native-vlan-id 424;
> encapsulation flexible-ethernet-services;
> unit 424 {
>      encapsulation vlan-vpls;
>      vlan-id 424;
> }
>
> I have a client injecting some traffic on the remote switch using outer
> vlan 424 and inner vlan 201. Remember outer vlan is not transported, so
> the L2VPN would only receive single tagged frames with vlan 201. I need
> the MX204 to add outer vlan 424 and transmit packets with outer vlan 424
> and inner vlan on interface xe-0/1/7. But instead I get this:
>
> 11:10:02.303264 00:22:07:4d:7b:0d > ff:ff:ff:ff:ff:ff, ethertype 802.1Q
> (0x8100), length 346: vlan 201, p 0, ethertype IPv4, 0.0.0.0.68 >
> 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:07:4d:7b:0d, length 300
>
> This is a tcpdump on a Linux server. Vlan 424 is not added and we just
> get singled tagged vlan 201 packets :-(.
>
> I have tried all sort of combinations including input and
> output-vlan-map but with no success. Anyone have some pointers on how to
> accomplish this?
>
> Thanks,
>
> Baldur
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
-- 
Regards,

Mark Tees