_65000_ in as-path - paging 8544, 16229, 37958

Marshall Eubanks tme at multicasttech.com
Wed Dec 10 09:58:11 CST 2008


On Dec 10, 2008, at 10:40 AM, Andy Davidson wrote:

> Hi,
>
> Seen in DFZ:
>
> 194.9.20.0 - 6661 42652 24611 34088 174 8544 16229 65000
>
> 196.216.161.0 - 8657 36881 36881 36881 36881 36881 36881 36881 36881  
> 36881 36881 65000 33763 37036
>
>
> We manage some bgp speakers running OpenBGPd.  This software appears  
> to tear down the session when encountering at least one of these  
> paths :
>
> Dec 10 15:31:48 l1-c1 bgpd[15300]: neighbor 84.x.x.x (S): state  
> change Established -> Idle, reason: Fatal error
>
>
> 194.9.20.0 looks like it started being originated by 65000 at 12:30  
> UTC today or so - this was also the time I started seeing openbgp  
> behave this this way.  Renesys thinks 12:58UTC.
>

In my DFZ BGP today I see

AS  64553  IANA-RSVD2                      |    1 prefixes |    1  
prefixes &    1 ASN supported |      254 Addresses |   6 hops | as  
path   174  2914  9498  9730  9498 64553
  AS  65000  IANA-RSVD2                      |    1 prefixes |    1  
prefixes &    1 ASN supported |      254 Addresses |   4 hops | as  
path   174  8544 16229 65000
  AS  65009  IANA-RSVD2                      |    2 prefixes |    2  
prefixes &    1 ASN supported |     2300 Addresses |   3 hops | as  
path   174  8167 65009
  AS  65500  IANA-RSVD2                      |    1 prefixes |    1  
prefixes &    1 ASN supported |      254 Addresses |   4 hops | as  
path   174 21385 33891 65500
  AS  65530  IANA-RSVD2                      |    2 prefixes |    2  
prefixes &    1 ASN supported |      764 Addresses |   5 hops | as  
path   174  3320  5483 41313 65530

This is fairly typical.

Is there some reason why 65000 is especially problematic ?

Regards
Marshall


>
> Andy
>





More information about the NANOG mailing list