Task 2 Enabling Syslog

Syslog data

>. ! Syslog unidirectional

Cisco IOS sending syslog data

Cisco IOS sending syslog data

>. ! Syslog unidirectional

Note Cisco System's UNIX syslog format is compatible with 4.3 BSD UNIX.

Cisco AS5x00 Case Study for Basic IP Modem Services

Cisco AS5x00 Case Study for Basic IP Modem Services

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.

53 0 0-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)#AZ

53 0 0-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.

If you are working with multiple network access servers, assign a different logging facility tag to each server. Syslog information can be collected and sorted into different files on the syslog server.

For example:

• Assign local1 to NAS1

• Assign local2 to NAS2

• Assign local3 to NAS3

Assigning a different tag to each device enables you to intelligently sort and view syslog messages:

logging facility local7

Step 4 Verify that local buffered logging is working:

53 0 0-NAS#show logging

Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns) Console logging: disabled

Monitor logging: level debugging, 0 messages logged Buffer logging: level debugging, 2 messages logged Trap logging: level debugging, 53 message lines logged Logging to 172.22.66.18, 2 message lines logged

Log Buffer (10000 bytes):

Sep 26 16:32:02.848 PDT: %SYS-5-CONFIG_I: Configured from console by admin on console Sep 26 16:33:16.069 PDT: %SYS-5-CONFIG_I: Configured from console by admin on console 53 0 0-NAS#

Continue reading here: Task

Was this article helpful?

0 0