
Hi,
I have some notes regarding the operation of smilint 0.3.0 (under NT/cygwin 1.3.9 environment), used as d:\cygwin\usr\local\bin\smilint -s -i import-unused -l 6 mibfile:
1. smilint seems to require SYNTAX clause before an enumerated DEFVAL clause in an AC VARIATION clause, otherwise: 'D:\DATA\SNMPmibs\CDXC1616-AC.MIB:423: [2] default value syntax does not match object syntax' is output. Although once it's used, further SYNTAX statements for further VARIATION clauses of the same type are not required within the same SUPPORTS clause. But another SUPPORTS clause needs to repeat the SYNTAX statement.
2. Within an AGENT-CAPABILITIES macro, if an object within a group which is not within an INCLUDES clause, but is mentioned in a subsequent VARIATION clause, should a warning or error of some sort be generated?
3. Smilint never seems to mind if hyphens are left in object or TC names, even when it knows the mib must be SMIv2.
Example for 1: IMPORTS : : : : augBidirectional, sdhNE, opticalSPITTPBidirectional, rsTTPTrailTraceBidirectional, msTTPBidirectional, au4CTPBidirectionalR1, vc4TTPBidirectionalR1 FROM WD-G774-MIB; : : : : SUPPORTS WD-G774-MIB INCLUDES { sdhNE, opticalSPITTPBidirectional, rsTTPTrailTraceBidirectional, msTTPBidirectional, au4CTPBidirectionalR1, vc4TTPBidirectionalR1 } : : : : VARIATION g774SdhNEAdministrativeState SYNTAX AdministrativeState -- <===== Need this line ACCESS read-only DEFVAL { unlocked } -- <===== Else this is rejected DESCRIPTION "It will not be possible to set this attribute value from the management station. It will indicate unlocked, or possibly shutting down." VARIATION g774OSPITTPBiAdministrativeState ACCESS read-only -- <===== SYNTAX now not needed DEFVAL { unlocked } DESCRIPTION "It will not be possible to set this attribute value from the management station. It will indicate unlocked, or possibly shutting down." : : : :
Example for 2: IMPORTS : : : : augBidirectional, sdhNE, opticalSPITTPBidirectional, rsTTPTrailTraceBidirectional, msTTPBidirectional, au4CTPBidirectionalR1, vc4TTPBidirectionalR1 FROM WD-G774-MIB; : : : : SUPPORTS WD-G774-MIB INCLUDES { sdhNE, opticalSPITTPBidirectional, rsTTPTrailTraceBidirectional, msTTPBidirectional, au4CTPBidirectionalR1, vc4TTPBidirectionalR1 } : : : : VARIATION augBidirectional -- <===== GROUP not part of INCLUDES DESCRIPTION "Not supported at present, all msTTPBidirectional and protectedTTPBidirectional objects will 'contain' au4CTPBidirectionalR1 objects directly as there is a 1:1 containment relationship between AUG and MS TTP for ETSI systems" VARIATION g774AugBiAugId -- <===== object not part of INCLUDES DESCRIPTION "Not supported at present, all msTTPBidirectional and protectedTTPBidirectional objects will 'contain' au4CTPBidirectionalR1 objects directly as there is a 1:1 containment relationship between AUG and MS TTP for ETSI systems" : : : :
Any comments would be appreciated - Thanks for a great set of tools!
Regards,
Tim Riches Principal Design Engineer
-------------------------------------------------------------- Westbridge Design Ltd Hurst Barns, Hurst Lane Privett, Alton Hants, GU34 3PL UK
e-mail: tim.riches@westbridge-design.co.uk Tel: +44 (0)1730 828111 Fax: +44 (0)1730 828123

Tim Riches writes:
Tim> I have some notes regarding the operation of smilint 0.3.0 (under Tim> NT/cygwin 1.3.9 environment), used as Tim> d:\cygwin\usr\local\bin\smilint -s -i import-unused -l 6 mibfile:
Tim> 1. smilint seems to require SYNTAX clause before an enumerated Tim> DEFVAL clause in an AC VARIATION clause, otherwise: Tim> 'D:\DATA\SNMPmibs\CDXC1616-AC.MIB:423: [2] default value syntax Tim> does not match object syntax' is output. Although once it's Tim> used, further SYNTAX statements for further VARIATION clauses of Tim> the same type are not required within the same SUPPORTS clause. Tim> But another SUPPORTS clause needs to repeat the SYNTAX statement.
Tim> 2. Within an AGENT-CAPABILITIES macro, if an object within a Tim> group which is not within an INCLUDES clause, but is mentioned in Tim> a subsequent VARIATION clause, should a warning or error of some Tim> sort be generated?
There is right now very little support for checking agent capability clauses. This is an area where people who actually use agent capability clauses are more than welcome to contribute patches...
Tim> 3. Smilint never seems to mind if hyphens are left in object or Tim> TC names, even when it knows the mib must be SMIv2.
Running 'smilint -l 6 IP-FORWARD-MIB' generates among other things:
IP-FORWARD-MIB:649: warning: named number `is-is' must not include a hyphen in SMIv2
If you think you have found a bug, please send small MIB fragments. It would be even more helpful if you write them as test modules (see test/mibs/LIBS-TEST-xxx-MIB for examples) so that we can include them in the regression test suite to ensure that fixed bugs will never show up again.
/js
participants (2)
-
Juergen Schoenwaelder
-
Tim Riches