max-request-retries 10000
bootstrap-threshold 5000
Provisioning Mes h Nodes
Provisioning mesh nodes is similar to t hin APs; however, there are some key differences.Thin A Ps establish a
channelto the controller from which they receive the configuration for each radio interface.Mesh nodes, in contrast,
get their radio interfaces up and runningbefore making contact wi th the controller.This requiresa minimum set of
parametersfrom the AP group andmesh cluster that enables the mesh node to disc over a neighbort o create a mesh
linkand subsequent channel with the controller. To do this, yo u must first configure mesh clusterprofiles for each
mesh node prior to deployment. See “Mesh Radio Profiles” for more information.
Oneach radio interface,yo u provision a mode of operation: mesh node or thin AP (access) mode. I f you do not
specify mesh,the AP operates in thin AP (access) mode. If you configuremesh, the AP is provisioned with a
minimum of two mesh cluster profiles: the “default” mesh clusterprofile and an emergency read-only recovery profile,
as described in the section “Mesh Clusters”.I fy ou createand select multiple mesh cluster profiles,t heA P is
provisioned with those as well. If you have a dual-radio AP and configureo neradio for mesh and the other as a thin
AP, each radio is provisioned as configured.
Each radio provisioned in mesh mode can operate in one of two roles:mesh portal or mesh point. You explicitly
configurethe role, as described in this section. This allows the AP to know whether it uses the mesh link(via t he
mesh point/meshportal) or an E thernetlink to establish a connection to the controller.
During the provisioning process, mesh nodes look for a mesh profilet hat the AP group and AP name is a member of
and stores that information in flash.If you have multiple cluster profiles, the meshportal uses the best profile to
bring-upthe mesh network. Mesh points in contrast go throughthe list of mesh cluster profilesi n orderof prio rity to
decide which profile to use to associate t hemselveswit h the network.I n addition, when a mesh point is provisioned,
the country code is sent to the AP from its AP name or AP group along with the mesh cluster profiles. Meshnodes
also learnthe recovery profile, which is automatically generated by the master controller.If the other mesh cluster
profilesare unavailable, mesh nodes use the recoveryprofile to establish a link to the master controller; data
forwardingdoes not take place.
NOTE:If you create a new mesh cluster profile for an existing deployment, you must re-provision the AP for thenew profileto take
effect.If you re-provision mesh nodes that are already operating, re-provisionthe most distant (highest hop count) mesh points first
followed by them eshportals. If you re-provision the mesh portal first, the mesh points may be unable to form a mesh link. Re-
provisioning theAP causes it to automatically reboot. This may cause a disruption of service to the network.
This section describes the following topics:
l“Outdoor AP Parameters”
l“Provisioning Caveats”
l“Provisioning Mesh Nodes”

Outdoor A P Parameters

If you are using outdoor APs and planning an outdoor mesh deployment, you can enter the following outdoor
parameterswhen provisioning the A P:
lLatitude and longitudecoo rdinateso ft heA P. These location identifiers allow you to more easily locate the AP
for inventory and troubleshootingpurposes.
lAltitude, in meters, of the AP.
lAntenna bearingto determine horizontal coverage.
lAntenna anglefor opti mumantenna coverage.
DellPowerConnect W- Series ArubaOS 6.2 | UserGuide SecureEnterprise Mesh | 467