1)I am getting the following error:
%MDT-4-LBSRC: VRF ABC1: MDT EthernetX/Y uses source address 220.127.116.11 from a non-loopback interface
on R6 (Most probably due to VPNv4 BGP source address). It's solvable with bgp next-hop Loopback0 statement under vrf address-family. I am curious why you didn't encounter the same issue.
2) What is the reason in below configuration without enabled SSM?
Configure MP-BGP IPv4 MDT between R2, R7, R8 and R9, R9 is route-
Configure MP-BGP IPv4 MDT between R6 and R9
Ensure multicast VPN source and group information be distributed among
R2, R7, R8, R9 and R6
1) I meet the error on some IOS version before, and in this version, this error not appear. And I think "bgp next-hop loopkack0" is a good practice to avoid this issue.
2) Yes, this question can be written as SSM based so that MDT make more sense. here the question purpose is just for the undestanding of MDT update.
To make MSDP working I leaked the R2 and R6 loopbacks between ***. I did it with redistribution between isis and bgp ipv4 unicast. Is there any better way to do it?
When I finished the TE lab and everything was working and started with the MVPN lab I couldn't make it working if I didn't disable the TE tunnels in R2 and R8. Is there any way to make MVPN works with the TE tunnels in core up and running?
Have you checked for RPF failures? When running MPLS-TE, you have to make sure tunnels are not used for RPF check, as multicast is not forwarded in tunnels, or label switched (unless running LSM).
Do this by enabling mpls traffic-eng multicast-intact ISIS or OSPF.
Joachim Jerberg Jensen