Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
external-header-nav
Documentation
Menu
License Guide
Quick Starts
Validated Designs
Explore Pathfinder Apps
CLI Explorer
Feature Explorer
Hardware Compatibility Tool
Port Checker
Browse All
Collapse

Pathfinder Apps

All

By Software

By Hardware

Learn More
Pathfinder HomeCLI ExplorerCompliance AdvisorFeature ExplorerHardware Compatibility ToolJunos XML API ExplorerJunos YANG Data Model ExplorerPort CheckerPower CalculatorSNMP MIB ExplorerSystem Log Explorer
CLI ExplorerFeature ExplorerJunos XML API ExplorerJunos YANG Data Model ExplorerSNMP MIB ExplorerSystem Log Explorer
Compliance AdvisorFeature ExplorerHardware Compatibility ToolPort CheckerPower Calculator
Home Documentation Junos OS Junos CLI Reference CLI Reference F

Junos CLI Reference

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
ON THIS PAGE
keyboard_arrow_right

flow-label-transmit-static

date_range 19-Nov-23
arrow_backward
arrow_forward

Syntax

content_copy zoom_out_map
flow-label-transmit-static;

Hierarchy Level

content_copy zoom_out_map
[edit protocols l2circuit neighbor neighbor-id interface interface-name],
[edit routing-instances instance-name protocols evpn],
[edit routing-instances instance-name protocols evpn interface interface-name]

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.

Related Documentation

arrow_backward PREVIOUS flow-label-transmit
NEXT arrow_forward flow-level-bandwidth (DDoS Flow Detection)
external-footer-nav