I am having difficulty getting this MIB module to pass smilint. The issue relates to the use of AUGMENTS. If I do not IMPORT objects from RMON2, then I get severity [1] errors, but if I use IMPORT then I get the following severity [3] errors. Any advise to correct or is this an smilint issue?
I have attached the draft MIB module.
Thanks, Bob Cole
smilint returns:
" rgc@chapman:~/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02$ smilint -m -s -l 6 -i namelength-32 /home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB /home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:523: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryControlObjects' is not defined in this module /home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:524: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryControlBucketsRequested' is not defined in this module /home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:525: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryControlBucketsGranted' is not defined in this module /home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:529: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryControlInterval' is not defined in this module /home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:532: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryControlOwner' is not defined in this module /home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:534: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryControlStatus' is not defined in this module /home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:543: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryObjectVariable' is not defined in this module /home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:547: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryObjectSampleType' is not defined in this module /home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:307: [5] {index-element-accessible} warning: index element `reportSampledReportIndex' of row `reportSampledEntry' should be not-accessible in SMIv2 MIB /home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:459: [5] {notification-not-reversible} warning: notification `reportSampledNewDataReport' is not reverse mappable "
Can't seem to get rid of the level [3] complaints. Basically, i can't seem to use AUGMENTS without IMPORTS objects from RMON3, but then it complains that these are not defined within this module.
I have attached .xml and .txt.
Is 'usrHistoryControlObjects' anywhere in your MIB file?
On Wed, Nov 2, 2011 at 6:16 PM, Robert G Cole rgcole01@comcast.net wrote:
I am having difficulty getting this MIB module to pass smilint. The issue relates to the use of AUGMENTS. If I do not IMPORT objects from RMON2, then I get severity [1] errors, but if I use IMPORT then I get the following severity [3] errors. Any advise to correct or is this an smilint issue?
I have attached the draft MIB module.
Thanks, Bob Cole
smilint returns:
" rgc@chapman:~/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02$ smilint -m -s -l 6 -i namelength-32
/home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB
/home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:523: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryControlObjects' is not defined in this module
/home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:524: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryControlBucketsRequested' is not defined in this module
/home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:525: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryControlBucketsGranted' is not defined in this module
/home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:529: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryControlInterval' is not defined in this module
/home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:532: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryControlOwner' is not defined in this module
/home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:534: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryControlStatus' is not defined in this module
/home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:543: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryObjectVariable' is not defined in this module
/home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:547: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryObjectSampleType' is not defined in this module
/home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:307: [5] {index-element-accessible} warning: index element `reportSampledReportIndex' of row `reportSampledEntry' should be not-accessible in SMIv2 MIB
/home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:459: [5] {notification-not-reversible} warning: notification `reportSampledNewDataReport' is not reverse mappable
"
Can't seem to get rid of the level [3] complaints. Basically, i can't seem to use AUGMENTS without IMPORTS objects from RMON3, but then it complains that these are not defined within this module.
I have attached .xml and .txt.
-- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To unsubscribe or adjust !! your settings, send a mail message to libsmi-request@ibr.cs.tu-bs.de !! or look at https://www.ibr.cs.tu-bs.de/mailman/listinfo/libsmi.
On Wed, Nov 02, 2011 at 07:16:26PM -0400, Robert G Cole wrote:
I am having difficulty getting this MIB module to pass smilint. The issue relates to the use of AUGMENTS. If I do not IMPORT objects from RMON2, then I get severity [1] errors, but if I use IMPORT then I get the following severity [3] errors. Any advise to correct or is this an smilint issue?
Section 3.1 of RFC 2580 says:
The OBJECTS clause, which must be present, is used to specify each object contained in the conformance group. Each of the specified objects must be defined in the same information module as the OBJECT-GROUP macro appears, and must have a MAX-ACCESS clause value of "accessible-for-notify", "read-only", "read-write", or "read- create".
The second sentence says that the objects have to be defined in the _same_ information module as the OBJECT-GROUP macro appears. This is what smilint is checking. (No, I can't explain spontaneously why this rule is in RFC 2580.)
/js
Thanks, I think ( but do not understand ) that the attached fixed the situation ( the errors disappeared from the smilint check). I guess that the conformance assumes objects that are augmented from other information modules?
Bob
On Thu, 2011-11-03 at 06:57 +0100, Juergen Schoenwaelder wrote:
On Wed, Nov 02, 2011 at 07:16:26PM -0400, Robert G Cole wrote:
I am having difficulty getting this MIB module to pass smilint. The issue relates to the use of AUGMENTS. If I do not IMPORT objects from RMON2, then I get severity [1] errors, but if I use IMPORT then I get the following severity [3] errors. Any advise to correct or is this an smilint issue?
Section 3.1 of RFC 2580 says:
The OBJECTS clause, which must be present, is used to specify each object contained in the conformance group. Each of the specified objects must be defined in the same information module as the OBJECT-GROUP macro appears, and must have a MAX-ACCESS clause value of "accessible-for-notify", "read-only", "read-write", or "read- create".
The second sentence says that the objects have to be defined in the _same_ information module as the OBJECT-GROUP macro appears. This is what smilint is checking. (No, I can't explain spontaneously why this rule is in RFC 2580.)
/js
On Thu, Nov 03, 2011 at 09:58:01PM -0400, Robert G Cole wrote:
Thanks, I think ( but do not understand ) that the attached fixed the situation ( the errors disappeared from the smilint check). I guess that the conformance assumes objects that are augmented from other information modules?
Since this module seems to be an extension of the RMON2-MIB, its name should probably be RMON2-REPORT-SAMPLES-MIB or something like that.
/js
participants (3)
-
James Gosnell -
Juergen Schoenwaelder -
Robert G Cole