Re: Multicast boundary or ip igmp access group

From: Gregory Gombas (ggombas@gmail.com)
Date: Tue Oct 16 2007 - 11:40:31 ART


Great question.

I think it depends on the wording of the questions for example:
1. Prevent hosts from requesting multicast traffic - (igmp ACL)
2. Prevent multicast traffic from exiting link - (boundary).

On 10/12/07, nicky noname <cisco2study@gmail.com> wrote:
> Hello,
>
> I have had this doubt in my head for quite a while. I thought we used the
> multicast boundary command to limit the scopt of the administratively
> scopped m-cast addresses. the Doc CD defines it's use,
>
> "Use this command to configure an administratively scoped boundary on an
> interface to filter multicast group addresses in the range defined by the *
> access-list* argument. A standard access list defines the range of addresses
> affected. When this command is configured, no multicast data packets are
> allowed to flow across the boundary from either direction. Restricting
> multicast data packet flow enables reuse of the same multicast group address
> in different administrative domains."
>
>
> Then to define the ip igmp access-group command,( which would see to be for
> limiting access to specify m-cast feeds in particular)
>
> To control the multicast groups that hosts on the subnet serviced by an
> interface can join, use the *ip igmp access-group* command in interface
> configuration mode. To disable this control, use the *no* form of this
> command.
>
>
> So, are these two commands complete interchangeable?........i understand
> that there may be added fuctionality on the boundary command....but i guess
> we can use the igmp access-group command also it limit auto-rp
> advertisements. I would need to lab this.
>
> If you have a clear understanding of the relationship between the commands,
> I would appreciate your opinion.
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html



This archive was generated by hypermail 2.1.4 : Fri Nov 16 2007 - 13:11:15 ART