Configure PIM Sparse Mode with Bootstrap RP

In this section, we will convert the existing multicast topology from a statically defined RP to a bootstrap learned RP. As part of this conversion, the network is being redesigned to add a second RP for redundancy. The configuration objectives are as follows:

  • Remove the static RP definition from all routers.

  • Configure Stout as a second RP for the 224/4 group range.

  • Use bootstrap-based RP election, and make sure that PBR is the BSR when operational.

  • Ensure that there is no single point of RP/BSR failure in the network.

The new redundancy requirements make it clear that the network will need two RPs and two candidate BSRs. Further, the bootstrap priority will need to be higher (more preferred) at PBR to ensure that it is the BSR when operational. Figure 11-14 shows the updated topology.

Bootstrap RP election

Figure 11-14. Bootstrap RP election

The figure shows that both PBR and Stout are configured to function as candidate RPs and candidate BSRs (C-RP and C-BSR). Although not technically necessary, currently it is a best practice to make the C-RP and C-BSR functionality collocated, given that the loss of either function kills PIM sparse mode operation and negates any benefits associated with distributing C-BSR and C-RP functionality among different nodes. The higher BSR priority setting at PBR results in its election as the domain’s BSR when operational; otherwise, ...

Get Junos Enterprise Routing, 2nd Edition now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.