[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
lots of prepends
- Subject: lots of prepends
- From: pstewart at nexicomgroup.net (Paul Stewart)
- Date: Thu, 19 Feb 2009 16:24:27 -0500
- In-reply-to: <[email protected]>
- References: <[email protected]>
Just seen that here too:
Feb 19 16:20:35: %BGP-6-ASPATH: Long AS path 8001 8928 20912 20912 20912
20912 20912 20912 20912 20912 20912 20912 20912 20912 20912 20912 20912
20912 20912 20912 20912 20912 20912 20912 20912 20912 20912 20912 20912
20912 20912 20912 20912 20912 20912 20912 20912 20912 20912 20912 20912
20912 20912 20912 20912 20912 20912 20912 20912 20912 20912 20912 20912
20912 20912 20912 20912 20912 20912 20912 20912 20912 20912 20912 20912
20912 20912 20912 20912 20912 20912 20912 20912 20912 20912 20912 20912
20912 20912 20912 received from 207.99.64.25: More than configured
MAXAS-LIMIT
Our AS path limit is 100 which is way too high in my opinion but
regardless I was trying to figure out any logic in this.... I can
remember prepending one of our upstreams 4X at one point thinking that
was a bit nuts .... thankfully we don't prepend anyone these days....
Paul
-----Original Message-----
From: Mikael Abrahamsson [mailto:swmike at swm.pp.se]
Sent: Thursday, February 19, 2009 4:21 PM
To: nanog at nanog.org
Subject: lots of prepends
Today 85.119.176.0/21 was announced by AS20912 with 177 prepends. I
noticed 20912 modulo 256 is 176. AS47868 modulo 256 is 252 which matches
this mondays prepend-incident.
So, what router OS will put 20912 into a byte and thus end up with 176
in
something like "set as-path prepend last-as <no of prepends>" ? It needs
to be fixed.
Has anyone noticed any ill effects with IOS and using "bgp max-as"? Will
it just drop any prefixes with long as-paths and no other ill
operational
effects?
--
Mikael Abrahamsson email: swmike at swm.pp.se
----------------------------------------------------------------------------
"The information transmitted is intended only for the person or entity to which it is addressed and contains confidential and/or privileged material. If you received this in error, please contact the sender immediately and then destroy this transmission, including all attachments, without copying, distributing or disclosing same. Thank you."