Q:
Secondary Managed Device in 8.0
A: The secondary managed device provides reliability and redundancy; however the functionality of a secondary managed device is initiated only after an AP terminates on a managed device successfully and retrieves the configuration. If the AP boots up and fails to connect to the managed device the AP cannot be managed. To address this, ArubaOS 8.0 introduces the secondary managed device feature. In a scenario where the managed device is not reachable, the AP will try to reach the secondary managed device and if successful will terminate on the secondary managed device. The secondary managed device details are not stored in the system flash when the AP is deployed for the first time, but only after a successful configuration. An AP can use the secondary managed device feature after the AP reboots.
Note: If an AP has not been configured to a managed device after deployment, the secondary managed device feature will not be applicable.
To enable the secondary managed device feature in Web UI:
1. In the Managed Network node hierarchy, navigate to Configuration > System > Profiles.
2. Select AP > AP System under All Profiles.
3. Select the AP profile for which the secondary managed device feature is to be enabled. The AP system
profile section is displayed.
4. Enter an IP or FQDN value for the secondary managed device in the Secondary Master IP/FQDN field.
5. Click Save.
6. Click Pending Changes.
7. In the Pending Changes window, select the check box and click Deploy changes.
To enable the secondary managed device feature in CLI:
(host) [mynode] (config) #ap system-profile <profile name>
(host) [mynode] (AP system profile "profile name")#secondary-master <value>