[prev in list] [next in list] [prev in thread] [next in thread] 

List:       net-snmp-support
Subject:    [ net-snmp-Support Requests-413493 ] extend the agent to support new traps?
From:       noreply () sourceforge ! net
Date:       2001-04-05 10:03:19
[Download RAW message or body]

Support Requests item #413493, was updated on 2001-04-03 11:32
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=212694&aid=413493&group_id=12694

Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: extend the agent to support new traps?

Initial Comment:
Hi,

From the net-snmp package, it only supports traps 
which are sent out by the agent. To extend the agent 
to support traps which sent out by other application. 
Is it true that the best way is to have the agent fork
() a trap daemon to wait for traps. Then have the trap 
daemon calls the correct trap APIs(provided by the net-
snmp package)to send out the traps.  So there are two 
daemons(agent and trap) are runing when snmpd is 
executed.

BTW, I am running on LINUX OS.

Thanks.

----------------------------------------------------------------------

>Comment By: Dave Shield (dts12)
Date: 2001-04-05 03:03

Message:
Logged In: YES 
user_id=88893

It is not true that "the net-snmp package .. only supports
traps ... sent out by the agent".

There are *two* "notification originator" applications
in the suite.  The agent is one of them, and 'snmptrap'
(aka 'snmpinform') is the other.

If you want a third application to generate traps, it
can do this either by registering as a subagent of the
main SNMP daemon, by invoking 'snmptrap' to generate the
trap, or by implementing this capability internally
within the application (using the snmptrap.c code as a
guideline).

There is no good reason to have the agent fork off a
notification handler (i.e. snmptrapd).  These are two
totally difference styles of application.
  The external application would need to do the same sort
of processing to communicate with this 'intermediate'
trap handler, so it might as well send out the traps
itself.

Dave

----------------------------------------------------------------------

Comment By: Niels Baggesen (nba)
Date: 2001-04-03 15:49

Message:
Logged In: YES 
user_id=88647

Why do you want the traps to go through snmpd?

If that is really what you want, the best way would be to
modify snmptrap to connect to snmpd using AgentX protocol.

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=212694&aid=413493&group_id=12694

_______________________________________________
Net-snmp-support mailing list
Net-snmp-support@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/net-snmp-support

[prev in list] [next in list] [prev in thread] [next in thread]