D-13
Cisco Wireless LAN Controller Configuration Guide
OL-17037-01
Appendix D Troubleshooting
Viewing Access Point Event Logs
Logging to console :
- Logging of system messages to console :
- Logging filter level.......................... errors
- Number of system messages logged.............. 0
- Number of system messages dropped............. 11622
- Logging of debug messages to console .......... Enabled
- Number of debug messages logged............... 0
- Number of debug messages dropped.............. 0
Logging to syslog :
- Syslog facility................................ local0
- Logging of system messages to syslog :
- Logging filter level.......................... errors
- Number of system messages logged.............. 8716
- Number of debug messages dropped............... 0
- Number of remote syslog hosts.................. 0
- Host 0....................................... Not Configured
- Host 1....................................... Not Configured
- Host 2....................................... Not Configured
Logging of traceback............................. Disabled
Logging of process information................... Disabled
Logging of source file informational............. Enabled
Timestamping of messages.........................
- Timestamping of system messages................ Enabled
- Timestamp format.............................. Date and Time
- Timestamping of debug messages................. Enabled
- Timestamp format.............................. Date and Time
Logging buffer (8722 logged, 2910 dropped)
*Mar 26 09:23:13.574: %MM-3-INVALID_PKT_RECVD: mm_listen.c:5508 Received an invalid packet
from 1.100.163.144. Source member:0.0.0.0. source member unknown.
*Mar 26 09:23:13.574: %MM-3-INVALID_PKT_RECVD: mm_listen.c:5508 Received an invalid packet
from 1.100.163.144. Source member:0.0.0.0. source member unknown.
Previous message occurred 2 times.
*Mar 26 09:22:44.925: %MM-3-INVALID_PKT_RECVD: mm_listen.c:5508 Received an invalid packet
from 1.100.163.144. Source member:0.0.0.0. source member unknown.
...
Viewing Access Point Event Logs
Access points log all system messages (with a severity level greater than or equal to notifications) to the
access point event log. The event log can contain up to 1024 lines of messages, with up to 128 characters
per line. When the event log becomes filled, the oldest message is removed to accommodate a new event
message. The event log is saved in a file on the access point flash, which ensures that it is saved through
a reboot cycle. To minimize the number of writes to the access point flash, the contents of the event log
are written to the event log file during normal reload and crash scenarios only.
Use these CLI commands to view or clear the access point event log from the controller:
•
To view the contents of the event log file for an access point that is joined to the controller, enter
this command:
show ap eventlog
Cisco_AP
Information similar to the following appears:
AP event log download has been initiated
Waiting for download to complete