why traceroute lost ,ping is ok

[topnewinfo]

Interface              IP-Address      OK? Method Status                Protocol

GigabitEthernet1/1     10.0.60.5       YES NVRAM  up                    up     

GigabitEthernet1/2     10.0.60.29      YES manual up                    up   

GigabitEthernet1/3     unassigned      YES NVRAM  down                  down   

GigabitEthernet1/4     unassigned      YES manual down                  down   

GigabitEthernet1/5                            YES NVRAM  down                  down   

GigabitEthernet1/6                            YES manual administratively down down   

GigabitEthernet1/7     10.0.60.17      YES manual up                    up     

GigabitEthernet1/8     unassigned      YES manual up                    up     

JT-a#traceroute 10.0.60.6

Type escape sequence to abort.

Tracing the route to 10.0.60.6

  1 10.0.60.6 0 msec *  0 msec

JT-a#traceroute 10.0.60.18

Type escape sequence to abort.

Tracing the route to 10.0.60.18

  1 10.0.60.18 4 msec *  4 msec

JT-a#tr 10.0.60.30

Type escape sequence to abort.

Tracing the route to 10.0.60.30

  1 10.0.60.30 0 msec *  0 msec

JT-a#ping 10.0.60.30

Type escape sequence to abort.

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

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms

JT-a#ping 10.0.60.18

Type escape sequence to abort.

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

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms

JT-a#ping 10.0.60.6

Type escape sequence to abort.

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

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms

[Steve Fuller · Accepted solution]

Hi,

Losing a single probe at some hops in the traceroute output is typically due rate limiting running on the router that is responding to the probe, and is not a cause or concern.

Take a read of the Packet Life blog, Traceroute timeouts for further details of the cause.

Regards

[topnewinfo]

hi steve.

Thanks. After executing the no ip icmp rate-limit unreachable command, It's ok. thank u.

but, why don't executing the  sh ip icmp  command?

4506-E-2#sh ip icmp

                ^

% Invalid input detected at '^' marker.

4506-E-2#sh ip i?

igmp  interface  irdp