From: Hobbs (deadheadblues@gmail.com)
Date: Mon Feb 16 2009 - 15:00:06 ARST
ah, I see what you mean...not sure if there is a way...
On Mon, Feb 16, 2009 at 9:55 AM, jay <jaymhanna@gmail.com> wrote:
> Thanks for the reply.
>
>
>
> To do so, would mean one would have to know what is allowed and what is
> denied. Can you still log only after exceeding the rate-limit if your
access
> list is just "permit any log" type of list?
>
>
>
> Even if I had a deny statement, it seems I would log entries that get
> denied regardless of whether they exceeded the rate-limit or nottrue?
>
>
>
> jay
>
>
>
> *From:* Hobbs [mailto:deadheadblues@gmail.com]
> *Sent:* Monday, February 16, 2009 11:48 AM
> *To:* jay
> *Cc:* ccie forum; comserv@groupstudy.com
> *Subject:* Re: Rate Limiting Multicast
>
>
>
> Use the log keyword on the deny statement at the end of your ACL.
>
> On Mon, Feb 16, 2009 at 9:26 AM, jay <jaymhanna@gmail.com> wrote:
>
> Is there a way to limit multicast traffic arriving on interface and log
> when
> it has been exceeded. I know about the "ip multicast rate-limit" interface,
> and I know it takes an access list for source and group which can be given
> the "log" key word. So if one uses the logged access list method, and lets
> suppose we only use a group list which just allow all groups. Wont the
> logging log all multicast traffic and not only that which exceeds the
> rate-limit?
>
> Is there a better way to do this?
>
>
> 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 : Sun Mar 01 2009 - 09:44:11 ARST