Path: utzoo!attcan!uunet!cs.utexas.edu!news-server.csri.toronto.edu!utgpu!cunews!bnrgate!bwdls56!fortinp
From: fortinp@bwdls56.bnr.ca (Pierre Fortin)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: 8.1(14) debug locks up router
Summary: "logging on" bug?
Message-ID: <1990Oct15.171333.28849@bnrgate.bnr.ca>
Date: 15 Oct 90 17:13:33 GMT
References: <1990Oct15.164223.25730@bnrgate.bnr.ca>
Sender: news@bnrgate.bnr.ca (USENET News System)
Organization: Bell-Northern Research, Ltd. Ottawa Ontario CANADA
Lines: 22

In article <1990Oct15.164223.25730@bnrgate.bnr.ca>, fortinp@bwdls56.bnr.ca (Pierre Fortin) writes:
> The problem:  debug output while requested from a telnet session was 
> simultaneously being sent out the _real_ console port at a paltry rate of
> 9600 bits per second.  I don't know the exact internal workings, but the
> end result was certainly visible.  This problem was not apparent on 8.0(9).

Hmmm... I just checked the configuration in one of the routers which suffered
a disastrous logical fate.  The router is setup with "logging on" which is
the default.  I entered the command and checked the config just to be sure.
The manual reads: "The _logging on_ subcommand enables message logging to all
destinations except the console."
 
Is there a bug here?  Why was the real console outputting debug messages if
the manual is correct and the router was defaulting to *not*(?) send output
to the real console?



Pierre Fortin       Bell-Northern Research     I know, my postings are
Internet Systems    P.O.Box 3511, Stn C        terse and humourless. So?
(613)763-2598       Ottawa, Ontario            RIP: aptly named protocol
fortinp@bnr.ca      Canada    K1Y 4H7          AppleTalk: Adam&Eve's design