cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
688
Views
0
Helpful
1
Replies

WLAN APs send syslog broadcasts in controller mode

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

1 Accepted Solution

Accepted Solutions

dancampb
Level 7
Level 7

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.

View solution in original post

1 Reply 1

dancampb
Level 7
Level 7

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.

Getting Started

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:

Review Cisco Networking products for a $25 gift card