Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 
Community Member

BGP Conversion Time


Has anyone can tell me the convergence time for BGP. Basically, I have 2 CEs on redundancy. However, I find that the time taken to failover from primary to secondary link took 22secs. Is this a normal timing taken for conversion over MPLS on BGP?


Re: BGP Conversion Time


the time could even be worse. eBGP takes up to 30 seconds to announce an update, iBGP up to 5 seconds. So you could get a convergence time of over a minute (2x eBGP + iBGP).

To reduce this use the command "neighbor advertisement-interval"

You can also improve convergence time using BFD: "Decreasing BGP Convergence Time Using BFD"

Or by adjusting timers with "neighbor timers"

You might want to investigate the convergence time improvement by adjusting the scan interval. This might be, however, somewhat risky in that it could lead to less stability, if the interval is choosen too small and the CPU load generated is too high. So use with care.

Hope this helps! Please rate all posts.

Regards, Martin

Re: BGP Conversion Time

Hi ,

I think you have set the hold timer to 20 sec , and the convergence time of 22 sec is normal and its fine for the router's cpu and memory rather than trying to play with the timers.

Pls let us know if you have tried to reduce the timers and router's cpu is also fine.


vanesh k

Re: BGP Conversion Time

Hi Vanesh,

unfortunately your conclusion is not so straight forward. BGP sends triggered updates. So in principle you could a convergence time of few seconds only. However the situation is more complicated, because many timers are involved. A single measurement with no description of the precise settings does not allow for a conclusion which timer is set to which value. Even with all timers at default values you CAN get 22 sec.

Regards, Martin

Re: BGP Conversion Time


in addition to the other posts, and provided you run at least IOS 12.3(14)T, you might want to try the command 'neighbor x.x.x.x fall-over', which introduces a feature called fast peering session deactivation. Basically, when this feature is enabled, 'adjacency changes are detected, and terminated peering sessions are deactivated in between the default or configured BGP scanning interval.'

This might speed up the convergence...



Re: BGP Conversion Time

Hi Martin,

I think the post was about redundancy for the CE's .And there is no use of triggered updates as my BGP would go down on primary path and PE would note about the down state after the hold down time , thats why I said 20sec and once PE has confirmed abt the invalidity then comes the triggered updates between the PE routers for the fallback to happen and this may vary from 1 to 5 sec ...

pls correct me if anything is wrong.


vanesh k

CreatePlease to create content