-
Cisco ASR 9000 Series Aggregation Services Router Interface and Hardware Component Command Reference, Release 4.2.x
-
Preface
-
Dense Wavelength Division Multiplexing Commands on the Cisco ASR 9000 Series Router
-
Diagnostics Commands on the Cisco ASR 9000 Series Router
-
Ethernet Interface Commands on the Cisco ASR 9000 Series Router
-
Ethernet OAM Commands on the Cisco ASR 9000 Series Router
-
Frame Relay Commands on the Cisco ASR 9000 Series Router
-
Global Interface Commands on the Cisco ASR 9000 Series Router
-
Internal Ethernet Control Network Commands on the Cisco ASR 9000 Series Router
-
Integrated Routing and Bridging Commands on the Cisco ASR 9000 Series Router
-
Link Bundling Commands on the Cisco ASR 9000 Series Router
-
Management Ethernet Interface Commands on the Cisco ASR 9000 Series Router
-
Multilink Commands on the Cisco ASR 9000 Series Router
-
Packet-over-SONET Interface Commands on the Cisco ASR 9000 Series Router
-
PPP Commands on the Cisco ASR 9000 Series Router
-
Serial Interface Commands on the Cisco ASR 9000 Series Router
-
SONET Controller Commands on the Cisco ASR 9000 Series Router
-
T3, E3, T1, E1 Controller Commands on the Cisco ASR 9000 Series Router
-
Traffic Mirroring Commands on the Cisco ASR 9000 Series Router
-
VLAN Subinterface Commands on the Cisco ASR 9000 Series Router
-
10-Gigabit Ethernet WAN PHY Controller Commands on the Cisco ASR 9000 Series Router
-
Index
-
Feedback
Contents
Link Bundling Commands on the Cisco ASR 9000 Series Router
- backbone interface
- bundle-hash
- bundle id
- bundle load-balancing hash
- bundle load-balancing hash (EFP)
- bundle maximum-active links
- bundle minimum-active bandwidth
- bundle minimum-active links
- bundle port-priority
- clear lacp counters
- hw-module load-balance bundle l2-service l3-params
- interface (bundle)
- isolation recovery-delay
- lacp cisco enable
- lacp fast-switchover
- lacp packet-capture
- lacp period short
- lacp system priority
- member neighbor
- mlacp connect
- mlacp iccp-group
- mlacp node
- mlacp port-priority
- mlacp system mac
- mlacp system priority
- redundancy iccp group
- redundancy one-way
- show bundle
- show bundle brief
- show bundle load-balancing
- show bundle replication bundle-ether
- show iccp group
- show lacp bundle
- show lacp counters
- show lacp io
- show lacp packet-capture
- show lacp port
- show lacp system-id
- show mlacp
- show mlacp counters
backbone interface
To configure interchassis group ICCP backbone interface, use the backbone interface command in the redundancy group ICCP configuration mode. To return to the default behavior, use the no form of this command.
Syntax Description
type
Interface type. For more information, use the question mark (?) online help function.
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.
Task ID
Examples
The following example shows how to configure interchassis group ICCP backbone interface:
RP/0/RSP0/CPU0:router# configure RP/0/RSP0/CPU0:router(config)# redundancy iccp group 10 RP/0/RSP0/CPU0:router(config-redundancy-iccp-group)# backbone interface GigabitEthernet 0/2/1/0 RP/0/RSP0/CPU0:router(config-redundancy-iccp-group)#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 } 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.
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 the following 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.
Note
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.
You can use the show bundle command to get IP address information.
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/RSP0/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/RSP0/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/RSP0/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
The following example shows how to add a port onto a bundle:
RP/0/RSP0/CPU0:router(config)# interface GigabitEthernet 0/1/5/0 RP/0/RSP0/CPU0:router(config-if)# bundle id 1The following example shows how to add an active LACP port onto an aggregated interface (or bundle):
RP/0/RSP0/CPU0:router(config)# interface GigabitEthernet 0/6/5/7 RP/0/RSP0/CPU0:router(config-if)# bundle id 5 mode activebundle load-balancing hash
To specify the hash function to be used for traffic being forwarded over a bundle interface, use the bundle load-balancing hash command in interface configuration mode. To return to the default, use the no form of the command.
Syntax Description
dst-ip Specifies a load-balancing hash based on destination IP address.
src-ip Specifies a load-balancing hash based on source IP address.
Command Default
The default platform hashes for the bundle are used. For IPv4 traffic, the default hash is based on router ID, source IP, destination IP, and if available, source and destination Layer 4 port.
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 load balancing hashes based on source IP address or destination IP address are used for MGSCP deployment models where traffic forwarded from the subscriber side of the network is based on source IP address, and traffic forwarded from the core side of the network is based on destination IP address.
Task ID
Examples
The following example configures load balancing on bundle members based on source IP address:
RP/0/RSP0/CPU0:router(config)#interface Bundle-Ether 100 RP/0/RSP0/CPU0:router(config-if)# bundle load-balancing hash src-ipRelated Commands
Command
Description
Specifies or creates a new bundle and enters interface configuration mode for that bundle.
Enables use of Cisco-specific TLVs in addition to standard TLVs for negotiating and exchanging LACP information on link bundles.
Displays information about configured bundles.
Displays load balancing information, such as the ports, usage, weight, and distribution of traffic on individual members of a link bundle interface.
bundle load-balancing hash (EFP)
To configure all egressing traffic on a particular subinterface of a bundle to flow through the same physical member link , use the bundle load-balancing hash (EFP) command in subinterface configuration mode.
Syntax Description
hash-value
Numeric value that specifies the physical member link through which all egressing traffic in this bundle will flow. The values are 1 through 64.
auto
The physical member link through which all egressing traffic on this bundle will flow is automatically chosen.
Command History
Release
Modification
Release 3.9.0
This command was introduced.
Release 4.0.0
The hash-value range was changed from an upper limit of 8 to 64.
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 is only available on an Ethernet Bundle subinterface with Layer 2 transport (l2transport) enabled.
This command allows the user to configure all egressing traffic on the fixed members of a bundle to flow through the same physical member link. If the active members of the bundle change, the traffic for the bundle may get mapped to a different physical link that has a hash value that matches the configured value.
Task ID
Examples
The following example shows how to configure all egressing traffic on the fixed members of a bundle to flow through the same physical member link automatically.
RP/0/RSP0/CPU0:router# config RP/0/RSP0/CPU0:router(config)# interface bundle-ether 1.1 l2transport RP/0/RSP0/CPU0:router(config-subif)# bundle load-balancing hash autoThe following example shows how to configure all egressing traffic on the fixed members of a bundle to flow through a specified physical member link.
RP/0/RSP0/CPU0:router# config RP/0/RSP0/CPU0:router(config)# interface bundle-ether 1.1 l2transport RP/0/RSP0/CPU0:router(config-subif)# bundle load-balancing hash 1Related Commands
Command
Description
Displays the source and destination IP addresses for the member links.
Specifies or creates a new bundle and enters interface configuration mode for that bundle.
Displays information about configured bundles.
Displays load balancing information, such as the ports, usage, weight, and distribution of traffic on individual members of a link bundle interface.
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.
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.
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 maximum-active links command is supported only for bundles that are not running LACP.
- Running Link Aggregation Control Protocol (LACP), and the hot-standby option is implemented.
- Not running LACP.
If the bundle maximum-active links command is issued, then only the highest-priority link within the bundle is active . The priority is based on the value from the bundle port-priority command, where a lower value is a higher priority. Therefore, we recommend that you configure a higher priority on the link that you want to be the active link.
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 sets the required number of active links required to bring up Ethernet bundle 5 to 2:
RP/0/RSP0/CPU0:router(config)# interface Bundle-Ether 5 RP/0/RSP0/CPU0:router(config-if)# bundle maximum-active links 1bundle 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 is equivalent to the combined bandwidths of 8 TenGigabitEthernet 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.
Task ID
Examples
The following example shows how to set the minimum amount of bandwidth required before a user can bring up a specific bundle. In this example, the user sets the minimum amount of bandwidth required to bring up Ethernet bundle 1 to 620000:
RP/0/RSP0/CPU0:router(config)# interface Bundle-Ether 1 RP/0/RSP0/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
Release
Modification
Release 3.7.2
This command was introduced.
Release 4.0.0
The command range maximum was changed from 8 to 64.
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 2 links must be active before the bundle can be brought up:
RP/0/RSP0/CPU0:router(config)# interface Bundle-Ether 5 RP/0/RSP0/CPU0:router(config-if)# bundle minimum-active links 2bundle port-priority
To configure Link Aggregation Control Protocol (LACP) 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.
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 LACP priority value forms part of the port ID, which is transmitted within the LACP packets that are exchanged with the peer. The peer uses the LACP packets to determine whether a given port should carry traffic for the bundle.
For Multi-Gigabit Service Control Point (MGSCP), the bundle port-priority command applies to working links.
Note
A lower LACP value is a higher LACP priority for the port.
Task ID
Examples
The following example shows how to configure LACP priority on a port:
RP/0/RSP0/CPU0:router# config RP/0/RSP0/CPU0:router(config)# interface gigabitethernet 0/1/0/1 RP/0/RSP0/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 | port { GigabitEthernet 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.
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.
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
hw-module load-balance bundle l2-service l3-params
Note
Effective with Cisco IOS XR Release 4.0.1, the hw-module load-balance bundle l2-service l3-params command is replaced by the load-balancing flow L2VPN configuration command. See the load-balancing flow command in the Cisco ASR 9000 Series Aggregation Services Router L2VPN and Ethernet Services Command Reference for more information.
To configure load balancing for L2 services using L3 parameters, use the hw-module load-balance bundle l2-service l3-params command in global configuration mode. To disable load balance L2 services, use the no form of this command.
hw-module load-balance bundle l2-service l3-params
no hw-module load-balance bundle l2-service l3-params
Command History
Release
Modification
Release 3.9.1
This command was introduced.
Release 4.0.0
This command was replaced by the load-balancing flow command.
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 enables the L2 service-specific load-balancing for bundle Ethernet Flow Points (EFPs). By default, bundle load-balancing is done based on the MAC SA/DA fields in the packet header. When L2 service-specific load-balancing is configured, all traffic egressing bundle EFPs are load-balanced based on the IPv4 source and destination addresses in the packet. If the packet does not have IPv4 addresses, the default load-balancing is used.
Task ID
interface (bundle)
To create a new bundle and enter interface configuration mode for that bundle, use the interface (bundle) command in global configuration mode. To delete a bundle, use the no form of this command.
Syntax Description
Bundle-Ether Specifies or creates an Ethernet 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
isolation recovery-delay
To specify a delay before clearing the isolation condition after recovery from failure, use the isolation recovery-delay command in the redundancy group ICCP configuration mode. To return to the default value, use the no form of this command.
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.
Examples
The following example shows how to configure ICCP parameters:RP/0/RSP0/CPU0:router# configure RP/0/RSP0/CPU0:router(config)# redundancy iccp group 10 RP/0/RSP0/CPU0:router(config-redundancy-iccp-group)# isolation recovery-delay 35 RP/0/RSP0/CPU0:router(config-redundancy-iccp-group)#Task ID
lacp cisco enable
To enable use of Cisco-specific TLVs in addition to standard TLVs for negotiating and exchanging LACP information on link bundles, use the lacp cisco enable command in interface configuration mode. To return to the default, use the no form of the command.
Syntax Description
link-order signaled (Optional) Includes link order numbering as part of the LACP processing.
Note This keyword is required for MGSCP.
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.
The lacp cisco enable link-order signaled command is required on bundle interfaces supporting deployment of Multi-Gigabit Service Control Point (MGSCP), and must be configured symmetrically on both the access and core bundle. When link order signaling is enabled, then only one set of Link Ordering Numbers (LONs) are used for the bundle, and LACP processing of LONs is enabled for load balancing tables.
The LONs from the highest priority LACP system take precedence. Where both systems have the same LACP system ID (for example, with MGSCP where both ends of the bundle terminate on the same device), the LONs from the bundle interface with the numerically lowest bundle ID take precedence.
When lacp cisco enable command is configured without link order signaling, then links are assigned ordering numbers as they become active and keep them until the link goes inactive. The numbers are exchanged using LACP, but they are not used.
Task ID
Examples
Example
The following example enables the use of Cisco TLVs to include link order numbering as part of the LACP processing on this bundle:
RP/0/RSP0/CPU0:router(config)# interface Bundle-Ether 100 RP/0/RSP0/CPU0:router(config-if)# lacp cisco enable link-order signaledlacp fast-switchover
To disable the wait-while timer in the LACP state machine, use the lacp fast-switchover command in interface configuration mode. To re-enable the wait-while timer, use the no form of this command.
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 have 1:1 link protection enabled (you set the value of the bundle maximum-active links command to 1) on a bundle with member links running LACP, you can optionally disable the wait-while timer in the LACP state machine. Disabling this timer causes a bundle member link in standby mode to expedite its normal state negotiations, thereby enabling a faster switchover from a failed active link to the standby link.
Regardless of the type of switchover you are using, the default IEEE standard-based or the faster proprietary optimized switchover, the state negotiations of the standby link is expedited. (For more information about the switchover types, refer to the bundle maximum-active links command.) However, enabling the lacp fast-switchover command provides a greater benefit if used with the IEEE standard-based switchover.
Examples
The following example shows how to disable the wait-while timer for LACP-enabled member links of Bundle-Ether 28:
RP/0/RSP0/CPU0:router(config)# interface Bundle-Ether 28 RP/0/RSP0/CPU0:router(config-if)# lacp fast-switchoverThe following example shows how to re-enable the wait-while timer for LACP-enabled member links of Bundle-Ether 28:
RP/0/RSP0/CPU0:router(config)# interface Bundle-Ether 28 RP/0/RSP0/CPU0:router(config-if)# no lacp fast-switchoverlacp 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 | tengige interface-path-id number-of-packets }
To stop capturing LACP packets or to clear captured LACP packets, use the lacp packet-capture command in EXEC mode. { lacp packet-capture [ bundle-ether bundle-id ] [ gigabitethernet interface-path-id ] [ tengige interface-path-id ] clear | stop }
Syntax Description
bundle-ether
Ethernet bundle interface specified by bundle-id.
GigabitEthernet
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 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
RP/0/RSP0/CPU0:router# lacp packet-capture pos 0/1/0/0 100RP/0/RSP0/CPU0:router# lacp packet-capture pos 0/1/0/0 stopRP/0/RSP0/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/RSP0/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/RSP0/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
Router A
The following example shows how to enable a default Link Aggregation Control Protocol (LACP) short period on a Gigabit Ethernet interface:
RP/0/RSP0/CPU0:router# config RP/0/RSP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0 RP/0/RSP0/CPU0:router(config-if)# lacp period short RP/0/RSP0/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/RSP0/CPU0:router# config RP/0/RSP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0 RP/0/RSP0/CPU0:router(config-if)# lacp period short RP/0/RSP0/CPU0:router(config-if)# commitRP/0/RSP0/CPU0:router# config RP/0/RSP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0 RP/0/RSP0/CPU0:router(config-if)# lacp period short RP/0/RSP0/CPU0:router(config-if)# commitRP/0/RSP0/CPU0:router# config RP/0/RSP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0 RP/0/RSP0/CPU0:router(config-if)# lacp period short transmit 500 RP/0/RSP0/CPU0:router(config-if)# commitRP/0/RSP0/CPU0:router# config RP/0/RSP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0 RP/0/RSP0/CPU0:router(config-if)# lacp period short transmit 500 RP/0/RSP0/CPU0:router(config-if)# commitRP/0/RSP0/CPU0:router# config RP/0/RSP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0 RP/0/RSP0/CPU0:router(config-if)# lacp period short receive 500 RP/0/RSP0/CPU0:router(config-if)# commitRP/0/RSP0/CPU0:router# config RP/0/RSP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0 RP/0/RSP0/CPU0:router(config-if)# lacp period short receive 500 RP/0/RSP0/CPU0:router(config-if)# commitlacp system priority
To configure the priority for the current system, enter the lacp system priority command in global configuration mode. To return to the default LACP system priority value, use the no form of this command.
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/RSP0/CPU0:router(config)# lacp system priority 100member neighbor
To configure interchassis group ICCP members, use the member neighbor command in redundancy ICCP group configuration mode. To return to the default behavior, use the no form of this command.
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.
Task ID
Examples
The following example shows how to configure interchassis group ICCP members:RP/0/RSP0/CPU0:router# configure RP/0/RSP0/CPU0:router(config)# redundancy iccp group 10 RP/0/RSP0/CPU0:router(config-redundancy-iccp-group)# member neighbor 10.1.1.1 RP/0/RSP0/CPU0:router(config-redundancy-iccp-group)#mlacp connect
To specify configuration options for connecting to mLACP peers, use the mlacp connect command in the redundancy ICCP group configuration mode. To disable this feature, use the no form of this command.
Syntax Description
timeout
Specifies the time to wait before assuming mLACP peer is down.
seconds
Number of seconds to wait before assuming the mLACP peer is down.
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 specify configuration options for connecting to mLACP peers:
RP/0/RSP0/CPU0:router# configure RP/0/RSP0/CPU0:router(config)# redundancy iccp group 10 RP/0/RSP0/CPU0:router(config-redundancy-iccp-group)# mlacp connect timeout 100 RP/0/RSP0/CPU0:router(config-redundancy-iccp-group)#mlacp iccp-group
To configure ICCP redundancy group for a bundle, use the mlacp iccp-group command in bundle interface configuration mode. To return to the default value, use the no form of this command.
Syntax Description
group-id
Specifies the ICCP redundancy group in which the bundle should operate. The group-id value ranges between 1-4294967295.
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
mlacp node
To configure the mLACP node ID to be used in the ICCP group, use the mlacp node command in the redundancy ICCP group configuration mode. To return to the default value, use the no form of this command.
Syntax Description
node-id
Specifies the unique node ID in the ICCP group for this system. The node-id value ranges between 0 to 7.
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
mlacp port-priority
To set the priority for all member links, use the mlacp port-priority command in bundle interface configuration mode. To return to the default value, use the no form of this command.
Syntax Description
priority
Specifies the priority for member ports. The priority value ranges between 1-65535. A lower value indicates 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.
Task ID
mlacp system mac
To configure the LACP system ID to be used in an ICCP group, use the mlacp system mac command in the redundancy ICCP group configuration mode. To return to the default value, use the no form of this command.
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.
Task ID
mlacp system priority
To configure the LACP system priority to be used in the ICCP group, use the mlacp system priority command in the redundancy ICCP group configuration mode. To return to the default value, use the no form of this command.
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.
Task ID
redundancy iccp group
To configure Inter Chassis Communication Protocol (ICCP) parameters, use the redundancy iccp group command in the global configuration mode. To return to the default, use the no form of this command.
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.
Task ID
redundancy one-way
To enforce one-way pseudowire redundancy behavior when the redundancy group is configured, use the redundancy one-way command in the L2VPN pseudowire class configuration mode. To return to the default, use the no form of this command.
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 :RP/0/RSP0/CPU0:router# configure RP/0/RSP0/CPU0:router(config)# l2vpn RP/0/RSP0/CPU0:router(config-l2vpn)# pw-class class_mpls RP/0/RSP0/CPU0:router(config-l2vpn-pwc)# encapsulation mpls RP/0/RSP0/CPU0:router(config-l2vpn-pwc-mpls)# redundancy one-way RP/0/RSP0/CPU0:router(config-l2vpn-pwc-mpls)#show 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
Release Modification Release 3.7.2
This command was introduced.
Release 3.8.0
The reasons keyword was removed.
Release 4.0.0
The output for this command was replaced with a new format.
Release 4.1.0
The following output fields were added: Release 4.2.0
Support for Bundle-POS was added.
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-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/RSP0/CPU0:router# show bundle Bundle-Ether 2 Status: Up Local links <active/standby/configured>: 1 / 0 / 1 Local bandwidth <effective/available>: 100000 (100000) kbps MAC address (source): 1234.4321.1111 (Gi0/0/0/1) Minimum active links / bandwidth: 1 / 500 kbps Maximum active links: 32 Wait-while timer: 2000 ms Load-balancing: Default LACP: Operational Flap suppression timer: 2500 ms Cisco extensions: Disabled mLACP: Operational Interchassis group: 3 Foreign links <active/configured>: 1 / 1 Switchover type: Revertive Recovery delay: 300 s Maximize threshold: 2 links 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/0/0/1 Local Active 0x8000, 0x0001 100000 MyFirstInterface 10.10.10.123 Negotiating 0x8000, 0x0032 100000 Bundle-Ether 3 Status: Up Local links <active/standby/configured>: 1 / 0 / 1 Local bandwidth <effective/available>: 100000 / 100000 kbps MAC address (source): 1234.4321.2222 (chassis pool) Minimum active links / bandwidth: 1 / 500 kbps Maximum active links: 32 (from partner) Wait-while timer: 100 ms Load-balancing: Link order signaling: Operational Hash type: Src-IP LACP: Operational Flap suppression timer: 120 s Cisco extensions: Enabled mLACP: Not configured IPv4 BFD: Not operational Port Device State Port ID B/W, kbps -------------------- --------------- ----------- -------------- ----------- Gi0/0/0/2 Local Active 0x8000, 0x0002 100000
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
The following 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/RSP0/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.
Table 4 show bundle brief Field Descriptions Field Description Name
Abbreviated name of the bundle interface, with the following possible formats:
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:
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 bundle load-balancing
To display load balancing information, such as the ports, usage, weight, and distribution of traffic on individual members of a link bundle interface, use the show bundle load-balancing 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.
Bundle-POS bundle-id
(Optional) Specifies the number of the POS bundle whose information you want to display. Range is 1 through 65535.
brief
(Optional) Displays summary information for all nodes or for a specified location.
detail
(Optional) Displays detailed information for all nodes or for a specified location.
location
(Optional) Specifies the location of the node.
For more information about the syntax for the router, use the question mark (?) online help function.
Command Default
When the brief or detail keywords are used and no location is specified, information is displayed for all nodes on the router.
Command History
Release
Modification
Release 3.9.0
This command was introduced.
Release 4.2.0
The Bundle-POS keyword 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.
Task ID
Examples
Example 1
The following examples show how to use the show bundle load-balancing command and its various keywords:
RP/0/RSP0/CPU0:router# show bundle load-balancing brief Node: 0/0/CPU0 Sub-Intf Member Total Interface Count Count Wgt. ----------------- -------- ------------ Bundle-Ether12345 10 63 134 Node: 0/1/CPU0 Sub-Intf Member Total Interface Count Count Wgt. ----------------- -------- ------------ Bundle-Ether12345 10 63 134 show bundle load-balancing brief location 0/0/CPU0 Node: 0/0/CPU0 Sub-Intf Member Total Interface Count Count Wgt. ----------------- -------- ------------ Bundle-Ether12345 10 63 134RP/0/RSP0/CPU0:router# show bundle load-balancing location 0/0/CPU0 ============================================================================== Bundle-Ether12345 Type: Ether (L2) Members: 63 Total Weighting: 134 Sub-interfaces: 10 Member Information: Port ID BW ------------ -- -- Gi0/0/0/1 0 10 Gi0/0/0/3 1 1 [...] Platform Information: ===================== Bundle Summary Information: --------------------------- Interface : Bundle-Ether100 Ifhandle : 0xa0000a0 Lag ID : 1 Virtual Port : 20 Number of Members : 4 Local to LC : 1 Member Information: ul_id Interface ifhandle SFP port slot ----- --------- --------- --- ---- ---- 0 Gi0/4/0/3 0x8000100 16 3 4 1 Gi0/4/0/10 0x80002c0 17 10 4 2 Gi0/4/0/17 0x8000480 17 17 4 3 Gi0/4/0/24 0x8000640 18 4 4 Bundle Table Information: ------------------------- [NP 0]: --------------------------------------------------------------------- Unicast (Global) LAG table | Multicast (Local) LAG table --------------------------------------------------------------------- idx local ul_id SFP port | idx local ul_id SFP port --------------------------------------------------------------------- 1 1 0 16 3 1 1 0 16 3 2 1 1 17 10 2 1 1 17 10 3 1 2 17 17 3 1 2 17 17 4 0 3 18 4 4 0 3 18 4 5 1 0 16 3 5 1 0 16 3 6 1 1 17 10 6 1 1 17 10 7 1 2 17 17 7 1 2 17 17 8 0 3 18 4 8 0 3 18 4 [NP 1]: --------------------------------------------------------------------- Unicast (Global) LAG table | Multicast (Local) LAG table --------------------------------------------------------------------- idx local ul_id SFP port | idx local ul_id SFP port --------------------------------------------------------------------- 1 0 0 16 3 1 0 0 16 3 2 0 1 17 10 2 0 1 17 10 3 0 2 17 17 3 0 2 17 17 4 1 3 18 4 4 1 3 18 4 5 0 0 16 3 5 0 0 16 3 6 0 1 17 10 6 0 1 17 10 7 0 2 17 17 7 0 2 17 17 8 1 3 18 4 8 1 3 18 4 ============================================================================== Bundle-POS3 Type: POS (L3) Members: 2 Total Weighting: 2 Sub-interfaces: 0 Member Information: Port: ID BW ------------ -- -- POS0/2/0/1 3 1 POS0/4/0/0 4 1 ==============================================================================RP/0/RSP0/CPU0:router# show bundle load-balancing Bundle-Ether 12345 detail location 0/0/CPU0 Bundle-Ether12345 Type: Ether (L2) Members: 63 Total Weighting: 134 Sub-interfaces: 10 Member Information: Port ID BW ------------ -- -- Gi0/0/0/1 0 10 Gi0/0/0/3 1 1 [...] Sub-interface Information: Sub-interface Type Load Balance ---------------------------- ---- ------------ Bundle-Ether12345.4294967295 L2 Default Bundle-Ether12345.2 L2 Hash: XID Bundle-Ether12345.3 L2 Fixed: 2 [...]RP/0/RSP0/CPU0:router# show bundle load-balancing Bundle-Ether12345.2 location 0/0/CPU0 Bundle-Ether12345 Type: Ether (L2) Members: 63 Total Weighting: 134 Sub-interfaces: 10 Sub-interface Information: Sub-interface Type Load Balance ---------------------------- ---- ------------ Bundle-Ether12345.2 L2 Hash: XID Platform Information: ===================== Bundle Summary Information: --------------------------- Interface : Bundle-Ether100 Ifhandle : 0xa0000a0 Lag ID : 1 Virtual Port : 20 Number of Members : 4 Local to LC : 1 Member Information: ul_id Interface ifhandle SFP port slot ----- --------- --------- --- ---- ---- 0 Gi0/4/0/3 0x8000100 16 3 4 1 Gi0/4/0/10 0x80002c0 17 10 4 2 Gi0/4/0/17 0x8000480 17 17 4 3 Gi0/4/0/24 0x8000640 18 4 4 Bundle Table Information: ------------------------- [NP 0]: --------------------------------------------------------------------- Unicast (Global) LAG table | Multicast (Local) LAG table --------------------------------------------------------------------- idx local ul_id SFP port | idx local ul_id SFP port --------------------------------------------------------------------- 1 1 0 16 3 1 1 0 16 3 2 1 1 17 10 2 1 1 17 10 3 1 2 17 17 3 1 2 17 17 4 0 3 18 4 4 0 3 18 4 5 1 0 16 3 5 1 0 16 3 6 1 1 17 10 6 1 1 17 10 7 1 2 17 17 7 1 2 17 17 8 0 3 18 4 8 0 3 18 4show 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 iccp group
Syntax Description
group-id
ICCP group ID.
location
Specifies the location.
node-id
Node ID. The node-id argument is entered in the rack/slot/module notation.
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
Example 1
The following example shows the output of the show iccp group command:
RP/0/RSP0/CPU0:router#show iccp group Redundancy Group 1 member ip:2.2.2.2 (router2), up (connected) monitor: route-watch (up) backbone interface Gi0/2/0/3: up enabled applications: mLACP isolation recovery delay timer: 180 s, not running Redundancy Group 2 member ip:2.2.2.2 (router2), up (disconnected) monitor: route-watch (up) backbone interface Gi0/2/0/3: up enabled applications: mLACP isolation recovery delay timer: 180 s, not runningRP/0/RSP0/CPU0:router#show iccp group 1 Redundancy Group 1 member ip:2.2.2.2 (router2), up (connected) monitor: route-watch (up) backbone interface Gi0/2/0/3: up enabled applications: mLACP isolation recovery delay timer: 180 s, not runningshow 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.
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/RSP0/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.
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/RSP0/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.
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.
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.
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/RSP0/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/RSP0/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)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.
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.
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
Example 1
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/RSP0/CPU0:router# lacp packet-capture gigabitethernet 0/1/0/0 100 RP/0/RSP0/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/RSP0/CPU0:router# lacp packet-capture gigabitethernet 0/1/0/0 100 RP/0/RSP0/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.
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 port information for all link bundles on a router:
RP/0/RSP0/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/RSP0/CPU0:router# show lacp system-id Priority MAC Address -------- ----------------- 0x8000 08-00-45-3a-65-01show mlacp
To display the MC-LAG information configured locally and for any connected mLACP peer devices, use the show mlacp command in the EXEC mode.
Syntax Description
Bundle-Ether interface-path-id
Displays the information for the ICCP group of the bundle and only the specified bundle.
iccp-group group-id
Displays information related to the ICCP group.
brief
Displays only the ICCP group information without any bundle information.
verbose
Displays the ICCP group, the bundle and member information.
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 examples display the MC-LAG information:
RP/0/RSP0/CPU0:router# show mlacp brief ICCP Group 1 Connect timer: Off Node LDP ID State System ID Sync Vers ---- --------------- ------------ ------------------------ ----- ---- 1 5.4.3.1 Up 0x0001,00-0d-00-0e-00-0f Done 1 2 Local Up 0x0001,00-0d-00-0e-00-0f Done - RP/0/RP0/CPU0:poa2#show mlacp ICCP Group 1 Connect timer: Off Node LDP ID State System ID Sync Vers ---- --------------- ------------ ------------------------ ----- ---- 1 5.4.3.1 Up 0x0001,00-0d-00-0e-00-0f Done 1 2 Local Up 0x0001,00-0d-00-0e-00-0f Done - Bundle-Ether1 (ROID: 0000.0001.0000.0000) Node Aggregator Name State Agg ID MAC Address ---- -------------------- ---------- ------ --------------- 1 BE1 Up 0x0001 0000.deaf.0000 2 Bundle-Ether1 Up 0x0001 0000.deaf.0000 RP/0/RP0/CPU0:router#show mlacp verbose ICCP Group 1 Connect timer: Off Node LDP ID State System ID Sync Vers ---- --------------- ------------ ------------------------ ----- ---- 1 5.4.3.1 Up 0x0001,00-0d-00-0e-00-0f Done 1 2 Local Up 0x0001,00-0d-00-0e-00-0f Done - Bundle-Ether1 (ROID: 0000.0001.0000.0000) Node Aggregator Name State Agg ID MAC Address ---- -------------------- ---------- ------ --------------- 1 BE1 Up 0x0001 0000.deaf.0000 2 Bundle-Ether1 Up 0x0001 0000.deaf.0000 Priority Node Port Name State Port Oper (Cfgd) ---- -------------------- ---------- ------ --------------- 1 Gi0/1/0/3 Up 0x9001 0x03e8 (0x03e8) 2 Gi0/0/0/1 Up 0xa001 0x07d0 (0x07d0)show mlacp counters
To display counters relating to mLACP information transferred to and from the local device, use the show mlacp counters command in the EXEC mode.
show mlacp counters [ bdl-info | ig-info | mbr-info [ bundle interface | member interface | iccp-group group-id | mlacp-device device-id | mlacp-interface foreign-member-interface ] ]
Syntax Description
Bundle-Ether
Displays the requested information associated with the bundle interface.
member interface
Displays the requested information associated with the member interface.
counters
Displays information on the mLACP counters.
bdl-info
Displays the bundles counters.
ig-info
Displays the ICCP group counters.
mbr-info
Displays the member counters.
mlacp-device
Displays the requested information associated with the mLACP device.
Note The mlacp-device and mlacp-interface keywords are available only when mLACP devices and mLACP interfaces are configured.
mlacp-interface
Displays the requested information associated with the mLACP interface.
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 examples display MC-LAG counter information:
Note
The GigabitEthernet 0/0/0/1 is configured to Bundle-Ether 1 which is within ICCP Group1. Hence, the show mlacp counters bdl-info GigabitEthernet 0/0/0/1 command displays the counters of the bundle that GigabitEthernet 0/0/0/1 is associated with (i.e. Bundle-Ether1). The show mlacp counters mbr-info Bundle-Ether 1 displays the counters of the members that Bundle-Ether1 is associated with (locally: GigabitEthernet 0/0/0/1, and on the foreign device: GigabitEthernet 0/1/0/3).
RP/0/RSP0/CPU0:router# show mlacp counters bdl-info GigabitEthernet 0/0/0/1 ICCP Group 1 TLVs Sent TLVs Received Bundle Config State Priority NAKs Priority -------------------- -------------------------------- --------------------- Local Device Bundle-Ether1 ????????????3 4 0 0 0 mLACP Peer 5.4.3.1 Bundle-Ether1 ????????????3 4 0 0 0 Sync Requests Bundle TLVs (config) (state) Last Cleared -------------------- -------------------------------- ------------ Local Device Bundle-Ether1 ???????????0 0 0 18m12s mLACP Peer 5.4.3.1 Bundle-Ether1 ???????????0 0 0 17m57s RP/0/0/CPU0:router#show mlacp counters mbr-info Bundle-Ether 1 Bundle-Ether1 (ICCP Group 1) TLVs Sent TLVs Received Port Config State Priority NAKs Priority -------------------- -------------------------------- --------------------- Local Device Gi0/0/0/1 ????????????????7 0 0 0 0 mLACP Peer 5.4.3.1 Gi0/1/0/3 ????????????????7 5 3 0 0 Sync Requests Port TLVs (config) (state) Last Cleared -------------------- -------------------------------- ------------ Local Device All ports ?????????????????0 0 0 19m3s Gi0/0/0/1 ?????????????????0 0 0 19m3s mLACP Peer 5.4.3.1 All ports ?????????????????1 1 1 18m49s Gi0/1/0/3 ?????????????????0 0 0 18m49s
