ADC

Transitioning between a L2 and L3 Cluster

August 20, 2024

Contributed by:

C C S

Note

Supported from NetScaler 11 onwards.

An L2 cluster is one where all the nodes are from the same network and an L3 cluster is one that can include nodes from different networks. You can seamlessly transition from one type of cluster to the other without any downtime for the applications that are deployed on the Citrix ADC.

Transitioning a cluster from L2 to L3

You can transition to an L3 cluster when you want the cluster to include nodes from other networks.

On the cluster IP address, do the following:

Create a nodegroup.

Example
```
> add cluster nodegroup NG0
```
This nodegroup is used in the next step to group all the nodes from the existing L2 cluster.
Transition the L2 cluster to an L3 cluster.

Example
```
> set cluster instance 1 -inc ENABLED -nodegroup NG0
```
This command achieves the dual purpose of transitioning to L3 cluster and also adding all the nodes of the L2 cluster to the nodegroup.
Now, you can add more nodes to the cluster as explained in “Adding a Node to the Cluster”.

Transitioning a cluster from L3 to L2

You can transition to an L2 cluster when you want to retain nodes that belong to a single network.

On the cluster IP address, do the following:

Remove the cluster nodes from the networks that you do not want to retain.

Example
```
> rm cluster node <nodeId>
```
Transition the L3 cluster to a L2 cluster.

Example
```
> set cluster instance 1 -inc DISABLED
```
The cluster now includes nodes only of a single network.

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.

Transitioning between a L2 and L3 Cluster

August 20, 2024

Contributed by:

C C S

August 20, 2024

Contributed by:

C C S

Transitioning between a L2 and L3 Cluster

Transitioning a cluster from L2 to L3

Transitioning a cluster from L3 to L2

In this article