From: Jeff Andiorio (jandiorio@gmail.com)
Date: Wed Mar 25 2009 - 19:42:18 ART
the difference is that the igmp filter is preventing the request for
traffic and the boundary prevents the traffic.
On 3/25/09, Pradeep Chandrashekaran <chanpraddy@gmail.com> wrote:
> Hey group,
> I have a task which asks me to filter a switch from receiving
> traffic for administratively scoped multicast groups regardless of any IGMP
> join messages it receives.
>
>
> The scenario is :
>
> R4---Fa0/0------Fa0/15---------SW1
>
> My Solution was:
> R4#sh run int fa0/0
> Building configuration...
>
> Current configuration : 146 bytes
> !
> interface FastEthernet0/0
> ip address 178.1.38.3 255.255.255.0
> ip pim sparse-dense-mode
> ip igmp access-group 11
> duplex auto
> speed auto
> end
>
> R4#
>
> R4#sh run | sec access-list 11
> access-list 11 deny 239.0.0.0 0.255.255.255
> access-list 11 permit 224.0.0.0 15.255.255.255
> R4#
>
> The Solution Script says:
>
> R4:
> interface Ethernet0/0
> ip multicast boundary 51
> !
> access-list 51 deny 239.0.0.0 0.255.255.255
> access-list 51 permit 224.0.0.0 15.255.255.255
>
> Can someone explain the difference?
>
> Thanks /Pradeep
>
>
> --
> Adversity introduces a man to himself.
>
>
> 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 : Mon Apr 06 2009 - 06:44:07 ART