> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of [EMAIL PROTECTED]
> The agent itself will not be aware of individual OIDs and
> their meaning.
> This will be done by the other process that also holds the
> actual data.
This is a bit of a design problem as stated. The (sub)agent is
responsible for managing its OID range, and therefore it is not possible to
have a subagent completely unaware of the OIDs. This does not, however, mean
that the subagent needs to be aware of the data underlying the MIB.
A common paradigm is to have the subagent register for the range of
values (table, MIB, whatever) that it will manage, and have the OP (other
process) manage the data within the range. The agent does OID
assembly/disassembly (i.e. breaking OIDs into range part and specific part),
possibly reformat the specific part to make it more understandable to the OP
(thus only the subagent need be MIB aware). The OP returns the values for the
requested data, then the subagent formats and assembles the response.
HTH,
Mike
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
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
