Configure an interface link bundle

Updated: September 11, 2026

Want to summarize with AI?

Provides step-by-step instructions for configuring an interface link bundle, guiding users through setup, required parameters, and validation procedures for proper operation.

Configure a link bundle between two routers and verify that the interfaces forming the bundle are active.

Cisco IOS XR software supports the EtherChannel method for bundling Ethernet interfaces. EtherChannel is a Cisco proprietary technology that allows you to configure multiple links in a bundle but does not check link compatibility automatically. IEEE 802.3ad encapsulation uses Link Aggregation Control Protocol (LACP) to ensure all member links in an Ethernet bundle are compatible.

Incompatible or failed links are automatically removed from the bundle.

Before you begin

Create a bundle instance.
Map physical interface(s) to the bundle.
For an Ethernet bundle to be active, you must perform the same configuration on both connection endpoints of the bundle.

Procedure

Create the Ethernet link bundle.

Example:

Router# configure
Router(config)# interface Bundle-Ether 3
Router(config-if)# ipv4 address 10.1.2.3 255.0.0.0
Router(config-if)# bundle maximum-active links 32 hot-standby
Router(config-if)# bundle minimum-active links 1
Router(config-if)# bundle minimum-active bandwidth 30000000
Router(config-if)# exit

Map the physical interfaces to the bundle.

Mixed link bundle mode is supported only when active-standby operation is configured.

Example:

Router(config)# interface HundredGigE 0/0/0/0
Router(config-if)# bundle id 3 mode active
Router(config-if)# no shutdown
Router(config)# exit

Router(config)# interface HundredGigE 0/0/0/1
Router(config-if)# bundle id 3 mode active
Router(config-if)# no shutdown
Router(config-if)# exit

Router(config)# interface HundredGigE 0/0/0/2
Router(config-if)# bundle id 3 mode active
Router(config-if)# no shutdown
Router(config-if)# exit

Check the running configuration.

Example:

Router# show running-configuration
configure
interface Bundle-Ether 3
 ipv4 address 10.1.2.3 255.0.0.0
 bundle maximum-active links 32 hot-standby
 bundle minimum-active links 1
 bundle minimum-active bandwidth 30000000
!
interface HundredGigE 0/0/0/0
 bundle-id 3 mode active
!

interface HundredGigE 0/0/0/1
 bundle-id 3 mode active
!
interface HundredGigE 0/0/0/2
 bundle-id 3 mode active
!

Use the show bundle bundle-ether 3 to verify that interfaces forming the bundle are active and the status of the bundle is Up.

Example:

Router# show bundle bundle-ether 3
Tue Feb  4 18:24:25.313 UTC

Bundle-Ether1
  Status:                                    Up
  Local links <active/standby/configured>:   3 / 0 / 3
  Local bandwidth <effective/available>:     30000000 (30000000) kbps
  MAC address (source):                      1234.1234.1234 (Configured)
  Inter-chassis link:                        No
  Minimum active links / bandwidth:          1 / 1 kbps
  Maximum active links:                      32
  Wait while timer:                          2000 ms
  Load balancing:                            Default
  LACP:                                      Operational
    Flap suppression timer:                  Off
    Cisco extensions:                        Disabled
    Non-revertive:                           Disabled
  mLACP:                                     Not configured
  IPv4 BFD:                                  Not configured

  Port                  Device           State        Port ID         B/W, kbps
  --------------------  ---------------  -----------  --------------  ----------
  Hu0/0/0/0            Local            Active       0x8000, 0x0000    10000000
      Link is Active
  Hu0/0/0/1            Local            Active       0x8000, 0x0000    10000000
      Link is Active
  Hu0/0/0/2            Local            Active       0x8000, 0x0000    10000000
      Link is Active

The interface link bundle is configured, and you can verify that the bundle status is Up and the member links are active.

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.