Advertisement
(Optional) To disable syslog messages and SNMP traps when dial interfaces go up and down, use the
commands no logging event link-status and no snmp trap link-status. Although up and down events
are legitimate events on dial interfaces, these events should not cause alarms as LAN and WAN
interfaces would.
!
interface Serial1/0/0:4:23
no logging event link-status
no snmp trap link-status
!
interface Group-Async0
no logging event link-status
no snmp trap link-status
!
In this example, only the fourth T1 of a T3 card is shown.
In some Cisco IOS images, the logging event link-status command is disabled by
default.
In this case study, all the syslog messages from the access servers are sent to a single log file. The syslog
messages from the backbone routers are sent to a different log file.
To configure the syslog daemon on a Solaris syslog server, follow these steps:
On the syslog server, edit the file syslog.conf in the /etc/ directory by using a text editor. To get syslog
working, you must add the following line to the file:
|
local0.debug
/var/log/router.log
|
The local facility number is
Cisco IOS device. See the logging facility command in Table 20.
The log file path name is
One tab exists between the facility number and the path name. Spaces are not permitted.
You can define any directory location/path for the .txt log file.
In the following example, the new line is in bold:
"syslog.conf" 53 lines, 1861 characters
#ident
"@(#)syslog.conf
#
# Copyright (c) 1991-1993, by Sun Microsystems, Inc.
#
# syslog configuration file.
#
# This file is processed by m4 so be careful to quote (`') names
# that match m4 reserved words.
# containing commas must be quoted.
#
#
#
#
. It must match the facility number configured in the
local0.debug
/var/log/router.log
1.3
93/12/09 SMI"
Also, within ifdef's, arguments
/* SunOS 5.0 */
Advertisement
