Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Enabling Distributed IGMP

Configuring distributed IGMP improves performance by reducing join and leave latency. This works by moving IGMP processing from the Routing Engine to the Packet Forwarding Engine. In contrast to centralized IGMP processing on the Routing Engine, the Packet Forwarding Engine disperses traffic across multiple Modular Port Concentrators (MPCs).

You can enable distributed IGMP on static interfaces or dynamic interfaces. As a prerequisite, you must enable enhanced IP network services on a single-chassis MX Series router.

Enabling Distributed IGMP on Static Interfaces

You can enable distributed IGMP on a static interface by configuring enhanced IP network services and including the distributed statement at the [edit protocols igmp interface interface-name] hierarchy level. Enhanced IP network services must be enabled (at the [chassis network-services enhanced-ip] hierarchy).

To enable distributed IGMP on a static interface:

  1. Configure the IGMP static interface.
  2. Enable distributed IGMP on a static interface.
  3. Commit the configuration.

Enabling Distributed IGMP on Dynamic Interfaces

You can enable distributed IGMP on a dynamic interface by configuring enhanced IP network services and including the distributed statement at the [edit dynamic profiles profile-name protocols] hierarchy level. Enhanced IP network services must be enabled (at the [chassis network-services enhanced-ip] hierarchy).

  1. Configure the IGMP interface.
  2. Enable distributed IGMP on a dynamic interface.
  3. Commit the configuration.

Configuring Multicast Traffic for Distributed IGMP

Configuring static source and group (S,G) addresses for distributed IGMP reduces join delays and sends multicast traffic to the last-hop router. You can configure static multicast groups (S,G) for distributed IGMP at the [edit protocols pim] hierarchy level. You can issue the distributed keyword at one of the following three hierarchy levels:

  • [edit protocols pim static]

    Issuing the distributed keyword at this hierarchy level enables static joins for specific multicast (S,G) groups and preprovisions all of them so that all distributed IGMP Packet Forwarding Engines receive traffic.

  • [edit protocols pim static group multicast-group-address]

    Issuing the distributed keyword at this hierarchy level enables static joins for multicast (S,G) groups so that all distributed IGMP Packet Forwarding Engines receive traffic and preprovisions a specific multicast group address (G).

  • [edit protocols pim static group multicast-group-address source source-address]

    Issuing the distributed keyword at this hierarchy level enables static joins for multicast (S,G) groups so that all Packet Forwarding Engines receive traffic, but preprovisions a specific multicast (S,G) group.

To configure static multicast (S,G) addresses for distributed IGMP:

  1. Configure static PIM.
  2. (Optional) Enable static joins for specific (S,G) addresses and preprovision all of them so that all distributed IGMP Packet Forwarding Engines receive traffic. In the example, multicast traffic for all of the groups (225.0.0.1, 10.10.10.1), (225.0.0.1, 10.10.10.2), and (225.0.0.2, *) is preprovisioned.
  3. (Optional) Enable static joins for specific multicast (S,G) groups so that all distributed IGMP Packet Forwarding Engines receive traffic and preprovision a specific multicast group address (G). In the example, multicast traffic for groups (225.0.0.1, 10.10.10.1) and (225.0.0.1, 10.10.10.2) is preprovisioned, but group (225.0.0.2, *) is not preprovisioned.
  4. (Optional) Enable a static join for specific multicast (S,G) groups so that all Packet Forwarding Engines receive traffic, but preprovision only one specific multicast address group. In the example, multicast traffic for group (225.0.0.1, 10.10.10.1) is preprovisioned, but all other groups are not preprovisioned.
  5. Commit the configuration.

See Also