Gateway

Configuring command propagation

January 8, 2024

Contributed by:

C S C

In a high availability setup, any command issued on the primary node propagates automatically to, and runs on, the secondary node before the command runs on the primary node. If command propagation fails, or if command execution fails on the secondary node, the primary node executes the command and logs an error. Command propagation uses port 3011.

In a high availability 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 a high availability pair. If you disable command propagation on the primary node, commands are not propagated to the secondary node. If you disable command propagation on the secondary node, commands propagated from the primary are not executed on the secondary node.

Note: After reenabling propagation, remember to force synchronization.

Note: If synchronization occurs while you are 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 in which propagation is disabled while synchronization is in progress.

To enable or disable propagation on the primary node

In the configuration utility, on the Configuration tab, in the navigation pane, expand System and then click High Availability.
In the details pane, on the Nodes tab, select a node and then click Edit.
Under HA propagation, do one of the following:
- To disable high availability propagation, clear the Primary node will propagate configuration to the Secondary check box.
- To enable high availability propagation, select the Primary node will propagate configuration to the Secondary check box.
Click OK.

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 command propagation

January 8, 2024

Contributed by:

C S C

January 8, 2024

Contributed by:

C S C

Configuring command propagation

To enable or disable propagation on the primary node

In this article