• Advertisement

HTC mobile phone access WLAN problem

Configuring Wireless Cisco Networks and Wireless Controllers.

Re:HTC mobile phone access WLAN problem

Postby Guest » Wed Jul 22, 2009 3:32 pm

*apfMsConnTask_0: Apr 21 11:12:12.918: 40:fc:89:30:3a:dd Sending Assoc Response to station on BSSID c0:62:6b:29:9d:40 (status 17)

Status Code 17 is usually used for Load Balancing...  If you run your debug longer, is your client ALWAYS associating to that same AP and ALWAYS getting rejected with Status 17? 

 

Does it work or fail if you move to another area with another AP?

 

 

Load-balancing should only reject a client X number of times and then let it on....   Your client clearly isn going somewhere else, so it should be allowed on.

 

Other than that, 17 is used for saying we can support another association....  I guess it could be possible the AP just won take new associations....  Can you get some other new device associated to the same AP?

 

 

Everytime Ive seen Status 17, it was load-balancing rejecting it... but this could be something new, and should impact all client on this AP (maybe other clients are properly going to another AP)

 

What is your load-balancing paramters?

what about the statistics (number of rejections)?

Guest
 

Advertisement

Re:HTC mobile phone access WLAN problem

Postby Guest » Wed Jul 22, 2009 3:56 pm

Hi,

 

Load Balance config :

Client Window Size
Maximum Denial Count

 

Load Balancing statistics :

Total Denied Client Count
Total Denial Message Sent
Exceeded Denial Max Limit Count
None 5G Candidate Count
None 2.4G Candidate Count

 

The following are the longer debug log, it have tried to associated to another AP ( 40:f4:ec:4a:74:60 )

 

*apfMsConnTask_0: Apr 21 11:10:45.850: 40:fc:89:30:3a:dd Adding mobile on LWAPP AP c0:62:6b:29:9d:40(0)
*apfMsConnTask_0: Apr 21 11:10:45.850: 40:fc:89:30:3a:dd Association received from mobile on AP c0:62:6b:29:9d:40
*apfMsConnTask_0: Apr 21 11:10:45.851: 40:fc:89:30:3a:dd Including FT Mobility Domain IE (length 5) in Initial assoc Resp to mobile
*apfMsConnTask_0: Apr 21 11:10:45.851: 40:fc:89:30:3a:dd Sending Assoc Response to station on BSSID c0:62:6b:29:9d:40 (status 17)
*osapiBsnTimer: Apr 21 11:10:50.833: 40:fc:89:30:3a:dd apfMsExpireCallback (apf_ms.c:599) Expiring Mobile!
*apfReceiveTask: Apr 21 11:10:50.833: 40:fc:89:30:3a:dd 0.0.0.0 START (0) Deleted mobile LWAPP rule on AP [c0:62:6b:29:9d:40]
*apfReceiveTask: Apr 21 11:10:50.833: 40:fc:89:30:3a:dd Deleting mobile on AP c0:62:6b:29:9d:40(0)
*apfMsConnTask_0: Apr 21 11:11:17.742: Deleting the client immediatly since WLAN is changed
*apfMsConnTask_0: Apr 21 11:11:26.600: 40:fc:89:30:3a:dd Adding mobile on LWAPP AP c0:62:6b:29:9d:40(0)
*apfMsConnTask_0: Apr 21 11:11:26.600: 40:fc:89:30:3a:dd Association received from mobile on AP c0:62:6b:29:9d:40
*apfMsConnTask_0: Apr 21 11:11:26.601: 40:fc:89:30:3a:dd Including FT Mobility Domain IE (length 5) in Initial assoc Resp to mobile
*apfMsConnTask_0: Apr 21 11:11:26.601: 40:fc:89:30:3a:dd Sending Assoc Response to station on BSSID c0:62:6b:29:9d:40 (status 17)
*osapiBsnTimer: Apr 21 11:11:31.434: 40:fc:89:30:3a:dd apfMsExpireCallback (apf_ms.c:599) Expiring Mobile!
*apfReceiveTask: Apr 21 11:11:31.434: 40:fc:89:30:3a:dd 0.0.0.0 START (0) Deleted mobile LWAPP rule on AP [c0:62:6b:29:9d:40]
*apfReceiveTask: Apr 21 11:11:31.434: 40:fc:89:30:3a:dd Deleting mobile on AP c0:62:6b:29:9d:40(0)
*apfMsConnTask_0: Apr 21 11:11:49.341: 40:fc:89:30:3a:dd Adding mobile on LWAPP AP c0:62:6b:29:9d:40(0)
*apfMsConnTask_0: Apr 21 11:11:49.341: 40:fc:89:30:3a:dd Association received from mobile on AP c0:62:6b:29:9d:40
*apfMsConnTask_0: Apr 21 11:11:49.341: 40:fc:89:30:3a:dd Including FT Mobility Domain IE (length 5) in Initial assoc Resp to mobile
*apfMsConnTask_0: Apr 21 11:11:49.341: 40:fc:89:30:3a:dd Sending Assoc Response to station on BSSID c0:62:6b:29:9d:40 (status 17)
*osapiBsnTimer: Apr 21 11:11:54.234: 40:fc:89:30:3a:dd apfMsExpireCallback (apf_ms.c:599) Expiring Mobile!
*apfReceiveTask: Apr 21 11:11:54.234: 40:fc:89:30:3a:dd 0.0.0.0 START (0) Deleted mobile LWAPP rule on AP [c0:62:6b:29:9d:40]
*apfReceiveTask: Apr 21 11:11:54.234: 40:fc:89:30:3a:dd Deleting mobile on AP c0:62:6b:29:9d:40(0)
*apfMsConnTask_0: Apr 21 11:12:12.918: 40:fc:89:30:3a:dd Adding mobile on LWAPP AP c0:62:6b:29:9d:40(0)
*apfMsConnTask_0: Apr 21 11:12:12.918: 40:fc:89:30:3a:dd Association received from mobile on AP c0:62:6b:29:9d:40
*apfMsConnTask_0: Apr 21 11:12:12.918: 40:fc:89:30:3a:dd Including FT Mobility Domain IE (length 5) in Initial assoc Resp to mobile
*apfMsConnTask_0: Apr 21 11:12:12.918: 40:fc:89:30:3a:dd Sending Assoc Response to station on BSSID c0:62:6b:29:9d:40 (status 17)
*osapiBsnTimer: Apr 21 11:12:17.834: 40:fc:89:30:3a:dd apfMsExpireCallback (apf_ms.c:599) Expiring Mobile!
*apfReceiveTask: Apr 21 11:12:17.834: 40:fc:89:30:3a:dd 0.0.0.0 START (0) Deleted mobile LWAPP rule on AP [c0:62:6b:29:9d:40]
*apfReceiveTask: Apr 21 11:12:17.834: 40:fc:89:30:3a:dd Deleting mobile on AP c0:62:6b:29:9d:40(0)
*apfMsConnTask_0: Apr 21 11:12:33.105: 40:fc:89:30:3a:dd Adding mobile on LWAPP AP 40:f4:ec:4a:74:60(0)
*apfMsConnTask_0: Apr 21 11:12:33.105: 40:fc:89:30:3a:dd Association received from mobile on AP 40:f4:ec:4a:74:60
*apfMsConnTask_0: Apr 21 11:12:33.105: 40:fc:89:30:3a:dd Including FT Mobility Domain IE (length 5) in Initial assoc Resp to mobile
*apfMsConnTask_0: Apr 21 11:12:33.105: 40:fc:89:30:3a:dd Sending Assoc Response to station on BSSID 40:f4:ec:4a:74:60 (status 17)
*osapiBsnTimer: Apr 21 11:12:38.034: 40:fc:89:30:3a:dd apfMsExpireCallback (apf_ms.c:599) Expiring Mobile!
*apfReceiveTask: Apr 21 11:12:38.034: 40:fc:89:30:3a:dd 0.0.0.0 START (0) Deleted mobile LWAPP rule on AP [40:f4:ec:4a:74:60]
*apfReceiveTask: Apr 21 11:12:38.034: 40:fc:89:30:3a:dd Deleting mobile on AP 40:f4:ec:4a:74:60(0)
*apfMsConnTask_0: Apr 21 11:12:40.828: 40:fc:89:30:3a:dd Adding mobile on LWAPP AP 40:f4:ec:4a:74:60(0)
*apfMsConnTask_0: Apr 21 11:12:40.828: 40:fc:89:30:3a:dd Association received from mobile on AP 40:f4:ec:4a:74:60
*apfMsConnTask_0: Apr 21 11:12:40.828: 40:fc:89:30:3a:dd Including FT Mobility Domain IE (length 5) in Initial assoc Resp to mobile
*apfMsConnTask_0: Apr 21 11:12:40.828: 40:fc:89:30:3a:dd Sending Assoc Response to station on BSSID 40:f4:ec:4a:74:60 (status 17)
*osapiBsnTimer: Apr 21 11:12:45.634: 40:fc:89:30:3a:dd apfMsExpireCallback (apf_ms.c:599) Expiring Mobile!
*apfReceiveTask: Apr 21 11:12:45.634: 40:fc:89:30:3a:dd 0.0.0.0 START (0) Deleted mobile LWAPP rule on AP [40:f4:ec:4a:74:60]
*apfReceiveTask: Apr 21 11:12:45.634: 40:fc:89:30:3a:dd Deleting mobile on AP 40:f4:ec:4a:74:60(0)
*apfMsConnTask_0: Apr 21 11:13:01.224: 40:fc:89:30:3a:dd Adding mobile on LWAPP AP c0:62:6b:29:9d:40(0)
*apfMsConnTask_0: Apr 21 11:13:01.224: 40:fc:89:30:3a:dd Association received from mobile on AP c0:62:6b:29:9d:40
*apfMsConnTask_0: Apr 21 11:13:01.224: 40:fc:89:30:3a:dd Including FT Mobility Domain IE (length 5) in Initial assoc Resp to mobile
*apfMsConnTask_0: Apr 21 11:13:01.224: 40:fc:89:30:3a:dd Sending Assoc Response to station on BSSID c0:62:6b:29:9d:40 (status 17)
*osapiBsnTimer: Apr 21 11:13:06.034: 40:fc:89:30:3a:dd apfMsExpireCallback (apf_ms.c:599) Expiring Mobile!
*apfReceiveTask: Apr 21 11:13:06.034: 40:fc:89:30:3a:dd 0.0.0.0 START (0) Deleted mobile LWAPP rule on AP [c0:62:6b:29:9d:40]
*apfReceiveTask: Apr 21 11:13:06.034: 40:fc:89:30:3a:dd Deleting mobile on AP c0:62:6b:29:9d:40(0)

 

Best Regards,

 

Jackson Ku

Guest
 

Re:HTC mobile phone access WLAN problem

Postby Guest » Wed Jul 22, 2009 5:00 pm

why dont you try disabling aggessive load balancing?

Guest
 

Re:HTC mobile phone access WLAN problem

Postby Guest » Wed Jul 22, 2009 5:19 pm

Line 7: *apfMsConnTask_0: Apr 21 11:10:45.851: 40:fc:89:30:3a:dd Sending Assoc Response to station on BSSID c0:62:6b:29:9d:40 (status 17)
Line 15: *apfMsConnTask_0: Apr 21 11:11:26.601: 40:fc:89:30:3a:dd Sending Assoc Response to station on BSSID c0:62:6b:29:9d:40 (status 17)
Line 22: *apfMsConnTask_0: Apr 21 11:11:49.341: 40:fc:89:30:3a:dd Sending Assoc Response to station on BSSID c0:62:6b:29:9d:40 (status 17)
Line 29: *apfMsConnTask_0: Apr 21 11:12:12.918: 40:fc:89:30:3a:dd Sending Assoc Response to station on BSSID c0:62:6b:29:9d:40 (status 17)
Line 36: *apfMsConnTask_0: Apr 21 11:12:33.105: 40:fc:89:30:3a:dd Sending Assoc Response to station on BSSID 40:f4:ec:4a:74:60 (status 17)
Line 43: *apfMsConnTask_0: Apr 21 11:12:40.828: 40:fc:89:30:3a:dd Sending Assoc Response to station on BSSID 40:f4:ec:4a:74:60 (status 17)
Line 50: *apfMsConnTask_0: Apr 21 11:13:01.224: 40:fc:89:30:3a:dd Sending Assoc Response to station on BSSID c0:62:6b:29:9d:40 (status 17)

 

umm... so a denial of 3 means that 4th  association response SHOULD have sent Status 0  unless it is something else going on....

So Im a little confused why your client wasn accepted

 

What if you disable load-balancing on the WLAN this thing associates to?  If it still rejecting the client, then either this AP seriously screwy, or something else is going on

 

 

but clearly, your load balancing statistics show a heck of alot of rejections...

Guest
 

Re:HTC mobile phone access WLAN problem

Postby Guest » Wed Jul 22, 2009 6:09 pm

Hi,

 

I will try to disable client load balance per WLAN.. ( I have also enable band select, maybe it is the reseon of high rejection?? )

 

Best Regards,

 

Jackson Ku

Guest
 

PreviousNext


  • Advertisement


Similar topics

Basic cisco ip phone configuration using CME
Forum: Cisco IP Communications
Author: boga83
Replies: 0

uc520 problem
Forum: Cisco IP Communications
Author: Guest
Replies: 0

nat problem with ver 8.4
Forum: Cisco Security
Author: Guest
Replies: 0

QoS on trunked access links
Forum: Cisco Switching
Author: Anonymous
Replies: 4

cannot call dn on a 7962 phone
Forum: Cisco IP Communications
Author: Guest
Replies: 1


Return to Cisco Wireless

Who is online

Users browsing this forum: No registered users and 2 guests