Configuring Remote Log Server - Cisco WAP131 Administration Manual

Administration
Log Settings
STEP 3
STEP 1
STEP 2
Cisco WAP131 and WAP351 Administration Guide
reached, the oldest log message is overwritten by the newest message.
Clear this field to save system logs to volatile memory. Logs in volatile
memory are deleted when the system reboots.
• Severity—Select the severity that an event must have for it to be written to
the log in nonvolatile memory, the other will be written to volatile memory.
• Depth—Enter the maximum number of messages, up to 1000, that can be
stored in volatile memory. When the number that you configure in this field is
reached, the oldest log event is overwritten by the newest log event. Note
that the maximum number of log messages that can be stored in nonvolatile
memory (the persistent log) is 1000, which is not configurable.
Click Save. The changes are saved to the Startup Configuration.

Configuring Remote Log Server

The kernel log is a comprehensive list of system events and kernel messages such
as error conditions.
You cannot view kernel log messages directly from the configuration utility. You
must first set up a remote log server to receive and capture logs. Then you can
configure the WAP device to log to the remote log server. The WAP device
supports up to two remote log servers.
The remote log server collection for the syslog messages provides these features:
• Allows aggregation of syslog messages from multiple APs.
• Stores a longer history of messages than is kept on a single WAP device.
• Triggers scripted management operations and alerts.
To specify a host on your network to serve as a remote log server:
Select Administration > Log Settings.
In the Remote Log Server Table, configure these parameters :
• Remote Log Server—Enter the IPv4 or IPv6 address, or the host name of the
remote log server.
3
41