Link Bundling Commands on Cisco IOS XR Software
This module contains commands for configuring and monitoring Link Bundling on Cisco IOS XR software.
Note The Cisco XR 12000 Series Router currently does not support Packet-over-SONET/SDH (POS) interfaces. Therefore, the Cisco XR 12000 Series Router does not support the POS-related commands, keywords, and arguments presented in this chapter.
bundle-hash
To calculate load balancing across members of a link bundle, use the bundle-hash command in EXEC mode.
Cisco CRS-1
bundle-hash {Bundle-Ether bundle-id | Bundle-POS bundle-id | members {GigabitEthernet interface-path-id... | TenGigE interface-path-id... | POS interface-path-id...}}
Cisco XR 12000 Series
bundle-hash {Bundle-Ether bundle-id | members {GigabitEthernet interface-path-id... | TenGigE interface-path-id...}}
Syntax Description
Bundle-Ether bundle-id |
Specifies an Ethernet bundle for which you want to calculate load balancing. Range is 1- 65535. |
Bundle-POS bundle-id |
Specifies a POS bundle for which you want to calculate load balancing. Range is 1- 65535. Note This keyword is supported on the Cisco CRS-1 router only. It is not supported on the Cisco XR 12000 Series Router. |
members |
Identifies specific bundle member links for which you want to calculate load balancing. |
GigabitEthernet |
Specifies the Gigabit Ethernet interface for which you want to calculate load balancing. |
TenGigE |
Specifies the 10 Gigabit Ethernet interface for which you want to calculate load balancing. |
POS |
Specifies the POS interface for which you want to calculate load balancing. Note This keyword is supported on the Cisco CRS-1 router only. It is not supported on the Cisco XR 12000 Series Router. |
interface-path-id |
Physical interface or virtual interface. Note Use the show interfaces command to see a list of all interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.6.0 |
This command was introduced on the Cisco CRS-1 router and the Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, 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. 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 System Security Configuration Guide.
For the interface-path-id argument, use the following guidelines:
•If specifying a physical interface, the naming notation is rack/slot/module/port. The slash between values is required as part of the notation. An explanation of each component of the naming notation is as follows:
–rack: Chassis number of the rack.
–slot: Physical slot number of the line card.
–module: Module number. A physical layer interface module (PLIM) is always 0.
–port: Physical port number of the interface.
•If specifying a virtual interface, the number range varies, depending on interface type.
Bundle interface traffic is distributed over the various member links of a bundle according to a hash algorithm. The bundle-hash command allows you to determine which bundle member link would carry a particular flow of traffic.
The bundle-hash command invokes a utility that initially prompts you to select some options, with availability that depends on the platform. Based on the options you select, the utility further prompts you to provide information to describe a flow. Table 35 provides a general summary of the options, the platforms on which the options are available, and the information you need to provide for each selected option.
Note The actual information that you need to provide depends on the selections you make and may vary from the information provided in Table 35.
Table 35 bundle-hash Command Options and Related Information
|
Platform Upon Which Option is Available
|
Information You Need to Provide
|
Hash Algorithm—An algorithm to calculate the bundle load balance. The intent of the hash algorithm is to determine the member link that a particular flow would take. |
3-tuple |
Cisco CRS-1 router, Cisco XR 12000 Series Router |
L3 information: •Source IP address •Destination IP address •Destination subnet prefix •Bundle IP address |
7-tuple |
Cisco CRS-1 router |
L3 information: •Source IP address •Destination IP address •Protocol L4 information: •Source port •Destination port Platform-related information: •Router ID •Ingress interface |
User Mode—The default is single mode. |
Single mode |
Cisco CRS-1 router, Cisco XR 12000 Series Router |
Information for a single source port and destination port. The utility uses this information to calculate the hash and display the bundle load-balance distribution among the user-provided physical/bundle links. While in single mode, you may receive the following prompt:
Compute destination address set for all
members [y|n]:
If you enter y(es), several sample IPv4 addresses in the destination subnet are generated, and the link is calculated for each sample address. During this calculation, the destination network address is derived from the destination IPv4 address and the subnet prefix. |
Range mode |
Cisco CRS-1 router, Cisco XR 12000 Series Router |
Information for sets of source and destination addresses to generate a packet flow for each set. The utility uses this information to calculate the hash for the generated packet flows and display the user-provided egress member links/bundle interfaces and the number of packet flows on each link. |
IP Addressing Scheme—The IP addressing scheme of the bundle. |
IPv4 |
Cisco CRS-1 router, Cisco XR 12000 Series Router |
IPv4 addresses |
IPv6 |
Cisco CRS-1 router |
IPv6 addresses |
Examples
Cisco CRS-1 router: Examples 1 and 2
Examples 1 and 2 for the Cisco CRS-1 router use a link bundle named bundle-ether 28.
Background Information for bundle-ether 28
Summary:
Source IPv4 address = 10.12.28.2 (subnet prefix 8)
Destination IPv4 address = 10.12.28.1 (subnet prefix 8)
Bundle IPv4 address = 10.12.28.2
Members = GigabitEthernet 0/1/5/6, GigabitEthernet 0/1/5/7, GigabitEthernet 0/6/5/5, GigabitEthernet 0/6/5/6, GigabitEthernet 0/6/5/7
RP/0/RP0/CPU0:router# show bundle bundle-ether 28
State: 0 - Port is Detached. 1 - Port is Waiting.
2 - Port is Attached. 3 - Port is Collecting.
4 - Port is Distributing.
Bandwidth (Kbps) Min active Max active
Effective Available MAC address Links B/W (Kbps) Links
---------- ---------- -------------- ----- ---------- -----
5000000 5000000 0015.6358.b903 1 1 32
Port State Port ID B/W (Kbps) MAC address
------------ ----- -------------- ---------- ---------------
Gi0/1/5/6 4 0x8000, 0x0003 1000000 0015.6358.bcb8
Gi0/1/5/7 4 0x8000, 0x0004 1000000 0015.6358.bcb9
Gi0/6/5/5 4 0x8000, 0x0005 1000000 0015.6358.be38
Gi0/6/5/6 4 0x8000, 0x0006 1000000 0015.6358.be39
Gi0/6/5/7 4 0x8000, 0x0007 1000000 0015.6358.be3a
RP/0/RP0/CPU0:router# show running-config interface bundle-ether 28
description Connected to P1_CRS-8 Bundle-Ether 28
ipv4 address 10.12.28.2 255.255.255.0
Example 1
The following example shows how to calculate load balancing across the members of a link bundle (bundle-ether 28) using the 3-tuple hash algorithm, a single source and destination, and IPv4 addresses:
RP/0/RP0/CPU0:router# bundle-hash bundle-ether 28
Specify load-balance configuration (L3/3-tuple or L4/7-tuple) (L3,L4): l3
Single SA/DA pair (IPv4,IPv6) or range (IPv4 only): S/R [S]: s
Enter bundle type IP V4 (1) or IP V6 (2): 1
Enter source IP V4 address: 10.12.28.2
Enter destination IP V4 address: 10.12.28.1
Compute destination address set for all members? [y/n]: y
Enter subnet prefix for destination address set: 8
Enter bundle IP V4 address [10.12.28.2]: 10.12.28.2
Link hashed to is GigabitEthernet0/6/5/7
Destination address set for subnet 10.0.0.0:
10.0.0.6 hashes to link GigabitEthernet0/1/5/6
10.0.0.8 hashes to link GigabitEthernet0/6/5/5
10.0.0.12 hashes to link GigabitEthernet0/6/5/6
10.0.0.2 hashes to link GigabitEthernet0/6/5/7
10.0.0.1 hashes to link GigabitEthernet0/1/5/7
Example 2
The following example shows how to calculate load balancing across the members of a link bundle (bundle-ether 28) using the 3-tuple hash algorithm, a range of source and destinations, and IPv4 addresses:
RP/0/RP0/CPU0:router# bundle-hash bundle-ether 28
Specify load-balance configuration (L3/3-tuple or L4/7-tuple) (L3,L4): l3
Single SA/DA pair (IPv4,IPv6) or range (IPv4 only): S/R [S]: r
Maximum number of flows (num src addr * num dst addr): 65536
Enter first source IP address: 10.12.28.2
Enter subnet prefix for source address set: 8
Enter number of source addresses (1-245): 20
Enter source address modifier (1-12) [def:1]: 5
Enter destination IP address: 10.12.28.1
Enter subnet prefix for destination address set: 8
Enter number of destination addresses (1-245): 20
Enter destination address modifier (1-12) [1]: 5
Many to many (M) or simple pairs (S)? [M]: s
Calculating simple pairs...
Member GigabitEthernet0/1/5/6 has 6 hits
Member GigabitEthernet0/6/5/5 has 2 hits
Member GigabitEthernet0/6/5/6 has 2 hits
Member GigabitEthernet0/6/5/7 has 9 hits
Member GigabitEthernet0/1/5/7 has 1 hits
Cisco CRS-1 router: Example 3
Example 3 for the Cisco CRS-1 router uses a link bundle named bundle-ether 202.
Background Information for bundle-ether 202
Summary:
Source IPv4 address = 172.20.180.167 (subnet prefix 24)
Destination IPv4 address = 172.30.15.42 (subnet prefix 24)
Bundle IPv4 address = 209.165.200.225
Members = GigabitEthernet 0/2/0/1, GigabitEthernet 0/2/0/2, GigabitEthernet 0/3/3/6, GigabitEthernet 0/0/3/0, GigabitEthernet 0/0/3/1
RP/0/RP0/CPU0:router# show bundle bundle-ether 202
State: 0 - Port is Detached. 1 - Port is Waiting.
2 - Port is Attached. 3 - Port is Collecting.
4 - Port is Distributing.
Bandwidth (Kbps) Min active Max active
Effective Available MAC address Links B/W (Kbps) Links
---------- ---------- -------------- ----- ---------- -----
4000000 4000000 0000.0c06.0001 1 1 32
Port State Port ID B/W (Kbps) MAC address
------------ ----- -------------- ---------- ---------------
Gi0/2/0/1 4 0x8000, 0x0005 1000000 0000.0c01.2752
Gi0/2/0/2 4 0x8000, 0x0004 1000000 0000.0c02.52e3
Gi0/3/3/6 4 0x8000, 0x0008 1000000 0000.0c06.ac96
Gi0/0/3/0 4 0x8000, 0x0006 1000000 0000.0c00.4605
Gi0/0/3/1 4 0x8000, 0x0007 1000000 0000.0c01.7cfb
RP/0/RP0/CPU0:router# show running-config interface bundle-ether 202
interface Bundle-Ether202
ipv4 address 209.165.200.225 255.255.255.0
ipv6 address ::109:109:109:3/112
bundle minimum-active links 1
The following example shows how to calculate load balancing across the members of a link bundle (bundle-ether 202) using the 7-tuple hash algorithm, a single source and destination, and IPv4 addresses:
RP/0/RP0/CPU0:router# bundle-hash bundle-ether 202
Specify load-balance configuration (L3/3-tuple or L4/7-tuple) (L3,L4): l4
Single SA:SP/DA:SP pair (IPv4,IPv6) or range (IPv4 only): S/R [S]: s
Enter bundle type IP V4 (1) or IP V6 (2): 1
Enter source IP V4 address: 172.20.180.167
Enter destination IP V4 address: 172.30.15.42
- physical interface format: [ POS | GigabitEthernet | TenGigE ]R/S/I/P
- bundle interface format: [ Bundle-Ether | Bundle-POS ]bundle-id
Enter ingress interface: GigabitEthernet0/2/0/3
Enter L4 protocol (TCP,UDP,SCTP,L2TPV3,NONE): UDP
Enter destination port: 2000
Compute destination address set for all members? [y/n]: n
S/D pair 172.20.180.167:1000/172.30.15.42:2000 -- Link hashed to is GigabitEthernet0/3/3/6
Enter bundle type IP V4 (1) or IP V6 (2): 1
Enter source IP V4 address [172.20.180.167]: 172.20.180.167
Enter destination IP V4 address [172.30.15.42]: 172.30.15.42
- physical interface format: [ POS | GigabitEthernet | TenGigE ]R/S/I/P
- bundle interface format: [ Bundle-Ether | Bundle-POS ]bundle-id
Enter ingress interface [GigabitEthernet0/2/0/3]: GigabitEthernet0/2/0/3
Enter L4 protocol (TCP,UDP,SCTP,L2TPV3,NONE) [udp]: UDP
Enter src port [1000]: 1000
Enter destination port [2000]: 2000
Compute destination address set for all members? [y/n]: y
Enter subnet prefix for destination address set: 24
Enter bundle IP V4 address [172.20.180.167]: 209.165.200.225
S/D pair 172.20.180.167:1000/172.30.15.42:2000 -- Link hashed to is GigabitEthernet0/3/3/6
Destination address set for subnet 172.30.15.0:
S/D pair 172.20.180.167:1000/172.30.15.1:2000 hashes to link GigabitEthernet0/3/3/6
S/D pair 172.20.180.167:1000/172.30.15.6:2000 hashes to link GigabitEthernet0/2/0/1
S/D pair 172.20.180.167:1000/172.30.15.3:2000 hashes to link GigabitEthernet0/2/0/2
S/D pair 172.20.180.167:1000/172.30.15.5:2000 hashes to link GigabitEthernet0/0/3/0
Cisco XR 12000 Series Router: Examples 1 - 3
Examples 1, 2, and 3 for the Cisco XR 12000 Series Router use a link bundle named bundle-ether 2.
Background Information for bundle-ether 2
Summary for example 1:
Source IPv4 address = 10.23.23.23 (subnet prefix 24)
Destination IPv4 address = 10.12.12.12 (subnet prefix 24)
Bundle IPv4 address = 10.1.1.2
Members = GigabitEthernet 0/2/1/0, GigabitEthernet 0/2/1/1
Summary for example 2:
Source IPv4 address = 10.1.1.1 (subnet prefix 24)
Destination IPv4 address = 10.4.4.4 (subnet prefix 24)
Bundle IPv4 address = 10.1.1.2
Members = GigabitEthernet 0/2/1/0, GigabitEthernet 0/2/1/1
Summary for example 3:
Source IPv4 address = 10.1.1.1 (subnet prefix 16)
Destination IPv4 address = 10.2.1.1 (subnet prefix 16)
Bundle IPv4 address = 10.1.1.2
Members = GigabitEthernet 0/2/1/0, GigabitEthernet 0/2/1/1
RP/0/0/CPU0:router# show bundle bundle-ether 2
State: 0 - Port is Detached. 1 - Port is Waiting.
2 - Port is Attached. 3 - Port is Collecting.
4 - Port is Distributing.
Minimum active Maximum active
B/W (Kbps) MAC address Links B/W (Kbps) Links
---------- -------------- ----- ---------- -----
2000000 000b.602f.fa37 1 1 8
Port State Port ID B/W (Kbps) MAC address
------------ ----- -------------- ---------- ---------------
Gi0/2/1/0 4 0x8000, 0x0002 1000000 000b.602f.fa37*
Gi0/2/1/1 4 0x8000, 0x0003 1000000 000b.602f.fa38
RP/0/0/CPU0:router# show running-config interface bundle-ether 2
ipv4 address 10.1.1.2 255.255.255.0
Example 1
The following example shows how to calculate load balancing across the members of a link bundle (bundle-ether 2) using a single source and destination:
RP/0/0/CPU0:router# bundle-hash bundle-ether 2
Single SA/DA pair or range: S/R [S]: s
Enter source IP V4 address: 10.23.23.23
Enter destination IP V4 address: 10.12.12.12
Compute destination address set for all members? [y/n]: y
Enter subnet prefix for destination address set: 24
Enter bundle IP V4 address [10.23.23.23]: 10.1.1.2
Link hashed [hash:0] to is GigabitEthernet0/2/1/1 member id 0 ifh 0x3000b00
Destination address set for subnet 10.12.12.0:
10.12.12.2 [hash:6] hashes to link GigabitEthernet0/2/1/1
10.12.12.1 [hash:5] hashes to link GigabitEthernet0/2/1/0
Example 2
The following example shows how to calculate load balancing across the members of a link bundle (bundle-ether 2) using a range of source and destinations:
RP/0/0/CPU0:router# bundle-hash bundle-ether 2
Single SA/DA pair or range: S/R [S]: r
Enter first source IP address: 10.1.1.1
Enter subnet prefix for source address set: 24
Enter number of source addresses (1-65536): 100
Enter source address modifier (1-167114) [1]: 1
Enter destination IP address: 10.4.4.4
Enter subnet prefix for destination address set: 24
Enter number of destination addresses (1-655): 10
Enter destination address modifier (1-1651404) [1]: 1
Total number of hits 1000
Member GigabitEthernet0/2/1/1 has 500 hits
Member GigabitEthernet0/2/1/0 has 500 hits
Example 3
The following example shows how to calculate load balancing across specified members of a link bundle (bundle-ether 2) using a single source and destination:
RP/0/0/CPU0:router# bundle-hash members gigabitEthernet 0/2/1/1 gigabitEthernet 0/2/1/0
Single SA/DA pair or range: S/R [S]: s
Enter source IP V4 address: 10.1.1.1
Enter destination IP V4 address: 10.2.1.1
Compute destination address set for all members? [y/n]: y
Enter subnet prefix for destination address set: 16
Enter bundle IP V4 address [10.1.1.1]: 10.1.1.2
Link hashed [hash:6] to is GigabitEthernet0/2/1/1 member id 0 ifh 0x3000b00
Destination address set for subnet 10.2.1.0:
10.2.1.1 [hash:6] hashes to link GigabitEthernet0/2/1/1
10.2.1.2 [hash:5] hashes to link GigabitEthernet0/2/1/0
Related Commands
|
|
bundle id |
Adds a port to an aggregated interface (or bundle). |
bundle id
To add a port to an aggregated interface (or bundle), enter the bundle id command in interface configuration mode.
bundle id bundle-id [mode {active | on | passive}]
no bundle id bundle-id
Syntax Description
bundle-id |
Bundle on which you want to add a port. Range is 1 through 65535. |
mode |
(Optional) Specifies the mode of operation, as follows: •active—Use the mode active keywords to run Link Aggregation Control Protocol (LACP) in active mode over the port. When you specify active, the port joins the bundle and is activated if LACP determines that it is compatible. •on—Use the mode on keywords to add the link to a bundle without running LACP over the port. •passive—Use the mode passive keywords to run LACP in passive mode over the port. When you specify passive, LACP packets are sent only if the other end of the link is using active LACP. The link joins the bundle and is activated if LACP packets are exchanged and the port is compatible. |
Defaults
mode = on
Command Modes
Interface configuration
Command History
|
|
Release 3.2 |
This command was introduced on the Cisco CRS-1 router. |
Release 3.3.0 |
The bundle id command syntax was changed from bundle-id. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
This command was first supported on the Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, 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. 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 System Security Configuration Guide.
If you enter the bundle id command and specify a port that is already bound to a bundle, the port unbinds from the original bundle and becomes attached to the new bundle. If the bundle numbers are the same, then the port does not unbind, but the mode changes to mode you specified with the bundle id command.
Examples
The following example shows how to add a port onto a bundle:
RP/0/RP0/CPU0:router(config)# interface GigabitEthernet 0/1/5/0
RP/0/RP0/CPU0:router(config-if)# bundle id 1
The following example shows how to add an active LACP port onto an aggregated interface (or bundle):
RP/0/RP0/CPU0:router(config)# interface GigabitEthernet 0/6/5/7
RP/0/RP0/CPU0:router(config-if)# bundle id 5 mode active
Related Commands
bundle maximum-active links
To designate one active link and one standby link that can take over immediately for a bundle if the active link fails, use the bundle maximum-active links command in interface configuration mode. To return to the default maximum active links value, use the no form of this command.
bundle maximum-active links links [hot-standby]
no bundle maximum-active links links
Syntax Description
links |
Number of active links you want to bring up in the specified bundle. The only valid value is 1. Note In Release 3.3.0 and subsequent releases, only one active link is supported. |
hot-standby |
(Optional) Determines how a switchover between active and standby links is implemented. This option is available only on links with LACP enabled. By default, a switchover is implemented per an IEEE standard approach. If you optionally specify the hot-standby keyword, a switchover is implemented per a faster proprietary optimization. |
Defaults
By default, a maximum of 32 links in a bundle can be active on a Cisco CRS-1 router, and a maximum of 8 links can be active on a Cisco XR 12000 Series Router.
Command Modes
Interface configuration
Command History
|
|
Release 3.3.0 |
This command was introduced on the Cisco CRS-1 router. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
This command was introduced on the Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
The hot-standby keyword was added. |
Usage Guidelines
To use this command, 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. 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 System Security Configuration Guide.
Note The Cisco XR 12000 Series Router does not currently support 1:1 link protection. Therefore, the bundle maximum-active links command is not supported on the Cisco XR 12000 Series Router.
By default, multiple links can actively carry traffic for a bundle. However, if one of the links fails, there is no dedicated standby link to take its place. The bundle maximum-active links command enables you to implement the optional 1:1 link protection, which means for the specified bundle, you designate one active link and one or more standby links that can take over immediately if the active link fails.
By setting the bundle maximum-active links command to 1, the highest-priority link within the bundle becomes active (distributing state) and the remaining links are in standby mode. If a standby link meets one of the following criteria, it is in the collecting state:
•Running Link Aggregation Control Protocol (LACP), and the hot-standby option is implemented.
•Not running LACP.
If a standby link does not meet either of these criteria, it is in the waiting state.
The second highest-priority link within the bundle becomes the standby link that takes over immediately if the active link fails. The priority is based on the value from the bundle port-priority command, where a lower value is a higher priority. Therefore, you must configure the highest priority (lowest value) for the link that you want to be active and the second-highest priority for the link that you want to act as a backup to the active link.
Note We recommend designating only one backup link to the active link. Although you can designate an additional backup link, maintaining two backup links consumes more bandwidth and offsets any benefits that may be gained.
Note If a link is not running LACP, the configuration of the bundle maximum-active links and bundle port-priority commands or equivalent commands must be the same on both ends of the link. If a link is running LACP, the configuration of the bundle maximum-active links command only must be the same on both ends of the link.
The hot-standby option of using an IEEE standard-based switchover (the default) or a faster proprietary optimized switchover is available only for active and standby links running LACP. For links not running LACP, the proprietary optimized switchover option is used.
When using one of the hot-standby options on a Cisco IOS XR device, the peer device must have a standby link configured and be one of the following:
•Another Cisco IOS XR device using the same option.
•Another device using an IEEE standard-based switchover. (Cisco does not recommend using this option because unexpected behavior, such as the peer sending traffic on the standby link, can occur.)
Examples
In the following example, the user implements 1:1 link protection for Ethernet bundle 5 and specifies that the proprietary optimization is used for the LACP-enabled active and standby links:
RP/0/RP0/CPU0:router(config)# interface bundle-ether 5
RP/0/RP0/CPU0:router(config-if)# bundle maximum-active links 1 hot-standby
The following example shows how to display information about Ethernet bundle 5:
RP/0/RSP0/CPU0:router # show bundle bundle-ether 5
State: 0 - Port is Detached. 1 - Port is Waiting.
2 - Port is Attached. 3 - Port is Collecting.
4 - Port is Distributing.
Minimum active Maximum active
B/W (Kbps) MAC address Links B/W (Kbps) Links
---------- -------------- ----- ---------- -----
10000000 001d.e5eb.2898 1 1 1
Port State Port ID B/W (Kbps) MAC address
------------ ----- -------------- ---------- ---------------
Te0/1/0/1 4 0x8000, 0x0001 10000000 0000.abab.0001
Te0/1/0/0 3 0x8000, 0x0002 10000000 0000.abab.0000
In the show bundle bundle-ether 5 command output, the state of the active link is 4, which indicates that the port is distributing. The state of the standby link is 3, which indicates that the port is collecting.
In the following example, the user implements 1:1 link protection for Ethernet bundle 5 and does not specify the hot-standby keyword, because the user wants to use the default IEEE standard-based switchover on the LACP-enabled active and standby links:
RP/0/RP0/CPU0:router(config)# interface bundle-ether 5
RP/0/RP0/CPU0:router(config-if)# bundle maximum-active links 1
The following example shows how to display information about Ethernet bundle 5:
RP/0/RSP0/CPU0:router # show bundle bundle-ether 5
State: 0 - Port is Detached. 1 - Port is Waiting.
2 - Port is Attached. 3 - Port is Collecting.
4 - Port is Distributing.
Minimum active Maximum active
B/W (Kbps) MAC address Links B/W (Kbps) Links
---------- -------------- ----- ---------- -----
10000000 001d.e5eb.2898 1 1 1
Port State Port ID B/W (Kbps) MAC address
------------ ----- -------------- ---------- ---------------
Te0/1/0/1 4 0x8000, 0x0001 10000000 0000.abab.0001
Te0/1/0/0 1 0x8000, 0x0002 10000000 0000.abab.0000
In the show bundle bundle-ether 5 command output, the state of the active link is 4, which indicates that the port is distributing. The state of the standby link is 1, which indicates that the port is waiting.
In the following example, the user implements 1:1 link protection for Ethernet bundle 5 and does not specify the hot-standby keyword, because the LACP-disabled link automatically uses the proprietary optimized switchover:
RP/0/RP0/CPU0:router(config)# interface bundle-ether 5
RP/0/RP0/CPU0:router(config-if)# bundle maximum-active links 1
The following example shows how to display information about Ethernet bundle 5:
RP/0/RSP0/CPU0:router # show bundle bundle-ether 5
State: 0 - Port is Detached. 1 - Port is Waiting.
2 - Port is Attached. 3 - Port is Collecting.
4 - Port is Distributing.
Minimum active Maximum active
B/W (Kbps) MAC address Links B/W (Kbps) Links
---------- -------------- ----- ---------- -----
10000000 001d.e5eb.2898 1 1 1
Port State Port ID B/W (Kbps) MAC address
------------ ----- -------------- ---------- ---------------
Te0/1/0/1 4 0x8000, 0x0001 10000000 0000.abab.0001
Te0/1/0/0 3 0x8000, 0x0002 10000000 0000.abab.0000
In the show bundle bundle-ether 5 command output, the state of the active link is 4, which indicates that the port is distributing. The state of the standby link is 3, which indicates that the port is collecting.
Related Commands
bundle minimum-active bandwidth
To set the minimum amount of bandwidth required before a user can bring up a specific bundle, use the bundle minimum-active bandwidth command in interface configuration mode.
bundle minimum-active bandwidth kbps
Syntax Description
kbps |
Minimum bandwidth required before you can bring up a bundle. Range is from 1 through a number that varies depending on the platform and the bundle type. |
Defaults
kbps: 1
Command Modes
Interface configuration
Command History
|
|
Release 3.3.0 |
This command was introduced on the Cisco CRS-1 router. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
This command was first supported on the Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, 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. 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 System Security Configuration Guide.
Examples
The following example shows how to set the minimum amount of bandwidth required before a user can bring up a specific bundle. In this example, the user sets the minimum amount of bandwidth required to bring up Ethernet bundle 1 to 620000:
RP/0/RP0/CPU0:router(config)# interface Bundle-Ether 1
RP/0/RP0/CPU0:router(config-if)# bundle minimum-active bandwidth 620000
Related Commands
bundle minimum-active links
To set the number of active links required to bring up a specific bundle, use the bundle minimum-active links command in interface configuration mode.
bundle minimum-active links links
Syntax Description
links |
Number of active links you want to bring up in the specified bundle. For a Cisco CRS-1 router, the range is from 1 through 32. For a Cisco XR 12000 Series Router, the range is from 1 through 8. |
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
|
|
Release 3.3.0 |
This command was introduced on the Cisco CRS-1 router. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
This command was first supported on the Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, 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. 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 System Security Configuration Guide.
Examples
The following example shows how to set the number of active links required to bring up a specific bundle on a Cisco CRS-1 router. In this example, the user configures Ethernet bundle 5 so that two links must be active before the bundle can be brought up:
RP/0/RP0/CPU0:router(config)# interface Bundle-Ether 5
RP/0/RP0/CPU0:router(config-if)# bundle minimum-active links 2
Related Commands
bundle port-priority
To configure a port priority for a bundle member link, enter the bundle port-priority command in interface configuration mode. To return to the default priority value, use the no form of this command.
bundle port-priority priority
no bundle port-priority priority
Syntax Description
priority |
Priority for this port, where a lower value equals a higher priority. Replace the priority argument with a number. Range is from 0 through 65535. |
Defaults
priority = 32768
Command Modes
Interface configuration
Command History
|
|
Release 3.2 |
This command was introduced on the Cisco CRS-1 router. |
Release 3.3.0 |
The command name was changed from lacp port-priority to bundle port-priority. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
This command was first supported on the Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, 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. 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 System Security Configuration Guide.
The bundle port-priority command enables you to determine whether or not similar ports, for example, Gigabit Ethernet ports with Link Aggregation Control Protocol (LACP) enabled or with LACP disabled, are aggregated based on the priority of the port.
In cases where LACP is enabled on aggregated ports, the port priority forms part of the port ID, which is transmitted within a packet when a device exchanges packets with its peer. The peers use the port ID within the packets to determine whether a given port should carry traffic for the bundle.
In cases where LACP is disabled, the port priority is used locally, and a device does not communicate its priority to a peer. Therefore, the peers should have the same priority configured to avoid a mismatch in which links are used for carrying traffic. For example, you could set up the port priorities so that a device would use links 1, 3, and 4 for carrying traffic, and its peer would use links 1, 2, and 3, where links use the same numbering sequence at both ends.
Note A lower value is a higher priority for the port.
Examples
The following example shows how to configure the priority of a port:
RP/0/RP0/CPU0router(config-if)# bundle port-priority 1
Related Commands
clear lacp counters
To clear Link Aggregation Control Protocol (LACP) counters for all members of all bundles, all members of a specific bundle, or for a specific port, enter the clear lacp counters command in EXEC mode.
clear lacp counters [bundle {Bundle-Ether bundle-id | Bundle-POS bundle-id} | port {GigabitEthernet interface-path-id | TenGigE interface-path-id | POS interface-path-id}]
Syntax Description
bundle |
(Optional) Clears LACP counters for all members of a bundle. |
Bundle-Ether node-id |
(Optional) Ethernet bundle. Use the node-id argument to specify the node ID number of the LACP counters you want to clear. Range is 1 through 65535. |
Bundle-POS bundle-id |
(Optional) POS bundle. Use the bundle-id argument to specify the bundle ID number of the LACP counters you want to clear. Range is from 1 through 65535. |
port |
(Optional) Clears all LACP counters on the specified bundle or interface. |
GigabitEthernet |
(Optional) Gigabit Ethernet interface. Use the interface-path-id argument to specify the Gigabit Ethernet interface whose LACP counters you want to clear. |
TenGigE |
(Optional) Ten Gigabit Ethernet interface. Use the interface-path-id argument to specify the Ten Gigabit Ethernet interface whose LACP counters you want to clear. |
POS |
(Optional) Packet-over-SONET/SDH (POS) interface. Use the interface-path-id argument to specify the POS interface whose LACP counters you want to clear. |
interface-path-id |
Physical interface or virtual interface. Note Use the show interfaces command to see a list of all interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.2 |
This command was introduced on the Cisco CRS-1 router. |
Release 3.3.0 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
This command was first supported on the Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, 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. 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 System Security Configuration Guide.
For the interface-path-id argument, use the following guidelines:
•If specifying a physical interface, the naming notation is rack/slot/module/port. The slash between values is required as part of the notation. An explanation of each component of the naming notation is as follows:
–rack: Chassis number of the rack.
–slot: Physical slot number of the line card.
–module: Module number. A physical layer interface module (PLIM) is always 0.
–port: Physical port number of the interface.
•If specifying a virtual interface, the number range varies, depending on interface type.
|
|
bundle |
execute |
basic-services |
read, write |
Examples
The following example shows how to clear LACP counters:
RP/0/RP0/CPU0:router# clear lacp counters
Related Commands
interface Bundle-Ether
To create a new Ethernet bundle and enter interface configuration mode for that bundle, use the interface Bundle-Ether command in global configuration mode. To delete an Ethernet bundle, use the no form of this command.
interface Bundle-Ether bundle-id
no interface Bundle-Ether bundle-id
Syntax Description
bundle-id |
Ethernet bundle you want to create or configure. Replace bundle-id with a bundle identifier. Range is from 1 through 65535. |
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
|
|
Release 3.2 |
This command was introduced on the Cisco CRS-1 router. |
Release 3.3.0 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
This command was first supported on the Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, 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. 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 System Security Configuration Guide.
Examples
The following example shows how to create a new Ethernet bundle and enter interface configuration mode for that bundle.:
RP/0/RP0/CPU0:router(config)# interface Bundle-Ether 3
RP/0/RP0/CPU0:router(config-if)#
Related Commands
interface Bundle-POS
To create a new Packet-over-SONET/SDH (POS) bundle and enter interface configuration mode for that bundle, use the interface Bundle-POS command in global configuration mode. To delete a POS bundle, use the no form of this command.
interface Bundle-POS bundle-id
no interface Bundle-POS bundle-id
Syntax Description
bundle-id |
Number of the POS bundle you want to create or configure. Replace bundle-id with a bundle identifier. Range is from 1 through 65535. |
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
|
|
Release 3.2 |
This command was introduced on the Cisco CRS-1 router. |
Release 3.3.0 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, 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. 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 System Security Configuration Guide.
Examples
The following example shows how to create a new POS bundle and enter interface configuration mode for that bundle.:
RP/0/RP0/CPU0:router(config)# interface Bundle-POS 10
RP/0/RP0/CPU0:router(config-if)#
Related Commands
lacp fast-switchover
To disable the wait-while timer in the LACP state machine, use the lacp fast-switchover command in interface configuration mode. To re-enable the wait-while timer, use the no form of this command.
lacp fast-switchover
no lacp fast-switchover
Syntax Description
This command has no arguments or keywords.
Command Default
The wait-while timer in the LACP state machine is enabled.
Command Modes
Interface configuration (config-if)
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 router and the Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, 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. 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 System Security Configuration Guide.
Note The Cisco XR 12000 Series Router does not currently support 1:1 link protection. Therefore, the lacp fast-switchover command is not supported on the Cisco XR 12000 Series Router.
If you have 1:1 link protection enabled (you set the value of the bundle maximum-active links command to 1) on a bundle with member links running LACP, you can optionally disable the wait-while timer in the LACP state machine. Disabling this timer causes a bundle member link in standby mode to expedite its normal state negotiations, thereby enabling a faster switchover from a failed active link to the standby link.
Regardless of the type of switchover you are using, the default IEEE standard-based or the faster proprietary optimized switchover, the state negotiations of the standby link is expedited. (For more information about the switchover types, refer to the bundle maximum-active links command.) However, enabling the lacp fast-switchover command provides a greater benefit if used with the IEEE standard-based switchover.
Examples
The following example shows how to disable the wait-while timer for LACP-enabled member links of Bundle-Ether 28:
RP/0/RP0/CPU0:router(config)# interface Bundle-Ether 28
RP/0/RP0/CPU0:router(config-if)# lacp fast-switchover
The following example shows how to re-enable the wait-while timer for LACP-enabled member links of Bundle-Ether 28:
RP/0/RP0/CPU0:router(config)# interface Bundle-Ether 28
RP/0/RP0/CPU0:router(config-if)# no lacp fast-switchover
Related Commands
|
|
bundle maximum-active links |
Designates one active link in a bundle and one link in standby mode that can take over immediately if the active link fails. |
lacp period short
To configure a one second interval between LACP packets that are received from the peer, enter the lacp period command in interface configuration mode. To return to the default LACP period, use the no form of this command.
lacp period short
no lacp period
Syntax Description
This command has no arguments or keywords.
Defaults
If you do not enter the lacp period short command, then the peer transmits LACP packets every 30 seconds
Command Modes
Interface configuration
Command History
|
|
Release 3.2 |
This command was introduced on the Cisco CRS-1 router. |
Release 3.3.0 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
This command was first supported on the Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to configure a one-second interval between LACP packets that are received from the peer:
RP/0/RP0/CPU0:router(config-if)# lacp period short
Related Commands
|
|
bundle id |
Adds a port to an aggregated interface (or bundle). |
show lacp port |
Displays detailed information about LACP ports. |
show lacp bundle |
Displays detailed information about LACP ports and their peers. |
lacp system priority
To configure the priority for the current system, enter the lacp system priority command in global configuration mode. To return to the default LACP system priority value, use the no form of this command.
lacp system priority priority
Syntax Description
priority |
Priority for this system. Replace priority with a number. Range is from 0 through 65535. A lower value is higher priority. |
Defaults
priority: 32768
Command Modes
Global configuration
Command History
|
|
Release 3.2 |
This command was introduced on the Cisco CRS-1 router. |
Release 3.3.0 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
This command was first supported on the Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, 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. 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 System Security Configuration Guide.
The system priority value forms part of the LACP system ID, which is transmitted within each LACP packet. The system ID, port ID and key combine to uniquely define a port within a LACP system.
Examples
The following example shows how to configure an LACP priority of 100 on a router:
RP/0/RP0/CPU0router(config)# lacp system priority 100
Related Commands
show bundle Bundle-Ether
To display information about a specific Ethernet bundle, enter the show bundle Bundle-Ether command in EXEC mode.
show bundle Bundle-Ether bundle-id
Syntax Description
bundle-id |
Number of the Ethernet bundle whose information you want to display. Replace bundle-id with a bundle identifier. Range is from 1 through 65535. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.2 |
This command was introduced on the Cisco CRS-1 router. |
Release 3.3.0 |
•The output for this command was modified. •The reasons keyword was added. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
This command was first supported on the Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
The reasons keyword was removed. |
Usage Guidelines
To use this command, 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. 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 System Security Configuration Guide.
The show bundle Bundle-Ether command output includes a reason field, which briefly describes both normal and error states of the link. For a listing of each state, along with an explanation about the state, reasons the link is in that state, and possible corrective actions you can take to resolve an error state, see Table 37.
Examples
The following example shows the output from the show bundle Bundle-Ether command:
RP/0/RP0/CPU0:router# show bundle Bundle-Ether 1
State: 0 - Port is Detached. 1 - Port is Waiting.
2 - Port is Attached. 3 - Port is Collecting.
4 - Port is Distributing.
Minimum active Maximum active
B/W (Kbps) MAC address Links B/W (Kbps) Links
---------- -------------- ----- ---------- -----
0 0800.453a.651d 1 620000 32
Port State Port ID B/W (Kbps) MAC address
------------ ----- -------------- ---------- ---------------
Gi0/0/2/0 0 0x8000, 0x0001 1000000 0800.453a.651d*
Link is marked individual by partner
Table 36 describes the significant fields shown in the display.
Table 36 show bundle Bundle-Ether Field Descriptions
|
|
B/W (Kbps) |
Bundled interface bandwidth, in kilobits per second. |
MAC address |
MAC address of the bundle. |
Minimum links |
Minimum number of active links required before the specified bundle can be activated. |
active B/W (Kbps) |
Minimum amount of bandwidth required before a user can bring up the specified bundle. |
Maximum active links |
Maximum number of links that can be actively carrying traffic in the specified bundle. |
Port ID |
Port identifier, in the rack/slot/module/port format. |
State |
Current state of the specified port. Possible port states are as follows: •0—Port is Detached •1—Port is Waiting •2—Port is Attached •3—Port is Collecting •4—Port is Distributing |
Port ID |
Port identifier in hexadecimal format |
B/W (Kbps) |
Port bandwidth, in kilobits per second. |
MAC address |
MAC address associated with the specified port. |
reason |
Brief description of normal or error state of the link. For a listing of each state, along with an explanation about the state, reasons the link is in that state, and possible corrective actions you can take to resolve an error state, see Table 37. |
Table 37 Ethernet Link State Explanation, Cause, and Action
|
State Selection logic has not yet been run for the bundle this link is a member of Explanation Status is not yet determined; process initialization is not complete. Cause In most cases, indicates that the bundlemgr_distrib process has not completed initialization after a restart or failover. If the command is run soon after a restart or failover, this behavior is expected. In other cases, indicates a problem during process initialization. Action Restart the bundlemgr_distrib process. If restarting this process does not work, restart the ifmgr process. |
State Link is down Explanation Interface or line protocol state is not operationally up. Possible explanations are that the port is shut down, the port is not connected to a peer or is shut down on the peer, or the L1 or L2 is affected by signalling problems. Cause A normal condition in which the link is shut down or not connected. Other causes include a fault with the line or a misconfiguration of the line protocol. Action Check the port configuration and status on both devices. |
State Link is being removed from the bundle Explanation Bundle membership configuration was removed from the link, and the effects of this action are still being processed. Cause If receiving this reason is transient, the condition is normal. If the reason is persistent, a problem is present. Action If reason is persistent, restart the bundlemgr_distrib process. |
State Link has wrong duplexity Explanation Link is configured to run LACP but is in half-duplex mode. Or the link duplexity does not match that of the primary link. Cause Link is improperly configured. Links running LACP must be full-duplex, and all links in a bundle must have the same duplexity. Action If LACP is running, check to make sure link is in full-duplex mode. Otherwise, check the duplexity of the other bundle members and correct the duplexity setting of this link accordingly. |
State Link has wrong bandwidth Explanation The acceptable bandwidth for links in a bundle is determined by the existing configured links in a bundle. All links must have a bandwidth within a certain range of the first links added. This link has a bandwidth outside that range. Cause Link is improperly configured. All links must have a bandwidth within a certain range of each other. The range is determined by the platform. For the Cisco CRS-1 router, the range is four times, while the Cisco XR 12000 Series Router requires that the bandwidth is the same on all links. Action Reconfigure the links with the incorrect bandwidth. |
State Link is a loopback interface Explanation LACP detected that the peer device has the same LACP system ID as the local device. Cause A port is connected to another port on the same device, or the system ID settings of two devices are identical. This latter case usually indicates a failure to acquire a unique system MAC address from the backplane of the device. Action Check the cabling to ensure that two ports on the same device are not connected. If the connection is between two devices, then check that the backplane is correctly programmed with a base MAC address. |
State Link has wrong activity type Explanation The use of LACP on this link is inconsistent with the use of LACP on other links in the bundle. Some links are configured to run LACP, but others are not. Cause Link is improperly configured. All links must either be running LACP or not running LACP. Action Check the LACP configuration on the link, and reconfigure the setting as appropriate. |
State Link's bundle already has maximum number of members allowed Explanation A bundle can only have a certain number of members attached to it. This state indicates that more links are configured than can be attached. The Cisco CRS-1 router has a limit of 32, and the Cisco XR 12000 Series Router has a limit of 8. Cause Although the number of members is over-configured, this condition is normal. Action No action is required. If desired, you can remove the extra links from the bundle and assign them to a different bundle. |
State Link is attached to a shared medium Note The detection of this condition is not currently supported. Explanation Link bundles can operate using point-to-point links only. The link is running over a shared media, which makes the link unusable. Cause The link is connected to a shared media device or network. Action Check the connectivity of the link to make sure that all links are point-to-point connections. |
State Link has wrong LAG ID Explanation The LAG ID of this link differs from that of the primary link, which indicates that the port on the peer device is not configured to be in the same bundle as the port to which the primary link is connected. It could also indicate that the connections are to different peer devices. Cause Link is improperly configured, or a cabling problem exists. Action Check the link configuration and connectivity, and modify as appropriate. |
State Link's bundle does not exist Explanation Link was configured to be a member of a bundle that does not exist. Cause Link is improperly configured. Action Configure the non-existent bundle interface, or reconfigure the link to be in the desired bundle. |
State Link's bundle has no primary link Explanation No link is configured to be a member of the bundle that is currently a candidate for aggregation. Cause To be considered a candidate for aggregation, a link must be up, and it must be compatible with previously configured links regarding bandwidth and LACP usage. For links running LACP, the links must also be full-duplex, and the partner must indicate an ability to form an aggregation. If there is no primary link, it is because there are no links that meet these criteria. Action Check all the links in a bundle against the criteria, and take the appropriate action. |
State Link's bundle is shut down Explanation The link is configured as a member of a bundle that is shut down. Cause If the bundle is indeed shut down, this condition is normal. Action Clear the shutdown configuration on the bundle. |
State Link is marked individual by partner Explanation Peer device has not set the aggregatable bit in the LACPDUs it is sending. The Cisco IOS XR software does not support forming bundles with links that are not marked as aggregatable. Cause Indicates that the peer LACP status is defaulted, which means that LACP packets are not being received. Action Check to make sure that the peer is sending LACP packets and that the packets are delivered to the bundlemgr_local process on the line card where the port is located. |
State Link is in InSync state Explanation Indicates that LACP data exchanged between two peer devices is correct, and the link is compatible with other links already in the bundle. Typically, this state is transitory and occurs before the link moves to Collecting and then Distributing states. Cause If link remains in this state, the link may not be synchronized on the peer device. Possible causes are a misconfiguration or cabling error such that the ports on each device are not set up as members of the same bundle on both ends. Action Check the configuration and connectivity, and take the appropriate action. |
State Link is in Collecting state Explanation Indicates that LACP data exchanged between two peer devices is correct and that both devices are now synchronized. Typically, this state is transitory and occurs before the link moves to the Distributing state. Cause If the link remains in this state, the peer has not reached Collecting state. Possible causes are a fault with the peer, a loss of packets on the line, or a local software problem that is preventing the transmission to Distributing state. Action Check the peer status, and look for packet loss on the link. |
State Link exceeds maximum active limit Explanation You set the bundle maximum-active links to x on the bundle, and there are already x links active in the bundle. As a result, this link is held in standby state (either Detached or Collecting depending on whether the hot-standby option was specified). Cause Assuming that there are actually x active links in the bundle, this condition is normal. Action No action is required. |
State Link is in Distributing state Explanation The link is fully active, transmitting and receiving traffic. This reason is not usually displayed because it is the normal stable state. Cause This conditional is normal. Action No action is required. |
Related Commands
|
|
bundle id |
Adds a port to an aggregated interface (or bundle). |
show lacp bundle |
Displays detailed information about LACP ports and their peers. |
show interfaces |
Displays statistics for all interfaces configured on the router or on a specific node. |
show bundle Bundle-POS
To display information about a specific POS bundle, enter the show bundle Bundle-POS command in EXEC mode.
show bundle Bundle-POS bundle-id
Syntax Description
bundle-id |
Number of the POS bundle whose information you want to display. Replace bundle-id with a bundle identifier. Range is from 1 through 65535. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.2 |
This command was introduced on the Cisco CRS-1 router. |
Release 3.3.0 |
•The output for this command was modified. •The reasons keyword was added. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
The reasons keyword was removed. |
Usage Guidelines
To use this command, 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. 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 System Security Configuration Guide.
The show bundle Bundle-POS command output includes a reason field, which briefly describes both normal and error states of the link. For a listing of each state, along with an explanation about the state, reasons the link is in that state, and possible corrective actions you can take to resolve an error state, see Table 39.
Examples
The following is sample output from the show bundle Bundle-POS command:
RP/0/RP0/CPU0:router# show bundle Bundle-POS 5
State: 0 - Port is Detached. 1 - Port is Waiting.
2 - Port is Attached. 3 - Port is Collecting.
4 - Port is Distributing.
Minimum active Maximum active
B/W (Kbps) MAC address Links B/W (Kbps) Links
---------- -------------- ----- ---------- -----
Port State Port ID B/W (Kbps) MAC address
------------ ----- -------------- ---------- ---------------
PO0/0/0/0 0 0x8000, 0x0001 155520 N/A
PO0/0/0/1 0 0x8000, 0x0002 155520 N/A
PO0/0/0/2 0 0x8000, 0x0003 155520 N/A
Table 38 describes the significant fields shown in the display.
Table 38 show bundle Bundle-POS Field Descriptions
|
|
B/W (Kbps) |
Bundled interface bandwidth, in kilobits per second. |
MAC address |
MAC address of the bundle. |
Minimum links |
Minimum number of active links required before the specified bundle can be activated. |
active B/W (Kbps) |
Minimum amount of bandwidth required before a user can bring up the specified bundle. |
Maximum active links |
Maximum number of links that can be actively carrying traffic in the specified bundle. |
Port |
Port identifier, in the rack/slot/module/port format. |
State |
Current state of the specified port. |
Port ID |
Port identifier, in hexadecimal format. |
B/W (Kbps) |
Individual interface bandwidth, in kilobits. |
MAC address |
Mac address for the specified interface. |
reason |
Brief description of normal and error states of the link. For a listing of each state, along with an explanation about the state, reasons the link is in that state, and possible corrective actions you can take to resolve an error state, see Table 39. |
Table 39 POS Link State Explanation, Cause, and Action
|
State Selection logic has not yet been run for the bundle this link is a member of Explanation Status is not yet determined; process initialization is not complete. Cause In most cases, indicates that the bundlemgr_distrib process has not completed initialization after a restart or failover. If the command is run soon after a restart or failover, this behavior is expected. In other cases, indicates a problem during process initialization. Action Restart the bundlemgr_distrib process. If restarting this process does not work, restart the ifmgr process. |
State Link is down Explanation Interface or line protocol state is not operationally up. Possible explanations are that the port is shut down, the port is not connected to a peer or is shut down on the peer, or the L1 or L2 is affected by signalling problems. Cause A normal condition in which the link is shut down or not connected. Other causes include a fault with the line or a misconfiguration of the line protocol. Action Check the port configuration and status on both devices. |
State Link is being removed from the bundle Explanation Bundle membership configuration was removed from the link, and the effects of this action are still being processed. Cause If receiving this reason is transient, the condition is normal. If the reason is persistent, a problem is present. Action If reason is persistent, restart the bundlemgr_distrib process. |
State Link has wrong bandwidth Explanation The acceptable bandwidth for links in a bundle is determined by the existing configured links in a bundle. All links must have a bandwidth within a certain range of the first links added. This link has a bandwidth outside that range. Cause Link is improperly configured. All links must have a bandwidth within a certain range of each other. The range is determined by the platform. For the Cisco CRS-1 router, the range is four times, while the Cisco XR 12000 Series Router requires that the bandwidth is the same on all links. Action Reconfigure the links with the incorrect bandwidth. |
State Link is a loopback interface Explanation LACP detected that the peer device has the same LACP system ID as the local device. Cause A port is connected to another port on the same device, or the system ID settings of two devices are identical. This latter case usually indicates a failure to acquire a unique system MAC address from the backplane of the device. Action Check the cabling to ensure that two ports on the same device are not connected. If the connection is between two devices, then check that the backplane is correctly programmed with a base MAC address. |
State Link has wrong activity type Explanation The use of LACP on this link is inconsistent with the use of LACP on other links in the bundle. Some links are configured to run LACP, but others are not. Cause Link is improperly configured. All links must either be running LACP or not running LACP. Action Check the LACP configuration on the link, and reconfigure the setting as appropriate. |
State Link's bundle already has maximum number of members allowed Explanation A bundle can only have a certain number of members attached to it. This state indicates that more links are configured than can be attached. The Cisco CRS-1 router has a limit of 32, and the Cisco XR 12000 Series Router has a limit of 8. Cause Although the number of members is over-configured, this condition is normal. Action No action is required. If desired, you can remove the extra links from the bundle and assign them to a different bundle. |
State Link has wrong LAG ID Explanation The LAG ID of this link differs from that of the primary link, which indicates that the port on the peer device is not configured to be in the same bundle as the port to which the primary link is connected. It could also indicate that the connections are to different peer devices. Cause Link is improperly configured, or a cabling problem exists. Action Check the link configuration and connectivity, and modify as appropriate. |
State Link's bundle does not exist Explanation Link was configured to be a member of a bundle that does not exist. Cause Link is improperly configured. Action Configure the non-existent bundle interface, or reconfigure the link to be in the desired bundle. |
State Link's bundle has no primary link Explanation No link is configured to be a member of the bundle that is currently a candidate for aggregation. Cause To be considered a candidate for aggregation, a link must be up, and it must be compatible with previously configured links regarding bandwidth and LACP usage. For links running LACP, the links must also be full-duplex, and the partner must indicate an ability to form an aggregation. If there is no primary link, it is because there are no links that meet these criteria. Action Check all the links in a bundle against the criteria, and take the appropriate action. |
State Link's bundle is shut down Explanation The link is configured as a member of a bundle that is shut down. Cause If the bundle is indeed shut down, this condition is normal. Action Clear the shutdown configuration on the bundle. |
State Link is marked individual by partner Explanation Peer device has not set the aggregatable bit in the LACPDUs it is sending. The Cisco IOS XR software does not support forming bundles with links that are not marked as aggregatable. Cause Indicates that the peer LACP status is defaulted, which means that LACP packets are not being received. Action Check to make sure that the peer is sending LACP packets and that the packets are delivered to the bundlemgr_local process on the line card where the port is located. |
State Link is in InSync state Explanation Indicates that LACP data exchanged between two peer devices is correct, and the link is compatible with other links already in the bundle. Typically, this state is transitory and occurs before the link moves to Collecting and then Distributing states. Cause If link remains in this state, the link may not be synchronized on the peer device. Possible causes are a misconfiguration or cabling error such that the ports on each device are not set up as members of the same bundle on both ends. Action Check the configuration and connectivity, and take the appropriate action. |
State Link is in Collecting state Explanation Indicates that LACP data exchanged between two peer devices is correct and that both devices are now synchronized. Typically, this state is transitory and occurs before the link moves to the Distributing state. Cause If the link remains in this state, the peer has not reached Collecting state. Possible causes are a fault with the peer, a loss of packets on the line, or a local software problem that is preventing the transmission to Distributing state. Action Check the peer status, and look for packet loss on the link. |
State Link exceeds maximum active limit Explanation You set the bundle maximum-active links to x on the bundle, and there are already x links active in the bundle. As a result, this link is held in standby state (either Detached or Collecting depending on whether the hot-standby option was specified). Cause Assuming that there are actually x active links in the bundle, this condition is normal. Action No action is required. |
State Link is in Distributing state Explanation The link is fully active, transmitting and receiving traffic. This reason is not usually displayed because it is the normal stable state. Cause This conditional is normal. Action No action is required. |
Related Commands
|
|
bundle id |
Adds a port to an aggregated interface (or bundle). |
show lacp bundle |
Displays detailed information about LACP ports and their peers. |
show interfaces |
Displays statistics for all interfaces configured on the router or on a specific node. |
show lacp bundle
To display detailed information about Link Aggregation Control Protocol (LACP) ports and their peers, enter the show lacp bundle command in EXEC mode.
show lacp bundle [Bundle-Ether bundle-id | Bundle-POS bundle-id]
Syntax Description
Bundle-Ether bundle-id |
(Optional) Specifies the number of the Ethernet bundle you want to display. Range is 1 through 65535. |
Bundle-POS bundle-id |
(Optional) Specifies the number of the POS bundle whose information you want to display. Range is 1 through 65535. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.2 |
This command was introduced on the Cisco CRS-1 router. |
Release 3.3.0 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
This command was first supported on the Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, 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. 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 System Security Configuration Guide.
Examples
The following example shows how to display LACP information for a specific Ethernet Bundle:
RP/0/RP0/CPU0:router# show lacp bundle Bundle-Ether 1
Flags: A - Device is in Active mode. P - Device is in Passive mode.
S - Device sends PDUs at slow rate. F - Device sends PDUs at fast rate.
D - Port is using default values for partner information
E - Information about partner has expired
State: 0 - Port is Not Aggregatable. 1 - Port is Out Of Sync with peer.
2 - Port is In Sync with peer. 3 - Port is Collecting.
4 - Port is Collecting and Distributing.
Minimum active Maximum active
B/W (Kbps) MAC address Links B/W (Kbps) Links
---------- -------------- ----- ---------- -----
0 0800.453a.651d 1 620000 32
Port State Flags Port ID Key System-ID
------------ ----- ----- -------------- ------ -------------------------
Gi0/0/2/0 1 ASDE 0x8000, 0x0001 0x0001 0x8000, 08-00-45-3a-65-01
PEER 0 PSD 0xffff, 0x0000 0x0000 0xffff, 00-00-00-00-00-00
Table 40 describes the significant fields shown in the display.
Table 40 show lacp bundle Field Descriptions
|
|
Flags |
Describes the possible flags that may apply to a device or port, under the "Flags" field. |
State |
Describes the possible flags that may apply the port state, under the "State" field. |
Port |
Port identifier, in the rack/slot/module/port notation. |
State |
Provides information about the state of the specified port. Possible flags are: •0 - Port is not aggregatable. •1 - Port is out of sync with peer. •2 - Port is in sync with peer. •3 - Port is Collecting. •4 - Port is Collecting and Distributing |
Flags |
Provides information about the state of the specified device or port. Possible flags are: •A - Device is in Active mode. •P - Device is in Passive mode. •S - Device requests peer to send PDUs at a slow rate. •F - Device requests peer to send PDUs at a fast rate. •D - Port is using default values for partner information. •E - Information about partner has expired. |
Port ID |
Port identifier, expressed in the format Nxnnnn. N is the port priority, and nnnn is the port number assigned by the sending router. |
Key |
2-byte number associated with the specified link and aggregator. Each port assigned an operational Key. The ability of one port to aggregate with another is summarized by this key. Ports which have the same key select the same bundled interface. The system ID, port ID and key combine to uniquely define a port within a LACP system. |
System-ID |
System identifier. The System ID is a LACP property of the system which is transmitted within each LACP packet together with the details of the link. |
Related Commands
show lacp counters
To display Link Aggregation Control Protocol (LACP) statistics, enter the show lacp counters command in EXEC mode.
show lacp counters [Bundle-Ether bundle-id | Bundle-POS bundle-id]
Syntax Description
Bundle-Ether bundle-id |
Specifies the Ethernet bundle whose counters you want to display. Replace bundle-id with a bundle identifier. Range is from 1 through 65535. |
Bundle-POS bundle-id |
Specifies the POS bundle whose counters you want to display. Replace bundle-id with a bundle identifier. Range is from 1 through 65535. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.2.0 |
This command was introduced on the Cisco CRS-1 router. |
Release 3.3.0 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
This command was first supported on the Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, 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. 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 System Security Configuration Guide.
Examples
The following example shows how to display LACP counters on an Ethernet bundle:
RP/0/RP0/CPU0:router# show lacp counters bundle-ether 4
Port Sent Received Received Resp. Sent Last Cleared
------------- ---------------------- ---------------------- ------------
Port Excess Excess Pkt Errors
------------- ---------- ---------- ----------
Table 41 describes the significant fields shown in the display.
Table 41 show lacp counters Field Descriptions
|
|
LACPDUs |
Provides the following statistics for Link Aggregation Control Protocol data units (LACPDUs): •Port •Sent •Received •Last Cleared •Excess •Pkt Errors |
Marker |
Provides the following statistics for marker packets: •Received •Resp. Sent •Last Cleared •Excess •Pkt Errors Note The Marker Protocol is used by 802.3ad bundles to ensure that data no longer is transmitted on a link when a flow is redistributed away from that link. |
Related Commands
|
|
clear lacp counters |
Clears LACP counters for all members of all bundles, all members of a specific bundle, or for a specific port. |
show lacp port
To display detailed information about Link Aggregation Control Protocol (LACP) ports, enter the show lacp port command in EXEC mode.
show lacp port [GigabitEthernet interface-path-id | TenGigE interface-path-id | POS interface-path-id]
Syntax Description
GigabitEthernet |
(Optional) Gigabit Ethernet interface. Use the interface-path-id argument to specify the Gigabit Ethernet interface whose LACP counters you want to display. |
TenGigE |
(Optional) Ten Gigabit Ethernet interface. Use the interface-path-id argument to specify the Ten Gigabit Ethernet interface whose LACP counters you want to display. |
POS |
(Optional) Packet-over-SONET/SDH (POS) interface. Use the interface-path-id argument to specify the POS interface whose LACP counters you want to display. |
interface-path-id |
Physical interface or virtual interface. Note Use the show interfaces command to see a list of all interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.2 |
This command was introduced on the Cisco CRS-1 router. |
Release 3.3.0 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
This command was first supported on the Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, 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. 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 System Security Configuration Guide.
For the interface-path-id argument, if specifying a physical interface, the naming notation is rack/slot/module/port. The slash between values is required as part of the notation. An explanation of each component of the naming notation is as follows:
•rack: Chassis number of the rack.
•slot: Physical slot number of the line card.
•module: Module number. A physical layer interface module (PLIM) is always 0.
•port: Physical port number of the interface.
Examples
The following example shows how to display LACP port information for all link bundles on a router:
RP/0/RP0/CPU0:router# show lacp port
Flags: A - Device is in Active mode. P - Device is in Passive mode.
S - Device sends PDUs at slow rate. F - Device sends PDUs at fast rate.
D - Port is using default values for partner information
E - Information about partner has expired
State: 0 - Port is Not Aggregatable. 1 - Port is Out Of Sync with peer.
2 - Port is In Sync with peer. 3 - Port is Collecting.
4 - Port is Collecting and Distributing.
Minimum active Maximum active
B/W (Kbps) MAC address Links B/W (Kbps) Links
---------- -------------- ----- ---------- -----
0 0800.453a.651d 1 620000 32
Port State Flags Port ID Key System-ID
------------ ----- ----- -------------- ------ -------------------------
Gi0/0/2/0 1 ASDE 0x8000, 0x0001 0x0001 0x8000, 08-00-45-3a-65-01
PEER 0 PSD 0xffff, 0x0000 0x0000 0xffff, 00-00-00-00-00-00
Table 42 describes the significant fields shown in the display.
Table 42 show lacp port Field Descriptions
|
|
Port |
Identifies the LACP port whose information is displayed. The port number is expressed in the rack/slot/module/port notation. |
State |
Provides information about the state of the specified device or port. Possible flags are: •A - Device is in Active mode. •P - Device is in Passive mode. •S - Device requests peer to send PDUs at a slow rate. •F - Device requests peer to send PDUs at a fast rate. •D - Port is using default values for partner information. •E - Information about partner has expired. |
Flags |
Provides information about the state of the specified port. Possible flags are: •0 - Port is not aggregatable. •1 - Port is out of sync with peer. •2 - Port is in sync with peer. •3 - Port is Collecting. •4 - Port is Collecting and Distributing |
Port ID |
Port identifier, expressed in the following format: Nxnnnn. N is the port priority, and nnnn is the port number assigned by the sending router. |
Key |
2-byte number associated with the specified link and aggregator. Each port assigned an operational Key. The ability of one port to aggregate with another is summarized by this key. Ports which have the same key select the same bundled interface. The system ID, port ID and key combine to uniquely define a port within a LACP system. |
System-ID |
System identifier. The System ID is an LACP property of the system which is transmitted within each LACP packet together with the details of the link. |
Related Commands
show lacp system-id
To display the local system ID used by the Link Aggregation Control Protocol (LACP), enter the show lacp system-id command in EXEC mode.
show lacp system-id
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.2 |
This command was introduced on the Cisco CRS-1 router. |
Release 3.3.0 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
This command was first supported on the Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, 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. 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 System Security Configuration Guide.
Note The System ID and details about the specific link are transmitted within each LACP packet.
Examples
The following example shows how to display the system ID used by the LACP:
RP/0/RP0/CPU0:router# show lacp system-id
-------- -----------------
Table 43 describes the significant fields shown in the display.
Table 43 show lacp system-id Field Descriptions
|
|
Priority |
Priority for this system. A lower value is higher priority. |
MAC Address |
MAC address associated with the LACP system ID. |
Related Commands