On 16 July 2010 13:11, <[email protected]> wrote:
> It times out while we are walking through mib file we created for our
> hardware.
Then the problem must lie within the code that you have
written to implement your MIB.
This is the first time that you have mentioned a private MIB.
Up to now, you have been giving the impression that you're
having problems with the standard MIBs.
> Agent should walk all the predefined mibs first then user-defined?
> Is there any order?
Agents do not walk the MIB tree. Applications walk the MIB tree.
An agent will simply return the "next value" after each requested
OID. Try walking the tree using the option '-On' to see how
the OIDs are ordered.
(Or re-read any books you have on SNMP - this is fairly
basic stuff!)
> Or this break is creating the problem?
There is no break.
The various MIB files (and the distinction between standard and
user-defined) is purely an administrative convenience for us humans.
The agent/apps/protocol all work with a combined OID tree containing
"everything they know about"
Dave
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
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
