Go CCIE Go!! - A Cisco Certified Internetwork Expert

Thanks Geert, both seem to be acheiving the same result, stopping a particular mcast from crossing a device, ie if the question asked was make sure 224.x.y.z is not available on this interface then could we use either…?
On 26/02/2008, Geert Nijs wrote: > > Actually they are completely different. > > ip igmp access-group acts on IGMP packets at the edge and determines which > groups a client can join by determining which IGMP membership packets the > switch will accept. > > ip multicast boundary acts on the actual multicast stream packets and > determines which multicast packets will pass the boundary by looking at the > multicast destination address. > Certain destination addresses can be filtered using ACLs. If needed, it > can also filter auto-rp messages to remove the same groups from the auto-rp > advertisements. > > regards, > Geert > > ________________________________________ > From: nobody@groupstudy.com [nobody@groupstudy.com] On Behalf Of Andy [ > and123and@googlemail.com] > Sent: 26 February 2008 14:43 > To: ccie forum > Subject: “ip multicast boundary” v “ip igmp access-group” > > Hi > > the two commands below kinda acheive the same thing, dont they? What are > the > differences and when to use one over the other. > > ip multicast boundary > > ip igmp access-group > > Thanks > > -A > > _______________________________________________________________________ > Subscription information may be found at: > http://www.groupstudy.com/list/CCIELab.html > > disclaimer : http://webservices.simac.be/disclaimer.htm