From: Erhan Kurt (kurt@xxxxxxxxxxxxxxx)
Date: Thu Jun 06 2002 - 08:57:52 GMT-3
As far as I know, no way to reduce..
Folks,
Not for this question but to save time in BGP, how about using neighbor
soft-reconfiguration inbound?
Erhan
-----Original Message-----
From: Khurram Khani [mailto:kkhani@nortelnetworks.com]
Sent: 05 Haziran 2002 Gar:amba 00:48
To: ccielab@groupstudy.com
Subject: BGP: Delay in sending UPDATE Packet by Source Router
Hi,
When I try to advertise/withdraw route from BGP. I notice that the Source
Router sends the BGP UPDATE packet after around 35sec to 37secs of issuing
the command in router bgp. For example when I try to do
router bgp xx
redistribute connected metric 1 <--- I add this command
After pressing the Enter , I see that UPDATE packet is sent after around
35secs by BGP process. How can I reduce this time?? and why BGP process is
waiting this long to send the update?
Similarly when I try to withdraw routes using
no redistribute connected
I see the same in sending out the UPDATE packet again to the neighbours, Any
thoughts?
help apprecaited
Thanx
Khurram Khani.
R2-2509(config-router)#no redistribute connec R2-2509(config-router)#
<--- around 35 secs delay here --->
BGP: scanning routing tables
BGP: nettable_scan: invalidate sourced path for 2.0.0.0/8
BGP: no valid path for 2.0.0.0/8
BGP: nettable_scan: invalidate sourced path for 134.177.0.0/16
BGP: no valid path for 134.177.0.0/16
BGP: nettable_walker 2.0.0.0/255.0.0.0 no best path selected
BGP: nettable_walker 134.177.0.0/255.255.0.0 no best path selected
BGP: 10.10.10.1 computing updates, neighbor version 26, table version 28,
starting at 0.0.0.0
BGP: 10.10.10.1 send UPDATE 2.0.0.0/8 -- unreachable
BGP: 10.10.10.1 send UPDATE 134.177.0.0/16 -- unreachable
BGP: 1 updates (average = 28, maximum = 28)
BGP: 10.10.10.1 updates replicated for neighbors : 134.177.211.200,
134.177.214.201
BGP: 10.10.10.1 1 updates enqueued (average=28, maximum=28)
BGP: 10.10.10.1 update run completed, ran for 4294967292ms, neighbor version
26, start version 28, throttled to 28, check point net 0.0.0.0
BGP: 134.177.211.5 computing updates, neighbor version 26, table version 28,
starting at 0.0.0.0
BGP: 134.177.211.5 send UPDATE 2.0.0.0/8 -- unreachable
BGP: 134.177.211.5 send UPDATE 134.177.0.0/16 -- unreachable
BGP: 134.177.211.5 1 updates enqueued (average=28, maximum=28)
BGP: 134.177.211.5 update run completed, ran for 8ms, neighbor version 26,
start version 28, throttled to 28, check point net 0.0.
This archive was generated by hypermail 2.1.4 : Tue Jul 02 2002 - 08:12:26 GMT-3