Shared Lag State Tracking; Configure Shared Lag State Tracking - Dell Force10 S4810P Configuration Manual

High-density, 1ru 48-port 10gbe switch

Hide thumbs Also See for Force10 S4810P:

Table of Contents

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 the following illustration, 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.

To avoid packet loss, traffic must be re-directed through the next lowest-cost link (R3 to R4). FT OS 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.

To configure

Note: If a LAG interface is part of a redundant pair, it cannot be used as a member of a failover group

created for Shared LAG State Tracking.

Enter port-channel failover group mode.

Create a failover group and specify the

two port-channels that will be members

of the group.

In the following example, LAGs 1 and 2 have been placed into to the same failover group.

Link Aggregation Control Protocol (LACP)

Po 1 failure

Shared LAG State Tracking

Po 2 over-subscribed

, you configure a failover group :

port-channel

failover-group

group number port-channel

number port-channel

Command Mode

CONFIGURATION

CONFIG-PO-FAILOVER-GRP