Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Junos CLI Reference
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

flow-label-static

date_range 19-Nov-23

Syntax

content_copy zoom_out_map
   flow-label-static;

Hierarchy Level

content_copy zoom_out_map
[edit routing-instances name protocols evpn]
  

Description

For EVPN-MPLS E-LAN services, configure the router to signal the ability to push the flow-aware transport (FAT) flow label on pseudowire packets received from a provider edge (PE) router or to pop the FAT flow label on pseudowire packets transmitted to a 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 cannot handle the pseudowire packet with the flow label, it drops the packet. A change in FAT flow label configuration is a catastrophic event, causing traffic loss. RFC 6391 describes FAT flow labels and how they are used.

With FAT flow labels, you can load balance known unicast 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 pop or push FAT flow labels for these EVPN service types:

  • vlan-based

  • vlan-bundle

  • vlan-aware

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 Evolved Release 22.2R1.

footer-navigation