Troubleshooting Tip: FortiAuthenticator routing issue with node-specific gateway for High Availability cluster

Description

This article describes a High Availability issue with FortiAuthenticator where the node-specific gateway overrides the static routing after a reboot. The article provides a step-by-step guide to resolving this issue.

Scope

FortiAuthenticator.

Solution

To resolve the High Availability issue with FortiAuthenticator, where the node-specific gateway overrides the static routing after a reboot, follow these steps:

1. Go to the CLI of FortiAuthenticator.

2. Remove the existing static route that is not working or has been overridden by the node-specific gateway.

3. Re-add the static route.

To delete a static route:

 config router static
 delete <Route ID>
 end

To add a static route:

edit <Route ID>
set device <interface_name>
set dst x.x.x.x/xx
set gateway x.x.x.x
end

This issue is fixed in FortiAuthenticator version 6.6.3. It is recommended to upgrade to this version or later to avoid this issue.