close

keyboard_arrow_left

Table of Contents Expand all

list Table of Contents

English

ingress-node-replication (EVPN)

date_range 19-Nov-23

arrow_backward

arrow_forward

Syntax

content_copy zoom_out_map
ingress-node-replication;

Hierarchy Level

[edit routing-instances routing-instance-name vlans vlan-name vxlan],
[edit vlans vlan-name vxlan]

Description

EVPN all-active mode with VXLAN encapsulation is based on the local bias for traffic coming from the access layer (redundant Layer 2 gateway function through a pair of top-of-rack switches). Because the traffic has no MPLS label, the split-horizon filtering rule for multihomed Ethernet segments is modified to be based on the IP address of the EVPN provider edge (PE) device instead of the MPLS ES-label. This is called local bias for EVPN-VXLAN.

Each EVPN PE device tracks the IP address of its peer multihomed EVPN PE devices that share the same Ethernet segment. This is the source VTEP IP address (outer SIP) for each VXLAN packet received from other EVPN PE devices. The PE device enforces the local bias filtering rule on both ingress and egress PE devices for the multi-destination traffic. For egress traffic, there is no forwarding of any multi-destination packets to the same multihomed Ethernet segment that an egress PE device shares with its ingress PE, regardless of the egress PE device’s DF election status for that Ethernet segment. Ingress traffic is responsible for forwarding multi-destination packets coming from any directly attached access interfaces to the rest of the multi-homed Ethernet segments associated with it, regardless of the ingress PE device’s designated forwarder election status on the connected physical device segment.

Note:

With this statement configured, the device adds all active VTEP interfaces to every bridge domain (VLAN). However, the default routing behavior without this statement results in an optimal flood list with VTEPs and VLANs associated only based on advertised EVPN Type 3 routes. As a result, in general you don't need to configure this statement on EVPN-VXLAN devices.

If you add or remove this option in an existing VLAN configuration statement and commit the change, the device removes the corresponding VLAN from the forwarding plane and adds it back into the forwarding plane. This causes traffic disruption. As a result, you should plan to make either of those types of changes during a maintenance window.

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.1X53-D30 .

arrow_backward PREVIOUS ingress-node-replication

NEXT arrow_forward ingress-only

Junos CLI Reference

ON THIS PAGE

ingress-node-replication (EVPN)

Syntax

Hierarchy Level

Description

Required Privilege Level

Release Information

Stay in touch

Helped me install or use the product
Accelerated my deployment

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

Junos CLI Reference

ON THIS PAGE

ingress-node-replication (EVPN)

Syntax

Hierarchy Level

Description

Required Privilege Level

Release Information

Related Documentation

Stay in touch