Hi Dave, Thanks for the speedy response. It was a great help. This means that it is not possible to restrict particular TRAPS from being send by the agent or received by the server, using snmp views. Plz correct if my understanding is wrong and also let know if there is any other approach to achieve this trap restriction.
Mayank -----Original Message----- From: dave.shi...@googlemail.com [mailto:dave.shi...@googlemail.com] On Behalf Of Dave Shield Sent: Wednesday, February 17, 2010 6:22 PM To: Mayank Mittal Cc: srikapilan.gan...@wipro.com; net-snmp-coders@lists.sourceforge.net; mayank.mitt...@wipro.com Subject: Re: TRAPS sent for excluded MIBS Thanks for that detail - it makes things much clearer. One comment about the access control settings: group network-operator usm user1 rouser user1 I strongly suggest that you use *either* the com2sec/group/access approach, *or* the r[ow]{user,community} approach. But do not try to mix the two. Particularly not for the same user (or community) name. This will just lead to confusion. On 17 February 2010 12:09, Mayank Mittal <maymi...@cisco.com> wrote: > Where does net-snmp check the notify view before sending a > trap to verify whether or not a particular trap is included or excluded It doesn't. The notify view has never been implemented. (Either for the notification payload, or for the trap OID itself) Patches to rectify this situation would be most welcome. Dave ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
