ADC

Configuring redundancy for node groups

September 14, 2021

Contributed by:

Note

Supported from NetScaler 10.5 Build 52.1115.e onwards.

Node groups can be configured such that when one node group goes down, another node group can take over and process traffic. For example, when a node group NG1 goes down, NG2 takes over.

Note

This functionality can be used to configure data center redundancy where each node group is configured as a data center.

To achieve this use case, cluster nodes must be logically grouped into node groups, where some node groups must be configured as ACTIVE and others as SPARE. The active node group with the highest priority (that is, the lowest priority number) is made operationally active and therefore serves traffic. When a node from this operationally active node group goes down, the node count of this node group is compared with the node count of the other active node groups in order of their priority. If a node group has a higher or equal node count, that node group is made operationally active. Else, the spare node groups are checked.

Note

Only one state-specific node group can be active at a given point in time.

A cluster node inherits the state of the node group. So, if a node with “SPARE” state is added to the node group with state as “ACTIVE”, the node automatically behaves as an active node.

The pre-emption parameter that is defined for the cluster instance decides whether the initial active node group takes the control when it comes up again.

A spare node group can take up a node group and host active traffic when an active node group goes down.

The following figure shows a node group setup that has node group redundancy defined. NG1 is initially the active node group. When it loses one of the nodes, the spare node group (NG3) with the highest priority starts serving traffic.

Figure 1. Citrix ADC cluster with node group redundancy configured.

Node group redundancy

Configuring redundancy for node groups

Log on to the cluster IP address.

Create the active node group and bind the required cluster nodes.

> add cluster nodegroup NG1 -state ACTIVE
> bind cluster nodegroup NG1 -node n1
> bind cluster nodegroup NG1 -node n2
> bind cluster nodegroup NG1 -node n3

Create the spare node group and bind the requisite nodes.

> add cluster nodegroup NG2 -state SPARE -priority 20
> bind cluster nodegroup NG2 -node n4
> bind cluster nodegroup NG2 -node n5
> bind cluster nodegroup NG2 -node n6

Create another spare node group and bind the requisite nodes.

> add cluster nodegroup NG3 -state SPARE -priority 10
> bind cluster nodegroup NG3 -node n7
> bind cluster nodegroup NG3 -node n8
> bind cluster nodegroup NG3 -node n9

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 redundancy for node groups

September 14, 2021

Contributed by:

September 14, 2021

Contributed by:

Configuring redundancy for node groups

Configuring redundancy for node groups

In this article