Hi Chris ,
Good to know that this is working for you as expected in D40 .There is an
"internal" PR mentioning a case wrt "specific payload parsing " in L2ckt
case .This issue is addressed via that PR in D40 and hence it works .
thanks, Nebu.
From: Chris Wopat <m...@falz.net>
To: "juniper-nsp@puck.nether.net" <juniper-nsp@puck.nether.net>
Cc: nebu thomas <nebuvtho...@yahoo.com>
Sent: Wednesday, January 18, 2017 4:08 AM
Subject: Re: [j-nsp] QFX5100 routing engine filter eats customer l2circuit
packets
On 01/14/2017 02:25 AM, nebu thomas wrote:
> Hi Chris,
> Per your email , I understand it is this specific payload coming thru the
> L2ckt which is reporting this issue .
>
> Hence my earlier suggestion to test with14.1X53-D40 , and verify whether it
> helps in your case .
We were able to do some lab testing on D40 today and it is indeed acting
quite differently than D35 was.
* Previously 'monitor traffic interface <l2circuitiface>' would
consistently show some types of the tunneled traffic hitting the RE
(eigrp, ospf were tested).
* On D35 I could make many adjustments to the QFX's lo0 filter to get
that traffic to drop. on D40 I am no longer able to, as expected.
Interesting as there were no fixes listed related to this. Perhaps the
"LDP on IRB" change up also fixed this behavior.
If you (or anyone here?) is aware of the PR# related to this, I'd love
to know what it was.
--Chris
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
