Description:
To prevent the internal syslog from flooding with superfluous messages, access points with LCOS LX in their factory state have the log level set to Info. However, troubleshooting is aided by additionally saving messages with a higher log level (Warning, Error and Debug) to the syslog. This can be implemented by changing the logging settings. Furthermore, adjusting the logging settings makes it possible to save trace outputs to the internal syslog without having to run the trace separately from the command line.
This article describes how higher log levels and trace information can be saved to the internal syslog of an access point with LCOS LX.
Requirements:
- LCOS LX as of version 6.10 (download latest version)
- SSH client for command-line access (e.g. PuTTY)
- Any browser for access via WEBconfig
Procedure:
1) Configuring the logging settings on the access point:
The logging settings cannot be adjusted via LANconfig or WEBconfig, only from the command line.
1.1) Connect to the access point using a terminal program and enter the command cd setup/logging to switch to the menu for the logging settings.
The ls command displays the content of the menu.
1.2) Enter the command set operating yes to enable extended logging.
1.3) Enter the command set level debug to increase the log level to debug. This is the highest log level. A log level always includes the log levels below it.
You can alternatively set a lower log level. The following levels are available (in ascending order):
- Info
- Warning
- Error
- Debug
1.4) Then enter the command flash so that the changes are boot persistent. This ensures that the changes are still available after a restart or a power outage.
When you no longer need the extended logs, they should be deactivated so that they are no longer written to the syslog. To do this, enter the terminal command set setup/logging/operating no (assuming you are at the root level). Save the boot-persistent configuration with the flash command.
2) Saving traces to the internal syslog (optional):
2.1) Enter the command in the format set setup/logging/trace <trace-name> (in this example set setup/logging/trace wlan) so that this trace is saved to the internal syslog. Multiple traces can also be recorded simultaneously by executing this command again for the desired trace.
Use the command trace ? to view the traces available on the access point.
2.2) Enter the command flash so that the changes are boot persistent. This ensures that the changes are still available after a restart or a power outage.
If the trace outputs are no longer required, they should be deactivated to stop writing them to the internal syslog. To do this, use a terminal program to enter a command in the format del setup/logging/trace <trace-name> (in this example del setup/logging/trace wlan). Save the boot-persistent configuration with the flash command.
3) Viewing the syslog on the access point:
3.1) Use a web browser to connect to the access point and go to the menu Diagnosis → Logs.
3.2) The extended logging information is now displayed in the syslog (in this example an excerpt from a CAPWAP trace). Traces can contain different log levels.
