smilint output for ./BGP4-OPT-PARAMETERS-MIB


Message Severities
SeverityCount
severe9
error10
change recommended8
warning13
fyi1
Message Types
TypeCount
augment-no-row (error)1
basetype-unknown (error)1
group-membership (change recommended)8
identifier-case-match (warning)1
import-unused (warning)7
index-element-no-range (error)1
internal-flushing (warning)4
internal-other (severe)4
module-identity-missing (error)1
module-not-found (severe)1
object-identifier-unknown (severe)4
parent-scalar (error)3
previous-definition (fyi)1
row-name-table-name (warning)1
row-node-subidentifier-one (error)1
type-unknown (error)2

Messages:

BGP4-OPT-PARAMETERS-MIB

   1: -- extracted from draft-jhaas-bgp4-mib-opt-00.txt
   2: -- at Sat Feb 24 06:04:17 2001
   3: 
   4:       BGP4-OPT-PARAMETERS-MIB DEFINITIONS ::= BEGIN
   5: 
   6:       IMPORTS
   7:           MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
   7: warning - warning: identifier `NOTIFICATION-TYPE' imported from module `SNMPv2-SMI' is never used
   8:               Integer32, Counter32, Gauge32, mib-2
   8: warning - warning: identifier `Counter32' imported from module `SNMPv2-SMI' is never used
   8: warning -
warning: identifier `Gauge32' imported from module `SNMPv2-SMI' is never used

   8: warning -
warning: identifier `mib-2' imported from module `SNMPv2-SMI' is never used
   9:               FROM SNMPv2-SMI
  10: 
  11:           bgpPeerRemoteAddr FROM BGP-MIB
  11: severe - failed to locate MIB module `BGP-MIB'
  12: 
  13:           TruthValue, AutonomousType FROM SNMPv2-TC
  14: 
  15:           MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
  15: warning - warning: identifier `MODULE-COMPLIANCE' imported from module `SNMPv2-CONF' is never used
  15: warning -
warning: identifier `OBJECT-GROUP' imported from module `SNMPv2-CONF' is never used

  15: warning -
warning: identifier `NOTIFICATION-GROUP' imported from module `SNMPv2-CONF' is never used
  16:               FROM SNMPv2-CONF;
  17: 
  18: 
  19:       bgp4OptParametersMIB MODULE-IDENTITY
  20:           LAST-UPDATED "200102230000Z"
  21:           ORGANIZATION "IETF IDR Working Group"
  22:           CONTACT-INFO
  23:               "E-Mail: idr@merit.net
  24: 
  25:                Editor:  Susan Hares
  26:                         517 W. William Street
  27:                         Ann Arbor, MI  48103-4943
  28:                         Tel: +1 734 936 2095
  29:                         Fax: +1 734 615-3241
  30:                         E-mail: skh@nexthop.com
  31: 
  32:                Authors: Jeffrey Haas
  33:                         NextHop Technologies
  34:                         517 W. William Street
  35:                         Ann Arbor, MI  48103-4943
  36:                         Tel: +1 734 936 2095
  37:                         Fax: +1 734 615-3241
  38:                         E-mail: jhaas@nexthop.com"
  39: 
  40:           DESCRIPTION
  41:               "The extension of the MIB module for BGP-4 for
  42:                optional parameters."
  43:           REVISION    "200102230000Z"
  44:           DESCRIPTION
  45:               "Initial proposal.
  46:                Definition of MIB extension for the following
  47:                optional exetnsions to BGP-4"
  48: 
  49:           REFERENCE
  49: severe - syntax error, unexpected REFERENCE, expecting COLON_COLON_EQUAL
  50:               "RFC 1771 - Border Gateway Protocol, Version 4
  51:                RFC 2385 - TCP MD5 Authentication
  52:                RFC 2842 - Capabilities Advertisement with BGP-4"
  53:           ::= { bgp 9 }
  53: warning - warning: flushing recent incorrect declaration, see previous error(s)
  54: 
  55:       -- bgpAuthenticationTable        { bgp4OptParametersMIB 1 }
  56:       -- bgpCapabilitySupportAvailable { bgp4OptParametersMIB 2 }
  57:       -- bgpSupportedCapabilities      { bgp4OptParametersMIB 3 }
  58:       -- bgpPeerCapabilitiesTable      { bgp4OptParametersMIB 4 }
  59:       -- bgpProtocolExtensions         { bgp4OptParametersMIB 5 }
  60: 
  61: 
  62:       bgpAuthenticationTable OBJECT-TYPE
  63:           SYNTAX     SEQUENCE OF BgpAuthenticationPeerEntry
  63: error - unknown type `BgpAuthenticationPeerEntry'
  64:           MAX-ACCESS not-accessible
  65:           STATUS     current
  66:           DESCRIPTION
  67:               "The BGP-4 Authentication Table contains information
  68:                about BGP Authentication Options on a per-peer basis."
  69:           REFERENCE
  70:               "RFC 1771 - Border Gateway Protocol, Version 4"
  71:           ::= { bgp4OptParametersMIB 1 }
  71: severe - unknown object identifier label `bgp4OptParametersMIB'
  72: 
  73:       bgpAuthenticationPeerEntry OBJECT-TYPE
  73: warning - warning: row identifier `bgpAuthenticationPeerEntry' should have the same prefix as table identifier `bgpAuthenticationTable'
  74:           SYNTAX     BgpAuthenticationPeerEntry
  75:           MAX-ACCESS not-accessible
  76:           STATUS     current
  77:           DESCRIPTION
  78:               "Information about Authentication on a per-peer basis."
  79:           INDEX {
  80:               bgpPeerRemoteAddr,
  80: severe - unknown object identifier label `bgpPeerRemoteAddr'
  81:               bgpAuthenticationDirection
  82:               }
  82: severe - unknown object identifier label `bgpAuthenticationDirection'
  82: error -
index element `bgpAuthenticationDirection' of row `bgpAuthenticationPeerEntry' must have a range restriction
  83:           ::= { bgpAuthenticationTable 1 }
  84: 
  85:       bgpAuthenticationEntry OBJECT-TYPE
  85: error - type `BgpAuthenticationEntry' of node `bgpAuthenticationEntry' does not resolve to a known base type
  86:           SYNTAX     BgpAuthenticationEntry
  87:           MAX-ACCESS not-accessible
  87: error - unknown type `BgpAuthenticationEntry'
  88:           STATUS     current
  89:           DESCRIPTION
  90:               "Information about BGP-4 Authentication."
  91:           ::= { bgpAuthenticationPeerEntry 2 }
  92: 
  93:       BgpAuthenticationEntry ::= SEQUENCE {
  94:           bgpAuthenticationDirection    Integer32
  95:           bgpAuthenticationCode         Integer32
  95: severe - syntax error, unexpected LOWERCASE_IDENTIFIER, expecting '}' or ','
  96:           bgpAuthenticationDataLength   Integer32
  97:           bgpAuthenticationDataContents OCTET STRING
  98:       }
  98: warning - warning: flushing recent incorrect declaration, see previous error(s)
  99: 
 100:       bgpAuthenticationDirection OBJECT-TYPE
 101:           SYNTAX Integer32 {
 101: severe - syntax error, unexpected '{', expecting STATUS
 102:               sent     (1) -- Authorization is being sent
 103:               received (2) -- Authorization is being received
 104:               }
 104: warning - warning: flushing recent incorrect declaration, see previous error(s)
 105:           MAX-ACCESS not-accessible
 105: severe - syntax error, unexpected MAX_ACCESS
 106:           STATUS     current
 107:           DESCRIPTION
 108:               "This variable indicates whether authentication
 109:                information is either being sent by the BGP
 110:                speaker or has been been received by the BGP
 111:                speaker.  It also serves as the index into the
 112:                table of authentication information for the
 113:                direction of authentication."
 114:           ::= { bgpAuthenticationEntry 1 }
 114: warning - warning: flushing recent incorrect declaration, see previous error(s)
 115: 
 116:       bgpAuthenticationCode OBJECT-TYPE
 116: error - scalar's parent node must be simple node
 116: change recommended -
warning: node `bgpAuthenticationCode' must be contained in at least one conformance group
 117:           SYNTAX     Integer32 (-1 | 0..255)
 118:           MAX-ACCESS read-write
 119:           STATUS     current
 120:           DESCRIPTION
 121:               "This is the AuthenticationCode used.
 122:                This value is set to -1 if Authentication is
 123:                not present."
 124:           REFERENCE
 125:               "RFC 1771, sec. 4.2.a"
 126:           ::= { bgpAuthenticationEntry 2 }
 127: 
 128:       bgpAuthenticationDataLength OBJECT-TYPE
 128: error - scalar's parent node must be simple node
 128: change recommended -
warning: node `bgpAuthenticationDataLength' must be contained in at least one conformance group
 129:           SYNTAX     Integer32 (-1 | 0..252)
 130:           MAX-ACCESS read-write
 131:           STATUS     current
 132:           DESCRIPTION
 133:               "This value is derived from the optional
 134:                parameter length minus one (the size of
 135:                bgpAuthenticationCode).  This value may be no
 136:                larger than 252 due to overhead.  This value
 137:                is set to -1 if Authentication is not present."
 138:           ::= { bgpAuthenticationEntry 3 }
 139: 
 140:       bgpAuthenticationDataContents OBJECT-TYPE
 140: error - scalar's parent node must be simple node
 140: change recommended -
warning: node `bgpAuthenticationDataContents' must be contained in at least one conformance group
 141:           SYNTAX     OCTET STRING (SIZE (1..252))
 142:           MAX-ACCESS read-write
 143:           STATUS     current
 144:           DESCRIPTION
 145:               "This is the Authentication payload.  The
 146:                semantics of this variable are interpreted
 147:                according to the authentication code."
 148:           ::= { bgpAuthenticationEntry 4 }
 149: 
 150:       bgpCapabilitySupportAvailable OBJECT-TYPE
 150: change recommended - warning: node `bgpCapabilitySupportAvailable' must be contained in at least one conformance group
 151:           SYNTAX     TruthValue
 152:           MAX-ACCESS read-write
 153:           STATUS     current
 154:           DESCRIPTION
 155:               "This variable determines whether BGP-4
 156:                capabilities are supported in this
 157:                implementation.  This variable may be set to
 158:                false to disable capability support."
 159:           ::= { bgp4OptParametersMIB 2 }
 160: 
 161:       bgpSupportedCapabilities OBJECT-TYPE
 161: change recommended - warning: node `bgpSupportedCapabilities' must be contained in at least one conformance group
 162:           SYNTAX     OCTET STRING (SIZE(0..32)) -- 256 bit vector
 163:           MAX-ACCESS read-only
 164:           STATUS     current
 165:           DESCRIPTION
 166:               "Vector of BGP-4 capabilities that are
 167:                supported in this implementation.  Capabilities
 168:                are identified via the string of bits within
 169:                this object.  The first octet contains bits
 170:                0 to 7, the second octet contains bits 8 to 15
 171:                and so on.  If a bit, i, is present and set,
 172:                then the capability (i+1) is supported.
 173: 
 174:                When capabilities are not supported, all bits
 175:                must be zero."
 176:           ::= { bgp4OptParametersMIB 3 }
 177: 
 178:       bgpPeerCapabilitiesTable OBJECT-TYPE
 179:           SYNTAX     SEQUENCE OF BgpPeerCapabilitiesEntry
 180:           MAX-ACCESS not-accessible
 181:           STATUS     current
 182:           DESCRIPTION
 183:               "This table contains contains the capabilities
 184:                that are supported for a given peer."
 185:           ::= { bgp4OptParametersMIB 4 }
 186: 
 187:       BgpPeerCapabilitiesEntry ::= SEQUENCE {
 187: fyi - info: previous definition of `BgpPeerCapabilitiesEntry'
 188:           bgpPeerCapabilitiesAnnounced
 189:               OCTET STRING,
 190:           bgpPeerCapabilitiesReceived
 191:               OCTET STRING
 192:       }
 193: 
 194:       bgpPeerCapabilitiesEntry OBJECT-TYPE
 194: warning - warning: identifier `bgpPeerCapabilitiesEntry' differs from `BgpPeerCapabilitiesEntry' only in case
 194: error -
subidentifier of row node `bgpPeerCapabilitiesEntry' must be 1

 194: error -
row `bgpPeerCapabilitiesEntry' augments or extends `bgpPeerTable' which is not a row
 195:           SYNTAX     BgpPeerCapabilitiesEntry
 196:           MAX-ACCESS not-accessible
 197:           STATUS     current
 198:           DESCRIPTION
 199:               "These entries are keyed by a BGP-4 peer's remote
 200:                address and port combination over which the
 201:                peering session has been established."
 202:           AUGMENTS { bgpPeerTable }
 202: severe - unknown object identifier label `bgpPeerTable'
 203:           ::= { bgpPeerCapabilitiesTable 2 }
 204: 
 205:       bgpPeerCapabilitiesAnnounced OBJECT-TYPE
 205: change recommended - warning: node `bgpPeerCapabilitiesAnnounced' must be contained in at least one conformance group
 206:           SYNTAX     OCTET STRING (SIZE (0..32))
 207:           MAX-ACCESS read-only
 208:           STATUS     current
 209:           DESCRIPTION
 210:               "This bit vector identifies which capabilities
 211:                have been announced to a BGP-4 speaker.
 212: 
 213:                Capabilities are identified via the string of
 214:                bits within this object.  The first octet
 215:                contains bits 0 to 7, the second octet contains
 216:                bits 8 to 15 and so on.  If a bit, i, is present
 217:                and set, then the capability (i+1) is supported.
 218: 
 219:                When capabilities are not supported, all bits
 220:                must be zero."
 221:       ::= { bgpPeerCapabilitiesEntry 1 }
 222: 
 223: 
 224:       bgpPeerCapabilitiesReceived OBJECT-TYPE
 224: change recommended - warning: node `bgpPeerCapabilitiesReceived' must be contained in at least one conformance group
 225:           SYNTAX     OCTET STRING (SIZE (0..32))
 226:           MAX-ACCESS read-only
 227:           STATUS     current
 228:           DESCRIPTION
 229:               "This bit vector identifies which capabilities have
 230:                 been announced by the remote BGP-4 speaker.
 231: 
 232:                Capabilities are identified via the string of bits
 233:                within this object.  The first octet contains bits 0
 234:                to 7, the second octet contains bits 8 to 15 and so
 235:                on.  If a bit, i, is present and set, then the
 236:                capability (i+1) is supported.
 237: 
 238:                When capabilities are not supported, all bits must
 239:                be zero."
 240:           ::= { bgpPeerCapabilitiesEntry 2 }
 241: 
 242: 
 243:       bgpProtocolExtensions OBJECT-TYPE
 243: change recommended - warning: node `bgpProtocolExtensions' must be contained in at least one conformance group
 244:           SYNTAX     AutonomousType
 245:           MAX-ACCESS read-only
 246:           STATUS     current
 247:           DESCRIPTION
 248:               "Registration point for MIB Modules for BGP
 249:                Protocol Extensions.
 250: 
 251:                The Capabilities Advertisement RFC delineates
 252:                IANA registered capability code numbers, 0-127
 253:                and private use capability code numbers, 128-255.
 254: 
 255:                The first sub-identifier will be the enterprise
 256:                number of the registering entity.  This is used
 257:                to remove the ambiguity of the private use
 258:                portion of the capability code assignments.  For
 259:                IANA registered capability codes 0-127, the first
 260:                sub-identifier will be 0.
 261: 
 262:                The second sub-identifier will be the capability
 263:                code for the advertised capability.
 264: 
 265:                For example, the MPBGP-MIB would be assigned as
 266:                { bgpProtocolStandardExtensions 0 1 } since it
 267:                has been assigned capability code number 1 and
 268:                is an IETF assigned (IANA registered) capability
 269:                extension."
 270:           REFERENCE
 271:               "RFC 2842 - Capabilities Advertisement with BGP-4"
 272:           ::= { bgp4OptParametersMIB 5 }
 273: 
 274: 
 275:       END
 275: error - missing MODULE-IDENTITY clause in SMIv2 MIB