When I use debug in my lab, sometimes the router just stops debugging. For example, it may be debugging fine for awhile. Then, all of a sudden, it will just stop debugging. The router is still alive, as I am perfectly able to type in commands, change things around, etc. It just no longer produces debug information. It's happened to me on both the console and telnet (and I have typed term mon about a billion times). I type show debug, and it shows that debugging is on. But there is no output. I even type "debug all" (it's not a production router), and still get no output which is ridiculous because I'm running a bunch of routing protocols on the router. Like I said, the router doesn't die after I type debug all (because it is very lightly loaded), as I am perfectly able to type in config commands and show commands. It just does not produce any debug output. Nor does clear logging help. The only thing that I have found that helps is to reboot the router. Then, I can put in some debug commands, and debug output will be created. And then of course, after some time, the router will just stop debugging, and I have to reboot it again. So, anybody know what is up with that? I am using 12.0(17). Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=5527&t=5527 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
