Routing
Routing

Layer-2 VPLS QinQ Issue (MX2020-MX960)

‎12-09-2018 02:11 AM

Hello,

I'm facing an issue within our network regarding QinQ over VPLS.

 

My network is as below:

 

Laptop <-> Microwave/FTTX <-> MX2020 <-> MX960 <-> MX960 <-> IGW

 

The issue being faced is that there is an untagged packet being sent from the Laptop end and travelling over Microwave facility facing towards MX2020. But when a vlan-id is configured, I can receive the MAC address as opposed to configuring a different vlan-id. But this packet is not being forwarded at all over VPLS towards the two MX960s connected with each other and because of that there is no traffic flow to/from Laptop towards IGW.

 

When the MX2020 is configured for the vlan-id 580, I can receive MAC address from the laptop as opposed to when the vlan-id is configured 3810 (which is configured for both MX960s and MX2020 should push it with this VLAN towards MX960 over VPLS).

 

Now, I have tried vlan-tags inner/outer, with inner being 3810 and outer being 580, but doing this the MAC address of the laptop is not observed. Only when I make it vlan-id 580, the MAC is observed. Whereas I can constantly learn the MAC address from the MX960.

 

In other scenarios, my network team uses the same inner/outer tags at MX2020, with vpls routing-instance having vlan-id set to none and MX960 with pop/push operations and it works fine. What could be causing this issue? I believe only issue is with vlan-tag manipulation.

 

Configuration at MX2020 (When vlan-id is changed from 3810 to 580, I can receive MAC from the laptop, otherwise I don't)

set interfaces ae403 unit 3810 policer-overhead -16
set interfaces ae403 unit 3810 description "TEST"
set interfaces ae403 unit 3810 encapsulation vlan-vpls
set interfaces ae403 unit 3810 vlan-id 580

VPLS configuration on MX2020

description "TEST";
instance-type vpls;
vlan-id none; interface ae403.3810; protocols { vpls { encapsulation-type ethernet-vlan; no-control-word; enable-mac-move-action; mac-pinning; no-tunnel-services; vpls-id 18517300; pseudowire-status-tlv; neighbor XXX.XXX.XXX.XX; } }

VPLS-id: 18517300
Neighbor Type St Time last up # Up trans
XXX.XXX.XXX.XX(vpls-id 18517300) rmt Up Dec 6 17:16:17 2018 1
Remote PE: XXX.XXX.XXX.XX, Negotiated control-word: No
Incoming label: 8082, Outgoing label: 404003
Negotiated PW status TLV: No
Local interface: lsi.1051951, Status: Up, Encapsulation: VLAN
Description: Intf - vpls NAME-OF-VPLS neighbor XXX.XXX.XXX.XX vpls-id 18517300
Flow Label Transmit: No, Flow Label Receive: No

The MX960 connected with MX2020 is configured as l2circuits with below configuration:

set interfaces ae1 unit 3810 description TEST
set interfaces ae1 unit 3810 encapsulation vlan-ccc
set interfaces ae1 unit 3810 vlan-id 3810
set interfaces ae1 unit 3810 input-vlan-map pop
set interfaces ae1 unit 3810 output-vlan-map push
set protocols l2circuit neighbor XXX.XXX.XX.XX interface ae1.3810 virtual-circuit-id 18517300
set protocols l2circuit neighbor XXX.XXX.XX.XX interface ae1.3810 description TEST
set protocols l2circuit neighbor XXX.XXX.XX.XX interface ae1.3810 no-control-word
set protocols l2circuit neighbor XXX.XXX.XX.XX interface ae1.3810 mtu 1500
set protocols l2circuit neighbor XXX.XXX.XX.XX interface ae1.3810 encapsulation-type ethernet-vlan
set protocols l2circuit neighbor XXX.XXX.XX.XX interface ae1.3810 pseudowire-status-tlv