Right now, if a client device is already connected to an AP, any setting changes made from cnMaestro won’t affect the currently connected devices. Once the device connects to a different AP (for example, roaming), that AP will check/get the updated information from cnMaestro Cloud. So, for instance, if I have hit the limit of number of devices on an easypass, even if I increase the number through cnMaestro, it doesn’t update on the device that was just refused access due to reaching the limit because it doesn’t update. Updates should push to the devices or the device should poll for updates so this is more instantaneous. This was not an issue on the old Xirrus platform. It just worked.
Hi Thomas Balne,
can you provide more context what portal type here for the device limit? and how does XMS do here?
Thanks
Raja M
Easypass Onboarding. When you hit the max number of devices, the device sends you to a site to choose to remove a device to make room for the current one. If I instead want to allow that user additional devices, if I increase the limit in cn Maestro, the device continues to prompt that the limit has been reached and to remove a device. Only after the device connects to a new AP does it realize that I’ve increased the device limit and allows it to connect unimpeeded. In XMS, this just worked. If the device limit was hit, I would increase it in XMS cloud and the device would fairly instantly understand that the limit has been increased and when you tried to connect again it allowed you to.