monitor and notificationEvent

"H. McManus" <[email protected]>
Newsgroups gmane.network.net-snmp.user
Organization Genexis BV
Message-ID <[email protected]>
Hi,

I've got a couple of questions regarding the use of the monitor and 
notificationEvent directives in snmpd.conf.

Take the following (hypothetical) situation. There is a proc directive to 
monitor several processes. The goal is to send a trap when an error flag is 
set in the prTable. The trap is to contain the index and the error message.

First off, should the extra objects index and prErrMessage be listed with the 
"monitor" or the "notificationEvent" lines? Does it matter? 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.

Second, if I include the extra objects in the notificationEvent line, what is 
the exact syntax for doing so? The man page says the syntax is 
`notificationEvent "name" NOTIFICATION-TYPE -o oid -o another_oid`, however 
in the examples given in man snmpd.examples, there is no -o used, it just 
lists the extra objects to include. Which is the correct syntax?

Lastly, with the notificationEvent line, does it matter terribly much which 
NOTIFICATION-TYPE you include? The linkUp, coldStart etc ones are not very 
appropriate, is it ok just to use something generic like mteTriggerFired?

Many many thanks in advance.

Helen.


-------------------------------------------------------
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.