three out of four is not bad, but I need them all

[julian]

Hi Gang,

I am reposting this with more detail. I am a newbie and so far you all have been a big help. I have two 1841 routers handling my point to point private line.

The routers connects two subnets at each office to the other locations end points.

Router One has our LAN which is 10.33.0.0 255.255.252.0 and our SAN which is 192.168.0.0 255.255.255.0

Router Two is our branch office and hosts LAN 10.33.4.0 255.255.255.0 and SAN 192.168.1.0 255.255.255.0

Right now, router one can ping across the P2P WAN and gets replies from both 10.33.4.0 and 192.168.1.0. This is the behavior I want.

Router Two can ping 10.33.0.0 but can not reach the 192.168.0.0 subnet. I need to establish this so I can replicate our SAN between the two sites.

I am attaching the two configurations for your review.

Again, I need to be able to have each site access the two subnets on the other side of the WAN P2P going in both directions.

Please help, everything looks good to me but only three of the four routes are working.

[Richard Burts]

Julian

Thanks for providing some more detail. Based on what is in the configs it looks to me like it should be working. But you say that it is not, so we will look further. Would you post the output of show ip route on both routers? Perhaps that will give us a clue.

I also would like to see the output of show ip interface brief from both routers. It occurs to me that one thing that could produce the behavior that you describe is if the FastEthernet0/1 of router 1 were protocol down, or interface down, or shutdown. So lets verify the state of all interfaces.

I do have a few observations and suggestions, though I am not sure that any of them are the answer to the problem.

- both routers have permanent static routes for the connected networks. These are not needed because a connected interface will always be put into the table. Lets try removing the static routes to the routers own interfaces.

- I see that router 1 has some NAT configuration but does not have NAT inside or NAT outside. Lets remove the line:

ip nat inside source list 1 interface Serial0/0/0 overload

and remove access-list 1

- there is a named access list WAN which is defined but I do not see it applied. Lets remove that access list.

- I am not sure why the static routes are all coded as permanent. This is kind of unusual but I do not see that it hurts anything.

HTH

Rick

[jackyoung · Accepted solution]

I suggest to simplfy the configuration as below :

Router 1 :

Remove

ip route 10.33.0.0 255.255.252.0 FastEthernet0/0 permanent

ip route 192.168.0.0 255.255.255.0 FastEthernet0/1 permanent

Router 2 :

ip route 10.33.4.0 255.255.255.0 FastEthernet0/0 permanent

ip route 192.168.1.0 255.255.255.0 FastEthernet0/1 permanent

There is no need to define the static route which is the local interface subnet.

Check the default gateway of the SAN in router 1 side is pointing to the router 1's LAN, i.e.192.168.0.254/24

If the problem still exist, do a trace route and please show us the result.

Please advise us the test result.

Hope this helps.

[julian]

Thanks Jack,

Your recommendation to check the SANs gateways did the trick. I deleted the local routes as well but as soon I placed a gateway on the SAN boxes my pings completed.

You have saved the day!

[jackyoung]

You're welcome. It is good that it solved your question. We come to here is to share knowledge. Happy Networking. ;)