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

pim-to-igmp-proxy

date_range 20-Nov-23

Syntax

content_copy zoom_out_map
pim-to-igmp-proxy {
    upstream-interface [ interface-names ];
}

Hierarchy Level

content_copy zoom_out_map
[edit logical-systems logical-system-name routing-options multicast],
[edit routing-options multicast]

Description

Use the pim-to-igmp-proxy statement to have Internet Group Management Protocol (IGMP) forward IPv4 multicast traffic across Protocol Independent Multicast (PIM) sparse mode domains.

Configure the rendezvous point (RP) routing device that resides between a customer edge-facing PIM domain and a core-facing PIM domain to translate PIM join or prune messages into corresponding IGMP report or leave messages. The routing device then transmits the report or leave messages by proxying them to one or two upstream interfaces that you configure on the RP routing device.

On the IGMP upstream interface(s) used to send proxied PIM traffic, set the IP address so it is the lowest IP on the network to ensure that the proxying router is always the IGMP querier.

Note too that you should not enable PIM on the IGMP upstream interface(s).

The pim-to-igmp-proxy statement is not supported for routing instances configured with multicast VPNs.

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

footer-navigation