Dave,

your considerations were correct and they should solve my problem.

Thanks for the puntual answer.

gn

PS: Below follows my replies...

Dave Shield wrote:
To be clear, the implementation of the Event-MIB ....
[...]
The Event-MIB creates a 'callback' session looping back to the agent,
which is used for sending internal requests for the MIB values it needs.

I checked again the code of mteTriggerTable.c. Here is the codeline:

        mte_callback_sess = netsnmp_callback_open(callback_master_num,
                                                  NULL, NULL, NULL);

It was not straight for me to undestand that here was the difference.
Thanks!

[...]
These requests do indeed pass through the security stacks, but *don't*
actually involve building the SNMP message, or UDP packet.   The PDU
data structure is passed across directly.
   (At least, that's my reading of the snmplib/snmpCallbackDomain.c code)
I see.

Are you talking about retrieving a particular MIB object value, or a
general-purpose mechanism that can be used with arbitrary OIDs?
Was the general-purpose.

But the approach provided for a general-purpose mechanism is the
"callback request" as used by Event-MIB.    It involves a certain
overhead, but is significantly simpler than trying to mimic the
the necessary PDU handling within the Event-MIB handler itself.
Definetevly. I consider this method as the "internal function call" I was looking for.


Dave




------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ Net-snmp-coders mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to