Please forgive my utter lack of BGP knowledge. I am new to the networking world, and even moreso, the BGP world.
We are having an issue where one of our ISP routers can ping both google.com and 188.8.131.52, but the other can only hit google.com and not 184.108.40.206.
In my troubleshooting I noticed that the working router has a proper next hop to the isp when pinging both name and ip. The non working router's next hop is the working router's ip when attemping 220.127.116.11. When pinging google.com from the non working router, it does have its proper next hop of the isp it is connected to.
I further verified that when executing sh ip bgp, that the non working router shows a *>i for 18.104.22.168 to the working router's interface, whereas the working router shows the proper *> for 22.214.171.124 to its isp connection.
So as I understand it, the non working router is learning incorrect BGP routes? Not sure what else I should be looking for, so any assistance is appreciated.
To assist you further can you post or explain how your routers are connected to each other, your network and the isps
Hi Paul. Thanks for the reply. They are directly connected on their g0/2 interfaces via ospf. The router that cannot hit 126.96.36.199 is connected to Century Link, and the one that can is connected to Level 3.
In your iBGP configuration, do you have "next-hop-self" set on both sides?
Also, Google.com for me resolves to 188.8.131.52 (right now) as opposed to their public DNS of 184.108.40.206 and 220.127.116.11.
I suspect that if you are using RFC1918 between your routers (we do that as well) that your source IP is the interface that is cross-connected across to the working router.
Some more information as @paul driver suggested will also be helpful.
Hi Tim. Thanks for the reply. Yes, next hop self is configured as the other router on each router. On the router that cannot ping 18.104.22.168, it can ping 22.214.171.124. Seems odd that it would learn the router for 126.96.36.199/9 as going through the other router.
You suspected right. When tracerouting to 188.8.131.52 from the router that cannot ping it, it does have the source as the interface that cross connects the two.
Just to add your non working router is not necessarily learning incorrect routes unless you want everything to go via the directly connected ISP.
It probably just means that as far as your non working router is concerned the better path to 184.108.40.206 is via the other router, better path being determined by the BGP best path algorithm.
So it may or may not be an issue depending on what exactly you want in terms of traffic paths.
Hi Jon. Thanks for the reply. Definitely understood as far as that logic is concerned. Then my question is why the router still cannot ping 220.127.116.11. If it goes to the other router, that is fine, but I am not understanding where it is getting hung up that it cannot get through the router that can ping 18.104.22.168.
Can you post a topology for clarity and if possible a configuration of both routers