Configuration manual

Link Aggregation Control Protocol | 565
• 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. See Hitless Behavior on page 405.
Configure LACP to be hitless using the command redundancy protocol lacp from CONFIGURATION
mode, as shown in Figure 25-10.
Figure 25-10. Enabling Hitless LACP
LACP Basic Configuration Example
The screenshots in this section are based on the example topology shown in Figure 25-11. Two routers are
named ALPHA and BRAVO, and their hostname prompts reflect those names.
The sections are:
• Configuring a LAG on ALPHA on page 566
• Summary of the configuration on ALPHA on page 570
• Summary of the configuration on BRAVO on page 571
Force10(conf)#redundancy protocol lacp
Force10#show running-config redundancy
!
redundancy protocol lacp
Force10#
Force10#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