Cluster Heartbeat Configuration
less than a minute
Heartbeat
The cluster heartbeat defines a persistent connection between cluster members. The heartbeat is used to determine the health of the cluster and to determine which member is the active member. This configuration is required on cluster members.
| Field Name | Description |
|---|---|
| Heartbeat Host | The IP (bound to an interface) on which heartbeat communication will occur |
| Heartbeat Port | The port on which heartbeat communication will occur |
Status Endpoint
(Optional) The Status Endpoint allows you to start an HTTP REST endpoint on a port on the WAN interface IP that will return a 200 response if the member is healthy and the active cluster member. This is commonly needed if a load balancer is being placed in front a cluster to provide high-availability for ZTNA or Wireguard gateway traffic.
| Field Name | Description |
|---|---|
| Endpoint IP | Can be set to the WAN or LAN interface IP address |
| Endpoint Port | Defines the port that the HTTP server will listen on. If blank the HTTP server will be disabled. |
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.