Important Points About Shared Lag State Tracking; Configure Lacp As Hitless - Dell Force10 Z9000 Configuration Manual

Figure 22-9. Viewing Status of a Failover Group Member
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:
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 in
configured on that router (the feature can be configured on one or both sides of a link). For example, in
Figure 22-8, 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.

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
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.
Configure LACP to be hitless using the command
mode, as shown in
| Link Aggregation Control Protocol (LACP)
476
Gi 1/17(U)
is supported only on platforms:
Figure 22-10.
Message 1 appear only if Shared LAG State Tracking is
c e
redundancy protocol lacp
from CONFIGURATION