The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
System logs are records of system events. They are useful for network troubleshooting, to debug packet flow, and to monitor events. These logs can be saved on the RAM, NVRAM, and on remote log servers. Logs help you to administer the status of the device. This document describes the log settings configuration and explains the log status on the WAP551 and WAP561.
Step 1. Log in to the Access Point Configuration Utility to choose Administration > Log Settings. The Log Settings page opens:
Step 2. (Optional) If you want the logs to be saved permanently so that it is not lost when the WAP reboots, check the Enable check box in the Persistence field to enable the persistence feature. This is especially useful in case of unexpected system reboots when an undesirable event or failure occurs. Up to 128 log messages can be saved in the NVRAM, after which logs are overwritten. If Enable is unchecked, logs are saved in volatile memory.
Step 3. Choose the severity level from the Severity drop-down list. The severity chosen is inclusive of all the higher levels, so logs are kept for all severity levels from the top level down to the chosen level. The are the available severity levels are as follows:
• Emergency — A panic condition which affects multiple applications and server/sites.
• Alert — This type of condition needs an immediate action to be performed. Condition need to be fixed right away.
• Critical — The system is in a critical state. This type of log Indicates failure in primary system. Also needs to be addresses right away.
• Error — A non-urgent system error has occurred. These must be resolved within a given time.
• Warning — No error has occurred yet, but an indication that it will take place if action is not taken.
• Notice — The system functions properly, but a system notice has occurred. These are events that are unusual but not error conditions. They might be useful to detect conditions that may cause potential error.
• Informational — Provides device information. May be needed for report purposes.
• Debug — Provides detailed information about the log, which is useful for debugging.
Step 4. As log messages are generated, they are placed in a queue for transmission. The Depth field specifies the number of messages that can be queued at one time in the volatile memory. Up to 512 messages can be queued at one time. Enter the desired queue length in the Depth field.
Step 5. (Optional) If you wish to send the log messages to a remote syslog server, check the Enable check box in the Remote Log field.
Timesaver: If you did not check the Enable check box, skip Step 6 and Step 7. Go to Step 8.
Step 6. Enter the domain name or IP address of the syslog server in the Server IPv4/IPv6 Address/Name field.
Step 7. Enter the number of the UDP port of the syslog server where the logs are sent in the UDP Port field. The default port is 514.
Step 8. Click Save to save the settings.
Step 1. Log in to the Access Point Configuration Utility to choose Status and Statistics > Log. The Log page opens.
The Log Table has the following fields:
• Time Stamp — This field displays the month, day, year, and time the log was created.
• Severity — This field displays the severity level associated with the event.
• Service — This field displays the service or the software component that generated the log.
• Description — This field describes the event logged.
Step 2. (Optional) If you wish to clear the logs click Clear All.
Step 3. (Optional) If you want to update the Log Table click Refresh.