Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Can traceroute, but I can't ping?

Attached is a view of the topology. What the topoology doesn't show is there are also two PVCs connecting R3->R2 and R1->R4. Each interface on these diagnals have IP 10.1.100.X; where X is the router number. This may be familiar to some because it is the lab topology from the courses. All routers (except SW1) are set up with multipoint subinterfaces configured as point-to-point links. I am attempting to ping SW1's loopback from R2. Here's the bizzare thing, I can traceroute from SW1 to 10.1.100.2, but I can't ping it! Output shown below:

SW1#traceroute 10.1.100.2

Type escape sequence to abort.

Tracing the route to 10.1.100.2

  1 10.1.101.1 12 msec

    10.1.103.3 16 msec

    10.1.101.1 8 msec

  2 10.1.100.2 28 msec

    10.1.100.4 24 msec

    10.1.100.2 28 msec

SW1#ping 10.1.100.2

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.1.100.2, timeout is 2 seconds:

.....

Success rate is 0 percent (0/5)

I have also attached the configs. I skipped R4 because I could only upload 5 files. Let me know if you need it. I'm sure I've misconfigured something, but I'm not sure what. For some reason, GNS3 isn't showing the changes until I close down the project. I'm no longer running EIGRP; all routers are confirmed to be running OSPF on all interfaces in area 0.

2 REPLIES
New Member

Re: Can traceroute, but I can't ping?

Oh, and ping works from R4 to the 192.168.1.99 address and it also works from R2 if I remove the s1/0.2 interface on all devices.

New Member

Can traceroute, but I can't ping?

Ping is funny. Make sure you are sourcing the ping as well.

411
Views
0
Helpful
2
Replies
CreatePlease login to create content