[c-nsp] IBGP route stays stuck

[Pete Lumbis]

Perhaps when the floating static kicks in on PE2 the weight will be 32768,
most likely making it the best route in the BGP table, causing it to
advertise to PE1? I've seen similar configurations run into this. If this
is your issue the solution is a route-map on the redistribution statement
setting the weight to 0

On Wed, Oct 22, 2014 at 2:30 AM, Pasquino Andrea <andrea.pasquino at eng.it>
wrote:

> Hello,
>
> This is the scenario:
>
> I have PE1 and PE2 in AS100
> PE1 has an EBGP peering with AS200 and receives a certain prefix a.b.c.d
> with LP=222
> The same prefix a.b.c.d is redistributed on PE2 with LP=33 from a floating
> static route, and serves as a back-up route
>
> Now here's what happens: if for some reason AS200 stops announcing prefix
> a.b.c.d, then the announcement from PE2 kicks and we are happy (back-up
> runs fine)
>
> When  AS200 starts again announcing prefix a.b.c.d, then the announcement
> from PE2 does not get flushed from PE1 and PE2. We have to erase the "ip
> route vrf blahblah" command and rewrite it
>
> Have you any clues ?
>
> Andrea
>
> _______________________________________________
> 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/
>