I tried the following simple topology for mVPN-
CE1 is connected to the source and CE2 has the receiver.
PE1 & PE3 VRF configuration-
ip vrf CUST1
route-target both 1:1
bgp next-hop Loopback 0
mdt default 184.108.40.206
mdt data 220.127.116.11 0.0.0.15 threshold 1 list 100
access-list 100 permit ip any any
I could send the multicast traffic from one end to another using the Default-MDT. PIM adjacency is formed over the MTI Tunnel 0.
The issue is- no matter how much multicast traffic is sent across (multicast traffic here is large ping packets), PE3 does not switchover to Data-MDT.
Please share your thoughts.
You don't need the ACL in your case and mdt-data cmd is only required on the PE connected to the source but it can't explain why it's not working.
This is the PIM debug you should have on PE connected to the source:
*Sep 13 10:36:01.683: PIM(1): MDT threshold exceeded for (18.104.22.168,22.214.171.124)
*Sep 13 10:36:01.683: PIM(1): MDT join sent for (126.96.36.199,188.8.131.52) MDT:184.108.40.206 Tunnel0
you could try with a threshold of 5 and see if it change something.
If your source is a router sending ping, please set the timeout to 0
The "debug ip pim" command should show Data-join TLVs from the PE router when the traffic for (S,G) entry exceeds the set threshold. But I didn't see any such messages.
Just wondering, did you try this in ur lab? Which routers and IOS did you use? I used 2691 with 12.4(25a) IOS. According to Cisco feature navigator, it supports mVPN.
Could you paste the output of following from your configuration on PE1 and PE3:
"show run | i pim"
"show ip pim mdt bgp"
show ip pim mdt bgp output is as follows-
PE1# show ip pim mdt bgp
Peer (Route Distinguisher + IPv4) Next Hop
MDT group 220.127.116.11
Here's another output- It clearly states Default-MDT group is created.
PE1#show ip pim mdt
* implies group is the MDT default group
MDT Group Interface Source VRF
* 18.104.22.168 Tunnel0 Loopback0 CUST1
I dont have the configs at this stage,only had this output handy.
I still need to try Laurent's tip of setting the timeout to 0 since I am send ping packets from a router.
Will update this post once I implement that.
The IOS you are using is SRC series and in the outputs you are getting extended community of 2:X:X.
Please let us know have you enabled the ipv4 mdt under bgp or not.
address-family ipv4 mdt
I have used this IOS on 2691 router-
Also, I did not enable ipv4 mdt. Most books do not have it enabled, however they could be using older IOS then.
I might have to try enabling ipv4 mdt.
Just like to provide an update that this issue was resolved when I switched over to 7200 series routers. I was able to switchover to the Data-MDT as soon as the threshold was reached.
Thank you all.
I once had a similar issue in my network where a CPP (control plane policing) policy was dropping the data-MDT joins.
Not saying this is the reason in your case but you might wanna check on these lines:
i.e. whether or not the data MDT join is being generated and makes it through the network while using the 7600/6500