Fortinet black logo

GCP Administration Guide

Configure health check probe responders

Configure health check probe responders

To configure health check probe responders:
  1. In Google Cloud console, go to Network Services > Load balancing.
  2. Find the external and internal load balancers (LB) that you created and note their frontend IP addresses (public for external LB and private for internal LB).
  3. In the FortiGate CLI, add a secondary IP address to port1, replacing ELB_FRONTEND with the external LB frontend public IP address:

    config system interface edit port1 set secondary-IP enable config secondaryip edit 0 set ip ELB_FRONTEND/32 set allowaccess probe-response next end next end

  4. Repeat the same step for port2 and the internal LB frontend:

    config system interface edit port2 set secondary-IP enable config secondaryip edit 0 set ip ILB_FRONTEND/32 set allowaccess probe-response next end next end

  5. Enable HTTP probe responses:

    config system probe-response set mode http-probe end

  6. Enter y to confirm restarting the probe response daemon.

Configure health check probe responders

To configure health check probe responders:
  1. In Google Cloud console, go to Network Services > Load balancing.
  2. Find the external and internal load balancers (LB) that you created and note their frontend IP addresses (public for external LB and private for internal LB).
  3. In the FortiGate CLI, add a secondary IP address to port1, replacing ELB_FRONTEND with the external LB frontend public IP address:

    config system interface edit port1 set secondary-IP enable config secondaryip edit 0 set ip ELB_FRONTEND/32 set allowaccess probe-response next end next end

  4. Repeat the same step for port2 and the internal LB frontend:

    config system interface edit port2 set secondary-IP enable config secondaryip edit 0 set ip ILB_FRONTEND/32 set allowaccess probe-response next end next end

  5. Enable HTTP probe responses:

    config system probe-response set mode http-probe end

  6. Enter y to confirm restarting the probe response daemon.