RE: snmp.conf syntax

> The DisMan monitoring simply says "send a notification".
> It doesn't control where those notifications are sent, or what version
> they should be.
> That's the role of "trapsink" and similar.
> 
> If you configure the agent with "trapsink", then it will send v1 traps.
> If you configure the agent with "trap2sink", then it will send v2c traps.
> If you configure the agent with "informsink", then it will send v2c informs.

I read this in man pages:
notificationEvent ENAME NOTIFICATION [-n] [-i OID | -o OID ]* 
defines a notification event named ENAME. This can be triggered from a given monitor entry by specifying the option -e ENAME (see above). NOTIFICATION should be the OID of the NOTIFICATION-TYPE definition for the notification to be generated.

The question was if NOTIFICATION really has to be OID of NOTIFICATION-TYPE or if it is possible to somehow put TRAP-TYPE here (I have to use some SMIv1 mibs)
> 
Michal Filka

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
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