Re: [j-nsp] Problem with QinQ MPLS Service + Switch

Yeah I’m not sure about how to do QinQ https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/vlan-double-tagging-with-l3-interface.html Aaron > On Oct 6, 2018, at 1:37 PM, Robert Hass wrote: > > l2circuit configuration on r03 is fine. I just made mistake putting post on

Re: [j-nsp] Problem with QinQ MPLS Service + Switch

l2circuit configuration on r03 is fine. I just made mistake putting post on j-nsp. Why should I push and pop on R03 ? See that QinQ (so adding second dot1q tag) is done on catalyst switch. On Sat, Oct 6, 2018 at 3:07 PM Aaron1 wrote: > And if that doesn’t work, you might need to push and pop on

Re: [j-nsp] Problem with QinQ MPLS Service + Switch

And if that doesn’t work, you might need to push and pop on the R03 side... ...also, is customer sending you 300 tagged frames on r01? If not then I don’t think you should tag and push and pop there on r01 Uni port Aaron > On Oct 6, 2018, at 8:03 AM, Aaron1 wrote: > > At least fix this on r

Re: [j-nsp] Problem with QinQ MPLS Service + Switch

At least fix this on r03... interface xe-0/0/0.300 Should be ... interface xe-0/0/1.300 Aaron > On Oct 6, 2018, at 2:19 AM, Robert Hass wrote: > > interface xe-0/0/0.300 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net

[j-nsp] Problem with QinQ MPLS Service + Switch

Hi I have MPLS network based on MX80 routers: r01, r02, r03 I need to establish MPLS Layer2 service with QinQ from r01:xe-0/0/0 to r03:xe-0/0/1.300 (VLAN 300). Customer on r01 is directly terminated on MX80 And on r03 customer is terminated via Catalyst switch (sw01) on port TenGig1/1/4 (VLAN300)