-
Interface and Hardware Component Command Reference for the Cisco NCS 6000 Series Routers
-
Preface
-
Ethernet Interface Commands \n\t
-
Ethernet OAM Commands
-
Global Interface Commands
-
Link Bundling Commands
-
Management Ethernet Interface Commands
-
Null Interface Commands
-
Packet-over-SONET Interface Commands
-
PPP Commands
-
VLAN Subinterface Commands
-
10-Gigabit Ethernet\n\t WAN PHY Controller Commands
-
Index
-
Feedback
Contents
Link Bundling Commands
- bundle-hash
- bundle id
- bundle maximum-active links
- bundle minimum-active bandwidth
- bundle minimum-active links
- bundle port-priority
- clear lacp counters
- interface (bundle)
- lacp packet-capture
- lacp period short
- lacp system priority
- show bundle
- show bundle brief
- show bundle replication bundle-ether
- show lacp bundle
- show lacp counters
- show lacp io
- show lacp packet-capture
- show lacp port
- show lacp system-id
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 EXEC mode.
bundle-hash { Bundle-Ether bundle-id | members { GigabitEthernet | 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.
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.
HundredGigE
Specified 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 History
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.
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:
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.
Table 1 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 Table 1.
Table 1 bundle-hash Command OptionsOption
Information You Need to Provide
L3/3-tuple
L3 information:
L4/7-tuple
L3 information:
L4 information:
Platform-related information:
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
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 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/7The 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 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 hitsThe 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: [ GigabitEthernet | TenGigE ]R/S/I/P - bundle interface format: [ Bundle-Ether]bundle-id Enter ingress interface: GigabitEthernet0/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 GigabitEthernet0/3/3/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: [GigabitEthernet | TenGigE ]R/S/I/P - bundle interface format: [ Bundle-Ether ]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 Another? [y]: nbundle id
To add a port to an aggregated interface (or bundle), enter the bundle id command in interface configuration mode.
Syntax Description
Command History
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.
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
Examples
This 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 1This 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 activebundle 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.
Syntax Description
links
Number of active links you want to bring up in the specified bundle, up to the maximum supported on the platform.
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.
Command History
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.
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:
Task ID
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-standbyThe 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.0000In 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 1The 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 10x8000, 0x0002 10000000 0000.abab.0000In 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)#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.0000In 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.
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.
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.
Command History
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.
Task ID
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 620000bundle 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.
Syntax Description
links
Minimum number of active links allowed in the specified bundle.
The range is from 1 through 64.
Command History
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.
Task ID
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 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 2bundle 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.
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 History
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.
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
Examples
The following example shows how to configure the priority of a port:
RP/0/RP0/CPU0:router# config RP/0/RP0/CPU0:router(config)# interface gigabitethernet 0/1/0/1 RP/0/RP0/CPU0:router(config-if)# bundle port-priority 1clear 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.
Command History
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.
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
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-POS } bundle-id
no interface { Bundle-Ether | Bundle-POS } bundle-id
Syntax Description
Bundle-Ether Specifies or creates an Ethernet bundle interface.
Bundle-POS Specifies or creates a POS bundle interface.
bundle-id Number from 1 to 65535 that identifies a particular bundle.
Command History
Usage Guidelines
You must be in a user group associated with a task group that includes the proper task IDs. The command reference guides include the task IDs required for each command. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
Task ID
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)#This example shows how to create a new POS bundle and enter interface configuration mode:
RP/0/RP0/CPU0:router(config)# interface Bundle-POS 10 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 EXEC mode.
{ lacp packet-capture gigabitethernet interface-path-id | pos 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 EXEC mode.
{ lacp packet-capture [ bundle-ether bundle-id ] [ bundle-pos bundle-id ] [ gigabitethernet interface-path-id ] [ pos interface-path-id ] [ tengige interface-path-id ] clear | stop }
Syntax Description
bundle-ether
Ethernet bundle interface specified by bundle-id.
bundle-pos
Packet-over-SONET (POS) bundle interface specified by bundle-id.
GigabitEthernet
Gigabit Ethernet interface specified by interface-path-id.
POS
Packet-over-SONET (POS) 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 History
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.
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
Examples
The following example shows how to capture LACP packets on a POS interface:
RP/0/RP0/CPU0:router# lacp packet-capture pos 0/1/0/0 100The following example shows how to stop capturing LACP packets on a POS interface:
RP/0/RP0/CPU0:router# lacp packet-capture pos 0/1/0/0 stopThe following example shows how to clear all captured LACP packets on a POS interface:
RP/0/RP0/CPU0:router# lacp packet-capture pos 0/1/0/0 clearThe following example shows how to capture LACP packets on a Gigabit Ethernet interface:
RP/0/RP0/CPU0:router# lacp packet-capture gigabitethernet 0/2/0/0 100The following example shows how to stop capturing LACP packets on a Gigabit Ethernet interface:
RP/0/RP0/CPU0:router# lacp packet-capture gigabitethernet 0/2/0/0 stopRelated Commands
Command
Description
Displays the LACP transmission information that used by the transmitting device for sending packets on an interface.
Displays the contents of LACP packets that are sent and received on an interface.
Enables a short period time interval for the transmission and reception of LACP packets.
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 History
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.
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.
Task ID
Examples
The following example shows how to enable a default Link Aggregation Control Protocol (LACP) short period on a Gigabit Ethernet interface:
RP/0/RP0/CPU0:router# config RP/0/RP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0 RP/0/RP0/CPU0:router(config-if)# lacp period short RP/0/RP0/CPU0:router(config-if)# commitThe 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 gigabitethernet 0/1/0/0 RP/0/RP0/CPU0:router(config-if)# lacp period short RP/0/RP0/CPU0:router(config-if)# commitRP/0/RP0/CPU0:router# config RP/0/RP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0 RP/0/RP0/CPU0:router(config-if)# lacp period short RP/0/RP0/CPU0:router(config-if)# commitRP/0/RP0/CPU0:router# config RP/0/RP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0 RP/0/RP0/CPU0:router(config-if)# lacp period short transmit 500 RP/0/RP0/CPU0:router(config-if)# commitRP/0/RP0/CPU0:router# config RP/0/RP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0 RP/0/RP0/CPU0:router(config-if)# lacp period short transmit 500 RP/0/RP0/CPU0:router(config-if)# commitRP/0/RP0/CPU0:router# config RP/0/RP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0 RP/0/RP0/CPU0:router(config-if)# lacp period short receive 500 RP/0/RP0/CPU0:router(config-if)# commitRP/0/RP0/CPU0:router# config RP/0/RP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0 RP/0/RP0/CPU0:router(config-if)# lacp period short receive 500 RP/0/RP0/CPU0:router(config-if)# commitlacp system priority
To configure the priority for the current system, enter the lacp system priority command in XR Config mode. To return to the default LACP system priority value, use the no form of this command.
Syntax Description
s
Priority for this system. Replace priority with a number. Range is from 1 through 65535. A lower value is higher priority.
Command History
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.
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
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 100show bundle
To display information about all bundles or a specific bundle of a particular type, use the show bundle command in EXEC configuration mode.
Syntax Description
Bundle-Ether Displays information for the specified Ethernet bundle.
Bundle-POS Displays information for the specified POS bundle.
bundle-id Number from 1 to 65535 that identifies a particular bundle.
Command History
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.
To see information for all bundles configured on the router, use the show bundleform of the command.
To see information for a specific bundle, use the show bundle Bundle-Etherbundle-idor show bundle Bundle-POSbundle-id form of the command with the number of the configured bundle.
Task ID
Examples
The following example shows output for all bundle interfaces that are configured on the router:
RP/0/RP0/CPU0:router# show bundle Sun Mar 6 12:16:25.601 PST Bundle-Ether10 Status: Up Local links <active/standby/configured>: 1 / 1 / 2 Local bandwidth <effective/available>: 1000000 (1000000) kbps MAC address (source): f866.f213.25a8 (Gi0/1/0/16) Minimum active links / bandwidth: 1 / 1 kbps Maximum active links: 1 Wait while timer: 2000 ms Load balancing: Default LACP: Operational Flap suppression timer: Off Cisco extensions: Disabled mLACP: Not configured IPv4 BFD: Not operational State: Off Fast detect: Enabled Start timer: Off Neighbor-unconfigured timer: Off Preferred min interval: 150 ms Preferred multiple: 3 Destination address: Not Configured Port Device State Port ID B/W, kbps -------------------- --------------- ----------- -------------- ---------- Gi0/1/0/9 Local Active 0x0001, 0x0001 1000000 Link is Active Gi0/1/0/10 Local Standby 0x0002, 0x0002 1000000 Link is Standby due to maximum-active links configuration
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 EXEC configuration mode.
Command History
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.
Task ID
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 | -------|----------|---------------|------|-----|---------------|------------| BE16 - Up On Off 1 / 1 / 2 1000000 BE100 - Down Off Off 0 / 0 / 0 0Table 1 describes the fields shown in the display.
show bundle replication bundle-ether
To display the replication status of a link bundle interface, use the show bundle replication bundle-ether command in EXEC mode.
Syntax Description
all
Shows replication status for all nodes.
in-progress
Shows only nodes with replication in progress.
pending
Shows only nodes pending replication.
Command History
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.
Task ID
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.
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 History
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.
Task ID
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. Bundle-Ether1 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 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:
Flags
Provides information about the state of the specified device or port. Possible flags are:
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 counters
To display Link Aggregation Control Protocol (LACP) statistics, enter the show lacp counters command in EXEC mode.
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.
Command History
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.
Task ID
Examples
The following example shows how to display LACP counters on an Ethernet bundle:
RP/0/RP0/CPU0:router# show lacp counters bundle-ether 1 Bundle-Ether1 LACPDUs Marker Port Sent Received Received Resp. Sent Last Cleared ------------- ---------------------- ---------------------- ------------ Gi0/0/2/0 12 0 0 0 never Port Excess Excess Pkt Errors ------------- ---------- ---------- ---------- Gi0/0/2/0 0 0 0
Table 6 show lacp counters Field Descriptions Field
Description
LACPDUs
Provides the following statistics for Link Aggregation Control Protocol data units (LACPDUs):
Marker
Provides the following statistics for marker packets:
Note The Marker Protocol is used by IEEE 802.3ad bundles to ensure that data no longer is transmitted on a link when a flow is redistributed away from that link.
show lacp io
To display the Link Aggregation Control Protocol (LACP) transmission information that used by the transmitting device for sending packets on an interface, use the show lacp io command in EXEC mode.
show lacp io { Bundle-Ether | bundle-POS } bundle-id { GigabitEthernet | POS | TenGigE } interface-path-id
Syntax Description
Bundle-Ether bundle-id
(Optional) Displays information for the Ethernet bundle interface with the specified bundle-id. The range is 1 through 65535.
Bundle-POS bundle-id
(Optional) Displays information for the POS bundle interface with the specified bundle-id. The range is 1 through 65535.
GigabitEthernet
(Optional) Displays information for the Gigabit Ethernet interface with the specified interface-path-id.
TenGigE
(Optional) Displays information for the Ten Gigabit Ethernet interface with the specified interface-path-id.
POS
(Optional) Displays information for the POS interface with the specified 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 takes no parameters and displays information for all actively transmitting interfaces.
Command History
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.
This command displays information only for interfaces that are actively transmitting packets.
Task ID
Examples
The following example shows how to display Link Aggregation Control Protocol (LACP) information for the Ethernet bundle interface with bundle ID 28.
RP/0/RP0/CPU0:router# show lacp io bundle-ether 28 Thu Jun 18 16:28:54.068 PST Bundle-Ether28 Interface GigabitEthernet0/1/5/6 ================================ Interface handle: 0x01180100 Interface media type: Ethernet Fast periodic interval: 1000ms Source MAC address: 0015.63c0.b3b8 Actor system: 0x8000, 00-15-63-c0-b0-04 Actor key: 0x001c Actor port: 0x8000, 0x0001 Actor state: Act (T/o) Agg Sync Coll Dist (Def) (Exp) Partner system: 0x8000, 00-15-63-58-b9-04 Partner key: 0x001c Partner port: 0x0001, 0x0003 Partner state: Act (T/o) Agg Sync Coll Dist (Def) (Exp) Interface GigabitEthernet0/1/5/7 ================================ Interface handle: 0x01180120 Interface media type: Ethernet Fast periodic interval: 1000ms Source MAC address: 0015.63c0.b3b9 Actor system: 0x8000, 00-15-63-c0-b0-04 Actor key: 0x001c Actor port: 0x8000, 0x0002 Actor state: Act (T/o) Agg Sync (Coll) (Dist) (Def) (Exp) Partner system: 0x8000, 00-15-63-58-b9-04 Partner key: 0x001c Partner port: 0x0002, 0x0004 Partner state: Act (T/o) Agg (Sync) (Coll) (Dist) (Def) (Exp)The following example shows how to display Link Aggregation Control Protocol (LACP) information for all actively transmitting interfaces:
RP/0/RP0/CPU0:router# show lacp io Thu Jun 18 16:33:57.330 PST Bundle-Ether28 Interface GigabitEthernet0/1/5/6 ================================ Interface handle: 0x01180100 Interface media type: Ethernet Fast periodic interval: 1000ms Source MAC address: 0015.63c0.b3b8 Actor system: 0x8000, 00-15-63-c0-b0-04 Actor key: 0x001c Actor port: 0x8000, 0x0001 Actor state: Act (T/o) Agg Sync Coll Dist (Def) (Exp) Partner system: 0x8000, 00-15-63-58-b9-04 Partner key: 0x001c Partner port: 0x0001, 0x0003 Partner state: Act (T/o) Agg Sync Coll Dist (Def) (Exp) Interface GigabitEthernet0/1/5/7 ================================ Interface handle: 0x01180120 Interface media type: Ethernet Fast periodic interval: 1000ms Source MAC address: 0015.63c0.b3b9 Actor system: 0x8000, 00-15-63-c0-b0-04 Actor key: 0x001c Actor port: 0x8000, 0x0002 Actor state: Act (T/o) Agg Sync (Coll) (Dist) (Def) (Exp) Partner system: 0x8000, 00-15-63-58-b9-04 Partner key: 0x001c Partner port: 0x0002, 0x0004 Partner state: Act (T/o) Agg (Sync) (Coll) (Dist) (Def) (Exp)Bundle-POS24 Interface POS0/1/4/0 ==================== Interface handle: 0x011804c0 Interface media type: POS Fast periodic interval: 1000ms Actor system: 0x8000, 00-15-63-c0-b0-04 Actor key: 0x0018 Actor port: 0x8000, 0x0003 Actor state: Act (T/o) Agg Sync Coll Dist (Def) (Exp) Partner system: 0x8000, 00-15-63-58-b9-04 Partner key: 0x0018 Partner port: 0x8000, 0x0001 Partner state: Act (T/o) Agg Sync Coll Dist (Def) (Exp) Interface POS0/1/4/1 ==================== Interface handle: 0x011804e0 Interface media type: POS Fast periodic interval: 1000ms Actor system: 0x8000, 00-15-63-c0-b0-04 Actor key: 0x0018 Actor port: 0x8000, 0x0004 Actor state: Act (T/o) Agg Sync Coll Dist (Def) (Exp) Partner system: 0x8000, 00-15-63-58-b9-04 Partner key: 0x0018 Partner port: 0x8000, 0x0002 Partner state: Act (T/o) Agg Sync Coll Dist (Def) (Exp)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 EXEC mode.
show lacp packet-capture [decoded] [ in | out ] { GigabitEthernet | POS | 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.
GigabitEthernet
Displays packet information for the Gigabit Ethernet interface specified by interface-path-id.
POS
Displays packet information for the POS 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 History
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.
Note
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
Examples
The following example shows how to display the contents of an LACP packet, in hexadecimal, for 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 gigabitethernet 0/1/0/0 100 RP/0/RP0/CPU0:router# show lacp packet-capture gigabitethernet 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 gigabitethernet 0/1/0/0 100 RP/0/RP0/CPU0:router# show lacp packet-capture decoded gigabitethernet 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: 0Related Commands
Command
Description
Displays the LACP transmission information that used by the transmitting device for sending packets on an interface.
Enables a short period time interval for the transmission and reception of LACP packets.
Captures LACP packets so that their information can be displayed.
show lacp port
To display detailed information about Link Aggregation Control Protocol (LACP) ports, enter the show lacp port command in EXEC mode.
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.
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 History
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.
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:
Task ID
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. Bundle-Ether1 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 7 show lacp port Field Descriptions Field
Description
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:
Flags
Provides information about the state of the specified port. Possible flags are:
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
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 an LACP property of the system which is transmitted within each LACP packet together with the details of the link.
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.
Command History
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.
Note
The System ID and details about the specific link are transmitted within each LACP packet.
Task ID
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
