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

BGP Multihoming

Multihoming our internet connection to 2 different ISPs. Packets are coming in through both ISPs as I cannot control their routes.

Question is, in general and on average, how fast do the Internet BGP tables converge if one of my links to either ISP goes down?

For example, if incoming routes are coming through ISP1 and its link goes down, how long will it usually take for all incoming traffic to be redirected to ISP2?




Re: BGP Multihoming

It will take at least 3 minutes for the neighbors to go down .

Say your linke to ISP one goes down it will take 3 minutes for BGP to drop, Now when the link goes down there is no gaurentee that routes you are learning from ISP 1 will be advertiesed by ISP 2 . What you can do is configure default routes on both rotuers with an admin distance of 250 , this way if one link drops and there is no route then traffic will always be fowarded out one of the links

ip route nexthopIP 250


Re: BGP Multihoming

It's actually going to depend, as well, on how the BGP session is set up to the provider. If you're using bgp fast-external-fallover, and you are peering with the directly connected interfaces over a point-to-point of some type (not using eBGP multihop), then when the interface fails, the BGP session will fail.

Other than this, you could also set your BGP timers very low, if you're willing to incur the extra cost in TCP keep's, and the ISP's are willing to play along.



Re: BGP Multihoming

In addition to the amount of time required for ISP1's router to detect that your circuit is down and stop advertising your routes (adjustable by BGP timers as mentioned), it also takes time for this change to propagate across the Internet. Routes to your network via ISP1 have to be withdrawn on Internet BGP routers, and the routes via ISP2 have to be added. This should normally take on the order of a minute or two, though it can take longer for certain networks to receive the updates due to busy routers, and other factors.

CreatePlease to create content