For example, to use interface 1/2 as the backplane interface for node 4, connect a cable from the 1/2 interface of node 4 to the backplane switch.
Important points to note when setting up the cluster backplane
Do not use the appliance's management interface (0/x) as the backplane interface. In a cluster, the interface 0/1/x is read as:
0 -> node ID 0
1/x -> NetScaler interface
Backlane interfaces must not be used for the client or server data planes.
Configure a link aggregate (LA) channel to optimize the throughput of the cluster backplane.
Citrix recommends that you dedicate a separate switch for the backplane, so that large amounts of traffic can be handled seamlessly.
Backplane interfaces of all nodes of a cluster must be connected to the same switch and bound to the same L2 VLAN.
If you have multiple clusters with the same cluster instance ID, make sure that the backplane interfaces of each cluster are bound to a different VLAN.
The backplane interface is always monitored, regardless of the HA monitoring settings of that interface.
> set interface <backplane_interface> -mtu <value>
The MTU for interfaces of the backplane switch must be specified to be greater than or equal to 1578 bytes, if the cluster has features like MBF, L2 policies, ACLs, routing in CLAG deployments, and vPath.