On 25/02/2008, oknets10 <[EMAIL PROTECTED]> wrote:
> I'm trying to run an agentx master & subagent using the original snmpd.
>
> Opening the session has succeeded, but all the registration is failed with
> error 263 (duplicate).
If you're using the same binary for both master and subagent
(and assuming all modules are active), then this is to be expected.
The master agent will register all the internal modules it knows about,
so the subagent doesn't have anything left to do.
Try disabling one of the MIB modules in the master agent(e.g.
"snmpd -I-hr_system") and check that queries to this module fail.
Then start up the subagent, and see whether you can now query
this group.
> I see in the messages that the subagent is sending, that the
> NON_DEFAULT_CONTEXT bit is set, but the length of the context is 0.
> I guess this is because no context is defined in the subagent ?
I'm surprised that the bit is set at all, in fact.
Yes - all MIB modules will be registered in the default context
(which is the same as the null "non-default" context).
> Can I control the context the subagent is sending only by configuration,
> or do I need to write some code ?
You'd need to write (or change) the code.
See the FAQ entry
How can I register a MIB module in a different (SNMPv3) context?
http://www.net-snmp.org/wiki/index.php/FAQ:Coding_22
Dave
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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
