Shared Lag State Tracking; Configure Shared Lag State Tracking - Dell Force10 MXL Blade Configuration Manual

Configuration guide for the mxl 10/40gbe switch io module
Hide thumbs Also See for Force10 MXL Blade:
Table of Contents

Advertisement

Shared LAG State Tracking

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
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 16-5. 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. This is
shared LAG state tracking. To achieve this functionality, you must group LAG 1 and LAG 2 into a single
entity, called a failover group.

Configure Shared LAG State Tracking

To configure shared LAG state tracking, you must first configure a failover group. Follow these steps:
Step
Task
1
Enter port-channel failover group mode.
2
Create a failover group and specify the
two port-channels that will be members
of the group.
292
|
Link Aggregation Control Protocol (LACP)
16-5, line-rate traffic from R1 destined for R4 follows the lowest-cost route via R2. Traffic is
Po 1 failure
R1
R4
Po 2 over-subscribed
R2
Command
port-channel failover-group
group number port-channel
number port-channel number
R3
fnC0049mp
Command Mode
CONFIGURATION
CONFIG-PO-FAILOVER-GRP

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents