• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2920
  • Last Modified:

Cisco WLC 2500 Series - Cisco 1601i Access Points

We have two 1601i access points that are lightweight and controlled by a WLC 2500.

We are having issues with them dropping clients and the client will reassociate and drop again.  They go through this cycle constantly.  I have found on the web that the antenna power may be causing the issues.  I have tried changing the power settings and nothing works.

Does anyone know what we can try on this?
0
considerscs
Asked:
considerscs
  • 13
  • 10
9 Solutions
 
Craig BeckCommented:
What code are you running on the WLC?  I'll guess it's 7.4?

If so, try upgrading to 7.5 or 7.6.
0
 
considerscsAuthor Commented:
I am on 7.5.102.0.  I have tried upgrading in the past and it doesnt help.  Below is the link I found for the power issues for the antennas.

http://networkengineering.stackexchange.com/questions/2774/wifi-dropping-randomly-on-cisco-ap-1602

The only thing is, this refers to autonomous and I need it for lightweight or how to configure this on the WLC.
0
 
Craig BeckCommented:
The article you refer to only offers that answer as a possible solution and was not marked specifically as 'the answer'.

I've not seen any issues with the 1600 APs and v7.5 or 7.6 code.  I did with the 7.4 train, but that was resolved.

Can you post the logs from the WLC?
0
Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

 
considerscsAuthor Commented:
What 7.5 code have you run?  Higher than the 7.5.110.0?  I will attempt another upgrade to see if that resolves it.

Here is a portion of the logs.  I am seeing this error alot.

*Dot1x_NW_MsgTask_5: Mar 04 19:31:00.657: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:361 Invalid replay counter from client 84:4b:f5:62:09:75 - got 00 00 00 00 00 00 00 00, expected 00 00 00 00 00 00 00 01
*Dot1x_NW_MsgTask_5: Mar 04 19:31:00.648: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:361 Invalid replay counter from client 84:4b:f5:62:09:75 - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 01
*Dot1x_NW_MsgTask_5: Mar 04 19:31:00.005: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:361 Invalid replay counter from client 84:4b:f5:62:09:75 - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 00
*Dot1x_NW_MsgTask_5: Mar 04 19:30:56.834: #DOT1X-3-INVALID_WPA_KEY_STATE: 1x_eapkey.c:2112 Received EAPOL-key message while in invalid state (0) - version 1, type 3, descriptor 2, client 84:4b:f5:62:09:75
*Dot1x_NW_MsgTask_5: Mar 04 19:30:55.874: #DOT1X-3-INVALID_REPLAY_CTR: 1x_eapkey.c:361 Invalid replay counter from client 84:4b:f5:62:09:75 - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 02
0
 
Craig BeckCommented:
That looks like a TKIP problem.

What authentication/encryption are you using?
0
 
considerscsAuthor Commented:
WPA w/ TKIP
WPA2 w/ AES
0
 
Craig BeckCommented:
Can you turn off WPA/TKIP and see if you still get the errors/dropouts?
0
 
considerscsAuthor Commented:
After removing WPA policy I am still seeing the drops.

Here is the log after this change was made seeing the same as above.

INVALID_REPLAY_CTR: 1x_eapkey.c:361 Invalid replay counter from client bc:92:6b:88:d0:fb - got 00 00 00 00 00 00 00 02, expected 00 00 00 00 00 00 00 03
0
 
considerscsAuthor Commented:
The weird part is that we have two 1602i and they are the ones dropping clients, but we have 8 1130s and never have any issues with dropping clients.
0
 
Craig BeckCommented:
Ok so if you take a client which works fine on the 1130 APs, and try to connect to the 1600 APs, do you see the issue?

Are the 1130s and the 1600s using the same WLANs?
0
 
considerscsAuthor Commented:
Yes, all using same WLAN.  We have a production and free wifi.  When clients move buildings, they are fine on 1130s, when they come to the 1602i they drop consistently.

On the free wifi on the 1602i, they can connect and stay connected, but on the production which is protected, they continue to drop.
0
 
Craig BeckCommented:
How are you doing the 802.1x?  What RADIUS do you have?  Can you see anything in the RADIUS logs?
0
 
considerscsAuthor Commented:
802.1x is not enabled on the WLAN under authentication key management in the WLAN settings.

Only PSK is enabled with PSK format of ASCII
0
 
Craig BeckCommented:
Ok, so I don't understand why you're seeing this:

DOT1X-3-INVALID_WPA_KEY_STATE
That would mean you're trying to use 802.1x at the client side, but if you're using a PSK the client shouldn't be trying to use 802.1x

How are your clients configured to connect to the WLAN? Do you do this manually or via GPO for example?
0
 
considerscsAuthor Commented:
Manually all clients are added as we image their pcs and set them up on site for them.  So they are joined based on the wireless network showing in Windows 7, and then typing in the password.
0
 
Craig BeckCommented:
Are you using a recent NIC driver?
0
 
considerscsAuthor Commented:
Yes, all these machines having conneciton issues are brand new machines with the most updated drivers from the manufacturer.
0
 
considerscsAuthor Commented:
i did see somewhere that the Intel 6500 (I believe thats the model) card is know by Cisco to have issues with the 1602i, but we do not have any of those.
0
 
Craig BeckCommented:
In the Layer2 Security tab for the WLAN, do you have Auth Key Mgmt set to 802.1X or 802.1X + CCKM?
0
 
considerscsAuthor Commented:
Neither are checked.  I only have PSK checked.  See the image attached for a screenshot of this tab.

Maybe not having these checked is the issue.
auth-key-management.png
0
 
Craig BeckCommented:
Ok so it has to be something that the client is doing then.  The WLC isn't expecting to see any 802.1x so when the client sends an EAPOL frame it drops the connection.

You should review the client's configuration.
0
 
considerscsAuthor Commented:
My only concern with it being the WLC versus the client is that, these same clients connect to the exact same WLC and WLAN at another building with an 1130 AP.  So why is the 1602i the only ones that are kicking clients?
0
 
considerscsAuthor Commented:
problem not resolved but giving points for the assistance
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Turn Raw Data into a Real Career

There’s a growing demand for qualified analysts who can make sense of Big Data. With an MS in Data Analytics, you can become the data mining, management, mapping, and munging expert that today’s leading corporations desperately need.

  • 13
  • 10
Tackle projects and never again get stuck behind a technical roadblock.
Join Now