Hi again all, On Tue, Jan 12, 2010 at 11:30 AM, Dale Shaw <dale.shaw+j-...@gmail.com> wrote: > > I'm operating in a bit of an information vacuum here, but I'm trying > to help out some colleagues with a server NIC teaming / EX switch > problem.
Here's an update: My colleagues revisited the problem last night and disabling IGMP snooping has 'fixed' the problem. My question is, why is the switch doing anything but flood non-IP L2 multicasts and why is this traffic subject to the rules of IGMP snooping? :-) (The NIC team member interfaces won't be sending IGMP joins -- it's not IP multicast.) The previously referenced PR (PR/492704) sounded promising -- does anyone have any insight into how the fix for that has been/is being implemented? If disabling IGMP snooping is indeed the 'best' fix, what does the list consider the most elegant / least intrusive way of disabling it? They disabled it for the whole VLAN ("set protocols igmp-snooping vlan server disable") but I'm guessing this means IP multicast traffic will be flooded to all stations in the VLAN whether they're interested in the traffic, or not. The second link (PDF) below seems to indicate IGMP snooping can be disabled explicitly on individual interfaces like so: protocols { igmp { interface interface-name; disable; } } Other useful references: http://kb.juniper.net/index?page=content&id=KB15316&actp=LIST http://kb.juniper.net/library/CUSTOMERSERVICE/technotes/8010061-EN.PDF cheers, Dale _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp