05-18-2009 12:46 AM - edited 07-03-2021 05:36 PM
Hi,
in a test environment we use several 1131 wlan aps in controller mode with software version 4.2.176.0.
With wireshark running on a client pc in the same subnet as the wlan aps reside I saw that the wlan aps are sending syslog messages to the broadcast address 255.255.255.255 like "AP:<mac-address> %LWAPP-3-CLIENTERRORLOG: Decode Msg: could not match WLAN ID 5".
Does anybody know if this is expected behaviour and how I can correctly configure syslog on the aps in controller mode?
Many thanks in advance,
Thorsten Steffen
Solved! Go to Solution.
05-18-2009 09:04 AM
Hi,
Yes, the AP broadcasting syslogs is an expected behavior. It helps in troubleshooting AP join issues. If you don't want the AP broadcasting the messages you can either configure the AP's to send them as unicasts or disable the syslogging by defining a destination address of 0.0.0.0.
You would use the "config ap syslog host..." command on the controller to configure this. Obviously this command only works for the AP's after they have already joined the controller.
05-18-2009 09:04 AM
Hi,
Yes, the AP broadcasting syslogs is an expected behavior. It helps in troubleshooting AP join issues. If you don't want the AP broadcasting the messages you can either configure the AP's to send them as unicasts or disable the syslogging by defining a destination address of 0.0.0.0.
You would use the "config ap syslog host..." command on the controller to configure this. Obviously this command only works for the AP's after they have already joined the controller.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: