02-02-2022 06:37 AM - edited 02-02-2022 06:39 AM
Hello Cisco-WLAN-Experts,
this hospital has invested in more than 1000 of 3800-APs running on 8.10.162.0-Software.
Nearly on a dialy bais, we are forced to reset some of them due to the follwing error:
CleanAir Sensor Status: 'Down' Error Code:
'CleanAir sensor is not operational due to crash. Please reset AP to resolve problem.'
This series of Cisco APs is obviously not the best of breed.
Any idea, what might cause this annoying problem ?
And as already discussed, a lot of chatter: Wl1: Beacon on them:
Feb 2 13:57:13 kernel: [*02/02/2022 13:57:13.6984] chatter: wl1: Beacon rate info: Previous: 252249856 Current: 252446464
Feb 2 13:57:13 kernel: [*02/02/2022 13:57:13.6984] chatter: wl1: Beacon PID : Previous: 9 Current: 12
Feb 2 14:12:50 kernel: [*02/02/2022 14:12:50.8691] chatter: wl1: Beacon rate info: Previous: 252446464 Current: 252643072
Feb 2 14:12:50 kernel: [*02/02/2022 14:12:50.8691] chatter: wl1: Beacon PID : Previous: 12 Current: 15
Feb 2 14:28:29 kernel: [*02/02/2022 14:28:29.5507] chatter: wl1: Beacon rate info: Previous: 252643072 Current: 252446464
Feb 2 14:28:29 kernel: [*02/02/2022 14:28:29.5508] chatter: wl1: Beacon PID : Previous: 15 Current: 12
Feb 2 14:33:52 sshd[25618]: error: Could not get shadow information for admin
Feb 2 14:33:52 sshd[25618]: Accepted password for admin from 10.235.19.1 port 54094 ssh2
Feb 2 14:33:53 FIPS[25675]: *** shell: FIPS Mode = disabled ***
Feb 2 14:37:19 kernel: [02/02/2022 14:37:19.8421] SELinux: initialized (dev mtd_inodefs, type mtd_inodefs), not configured for labeling
Feb 2 14:37:20 kernel: [02/02/2022 14:37:20.3221] SELinux: initialized (dev mtd_inodefs, type mtd_inodefs), not configured for labeling
Feb 2 14:37:20 kernel: [02/02/2022 14:37:20.3421] SELinux: initialized (dev mtd_inodefs, type mtd_inodefs), not configured for labeling
Are these messages forcing the AP to go down on its knees sooner or later ?
Thank You for any Tipps to cure this mis-behaviour of Cisco WLAN APs.
Kind regards
Wini
02-02-2022 10:09 AM
- FYI : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwa49815 and or it seems that your issue 'sits on the same train' , advising to escalate through TAC.
M.
02-02-2022 01:55 PM
This happens regularly regardless of what AireOS. Either disable/enable the radio or reboot the AP.
Please observe the frequency of this event happening (daily, weekly, etc).
NOTE: Do not use the "reload" command from the AP or WLC. Instead, turn PoE off and then on.
02-03-2022 11:01 PM
Hello Leo and Marce1000,
thank You for Your tips and links.
I will try to observe this and will also try to send the WLAN APs syslog to our Prime.
Maybe the syslog messages will put more light on this.
Kind regards
Wini
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide