Redundant Interface Set

Last published : Sep 22, 2026
Note
Link redundancy configuration is not supported on a NetScaler VPX instance hosted on a NetScaler SDX appliance.
A redundant interface set is a set of interfaces where one of the interfaces is active and the remaining ones are standby. If the active interface fails, one of the standby interfaces takes over and becomes active.
The following are the main benefits of using redundant interface sets:
  • A redundant interface set ensures connection reliability between the NetScaler appliance and a peer device by providing backup links between them.
  • Unlike link redundancy using LACP, no configuration is required on the peer device for a redundant interface set. To the peer device, the redundant interface set appear as individual interfaces and not as a set or collection.
  • In a high availability configuration (HA), redundant interface sets can minimize the number the HA failovers.
Note
Redundant Interface Set was formerly known as 'NIC bundling' when first introduced in 10.5 release.
Related information

How a Redundant Interface Set Works

For a redundant interface set, the NetScaler appliance derives a MAC address based on an internal algorithm and assigns it to the redundant interface set. This MAC address is shared by all the member interfaces and is used only by the active interface at a time. The active interface broadcasts GARP messages, which contain the MAC address assigned to the redundant interface set and not the interface's own physical MAC address. When the current active interface fails and is taken over by another interface, the new active interface sends GARP messages. The peer device updates its forwarding table with the new active interface information. The standby interfaces do not send any GARP messages. The standby interfaces do not send any packets and they drop any packets they receive.
In a redundant interface set, selection of the member interface as active is based on either of the following factors:
  • Redundant interface priority. This is a parameter of an interface and it defines the priority of the interface in a redundant interface set for the active member selection. This parameter specifies a positive integer. Lower the value higher the priority of active member selection. The member interface with the highest priority (lowest value) is selected as the active interface of the redundant interface set.
  • Binding order of the member interfaces. If all the member interfaces have the same redundant interface priority, the member interface that was bound first to the redundant interface set is selected as the active interface of the redundant interface set.
In a redundant interface set, active interface selection is triggered in one of the following events:
  • When the current active interface fails or you disable it.
  • When you set the priority of a standby interface to a value lower than that of the current active interface. The standby interface takes over as the active interface.
  • When you bind an interface whose priority is lower than that of the current active interface. The newly bound interface takes over as the active interface.

Points to Consider for Configuring Redundant Interface Sets

Consider the following points before you configure a redundant interface set:
  • In a standalone appliance or an appliance in a high availability setup, a link redundant set is specified in LR/X notation, where X can range from 1 to 4. For example, LR/1.
  • In a high availability configuration, redundant interface set configurations do not propagate or synchronize to the secondary node.
  • You can configure a maximum of four redundant interface sets on a NetScaler appliance.
  • You can bind a maximum of 16 interfaces to a redundant interface set.
  • Member interfaces of a redundant interface set cannot be bound to another redundant interface set.
  • Member interfaces of a redundant interface set cannot be bound to a link aggregate (LA) channel.
  • LA channels cannot be bound to a redundant interface set.
  • Redundant interface sets cannot be bound to an LA channel.
  • In a cluster setup:
    • Redundant interface sets cannot be bound to a cluster link aggregation.
    • A link redundant set is specified in N/LR/X notation (for example, 1/LR/3). Where: N is the ID of the cluster node on which the redundant interface set is to be created. X is a link-redundant set identifier on a cluster node. X can range 1–4.
    • A cluster link aggregation cannot be bound to a redundant interface set.
    • A redundant interface set can include only the interfaces of the node to which the redundant interface set belongs.
    • An Existing elink redundancy set configuration on a standalone appliance automatically changes to cluster notation (N/LR/X) after the appliance is added to a cluster setup.

Configuration Steps

Configuring a redundant interface set on a NetScaler appliance consists of the following tasks:
  • Create a redundant interface set. Use the channel command operation for creating a redundant interface set.
    In a standalone appliance or an appliance in a high availability setup, a link redundant set is specified in LR/X notation, where X can range from 1 to 4. For example, LR/1.
    In a cluster setup, a link redundant set is specified in N/LR/X (for example, 1/LR/3), where: N is the ID of the cluster node on which the redundant interface set is to be created; X is the link redundant set identifier on a cluster node. X can range 1–4.
  • Bind interfaces to the redundant interface set. Associate the desired interfaces with the redundant interface set. An interface cannot be a part of multiple redundant interface sets.
  • (Optional) Set a redundant interface priority on the member interface. Use the interface command operation for setting the redundant interface priority on a desired member interface of a redundant interface set.
To create a redundant interface set by using the CLI:
At the command prompt:
  • add channel \<ID>
  • show channel \<ID>
To bind interfaces to a redundant interface set by using the CLI:
At the command prompt:
  • bind channel \<ID> \<ifnum>
  • show channel \<ID>
To set a redundant interface priority of an interface by using the CLI:
At the command prompt:
  • set interface \<ID> -lrsetpriority \<positive_integer>
  • show interface \<ID>
Sample configuration 1:
In the following example, a redundant interface set LR/1 is created, and interfaces 1/1, 1/2, 1/3, and 1/4 are bound to LR/1. The redundant interface priority is set to a default value of 1024 for all these member interfaces. Output of the show channel command displays that the interface 1/1 is the current active interface for the redundant interface set lr/1.
> add channel lr/1
 Done
> bind channel lr/1 1/1 1/2 1/3 1/4
 Done
> show channel
1)    Interface LR/1 (Link Redundant) #23
        flags=0x100c020 <ENABLED, UP, LINKREDUNDANT, UP, HAMON, 802.1q>
        MTU=1500, native vlan=1, MAC=36:97:a2:b7:6b:a9, uptime 0h00m00s
        Requested: media NONE, speed AUTO, duplex NONE, fctl OFF,
                 throughput 0
        Actual: throughput 1000
        LLDP Mode: NONE,
        RX: Pkts(1) Bytes(52) Errs(0) Drops(1) Stalls(0)
        TX: Pkts(2) Bytes(84) Errs(0) Drops(4) Stalls(0)
        NIC: InDisc(0) OutDisc(0) Fctls(0) Stalls(0) Hangs(0) Muted(0)
        Bandwidth thresholds are not set.
                1/1: UTP-1000-FULL-OFF          UP  0h14m06s    LR Active Member
                1/2: UTP-1000-FULL-OFF          UP  0h14m06s    LR Inactive Member
                1/3: UTP-1000-FULL-OFF          UP  0h14m06s    LR Inactive Member
                1/4: UTP-1000-FULL-OFF          UP  0h14m06s    LR Inactive Member
Done
Sample configuration 2:
In the following example, a redundant interface priority of the member interface 1/4 is set to 100, which is lower than the set redundant interface priority of all the other member interfaces of LR/1.
Output of the show channel command displays that the interface 1/4 is the current active interface for the redundant interface set LR/1.
> set interface 1/4 -lrsetPriority 100
Done
> show channel
1)      Interface LR/1 (Link Redundant) #23
        flags=0x100c020 <ENABLED, UP, LINKREDUNDANT, UP, HAMON, 802.1q>
        MTU=1500, native vlan=1, MAC=36:97:a2:b7:6b:a9, uptime 0h00m00s
        Requested: media NONE, speed AUTO, duplex NONE, fctl OFF,
                 throughput 0
        Actual: throughput 1000
        LLDP Mode: NONE,
        RX: Pkts(1) Bytes(52) Errs(0) Drops(1) Stalls(0)
        TX: Pkts(2) Bytes(84) Errs(0) Drops(4) Stalls(0)
        NIC: InDisc(0) OutDisc(0) Fctls(0) Stalls(0) Hangs(0) Muted(0)
        Bandwidth thresholds are not set.
                1/1: UTP-1000-FULL-OFF          UP  0h14m06s    LR Inactive Member
                1/2: UTP-1000-FULL-OFF          UP  0h14m06s    LR Inactive Member
                1/3: UTP-1000-FULL-OFF          UP  0h14m06s    LR Inactive Member
                1/4: UTP-1000-FULL-OFF          UP  0h14m06s    LR Active Member
Done
Sample configuration 3:
Consider a cluster setup of four nodes N1, N2, N3, and N4. In this example, redundant interface set 1/LR/3 is created on node N1, and interfaces 1/1/1, 1/1/2, and 1/1/3 are bound to it. The redundant interface priority is set to a default value of 1024 for all these member interfaces. Output of the show channel command indicates that interface 1/1/1 is the current active interface for redundant interface set 1/LR/3.
    > add channel 1/LR/3

    Done
    > bind channel 1/LR/3 1/1/1 1/1/2 1/1/3

    Done
    > show channel
    1)    Interface 1/LR/3 (Link Redundant) #14
            flags=0x100c020 <ENABLED, UP, LINKREDUNDANT, UP, HAMON, 802.1q>
            MTU=1500, native vlan=1, MAC=36:97:a2:b7:6b:a9, uptime 0h00m00s
            Requested: media NONE, speed AUTO, duplex NONE, fctl OFF,
            throughput 0
            Actual: throughput 1000
            LLDP Mode: NONE,
            RX: Pkts(66) Bytes(4406) Errs(0) Drops(82) Stalls(0)
            TX: Pkts(55) Bytes(2626) Errs(0) Drops(145) Stalls(0)
            NIC: InDisc(0) OutDisc(0) Fctls(0) Stalls(0) Hangs(0) Muted(0)
            Bandwidth thresholds are not set.

            1/1/1: UTP-1000-FULL-OFF UP  0h14m06s LR Active Member
            1/1/2: UTP-1000-FULL-OFF UP  0h14m06s LR Inactive Member
            1/1/3: UTP-1000-FULL-OFF UP  0h14m06s LR Inactive Member

    Done