On 11/15/12 1:58 AM, Claudio Jeker wrote:
On Wed, Nov 14, 2012 at 04:57:17PM -0500, Daniel Ouellet wrote:
Hi,
I am hoping that I may be able to somehow reach the consultant that
support the router server at Equinix in Ashburn VA here, or may be
someone else can provide me a bit more details as to how I could
possibly find more details or history on this problem.
There is a dual setup at Equinix that use OpenBSD as router servers
for public peering there, but somehow the version of the bgpd used
is older and I cant get them to upgrade it to the latest one and
possibly address thsi issue here.
What I get is this from the various routers servers (two) when I try
to either bring IPv4 or IPv6 with it:
Nov 14 16:24:55.432 EST: %BGP-3-NOTIFICATION: sent to neighbor
2001:504:0:2:FFFF:FFFF:FFFF:1 3/11 (invalid or corrupt AS path) 13
bytes 40020A02 02000023 2A0000BD 95
Why is your router unhappy about this AS path? This is a valid 4-byte
AS_PATH. Could it be that for some strange reason one side thinks that
4-byte AS are enabled and the other still expects 2-byte AS numbers?
I get the same announce from others and I have no problem, it is when I
get the 4 bytes AS from the router servers that is do not like it.
I try may version of IOS on my side just to be safe and be sure, and it
always give the same things, but only when it comes from the bgpd. I did
get that error as well when it was coming from a Brocande router as
well, but only temporary and when the other ISP reset his brocande
router it establish right up. But that happen only once in 18 months.
Just an example of as 4 bytes.
for the AS 197373 just to take that one as there is many more I can provide.
I get the announcement from these. 5 different ISP without problem, but
the same announcement from the router server will end up rejected as you
saw above.
But as you can see, it is not that I reject the 4 bytes, I do see them
in the table and I sure process them as well or they would not show up here.
That's just one example, I have as I said plenty more a swell, but
anytime the 4 bytes come from the router server side, it is resulting in
the same issue.
Below, you see the AS 197373 getting to me via these ases: 6461, 9002,
8359, 1273 and 3356 just for this case. If you need more I sure can
provide a very long list, but that would end up being he same anyway.
The bottom line is when I get an announcement from the router server
that include a 4 bytes AS, it reset the session with a reject message
back as pointed out.
Hope this help you more.
Best,
Daniel
IBX#sh ip bgp path | i 197373
0x10B3C968 189 1 4 6461 3356 28858 197373 197373 197373
197373 197373 197373 i
0x921A828 198 1 4 6461 3356 28858 197373 197373 197373
197373 197373 197373 i
0x990DC30 789 1 0 9002 16066 197373 i
0x106F8248 975 1 3000 8359 8359 8359 16066 197373 i
0x954C178 1014 1 3000 8359 8359 8359 16066 197373 i
0xEC3F4F8 1020 1 0 9002 16066 197373 i
0xEC316C8 2446 1 4081 6461 9002 16066 197373 i
0xEC37938 2549 1 4081 6461 9002 16066 197373 i
0xB609DCC 2818 1 0 1273 9002 16066 197373 i
0xB60A09C 2827 1 0 1273 9002 16066 197373 i
0xF6A7888 3460 1 0 3356 28858 197373 197373 197373 197373
197373 197373 i
