Thanks, that clears it up. I can use the Entry node to verify the read-create access.
-----Original Message----- From: Juergen Schoenwaelder [mailto:j.schoenwaelder@iu-bremen.de] Sent: Monday, March 06, 2006 2:14 PM To: John Wiebe Cc: libsmi@ibr.cs.tu-bs.de Subject: Re: [libsmi] smiquery not showing correct MAX-ACCESS.
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