09-30-2006 03:49 PM - edited 03-03-2019 05:19 AM
RouterB,EIGRP 100
s0:152.1.1.1/16
Lo:1.1.1.1/24
no auto-summary]- connected to V35---
[s0/0 RouterA,Lo:2.2.2.2/24,EIGRP AS 100, OSPF Area0, s0/1]/
--- connected to---
[s0/0:192.168.15.2/24
RouterC, OSPF 200,
Area 1]
As you can see in the show ip route from RouterC below, I am able to see a route for 1.1.1.0/24. It is an EIGRP AS redistributed into OSPF.
However, I ping '1.1.1.1' from RouterC, but it times out. Why can't I get to 1.1.1.1 from RouterC ?!
RouterC# Show ip route
1.0.0.0/24 is subnetted, 1 subnets
O E2 1.1.1.0 [110/1000] via 192.168.15.1, 00:04:06, Serial0/0
O E2 152.1.0.0/16 [110/1000] via 192.168.15.1, 00:06:12, Serial0/0
2.0.0.0/32 is subnetted, 1 subnets
O IA 2.2.2.2 [110/65] via 192.168.15.1, 00:06:19, Serial0/0
3.0.0.0/24 is subnetted, 1 subnets
C 3.3.3.0 is directly connected, Loopback0
C 192.168.15.0/24 is directly connected, Serial0/0
RouterC#ping 1.1.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Solved! Go to Solution.
09-30-2006 05:57 PM
Hi,
You probably do not have a route to 192.168.15.0/24 on RouterB. Are you redistributing OSPF into EIGRP? The return traffic may be the problem here.
If you still have problems, post Router A's configuration.
HTH
Sundar
09-30-2006 05:57 PM
Hi,
You probably do not have a route to 192.168.15.0/24 on RouterB. Are you redistributing OSPF into EIGRP? The return traffic may be the problem here.
If you still have problems, post Router A's configuration.
HTH
Sundar
09-30-2006 06:38 PM
I agree with Sundar that since the route appears in the routing table that you probably do have a viable path to get to 1.1.1.0 and that the problem is most likely lack of a return path.
One way to verify this would be to run debug ip icmp on the router that you are attempting to ping and then do the ping again. If the debug output shows that the ping packets are being received then you have verified that the problem is with the return path.
HTH
Rick
09-30-2006 11:52 PM
You guys rule. That was it.
I simply put a static route on RouterB;
'ip route 192.168.1.0 255.255.255.0 152.1.1.2' and now the packets know the way back to RouterC.
By the way if you think the static route above is the cleanest way to get this solved ?
10-02-2006 09:34 AM
I'm assuming you're doing mutual redist on routerA. RouterB don't have a route to get back to routerC. Check redist configs on routerA. Do this on both routerA and B: "deb ip icmp" and try again after you fix the routing table on B.
10-02-2006 12:36 PM
In reality I was doing a one-way redistribution. But I understand your point, if I don't do the two-way redistribution, then the other option is to create a static route on RouterB so the traffic will know how to get to RouterC, as I've done. Thanks !
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: