Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

Configuring PIM-to-IGMP Message Translation

You can configure the rendezvous point (RP) routing device to translate PIM join or prune messages into corresponding IGMP report or leave messages. To do so, include the pim-to-igmp-proxy statement at the [edit routing-options multicast] hierarchy level:

[edit routing-options multicast]
pim-to-igmp-proxy {upstream-interface [ interface-names ];}

Enabling the routing device to perform PIM-to-IGMP message translation, also referred to as PIM-to-IGMP proxy, is useful when you want to use IGMP to forward IPv4 multicast traffic between a PIM sparse mode edge domain and a PIM sparse mode core domain in certain network topologies.

Before you begin configuring PIM-to-IGMP message translation:

  • Make sure that the routing device connecting the PIM edge domain and that the PIM core domain is the static or elected RP routing device.
  • Make sure that the PIM sparse mode (PIM-SM) routing protocol is running on the RP routing device.
  • If you plan to configure two upstream interfaces, make sure that reverse-path forwarding (RPF) is running in the PIM-SM core domain. Because the RP router transmits the same IGMP messages and multicast traffic on both upstream interfaces, you need to run RPF to verify that multicast packets are received on the correct incoming interface and to avoid sending duplicate packets.

To configure the RP routing device to translate PIM join or prune messages into corresponding IGMP report or leave messages:

  1. Include the pim-to-igmp-proxy statement, specifying the names of one or two logical interfaces to function as the upstream interfaces on which the routing device transmits IGMP report or leave messages.

    The following example configures PIM-to-IGMP message translation on a single upstream interface, ge-0/1/0.1.

    [edit routing-options multicast]user@host# set pim-to-igmp-proxy upstream-interface ge-0/1/0.1

    The following example configures PIM-to-IGMP message translation on two upstream interfaces, ge-0/1/0.1 and ge-0/1/0.2. You must include the logical interface names within square brackets ( [ ] ) when you configure a set of two upstream interfaces.

    [edit routing-options multicast]user@host# set pim-to-igmp-proxy upstream-interface [ge-0/1/0.1 ge-0/1/0.2]
  2. Use the show multicast pim-to-igmp-proxy command to display the PIM-to-IGMP proxy state (enabled or disabled) and the name or names of the configured upstream interfaces.
    user@host# run show multicast pim-to-igmp-proxy
    Proxy state: enabled
ge-0/1/0.1
ge-0/1/0.2
 

Related Documentation

 

Published: 2013-02-12

Previous Page Next Page