[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: smilint warnings



On Wed, 30 Mar 2005, Romascanu, Dan (Dan) wrote:
> Can somebody explain the [following] level 5 warnings?
> 
> rtcpxrmib_mar28_05.mib.txt:1590: [5]
> {notification-not-reversible} warning: notification
> `rtcpXrVoipThresholdViolation' is not reverse mappable

It means that the next-to-last sub-ID is non-zero.  That is a
problem for mapping between SNMPv3 and SNMPv1, see RFC 3584 for
details.  The fix is to change from this:

--
-- OBJECTS
--
rtcpXrMIBObjects  OBJECT IDENTIFIER ::= { rtcpXrMIB 1 }
rtcpXrConformance OBJECT IDENTIFIER ::= { rtcpXrMIB 2 }
rtcpXrEvents      OBJECT IDENTIFIER ::= { rtcpXrMIB 3 }

to this:

--
-- Top-Level OID Trees
--
rtcpXrEvents      OBJECT IDENTIFIER ::= { rtcpXrMIB 0 }
rtcpXrMIBObjects  OBJECT IDENTIFIER ::= { rtcpXrMIB 1 }
rtcpXrConformance OBJECT IDENTIFIER ::= { rtcpXrMIB 2 }

This issue is covered in Section 4.6.5 and Appendix D of
<draft-ietf-ops-mib-review-guidelines-04.txt>

> rtcpxrmib_mar28_05.mib.txt:66: [5] {type-without-format}
> warning: type `LeveldB' has no format specification
> rtcpxrmib_mar28_05.mib.txt:72: [5] {type-without-format}
> warning: type `Rfactor' has no format specification
> rtcpxrmib_mar28_05.mib.txt:82: [5] {type-without-format}
> warning: type `ScaledMOSscore' has no format specification
> rtcpxrmib_mar28_05.mib.txt:94: [5] {type-without-format}
> warning: type `Percentage' has no format specification

These warnings arise because the TC definitions `LeveldB',
`Rfactor', `ScaledMOSscore', and `Percentage' have no
DISPLAY-HINT clause. Although its presence is optional, it
is a good idea to include it;  see Section 4.6.3 of
<draft-ietf-ops-mib-review-guidelines-04.txt>

Mike Heard