"ip multicast boundary" is only available for layer 3 interfaces. So, if I need to restrict multicast to an individual AP, that's not an option.
Jason Boyers - CCIE #26024 (Wireless) Technical Instructor - IPexpert [email protected] On Mar 31, 2011, at 7:44 AM, Ralph Olsen <[email protected]> wrote: > I would go to the proctor and say: "I can solve this task using option > A and B, do you can if I use one or the other?" > > If the answer is "I don't care" do what ever. > > If the answer is "I can't answer that", then read the question again > and select the best option. :o) > > /Ralph > > 2011/3/31 Leigh Jewell <[email protected]>: >> 2.7 Multicat (IGMP, PIM) >> >> The question calls restrictions on a multicat group "... should be the only >> multicast stream permitted in the administratively scoped range across the >> link" and additionally there was a need not to allow this multicat group to >> the Autonomous APs. >> >> The answer users an ACL to block the traffic. Reading the Multicast SRND it >> seems to prefer using 'ip multicast boundary' command as a way for >> restricting multicast groups. >> >> The question is here, do we just ask the proctor and if in doubt stick to a >> SRND ? >> >> Cheers, >> Leigh >> -- >> CCIE Blog - http://leigh-cciewireless.blogspot.com/ >> >> _______________________________________________ >> For more information regarding industry leading CCIE Lab training, please >> visit www.ipexpert.com >> >> > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
