[c-nsp] iBGP and redistributing full table to RR...no best path?

[CiscoNSP List]

Ok - Ive worked out why the routes were not being installed...was due to my inbound route map on the RR...I had it configured to only accept a certain community tag (That was added in the eBGP peering session on the ASR1006).

...so, is there anyway to maintain the community tags that I add ingress with our eBGP peering sessions, when I re-advertise via iBGP, or must I re-tag ingress on the RR in iBGP?
 

> From: cisconsp_list at hotmail.com
> To: cisco-nsp at puck.nether.net
> Date: Mon, 19 Jan 2015 05:47:30 +1100
> Subject: [c-nsp] iBGP and redistributing full table to RR...no best path?
> 
> Hi Everyone,
> 
> I've setup a test iBGP session from an edge router(ASR1006) -> an RR (ASR1001), and filtered the advertisements from ASR1006->RR to only being from one of our upstreams via matching a community tag.
> 
> Session comes up, all the correct routes are "advertised" to the RR, but I see "no best path" due to the next hop being "inaccessible"....which makes sense...the RR doesnt know about the next hop being advertised to it from the ASR1006.
> 
> So, I tried adding "next hop self" to ASR1006 for neighbour ASR1001(RR) - This updated all the routes with the loop IP of the ASR1006, and the ASR1001 has a route for this IP(And can reach it), but, the routes are still not being installed due to "no best path"? (The next hop being "inaccessible" is no longer being reported).
> 
> All the routes received from this iBGP session, only have one path available, the RR can reach the next hop(It is peering via this IP), but it still reports each route as "no best path"?
> 
> Any help would be greatly appreciated.
> 
> Cheers. 		 	   		  
> _______________________________________________
> 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/