cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1770
Views
0
Helpful
11
Replies

guidelines available to optimize 1602E AP bridging throughput

will
Level 3
Level 3

hi, I have a pair of 1600 AP's in stand-alone mode, configured as a wireless bridge. there are a few vlans going across this link currently.

I started to research wan compression options as a means for optimize the throughput, but then wondered if I had reached the full configuration potential of he AP's themselves. Does anyone have any general guidelines about optimize these AP's for throughput in bridge mode configuration?

Is WIFI compression an option on the bridge connection?

thx in advance!

Will

11 Replies 11

Scott Fella
Hall of Fame
Hall of Fame

I have not heard anyone ever trying to use any sort of compression on PTP links. If your saturating the link, it means it's time to look for a better solution, one that provides more overall throughput. 

-Scott

-Scott
*** Please rate helpful posts ***

thx scott, I figured WAN optimization technology might be an interesting twist if possible. However, I was more interested in optimizing the AP's for their Wifi traffic. I believe one of my issues stem from this problem discussed here:

https://supportforums.cisco.com/discussion/11756186/non-root-wireless-bridge-speed-issue

For example, I have a 40Mhz channel width configured on the root bridge, but the non-root bridge cannot be set and does not auto configure for 40 Mhz. it appears with 20 Mhz.

Also, I'm wondering if 802.11n requires a special SSID for each n channel it uses? If there is some sort of dynamic SSID generation based off the root SSID, that occurs during Wifi setup, then the static configured AP's for a bridge, might not support max 802.11n speeds? I only have one vlan configured per SSID.

I'm currently getting about 65Mbps transfer across the bridge between two hosts in a Vlan, and I see that the AP's are communicating primarily on the higher MCS speeds. The AP's have a cisco 3-way antenna on each side (abc-antenna enabled), so I thought the AP's would be smart enough to bond all the channels between the root and non-root bridge. Just cannot seem to make it happen.

Standard for 802.11n is either using open authentication or use WPA2/AES.  If the encryption is set for WPA/TKIP, you will not negotiate 802.11n rates.  Always start with the basics and build from there.

-Scott

-Scott
*** Please rate helpful posts ***

here are some notes and test results for those in need of the same thing. i have also documented some questions at the end. I’m still seeking some answers and not 100% sure I have tapped the potential of these 1062e AP’s running in bridging mode.

Test details:

- HP DL ProLiant-class servers with updated NIC drivers for the test

- Copy from a windows 2003 server to another windows 2003 server

- CIFS file transfer of a set of small files totaling 1.763 gigabytes

- wired NIC speeds = 1gbps connected via cisco 2960 series switch (current switch firmware)

- wired transfer speeds of about 176 Mbps throughput (baseline wired transfer)

Wifi details: So I have a baseline in this environment of about 175 Mbps transfer rate over the Gb Ethernet NIC’s. Now I try to optimize my transfer over the WAP bridged environment. Here are the details:

  • Two cisco 1602e AP’s configured in bridging mode (carrying 3 vlans) (Fairly recent 15.x OS).

    Cisco IOS Software, C1600 Software (AP1G2-K9W7-M), Version 15.2(4)JB5, RELEASE SOFTWARE (fc1) System image file is "flash:/ap1g2-k9w7-mx.152-4.JB5/ap1g2-k9w7-mx.152-4.JB5

  • Using the cisco certified 3-pole patch antenna (AIR-ANT5160NP-R), pretty much line of site @ 35-40m apart. Disabled the 2.4Ghz antenna permanently. Using just 5.0 Ghz.

  • Native vlan1 carries most of the vlan traffic. The other two vlans were shut during testing or not utilized much at all.

  • Tweaked several variables on the AP configuration in attempt to optimize transfer speeds.

  • Both sides of the AP’s were supported by cisco Gb switches.

  • AP’s uplinked to the switches via 1Gb switchport. Entire path from server to server was 1 Gb, except for the Wifi bridge.

  • Tried to do testing after hours and verified there was not much other traffic at that time over AP bridge.

  • Test started out at about 58 Mbps transfer over the air for the above file set.

  •  

Variables I tweaked: Things I did to make improvements (and their effect):

  1. Ensure the Dot11radio was configured with WPA & AES authentication:

    dot11 ssid BP1-C

       vlan 1

       authentication open

       authentication key-management wpa version 2

                   

    interface Dot11Radio1

     no ip address

     encryption vlan 1 mode ciphers aes-ccm

     encryption mode ciphers aes-ccm

Supposedly this is a requirement for 802.11n channel -bonding. I had this above already configured.

  1. Change antenna distance config from 1KM -> 0KM (AP's are actually about 40m apart):

This didn’t yield any substantial performance throughput. Left at 0 though.

2. change Ethernet Encapsulation Transform:RFC1042-> 802.1H

This didn’t yield any substantial performance throughput; reverted back (wanted to keep standardized.

3. Removed the non-vlan-1 vlans (thought there might be some sort of per-vlan-antenna band limitation). Thought I may be losing bandwidth because the AP was dedicating a particular band to a particular vlan in the bridge:

This didn’t yield any substantial performance throughput; reverted back to “trunk configuration”

4. Optimized DFS - was missing one channel in the UNII-2-Ext Spectrum (Band3):

This is pretty important and actually allows the AP to get more chance for success when seeking a 40 Mhz channel. See the below link for the channel breakdown. In the other 5 Ghz bands, there isn’t much room for the 40 Mhz channel allocation. 40 Mhz (double-wide) channel is important for AP, as it allows more information to be sent at one time:

https://sites.google.com/site/802dot11study/ch06/notes

Even though this seemed important, it didn’t really increase my speed too much; I got about 10% bump, but this was probably from choosing a different channel for communication. I was not able to get 40 Mhz channel allocation – see below in conclusions.

5. Change beamfrom from OFDM to RSSI

This didn’t yield any substantial performance throughput. Left the same – OFDM

6. Enable WMM (world mode multi-domain): world-mode dot11d country-code US outdoor

This seemed to provide about 5 Mbps improvement. I thought this was the missing link to achieving remarkable speed gains as it seems to be needed for 802.11n. But it didn’t give me the big jump I was expecting. Nevertheless, I left it enabled. NOTE: there is a bug in the GUI config tool that doesn’t let me configure this so I did it via the command line.

7. Set guard Interval – long or short:

This is a bit odd as you can only configure GI=any or GI=long. There is no hardfixing it at GI=short. GI=short is supposedly best performing, but I couldn’t hardset that. This was default so I just left it at GI=any. I didn’t test speed drop with GI=long enabled, but suspect it would go down 5% at most based on numbers.

8. Enable or disable PSPF (Public Secure Packet Forwarding):

This didn’t yield any substantial performance throughput. Left the enabled – PSFP=yes

 

Conclusions: so after all this playing around, I only managed to go from about 60 Mpbs -> 70 Mbps in my real world transfer speeds, most of it from probably just setting up on a different channel. My AP shows I’m communicating at high MCS speeds. Use this command to verify. It has a lot of good output:

#AP1  sho controllers dot11Radio 1

My traffic is in these channel allocations: RATE m13-2, RATE m14-2, RATE m15-2, with m15-2 dominating by a factor of 10-20 over the lower rates.

According to this link:

http://www.cisco.com/c/en/us/products/collateral/wireless/aironet-1600-series/data_sheet_c78-715702.html

I should be getting ~137 Mbps (20 Mhz) or 285 Mbps (40 Mhz). If I halve this for the communication being half-duplex and wireless inefficiencies, I should be at about 67 & 142 Mbps respectively. My conclusion is that I’m just not getting the antennas to bond at 40 Mhz. So here I am: a bit stuck and cannot figure out why they are not bonding. I hope this helps others. And I hope someone can point out the missing link! I want to go to about 142 Mbps!

Did you set the channel width to 40mhz?

http://www.cisco.com/c/en/us/td/docs/wireless/access_point/12-4_10b_JA/configuration/guide/scg12410b/scg12410b-chap6-radio.html#wp1209277

I would start out using one of the unii-3 channels also.

-Scott

-Scott
*** Please rate helpful posts ***

hi scott, thx for you continued feedback! I fixed to the band 3 channels like you mentioned (but this still is in the DFS range). I also set to a channel in band 4. but still same transfer speeds. I think part of my problem was a display bug in the gui, documented in this bug: bug = CSCup72880. the GUI shows 20 Mhz channel width.

If I use the sho controllers command, I can see the channel width, which is 40 Mhz, but in the Gui it always said 20 Mhz. I wasn't sure which was correct since they conflicted. Anyway, I think there is no further way to increase the bridge transfer speeds above 70 Mbps. this is kind of sad, since this should be capable of much more. I would be interested to know others results and tests. I'm dumping some output from the two AP's below:

 

ROOT_BRDIGDE:
interface Dot11Radio1
 no ip address
 !
 encryption vlan 1 mode ciphers aes-ccm
 encryption mode ciphers aes-ccm
 !
 peakdetect
 no dfs band block
 stbc
 beamform ofdm
 speed  basic-6.0 basic-9.0 basic-12.0 basic-18.0 basic-24.0 basic-36.0 basic-48.0 basic-54.0 m0. m1. m2. m3. m4. m5. m6. m7. m8. m9. m10. m11. m12. m13. m14. m15.
 packet max-retries 3 0 fail-threshold 100 500 priority 5 drop-packet
 packet max-retries 3 0 fail-threshold 100 500 priority 6 drop-packet
 channel width 40-above
 channel dfs
 station-role root bridge
!
AP1#sh controllers dot11Radio 1
!
interface Dot11Radio1
Radio Griffin 5, Base Address 34db.fde2.b600, BBlock version 0.00, Software version 4.18.1
Serial number:
Unused dynamic SQRAM memory: 0x000001C4 (0 KB)
Unused dynamic SDRAM memory: 0x00000000 (0 KB)
Number of supported simultaneous BSSID on Dot11Radio1: 16
Carrier Set: Americas (OFDM) (US) (-A)
Uniform Spreading Required: Yes
Configured Frequency: 5540 MHz  Channel 108  40MHz, extended above (DFS enabled)
Allowed Frequencies: * Dynamic Frequency Selection (DFS) only
         5180( 36)  5200( 40)  5220( 44)  5240( 48) *5260( 52) *5280( 56) *5300( 60) *5320( 64) *5500(100) *5520(104)
        *5540(108) *5560(112) *5580(116) *5660(132) *5680(136) *5700(140)  5745(149)  5765(153)  5785(157)  5805(161)
         5825(165)
Listen Frequencies:
         5180( 36)  5200( 40)  5220( 44)  5240( 48)  5260( 52)  5280( 56)  5300( 60)  5320( 64)  5500(100)  5520(104)
         5540(108)  5560(112)  5580(116)  5600(120)  5620(124)  5640(128)  5660(132)  5680(136)  5700(140)  5745(149)
         5765(153)  5785(157)  5805(161)  5825(165)

DFS Blocked Frequencies: none
Beacon Flags: 0, Interface Flags 20105, Interface Events 0, Mode A; Beacons are enabled; Probes are enabled
Configured TxPower:             17 dBm (Level Index 1)
Allowed Power Levels:           17 14 11  8  dBm
Allowed Client Power Levels:    17 14 11  8  dBm
Antenna:                        Rx[a b c ]
                                Tx[a b c  ofdm all]
                                External
                                Gain [Allowed 12, In Use 12]  (dBi x 2), In Use 12]  (dBi x 2), In Use 12]  (dBi x 2), In Use 12]  (dBi x 2), Reported 0, In Use 12]  (dBi x 2)
Active Rates:  basic-6.0 basic-9.0 basic-12.0 basic-18.0 basic-24.0 basic-36.0 basic-48.0 basic-54.0 m0-2 m1-2 m2-2 m3-2 m4-2 m5-2 m6-2 m7-2 m8-2 m9-2 m10-2 m11-2 m12-2 m13-2 m14-2 m15-2
Current Rates:  basic-6.0 basic-9.0 basic-12.0 basic-18.0 basic-24.0 basic-36.0 basic-48.0 basic-54.0 m0-2 m1-2 m2-2 m3-2 m4-2 m5-2 m6-2 m7-2 m8-2 m9-2 m10-2 m11-2 m12-2 m13-2 m14-2 m15-2
Allowed Rates:  6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0
All Rates:  6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0 m0-2 m1-2 m2-2 m3-2 m4-2 m5-2 m6-2 m7-2 m8-2 m9-2 m10-2 m11-2 m12-2 m13-2 m14-2 m15-2
Default Rates:  basic-6.0 9.0 basic-12.0 18.0 basic-24.0 36.0 48.0 54.0 m0-2 m1-2 m2-2 m3-2 m4-2 m5-2 m6-2 m7-2 m8-2 m9-2 m10-2 m11-2 m12-2 m13-2 m14-2 m15-2
Best Range Rates:  basic-6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0 m0-2 m1-2 m2-2 m3-2 m4-2 m5-2 m6-2 m7-2 m8-2 m9-2 m10-2 m11-2 m12-2 m13-2 m14-2 m15-2
Best Throughput Rates:  basic-6.0 basic-9.0 basic-12.0 basic-18.0 basic-24.0 basic-36.0 basic-48.0 basic-54.0 m0-2 m1-2 m2-2 m3-2 m4-2 m5-2 m6-2 m7-2 m8-2 m9-2 m10-2 m11-2 m12-2 m13-2 m14-2 m15-2
Current Voice Rates:  basic-6.0 basic-12.0 basic-24.0
Default Voice Rates:  basic-6.0 basic-12.0 basic-24.0
Managment Rates:  basic-6.0
Multicast Rates:  basic-6.0 basic-9.0 basic-12.0 basic-18.0 basic-24.0 basic-36.0 basic-48.0 basic-54.0
 Multicast Active rate: 54.0
RTS Rates:  basic-6.0 basic-9.0 basic-12.0 basic-18.0 basic-24.0 basic-36.0 basic-48.0 basic-54.0
RTS Active rate 54.0
RTS Max rate 54.0
 Local Packet Rate Probing is disabled : Packet Size 20
Data Rate Sensitivity (rate, SNR dB, Contention dBm)
( 6.0, 15, -89)   ( 9.0, 16, -88)   (12.0, 18, -88)   (18.0, 19, -86)  
(24.0, 20, -85)   (36.0, 24, -81)   (48.0, 27, -78)   (54.0, 31, -77)  
Hardware Beamforming: Configured Yes, Active Yes
TX A-MPDU Priority: 0x31 A-MSDU Priority 0x3F
 RIFS 0
Guard-Interval: Any
HT protection: HT (no protection).
Neighbors with non-HT members:

===========================================================
!
NON ROOT-BRIDGE:
interface Dot11Radio1
 no ip address
 !
 encryption vlan 1 mode ciphers aes-ccm
 encryption mode ciphers aes-ccm
 !
 ssid BP1-C
 !
 peakdetect
 stbc
 beamform ofdm
 speed  basic-6.0 basic-9.0 basic-12.0 basic-18.0 basic-24.0 basic-36.0 basic-48.0 basic-54.0 m0. m1. m2. m3. m4. m5. m6. m7. m8. m9. m10. m11. m12. m13. m14. m15.
 packet max-retries 3 0 fail-threshold 100 500 priority 5 drop-packet
 packet max-retries 3 0 fail-threshold 100 500 priority 6 drop-packet
 station-role non-root
!
AP2#sh controllers dot11Radio 1
!
interface Dot11Radio1
Radio Griffin 5, Base Address b000.b437.0840, BBlock version 0.00, Software version 4.18.1
Serial number: FOC180919ZZ
Unused dynamic SQRAM memory: 0x000001C4 (0 KB)
Unused dynamic SDRAM memory: 0x00000000 (0 KB)
Number of supported simultaneous BSSID on Dot11Radio1: 16
Carrier Set: Americas (OFDM) (US) (-A)
Uniform Spreading Required: Yes
Configured Frequency: 5540 MHz  Channel 108  40MHz, extended above (DFS enabled)
Allowed Frequencies: * Dynamic Frequency Selection (DFS) only
         5180( 36)  5200( 40)  5220( 44)  5240( 48) *5260( 52) *5280( 56) *5300( 60) *5320( 64) *5500(100) *5520(104)
        *5540(108) *5560(112) *5580(116) *5660(132) *5680(136) *5700(140)  5745(149)  5765(153)  5785(157)  5805(161)
         5825(165)
Listen Frequencies:
         5180( 36)  5200( 40)  5220( 44)  5240( 48)  5260( 52)  5280( 56)  5300( 60)  5320( 64)  5500(100)  5520(104)
         5540(108)  5560(112)  5580(116)  5600(120)  5620(124)  5640(128)  5660(132)  5680(136)  5700(140)  5745(149)
         5765(153)  5785(157)  5805(161)  5825(165)

DFS Blocked Frequencies: none
Beacon Flags: 0, Interface Flags 20105, Interface Events 0, Mode 4; Beacons are disabled; Probes are disabled
Configured TxPower:             17 dBm (Level Index 1)
Allowed Power Levels:           17 14 11  8  dBm
Allowed Client Power Levels:    17 14 11  8  dBm
Antenna:                        Rx[a b c ]
                                Tx[a b c  ofdm all]
                                External
                                Gain [Allowed 12, In Use 12]  (dBi x 2), In Use 12]  (dBi x 2), In Use 12]  (dBi x 2), In Use 12]  (dBi x 2), Reported 0, In Use 12]  (dBi x 2)
Active Rates:  basic-6.0 basic-9.0 basic-12.0 basic-18.0 basic-24.0 basic-36.0 basic-48.0 basic-54.0 m0-2 m1-2 m2-2 m3-2 m4-2 m5-2 m6-2 m7-2 m8-2 m9-2 m10-2 m11-2 m12-2 m13-2 m14-2 m15-2
Current Rates:  basic-6.0 basic-9.0 basic-12.0 basic-18.0 basic-24.0 basic-36.0 basic-48.0 basic-54.0 m0-2 m1-2 m2-2 m3-2 m4-2 m5-2 m6-2 m7-2 m8-2 m9-2 m10-2 m11-2 m12-2 m13-2 m14-2 m15-2
Allowed Rates:  6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0
All Rates:  6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0 m0-2 m1-2 m2-2 m3-2 m4-2 m5-2 m6-2 m7-2 m8-2 m9-2 m10-2 m11-2 m12-2 m13-2 m14-2 m15-2
Default Rates:  basic-6.0 9.0 basic-12.0 18.0 basic-24.0 36.0 48.0 54.0 m0-2 m1-2 m2-2 m3-2 m4-2 m5-2 m6-2 m7-2 m8-2 m9-2 m10-2 m11-2 m12-2 m13-2 m14-2 m15-2
Best Range Rates:  basic-6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0 m0-2 m1-2 m2-2 m3-2 m4-2 m5-2 m6-2 m7-2 m8-2 m9-2 m10-2 m11-2 m12-2 m13-2 m14-2 m15-2
Best Throughput Rates:  basic-6.0 basic-9.0 basic-12.0 basic-18.0 basic-24.0 basic-36.0 basic-48.0 basic-54.0 m0-2 m1-2 m2-2 m3-2 m4-2 m5-2 m6-2 m7-2 m8-2 m9-2 m10-2 m11-2 m12-2 m13-2 m14-2 m15-2
Current Voice Rates:  basic-6.0 basic-12.0 basic-24.0
Default Voice Rates:  basic-6.0 basic-12.0 basic-24.0
Managment Rates:  basic-6.0
Multicast Rates:  basic-6.0 basic-9.0 basic-12.0 basic-18.0 basic-24.0 basic-36.0 basic-48.0 basic-54.0
 Multicast Active rate: 54.0
RTS Rates:  basic-6.0 basic-9.0 basic-12.0 basic-18.0 basic-24.0 basic-36.0 basic-48.0 basic-54.0
RTS Active rate 54.0
RTS Max rate 54.0
 Local Packet Rate Probing is disabled : Packet Size 20
Data Rate Sensitivity (rate, SNR dB, Contention dBm)
( 6.0, 15, -89)   ( 9.0, 16, -88)   (12.0, 18, -88)   (18.0, 19, -86)  
(24.0, 20, -85)   (36.0, 24, -81)   (48.0, 27, -78)   (54.0, 31, -77)  
Hardware Beamforming: Configured Yes, Active Yes
TX A-MPDU Priority: 0x31 A-MSDU Priority 0x3F
 RIFS 0
Guard-Interval: Any
HT protection: HT (no protection).
Neighbors with non-HT members:

hi all, just an update to this case. in the end, I contacted TAC on the issue. they had a good guy who gave the config a once-over. I also obtained a newer OS to apply to device. I made a few minor adjustments based on TAC recommendations. However, with these changes, I only obtained about  5Mpbs improvement. so I'm still at about 75 Mbps throughput for the Wifi device.

I have tested the file transfer with both CIFS and FTP to rule out possible protocol issues. My conclusion at the moment is that I just cannot achieve the marketing numbers of 175 mbps due to some sort of interference in the area. Or you just cannot obtain >75Mbps transfer speeds on a Wifi bridge.

If anyone has any questions, comments, please feel free to contact me offline.

Yeah... I don't see great throughout on the APs and maybe it's the code. Most of the time I deal with bridge links, I use a different vendor hat specialized in bridge links. 

-Scott

-Scott
*** Please rate helpful posts ***

The newer 1572 are out which will higher TX speeds. Thats an alternative. 

 

What I find in PTP the better the signal drives better the performance. In other words, sometime taking that link from -78 to -68 you will see a good leap in transmissions speed. Depending on your deployment it will involve different antennas etc .. 

 

Just my 2 cents .

"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
___________________________________________________________

Abhishek Abhishek
Cisco Employee
Cisco Employee

You can also configure the access point/bridge to set the data rates automatically to optimize either range or throughput. When you enter range for the data rate setting, the access point/bridge sets the 6-Mbps rate to basic and the other rates to enabled. When you enter throughput for the data rate setting, the access point/bridge sets all data rates to basic. Enter default to set the data rates to factory defaults

Beginning in privileged EXEC mode, follow these steps to configure the radio data rates:

 

 
 
Command
Purpose

Step 1 

configure terminal

Enter global configuration mode.

Step 2 

interface dot11radio 0

Enter interface configuration mode for the radio interface.

Step 3 

speed

{[1.0] [2.0] [5.5] [6.0] [9.0] [11.0] [12.0] [18.0] [24.0] [36.0] [48.0] [54.0] [basic-1.0] [basic-2.0] [basic-5.5] [basic-6.0] [basic-9.0] [basic-11.0] [basic-12.0] [basic-18.0] [basic-24.0] [basic-36.0] [basic-48.0] [basic-54.0] | range |
throughput [ofdm] | default }

Set each data rate to basic or enabled, or enter range to optimize range or throughput to optimize throughput.

Enter 1.0, 2.0, 5.5, 6.0, 9.0, 11.0, 12.0, 18.0, 24.0, 36.0, 48.0, and 54.0 to set these data rates to enabled on the 802.11g, 2.4-GHz radio.

Enter basic-1.0, basic-2.0, basic-5.5, basic-6.0, basic-9.0, basic-11.0, basic-12.0, basic-18.0, basic-24.0, basic-36.0, basic-48.0, and basic-54.0 to set these data rates to basic on the 802.11g, 2.4-GHz radio.

Note The client must support the basic rate that you select or it cannot associate to the wireless device. If you select 12 Mbps or higher for the basic data rate on the 802.11g radio, 802.11b client devices cannot associate to the wireless device 802.11g radio.

(Optional) Enter range or throughput or ofdm-throughput (no ERP protection) to automatically optimize radio range or throughput. When you enter range, the wireless device sets the lowest data rate to basic and the other rates to enabled. When you enter throughput, the wireless device sets all data rates to basic.

(Optional) Enter speed throughput ofdm to set all OFDM rates (6, 9, 12, 18, 24, 36, and 48) to basic (required) and set all the CCK rates (1, 2, 5.5, and 11) to disabled. This setting disables 802.11b protection mechanisms and provides maximum throughput for 802.11g clients. However, it prevents 802.11b clients from associating to the access point.

(Optional) Enter default to set the data rates to factory default settings (not supported on 802.11b radios).

On the 802.11g radio, the default option sets rates 1, 2, 5.5, and 11 to basic, and rates 6, 9, 12, 18, 24, 36, 48, and 54 to enabled. These rate settings allow both 802.11b and 802.11g client devices to associate to the wireless device 802.11g radio.

Step 4 

end

Return to privileged EXEC mode.

Step 5 

copy running-config startup-config

(Optional) Save your entries in the configuration file.

 

Use the no form of the speed command to disable data rates. When you use the no form of the command, all data rates are disabled except the rates you name in the command. This example shows how to disable data rate 6.0:

ap# configure terminal

ap(config)# interface dot11radio 0

ap(config-if)# no speed basic-9.0 basic-12.0 basic-18.0 basic-24.0 basic-36.0 basic-48.0 
basic-54.0

ap(config-if)# end

Data rate 6 is disabled, and the rest of the rates are set to basic.

This example shows how to set up the access point/bridge for 54-Mbps service only:

ap# configure terminal

ap(config)# interface dot11radio 0

ap(config-if)# speed basic-54.0

ap(config-if)# end

thx abishek, I have the data rates set automatically to optimize for speed. I thought about hardsetting the speed; however, I verified that my data transfer rates are in the MCS15-2 category primarily. In other words, I'm getting the 802.11n high speed transfer. So something odd is going on, as the data transfer rates are primarily high speed, but I'm not maximizing my transfer according to the marketing specs for mcs15-2. I believe I'm operating at the 40 Mhz channel BW now too. I'm currently still working with TAC on this, but don't know if I will have a resolution. Current theory is the antenna may have something to do with it. the antenna is a cisco 5.0 GHz directional patch AIR-ANT5160NP-R= on both sides. distance is about 60' between AP's.

Review Cisco Networking for a $25 gift card