How do I ensure that Content Gateway is properly identified in the network?

Content Gateway: Frequently Asked Questions : How do I ensure that Content Gateway is properly identified in the network?

How do I ensure that Content Gateway is properly identified in the network?

Content Gateway FAQs | Forcepoint Web Security | v8.4.x | 31-July-2017

To ensure that every Content Gateway node is found and correctly identified on the network, configure the /etc/hosts file on every Content Gateway node in a cluster.


	Note If Content Gateway is located on an appliance, there is nothing to do. Configuration of the /etc/hosts is handled automatically as part of initial configuration.

If this is not done, Content Gateway may fail to connect to the Forcepoint Web Security Policy Server or other network services. Sometimes the problem doesn't surface immediately, or surfaces after a second Content Gateway node is added.


	Important In a Content Gateway cluster, the cluster name, which is shared by all nodes, cannot be the same as any hostname.

Configuring the /etc/hosts file

On each Content Gateway node, edit the /etc/hosts file to include—ON THE FIRST LINE—the IP address, fully qualified domain name, and hostname of the node.

Log on to the Content Gateway host system as root.

Edit /etc/hosts. A typical default /etc/hosts file looks like:

127.0.0.1 localhost.localdomain localhost

Open a new first line and specify the IP address, domain name, and hostname of the system. The format is:

xxx.xxx.xxx.xxx [FQDN] [hostname]

[FQDN] is the fully-qualified domain name of the machine, e.g. hostname.subdomain.top-level-domain.

[hostname] is the system hostname.

For example:

10.10.10.10 wcg1.example.com wcg1

127.0.0.1 localhost.localdomain localhost

The IP address must be static and not served by DHCP. The proxy uses this IP address in features such as transparent authentication and hierarchical caching.