Use this page to perform the following tasks:
Optimization is not run automatically by the Meru Wireless LAN System. You must specifically run optimization for each area, as previously listed. Optimization is not run when the controller reboots or when an access point is added to the WLAN. Any optimization performed before an access point reboots is persistent after the reboot. Optimization is not persistent across controller reboots.
If you run optimization for one area and then run optimization for another
area, the changes made for the first optimization are undone before the
current optimization is run.
You can get the highest throughputs and speeds for data and voice by
running performance optimization. Performance optimization uses the
maximum number of channels, but substantially reduces your coverage by
limiting the network to the higher 802.11 transmit rates. Some older clients
that cannot accept high base rates or react poorly to short preambles
might still have difficulties.
Note You still must enable high-density mode for specific access
points if you want to use that additional feature.
To optimize performance, click Performance. The configuration
file is modified to enhance WLAN performance. The optimization process
takes several minutes. The following table lists the configuration parameters that are modified
when you optimize performance.To optimize performance
| Device modified | Configuration parameters modified |
| Controller |
|
| Access points | Sets thresholds for transmit rate adaption (not configurable except with this optimization process). |
If you do not want to use the three channels used when the autochannel command was run during optimization, do the following:
controller(config)# autochannel channel-id-1 channel-id-2 ...
To minimize the packet loss incurred by stations during handoffs, run handoff optimization. Run handoff optimization for any application and network where handoffs are concerns, such as in voice networks. Running handoff optimization might reduce your overall throughput by not using other channels, but could increase performance by eliminating handoff overhead and ping-ponging.
To optimize handoffs, click Handoff. The configuration file is modified to optimize the handoff process. The optimization process takes several minutes.
The following table lists the configuration parameters that are modified when you optimize handoffs.
| Device modified | Configuration parameters modified |
| Controller |
|
| Access points | None. |
To optimize your network to reach the largest number of stations at the furthest distances, run coverage optimization. Only run coverage optimization if coverage and range are your main concerns. Coverage optimization reduces network performance if you have clients operating below the peak transmit rate, as they do at greater distances from access points.
To optimize coverage, click Coverage. The configuration file is modified to enhance coverage. The optimization process takes several minutes.
The following table lists the configuration parameters that are modified when you optimize coverage.
| Device modified | Configuration parameters modified |
| Controller |
|
| Access points | None. |
To optimize your network to provide the best service for older clients that incompletely implement the 802.11 standard, run nonconfirming-client optimization. You might need to run this type of optimization if you have clients using certain types of 802.11 cards that react poorly to short preambles or customized base transmit rates. Running nonconforming-client optimization affects performance and increases overhead on the air if you use multiple ESS profiles in your system.
To optimize nonconforming clients, click Nonconforming Clients. The configuration file is modified to enhance use of nonconforming clients. The optimization process takes several minutes.
The following table lists the configuration parameters that are modified when you optimize nonconforming clients.
| Device modified | Configuration parameters modified |
| Controller |
|
| Access points | Maximizes the frequency of beacons sent by setting beacon interval to 1. |
Run rogue access point mitigation optimization to optimize your network to detect and disrupt rogue access points above all else. Run this type of optimization if defeating rogues is your greatest concern, and you are willing to dedicate your airtime to this task over providing consistent service. Do not run this type of optimization if you only want to detect or slow down, rather than maximize the disruption of, rogues. Note: This is the only type of optimization that removes the guarantee of consistency in service. However, you might still provide acceptable service with this feature, depending on your network.
To optimize rogue access point mitigation, click Rogue AP Mitigation. The configuration file is modified to enhance rogue access point mitigation. The optimization process takes several minutes.
The following table lists the configuration parameters that are modified when you optimize rogue access point mitigation.
| Device modified | Configuration parameters modified |
| Controller | None. |
| Access points |
|
Running manual optimization gives you the greatest flexibility, by allowing you to configure the system manually, without choosing any type of automatic optimization. Any previous optimization parameters are reset to system default values after running manual optimization.
To run manual optimization, click Manual. The process takes several minutes.
The following table lists the configuration parameters that are modified during a manual optimization.
|
| Device modified | Configuration parameters modified |
|
Performance | Controller |
|
|
| Access points |
Resets thresholds for transmit rate adaption (not configurable except with the undo optimization process). |
|
Handoff | Controller | None. |
|
| Access points | None. |
|
Coverage | Controller | None. |
|
| Access points | None. |
|
Nonconforming clients | Controller |
|
|
| Access points | Beacon interval is reset to default value of 10. |
|
Rogue access point mitigation | Controller | None. |
|
| Access points |
|