smilint output for ./CONFORMANCE-MIB


Message Severities
SeverityCount
error1
minor error1
warning1
Message Types
TypeCount
index-element-no-size (minor error)1
index-exceeds-too-large (warning)1
object-identifier-not-prefix (error)1

Messages:

CONFORMANCE-MIB

   1: -- extracted from draft-bierman-conf-mib-00.txt
   2: -- at Sat Jun  1 06:08:59 2002
   3: 
   4: CONFORMANCE-MIB DEFINITIONS ::= BEGIN
   5: 
   6: IMPORTS
   7:         MODULE-IDENTITY, OBJECT-TYPE, mib-2
   8:                 FROM SNMPv2-SMI
   9:         MODULE-COMPLIANCE, OBJECT-GROUP
  10:                 FROM SNMPv2-CONF
  11:         TEXTUAL-CONVENTION, TimeStamp
  12:                 FROM SNMPv2-TC;
  13: 
  14: conformanceMIB MODULE-IDENTITY
  15:     LAST-UPDATED    "200205300000Z"
  16:     ORGANIZATION    "IETF OPS-NM Area"
  17:     CONTACT-INFO
  18:             "        Andy Bierman
  19:                      Cisco Systems, Inc.
  20:                 Tel: +1 408 527-3711
  21:              E-mail: abierman@cisco.com
  22:              Postal: 170 West Tasman Drive
  23:                      San Jose, CA USA 95134
  24: 
  25:              Send comments to <mibs@ops.ietf.org>"
  26:     DESCRIPTION
  27:             "Contains objects which describe the conformance
  28:              level for specific data objects."
  29:     REVISION  "200205300000Z"
  30:        DESCRIPTION
  31:             "Initial version."
  32:   ::= { mib-2 xxx }   -- unassigned
  32: error - Object identifier element `xxx' name only allowed as first element
  33: 
  34: 
  35: confMibObjects       OBJECT IDENTIFIER ::= { conformanceMIB 1 }
  36: confMibNotifications OBJECT IDENTIFIER ::= { conformanceMIB 2 }
  37: confMibConformance   OBJECT IDENTIFIER ::= { conformanceMIB 3 }
  38: 
  39: confMibConformanceObjects OBJECT IDENTIFIER
  40:                                        ::= { confMibObjects 1 }
  41: 
  42: --
  43: -- Textual Conventions
  44: --
  45: 
  46: ConformanceLevel ::= TEXTUAL-CONVENTION
  47:     STATUS current
  48:     DESCRIPTION
  49:             "An indication of the conformance level for a particular set
  50:             of MIB objects.
  51: 
  52:             The value 'noConf' indicates that the agent does not
  53:             implement any of the required semantics for the associated
  54:             set of objects.  Usually this means the object is not
  55:             implemented at all.  However, it also indicates the special
  56:             case in which incorrect values are returned, e.g., counter
  57:             objects that always return zero, string objects that always
  58:             return a zero-length string (but should not), hard-wired
  59:             (potentially incorrect) enumerations or gauges.
  60: 
  61:             The value 'otherConf' indicates that the implementation
  62:             complies with the semantics of the associated set of objects
  63:             in a manner that varies from the specification in some way.
  64: 
  65:             The value 'minConf' indicates that the implementation
  66:             complies with the semantics of the associated set of objects
  67:             as refined by a GROUP clause or an OBJECT clause within a
  68:             MODULE-COMPLIANCE macro.
  69: 
  70:             The value 'fullConf' indicates that the implementation
  71:             complies with the semantics of the associated set of objects
  72:             as defined by an indicated compliance statement for the set
  73:             of objects.
  74: 
  75:             The value 'completeConf' indicates that the implementation
  76:             complies with the full semantics of the associated set of
  77:             objects as defined by the data definitions for the objects.
  78:             This may be greater than than the conformance level
  79:             indicated by the 'fullConf' enumeration if the indicated
  80:             compliance statement does not require full implementation of
  81:             the entire set of objects."
  82:     REFERENCE
  83:        "RFC 2580, section 5."
  84:     SYNTAX INTEGER {
  85:                     noConf(1),
  86:                     otherConf(2),
  87:                     minConf(3),
  88:                     fullConf(4),
  89:                     completeConf(5)
  90:                    }
  91: 
  92: 
  93: ConformanceString ::= TEXTUAL-CONVENTION
  94:     STATUS current
  95:     DESCRIPTION
  96:             "An administrative string identifying conformance
  97:             information.
  98: 
  99:             An object of this type SHOULD follow the encoding rules for
 100:             an SnmpAdminString, except its length is limited to 1024
 101:             octets instead of 255 octets."
 102:     REFERENCE
 103:        "RFC 2571, section 5."
 104:     SYNTAX OCTET STRING (SIZE (0..1024))    -- SnmpAdminString
 105: 
 106: --
 107: -- Conformance Group scalars
 108: --
 109: 
 110: confLastUpdateTime OBJECT-TYPE
 111:     SYNTAX      TimeStamp
 112:     MAX-ACCESS  read-only
 113:     STATUS      current
 114:     DESCRIPTION
 115:             "The value of sysUpTime when the agent last added, deleted,
 116:             or modified an entry in the confTable."
 117:     ::= { confMibConformanceObjects 1 }
 118: 
 119: --
 120: -- Conformance Table
 121: --
 122: 
 123: confTable OBJECT-TYPE
 124:     SYNTAX      SEQUENCE OF ConfEntry
 125:     MAX-ACCESS  not-accessible
 126:     STATUS      current
 127:     DESCRIPTION
 128:             "A list of entries describing the MIB conformance for this
 129:             agent."
 130:     ::= { confMibConformanceObjects 2 }
 131: 
 132: confEntry OBJECT-TYPE
 132: warning - warning: index of row `confEntry' can exceed OID size limit by 7 subidentifier(s)
 133:     SYNTAX      ConfEntry
 134:     MAX-ACCESS  not-accessible
 135:     STATUS      current
 136:     DESCRIPTION
 137:             "A conceptual row in the confTable. Entries SHOULD be
 138:             created by the agent at system reinitialization time.
 139:             However, agents MAY create, delete, or modify entries in
 140:             this table to support dynamic loading and unloading of MIB
 141:             modules. It is possible that overlapping entries will exist
 142:             in this table, in which case the more specific entry (i.e.,
 143:             the one with the longest confSubTree INDEX) takes
 144:             precedence."
 145:     INDEX { confSubTree }
 146:     ::= { confTable 1 }
 147: 
 148: 
 149: ConfEntry ::= SEQUENCE {
 150:     confSubTree                      OBJECT IDENTIFIER,
 151:     confModuleCompliance             OBJECT IDENTIFIER,
 152:     confLevel                        ConformanceLevel,
 153:     confVarSyntax                    ConformanceString }
 154: 
 155: confSubTree OBJECT-TYPE
 155: minor error - index element `confSubTree' of row `confEntry' should but cannot have a size restriction
 156:     SYNTAX      OBJECT IDENTIFIER
 157:     MAX-ACCESS  not-accessible
 158:     STATUS      current
 159:     DESCRIPTION
 160:             "The root of the MIB sub-tree associated with this entry.
 161:             This object SHOULD identify an interior node to indicate
 162:             multiple MIB objects or a leaf node to indicate a single MIB
 163:             object."
 164:     ::= { confEntry 1 }
 165: 
 166: confModuleCompliance OBJECT-TYPE
 167:     SYNTAX      OBJECT IDENTIFIER
 168:     MAX-ACCESS  read-only
 169:     STATUS      current
 170:     DESCRIPTION
 171:             "Identifies the MODULE-COMPLIANCE macro name for the
 172:             associated set of MIB objects. If no appropriate value can
 173:             be determined, then the agent will return '0.0'."
 174:     REFERENCE
 175:             "RFC 2580, section 5.5."
 176:     ::= { confEntry 2 }
 177: 
 178: confLevel OBJECT-TYPE
 179:     SYNTAX      ConformanceLevel
 180:     MAX-ACCESS  read-only
 181:     STATUS      current
 182:     DESCRIPTION
 183:             "Indicates the basic level of conformance for the associated
 184:             set of MIB objects.
 185: 
 186:             If this object contains the value 'otherConf', then the
 187:             confVarSyntax object SHOULD be present for the associated
 188:             entry.
 189: 
 190:             If this object contains the value 'fullConf', 'minConf', or
 191:             'noConf' then the confVarSyntax object MAY be present for
 192:             the associated entry.
 193: 
 194:             If this object contains the value 'completeConf' then the
 195:             confVarSyntax object SHOULD NOT be present for the
 196:             associated entry."
 197:     REFERENCE
 198:             "RFC 2580, section 5."
 199:     ::= { confEntry 3 }
 200: 
 201: confVarSyntax OBJECT-TYPE
 202:     SYNTAX      ConformanceString
 203:     MAX-ACCESS  read-only
 204:     STATUS      current
 205:     DESCRIPTION
 206:             "A textual representation of the syntactical variation
 207:             described by this variation structure.
 208: 
 209:             If the associated confLevel object is equal to 'otherConf',
 210:             then this string SHOULD contain the the same value as the
 211:             SYNTAX clause within a VARIATION clause of an AGENT-
 212:             CAPABILITIES macro.
 213: 
 214:             If the associated confLevel object is equal to 'minConf',
 215:             and this entry identifies a set of MIB objects, then this
 216:             string MAY identify the applicable GROUP clause(s)
 217:             associated with the entry.
 218: 
 219:             For all entries in which the associated confLevel object is
 220:             equal to 'minConf', this string SHOULD contain the same
 221:             value as the SYNTAX, WRITE-SYNTAX, and/or MIN-ACCESS clauses
 222:             present within the OBJECT clause of a MODULE-COMPLIANCE
 223:             macro. The actual keyword (e.g., 'SYNTAX') SHOULD precede
 224:             the quoted string value.  Multiple clauses MAY be
 225:             concatenated within a single string, and SHOULD be separated
 226:             by whitespace.  If this entry identifies multiple objects,
 227:             then the same clause(s) must apply to all objects.
 228: 
 229:             The agent MAY return a zero-length string instead of a
 230:             noSuchInstance exception."
 231:     REFERENCE
 232:             "RFC 2580, sections 5.4.3 and 6.5.2."
 233:     ::= { confEntry 4 }
 234: 
 235: --
 236: -- Notification Section  (none defined)
 237: --
 238: 
 239: --
 240: -- Conformance Section
 241: --
 242: 
 243: confMibCompliances OBJECT IDENTIFIER ::= { confMibConformance 1 }
 244: confMibGroups      OBJECT IDENTIFIER ::= { confMibConformance 2 }
 245: 
 246: confMibCompliance MODULE-COMPLIANCE
 247:     STATUS  current
 248:     DESCRIPTION
 249:             "Describes the requirements for conformance to the
 250:             Conformance MIB."
 251:     MODULE  -- this module
 252:         MANDATORY-GROUPS { confMibConformanceGroup }
 253: 
 254:     ::= { confMibCompliances 1 }
 255: 
 256: -- Object Groups
 257: 
 258: confMibConformanceGroup OBJECT-GROUP
 259:     OBJECTS {
 260:              confLastUpdateTime,
 261:              confModuleCompliance,
 262:              confLevel,
 263:              confVarSyntax
 264:     }
 265:     STATUS  current
 266:     DESCRIPTION
 267:             "A collection of objects used to describe the conformance
 268:             level of the MIB objects supported by an agent."
 269:     ::= { confMibGroups 1 }
 270: 
 271: END
 272: 
 273: -- 
 274: -- Copyright (C) The Internet Society (2002).  All Rights Reserved.
 275: -- 
 276: -- This document and translations of it may be copied and furnished to
 277: -- others, and derivative works that comment on or otherwise explain it or
 278: -- assist in its implementation may be prepared, copied, published and
 279: -- distributed, in whole or in part, without restriction of any kind,
 280: -- provided that the above copyright notice and this paragraph are included
 281: -- on all such copies and derivative works.  However, this document itself
 282: -- may not be modified in any way, such as by removing the copyright notice
 283: -- or references to the Internet Society or other Internet organizations,
 284: -- except as needed for the purpose of developing Internet standards in
 285: -- which case the procedures for copyrights defined in the Internet
 286: -- Standards process must be followed, or as required to translate it into
 287: -- languages other than English.
 288: -- 
 289: -- The limited permissions granted above are perpetual and will not be
 290: -- revoked by the Internet Society or its successors or assigns.
 291: -- 
 292: -- This document and the information contained herein is provided on an "AS
 293: -- IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
 294: -- FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
 295: -- LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
 296: -- INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
 297: -- FITNESS FOR A PARTICULAR PURPOSE.
 298: