Cisco Router 860, 880 Series User Manual

							      System Message Logging
Configuring System Message Logging
7
Cisco 800 Series Integrated Services Routers Wireless Software Configuration Guide
xx-xxxxx-xx
NoteSpecifying 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 command in global configuration mode. 
To disable logging to a terminal other than the console, use the no logging monitor command in global 
configuration mode. To disable logging to syslog servers, use the no logging trap command in global 
configuration mode.
Ta b l e 3 describes the severity level keywords. It also lists the corresponding UNIX 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: debug commands are typically 
used only by the Technical Assistance Center (TAC).
 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.
NoteAuthentication request log messages are not logged on to a syslog server. This feature is not supported 
on Cisco Aironet access points.
Step 4logging trap levelLimits messages logged to the syslog servers.
By default, syslog servers receive informational messages and 
numerically lower levels (see 
Ta b l e 3 on page 7).
For complete steps for configuring syslog servers, see the “Configuring 
UNIX Syslog Servers” section on page 9.
Step 5endReturns to privileged EXEC mode.
Command Purpose
Ta b l e 3 Message Logging Level Keywords 
Level KeywordLevelDescriptionSyslog Definition
emergencies0System unstableLOG_EMERG
alerts1Immediate action neededLOG_ALERT
critical2Critical conditionsLOG_CRIT
errors3Error conditionsLOG_ERR
warnings4Warning conditionsLOG_WARNING
notifications5Normal but significant conditionLOG_NOTICE
informational6Informational messages onlyLOG_INFO
debugging7Debugging messagesLOG_DEBUG 
						

							      System Message Logging
Configuring System Message Logging
8
Cisco 800 Series Integrated Services Routers Wireless Software Configuration Guide
xx-xxxxx-xx
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 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 
Ta b l e 3 on 
page 7) are stored in the history table even if syslog traps are not enabled.
To change the level and history table size defaults, follow these steps, beginning in privileged EXEC 
mode:
When the history table is full (it contains the maximum number of message entries specified with the 
logging history size command in global configuration mode), 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 command in 
global configuration mode. To return the number of messages in the history table to the default value, 
use the no logging history size command in global configuration mode.
CommandPurpose
Step 1configure terminalEnters global configuration mode.
Step 2logging history level1
1.Table 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.
Changes the default level of syslog messages stored in the history file and 
sent to the SNMP server.
See Ta b l e 3 on page 7 for a list of level keywords.
By default, warnings, errors, critical, alerts, and emergencies messages 
are sent.
Step 3logging history size numberSpecifies 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.
Step 4endReturns to privileged EXEC mode. 
						

							      System Message Logging
Configuring System Message Logging
9
Cisco 800 Series Integrated Services Routers Wireless Software Configuration Guide
xx-xxxxx-xx
Setting a Logging Rate Limit
You can set 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.
To enable a logging rate limit, follow these steps, beginning in privileged EXEC mode:
To disable the rate limit, use the no logging rate-limit command in global configuration mode.
Configuring UNIX Syslog Servers
The next sections describe how to configure the 4.3 BSD UNIX server syslog daemon and define the 
UNIX system logging facility.
Logging Messages to a UNIX Syslog Daemon
Before you can send system log messages to a UNIX syslog server, you must configure the syslog 
daemon on a UNIX server. Log in as root, and perform these steps.
NoteSome recent versions of UNIX syslog daemons no longer accept by default syslog packets from the 
network. If this is the case with your system, use the UNIX man syslogd command to determine what 
options must be added to or removed from the syslog command line to enable logging of remote syslog 
messages.
Step 1Add a line such as the following to the file /etc/syslog.conf:
local7.debug /usr/adm/logs/cisco.log
The local7 keyword specifies the logging facility to be used; see Ta b l e 4 on page 10 for information on 
the facilities. The debug keyword specifies the syslog level; see Ta b l e 3 on page 7 for information on 
the severity levels. The syslog daemon sends messages at this level or at a greater severity level to the 
file specified in the next field. The file must already exist, and the syslog daemon must have permission 
to write to it.
Step 2Create the log file by entering these commands at the UNIX shell prompt:
$ touch /usr/adm/log/cisco.log
$ chmod 666 /usr/adm/log/cisco.log
CommandPurpose
Step 1configure terminalEnters global configuration mode.
Step 2logging rate-limit seconds 
[all | console] 
[except severity]
Enables a logging rate limit in seconds.
 (Optional) Apply the limit to all logging or only to 
messages logged to the console.
 (Optional) Exempt a specific severity from the limit.
Step 3endReturns to privileged EXEC mode. 
						

							      System Message Logging
Configuring System Message Logging
10
Cisco 800 Series Integrated Services Routers Wireless Software Configuration Guide
xx-xxxxx-xx
Step 3Ensure the syslog daemon reads the new changes by entering this command:
$ kill -HUP `cat /etc/syslog.pid`
For more information, see the man syslog.conf and man syslogd commands on your UNIX system.
Configuring the UNIX 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 UNIX syslog facilities.
To configure UNIX system facility message logging, follow these steps, beginning in privileged EXEC 
mode:
To remove a syslog server, use the no logging host command in global configuration mode, and specify 
the syslog server IP address. To disable logging to syslog servers, enter the no logging trap command 
in global configuration mode.
Ta b l e 4 lists the 4.3 BSD UNIX system facilities that the Cisco IOS software supports. For more 
information about these facilities, consult the operator’s manual for your UNIX operating system.
CommandPurpose
Step 1configure terminalEnters global configuration mode.
Step 2logging hostLogs messages to a UNIX 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.
Step 3logging trap levelLimits messages logged to the syslog servers.
Be default, syslog servers receive informational messages and lower. See 
Ta b l e 3 on page 7 for level keywords.
Step 4logging facility facility-typeConfigures the syslog facility. See Ta b l e 4 on page 10 for facility-type 
keywords.
The default is local7.
Step 5endReturns to privileged EXEC mode.
Ta b l e 4 Logging Facility-Type Keywords 
Facility Type Keyword Description
authAuthorization system
cronCron facility
daemon System daemon
kernKernel
local0-7 Locally defined messages
lprLine printer system
mail Mail system
newsUSENET news 
						

							      System Message Logging
Configuring System Message Logging
11
Cisco 800 Series Integrated Services Routers Wireless Software Configuration Guide
xx-xxxxx-xx
Displaying the Logging Configuration
To display the current logging configuration and the contents of the log buffer, use the show logging 
command in privileged EXEC mode. For information about the fields in this display, refer to the Cisco 
IOS Configuration Fundamentals Command Reference for Release 12.2.
To display the logging history file, use the show logging history command in privileged EXEC mode.
sys9 System use
sys10System use
sys11 System use
sys12System use
sys13System use
sys14System use
syslogSystem log
userUser process
uucp UNIX-to-UNIX copy system
Table 4 Logging Facility-Type Keywords (continued)
Facility Type Keyword  Description 
						

							      System Message Logging
Configuring System Message Logging
12
Cisco 800 Series Integrated Services Routers Wireless Software Configuration Guide
xx-xxxxx-xx 
						

							 
F-1
Book Title
OL-xxxxx-xx
APPENDIXF
Radio Channel Settings
This appendix lists the radio channels supported by Cisco access products in the regulatory domains of 
the world. 
 IEEE 802.11n (2.4-GHz Band), page F-2 
						

							 
F-2
Book Title
OL-xxxxx-xx
Appendix F      Radio Channel Settings
  IEEE 802.11n (2.4-GHz Band)
IEEE 802.11n (2.4-GHz Band)
Ta b l e F-1 lists the channel identifiers, channel center frequencies, and regulatory domains for IEEE 
802.11n 2.4GHz radio.
Ta b l e F-1 Channels for IEEE 802.11n 2.4-GHz Radio Band
Channel 
IdentifierCenter Frequency 
(MHz)
Regulatory Domains
Americas 
(–A)EMEA 
(–E)
Japan 
(–P)
12412XXX
22417XXX
32422XXX
42427XXX
52432XXX
62437XXX
72442XXX
82447XXX
92452XXX
102457XXX
112462XXX
122467–XX
132472–XX
142484–––