smilint output for ./ENTSUPPL-MIB


Message Severities
SeverityCount
error6
minor error1
Message Types
TypeCount
bad-identifier-case (error)1
basetype-unknown (error)1
date-length (error)1
object-identifier-not-prefix (error)1
revision-missing (minor error)1
sequence-type-mismatch (error)1
type-unknown (error)1

Messages:

ENTSUPPL-MIB

   1: -- extracted from draft-tesink-entity-supplmib-01.txt
   2: -- at Fri Aug 20 06:22:54 2004
   3: 
   4:    ENTSUPPL-MIB DEFINITIONS ::= BEGIN
   5: 
   6:    IMPORTS
   7:        MODULE-IDENTITY, OBJECT-TYPE,
   8:        transmission
   9:            FROM SNMPv2-SMI
  10:        DateAndTime
  11:            FROM SNMPv2-TC
  12:        MODULE-COMPLIANCE, OBJECT-GROUP
  13:            FROM SNMPv2-CONF
  14:        entPhysicalIndex
  15:            FROM ENTITY-MIB;
  16: 
  17:    entitySupplMIB MODULE-IDENTITY
  18:        LAST-UPDATED "200408160000Z"  -- August 16, 2004
  19:            ORGANIZATION "IETF Entity MIB Working Group"
  20:            CONTACT-INFO
  21:               "WG charter:
  22:                  http://www.ietf.org/html.charters/entmib-charter.html
  23: 
  24:                Mailing Lists:
  25:                  General Discussion: entmib@ietf.org
  26:                  To Subscribe: http://www.ietf.org/mailman/listinfo/entmib
  27: 
  28:                 Chair: Margaret Wasserman
  29:                Postal:
  30:                   Tel:
  31:                E-mail: margaret@thingmagic.com
  32: 
  33:                Author: Kaj Tesink
  34:                Postal: One Telcordia Drive
  35:                        Piscataway, NJ 08854
  36:                        USA
  37:                   Tel: +1 732-699-6068
  38:                E-mail: kaj@research.telcordia.com"
  39: 
  40:        DESCRIPTION
  41:          "The objects in this MIB module are used in conjunction
  42:          with objects in the ENTITY-MIB to manage entities
  43: 
  44:          Copyright (C) The Internet Society (2004).  This version
  45:          of this MIB module is part of RFC yyyy;  see the RFC
  46:          itself for full legal notices."
  47: -- RFC Ed.: replace yyyy with actual RFC number & remove this notice
  48: 
  49:        REVISION    "200408160000Z "  -- August 16, 2004
  49: error - date specification `200408160000Z ' has an illegal length
  50:        DESCRIPTION "Initial version, published as RFC yyyy."
  51: -- RFC Ed.: replace yyyy with actual RFC number & remove this notice
  52: 
  53:        ::= { transmission XXX }
  53: minor error - revision for last update is missing
  53: error -
`XXX' should start with a lower case letter

  53: error - Object identifier element `XXX' name only allowed as first element
  54: -- RFC Ed.: replace XXX with IANA-assigned number & remove this notice
  55:    -- The main sections of the module
  56: 
  57:    entitySupplObjects     OBJECT IDENTIFIER ::= { entitySupplMIB 1 }
  58: 
  59:    entitySupplConformance OBJECT IDENTIFIER ::= { entitySupplMIB 2 }
  60: 
  61: 
  62: 
  63:    -- These objects provide extensions to the entPhysicalTable.
  64: 
  65:    entSupplPhysicalTable OBJECT-TYPE
  66:        SYNTAX  SEQUENCE OF EntSupplPhysicalEntry
  67:        MAX-ACCESS  not-accessible
  68:        STATUS  current
  69:        DESCRIPTION
  70:           "The table for supplementary objects to the entPhysicalTable."
  71:         ::= { entitySupplObjects 1 }
  72: 
  73:    entSupplPhysicalEntry OBJECT-TYPE
  74:        SYNTAX  EntSupplPhysicalEntry
  75:        MAX-ACCESS  not-accessible
  76:        STATUS  current
  77:        DESCRIPTION
  78:           "An entry in the entSupplPhysicalTable.  For each
  79:           instance of this object there MUST be a corresponding
  80:           instance of entPhysicalEntry."
  81:        INDEX  { entPhysicalIndex }
  82:         ::= { entSupplPhysicalTable 1 }
  83: 
  84:    EntSupplPhysicalEntry ::=
  85:        SEQUENCE {
  86:            entSupplPhysicalManufacturingDate DateAndTime,
  87:            entSupplPhysicalUris    OCTET STRING
  88:            }
  89: 
  90: 
  91:    entSupplPhysicalManufacturingDate  OBJECT-TYPE
  92:        SYNTAX      DateAndTime
  93:        MAX-ACCESS  read-only
  94:        STATUS      current
  95:        DESCRIPTION
  96:           "The manufacturing date for the physical entity."
  97:         ::= { entSupplPhysicalEntry 1 }
  98: 
  99:    entSupplPhysicalUris OBJECT-TYPE
  99: error - type `DisplayString' of node `entSupplPhysicalUris' does not resolve to a known base type
 100:        SYNTAX      DisplayString
 101:        MAX-ACCESS  read-write
 101: error - unknown type `DisplayString'
 102:        STATUS      current
 103:        DESCRIPTION
 104:           "This object contains additional identification information
 105:            about the physical entity. The object contains URIs and
 106:            therefore the syntax of this object must conform to RFC
 107:            2396 section 2. Multiple URIs may be separated by white
 108:            space characters."
 109:        ::= { entSupplPhysicalEntry 2 }
 109: error - type of `entSupplPhysicalUris' in sequence and object type definition do not match
 110: 
 111: 
 112: 
 113:    --
 114:    --     Conformance Statements
 115:    --
 116: 
 117:    entitySupplGroups      OBJECT IDENTIFIER ::= { entitySupplConformance 1 }
 118: 
 119:    entitySupplCompliances OBJECT IDENTIFIER ::= { entitySupplConformance 2 }
 120: 
 121:    --     Object Groups
 122: 
 123:    entitySupplPhysicalGroup OBJECT-GROUP
 124:        OBJECTS {
 125:            entSupplPhysicalManufacturingDate,
 126:            entSupplPhysicalUris
 127:            }
 128:        STATUS  current
 129:        DESCRIPTION
 130:           "A collection of supplemental objects
 131:            for to support physical entity features."
 132:         ::= { entitySupplGroups 1 }
 133: 
 134: 
 135:    --     Compliance Statements
 136: 
 137:    entitySupplCompliance MODULE-COMPLIANCE
 138:        STATUS  current
 139:        DESCRIPTION
 140:           "The compliance statement for entities that support
 141:           this module.  Compliance with the entity3Compliance
 142:           statement of the ENTITY-MIB is prerequisite."
 143: 
 144:        MODULE  -- this module
 145:            MANDATORY-GROUPS {
 146:                entitySupplPhysicalGroup
 147:                }
 148: 
 149:            OBJECT       entSupplPhysicalUris
 150:            MIN-ACCESS   read-only
 151:            DESCRIPTION
 152:                "Write access is not required."
 153: 
 154:         ::= { entitySupplCompliances 1 }
 155: 
 156:    END
 157: 
 158: -- 
 159: --    Copyright (C) The Internet Society (2004).  All Rights Reserved.
 160: -- 
 161: --    This document and translations of it may be copied and furnished to
 162: --    others, and derivative works that comment on or otherwise explain it
 163: --    or assist in its implementation may be prepared, copied, published
 164: --    and distributed, in whole or in part, without restriction of any
 165: --    kind, provided that the above copyright notice and this paragraph are
 166: --    included on all such copies and derivative works.  However, this
 167: --    document itself may not be modified in any way, such as by removing
 168: --    the copyright notice or references to the Internet Society or other
 169: --    Internet organizations, except as needed for the purpose of
 170: --    developing Internet standards in which case the procedures for
 171: --    copyrights defined in the Internet Standards process must be
 172: --    followed, or as required to translate it into languages other than
 173: --    English.
 174: -- 
 175: --    The limited permissions granted above are perpetual and will not be
 176: --    revoked by the Internet Society or its successors or assigns.
 177: -- 
 178: --    This document and the information contained herein is provided on an
 179: --    "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
 180: --    TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
 181: --    BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
 182: --    HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
 183: --    MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 184: --       ************************************************************
 185: --       * NOTES TO RFC Editor (to be removed prior to publication) *
 186: --       *                                                          *
 187: --       * 1.) The normative references [RFCwwww] and [RFCzzzz]     *
 188: --       * must be updated to point to the appropriate              *
 189: --       * RFC when the corresponding Internet Draft is published,  *
 190: --       * and all occurrences of the reference tags must be        *
 191: --       * changed.                                                 *
 192: --       *                                                          *
 193: --       * 2.) Please replace all occurrences of "yyyy" in the      *
 194: --       * DESCRIPTION clause of the MODULE-IDENTITY invocation     *
 195: --       * in Section 4 with the RFC number assigned to this        *
 196: --       * specification and remove the accompanying notes.         *
 197: --       *                                                          *
 198: --       * 3.) Please replace "XXX" in the MODULE-IDENTITY value    *
 199: --       * with an IANA-assigned value under the 'transmission'     *
 200: --       * subtree and remove the accompanying note.                *
 201: --       *                                                          *
 202: --       ************************************************************
 203: