Changing clustering configuration

Clustering is usually configured when you install the proxy. You can, however, configure clustering afterward, or at any time, in the Content Gateway manager.

In the Content Gateway manager, go to Configure > My Proxy > Basic > Clustering.

In the Cluster Type area, select the clustering mode:

Select Management Clustering to include this proxy in a cluster.

Select Single Node if this node is not part of a cluster.

In the Interface area, enter the name of the network interface. This is the interface used by Content Gateway to communicate with other nodes in the cluster, for example: eth1.

Node configuration information is multicast, in plain text, to other Content Gateway nodes on the same subnet. Therefore, Websense recommends that clients be located on a separate subnet from Content Gateway nodes (multicast communications for clustering are not routed).

On V-Series appliances, P1 (eth0) is the recommended interface. However, you may also use P2 (eth1) if you want to isolate cluster management traffic.

In the Cluster Multicast Group Address area, enter the multicast group address that all members of the cluster share. The default is 224.0.1.37.

Warning

Ensure that the multicast IP address does not conflict with the same address used by any other application or service.

If there is a conflict and the Content Gateway node is allowed to restart, it will fail to initialize the interface and the Content Gateway instance will shut down. You can verify the condition by examining /var/log/messages and looking for a message similar to:

[LocalManager::initCCom] Unable to find network interface eth2.#011 Exiting

To correct the problem, identify a unique multicast IP address that will work for all members of the cluster and:

If Content Gateway is on an appliance:

Log on to the appliance manager, go to Administration > Toolbox, and open the Command Line Utility.

Select the Websense Content Gateway Module and then the command 'content-line -s'.

Specify the Variable Name proxy.config.cluster.mc_group_addr and give Value the multicast IP address.

Check each member of the cluster to ensure that they are all using the same multicast IP address.

Restart the node.

If Content Gateway is installed on a separate server:

Log on to the Linux host and go to /opt/WCG/config.

Edit (vi) records.config, find proxy.config.cluster.mc_group_addr and assign it the value of the multicast IP address.

Check each member of the cluster to ensure that they are all using the same multicast IP address.

Restart the node.

Click Apply.

Click Restart on Configure > My Proxy > Basic > General.


	Important Content Gateway does not apply the clustering mode change to all of the nodes in the cluster. You must change the clustering mode on each node individually.