[Xorp-users] BGP update never sent out - why ?

[NezLeShmil]

I am using XORP Release-1.4.

 The exact Debug Message I am getting is:

 [ 6965  +723 ../../bgp/next_hop_resolver.cc ] This registration is already
queued

When I am seeing this message the BGP Update which is supposed by the
xorp_bgp is not sent.

 That is a part of my log which is HUGE ! the xorp is connecting to a real
Core Router and receving around 250 000 routes, and updates at a rate of 10
TPS.

 Xorp LOG:

 [ 6965  +111 ../../bgp/bgp_trie.cc ] deleting route for 167.203.144.0/20
with attributes 0xc858068[ 6965  +117 ../../bgp/bgp_trie.cc ]  and erasing
chain

[ 6965  +127 ../../bgp/bgp_trie.cc ]

[ 6965   +69 ../../bgp/attribute_manager.cc ]
AttributeManager<A>::delete_attribute_list 0xc858068

[ 6965   +76 ../../bgp/attribute_manager.cc ] ** (-) ref count for 0xc858068
now 1

[ 6965   +39 ../../bgp/attribute_manager.cc ]
AttributeManager<A>::add_attribute_list

[ 6965   +55 ../../bgp/attribute_manager.cc ] ** (+) ref count for 0xc90ab58
now 3

[ 6965   +56 ../../bgp/attribute_manager.cc ] done

[ 6965   +83 ../../bgp/bgp_trie.cc ] storing route for 167.203.144.0/20 with
attributes 0xc90ab58[ 6965 +1103 ../../libxorp/ref_trie.hh ] ++ insert
167.203.144.0/20

[ 6965 +1150 ../../libxorp/ref_trie.hh ] case D:  |----.-x--|

[ 6965 +1146 ../../libxorp/ref_trie.hh ] case C:  |--x-.----|

[ 6965 +1150 ../../libxorp/ref_trie.hh ] case D:  |----.-x--|

[ 6965 +1146 ../../libxorp/ref_trie.hh ] case C:  |--x-.----|

[ 6965 +1146 ../../libxorp/ref_trie.hh ] case C:  |--x-.----|

[ 6965 +1150 ../../libxorp/ref_trie.hh ] case D:  |----.-x--|

[ 6965 +1150 ../../libxorp/ref_trie.hh ] case D:  |----.-x--|

[ 6965 +1150 ../../libxorp/ref_trie.hh ] case D:  |----.-x--|

[ 6965 +1150 ../../libxorp/ref_trie.hh ] case D:  |----.-x--|

[ 6965 +1150 ../../libxorp/ref_trie.hh ] case D:  |----.-x--|

[ 6965 +1146 ../../libxorp/ref_trie.hh ] case C:  |--x-.----|

[ 6965 +1146 ../../libxorp/ref_trie.hh ] case C:  |--x-.----|

[ 6965 +1150 ../../libxorp/ref_trie.hh ] case D:  |----.-x--|

[ 6965 +1146 ../../libxorp/ref_trie.hh ] case C:  |--x-.----|

[ 6965 +1150 ../../libxorp/ref_trie.hh ] case D:  |----.-x--|

[ 6965 +1150 ../../libxorp/ref_trie.hh ] case D:  |----.-x--|

[ 6965 +1150 ../../libxorp/ref_trie.hh ] case D:  |----.-x--|

[ 6965   +39 ../../bgp/attribute_manager.cc ]
AttributeManager<A>::add_attribute_list

[ 6965   +55 ../../bgp/attribute_manager.cc ] ** (+) ref count for 0xc90ab58
now 4

[ 6965   +56 ../../bgp/attribute_manager.cc ] done

[ 6965   +90 ../../bgp/bgp_trie.cc ]  on new chain[ 6965   +93
../../bgp/bgp_trie.cc ]

[ 6965   +69 ../../bgp/attribute_manager.cc ]
AttributeManager<A>::delete_attribute_list 0xc90ab58

[ 6965   +76 ../../bgp/attribute_manager.cc ] ** (-) ref count for 0xc90ab58
now 3

[ 6965   +80 ../../bgp/next_hop_resolver.cc ] E nexthop 24.30.219.200 net
167.203.144.0/20 requested 0x84270b8

[ 6965  +565 ../../bgp/next_hop_resolver.cc ] C nexthop 24.30.219.200
reference count incr 1

[ 6965  +711 ../../bgp/next_hop_resolver.cc ] R nexthop 24.30.219.200 net
167.203.144.0/20 requested 0x84270b8

[ 6965  +723 ../../bgp/next_hop_resolver.cc ] This registration is already
queued

[ 6965   +69 ../../bgp/attribute_manager.cc ]
AttributeManager<A>::delete_attribute_list 0xc90ab58

[ 6965   +76 ../../bgp/attribute_manager.cc ] ** (-) ref count for 0xc90ab58
now 2

[ 2008/06/02 09:57:01  TRACE xorp_bgp:6965 BGP +281 ../../bgp/peer.cc
get_message ] Peer {24.28.212.18(179) 24.30.219.207(179)}: Receive: Update
Packet

 - Next Hop Attribute 24.30.219.1

 - Origin Path Attribute - IGP

 - AS Path Attribute AsPath: [AS/65201, AS/65199, AS/65200, AS/64990,
AS/13560, AS/7843, AS/3549, AS/10026, AS/18485, AS/18880, AS/18880]

 - Local Preference Attribute - 100

 - Community Attribute 65300:1300 0xff140514

 - Nlri 198.175.161.0/24





----- Original Message ----- 
From: "Bruce M Simpson" <bms at incunabulum.net>
To: "NezLeShmil" <nezleshmil at gmail.com>
Cc: <xorp-users at xorp.org>
Sent: Thursday, June 12, 2008 10:48 AM
Subject: Re: [Xorp-users] BGP update never sent out - why ?


> Hi,
>
> I was forwarded your question.
> However, it's difficult to say what the problem could be without more
data.
>
> Can you please provide further information:
>
>  * your full XORP configuration
>
>  * the version of XORP which you are using
>
>  * the *exact* error message which you are seeing when an update is not
> sent.
>    * Have you looked at what is being sent to your BGP peers with a
> packet capture utility e.g. Wireshark?
>
>  * Also, have you compiled XORP with debugging messages enabled?
>    The messages you are seeing should not be seen otherwise.
>
> thanks!
> BMS
>
> P.S. I am not on xorp-users@ just at the moment so please Cc any replies
> to the list.
>