Motorola RFS Series, Справочное руководство системы

Страница: 25 / 590

Overview
1-13
Self Healing Actions
If AP1 detects AP2 and AP3 as its neighbors, you can assign failure actions to AP2 and AP3 whenever AP1
fails.
Assign up to four self healing actions:
1. No action
2. Decrease supported rates
3. Increase Tx power
4. Both 2 and 3.
You can specify the Detector AP (AP2 or AP3) to stop detecting and adopt the RF settings of the failed AP. For
more information on configuring self healing, see
Configuring Self Healing on page 5-53 .
1.2.2.9 Wireless Capacity
Wireless capacity specifies the maximum numbers of MUs, Access Ports and wireless networks usable by a
switch. Wireless capacity is largely independent of performance. Aggregate switch performance is divided
among the switch clients (MUs and Access Ports) to find the performance experienced by a given user. Each
switch platform is targeted at specific market segments, so the capacity of each platform is chosen
appropriately. Wireless switch capacity is measured by:
• The maximum number of WLANs per switch
• The maximum number of Access Ports adopted per switch
• The maximum number of MUs per switch
• The maximum number of MUs per Access Port.
The actual number of Access Ports adoptable by a switch is defined by the switch licenses or the total
licenses in the cluster in which this switch is a member.
1.2.2.10 AP and MU Load Balancing
Fine tune a network to evenly distribute data and/or processing across available resources. Refer to the
following:
• MU Balancing Across Multiple APs
• AP Balancing Across Multiple Switches
MU Balancing Across Multiple APs
Per the 802.11 standard, AP and MU association is a process conducted independently of the switch. 802.11
provides message elements used by the MU firmware to influence roaming decisions. The switch
implements the following MU load balancing techniques:
• 802.11e admission control — 1 byte: channel utilization% and 1 byte: MU count is sent in QBSS Load
Element in beacons to MU.
• Motorola load balancing element (proprietary) — 2 byte: MU Count are sent in beacon to MU.
For more information on Access Port adoption in a layer 3 environment, see Configuring Layer 3 Access Port
Adoption on page 4-138 .