Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!rutgers!gatech!ncar!boulder!daemon
From: BILLW@mathom.cisco.com (WilliamChops Westfield)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: Debug woes, hoped for fixes
Message-ID: <28806@boulder.Colorado.EDU>
Date: 28 Oct 90 09:24:22 GMT
Sender: daemon@boulder.Colorado.EDU
Lines: 30


    Calling CISCO tells us this is a know "feature".  DEBUG has a higher
    priority than almost anything.  DEBUG should not be used on a busy
    production system.

Actuallty, it is not debugging itself that has such high priority - it
is the output of this debugging information to the console terminal.


    I think CISCO should allow DEBUG in production, especially of the
    routing information.  By default DEBUG should turn off after a short
    time (2 or 3 minutes) or after some limit such as buffer limits are
    hit, or after 500 lines of output or some such definable termination
    condition.

There are a couple of things you can do within the current architecture
that do essentially what you are asking for.  The key is to prevent the
debug output from being sent to the console.  One way to do this is to
explicitly disable logging to the console ("no logging console" config
command), and instead pick up the output on a tcp vty with "terminal
monitor" turned on.  The other way is to configure the system with the
"logging buffered" command, which saves the debugging output in a buffers,
and displays it when you do a "show logging" command.

Note that either of the methods may result in lost debugging messages,
which can be very confusing.

Bill Westfield
cisco Systems.
-------