Cisco Cisco WAP551 Wireless-N Single Radio Selectable Band Access Point 관리 매뉴얼
Administration
Log Settings
Cisco Small Business WAP551 and WAP561 Wireless-N Access Point
30
3
Log Settings
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.
permanent memory. You can also send logs to a remote host.
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.
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.
degrade network performance. Only enable persistent logging to debug a
problem. Make sure that you disable persistent logging after you finish debugging
the problem.
To configure persistent logging:
STEP 1
Select Administration > Log Settings in the navigation pane.
STEP 2
Configure the parameters:
•
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.
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.
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.
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.