Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Configuring PIM-to-IGMP and PIM-to-MLD Message Translation

 

Understanding PIM-to-IGMP and PIM-to-MLD Message Translation

Routing devices can translate Protocol Independent Multicast (PIM) join and prune messages into corresponding Internet Group Management Protocol (IGMP) or Multicast Listener Discovery (MLD) report or leave messages. You can use this feature to forward multicast traffic across PIM domains in certain network topologies.

In some network configurations, customers are unable to run PIM between the customer edge-facing PIM domain and the core-facing PIM domain, even though PIM is running in sparse mode within each of these domains. Because PIM is not running between the domains, customers with this configuration cannot use PIM to forward multicast traffic across the domains. Instead, they might want to use IGMP to forward IPv4 multicast traffic, or MLD to forward IPv6 multicast traffic across the domains.

To enable the use of IGMP or MLD to forward multicast traffic across the PIM domains in such topologies, you can configure the rendezvous point (RP) router that resides between the edge domain and core domain to translate PIM join or prune messages received from PIM neighbors on downstream interfaces into corresponding IGMP or MLD report or leave messages. The router then transmits the report or leave messages by proxying them to one or two upstream interfaces that you configure on the RP router. As a result, this feature is sometimes referred to as PIM-to-IGMP proxy or PIM-to-MLD proxy.

To configure the RP router to translate PIM join or prune messages into IGMP report or leave messages, include the pim-to-igmp-proxy statement at the [edit routing-options multicast] hierarchy level. Similarly, to configure the RP router to translate PIM join or prune messages into MLD report or leave messages, include the pim-to-mld-proxy statement at the [edit routing-options multicast] hierarchy level. As part of the configuration, you must specify the full name of at least one, but not more than two, upstream interfaces on which to enable the PIM-to-IGMP proxy or PIM-to-MLD proxy feature.

The following guidelines apply when you configure PIM-to-IGMP or PIM-to-MLD message translation:

  • Make sure that the router connecting the PIM edge domain and the PIM core domain is the static or elected RP router.

  • Make sure that the RP router is using the PIM sparse mode (PIM-SM) multicast routing protocol.

  • When you configure an upstream interface, use the full logical interface specification (for example, ge-0/0/1.0) and not just the physical interface specification (ge-0/0/1).

  • When you configure two upstream interfaces, the RP router transmits the same IGMP or MLD report messages and multicast traffic on both upstream interfaces. As a result, make sure that reverse-path forwarding (RPF) is running in the PIM-SM core domain to verify that multicast packets are received on the correct incoming interface and to avoid sending duplicate packets.

  • The router transmits IGMP or MLD report messages on one or both upstream interfaces only for the first PIM join message that it receives among all of the downstream interfaces. Similarly, the router transmits IGMP or MLD leave messages on one or both upstream interfaces only if it receives a PIM prune message for the last downstream interface.

  • Upstream interfaces support both local sources and remote sources.

  • Multicast traffic received from an upstream interface is accepted as if it came from a host.

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:

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.

    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.

  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

Configuring PIM-to-MLD Message Translation

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

Enabling the routing device to perform PIM-to-MLD message translation, also referred to as PIM-to-MLD proxy, is useful when you want to use MLD to forward IPv6 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-MLD 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 routing device transmits the same MLD 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 MLD report or leave messages:

  1. Include the pim-to-mld-proxy statement, specifying the names of one or two logical interfaces to function as the upstream interfaces on which the router transmits MLD report or leave messages.

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

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

  2. Use the show multicast pim-to-mld-proxy command to display the PIM-to-MLD proxy state (enabled or disabled) and the name or names of the configured upstream interfaces.
    user@host# run show multicast pim-to-mld-proxy

Related Documentation