[c-nsp] BGP fast converge

[Christophe Devriese]

Why not just create a direct link between CE1 and CE3 ? Then use something 
with very fast convergence like is-is to distribute next-hop ip's between 
[CP]E[13] ...

If both the CE and PE are fast enough, also reducing the timers (all of them, 
according to spec) would help the failover time quite a lot.

Also, getting the switches out from between them would solve the issues.

Regards,

Christophe

On Friday 28 July 2006 15:27, Mario Velazquez wrote:
> Hi, i am having some problems in my metro network, bgp convergence is
> really a problem, i was looking arround for some fast convergence
> features like BGP Fast Peering Session Deactivation and BGP Next-Hop
> Address Tracking. this is what i have so far:
>
> a little diagram of what i have:
>
> CE1---SW1----PE1----MPLS----PE2--------CE2
> CE3---SW2----PE3                       PE4--------CE4
>
> CE1 and CE3 are in the same site, the same for CE2 and CE4, the CE-PE
> connection is bgp.
> All CE are running ospf with more or less than 6000 routes each.
> the problem is between CE1/PE1 and CE3/PE3 because when if one port
> fails in SW1/SW2 the bgp session will not be dropped until the dead
> timer expires (180s).
>
> i have this configuration in all CE
>
> outer bgp 222
> no synchronization
> bgp log-neighbor-changes
> network 20.0.0.0
> neighbor 1.1.1.1 remote-as 13591
> neighbor 1.1.1.1 ebgp-multihop 3
> neighbor 1.1.1.1 fall-over
> neighbor 3.3.3.3 remote-as 13591
> neighbor 3.3.3.3 ebgp-multihop 3
> neighbor 3.3.3.3 fall-over
> no auto-summary
>
> But nothing seems to change, in the case of a port fail in SW1 or SW2
> bgp stills wait for the peer dead timer.Is there something missing? or
> am i using the wrong feature? or i have a bad config
>
> thanks a lot
>
> Mario
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/