ADC

Configuring synchronization

November 8, 2023

Contributed by:

C S S

Synchronization is a process of duplicating the configuration of the primary node on the secondary node. The purpose of synchronization is to ensure that there’s no loss of configuration information between the primary and the secondary nodes, regardless of the number of failovers that occur. Synchronization uses TCP port 3008 or 3010.

Synchronization is triggered when one of the following conditions is met:

The secondary node in an HA setup comes up after a restart.
The primary node becomes secondary after a failover.

Automatic synchronization is enabled by default. You can also force synchronization.

Note:

During an HA synchronization, the secondary node runs the clear ns config command to clear the existing configuration and load the new configuration pulled from the primary node. However, the clear configuration does not remove the default static route configured in the secondary node. If this default static route points to an incorrect gateway, it might result in downtime of the services.

Disabling or enabling synchronization

Automatic HA synchronization is enabled by default on each node in an HA pair. You can enable or disable it on either node.

To disable or enable automatic synchronization by using the command line interface

At the command prompt, type:

set HA node -haSync DISABLED
set HA node -haSync ENABLED

To disable or enable synchronization by using the GUI

Navigate to System > High Availability.
Under HA Synchronization, clear or select the Secondary node will fetch the configuration from the Primary option.

Forcing the secondary node to synchronize with the primary node

In addition to automatic synchronization, the Citrix ADC supports forced synchronization. You can force the synchronization from either the primary or the secondary node. When you force synchronization from the secondary node, it starts synchronizing its configuration with the primary node.

However, if synchronization is already in progress, forced synchronization fails and the system displays a warning. Forced synchronization also fails in any of the following circumstances:

You force synchronization on a standalone system.
The secondary node is disabled.
HA synchronization is disabled on the secondary node.

To force synchronization by using the command line interface

At the command prompt, type:

force HA sync

To force synchronization by using the GUI

Navigate to System > High Availability.
On the Nodes tab, in the Action list, click Force Synchronization.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Configuring synchronization

November 8, 2023

Contributed by:

C S S

November 8, 2023

Contributed by:

C S S

Configuring synchronization

Disabling or enabling synchronization

To disable or enable automatic synchronization by using the command line interface

To disable or enable synchronization by using the GUI

Forcing the secondary node to synchronize with the primary node

To force synchronization by using the command line interface

To force synchronization by using the GUI

In this article