[c-nsp] BGP routes co-existing with different local-preference

Bruce Pinsky bep at whack.org
Tue Oct 25 13:17:42 EDT 2005


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rubens Kuhl Jr. wrote:
>>Upon further investigation, it seems that the BGP session with the
>>router that went down took it's time to time out, which meant the
>>former best routes stayed for some time.
> 
> 
> Upgrading to 12.0(29)S or later would give you "BGP Fast Peering
> Session Deactivation":
> 
> "The BGP Support for Fast Peering Session Deactivation feature
> introduces an event driven notification system that allows a Border
> Gateway Protocol (BGP) process to monitor BGP peering sessions on a
> per-neighbor basis. This feature improves the response time of BGP to
> adjacency changes by allowing BGP to detect an adjacency change and
> deactivate the terminated session in between standard BGP scanning
> intervals. Enabling this feature improves overall BGP convergence."
> 

Which shouldn't be required if you are running a version that supports BGP
Next Hop tracking and use an IGP to propagate next hops to neighboring routers.


- --
=========
bep

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)

iD8DBQFDXmi2E1XcgMgrtyYRAnxgAJ0dyHBYVbCYbMu5inht10lRK+CVvQCg21FL
06ik2TNx6EQMaXvl4IPiWpw=
=x6Qq
-----END PGP SIGNATURE-----


More information about the cisco-nsp mailing list