04-15-2022 10:13 AM - edited 10-19-2023 12:54 PM
Log info attached from one AP and the WLC
04-16-2022 06:31 AM
I noticed this in the 17.8.1 release notes - try 17.3.5a and don't forget the CSCwb13784 SMU for the MTU issue?
AP flaps when WNCd to which it maps report high CPU utilization. |
04-16-2022 12:28 PM - edited 04-16-2022 12:29 PM
In the bootflash, do you see any crash file ? if you do you can run more, it might give you insight into why the AP crashed and you will have a better direction to work on the fix.
here is an example, while led to a bug :
9800#dir bootflash-2:
Directory of bootflash-2:/
24505 -rw- 158219 Feb 9 2022 18:05:12 -06:00 AP_D103.crash
24504 -rw- 74914 Jan 21 2022 00:43:53 -06:00 AP_E107.crash
9880#more bootflash-2:AP_D103.crash
AP_D103.crash crashed at Wed Jun 30 22:20:17 2021 UTC(BOOT_CNT 36) due to:
FIQ/NMI reset
hope this helps.
06-07-2022 12:36 AM
Hello All,
I am also facing the same issues in our 9800 WLC,some 3800 WAPs are disconnecting and rejoining for every 2 mins.
*Jun 7 02:20:46.207: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: Session-IP: 10.200.38.55[5256] Mac: 6c31.0e8a.c900 CAPWAP
DTLS session closed for AP, cause: DTLS server session shutdown.
Pls could someone help here
06-07-2022 01:45 AM
What version of IOS-XE?
What do you see on the AP logs?
06-07-2022 04:14 AM
IOS-17.3.4c
*Jun 7 02:20:46.207: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: Session-IP: 10.200.38.55[5256] Mac: 6c31.0e8a.c900 CAPWAP
DTLS session closed for AP, cause: DTLS server session shutdown.
06-07-2022 02:03 AM
>...could someone help here ?
- Did you already check the (previous) replies in the thread.
For the rest you may have the current controller configuration reviewed with (CLI) show tech wireless : have the output analyzed by https://cway.cisco.com/tools/WirelessAnalyzer/
Look for hints and advisories , not use command as mentioned in green , do not use traditional show tech-support , for Wireless Analyzer.
M.
06-07-2022 06:39 AM
I believe we resolved our issue by increasing the WLAN timeout session in the policy to 86400 and idle timeout to 3600 sec
01-17-2024 07:12 AM
Hello,
Can you please confirm how you changed the timeout?
Many thanks,
01-18-2024 05:35 AM
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