602| Secure Enterprise Mesh AOS-W 6.5.3.x| User Guide
Mesh points, unlike mesh portals, do not scan channels. This means that once a mesh point has selected a
mesh portal or an upstream mesh point, it tunes to this channel, forms the link, and does not scan again unless
the mesh link gets broken. This provides good mesh link stability, but may adversely affect system throughput
in networks with mesh portals and mesh points. When ARM assigns optimal channels to mesh portals, those
portals use different channels. Once the mesh network has formed and all the mesh points have selected a
portal (or upstream mesh point), those mesh points are not be able to detect other portals on other channels
that could offer better throughput. This type of suboptimal mesh network may form if, for example, two or
three mesh points select the same mesh portal after booting, form the mesh network, and leave a nearby
mesh portal without any mesh points. Again, this does not affect mesh functionality, but may affect total
system throughput. For details about associating an ARM profile with a mesh AP, see Assigning an ARM Profile
on page 566.
High-Throughput Radio Profiles
Each 802.11a and 802.11g radio profile also references a high-throughput profile that manages an AP or AP
group’s 40Mhz tolerance settings. For information about referencing a high-throughput profile, see Assigning a
High-throughput Profile on page 566.
Mesh High-Throughput SSID Profiles
High-throughput APs support additional settings not available in legacy APs. A mesh high-throughput SSID
profile can enable or disable high-throughput (802.11n) features and 40 MHz channel usage, and define values
for aggregated MAC protocol data units (MDPUs), and Modulation and Coding Scheme (MCS) ranges.
Alcatel-Lucent provides a “default” version of the mesh high-throughput SSID profile. You can use the “default”
version or create a new instance of a profile which you can then edit as you need. High-throughput mesh
nodes operating in different cluster profiles can share the same high-throughput SSID radio profile. For
information about configuring mesh high-throughput SSID profiles, see Creating and Editing Mesh High-
Throughput SSID Profiles .
Wired AP Profiles
The wired AP profile controls the configuration of the Ethernet port(s) on your AP. You can use the wired AP
profile to configure Ethernet ports for bridging or secure jack operation using the wired AP profile. For details,
see Configuring Ethernet Ports for Mesh on page 624
Mesh Recovery Profiles
In addition to the “default” and user-defined mesh cluster profiles, mesh nodes also have a recovery profile.
The master switch dynamically generates a recovery profile, and each mesh node provisioned by the same
master switch has the same recovery profile. The recovery profile is based on a pre-shared key (PSK), and mesh
nodes use the recovery profile to establish a link to the switch if the mesh link is broken and no other mesh
cluster profiles are available.
The mesh portal advertises the provisioned cluster profile. If a mesh point is unaware of the active mesh
cluster profile, but is aware of and has the same recovery profile as the mesh portal, the mesh point can use
the recovery profile to connect to the mesh portal.
The mesh point must have the same recovery profile as the parent to which it connects. If you provision the mesh
points with the same master switch, the recovery profiles should match. To verify that the recovery profile names
match, use the command show ap mesh debug provisioned-clusters {ap-name <name> | bssid<bssid> | ip-
addr<ipaddr>}. To view the recovery profile on the switch, use the command show running-config | include
recovery.
To Next Page
Loading...