Documentation | Support

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Clusters
Clusters
 
Help | Content Gateway | v8.4.x
Related topics:
*
Changing clustering configuration
*
Adding nodes to a cluster
*
Deleting nodes from a cluster
*
Virtual IP failover
Content Gateway scales from a single node to a cluster of 2 or more nodes, with a maximum recommended limit of 16. This allows you to quickly increase capacity and improve system performance and reliability.
 
* 
Note 
For assistance with scaling your deployment, contact your Forcepoint account representative.
*
Content Gateway detects the addition and deletion of nodes in the cluster and can detect when a node is down.
*
You can add or delete a node from a cluster at any time.
*
When you remove a node from the cluster, Content Gateway removes all references to the missing node.
*
Restarting a node in the cluster causes all nodes in the cluster to restart.
*
When the Virtual IP failover feature is enabled, the live nodes in a cluster can assume a failed node's traffic.
*
Nodes in a cluster automatically share configuration information except for the following:
*
Filtering Service and Policy Service IP addresses are not propagated around the cluster.
*
In transparent proxy deployments with WCCP, the service group enabled/disabled state and weight settings are not propagated. See Transparent interception with WCCP v2 devices.
*
When SSL support is enabled, the Dynamic Incident List is not propagated around the cluster.
Content Gateway uses a proprietary protocol for clustering, which is multicast for node discovery and heartbeat, and unicast for all data exchange within the cluster.
 
* 
Important 
It is recommended that a dedicated network interface be used for Content Gateway cluster communication, except when the host is a Forcepoint appliance, in which case the P1 interface is recommended.
 
* 
Important 
In a proxy hierarchy, the nodes in the cluster cannot be a mixture of HTTP parents and children.
Management clustering
In management clustering mode you can administer all Content Gateway nodes at the same time because cluster nodes share configuration information.
*
Content Gateway uses a multicast management protocol to maintain a single system image of all nodes in the cluster.
*
Information about cluster membership, configuration, and exceptions is shared across all nodes.
*
The content_manager process propagates configuration changes to cluster nodes.
*
When the HTTPS option is enabled (SSL support), its settings also propagate around the cluster, except for the Dynamic Incident List.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Clusters
Copyright 2017 Forcepoint. All rights reserved.