Administrator Guide

Members in this channel: Gi 1/17(U)
ARP type: ARPA, ARP Timeout 04:00:00
Last clearing of "show interface" counters 00:01:28
Queueing strategy: fifo
NOTE: The set of console messages shown above appear only if you configure shared LAG state tracking on that router
(you can configure the feature on one or both sides of a link). For example, as previously shown, if you configured
shared LAG state tracking on R2 only, no messages appear on R4 regarding the state of LAGs in a failover group.
Important Points about Shared LAG State Tracking
The following is more information about shared LAG state tracking.
• This feature is available for static and dynamic LAGs.
• Only a LAG can be a member of a failover group.
• You can configure shared LAG state tracking on one side of a link or on both sides.
• If a LAG that is part of a failover group is deleted, the failover group is deleted.
• If a LAG moves to the Down state due to this feature, its members may still be in the Up state.
LACP Basic Configuration Example
The screenshots in this section are based on the following example topology. Two routers are named ALPHA and BRAVO, and their
hostname prompts reflect those names.
Figure 56. LACP Basic Configuration Example
Configure a LAG on ALPHA
The following example creates a LAG on ALPHA.
Example of Configuring a LAG
Alpha(conf)#interface port-channel 10
Alpha(conf-if-po-10)#no ip address
Alpha(conf-if-po-10)#switchport
Alpha(conf-if-po-10)#no shutdown
Alpha(conf-if-po-10)#show config
!
interface Port-channel 10
no ip address
switchport
no shutdown
!
Alpha(conf-if-po-10)#
The following example inspects a LAG port configuration on ALPHA.
400
Link Aggregation Control Protocol (LACP)