12.3(8)JEC client timeout bug?

Unanswered Question
Jan 16th, 2008

I upgraded several AP 1230s to 12.3(8)JEC last week, and I'm seeing a strange dot11 association issue. It looks like clients are no longer being timed out, and the AP ends up with a huge list of every client that has ever associated.

A 'show dot11 associations all-client' shows data like this:

Connected for : 41515 seconds

Activity Timeout : 24159 seconds

Last Activity : 41437 seconds ago

This behavior cropped up after the upgrade. The previous JEB revision did not exhibit it.

Is this a known issue, and/or are there configuration directives I can use as a workaround?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
htarra Tue, 01/22/2008 - 10:25

I just recognized that the missing username issue is probably limited to one

subnet and checked the corresponding WDS device within this subnet by "show

wlccp wds nm". Despite enabling client tracking on the WLSE, the mode is listed inactive on the corresponding WDS device:

On all our other WDS devices client tracking is active and link to WNM is UP.

mltllt Mon, 01/28/2008 - 11:47

I seem to be having the same problem.

JEC seems to be really buggy!

rpettersen Thu, 01/31/2008 - 02:43

Hi !

Are you using a single antenna ?

In 12.3(8)JEC the commands :

antenna transmitt rigt/left

antenna receive right/left

Are missing, therefore you get a weeker

signal if you are using only one antenna

and the result is users drops out and in, alway's re-associate.

ICTNetworking Thu, 01/31/2008 - 03:21

We're using dual antennas. Also, the clients on the association list are long gone. An AP running this code can have 50 associated clients when no machine is within 500 feet.

mltllt Thu, 04/03/2008 - 12:47

JEC1 has the same problems. Although the missing antenna commands have been fixed.

Use JEA3, it seems to work.

Matt

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode