very extensive explaination. and one more doubt is for the buffered view, having 'logging traps' command to control the size and severity level, but what the command 'logging buffer' and 'command logging facility' used for? thanks,
-----Original Message----- From: Baety Wayne A1C 18 CS/SCBX [mailto:[EMAIL PROTECTED]] Sent: 2002e941f 30f% 18:11 To: [EMAIL PROTECTED] Subject: RE: term no mon command [7:33658] There are 4 places logging information is sent; via the monitor, the console, SNMP, and a buffer. Each logging destination can be likened to 4 different views. In each view you can control the amount or severity of the logging information (debug, informational, notification, warn, errors, alerts, critical, emergencies). When you enable a view to have a certain logging level, it enables all higher logging level messages as well to be outputted to the view. When you plug a terminal into the console port with an async cable this is called the console view (line con 0). The command 'logging console ' controls the severity of logging information sent to the console. You can totally disable all logging to the console with the command 'no logging console'. When you telnet to an active interface on the router this is called the monitor view (line vty 0 4 and line aux 0). The command 'logging monitor ' controls the severity of logging information sent to the monitor. By default, you need to type 'terminal monitor' to actually activate this view when you telnet. You can totally disable all logging to the monitor with the command 'no logging monitor'. When you configure the router to output logging information to a syslog server with 'logging ' this is called the buffered view. The command 'logging trap ' controls the severity of logging information sent to the buffer. You can totally disable all logging to the console with the command 'no logging trap'. When you configure the router to output logging information to a SNMP network management station with 'snmp-server host ' this is called the SNMP view. The command 'logging history ' controls the severity of logging information sent via SNMP. You can totally disable all logging via SNMP with the command 'no logging history '. Note: For the SNMP view you must explicitly disallow the logging severity level. If you need more information on the use of all of the logging levels and what information is actually printed at each level take a look at the troubleshooting commands guide http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/fun_r /frprt3/frtroubl.htm (watch the line wrap) Good Luck! WAYNE BAETY, MCSE, A1C, USAF Network Systems Trainer > -----Original Message----- > From: Stuart Laubstein [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 30, 2002 5:12 PM > To: [EMAIL PROTECTED] > Subject: term no mon command [7:33658] > > I have a 3620 and I have to work on the console port but I am swamped with > messages every few seconds as people try to log in via the pri. I used the > term no mon command but it doesnt work--I still get connect messages etc. > Does anyone have an idea where these message come from and how I can shut > them off. We are using 12.0(7) XK1 Early Deployment release. > > thanks > > stuart Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=33675&t=33658 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
