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

snoop-pseudowires

date_range 20-Nov-23

Syntax

content_copy zoom_out_map
snoop-pseudowires;

Hierarchy Level

content_copy zoom_out_map
[edit routing-instances routing-instance-name igmp-snooping-options]
[edit logical-systems logical-system -name routing-instances routing-instance-nameigmp-snooping-options]

Description

The default IGMP snooping implementation for a VPLS instance adds each pseudowire interface to its oif list. It includes traffic from the ingress PE that is sent to egress PE even if there is no interest. The snoop-pseudowires option prevents multicast traffic from traversing the pseudowire (to egress PEs) unless there are IGMP receivers for the traffic. In other words, multicast traffic is forwarded only to VPLS core interfaces that are router interfaces, or that are IGMP receivers. In addition to the benefit of sending traffic to only interested PEs, snoop-pseudowires also optimizes a common path between PE-P routers wherever possible (so if two PEs connect via the same P router, only one copy of packet is sent; the packet would be replicated only on P routers for which the path is divergent).

Note:

Note that this option can only be enabled when instance-type is vpls. The snoop-pseudowires option cannot be enabled if use-p2mp-lsp is enabled for igmp-snooping-options.

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 15.1.

footer-navigation