an tagging and mix and match
> stuff. For the rest, config must stay the same.
>
> Keep your stuff simple, leave as much as you can to the system to figure
> out unless you absolutely need to force.
>
> Cheers.
>
> -Original Message-
> From: juniper-nsp On Behalf Of
out
unless you absolutely need to force.
Cheers.
-Original Message-
From: juniper-nsp On Behalf Of Liam Farr
Sent: July 18, 2019 11:26 AM
To: Heng Chai, Tan
Cc: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] l2circuit between QFX-5110 & MX204 - one way traffic
Hi,
Tried as follows;
Hi,
Tried as follows;
liam@NA-QFX5110-1# show interfaces xe-0/0/9
description "Temp Link to Arista";
vlan-tagging;
mtu 9216;
encapsulation flexible-ethernet-services;
unit 123 {
encapsulation vlan-ccc;
vlan-id 123;
input-vlan-map pop;
output-vlan-map push;
family ccc;
}
liam@
Try Alain's recommendation. I completely forgot about the input/output
vlan part. You should have it on the MX as well, so that VLAN 123 would
be transmitted over the l2circuit.
xe- {
description
flexible-vlan-tagging;
mtu 9216;
encapsulation flexible-ethernet-services;
un
Hi,
That removed my ability to run bridge interfaces on xe-0/0/9, which might
cause me some design issues further down the track for production
deployments.
Applied this config, but same result.
liam@NA-QFX5110-1# show interfaces xe-0/0/9
description "Temp Link to Arista";
vlan-tagging;
mtu 9216
Here is an production version (thx Phil) but on QFX-5100 and MX960
(and MX104 before).
This works for about 200ish circuits so far...
We had a bunch of issue with those which can lead to unresponsive
interface... So depending on your situation you may have to reboot the
switch :(
I’m only aware of that being an issue when vlan bridge encapsulation is enabled
on the PHY:
https://www.juniper.net/documentation/en_US/junos/topics/reference/general/mpls-limitations-qfx-series.html
(There may, of course, be other cases too that are documented elsewhere)
In any event, this wor
Try below on QFX5110 terminating l2circuit. Last I remember the
flexible-vlan-tagging + flexible-ethernet-services behaves oddly on the
QFX5110.
delete interfaces xe-0/0/9 flexible-vlan-tagging
set interfaces xe-0/0/9 vlan-tagging
set interfaces xe-0/0/9 encapsulation vlan-ccc
Heng Chai, Tan
Hi,
Not sure if I'm "doing the dumb" or Junos bug or limitation of the QFX /
Trident 2+ chip-set.
Trying to do a basic l2circuit as follows
VLAN Tagged Interface > MX204 l2circuit / ldp > QFX-5110 / ldp > QFX-5110
l2circuit / ldp > VLAN Tagged Interface
What I am seeing is traffic going Test De
9 matches
Mail list logo