Content Gateway configuration files fail to re-sync in clustering mode when a node is down and then restored
- Article Number: 000004464
- Products: Forcepoint V10000 Appliance, Forcepoint V20000 Appliance, Forcepoint V5000 Appliance, Forcepoint Virtual Appliance, Forcepoint Web Security, Forcepoint X Series Appliance, TRITON AP-WEB
- Version: 8.5, 8.4, 8.3, 8.2, 8.1, 8.0
- Last Published Date: November 30, 2020
Notes & Warnings
Note See Clusters for more information regarding Content Gateway clustering.
If you deploy two or more Forcepoint Web Security appliances so that their Content Gateway modules form a cluster, then all the Content Gateway nodes in that cluster share configuration information. This means that a configuration change on one Content Gateway node is automatically made in all other nodes.
However, there is a known situation that can temporarily disrupt the synchronization of configuration settings in a Content Gateway cluster. This article explains how that can occur, and tells how to correct it.
Suppose that appliances A and B are deployed as part of a Content Gateway cluster.
The underlying issue is simply that both Content Gateway modules changed (appliance A was restored; appliance B underwent a proxy configuration change while A was stopped). Thus, both Content Gateway modules increased their internal configuration tracking number by 1. So, the two appliances think their Content Gateway configurations match.
A simple restart does not resolve this problem.
Instead, make a configuration change on either of Content Gateways in the cluster and click Apply. There is no need to restart after the Apply.