Log Settings; Configuring The Persistent Log - Cisco WAP121 Administration Manual

Administration

Log Settings

Log Settings
!
CAUTION
STEP 1
STEP 2
Cisco Small Business WAP121 and WAP321 Wireless-N Access Point with PoE
You can use the Log Settings page to enable log messages to be saved in
permanent memory. You can also send logs to a remote host.

Configuring the Persistent Log

If the system unexpectedly reboots, log messages can be useful to diagnose the
cause. However, log messages are erased when the system reboots unless you
enable persistent logging.
Enabling persistent logging can wear out the flash (non-volatile) memory and
degrade network performance. You should only enable persistent logging to debug
a problem. Make sure you disable persistent logging after you finish debugging the
problem.
To configure persistent logging:
Click Administration > Log Settings in the navigation window.
Configure the parameters:
• Persistence—Click Enable to save system logs to nonvolatile memory so
that the logs are kept when the WAP device reboots. 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–7 are written to volatile memory. The
severity levels are as follows:
- 0—Emergency
- 1—Alert
- 2—Critical
- 3—Error
- 4—Warning
3
33