In Juniper speak 'bgp-error-tolerance' keeps the BGP sessions up, but downstream networks might still suffer from this.
With 'bgp-error-tolerance' enabled, the actual attribute that is malformed impacts this a lot. In some cases the specific malformed attribute will just be deleted, so it acts as a filter. In other cases the route will be hidden and not propagate further. https://www.juniper.net/documentation/us/en/software/junos/bgp/topics/topic-... On Tue, May 20, 2025 at 9:50 AM Niels den Otter via NANOG < nanog@lists.nanog.org> wrote:
Hello Simon,
We have seen the same in our network (was a BGP update for a specific /40 (!) IPv4 prefix as far as we can see).
In Juniper speak 'bgp-error-tolerance' keeps the BGP sessions up, but downstream networks might still suffer from this.
Regards,
Niels _______________________________________________ NANOG mailing list
https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/CDMNBBMC...