Tim Stevenson wrote:
That's not really the critical thing, so much as - you need an IGMP
querier active in the VLAN in order for snooping to work
correctly/reliably. Some applications may behave fine without; others
won't. The key is periodic joins from the hosts are required to
maintain membership state for snooping. The querier ensures that happens.
So what you really need is an SVI *with* an IP address for that vlan,
and then enable igmp snooping querier for that vlan. The configured IP
is used to source queries. The SVI in this case can actually be
shutdown, it doesn't really matter.
The config is like:
int vlan 200
ip add 10.1.1.1/24
ip igmp snooping querier
shut
The other option is to just enable PIM on the (admin up) SVI in the
vlan, but you may not want to do that, depends on the network design.
int vlan 200
ip add 10.1.1.1/24
ip pim sparse
no shut
HTH,
Tim
Creating an unnumbered interface didn't seems to work. Now I am trying
your solution, the one with "ip igmp snooping querier". I don't want to
involve the switches in any multicast routing.
--
Best regards,
Adrian Minta
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
