FWIW, I have single digit NANOG shirts in my closet... of course, I couldn't /*fit* into them/... anymore. It has been almos_t_ 20 years..... Time flies.... eh ? Seems like just yesterday Bill, John, I and /*Moses*/ were all having lunch in Denver. ;-) On 09/23/2015 05:20 PM, Mike Hammett wrote:
Fearing you might be on here, I tried to be fairly non-offensive in my post. ;-)
----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com
------------------------------------------------------------------------ *From: *"Richard Irving" <rirving@antient.org> *To: *"Simon Lockhart" <simon@slimey.org>, "Mike Hammett" <nanog@ics-il.net> *Cc: *"NANOG" <nanog@nanog.org> *Sent: *Wednesday, September 23, 2015 4:19:23 PM *Subject: *Re: 4 byte ASNs through OpenBGPd to old Cisco IOS
Typo.
They did, and it *has* now formed peering with the RSD.
Thanks!
12.4.(24)T is the first version from that IOS train that natively supports 4 byte ASN's.
We can upgrade at a more convenient time and date.
:-)
On Wed Sep 23, 2015 at 03:37:31PM -0500, Mike Hammett wrote:
Do any of you have any useful input other than they need to upgrade
On 09/23/2015 05:04 PM, Simon Lockhart wrote: their IOS
to something newer than 4.5 years old? I recently went through a very similar issue, and was convinced it was related to 32 bit ASNs.
Are they seeing this error? Sep 1 08:40:41.506 UTC: %BGP-3-NOTIFICATION: sent to neighbor xxx.xxx.xxx.xxx 3/11 (invalid or corrupt AS path) 11 bytes 40020802 033C3424 580097
If so, have they configured "no bgp enforce-first-as" in their BGP router config?
Simon