[MX] Setting up an MX-Series node for use as an RP or source DR in a PIM Sparse-Mode network

Summary:

Sparse-Mode Protocol Independent Multicast (PIM) requires a Rendezvous Point (RP) to function. An MX Series node can be set up as an RP or a Designated Router (DR) by setting one of its interfaces to tunnel mode.

This article explains how is done.

Symptoms:

In the PIM Sparse-Mode implementation, the source Designated Router (DR) takes the initial multicast packets and encapsulates them into PIM register messages. It then unicasts them to the PIM Sparse-Mode RP router, where the PIM register messages are de-encapsulated.

On Juniper Networks routers, data packets are encapsulated and de-encapsulated into tunnels by means of hardware and not the software running on the router's processor. The hardware that is used to create tunnel interfaces is a Tunnel Services Physical Interface Card (PIC). All RP routers and IP version 4 (IPv4) PIM Sparse-Mode DRs that are connected to a multicast source require a Tunnel Services PIC.

Solution:

To enable tunnel interfaces on an MX Series node, include the tunnel-services statement at the [edit chassis fpc slot-number pic number] hierarchy level. To configure the bandwidth for a tunnel interface, include the bandwidth statement at the [edit chassis fpc slot-number pic number] hierarchy level.

The following example shows a tunnel interface with 1 Gbps of bandwidth configured on PFE 1 of the Dense Port Concentrator (DPC) installed in slot 4 of an MX Series node:

chassis }
    fpc 4;
    pic 1 {
        tunnel services {
            bandwidth 1g;
        }
    }
}

Modification History:

2020-05-07: Updated links in the article and check its content for accuracy; article relevant and valid

Knowledge Base