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

ingress-node-replication

date_range 19-Nov-23

Syntax

content_copy zoom_out_map
ingress-node-replication; 

Hierarchy Level

content_copy zoom_out_map
[edit bridge-domains bridge-domain-name vxlan], 
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name vxlan], 
[edit routing-instances routing-instance-name vlans vlan-name vxlan], 
[edit routing-instances routing-instance-name vxlan]
[edit vlans vlan-name vxlan] 

Description

Enable ingress node replication for a specified Virtual Extensible LAN (VXLAN) that is managed by the Open vSwitch Database (OVSDB) management protocol.

With this feature enabled, instead of service nodes, Juniper Networks devices with OVSDB implemented handle incoming broadcast, unknown unicast, or multicast (BUM) traffic. For more information about the scenarios in which you can use ingress node replication and how it works, see Understanding How Layer 2 BUM and Layer 3 Routed Multicast Traffic Are Handled with OVSDB.

Note:

When Juniper Networks devices replicate Layer 2 BUM packets to a large number of remote software VTEPs, the performance of the Juniper Networks devices might be impacted.

Default

If you do not include the ingress-node-replication statement, one or more service nodes handle BUM traffic.

Required Privilege Level

admin—To view this statement in the configuration.

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

Release Information

Statement introduced in Junos OS Release 14.1R2.

footer-navigation