06-12-2022 09:11 PM
By default any Unleashed AP plugged into the same L2 will automatically join the master. Is there a way to disable this behavior?
I know ZD allows changing the policy by issuing no ap-auto-approve but I don't see the equivalent for Unleashed. I saw the topic from 2 years ago but no solution was provided there 😞
Anyone have any idea? Obviously Unleashed evolved over the years, so maybe there is a way to do that?
Solved! Go to Solution.
06-14-2022 07:29 PM
Hi @kiler129
Unfortunately the requirement you are looking for is not available as of now. We though have opened a feature request to support the disabling of auto approval and in future this might be added/reconsidered again but as of now it is not supported.
Best Regards
Vineet
06-14-2022 07:29 PM
Hi @kiler129
Unfortunately the requirement you are looking for is not available as of now. We though have opened a feature request to support the disabling of auto approval and in future this might be added/reconsidered again but as of now it is not supported.
Best Regards
Vineet
04-10-2023 09:05 PM
Due to the behavior of the requirement, I guess the customer cannot create multiple unleashed within the same L2 subnet because each unleahsed AP will automaticlly join to the existing master AP.
Is my understanding correct?
Best Regards,
Koji Onodera
05-01-2023 01:46 AM
That is correct, within same L2 only one can act as master and rest would join it as slave.
Best Regards
Vineet