From: GAURAV MADAN (gauravmadan1177@gmail.com)
Date: Fri Feb 20 2009 - 14:06:43 ARST
Hobbs
I had this thing in mind (whatever u said) but somehow i feel my sol (sol 1)
is correct based on following :
1) As i know ; multicast boundary filters based on dest address and
access-grp filters based on source-address
So If i use the multicast boundary ; I am actually instructing the router
to filter the pkts with dest as < whatever specified>.
2) If I specify access-grp command ; I am actually saying that "Please
listen to IGMP jons for these addresses only"
Again if we have join ; then only traffic will b forwarded .
SO I have feeling ; that sol 1 is valid .
Can someone put more light on this case
Regards
Gaurav Madan.
On Fri, Feb 20, 2009 at 9:22 PM, Hobbs <deadheadblues@gmail.com> wrote:
> Gaurav,
> IGMP solution looks right. Remember hosts use IGMP to join groups. I
> believe multicast boundary is used to filter PIM joins from routers (as
> opposed to IGMP reports from hosts).
>
> On Fri, Feb 20, 2009 at 8:03 AM, GAURAV MADAN <gauravmadan1177@gmail.com
> > wrote:
>
>> Hi All
>>
>> I have a case which says :
>>
>>
>> R4
>> | f0/0
>> |
>> CLIENTS
>>
>> These clients shd only recieve feeds for groups 225.25.25.25 and
>> 226.26.26.26
>>
>> I answered :
>>
>> Rack1R4(config-if)#do sh ip access-li
>> Standard IP access list 17
>> 10 permit 225.25.25.25
>> 20 permit 226.26.26.26
>>
>> int f0/0
>> ip multicast boundary 17
>> !
>>
>>
>> 2nd solution
>> ---------------------
>> Let these clients join these 2 grps only
>>
>> int f0/0
>> ip igmp access-grp 17
>> !
>>
>> Let me know if and why sol 1 is wrong ?
>>
>> Gaurav Madan
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sun Mar 01 2009 - 09:44:12 ARST