Re: monitor and notificationEvent

On Mon, 2006-03-13 at 14:59 +0100, H. McManus wrote:
> First off, should the extra objects index and prErrMessage
> be listed with the "monitor" or the "notificationEvent"
> lines? Does it matter?

Probably not.

Logically, it probably makes more sense for them to be listed
with the "monitor" entry, since they are related to the test
that triggers the notification, rather than the trap itself.
For example, you might well wish to have different objects
associated with a "proc" monitor entry, compared to a "disk"
entry.
   If the two entries are basically sending the same notification,
then ideally you'd want to use the same "notificationEvent" for
both - so the differences (i.e. the extra trap payload) would
need to be associated with the monitor rather than the trap.


>                                             I've read the 
> explanation with the strictDisman entry, but I have to be
> honest and say I don't really understand what it's saying.

It's basically discussing the order in which objects are
added to the notification payload list.  Should it be trigger
objects ("monitor -o") first, followed by event objects
("notificationEvent")?   Or should it be event then trigger?

   The specs say one thing - the Right Thing To Do is the
other :-)

> Second, if I include the extra objects in the notificationEvent
> line, what is the exact syntax for doing so?

Go by the man page.
This was updated when the DisMan Event module was re-implemented.
I haven't had the time to rewrite all of the examples as well.
We try to retain backwards compatability, so the older syntax
*should* work as well, but it's safer to follow the man page.


> Lastly, with the notificationEvent line, does it matter terribly
> much which NOTIFICATION-TYPE you include?

Not at all - it all depends on what notification you want to be sent.

>  The linkUp, coldStart etc ones are not very 
> appropriate, is it ok just to use something generic like mteTriggerFired?

That's what will be sent by default.
If you're happy to use the standard DisMan Event MIB traps,
then you don't need to specify an explicit notificationEvent at all.
The system will choose the relevant trap automatically.
   It's only if you want to change this to a different trap
that you need to use the '-e' flag.


Dave


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
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