On 29/05/07, ALBERT BEZZINA <[EMAIL PROTECTED]> wrote:
> I am assume that when you have this kind of tables one should use the
> AUGMENTS clause. Am I write?
Yes.
> Furthermore, can a table have both an AUGMENTS and INDEX clauses?
No.
One or the other, not both.
> For example, I would like to define a table - a general one, than a
> sub-table/s.....
> I would like the sub-tables to have other variables as INDEXs which are not
> all common to all tables.
For each of the subtables, you'd have an INDEX clause which lists all
of the index objects for that table. See hrPartitionTable for an example.
> hlSearchLastEntry OBJECT-TYPE
> SYNTAX HlSearchLastTable
> MAX-ACCESS not-accessible
> STATUS current
> DESCRIPTION
> "A conceptual row within the 'hlSearchLastTable'."
> INDEX / AUGMENTS { hlToken, hlNumOfMsgs } OR
INDEX { hlToken, hlNumOfMsgs }
> ::= { hlSearchLastTable 1 }
One final comment:
> AUGMENTS {hlToken} ....
You don't AUGMENT an index, you AUGMENT a table.
AUGMENTS { hlConfigTable }
but only if the index objects are *exactly* the same.
Dave
-------------------------------------------------------------------------
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-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
