I do this now with all of my sites. I manage clients by setting a Mac acl deny list on the ap. Then I back up all of my AP configs daily, as I hope you do as well. So if something needs to be changed I preprogram the AP and put it In place and resolve the issue.
This has another effect which is good and bad depending on your view. Say you reboot the AP, the client can see other AP at another site, it will connect to that and effectively restore service to the customer, limiting or eliminating downtime. We use air control to manage low signal clients and if the signal is too low, we add that client to the deny list for that AP and then kick them so they will go back to an appointment with better signal.
This makes our installations very easy. We have a single config that we load into all radios and the tech uses a GPS to look at site directions. He points, aims for best signal, and moves on. If multiple sites are available for a client, he just power cycles the radio and points in the new direction to check signal quality to that location.
This has worked very well for us and with a little bit of AP management has been easily maintainable.
On Jun 26, 2017 08:05, Josh Luthman <[email protected]> wrote:
I had an AP with a bit too many people on it and we put up a second AP to overlap the coverage. The customers all rebooted and they've been appropriately connected to the correct AP for the last few days.Has anyone ever changed the SSIDs to make sure they're locked to the right AP? (I'm not willing to do lock to MAC). Or have you just left multiple APs with the same SSID and things turned out all right?Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
_______________________________________________ Ubnt_users mailing list [email protected] http://lists.wispa.org/mailman/listinfo/ubnt_users
