EasyManua.ls Logo

Alcatel-Lucent AOS-W 6.5.3.x - Optimizing Aps over Low-Speed Links

Alcatel-Lucent AOS-W 6.5.3.x
1160 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
572| Access Points AOS-W 6.5.3.x| User Guide
frer-high-wm <percent>
frer-low-wm <percent>
frr-high-wm <percent>
frr-low-wm <percent>
Optimizing APs Over Low-Speed Links
The AOS-W AP system profile contains multiple configuration settings to help you validate and optimize your
AP connections to a switch.
This section includes the following information about these features:
n AP Health Checks on page 572
n Optimizing AP Connections over Low-Speed Links on page 572
AP Health Checks
The AP Health check feature uses ping probes to check reachability and latency levels for the connection
between the AP and the switch. The recorded latency information appears in the output of the show ap ip
health-check command. If the switch IPaddress becomes unreachable from the AP uplink, this feature
records the time that the connection failed, and saves that information in a log file (tmp/ap_hcm_log) on the
AP.
This feature is disabled by default, and is enabled by selecting the Health Check option in the AP system profile. For
details see Optional AP Configuration Settings on page 543
Optimizing AP Connections over Low-Speed Links
Depending on your deployment scenario, you may have APs or remote APs that connect to a switch located
across low-speed (less than 1Mbps capacity) or high-latency (greater than 100ms) links.
With low-speed links, if heartbeat or keep alive packets are not received between the AP and switch during the
defined interval, APs may reboot causing clients to re-associate. You can adjust the bootstrap threshold and
prioritize AP heartbeats to optimize these types of links. In addition, high bandwidth applications may saturate
low-speed links. For example, if you have tunnel-mode SSIDs, use them with low-bandwidth applications such
as barcode scanning, small database lookups, and Telnet to avoid saturating the link. If you have traffic that will
remain local, deploying remote APs and configuring SSIDs as bridge-mode SSIDs can also prevent link
saturation.
With high-latency links, consider the amount and type of client devices accessing the links. Alcatel-Lucent APs
locally process 802.11 probe-requests and probe-responses, but the 802.11 association process requires
interaction with the switch.
When deploying APs across low-speed or high-latency links, The following best practices are recommended:
n Connect APs and switches over a link with a capacity of 1Mbps or greater.
n Maintain a minimum link speed of 64Kbps per AP and per bridge-mode SSID. This is the minimum speed
required for downloading software images.
n Adjust the bootstrap threshold to 30 if the network experiences packet loss. This makes the AP recover
more slowly in the event of a failure, but it will be more tolerant to heartbeat packet loss.
n Prioritize AP heartbeats to prevent losing connectivity with the switch.
n If possible, reduce the number of tunnel-mode SSIDs. Each SSID creates a tunnel to the switch with its own
tunnel keep alive traffic.
n If most of the data traffic will remain local to the site, deploy remote APs in bridging mode. For more
information about remote APs, see Access Points on page 509.

Table of Contents