[195078] in North American Network Operators' Group
Re: Long AS Path
daemon@ATHENA.MIT.EDU (Olivier Benghozi)
Tue Jun 20 19:33:13 2017
X-Original-To: nanog@nanog.org
From: Olivier Benghozi <olivier.benghozi@wifirst.fr>
Date: Wed, 21 Jun 2017 01:33:07 +0200
To: "nanog@nanog.org" <nanog@nanog.org>
In-Reply-To: <e679487be750411a874b7376a7037aa9@EX-01.m21.local>
Errors-To: nanog-bounces@nanog.org
Yes, we had this kind of stuff in our logs:
Jun 20 08:15:25 cr-co-01-pareq2-re0 rpd[9656]: %DAEMON-3: Prefix Send =
failed ! x:x:186.177.176.0/23 (label 19) =
bgp_rt_trace_too_big_message:1213 path attribute too big. Cannot build =
update.
The AS path we have here is currently 12956 262206 262206 262197...
> On 21 june 2017 at 01:12, James Braunegg <james.braunegg@micron21.com> =
wrote :
>=20
> Just wondering if anyone else saw this yesterday afternoon ?
>=20
> Jun 20 16:57:29:E:BGP: =46rom Peer 38.X.X.X received Long AS_PATH=3D =
AS_SEQ(2) 174 12956 23456 23456 23456 23456 23456 23456 23456 23456 =
23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 23456 =
23456 23456 23456 23456 23456 23456 23456 23456 ... attribute length =
(567) More than configured MAXAS-LIMIT
>=20
> Someone is having fun, creating weird and wonderful long AS paths =
based around AS 23456, we saw the same pattern of data from numerous =
upstream providers.
