HI,
Note that it is very unusual to create tables that consist of just index columns. Typically one would have at least one status or timestamp column in the table.
At 08:04 PM 4/3/2002 +0530, Vivekanandan V wrote:
Hello,
Section7.7 of Rfc2578(SNMPv2-SMI), states that the INDEX element must be READ-ONLY in the following case:
"a conceptual row must contain at least one columnar object which is not an auxiliary object. In the event that all of a conceptual row's columnar objects are also specified in its INDEX clause, then one of them must be accessible, i.e., have a MAX-ACCESS clause of "read-only". (Note that this situation does not arise for a conceptual row allowing create access, since such a row will have a status column which will not be an auxiliary object.)
In my mib, Iam having a table satisfying the above condition. But still Iam getting a warning (in Level-5)in libsmi, that "index element should be not-accessible in SMIv2 MIB".
Please let me know whether the problem is with my mib or with the tool.
P.S: I have attached the part of the mib, where Iam getting the warning.
Thanks & Regards, Vivekanandan.V
-----Original Message----- From: libsmi-admin@ibr.cs.tu-bs.de [mailto:libsmi-admin@ibr.cs.tu-bs.de]On Behalf Of Juergen Schoenwaelder Sent: Wednesday,March 20,2002 6:06 PM To: vivekav@future.futsoft.com Cc: libsmi@ibr.cs.tu-bs.de Subject: Re: [libsmi] Index elements should be not-accessible.....
Vivekanandan V writes:
Vivekanandan> Iam using smilint 0.3.1. For Index elements (of Tables) Vivekanandan> having a MAX-ACCESS as read-only, an error is given in Vivekanandan> severity level 5 as, " index element should be Vivekanandan> not-accessible in SMIv2 MIB" So, does it mean that Index Vivekanandan> elements cannot be read-only?? If so, can you please Vivekanandan> let me know whether is it mentioned in any standard Vivekanandan> Rfc??
See RFC 2578 at the end of section 7.7 for the details.
/js
-- Juergen Schoenwaelder http://www.informatik.uni-osnabrueck.de/schoenw/
Regards, /david t. perkins