PIM Sparse Mode: Static RP
At this stage, you should have an extensive grounding in IP multicast theory in general, and in PIM sparse mode operation in particular. This knowledge is soon to bear fruit as you configure and validate the operation of PIM sparse mode using a statically defined RP with Juniper Networks’ routers.
The initial PIM sparse mode deployment goals are as follows:
PBRas an RP for the entire multicast address range.
Configure all other routers to use
PBRas the domain’s RP without using BSR or auto-RP.
Ciderto function as a multicast receiver for group 18.104.22.168.
Aleas a multicast source to generate traffic to group 22.214.171.124.
Verify RPT join and subsequent traffic-driven switches to SPT.
Figure 10-13 details the portion of Beer-Co’s network that is to be enabled for multicast support. The figure also highlights key aspects of the IGP routing infrastructure now in place.
Figure 10-13. Beer-Co’s multicast topology
Details to note in Figure 10-13 include the following:
The default OSPF bandwidth scaling factor is in effect with the exception of
PBR’s end of the
Lagerlink (asymmetric) and the
Bocklink. The metric for these links has been altered in an effort to favor the
Porterpath for communications between
Aleis configured to emulate a host sending to a multicast group.
Aleuses a default route ...