cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2232
Views
0
Helpful
1
Replies

Problems with WLC 5520 message APs AIR-AP1832I-N-K9 and AIR -AP1542I-N-K9

JoN41989
Level 1
Level 1

Hello,


I hope you are well, I currently have a WLC 5520 with firmware 8.5.135 which is recommended by Cisco, use this version because I have APs AIR-AP1832I-N-K9 (It is compatible with this version according to the documentation) and AIR -AP1542I-N-K9 (This model is compatible with this version and higher, lower, not in the documentation), now I am presenting partial disconnections in the AP. come back, I was able to capture the logs and it shows me the following:

*osapiBsnTimer: Jan 08 14:23:24.710: %DTLS-3-HANDSHAKE_FAILURE: openssl_dtls.c:3224 Failed to complete DTLS handshake with peer 172.16.2.48
*osapiBsnTimer: Jan 08 14:23:12.898: %DTLS-3-HANDSHAKE_FAILURE: openssl_dtls.c:3224 Failed to complete DTLS handshake with peer 172.16.2.74
*osapiBsnTimer: Jan 08 14:23:11.898: %DTLS-3-HANDSHAKE_FAILURE: openssl_dtls.c:3224 Failed to complete DTLS handshake with peer 172.16.2.64
*osapiBsnTimer: Jan 08 14:23:07.298: %DTLS-3-HANDSHAKE_FAILURE: openssl_dtls.c:3224 Failed to complete DTLS handshake with peer 172.16.2.61
*osapiBsnTimer: Jan 08 14:23:05.890: %DTLS-3-HANDSHAKE_FAILURE: openssl_dtls.c:3224 Failed to complete DTLS handshake with peer 172.16.2.209
*spamApTask1: Jan 08 14:23:00.490: %CAPWAP-3-DTLS_CLOSED_ERR: capwap_ac_sm.c:7076 00:7e:95:73:c0:c0:  DTLS connection closed forAP  172:16:2:177 (5256), Controller: 172:16:1:253 (5246) Echo Timer Expiry
*spamApTask1: Jan 08 14:23:00.490: %CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:7821 Did not receive heartbeat reply; AP: 00:7e:95:73:c0:c0
*spamApTask0: Jan 08 14:22:51.490: %CAPWAP-3-DTLS_CLOSED_ERR: capwap_ac_sm.c:7076 b0:90:7e:a5:38:00:  DTLS connection closed forAP  172:16:2:40 (5256), Controller: 172:16:1:253 (5246) AP Message Timeout
*spamApTask0: Jan 08 14:22:51.490: %CAPWAP-3-MAX_RETRANSMISSIONS_REACHED: capwap_ac_sm.c:7623 Max retransmissions reached on AP(b0:90:7e:a5:38:00),message (CAPWAP_CONFIGURATION_UPDATE_REQUEST
),number of pending messages(2)
*spamApTask4: Jan 08 14:22:48.486: %CAPWAP-3-DTLS_CLOSED_ERR: capwap_ac_sm.c:7076 00:7e:95:73:cb:a0:  DTLS connection closed forAP  172:16:3:156 (5256), Controller: 172:16:1:253 (5246) Echo Timer Expiry
*spamApTask4: Jan 08 14:22:48.486: %CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:7821 Did not receive heartbeat reply; AP: 00:7e:95:73:cb:a0
*osapiBsnTimer: Jan 08 14:22:47.886: %DTLS-3-HANDSHAKE_FAILURE: openssl_dtls.c:3224 Failed to complete DTLS handshake with peer 172.16.2.80
*osapiBsnTimer: Jan 08 14:22:42.878: %DTLS-3-HANDSHAKE_FAILURE: openssl_dtls.c:3224 Failed to complete DTLS handshake with peer 172.16.2.106
*osapiBsnTimer: Jan 08 14:22:29.666: %DTLS-3-HANDSHAKE_FAILURE: openssl_dtls.c:3224 Failed to complete DTLS handshake with peer 172.16.2.75
*osapiBsnTimer: Jan 08 14:22:29.666: %DTLS-3-HANDSHAKE_FAILURE: openssl_dtls.c:3224 Failed to complete DTLS handshake with peer 172.16.2.184
*osapiBsnTimer: Jan 08 14:21:24.594: %DTLS-3-HANDSHAKE_FAILURE: openssl_dtls.c:3224 Failed to complete DTLS handshake with peer 172.16.2.43
*osapiBsnTimer: Jan 08 14:21:18.990: %DTLS-3-HANDSHAKE_FAILURE: openssl_dtls.c:3224 Failed to complete DTLS handshake with peer 172.16.2.42
*spamReceiveTask: Jan 08 14:20:57.968: %CAPWAP-3-DTLS_CONN_ERR: capwap_ac.c:1118 b0:90:7e:a5:3c:80:  DTLS connection not found forAP  172.16.2.134 (5248), Controller: 172.16.1.253 (5246) send packet
*spamReceiveTask: Jan 08 14:20:57.911: %CAPWAP-3-DTLS_CONN_ERR: capwap_ac.c:1118 b0:90:7e:a5:c3:c0:  DTLS connection not found forAP  172.16.3.229 (5248), Controller: 172.16.1.253 (5246) send packet
*osapiBsnTimer: Jan 08 14:20:54.138: %DTLS-3-HANDSHAKE_FAILURE: openssl_dtls.c:3224 Failed to complete DTLS handshake with peer 172.16.2.105
*spamApTask1: Jan 08 14:20:53.338: %CAPWAP-3-DTLS_CLOSED_ERR: capwap_ac_sm.c:7076 00:7e:95:73:c9:c0:  DTLS connection closed forAP  172:16:2:73 (5248), Controller: 172:16:1:253 (5246) Echo Timer Expiry
*spamApTask1: Jan 08 14:20:53.338: %CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:7821 Did not receive heartbeat reply; AP: 00:7e:95:73:c9:c0
*spamApTask0: Jan 08 14:20:50.138: %CAPWAP-3-DTLS_CLOSED_ERR: capwap_ac_sm.c:7076 b0:90:7e:a5:c2:80:  DTLS connection closed forAP  172:16:2:96 (5248), Controller: 172:16:1:253 (5246) Echo Timer Expiry
*spamApTask0: Jan 08 14:20:50.138: %CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:7821 Did not receive heartbeat reply; AP: b0:90:7e:a5:c2:80
*spamApTask0: Jan 08 14:20:21.498: %CAPWAP-3-DTLS_CLOSED_ERR: capwap_ac_sm.c:7076 00:7e:95:73:98:e0:  DTLS connection closed forAP  172:16:2:64 (5256), Controller: 172:16:1:253 (5246) Echo Timer Expiry

 

Note some changes because it will also present IP conflicts with DHCP, while clean pools and all APs are by DHCP and disable the Enable DHCP Proxy option.

I hope you can support me or advise anyone who may be the best option or in your case raise a case.

I look forward to your comments.

Best regards

1 Reply 1

patoberli
VIP Alumni
VIP Alumni
This here "capwap_ac_sm.c:7821 Did not receive heartbeat reply; AP: b0:90:7e:a5:c2:80" sounds like your AP is unable to talk to the WLC. Do you maybe have a firewall between the IPs AP: 172:16:2:64, Controller: 172:16:1:253 which could cause this?
Or is this over a WAN network which could be overloaded for short times?
Review Cisco Networking for a $25 gift card