Cisco IP Debuggin Not Working

I am having problems getting DEBUG IP ICMP to work on my 7507.  This router have one fast ethernet interface and several serial interfaces as it serves as my frame relay router.

I have made sure that my NO IP ROUTE-CACHE command is applied to the interface that the packets I want to watch are comming from, but still no luck.  I have also tried applying an access list to no avail.

I'm just trying to ping between two 7507 routers.  

This is causing me to not be able to troubleshoot a routing issue right now on my backbone.

Who is Participating?
mikebernhardtConnect With a Mentor Commented:
By the way, the above doesn't rely on debug at all- it's just logging packets. And a correction- if you want to see the logging messages in your term mon then you need to configure "logging level debug"

apply the access list to the appropriate interface with
access-group 100 in
access-group 100 out
Are you using a telnet session, or straight on the console port?
If using telnet, issue "term mon" command
TroyGAAuthor Commented:
Forgot to add that in ; yes using a telnet session with the following commands:

debug ip icmp
ter mon

Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

TroyGAAuthor Commented:
I looked over the two articles listed here and have tried everything suggested.

Not using CEF or any other fast switch mechanisms.

It's just not working =/
In order to have your debugging messages appear in a console, you need the following:
1) Define target logging level:
    Level       Keyword       Description
    0         emergencies   System is unusable.
    1         alerts             Immediate action is needed.
    2         critical            Critical conditions exist.
    3          errors            Error conditions exist.
    4          warnings        Warning conditions exist.
    5          notification     Normal, but significant, conditions exist.
    6          informational  Informational messages.
    7          debugging      Debugging messages.
2) Define where you want to output logs: console, monitor (telnet session) or syslog
3) Configure logging:
    config t
    logging console <logging level>   <----if you want logging to serial port console
    logging buffered                         <----if you want logging to telnet monitor
    logging monitor <logging level>
    logging <ip address>                  <----if you want to log to syslog
    logging trap <level>
4) To see actual monitor logs, "term mon" at telnet session.

In your case:
logging buffered
logging monitor debug
term mon
debug ip icmp

TroyGAAuthor Commented:
I wish I could say that worked but again, nothing is happening =(
A few things to check:
1) Configure "logging on";
2) If you are doing conditional debugging ("debug interface"), make sure you selectec the "right" interfaces, or just do "no debug interface" or "no debug interface all" to reset it;
3) If you are using conditional debugging, double check "debug condition" command nesting.

I have had a similar problem sometimes and I never figured out why. You should definitely be able to do it with an access list. for example if you created the following access list and applied it both inbound and outbound, you should see every icmp packet logged:

access-list 100 permit icmp any any log
access-list 100 permit ip any any

All that logging stuff from earlier has nothing to do with whether you will see the debug output, it only affects how it logs the debug. If you set "term mon" in your vty session you will see it. On the console you have to set "logging console" but this is on by default.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.