One of the limitations in deploying Check Point CloudGuard Cluster High Availability is that
One of the limitations in deploying Check Point CloudGuard Cluster High Availability is that
High Availability configurations support only two Security Gateway members. In Check Point CloudGuard Cluster High Availability, the limitation regarding the number of members allowed in a cluster is that only two Security Gateway members can be used in such configuration. This restriction is crucial to understand for proper planning and deployment of the CloudGuard environment.
Only two Cluster Members in a cluster are supported Known Limitations See sk109141 for information about supported Jumbo Hotfix Accumulators. Only two Cluster Members in a cluster are supported. Only High Availability Mode (Active/Standby) is supported. Load Sharing Mode is not supported. VRRP cluster is not supported. Only the Active Cluster Member can reach services from the cluster through VPN. The Standby Cluster Member can reach those services only when it becomes the Active Cluster Member. For outbound and VPN traffic, you cannot delete or disable the public IP addresses of Cluster Members. The feature is only available in Azure Resource Manager deployments. It is not supported with Azure Service Manager (also known as classic) deployments. When you use the standard Internal Load Balancer it does not support Stateful failover. QoS is not applied to interfaces when Route Based VPN is configured, see sk36157.