My question is...Best Practices....should we be creating a separate SSID Profile for each location (broadcasting the same SSID Name) or stick to one? The single SSID Profile has worked and seemed like a single place to make changes, but we are about to add 50+ more AP's and I want to make sure we are following best practices with them.
I'm not sure of best practice from Aerohive but this capability is one of the benefits to their policy management.
We have 30+ locations with 100s of AP's using the same SSID profile.
I have found this works great %99 of the time, if there are scenarios where we need to do a "phased" change then the site being change will get a new SSID policy so we do not have to update all APs.
This happened when deploying captive web portal, at the pilot sites we create a separate SSID profile with the CWP enabled. Once testing was complete we changed the single shared SSID profile for all the sites.
The other reason was under Additional Settings for the Network Policy, we needed to set the NTP Server time zone. Without that, our local RADIUS server was not authenticating properly and we are in four different time zones.
Thanks for the replies.