Wireless client lose or have a problem to connect Ap.

lucasfreitas83 — Mon, 05 Jul 2021 14:48:10 GMT

Hello everyone,

I have WLC 2504(8.2.161.0) and Aps 1702I(15.3(3)JC8) and 1602I(15.3(3)JC8).

I have 3 problems.

1º When you try to connect to the SSID Corp, for example, the connection is delayed or not connected. If you try again, the connection may successful.

2º After a stable connection, some clients end up losing connection (even though they have not been launched in the place) and the return signals, returning to stage 1.

3º Some of these clients sometimes after connecting receive the message that the connection is limited, but does not perceive problems, the client can use the network and normal browsing.I have already updated the wireless card driver, set a fixed DNS to isolate, have already tested on other devices and have the same symptom.

In the logs of APs I see why sometimes the radio interfaces flapping are down/UP.

ADM-AP04

Oct 30 11:59:59.915: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

Oct 30 12:00:00.915: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

Oct 30 12:00:00.963: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

Oct 30 12:40:46.859: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

Oct 30 12:40:47.023: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

Oct 30 17:46:32.519: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

Oct 30 17:46:33.531: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

Oct 31 18:55:00.515: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

Oct 31 18:55:01.527: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

ADM-AP10

Oct 30 12:50:57.111: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

Oct 30 12:50:58.119: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

ADM-AP11

Oct 31 13:32:13.166: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

However the times and amounts of time the problem occurs does not hit. I have more incidence of the problem than the one reported in the logs

These are the last logs of the controller

*apfMsConnTask_3: Nov 03 08:21:34.211: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:99:da.
*apfMsConnTask_4: Nov 03 08:21:29.383: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:9b:21.
*apfMsConnTask_3: Nov 03 08:21:18.492: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:9b:21.
*Dot1x_NW_MsgTask_1: Nov 03 08:21:15.763: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:449 Invalid replay counter from client 00:10:20:59:9b:c9 - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 02
*apfMsConnTask_1: Nov 03 08:20:52.907: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:99:5d.
*apfMsConnTask_2: Nov 03 08:20:51.030: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:6c:fd:fa.
*apfMsConnTask_5: Nov 03 08:20:50.275: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:9b:21.
*Dot1x_NW_MsgTask_5: Nov 03 08:20:49.475: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:449 Invalid replay counter from client 98:39:8e:5c:60:dd - got 00 00 00 00 00 00 00 03, expected 00 00 00 00 00 00 00 04
*apfMsConnTask_7: Nov 03 08:20:49.310: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:9b:bc.
*Dot1x_NW_MsgTask_6: Nov 03 08:20:46.722: %DOT1X-3-INVALID_WPA_KEY_STATE: 1x_eapkey.c:2532 Received EAPOL-key message while in invalid state (4) - version 2, type 3, descriptor 2, client e0:b5:2d:82:60:66
*Dot1x_NW_MsgTask_4: Nov 03 08:20:40.926: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:449 Invalid replay counter from client 00:23:68:fc:a3:cc - got 00 00 00 00 00 00 00 00, expected 00 00 00 00 00 00 00 01
*apfMsConnTask_3: Nov 03 08:20:36.143: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:99:5d.
*apfMsConnTask_7: Nov 03 08:20:35.451: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:6c:fd:fa.
*apfMsConnTask_7: Nov 03 08:20:33.335: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:9b:bc.
*apfMsConnTask_5: Nov 03 08:20:29.112: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:9b:21.
*apfMsConnTask_5: Nov 03 08:20:23.658: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:9b:21.
*apfMsConnTask_2: Nov 03 08:20:22.752: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:9b:bc.
*apfMsConnTask_5: Nov 03 08:20:12.009: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:9b:bc.
*apfMsConnTask_7: Nov 03 08:20:11.265: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:5a:d0:9c.
*apfMsConnTask_4: Nov 03 08:20:05.362: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:9b:bc.
*apfMsConnTask_3: Nov 03 08:20:00.031: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:9b:21.
*apfMsConnTask_4: Nov 03 08:19:54.918: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:9b:21.
*apfMsConnTask_5: Nov 03 08:19:54.353: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:5a:d0:9c.

*apfMsConnTask_4: Nov 03 08:19:50.941: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:99:5d.
*apfMsConnTask_5: Nov 03 08:19:33.251: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:9b:21.
*apfMsConnTask_3: Nov 03 08:19:32.090: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:9b:bc.
*apfMsConnTask_4: Nov 03 08:19:31.523: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:99:da.
*apfMsConnTask_3: Nov 03 08:19:13.490: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:5a:d0:9c.
*apfMsConnTask_4: Nov 03 08:18:53.890: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:9b:bc.
*apfMsConnTask_3: Nov 03 08:18:47.481: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:99:da.
*apfMsConnTask_4: Nov 03 08:18:38.874: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:9b:21.
*apfMsConnTask_3: Nov 03 08:18:14.742: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:99:5d.
*apfMsConnTask_3: Nov 03 08:18:07.944: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:9b:21.
*apfMsConnTask_4: Nov 03 08:18:00.755: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:99:da.
*apfMsConnTask_1: Nov 03 08:17:54.239: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:5a:d0:9c.
*Dot1x_NW_MsgTask_2: Nov 03 08:17:43.929: %DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:449 Invalid replay counter from client 00:10:20:59:99:da - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
*apfMsConnTask_7: Nov 03 08:17:40.681: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from stat 00 00 00 03

Please, does anyone have any ideas to check?

Re: Wireless client lose or have a problem to connect Ap.

Leo Laohoo — Fri, 03 Nov 2017 22:51:05 GMT

@lucasfreitas83 wrote:

*apfMsConnTask_3: Nov 03 08:21:34.211: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:216 Could not check supported rates. Invalid Supported Rates from station . Length :0. Mobile MAC: 00:10:20:59:99:da.

Check the data sheets or specification of the wireless clients and compare the data rates enabled on the controller. This log states that the wireless client is (possibly) only configured to support low data rates while your controller is configured for high-speed data rates.

Re: Wireless client lose or have a problem to connect Ap.

lucasfreitas83 — Mon, 06 Nov 2017 10:13:00 GMT

Leo, thanks for your comment.

I have collectors wifi, this error referer these collectors. I don't see the same error in MAC of the clients.

Re: Wireless client lose or have a problem to connect Ap.

lucasfreitas83 — Wed, 22 Nov 2017 18:29:16 GMT

Hey People,
I resolve my problem with an update the controller to version 8.3.133.

Thanks a lot.

Re: Wireless client lose or have a problem to connect Ap.

janf — Thu, 07 Dec 2017 16:45:49 GMT

What model APs where you having this problem with?

Thanks!

Re: Wireless client lose or have a problem to connect Ap.

lucasfreitas83 — Thu, 07 Dec 2017 16:48:37 GMT

Hello,

The Ap models are (1600 - 1700 - 2600)

Re: Wireless client lose or have a problem to connect Ap.

cm467 — Thu, 05 Apr 2018 15:19:13 GMT

Be careful when applying 8.3 updates. Many APs will only work with 8.0.x. Read the notes for supported APs before applying any updates or you will lose half of your wifi AP's.

Re: Wireless client lose or have a problem to connect Ap.

lucasfreitas83 — Thu, 05 Apr 2018 16:56:19 GMT

Hi,

All Aps work well in the WLC with new firmware.

APs 1600 and 1700 not have problem in 8.3.

My problem is the clients losing the connection with AP.

Re: Wireless client lose or have a problem to connect Ap.

d.friday — Mon, 15 Apr 2019 19:59:06 GMT

Invalid Supported Rates from stat 00 00 00 03
Did you turn off some of the data rates on the WLC, if so turn then back and see if that helps.
David

topic Re: Wireless client lose or have a problem to connect Ap. in Wireless

Wireless client lose or have a problem to connect Ap.

Re: Wireless client lose or have a problem to connect Ap.

Re: Wireless client lose or have a problem to connect Ap.

Re: Wireless client lose or have a problem to connect Ap.

Re: Wireless client lose or have a problem to connect Ap.

Re: Wireless client lose or have a problem to connect Ap.

Re: Wireless client lose or have a problem to connect Ap.

Re: Wireless client lose or have a problem to connect Ap.

Re: Wireless client lose or have a problem to connect Ap.