[rbak-nsp] BGP errors - upstream says related to 4byte AS?

[Brandon Leeberg]

send NOTIFICATION: 3/4 (update: attribute flags error) with 11 byte data. mxReadMs=5897

notification msg sent (nbr 129.250.203.101, context 0x40080002 32 bytes, repeated 167 times, code 3/4 (update: attribute flags error) -
 0000 0000 ffff ffff ffff ffff ffff ffff ffff ffff 0020 0303 04e0 0708 0003 02ed

We have TONS of these, but only on the session with the one provider (NTT). NTT claims that it is due to 4-byte AS being enabled (I can't find how to disable it). Our side hasn't changed, but they did an update. They claim that out of hundreds of neighbors, we are the only ones having a problem.


This was their response: "What looks like is happening is that when the attribute AS4_AGGREGATOR has a 4byte ASN it is not being properly handled by your device.

While talking with our dev group about the pcap data and tracking down which update is the culprit one of our devs pointed out this thread which looks to match up:

https://mailman.nanog.org/pipermail/nanog/2011-December/042519.html "



both we the upstream provider have 2byte ASNs.



Any help would be greatly appreciated.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/redback-nsp/attachments/20180324/e1019bf0/attachment.html>