08-01-2002 12:41 AM - edited 03-02-2019 12:20 AM
I have a problem with syslogging on Cisco5500. Configuration lines are:
#syslog
set logging console disable
set logging server enable
set logging server 2A.B.C.D
set logging level cdp 5 default
set logging level mcast 5 default
set logging level dvlan 5 default
set logging level earl 5 default
set logging level fddi 5 default
set logging level ip 5 default
set logging level pruning 5 default
set logging level snmp 5 default
set logging level spantree 5 default
set logging level tac 5 default
set logging level tcp 5 default
set logging level telnet 5 default
set logging level tftp 5 default
set logging level vtp 5 default
set logging level vmps 5 default
set logging level kernel 5 default
set logging level filesys 5 default
set logging level drip 5 default
set logging level protfilt 5 default
set logging level security 5 default
set logging level radius 5 default
set logging level udld 5 default
set logging level gvrp 5 default
set logging level cops 5 default
set logging level qos 5 default
set logging server facility LOCAL5
set logging server severity 5
set logging buffer 200
Even if I change severity to 7 nothing happens. Only one line reached syslogd - 2002 Jul 31 17:37:44 MSK +03:00 %SYS-5-SYS_RESET:System reset from
> telnet/192.168....
OSversion - 6.3 (When there was 5.5 I have the same results).
Does anyone know what happens ?
08-01-2002 08:31 PM
Are you having issues with logging to the console or a syslog server? If it's the console..I see that console logging is disabled. If you are trying to log to a server, make sure you have set up your server to receive messages. The following page on CCO should help
http://cio.cisco.com/univercd/cc/td/doc/product/lan/cat5000/rel_6_3/config/logging.htm
08-01-2002 10:18 PM
The console logging works fine even if I said in config 'set logg cons disabled' - all messages fall to console routinely. Also syslog server works correctly - it's not only one Cisco I have, it's only one Cisco wich logging into console and avoid logging almost all messages to server (except only one where I reloading this Cisco). It was on old software (5.5) and it's on the new one (6.3).
08-08-2002 02:06 AM
Perhaps you should set the severity to all 6. Initially we have this problem on the 6000 and after setting it to 6, can received. Hopes it help.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide