10-17-2011 09:59 AM
10-17-2011 09:54 PM
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
10-18-2011 08:27 AM
10-18-2011 09:00 AM
1) Are you using your 802.11A channels with APs in A/N mode (specifically 40MHz) or just traditional .11a in 20MHz mode?
2) When you have your high-order regulatory domain profile in place, have you tried running a packet capture session from that specific AP to see if you're getting probe requests from the specific client device? This would help narrow down whether your client device even considers it a valid channel to try to use.
For instance, I noticed that channel 165 was included in the 'default' regulatory domain profile under 3.x as a .11a channel (20MHz), but when using Network Monitor on a Win7 laptop (Intel Centrino 5300 chipset) it doesn't allow channel 165 as a valid channel for scanning. This is just one example case, YMMV depending on chipset, but you may run into similar findings. I'd give the packet capture noted above a try with your various devices and see if they ever try looking on your suspect channels.
Please let us know what you find, Aruba code version aside, supported channels on the client-side devices seems to still be a mixed bag.
10-19-2011 03:51 PM
Ref 1. Not sure. I need to get my hands on a Spectrum Analyzer. I can say that the 40 MHZ channel usage is checked under the High-Throughput Profiles, but no channel pairs are identified under the Regulatory Domain Profiles. Aren't the two related? Under our only "n" capable AP's (AP-105), the AP monitoring shows HT-20MHZ under "b/g" and HT-40MHZ under "a", but I'm not sure that is dictating real HT mode or what it is capable of.
Ref 2. I have not run a trace yet. Wasn't sure what I would be looking for. Your feedback is helpful, as although our lower-order channels (36 - 64) are checked, AP's are just using 36,40,44 and 48...
Time allowing, I will try the trace and let you know how it goes.
10-21-2011 08:28 AM
#1) Correct, you'd need to have channel pairs defined in your regulatory domain profile in order for the APs to start using them.
Thankfully, no need to find a spectrum analyzer to verify what channels/channel pairs are being used. If you log onto the controller via CLI, run the command "show ap active" to display the APs and their currently used channels. Once you define 40-MHz channel pairs in your reg-domain profile, you should start to see your 105's using the wide channels, indicated with a "+" or "-" next to the standard channel number, like the following:
10-24-2011 10:55 AM
Description of issue:
Symbol/Motorola clients are experiencing severe intermittent roaming delay while roaming through the warehouse. These delays times can be as long as 5-7 seconds. The application is thin-client and Wavelink telnet based. The delay is measured by pressing the enter key rapidly (about once every second) at a login screen while walking thru the warehouse. Delays are detected when the device does not receive the echo from the server.
Traces have been taken (with encryption on only) and multiple reauthentication requests were detected during delay times.
- The wired network has been tested thoroughly and is under 24/7 monitoring.
- A Laptop with an Intel 5100 chipset running the same test does NOT have this issue while roaming side by side with a Motorola device that actually experiences severe delay.
- 802.11A coverage in warehouse is excellent with Airmagnet heat map conducted with minimum 25 SNR, NO holes. The Motorola devices are only allowed to use 802.11A .
- Although the current encryption-type is WPA-2 AES, testing has been conducted with encryption DISABLED and has NO effect on the issue.
- Testing with fast roaming enabled or disabled has NO effect on the issue.
- Testing with high-throughput enabled or disabled has NO effect on the issue.
- Dual Aruba 6000 controllers (standardized on 184.108.40.206)
- AP70's at two locations and AP 124/125 at two locations
- HP2610 Switches at Distribution Layer
Clients and driver builds:
- Motorola / Symbol VC5090 (latest Fusion .23B)
- Motorola / Symbol MC9090 (latest Fusion .23B)
- Motorola / Symbol MC9500 (tested both Jedi .08R and hotfix .20R)
ap regulatory-domain-profile "default"
10-24-2011 12:39 PM
I tested last week with a Wyse thin client (dual-band wireless adapter) and the roaming hand-off is smooth as silk, even with the AP's txing on higher order "a" channels so the wireless environment seems to be exonerated. Why the HP thin client, Linksys dual-band USB card, and MAC Airport I tested with don't like those frequencies is still a mystery. I need to check some traces as Justin recommended and see what is happening behind the scenes.
You might check with Motorola but I didn't get any helpful responses with Alcatel or HP. Just some "try this" scenarios which didn't work....
I have changed our regulatory domain to all 802.11a "low-order" channels until we can get these thin clients changed out...