Reference Guide

536 | Link Aggregation Control Protocol
www.dell.com | support.dell.com
View the status of a failover group member using the command show interface port-channel, as shown in
the following example.
R2#show interface Port-channel 2
Port-channel 2 is up, line protocol is down (Failover-group 1 is down)
Hardware address is 00:01:e8:05:e8:4c, Current address is 00:01:e8:05:e8:4c
Interface index is 1107755010
Minimum number of links to bring Port-channel up is 1
Port-channel is part of failover-group 1
Internet address is not set
MTU 1554 bytes, IP MTU 1500 bytes
LineSpeed 1000 Mbit
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
Important Points 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.
• Shared LAG State Tracking can be configured 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.
Configure LACP as Hitless
Configure LACP as Hitless is supported only on platforms: c e
LACP on Dell Force10 systems can be configured to be hitless. When configured as hitless, there is no
noticeable impact on dynamic LAG state upon an RPM failover. Critical LACP state information is
synchronized between the two RPMs. Refer to Hitless Behavior.
Configure LACP to be hitless using the command redundancy protocol lacp from CONFIGURATION
mode, as shown in the following example.
FTOS(conf)#redundancy protocol lacp
FTOS#show running-config redundancy
redundancy protocol lacp
FTOS#show running-config interface gigabitethernet 0/12
!
interface GigabitEthernet 0/12
no ip address
!
port-channel-protocol LACP
port-channel 200 mode active
no shutdown
Note: The set of console messages shown in Message 2 appear only if Shared LAG State Tracking is
configured on that router (the feature can be configured on one or both sides of a link). For example, in
Figure 27-2, if Shared LAG State Tracking is configured on R2 only, then no messages appear on R4
regarding the state of LAGs in a failover group.