Failed DTLS handshake and rejoining

[frederick.mercado]

Log info attached from one AP and the WLC

[Rich R]

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?

CSCwa35350

AP flaps when WNCd to which it maps report high CPU utilization.

[ammahend]

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.

[ChristiesNetwork_Team7857]

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

[Rich R]

What version of IOS-XE?

What do you see on the AP logs?

[ChristiesNetwork_Team7857]

 

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.

[marce1000]

                           >...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.

[frederick.mercado]

I believe we resolved our issue by increasing the WLAN timeout session in the policy to 86400 and idle timeout to 3600 sec

[hara12386]

Hello,

Can you please confirm how you changed the timeout?

Many thanks,

[Rich R]

https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-9/config-guide/b_wl_17_9_cg/m_config_model.html#task_lv2_g5n_kz