There are several things that might cause this issue. I suggest that you check on these things:
- did you issue the command terminal monitor before running the debug? If you are accessing the router remotely (telnet or SSH) then terminal monitor will send a copy of log messages to your session. If you do not enter terminal monitor then no copy of the debug output goes to your session.
- did you change the severity level of output going to the monitor logging? You can check this by looking at the output at the beginning of the show log command.
- did you try looking in the output of show log for the debug output? This can be helpful if you forgot to use terminal monitor.
- is it possible that no IP packets matched the conditions in your access list. Perhaps you can post the access list so we can check it.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...