This was definitely the right answer, thank you for the help. I see that this
has just been patched in frr.
https://github.com/donaldsharp/frr/commit/084002351fbfd6b4e2d9c4c218288b2324ad81cd
On 9/7/17, 9:15 PM, "Andreas Jaggi" <a...@open.ch> wrote:
Hi Andrew
We observed this as well and are also looking into this (as we had one case
where this caused flapping of our iBGP session).
My current understanding is that the oversize UPDATE mentioned by Pawel
triggered a bug in Quagga which caused that the UPDATE message sent out by
Quagga to its peers was malformed.
The error message you see in the logs is then emited by the peers of the
Quagga host when they receive the malformed UPDATE message.
I'm currently preparing a bug-report and patch for Quagga regarding this.
As an immediate workaround to prevent this you could add an as-path filter
to discard oversized UPDATEs with more than 255 AS_PATH entries.
Important point here is that this as-path filter is added on the peers of
the host which logged the error message.
Adding the as-path filter only on the host with the error message will not
be enough as the packet attribute validation is done before the as-path filter
is applied.
Cheers
Andreas
On Thu, Sep 07, 2017 at 09:37:17PM +0000, Andrew Kerr wrote:
> We have had one occurrence in July, and another just today, where over an
hour period our BGP sessions have flapped repeatedly over an hour and logged
this message:
> Sep 7 05:38:38 $HOSTNAME bgpd[17794]: $IP: BGP type 2 length 3294 is too
large, attribute total length is 2314. attr_endp is 0x7f4b8db1478d. endp is
0x7f4b8db143b1
> (substituting $HOSTNAME and $IP for our real hostname and IP)
>
> We???re running version 0.99.24.1 on debian 4, etch.
>
> The most recent occurrence was 9/7/2017 between 05:38:38 UTC and 06:24:14
UTC. The previous occurrence was 6/20 at 6:15 UTC. The only other reference
I???ve found is a previous message to this group on 7/17/2017 with someone
running and older version that was encouraged top upgrade to 0.99.24, which is
where we???re already at.
>
> Has anyone else encountered this? Any suggestions?
> This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement,
>
> you may review at https://www.amdocs.com/about/email-disclaimer
<https://www.amdocs.com/about/email-disclaimer>
> _______________________________________________
> Quagga-users mailing list
> Quagga-users@lists.quagga.net
> https://lists.quagga.net/mailman/listinfo/quagga-users
--
andreas jaggi
lead engineer network services
open systems ag
raeffelstrasse 29
ch-8045 zurich
t: +41 58 100 10 10
f: +41 58 100 10 11
a...@open.ch
http://www.open.ch
This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
<https://www.amdocs.com/about/email-disclaimer>
_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-users
