[c-nsp] Connected routes / Static routes advertised to RR's

[CiscoNSP List]

Just an update to this - the "match protocol static" didnt fix the problem, but adding "next-hop-self" to peer policy did....I dont know if both were required (Only had limited time to test)....but static routes on the RR-client are now working, as the next hop is now the loop of the rr-client.


Thanks to all who replied...and if anyone could confirm if "both" conf additions are necessary, or if just "next-hop-self" is, it would be greatly appreciated (I wont have access to the routers until tomorrow to test to see if they are both needed)



Cheers!


________________________________
From: cisco-nsp <cisco-nsp-bounces at puck.nether.net> on behalf of CiscoNSP List <CiscoNSP_list at hotmail.com>
Sent: Thursday, 30 June 2016 7:45 AM
To: Oliver Boehmer (oboehmer); Nick Hilliard
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Connected routes / Static routes advertised to RR's

Thanks Oliver - Yes, we do have selective next-hop tracking...another list member e-mailed me directly re this also...so statics need to be redistributed with the loop of the rr-client it resides on


I do have redistribute static in bgp, and the loop range is in the PL for redist static....and also a route-map for nexthop:


#rr-client

 address-family ipv4
  bgp additional-paths select best-external
  bgp additional-paths install
  bgp nexthop route-map BGP_NHT
  bgp nexthop trigger delay 0
  redistribute connected route-map LOCAL_RANGES
  redistribute static route-map LOCAL_RANGES
  neighbor xxx.xxx.76.212 activate
  neighbor xxx.xxx.76.212 inherit peer-policy TO_RR
  neighbor xxx.xxx.76.212 route-map FROM_GC_RR in
  neighbor xxx.xxx.76.212 route-map TO_GC_RR out
  neighbor xxx.xxx.76.213 activate
  neighbor xxx.xxx.76.213 inherit peer-policy TO_RR
  neighbor xxx.xxx.76.213 route-map FROM_GC_RR in
  neighbor xxx.xxx.76.213 route-map TO_GC_RR out

route-map BGP_NHT permit 10
 match ip address prefix-list PL_NGN_LOOPBACKS
 match source-protocol ospf 100
route-map BGP_NHT permit 20
 match source-protocol connected

So to advertise statics with the loop of the rr-client, I would need to add (And on all other rr-clients)

route-map BGP_NHT permit 30
 match source-protocol static

And clear bgp session with RR I assume (I havent tried the above, no access to the routers atm)

NB - route-map LOCAL_RANGES includes a PL with all our ip prefixes (Including all our rr-clients Loop IP's)


________________________________
From: Oliver Boehmer (oboehmer) <oboehmer at cisco.com>
Sent: Wednesday, 29 June 2016 9:19 PM
To: Nick Hilliard; CiscoNSP List
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Connected routes / Static routes advertised to RR's

Nick wrote:
> CiscoNSP List wrote:
> > Static route to that prefix on the RR-client, shows as "no best path"
> > as the 79.106 prefix is "inaccessible"?  but as above, it is
> > accessible and I can ping it? (So the static is not advertised to any
> > other RR-clients):
>
> you'd make it a lot easier for people to see what was going on if you
> used rr# and client# for the prompts, as appropriate.
>
> What does "show ip route xxx.xxx.79.106" look like on the client?


In addition, can you please include your RR BGP config? The next-hop is visible via a /30 route. Do you have selective next-hop tracking configured with route-map limit next-hops to /32s or something else which would require next-hops to be /32?

        oli


_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
cisco-nsp Info Page - puck.nether.net<https://puck.nether.net/mailman/listinfo/cisco-nsp>
puck.nether.net
To see the collection of prior postings to the list, visit the cisco-nsp Archives. Using cisco-nsp: To post a message to all the list members, send ...



archive at http://puck.nether.net/pipermail/cisco-nsp/