From: NET HE (he_net@hotmail.com)
Date: Thu Feb 12 2009 - 23:49:09 ARST
If the question wording is exactly as you mentioned, I wouldn't pick up any
solutions you provided. I would do
access-li 11 deny 224.0.1.39access-li 11 deny 224.0.1.40access-li 11 per any
int f0/0ip multicast boundary 11 out
Why, because your solution 1 didn't specify in or out, by default it works on
both directions. Since your question says " multicast AUTO-RP announce and
discovery messagesshould not be sent out f0/0 ", it means the interface should
still be able to receive auto-rp announce and discovery messages. Imaging the
interface of this router is connected to a upstream router, which is a RP.
Best Regards, Net (Xin) He > Date: Thu, 12 Feb 2009 09:58:26 -0700> Subject:
Re: multicast boundary> From: deadheadblues@gmail.com> To:
gauravmadan1177@gmail.com> CC: ccielab@groupstudy.com> > Hi Gaurav,> > I just
quickly labbed these scenarios and this is my understanding,> please chime in
if I am mistaken:> > Solution 1: You are preventing joins for the AUTO-RP
groups, so in> effect it does what you are tasked with. Since the upstream
device> prevents the downstream device from joining those groups, it will not>
forward AUTO-RP messages out of that interface.> > Solution 2: You are
actually preventing the AUTO-RP messages from> being sent to the downstream
router. You are also preventing any> mroute state for any group.> > Solution
3: I think this accomplishes the same as #1 because you are> preventing the
AUTO-RP groups from being joined by the downstream> router.> > It looks like
the filter-autorp keyword works on groups that were> denied by the ACL. So if
you are going to deny everything anyway, then> filter-autorp is redundant. ANd
if you are going to prevent the> AUTO-RP groups from being joined, the
filtering AUTO-RP messages for> the other groups is again redundant.> > That
being said, they all seem to solve your task. If I had a choice,> I don't know
what I would pick... :)> > -hth> > > On Thu, Feb 12, 2009 at 8:06 AM, GAURAV
MADAN <gauravmadan1177@gmail.com> wrote:> > HI All> >> > I have a task that
says multicast AUTO-RP announce and discovery messages> > should not be sent
out f0/0> >> > Sol 1> > ************> > access-li 11 deny 224.0.1.39> >
access-li 11 deny 224.0.1.40> > access-li 11 per any> >> > int f0/0> > ip
multicast boundary 11> >> > Sol 2> > ********> > access-li 12 deny 224.0.0.0 0
15.255.255.255> > acess-li 12 per any> >> > int f0/0> > ip multicast boundary
12 filter-autorp> >> > As far as i understand ; In sol2 i dont want any
multicast traffic coming in> > this interface and also i am denying auto-rp
announce and discovery messages> > out this interface.> > Am i right ?> >> >
Sol 3> > *********> >> > access-li 11 deny 224.0.1.39 access-li 11 deny
224.0.1.40> > access-li 11 per any> >> > int f0/0> > ip multicast boundary 11
filter-autorp> >> > I am really confused with this "filter auto-rp " keyword
now> >> >> > Can someone explain the meaning of 3 sols given above> >> > Thnx
in advance> > gaurav madan.> >> >> > Blogs and organic groups at
http://www.ccie.net> >> >
This archive was generated by hypermail 2.1.4 : Sun Mar 01 2009 - 09:44:11 ARST