I have a provider edge router that is vrf aware using eBGP to link the MPLS network together. This provider edge connects to one of our core routers. The core is connected to another core which uses iBGP to connect the MPLS network.
When I do a show route on the provider edge- it shows the next hop as the route for the subnets. I can also ping this hop thru the vrf.
However, from the remote core side (iBGP) it shows the provider edge as the next hop, and cannot ping that throught the vrf. Thus, sites connected to the remote core cannot see the ones connected to the provider edge, even though the routes are all in place, with the exception of this hop issue.
I am told that this is an iBGP issue- but do not know how to resolve it. Any ideas?
It sounds like you either have to redistribute the IP of the next hop into your IGP or configure next hop self on your edge router. Assuming that the route is in teh bgp table it is not being installed in the routing table becauase the next hop is not reachable.
1. Introduction Internet security is important with the increasing
attacks that are happening every day. Many internet and browsing
security solutions exist, but some are not very easy to use or maybe the
question is how can I enable them? In this referen...
Cisco Software Manager Server API Guide This document describes the
programmatic interfaces, RESTful APIs, which are supported by Cisco
Software Manager Server (CSM Server). Overview CSM Server supports a set
of finite RESTful APIs. The first step to use ...
If you are using Cisco's new linux-based Cisco Software Manager server,
then you probably want to make sure there is a startup service for
it.I'll assume that you've already installed the CSM server on a
systemd-based linux system. The commands given belo...