[ Sorry for the delay in responding to this ]

> is it possible to several agentX register the same MIB in one master
> agent? How can I do that?

What exactly do you mean by that?

Do you mean different subagents registering different subtrees
that happen to be defined within the same MIB?
That's no problem - the agent doesn't care about how objects
are distributed between MIB files.  It just works with the global
OID tree, and you can register different subtrees in different
subagents with no problem at all.

Or do you mean different rows within a single table being handled
by different subagents?   That's certainly possible within the AgentX
protocol - using the idea of "ranges" in the registration request.
The Net-SNMP agent does support this, but it probably hasn't be used
very much, so there may be some bugs waiting to be shaken out.

Or do you mean different subagents registering *exactly* the same
MIB objects - with only one actually being active?  
That's possible using the idea of a registration "priority".
Again - the Net-SNMP agent should support this, though it won't
have received much use in practise.

Or do you mean different subagents registering exactly the same
MIB objects - with *all* of them being accessible?  
That could be done using AgentX "contexts".
  The latest Net-SNMP code does now support this (though earlier
releases didn't).


It's a bit difficult to offer more definite advise without a
better idea of exactly what you're trying to do.


Dave




-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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

Reply via email to