[c-nsp] RTBH - anyone using this?

[Matyas Koszik]

You need to add disable-connected-check to the peer's bgp configuration.
(I know the documentation doesn't say so but that's what makes it work for me.)


On Tue, 22 Jan 2008, Drew Weaver wrote:

> I’m following this guide:
>
> http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6586/ps6642/prod_white_paper0900aecd80313fac.pdf
>
> if anyone knows of a better one please do enlighten me â˜ş
>
> Everything works a lot better than I imagined it would except for one issue and one question.
>
> Question: There is simply no reason to be exporting the routes from the edge routers to the triggers if I am reading this document correctly. Rather than using prefix or filter lists, is there a handy way to make the edge routers not send routes to the trigger server (using a command in that peer-group?)
>
> The issue I am having is kind of strange and I’ve never ran across it before like many of my issues‌..
>
> RTBH has you add a static route on the edge routers which acts as a next-hop for the routes which are sent by the trigger server/router. For whatever reason the routes sent by the trigger server/router aren’t being entered into my routing table on the Edge routers because it is giving me RIB failures:
>
> LAB01#sh ip bgp nei 10.1.0.11 routes
> BGP table version is 476702490, local router ID is 10.1.0.9
> Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
>               r RIB-failure, S Stale
> Origin codes: i - IGP, e - EGP, ? - incomplete
>
>    Network          Next Hop            Metric LocPrf Weight Path
> r>iblocked/28
>                     192.0.2.1                0    200      0 i
>
> LAB01#sh ip route 192.0.2.1
> Routing entry for 192.0.2.1/32
>   Known via "static", distance 1, metric 0 (connected)
>   Tag 50
>   Redistributing via ospf 1
>   Routing Descriptor Blocks:
>   * directly connected, via Null0
>       Route metric is 0, traffic share count is 1
>       Route tag 50
>
> Clearly there is a route to 192.0.2.1 with a destination of Null so it does appear to be a valid route, yet bgp refuses to add the “blocked/28” route to the routing table.
>
> Has anyone ran into this before?
>
> Thanks!
>
> -Drew
>
> _______________________________________________
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/