This is no different than with a regular (non-vrf) BGP environment. The next-hop is not changed by the RR and the RR clients have to have a route in the RIB to resolve the BGP next hop for the route to be considered valid by BGP.
People usually configure nexthop-self on the RR clients or redistribute the access link IP addresses into the IGP so that the BGP next hop resolution takes place properly.
Hope this helps,
Harold Ritter Sr. Technical Leader CCIE 4168 (R&S, SP) email@example.com México móvil: +52 1 55 8312 4915 Cisco México Paseo de la Reforma 222 Piso 19 Cuauhtémoc, Juárez Ciudad de México, 06600 México
I'm a little confuse, but OK. I have configured loopback interface in IGP, of course that the problem was fixed, but the next-hop value was not changed, after this I have configured PBR to change next-hop, and it works fine.
Introduction: The "external-out enable" command is available for
configuration under the "router ospf process" in case of the IOS-XR
operating system. This command basically enables advertisement of
intra-area routes on the device as external routes in th...
Introduction Basic configuration for netflow Scale parameters for
netflow Netflow support Architecture Packet flow for netflow Inside the
LC CPU Netflow Cache size, maintenance and memory Sample usage Cache
Size Aging Permanent cache Characteristics Which...