Hi!
Pat> We've written a tiny MIB module to describe a single trap we send from Pat> one of our applications. Apart from the trap itself, the only objects Pat> in the module were there to provide variables carried in the trap Pat> notification.
Pat> To avoid adding "unnecessary" object types, I hung all the variables Pat> off the trap e.g.:
Pat> eltrap TRAP-TYPE Pat> ENTERPRISE trapObjs Pat> VARIABLES {v1, v2 } Pat> DESCRIPTION Pat> "blah blah" Pat> ::= 1
Pat> v1 OBJECT-TYPE Pat> SYNTAX DisplayString Pat> ... Pat> ::= { eltrap 1 }
Pat> Before sending this to a customer, we ran it through smilint. There Pat> were no errors or warnings reported. The customer's MIB compiler (from Pat> SNMP Research) objected as the parent node of v1 was a TRAP-TYPE Pat> instead of an OBJECT-TYPE.
Pat> Having the opportunity (:-)) to reconsider what I'd done, I see the Pat> error of my ways. However, was it an error? If so, is it a bug in Pat> smilint/libsmi that the error wasn't reported?
Pat> The version is libsmi 0.3.0 on Linux.
Yes. This should be reported as an error by smilint. I'll take a closer look and hope to get parent node checks added in the next libsmi release. Thanks for pointing this out.
-frank