evpn-vxlan

Configure Group Based Policy (GBP) policy enforcement at the ingress node.

Associate the specified <gbp-filter> with the routing instance.

Use this option to enable EVPN Type 5 tag propagation, which is the ability to pass a source GBP tag within the extended BGP communities string of an EVPN Type 5 advertisement. By propagating the source GBP tag across the network, remote endpoints gain the information necessary to enforce GBP policies at their ingress.

The specified <gbp-filter> must be an IP-based (IP address or IP prefix) GBP filter.

This option has no effect if the specified <gbp-filter> is not an IP-based filter.

Allow MAC-based GBP filters and IP-based GBP filters to apply to both routed and switched traffic.

If disabled, then MAC-based GBP filters apply only to switched traffic, and IP-based GBP filters apply only to routed traffic.

Starting in Junos OS Release 25.4R1, this option is enabled by default.

This setting has no effect on other GBP filters, such as port and VLAN GBP filters.

Allow only GBP source and destination tags as matches in GBP policy.

Configuring the IPv4 and IPv6 L4 filters can reduce the supported GBP scale. These matches are supported by default. However, on the EX4650 series, QFX5120-32C, and QFX5120-48Y switches, you can use this option to allow only GBP source and destination tags as matches in GBP policy.

Insert the specified GBP source tag in all host originated packets.

Range for gbp-src-tag: 1 through 65535.

Enable fast reroute egress link protection (ELP) on provider edge (PE) devices for access links to multihomed customer edge (CE) devices in an EVPN-VXLAN fabric. With this statement, you also specify the IPv4 or IPv6 device reroute address, which is a secondary loopback address you configure as the fast reroute ELP tunnel source VTEP address for an Ethernet segment.

This feature helps to minimize load-balanced traffic loss when the link from a PE device to a multihomed CE device goes down.

Create shared VXLAN tunnel endpoint (VTEP) tunnels to EVPN provider edge (PE) devices to save VTEP resources.

Don't install EVPN remote destination routes learned from remote Data Center Interconnect (DCI) peers across an interconnecting WAN.

Use this option with other options and routing policies on distribution layer devices to help optimize managing remote host routes in very large campus EVPN-VXLAN networks that use DCI with EVPN Type 2 and Type 5 route stitching. See EVPN Host Route Management for Large-Scale Stretched Campus Networks for details.

With this option, a distribution layer device skips installing remote host routes (IPv4 /32 routes and IPv6 /128 routes) learned from devices at other office or locations in the campus network. Instead, to optimize host route management, the distribution layer devices install and use only Type 5 subnet routes advertised from the core layer.