Libsmi December 2001

libsmi@ibr.cs.tu-bs.de

13 participants
10 discussions

read-create access
by Deshmukh, Abhay 26 Dec '01

26 Dec '01

Hi, I find that : for table columnar objects having read-create access, smilib returns SmiNode structure having the following two members as access=SMI_ACCESS_READ_WRITE create=0 where as I expected create=1 Due to this we incorrectly get the access as ReadWrite instead of ReadCreate for some objects having ReadCreate access. Can anybody explain the reason ? However, for table-entry object ( which is generally not-accessible, If I mention access as read-create, smilib returns expected correct values of ReadCreate) kr, abhay -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de>. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

2 1

vc++
by K.C. Norseth 25 Dec '01

25 Dec '01

I am trying to get everything to compile using Visual C++. Has anyone been successful and can you tell me what you had to do? K.C.

3 2

DTD for xml
by Deshmukh, Abhay 24 Dec '01

24 Dec '01

Hi, Where can I get the DTD corresponding to the XML output produced by 'smidump -f xml' ? Regards, Abhay -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de>. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

2 1

Error check not provided in libsmi.....
by Vivekanandan V 14 Dec '01

14 Dec '01

Hello, If a table element is declared as a particular type in the Entry and later declared as a different type in its declaration part, it is not given as an error by the libsmi tool. For example, PppGzipStatusEntry ::= SEQUENCE { pppGzipStatusIfIndex INTEGER, pppGzipStatusRxIfWindowSize INTEGER, pppGzipStatusTxIfDecompressedDataSize Counter32 } pppGzipStatusTxIfDecompressedDataSize OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "" ::= { pppGzipStatusEntry 3 } Here "pppGzipStatusTxIfDecompressedDataSize" is declared as Counter32 type in 'PppGzipStatusEntry' but later declared as INTEGER in its definition part. This should be given as an error. But libsmi tool doesn't check for these mistakes!!!!! Kind Regards, Vivekanandan.V -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de>. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

2 1

Table Index
by Sanjay M 11 Dec '01

11 Dec '01

Hi all, How I can able to get the table index details from the MIB file?, because some table contains more than one index. I want the information of all the index including the oid and name of the index. Expecting an early replay --Thanks in advance Sanjay __________________________________________________ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de>. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

2 1

Re: [libsmi] Clarification req on Rfc:1905.......
by Dave Shield 07 Dec '01

07 Dec '01

> Then what is the difference between 'inconsistentname' > and 'inconsistentvalue'??? Errr... OK - the printer example should indeed probably return 'inconsistentValue'. My mistake. Sorry. But I believe that the 'thisMonthsSales' example still holds good. Dave P.S: This doesn't really feel like a question related to the 'libsmi' package - which is the purpose of this particular mailing list. Can I suggest this discussion be taken elsewhere before Frank et al start muttering at us in incomprehensible German.... :-) -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de>. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

1 0

Re: [libsmi] Clarification req on Rfc:1905.......
by Dave Shield 07 Dec '01

07 Dec '01

> Rfc:1905 (Protocol Operations of v2 SNMP) states that the following : > > (7) If the variable binding's name specifies a variable which does not exist > and could not ever be created ...... `noCreation' > > (8) Otherwise, if the variable binding's name specifies a variable which does > not exist but can not be created under the present circumstances (even > though it could be created under other circumstances)... `inconsistentName > I cannot get the exact difference between 1 & 2. [I've renumbered these as (7) and (8) to match RFC 1905: 4.2.5] Consider the following scenario: SET sysLocation.1="behind you" sysLocation.1 does not exist, and cannot ever be created - it's a scalar object (not part of a table), so the only valid subindex is 0. But sysLocation.0 *does* exist, so there is "some [variable] sharing the same OBJECT IDENTIFIER prefix [which] might under some circumstances be able to be created" (or at least modified, which is sufficient to pass 4.2.5 step (2)) Hence I'd expect this to return "noCreation". Alternatively, consider a table, indexed by days of the week (perhaps an enumeration 1..7). Then you might get SET wasIAtWork.sunday(1) = no(1) SET wasIAtWork.monday(2) = yes(2) : SET wasIAtWork.friday(6) = inBodyOnly(3) => wrongValue SET wasIAtWork.saturday(7) = no(1) SET wasIAtWork.8 = no(1) => noCreation As far as "inconsistent name" is concerned, consider a similar table, indexed by days of the month, i.e. in the range 1..31. But not all these are necessarily valid for any given month (esp 31, and in February) So this month I could run SET thisMonthsSales.29 = 100000 SET thisMonthsSales.30 = 200000 SET thisMonthsSales.31 = 300000 quite happily. But trying the same thing during November - there is no November 31st, so the variable "thisMonthsSales.31" won't exist, and can't be created. (At least not given a good implementation!) But in different circumstances (e.g. December) the same variable *could* be created. Hence I'd expect this request to return "inconsistentName" during November. A more realistic example might be: SET printerOverallStatus.0 = down => OK SET printerQueue.queueStatus.1 = enabled => inconsistentName SET printerOverallStatus.0 = up => OK SET printerQueue.queueStatus.1 = enabled => OK i.e. I can only enable a particular queue when the printer system as a whole is up. If the whole of the printer system is down, then I can't enable individual bits of it. So whether a particular request works will depend on "other circumstances". Does that help any? Dave -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de>. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

2 1

Clarification req on Rfc:1905.......
by Vivekanandan V 07 Dec '01

07 Dec '01

Hi, Rfc:1905 (Protocol Operations of v2 SNMP) states that the following : 1. If the variable binding's name specifies a variable which does not exist and could not ever be created (even though some variables sharing the same OBJECT IDENTIFIER prefix might under some circumstances be able to be created), then the value of the Response-PDU's error-status field is set to `noCreation', and the value of its error-index field is set to the index of the failed variable binding. 2.Otherwise, if the variable binding's name specifies a variable which does not exist but can not be created under the present circumstances (even though it could be created under other circumstances), then the value of the Response-PDU's error-status field is set to `inconsistentName', and the value of its error- index field is set to the index of the failed variable binding. I cannot get the exact difference between 1 & 2. Can any one clearly tell me when the error status 'inconsisent name' and 'noCreation' wil be returned??? Thanks, Regards, Vivekanandan.V -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de>. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

1 0

How to get the table information
by Ashok Kumar [ GVG DDF ] 05 Dec '01

05 Dec '01

Hi I am able to get all internal data structures using compiler api is working fine. Thanks for excellent work. > Now to the question: How I can get the table information form the MIB > file, > that is I want table name, table oid, column count, column names and index > details. > In this mail I attached small portion of MIB > > -- Relay Table definition starts here > > relayTable OBJECT-TYPE > SYNTAX SEQUENCE OF RelayEntry > ACCESS not-accessible > STATUS current > DESCRIPTION "A table containing Relay-specific information" > ::= { attributes 1} > > relayEntry OBJECT-TYPE > SYNTAX RelayEntry > ACCESS not-accessible > STATUS current > DESCRIPTION "Information about a particular Relay" > INDEX {relayNumber} > ::= { relayTable 1} > > RelayEntry ::= SEQUENCE{ relayNumber Integer32, > relayStatus INTEGER, > relayType INTEGER} > > relayNumber OBJECT-TYPE > SYNTAX Integer32 > MAX-ACCESS read-only > STATUS current > DESCRIPTION "This attribute gives the Relay number " > ::= { relayEntry 1} > > relayStatus OBJECT-TYPE > SYNTAX INTEGER { open(1), close(2) } > MAX-ACCESS read-only > STATUS current > DESCRIPTION "This attribute gives the status of the > Relay that is either open or close" > ::= { relayEntry 2} > > relayType OBJECT-TYPE > SYNTAX INTEGER { in(1), out(2) } > MAX-ACCESS read-only > STATUS current > DESCRIPTION "This attribute gives the Type of the > Relay that is In or Out" > ::= { relayEntry 3} > > -- Table definition ends here > > Thanks and regards > ashok

2 1

Clarification in smilint.......
by Vivekanandan V 04 Dec '01

04 Dec '01

Hello, When Iam compiling Ip-forward.mib (Rfc:2096), using smilint 0.2.6, I get the following error message: --> index element 'ipCidrRouteTos' of row 'ipCidrRouteEntry' must have a range restriction. Whether it is mandatory to impose a range restriction on all index elements of a table ??? If so, can you please let me know where this has been mentioned in any Rfc. Thanking you in advance, Regards, Vivekanandan.V P.S: zip file of ip-forward.mib attached with this mail.

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

Libsmi December 2001