Recently we configured our access ports to apply a network access policy.
All our switches are in the latest stable firmware version MS17.2.1
We noticed that if we lose connectivity for a few seconds against our Radius servers, all our ports stops sending request to the Radius servers and in the event log we can see, so this users goes directly to the Authentication Critical Failure vlan, skipping the 802.1X process.
802.1X critical auth VLAN port:34, old_state: auth_critical, new_state:auth_closed
We opened a case with Cisco Meraki and they recommended us to enable a feature called Radius Monitoring to recover the service when this Radius servers comes up again... we tested this new feature in a lab with 3 users and it seems to be working fine, but when we apply the same Radius Monitoring in a full office with more than 300 users, this issue start happening again.
What can we do to avoid this issue?
Is there any configuration recommended in this cases?