Log Settings

Use the Log Settings page to enable log messages to be saved in permanent memory. You can also send logs to a remote host.

If the system unexpectedly reboots, the log messages can be useful to diagnose the cause. However, log messages are erased when the system reboots unless you enable persistent logging.

Caution
Enabling persistent logging can wear out the flash (nonvolatile) memory and degrade network performance. Only enable persistent logging to debug a problem. Make sure that you disable persistent logging after you finish debugging the problem.

Configuring the Persistent Log

Procedure

Step 1

Select Notification > Log Settings.

Step 2

Configure these parameters:

  • Persistence — Check Enable to save the system logs to the nonvolatile memory so that the logs are kept when the WAP device reboots. You can save up to 1000 log messages. When the limit of 1000 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 — Select the severity from the drop-down list (Emergency, Alert, Critical, Error, Warning, Notice, Info or Debug) used to filter the event messages that will be saved in the nonvolatile memory. All other messages will be saved in the 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.

Step 3

Click Save.