Users Guide

Dell PowerConnect ArubaOS 5.0 | User Guide Secure Enterprise Mesh | 195
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.
If a mesh point connects to a parent using the recovery profile, it may immediately exit recovery if the parent is
actively using one of its provisioned mesh cluster profiles. Once in recovery, a mesh point periodically exits
recovery to see if it can connect using an available provisioned mesh cluster profile. The recovery profile is read-
only; it cannot be modified or deleted.
The recovery profile is stored in the master controllers’ configuration file and is unique to that master controller.
If necessary, you can transfer your configuration to another controller. If you do this, make sure your new mesh
cluster is running and you have re-provisioned the mesh nodes before deleting your previous configuration. The
APs will learn the new recovery profile after they are provisioned with the new controller. This is also true if you
provision a mesh node with one master controller and use it with a different master controller. In this case, the
recovery profile will not work on the mesh node until you re-provision it with the new master controller.
Mesh Solutions
You can configure the following single-hop and multi-hop solutions:
z Thin AP services with wireless backhaul deployment
z Point-to-point deployment
z Point-to-multipoint deployment
z High-availability deployment
With a thin AP wireless backhaul deployment, mesh provides services and security to remote wireless clients and
sends all control and user traffic to the master controller over a wireless backhaul mesh link.
The remaining deployments allow you to extend your existing wired network by providing a wireless bridge to
connect Ethernet LAN segments. You can use these deployments to bridge Ethernet LANs between floors, office
buildings, campuses, factories, warehouses and other environments where you do not have access to physical
ports or cable to extend the wired network. In these scenarios, a wireless backhaul carries traffic between the Dell
APs configured as the mesh portal and the mesh point, to the Ethernet LAN.
Thin AP Services with Wireless Backhaul Deployment
To expand your wireless coverage without bridging Ethernet LAN segments, you can use thin AP services with a
wireless backhaul. In this scenario, the mesh point provides network access for wireless clients and establishes a
mesh path to the mesh portal, which uses its wired interface to connect to the controller. Use the 802.11g radio
for WLAN and controller services and the 802.11a radio for mesh services. Figure 34 shows the wireless backhaul
between the mesh portal to the mesh point that services the wireless clients.
Note: 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 controller, the recovery profiles should match.
To verify that the recovery profile names match, use the following command: show ap mesh debug provisioned-clusters {ap-name
<name> | bssid <bssid> | ip-addr <ipaddr>}.
To view the recovery profile on the controller, use the following command: show running-config | include recovery.