Controller Based WLANs

How is the AP mesh recovery profile used?

Aruba Employee

Product and Software: This article applies to all Aruba controllers and ArubaOS 3.3.2.x and later.

When mesh APs are configured, a mesh recovery profile is automatically generated on the Aruba controller.

If you look in the running configuration, you should see the following output when configuring mesh:

(Columbus) #show running-config | include recovery
Building Configuration...
ap mesh-recovery-profile cluster RecoveryhnwZWRo4T6dF89dk wpa-hexkey da62aa651ed7e2bd1924b80a6907cfcef1596e7f802c8a1e494932656601d61bce889b0faedd2e6a62a1e62d06205cb0c395231f38377f1a4a695c41b0dbabb4c6afd78a17035e88431395d119251b3b



The AP mesh recovery profile is used by mesh points in the following cases:
· If there is no other mesh portal or mesh point available with the configured mesh cluster for the mesh point to associate with.
· If there is a mismatch with the WPA key or passphrase.


Note: The mesh recovery profile is generated by each controller and is unique to the controller. A mesh point that was provisioned on one controller will not be able to connect to a mesh portal or mesh point that was provisioned on another controller.



How Mesh Recovery Works
The mesh recovery profile works like this:
· The mesh point loses the mesh link it previously had established to either a mesh portal or to another mesh point or it does not find a valid mesh parent after first coming up.
· The mesh point scans for 5 minutes after detecting that the mesh link has gone down (10-30 seconds) to find the configured cluster ESSID so it can create a new mesh link within its cluster.
· After 5 minutes, if the mesh point does not find the configured cluster ESSID, the mesh point enters recovery mode. The mesh point scans for its provisioned mesh recovery ESSID for 5 minutes and creates a recovery mesh link to a mesh portal or to a mesh point that has the correct recovery profile.
· If after 5 minutes the mesh point is also unable to establish a mesh recovery link, the mesh point reboots and tries again.
· If the mesh point is able to establish a mesh recovery link, after 10 minutes of having the mesh recovery link, the mesh point begins scanning again to find the configured cluster ESSID.
· If the configured cluster ESSID is not found, the mesh point again enters recovery mode to create a recovery mesh link.
· After 20 minutes, the mesh point again scans to find the configured cluster ESSID.
· If the configured cluster ESSID is not found, the mesh point again enters recovery mode to create a recovery mesh link.
· After 30 minutes, the mesh point again scans to find the configured cluster ESSID.
· If the configured cluster ESSID is not found, the mesh point again enters recovery mode to create a recovery mesh link.
· Every 30 minutes thereafter, the mesh point scans to find the configured cluster ESSID.

During the time the mesh point has a mesh recovery link, the user can take corrective action on the mesh point:
· Reprovision with new parameters that may include anything that can normally be provisioned on an AP, such as, name, group, mesh radio profile, and mesh cluster profile. This may simply mean reprovisioning to make sure the WPA key or passphrase is correct or provisioning with new mesh cluster parameters.




Mesh Recovery in Operation
The following controller has two mesh clusters:

(Columbus) #show ap mesh topology

Mesh Cluster Name: mesh1
------------------------
Name Mesh Role Parent Path Cost Node Cost Link Cost Hop Count RSSI Rate Tx/Rx Last Update Uplink Age #Children
---- --------- ------ --------- --------- --------- --------- ---- ---------- ----------- ---------- ---------
point1 Point portal1 4 0 0 1 43 54/54 6m:46s 6h:49m:55s 0
portal1 Portal - 3 1 0 0 0 - 6m:46s 15h:29m:12s 1

Mesh Cluster Name: mesh2
------------------------
Name Mesh Role Parent Path Cost Node Cost Link Cost Hop Count RSSI Rate Tx/Rx Last Update Uplink Age #Children
---- --------- ------ --------- --------- --------- --------- ---- ---------- ----------- ---------- ---------
point2 Point portal2 4 0 0 1 50 54/54 4m:12s 3h:56m:51s 0
portal2 Portal - 3 1 0 0 0 - 4m:12s 15h:0m:29s 1

Total APs :4
(R): Recovery AP. (N): 11N Enabled. For Portals 'Uplink Age' equals uptime.




Now, shut the port connected to portal2 to bring down the mesh portal in cluster mesh2. After 10 minutes, point2 is in recovery mode:

(Columbus) #show ap mesh topology

Mesh Cluster Name: mesh1
------------------------
Name Mesh Role Parent Path Cost Node Cost Link Cost Hop Count RSSI Rate Tx/Rx Last Update Uplink Age #Children
---- --------- ------ --------- --------- --------- --------- ---- ---------- ----------- ---------- ---------
point1 Point portal1 4 0 0 1 46 54/54 4m:30s 7h:2m:8s 0
portal1 Portal - 3 1 0 0 0 - 40s 15h:41m:26s 1

Mesh Cluster Name: RecoveryhnwZWRo4T6dF89dk
-------------------------------------------
Name Mesh Role Parent Path Cost Node Cost Link Cost Hop Count RSSI Rate Tx/Rx Last Update Uplink Age #Children
---- --------- ------ --------- --------- --------- --------- ---- ---------- ----------- ---------- ---------
point2 Point portal1 4 0 0 1 45 0/54 20s 1m:39s 0

Total APs :3
(R): Recovery AP. (N): 11N Enabled. For Portals 'Uplink Age' equals uptime.




Now the mesh point in recovery mode can be reprovisioned. In this case, point2 is reprovisioned to be part of cluster mesh1:

(Columbus) (config) #provision-ap
(Columbus) (AP provisioning) #read-bootinfo ap-name point2
(Columbus) (AP provisioning) #ap-group mesh1
(Columbus) (AP provisioning) #reprovision ap-name point2




The provisioning parameters are saved, so you should always clear the parameters:

(Columbus) (AP provisioning) #clear provisioning-ap-list
(Columbus) (AP provisioning) #clear provisioning-params




After provisioning, the AP will reboot and come up in AP group mesh1:

(Columbus) #show ap active

Active AP Table
---------------
Name Group IP Address 11g Clients 11g Ch/EIRP/MaxEIRP 11a Clients 11a Ch/EIRP/MaxEIRP AP Type Flags Uptime Outer IP
---- ----- ---------- ----------- ------------------- ----------- ------------------- ------- ----- ------ --------
point2 mesh1 172.1.171.35 0 AP:11/9/0 0 MP+AP:36/0/0 65 M 1m:13s N/A
portal1 mesh1 172.1.171.37 0 AP:6/18/22 0 MPP+AP:36/9/23 65 M 15h:30m:58s N/A
point1 mesh1 172.1.171.38 0 AP:11/15/22 0 MP+AP:36/20/23 65 M 15h:26m:41s N/A

(Columbus) #show ap mesh topology

Mesh Cluster Name: mesh1
------------------------
Name Mesh Role Parent Path Cost Node Cost Link Cost Hop Count RSSI Rate Tx/Rx Last Update Uplink Age #Children
---- --------- ------ --------- --------- --------- --------- ---- ---------- ----------- ---------- ---------
point1 Point portal1 4 2 0 1 47 6/6 52s 7h:6m:43s 1
point2 Point point1 6 0 0 2 78 54/36 25s 51s 0
portal1 Portal - 3 1 0 0 0 - 5m:18s 15h:46m:4s 1

Total APs :3
(R): Recovery AP. (N): 11N Enabled. For Portals 'Uplink Age' equals uptime.




Mesh Recovery and Two Controllers
As mentioned, the mesh recovery profile is uniquely generated on each controller, which can be seen in the following output from two controllers:

(Phoenix) #show running-config | include recovery
Building Configuration...
ap mesh-recovery-profile cluster RecoveryBWKC1mfgUStxNSVr wpa-hexkey 7d4ca60d8fefcbd87a8134866471fae26abd91701855b35085f760299cf37536e868cac38547628dd35274d9a83ad982dc1e383b919c56d3b0ce9172c21db2c9cf3a90ae30704fbd3beaa77dbac89571

(Columbus) #show running-config | include recovery
Building Configuration...
ap mesh-recovery-profile cluster RecoveryhnwZWRo4T6dF89dk wpa-hexkey 5152fd67c375182018df49f68bd312b50d1979f5cd5b62d5d2053c0282ccb583d67488e63d6333671b8bcaccc7e060aebcff55f6185b53985033652f0743cfe450989b81f7e40b278e7d09b62922a6d2




Copying the Recovery Profile from One Controller to Another Controller
To copy the recovery profile from one controller to another controller, follow these steps:
1) Issue this command (SCP or FTP can be used too):
copy flash: default.cfg tftp: <IP of tftp server> <file name>
2) Edit the configuration to remove the line with the mesh recovery profile and copy the line from the other controller into the configuration.
3) Copy the edited configuration back to the controller by issuing this command:
copy tftp: <IP of tftp server> <file name> flash: new_cfg
copy flash: new_cfg flash: default.cfg



4) Reboot the controller so the new configuration becomes active.
5) Verify that the mesh recovery profiles are the same on both controllers.

After you copy the mesh recovery profile line from the Phoenix controller to the Columbus controller, the two controllers should show the following output. (After the 'encrypt disable' command, the lines should be identical.)

Phoenix
(Phoenix) #show running-config | include recovery
Building Configuration...
ap mesh-recovery-profile cluster RecoveryBWKC1mfgUStxNSVr wpa-hexkey 50bbd87e869e69c7c0072268dd7373bb7a107bc119569ca8bb036e3feb7780b517c33de68a9f7311ce06cbc483834a0aa2c711b4a25c6a197bfad805745da7ad6eaabbfa55d68103ec81d3a05bd4c5ed

(Phoenix) #
(Phoenix) #encrypt disable
(Phoenix) #
(Phoenix) #show running-config | include recovery
Building Configuration...
ap mesh-recovery-profile cluster RecoveryBWKC1mfgUStxNSVr wpa-hexkey 94AF6C7D85211437F72EFC16E51A7304482897D4B9ECCB6C9A8940EAE94A06D6

Columbus
(Columbus) #show running-config | include recovery
Building Configuration...
ap mesh-recovery-profile cluster RecoveryBWKC1mfgUStxNSVr wpa-hexkey d4aefea1d8a19b3dd9137a32332906074b095ed74f94c15cb221d9a5d9a671a8b95d86ea2ff8320b4b89941e3dfcd4acd57eb2c07476cc4bf98257ed79144fd1133875ec332d8c7e275c78576a5a6aaa

(Columbus) #
(Columbus) #encrypt disable
(Columbus) #
(Columbus) #show running-config | include recovery
Building Configuration...
ap mesh-recovery-profile cluster RecoveryBWKC1mfgUStxNSVr wpa-hexkey 94AF6C7D85211437F72EFC16E51A7304482897D4B9ECCB6C9A8940EAE94A06D6




Reprovisioning the Mesh APs
After you successfully copy the mesh recovery profile so that both controllers have the same profiles, you must reprovision the APs on the second controller so that the new mesh recovery profile is pushed down to the mesh APs. This reprovision is necessary only once after the mesh recovery profile has been changed on the controller. The controller continues to use the same mesh recovery profile, even after the controller is rebooted.

(Columbus) (config) #provision-ap
(Columbus) (AP provisioning) #read-bootinfo ap-name point1
(Columbus) (AP provisioning) #reprovision ap-name point1
(Columbus) (AP provisioning) #
(Columbus) (AP provisioning) #clear provisioning-params
(Columbus) (AP provisioning) #clear provisioning-ap-list
(Columbus) (AP provisioning) #
(Columbus) (AP provisioning) #read-bootinfo ap-name portal1
(Columbus) (AP provisioning) #reprovision ap-name portal1
(Columbus) (AP provisioning) #
(Columbus) (AP provisioning) #clear provisioning-params
(Columbus) (AP provisioning) #clear provisioning-ap-list




Mesh Recovery in Operation with Two Controllers
After you reprovision the mesh APs on Columbus, the following topology is on the two controllers:

(Phoenix) #show ap mesh topology

Mesh Cluster Name: mesh2
------------------------
Name Mesh Role Parent Path Cost Node Cost Link Cost Hop Count RSSI Rate Tx/Rx Last Update Uplink Age #Children
---- --------- ------ --------- --------- --------- --------- ---- ---------- ----------- ---------- ---------
point2 Point portal2 4 0 0 1 39 54/54 7m:26s 8m:39s 0
portal2 Portal - 3 1 0 0 0 - 7m:32s 1h:26m:49s 1

Total APs :2
(R): Recovery AP. (N): 11N Enabled. For Portals 'Uplink Age' equals uptime.

(Columbus) #show ap mesh topology

Mesh Cluster Name: mesh1
------------------------
Name Mesh Role Parent Path Cost Node Cost Link Cost Hop Count RSSI Rate Tx/Rx Last Update Uplink Age #Children
---- --------- ------ --------- --------- --------- --------- ---- ---------- ----------- ---------- ---------
point1 Point portal1 4 0 0 1 54 54/54 2m:32s 3m:58s 0
portal1 Portal - 3 1 0 0 0 - 1m:0s 17h:27m:55s 1

Total APs :2
(R): Recovery AP. (N): 11N Enabled. For Portals 'Uplink Age' equals uptime.




Shut the port connected to portal2. After 10 minutes, point2 goes into recovery mode and can be seen on Columbus:

(Columbus) #show ap mesh topology

Mesh Cluster Name: mesh1
------------------------
Name Mesh Role Parent Path Cost Node Cost Link Cost Hop Count RSSI Rate Tx/Rx Last Update Uplink Age #Children
---- --------- ------ --------- --------- --------- --------- ---- ---------- ----------- ---------- ---------
point1 Point portal1 4 0 0 1 50 54/54 47s 43m:50s 0
portal1 Portal - 3 1 0 0 0 - 47s 44m:59s 1

Mesh Cluster Name: RecoveryBWKC1mfgUStxNSVr
-------------------------------------------
Name Mesh Role Parent Path Cost Node Cost Link Cost Hop Count RSSI Rate Tx/Rx Last Update Uplink Age #Children
---- --------- ------ --------- --------- --------- --------- ---- ---------- ----------- ---------- ---------
point2 Point portal1 4 0 0 1 48 14/48 47s 1m:35s 0

Total APs :3
(R): Recovery AP. (N): 11N Enabled. For Portals 'Uplink Age' equals uptime.

Now the user can take corrective action on point2.

Version history
Revision #:
1 of 1
Last update:
‎07-05-2014 02:58 AM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.