RE: To get a row/column objects

> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Dave Shield
> Sent: Tuesday, July 29, 2008 11:49 PM

> Unfortunately, the ifTable is a hold-over from the very beginning of
> SNMP, when men were men, women were women, and MIB table
> design was not particularly well understood.

	...and the sheep were relieved!

> So:
> >        To sum it all up the first returnable object is 
> ifTable.ifEntry.ifDescr, or ifTable.1.2 .
> >  If you get next on ifTable, the correct response is 
> ifTable.1.2.(first index).
> >  If you get next on ifIndex.1, or ifTable.1.1, the correct 
> response is ifTable.1.2.(first index).
> 
> *ought* to be true, but isn't.
> The first returnable object is actually 
> ifTable.ifEntry.ifIndex  (ifTable.1.1)
> and these GETNEXTs would actually return ifTable.1.1.(first index)

	Thanks for the clarification.  So if the OP performed the second get-next on ifTable.1.1 instead of ifTable.1, the intended result would have been achieved, but, again, it is often better to use snmpgetnext or one of the helper functions like snmptable or snmpwalk than to try to anticipate the next value.


	HTH,

Mike

P.S.  Naughty crossposting OP!  Now both Dave and I have fallen prey to your evil schemes!  I shall have my revengessss.... SHIIIIIIRE.....  BAGGGINNNSSSSSSSSSSS.....

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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