Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Configuring PIM Bootstrap Router

Understanding the PIM Bootstrap Router

To determine which routing device is the rendezvous point (RP), all routing devices within a PIM sparse-mode domain collect bootstrap messages. A PIM sparse-mode domain is a group of routing devices that all share the same RP router. The domain bootstrap routing device initiates bootstrap messages, which are sent hop by hop within the domain. The routing devices use bootstrap messages to distribute RP information dynamically and to elect a bootstrap routing device when necessary.

Configuring PIM Bootstrap Properties for IPv4

For correct operation, every multicast routing device within a PIM domain must be able to map a particular multicast group address to the same Rendezvous Point (RP). The bootstrap routing device mechanism is one way that a multicast routing device can learn the set of group-to-RP mappings. Bootstrap routing devices are supported in IPv4 and IPv6.

Note: For legacy configuration purposes, there are two sections that describe the configuration of bootstrap routing devices: one section for both IPv4 and IPv6, and this section, which is for IPv4 only. The method described in Configuring PIM Bootstrap Properties for IPv4 or IPv6 is recommended. A commit error occurs if the same IPv4 bootstrap statements are included in both the IPv4-only and the IPv4-and-IPv6 sections of the hierarchy. The error message is “duplicate IPv4 bootstrap configuration.”

To determine which routing device is the RP, all routing devices within a PIM domain collect bootstrap messages. A PIM domain is a contiguous set of routing devices that implement PIM. All are configured to operate within a common boundary. The domain's bootstrap routing device initiates bootstrap messages, which are sent hop by hop within the domain. The routing devices use bootstrap messages to distribute RP information dynamically and to elect a bootstrap routing device when necessary.

PIM bootstrap messages are sourced from the loopback address, which is always up. The loopback address must be routable; if it is not routable, then the bootstrap routing device is unable to send bootstrap messages to update the RP domain members. See Configuring the Loopback Interface for information about configuring a loopback interface.

1. Configure the bootstrap priority.

   By default, each routing device has a bootstrap priority of 0, which means the routing device can never be the bootstrap routing device. A priority of 0 disables the function for IPv4 and does not cause the routing device to send bootstrap routing device packets with a 0 in the priority field. The routing device with the highest priority value is elected to be the bootstrap routing device. In the case of a tie, the routing device with the highest IP address is elected to be the bootstrap routing device. A simple bootstrap configuration assigns a bootstrap priority value to a routing device.

   [edit protocols pim rp]user@host# set bootstrap-priority 3
2. (Optional) Create import and export policies to control the flow of IPv4 bootstrap messages to and from the RP, and apply the policies to PIM. Import and export policies are useful when some of the routing devices in your PIM domain have interfaces that connect to other PIM domains. Configuring a policy prevents bootstrap messages from crossing domain boundaries. The bootstrap-import statement prevents messages from being imported into the RP. The bootstrap-export statement prevents messages from being exported from the RP.
   [edit protocols pim rp]user@host# set bootstrap-import pim-bootstrap-importuser@host# set bootstrap-export pim-bootstrap-export
3. Configure the policies.
   [edit policy-options policy-statement pim-bootstrap-import]user@host# set from interface se-0/0/0user@host# set then reject
   [edit policy-options policy-statement pim-bootstrap-export]user@host# set from interface se-0/0/0user@host# set then reject
4. Monitor the operation of PIM bootstrap routing devices by running the show pim bootstrap command.

Configuring PIM Bootstrap Properties for IPv4 or IPv6

For correct operation, every multicast routing device within a PIM domain must be able to map a particular multicast group address to the same Rendezvous Point (RP). The bootstrap routing device mechanism is one way that a multicast routing device can learn the set of group-to-RP mappings. Bootstrap routing devices are supported in IPv4 and IPv6.

Note: For legacy configuration purposes, there are two sections that describe the configuration of bootstrap routing devices: one section for IPv4 only, and this section, which is for both IPv4 and IPv6. The method described in this section is recommended. A commit error occurs if the same IPv4 bootstrap statements are included in both the IPv4-only and the IPv4-and-IPv6 sections of the hierarchy. The error message is “duplicate IPv4 bootstrap configuration.”

To determine which routing device is the RP, all routing devices within a PIM domain collect bootstrap messages. A PIM domain is a contiguous set of routing devices that implement PIM. All devices are configured to operate within a common boundary. The domain's bootstrap routing device initiates bootstrap messages, which are sent hop by hop within the domain. The routing devices use bootstrap messages to distribute RP information dynamically and to elect a bootstrap routing device when necessary.

PIM bootstrap messages are sourced from the loopback address, which is always up. The loopback address must be routable; if it is not routable, then the bootstrap routing device is unable to send bootstrap messages to update the RP domain members. See Configuring the Loopback Interface for information about configuring a loopback interface.

1. Configure the bootstrap priority.

   By default, each routing device has a bootstrap priority of 0, which means the routing device can never be the bootstrap routing device. The routing device with the highest priority value is elected to be the bootstrap routing device. In the case of a tie, the routing device with the highest IP address is elected to be the bootstrap routing device. A simple bootstrap configuration assigns a bootstrap priority value to a routing device.

   Note: In the IPv4-only configuration, specifying a bootstrap priority of 0 disables the bootstrap function and does not cause the routing device to send BSR packets with a 0 in the priority field. In the configuration shown here, specifying a bootstrap priority of 0 does not disable the function, but causes the routing device to send BSR packets with a 0 in the priority field. To disable the bootstrap function in the IPv4 and IPv6 configuration, delete the bootstrap statement.

   user@host# edit protocols pim rpuser@host# set bootstrap family inet priority 3
2. (Optional) Create import and export policies to control the flow of bootstrap messages to and from the RP, and apply the policies to PIM. Import and export policies are useful when some of the routing devices in your PIM domain have interfaces that connect to other PIM domains. Configuring a policy prevents bootstrap messages from crossing domain boundaries. The import statement prevents messages from being imported into the RP. The export statement prevents messages from being exported from the RP.
   [edit protocols pim rp]user@host# set bootstrap family inet import pim-bootstrap-importuser@host# set bootstrap family inet export pim-bootstrap-export
3. Configure the policies.
   [edit policy-options policy-statement pim-bootstrap-import]user@host# set from interface se-0/0/0user@host# set then rejectuser@host# exituser@host# edit policy-options policy-statement pim-bootstrap-exportuser@host# set from interface se-0/0/0user@host# set then reject
4. Monitor the operation of PIM bootstrap routing devices by running the show pim bootstrap command.

Example: Rejecting PIM Bootstrap Messages at the Boundary of a PIM Domain

In this example, the from interface so-0-1/0 then reject policy statement rejects bootstrap messages from the specified interface (the example is configured for both IPv4 and IPv6 operation):

Example: Configuring PIM BSR Filters

Configure a filter to prevent BSR messages from entering or leaving your network. Add this configuration to all routers: