Danny, With iBGP the timers for BGP are not really important... You actually need to worry about the IGP convergence. The reason for that is that usually when a link fails, you don't really expect the BGP session to the RR to go down, but just use the redundant IGP path.
Some other features you may check out: BGP Support for Fast Peering Session Deactivation http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps1829/products_ feature_guide09186a00802a6d4f.html BGP Support for Next-Hop Address Tracking http://www.cisco.com/en/US/partner/products/ps6350/products_configuratio n_guide_chapter09186a008045561e.html The above features are much better than just changing timers, as they are based on even triggers coming from IGP and not polling with keepalive messages. Arie -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Danny Sent: Saturday, May 26, 2007 22:11 PM To: [email protected] Subject: [c-nsp] [Query] Bgp Session timers Hello all , We are running a ISP with cisco boxes around 30 GSRs on the geography . The boxes are on RR IBGP hireachial architecture Can you guys suggest the best practices hold down and keepalive timers you set for the IBGP sessions on your ISP network ??? . Due you lower down the timers for ebgp with your peers and transits too ?? Regards Danny Imbroglio Communique , Inde _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
