Configuring Control Word for EVPN-MPLS

date_range 20-Dec-24

arrow_backward

arrow_forward

Transit devices in an EVPN-MPLS network are not aware of the type of payload it carries. While parsing an MPLS encapsulated packet for hashing, a transit device can incorrectly calculate an Ethernet payload as an IPv4 or IPv6 payload if the first nibble of the destination address MAC is 0x4 or 0x6, respectively, causing out-of-order packet delivery. To identify the payload as an Ethernet payload, we can insert a control word with a value of 0 in the first four bits between the label stack and the L2 header of the packet. This ensures that the packet is not identified as an IPv4 or IPv6 packet.

Note:

You do not need to enable control word on the devices in your transit network when the transit devices consist of Juniper Networks EX 9200 switches, MX series routers, or PTX Series routers. These Juniper devices correctly identify the Ethernet payload as an IPv4/IPv6 payloads, even when the Ethernet destination MAC address starts with 0x4 or 0x6 nibble. The Juniper devices perform hashing based on the IP header fields inside the Ethernet frame and will not send out-of-order packets. In this case, we recommend not using control word as there are no benefits..

To enable control word, set control-word for the evpn protocol for a specified routing instance. The following output shows a sample multihomed routing instance with control word configured

content_copy zoom_out_map
user@router1# show routing-instances
routing-instances EVPN-green
vlan-id 200;
interface ae0.1;
route-distinguisher 10.255.255.1:200;
vrf-target target:100:200;
protocols {
    evpn {
        control-word; 
        }        
}

To view routes where control word is supported, use the show route table mpls.0 protocol evpn operational command. Egress routes display an offset of 252.

content_copy zoom_out_map
show route table mpls.0 protocol evpn
303744             *[EVPN/7] 00:00:13, remote-pe 10.255.255.2, routing-instance blue, route-type Egress-MAC
                   > to 5.0.0.1 via ge-0/0/2.0, Push 299984 Offset: 252
303760             *[EVPN/7] 00:00:13, remote-pe 10.255.255.2, routing-instance blue, route-type Egress-MAC
                   > to 5.0.0.1 via ge-0/0/2.0, Push 299888 Offset: 252
303776             *[EVPN/7] 00:00:13, remote-pe 10.255.255.2, routing-instance blue, route-type Egress-MAC
                   > to 5.0.0.1 via ge-0/0/2.0, Push 300032 Offset: 252
303792             *[EVPN/7] 00:00:13, remote-pe 10.255.255.2, routing-instance blue, route-type Egress-IM, vlan-id 4
                   > to 5.0.0.1 via ge-0/0/2.0, Push 302000 Offset: 252
303808             *[EVPN/7] 00:00:13, remote-pe 10.255.255.2, routing-instance blue, route-type Egress-IM, vlan-id 5
                   > to 5.0.0.1 via ge-0/0/2.0, Push 302016 Offset: 252
303824             *[EVPN/7] 00:00:13, remote-pe 10.255.255.2, routing-instance blue, route-type Egress-IM, vlan-id 6
                   > to 5.0.0.1 via ge-0/0/2.0, Push 302032 Offset: 252

arrow_backward PREVIOUS Configuring Entropy Labels

NEXT arrow_forward Understanding P2MPs LSP for the EVPN Inclusive Provider Tunnel

EVPN User Guide

Configuring Control Word for EVPN-MPLS

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry