BGP and MPLS Issue

Unanswered Question
Jul 10th, 2007

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?

Greg

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
keegan.holley Sat, 07/14/2007 - 15:59

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.

gregwoodson Mon, 07/16/2007 - 05:11

This issue has been resolved. It was a combination of neighbor next-hop configs as well as ospf distribution.

Thanks!

Actions

This Discussion