Wireless client issue

[LEN SNEED]

I am having trouble with a wlan at one of our locations.  This problem occurs randomly with most of the users there but in the example below I have included the most troubled.  The clients experience awful wireless performance and response times for periods of time and then function well at other times.  There are also 3 other wlans from 3 seperate locations on this wlc.  I have had difficulty in finding docs on the debug messages for wlc including the ones below.  The user in the example below experiences the problem continually.  I have checked for interference sources in the different areas of the building however multiple users can be associated to the same ap in the same are and only one will have the problem.  I have also checked my coverage areas, ap channels and tx powers and all seem fine.  Any ideas?

Cisco Controller) >debug location client enable

*Jan 17 08:40:42.515: 00:1c:bf:d6:42:a9 LBS  Client 00:1c:bf:d6:42:a9 pkt from AP 00:23:eb:0b:bb:d0(1) RSSI (A -89, B -80), SNR 32, Chan 0, Pwr 0, Type 0

*Jan 17 08:40:42.515: 00:1c:bf:d6:42:a9 Load Balancing Timeout for AP 00:23:eb:0b:bd:f0(0) for mobile 00:1c:bf:d6:42:a9 with RSSI (A -68, B -68), SNR 32, time (A 2486447258, B 2486447258)

*Jan 17 08:40:42.515: 00:1c:bf:d6:42:a9 Load Balancing Timeout for AP 00:23:eb:0b:bd:20(0) for mobile 00:1c:bf:d6:42:a9 with RSSI (A -50, B -52), SNR 32, time (A 2486447257, B 2486447257)

*Jan 17 08:40:42.515: 00:1c:bf:d6:42:a9 Load Balancing Timeout for AP 00:23:eb:0b:bb:d0(0) for mobile 00:1c:bf:d6:42:a9 with RSSI (A -65, B -59), SNR 32, time (A 2486447230, B 2486447230)

*Jan 17 08:40:42.515: 00:1c:bf:d6:42:a9 Load Balancing Timeout for AP 00:23:eb:0b:b3:60(0) for mobile 00:1c:bf:d6:42:a9 with RSSI (A -35, B -49), SNR 32, time (A 2486447285, B 2486447285)

*Jan 17 08:40:42.515: 00:1c:bf:d6:42:a9 Load Balancing Timeout for AP 00:23:eb:0b:b3:60(1) for mobile 00:1c:bf:d6:42:a9 with RSSI (A -67, B -54), SNR 32, time (A 2486447333, B 2486447333)

*Jan 17 08:40:42.515: 00:1c:bf:d6:42:a9 Load Balancing Timeout for AP 00:23:eb:0b:bb:d0(1) for mobile 00:1c:bf:d6:42:a9 with RSSI (A -88, B -90), SNR 32, time (A 2486447370, B 2486447370)

*Jan 17 08:40:42.515: 00:1c:bf:d6:42:a9 Load Balancing Timeout for AP 00:23:eb:0b:bd:f0(1) for mobile 00:1c:bf:d6:42:a9 with RSSI (A -79, B -89), SNR 32, time (A 2486447339, B 2486447339)

*Jan 17 08:40:42.515: 00:1c:bf:d6:42:a9 Load Balancing Timeout for AP 00:23:eb:0b:bd:20(1) for mobile 00:1c:bf:d6:42:a9 with RSSI (A -76, B -75), SNR 32, time (A 2486447354, B 2486447354)

*Jan 17 08:40:42.515: 00:1c:bf:d6:42:a9 LBS 8 entries expired, RSSI client 00:1c:bf:d6:42:a9
*Jan 17 08:40:42.515: 00:1c:bf:d6:42:a9 LBS new RSSI A -89, client 00:1c:bf:d6:42:a9
*Jan 17 08:40:42.515: 00:1c:bf:d6:42:a9 LBS new RSSI B -80, client 00:1c:bf:d6:42:a9
*Jan 17 08:40:42.515: 00:1c:bf:d6:42:a9 LBS Client data stored from AP 00:23:eb:0b:bb:d0(1) new saved RSSI (A -89, B -80), SNR 32, inUse 1,  [rcvd RSSI (A -89, B -80), SNR 32]

*Jan 17 08:40:42.527: 00:1c:bf:d6:42:a9 LBS  Client 00:1c:bf:d6:42:a9 pkt from AP 00:23:eb:0b:bd:f0(1) RSSI (A -76, B -82), SNR 32, Chan 0, Pwr 0, Type 0

*Jan 17 08:40:42.527: 00:1c:bf:d6:42:a9 LBS new RSSI A -76, client 00:1c:bf:d6:42:a9
*Jan 17 08:40:42.527: 00:1c:bf:d6:42:a9 LBS new RSSI B -82, client 00:1c:bf:d6:42:a9
*Jan 17 08:40:42.527: 00:1c:bf:d6:42:a9 LBS Client data stored from AP 00:23:eb:0b:bd:f0(1) new saved RSSI (A -76, B -82), SNR 32, inUse 1,  [rcvd RSSI (A -76, B -82), SNR 32]

*Jan 17 08:40:42.527: 00:1c:bf:d6:42:a9 LBS  Client 00:1c:bf:d6:42:a9 pkt from AP 00:23:eb:0b:b3:60(1) RSSI (A -60, B -53), SNR 32, Chan 0, Pwr 0, Type 0

*Jan 17 08:40:42.527: 00:1c:bf:d6:42:a9 LBS new RSSI A -60, client 00:1c:bf:d6:42:a9
*Jan 17 08:40:42.527: 00:1c:bf:d6:42:a9 LBS new RSSI B -53, client 00:1c:bf:d6:42:a9
*Jan 17 08:40:42.527: 00:1c:bf:d6:42:a9 LBS Client data stored from AP 00:23:eb:0b:b3:60(1) new saved RSSI (A -60, B -53), SNR 32, inUse 1,  [rcvd RSSI (A -60, B -53), SNR 32]

*Jan 17 08:40:42.543: 00:1c:bf:d6:42:a9 LBS  Client 00:1c:bf:d6:42:a9 pkt from AP 00:23:eb:0b:bd:20(1) RSSI (A -70, B -86), SNR 32, Chan 0, Pwr 0, Type 0

*Jan 17 08:40:42.543: 00:1c:bf:d6:42:a9 LBS new RSSI A -70, client 00:1c:bf:d6:42:a9
*Jan 17 08:40:42.543: 00:1c:bf:d6:42:a9 LBS new RSSI B -86, client 00:1c:bf:d6:42:a9
*Jan 17 08:40:42.543: 00:1c:bf:d6:42:a9 LBS Client data stored from AP 00:23:eb:0b:bd:20(1) new saved RSSI (A -70, B -86), SNR 32, inUse 1,  [rcvd RSSI (A -70, B -86), SNR 32]

Thanks in advance.

[Stephen Rodriguez · Accepted solution]

Len,

      The debug you are running, debug location client enable, is not the correct debug.  It is used for when you are trying to debug the actual location/MSE messages about a client.

You should run debug client < cleints mac address>

This debug will give you the information about how the client is trying to access the network, EAP messages, as well as if the keys are being passed or not.

Cheers,
Steve

--

If  this helps you and/or answers your question please mark the question as "answered" and/or rate it, so other users can easily find it.

[LEN SNEED]

Thanks Steve.  Will do.

[LEN SNEED]

Thanks for the input Steve.  I still haven't quite got the exact cause of the issue

nailed down but I am making a visit to the site this week because I have discovered a possible source of interference at the location.

Thanks again for your response.

Len.