Administration
Log Settings
Cisco WAP571/E Administration Guide 39
3
• Persistence—Click Enable to save system logs to nonvolatile memory so
that the logs are kept when the WAP device reboots. You can save up to 128
log messages in the nonvolatile memory. When the limit of 128 is 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—The minimum severity that an event must have for it to be written
to the log in nonvolatile memory. For example, if you specify 2 (critical), then
critical, alert, and emergency events are logged to nonvolatile memory. Error
messages with a severity level of 3 to 7 are written to volatile memory.
• Depth—The maximum number of messages, up to 512, that can be stored in
volatile memory. When the number 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 128, which is not configurable.
STEP 3 Click Save. The changes are saved to the Startup Configuration.
Remote Log Server
The Kernel Log is a comprehensive list of system events (shown in the System
Log) and kernel messages such as error conditions.
You cannot view kernel log messages directly from the web interface. 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.
Remote log server collection for WAP device 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:
STEP 1 Select Administration > Log Settings in the navigation pane.
STEP 2 Configure the parameters:
To Next Page
Loading...
Need help?
General
