WLAN AP 3802i chatter: wl0: Beacon

[Gehrig_W]

Hello Cisco WLAN experts,

on some of our newly deployed 3802i-APs we face problems with WLAN clients and found the following

messages in the AP log file:

 kernel: [*01/27/2022 09:25:29.2937] chatter: wl0: Beacon rate info: Previous: 252249856 Current: 252053248
 kernel: [*01/27/2022 09:25:29.2937] chatter: wl0: Beacon PID : Previous: 9 Current: 6
 kernel: [*01/27/2022 09:39:59.0753] chatter: wl0: Beacon rate info: Previous: 252053248 Current: 252249856
 kernel: [*01/27/2022 09:39:59.0754] chatter: wl0: Beacon PID : Previous: 6 Current: 9
 kernel: [*01/27/2022 09:54:22.3144] chatter: wl0: Beacon rate info: Previous: 252249856 Current: 252053248
 kernel: [*01/27/2022 09:54:22.3145] chatter: wl0: Beacon PID : Previous: 9 Current: 6
 kernel: [*01/27/2022 10:08:45.2374] chatter: wl0: Beacon rate info: Previous: 252053248 Current: 252249856
 kernel: [*01/27/2022 10:08:45.2374] chatter: wl0: Beacon PID : Previous: 6 Current: 9
 kernel: [*01/27/2022 10:52:18.1861] chatter: wl0: Beacon rate info: Previous: 252249856 Current: 252053248
 kernel: [*01/27/2022 10:52:18.1862] chatter: wl0: Beacon PID : Previous: 9 Current: 6
 kernel: [*01/27/2022 11:06:42.4480] chatter: wl0: Beacon rate info: Previous: 252053248 Current: 252249856
 kernel: [*01/27/2022 11:06:42.4480] chatter: wl0: Beacon PID : Previous: 6 Current: 9
 kernel: [*01/27/2022 11:35:20.2132] chatter: wl0: Beacon rate info: Previous: 252249856 Current: 252053248
 kernel: [*01/27/2022 11:35:20.2132] chatter: wl0: Beacon PID : Previous: 9 Current: 6
 kernel: [*01/27/2022 11:49:40.3726] chatter: wl0: Beacon rate info: Previous: 252053248 Current: 251856640
 kernel: [*01/27/2022 11:49:40.3726] chatter: wl0: Beacon PID : Previous: 6 Current: 3

On Prime we see the attached Events for this WLAN-AP.

Can someone please explain what these messages mean ?

By the way, where can I find a complete Message Guide that explains all Log-file-entries and their log-level ?

I'm asking because we would like to use a cntrla Syslog-viewer on our Prie to identify WLAN APs with problems.

Thank You for Your help

Kind regards

Wini

[Anjana A]

Hi,

please explain the issue with the wlan client?

Share us the wlc model/AP model and the ios version.

Regards,

Anjana

[Gehrig_W]

Hello Anjana,

the WLC is a 5520, the AP a 3802i and SW-version running is  8.10.162.0.

Is  this something from Cleanair ? Bluetooth Beacons ?

Kind regards

Wini

[Scott Fella]

Before looking at the logs, can you explain what the issue(s) are?  Have you been able to reproduce the issue and then have you tested with other devices?  You have to gather more data and provide that so that others can help you. If you are using radius, look at the logs and try to correlate the data you have. 
Next steps is to run a debug and use this tool:

https://community.cisco.com/t5/wireless/wlc-debug-analyzer/td-p/2876223

[Gehrig_W]

Hello Scott,

thank You very much for pointing me to the WLC-debug-analyzer.

Please notice, that the shown Logs are from the WLAn AP itself, not the WLC.

Due You have any idea what a chatter is ?

kernel: [*01/27/2022 09:25:29.2937] chatter: wl0: Beacon rate info: Previous: 252249856 Current: 252053248
kernel: [*01/27/2022 09:25:29.2937] chatter: wl0: Beacon PID : Previous: 9 Current: 6

I'm also looking for an information source that covers all the WLAn AP log messages.

Do You know whethe such a Message-Guide for Cisco WLAN APs exist ?

Thank You in advance

Wini

[Scott Fella]

Wini,

TAC would have that information. As far as looking at logs, debugs ran from the controller is better than parsing syslog or ap output. I think majority of the engineers here would just Google the info and see if there is anything out there. There also is a bug toolkit you can search through, but for output on the AP, you might not find much. The controllers mange the access points, so that is why the debugs are your best way of identifying “what is it” messages. The debug analyzer will help you understand it.
Don’t go that route of looking at ap messages and use the tools that are provided to help.  

[Gehrig_W]

 I would also like to add info from another 3802i-APs log which shows even a crash of a cleanair sensor

accompanying the chattter log messages.

Jan 28 09:25:30 NCI: CLEANAIR: Slot 0 enabled
Jan 28 09:27:06 NCI: E0: Sensor receive failure (0), 22
Jan 28 09:27:06 NCI: E0: Fatal condition, shutdownNci needed, Receive Failure
Jan 28 09:27:06 NCI: CLEANAIR: Slot 0 shutdown
Jan 28 09:27:06 NCI: I0: shutdownNci
Jan 28 09:27:06 NCI: CLEANAIR: Excessive errors on slot 0. CleanAir turned off until disabled/re-enabled
Jan 28 09:42:55 kernel: [*01/28/2022 09:42:55.5579] chatter: wl1: Beacon rate info: Previous: 252643072 Current: 252446464
Jan 28 09:42:55 kernel: [*01/28/2022 09:42:55.5579] chatter: wl1: Beacon PID : Previous: 15 Current: 12
Jan 28 10:24:56 kernel: [*01/28/2022 10:24:56.5594] chatter: wl1: Beacon rate info: Previous: 252446464 Current: 252643072
Jan 28 10:24:56 kernel: [*01/28/2022 10:24:56.5594] chatter: wl1: Beacon PID : Previous: 12 Current: 15
Jan 28 10:43:09 kernel: [*01/28/2022 10:43:09.2719] chatter: wl1: Beacon rate info: Previous: 252643072 Current: 252839680
Jan 28 10:43:09 kernel: [*01/28/2022 10:43:09.2719] chatter: wl1: Beacon PID : Previous: 15 Current: 18

Our Prime tells us to reboot the devices:

CleanAir Sensor Status: 'Down' Error Code: 'CleanAir sensor is not operational due to crash. Please reset AP to resolve problem.'

Any idea ?

Wini

[marce1000]

      - FYI : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCti96438

 M.

[Gehrig_W]

Hello Marce1000,

thank You for Your link to Bug-Description CSCti96438

Unfortunately it does not cover the 3800-AP, nor does it contain information about which SW-version fixes this bug.

The proposed Debug Analyzer will not help in solving this AP-related problem.

The tool troubleshoots issues with wireless client association, authentication, roaming, and connectivity issues only.

Or does it also cover WLAN AP operational problems ?

The "chatter" and "Beacon" sound more like a problem in the area of Bluetooth Beacons around the AP that

create non-wireless influences on this AP maybe.

Kind regards

Wini

[Scott Fella]

Please open a TAC case to get your answer to your question.  Bugs, don't have to list all the affected devices, you just need to look at what other devices are affected and then figure out if it might be the bug you are hitting or not.  At the end, opening a tac case will point you in the right direction.  I wouldn't chase this issue "thinking" that its the cause of your problems, without really looking at the problem and isolating what is working and what is not from your testing.