I've read the one document 'Configuring Multicast VPN Extranet Support'. But it only talks about remote MVRF M-cast, not MVRF sharing with S, G exist behind the same PE (pair).
After doing a practical implementation last Friday where the source MVRF was to be joined to by receivers in another User (M)VRF, it was required to point the MVRFs to the same RP (PE)...using a static command, ip pim...rp-address OVERride...predictably, each MVRF was pointing to its own RP, (running autoRP in this environment with pairs of PE's at each distribution point around the campus). I understand why the OVERride would work here, but it's not ideal.
QUESTION(S):
What is the best method for creating this "pointing to same RP" solution in a more dynamic fashion so that it will support M-Cast VPN Extranet MVPN/MVRF's behind the same PE(s)?
We'll need high availability aspects for this to be scalable/reliable.
Can it be made to work with AutoRP, or, are pointing all MVPN/MVRFs to the same pair of weighted static RP's the solution? Or, is the OVERride the only solution for Extranet MVPN?
(Note that the documentations says the source and RP must be behind the same PE - I get that, just not how to improve M-cast HA aspects since now we're pinning up a single point of failure RP - that can't be a good thing.)
