Multicast: rather than dense, sparse it and let’s meet at rendez-vous point… Part 5

Client1 is configured to join multicast destined for group 226.0.0.1 and sent from Server1

Instead of PIM-Dense (flood and prune) we use PIM-Sparse to build the forwarding path from the server to the client

Multicast routing: From the source… Part 3

We build on our discussion from the previous blogs

The test topolgy

How R3 handles Server2 source multicast trafic?