I did some tests with CoA and 802.11r and came to a different conclusion compared to what is stated in the documentation *and* on the dashboard. In my network (MR 31.1.5.1), I have an SSID that is configured with 802.1X and both CoA and 802.11r.   The dashboard states that 802.11r would be disabled: And the documentation states that 802.11r gets disabled:   But in reality, 802.11r is still announced:   And Roaming is done based on 802.11r:   In the RADIUS capture, I only see the initial communication but no further exchange when roaming.   CoA is indeed not working as it should: It works when the Client is connected to the AP that made the initial connection (also after a roam back). It doesn't work on other APs. When the client is connected to a different AP, the original AP gets the CoA request and answers with CoA-NAK, "Session-Context-Not-Found".   The misleading statements in the dashboard and the documentation should be corrected. Or even better, CoA should be implemented in a way that it works. 😉   ... View more

This is from the the CW9178/9176 Installation Guide:   Warning: If the Networks in the Organization where the CW9178I is to be installed have Meraki Sensors, it is required to create a separate network for the CW9178I for staging purposes. Once the CW9178I connects to the cloud and updates the new firmware, then the AP can be moved to the network where the CW9178I needs to operate.   Has anyone an idea or an info what the reason for this is? ... View more