Go to the table of contents Go to the previous page Go to the next page Go to the index View or print as PDF
Clusters
Related topics:
*
When the Virtual IP failover feature is enabled, the live nodes in a cluster can assume a failed node's traffic.
Note 
Important 
It is recommended that a dedicated network interface be used for Content Gateway cluster communication, except when the host is a V-Series appliance, in which case the P1 (eth0) interface is recommended.
Important 
Note 
*
The content_manager process propagates configuration changes to cluster nodes.
To configure SSL Manager to propagate configuration information around the cluster, one node must be selected as the primary node on which all SSL configuration changes are made. The primary is known as the SSL Manager Configuration Server. All other nodes are secondaries.
3.
Go to the Configure > My Proxy > Basic > Clustering tab.
4.
In the SSL Manager Configuration Server field, enter the IP address of the SSL Manager Configuration Server (the primary). If the field is not editable, the system is not a member of a cluster.
5.
Click Apply and restart Content Gateway. Note that all Content Gateway nodes are restarted. The restart identifies the primary to all cluster members and activates SSL clustering.
The configuration can be confirmed on the Monitor > My Proxy > Summary page, at the bottom of the Node Details section. If the SSL Manager Configuration Server IP address is a link, the server is another node in the cluster. Click the link to log onto the SSL Manager Configuration Server.

Go to the table of contents Go to the previous page Go to the next page Go to the index View or print as PDF
Clusters