Created on 10-31-2024 06:05 AM Edited on 11-28-2024 01:13 AM By Jean-Philippe_P
Description | This article describes how to identify and correct an issue where there is a System check with Admin GUI check failure on the Primary that causes the Primary to repeatedly failover to the secondary after upgrading to 9.4.7 on a system with HA and shared IP configured. |
Scope | FortiNAC v.9.4.7. |
Solution |
Issue:
Validation:
To validate that the logs confirm the issue, look for the following in 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. |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.