Hi, i have been trying to use debug Packet command on cli ( with terminal monitor on). But i am not able to see any result ? why is that so. I can see various other debug results but i couldnt see a single line shown after debug packet. Is this command not working anymore or is there any other issue ??
This command does work but will only show packets that are process switch and not cef switched. If you ping an IP address on the router and debug for that, you will see output.
Adding a log entry to line on the ACL attached to the interface will force the packet to be punted to the CPU and also show up in the output.
Added an ACL to your interface with a log against the entry you want to see
example below :-
access-list 100 permit ip host 188.8.131.52 host 184.108.40.206 log
access-list 100 permit ip host 220.127.116.11 host 18.104.22.168 log
access-list 100 permit ip any any
ip address 192.168.1.1 255.255.255.252
ip access-group 101 in
Router#debug ip packet 100
This command also only shows packets that have been process switched, so the ACL attached to the interface with a log solution I suggested should also work.
The debug packet command displays all process-level packets for both outbound and inbound packets.
Just wanted to say thanks much. Adding the access list (with the log option) on the appropriate interface, did it for me. It produced the results I wanted. Before I was not able to see the expected output from packets to the far end device, after the acl I could see activity to the destinations of interest.
Where would we be without this forum and others like it?
Not sure how that will help as the log entry forces the packet to be process switched as can be observed with the command
I have not been able to get any output from debug packet but the command 'debug ip packet detail' should give you all the info you need.