Why Cannot an MDT Be Set Up Correctly If the RPF Neighbor Is Not a PIM Neighbor?

Adamcolob · Created May 15, 2017 07:24:59

The PIM protocol does not maintain its own unicast routing table. Instead, it uses the existing unicast routing table as a basis for the RPF check. Generally, the object of the RPF check is the multicast source. On a PIM-SM network, the objects of the RPF check can be the multicast source, RP, and BSR. For the object of an RPF check, the PIM device searches the existing unicast routing table for an optimal route to the object. The outbound interface of the route acts as an RPF interface and the next-hop device acts as an RPF neighbor. If there are multiple next-hop addresses, the hop with the highest IP address acts as the RPF neighbor. You can view that the RPF neighbor completely depends on the existing unicast route and is independent of the PIM protocol.

The PIM protocol, however, requires that the RPF neighbor be a PIM neighbor. This requirement can be guaranteed through network design. PIM protocol does not select an RPF neighbor from non-PIM neighbors because PIM protocol does not maintain the unicast routing information independently. If the corresponding interface of the device where the RPF neighbor resides is not enabled with PIM, the MDT cannot be correctly set up and hence multicast forwarding fails.

Solution: Enable the PIM protocol on the corresponding interface where the RPF neighbor resides.

Danielarab · Created May 14, 2020 18:53:02

Good post

Danielarab · Created May 14, 2020 18:53:12

thanks for taking you time!

Why Cannot an MDT Be Set Up Correctly If the RPF Neighbor Is Not a PIM Neighbor?

Third Party’s Trade Secret

My Followers

Enterprise

Consumer

Corporate

Carriers

Why Cannot an MDT Be Set Up Correctly If the RPF Neighbor Is Not a PIM Neighbor?

Third Party’s Trade Secret

My Followers