[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: LMP MIB

To: "Thomas D. Nadeau" <tnadeau@cisco.com>
Subject: RE: LMP MIB
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
Date: Fri, 12 Apr 2002 18:03:11 +0200
Cc: Kireeti Kompella <kireeti@juniper.net>, ccamp@ops.ietf.org
> >Below is the report. PLEASE PLEASE fix those things FIRST.
> >And I did not look at the content at all yet.
> 
> Will do ASAP.  I used smilint and found only warnings, but
> I could be wrong.   Could you post those two URLs that one
> can send MIBs to so that they can be processed?  Others may
> find this useful.
> 
I have now attached the SMIlint errors/warnings as well.
The list is impressive. The wng about length of a descriptor
being lonbger than 32 is one that you can take with a grain
of salt, but many of the other better be checked. Some of
those warnings do not always mean REALLY BROKEN, but in many
cases it is an indication of possible SLOPPY WORK (if I may
be so rude). Why don't you guys try to make the list as short
as possible (or disappear). Or do you want the MIB Doctor 
review or the AD review to be triggered with "red alert
signals" ??

I am not aware you can email a MIB to a SMICng server.
I have a copy and I check all MIBs with the it. So does the
RFC-Editor these days just before a MIB RFC is published.
It is a very strict syntax checker, but that helps me/us pay 
attention to all the incorrect and even to some possibly correct
but questionable uses of syntax. Info at:

   http://www.snmpinfo.com  (sorry it is a bit commercial)

The mail address for SMIlint is as follows:

    smilint@ibr.cs.tu-bs.de

Just put your MIB in the body of the email and it will check
the MIB (highest severity level) and return results.
SMIlint is also available for free and can be downloaded from:

   http://www.ibr.cs.tu-bs.de/projects/libsmi/

>          In any event, a new version will be published after
> the last call period is over that includes all of the suggested
> changes AND compiles cleanly with SmicNg AND SmiLint.
> 
Great Thank you.
But I wanted all people to try and be aware that it might actually
be a VERY GOOD THING to get the syntax correct before even
thinking of a WG Last Call and certainly before sending anything
to the AD for consideration on standards track.

Bert
----- smilint output ------------
-----Original Message-----
From: smilint@ibr.cs.tu-bs.de [mailto:smilint@ibr.cs.tu-bs.de]
Sent: Friday, April 12, 2002 5:36 PM
To: Wijnen, Bert (Bert)
Subject: Your smilint job


output of smilint -l 9 follows,
empty output means everything is fine.
--start--
81: date specification `200105223200Z' contains an illegal hour
749: warning: object identifier name `dataBearingChannelLinkMuxCapability' longer than 32 characters
770: warning: object identifier name `dataBearingChannelPreferredProtection' longer than 32 characters
782: warning: object identifier name `dataBearingChannelCurrentProtection' longer than 32 characters
820: warning: object identifier name `dataBearingChannelDescriptorTable' longer than 32 characters
903: warning: object identifier name `dataBearingChannelMinReservableBandwidth' longer than 32 characters
918: warning: object identifier name `dataBearingChannelMaxReservableBandwidth' longer than 32 characters
944: warning: object identifier name `dataBearingChannelDescrStorageType' longer than 32 characters
1007: warning: object identifier name `dataBearingChannelUnreservedBandwidth' longer than 32 characters
1022: warning: object identifier name `dataBearingChannelMaximumLspBandwidth' longer than 32 characters
1243: warning: object identifier name `linkBundlingMonitoringModuleCompliance' longer than 32 characters
829: warning: row identifier `dataBearingChannelDescrEntry' should have the same prefix as table identifier `dataBearingChannelDescriptorTable'
1100: warning: refined object `dataBearingChannelDescrRowStatus' not listed in a mandatory or optional group
1100: warning: refined object `dataBearingChannelDescrStorageType' not listed in a mandatory or optional group
1100: warning: refined object `dataBearingChannelBwRowStatus' not listed in a mandatory or optional group
1100: warning: refined object `dataBearingChannelBwStorageType' not listed in a mandatory or optional group
1243: warning: refined object `dataBearingChannelEncodingType' not listed in a mandatory or optional group
1243: warning: refined object `dataBearingChannelDescrPriority' not listed in a mandatory or optional group
1243: warning: refined object `dataBearingChannelMinReservableBandwidth' not listed in a mandatory or optional group
1243: warning: refined object `dataBearingChannelDescrRowStatus' not listed in a mandatory or optional group
1243: warning: refined object `dataBearingChannelDescrStorageType' not listed in a mandatory or optional group
1243: warning: refined object `dataBearingChannelBwRowStatus' not listed in a mandatory or optional group
1243: warning: refined object `dataBearingChannelBwStorageType' not listed in a mandatory or optional group
1495: warning: current group `dataBearingChannelBandwidthGroup' is unconditionally optional
1514: warning: current group `linkBundlingNotificationGroup' is unconditionally optional
5: warning: identifier `Integer32' imported from module `SNMPv2-SMI' is never used
11: warning: identifier `TEXTUAL-CONVENTION' imported from module `SNMPv2-TC' is never used
12: warning: identifier `RowPointer' imported from module `SNMPv2-TC' is never used
12: warning: identifier `TimeStamp' imported from module `SNMPv2-TC' is never used
15: warning: identifier `InterfaceIndex' imported from module `IF-MIB' is never used
22: warning: identifier `InetAddressType' imported from module `INET-ADDRESS-MIB' is never used
165: warning: `InetAddress' object should have an accompanied preceding `InetAdressType' object
174: warning: `InetAddress' object should have an accompanied preceding `InetAdressType' object
2708: warning: object identifier name `lmpCcChannelStatusRequestReceived' longer than 32 characters
2726: warning: object identifier name `lmpCcChannelStatusRequestRetransmit' longer than 32 characters
2735: warning: object identifier name `lmpCcChannelStatusResponseReceived' longer than 32 characters
3125: warning: object identifier name `lmpDataBearingLinkRemoteIpAddress' longer than 32 characters
3162: warning: object identifier name `lmpDataBearingLinkActiveOperStatus' longer than 32 characters
3180: warning: object identifier name `lmpDataBearingLinkPassiveOperStatus' longer than 32 characters
3272: warning: object identifier name `lmpDataBearingLinkActiveTestSuccess' longer than 32 characters
3282: warning: object identifier name `lmpDataBearingLinkActiveTestFailure' longer than 32 characters
3291: warning: object identifier name `lmpDataBearingLinkPassiveTestSuccess' longer than 32 characters
3301: warning: object identifier name `lmpDataBearingLinkPassiveTestFailure' longer than 32 characters
3311: warning: object identifier name `lmpDataBearingLinkCounterDiscontinuityTime' longer than 32 characters
3330: warning: object identifier name `lmpLinkPropertyMismatchNotifEnable' longer than 32 characters
3403: warning: object identifier name `lmpDataBearingLinkPropertyMismatch' longer than 32 characters
3459: warning: object identifier name `lmpDataBearingLinkVerificationFailure' longer than 32 characters
3978: warning: object identifier name `lmpControlChannelIsInterfaceGroup' longer than 32 characters
3986: warning: object identifier name `lmpControlChannelIsNotInterfaceGroup' longer than 32 characters
1713: warning: index element `lmpNbrNodeId' of row `lmpNbrEntry' should be not-accessible in SMIv2 MIB
1713: warning: index of row `lmpNbrEntry' can exceed OID size limit by 138 subidentifier(s)
1903: warning: index element `lmpCcId' of row `lmpControlChannelEntry' should be not-accessible in SMIv2 MIB
3403: warning: object `ifStackHigherLayer' of notification `lmpDataBearingLinkPropertyMismatch' must not be `not-accessible'
2434: warning: node `lmpCcBeginVerifyRetransmit' must be contained in at least one conformance group
2498: warning: node `lmpCcEndVerifyRetransmit' must be contained in at least one conformance group
2544: warning: node `lmpCcTestStatusSuccessRetransmit' must be contained in at least one conformance group
2571: warning: node `lmpCcTestStatusFailureRetransmit' must be contained in at least one conformance group
2580: warning: node `lmpCcTestStatusAckReceived' must be contained in at least one conformance group
2589: warning: node `lmpCcTestStatusAckSent' must be contained in at least one conformance group
4124: warning: current group `lmpNotificationGroup' is unconditionally optional
1656: warning: textual convention `NodeID' can not be derived from the textual convention `InetAddress'
1530: warning: identifier `Integer32' imported from module `SNMPv2-SMI' is never used
1537: warning: identifier `RowPointer' imported from module `SNMPv2-TC' is never used
1540: warning: identifier `InterfaceIndex' imported from module `IF-MIB' is never used
1543: warning: identifier `InetAddressType' imported from module `INET-ADDRESS-MIB' is never used
1733: warning: `InetAddress' object should have an accompanied preceding `InetAdressType' object
1972: warning: `InetAddress' object should have an accompanied preceding `InetAdressType' object
2809: warning: `InetAddress' object should have an accompanied preceding `InetAdressType' object
3125: warning: `InetAddress' object should have an accompanied preceding `InetAdressType' object
--end--
Prev by Date: RE: LMP MIB
Next by Date: RE: CCAMP WG Last Call on GMPLS Routing Documents
Previous by thread: RE: LMP MIB
Index(es):
- Date
- Thread