On Wed, Sep 26, 2012 at 12:05:40PM +0300, Evgheni Antropov wrote:
Hello everybody
I have a couple of issue, according with my own MIB file.
I can divide error on 4 section:
[4] {group-membership} warning: node `Location' must be contained in at least one conformance group
[5] {group-unref} warning: current group `DNSGroup' is not referenced in this module
[2] {parent-scalar} scalar's parent node must be simple node
[5] {row-name-table-name} warning: row identifier `MetersTableEntry' should have the same prefix as table identifier `MetersTable'
I need to know if those warnings/errors are critical and if they can be fixed and how. All errors show on http://www.simpleweb.org/ietf/mibs/validate/ and http://www.ibr.cs.tu-bs.de/bin/smitools.cgi with severity level 3,4,5 and
Here is an excerpt from the smilint manual page:
All generated error and warning messages have an associated severity level. The actual severity levels are:
0 Internal error, no recovery possible. Examples are memory allocation failures. Errors of this level usually cause the application to abort.
1 Major SMI/SPPI error, recovery somehow possible but may lead to severe problems. Examples are lexically unexpected characters or unknown keywords. Errors of this kind usually lead to follow-on errors.
2 SMI/SPPI error which is probably tolerated by some implementations. Examples are MIB/PIB modules which mix constructs from different SMI/SPPI versions.
3 SMI/SPPI error which is likely tolerated by many implementations. Examples are misplaced SMIv2 MODULE-IDENTITY invocations or SMIv2 textual conventions derived from other textual conventions.
4 Something which is not strictly an error but which is recommended to be changed. Warnings of this level are usually considered during MIB reviews.
5 Something that is basically correct but might be problematic in certain environments or usage scenarios. Examples are warnings that identifiers only differ in case or that type definitions are not used within the defining module.
6 Messages of this level are auxiliary notices. Examples are messages that point to a previous definition in case of a redefinition.
Higher levels are currently not used and lead to the same effects as level 6 does. Note that errors up to level 3 are errors violating the specifications and must be fixed by the responsible author. The warnings generated with level 4 should be considered during normal MIB/PIB reviews.
This means only
[2] {parent-scalar} scalar's parent node must be simple node
really needs to be fixed. 1) and 2) relate to conformance definitions, which is important for standardized MIB modules but less so for proprietary MIB modules. 5) is a deviation from common naming conventions, does not really hurt but I personally would probably fix it an rename MetersTableEntry to MetersEntry (but then it must start with a lowercase letter - perhaps you removed some prefix before sending this to the list?).
/js