Ok, then this means when a "snmpwalk" command for Table1 occurs then I will be
populating "one row" of data from Table2 everytime, since I have code in the
Table2_row_prep() routine.
I just wanted to make sure it was not a problem. Thanks for clarifying.
Dave Shield <[EMAIL PROTECTED]> wrote: On 12/06/07, Need Help wrote:
> I noticed when I perform a "snmpwalk" of Table1, then all the data is
> displayed correctly and then "one" call is made to Table2_row_prep() with
> row index = 1.
>
> Is this normal?
Yes.
Remember that the walk doesn't know when it's reached the end
of the table. It simply keeps asking for the "next value".
It's only when that next value is no longer relevant to the
requested table, that it knows it can stop.
But it needs to retrieve that final "irrelevant" value before it
can tell this, which means that the agent must supply it.
Assuming the two tables are immediately next to each other,
that means that the agent will start querying the second
table, before the snmpwalk command can stop.
Dave
---------------------------------
Park yourself in front of a world of choices in alternative vehicles.
Visit the Yahoo! Auto Green Center.-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
