Configuring Local PIM RPs

Local RP configuration makes the routing device a statically defined RP. To configure the routing device’s RP properties, include the local statement:

You can include this statement at the following hierarchy levels:

• [edit protocols pim rp]
• [edit routing-instances routing-instance-name protocols pim rp]

For an overview of logical systems and a detailed example of logical system configuration, see the Junos Logical Systems Feature Guide.

Configuring the IP Protocol Family

PIM supports both IP version 4 (IPv4) and IP version 6 (IPv6) addressing.

IPv6 PIM hello messages are sent to every interface on which you configure family inet6, whether at the PIM level of the hierarchy or not. As a result, if you configure an interface with both family inet at the [edit interface interface-name] hierarchy level and family inet6 at the [edit protocols pim interface interface-name] hierarchy level, PIM sends both IPv4 and IPv6 hellos to that interface.

By default, PIM operates in sparse mode on an interface. If you explicitly configure sparse mode, PIM uses this setting for all IPv6 multicast groups. However, if you configure sparse-dense mode, PIM does not accept IPv6 multicast groups as dense groups and operates in sparse mode over them.

For correct operation of PIM sparse mode, the RP address must be known to a routing device. The Junos IPv6 PIM implementation supports only static RP configuration. Automatic RP announcement and bootstrap routers are not available with IPv6. You configure the static IPv6 RP address in the same way as IPv4 addresses, by including the address statement. However, on a routing device that is itself the RP, include the address statement at the [edit protocols pim rp local family inet6] or [edit routing-instances routing-instance-name protocols pim rp local family inet6] hierarchy level.

For an overview of logical systems and a detailed example of logical system configuration, see the Junos Logical Systems Feature Guide.

The Multicast Listener Discovery (MLD) protocol is automatically enabled on any broadcast interfaces on which you configure PIM and family inet6. For an overview of MLD, see MLD Overview.

To specify whether IPv4 or IPv6 local RP properties apply to the configuration values, include the family statement:

You can include this statement at the following hierarchy levels:

• [edit protocols pim rp local]
• [edit routing-instances routing-instance-name protocols pim rp local]

Configuring the Local RP Address

To specify the local RP address, include the address statement:

You can include this statement at the following hierarchy levels:

• [edit protocols pim rp local family]
• [edit routing-instances routing-instance-name protocols pim rp local family]

Configuring the Routing Device’s RP Priority

The routing device’s priority value for becoming the RP is included in the bootstrap messages that the routing device sends. Use a smaller number to increase the likelihood that the routing device becomes the RP for local multicast groups. Each PIM routing device uses the priority value and other factors to determine the candidate RPs for a particular group range. After the set of candidate RPs is distributed, each routing device determines algorithmically the RP from the candidate RP set using a well-known hash function.

By default, the priority value is set to 1. If this value is set to 0, the bootstrap router can override the group range being advertised by the candidate RP. To modify the routing device’s priority, include the priority statement:

You can include this statement at the following hierarchy levels:

• [edit protocols pim rp local family]
• [edit routing-instances routing-instance-name protocols pim rp local family]

The priority can be a number from 0 through 255.

Configuring the Groups for Which the Routing Device Is the RP

By default, a routing device running PIM is eligible to be the RP for all groups (224.0.0.0/4). To limit the groups for which this routing device can be the RP, include the group-ranges statement:

You can include this statement at the following hierarchy levels:

• [edit protocols pim rp local family]
• [edit routing-instances routing-instance-name protocols pim rp local family]

Modifying the Local RP Hold Time

If the local routing device is configured as an RP, it is considered a candidate RP for its local multicast groups. For candidate RPs, the hold time is used by the bootstrap router to time out RPs, and applies to the bootstrap RP-set mechanism. The RP hold time is part of the candidate RP advertisement message sent by the local routing device to the bootstrap router. If the bootstrap router does not receive a candidate RP advertisement from an RP within the hold time, it removes that routing device from its list of candidate RPs. The default hold time is 150 seconds.

To modify the hold-time value for the local RP, include the hold-time statement:

You can include this statement at the following hierarchy levels:

• [edit protocols pim rp local family]
• [edit routing-instances routing-instance-name protocols pim rp local family]