08-29-2013 11:35 AM - edited 03-07-2019 03:12 PM
Hi,
So here's my scenario: I receive a bunch of different multicast feeds from seperate sources. This is all sparse-mode multicast and each group of feeds has its own RP address. To date, I've been managing the group-to-RP mappings using static ip pim rp-address commands, but as the number of feeds, sources, and internal routers grows, this is becoming unwieldy. I'd like to be able to map all of my groups at the edge to one RP for use internally, then have the edge router configured with the individual mappings, or at least distribute the RP mappings centrally so there's only one management point.
I've been reading about using AutoRP and BSR to distribute RP mappings throughout the network, but it seems like both of these require you to prop up one of your own routers as the RP:
AutoRP -- ip pim send-rp-announce <interface> group-list <acl>
BSR - ip pim rp-candidate <interface> group-list <acl>
I setup a small lab with this topology:
Group a.a.a.a Source1 ---- RTR1 (RP) --------||------- EDGERTR (RP)--------- RTRA------- Receiver
RTR1 is configured with:
ip pim rp-address <RTR1 Lo0>
EDGERTR is configured with:
ip access-list standard GROUPA
permit a.a.a.a
ip access-list standard RP-GROUPS
permit a.a.a.a
ip pim rp-address <RTR1 Lo0> GROUPA
ip pim bsr-candidate Loopback0 0
ip pim rp-candidate Loopback0 group-list RP-GROUPS
RTRA correctly shows EDGERTR's loopback as the RP for a.a.a.a.
I've been able to get this working in a simple test environment using BSR, but I'm not confident in my lab setup because I can't seem to constrain the BSR messages in the "internal" part of the network (EDGERTR-RTRA). If I attempt to use ip pim bsr-border on the interface facing RTR1, it prevents data from flowing. I assume this is because the source is registering with the RTR1 RP, and the receiver is sending the join up the tree to the internal RP, but there's nothing to bridge that gap between the two RP's.
So my goal to have something like this:
Group a.a.a.a Source1 ---- RTR1 (RP) --------||------- EDGERTR (RP)--------- RTRA------- Receiver
Group b.b.b.b Source2 ---- RTR2 (RP) --------||
So at EDGERTR, a.a.a.a is mapped to the correct RP at RTR1, but at RTRA it's mapped to EDGERTR using AutoRP or BSR. Same for b.b.b.b, and so on.
Any ideas on what I'm doing wrong, or any suggestions on a better way to do this?
Thanks
08-29-2013 12:01 PM
Hello,
Are you familiar with Multicast Source Discovery Protocol (MSDP)? This protocol allows multiple RPs to exchange information about active sources. In your case, if your RTR1 RP becomes aware of the source to the group a.a.a.a, it will inform the EDGERTR RP so that it knows about the source and can send PIM Join towards it. I believe it would work even across BSR borders.
Read the following document about Anycast RP - your situation is quite similar.
http://www.cisco.com/en/US/docs/ios/solutions_docs/ip_multicast/White_papers/anycast.html
Feel welcome to ask further!
Best regards,
Peter
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide