lostjay
02-01-07, 09:46 AM
Hi all,
I'm in the process of altering a point-to-point connection between our main data center and remote web farm - trying to make it work bi-directionally. Currently, it's only used to push data out. I want the servers to report alarms back.
The T-1 is unnumbered and there's going to be a pair of these pipes when it's all done. We used a Cisco sample configuration paper for "Inverse MUX application using Multilink PPP" to set this up.
The link is working fine for pushing data to the remote, but currently we can't get anything back from there. And we don't understand why.
If I go to the remote site physically, I can ping and traceroute to the data center's router. I cannot ping or trace to any machine on that network. Oddly enough, if I login to that router, I can successfully ping or trace to any machine on that network and beyond including some known DNS servers out on the internet.
The data center router has its FastEthernet0/0 interface at 12.191.53.49, its Serial/0/0/0 interface is at 192.168.1.1 and we have tried both static and dynamic (RIPv2) route configurations to the 12.0.0.0 network. At last look with RIPV2 routes, show ip routes said:
Gateway of last resort is 12.191.53.1 to network 0.0.0.0
R 10.0.0.0/8 [120/1] via 192.168.1.2, 00:00:04, Virtual-Access2
12.0.0.0/24 is subnetted, 1 subnets
C 12.191.53.0 is directly connected, FastEthernet0/0
192.168.1.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.1.0/24 is directly connected, Loopback0
C 192.168.1.2/32 is directly connected, Virtual-Access2
S* 0.0.0.0/0 [1/0] via 12.191.53.1
The reference to the 10.0.0.0/8 network refers to the Remote router's network. And that one seems to work fine.
So, I do not understand why nothing passes through this router from the serial interface to the 12.191.53.0 network at the data center. When I traceroute back from the remote, everything dies at 192.168.1.1. Have I missed something major?
TIA,
Jay
I'm in the process of altering a point-to-point connection between our main data center and remote web farm - trying to make it work bi-directionally. Currently, it's only used to push data out. I want the servers to report alarms back.
The T-1 is unnumbered and there's going to be a pair of these pipes when it's all done. We used a Cisco sample configuration paper for "Inverse MUX application using Multilink PPP" to set this up.
The link is working fine for pushing data to the remote, but currently we can't get anything back from there. And we don't understand why.
If I go to the remote site physically, I can ping and traceroute to the data center's router. I cannot ping or trace to any machine on that network. Oddly enough, if I login to that router, I can successfully ping or trace to any machine on that network and beyond including some known DNS servers out on the internet.
The data center router has its FastEthernet0/0 interface at 12.191.53.49, its Serial/0/0/0 interface is at 192.168.1.1 and we have tried both static and dynamic (RIPv2) route configurations to the 12.0.0.0 network. At last look with RIPV2 routes, show ip routes said:
Gateway of last resort is 12.191.53.1 to network 0.0.0.0
R 10.0.0.0/8 [120/1] via 192.168.1.2, 00:00:04, Virtual-Access2
12.0.0.0/24 is subnetted, 1 subnets
C 12.191.53.0 is directly connected, FastEthernet0/0
192.168.1.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.1.0/24 is directly connected, Loopback0
C 192.168.1.2/32 is directly connected, Virtual-Access2
S* 0.0.0.0/0 [1/0] via 12.191.53.1
The reference to the 10.0.0.0/8 network refers to the Remote router's network. And that one seems to work fine.
So, I do not understand why nothing passes through this router from the serial interface to the 12.191.53.0 network at the data center. When I traceroute back from the remote, everything dies at 192.168.1.1. Have I missed something major?
TIA,
Jay