This is a discussion on Re: Who should send traps ? within the SNMP Users forums, part of the Networking and Network Related category; On 25/02/07, josu@free.fr <josu@free.fr> wrote: > The DisMan Event MIB seems also ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
On 25/02/07, josu@free.fr <josu@free.fr> wrote:
> The DisMan Event MIB seems also to be a possibility but I am a bit afraid > of performance issues as I have seen in a MAN page that the default value for > active monitoring is 10 minutes and the system must be much more reactive. The *default* monitoring period is 10 minutes, but it would be perfectly acceptable (even normal) for you to configure a monitor entry with a more frequent polling frequency. However: > This application must store detected events in the local MIB and inform another > supervision system by sending an acknowledged TRAP (an inform if I am right). since your application is already detecting the events in question, it would make more sense for this application to report them immediately. I'd suggest having your application generate the notification itself. > - The FAQ mention that the agent can exchange over UDP ot TCP but I was > not able to find any information about configuration or feedback. You specify the trap destination by giving the name of the host, including an (optional) transport specifier. The default is UDP, so this is simply the name of the host: trapsink someHost But you can specify a TCP-based destination by including the "tcp:" transport specifier: trapsink tcp:someHost As far as the rest of the code is concerned, there's no difference between the two. They're handled in exactly the same manner. > Instead of using an inform, I may prefer to rely on TCP rather than UDP if > possible. If you wish, though it probably doesn't gain you much. You're also requiring the trap receiver to listen on the TCP port as well (which few systems do by default, and some systems may not support at all). > - Is it possible to configure timeouts and retries for the INFORM ? Yes - in exactly the same way as any other SNMP request. Use the 'retries' and 'timeout' parameters of the session structure. Dave ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?p...rge&CID=DEVDEV _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/...net-snmp-users |