flow-label-transmit-static

Syntax

Hierarchy Level

Description

Configure the router to push the flow label on pseudowire packets it sends to a remote provider edge (PE) router. The ingress PE router inserts the flow label in the pseudowire packet regardless of the information exchanged in the signaling plane. If the egress PE router can't handle a pseudowire packet that contains the flow label, it drops the packet.

Flow-aware transport of pseudowires (FAT) flow labels enable load balancing of MPLS packets across equal-cost multipath (ECMP) paths or link aggregation groups (LAGs) without the need for deep packet inspection of the payload. You can use this statement to enable devices to push FAT flow labels for:

• Forwarding equivalence class (FEC) 128 pseudowires in:

  • Virtual private LAN service (VPLS) networks.

  • Virtual private wire service (VPWS) networks.

  In these cases, configure this statement in the [edit protocols l2circuit neighbor neighbor-id interface interface-name] hierarchy.

• Pseudowires in Ethernet VPN (EVPN)-MPLS networks with VPWS (EVPN-VPWS):

  • Globally in an EVPN-VPWS routing instance.

    In this case, configure this statement in the [edit routing-instances instance-name protocols evpn] hierarchy.

  • For specific interfaces in an EVPN-VPWS routing instance.

    In this case, configure this statement in the [edit routing-instances instance-name protocols evpn interface interface-name] hierarchy.

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 14.1.

Support in a EVPN-VPWS routing instance added in Junos OS Release 21.1R1.