Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

ESI-LAG

This section briefly describes the Ethernet Segment Identifier–Link Aggregation Group (ESI-LAG) feature and its configuration on the QFX5230, QFX5240, and QFX5241 Switches.

Overview

Note: The QFX5220 does not support ESI-LAG.

The provider edge (PE) devices in an EVPN fabric can handle traffic to and from the attached multihomed end devices by grouping the multihoming links into an EVPN Ethernet segment with an identifier. This identifier is known as Ethernet segment identifier (ESI). The multihoming links participating in the Ethernet segment are configured into a link aggregation group (LAG). Thus, the set of multihomed links is called an ESI LAG or EZ-LAG. ESI-LAG provides a simplified configuration statement hierarchy and a built-in commit script that you can use to set up EVPN dual-homing. You can then easily migrate a multichassis link aggregation group (MC-LAG) topology to a standards-based EVPN-VXLAN multihoming model. For more information about ESI-LAG, see Benefits of using Easy EVPN LAG Configuration.

Note: ESI-LAG is an optional feature meant for only multihoming. The feature is not applicable to single-homing users.

Configure ESI-LAG on QFX5230, QFX5240, and QFX5241 Switches

To configure ESI-LAG on your QFX Series Switch:

  • Run the following sample CLI commands at the [edit services evpn] hierarchy level by providing the parameters to set up the prescribed EVPN fabric.

    The following sample configuration requires minimal parameters to configure an EVPN fabric with a single server dual-homed to two PE devices. When you commit the configuration, the built-in commit script generates the full underlying EVPN and ESI-LAG configuration. For more information about ESI-LAG, see Easy EVPN LAG (EZ-LAG) Configuration.

    Note: This configuration is for a single PE device. For a dual-homed server, you must apply same configuration on the second PE device, using its local interface connected to the same server.

    A built-in commit script processes the simplified configuration elements at commit time (before the standard Junos OS Evolved configuration validity checks) and generates a corresponding EVPN fabric configuration.

    Note: The commit script for this feature, services_evpn_commit_script.py, is enabled by default on supported platforms.

Verify ESI-LAG Configuration

To verify your ESI-LAG configuration, run the following commands: