Interface and Hardware Component Command Reference for Cisco NCS 5500 Series, Cisco NCS 540 Series, and Cisco NCS 560 Series Routers

bundle-hash

To display the source and destination IP addresses for the member links, distributed by the load balancing feature, in a multilink interface bundle, use the bundle-hash command in .

bundle-hash {Bundle-Ether bundle-id | members {TenGigabitEthernet | HundredGigabitEthernet} 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.

ibundle-id

Number from 1 to 65535 that identifies a particular bundle.

members

Identifies specific bundle member links for which you want to calculate load balancing.

TenGigE

Specifies the 10 Gigabit Ethernet interface for which you want to calculate load balancing.

HundredGigE

Specifies the 100 Gigabit Ethernet interface for which you want to calculate load balancing.

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.

Command Default

No default behavior or values

Command Modes

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

Bundle interface traffic is distributed over the various member links of a bundle according to a hash function. The bundle-hash command allows you to determine which bundle member link will carry a particular flow of traffic.

You can use the bundle-hash command to get these information:

Which members are used for a specified source/destination address pair, such as 10.10.10.1 20.20.20.1
The destination IP address for a specified source IP address on a specified member.
The load balancing distribution–how many times the members of a bundle are used for a specified range of IP addresses.

The bundle-hash command does not display all possible IP addresses in an entire series. It stops displaying addresses after all the addresses for all the members of the bundle have been displayed once.

The bundle-hash command invokes a utility that initially prompts you to select some options. Based on the options you select, the utility prompts you more options to select. The initial options to select are as follows:

L3/3-tuple or L4/7-tuple
Single pair or Range
IPv4 or IPv6

The bundle-hash command utility prompts you for these options as follows:

Specify load-balance configuration (L3/3-tuple or L4/7-tuple) (L3,L4):
Single SA/DA pair (IPv4,IPv6) or range (IPv4 only): S/R [S]:
Enter bundle type IP V4 (1) or IP V6 (2):
Enter source IP V4 address:
Enter destination IP V4 address:
Compute destination address set for all members? [y/n]:
Enter subnet prefix for destination address set:
Enter bundle IP V4 address [10.10.10.10]:

You may also be prompted to make further option choices depending on your selections.

You can use the show bundle command to get IP address information.

The below table provides a general summary of the options and the information you need to provide for each selected option. The actual information that you need to provide depends on the selections you make and may vary from the information provided in the below table.

Table 1. bundle-hash Command Options
Option	Information You Need to Provide
L3/3-tuple	L3 information: Source IP address Destination IP address Destination subnet prefix Bundle IP address
L4/7-tuple	L3 information: Source IP address Destination IP address Protocol L4 information: Source port Destination port Platform-related information: Router ID Ingress interface
Single pair	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. The default is single mode. While in single mode, you may receive the following prompt:
Range	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.
IPv4	IPv4 addresses
IPv6	IPv6 addresses


		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.

Task ID


Task ID	Operations
bundle	read

Examples

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 HundredGigE0/6/0/7

Destination address set for subnet 10.0.0.0:
  10.0.0.6 hashes to link HundredGigE0/1/0/0
  10.0.0.8 hashes to link HundredGigE0/6/0/5
  10.0.0.12 hashes to link HundredGigE0/6/0/6
  10.0.0.2 hashes to link HundredGigE0/6/0/7
  10.0.0.1 hashes to link HundredGigE0/1/0/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 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...

Total number of hits 20
Member HundredGigE0/1/0/0 has 6 hits
Member HundredGigE0/6/0/5 has 2 hits
Member HundredGigE0/6/0/6 has 2 hits
Member HundredGigE0/6/0/7 has 9 hits
Member HundredGigE0/1/0/1 has 1 hits

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
 
  Ingress interface --
  - physical interface format: [ TenGigE |  HundredGigE]R/S/I/P
  - bundle interface format:   [ Bundle-Ether]bundle-id
  Enter ingress interface: HundredGigE0/2/0/3
 
  Enter L4 protocol (TCP,UDP,SCTP,L2TPV3,NONE): UDP
  Enter src port: 1000
  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 HundredGigE0/3/0/6
 
Another? [y]: y
 
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
 
  Ingress interface --
  - physical interface format: [HundredGigE | TenGigE ]R/S/I/P
  - bundle interface format:   [ Bundle-Ether ]bundle-id
  Enter ingress interface [HundredgigE0/2/0/3]: HundredGigE0/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 HundredGigE0/3/0/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 HundredGigE0/3/0/6
  S/D pair 172.20.180.167:1000/172.30.15.6:2000 hashes to link HundredGigE0/2/0/1
  S/D pair 172.20.180.167:1000/172.30.15.3:2000 hashes to link HundredGigE0/2/0/2
  S/D pair 172.20.180.167:1000/172.30.15.5:2000 hashes to link HundredGigE0/2/0/3
 
Another? [y]: n

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`	Number of the bundle (from 1 to 65535) on which you want to add a port.
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 configure an Etherchannel link over the port (no LACP running 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.

Command Default

The default setting is mode on.

Command Modes

Interface configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

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.

Task ID


Task ID	Operations
bundle	read, write

Examples

This example shows how to add a port onto a bundle:


RP/0/RP0/CPU0:router(config)# interface TenGigE 0/1/0/0
RP/0/RP0/CPU0:router(config-if)# bundle id 1

This example shows how to add an active LACP port onto an aggregated interface (or bundle):


RP/0/RP0/CPU0:router(config)# interface TenGigE 0/6/0/1
RP/0/RP0/CPU0:router(config-if)# bundle id 5 mode active

bundle maximum-active links

To designate one active link and one link in standby mode 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, up to the maximum supported on the platform. The range is 1 to 64.
hot-standby	Modifies some default timeouts, such as wait-while timer and suppress-flaps, to avoid bundle-level flaps when the highest priority link fails or recovers.

Command Default

No default behavior or values

Command Modes

Interface configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

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:

The misconfiguration or inconsistent configuration with a remote side can be causing traffic loss even though the bundle is up. We recommend that you use LACP protocol to better protect against the misconfiguration.

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) forthe 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.)

Task ID


Task ID	Operations
bundle	read, write

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

Examples

The following example shows how to set default values for timeouts, to avoid bundle-level flaps when the highest priority link fails or recovers:

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

Examples

The following example shows how to display information about Ethernet bundle 5:


RP/0/RP0/CPU0:router(config)# show Bundle-Ether 5
 

State: 0 - Port is Detached. 1 - Port is Waiting.
       2 - Port is Attached. 3 - Port is Collecting.
       4 - Port is Distributing.

Bundle-Ether 5
                                Minimum active     Maximum active
  B/W (Kbps)   MAC address      Links  B/W (Kbps)  Links
  ----------   --------------   -----  ----------  -----
10000000001d.e5eb.2898111
   
  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.

Examples

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)# show Bundle-Ether 5
 

State: 0 - Port is Detached. 1 - Port is Waiting.
       2 - Port is Attached. 3 - Port is Collecting.
       4 - Port is Distributing.

Bundle-Ether 5
                                Minimum active     Maximum active
  B/W (Kbps)   MAC address      Links  B/W (Kbps)  Links
  ----------   --------------   -----  ----------  -----
10000000001d.e5eb.2898111

  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.

Examples

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)#

The following example shows how to display information about Ethernet bundle 5:

RP/0/RP0/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.

Bundle-Ether 5
                                Minimum active     Maximum active
  B/W (Kbps)   MAC address      Links  B/W (Kbps)  Links
  ----------   --------------   -----  ----------  -----
10000000001d.e5eb.2898111

  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 the port is distributing. The state of the standby link is 3, which indicates that the port is collecting.

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 is equivalent to the combined bandwidths of 8 TenGigabitEthernet interfaces.

Command Default

The default setting is kbps = 1.

Command Modes

Interface configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID


Task ID	Operations
bundle	read, write

Examples

This 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

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`	Minimum number of active links allowed in the specified bundle. The range is from 1 through 64.

Command Default

No default behavior or values

Command Modes

Interface configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID


Task ID	Operations
bundle	read, write

Examples

The following example shows how to set the number of active links required to bring up a specific bundle. In this example, the user configures Ethernet bundle 5 so that 2 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

bundle port-priority

To configure priority for a port , enter the bundle port-priority command in interface configuration mode. To return to the default LACP 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 1 through 65535.

Command Default

priority : 32768

Command Modes

Interface configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

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.

Task ID


Task ID	Operations
bundle	read, write

Examples

The following example shows how to configure LACP priority on a port:


RP/0/RP0/CPU0:router# config 
RP/0/RP0/CPU0:router(config)# interface HundredGigE 0/1/0/1
RP/0/RP0/CPU0:router(config-if)# bundle port-priority 1

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 .

clear lacp counters [bundle Bundle-Ether bundle-id| bundle-id | port {HundredGigE interface-path-id | TenGigE 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.

port

(Optional) Clears all LACP counters on the specified bundle or interface.

HundredGigE

(Optional) Hundred Gigabit Ethernet interface. Use the interface-path-id argument to specify the interface whose LACP counters you want to clear.

TenGigE

(Optional) Ten Gigabit Ethernet interface. Use the interface-path-id argument to specify the 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.

Command Default

No default behavior or values

Command Modes

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

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:
- If specifying a virtual interface, the number range varies, depending on interface type.

Task ID


Task ID	Operations
bundle	execute
basic-services	read, write

Examples

The following example shows how to clear LACP counters:


RP/0/RP0/CPU0:router# clear lacp counters

hw-module profile load-balance algorithm

To modify the hashing algorithm that is used for ECMP and bundle member selection, use the hw-module profile load-balance algorithm command in XR Config mode.

hw-module profile load-balance algorithm { L3-only | PPPoE | gtp | gtp-mpls | inner-l2-field | ip-tunnel | layer2 | mpls-lsr-ler | mpls-lsr-ler-optimized | mpls-safe-speculative-parsing }

Syntax Description


ip-tunnel	Allows the hashing algorithm to use the outer IPv4 GRE header even while doing an IP tunnel decapsulation.
layer2	Allows the hashing algorithm to use the inner IP header information while doing layer 2 forwarding with inner payload as MPLS.
gtp	Allows hashing based on the tunnel id in GTP-U packets.
gtp-mpls	Allows hashing based on the tunnel id in GTP-U packets intead of Layer 4 packets when underlay network is MPLS.
mpls-safe-speculative-parsing	Allows hashing based on the first nibble of the MAC DA address.
pppoe	Allows hashing based on inner IPv4 or IPv6 headers for PPPoE packets. We recommend enabling this hashing on head and tail nodes.
L3-Only	Allows hashing for L3 header only. We recommend enabling this hashing when majority of traffic is fragmented.
mpls-lsr-ler	Allows hashing in Label Edge Router (LER) and Label Switched Routers (LSRs) with MPLS traffic. This profile is recommended to be used when the following traffic flows are prominent: IPv4 pop and lookup flows (EthoMPLS2/3oIPv4oL4) with L4 as TCP or UDP IPv6 pop and lookup flows (EthoMPLS2/3oIPv6oXX) with L4 as TCP or UDP
mpls-lsr-ler-optimized	Allows optimized hashing in LER and LSR with MPLS IPv6 traffic. This profile is recommended to be used when the following traffic flows are prominent: 4 Label IPv6 flows (EthoMPLS4/6oIPv6) IPv6 pop and lookup flows (EthoMPLS2/3oIPv6oXX) with L4 as non-TCP/UDP (for example, no next header, GRE)
inner-L2-field	Allows the hashing algorithm to use the inner ethernet fields of the source MAC and destination MAC addresses.

Command Default

No load-balancing profile is configured.

Command Modes

XR Config mode

Command History


Release	Modification
7.10.1	The mpls-lsr-ler-optimized keyword was introduced.
7.7.2	The inner-l2-field keyword was introduced.
6.5.1	This command was modified.
6.3.2	This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Without control-word, L2VPN traffic is considered to be IPv4 or IPv6 traffic depending on the presence of nibble 4 or nibble 6 in the payload after the last label in the traffic. The matching offset fields are considered for load-balancing hash calculation. This may cause hashing of a single flow to different links resulting in decrease of end user throughput.

Note

Only one of the load-balancing profiles should be enabled at a time. The last configured CLI takes precedence.
While adding or removing the hw-module profile load-balance algorithm mpls-lsr-ler and hw-module profile load-balance algorithm mpls-lsr-ler-optimized commands, there is no need to reload the router.
While adding or removing the hw-module profile load-balance algorithm ip-tunnel and hw-module profile load-balance algorithm PPPoE commands, you must reload the router.
The hw-module profile segment-routing srv6 is mutually exclusive with hw-module profile load-balance algorithm PPPoE and hw-module profile load-balance algorithm ip-tunnel commands.

Task ID


Task ID	Operation
bundle	read, write

Examples

This example shows how to configure the hw-module profile load-balance algorithm command to use the outer IPv4 GRE header for hashing even while doing an IP tunnel decapsulation.


RP/0/RP0/CPU0:Router(config)# hw-module profile load-balance algorithm ip-tunnel

This example shows how to configure the hw-module profile load-balance algorithm command to use the tunnel id in GTP-U packets for hashing.


RP/0/RP0/CPU0:Router(config)# hw-module profile load-balance algorithm gtp

This example shows how to configure the hw-module profile load-balance algorithm command to hash the L2VPN traffic to the right egress link.

RP/0/RP0/CPU0:Router(config)# hw-module profile load-balance algorithm mpls-safe-speculative-parsing

This example shows how to configure the hw-module profile load-balance algorithm command to hash the IPv6 traffic with four MPLS labels to ensure optimized load-balancing.

RP/0/RP0/CPU0:ios(config)#hw-module profile load-balance algorithm mpls-lsr-ler-optimized

hw-module profile bundle-hash

To customize the hash key used in per-packet load balancing on a link aggregation group (LAG) or bundle interfaces, use the hw-module profile bundle-hash command in global configuration mode.

hw-module profile bundle-hash { hash-index index location location | ignore-ingress-port | per-packet-round-robin }

Syntax Description


hash-index	Configures the hash polynomial for the ASIC to customize the LAG load-balancing algorithm.
`index`	Specifies the hashing index.
location	Specifies that the location of the bundle-hash polynomial configuration follows.
`location`	Specifies the location of the bundle-hash polynomial configuration.
ignore-ingress-port	Excludes ingress traffic port from the hash-key computation.
per-packet-round-robin	Enables egressing traffic in a per-packet round robin manner across all LAG or bundle members.

Command Default

No default behavior or values

Command Modes

Global Configuration

Command History


Release	Modification
Release 7.3.1	This command was modified to introduce: hash-index per-packet-round-robin
Release 7.1.2	This command was introduced.

Usage Guidelines

The hw-module profile bundle-hash command is applicable to NCS 5500 fixed port routers and NCS 5500 modular routers with NCS 5500 line cards.
The hw-module profile bundle-hash ignore-ingress-port command configures the hash-key computation for LAG and bundle interfaces load balancing to exclude ingress traffic port.

The hw-module profile bundle-hash per-packet-round-robin command enables the router to egress traffic in a per-packet round robin method across all LAG and bundle interfaces. This command suppresses any internal load-balancing algorithms and uses only the per-packet round robin method.

Caution

Use the hw-module profile bundle-hash per-packet-round-robin command for debug purposes only. Do not use the command in a production environment as it could cause an out-of-order (OOO) delivery of packets.

The hw-module profile bundle-hash ignore-ingress-port and hw-module profile bundle-hash per-packet-round-robin commands are configured at global level and is applicable to all line cards installed in the router.
The hw-module profile bundle-hash hash-index command enables you to customize the LAG load-balancing algorithm by changing the hash polynomial used by the load-balancing ASIC. The router continues to use the existing 7-tuples algorithm, but you can change the polynomial value used internally.
The hw-module profile bundle-hash hash-index command supports the following hash-indices:
- 1 Use Polynomial value 0x8011
- 10 Use LB-Key-Pkt-Data directly
- 11 Use counter incremented every packet
- 12 Use counter incremented every two clocks
- 2 Use Polynomial value 0x8423
- 3 Use Polynomial value 0x8101
- 4 Use Polynomial value 0x84A1
- 5 Use Polynomial value 0x9019
The hw-module profile bundle-hash hash-index command is applicable only to the particular location or line card specified while configuring this command.

Task ID


Task ID	Operations
bundle	read

Examples

The following example shows how to configure hash-index using hw-module profile bundle-hash :


Router# configure
Router (config)# hw-module profile bundle-hash hash-index 10 location 0/0/CPU0
Router (config)# commit

Examples

The following example shows how to configure ignore-ingress-port using hw-module profile bundle-hash :


Router# configure
Router (config)# hw-module profile bundle-hash ignore-ingress-port
Router (config)# commit

Examples

The following example shows how to configure per-packet-round-robin using hw-module profile bundle-hash :


Router# configure
Router (config)# hw-module profile bundle-hash per-packet-round-robin
Router (config)# commit

interface (bundle)

To create a new bundle and enter interface configuration mode for that bundle, use the interface (bundle) command in XR Config mode. To delete a bundle, use the no form of this command.

interface Bundle-Ether bundle-id

no interface Bundle-Ether bundle-id

Syntax Description


Bundle-Ether	Specifies or creates an Ethernet bundle interface.
`bundle-id`	Number from 1 to 65535 that identifies a particular bundle.

Command Default

No bundle interface is configured.

Command Modes

XR Config mode

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID


Task ID	Operation
bundle	read, write

Examples

This example shows how to create an Ethernet bundle and enter interface configuration mode:


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

lacp packet-capture

To capture LACP packets so that their information can be displayed by the show lacp packet-capture command, use the lacp packet-capture command in .

{lacp packet-capture HundredGigE interface-path-id | TenGigE interface-path-id number-of-packets}

To stop capturing LACP packets or to clear captured LACP packets, use the lacp packet-capture stop or lacp packet-capture clear command in .

{lacp packet-capture [bundle-ether bundle-id] [HundredGigE interface-path-id] [TenGigE interface-path-id] clear | stop}

Syntax Description

bundle-ether

Ethernet bundle interface specified by bundle-id .

HundredGigE

Hundred Gigabit Ethernet interface specified by interface-path-id .

TenGigE

Ten Gigabit Ethernet interface specified by interface-path-id .

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.

bundle-id

Number specifying the bundle interface. The range is 1 to 65535.

number-of-packets

Number of packets to capture.

clear

Clears all currently captured packets.

stop

Stops capturing packets.

Command Default

The default (no parameters) executes globally for all interfaces on the line card.

Command Modes

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

The lacp packet-capture command captures transmitted and received LACP packets on a single bundle member interface. The contents of these packets can then be displayed by the show lacp packet-capture command. If the lacp packet-capture command is not issued, the show lacp packet-capture command does not display any information.

The lacp packet-capture command continues capturing LACP packets until the stop keyword is issued for that port or that bundle. Captured packets are stored and continue to be displayed until the clear keyword is issued for that port or that bundle.

LACP packets can only be captured for one port on a line card at a time. Starting a packet capture on a port implicitly stops and clears all packet-captures on all other ports on that line card.

To stop capturing LACP packets before the specified number of packets have been captured, issue the stop keyword.

If stop is specified for a single interface, packet capturing is stopped only on that interface.

If stop is specified for a bundle interface, packet capturing is stopped on all members of that bundle.

If stop is specified globally (the default - no parameters), packet capturing is stopped on all bundle interfaces on the router.

To clear all captured LACP packets that are stored for an interface, issue the clear keyword.

If clear is specified for a single interface, packets are cleared only on that interface.

If clear is specified for a bundle interface, packets are cleared on all members of that bundle.

If clear is specified globally (the default - no parameters), packets are cleared on all bundle interfaces on the router.

Task ID


Task ID	Operations
bundle	read

Examples

This example shows how to stop LACP packets on an interface:


RP/0/RP0/CPU0:router# lacp packet-capture HundredGigE 0/2/0/0 100

The following example shows how to stop capturing LACP packets on a Gigabit Ethernet interface:


RP/0/RP0/CPU0:router# lacp packet-capture HundredGigE 0/2/0/0 stop

lacp period short

To enable a short period time interval for the transmission and reception of Link Aggregation Control Protocol (LACP) packets, use the lacp period short command in interface configuration mode. To return to the default short period, use the no form of this command.

lacp period short [receive interval] [transmit interval]

no lacp period short [receive interval] [transmit interval]

Syntax Description


receive `interval`	Time interval (in milliseconds) for receiving LACP packets when LACP short period is enabled. The range is 100 to 1000 and must be multiples of 100, such as 100, 200, 300, and so on.
transmit `interval`	Time interval (in milliseconds) for transmitting LACP packets when LACP short period is enabled. The range is 100 to 1000 and must be multiples of 100, such as 100, 200, 300, and so on.

Command Default

The default is 1000.

Command Modes

Interface configuration

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

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.

Note

Starting with Cisco IOS XR Software Release 7.1.1, the lacp period short receive and lacp period short transmit commands are deprecated. Use the lacp period <time in milliseconds> command to configure LACP receive and transmit time. Before using this command, you must first execute lacp cisco enable command in the bundle interface mode. Without lacp cisco enable command, the members may still transmit at the standard interval of 1 second.

Task ID


Task ID	Operations
bundle	read, write

Examples

The following example shows how to enable a default Link Aggregation Control Protocol (LACP) short period on an interface:


RP/0/RP0/CPU0:router# config 
RP/0/RP0/CPU0:router(config)# interface HundredGigE 0/1/0/0 
RP/0/RP0/CPU0:router(config-if)# lacp period short 
RP/0/RP0/CPU0:router(config-if)# commit

The following example shows how to configure custom Link Aggregation Control Protocol (LACP) short period transmit and receive intervals at both ends of a connection:


RP/0/RP0/CPU0:router# config 
RP/0/RP0/CPU0:router(config)# interface HundredGigE 0/1/0/0 
RP/0/RP0/CPU0:router(config-if)# lacp period short transmit 500 
RP/0/RP0/CPU0:router(config-if)# commit


RP/0/RP0/CPU0:router# config 
RP/0/RP0/CPU0:router(config)# interface HundredGigE 0/1/0/0 
RP/0/RP0/CPU0:router(config-if)# lacp period short transmit 500 
RP/0/RP0/CPU0:router(config-if)# commit


RP/0/RP0/CPU0:router# config 
RP/0/RP0/CPU0:router(config)# interface HundredGigE 0/1/0/0 
RP/0/RP0/CPU0:router(config-if)# lacp period short receive 500 
RP/0/RP0/CPU0:router(config-if)# commit


RP/0/RP0/CPU0:router# config 
RP/0/RP0/CPU0:router(config)# interface HundredGigE 0/1/0/0 
RP/0/RP0/CPU0:router(config-if)# lacp period short receive 500  
RP/0/RP0/CPU0:router(config-if)# commit

lacp system priority

To configure the priority for the current system, enter the lacp system priority command in XR Config mode mode.

lacp system priority priority

Syntax Description


`priority`	Priority for this system. Replace `priority` with a number. Range is from 1 through 65535. A lower value is higher priority.

Command Default

The default setting is priority = 32768.

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

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.

Task ID


Task ID	Operations
bundle	read, write

Examples

The following example shows how to configure an LACP priority of 100 on a router:



RP/0/RP0/CPU0:router(config)# lacp system priority 100

The following example shows how to configure an LACP priority of 10 and MAC address on the Bundle-Ether interface:



RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface Bundle-Ether 1
RP/0/RP0/CPU0:router(config-if)# lacp system priority 10
RP/0/RP0/CPU0:router(config-if)# lacp system mac 00c1.4c00.bd15
RP/0/RP0/CPU0:router(config-if)# commit

show bundle

To display information about all bundles or a specific bundle of a particular type, use the show bundle command in XR EXEC mode.

show bundle [Bundle-Ether bundle-id]

Syntax Description


Bundle-Ether	Displays information for the specified Ethernet bundle.
`bundle-id`	Number from 1 to 65535 that identifies a particular bundle.

Command Default

Information is displayed for all configured bundles.

Command Modes

XR EXEC mode

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

To see information for all bundles configured on the router, use the show bundle form of the command.

To see information for a specific bundle, use the show bundle Bundle-Etherbundle-id form of the command with the number of the configured bundle.

Task ID


Task ID	Operation
bundle	read

Examples

This example shows output for all bundle interfaces that are configured on the router:

Note

Though mLACP related fields are shown in the output, MC-LAG is not currently supported.

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

 Bundle-Ether1
  Status:                                    Up
  Local links <active/standby/configured>:   2 / 0 / 2
  Local bandwidth <effective/available>:     20000000 (20000000) kbps
  MAC address (source):                      ea74.b3bd.f484 (Chassis pool)
  Inter-chassis link:                        No
  Minimum active links / bandwidth:          1 / 1 kbps
  Maximum active links:                      64
  Wait while timer:                          2000 ms
  Load balancing:                            
    Link order signaling:                    Not configured
    Hash type:                               Default
    Locality threshold:                      None
  LACP:                                      Operational
    Flap suppression timer:                  Off
    Cisco extensions:                        Disabled
    Non-revertive:                           Disabled
  mLACP:                                     Not configured
  IPv4 BFD:                                  Not configured
  IPv6 BFD:                                  Not configured

  Port                  Device           State        Port ID         B/W, kbps
  --------------------  ---------------  -----------  --------------  ----------
  Te0/0/0/0/0           Local            Active       0x8000, 0x0006    10000000
      Link is Active
  Te0/0/0/0/1           Local            Active       0x8000, 0x0005    10000000
      Link is Active

Table 2. show bundle Field Descriptions
Field	Description
Bundle-typenumber	Full name of the bundle interface, where type is Ether (Ethernet) , followed by the configured number of the bundle.
Status:	State of the bundle on the local device, with one of the following possible values: Admin down—The bundle has been configured to be shut down. Bundle shut—The bundle is holding all links in Standby state and will not support any traffic. Down—The bundle is operationally down. It has no Active members on the local device. mLACP cold standby—The bundle is acting as a multichassis LACP Standby device, but the higher layers are not synchronized. mLACP hot standby—The bundle is Up on the mLACP peer device, and the local device is ready to take over if that bundle goes down on the peer. Nak—The local and peer devices cannot resolve a configuration error. Partner down—The partner system indicates that the bundle is unable to forward traffic at its end. PE isolated—The bundle is isolated from the core. Up—The bundle has Active members on this device.
Local links <active/standby/configured>:	The number of links on the device (from 0 to the maximum number of supported links for the bundle) in the format x / y / z, with the following values: x—Number of links in Active state on the bundle. y—Number of links in Standby state on the bundle. z—Total number of links configured on the bundle.
Local bandwidth <effective/available>:	Bandwidth characteristics on the bundle in kilobits per second (kbps) in the format x / y, with the following values: x—Current bandwidth of the bundle (this effective bandwidth might be limited by configuration). y—Available bandwidth of the bundle that is the sum of the bandwidths of all of the locally active links.
MAC address (source):	Layer 2 MAC address on the bundle interface in the format xxxx.xxxx.xxxx. The (source) of the address is shown in parentheses with the following possible values: Interface name—The MAC address is from the displayed member interface type and path. Configured—The MAC address is explicity configured. Chassis pool—The MAC address is from the available pool of addresses for the chassis. [unknown MAC source 0]—No MAC address could be assigned to the bundle. (You might see this display if you have not completed your bundle configuration.)
Minimum active links / bandwidth:	Displays the following information in the format x / y kbps, with the following values: x—Minimum number of active links (from 1 to the maximum number of links supported on the bundle) that are required for the bundle to be operative. y—Minimum total bandwidth on active links (in kbps) that is required for the bundle to be operative. (partner)—Shows that the peer system's value is in use.
Maximum active links:	Maximum number of links (from 1 to the maximum supported on a bundle) that can be active on the bundle.
Wait-while timer:	Amount of time (in milliseconds) that the system allows for the Link Aggregation Control Protocol (LACP) to negotiate on a "working"link, before moving a "protect"or backup link to Standby state.
Load balancing:	Type of load balancing in use on the bundle, with the following possible values: Default—The default load balancing method for the system is used on the bundle, and the load balancing sub-fields are not displayed. No value—Another load balancing method is in use on the bundle, with information shown in the related sub-fields of the display.
Link order signaling:	Displays whether or not link order signaling is operating on the bundle, with the following possible values: Operational—Link ordering for load balancing is working through the exchange of an additional, Cisco-specific LACP type length value (TLV) that contains the ordering information. Not operational—A consistent set of link ordering numbers (LONs) has not been received by a higher priority partner, or the LONs to be made active are not consistent with the maximum number of active links supported by the bundle.
Hash type:	The information to be used for the load balancing hash on the bundle, with the following possible values: Dst-IP—The load balancing on the bundle is based on the packet's destination IP address. Src-IP—The load balancing on the bundle is based on the packet's source IP address.
LACP:	Displays whether or not Link Aggregation Control Protocol (LACP) is active on the bundle, with the following possible values: Operational—All required configuration has been committed and LACP is in use on active members. Not operational—LACP is not working because some mandatory configuration is missing on the bundle or on the active members of the bundle. Not configured—None of the mandatory configuration for LACP has been committed on the bundle, and the LACP sub-fields are not displayed.
Flap suppression timer:	Displays the status of the flap suppression timer, with the following possible values: Off—The flap suppression timer is not configured using the lacp switchover suppress-flaps command. x ms—Amount of time allowed (in milliseconds) for standby links to activate after a working link fails, before putting the link in Down state.
Cisco extensions:	Displays whether or not the Cisco-specific TLVs for LACP are enabled. The possible values are "Enabled" and "Disabled".
Non-revertive:	Displays whether non-revertive behavior for the bundle interface is enabled or not. The possible values are "Enabled" and "Disabled".
mLACP:	Displays whether or not the bundle is operating using Multichassis Link Aggregation (MC-LAG), with the following possible values: Operational—All required configuration has been committed for MC-LAG and mLACP is in use on the bundle. Not operational—mLACP is not working because some mandatory configuration for MC-LAG is missing on the bundle or on the active members of the bundle. Not configured—None of the mandatory configuration for MC-LAG has been committed on the bundle, and the mLACP sub-fields are not displayed.
IPv4 BFD:	Displays whether or not IPv4-based bidirectional forwarding (BFD) is operating on the bundle interface, with the following possible values: Operational—All required configuration has been committed for IPv4 BFD, and it is in use on the bundle. Not operational—IPv4 BFD is not working because some mandatory configuration is missing on the bundle or on the active members of the bundle. Not configured—None of the mandatory configuration for IPv4 BFD has been committed on the bundle, and the BFD sub-fields are not displayed.
State:	When BFD is enabled, displays the state of BFD sessions on the bundle from the sessions running on bundle members that is communicated to interested protocols, with the following possible values: Down—The configured minimim threshold for active links or bandwidth for BFD bundle members is not available so BFD sessions are down. Off—BFD is not configured on bundle members. Up—BFD sessions on bundle members are up because the minimum threshold for the number of active links or bandwidth is met.
Fast detect:	Displays whether or not BFD fast detection is configured on the bundle, with the following possible values: Enabled—Thebfd fast-detect command is configured on the bundle. Disabled—The bfd fast-detect command is not configured on the bundle.
Start timer:	Displays status of the BFD start timer that is configured using the bfd address-family ipv4 timers start command, with the following possible values: x s—Number of seconds (from 60 to 3600) after startup of a BFD member link session to wait for the expected notification from the BFD peer to be received, so that the session can be declared up. If the SCN is not received after that period of time, the BFD session is declared down. Off—The start timer is not configured, and a BFD session is only declared Down upon notification from the BFD server.
Neighbor-unconfigured timer:	Displays status of the BFD start timer that is configured using the bfd address-family ipv4 timers nbr-unconfig command, with the following possible values: x s—Number of seconds (from 60 to 3600) to wait after receipt of notification that the BFD configuration has been removed by a BFD neighbor, so that any configuration inconsistency between the BFD peers can be fixed. If the BFD configuration issue is not resolved before the specified timer is reached, the BFD session is declared down. Off—The neighbor-unconfigured timer is not configured, and a BFD session is only declared Down upon notification from the BFD server.
Preferred min interval:	Number of milliseconds (in the format x ms) as the minimum control packet interval for BFD sessions. The range is 15 to 30000.
Preferred multiple:	Value of the multiplier (from 2 to 50) that is used for echo failure detection, which specifies the maximum number of echo packets that can be missed before a BFD session is declared Down.
Destination address:	Destination IP address for BFD sessions on bundle member links that is configured using the bfd address-family ipv4 destination command. "Not configured" is displayed when no destination IP address is configured.
Port	Name of the local interface port that is configured to be a bundle member, or a foreign interface received by an mLACP peer device. The possible values are the shortened interface name or a text string.
Device	Label Distribution Protocol (LDP) address of the device where the interface port is located, with the following possible values: address—IP address of the device. Local—Interface port is on the local device.
State	Status of the port, with one of the following possible values Active—Link can send and receive traffic. BFD Running—Link is inactive because BFD is down or has not been fully negotiated. Configured—Link is not operational or remains down due to a configuration mismatch. The link is not available for switchover from failure of an active link. Hot Standby—Link is ready to take over if an active link fails and can immediately transition to Active state without further exchange of LACP protocol data units (PDUs). Negotiating—Link is in the process of LACP negotiation and is being held in a lower LACP state by the peer (for example, because the link is Standby on the peer.) Standby—Link is not sending or receiving traffic, but is available for swithchover from failure of an active link.
Port ID	ID of the interface port in the format x/y, with the following values: x—Port priority as a 2-byte hexadecimal value. y—Link ID as a 2-byte hexadecimal value.
B/W, kbps	Bandwidth of the interface port in kilobits per second.
State reason	Text string that is displayed beneath the bundle member listing explaining why a link has not reached Active state.

Table 3. State Reasons
Reason	Description
BFD session is unconfigured on the remote end	The link is in BFD Running state because LACP is negotiated but the BFD session from the remote device has been unconfigured.
BFD state of this link is Down	The link is in BFD Running state because LACP is negotiated but the BFD session between the local system and the remote device is Down.
Bundle has been shut down	The link is in Configured state because the bundle it is configured as a member of is administratively down.
Bundle interface is not present in configuration	The link is in Configured state because the bundle it is configured as a member of has not itself been configured.
Bundle is in the process of being created	The link is in Configured state because the bundle it is configured as a member of is still being created.
Bundle is in the process of being deleted	The link is in Configured state because the bundle it is configured as a member of is being deleted.
Bundle is in the process of being replicated to this location	The link is in Configured state because the bundle it is configured as a member of is still being replicated to the linecard where the link is located.
Forced switchover to the mLACP peer	The link is in Configured state because it has been brought down as part of a forced switchover to the mLACP peer PoA. This happens only when brute force switchovers are configured.
ICCP group is isolated from the core network	The link is in Configured state because there is no connectivity through the network core for the ICCP group that the link and its bundle are part of. Therefore, the link has been brought down to prevent any traffic being sent by the LACP partner device.
Incompatible with other links in the bundle (bandwidth out of range)	The link is in Configured state because its bandwidth is incompatible with other links configured to be in the same bundle. The bandwidth may be too high or too low.
LACP shutdown is configured for the bundle	The link is in Standby state because the bundle is configured with LACP shutdown.
Incompatible with other links in the bundle (LACP vs non-LACP)	The link is in Configured state because its use of LACP is incompatible with other links configured in the same bundle. Some links might be running LACP while others are not.
Link is Attached and has not gone Collecting (reason unknown)	The link is in Negotiating state because the mLACP peer PoA has not indicated that the link has gone Collecting in the Mux machine. This could be because of an issue between the mLACP peer and its LACP partner or because this state has not been communicated to the local system.
Link is Collecting and has not gone Distributing (reason unknown)	The link is in Negotiating state because the mLACP peer PoA has not indicated that the link has gone Distributing in the Mux machine. This could be because of an issue between the mLACP peer and its LACP partner or because this state has not been communicated to the local system.
Link is being removed from the bundle	The link is being removed from the bundle and remains in Configured state while this happens.
Link is Defaulted; LACPDUs are not being received from the partner	The link is in Configured state because no LACPDUs are being received from the LACP partner device. Either the partner is not transmitting or the packets are getting lost.
Link is down	The link is in Configured state because it is operationally or administratively down.
Link is Expired; LACPDUs are not being received from the partner	The link is in Negotiating state because no LACPDUs have been received from the LACP Partner device in the Current-While period and the link is now marked as Expired in the Receive machine.
Link is in the process of being created	The link is in Configured state because the member configuration is still being processed.
Link is marked as Standby by mLACP peer	The link is in Standby state because this has been indicated by the mLACP peer PoA.
Link is Not Aggregatable (reason unknown)	The link is in Configured state because it is marked as an Individual link by the mLACP peer PoA.
Link is not operational as a result of mLACP negotiations	mLACP negotiations with the peer have led to this link being kept in Configured state. This is likely to indicate a misconfiguration between the two peer devices.
Link is Standby; bundle has more links than are supported	The link is in Standby state because the number of links in Selected state has already reached the hard platform limit on the number of active links.
Link is Standby due to maximum-active links configuration	The link is in Standby state because the number of links in Selected state has already reached the configured maximum active links threshold.
Link is waiting for BFD session to start	The link is in BFD Running state because LACP is negotiated but the BFD session has not started from the remote device.
Loopback: Actor and Partner have the same System ID and Key	The link is in Configured state because a loopback condition has been detected on the link—two links configured to be members of the bundle are actually connected to each other.
Not enough links available to meet minimum-active threshold	The link is in Standby state because there are not enough selectable links (i.e. links which meet the criteria to be marked Selected within the bundle) to meet the minimum active links/bandwidth threshold.
Partner has marked the link as Not Aggregatable	The link is in Configured state because it is marked as an Individual link by the LACP partner device.
Partner has not advertised that it is Collecting	The link is in Negotiating state because the LACP partner device has not advertised that the link is in Collecting state in its LACPDUs.
Partner has not echoed the correct parameters for this link	The link is in Negotiating state because the LACP partner device has not correctly echoed the local system's port information in the LACPDUs it is sending.
Partner is not Synchronized (Waiting, not Selected, or out-of-date)	The link is in Negotiating state because the mLACP peer PoA has not indicated that its LACP partner device is Synchronized. This could be because the devices are genuinely not Synchronized or because this state has not been communicated to the local system.
Partner is not Synchronized (Waiting, Standby, or LAG ID mismatch)	The link is in Negotiating state because the LACP partner device has not indicated that it is Synchronized in the LACPDUs it is sending. On the partner device the link could still be waiting for the Wait-While timer to expire, it could be held in Standby state, or there could be a misconfiguration leading to a LAG ID mismatch between links configured to be within the same bundle.
Partner System ID/Key do not match that of the Selected links	The link is in Configured state because the System ID or Operational Key specified by the LACP partner device does not match that seen on other Selected links within the same bundle. This probably indicates a misconfiguration.
Wait-while timer is running	The link is in Configured state because the Wait-While timer is still running and the new state has not yet been determined.

show bundle brief

To display summary information about all configured bundles, use the show bundle brief command in XR EXEC mode.

show bundle brief

Syntax Description

This command has no keywords or arguments.

Command Default

Information for all configured bundles is displayed.

Command Modes

XR EXEC mode

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID


Task ID	Operation
bundle	read

Examples

These examples shows the status of two bundles, BE16 and BE100, that are configured on the router. Both are Ethernet bundles and only bundle 16 is Up:

RP/0/RP0/CPU0:router# show bundle brief
Thu Mar  3 14:40:35.167 PST

Name   | IG       | State         | LACP | BFD |     Links     | Local b/w, |
       |          |               |      |     | act/stby/cfgd |    kbps    |
-------|----------|---------------|------|-----|---------------|------------|
BE1              - Up              On     Off         2 / 0 / 2     20000000
BE2              - Down            Off    Off         0 / 0 / 0            0
BE3              - Admin down      Off    Off         0 / 0 / 1            0
BE100            - Up              On     Off         3 / 0 / 6     30000000

The below table describes the fields shown in the display.

Table 4. show bundle brief Field Descriptions
Field	Description
Name	Abbreviated name of the bundle interface, with the following possible formats: BEx—Ethernet bundle with ID number x.
IG	Interchassis group ID (if configured) of which the bundle is a member.
State	State of the bundle on the local device, with the following possible values: Admin down—The bundle has been configured to be shut down. Bundle shut—The bundle is holding all links in Standby state and will not support any traffic. Down—The bundle is operationally down. It has no Active members on the local device. mLACP cold standby—The bundle is acting as a multichassis LACP Standby device, but the higher layers are not synchronized. mLACP hot standby—The bundle is Up on the mLACP peer device, and the local device is ready to take over if that bundle goes down on the peer. Nak—The local and peer devices cannot resolve a configuration error. Partner down—The partner system indicates that the bundle is unable to forward traffic at its end. PE isolated—The bundle is isolated from the core. Up—The bundle has Active members on this device.
LACP	Status of the Link Aggregation Control Protocol (LACP) on the bundle, with the following possible values: On—LACP is in use on the bundle. Off—LACP is not active.
BFD	When BFD is enabled, displays the state of BFD sessions on the bundle from the sessions running on bundle members that is communicated to interested protocols, with the following possible values: Down—The configured minimim threshold for active links or bandwidth for BFD bundle members is not available so BFD sessions are down. Off—BFD is not configured on bundle members. Up—BFD sessions on bundle members are up because the minimum threshold for the number of active links or bandwidth is met.
Links act/stby/cfgd	Number of links on the bundle with a particular status in the format x/y/z, with the following values: x—Number of links in Active state on the bundle for the local device (from 1 to the maximum number of links supported on the bundle). y—Number of links in Standby state on the bundle for the local device (from 1 to the maximum number of links supported on the bundle). z—Total number of links configured on the bundle for the local device (from 1 to the maximum number of links supported on the bundle).
Local b/w, kbps	Current bandwidth of the bundle on the local device (this effective bandwidth might be limited by configuration).

show lacp bundle-ether

To display detailed information about Link Aggregation Control Protocol (LACP) ports and their peers, enter the show lacp bundle command in XR EXEC mode.

show lacp {Bundle-Ether} bundle-id

Syntax Description


Bundle-Ether `bundle-id`	(Optional) Specifies the number of the Ethernet bundle whose information you want to display. Range is 1 through 65535.

Command Default

No default behavior or values

Command Modes

XR EXEC mode

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID


Task ID	Operations
bundle	read

Examples

This example shows how to display LACP information for a specific Ethernet Bundle:


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

Wed Jun 22 20:34:58.085 UTC
State: a - Port is marked as Aggregatable.
       s - Port is Synchronized with peer.
       c - Port is marked as Collecting.
       d - Port is marked as Distributing.
       A - Device is in Active mode.
       F - Device requests PDUs from the peer at fast rate.
       D - Port is using default values for partner information.
       E - Information about partner has expired.

Bundle-Ether1

  Port          (rate)  State    Port ID       Key    System ID
  --------------------  -------- ------------- ------ ------------------------
Local
  Te0/0/0/0/0      30s  ascdA--- 0x8000,0x0006 0x0001 0x8000,ea-74-b3-bd-f4-85
   Partner         30s  ascdA--- 0x8000,0x0002 0x0001 0x8000,1c-df-0f-39-d1-05
  Te0/0/0/0/1      30s  ascdA--- 0x8000,0x0005 0x0001 0x8000,ea-74-b3-bd-f4-85
   Partner         30s  ascdA--- 0x8000,0x0001 0x0001 0x8000,1c-df-0f-39-d1-05

  Port                  Receive    Period Selection  Mux       A Churn P Churn
  --------------------  ---------- ------ ---------- --------- ------- -------
Local
  Te0/0/0/0/0           Current    Slow   Selected   Distrib   None    None   
  Te0/0/0/0/1           Current    Slow   Selected   Distrib   None    None   
RP/0/RP0/CPU0:vpnPE1#

Table 5. show lacp bundle Field Descriptions
Field	Description
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	Two-byte number associated with the specified link and aggregator. Each port is 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.

show lacp packet-capture

To display the contents of Link Aggregation Control Protocol (LACP) packets that are sent and received on an interface, use the show lacp packet-capture command in XR EXEC mode.

show lacp packet-capture [decoded] [in | out] {HundredGigE | TenGigE}interface-path-id

Syntax Description

decoded

(Optional) Displays packet information in decoded form for the specified interface.

in

(Optional) Displays packet information for ingress packets only.

out

(Optional) Displays packet information for egress packets only.

HundredGigE

Displays packet information for the Hundred Gigabit Ethernet interface specified by interface-path-id .

TenGigE

Displays packet information for the Ten Gigabit Ethernet interface specified by interface-path-id .

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.

Command Default

The default displays both in and out information.

Command Modes

XR EXEC mode

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

The lacp packet-capture command captures transmit and receive packets on a single interface. The contents of these packets can then be displayed by the show lacp packet-capture command. If the lacp packet-capture command is not issued, the show lacp packet-capture command does not display any information.

Task ID


Task ID	Operations
bundle	read

Examples

Note

In the following example, after you issue the lacp packet-capture command, you must wait for a reasonable amount of time for the system to capture packets that are sent and received on the interface before you issue the show lacp packet-capture command. Otherwise, there is no information to display.


RP/0/RP0/CPU0:router# lacp packet-capture HundredGigE 0/1/0/0 100
RP/0/RP0/CPU0:router# show lacp packet-capture HundredGigE 0/1/0/0 

Wed Apr 29 16:27:40.996 GMT
OUT  Apr 29 17:05:50.123
========================
01 01 01 14 80 00 02 a7 4c 81 95 04 00 01 80 00 00 01 45 00 
00 00 02 14 ff ff 00 00 00 00 00 00 00 00 ff ff 00 00 40 00 
00 00 03 10 ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 

OUT  Apr 29 17:35:50.124
========================
...

The following example shows how to display the LACP parameters, decoded from individual packets, transmitted and received on a Gigabit Ethernet interface:

Note

In the following example, after you issue the lacp packet-capture command, you must wait for a reasonable amount of time for the system to capture packets that are sent and received on the interface before you issue the show lacp packet-capture command. Otherwise, there is no information to display.


RP/0/RP0/CPU0:router# lacp packet-capture HundredGigE 0/1/0/0 100
RP/0/RP0/CPU0:router# show lacp packet-capture decoded HundredGigE 0/1/0/0 

Wed Apr 29 16:27:54.748 GMT
OUT  Apr 29 17:06:03.008
========================
Subtype: 0x01 - LACP     Version: 1

TLV: 0x01 - Actor Information       Length:  20
System: Priority: 32768, ID: 02-a7-4c-81-95-04
Key: 0x0001, Port priority: 32768, Port ID:     1
State:  Act  (T/o)  Agg  (Sync) (Coll) (Dist)  Def  (Exp)

TLV: 0x02 - Partner Information     Length:  20
System: Priority: 65535, ID: 00-00-00-00-00-00
Key: 0x0000, Port priority: 65535, Port ID:     0
State: (Act) (T/o) (Agg) (Sync) (Coll) (Dist)  Def  (Exp)

TLV: 0x03 - Collector Information   Length:  16
Max delay: 65535

TLV: 0x00 - Terminator              Length:   0

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 XR EXEC mode.

show lacp system-id

Syntax Description

This command has no keywords or arguments.

Command Default

No default behavior or values

Command Modes

XR EXEC mode

Command History


Release	Modification
Release 6.0	This command was introduced.

Usage Guidelines

The System ID and details about the specific link are transmitted within each LACP packet.

Task ID


Task ID	Operations
bundle	read

Examples

The following example shows how to display the system ID used by the LACP:


RP/0/RP0/CPU0:router# show lacp system-id

Priority  MAC Address
--------  -----------------
  0x8000  08-00-45-3a-65-01

Table 6. show lacp system-id Field Descriptions
Field	Description
Priority	Priority for this system. A lower value is higher priority.
MAC Address	MAC address associated with the LACP system ID.

Bias-Free Language

Results

Chapter: Link Bundling Commands

Link Bundling Commands

bundle-hash

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Task ID

Examples

bundle id

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Task ID

Examples

bundle maximum-active links

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Task ID

Examples

Examples

Examples

Examples

Examples

bundle minimum-active bandwidth

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Task ID

Examples

bundle minimum-active links

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Task ID

Examples

bundle port-priority

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Task ID

Examples

clear lacp counters

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Task ID

Examples

hw-module profile load-balance algorithm

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Task ID

Examples

hw-module profile bundle-hash

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Task ID