Pim is needed on sender segments. Igmp is needed on receiver segments.
Basically one command is easier to do both jobs as they go hand and hand
with each other in the environments typically..
On Mar 1, 2011 10:16 AM, "Benjamin Lovell" <[email protected]> wrote:
> Turning on PIM also turns on the IGMP querier function so we therefor
> have turned on IGMP as query message is of type IGMP. I have never
> looked to see if we make a distinction between a multiaccess vlan
> interface and a point to point routed interface where it is not
> strictly needed but I assume we do not.
>
> -Ben
>
> On Feb 23, 2011, at 4:24 PM, John Neiberger wrote:
>
>> IGMP is enabled automatically when you enable PIM on an interface and
>> I can't figure out why. I've talked to a few other engineers and no
>> one can thing of why IGMP would need to be enabled on a
>> router-to-router connection running PIM. My only thought was that it
>> was a leftover from PIMv1, which used IGMP type 14 packets, but that's
>> a total guess.
>>
>> Do any of you happen to know the answer to this piece of trivia?
>>
>> Thanks!
>> John
>> _______________________________________________
>> cisco-nsp mailing list [email protected]
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
> _______________________________________________
> cisco-nsp mailing list [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
