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