Ah, that's good to know!  I've been noticing that problem on a 3660
running 12.2 and it was driving me crazy.  Last time I looked at CCO I
didn't see the bug report but either I missed it or it wasn't on there
yet.

Thanks for clearing that up for me.

John

>>> "Bill Carter"  8/24/01 7:04:07 AM >>>
There is a bug when logging synchronous is used on the vty or console
ports.

I hit this issue also.

^-^-^-^-^-^-^-^-^-^-^
Bill Carter
CCIE 5022
^-^-^-^-^-^-^-^-^-^-^


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Patrick Donlon
Sent: Friday, August 24, 2001 7:18 AM
To: [EMAIL PROTECTED] 
Subject: Logging debug messages [7:17107]


I'm having a strange problem with a 2600 running 12.2(1a), after a
short
period of time (30 to 60 mins) the router will stop logging messages to
the
vty lines with terminal monitor. I can perform a show logging history
and
see the last message in the history but nothing is display as it
happens,
some details below have a look and if anyone can see what's wrong let
me
know,

cheers Pat

 #sh logging
Syslog logging: enabled (0 messages dropped, 1 messages rate-limited,
0
flushes, 0 overruns)
    Console logging: level debugging, 152 messages logged
    Monitor logging: level debugging, 233 messages logged
        Logging to: vty66(0)
    Buffer logging: disabled
    Logging Exception size (4096 bytes)
    Trap logging: level informational, 19 message lines logged

#sh logging history
Syslog History Table:1 maximum table entries,
saving level warnings or higher
 16 messages ignored, 0 dropped, 0 recursion drops
 4 table entries flushed
 SNMP notifications not enabled
   entry number 5 : PARSER-3-BADSUBCMD
    Unrecognized subcommand 0 in exec command 'test crypto isa x.x.x.x
x.x.x.x desmd5 '
    timestamp: 699958




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=17125&t=17107
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to