Product Documentation

Using Cluster Link Aggregation

Feb 08, 2016

Cluster link aggregation, as the name suggests, is a group of interfaces of cluster nodes. It is an extension of NetScaler link aggregation. The only difference is that, while link aggregation requires the interfaces to be from the same device, in cluster link aggregation, the interfaces are from different nodes of the cluster. For more information about link aggregation, see "Configuring Link Aggregation".

Important

  • Cluster link aggregation is supported for a cluster of hardware (MPX) appliances.

  • Cluster link aggregation is supported for a cluster of virtual (VPX) appliances that are deployed on ESX and KVM hypervisors, with the following restrictions:

    • Dedicated interfaces need to be used. This means that the interfaces must not be shared with other virtual machines.

    • If the cluster link aggregation member interfaces are manually disabled or if cluster link aggregation itself is manually disabled, then interface power down capability is achieved only by LACP timeout mechanism.

    • Jumbo MTU is not supported on LACP cluster link aggregation.

Note: Cluster link aggregation is not supported on VPX appliances that are deployed on XenServer, AWS, and Hyper-V.

  • Cluster link aggregation is not supported on NetScaler SDX appliances.

For example, consider a three-node cluster where all three nodes are connected to the upstream switch. A cluster LA channel (CLA/1) is formed by binding interfaces 0/1/2, 1/1/2, and 2/1/2.

Figure 1. Cluster Link Aggregation topology

A cluster LA channel has the following attributes:

  • Each channel has a unique MAC agreed upon by cluster nodes.
  • The channel can bind both local and remote nodes' interfaces.
  • A maximum of four cluster LA channels are supported in a cluster.
  • Backplane interfaces cannot be part of a cluster LA channel.
  • When an interface is bound to a cluster LA channel, the channel parameters have precedence over the network interface parameters. A network interface can be bound to one channel only.
  • Management access to a cluster node, must not be configured on a cluster LA channel (for example, CLA/1) or its member interfaces. This is because when the node is INACTIVE, the corresponding cluster LA interface is marked as power down and therefore looses management access.
Figure 2. Traffic distribution flow using cluster LA