OMADA Controller - Optimize AP onboarding with specific WLAN Group set as "Default"
Hello,
per default, new adopted access points will use WLAN Group "Default" after being adopted. It would be an improvement for AP deployment, if you can set an individual WLAN Group per site.
Examples for better understanding:
- Site "Office" contains WLAN Group "Co-Working Space"
- Site "Hotel" contains WLAN Group "Guest Internet"
- Site "HQ" contains WLAN Group "ACME Internal
Newly adopted APs on site "Office" should automatically offer all the configured WLANs, which are assigned to site "Office".
Newly adopted APs on site "Hotel" should automatically offer all the configured WLANs, which are assigned to site "Hotel"
...
Currently, any new adopted AP is offering "Default", which contains "TP-LINK WLAN -random-", which - in case of unintended / unauthorized resets - might be a security issue.
Hi @guarana
Newly adopted APs on site "Office" should automatically offer all the configured WLANs, which are assigned to site "Office".
Newly adopted APs on site "Hotel" should automatically offer all the configured WLANs, which are assigned to site "Hotel"
>>This is already how the controller works.
Do you want to modify the name of the Default WLAN group to for example, "Office"? This is already supported:
If I was wrong, please correct me. and explain a little more about your requirement, better combined with some screenshots. Thanks.
Hello @Vincent-TP and thank you for your fast reply!
Looks like we didn't communicate our request clearly. It is not about renaming the default profile, it's about setting a specific configured WLAN group profile as "Site default".
This is what the WLAN groups look like:
- If you now go ahead and copy this site, the WLAN groups are copied. However - all access points assigned to this site are running "Default"
- It would be great to have an option for example in "Site Settings -> Site -> Wireless Feature" to choose which WLAN group should be default for this site.
We hope that this explains the request a bit better.
Kind Regards
guarana
Hi @guarana
As for my understanding, for example, if you want the HQ WLANs to be the Default WLAN group of the site, you can directly modify the default WLAN group name Default to HQ WLANs, and add other two WLAN groups as you want.
After that, the WLAN group will be:
With the above config, you have chosen the HQ WLANs as the default WLAN group of this site.
I am sorry if there is any further misunderstanding.
Hello @Vincent-TP,
we know that this is possible, however we prefer not to play around with "Default" profiles & values for a couple of reasons.
- We had serious issues with another vendor, who overwrites all modified data during an update for "Default" settings with "Default" values by design (!), which means critical configuration was gone.
This kind of "gambling" is unacceptable. - Changes are a problem, if you can only work with one profile by renaming it (imagine a radical switching from PSK to RADIUS auth while keeping the WLAN name - this is not possible with one WLAN group).
- Maintenance & documentation is difficult when including "Default".
Omada is a business solution, so it should be able to handle business requests without insecurities or "What-If's". This is why we asked for this optimization.
Kind Regards
guarana