Cisco WLAN controller - 802.11b stuck in probing

Unanswered Question
Apr 23rd, 2010

Hello all,

In a Cisco 4404 WLAN controller, why do the 802.11b clients get stuck in probing instead of associated?  (802.11g works fine).  I've tried the following:

1. Disabled/enabled all b/g radios

2. set 11mpbs rate to supported instead of mandatory

Both steps did not resolve the issue.  Please help!

-Will

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
rdvorak Sat, 04/24/2010 - 03:06

Hi,

beacons are send with the lowest mandatory rate so is 1, 2, 5.5 or 11 one of your mandatory rates.

If not the 802.11b station can't "hear" that beacons.

You could trace one beacon just to make sure to see all mandatory&supported rates from the clients point of view.

Kind regards,

Ron

George Stefanick Sat, 04/24/2010 - 06:51

If you drop into the CLI and run a "debug client" on one of your 802.11b devices you may see something of interest. Sounds like either data rate, aironet extensions or something is config that the B clients dont like.

wchengcisco Sun, 04/25/2010 - 06:41

Here's the debug log of a station stuck in probing (00:1c:bf:2e:3a:fc).  For some reason, the associated AP in the web gui is different than the one shown in the debug...

(Cisco Controller) >
(Cisco Controller) >Sun Apr 25 13:29:33 2010: 00:1c:bf:2e:3a:fc Adding mobile 00:1c:bf:2e:3a:fc on LWAPP AP 00:0b:85:7a:a1:a0(1)
Sun Apr 25 13:29:33 2010: 00:1c:bf:2e:3a:fc Scheduling deletion of Mobile Station: 00:1c:bf:2e:3a:fc (callerId: 23) in 5 seconds
Sun Apr 25 13:29:33 2010: 00:1c:bf:2e:3a:fc Changing state for mobile 00:1c:bf:2e:3a:fc on AP 00:0b:85:7a:a1:a0 from Idle to Probe
Sun Apr 25 13:29:33 2010: 00:1c:bf:2e:3a:fc Scheduling deletion of Mobile Station: 00:1c:bf:2e:3a:fc (callerId: 24) in 5 seconds
Sun Apr 25 13:29:33 2010: 00:1c:bf:2e:3a:fc Scheduling deletion of Mobile Station: 00:1c:bf:2e:3a:fc (callerId: 24) in 5 seconds
Sun Apr 25 13:29:33 2010: 00:1c:bf:2e:3a:fc Scheduling deletion of Mobile Station: 00:1c:bf:2e:3a:fc (callerId: 24) in 5 seconds
Sun Apr 25 13:29:33 2010: 00:1c:bf:2e:3a:fc Scheduling deletion of Mobile Station: 00:1c:bf:2e:3a:fc (callerId: 24) in 5 seconds
Sun Apr 25 13:29:33 2010: 00:1c:bf:2e:3a:fc Scheduling deletion of Mobile Station: 00:1c:bf:2e:3a:fc (callerId: 24) in 5 seconds
Sun Apr 25 13:29:33 2010: 00:1c:bf:2e:3a:fc Scheduling deletion of Mobile Station: 00:1c:bf:2e:3a:fc (callerId: 24) in 5 seconds
Sun Apr 25 13:29:33 2010: 00:1c:bf:2e:3a:fc Scheduling deletion of Mobile Station: 00:1c:bf:2e:3a:fc (callerId: 24) in 5 seconds
Sun Apr 25 13:29:33 2010: 00:1c:bf:2e:3a:fc Scheduling deletion of Mobile Station: 00:1c:bf:2e:3a:fc (callerId: 24) in 5 seconds
Sun Apr 25 13:29:33 2010: 00:1c:bf:2e:3a:fc Scheduling deletion of Mobile Station: 00:1c:bf:2e:3a:fc (callerId: 24) in 5 seconds
Sun Apr 25 13:29:39 2010: 00:1c:bf:2e:3a:fc 0.0.0.0 START (0) Deleted mobile LWAPP rule on AP [00:0b:85:7a:a1:a0]
Sun Apr 25 13:29:39 2010: 00:1c:bf:2e:3a:fc Deleting mobile 00:1c:bf:2e:3a:fc on AP 00:0b:85:7a:a1:a0(1)
Sun Apr 25 13:29:57 2010: 00:1c:bf:2e:3a:fc Adding mobile 00:1c:bf:2e:3a:fc on LWAPP AP 00:0b:85:7a:a1:a0(1)
Sun Apr 25 13:29:57 2010: 00:1c:bf:2e:3a:fc Scheduling deletion of Mobile Station: 00:1c:bf:2e:3a:fc (callerId: 23) in 5 seconds
Sun Apr 25 13:29:57 2010: 00:1c:bf:2e:3a:fc Changing state for mobile 00:1c:bf:2e:3a:fc on AP 00:0b:85:7a:a1:a0 from Idle to Probe
Sun Apr 25 13:29:57 2010: 00:1c:bf:2e:3a:fc Scheduling deletion of Mobile Station: 00:1c:bf:2e:3a:fc (callerId: 24) in 5 seconds
Sun Apr 25 13:29:57 2010: 00:1c:bf:2e:3a:fc Scheduling deletion of Mobile Station: 00:1c:bf:2e:3a:fc (callerId: 24) in 5 seconds
Sun Apr 25 13:29:57 2010: 00:1c:bf:2e:3a:fc Scheduling deletion of Mobile Station: 00:1c:bf:2e:3a:fc (callerId: 24) in 5 seconds
Sun Apr 25 13:29:57 2010: 00:1c:bf:2e:3a:fc Scheduling deletion of Mobile Station: 00:1c:bf:2e:3a:fc (callerId: 24) in 5 seconds
Sun Apr 25 13:29:57 2010: 00:1c:bf:2e:3a:fc Scheduling deletion of Mobile Station: 00:1c:bf:2e:3a:fc (callerId: 24) in 5 seconds
Sun Apr 25 13:29:57 2010: 00:1c:bf:2e:3a:fc Scheduling deletion of Mobile Station: 00:1c:bf:2e:3a:fc (callerId: 24) in 5 seconds
Sun Apr 25 13:29:57 2010: 00:1c:bf:2e:3a:fc Scheduling deletion of Mobile Station: 00:1c:bf:2e:3a:fc (callerId: 24) in 5 seconds
Sun Apr 25 13:29:57 2010: 00:1c:bf:2e:3a:fc Scheduling deletion of Mobile Station: 00:1c:bf:2e:3a:fc (callerId: 24) in 5 seconds
Sun Apr 25 13:29:57 2010: 00:1c:bf:2e:3a:fc Scheduling deletion of Mobile Station: 00:1c:bf:2e:3a:fc (callerId: 24) in 5 seconds
Sun Apr 25 13:30:03 2010: 00:1c:bf:2e:3a:fc 0.0.0.0 START (0) Deleted mobile LWAPP rule on AP [00:0b:85:7a:a1:a0]
Sun Apr 25 13:30:03 2010: 00:1c:bf:2e:3a:fc Deleting mobile 00:1c:bf:2e:3a:fc on AP 00:0b:85:7a:a1:a0(1)
Sun Apr 25 13:30:21 2010: 00:1c:bf:2e:3a:fc Adding mobile 00:1c:bf:2e:3a:fc on LWAPP AP 00:0b:85:7a:a1:a0(1)

George Stefanick Sun, 04/25/2010 - 08:44

hey bud,

Are you using any security? If so, turn it off and see what happens. Also see if Aironet IE is checked under WLANS

wchengcisco Sun, 04/25/2010 - 09:56

Thanks for the response.

No there is no security.  This controller is used in a hotel so everything is open system.  Also I think this is an older firmware, because Aironet IE is not there as an option under WLAN.

There are so many more users connected on the G network.. that makes me just want to forget about this b issue for now

Actions

This Discussion

Related Content