Try to add no-control-world under your l2circuit/neighbor/interface config on both sides (as well the VLAN push/pop on the ACX side).
2017-08-23 15:16 GMT+02:00 Jay Hanke <jayha...@gmail.com>: > No luck. Here is the config I tried > > unit 517 { > encapsulation vlan-ccc; > vlan-id 517; > input-vlan-map pop; > output-vlan-map push; > } > > > > On Wed, Aug 23, 2017 at 6:38 AM, Enoch Nyatoti <enyat...@yahoo.com> wrote: > > Hi, > > > > Can you try the following on your ACX5048 interface: > > > > set interfaces xe-0/0/46.517 input-vlan-map pop > > set interfaces xe-0/0/46.517 output-vlan-map push > > > > Best regards > > Enoch Nyatoti > > > > > > > > > > On Wednesday, August 23, 2017, 7:51:21 AM GMT+1, Jay Hanke > > <jayha...@gmail.com> wrote: > > > > > > I'm having an issue where I'm unable to pass traffic through a > > vlan-ccc between an ACX5048 and an EX4500. Other circuits on same > > boxes are working fine. The other circuits are ACX to ACX and EX to > > EX. > > > > PE1 (ex4500) > > > > > > l2circuit { > > neighbor 10.200.xx.xy { > > interface xe-0/0/1.517 { > > virtual-circuit-id 10000171; > > mtu 9000; > > encapsulation-type ethernet-vlan; > > } > > } > > } > > > > xe-0/0/1 { > > vlan-tagging; > > mtu 9216; > > encapsulation vlan-ccc; > > unit 517 { > > encapsulation vlan-ccc; > > vlan-id 517; > > } > > } > > > > PE2 (ACX5048): > > > > l2circuit { > > neighbor 10.200.xx.xx { > > interface xe-0/0/46.517 { > > virtual-circuit-id 10000171; > > mtu 9000; > > encapsulation-type ethernet-vlan; > > } > > } > > } > > > > xe-0/0/46 { > > > > vlan-tagging; > > mtu 9216; > > encapsulation flexible-ethernet-services; > > > > unit 517 { > > encapsulation vlan-ccc; > > vlan-id 517; > > } > > } > > > > I'm learning mac-addresses through the link on the PE2 side. > > > > The interface connected on the PE1 side doesn't learn anything. > > > > show l2circuit con shows the PW up on both PE devices. > > > > I've reloaded software on the EX4500 with the same result. There is > > one P router between the PE devices. > > > > All my existing PW are between EX4500 or between ACX. We don't have > > any working between systems with different models acting as PE > > devices. But quite a few working where PE devices are the same type. > > > > Any ideas? > > > > Jay > > _______________________________________________ > > juniper-nsp mailing list juniper-nsp@puck.nether.net > > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp