Cisco IOS XR Interface and Hardware Component Configuration Guide, Release 3.6
Configuring Link Bundling on Cisco IOS XR Software
Downloads: This chapterpdf (PDF - 528.0KB) The complete bookPDF (PDF - 4.93MB) | Feedback

Configuring Link Bundling on Cisco IOS XR Software

Table Of Contents

Configuring Link Bundling on Cisco IOS XR Software

Contents

Prerequisites for Configuring Link Bundling

Prerequisites for Configuring Link Bundling on a Cisco CRS-1 router

Prerequisites for Configuring Link Bundling on a Cisco XR 12000 Series Router

Restrictions for Configuring Link Bundling on the Cisco XR 12000 Series Router

Restrictions for Configuring Link Bundling on the Cisco CRS-1 Router

Information About Configuring Link Bundling

Link Bundling Overview

Characteristics of Link Bundles

Characteristics of CRS-1 Series Router Link Bundles

Characteristics of Cisco XR 12000 Series Router Link Bundles

Link Aggregation Through LACP

IEEE 802.3ad standard

QoS and Link Bundling

VLANS on an Ethernet Link Bundle

Link Bundle Configuration Overview

Nonstop Forwarding During Card Failover

Link Failover

How to Configure Link Bundling

Configuring Ethernet Link Bundles

Configuring VLAN Bundles

Configuring POS Link Bundles

Configuration Examples for CRS-1 Series Link Bundling

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance


Configuring Link Bundling on Cisco IOS XR Software


A bundle is a group of one or more ports that are aggregated together and treated as a single link. The different links within a single bundle can have varying speeds, where the fastest link can be a maximum of four times greater than the slowest link. Each bundle has a single MAC, a single IP address, and a single configuration set (such as quality of service [QoS]).

The CRS-1 Series Router and the Cisco XR 12000 Series Router support link bundling for Ethernet interfaces. The CRS-1 Series Router also supports bundling for Packet-over-SONET/SDH (POS) interfaces.


Note Bundles do not have a one-to-one modular services card association.


Feature History for Configuring Link Bundling on Cisco IOS XR Software

Release
Modification

Release 3.2

This feature was introduced on the Cisco CRS-1 router.

Release 3.3.0

This feature was updated as follows:

To support the 1:N redundancy feature, users can configure the minimum number of active links using the bundle minimum-active links command.

To support the 1:N redundancy feature, users can configure the minimum bandwidth in kbps using the bundle minimum-active links command.

Support was added for VLAN subinterfaces on Ethernet link bundles.

Output for show bundle bundle-Ether command and show bundle bundle-POS command was modified.

The reasons keyword was added to the show bundle bundle-Ether command and the show bundle bundle-POS command.

The bundle id command was changed from bundle-id.

BFD over bundled VLANs using static routes.

Release 3.4.0

The configuration procedures in this module were modified with enhancements.

Release 3.5.0

No modification.

Release 3.6.0

This feature was first supported on the Cisco XR 12000 Series Router.


Contents

This module includes the following sections:

Prerequisites for Configuring Link Bundling

Restrictions for Configuring Link Bundling on the Cisco XR 12000 Series Router

Restrictions for Configuring Link Bundling on the Cisco CRS-1 Router

Information About Configuring Link Bundling

How to Configure Link Bundling

Configuration Examples for CRS-1 Series Link Bundling

Additional References

Prerequisites for Configuring Link Bundling

The prerequisites for Link Bundling depend on the platform on which you are configuring this feature. This section includes the following information:

Prerequisites for Configuring Link Bundling on a Cisco CRS-1 router

Prerequisites for Configuring Link Bundling on a Cisco XR 12000 Series Router

Prerequisites for Configuring Link Bundling on a Cisco CRS-1 router

Before configuring Link Bundling on a Cisco IOS XR Router, be sure that the following tasks and conditions are met:

To perform these configuration tasks, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. All command task IDs are listed in individual command references and in the Cisco IOS XR Task ID Reference Guide.

If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR Software System Security Configuration Guide.You know the interface IP address.

You know which links should be included in the bundle you are configuring.

If you are configuring an Ethernet link bundle, you have at least one of the following Ethernet cards installed in the router:

8-port 10-Gigabit Ethernet physical layer interface module (PLIM)

1-port 10-Gigabit Ethernet shared port adapter (SPA)

10-port Gigabit Ethernet SPA

8-port Gigabit Ethernet SPA

5-port Gigabit Ethernet SPA

If you are configuring a POS link bundle, you have a POS line card or SPA installed in a router that is running Cisco IOS XR software.


Note For more information about physical interfaces, PLIMs, and modular services cards, refer to the Cisco CRS-1 Carrier Routing System 8-Slot Line Card Chassis System Description.


Prerequisites for Configuring Link Bundling on a Cisco XR 12000 Series Router

Before configuring Link Bundling on a Cisco XR 12000 Series Router, be sure that the following tasks and conditions are met:

To perform these configuration tasks, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. All command task IDs are listed in individual command references and in the Cisco IOS XR Task ID Reference Guide.

If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR Software System Security Configuration Guide.

You know the interface IP address.

You know which links should be included in the bundle you are configuring.

You have at least one of the following SIPs installed in the router:

Cisco XR 12000 SIP-401

Cisco XR 12000 SIP-501

Cisco XR 12000 SIP-601

If you are configuring an Ethernet link bundle, you have at least one of the following Ethernet cards installed in the router:

1-port 10-Gigabit Ethernet SPA

10-port Gigabit Ethernet SPA

8-port Gigabit Ethernet SPA

5-port Gigabit Ethernet SPA

Restrictions for Configuring Link Bundling on the Cisco XR 12000 Series Router

The Cisco XR 12000 Series Router does not support the following features related to Link Bundling:

POS interfaces

E3 interfaces


Note Although the Cisco XR 12000 Series Router does not support an E3 interface as a member of a link bundle, traffic entering through an E3 interface can egress out of a Link Bundling interface.


1:1 link protection

Bidirectional forwarding detection (BFD)

QoS

Access control lists (ACLs)

QinQ encapsulation

MPLS traffic engineering (TE)

IPv6

Multicast VPNs

Restrictions for Configuring Link Bundling on the Cisco CRS-1 Router

The Cisco CRS-1 Router does not support the following features related to Link Bundling:

A mix of Ethernet and POS interfaces

More than 64 links to a bundle

More than 32 bundles

POS links configured with encapsulation type other than HDLC

Mixed bundles. All links within a single bundle must be configured to run either POS Channel or 802.3ad.

Information About Configuring Link Bundling

To implement Link Bundling, you must understand the following concepts:

Link Bundling Overview

Characteristics of Link Bundles

Link Aggregation Through LACP

QoS and Link Bundling

Link Bundle Configuration Overview

Nonstop Forwarding During Card Failover

Link Failover

Link Bundling Overview

A link bundle is simply a group of ports that are bundled together and act as a single link. The advantages of link bundles are as follows:

Multiple links can span several line cards and SPAs to form a single interface. Thus, the failure of a single link does not cause a loss of connectivity.

Bundled interfaces increase bandwidth availability, because traffic is forwarded over all available members of the bundle. Therefore, traffic can move onto another link if one of the links within a bundle fails. You can add or remove bandwidth without interrupting packet flow. For example, you can upgrade from an OC-48c PLIM modular services card to an OC-192 PLIM modular services card without interrupting traffic.

All links within a bundle must be of the same type. For example, a bundle can contain all Ethernet interfaces, or it can contain all POS interfaces, but it cannot contain Ethernet and POS interfaces at the same time.

Cisco IOS XR software supports the following methods of forming bundles of Ethernet and POS interfaces:

IEEE 802.3ad—Standard technology that employs a Link Aggregation Control Protocol (LACP) to ensure that all the member links in a bundle are compatible. Links that are incompatible or have failed are automatically removed from a bundle.

EtherChannel or POS Channel—Cisco proprietary technology that allows the user to configure links to join a bundle, but has no mechanisms to check whether the links in a bundle are compatible. EtherChannel applies to Ethernet interfaces, and POS Channel applies to POS interfaces.


Note Link bundling is supported on all multishelf Cisco CRS-1 routers.


Characteristics of Link Bundles

This section describes link bundle characteristics that are common to both Cisco CRS-1 routers and Cisco XR 12000 Series Routers. For additional characteristics that are specific to each platform, see Characteristics of CRS-1 Series Router Link Bundles and Characteristics of Cisco XR 12000 Series Router Link Bundles.

The following list describes the properties and limitations of link bundles:

A bundle should contain links, each of which has LACP enabled or disabled. If a bundle contains links, some that have LACP enabled and some that have LACP disabled, the links with LACP disabled are not aggregated in the bundle.

Bundle membership can span across several modular services cards that are installed in a single router and across SPAS in the same service card.

For Ethernet link bundles, all ports and interfaces added to the bundle should have the same speed and bandwidth.

Physical layer and link layer configuration are performed on individual member links of a bundle.

Configuration of network layer protocols and higher layer applications is performed on the bundle itself.

A bundle can be administratively enabled or disabled.

Each individual link within a bundle can be administratively enabled or disabled.

The MAC address that is set on the bundle becomes the MAC address of the links within that bundle.

If a MAC address is not set on the bundle, the bundle and bundle members inherit the address of the first member.

Each link within a bundle can be configured to allow different keepalive periods on different members.

Load balancing (the distribution of data between member links) is done by flow instead of by packet.

Upper layer protocols, such as routing updates and hellos, are sent over any member link of an interface bundle.

All links within a single bundle must terminate on the same two systems. Both systems must be directly connected.

Bundled interfaces are point to point.

A bundle can contain physical links only. Tunnels and VLAN subinterfaces cannot be bundle members. However, you can create VLANs as subinterfaces of bundles.

An IPv4 address configuration on link bundles is identical to an IPv4 address configuration on regular interfaces.

Multicast traffic is load balanced over the members of a bundle. For a given flow, internal processes select the member link, and all traffic for that flow is sent over that member.

Characteristics of CRS-1 Series Router Link Bundles

The following list describes additional properties and limitations of link bundles that are specific to CRS-1 Series:

Link Bundling is supported on all multishelf Cisco CRS-1 routers.

A bundle can contain all Ethernet interfaces or all POS interfaces, but not a mix of Ethernet and POS interfaces.

A single bundle supports a maximum of 32 physical links. If you add more than 32 links to a bundle, only 32 of the links function, and the remaining links are automatically disabled.

A CRS-1 Series router supports a maximum of 32 bundles.

Ethernet and POS link bundles are created in the same way as Ethernet channels and POS channels, where the user enters the same configuration on both end systems.

For POS link bundles, different link speeds are allowed within a single bundle, with a maximum of four times the speed difference between the members of the bundle.

HDLC is the only supported encapsulation type for POS link bundles in Cisco IOS XR software. POS links that are configured with any other encapsulation type cannot join a bundle. Keep in mind that all POS link bundle members must be running HDLC for HDLC to work on a bundle.

QoS is supported and is applied proportionally on each bundle member.

Link layer protocols, such as CDP and HDLC keepalives, work independently on each link within a bundle.

All links within a single bundle must be configured to run either POS Channel or 802.3ad. Mixed bundles are not supported.

Characteristics of Cisco XR 12000 Series Router Link Bundles

The following list describes additional properties and limitations of link bundles that are specific to Cisco XR 12000 Series Routers:

A single bundle supports a maximum of 8 physical links. If you add more than 8 links to a bundle, only 8 of the links function, and the remaining links are automatically disabled.

A Cisco XR 12000 Series Router supports a maximum of 16 bundles.

Ethernet link bundles are created in the same way as Ethernet channels, where the user enters the same configuration on both end systems.

Link Aggregation Through LACP

Aggregating interfaces on different modular services cards provides redundancy, allowing traffic to be quickly redirected to other member links when an interface or modular services card failure occurs.

The optional Link Aggregation Control Protocol (LACP) is defined in the IEEE 802 standard. LACP communicates between two directly connected systems (or peers) to verify the compatibility of bundle members. For the CRS-1 Series router, the peer can be either another router or a switch. LACP monitors the operational state of link bundles to ensure the following:

All links terminate on the same two systems

Both systems consider the links to be part of the same bundle

All links have the appropriate settings on the peer

LACP transmits frames containing the local port state and the local view of the partner system's state. These frames are analyzed to ensure both systems are in agreement.

IEEE 802.3ad standard

The IEEE 802.3ad standard typically defines a method of forming Ethernet link bundles. In
Cisco IOS XR software, the IEEE 802.3ad standard is used on both Ethernet and POS link bundles.

For each link configured as bundle member, the following information is exchanged between the systems that host each end of the link bundle:

A globally unique local system identifier

An identifier (operational key) for the bundle of which the link is a member

An identifier (port ID) for the link

The current aggregation status of the link

This information is used to form the link aggregation group identifier (LAG ID). Links that share a common LAG ID can be aggregated. Individual links have unique LAG IDs.

The system identifier distinguishes one router from another, and its uniqueness is guaranteed through the use of a MAC address from the system. The bundle and link identifiers have significance only to the router assigning them, which must guarantee that no two links have the same identifier, and that no two bundles have the same identifier.

The information from the peer system is combined with the information from the local system to determine the compatibility of the links configured to be members of a bundle.

The MAC address of the first link attached to a bundle becomes the MAC address of the bundle itself. The bundle uses this MAC address until that link (the first link attached to the bundle) is detached from the bundle, or until the user configures a different MAC address. The bundle MAC address is used by all member links when passing bundle traffic. Any unicast or multicast addresses set on the bundle are also set on all the member links.


Note We recommend that you avoid modifying the MAC address, because changes in the MAC address can affect packet forwarding.


QoS and Link Bundling

On the ingress direction, QoS is applied to the local instance of a bundle. Each bundle is associated with a set of queues. QoS is applied to the various network layer protocols that are configured on the bundle.

On the egress direction, QoS is applied on the bundle with a reference to the member links. QoS is applied based on the sum of the member bandwidths.

Link Bundling supports the following QoS features:

hi priority /lo priority—Maximum bandwidth is calculated as a percentage of the bundle interface bandwidth. This percentage is then applied to every member link on the egress, or to the local bundle instance on ingress.

guaranteed bandwidth—Provided in percentage and applied to every member link.

traffic shaping—Provided in percentage and applied to every member link.

WRED—Minimum and maximum parameters are converted to the right proportion per member link or bundle instance, and then are applied to the bundle.

marking—Process of changing the packet QoS level according to a policy.

tail drop— Packets are dropped when the queue is full.

VLANS on an Ethernet Link Bundle

802.1Q VLAN subinterfaces can be configured on 802.3ad Ethernet link bundles. Keep the following information in mind when adding VLANS on an Ethernet link bundle:

The maximum number of VLANs allowed per bundle is 128.

The maximum number of bundled VLANs allowed per router is 4000.


Note The memory requirement for bundle VLANs is slightly higher than standard physical interfaces.


To create a VLAN subinterface on a bundle, include the VLAN subinterface instance with the interface Bundle-Ether command, as follows:

interface Bundle-Ether instance.subinterface

After you create a VLAN on an Ethernet link bundle, all physical VLAN subinterface configuration is supported on that link bundle.

Link Bundle Configuration Overview

The following steps provide a general overview of the link bundle configuration process. Keep in mind that a link must be cleared of all previous network layer configuration before it can be added to a bundle:

1. In global configuration mode, create a link bundle. To create an Ethernet link bundle, enter the interface Bundle-Ether command. To create a POS link bundle, enter the interface Bundle-POS command.

2. Assign an IP address and subnet mask to the virtual interface using the ipv4 address command.

3. Add interfaces to the bundle you created in Step 1 with the bundle id command in the interface configuration submode. You can add up to 32 links to a single bundle.


Note A link is configured to be a member of a bundle from the interface configuration submode for that link.


Nonstop Forwarding During Card Failover

Cisco IOS XR software supports nonstop forwarding during failover between active and standby paired RP cards. Nonstop forwarding ensures that there is no change in the state of the link bundles when a failover occurs.

For example, if an active RP fails, the standby RP becomes operational. If a failover occurs on the active node, you must perform a restart on the redundant node to enable the failover. The configuration, node state, and checkpoint data of the failed RP are replicated to the standby RP. The bundled interfaces will all be present when the standby RP becomes the active RP.


Note Failover is always onto the standby RP. If there is no standby pair, the configuration manager restores the configuration to another RP, thereby recreating the bundles and other virtual interfaces.



Note You do not need to configure anything to guarantee that the standby interface configurations are maintained.


Link Failover

When one member link in a bundle fails, traffic is redirected to the remaining operational member links and traffic flow remains uninterrupted.

How to Configure Link Bundling

This section contains the following procedures:

Configuring Ethernet Link Bundles

Configuring VLAN Bundles

Configuring POS Link Bundles

Configuring Ethernet Link Bundles

This section describes how to configure a Ethernet link bundle.


Note MAC accounting is not supported on Ethernet link bundles.



Note In order for an Ethernet bundle to be active, you must perform the same configuration on both connection endpoints of the bundle.


SUMMARY STEPS

The creation of an Ethernet link bundle involves creating a bundle and adding member interfaces to that bundle, as shown in the steps that follow.

1. configure

2. interface Bundle-Ether bundle-id

3. ipv4 address ipv4-address mask

4. bundle minimum-active bandwidth kbps

5. bundle minimum-active links links

6. bundle maximum-active links links

7. exit

8. interface {GigabitEthernet | TenGigE} instance

9. bundle id bundle-id [mode {active | on | passive}

10. no shutdown

11. exit

12. Repeat Step 8 through Step 11 to add more links to the bundle you created in Step 2.

13. end
or
commit

14. exit

15. exit

16. Perform Step 1 through Step 15 on the remote end of the connection.

17. show bundle Bundle-Ether bundle-id [reasons]

18. show lacp bundle Bundle-Ether bundle-id

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2 

interface Bundle-Ether bundle-id

Example:

RP/0/RP0/CPU0:router#(config)# interface Bundle-Ether 3

Creates and names a new Ethernet link bundle.

This interface Bundle-Ether command enters you into the interface configuration submode, where you can enter interface specific configuration commands are entered. Use the exit command to exit from the interface configuration submode back to the normal global configuration mode.

Step 3 

ipv4 address ipv4-address mask

Example:

RP/0/RP0/CPU0:router(config-if)# ipv4 address 10.1.2.3 255.0.0.0

Assigns an IP address and subnet mask to the virtual interface using the ipv4 address configuration subcommand.

Step 4 

bundle minimum-active bandwidth kbps

Example:

RP/0/RP0/CPU0:router(config-if)# bundle minimum-active bandwidth 580000

Sets the minimum amount of bandwidth required before a user can bring up a bundle.

Step 5 

bundle minimum-active links links

Example:

RP/0/RP0/CPU0:router(config-if)# bundle minimum-active links 2

Sets the number of active links required before you can bring up a specific bundle.

Step 6 

bundle maximum-active links links

Example:

RP/0/RP0/CPU0:router(config-if)# bundle maximum-active links 1

(Optional) Limits the number of links that can be actively carrying traffic in a specific bundle.

Note The default number of active links allowed in a single bundle is 32.

Note If the bundle maximum-active command is issued, then only the highest-priority link within the bundle is active. The priority is based on the value from the bundle port-priority command, where a lower value is a higher priority. Therefore, we recommend that you configure a higher priority on the link that you want to be the active link.

Step 7 

exit
Example:

RP/0/RP0/CPU0:router(config-if)# exit

Exits interface configuration submode for the Ethernet link bundle.

Step 8 

interface {GigabitEthernet | TenGigE} instance

Example:

RP/0/RP0/CPU0:router(config)# interface GigabitEthernet 1/0/0/0

Enters the interface configuration mode for the specified interface.

Enter the GigabitEthernet or TenGigE keyword to specify the interface type. Replace the instance argument with the node-id in the rack/slot/module format.

Step 9 

bundle id bundle-id [mode {active | on | passive}]

Example:
RP/0/RP0/CPU0:router(config-if)# bundle-id 3

Adds the link to the specified bundle.

To enable active or passive LACP on the bundle, include the optional mode active or mode passive keywords in the command string.

To add the link to the bundle without LACP support, include the optional mode on keywords with the command string.

Note If you do not specify the mode keyword, the default mode is on (LACP is not run over the port).

Step 10 

no shutdown

Example:

RP/0/RP0/CPU0:router(config-if)# no shutdown

(Optional) If a link is in the down state, bring it up. The no shutdown command returns the link to an up or down state depending on the configuration and state of the link.

Step 11 

exit
Example:

RP/0/RP0/CPU0:router(config-if)# exit

Exits interface configuration submode for the Ethernet interface.

Step 12 

interface {GigabitEthernet | TenGigE} number

bundle id bundle-id [mode {active | passive | on}]

no shutdown

exit

Example:

RP/0/RP0/CPU0:router(config)# interface GigabitEthernet 1/0/2/1

RP/0/RP0/CPU0:router(config-if)# bundle id 3
 
        
RP/0/RP0/CPU0:router(config-if)# no shutdown
 
        
RP/0/RP0/CPU0:router(config-if)# exit
 
        
RP/0/RP0/CPU0:router(config)# interface 
GigabitEthernet 1/0/2/3
 
        
RP/0/RP0/CPU0:router(config-if)# bundle id 3
 
        
RP/0/RP0/CPU0:router(config-if)# no shutdown
 
        
RP/0/RP0/CPU0:router(config-if)# exit

(Optional) Repeat Step 8 through Step 11 to add more links to the bundle.

Step 13 

end

or

commit

Example:

RP/0/RP0/CPU0:router(config-if)# end

or

RP/0/RP0/CPU0:router(config-if)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them 
before exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Step 14 

exit
Example:

RP/0/RP0/CPU0:router(config-if)# exit

Exits interface configuration mode.

Step 15 

exit
Example:

RP/0/RP0/CPU0:router(config)# exit

Exits global configuration mode.

Step 16 

Perform Step 1 through Step 15 on the remote end of the connection.

Brings up the other end of the link bundle.

Step 17 

show bundle Bundle-Ether bundle-id [reasons]
Example:
RP/0/RP0/CPU0:router# show bundle Bundle-Ether 3 
reasons

(Optional) Shows information about the specified Ethernet link bundle.

Step 18 

show lacp bundle Bundle-Ether bundle-id 
Example:

RP/0/RP0/CPU0:router# show lacp bundle
Bundle-Ether 3

(Optional) Shows detailed information about LACP ports and their peers.

Configuring VLAN Bundles

This section describes how to configure a VLAN bundle. The creation of a VLAN bundle involves three main tasks:

1. Create an Ethernet bundle

2. Create VLAN subinterfaces and assign them to the Ethernet bundle.

3. Assign Ethernet links to the Ethernet bundle.

These tasks are describe in detail in the procedure that follows.


Note In order for a VLAN bundle to be active, you must perform the same configuration on both ends of the bundle connection.


SUMMARY STEPS

The creation of a VLAN link bundle is described in the steps that follow.

1. configure

2. interface Bundle-Ether bundle-id

3. ipv4 address ipv4-address mask

4. bundle minimum-active bandwidth kbps

5. bundle minimum-active links links

6. bundle maximum-active links links

7. exit

8. interface Bundle-Ether bundle-id.vlan-id

9. dot1q vlan vlan-id

10. ipv4 address ipv4-address mask

11. no shutdown

12. exit

13. Repeat Step 7 through Step 12 to add more VLANS to the bundle you created in Step 2.

14. end
or
commit

15. exit

16. exit

17. show vlan interface

18. configure

19. interface {GigabitEthernet | TenGigE} instance

20. bundle id bundle-id [mode {active | on | passive}

21. no shutdown

22. Repeat Step19 through Step 21 to add more Ethernet Interfaces to the bundle you created in Step 2.

23. end
or
commit

24. Perform Step 1 through Step 23 on the remote end of the connection.

25. show bundle Bundle-Ether bundle-id [reasons]

26. show vlan trunks [{GigabitEthernet | TenGigE | Bundle-Ether} instance] [brief | summary] [location node-id]

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2 

interface Bundle-Ether bundle-id

Example:

RP/0/RP0/CPU0:router#(config)# interface Bundle-Ether 3

Creates and names a new Ethernet link bundle.

This interface Bundle-Ether command enters you into the interface configuration submode, where you can enter interface-specific configuration commands. Use the exit command to exit from the interface configuration submode back to the normal global configuration mode.

Step 3 

ipv4 address ipv4-address mask

Example:

RP/0/RP0/CPU0:router(config-if)# ipv4 address 10.1.2.3 255.0.0.0

Assigns an IP address and subnet mask to the virtual interface using the ipv4 address configuration subcommand.

Step 4 

bundle minimum-active bandwidth kbps

Example:

RP/0/RP0/CPU0:router(config-if)# bundle minimum-active bandwidth 580000

Sets the minimum amount of bandwidth required before a user can bring up a bundle.

Step 5 

bundle minimum-active links links

Example:

RP/0/RP0/CPU0:router(config-if)# bundle minimum-active links 2

Sets the number of active links required before you can bring up a specific bundle.

Step 6 

bundle maximum-active links links

Example:

RP/0/RP0/CPU0:router(config-if)# bundle maximum-active links 1

(Optional) Limits the number of links that can be actively carrying traffic in a specific bundle.

Note The default number of active links allowed in a single bundle is 32.

Note If the bundle maximum-active command is issued, then only the highest-priority link within the bundle is active. The priority is based on the value from the bundle port-priority command, where a lower value is a higher priority. Therefore, we recommend that you configure a higher priority on the link that you want to be the active link.

Step 7 

exit
Example:

RP/0/RP0/CPU0:router(config-if)# exit

Exits the interface configuration submode.

Step 8 

interface Bundle-Ether bundle-id.vlan-id

Example:

RP/0/RP0/CPU0:router#(config)# interface Bundle-Ether 3.1

Creates a new VLAN, and assigns the VLAN to the Ethernet bundle you created in Step 2.

Replace the bundle-id argument with the bundle-id you created in Step 2.

Replace the vlan-id with a subinterface identifier. Range is from 1 to 4094 inclusive (0 and 4095 are reserved).

Note When you include the .vlan-id argument with the interface Bundle-Ether bundle-id command, you enter subinterface configuration mode.

Step 9 

dot1q vlan vlan-id

Example:

RP/0/RP0/CPU0:router#(config-subif)# dot1q vlan 10

Assigns a VLAN to the subinterface.

Replace the vlan-id argument with a subinterface identifier. Range is from 1 to 4094 inclusive (0 and 4095 are reserved).

Step 10 

ipv4 address ipv4-address mask

Example:

RP/0/RP0/CPU0:router#(config-subif)# ipv4 address 10.1.2.3/24

Assigns an IP address and subnet mask to the subinterface.

Step 11 

no shutdown

Example:

RP/0/RP0/CPU0:router#(config-subif)# no shutdown

(Optional) If a link is in the down state, bring it up. The no shutdown command returns the link to an up or down state depending on the configuration and state of the link.

Step 12 

exit
Example:

RP/0/RP0/CPU0:router(config-subif)# exit

Exits subinterface configuration mode for the VLAN subinterface.

Step 13 

interface Bundle-Ether bundle-id.vlan-id
dot1q vlan vlan-id
ipv4 address ipv4-address mask

no shutdown

exit

Example:

RP/0/RP0/CPU0:router(config-subif)# interface Bundle-Ether 3.1

RP/0/RP0/CPU0:router(config-subif)# dot1q vlan 20
RP/0/RP0/CPU0:router(config-subif)# ipv4 address   
20.2.3.4/24
RP/0/RP0/CPU0:router(config-subif)# no shutdown
exit

(Optional) Adds more subinterfaces to the bundle.

Step 14 

end

or

commit

Example:

RP/0/RP0/CPU0:router(config-subif)# end

or

RP/0/RP0/CPU0:router(config-subif)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them 
before exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Step 15 

exit
Example:

RP/0/RP0/CPU0:router(config-subif)# end

Exits interface configuration mode.

Step 16 

exit
Example:

RP/0/RP0/CPU0:router(config)# exit

Exits global configuration mode.

Step 17 

show vlan interface
Example:

RP/0/RP0/CPU0:router # show vlan interface

Displays the current VLAN interface and status configuration.

Step 18 

configure
Example:

RP/0/RP0/CPU0:router # configure

Enters global configuration mode.

Step 19 

interface {GigabitEthernet | TenGigE} instance

Example:

RP/0/RP0/CPU0:router(config)# interface GigabitEthernet 1/0/0/0

Enters the interface configuration mode for the Ethernet interface you want to add to the Bundle.

Enter the GigabitEthernet or TenGigE keyword to specify the interface type. Replace the instance argument with the node-id in the rack/slot/module format.

Note A VLAN bundle is not active until you add an Ethernet interface on both ends of the link bundle.

Step 20 

bundle id bundle-id [mode {active | on | passive}]

Example:
RP/0/RP0/CPU0:router(config-if)# bundle-id 3

Adds an Ethernet interface to the bundle you configured in Step 2 through Step 13.

To enable active or passive LACP on the bundle, include the optional mode active or mode passive keywords in the command string.

To add the interface to the bundle without LACP support, include the optional mode on keywords with the command string.

Note If you do not specify the mode keyword, the default mode is on (LACP is not run over the port).

Step 21 

no shutdown

Example:

RP/0/RP0/CPU0:router(config-if)# no shutdown

(Optional) If a link is in the down state, bring it up. The no shutdown command returns the link to an up or down state depending on the configuration and state of the link.

Step 22 

Repeat Step 19 through Step 21 to add more Ethernet interfaces to the VLAN bundle.

Step 23 

end

or

commit

Example:

RP/0/RP0/CPU0:router(config-subif)# end

or

RP/0/RP0/CPU0:router(config-subif)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them 
before exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Step 24 

Perform Step 1 through Step 23 on the remote end of the VLAN bundle connection.

Brings up the other end of the link bundle.

Step 25 

show bundle Bundle-Ether bundle-id [reasons]
Example:
RP/0/RP0/CPU0:router# show bundle Bundle-Ether 3 
reasons

(Optional) Shows information about the specified Ethernet link bundle.

The show bundle Bundle-Ether command displays information about the specified bundle. If your bundle has been configured properly and is carrying traffic, the State field in the show bundle Bundle-Ether command output will show the number "4," which means the specified VLAN bundle port is "distributing."

Step 26 

show vlan trunks [{GigabitEthernet | TenGigE | Bundle-Ether} instance] [brief | summary] [location node-id]

Example:

RP/0/RP0/CPU0:router# show vlan trunk summary

(Optional) Displays summary information about each of the VLAN trunk interfaces.

The keywords have the following meanings:

briefDisplays a brief summary.

summaryDisplays a full summary.

locationDisplays information about the VLAN trunk interface on the given slot.

interfaceDisplays information about the specified interface or subinterface.

Use the show vlan trunks command to verify that all configured VLAN subinterfaces on an Ethernet bundle are "up."

Configuring POS Link Bundles

This section describes how to configure a POS link bundle.


Note In order for a POS bundle to be active, you must perform the same configuration on both connection endpoints of the POS bundle.


SUMMARY STEPS

The creation of a bundled POS interface involves configuring both the bundle and the member interfaces, as shown in the following steps.

1. configure

2. interface Bundle-POS bundle-id

3. ipv4 address ipv4-address mask

4. bundle minimum-active bandwidth kbps

5. bundle minimum-active links links

6. bundle maximum-active links links

7. exit

8. interface POS number

9. bundle id bundle-id [mode {active | on | passive}

10. no shutdown

11. exit

12. Repeat Step 8 through Step 11 to add more links to the bundle you created in Step 2.

13. end
or
commit

14. exit

15. exit

16. Perform Step 1 through Step 15 on the remote end of the connection.

17. show bundle Bundle-POS bundle-id [reasons]

18. show lacp bundle Bundle-POS bundle-id

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2 

interface Bundle-POS bundle-id

Example:

RP/0/RP0/CPU0:router#(config)#interface Bundle-POS 2

Configures and names the new bundled POS interface.

This interface command will enter you into the interface configuration submode, from where interface specific configuration commands are entered. Use the exit command to exit from the interface configuration submode back to the normal global configuration mode.

Step 3 

ipv4 address ipv4-address mask
Example:

RP/0/RP0/CPU0:router(config-if)# ipv4 address 10.1.2.3 255.0.0.0

Assigns an IP address and subnet mask to the virtual interface using the ip address configuration subcommand.

Step 4 

bundle minimum-active bandwidth kbps

Example:

RP/0/RP0/CPU0:router(config-if)# bundle minimum-active bandwidth 620000

Sets the minimum amount of bandwidth required before a user can bring up a bundle.

Step 5 

bundle minimum-active links links

Example:

RP/0/RP0/CPU0:router(config-if)# bundle minimum-active links 2

(Optional) Sets the number of active links required before you can bring up a specific bundle.

Step 6 

bundle maximum-active links links

Example:

RP/0/RP0/CPU0:router(config-if)# bundle maximum-active links 1

(Optional) Limits the number of links that can be actively carrying traffic in a specific bundle.

Note The default number of active links allowed in a single bundle is 32.

Note If the bundle maximum-active command is issued, then only the highest-priority link within the bundle is active. The priority is based on the value from the port-priority command, where a lower value is a higher priority. Therefore, we recommend that you configure a higher priority on the link that you want to be the active link.

Step 7 

exit

Exits the interface configuration submode.

Step 8 

interface POS instance

Example:

RP/0/RP0/CPU0:router(config)# interface POS 0/1/0/0

Enters the POS interface configuration mode and specifies the POS interface name and instance notation rack/slot/module/port.

Step 9 

bundle id bundle-id [mode {active | passive | on}]

Example:
RP/0/RP0/CPU0:router(config-if)# bundle-id 3 

Adds the link to the specified bundle.

To enable active or passive LACP on the bundle, include the optional mode active or mode passive keywords in the command string.

To add the link to the bundle without LACP support, include the optional mode on keywords with the command string.

Note If you do not specify the mode keyword, the default mode is on (LACP is not run over the port).

Step 10 

no shutdown

Example:

RP/0/RP0/CPU0:router(config-if)# no shutdown

Removes the shutdown configuration which forces the interface administratively down. The no shutdown command then returns the link to an up or down state, depending on the configuration and state of the link.

Step 11 

exit
Example:

RP/0/RP0/CPU0:router# exit

Exits the interface configuration submode for the POS interface.

Step 12 

Repeat Step 8 through Step 11 to add more links to a bundle

(Optional) Adds more links to the bundle you created in Step 2.

Step 13 

end

or

commit

Example:

RP/0/RP0/CPU0:router(config-if)# end

or

RP/0/RP0/CPU0:router(config-if)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them 
before exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Step 14 

exit
Example:

RP/0/RP0/CPU0:router(config-if)# exit

Exits interface configuration mode.

Step 15 

exit
Example:

RP/0/RP0/CPU0:router(config)# exit

Exits global configuration mode.

Step 16 

Perform Step 1 through Step 15 on the remote end of the connection.

Brings up the other end of the link bundle.

Step 17 

show bundle Bundle-POS number [reasons]
Example:

RP/0/RP0/CPU0:router# show bundle Bundle-POS 1 reasons

(Optional) Shows information about the specified POS link bundle.

Step 18 

show lacp bundle Bundle-POS bundle-id 
Example:

RP/0/RP0/CPU0:router# show lacp bundle Bundle-POS 3

(Optional) Shows detailed information about LACP ports and their peers.

Configuration Examples for CRS-1 Series Link Bundling

The following example shows how to join two ports to form an EtherChannel bundle running LACP:

RP/0/RP0/CPU0:Router# config
RP/0/RP0/CPU0:Router(config)# interface Bundle-Ether 3
RP/0/RP0/CPU0:Router(config-if)# ipv4 address 1.2.3.4/24
RP/0/RP0/CPU0:Router(config-if)# bundle minimum-active bandwidth 620000
RP/0/RP0/CPU0:Router(config-if)# bundle minimum-active links 1
RP/0/RP0/CPU0:Router(config-if)# exit
RP/0/RP0/CPU0:Router(config)# interface TenGigE 0/3/0/0
RP/0/RP0/CPU0:Router(config-if)# bundle id 3 mode active
RP/0/RP0/CPU0:Router(config-if)# no shutdown
RP/0/RP0/CPU0:Router(config)# exit
RP/0/RP0/CPU0:Router(config)# interface TenGigE 0/3/0/1
RP/0/RP0/CPU0:Router(config-if)# bundle id 3 mode active
RP/0/RP0/CPU0:Router(config-if)# no shutdown
RP/0/RP0/CPU0:Router(config-if)# exit
 
   

The following example shows how to create and bring up two VLANS on an Ethernet bundle:

RP/0/RP0/CPU0:Router# config
RP/0/RP0/CPU0:Router(config)# interface Bundle-Ether 1
RP/0/RP0/CPU0:Router(config-if)# ipv4 address 1.2.3.4/24
RP/0/RP0/CPU0:Router(config-if)# bundle minimum-active bandwidth 620000
RP/0/RP0/CPU0:Router(config-if)# bundle minimum-active links 1
RP/0/RP0/CPU0:Router(config-if)# exit
RP/0/RP0/CPU0:Router(config)# interface Bundle-Ether 1.1
RP/0/RP0/CPU0:Router(config-subif)# dot1q vlan 10
RP/0/RP0/CPU0:Router(config-subif)# ip addr 10.2.3.4/24
RP/0/RP0/CPU0:Router(config-subif)# no shutdown
RP/0/RP0/CPU0:Router(config-subif)# exit
RP/0/RP0/CPU0:Router(config)# interface Bundle-Ether 1.2
RP/0/RP0/CPU0:Router(config-subif)# dot1q vlan 20
RP/0/RP0/CPU0:Router(config-subif)# ip addr 20.2.3.4/24
RP/0/RP0/CPU0:Router(config-subif)# no shutdown
RP/0/RP0/CPU0:Router(config-subif)# exit
RP/0/RP0/CPU0:Router(config)#interface gig 0/1/5/7
RP/0/RP0/CPU0:Router(config-if)# bundle-id 1 mode act
RP/0/RP0/CPU0:Router(config-if)# commit
RP/0/RP0/CPU0:Router(config-if)# exit
RP/0/RP0/CPU0:Router(config)# exit
RP/0/RP0/CPU0:Router # show vlan trunks

The following example shows how to join two ports to form an POS link bundle:

Router# config
Router(config)# interface Bundle-POS 5
Router(config-if)# ipv4 address 1.2.3.4/24
Router(config-if)# bundle minimum-active bandwidth 620000
Router(config-if)# bundle minimum-active bandwidth 620000
Router(config-if)# exit
Router(config)# interface POS 0/0/1/0
Router(config-if)# bundle id 5 
Router(config-if)# no shutdown
Router(config-if)# exit
Router(config)# interface POS 0/0/1/1
Router(config-if)# bundle id 5 
Router(config-if)# no shutdown
Router(config-if)# exit

Additional References

The following sections provide references related to link bundle configuration.

Related Documents

Related Topic
Document Title

Cisco IOS XR master command reference

Cisco IOS XR Master Commands List

Cisco IOS XR interface configuration commands

Cisco IOS XR Interface and Hardware Component Command Reference

Initial system bootup and configuration information for a router using the Cisco IOS XR Software.

Cisco IOS XR Getting Started Guide

Information about user groups and task IDs

Cisco IOS XR Interface and Hardware Component Command Reference

Information about configuring interfaces and other components on the Cisco CRS-1 from a remote Craft Works Interface (CWI) client management application

Cisco CRS-1 Series Carrier Routing System Craft Works Interface Configuration Guide


Standards

Standards
Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.


MIBs

MIBs
MIBs Link

There are no applicable MIBs for this module.

To locate and download MIBs for selected platforms using
Cisco IOS XR Software, use the Cisco MIB Locator found at the following URL:

http://cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml


RFCs

RFCs
Title

No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.


Technical Assistance

Description
Link

The Cisco Technical Support website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.

http://www.cisco.com/techsupport