Core Issue
The next hop specified is invalid.
Resolution
Since the route exists in the Border Gateway Protocol (BGP) table, but not in the routing table, the problem is probably caused by one of these options:
- If the route in question is an internal BGP (iBGP) derived route, it is possible you have a synchronization problem. To resolve this issue, turn off the synchronization.
To learn more about synchronization, refer to the Synchronization section of BGP Case Studies.
- If the route in question is either an iBGP or an external BGP (eBGP) derived route, it is possible that the next hop address listed for the route does not exist in the routing table.
To confirm this, issue the show ip route x.x.x.x command output, where x.x.x.x is the next hop address. In this case, it is necessary to establish a route to the next hop, either statically or dynamically.
For an example of this type of problem, refer to the Practical Design Example section of BGP Case Studies.
Valid Route to BGP Next Hop
Valid route to next hop does not exist
show ip bgp {network mask}
Prefix / network exists, learned by eBGP NOT marked received only
Prefix / network exists, learned by iBGP NOT marked received only
