2008/6/27 Tewen Hsieh <[EMAIL PROTECTED]>:
> ex: when agent receive a request with oid: 1.3.6.1.4.1.7788.100.1.idx,
> it can use idx to find the correct row and get data.
That OID cannot be a valid instance of a MIB table.
It would need to be of the form 1.3.6.1.4.1.7788.100.1.column.idx
(assuming that 1.3.6.1.4.1.7788.100 is the OID of the table itself).
> But if my table is indexed by multiple indexes (ex: ip and vlan), how can
> agent mapping 1.3.6.1.4.1.7788.100.1.idx to the correct row?
It cannot,
Even with the missing column subidentifier added,
this OID does not map to an instance of a multi-indexed table.
The agent would need an OID of the form
1.3.6.1.4.1.7788.100.1.column.idx1.idx2
That's what multiple indexes means - the OIDs must
include multiple index values.
Dave
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
