The Journey of a Network Engineer

Nov 29 2011   1:29AM GMT

How Rendezvous Points (RP) Chosen in Auto-RP Multicast Domain?

Sulaiman Syed Profile: Sulaiman Syed

IP Multicast can work on Dense, or Sparse Mode. Dense, where all multicast traffic is flooded out of all the interfaces other than the one it came from (split horizon). It is easy to configure, and there are no planning with it. The down side is, it might create congestion in the network. Specially the WAN links, where every byte cost money. To tackle this issue, Sparse mode should be used.

Sparse mode, works by creating Shared-Tree that is rooted to the Rendezvous Point (RP). By default, all routers assume no one wants the multicast traffic, until they get a request for it.

To load balance the traffic, multiple RPs can be configured. But the question is, which RP will be responsible for which group of multicast streams?

The answer is simple, the RP will be chosen by Mapping Agent (MA) on the longest (most specific) Multicast group.

An example will clarify

R1(config)#ip access-list standard GROUP_1
R1(config)#ip pim send-rp-announce loopback 1 scope 5 group-list GROUP_1
R2(config)#ip access-list standard GROUP_2
R2(config)#ip pim send-rp-announce loopback 1 scope 5 group-list GROUP_2

What will happen, that R1 will be the RP for group to while R2 for to Group will have no RP, so the only way for that group to work is to be configured in Dense mode.

 Comment on this Post

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members comment.

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

Share this item with your network: