MTI source manipulation
You cannot manually configure MTI interfaces. The way the MTI works is the MTI should be sourced off the loopbacks that create the MP-BGP sessions. However, in the situation that you have multiple MP-BGP sessions on the same router (R1), say, one is for MP-iBGP (update-source loopback0, with IP address 188.8.131.52), another is for MP-eBGP (via directly connected interfaces with other AS, IP add is 184.108.40.206), I found the MTI on this router (R1) is always sourced off the highest IP address from the MP-BGP (no matter iBGP or eBGP) sessions. In this example, the MTI will always choose 220.127.116.11 as the source. This causes the mVPN not working, the PIM neighbor via the MTI cannot come up at all.
So my current solution is, in this situation, change the MP-eBGP from directly connected session to loopback to loopback multihop session. This can resolve this issue, but the problem is, usually when I realize this, I am doing multicast tasks, and the previous tasks have been done long time ago, if I change the configuration at this point, it's pretty risky, and the previous tasks didn't ask to create the MP-eBGP via loopbacks.
So I am wondering, is there any way to manipulate the MTI source? I guess the answer might be NO, but still want to check with you guys.