Pim-To-Igmp-Proxy - Juniper JUNOS OS 10.3 - SOFTWARE Manual

Related
Documentation

pim-to-igmp-proxy

Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
Copyright © 2010, Juniper Networks, Inc.
Configuring BGP Groups and Peers
Configuring BGP Groups and Peers
4-Byte Autonomous System Numbers Overview
Juniper Networks Implementation of 4-Byte Autonomous System Numbers
Establishing a Peer Relationship Between a 4-Byte Capable Router and a 2-Byte
Capable Router Using a 2-Byte AS Number
Establishing a Peer Relationship Between a 4-Byte Capable Router and a 2-Byte
Capable Router Using a 4-Byte AS Number
pim-to-igmp-proxy {
upstream-interface [ interface-names ];
}
[edit logical-systems logical-system-name routing-instances routing-instance-name
routing-options multicast],
[edit logical-systems logical-system-name routing-options multicast],
[edit routing-instances routing-instance-name routing-options multicast],
[edit routing-options multicast]
Statement introduced in Junos OS Release 9.6.
Statement introduced in Junos OS Release 9.6 for EX Series switches.
Configure the rendezvous point (RP) routing device that resides between a customer
edge–facing Protocol Independent Multicast (PIM) domain and a core-facing PIM domain
to translate PIM join or prune messages into corresponding Internet Group Management
Protocol (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. Including the
IGMP to forward IPv4 multicast traffic across the PIM sparse mode domains.
The remaining statement is explained separately.
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Configuring PIM-to-IGMP Message Translation
Chapter 73: Configuration Statements for Layer 3 Protocols
statement enables you to use
pim-to-igmp-proxy
1909