This section provides an example for configuring basic PIM-DM functions, so that a user can receive data from any multicast source in a normal unicast routing AS.
On a PIM-SM network that uses a BootStrap router (BSR) Rendezvous Point (RP), configure a BSR administrative domain to allow Candidate-BootStrap Routers (C-BSRs) to serve groups in a specified group address range.
This section provides an example for configuring filtering policies, including setting a valid source address range and a valid Candidate-Rendezvous Point (C-RP) address range, to prevent malicious packet attacks on a PIM-SM network.
If a receiver wants to perform the SPT switchover only when the rate of multicast data packets reaches the threshold, you need to configure triggering conditions for the SPT switchover. By default, the Rendezvous Point (RP) and the DR at the group member side immediately perform the shortest path tree (SPT) switchover after they receive the first multicast data packet.
This section provides an example for configuring basic Protocol Independent Multicast-Source-Specific Multicast (PIM-SSM) functions so that hosts can receive multicast data from specific multicast source.
In the scenario where multiple multicast sources and receivers are located in a PIM-SM domain, you can configure Anycast-Rendezvous Point (RP) peer relationships so that IP routing will automatically select the topologically closest RP for each source and receiver. This alleviates burdens on RPs, implements RP backup, and optimizes multicast forwarding paths.
On a PIM-SM network, you can configure IPv4 PIM IPsec on the interfaces setting up PIM neighbor relationships to protect the devices against forged IPv4 PIM protocol packets.
This section provides an example for configuring PIM FRR. PIM FRR helps minimize multicast traffic loss caused by link or node failures on networks that have high real-time transmission requirements.
This section provides an example for configuring PIM FRR on a ring network. PIM FRR relies on IGP FRR to compute primary and backup routes. IGP FRR can generally compute out both primary and backup routes on a node. However, a live network easily encounters backup route computation failures on some nodes due to the increase of nodes on the network. To resolve this issue, IP FRR needs to be deployed to work together with IGP FRR for route computation.