Home > Configuration > High Availability

Use this method to adds a peer node to an HA configuration. Each node must add the other as a peer. An algorithm determines which node becomes primary and which becomes secondary.

Use this method to bind routemonitor to HA node.

Use this method to forces an HA failover. Can be initiated from either node. A forced failover is not propagated or synchronized.,
Note: This method fails under any of the following conditions:
* The secondary node is disabled or configured to remain secondary.
* The primary node is configured to remain primary.
* The state of the peer node is unknown.
* You run the method on a standalone appliance.

Use this method to forces duplication of the primary node's configuration on the secondary node. Can be executed from either node.
Note: This method fails under any of the following conditions:
* Synchronization is already in progress.
* The secondary node is disabled.
* Synchronization is disabled on either node
* The secondary node is not accessible from the primary.
* You run the method on a standalone appliance.

Use this method to get the HA settings of both nodes or, if you specify a node, just the specified node.

Use this method to get the list of methods failed during HA configuration synchronization.

Use this method to removes the peer node from the HA configuration. To completely remove both the nodes from the HA configuration, you have to log on to each node and remove its peer node.

Use this method to set number of seconds after which a peer node is marked DOWN if heartbeat messages are not received from the peer node.

Use this method to set keep one node primary if both nodes fail the health check, so that a partially available node can back up data and handle traffic. This mode is set independently on each node.

Use this method to set automatically propagate all methods from the primary to the secondary node, except the following:
* All HA configuration related methods. For example, add ha node, set ha node, and bind ha node.
* All Interface related methods. For example, set interface and unset interface.
* All channels related methods. For example, add channel, set channel, and bind channel.
The propagated method is executed on the secondary node before it is executed on the primary. If method propagation fails, or if method execution fails on the secondary, the primary node executes the method and logs an error. Command propagation uses port 3010.
Note: After enabling propagation, run force synchronization on either node.

Use this method to set the HA status of the node. The HA status STAYSECONDARY is used to force the secondary device stay as secondary independent of the state of the Primary device. For example, in an existing HA setup, the Primary node has to be upgraded and this process would take few seconds. During the upgradation, it is possible that the Primary node may suffer from a downtime for a few seconds. However, the Secondary should not take over as the Primary node. Thus, the Secondary node should remain as Secondary even if there is a failure in the Primary node.
STAYPRIMARY configuration keeps the node in primary state in case if it is healthy, even if the peer node was the primary node initially. If the node with STAYPRIMARY setting (and no peer node) is added to a primary node (which has this node as the peer) then this node takes over as the new primary and the older node becomes secondary. ENABLED state means normal HA operation without any constraints/preferences. DISABLED state disables the normal HA operation of the node.

Use this method to set automatically maintain synchronization by duplicating the configuration of the primary node on the secondary node. This setting is not propagated. Automatic synchronization requires that this setting be enabled (the default) on the current secondary node. Synchronization uses TCP port 3010.

Use this method to set interval, in milliseconds, between heartbeat messages sent to the peer node. The heartbeat messages are UDP packets sent to port 3003 of the peer node.

Use this method to set max number of flips allowed before becoming sticky primary

Use this method to set interval after which flipping of node states can again start

Use this method to set strict mode flag for sync status

Use this method to set vlan on which HA related communication is sent. This include sync, propagation , connection mirroring , LB persistency config sync, persistent session sync and session state sync. However HA heartbeats can go all interfaces.

Use this method to synchronize various configuration files from the primary node to the secondary. You can run this method from either node. Files that are present on only the secondary and are specific to the secondary are not deleted. This method fails if the secondary node is disabled, the secondary node is not accessible from the primary, or you enter the method on a standalone appliance.

Use this method to unbind routemonitor from HA node.

Remove HA node deadinterval setting.

Remove HA node failsafe setting.

Remove HA node haprop setting.

Remove HA node hastatus setting.

Remove HA node hasync setting.

Remove HA node hellointerval setting.

Remove HA node maxflips setting.

Remove HA node maxfliptime setting.

Remove HA node syncstatusstrictmode setting.

Remove HA node syncvlan setting.