Index elements should be not-accessible.....
Hello,
Iam using smilint 0.3.1. For Index elements (of Tables) having a MAX-ACCESS as read-only, an error is given in severity level 5 as, " index element should be not-accessible in SMIv2 MIB" So, does it mean that Index elements cannot be read-only?? If so, can you please let me know whether is it mentioned in any standard Rfc??
Thanks & Regards, Vivekanandan.V *************************************************************************** This message is proprietary to Future Software Limited (FSL) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended.
If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSL accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. ***************************************************************************
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
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/
-- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To unsubscribe or adjust !! your settings, send a mail message to libsmi-request@ibr.cs.tu-bs.de !! or look at https://www.ibr.cs.tu-bs.de/mailman/listinfo/libsmi.
Vivekanandan V writes:
Vivekanandan> Section7.7 of Rfc2578(SNMPv2-SMI), states that the INDEX Vivekanandan> element must be READ-ONLY in the following case:
[...]
Vivekanandan> In my mib, Iam having a table satisfying the above Vivekanandan> condition. But still Iam getting a warning (in Vivekanandan> Level-5)in libsmi, that "index element should be Vivekanandan> not-accessible in SMIv2 MIB".
Vivekanandan> Please let me know whether the problem is with my mib or Vivekanandan> with the tool.
It is a problem with the tool. I actually found it is documented in the source. It is probably time to actually fix it.
/js
Hi!
Vivekanandan> Section7.7 of Rfc2578(SNMPv2-SMI), states that the INDEX Vivekanandan> element must be READ-ONLY in the following case:
Juergen> [...]
Vivekanandan> In my mib, Iam having a table satisfying the above Vivekanandan> condition. But still Iam getting a warning (in Vivekanandan> Level-5)in libsmi, that "index element should be Vivekanandan> not-accessible in SMIv2 MIB".
Vivekanandan> Please let me know whether the problem is with my mib or Vivekanandan> with the tool.
Juergen> It is a problem with the tool. I actually found it is Juergen> documented in the source. It is probably time to actually fix Juergen> it.
Fixed.
-frank
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
David T Perkins writes:
David> Note that it is very unusual to create tables that consist of David> just index columns. Typically one would have at least one David> status or timestamp column in the table.
I generally agree. However, vacmContextEntry in RFC 2575 is an example of such an unusal construction. So these things do exist.
/js
HI,
It looks like we are in agreement. Similarly to the OID values for columns in a table not being sequential, it is both legal to do this as well as having tables consisting of only index columns, but is also a questionable MIB design practice.
The vacm context table would most likely be more useful if there was a status column.
At 07:59 PM 4/3/2002 +0200, Juergen Schoenwaelder wrote:
David T Perkins writes:
David> Note that it is very unusual to create tables that consist of David> just index columns. Typically one would have at least one David> status or timestamp column in the table.
I generally agree. However, vacmContextEntry in RFC 2575 is an example of such an unusal construction. So these things do exist.
/js
-- Juergen Schoenwaelder http://www.informatik.uni-osnabrueck.de/schoenw/
Regards, /david t. perkins
participants (4)
-
David T. Perkins -
Frank Strauss -
Juergen Schoenwaelder -
Vivekanandan V