If you have a VLAN which used as the source of multicast streams there are considerations on how it is used specifically when you are “stretching” that VLAN across the fabric, i.e. you have the VLAN and router(s) for that VLAN on a particular distribution switch pair, but then you have the VLAN stretched across the fabric within an I-SID and presented out to edge switches that uplink to a different distribution switch pair (which obviously don’t have routers for that network).
There is a need to ensure that the VLAN interface on this different distribution switch pair (to where the source is) also has the ability to send such IGMP join requests direct to the IGMP Querier, otherwise without the mvpn-isid command, they are gobbled up before they reach the destination, which in this case is on Router A.
In the example below our client is connected to Switch B (on the left), and the Server that is providing the multicast stream is connected to Switch A on the right. They are both on VLAN 299 (tv) which is “stretched” across the Extreme Fabric via an I-SID. The routing for the VLAN is taking place on Router A, hence this has an IP address on the VLAN interface, but the Router B VLAN interface does not.
Clients connected to switch A can access the streams without issue, clients connected to another switch (not pictured) which is connected to Router A can also access the streams fine. But a Client connected to switch B cannot, the IGMP joins are made, the streams can be seen across the fabric, but the client never connects to it as expected.
For example the “tv” VLAN (299), you need to enable the “mvpn-isid 0 1″ command.
The additional “ip igmp routed-spb-querier-addr” is required, due to: By default IGMP Queries are sent on the “ip spb-multicast” enabled interfaces, using the IP address configured on the VLAN. However in the case of this configuration (Router B) the “mvpn-isid” enabled interface, has no IP Address is configured on the VLAN, because its not a routed interface, so the Queries are sent by default using source IP 0.0.0.0., which most clients don’t like. If the Multicast doesn’t work without the querier IP address, configure any random IP address as the IGMP querier IP (it can be 1.1.1.1 for example as it has only local significance) once that is added, restart the stream and you should find you can access it fine.
interface vlan 299
ip spb-multicast enable
mvpn-isid 0 1
(ip igmp upnp-filter)
ip igmp routed-spb-querier-addr 1.1.1.1
exitIt is also worth noting that a client which is connected to a non sender VLAN, i.e. not on the “tv” VLAN and has the routing “local” to it, i.e. the edge switch uplinks directly to the distribution switch pair where the routing for that VLAN happens, does not require the “mvpn-isid 0 1” or “ip igmp routed-spb-querier-addr” commands, because the multicast traffic hits the router and therefore not gobbled by the fabric and the routed interface acts as a IGMP Querier for that VLAN, Layer 2 and Layer 3 subnet ergo it does not need to be manually specified.
https://extreme-networks.my.site.com/ExtrArticleDetail?an=000110099
https://extreme-networks.my.site.com/ExtrArticleDetail?an=000096882