Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Debugging problem

Status
Not open for further replies.

superduperlopez

Technical User
Mar 21, 2006
32
GB
Hi,

I am expereincing the following problem with a Cisco 1701, flash:c1700-advsecurityk9-mz.124-5.bin.

I telnet into the router, type the terminal monitor command and then the fun begins......

if I do a "debug ip icmp" and do a ping somewhere I get the following...

TEST#debug ip icmp
ICMP packet debugging is on
TEST#ping 66.249.93.99

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 66.249.93.99, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 44/50/56 ms
TEST#
003201: May 3 13:45:56.140 London: ICMP: echo reply rcvd, src 66.249.93.99, dst 88.66.244.33
003202: May 3 13:45:56.192 London: ICMP: echo reply rcvd, src 66.249.93.99, dst 88.66.244.33
003203: May 3 13:45:56.252 London: ICMP: echo reply rcvd, src 66.249.93.99, dst 88.66.244.33
003204: May 3 13:45:56.296 London: ICMP: echo reply rcvd, src 66.249.93.99, dst 88.66.244.33
003205: May 3 13:45:56.348 London: ICMP: echo reply rcvd, src 66.249.93.99, dst 88.66.244.33

However, if I do a "debug ip packet" and ping again.......no thing happens....

TEST#debug ip packet
IP packet debugging is on
TEST#ping 66.249.93.99

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 66.249.93.99, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 40/46/56 ms
TEST#

any ideas on why some debugging commands are working and others aren't???

Thank you

 
Also, if your telnet`ing onto your router, you should also see that traffic too under the Debug Ip traffic.....

Ive always had problems with debugging on numerous routers, with inconsistant results... never have got to the bottom of it!


LEEroy
MCNE6,CCNA2,CWNA, Project+, CCSA
 
The icmp packets are being sourced from the interface closest to the destination. As such, they are not being routed across the router. If you want to see output in the debug ip packet, try using an extended ping and sourcing from another interface on the router. debug ip packet shows traffic that is crossing the router, not sourced from the router.

HTH
 
Did you turn off fast switching before debugging ip packets ? You have to turn off fast switching in order for the packets to hit the processor so that you can see them . On your interfaces type " no ip route-cache " .
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top