This Article helps to understand How to remove an Device stop being managed by Aruba central.
Environment : This article applies to Aruba Instant 6.2.1.0-3.3.0.0 or higher and managed by Aruba Central.
Network Topology : IAP---Aruba activate------Aruba central.
In order for an device to stop communicating with Central, it must find that there is no provisioning rule in Activate that tells it to contact Central.
This is achieved by unassigning a license from a device in Central.
- Unassigning a license in Central will move the device back into the default folder in Activate which does not have a provisioning rule.
- Every 1 minute the IAP sends stats to Central, and if unassigned, it will get timed out message from Central.
- show log Ap-debug(Sample logs)
May 26 16:45:30 awc[1654]: athena_read: 1175: cann't find session id from athena's message
May 26 16:46:28 awc[1654]: awc_init_connection: 1691: connecting to internal.central.arubanetworks.com:443
May 26 16:46:28 awc[1654]: tcp_connect: 138: recv timeout set to 5
May 26 16:46:28 awc[1654]: tcp_connect: 145: send timeout set to 5
- Then it will check back in Activate and see it is in default folder (without provisioning rule) and become locally managed. This can take up to 5 minutes. There is no need to reboot the AP, however, rebooting the AP may quicken the process.
- Also see that the message ‘Aruba Central Status: Connected’ has now changed back to ‘Aruba Central
These Two command will help to identify if the IAp is still manged by Aruba central or not.
