- Preface
- 1 - Overview of Access Point Features
- 2 - Using the Web-Browser Interface
- 3 - Using the Command-Line Interface
- 4 - Configuring the Access Point for the First Time
- 5 - Administrating the Access Point
- 6 - Configuring Radio Settings
- 7 - Configuring Multiple SSIDs
- 8 - Configuring Spanning Tree Protocol
- 9 - Configuring an Access Point as a Local Authenticator
- 10 - Configuring WLAN Authentication and Encryption
- 11 - Configuring Authentication Types
- 12 - Configuring Other Services
- 13 - Configuring RADIUS and TACACS+ Servers
- 14 - Configuring VLANs
- 15 - Configuring QoS
- 16 - Configuring Filters
- 17 - Configuring CDP
- 18 - Configuring SNMP
- 19 - Configuring Repeater and Standby Access Points and Workgroup Bridge Mode
- 20 - Managing Firmware and Configurations
- 21 - Configuring L2TPv3 Over UDP/IP
- 22 - Configuring Ethernet over GRE
- 23 - Configuring System Message Logging
- 24 - Troubleshooting
- 25 - Miscellaneous AP-Specific Configurations
- Appendix A - Protocol Filters
- Appendix B - Supported MIBs
- Appendix C - Error and Event Messages
- Understanding System Message Logging
- Configuring System Message Logging
- System Log Message Format
- Default System Message Logging Configuration
- Disabling and Enabling Message Logging
- Setting the Message Display Destination Device
- Enabling and Disabling Timestamps on Log Messages
- Enabling and Disabling Sequence Numbers in Log Messages
- Defining the Message Severity Level
- Limiting Syslog Messages Sent to the History Table and to SNMP
- Setting a Logging Rate Limit
- Configuring the System Logging Facility
- Displaying the Logging Configuration
Configuring System Message Logging
This chapter describes how to configure system message logging on your access point.
Note
For complete syntax and usage information for the commands used in this chapter, refer to the Cisco IOS Configuration Fundamentals Command Reference guide.
Understanding System Message Logging
By default, access points send the output from system messages and debug privileged EXEC commands to a logging process. The logging process controls the distribution of logging messages to various destinations, such as the logging buffer, terminal lines, or a syslog server, depending on your configuration. The process also sends messages to the console.
When the logging process is disabled, messages are sent only to the console. The messages are sent as they are generated, so message and debug output are interspersed with prompts or output from other commands. Messages are displayed on the console after the process that generated them has finished.
You can set the severity level of the messages to control the type of messages displayed on the console and each of the destinations. You can timestamp log messages or set the syslog source address to enhance real-time debugging and management.
You can access logged system messages by using the access point command-line interface (CLI) or by saving them to a properly configured syslog server. The access point software saves syslog messages in an internal buffer. You can remotely monitor system messages by accessing the access point through Telnet or by viewing the logs on a syslog server.
Configuring System Message Logging
This section describes how to configure system message logging. It contains this configuration information:
- System Log Message Format
- Default System Message Logging Configuration
- Disabling and Enabling Message Logging
- Setting the Message Display Destination Device
- Enabling and Disabling Timestamps on Log Messages
- Enabling and Disabling Sequence Numbers in Log Messages
- Defining the Message Severity Level
- Limiting Syslog Messages Sent to the History Table and to SNMP
- Setting a Logging Rate Limit
- Configuring the System Logging Facility
System Log Message Format
System log messages can contain up to 80 characters and a percent sign (%), which follows the optional sequence number or timestamp information, if configured. Messages are displayed in this format:
seq no:timestamp: %facility-severity-MNEMONIC:description
The part of the message preceding the percent sign depends on the setting of the service sequence-numbers, service timestamps log datetime, service timestamps log datetime [ localtime ] [ msec ] [ show-timezone ], or service timestamps log uptime global configuration command.
Table 23-1 describes the elements of syslog messages.
|
|
|
|---|---|
Stamps log messages with a sequence number only if the service sequence-numbers global configuration command is configured. For more information, see the “Enabling and Disabling Sequence Numbers in Log Messages” section. |
|
Date and time of the message or event. This information appears only if the service timestamps log [ datetime | log ] global configuration command is configured. For more information, see the “Enabling and Disabling Timestamps on Log Messages” section. |
|
The facility to which the message refers (for example, SNMP, SYS, and so forth). A facility can be a hardware device, a protocol, or a module of the system software. It denotes the source or the cause of the system message. |
|
Single-digit code from 0 to 7 that is the severity of the message. For a description of the severity levels, see Table 23-3. |
|
Text string containing detailed information about the event being reported. |
This example shows a partial access point system message:
Default System Message Logging Configuration
Table 23-2 shows the default system message logging configuration.
|
|
|
|---|---|
Debugging (and numerically lower levels; see Table 23-3) |
|
Local7 (see Table 23-4) |
|
Informational (and numerically lower levels; see Table 23-3) |
Disabling and Enabling Message Logging
Message logging is enabled by default. It must be enabled to send messages to any destination other than the console. When enabled, log messages are sent to a logging process, which logs messages to designated locations asynchronously to the processes that generated the messages.
Beginning in privileged EXEC mode, follow these steps to disable message logging:
|
|
|
|
|---|---|---|
Disabling the logging process can slow down the access point because a process must wait until the messages are written to the console before continuing. When the logging process is disabled, messages are displayed on the console as soon as they are produced, often appearing in the middle of command output.
The logging synchronous global configuration command also affects the display of messages to the console. When this command is enabled, messages appear only after you press Return. For more information, see the “Enabling and Disabling Timestamps on Log Messages” section.
To re-enable message logging after it has been disabled, use the logging on global configuration command.
Setting the Message Display Destination Device
If message logging is enabled, you can send messages to specific locations in addition to the console. Beginning in privileged EXEC mode, use one or more of the following commands to specify the locations that receive messages:
|
|
|
|
|---|---|---|
Log messages to an internal buffer. The default buffer size is 4096. The range is 4096 to 2147483647 bytes. Levels include emergencies 0, alerts 1, critical 2, errors 3, warnings 4, notifications 5, informational 6, and debugging 7. Note Do not make the buffer size too large because the access point could run out of memory for other tasks. Use the show memory privileged EXEC command to view the free processor memory on the access point; however, this value is the maximum available, and you should not set the buffer size to this amount. |
||
Log messages to a syslog server host. For host, specify the name or IP address of the host to be used as the syslog server. To build a list of syslog servers that receive logging messages, enter this command more than once. For complete syslog server configuration steps, see the “Configuring the System Logging Facility” section. |
||
Log messages to a non-console terminal during the current session. Terminal parameter-setting commands are set locally and do not remain in effect after the session has ended. You must perform this step for each session to see the debugging messages. |
||
The logging buffered global configuration command copies logging messages to an internal buffer. The buffer is circular, so newer messages overwrite older messages after the buffer is full. To display the messages that are logged in the buffer, use the show logging privileged EXEC command. The first message displayed is the oldest message in the buffer. To clear the contents of the buffer, use the clear logging privileged EXEC command.
To disable logging to the console, use the no logging console global configuration command.
Enabling and Disabling Timestamps on Log Messages
By default, log messages are not timestamped.
Beginning in privileged EXEC mode, follow these steps to enable timestamping of log messages:
To disable timestamps for both debug and log messages, use the no service timestamps global configuration command.
This example shows part of a logging display with the service timestamps log datetime global configuration command enabled:
This example shows part of a logging display with the s ervice timestamps log uptime global configuration command enabled:
Enabling and Disabling Sequence Numbers in Log Messages
Because there is a chance that more than one log message can have the same timestamp, you can display messages with sequence numbers so that you can unambiguously refer to a single message. By default, sequence numbers in log messages are not displayed.
Beginning in privileged EXEC mode, follow these steps to enable sequence numbers in log messages:
|
|
|
|
|---|---|---|
To disable sequence numbers, use the no service sequence-numbers global configuration command.
This example shows part of a logging display with sequence numbers enabled:
Defining the Message Severity Level
You can limit messages displayed to the selected device by specifying the severity level of the message, which are described in Table 23-3 .
Beginning in privileged EXEC mode, follow these steps to define the message severity level:
|
|
|
|
|---|---|---|
Limit messages logged to the console. By default, the console receives debugging messages and numerically lower levels (see Table 23-3). |
||
Limit messages logged to the terminal lines. By default, the terminal receives debugging messages and numerically lower levels (see Table 23-3). |
||
Limit messages logged to the syslog servers. By default, syslog servers receive informational messages and numerically lower levels (see Table 23-3). For complete syslog server configuration steps, see the “Configuring the System Logging Facility” section. |
||
Note Specifying a level causes messages at that level and numerically lower levels to be displayed at the destination.
To disable logging to the console, use the no logging console global configuration command. To disable logging to a terminal other than the console, use the no logging monitor global configuration command. To disable logging to syslog servers, use the no logging trap global configuration command.
Table 23-3 describes the level keywords. It also lists the corresponding syslog definitions from the most severe level to the least severe level.
|
|
|
|
|
|---|---|---|---|
The software generates four other categories of messages:
- Error messages about software or hardware malfunctions, displayed at levels warnings through emergencies. These types of messages mean that the functionality of the access point is affected.
- Output from the debug commands, displayed at the debugging level.
- Interface up or down transitions and system restart messages, displayed at the notifications level. This message is only for information; access point functionality is not affected.
- Reload requests and low-process stack messages, displayed at the informational level. This message is only for information; access point functionality is not affected.
Note Authentication request log messages are not logged on to a syslog server. This feature is not supported on Cisco Aironet access points.
Limiting Syslog Messages Sent to the History Table and to SNMP
If you have enabled syslog message traps to be sent to an SNMP network management station by using the snmp-server enable trap global configuration command, you can change the level of messages sent and stored in the access point history table. You can also change the number of messages that are stored in the history table.
Messages are stored in the history table because SNMP traps are not guaranteed to reach their destination. By default, one message of the level warning and numerically lower levels (see Table 23-3) are stored in the history table even if syslog traps are not enabled.
Beginning in privileged EXEC mode, follow these steps to change the level and history table size defaults:
|
|
|
|
|---|---|---|
logging history level1 |
Change the default level of syslog messages stored in the history file and sent to the SNMP server. See Table 23-3 for a list of level keywords. By default, warnings, errors, critical, alerts, and emergencies messages are sent. |
|
Specify the number of syslog messages that can be stored in the history table. The default is to store one message. The range is 1 to 500 messages. |
||
|
1.Table 23-3 lists the level keywords and severity level. For SNMP usage, the severity level values increase by 1. For example, emergencies equal 1, not 0, and critical equals 3, not 2. |
When the history table is full (it contains the maximum number of message entries specified with the logging history size global configuration command), the oldest message entry is deleted from the table to allow the new message entry to be stored.
To return the logging of syslog messages to the default level, use the no logging history global configuration command. To return the number of messages in the history table to the default value, use the no logging history size global configuration command.
Setting a Logging Rate Limit
You can enable a limit on the number of messages that the access point logs per second. You can enable the limit for all messages or for messages sent to the console, and you can specify that messages of a specific severity are exempt from the limit.
Beginning in privileged EXEC mode, follow these steps to enable a logging rate limit:
|
|
|
|
|---|---|---|
To disable the rate limit, use the no logging rate-limit global configuration command.
Configuring the System Logging Facility
When sending system log messages to an external device, you can cause the access point to identify its messages as originating from any of the syslog facilities.
Beginning in privileged EXEC mode, follow these steps to configure system facility message logging:
|
|
|
|
|---|---|---|
Log messages to a syslog server host by entering its IP address. To build a list of syslog servers that receive logging messages, enter this command more than once. |
||
Limit messages logged to the syslog servers. Be default, syslog servers receive informational messages and lower. See Table 23-3 for level keywords. |
||
Configure the syslog facility. See Table 23-4 for facility-type keywords. |
||
To remove a syslog server, use the no logging host global configuration command, and specify the syslog server IP address. To disable logging to syslog servers, enter the no logging trap global configuration command.
Table 23-4 lists the system facilities supported by the Cisco IOS software. For more information about these facilities, consult the operator’s manual for your syslog server.
|
|
|
|---|---|
Displaying the Logging Configuration
To display the current logging configuration and the contents of the log buffer, use the show logging privileged EXEC command. For information about the fields in this display, refer to the Cisco IOS Configuration Fundamentals Command Reference guide.
To display the logging history file, use the show logging history privileged EXEC command.
Feedback