Table Of Contents

Link Bundling Commands on Cisco IOS XR Software

bundle

bundle id

bundle-hash

bundle maximum-active links

bundle minimum-active bandwidth

bundle minimum-active links

bundle port-priority

clear lacp counters

interface Bundle-Ether

interface Bundle-POS

lacp period short

lacp system-priority

show bundle Bundle-Ether

show bundle Bundle-POS

show lacp bundle

show lacp counters

show lacp port

show lacp system-id

Link Bundling Commands on Cisco IOS XR Software

---

This module contains commands for configuring and monitoring Link Bundling on Cisco IOS XR software.

bundle

To create a multilink interface bundle, use the bundle command in the interface configuration mode. To remove a multilink interface bundle, use the no form of this command.

bundle bundleID

Syntax Description

bundleID

ID number of the multilink interface bundle. Range is from 1 through 1024.

Defaults

No default behavior or values

Command Modes

Interface configuration

Command History

Release	Modification
Release 3.4.1	This command was introduced on the Cisco XR 12000 Series Router.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

The bundle command is used in mgmtmultilink controller mode to dynamically create a multilink interface. This command is similar to the channel-group command on the T1 controller, which dynamically creates a serial interface.

Task ID

Task ID	Operations
sonet-sdh	read, write

Examples

The following example shows how to create a multilink interface with a bundle ID of 1:

RP/0/0/CPU0:router# configure

RP/0/0/CPU0:router(config)# controller mgmtmultilink 0/1/0/0

RP/0/0/CPU0:router(config-mgmtmultilink)# bundle 1

RP/0/0/CPU0:router(config-mgmtmultilink)# commit

This line prevents blank table in PDF.

Related Commands

Command	Description
multilink	Enters the config-if-multilink submode.
multilink fragment-size	Sets the fragment size to be used on the multilink interface.
multilink group	Adds the serial interface to the multilink interface.
ppp multilink minimum-active links	Sets the minimum number of active links required before the multilink interface line can be brought to the up state.

bundle id

To add a port to an aggregated interface (or bundle), enter the bundle id command in interface configuration mode.

bundle id bundle-id [mode {active | on | passive]

no bundle id bundle-id

Syntax Description

bundle-id	Bundle on which you want to add a port. Range is 1 through 65535.
bundle-id.vlan_id	VLAN bundle on which you want to add a port. The VLAN bundle ID is entered in the bundle-id.vlan_id format, and a period between the bundle-id and vlan_id arguments is required. •Replace the bundle-id argument with the bundle ID. Range is from 1 through 65535. •Replace the vlan_id argument with the VLAN trunk interface ID. Range is from 1 to 4094 inclusive (0 and 4095 are reserved). Note The vlan_id argument is available only for Ethernet bundles. You can not add a VLAN subinterface on a POS bundle.
mode	(Optional) Specifies the mode of operation, as follows: •active—Use the mode active keywords to run Link Aggregation Control Protocol (LACP) in active mode over the port. When you specify active, the port joins the bundle and is activated if LACP determines that it is compatible. •on—Use the mode on keywords to add the link to a bundle without running LACP over the port. •passive—Use the mode passive keywords to run LACP in passive mode over the port. When you specify passive, LACP packets are sent only if the other end of the link is using active LACP. The link joins the bundle and is activated if LACP packets are exchanged and the port is compatible.

Defaults

mode = on

Command Modes

Interface configuration

Command History

Release	Modification
Release 3.2	This command was introduced on the Cisco CRS-1.
Release 3.3.0	The bundle id command syntax was changed from bundle-id.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

If you enter the bundle id command and specify a port that is already bound to a bundle, the port unbinds from the original bundle and becomes attached to the new bundle. If the bundle numbers are the same, then the port does not unbind, but the mode changes to mode you specified with the bundle id command.

Task ID

Task ID	Operations
bundle	read, write

Examples

The following example shows how to add a port onto a bundle:

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

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

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

Related Commands

Command	Description
show bundle Bundle-Ether	Displays information about a specific Ethernet bundle.
show bundle Bundle-POS	Displays information about a specific POS bundle.
show interfaces	Displays statistics for all interfaces configured on the router or on a specific node.
show lacp bundle	Displays detailed information about LACP ports and their peers.
show lacp port	Displays detailed information about LACP ports.

bundle-hash

To calculate load balancing across the members of a multilink interface bundle, use the bundle-hash command in the EXEC mode.

bundle-hash bundleID

Syntax Description

bundleID

ID number of the multilink interface bundle. Range is from 1 through 1024.

Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release	Modification
Release 3.6.0	This command was introduced on the Cisco CRS-1 and the Cisco XR 12000 Series Router.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Bundle interface traffic is distributed over the various member links of a bundle according to a hash function. The bundle-hash command displays the load-balancing information.

This information includes such things as the member link on which the traffic for a specific source address and destination address is transmitted, or how the load balancing is distributed on member links for a specific subnet.

Task ID

Task ID	Operations
bundle	read

Examples

The following example shows how to calculate load balancing across the members of a multilink interface bundle:

RP/0/RP0/CPU0:router# bundle-hash bundleID 100

Related Commands

Command	Description
bundle id	Adds a port to an aggregated interface (or bundle).

bundle maximum-active links

To limit the number of links that can be actively carrying traffic in a specific bundle, use the bundle maximum-active links command in interface configuration mode.

bundle maximum-active links links

Syntax Description

links

Number of active links you want to bring up in the specified bundle. Replace the links with 1. Note In Release 3.3.0, only one active link is supported.

Defaults

No default behavior or values

Command Modes

Interface configuration

Command History

Release	Modification
Release 3.3.0	This command was introduced on the Cisco CRS-1.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

---

Note The bundle maximum-active links command is supported only for bundles that are not running LACP.

---

---

Note 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

Task ID	Operations
bundle	read, write

Examples

The following example shows how to set the number of active links required to bring up a specific bundle. In this example, the user sets the required number of active links required to bring up POS bundle 5 to 2:

RP/0/RP0/CPU0:router(config)# interface Bundle-POS 5

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

Related Commands

Command	Description
bundle minimum-active links	Sets the minimum amount of bandwidth required before a user can bring up a specific bundle.
show bundle Bundle-Ether	Displays information about a specific Ethernet bundle.
show bundle Bundle-POS	Displays information about a specific POS bundle.

bundle minimum-active bandwidth

To set the minimum amount of bandwidth required before a user can bring up a specific bundle, use the bundle minimum-active bandwidth command in interface configuration mode.

bundle minimum-active bandwidth kbps

Syntax Description

kbps	Minimum bandwidth required before you can bring up a bundle. Range is from 1 through a number that is equivalent to the combined bandwidths of 32 OC768 interfaces.

Defaults

kbps = 1

Command Modes

Interface configuration

Command History

Release	Modification
Release 3.3.0	This command was introduced on the Cisco CRS-1.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Task ID

Task ID	Operations
bundle	read, write

Examples

The following example shows how to set the minimum amount of bandwidth required before a user can bring up a specific bundle. In this example, the user sets the minimum amount of bandwidth required to bring up Ethernet bundle 1 to 620000:

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

RP/0/RP0/CPU0:router(config-if)# bundle minimum-active bandwidth 620000

Related Commands

Command	Description
show bundle Bundle-Ether	Displays information about a specific Ethernet bundle.
show bundle Bundle-POS	Displays information about a specific POS bundle.

bundle minimum-active links

To set the number of active links required to bring up a specific bundle, use the bundle minimum-active links command in interface configuration mode.

bundle minimum-active links links

Syntax Description

links

Number of active links you want to bring up in the specified bundle. Range is from 1 through 32.

Defaults

No default behavior or values

Command Modes

Interface configuration

Command History

Release	Modification
Release 3.3.0	This command was introduced on the Cisco CRS-1.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Task ID

Task ID	Operations
bundle	read, write

Examples

The following example shows how to set the number of active links required to bring up a specific bundle. In this example, the user configures POS bundle 5 so that 2 links must be active before the bundle can be brought up:

RP/0/RP0/CPU0:router(config)# interface Bundle-POS 5

RP/0/RP0/CPU0:router(config-if)# bundle minimum-active links 2

Related Commands

Command	Description
bundle maximum-active links	Sets the active links required to bring up a specific bundle.
show bundle Bundle-Ether	Displays information about a specific Ethernet bundle.
show bundle Bundle-POS	Displays information about a specific POS bundle.

bundle port-priority

To configure LACP priority for a port, enter the bundle port-priority command in interface configuration mode. To return to the default Link Aggregation Control Protocol (LACP) priority value, use the no form of this command.

bundle port-priority priority

no bundle port-priority priority

Syntax Description

priority

Priority for this port, where a lower value equals a higher priority. Replace the priority argument with a number. Range is from 0 through 65535.

Defaults

priority = 32768

Command Modes

Interface configuration

Command History

Release	Modification
Release 3.2	This command was introduced on the Cisco CRS-1.
Release 3.3.0	The command name was changed from lacp port-priority to bundle port-priority.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

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.

---

Note A lower LACP value is a higher LACP priority for the port.

---

Task ID

Task ID	Operations
bundle	read, write

Examples

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

RP/0/RP0/CPU0router(config-if)# bundle port-priority 1

Related Commands

Command	Description
bundle id	Adds a port to an aggregated interface (or bundle).
show lacp bundle	Displays detailed information about LACP ports and their peers.
show lacp port	Displays detailed information about LACP ports.
show lacp system-id	Displays the local system ID used by LACP.

clear lacp counters

To clear Link Aggregation Control Protocol (LACP) counters for all members of all bundles, all members of a specific bundle, or for a specific port, enter the clear lacp counters command in EXEC mode.

clear lacp counters [bundle {Bundle-Ether bundle-id | Bundle-POS bundle-id} | port {GigabitEthernet interface_instance | TenGigE interface_instance | POS interface_instance}]

Syntax Description

bundle	Clears LACP counters for all members of a bundle.
Bundle-Ether node-id	Specifies the Ethernet bundle whose LACP counters you want to clear. Replace node-id with a number. Range is from 1 through 65535.
Bundle-POS bundle-id	Specifies the POS bundle whose LACP counters you want to clear. Replace bundle-id with a bundle identifier. Range is from 1 through 65535.
port	Clears all LACP counters on the specified bundle or interface.
GigabitEthernet interface_instance	Specifies the Gigabit Ethernet interface whose LACP counters you want to clear. Replace bundle-id with the number of the bundle you want to clear.
TenGigE interface_instance	TenGigE interface whose LACP counters you want to clear. The interface_instance is expressed in the rack/slot/module/port notation.
POS interface_instance	Specifies the Packet-over-SONET/SDH (POS) interface whose LACP port counters you want to clear. The interface_instance is expressed in the rack/slot/module/port notation.

Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release	Modification
Release 3.2	This command was introduced on the Cisco CRS-1.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Task ID

Task ID	Operations
bundle	execute
basic-services	read, write

Examples

The following example shows how to clear LACP counters:

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

Related Commands

Command	Description
show lacp counters	Displays LACP statistics.

interface Bundle-Ether

To create a new Ethernet bundle and enter interface configuration mode for that bundle, use the interface Bundle-Ether command in global configuration mode. To delete an Ethernet bundle, use the no form of this command.

interface Bundle-Ether bundle-id

no interface Bundle-Ether bundle-id

Syntax Description

bundle-id

Ethernet bundle you want to create or configure. Replace bundle-id with a bundle identifier. Range is from 1 through 65535.

Defaults

No default behavior or values

Command Modes

Global configuration

Command History

Release	Modification
Release 3.2	This command was introduced on the Cisco CRS-1.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Task ID

Task ID	Operations
bundle	read, write

Examples

The following example shows how to create a new Ethernet bundle and enter interface configuration mode for that bundle.:

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

RP/0/RP0/CPU0:router(config-if)#

Related Commands

Command	Description
show bundle Bundle-Ether	Displays information about a specific Ethernet bundle.

interface Bundle-POS

To create a new Packet-over-SONET/SDH (POS) bundle and enter interface configuration mode for that bundle, use the interface Bundle-POS command in global configuration mode. To delete a POS bundle, use the no form of this command.

interface Bundle-POS bundle-id

no interface Bundle-POS bundle-id

Syntax Description

bundle-id

Number of the POS bundle you want to create or configure. Replace bundle-id with a bundle identifier. Range is from 1 through 65535.

Defaults

No default behavior or values

Command Modes

Global configuration

Command History

Release	Modification
Release 3.2	This command was introduced on the Cisco CRS-1.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Task ID

Task ID	Operations
bundle	read, write

Examples

The following example shows how to create a new POS bundle and enter interface configuration mode for that bundle.:

RP/0/RP0/CPU0:router(config)# interface Bundle-POS 10

RP/0/RP0/CPU0:router(config-if)#

Related Commands

Command	Description
show bundle Bundle-POS	Displays information about a specific Ethernet bundle.

lacp period short

To configure a one second interval between LACP packets that are received from the peer, enter the lacp period command in interface configuration mode. To return to the default LACP period, use the no form of this command.

lacp period short

no lacp period

Syntax Description

This command has no arguments or keywords.

Defaults

If you do not enter the lacp period short command, then the peer transmits LACP packets every 30 seconds

Command Modes

Interface configuration

Command History

Release	Modification
Release 3.2	This command was introduced on the Cisco CRS-1.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Task ID

Task ID	Operations
bundle	read, write

Examples

The following example shows how to configure a one-second interval between LACP packets that are received from the peer:

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

This line prevents blank table in PDF.

Related Commands

Command	Description
bundle id	Adds a port to an aggregated interface (or bundle).
show lacp port	Displays detailed information about LACP ports.
show lacp bundle	Displays detailed information about LACP ports and their peers.

lacp system-priority

To configure the priority for the current system, enter the lacp system-priority command in global configuration mode. To return to the default LACP system-priority value, use the no form of this command.

lacp system-priority priority

Syntax Description

priority

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

Defaults

priority = 32768

Command Modes

Global configuration

Command History

Release	Modification
Release 3.2	This command was introduced on the Cisco CRS-1.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

The system priority value forms part of the LACP system ID, which is transmitted within each LACP packet. The system ID, port ID and key combine to uniquely define a port within a LACP system.

Task ID

Task ID	Operations
bundle	read, write

Examples

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

RP/0/RP0/CPU0router(config)# lacp system-priority 100

This line prevents blank table in PDF.

Related Commands

Command	Description
show lacp system-id	Displays the local system ID used by LACP.
show lacp bundle	Displays detailed information about LACP ports and their peers.
show lacp port	Displays detailed information about LACP ports.

show bundle Bundle-Ether

To display information about a specific Ethernet bundle, enter the show bundle Bundle-Ether command in EXEC mode.

show bundle Bundle-Ether bundle-id [reasons]

Syntax Description

bundle-id	Number of the Ethernet bundle whose information you want to display. Replace bundle-id with a bundle identifier. Range is from 1 through 65535.
reasons	(Optional) Displays the "Mux Reason", which is the reason why each link is in its state.

Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release	Modification
Release 3.2	This command was introduced on the Cisco CRS-1.
Release 3.3.0	•The output for this command was modified. •The reasons keyword was added.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Task ID

Task ID	Operations
bundle	read

Examples

The following is sample output from the show bundle Bundle-Ether command:

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

State: 0 - Port is Detached. 1 - Port is Waiting.

       2 - Port is Attached. 3 - Port is Collecting.

       4 - Port is Distributing.

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  Port ID          B/W (Kbps)  MAC address

 ------------   -----  --------------   ----------  ---------------

 Gi0/0/2/0      0      0x8000, 0x0001      1000000  0800.453a.651d*

The following is sample output from the show bundle Bundle-Ether command with the reasons keyword included in the command string:

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

State: 0 - Port is Detached. 1 - Port is Waiting.

       2 - Port is Attached. 3 - Port is Collecting.

       4 - Port is 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  Port ID          B/W (Kbps)  MAC address

  ------------   -----  --------------   ----------  ---------------

  Gi0/0/2/0      0      0x8000, 0x0001      1000000  0800.453a.651d*

      Link is marked individual by partner

Table 54 describes the significant fields shown in the display.

Table 54 show bundle Bundle-Ether Field Descriptions 

Field	Description
B/W (Kbps)	Bundled interface bandwidth, in kilobits per second.
MAC address	MAC address of the bundle.
Minimum links	Minimum number of active links required before the specified bundle can be activated.
active B/W (Kbps)	Minimum amount of bandwidth required before a user can bring up the specified bundle.
Maximum active links	Maximum number of links that can be actively carrying traffic in the specified bundle.
Port ID	Port identifier, in the rack/slot/module/port format.
State	Current state of the specified port. Possible port states are as follows: •0—Port is Detached •1—Port is Waiting •2—Port is Attached •3—Port is Collecting •4—Port is Distributing
Port ID	Port identifier in hexadecimal format
B/W (Kbps)	Port bandwidth, in kilobits per second.
MAC address	MAC address associated with the specified port.
reason	Brief description of normal and error states of the link. For a listing of each state, along with an explanation about the state, reasons the link is in that state, and possible corrective actions you can take to resolve an error state, see Table 55.

Table 55 Ethernet Link State Explanation, Cause, and Action 

Reasons
State Selection logic has not yet been run for the bundle this link is a member of Explanation Status is not yet determined; process initialization is not complete. Cause In most cases, indicates that the bundlemgr_distrib process has not completed initialization after a restart or failover. If the command is run soon after a restart or failover, this behavior is expected. In other cases, indicates a problem during process initialization. Action Restart the bundlemgr_distrib process. If restarting this process does not work, restart the ifmgr process.
State Link is down Explanation Interface or line protocol state is not operationally up. Possible explanations are that the port is shut down, the port is not connected to a peer or is shut down on the peer, or the L1 or L2 is affected by signalling problems. Cause A normal condition in which the link is shut down or not connected. Other causes include a fault with the line or a misconfiguration of the line protocol. Action Check the port configuration and status on both devices.
State Link is being removed from the bundle Explanation Bundle membership configuration was removed from the link, and the effects of this action are still being processed. Cause If receiving this reason is transient, the condition is normal. If the reason is persistent, a problem is present. Action If reason is persistent, restart the bundlemgr_distrib process.
State Link has wrong duplexity Explanation Link is configured to run LACP but is in half-duplex mode. Or the link duplexity does not match that of the primary link. Cause Link is improperly configured. Links running LACP must be full-duplex, and all links in a bundle must have the same duplexity. Action If LACP is running, check to make sure link is in full-duplex mode. Otherwise, check the duplexity of the other bundle members and correct the duplexity setting of this link accordingly.
State Link has wrong bandwidth Explanation The acceptable bandwidth for links in a bundle is determined by the existing configured links in a bundle. All links must have a bandwidth within a certain range of the first links added. This link has a bandwidth outside that range. Cause Link is improperly configured. All links must have a bandwidth within a certain range of each other. The range is determined by the platform. For the Cisco CRS-1 Router, the range is four times, while the Cisco XR 12000 Series Router requires that the bandwidth is the same on all links. Action Reconfigure the links with the incorrect bandwidth.
State Link is a loopback interface Explanation LACP detected that the peer device has the same LACP system ID as the local device. Cause A port is connected to another port on the same device, or the system ID settings of two devices are identical. This latter case usually indicates a failure to acquire a unique system MAC address from the backplane of the device. Action Check the cabling to ensure that two ports on the same device are not connected. If the connection is between two devices, then check that the backplane is correctly programmed with a base MAC address.
State Link has wrong activity type Explanation The use of LACP on this link is inconsistent with the use of LACP on other links in the bundle. Some links are configured to run LACP, but others are not. Cause Link is improperly configured. All links must either be running LACP or not running LACP. Action Check the LACP configuration on the link, and reconfigure the setting as appropriate.
State Link's bundle already has maximum number of members allowed Explanation A bundle can only have a certain number of members attached to it. This state indicates that more links are configured than can be attached. The Cisco CRS-1 Router has a limit of 32, and the Cisco XR 12000 Series Router has a limit of 8. Cause Although the number of members is over-configured, this condition is normal. Action No action is required. If desired, you can remove the extra links from the bundle and assign them to a different bundle.
State Link is attached to a shared medium Note The detection of this condition is not currently supported. Explanation Link bundles can operate using point-to-point links only. The link is running over a shared media, which makes the link unusable. Cause The link is connected to a shared media device or network. Action Check the connectivity of the link to make sure that all links are point-to-point connections.
State Link has wrong LAG ID Explanation The LAG ID of this link differs from that of the primary link, which indicates that the port on the peer device is not configured to be in the same bundle as the port to which the primary link is connected. It could also indicate that the connections are to different peer devices. Cause Link is improperly configured, or a cabling problem exists. Action Check the link configuration and connectivity, and modify as appropriate.
State Link's bundle does not exist Explanation Link was configured to be a member of a bundle that does not exist. Cause Link is improperly configured. Action Configure the non-existent bundle interface, or reconfigure the link to be in the desired bundle.
State Link's bundle has no primary link Explanation No link is configured to be a member of the bundle that is currently a candidate for aggregation. Cause To be considered a candidate for aggregation, a link must be up, and it must be compatible with previously configured links regarding bandwidth and LACP usage. For links running LACP, the links must also be full-duplex, and the partner must indicate an ability to form an aggregation. If there is no primary link, it is because there are no links that meet these criteria. Action Check all the links in a bundle against the criteria, and take the appropriate action.
State Link's bundle is shut down Explanation The link is configured as a member of a bundle that is shut down. Cause If the bundle is indeed shut down, this condition is normal. Action Clear the shutdown configuration on the bundle.
State Link is marked individual by partner Explanation Peer device has not set the aggregatable bit in the LACPDUs it is sending. The Cisco IOS XR software does not support forming bundles with links that are not marked as aggregatable. Cause Indicates that the peer LACP status is defaulted, which means that LACP packets are not being received. Action Check to make sure that the peer is sending LACP packets and that the packets are delivered to the bundlemgr_local process on the line card where the port is located.
State Link is in InSync state Explanation Indicates that LACP data exchanged between two peer devices is correct, and the link is compatible with other links already in the bundle. Typically, this state is transitory and occurs before the link moves to Collecting and then Distributing states. Cause If link remains in this state, the link may not be synchronized on the peer device. Possible causes are a misconfiguration or cabling error such that the ports on each device are not set up as members of the same bundle on both ends. Action Check the configuration and connectivity, and take the appropriate action.
State Link is in Collecting state Explanation Indicates that LACP data exchanged between two peer devices is correct and that both devices are now synchronized. Typically, this state is transitory and occurs before the link moves to the Distributing state. Cause If the link remains in this state, the peer has not reached Collecting state. Possible causes are a fault with the peer, a loss of packets on the line, or a local software problem that is preventing the transmission to Distributing state. Action Check the peer status, and look for packet loss on the link.
State Link exceeds maximum active limit Explanation You set the bundle maximum-active links to x on the bundle, and there are already x links active in the bundle. As a result, this link is held in standby state (either Detached or Collecting depending on whether the hot-standby option was specified). Cause Assuming that there are actually x active links in the bundle, this condition is normal. Action No action is required.
State Link is in Distributing state Explanation The link is fully active, transmitting and receiving traffic. This reason is not usually displayed because it is the normal stable state. Cause This conditional is normal. Action No action is required.

Related Commands

Command	Description
bundle id	Adds a port to an aggregated interface (or bundle).
show lacp bundle	Displays detailed information about LACP ports and their peers.
show interfaces	Displays statistics for all interfaces configured on the router or on a specific node.

show bundle Bundle-POS

To display information about a specific POS bundle, enter the show bundle Bundle-POS command in EXEC mode.

show bundle Bundle-POS bundle-id [reasons]

Syntax Description

bundle-id	Number of the POS bundle whose information you want to display. Replace bundle-id with a bundle identifier. Range is from 1 through 65535.
reasons	(Optional) Displays the "Mux Reason", which is the reason why each link is in its state.

Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release	Modification
Release 3.2	This command was introduced on the Cisco CRS-1.
Release 3.3.0	•The output for this command was modified. •The reasons keyword was added.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Task ID

Task ID	Operations
bundle	read

Examples

The following is sample output from the show bundle Bundle-POS command:

RP/0/RP0/CPU0:router# show bundle Bundle-POS 5

State: 0 - Port is Detached. 1 - Port is Waiting.

       2 - Port is Attached. 3 - Port is Collecting.

       4 - Port is Distributing.

Bundle-POS5

                                Minimum active     Maximum active

  B/W (Kbps)   MAC address      Links  B/W (Kbps)  Links

  ----------   --------------   -----  ----------  -----

           0   N/A                  1           1     32

  Port           State  Port ID          B/W (Kbps)  MAC address

  ------------   -----  --------------   ----------  ---------------

  PO0/0/0/0      0      0x8000, 0x0001       155520  N/A

  PO0/0/0/1      0      0x8000, 0x0002       155520  N/A

  PO0/0/0/2      0      0x8000, 0x0003       155520  N/A

The following is sample output from the show bundle Bundle-POS command with the reasons keyword included in the command string:

RP/0/RP0/CPU0:router# show bundle Bundle-POS 5 reasons

Bundle-POS5

                                Minimum active     Maximum active

  B/W (Kbps)   MAC address      Links  B/W (Kbps)  Links

  ----------   --------------   -----  ----------  -----

           0   N/A                  1           1     32

  Port           State  Port ID          B/W (Kbps)  MAC address

  ------------   -----  --------------   ----------  ---------------

  PO0/0/0/0      0      0x8000, 0x0001       155520  N/A

      Link is down

  PO0/0/0/1      0      0x8000, 0x0002       155520  N/A

      Link is down

  PO0/0/0/2      0      0x8000, 0x0003       155520  N/A

      Link is down

Table 56 describes the significant fields shown in the display.

Table 56 show bundle Bundle-POS Field Descriptions 

Field	Description
B/W (Kbps)	Bundled interface bandwidth, in kilobits.
MAC address	MAC address of the bundle.
Minimum links	Minimum number of active links required before the specified bundle can be activated.
active B/W (Kbps)	Minimum amount of bandwidth required before a user can bring up the specified bundle.
Maximum active links	Maximum number of links that can be actively carrying traffic in the specified bundle.
Port	Port identifier, in the rack/slot/module/port format.
State	Current state of the specified port.
Port ID	Port identifier, in hexadecimal format.
B/W (Kbps)	Individual interface bandwidth, in kilobits.
MAC address	Mac address for the specified interface.
reason	Brief description of normal and error states of the link. For a listing of each state, along with an explanation about the state, reasons the link is in that state, and possible corrective actions you can take to resolve an error state, see Table 57.

Table 57 POS Link State Explanation, Cause, and Action 

Reasons
State Selection logic has not yet been run for the bundle this link is a member of Explanation Status is not yet determined; process initialization is not complete. Cause In most cases, indicates that the bundlemgr_distrib process has not completed initialization after a restart or failover. If the command is run soon after a restart or failover, this behavior is expected. In other cases, indicates a problem during process initialization. Action Restart the bundlemgr_distrib process. If restarting this process does not work, restart the ifmgr process.
State Link is down Explanation Interface or line protocol state is not operationally up. Possible explanations are that the port is shut down, the port is not connected to a peer or is shut down on the peer, or the L1 or L2 is affected by signalling problems. Cause A normal condition in which the link is shut down or not connected. Other causes include a fault with the line or a misconfiguration of the line protocol. Action Check the port configuration and status on both devices.
State Link is being removed from the bundle Explanation Bundle membership configuration was removed from the link, and the effects of this action are still being processed. Cause If receiving this reason is transient, the condition is normal. If the reason is persistent, a problem is present. Action If reason is persistent, restart the bundlemgr_distrib process.
State Link has wrong bandwidth Explanation The acceptable bandwidth for links in a bundle is determined by the existing configured links in a bundle. All links must have a bandwidth within a certain range of the first links added. This link has a bandwidth outside that range. Cause Link is improperly configured. All links must have a bandwidth within a certain range of each other. The range is determined by the platform. For the Cisco CRS-1 Router, the range is four times, while the Cisco XR 12000 Series Router requires that the bandwidth is the same on all links. Action Reconfigure the links with the incorrect bandwidth.
State Link is a loopback interface Explanation LACP detected that the peer device has the same LACP system ID as the local device. Cause A port is connected to another port on the same device, or the system ID settings of two devices are identical. This latter case usually indicates a failure to acquire a unique system MAC address from the backplane of the device. Action Check the cabling to ensure that two ports on the same device are not connected. If the connection is between two devices, then check that the backplane is correctly programmed with a base MAC address.
State Link has wrong activity type Explanation The use of LACP on this link is inconsistent with the use of LACP on other links in the bundle. Some links are configured to run LACP, but others are not. Cause Link is improperly configured. All links must either be running LACP or not running LACP. Action Check the LACP configuration on the link, and reconfigure the setting as appropriate.
State Link's bundle already has maximum number of members allowed Explanation A bundle can only have a certain number of members attached to it. This state indicates that more links are configured than can be attached. The Cisco CRS-1 Router has a limit of 32, and the Cisco XR 12000 Series Router has a limit of 8. Cause Although the number of members is over-configured, this condition is normal. Action No action is required. If desired, you can remove the extra links from the bundle and assign them to a different bundle.
State Link has wrong LAG ID Explanation The LAG ID of this link differs from that of the primary link, which indicates that the port on the peer device is not configured to be in the same bundle as the port to which the primary link is connected. It could also indicate that the connections are to different peer devices. Cause Link is improperly configured, or a cabling problem exists. Action Check the link configuration and connectivity, and modify as appropriate.
State Link's bundle does not exist Explanation Link was configured to be a member of a bundle that does not exist. Cause Link is improperly configured. Action Configure the non-existent bundle interface, or reconfigure the link to be in the desired bundle.
State Link's bundle has no primary link Explanation No link is configured to be a member of the bundle that is currently a candidate for aggregation. Cause To be considered a candidate for aggregation, a link must be up, and it must be compatible with previously configured links regarding bandwidth and LACP usage. For links running LACP, the links must also be full-duplex, and the partner must indicate an ability to form an aggregation. If there is no primary link, it is because there are no links that meet these criteria. Action Check all the links in a bundle against the criteria, and take the appropriate action.
State Link's bundle is shut down Explanation The link is configured as a member of a bundle that is shut down. Cause If the bundle is indeed shut down, this condition is normal. Action Clear the shutdown configuration on the bundle.
State Link is marked individual by partner Explanation Peer device has not set the aggregatable bit in the LACPDUs it is sending. The Cisco IOS XR software does not support forming bundles with links that are not marked as aggregatable. Cause Indicates that the peer LACP status is defaulted, which means that LACP packets are not being received. Action Check to make sure that the peer is sending LACP packets and that the packets are delivered to the bundlemgr_local process on the line card where the port is located.
State Link is in InSync state Explanation Indicates that LACP data exchanged between two peer devices is correct, and the link is compatible with other links already in the bundle. Typically, this state is transitory and occurs before the link moves to Collecting and then Distributing states. Cause If link remains in this state, the link may not be synchronized on the peer device. Possible causes are a misconfiguration or cabling error such that the ports on each device are not set up as members of the same bundle on both ends. Action Check the configuration and connectivity, and take the appropriate action.
State Link is in Collecting state Explanation Indicates that LACP data exchanged between two peer devices is correct and that both devices are now synchronized. Typically, this state is transitory and occurs before the link moves to the Distributing state. Cause If the link remains in this state, the peer has not reached Collecting state. Possible causes are a fault with the peer, a loss of packets on the line, or a local software problem that is preventing the transmission to Distributing state. Action Check the peer status, and look for packet loss on the link.
State Link exceeds maximum active limit Explanation You set the bundle maximum-active links to x on the bundle, and there are already x links active in the bundle. As a result, this link is held in standby state (either Detached or Collecting depending on whether the hot-standby option was specified). Cause Assuming that there are actually x active links in the bundle, this condition is normal. Action No action is required.
State Link is in Distributing state Explanation The link is fully active, transmitting and receiving traffic. This reason is not usually displayed because it is the normal stable state. Cause This conditional is normal. Action No action is required.

Related Commands

Command	Description
bundle id	Adds a port to an aggregated interface (or bundle).
show lacp bundle	Displays detailed information about LACP ports and their peers.
show interfaces	Displays statistics for all interfaces configured on the router or on a specific node.

show lacp bundle

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

show lacp bundle [Bundle-Ether bundle-id | Bundle-POS bundle-id]

Syntax Description

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

Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release	Modification
Release 3.2	This command was introduced on the Cisco CRS-1.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Task ID

Task ID	Operations
bundle	read

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 58 describes the significant fields shown in the display.

Table 58 show lacp bundle Field Descriptions

Field	Description
Flags	Describes the possible flags that may apply to a device or port, under the "Flags" field.
State	Describes the possible flags that may apply the port state, under the "State" field.
Port	Port identifier, in the rack/slot/module/port notation.
State	Provides information about the state of the specified port. Possible flags are: •0 - Port is not aggregatable. •1 - Port is out of sync with peer. •2 - Port is in sync with peer. •3 - Port is Collecting. •4 - Port is Collecting and Distributing
Flags	Provides information about the state of the specified device or port. Possible flags are: •A - Device is in Active mode. •P - Device is in Passive mode. •S - Device 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
Port ID	Port identifier, expressed in the format Nxnnnn. N is the port priority, and nnnn is the port number assigned by the sending router.
Key	2-byte number associated with the specified link and aggregator. Each port assigned an operational Key. The ability of one port to aggregate with another is summarized by this key. Ports which have the same key select the same bundled interface. The system ID, port ID and key combine to uniquely define a port within a LACP system.
System-ID	System identifier. The System ID is a LACP property of the system which is transmitted within each LACP packet together with the details of the link.

This line prevents blank table in PDF.

Related Commands

Command	Description
bundle id	Adds a port to an aggregated interface (or bundle).
show bundle Bundle-Ether	Displays information for a specific Ethernet bundle.
show bundle Bundle-POS	Displays information for a specific POS bundle.

show lacp counters

To display Link Aggregation Control Protocol (LACP) statistics, enter the show lacp counters command in EXEC mode.

show lacp counters [Bundle-Ether bundle-id | Bundle-POS bundle-id]

Syntax Description

Bundle-Ether bundle-id	Specifies the Ethernet bundle whose counters you want to display. Replace bundle-id with a bundle identifier. Range is from 1 through 65535.
Bundle-POS bundle-id	Specifies the POS bundle whose counters you want to display. Replace bundle-id with a bundle identifier. Range is from 1 through 65535.

Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release	Modification
Release 3.2	This command was introduced on the Cisco CRS-1.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Task ID

Task ID	Operations
bundle	read

Examples

The following example shows how to display LACP counters on an Ethernet bundle:

RP/0/RP0/CPU0:router# show lacp counters bundle-ether 4

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 59 describes the significant fields shown in the display.

Table 59 show lacp counters Field Descriptions

Field	Description
LACPDUs	Provides the following statistics for Link Aggregation Control Protocol data units (LACPDUs): •Port •Sent •Received •Last Cleared •Excess •Pkt Errors
Marker	Provides the following statistics for marker packets: •Received •Resp. Sent •Last Cleared •Excess •Pkt Errors Note The Marker Protocol is used by 802.3ad bundles to ensure that data no longer is transmitted on a link when a flow is redistributed away from that link.

Related Commands

Command	Description
clear lacp counters	Clears LACP counters for all members of all bundles, all members of a specific bundle, or for a specific port.

show lacp port

To display detailed information about Link Aggregation Control Protocol (LACP) ports, enter the show lacp port command in EXEC mode.

show lacp port [GigabitEthernet interface_instance | TenGigE interface_instance | POS interface_instance]

Syntax Description

GigabitEthernet interface_instance	Specifies the Gigabit Ethernet interface bundle whose LACP port information you want to display.The interface_instance is expressed in the rack/slot/module/port notation.
TenGigE interface_instance	Specifies the TenGigE interface whose LACP port information you want to display. The interface_instance is expressed in the rack/slot/module/port notation.
POS interface_instance	Specifies the Packet-over-SONET/SDH (POS) network whose LACP port information you want to display. The interface_instance is expressed in the rack/slot/module/port notation.

Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release	Modification
Release 3.2	This command was introduced on the Cisco CRS-1.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Task ID

Task ID	Operations
bundle	read

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 60 describes the significant fields shown in the display.

Table 60 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: •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
Flags	Provides information about the state of the specified port. Possible flags are: •0 - Port is not aggregatable. •1 - Port is out of sync with peer. •2 - Port is in sync with peer. •3 - Port is Collecting. •4 - Port is Collecting and Distributing
Port ID	Port identifier, expressed in the following format: Nxnnnn. N is the port priority, and nnnn is the port number assigned by the sending router.
Key	2-byte number associated with the specified link and aggregator. Each port assigned an operational Key. The ability of one port to aggregate with another is summarized by this key. Ports which have the same key select the same bundled interface. The system ID, port ID and key combine to uniquely define a port within a LACP system.
System-ID	System identifier. The System ID is an LACP property of the system which is transmitted within each LACP packet together with the details of the link.

This line prevents blank table in PDF.

Related Commands

Command	Description
bundle id	Adds a port to an aggregated interface (or bundle).
show bundle Bundle-Ether	Displays information about a specific Ethernet bundle.
show bundle Bundle-POS	Displays information about a specific POS bundle.

show lacp system-id

To display the local system ID used by the Link Aggregation Control Protocol (LACP), enter the show lacp system-id command in EXEC mode.

show lacp system-id

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release	Modification
Release 3.2	This command was introduced on the Cisco CRS-1.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

---

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

---

Task ID

Task ID	Operations
bundle	read

Examples

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

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

Priority  MAC Address

--------  -----------------

  0x8000  08-00-45-3a-65-01

Table 61 describes the significant fields shown in the display.

Table 61 show lacp system-id Field Descriptions

Field	Description
Priority	Priority for this system. A lower value is higher priority.
MAC Address	MAC address associated with the LACP system ID.

Related Commands

Command	Description
bundle id	Adds a port to an aggregated interface (or bundle).
show bundle Bundle-Ether	Displays information about a specific Ethernet bundle.
show bundle Bundle-POS	Displays information about a specific POS bundle.
show lacp bundle	Displays detailed information about LACP ports and their peers.
show lacp port	Displays detailed information about LACP ports