Here's my generic check-list that's working well for our environment.  The 
biggest improvements will be seen when MPDU and ADDBA are enabled, but 
you'll also see improvement if you flip over to g/n radio mode (keep those 
rare-but-pesky 802.11b clients away), and boost your min basic rate as 
high as your environment can handle.

These settings apply to the 36xx APs.  If an option isn't listed here, I 
leave it default.

AP -> Radio1

        Admin Mode: On
        Radio Mode: a/n
        Channel Width: 40MHz
        ATPC: Off*
 
        -> Advanced
                Dynamic Channel Selection:      Off
                Min Basic Rate: 12Mbps
 
                11N:
                        Protection Mode: Enabled
                        40MHz Protection Mode: CTS Only
                        40MHz Prot. Channel Offset: 20MHz
                        Aggregate MSDUs:        Disabled
                        Aggregate MPDUs:        Enabled
                        ADDBA Support:  Enabled
 

AP -> Radio2

        Admin Mode:     On
        Radio Mode: g/n
        Channel Width: 20MHz**
 
        -> Advanced
                Dynamic Channel Selection:      Off
                Min Basic Rate: 12Mbps
 
                11G:
                        Protection Mode: None (Only if in g/n radio mode!)
 
                11N:
                        Protection Mode:        Enabled
                        Aggregate MSDUs:        Disabled
                        Aggregate MPDUs:        Enabled
                        ADDBA Support:  Enabled



BTW, I can only sustain ~100Mbps throughput when connected to the 5GHz 
radio and there are no a-only radios associated.  As soon as a non-n radio 
associates, protection mode kicks in and you're down to about 30-40Mbps 
sustained w/these settings.

With MPDU and ADDBA disabled today, maximum throughput for my test client 
was 23Mbps  on @5GHz 802.11n.  :(


Derek Johnson
Data Communications Coordinator
Fort Hays State University
(785) 628 - 5688
[email protected]






From:   Andrew Hines <[email protected]>
To:     "Enterasys Customer Mailing List" <[email protected]>
Date:   09/06/2011 11:10 AM
Subject:        RE: [enterasys] Enterasys HiPath and Intel Clients



Hello Derek,
 
Up until now our testing has been fairly basic connectivity testing and 
verification that all our SSIDs work as before.
Based on your recommendations we have seen that enabling MPDU and ADDBA 
has increased FTP transfers from 6mb to 27mb for an N client connected on 
the 2.4 band!
We still are not up to 100Mb that you are reaching, so yes, if you could 
share your settings that would be great.
 
Thanks a lot sharing this information.
 
Andrew
 
 

From: [email protected] [mailto:[email protected]] 
Sent: martes, 06 de septiembre de 2011 15:27
To: Enterasys Customer Mailing List
Subject: RE: [enterasys] Enterasys HiPath and Intel Clients
 
Andrew, 

Before our initial deployment, I had a chance to tweak our settings in a 
"lab" (aka my office) to see what worked best for our environment.  I 
found I could really ramp up the sustained throughput for bulk transfers 
(SMB, large HTTP downloads, etc.) by enabling MPDU/ADDBA --  from ~35Mbps 
to ~100Mbps... 

MSDU - Disabled 
MPDU - Enabled 
ADDBA - Enabled 

Enabling MSDU caused my MacBook Pro's Atheros-based N adapter to stop 
receiving traffic after transferring x-number of bytes (very similar to 
the Intel 1000BGN problem).  It didn't seem to make a performance 
difference when enabled, so I wrote it off at the time and left it 
disabled.   

I'm interested to hear what you've found with your Airtime Fairness 
testing... Ours is set to 100% airtime and seems to be working well. 

Also, I'd be happy to share with the list the AP-specific settings I 
configure during deployment, if anyone is interested. 

Derek Johnson
Data Communications Coordinator
Fort Hays State University
(785) 628 - 5688
[email protected]






From:        Andrew Hines <[email protected]> 
To:        "Enterasys Customer Mailing List" <[email protected]> 
Date:        09/05/2011 04:04 AM 
Subject:        RE: [enterasys] Enterasys HiPath and Intel Clients 




Hello Derek, 
  
I have noticed that on our HiPath deployment both aggregate MPDUs and 
ADDBA support are disabled by default… We are in the process of converting 
our RoamAbout wireless network to HiPath and we have noticed there are 
lots of sub menus we still need to investigate and see if there are knobs 
and buttons that we should tune to get better performance, but at this 
point we have only really focused our testing on Airtime Fairness… so I 
was wondering if you could let me know what led you to enable both of 
these? 
  
Thanks 
Andrew 
  
 


From: [email protected] [mailto:[email protected]] 
Sent: viernes, 02 de septiembre de 2011 15:19
To: Enterasys Customer Mailing List
Subject: RE: [enterasys] Enterasys HiPath and Intel Clients 
  
Working with GTAC, they were able to isolate the two features causing 
certain Intel adapters grief in my test environment --  A-MPDU and ADDBA. 
Since disabling those features on the AP radios, my Intel 1000BGN testbox 
hasn't had any trouble sending/receiving traffic. 

To answer your specific question, the vast majority of complaints have 
come from users with HP systems running Windows 7 SP1 64-bit.  We've seen 
a few Vista SP2 32-bit and various Dell/Asus Windows 7 SP2 32-bit systems 
in the mix as well.  Two systems ran Atheros or RealTek and both users 
reported that a driver update fixed their issues.  All others have had 
Intel adapters of some kind, with the majority equipped with Intel 
1000BGN. 

There's a significant Mac presence in these particular buildings, and 
we've heard nothing but good things so far.  However if memory serves, 
Apple wifi hardware is either Atheros or Broadcom-based depending on the 
device. 

My gut says this is an Intel-HiPath bug, something to do with the behavior 
of the Intel driver itself. 

Derek Johnson
Data Communications Coordinator
Fort Hays State University
(785) 628 - 5688
[email protected]






From:        Jolyon Ansuz <[email protected]> 
To:        "Enterasys Customer Mailing List" <[email protected]> 
Date:        09/01/2011 08:09 PM 
Subject:        RE: [enterasys] Enterasys HiPath and Intel Clients 
 





Is this an operating system issue? Can this be reproduced on *nix, Mac, 
others?

Could this be a drivers issue on the OS, could this be a firmware issue on 
the H/W?

5c

Jolyon Ansuz

Senior Network and Communications Administrator
Communications Infrastructure 
Information Technology 
University of New England 
Armidale NSW 2351 
P: +61 2 6773 3568

From: [email protected] [mailto:[email protected]] 
Sent: Thursday, September 01, 2011 6:31 PM
To: Enterasys Customer Mailing List
Subject: [enterasys] Enterasys HiPath and Intel Clients

Is anyone out there having any trouble with Intel WLAN adapters and 
HiPath?  Specifically, we've had ~100 student laptops come in with Intel 
1000BGN adapters - latest drivers - that remain connected to the network, 
but stop receiving traffic from our 3610 APs.  Disconnect/reconnect and 
things are fine for a short while, then stop working again.  Some clients 
stop receiving traffic immediately after obtaining an IP address.  Open 
SSID, WPA2, it doesn't matter. 

I've also had trouble with random versions of the Intel 5100 adapter. 
5300/62xx/63xx only seem to experience occasional packet loss but 
otherwise no major problems.  Atheros/Broadcom adapters exhibit none of 
these issues.

I'm currently working with support, but it's pretty slow going so I 
thought I'd ping to see if others are having the same issues.  Running 
firmware 7.41.05.0003 here. 

Cheers! 

Derek Johnson
Data Communications Coordinator
Fort Hays State University
(785) 628 - 5688
[email protected] 
. --To unsubscribe from enterasys, send email to [email protected] with the 
body: unsubscribe enterasys [email protected] 

---
To unsubscribe from enterasys, send email to [email protected] with the 
body: unsubscribe enterasys [email protected] 
--To unsubscribe from enterasys, send email to [email protected] with the 
body: unsubscribe enterasys [email protected] 
--To unsubscribe from enterasys, send email to [email protected] with the 
body: unsubscribe enterasys [email protected] 
--To unsubscribe from enterasys, send email to [email protected] with the 
body: unsubscribe enterasys [email protected] 
--To unsubscribe from enterasys, send email to [email protected] with the 
body: unsubscribe enterasys [email protected] 


---
To unsubscribe from enterasys, send email to [email protected] with the body: 
unsubscribe enterasys [email protected]

Reply via email to