- Preface
- New and Changed Information in Release 4.3.x
- Preconfiguring Physical Interfaces on Cisco IOS XR Software
- Configuring ATM Interfaces on Cisco IOS XR Software
- Advanced Configuration and Modification of the Management Ethernet Interface on Cisco IOS XR Software
- Configuring Ethernet Interfaces on Cisco IOS XR Software
- Configuring Ethernet OAM on Cisco IOS XR Software
- Configuring Link Bundling on Cisco IOS XR Software
- Configuring Virtual Loopback and Null Interfaces on Cisco IOS XR Software
- Configuring Channelized SONET/SDH on Cisco IOS XR Software
- Configuring Circuit Emulation over Packet on Cisco IOS XR Software
- Configuring Clear Channel SONET Controllers on Cisco IOS XR Software
- Configuring Clear Channel T3/E3 and Channelized T3 and T1/E1 Controllers on Cisco IOS XR Software
- Configuring POS Interfaces on Cisco IOS XR Software
- Configuring Serial Interfaces on Cisco IOS XR Software
- Configuring Frame Relay on Cisco IOS XR Software
- Configuring PPP on Cisco IOS XR Software
- Configuring 802.1Q VLAN Interfaces on Cisco IOS XR Software
- Configuring Tunnel Interfaces on Cisco IOS XR Software
- Index
- Link Bundling Overview
- Features and Compatible Characteristics of Link Bundles
- Link Aggregation Through LACP
- LACP Short Period Time Intervals
- Load Balancing
- Unequal Bandwidth on Link Bundles
- QoS and Link Bundling
- MPLS-TE and FRR over Link Bundles
- VLANs on an Ethernet Link Bundle
- Link Bundle Configuration Overview
- Nonstop Forwarding During RP Switchover
- Link Switchover
Configuring Link Bundling on Cisco IOS XR Software
This module describes the configuration of link bundle interfaces on the Cisco XR 12000 Series Router.
A link bundle is a group of one or more ports that are aggregated together and treated as a single link.
Each bundle has a single MAC, a single IP address, and a single configuration set, such as Quality of Service (QoS).
Note 
Link bundles do not have a one-to-one modular services card association. Member links can terminate on different cards.
Feature History for Configuring Link Bundling
Contents
This module includes the following sections:
•Prerequisites for Configuring Link Bundling
•Information About Configuring Link Bundling
•How to Configure Link Bundling
•Configuration Examples for Link Bundling
Prerequisites for Configuring Link Bundling
You must be in a user group associated with a task group that includes the proper task IDs. The command reference guides include the task IDs required for each command. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 XR 12000 Series Router
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:
•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
•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
–4-port ISE Gigabit Ethernet Line Card
–4-port OC-3 POS/SDH SPA
–8-port OC-3 POS/SDH SPA
–2-port OC-12 POS/SDH SPA
–4-port OC-12 POS/SDH SPA
–8-port OC-12 POS/SDH SPA
–4-port OC-3 POS ISE Line Card
–8-port OC-3 POS ISE Line Card
–12-port OC-3 POS ISE Line Card
–16-port OC-3 POS ISE Line Card
–1-port OC-48 POS ISE Line Card
–4 port OC-12 POS ISE Line Card
Restrictions
After a system upgrade or reload, current link bundling design prevents a bundled interface from remaining in the up state if there are errors encountered on features, such as QOS, configured under it. This behavior applies to bundled interfaces only. Physical interfaces are not effected.
Media Access Control (MAC) Accounting is not supported on Ethernet link bundles.
Features Supported
On the Cisco XR 12000 Series Router, link bundling supports the following features:
•802.3ad LACP support
•Access Control Lists (ACLs)
•IPv4 unicast and multicast forwarding
•IPv6 unicast and multicast forwarding
•SNF, Routing protocols support over LB interface
•L2TPv3 with core-facing link bundles
•MPLS
•MPLS forwarding
•MPLS traffic engineering (TE)
•MPLS TE for Fast Re-route (FRR)
•mMVPN4 for both core- and edge-facing bundles
•PIM IPv6
•QoS on Link Bundles
•6PE with link bundles on the edge (with MPLS core)
•Unequal bandwidth
•uRPF
•VPLS with core-facing link bundles (Ethernet and POS SPAs only as supported by the Cisco XR 12000 SIP-600, SIP-401, SIP-501 and SIP-601)
•VPLS with link bundles as core (Ethernet and POS SPAs only as supported by the Cisco XR 12000 SIP-600, SIP-401, SIP-501 and SIP-601)
Features Not Supported
On the Cisco XR 12000 Series Router, link bundling does not support the following features:
•QinQ encapsulation
•Multicast VPNs
•1:1 link protection
•Channelized POS interfaces
•X-Blade with link-bundle interfaces in the core
•Interfaces on the 4-port ISE Gigabit Ethernet line card.
Link bundling is not supported on the 4-port ISE Gigabit Ethernet line card. No interfaces on this card can be members of a link bundle. However, traffic entering through interfaces on this card can be sent out through link bundle interfaces.
•All member links must be configured to run at the same speed. If members of a bundle are configured at different speeds, only members that run at the speed of the highest priority link will be active links in that bundle.
•The maximum number of link bundling interfaces allowed on a line card is 16:
–16 Ethernet bundles
–16 Packet-over-SONET (POS) bundles
•The maximum number of VLAN link bundle interfaces allowed on a line card is 100.
•The maximum number of members allowed in a link bundle is 8. Users can configure more than 8 members, but the additional links are created in the detached state and become active only when currently active members are detached from the bundle.
•You cannot configure Virtual Firewall (VFW) on a link bundle interface. Traffic from VFW cannot egress through a link bundle interface.
•A link bundle with LACP enabled will flap during Minimum Disruption Restart (MDR).
•For Packet-over-SONET (POS) link bundles, only HDLC encapsulation is supported. No other encapsulations are supported.
Information About Configuring Link Bundling
To configure link bundling, you must understand the following concepts:
•Features and Compatible Characteristics of Link Bundles
•Link Aggregation Through LACP
•LACP Short Period Time Intervals
•Unequal Bandwidth on Link Bundles
•MPLS-TE and FRR over Link Bundles
•Link Bundle Configuration Overview
•Nonstop Forwarding During RP Switchover
Link Bundling Overview
The Link Bundling feature allows you to group multiple point-to-point links together into one logical link and provide higher bidirectional bandwidth, redundancy, and load balancing between two routers. A virtual interface is assigned to the bundled link. The component links can be dynamically added and deleted from the virtual interface.
The virtual interface is treated as a single interface on which one can configure an IP address and other software features used by the link bundle. Packets sent to the link bundle are forwarded to one of the links in the bundle.
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.)
The following types of link bundling are supported on Cisco XR 12000 Series Routers:
•EtherChannel is used bundle multiple Gigabit Ethernet (GE) interfaces.
•Gigabit EtherChannel link bundles are at Layer 2 and use one MAC address and one IP address for all GigabitEthernet interfaces in the bundle.
•POS Channel is used to bundle multiple Packet-over-SONET (POS) interfaces.
On Cisco XR 12000 Series Routers, Gigabit EtherChannel and POS Channel link bundling provide the following benefits:
•Flexible, incremental bandwidth
•Transparency to network applications
•Support for IP unicast and MPLS traffic
•Load balancing (equal cost) across all active links on the bundle
•Redundancy: if there is a failure of an individual GE or POS link, the traffic flow through the channel is evenly distributed across the available links.
•Interoperability with link bundling implementations in other Cisco and OEM routers and switches.
•Out-of-service support: a Gigabit EtherChannel or POS Channel is brought down if the minimum number of Gigabit Ethernet or POS links are not up.
•Bandwidth propagation support: bandwidth changes in a Gigabit EtherChannel or POS Channel can be (optionally) propagated to the upper-layer protocols until the amount of bandwidth required in the link bundle exceeds a specified threshold.
Features and Compatible Characteristics of Link Bundles
Link bundles support the following features:
•ACL
•Basic IP
•Basic MPLS
•MPLS VPN
•Sampled Netflow
•BGP Policy Accounting
•HSRP/VRRP
•VLAN Bundling (Ethernet only)
•Basic IP
•Basic MPLS
•MPLS VPN
•Inter-AS
•WRED/MDRR per member interface.
The following list describes the properties and limitations of link bundles:
•A bundle contains 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.
•The Cisco XR 12000 Series Router supports a maximum of 16 bundles: 16 Etherbundles or 16 POS bundles.
•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.
•IPv4 and IPv6 addressing is supported on ethernet link bundles.
•A bundle can be administratively enabled or disabled. Beginning in Cisco IOS XR Release 3.8.4, when you shut down a bundle interface, the member links are put into err-disable link interface status and admin-down line protocol state. You can show the status of a bundle interface and its members using the show interfaces command.
•Each individual link within a bundle can be administratively enabled or disabled.
•Each individual member link within a bundle has unique MAC address.
•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 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 and on SPAs within the same 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. 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.
LACP Short Period Time Intervals
As packets are exchanged across member links of a bundled interface, some member links may slow down or time-out and fail. LACP packets are exchanged periodically across these links to verify the stability and reliability of the links over which they pass. The configuration of short period time intervals, in which LACP packets are sent, enables faster detection and recovery from link failures.
Note On the Cisco XR 12000 Series Router, only the default short period (1000 milliseconds) is supported.
Short period time intervals are configured as follows:
•In milliseconds
•In increments of 100 milliseconds
•In the range 100 to 1000 milliseconds
•The default is 1000 milliseconds (1 second)
•Up to 64 member links
•Up to 1280 packets per second (pps)
After 6 missed packets, the link is detached from the bundle.
When the short period time interval is not configured, LACP packets are transmitted over a member link every 30 seconds by default.
When the short period time interval is configured, LACP packets are transmitted over a member link once every 1000 milliseconds (1 second) by default. Optionally, both the transmit and receive intervals can be configured to less than 1000 milliseconds, independently or together, in increments of 100 milliseconds (100, 200, 300, and so on).
When you configure a custom LACP short period transmit interval at one end of a link, you must configure the same time period for the receive interval at the other end of the link.
Note You must always configure the transmit interval at both ends of the connection before you configure the receive interval at either end of the connection. Failure to configure the transmit interval at both ends first results in route flapping (a route going up and down continuously). When you remove a custom LACP short period, you must do it in reverse order. You must remove the receive intervals first and then the transmit intervals.
Load Balancing
Load balancing is a forwarding mechanism which distributes traffic over multiple links, based on Layer 3 routing information in the router. Per-flow load balancing is supported on all links in the bundle. This scheme achieves load sharing by allowing the router to distribute packets over one of the links in the bundle, that is determined through a hash calculation. The hash calculation is an algorithm for link selection based on certain parameters.
The standard hash calculation is a 3-tuple hashing, using the following parameters:
•IP source address
•IP destination address
•Router ID
7-tuple hashing can also be configured. based on Layer 3 and Layer 4 parameters:
•IP source address
•IP destination address
•Router ID
•Input interface
•IP protocol
•Layer 4 source port
•Layer 4 destination port
When per-flow load balancing and 3-tuple hashing is enabled, all packets for a certain source-destination pair will go through the same link, though there are multiple links available. Per-flow load balancing ensures that packets for a certain source-destination pair arrive in order.
Note For multicast traffic, ingress forwarding is based on the Fabric Multicast Group Identifier (FGID). Egress forwarding over the bundle is based on the bundle load balancing.
Unequal Bandwidth on Link Bundles
In Cisco IOS XR Releases prior to 4.1, all of the interfaces in a link bundle are required to have the same bandwidth characteristic. For example, an OC-3 POS link could be part of a bundle which has other OC-3 links, but it could not be part of a bundle with either OC-12 or OC-48 links.
Unequal bandwidth on link bundles allows links with different bandwidth characteristics to be part of the same bundle. This feature allows a 4:1 ratio in bandwidth characteristic of participating links in the same bundle, which means the following combination of links are supported:
•Bundles with OC-3 and OC-12 links
•Bundles with OC-12 and OC-48 links
The following combination of links are unsupported:
•Bundles with OC-3 and OC-48 links
•Bundles with Gigabit links and 10 Gigabit links
•Bundle with Gigabit and POS links
QoS and Link Bundling
On the Cisco XR 12000 Series Router, QoS features currently supported on Ethernet and Packet-over-SONET (POS) interfaces are also supported on link bundle interfaces.
For complete information on configuring QoS and important restrictions for link bundles, refer to the Cisco XR 12000 Series Router Modular Quality of Service Configuration Guide and the Cisco XR 12000 Series Router Modular Quality of Service Command Reference.
MPLS-TE and FRR over Link Bundles
Beginning with Cisco IOS XR Release 3.9.0, MPLS Traffic Engineering (TE) tunnels and Fast Re-Route (FRR) are supported on Link Bundle interfaces.
MPLS-TE and FRR are supported on the following types of Link Bundle interfaces:
•Packet-over-SONET (POS)
•Ethernet
MPLS-TE is supported, but FRR is not supported on the following types of Link Bundle interfaces:
•VLANs
The following example shows the configuration for FRR:
config
mpls traffic-eng
interface Bundle-Ether1
backup-path tunnel-te 2
!
For complete information on MPLS-TE and FRR, refer to the Cisco XR 12000 Series Router MPLS Configuration Guide and theCisco XR 12000 Series Router MPLS Command Reference.
Restrictions
The following restrictions apply to MPLS-TE and FRR over Link Bundles in Cisco IOS XR Release 3.9.0:
•The maximum number of links for MPLS-TE and FRR is 100.
•Backup assignments are void if both the primary assignment and the backup assignment are over the same physical Link Bundle interface.
•Packet loss greater than 50ms can happen if a single member link goes down, but the number of currently active members is still above the configured threshold.
•BFD is not supported on bundle interfaces.
MPLS-TE
MPLS-TE software enables an MPLS backbone to replicate and expand the traffic engineering capabilities of Layer 2 ATM and Frame Relay networks. MPLS is an integration of Layer 2 and Layer 3 technologies. By making traditional Layer 2 features available to Layer 3, MPLS enables traffic engineering (TE). With MPLS, TE capabilities are integrated into Layer 3, which optimizes the routing of IP traffic, given the constraints imposed by backbone capacity and topology.
FRR
Fast ReRoute (FRR) is used by MPLS-TE. FRR guarantees that if a TE tunnel fails, traffic is switched to a backup tunnel. FRR provides link protection to LSPs by rerouting traffic carried by LSPs to other links. The ability to configure FRR on a per-LSP basis makes it possible to provide different levels of FRR to tunnels with different bandwidths.
FRR is triggered on Link Bundles in the following ways:
•When the minimum links threshold is reached, FRR is triggered over a Link Bundle interface.
•When the minimum available bandwidth threshold is reached, FRR is triggered over a Link Bundle interface.
CLI
No new CLI commands are introduced in Cisco IOS XR Release 3.9.0.
See Example: Configuring MPLS-TE and FRR over Link Bundles for examples of how to configure MPLS-TE and FRR on Link Bundles.
To verify MPLS-TE and FRR over Link Bundles, use any of the following MPLS commands that are documented in the Cisco XR 12000 Series Router MPLS Command Reference:
•show [l cef [ipv4 | mpls] adjacency tunnel-te hardware [ingress | egress] location
•show int tunnel-te * accounting
•sshowh mpls traffic-eng fast-reroute database
•show mpls traffic-eng tunnels 1
•show mpls forwarding
•show cef ipv4 adjacency hardware egress location
•show cef ipv4 adjacency bundle-ether 22 hardware egress location
•show cef ipv4 address hardware ingress location
•show cef ipv4 address hardware egress location
•show cef ipv4 address hardware ingress location
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 100.
•The maximum number of bundled VLANs allowed per router is 1600.
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 interface-bundle-id.subinterface
After you create a VLAN on an Ethernet link bundle, all VLAN subinterface configuration is supported on that link bundle.
VLAN subinterfaces can support multiple Layer 2 frame types and services, such as Ethernet Flow Points - EFPs) and Layer 3 services.
Link Bundle Configuration Overview
The following steps provide a general overview of the link bundle configuration. 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 as a member of a bundle from the interface configuration submode for that link.
Nonstop Forwarding During RP Switchover
Cisco IOS XR software supports nonstop forwarding during switchover between active and standby paired RP cards. Nonstop forwarding ensures that there is no change in the state of the link bundles when a switchover occurs.
For example, if an active RP fails, the standby RP becomes operational. 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 You do not need to configure anything to guarantee that the standby interface configurations are maintained.
Link Switchover
By default, a maximum of 8 links can actively carry traffic on a Cisco XR 12000 Series Router. If one member link in a bundle fails, traffic is redirected to the remaining operational member links.
If the active and standby links are running LACP, you can choose between an IEEE standard-based switchover (the default) or a faster proprietary optimized switchover. If the active and standby links are not running LACP, the proprietary optimized switchover option is used.
Regardless of the type of switchover you are using, you can disable the wait-while timer, which expedites the state negotiations of the standby link and causes a faster switchover from a failed active link to the standby link.
How to Configure Link Bundling
This section contains the following procedures:
•Configuring Ethernet Link Bundles
•Configuring EFP Load Balancing on an Ethernet Link Bundle
•Configuring the Default LACP Short Period Time Interval
•Configuring Custom LACP Short Period Time Intervals
Configuring Ethernet Link Bundles
This section describes how to configure an 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 [hot-standby]
7. lacp fast-switchover
8. exit
9. interface {GigabitEthernet | TenGigE} interface-path-id
10. bundle id bundle-id [mode {active | on | passive}
11. bundle port-priority priority
12. no shutdown
13. exit
14. Repeat Step 8 through Step 11 to add more links to the bundle you created in Step 2.
15. end
or
commit
16. exit
17. exit
18. Perform Step 1 through Step 15 on the remote end of the connection.
19. show bundle Bundle-Ether bundle-id
20. show lacp Bundle-Ether bundle-id
DETAILED STEPS
Configuring EFP Load Balancing on an Ethernet Link Bundle
This section describes how to configure Ethernet flow point (EFP) Load Balancing on an Ethernet link bundle.
By default, Ethernet flow point (EFP) load balancing is enabled. However, the user can choose to configure all egressing traffic on the fixed members of a bundle to flow through the same physical member link. This configuration is available only on an Ethernet Bundle subinterface with Layer 2 transport (l2transport) enabled.
Note If the active members of the bundle change, the traffic for the bundle may get mapped to a different physical link that has a hash value that matches the configured value.
SUMMARY STEPS
Perform the following steps to configure EFP Load Balancing on an Ethernet link bundle:
1. configure
2. interface Bundle-Ether bundle-id l2transport
3. bundle load-balance hash hash-value [auto]
4. end
or
commit
DETAILED STEPS
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.
Restrictions
The Cisco XR 12000 Series Router does not currently support 1:1 link protection. Therefore, the bundle maximum-active links and lacp fast-switchover commands are not supported on the Cisco XR 12000 Series Router.
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 [hot-standby]
7. lacp fast-switchover
8. exit
9. interface Bundle-Ether bundle-id.vlan-id
10. dot1q vlan vlan-id
11. ipv4 address ipv4-address mask
12. no shutdown
13. exit
14. Repeat Step 9 through Step 12 to add more VLANS to the bundle you created in Step 2.
15. end
or
commit
16. exit
17. exit
18. configure
19. interface {GigabitEthernet | TenGigE} interface-path-id
20. bundle id bundle-id [mode {active | on | passive}
21. bundle port-priority priority
22. no shutdown
23. Repeat Step19 through Step 21 to add more Ethernet Interfaces to the bundle you created in Step 2.
24. end
or
commit
25. Perform Step 1 through Step 23 on the remote end of the connection.
26. show bundle Bundle-Ether bundle-id
27. show vlan interface
28. show vlan trunks [{GigabitEthernet | TenGigE | Bundle-Ether} interface-path-id] [brief | summary] [location node-id]
DETAILED STEPS
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 these 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 [hot-standby]
7. lacp fast-switchover
8. exit
9. interface POS interface-path-id
10. bundle id bundle-id [mode {active | on | passive}]
11. bundle port-priority priority
12. no shutdown
13. exit
14. Repeat Step 8 through Step 11 to add more links to the bundle you created in Step 2.
15. end
or
commit
16. exit
17. exit
18. Perform Step 1 through Step 15 on the remote end of the connection.
19. show bundle Bundle-POS bundle-id
20. show lacp bundle bundle-POS bundle-id
DETAILED STEPS
Configuring the Default LACP Short Period Time Interval
This section describes how to configure the default short period time interval for sending and receiving LACP packets on a Gigabit Ethernet interface. This procedure also enables the LACP short period.
SUMMARY STEPS
To enable an LACP short period time interval, using the default time of 1 second, perform the following steps.
1. configure
2. interface GigabitEthernet interface-path
3. bundle id number mode active
4. lacp period short
5. commit
DETAILED STEPS
Configuring Custom LACP Short Period Time Intervals
This section describes how to configure custom short period time intervals (less than 1000 milliseconds) for sending and receiving LACP packets on a Gigabit Ethernet interface.
Note You must always configure the transmit interval at both ends of the connection before you configure the receive interval at either end of the connection. Failure to configure the transmit interval at both ends first results in route flapping (a route going up and down continuously). When you remove a custom LACP short period, you must do it in reverse order. You must remove the receive intervals first and then the transmit intervals.
SUMMARY STEPS
To configure custom receive and transmit intervals for LACP packets, perform the following steps.
Router A
1. configure
2. interface GigabitEthernet interface-path
3. bundle id number mode active
4. lacp period short
5. commit
Router B
6. configure
7. interface GigabitEthernet interface-path
8. bundle id number mode active
9. lacp period short
10. commit
Router A
11. configure
12. interface GigabitEthernet interface-path
13. lacp period short transmit interval
14. commit
Router B
15. configure
16. interface GigabitEthernet interface-path
17. lacp period short transmit interval
18. commit
Router A
19. configure
20. interface GigabitEthernet interface-path
21. lacp period short receive interval
22. commit
Router B
23. configure
24. interface GigabitEthernet interface-path
25. lacp period short receive interval
26. commit or end
DETAILED STEPS
Configuration Examples for Link Bundling
This section contains the following examples:
•Example: Configuring an Ethernet Link Bundle
•Example: Configuring a VLAN Link Bundle
•Example: Configuring a POS Link Bundle
•Example: Configuring EFP Load Balancing on an Ethernet Link Bundle
•Examples: Configuring LACP Short Periods
•Example: Configuring MPLS-TE and FRR over Link Bundles
Example: Configuring an Ethernet Link Bundle
The following example shows how to join two ports to form an EtherChannel bundle running LACP:
Note The Cisco XR 12000 Series Router does not currently support 1:1 link protection. Therefore, the bundle maximum-active links and lacp fast-switchover commands are not supported on the Cisco XR 12000 Series Router.
RP/0/RP0/CPU0:Router# config
RP/0/0/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/0/CPU0:Router(config-if)# bundle maximum-active links 1 hot-standby
RP/0/0/CPU0:Router(config-if)# lacp fast-switchover
RP/0/0/CPU0:Router(config-if)# exit
RP/0/0/CPU0:Router(config)# interface TenGigE 0/3/0/0
RP/0/0/CPU0:Router(config-if)# bundle id 3 mode active
RP/0/0/CPU0:Router(config-if)# bundle port-priority 1
RP/0/0/CPU0:Router(config-if)# no shutdown
RP/0/0/CPU0:Router(config)# exit
RP/0/0/CPU0:Router(config)# interface TenGigE 0/3/0/1
RP/0/0/CPU0:Router(config-if)# bundle id 3 mode active
RP/0/0/CPU0:Router(config-if)# bundle port-priority 2
RP/0/0/CPU0:Router(config-if)# no shutdown
RP/0/0/CPU0:Router(config-if)# exit
Example: Configuring a VLAN Link Bundle
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/0/CPU0:Router(config-subif)# dot1q vlan 10
RP/0/0/CPU0:Router(config-subif)# ip addr 10.2.3.4/24
RP/0/0/CPU0:Router(config-subif)# no shutdown
RP/0/0/CPU0:Router(config-subif)# exit
RP/0/0/CPU0:Router(config)# interface Bundle-Ether 1.2
RP/0/0/CPU0:Router(config-subif)# dot1q vlan 20
RP/0/RP0/CPU0:Router(config-subif)# ip addr 20.2.3.4/24
RP/0/0/CPU0:Router(config-subif)# no shutdown
RP/0/0/CPU0:Router(config-subif)# exit
RP/0/0/CPU0:Router(config)#interface gig 0/1/5/7
RP/0/0/CPU0:Router(config-if)# bundle-id 1 mode act
RP/0/0/CPU0:Router(config-if)# commit
RP/0/0/CPU0:Router(config-if)# exit
RP/0/0/CPU0:Router(config)# exit
RP/0/0/CPU0:Router # show vlan trunks
Example: Configuring a POS Link Bundle
The following example shows how to join two ports to form a Packet-over-SONET (POS) link bundle:
RP/0/0/CPU0:Router# config
RP/0/0/CPU0:Router(config)# interface Bundle-POS 5
RP/0/0/CPU0:Router(config-if)# ipv4 address 1.2.3.4/24
RP/0/0/CPU0:Router(config-if)# bundle minimum-active bandwidth 620000
RP/0/0/CPU0:Router(config-if)# bundle minimum-active bandwidth 620000
RP/0/0/CPU0:Router(config-if)# exit
RP/0/0/CPU0:Router(config)# interface POS 0/0/1/1
RP/0/0/CPU0:Router(config-if)# bundle id 5
RP/0/0/CPU0:Router(config-if)# no shutdown
RP/0/0/CPU0:Router(config-if)# exit
Example: Configuring EFP Load Balancing on an Ethernet Link Bundle
The following example shows how to configure all egressing traffic on the fixed members of a bundle to flow through the same physical member link automatically.
RP/0/RP0/CPU0:router# configuration terminal
RP/0/RP0/CPU0:router(config)# interface bundle-ether 1.1 l2transport
RP/0/RP0/CPU0:router(config-subif)# bundle load-balancing hash auto
RP/0/RP0/CPU0:router(config-subif)#
The following example shows how to configure all egressing traffic on the fixed members of a bundle to flow through a specified physical member link.
RP/0/RP0/CPU0:router# configuration terminal
RP/0/RP0/CPU0:router(config)# interface bundle-ether 1.1 l2transport
RP/0/RP0/CPU0:router(config-subif)# bundle load-balancing hash 1
RP/0/RP0/CPU0:router(config-subif)#
Examples: Configuring LACP Short Periods
The following example shows how to configure the LACP short period time interval to the default time of 1000 milliseconds (1 second):
config
interface gigabitethernet 0/0/0/1
bundle id 1 mode active
lacp period short
commit
The following example shows how to configure custom LACP short period transmit and receive intervals to less than the default of 1000 milliseconds (1 second):
Router A
config
interface gigabitethernet 0/0/0/1
bundle id 1 mode active
lacp period short
commit
Router B
config
interface gigabitethernet 0/0/0/1
bundle id 1 mode active
lacp period short
commit
Router A
config
interface gigabitethernet 0/0/0/1
lacp period short transmit 100
commit
Router B
config
interface gigabitethernet 0/0/0/1
lacp period short transmit 100
commit
Router A
config
interface gigabitethernet 0/0/0/1
lacp period short receive 100
commit
Router B
config
interface gigabitethernet 0/0/0/1
lacp period short receive 100
commit
Example: Configuring MPLS-TE and FRR over Link Bundles
The following example shows how to configure MPLS-TE and FRR on a TE1 tunnel:
config
interface tunnel-te1
ipv4 unnumbered Loopback0
autoroute announce
destination 10.10.10.10
! For PBTS: All traffic which has exp set to 2, will take this tunnel.
policy-class 2
! For FRR
fast-reroute
record-route
path-option 1 explicit name PRIMARY
!
The following example shows how to configure MPLS-TE and FRR on an Ether bundle:
config
interface Bundle-Ether2
mtu 1500
ipv4 address 11.1.1.1 255.255.255.0
bundle minimum-active links 2
bundle minimum-active bandwidth 2000000
!
interface GigabitEthernet0/3/0/2
bundle id 2 mode active
!
interface GigabitEthernet0/3/0/3
bundle id 2 mode active
!
Note To trigger FRR using the minimum link threshold, use the bundle minimum-active links command and the bundle minimum-active bandwidth command in interface submode.
The following example shows how to configure a backup tunnel configuration on PLR:
config
interface tunnel-te2
! backup tunnel configuration on PLR
ipv4 unnumbered Loopback0
autoroute announce
destination 31.0.0.1
!
mpls traffic-eng
interface Bundle-Ether1 <=Protected interface.
backup-path tunnel-te 2 <= Backup tunnel
!
Additional References
These sections provide references related to link bundle configuration.
Related Documents
Standards
|
|
|
|---|---|
IEEE 802.3ad (incorporated as Annex 43 into 802.3-2002) |
— |
MIBs
RFCs
|
|
|
|---|---|
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature. |
— |
RFC 3812 |
— |
Feedback