GCP Load Blanacer

In a FortiGate HA setup, particularly in an active-passive configuration, the active unit handles all traffic and health checks, while the standby unit remains passive and does not perform active health checks. This is expected behavior, as the standby unit will only take over if the active unit fails.

For FortiWeb in an active-active setup, both units should be actively handling traffic and health checks. If the GCP load balancer is only showing the healthy status of the active unit and not the standby, it may be due to the following reasons:

1. Configuration Check: Ensure that the FortiWeb appliances are correctly configured for active-active operation. Both units should be set to handle traffic and perform health checks.

2. Health Check Configuration: Verify that the health check settings on the GCP load balancer are correctly configured to monitor both FortiWeb units. Ensure that the health check targets the correct IP addresses and ports for both units.

3. Network Connectivity: Check the network connectivity between the GCP load balancer and the FortiWeb units. Ensure that there are no network issues preventing the load balancer from reaching the standby unit.

4. Logs and Diagnostics: Review the logs and diagnostic information on both the FortiGate and FortiWeb units to identify any issues that might be affecting the health check status.

If the issue persists, further investigation into the specific configuration and network setup may be required.