RE: help needed with root oid and getnext operation

"Mike Ayers" <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <83E753BE7B6A324ABB336245BAF1DAAC0ADABF93@mailserver.metatv-ds.metatv.com>
> From: EYRE Bernadette [mailto:[email protected]] 
> Sent: Monday, February 23, 2009 6:25 PM

> 1 - what am I expected to return for GETNEXT call? Do I 
> return the index of the next valid object instance
>   or the actual value of the first valid object instance?

	Always return the next instance after, but not including, the queried value, or the end of view indicator (null?).

> 2 - if I'm expected to return a value as a reply to GETNEXT 
> call, why then my subagent is called again with GET mode?

	I can't say for sure, but there's nothing inherently wrong with this.  GET and GETNEXT should not cause any changes to the system state for this reason.

> 3 - if I'm expected to return only the index (modified oid?) 
> of the next valid instance, do I modify the
>  name field of the netsnmp_variable_list struct?

	I don't know - a little help from the list, please?

> 4 - when snmpget command is called on one of the columns of a 
> table do I return all the instances of that column?

	No.  Only return the exact instance asked for, and only if it exists.


	HTH,

Mike

------------------------------------------------------------------------------
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.