On 6/12/23 06:37, Saku Ytti wrote:
Either will help, configure either or both and you're good.
Actual fixed release will behave the same as if drop-path-attribute 28
had been configured. That is read T, read L, seek past V, without
parsing.
Thanks Saku. I just discovered that "protocols bgp
Either will help, configure either or both and you're good.
Actual fixed release will behave the same as if drop-path-attribute 28
had been configured. That is read T, read L, seek past V, without
parsing.
On Sun, 11 Jun 2023 at 19:36, Einar Bjarni Halldórsson wrote:
>
> On 6/11/23 15:24, Saku
On 6/11/23 15:24, Saku Ytti wrote:
set protocols bgp drop-path-attributes 28 works if your release is too
old for set protocols bgp bgp-error-tolerance, and is preferable in
some ways, as it will protect your downstream as well.
18.2R3-S3.11 supports protocols bgp bgp-error-tolerance, but
set protocols bgp drop-path-attributes 28 works if your release is too
old for set protocols bgp bgp-error-tolerance, and is preferable in
some ways, as it will protect your downstream as well.
On Sun, 11 Jun 2023 at 17:25, Einar Bjarni Halldórsson via juniper-nsp
wrote:
>
> Hi,
>
> We have two
Hi,
We have two MX204 edge routers, each with a connection to a different
upstream provider (and some IXP peerings on both).
Last week the IPv6 transit session on one of them starting flapping. It
turns out that we got hit with
5 matches
Mail list logo
