smiquery not showing correct MAX-ACCESS.

I've been using smiquery to get various information from MIB's. However, I've found that it isn't reporting the correct MAX-ACCESS if the MAX-ACCESS is read-create, it always returns read-write.
I noticed in the changelog that this was fixed once before and I'm courious if I am missing something obvious when I try to get this value. In the example below, I am using the default mibs shipped with libsmi. I am using libsmi-0.4.3 on a linux machine. Any help or work around would be appreciated.
Thanks,
libsmi-0.4.3 ChangLog:
2000-02-07 Frank Strauss strauss@ibr.cs.tu-bs.de
* tools/dump-mosy.c: fixed determination of types of %tc's and objects; added special type `ObjectID'. Added distinction of read-write/read-create. Checked output against mosy output for some standard modules (IF-MIB, RMON2-MIB, ...).
from the IF-MIB MAX-ACCESS ifStackStatus
ifStackStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION ...
smiquery -p IF-MIB node ifStackStatus
MibNode: IF-MIB::ifStackStatus OID: 1.3.6.1.2.1.31.1.2.1.3 ParentNode: IF-MIB::ifStackEntry Type: SNMPv2-TC::RowStatus Declaration: OBJECT-TYPE NodeKind: column Access: read-write Status: current Description: The status of the relationship between two sub-layers.
Changing the value of this object from 'active' to 'notInService' or 'destroy' will likely have consequences up and down the interface stack. Thus, write access to this object is likely to be inappropriate for some types of interfaces, and many implementations will choose not to support write-access for any type of interface.

On Mon, Mar 06, 2006 at 01:56:18PM -0500, John Wiebe wrote:
I've been using smiquery to get various information from MIB's. However, I've found that it isn't reporting the correct MAX-ACCESS if the MAX-ACCESS is read-create, it always returns read-write.
Libsmi has internally a different understanding of access levels than the SMIv2. If you have an SMIv2 table which supports row creation, you have to mark all writable columns read-create. Libsmi instead marks them as read-write and sets a creatable flag on the table's entry node. See for example
smiquery node SNMP-VIEW-BASED-ACM-MIB::vacmAccessEntry
and check the "Creatable:" line. Since smiquery reports the internal representation (very useful for debugging), this is just consistent.
/js
participants (2)
-
John Wiebe
-
Juergen Schoenwaelder