FTOS Configuration Guide for the C-Series - Force10 Networks

To debug LACP, use the following command:
Command Syntax Command Mode Purpose
[no] debug lacp [config | events |
pdu [in | out | [interface [in | out]]]]
Shared LAG State Tracking
EXEC Debug LACP, including configuration and events.
Shared LAG State Tracking provides the flexibility to bring down a port channel (LAG) based on the
operational state of another LAG. At any time, only two LAGs can be a part of a group such that the fate
(status) of one LAG depends on the other LAG.
In Figure 122, line-rate traffic from R1 destined for R4 follows the lowest-cost route via R2, as shown.
Traffic is equally distributed between LAGs 1 and 2. If LAG 1 fails, all traffic from R1 to R4 flows across
LAG 2 only. This condition over-subscribes the link, and packets are dropped.
Figure 122 LAGs using ECMP without Shared LAG State Tracking
To avoid packet loss, traffic must be re-directed through the next lowest-cost link (R3 to R4). FTOS has the
ability to bring LAG 2 down in the event that LAG 1 fails, so that traffic can be re-directed, as described.
This is what is meant by Shared LAG State Tracking. To achieve this functionality, you must group LAG 1
and LAG 2 into a single entity, called a failover group.
Configuring Shared LAG State Tracking
To configure Shared LAG State Tracking, you configure a failover group:
Step Task Command Command Mode
1
R1
Enter port-channel failover group
mode.
Po 1 failure
port-channel failover-group CONFIGURATION
214 Link Aggregation Control Protocol (LACP)
Po 1
Po 2
R4
Po 2 over-subscribed
R2 R3
fnC0049mp