Configuration Considerations for Enabling MPLS on a LAG Interface

When MPLS is globally enabled on the device, a port that is configured in a LAG can be enabled as an MPLS interface port to create an MPLS LAG. The user can do this through either of the following approaches:

Include a primary LAG port that has already been MPLS-enabled in a new LAG
MPLS-enable a primary LAG port of a previously configured LAG

The user must consider the following points when configuring MPLS on a LAG:

MPLS configuration on dynamic lag interfaces are supported.
MPLS is enabled on the primary port of the LAG and this enables MPLS on the entire LAG. Secondary ports of the LAG cannot be individually configured for MPLS.

Note

A hashing scheme for enhanced load balancing allows MPLS transit load balancing to include inner headers of different packet types in parallel. This hashing scheme is supported only with the "Layer 2 Optimized" Tcam profile and is enabled by default when the profile tcam layer2-optimised-1 configuration is activated. The "Error: Operation not supported in the current hardware TCAM profile" message is displayed for the following commands because these functionalities are already taken care of by this enhanced hashing scheme:

lag hash speculate-mpls inner-eth
lag hash speculate-mpls inner-ip-raw
lag hash speculate-mpls inner-ip-tag
lag hash speculate-mpls inner-ipv6-raw
lag hash speculate-mpls inner-ipv6-tag

For more information, see "MPLS transit load balancing" under "LAG load sharing" in the Extreme SLX-OS Layer 2 Switching Configuration Guide.