ADC

High Availability FAQs

November 8, 2023

Contributed by:

C S S

What are the various ports used to exchange the HA-related information between the nodes in an HA configuration?

In an HA configuration, both nodes use the following ports to exchange HA-related information:
- UDP Port 3003, to exchange heartbeat packets.
- TCP Port 3008 or 3010, for synchronization and command propagation.
What are the conditions that trigger synchronization?

Synchronization is triggered by any of the following conditions:
- The incarnation number of the primary node, received by the secondary, does not match that of the secondary node. Note: Both nodes in an HA configuration maintain a counter called incarnation number, which counts the number of configurations in the node’s configuration file. Each node sends its incarnation number to each other node in the heartbeat messages. The incarnation number isn’t incremented for the following commands:
  1. All HA configuration related commands. For example, add ha node, set ha node, and bind ha node.
  2. All Interface related commands. For example, set interface and unset interface.
  3. All channel-related commands. For example, add channel, set channel, and bind channel.
- The secondary node comes up after a restart.
- The primary node becomes secondary after a failover.
What configurations aren’t synced or propagated in an HA configuration in INC or non-INC mode?

The following commands are neither propagated nor synced to the secondary node:
- All node specific HA configuration commands. For example, add ha node, set ha node, and bind ha node.
- All Interface related configuration commands. For example, set interface and unset interface.
- All channel related configuration commands. For example, add channel, set channel, and bind channel.
Note:

The following configurations are neither synced nor propagated only in HA in INC mode. Each node has its own:
- SNIPs
- VLANs
- Routes (except LLB routes)
- Route monitors
- RNAT rules (except any RNAT rule with VIP as the NAT IP)
- Dynamic routing configurations
- Net profiles
Does a configuration added to the secondary node get synchronized on the primary?

No, a configuration added to the secondary node isn’t synchronized to the primary.
What can be the reason for both nodes claiming to be the primary in an HA configuration?

The most likely reason is that the primary and secondary nodes are both healthy but the secondary does not receive the heartbeat packets from the primary. The problem can be with the network between the nodes.
Does an HA configuration run into any issues if you deploy the two nodes with different system clock settings?

Different system-clock settings on the two nodes can cause the following issues:
- The time stamps in the log file entries do not match. This situation makes it difficult to analyze the log entries for any issues.
- After a failover, you might have problems with any type of cookie-based persistence for load balancing. A significant difference between the times can cause a cookie to expire sooner than expected, resulting in termination of the persistence session.
- Similar considerations apply to any time-related decisions on the nodes.
What are the conditions for failure of the force HA sync command?

Forced synchronization fails in any of the following circumstances:
- You force synchronization when synchronization is already in progress.
- You force synchronization on a standalone Citrix ADC appliance.
- The secondary node is disabled.
- HA synchronization is disabled on the current secondary node.
- HA propagation is disabled on the current primary node and you force synchronization from the primary.
What are the conditions for failure of the sync HA files command?

Synchronizing configuration files fail in either of the following circumstances:
- On a standalone system.
- With the secondary node disabled.
In an HA configuration, if the secondary node takes over as the primary, does it switch back to secondary status if the original primary comes back online?

No. After the secondary node takes over as the primary, it remains as primary even if the original primary node comes back online again. To interchange the primary and secondary status of the nodes, run the force failover command.
What are the conditions for failure of the force failover command?

A forced failover fails in any of the following circumstances:
- You force failover on a standalone system.
- The secondary node is disabled.
- The secondary node is configured to remain secondary.
- The primary node is configured to remain primary.
- The state of the peer node is unknown.

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.

High Availability FAQs

November 8, 2023

Contributed by:

C S S

November 8, 2023

Contributed by:

C S S

High Availability FAQs

In this article