When configuring anycast RP...can this be done in Auto-RP and BSR apart from static.
I am familiar with the technical documentation and in fact, it supports my standpoints. Perhaps there is a misunderstanding between the terms we both use, despite talking about the same thing. Let me discuss these things with you.
My standpoint is that AnycastRP cannot be successfully created without the help of MSDP. I am not saying that AutoRP or BSR are unusable or incompatible with AnycastRP - on the contrary, they are necessary and required also with AnycastRP, especially in large networks. What I am saying is that having AutoRP or BSR alone is not sufficient to provide AnycastRP service. You may have the AutoRP or BSR - absolutely no problem with that - but you must have MSDP in addition to those protocols in order to have a workable AnycastRP.
Quoting from the document "Anycast RP" at:
Anycast RP allows two or more rendezvous points (RPs) to share the load for source registration and the ability to act as hot backup routers for each other. Multicast Source Discovery Protocol (MSDP) is the key protocol that makes Anycast RP possible.
So, the AnycastRP is a configuration of multiple RPs that all have the same IP address which has certain benefits. The means of making this IP address known to multicast routers in your domain is another business - you may use BSR, AutoRP or static configuration for that. The problem here is that if two or more routers advertise the same IP address in a routing protocol, the network will be effectively partitioned - each router will use the closer RP, according to the routing protocol metrics. Now, consider that there are two RPs with the same IP address, A and B. A multicast sender close to router A starts sending the multicast stream. The multicast stream will be sent to the RP A. Further on, consider that there is a recipient of this traffic close to the RP B. A shared tree will be created for this recipient with the root in RP B. However, the RP B has no idea that there is already is a sender for this multicast group because it has never received a multicast packet from it. Without an additional protocol, the recipient closer to the RP B will never start receiving the multicast stream sent by a sender close to RP A. This is where the MSDP comes in. As soon as RP A notices there is a sender for a particular multicast group, it informs its MSDP neighbors (the RP B in this case) about the existence of a sender to a particular multicast group. The RP B will now know about it, and when a recipient subscribes to this group, the RP B is able to send the Join towards the sender, thereby creating a branch of multicast distribution tree through which the multicast stream can flow natively. Notice that neither AutoRP nor BSR can help you here because they do not disseminate information about multicast senders. You absolutely must use the MSDP here, otherwise, you can't have a true AnycastRP.
Regarding the multiple mapping agents: Quoting from document "Multicast Quick-Start Configuration Guide" at:
You can use one RP that also serves as the mapping agent, or you can configure multiple RPs and multiple mapping agents for redundancy purposes.
Also, quting from the internet draft where the AutoRP was first submitted to IETF (but never made it to RFC) available at:
For robustness purpose, multiple RP-mapping agents may be configured inside the same administrative domain. Each RP-mapping agent also listens to the the RP mapping discovery group CISCO-RP-DISCOVERY, and suppresses the sending of its own RP-mapping packets if it hears RP-mapping packets originated from another RP-mapping agent with a higher IP address.
I hope this clarifies the confusion in this field.
For Anycast RP, you need to use the Multicast Source Discovery Protocol (MSDP) in addition to providing routers with RP knowledge, be it static, BSR or AutoRP. The mechanisms for basic RP discovery like BSR or AutoRP or even static RP configuration are not capable alone to provide the Anycast RP functionality. Of course, you can combine any of them with MSDP.
You might want to read this document for further information and for configuration examples: