Envoy provides cluster load balancing between FortiADCs running at two or more geographically distributed locations -- called GeoSites. Each GeoSite is configured with a cluster that is capable of responding to requests for the same content. A GeoCluster is a collection of GeoSites that act together to determine the “best” GeoSite to respond to a particular request.
Envoy works together with special entries in the Domain Name System (DNS) configuration of the authoritative name server for a website.
Both GeoClusters and GeoSites are top-level objects in the CLI. In general:
GeoCluster flags can be either icmp (enable ICMP triangulation) or autof (automatic fallback). [The autof option is not yet implemented.]
Geosite Instance Flags
A flag may be turned off by prefixing with "!".
default | When enabled, designates this GeoSite instance as the default GeoSite instance for the GeoCluster. Envoy load balances to the default GeoSite instance whenever it cannot choose a GeoSite instance based on probe responses. [This can happen, for example, when probe responses are not received from any site, when the resource (cluster) is down at all available sites, etc.] If no default GeoSite instance is selected for a GeoCluster and all GeoSites are down, then Envoy sends a null response to the client DNS. |
disabled | When enabled, this GeoSite instance will not be selected as a response to a DNS query. |
hot_spare - | When enabled, indicates that this GeoSite instance will be selected only when no other sites are available. |
preferred | When enabled, indicates that this GeoSite instance will always be selected if it is available. |