2008/6/3 jyothi tallapaneni <[EMAIL PROTECTED]>: > when we create mib using mib editor it creates index > field as not accessible.
That is correct. See RFC 2578, section 7.7: Objects which are both specified in the INDEX clause of a conceptual row and also columnar objects of the same conceptual row are termed auxiliary objects. The MAX-ACCESS clause for auxiliary objects is "not-accessible" > Can' t we give the access type read-only of the index field There are only two situations where you can define the index object as "read-only" or above. One is if you are converting an old MIB module, originally written using SMIv1. The other is if you have a table where *all* of the column objects are also indexes to the table. In that case, you must declare one of them to be accessible. But as long as there is at least one accessible column object, then there is no need to make the index objects accessible. The values of those objects are automatically included as part of the OID of the accessible column(s). Dave ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ 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
