Technical Tip: After upgrading FortiNAC to 9.4.7 on an HA pair with shared IP a Admin GUI Check causes Primary to repeatedly failover to Secondary

1. When conditions are met after the FortiNAC is upgraded, there is a failure in the System health check where the Admin UI is deemed to be down, which causes the system to enter failover mode.
   
   
2. If the symptoms are experienced after an upgrade to 9.4.7, and the system is an HA setup with a shared IP, it is likely to experience this issue. This can be validated by reviewing the output.processmanager log.

yams.CampusManager INFO :: 2024-10-29 14:09:23:509 :: #1 :: getCustomHealthCheckConfig service:AdminGUI enabled:true global retry:3 internal retry:3 timeout:5000

yams.CampusManager INFO :: 2024-10-29 14:09:23:513 :: #1 :: getCustomHealthCheckConfig service:AdminGUI enabled:true global retry:3 internal retry:3 timeout:5000

yams.CampusManager INFO :: 2024-10-29 14:09:23:517 :: #1 :: checkService(AdminGUI) check protocol for AdminGUI failed, current count(retry) is max 3 will return fail

yams.CampusManager INFO :: 2024-10-29 14:09:23:517 :: #1 :: checkService(AdminGUI) check protocol for AdminGUI result:false

yams.CampusManager INFO :: 2024-10-29 14:09:23:517 :: #1 :: ******* System Check Failed! *******

yams.CampusManager INFO :: 2024-10-29 14:09:23:517 :: #1 :: ******* Changing status to - Secondary In Control ****

A temporary fix is to disable the Admin UI check in the CLI interface:

globaloptiontool -name highAvail.adminguiCheckEnabled -set false

This behavior is addressed on FortiNAC v9.4.8 and above.

Related documents:
FortiNAC v9.4.8 - Release notes.
FortiNAC v9.4.7 - Release notes - Known issues.