2009/2/23 Mike Goins <[email protected]>:
>> There are two basic options here.
>>
>> a) You can design your MIB tables to include an index which
>> specifies which device to query.
>>
>> This has the advantage that you can query several devices in a
>> single request, but does require that you have control over the MIB
>> definitions (and can change them)
>
>
> I know it is dated, but I was about to post the same question when I
> ran across this message looking through the archives. Is there an
> example MIB to show this?
Not really, no.
> Most of the examples are tied to tables
> which is not quite what I need
Most of the modules included with the Net-SNMP agent retrieve
the necessary information from a single source, and then decide
which bit(s) are required for a given request.
The approach outlined above is the reverse of this - you can't
start to retrieve the necessary information until you've looked
at the request and decided which bit of information to retrieve.
The closest framework would probably be the iterator helper.
This steps through the list of what rows are available
(in the get_{first,next} hook routines), and then retrieves the
necessary information for the chosen row in the handler.
That's probably the best starting point.
Dave
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
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
