I have a situation where in one of my offices I have a Cisco 1751 and a Cisco Pix. The Pix has internet access and the 1751 is a T1. There is a strange situation where I need to send traffic destined for one host through the pix.
The 1751 (10.75.2.1) is the gateway in the subnet. Under normal instances all traffic goes through this 1751 box. There is a tracker that sends traffic through an IPSEC tunnel on the Pix if the T1 is down. This part all works fine I am just telling you this so you have some context.
The pix is 10.75.2.2 - I can log into that pix and ping my address I am trying to create a route for no problem (lets say 188.8.131.52). I have defined in the 1751 a route which looks like this.
IP ROUTE 184.108.40.206 255.255.255.255 10.75.2.2
And there are two additional routes in this 1751 router...
IP ROUTE 0.0.0.0 0.0.0.0 220.127.116.11 track 10 (this is the tracker we are using and means default is to go over the T1)
IP ROUTE 0.0.0.0 0.0.0.0 10.75.2.2 200 (this is the secondary route to send traffic to the PIX if the T1 is down)
My question is this... I cannot seem to get the pix to show up when I do a traceroute in the 1751 to this 18.104.22.168 address - and I cannot ping 22.214.171.124 either. If I take the route off that sends teh traffic to 10.75.2.2 then the ping works but this sends the traffic through my default gateway. I cannot understand why if the pix can ping 126.96.36.199 any my 1751 gateway has a route to get to 188.8.131.52 it needs to go to the pix - that my 1751 cannot ping the 184.108.40.206 address...
Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.