nanog mailing list archives
Re: Long AS Path
From: Olivier Benghozi <olivier.benghozi () wifirst fr>
Date: Wed, 21 Jun 2017 01:33:07 +0200
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 : Just wondering if anyone else saw this yesterday afternoon ? Jun 20 16:57:29:E:BGP: From Peer 38.X.X.X received Long AS_PATH= 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 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.
Current thread:
- Long AS Path James Braunegg (Jun 20)
- Re: Long AS Path Olivier Benghozi (Jun 20)
- Re: Long AS Path Laszlo Hanyecz (Jun 20)
- Re: Long AS Path sthaug (Jun 21)
- Re: Long AS Path Randy Bush (Jun 21)
- Re: Long AS Path Stephen Satchell (Jun 21)
- Re: Long AS Path sthaug (Jun 21)
- Re: Long AS Path Mel Beckman (Jun 21)
- Re: Long AS Path Pierfrancesco Caci (Jun 21)
- Re: Long AS Path jim deleskie (Jun 22)
- Re: Long AS Path Mel Beckman (Jun 22)