Re: How to send the traps in different way.

    [ First - *please* don't mail me privately, without copying
     any responses to the mailing list.  I don't have the time
     or inclination to offer private, unpaid, SNMP consultancy.
     Keep discussions to the list, where others can both learn
     and offer advice.  Thanks.   ]

On 10 March 2010 11:41, Alexander King <[email protected]> wrote:
>>Monitoring values using the DisMan Event MIB will generate the same basic
>> trap (mteTriggerFired) containing a standard set of values.
>
> Do I just do that like the example given,or I need do something like
> after-generate-code work?I thank I need get the generate code,mapping the
> data,and config the snmptrapd.conf like the example given ,and it is the all
> work, is it right?


The point about using the DisMan Event MIB is that you don't need
to write *any* code.    This support is already present in the agent.

Just configure the appropriate "monitor" lines in the snmpd.conf file,
together with an SNMPv3 user to do the internal queries, and a
suitable "trapsink" (or equivalent).    The agent will then monitor
the target OID(s), and send traps when appropriate.
   You do not need to write any code whatsoever.


> I meaning,I neednot do the other work in my code if I want to just send the
> trap like you teach me.Have something I ignored?(have some sourcecodes
> as a example?)

You don't need any source code of your own.


>>The trap can also include additional varbinds, such as uitUPSNames.{N}
>>and uitUPSErrMessage.{N} shown above.
>
> It is looks like something below:
>
> uitUPSErrorTrap              NOTIFICATION-TYPE
>  OBJECTS                         {uitUPSErrorStatus,
> uitUPSErrMessage,uitUPSName}
> -- is it the meaning the OBJECTS can  include many MIB data identifiers?--
>  STATUS                          current
>  DESCRIPTION
>   "Critical UPS have failed and the system is shutting down."
>  ::= { uitTrap 0 131 }
>
> is it necessary has something relation between trap name and the ONJECTS
> include MIB data identifiers?Such as uitUPSErrorTrap and uitUPSErrorStatus,
> uitUPSErrMessage,uitUPSName.


By default, the "monitor" line will generate a "mteTriggerFired" trap.
You can specify an alternative notification using "notificationEvant"
and the '-e' flag for "monitor".
    See the snmpd.conf(5) man page for details.


But I'd suggest you get things working with the default mteTriggerFired
trap first.


Dave

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
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