Here is the scenario. I have 2 data centers miles apart. They are on a Paetec MPLS. I have a Lightower point to point Ethernet link between the two data centers as well. At data center A, I have a Paetec managed router (192.168.2.1). The subnets behind that router are 192.168.2.0, 192.168.100.0 and 192.168.101.0. I also have a Cisco 1841 that is configured with fa0 addressed as 192.168.2.250 and fa1 as 10.5.5.1. Fa1 is the one end of the point to point Ethernet link to data center B.
At data center B, I have a Paetec managed router (10.0.2.1). The subnets behind that router are 10.0.2.0, 10.0.100.0 and 10.0.101.0. I also have a Cisco 1841 that is configured with fa0 addressed as 10.0.2.250 and fa1 as 10.5.5.2.
What I want to happen is any traffic headed from data center A destined for 10.0.100.0 or 10.0.101.0 to be routed through the point to point Ethernet link. I had Paetec add routes in their managed router to route any traffic headed for 10.0.100.0 and 10.0.101.0 to my Cisco 1841 (192.168.2.250).
I wanted to do the same for traffic destined for 192.168.100.0 and 192.168.101.0 from data center B. Paetec added the appropriate routes to the router at data center B.
Now, if I trace from data center A to 10.0.100.45, I see this:
1 <1 ms <1 ms <1 ms 192.168.2.1
2 <1 ms <1 ms <1 ms 192.168.2.250
3 4 ms 4 ms 4 ms 10.5.5.2
4 3 ms 3 ms 3 ms 10.0.2.1
So the routing seems to be ok. However after it hits 10.0.2.1, it gets lost after that.
Am I missing something? Is this a misconfiguration on Paetec’s routers?
I am attaching the configuration for the 1841 in Data Center A