My biggest concern is whether I need to use an internal SNMP row index from
Table1 to somehow populate stuff in Table2 within NetSNMP or whether I can
simply start populating rows for Table2 with new row index values which have no
relationship to Table1 at all.
Somehow I keep thinking there is this relationship between Table1 and Table2
which needs to be maintained, although I can not figure out if this is true or
not. If it turns out to be true and I "do" need to maintain the relationship
when populating Table2 data then I have no idea how this needs to be done and
this is bothering me.
If there is no need to maintain a relationship between Table1 and Table2 since
the relationship is maintained automatically due to how the MIB file is
defined, then maybe I do not have any worries. I can simply populate Table2
without caring how Table1 has been populated ...... can you confirm this for me?
I am brand new to SNMP and thus have no idea how SNMP data is interpreted once
it has been received in the "real world". In my case, I would assume an SNMP
operator would request all AVInterfaces (Table1 data) to be displayed. Now the
SNMP operator can look through the list of interfaces to find the "1394"
interfaces which exist. Finally, the SNMP operator would request "1394"
specific information from Table2 (ie: the 1394 data table) to be displayed.
Does this seem correct?
Now, lets say there are five "AVInterfaces" which are displayed from making the
first SNMP request on Table1:
Index AVInterface
1 DVI
2 1394
3 HDMI
4 1394
5 DVI
Based on the aboev display of data, the SNMP operator would know that two 1394
interfaces exist which means that the 1394 Table (ie: Table2) will have two
entries.
If the SNMP operator wanted to request specific data relating to the 1394
AVInterface from "row 4" above, then how would the SNMP operator request the
data from Table2?
Can the SNMP operator request "Table2" 1394 data by somehow indicating "4" as
an index?
You mentioned I should not consider Table2 to be a separate table, but instead
consider Table2 to be an extension of Table1 only. This is confusing me as to
how an SNMP operator can request a certain row from within Table2. Basically,
the operator knows there are going to be two row entries in Table2, but I have
no idea how the SNMP operator would be smart enough to figure out which of
these two entries in Table2 is the one related to "Table 1, row 4".
Dave Shield <[EMAIL PROTECTED]> wrote: On 30/05/07, Need Help wrote:
> Perhaps I simply do not understand what SNMP should do
> regarding my two Tables.
It's quite reasonable to treat these tables as completely independent.
As long as you populate them with the correct information, the link
between the tables will be made automatically (since the underlying
data is linked).
Dave
---------------------------------
Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV. -------------------------------------------------------------------------
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
