I have an OTV-Multicast Query (haha, get it? Anyone...?)
Below is my logical topology, simplified to exclude the OTV VDCs and just show the L2 extension between data centers:
I was testing my mcast configuration and noticed a peculiarity. Being lazy in the lab, I only configured mcast on one side to test clients on both sides of the OTV. The result was that the client at DC2 could, in fact, receive mcast traffic just fine. However, after 3 minutes, it would lose its stream. Meanwhile, the client at the local side would continue to receive the stream.
So I figured this must be an IGMP issue. Digging deeper, indeed, the DC2 client is NOT receiving queries from the DC1 N7K. Interestingly, it's receiving PIM hellos just fine (224.0.0.13), and, again, it receives its requested stream no problem until the PIM timer expires. So multicast traffic is traversing the OTV connection just fine.
Next, I configured a L3 connection between the sites and extended PIM to the Vlan12 interface at DC2 (I can upload a topology image if helpful). Everything then worked fine, but I also noticed something interesting - both 7Ks viewed themselves as the IGMP querier, which means that, just as before, they are not seeing each others' IGMP queries, an apparent 'feature' of OTV.
So my question - is OTV blocking IGMP queries specifically? I tried pinging from DC1 to 224.0.0.1, sourced from Vlan12, and DC2's Vlan12 interface replied, so traffic toward 224.0.0.1 seems fine.
I'm curious if there's a way to make this work without extending the mcast domain - I tried this but it did not work: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/nx-os/multicast/configuration/guide/b_multicast/b_multicast_chapter_0110.html#concept_3D8E36AD4B3A48158C358C1B6546D522
Thanks!
Jeff