From: kevin gannon (kevin@gannons.net)
Date: Fri Mar 06 2009 - 14:42:39 ARST
Jay
Wondering did you get an answer to this in the end. It has me puzzled to.
The only other things I can think of are
1. rmon to monitor an SNMP variable and create a SNMP trap and you
can also catach snmp traps into syslog
2. An EEM script that monitor ths SNMP oid and sends a SYSLOG. This
could be a lot more painful than option one but would allow a custom
syslog message
3. Have a CAR rate limit on the incoming interface with an exceed action of
say set-prec-transmit 7
Then on the outgoing interface have any ACL like
access-list 100 deny any 224.0.0.0/42 eq dscp 56 log
access-list 100 permit ip any any
I am not exactly sure what you mean by log is this a specific message
or an log entry
will do ?
Regards
Kevin
On Mon, Feb 16, 2009 at 4:26 PM, 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 : Mon Apr 06 2009 - 06:44:04 ART