I have a provider edge router (PE) that is connected to a core router (core1) via eBGP. Core1 is connected to Core2 via IGP. A VRF was configured between PE and Core1 for a customer. We now have to extend that VRF to core2. When the configuration is put in, BGP works normally on the circuit, but the eBGP learned next-hop (PE) is shown as the next hope for routes on Core2, which cannot contact that router over the VRF.
Based on Cisco's configuration for eBGP and iBGP using next-hop-self, I tried to apply that via a neighbor statement within the vrf. Im now getting duplicate routes with change the vrf's route every minute or so. And Im not able to pass the traffic, which was the problem in the first place.
Attached are the configs for both the Core1 and Core2 routers, as well as the ip bgp vpnv4 vrf CustomerA statement from Core2 showing the weighted but duplicated routes.
Any help on a better way to do this would be appreciated.
This whole problem might be simpler due to this. From Core2, I cannot ping 10.0.1.1 from within the VRF. If I could do that, I could apply the neighbor next-hop-self on the main address family and solve this issue.
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...