Troubleshooting Tip: Require Message-Authentication set to 'Enable' causes RADIUS health check failure
| Description | This article describes the behavior where in High Availability configurations, the RADIUS health check fails when the RADIUS service is running properly. It can be triggered when the Require Message-Authenticator attribute is set to 'enable' under Network -> RADIUS -> Configuration in the FortiNAC Admin GUI. When the health check fails, FortiNAC initiates a failover to the secondary.
This leads FortiNAC's health check logic to think RADIUS is not responding and triggers a failover. |
| Scope | FortiNAC vF7.2.8, vF7.4.0, vF7.6.0 and greater. |
| Solution | This will be addressed in a future release.
Workaround: FortiNAC GUI Method.
Disable the RADIUS component of the health check. Login as admin and type:
Workaround - FortiNAC CLI Method (CentOS): Disable the RADIUS component of the health check. Login as root and type:
logout
The secondary server is in control: once the settings are changed, resume control to the primary server. |
