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
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
Hi,
> but it's just not allowed through software on the 10GE ports.
>
It is allowed since 16.1
> I'm not certain but I faintly recall that the fixed chassis MX80 didn't
> have QX.
>
Correct.
Best Regards,
Krasi
___
juniper-nsp mailing list juniper-n
This is bit nit picking but the QX isn't in any physical way tied to
the MIC slots, it's just dimensioning issue to avoid oversubscribing
the QX chip severely.
Technically the 10GE ports are the proper WAN side in MX80, MIC is
actually where the fabric normally would sit. All of the ports could
us
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
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
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)
7 matches
Mail list logo
