WLAN APs send syslog broadcasts in controller mode

Answered Question
May 18th, 2009
User Badges:

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

Correct Answer by dancampb about 8 years 1 week ago

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.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
dancampb Mon, 05/18/2009 - 09:04
User Badges:
  • Cisco Employee,

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.

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode