RE: Logging - terminal monitor not working [7:39957]
Cool! I will spend sometime today learning how to use the bug tool... Thanks, Pierre-Alex -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Sunday, March 31, 2002 12:00 PM To: [EMAIL PROTECTED] Subject: RE: Logging - terminal monitor not working [7:39957] Have seen it on many (mostly smaller) routers. Its a bug: > > ## Bug Id : CSCdu60369 > > ## Headline no syslog logging when logging synchronous enabled > > ## Product c2600 Model > > ## Component os-logging Duplicate of > > ## Severity 2 Status M > > ## Version Found12.0(7)T 12.0(6)S Fixed-in Version12.2(5) > > ## Release Notes > > ## > > ## The logging synchronous line configuration command may > > ## cause logging to stop. > > ## > > ## Workaround: Remove this command. hth Reinhold Pierre-Alex Guanel wrote: > > Amazing I removed logging synchronous on line console 0 > and debug > worked > > I am curious, what is the reason for "logging synchronous" > preventing debug > outputs > > on terminal lines? > > Pierre-Alex > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On > Behalf Of > Lidiya White > Sent: Saturday, March 30, 2002 5:46 PM > To: [EMAIL PROTECTED] > Subject: RE: Logging - terminal monitor not working [7:39957] > > > I would add "no ip route-cache" on that interface and make sure > that you > don't have "logging synchronous" under line con 0... > > -- Lidiya White > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On > Behalf Of > Pierre-Alex Guanel > Sent: Saturday, March 30, 2002 3:04 PM > To: [EMAIL PROTECTED] > Subject: Logging - terminal monitor not working [7:39957] > > Kind of a silly problem but can't figure it out ... > > I am connected to R1 via telnet. I have turned on debugging of > ip > packets > > I also have issued the command "terminal monitor" > > Yet I do not get anything logged when I ping the Ethernet > interface of > R1 > > Any ideas? > > Thanks > > > > R1#sh terminal > Line 2, Location: "", Type: "ANSI" > Length: 45 lines, Width: 80 columns > Baud rate (TX/RX) is 9600/9600 > Status: Ready, Active, No Exit Banner > Capabilities: Receives Logging Output > Modem state: Ready > Group codes:0 > Special Chars: Escape Hold Stop Start Disconnect Activation > ^^xnone - - none > Timeouts: Idle EXECIdle Session Modem Answer Session > Dispatch > never never > none not > set > Idle Session Disconnect Warning > never > Login-sequence User Response > 00:00:30 > Autoselect Initial Wait > not set > Modem type is unknown. > Session limit is not set. > Time since activation: 00:41:15 > Editing is enabled. > History is enabled, history size is 10. > DNS resolution in show commands is enabled > Full user help is disabled > Allowed transports are lat pad v120 mop telnet rlogin nasi. > Preferred > is > lat. > No output characters are padded > No special data dispatching characters > > > R1#sh logging > Syslog logging: enabled (0 messages dropped, 0 flushes, 0 > overruns) > Console logging: level debugging, 102 messages logged > Monitor logging: level debugging, 2 messages logged > Logging to: vty2(0) > Buffer logging: level debugging, 102 messages logged > Trap logging: level informational, 47 message lines logged > > Log Buffer (4096 bytes): Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=39991&t=39957 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Logging - terminal monitor not working [7:39957]
Have seen it on many (mostly smaller) routers. Its a bug: > > ## Bug Id : CSCdu60369 > > ## Headline no syslog logging when logging synchronous enabled > > ## Product c2600 Model > > ## Component os-logging Duplicate of > > ## Severity 2 Status M > > ## Version Found12.0(7)T 12.0(6)S Fixed-in Version12.2(5) > > ## Release Notes > > ## > > ## The logging synchronous line configuration command may > > ## cause logging to stop. > > ## > > ## Workaround: Remove this command. hth Reinhold Pierre-Alex Guanel wrote: > > Amazing I removed logging synchronous on line console 0 > and debug > worked > > I am curious, what is the reason for "logging synchronous" > preventing debug > outputs > > on terminal lines? > > Pierre-Alex > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On > Behalf Of > Lidiya White > Sent: Saturday, March 30, 2002 5:46 PM > To: [EMAIL PROTECTED] > Subject: RE: Logging - terminal monitor not working [7:39957] > > > I would add "no ip route-cache" on that interface and make sure > that you > don't have "logging synchronous" under line con 0... > > -- Lidiya White > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On > Behalf Of > Pierre-Alex Guanel > Sent: Saturday, March 30, 2002 3:04 PM > To: [EMAIL PROTECTED] > Subject: Logging - terminal monitor not working [7:39957] > > Kind of a silly problem but can't figure it out ... > > I am connected to R1 via telnet. I have turned on debugging of > ip > packets > > I also have issued the command "terminal monitor" > > Yet I do not get anything logged when I ping the Ethernet > interface of > R1 > > Any ideas? > > Thanks > > > > R1#sh terminal > Line 2, Location: "", Type: "ANSI" > Length: 45 lines, Width: 80 columns > Baud rate (TX/RX) is 9600/9600 > Status: Ready, Active, No Exit Banner > Capabilities: Receives Logging Output > Modem state: Ready > Group codes:0 > Special Chars: Escape Hold Stop Start Disconnect Activation > ^^xnone - - none > Timeouts: Idle EXECIdle Session Modem Answer Session > Dispatch > never never > none not > set > Idle Session Disconnect Warning > never > Login-sequence User Response > 00:00:30 > Autoselect Initial Wait > not set > Modem type is unknown. > Session limit is not set. > Time since activation: 00:41:15 > Editing is enabled. > History is enabled, history size is 10. > DNS resolution in show commands is enabled > Full user help is disabled > Allowed transports are lat pad v120 mop telnet rlogin nasi. > Preferred > is > lat. > No output characters are padded > No special data dispatching characters > > > R1#sh logging > Syslog logging: enabled (0 messages dropped, 0 flushes, 0 > overruns) > Console logging: level debugging, 102 messages logged > Monitor logging: level debugging, 2 messages logged > Logging to: vty2(0) > Buffer logging: level debugging, 102 messages logged > Trap logging: level informational, 47 message lines logged > > Log Buffer (4096 bytes): > > Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=39989&t=39957 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Logging - terminal monitor not working [7:39957]
Amazing I removed logging synchronous on line console 0 and debug worked I am curious, what is the reason for "logging synchronous" preventing debug outputs on terminal lines? Pierre-Alex -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Lidiya White Sent: Saturday, March 30, 2002 5:46 PM To: [EMAIL PROTECTED] Subject: RE: Logging - terminal monitor not working [7:39957] I would add "no ip route-cache" on that interface and make sure that you don't have "logging synchronous" under line con 0... -- Lidiya White -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Pierre-Alex Guanel Sent: Saturday, March 30, 2002 3:04 PM To: [EMAIL PROTECTED] Subject: Logging - terminal monitor not working [7:39957] Kind of a silly problem but can't figure it out ... I am connected to R1 via telnet. I have turned on debugging of ip packets I also have issued the command "terminal monitor" Yet I do not get anything logged when I ping the Ethernet interface of R1 Any ideas? Thanks R1#sh terminal Line 2, Location: "", Type: "ANSI" Length: 45 lines, Width: 80 columns Baud rate (TX/RX) is 9600/9600 Status: Ready, Active, No Exit Banner Capabilities: Receives Logging Output Modem state: Ready Group codes:0 Special Chars: Escape Hold Stop Start Disconnect Activation ^^xnone - - none Timeouts: Idle EXECIdle Session Modem Answer Session Dispatch never nevernone not set Idle Session Disconnect Warning never Login-sequence User Response 00:00:30 Autoselect Initial Wait not set Modem type is unknown. Session limit is not set. Time since activation: 00:41:15 Editing is enabled. History is enabled, history size is 10. DNS resolution in show commands is enabled Full user help is disabled Allowed transports are lat pad v120 mop telnet rlogin nasi. Preferred is lat. No output characters are padded No special data dispatching characters R1#sh logging Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns) Console logging: level debugging, 102 messages logged Monitor logging: level debugging, 2 messages logged Logging to: vty2(0) Buffer logging: level debugging, 102 messages logged Trap logging: level informational, 47 message lines logged Log Buffer (4096 bytes): Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=39965&t=39957 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Logging - terminal monitor not working [7:39957]
I would add "no ip route-cache" on that interface and make sure that you don't have "logging synchronous" under line con 0... -- Lidiya White -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Pierre-Alex Guanel Sent: Saturday, March 30, 2002 3:04 PM To: [EMAIL PROTECTED] Subject: Logging - terminal monitor not working [7:39957] Kind of a silly problem but can't figure it out ... I am connected to R1 via telnet. I have turned on debugging of ip packets I also have issued the command "terminal monitor" Yet I do not get anything logged when I ping the Ethernet interface of R1 Any ideas? Thanks R1#sh terminal Line 2, Location: "", Type: "ANSI" Length: 45 lines, Width: 80 columns Baud rate (TX/RX) is 9600/9600 Status: Ready, Active, No Exit Banner Capabilities: Receives Logging Output Modem state: Ready Group codes:0 Special Chars: Escape Hold Stop Start Disconnect Activation ^^xnone - - none Timeouts: Idle EXECIdle Session Modem Answer Session Dispatch never nevernone not set Idle Session Disconnect Warning never Login-sequence User Response 00:00:30 Autoselect Initial Wait not set Modem type is unknown. Session limit is not set. Time since activation: 00:41:15 Editing is enabled. History is enabled, history size is 10. DNS resolution in show commands is enabled Full user help is disabled Allowed transports are lat pad v120 mop telnet rlogin nasi. Preferred is lat. No output characters are padded No special data dispatching characters R1#sh logging Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns) Console logging: level debugging, 102 messages logged Monitor logging: level debugging, 2 messages logged Logging to: vty2(0) Buffer logging: level debugging, 102 messages logged Trap logging: level informational, 47 message lines logged Log Buffer (4096 bytes): Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=39964&t=39957 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
