Re: periodic TRAP watcher!

>       I'm not sure what you mean by this.  An OID is an object identifier, a set of numbers constructed using a certain set of rules, preferably >in conjunction with one of the official registrars to ensure universal uniqueness.

Sorry it was a mistake,  I use mib2c.notify.conf file to generate the
code frame for TRAP generation

>       I have *no* idea what you mean here.  mib2c is a tool used to generate implementation code based upon the MIB definition file.  The >mib2c.scalar.conf file is part of the mib2c source for parts of MIB implementations for some of the MIB implementations shipped with >net-snmp.

>      You can make either a standalone application or a MIB implementation, not both.

I use mib2c.notify.conf to generate source-code framework for TRAPs
associated with scalars in MIB - A trap module(this is what I meant by
stanalone application for dealing with traps - but is actually MIB
implementation).

and mib2c.scalar.conf to generate source-code framework for scalars in
the MIB - which is again a MIB implementation

><SNIP>
>             Typically,  the OID token will be the name (or numeric OID) of a
>             NOTIFICATION-TYPE object, and  the  specified  program  will  be
>             invoked  for notifications that match this OID exactly.  However
>             this token also supports a simple form  of  wildcard  suffixing.
>             By  appending  the  character  notification based within subtree
>             rooted at the specified OID.   For  example,  an  OID  token  of
>             .1.3.6.1.4.1*  would  match any enterprise specific notification
>             (including  the  specified  OID  itself).   An  OID   token   of
>             .1.3.6.1.4.1.*  would would work in much the same way, but would
>             not match this exact OID - just notifications that lay  strictly
>             below  this  root.   Note that this syntax does not support full
>             regular expressions or wildcards - an  OID  token  of  the  form
>             oid.*.subids is not valid.
></SNIP>

>       So you can write a traphandler routine that processes all your enterprise traps and invoke it with snmptrapd.  It will need to check >which specific trap it's been sent each time it's been called.


That was a very useful piece of information

Meanwhile I compiled new Net-SNMP agent with trap-watch-dog, when the
trap watch dog is running I am able make SET and GET requests
parallely(as Dave explained in his previous mail to this thread)

Many thanks for your reply.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users