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
header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Junos CLI Reference
Table of Contents Expand all
list Table of Contents

distributed (IGMP)

date_range 19-Nov-23

Syntax

content_copy zoom_out_map
distributed;

Hierarchy Level

content_copy zoom_out_map
[edit protocols igmp interface interface-name],
[edit dynamic-profiles protocols igmp interface $junos-interface-name]

Description

Enable distributed IGMP by moving IGMP processing from the Routing Engine to the Packet Forwarding Engine. Distributed IGMP reduces the join and leave latency of IGMP memberships.

Distributed IGMP is only available when chassis network-services enhanced-ip is configured.

Note:

When you enable distributed IGMP, the following interface options are not supported on the Packet Forwarding Engine: oif-map, group-limit, ssm-map, and static. However, the ssm-map-policy option is supported on distributed IGMP interfaces. The traceoptions and accounting statements can only be enabled for IGMP operations still performed on the Routing Engine; they are not supported on the Packet Forwarding Engine. The clear igmp membership command is not supported when distributed IGMP is enabled.

When the distributed command is enabled in conjunction with mldp-inband-signalling, (so PIM act as a multipoint LDP inband edge router), it supports interconnecting separate PIM domains via a MPLS-based core.

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.1X50.

Support added in Junos OS Release 18.2R1 for using distributed IGMP in conjunction with Multipoint LDP (mLDP) in-band signalling.

footer-navigation