Specifications

7-5
Cisco AS5x00 Case Study for Basic IP Modem Services
11/24/1999
Section 7 Enabling Management Protocols: NTP, SNMP, and Syslog
Enabling Syslog
Step 1
Enable debug timestamps and include the date, time, and milliseconds relative to the local time zone:
!
service timestamps debug datetime msec localtime show-timezone
service timestamps log datetime msec localtime show-timezone
!
Step 2
Verify that console logging is disabled. If it is enabled, the NAS will intermittently freeze up as soon as
the console port is overloaded with log messages. See the field “1 flushes.” Increments on this number
represents bad logging behavior.
5300-NAS#show logging
Syslog logging: enabled (0 messages dropped, 1 flushes, 0 overruns)
Console logging: level debugging, 1523 messages logged
Monitor logging: level debugging, 0 messages logged
Buffer logging: level debugging, 911 messages logged
Trap logging: level informational, 44 message lines logged
. . .
Snip
5300-NAS(config)#no logging console
5300-NAS(config)#^Z
5300-NAS#show logging
Syslog logging: enabled (0 messages dropped, 1 flushes, 0 overruns)
Console logging: disabled
Monitor logging: level debugging, 0 messages logged
Buffer logging: level debugging, 912 messages logged
Trap logging: level informational, 45 message lines logged
Warning
Not entering the
no logging console
command, might cause CPU interrupts, dropped
packets, and denial of service events. The router might lock up.
Step 3
Specify the logging configuration:
!
logging 172.22.66.18
logging buffered 10000 debugging
logging trap debugging
!
Figure 7-2 describes the commands in the previous configuration fragment.
Table 7-2 Syslog Commands
Command Purpose
logging 172.22.66.18
Specifies the syslog server’s IP address.
logging buffered 10000
debugging
Sets the internal log buffer to 10000 bytes for
debug output (newer messages overwrite older
messages).
logging trap debugging
Allows logging up to the debug level (all 8
levels) for all messages sent to the syslog
server.