Controller-less WLANs

If slave IAP is factory reset, why is the extended SSID config not applied post config sync?
Q:

If slave IAP is factory reset, why is the extended SSID config not applied post config sync?



A:

In an active IAP cluster, if Extended SSID is disabled and any of the slave is reset to factory default, then we might notice that Extended SSID is still enabled on the slave even after the config push. 

Below are the steps to test this setup:

1) Disable extended ssid and reload swarm
2) "show aps" will show extended SSID disabled on all aps 
3) Now factory reset one of the slaves and reload it
4) when slave comes up and syncs up the config, extended SSID will show up as enabled.

Solution:
In 4.2.1, extended ssid is enabled by default. And if we want to disable it, a reboot is needed after configuration change to let it take effect. This feature is by design in the mentioned code.
So, after a factory reset, AP joins the cluster where extended ssid is disabled, it will just get the configuration synced, but AP will have extended ssid in enabled state. We would need another reboot to disable the extended SSID.

Version history
Revision #:
2 of 2
Last update:
‎08-08-2016 12:23 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
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.