Hi,

I'm using smilint for the first time. And getting the following error when I compile one of the MIBs (SMIv1).

[1] {other} parse error, unexpected INTEGER, expecting UPPERCASE_IDENTIFIER or LOWERCASE_IDENTIFIER or NUMBER

The other tools like SMIC, Parse, Mosy etc. never complained about this. Why smilint is not accepting 'INTEGER' as index part (I'm referring to IndexPart in RFC-1212)

The object was defined as follows... memStatTable OBJECT-TYPE SYNTAX SEQUENCE OF MemStatEntry ACCESS not-accessible STATUS mandatory DESCRIPTION " Information about data buffer pools. Instance is pool number. 1 - 7 is D RAM 8 is M RAM 9 - is C RAM 10 - is H RAM" ::= { sysInfo 5 } memStatEntry OBJECT-TYPE SYNTAX MemStatEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A single entry in the Memory stats table" INDEX { INTEGER } ***** Error in this line ***** ::= { memStatTable 1 } MemStatEntry ::= SEQUENCE { accMemBlkEntSize INTEGER, accMemBlkEntTotal INTEGER, accMemBlkEntMax Gauge, accMemBlkEntInUse Gauge, accMemBlkEntFails Counter, accMemBlkEntType INTEGER, accMemBlkEntAllocs Counter, accMemBlkEntInitial INTEGER }

And also getting the following error. I observed that it is only complaining for the objects which are part of the index of a table. [2] {index-element-no-range} index element `oDiffServMeterInterface' of row `oDiffServMeterStatsEntry' must have a range restriction [1] {index-element-no-size} index element `oDiffServMeterIfMeterName' of row `oDiffServMeterStatsEntry' must have a size restriction

My question here is why smilint should complain about range/size restriction when the standard MIBs (ifIndex in RFC1213-MIB) don't specify range of any object (Type INTEGER) which is part of index.

/Amar