Source
Architecture, reliability & security assurance — found from sitemap — Appgate SDP
Checked for Appgate SDP on 10 Nov 2026
- Page
- https://support.appgate.com/docs/high-availability-ha-v7-0
- Checked
- 10 Nov 2026, 12:02 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:2f14dce0991678c477534a2a8e1468c7582c58722ab05eb5e39b3932da167392
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Ha builtin Report an error
“AppGate ZTNA includes built-in high availability (HA) mechanisms at multiple levels.”
-
Load balancer limitations Report an error
“You can use external load balancers in front of Controllers and Gateways, but doing so introduces limitations. Two of AppGate ZTNA's core security features—SPA and mutual TLS (mTLS)—restrict the use of several load balancer features, and some advanced HA features are unavailable entirely.”
-
Spa udp lb incompatible Report an error
“UDP-TCP SPA mode cannot be used with an external load balancer because the load balancer cannot handle both UDP and TCP traffic.”
-
Spa mtls lb layer Report an error
“TCP SPA mode with mTLS prevents the use of any application-layer load balancer, because together these features protect against man-in-the-middle attacks. The load balancer must operate exclusively at the DNS or TCP/IP layer.”
-
Supported lb configs Report an error
“Two configurations are supported: Round-robin DNS. Set the Client Hostname/IP (Gateway) or Profile DNS name (Controller) to return multiple IP addresses.”
-
Stateless appliances Report an error
“AppGate ZTNA uses linearly scalable, stateless appliances.”
-
Client round robin Report an error
“The client uses a built-in round-robin load-balancing algorithm to select Controllers and Gateways.”
-
Cross collective ha Report an error
“AppGate ZTNA also supports advanced mechanisms including cross-Collective HA, which allows clients to fail over to a different Collective when no Controllers are available.”
-
Multi logforwarder ha Report an error
“HA functionality extends to Connectors (see Adding a Connector) and multi-LogForwarder HA (see Audit logs).”
-
Internal ha triggers Report an error
“The Controller instructs the client to fail over to a different Controller due to high load, exhausted IP pool space, or LDAP timeouts. This requires multiple Controllers per Collective.”
-
Controller profile dns Report an error
“The internal load-balancing mechanism relies on the profile DNS name created when you create the first Controller. This name is automatically shared across all Controllers in the Collective. Create a multiple A-record DNS entry for this name—one record per Controller.”
-
Profile group weighting Report an error
“A profile group contains multiple client profiles from any Collective. Each profile is assigned a weighting that works similarly to Gateway weightings. When no Controllers for a given client profile are available, the client checks for another profile in the same group.”
-
Alternative auth path Report an error
“Cross-Collective HA can also provide an alternative authentication path to a single Collective. For example, assign a higher weighting to an OIDC client profile and a lower weighting to an LDAP profile.”
-
Gateway autosuspend thresholds Report an error
“eventQueueUsage Percentage of the event queue used (events awaiting processing by sessiond) 70% 50% javaHeapUsage Percentage of sessiond memory used versus maxiumum heap 90% 75% numberOfSessions Number of user sessions on the Gateway 8000 7500 systemMemoryUsage Percentage of total memory used on the Gateway 85% 70%”
-
Session retention after failover Report an error
“Because there is no Gateway-to-Gateway communication in AppGate ZTNA, the original Gateway retains the user's session for five minutes after the client connects elsewhere, then terminates it.”
-
Transparent failover Report an error
“Established network connections continue without interruption, and the failover is transparent to the user and to applications on the device.”
-
Snat stateful failover Report an error
“Stateful failover at the TCP/IP level is not possible when SNAT is enabled, because the protected host must see the failed-over connection from the same IP address.”
-
Keepalive interval Report an error
“Once connected, the client monitors traffic and sends a keep-alive message every five seconds when no application traffic is detected.”
-
Gateway weighting Report an error
“Each Gateway is assigned a three-digit Client Tunneling - Load Balance Weighting Factor. Gateways with equal weights receive equal traffic. The ratio between weights determines the distribution—not the absolute values.”
-
Zero weight reserve Report an error
“Assigning a weight of zero to a Gateway places it in reserve. The client always tries higher-weighted Gateways first. It tries zero-weighted Gateways only when no others are available.”
-
Priority groups Report an error
“Priority groups activate automatically when every Gateway on a Site uses a weighting factor of four or more digits (greater than 999). The last three digits represent the weighting factor. The preceding digits represent the priority group number. Higher group numbers are tried first.”
-
Monitored action failover Report an error
“When configuring an entitlement, you can enable monitoring for HTTP and TCP Up action types. The system checks monitored applications for return traffic. If no return traffic arrives within the response timeout period, the system marks the application as unhealthy.”
-
Unhealthy report retention Report an error
“The client retains unhealthy reports for 10 minutes, after which it assumes the Gateway is healthy again.”
-
Fallback site Report an error
“The client attempts to find a working Gateway on a Site for a minimum of 30 seconds. After this period, the client switches to the fallback Site.”
-
Fallback site no chaining Report an error
“The fallback Site feature does not support chaining Sites. You can have only one primary and one fallback Site for a given entitlement.”
-
Fallback site ram sizing Report an error
“the fallback Site uses approximately 50 percent of the additional RAM required for the extra entitlements during normal operation, rising to 100 percent when failover occurs.”
-
Fallback site policy control Report an error
“Enable Use fallback Site in the relevant policies to control which users can use the fallback Site.”
Scores citing this record
- The DevOps Engineer Identity, access policy & device posture
- The DevOps Engineer Architecture, reliability & security assurance
- The DevOps Engineer European sovereignty
- The IT Lead Identity, access policy & device posture
- The IT Lead Architecture, reliability & security assurance
- The IT Lead European sovereignty
- The MSP Technician Identity, access policy & device posture
- The MSP Technician Architecture, reliability & security assurance
- The MSP Technician European sovereignty
- The Operations Manager Access model & connectivity
- The Operations Manager Identity, access policy & device posture
- The Operations Manager Architecture, reliability & security assurance
- The Operations Manager European sovereignty
- The Information Security Officer Architecture, reliability & security assurance
- The Skeptic Identity, access policy & device posture
- The Skeptic Architecture, reliability & security assurance