ADC

Configuring command propagation

In an HA setup, any command issued on the primary node propagates to the secondary node. The propagated command is run on the secondary node before it’s run on the primary node. If command propagation or execution fails on the secondary, the primary node runs the command and logs an error. Command propagation uses TCP port 3008 or 3010.

In an HA pair configuration, command propagation is enabled by default on both the primary and secondary nodes. You can enable or disable command propagation on either node in an HA pair. If you disable command propagation on the primary node, commands aren’t propagated to the secondary node. If you disable command propagation on the secondary node, commands propagated from the primary node aren’t run on the secondary node.

Note

After re-enabling propagation, remember to force synchronization.

If synchronization occurs while you’re disabling propagation, any configuration-related changes that you make before the disabling of propagation takes effect are synchronized with the secondary node. This is also true for cases where propagation is disabled while synchronization is in progress.

To disable or enable command propagation by using the command line interface

At the command prompt, type:

  • set HA node -haProp DISABLED
  • set HA node -haProp ENABLED

To disable or enable command propagation by using the GUI

  1. Navigate to System > High Availability and, on the Nodes tab, open the node.
  2. Clear or select the Primary node will propagate the configuration to the Secondary option.

Note:

Command propagation is disabled during HA synchronization to prevent any conflicting command settings, which can lead to command propagation failure.

Configuring command propagation