smilint output for ./VPLS-GENERIC-DRAFT-01-MIB


Message Severities
SeverityCount
severe23
error103
minor error2
change recommended21
warning17
Message Types
TypeCount
access-invalid-smiv1 (error)15
basetype-unknown (error)9
defval-syntax (error)6
group-membership (change recommended)3
group-object-status (change recommended)18
group-unref (warning)2
index-illegal-basetype (severe)1
internal-flushing (warning)14
internal-other (severe)14
macro-not-imported (error)35
module-identity-missing (error)1
object-identifier-unknown (severe)8
parent-row (error)1
sequence-no-column (minor error)2
sequence-order (warning)1
status-invalid-smiv1 (error)28
type-unknown (error)8

Messages:

VPLS-GENERIC-DRAFT-01-MIB

   1: -- extracted from draft-nadeau-l2vpn-vpls-mib-03.txt
   2: -- at Fri Feb 16 06:08:13 2007
   3: 
   4:       VPLS-GENERIC-DRAFT-01-MIB DEFINITIONS ::= BEGIN
   5:         draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB        Dec 22, 2006
   5: severe - syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECT
   6: 
   7: 
   8: 
   9:       IMPORTS
  10:       NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
  11:       Unsigned32, Counter32, transmission
  12:          FROM SNMPv2-SMI                    -- RFC2578
  13: 
  14:       MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
  15:          FROM SNMPv2-CONF                   -- RFC2580
  16: 
  17:       TruthValue, RowStatus, StorageType
  18:          FROM SNMPv2-TC                     -- RFC2579
  19: 
  20:       SnmpAdminString
  21:          FROM SNMP-FRAMEWORK-MIB            -- RFC3411
  22: 
  23:        PwIndexType
  24:                FROM PW-TC-STD-MIB
  25: 
  26:         VPNIdOrZero
  27:                FROM VPN-TC-STD-MIB           -- RFC4265
  28: ;
  29:         
  30: 
  31:    vplsGenericDraft01MIB MODULE-IDENTITY
  32:       LAST-UPDATED "200608301200Z"  -- 30 Aug 2006 12:00:00 GMT
  33:       ORGANIZATION "Layer 2 Virtual Private Networks (L2VPN)
  34:                                  Working  Group"
  35:       CONTACT-INFO
  36:           "
  37:            Thomas D. Nadeau
  38:            Email:  tnadeau@cisco.com
  39: 
  40:            The L2VPN Working Group (email distribution l2vpn@ietf.org,
  41:            http://www.ietf.org/html.charters/l2vpn-charter.html)
  42:            "
  43: 
  44:       DESCRIPTION
  45:           "Copyright (C) The Internet Society (2007). The initial
  46:            version of this MIB module was published in RFC XXXX.
  47:    -- RFC Editor: Please replace XXXX with RFC number & remove
  48:    --                    this note.
  49: 
  50:            For full legal notices see the RFC itself or see:
  51:            http://www.ietf.org/copyrights/ianamib.html
  52: 
  53:            This MIB module contains generic managed object definitions
  54:            for Virtual Private LAN Services as in [L2VPN-VPLS-LDP] and
  55:            [L2VPN-VPLS-BGP]
  56: 
  57:         draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB        Dec 22, 2006
  58: 
  59: 
  60: 
  61:            This MIB module enables the use of any underlying Pseudo Wire
  62:            network."
  63: 
  64:       -- Revision history.
  65:       REVISION
  66:           "200608301200Z"  -- 30 August 2006 12:00:00 GMT
  67:       DESCRIPTION
  68:           "Changes from previous version:
  69:            1) Moved LDP Specific information to VPLS-LDP-DRAFT-01-MIB
  70:            2) Created the vplsStatusTable to store status information.
  71:            3)
  72:           "
  73:       REVISION
  74:           "200606041200Z"  -- 4 June 2006 12:00:00 GMT
  75:         
  76: 
  77:       DESCRIPTION "Initial version published as part of RFC YYYY."
  78:    -- RFC Editor: please replace YYYY with IANA assigned value, and
  79:    -- delete this note.
  80: 
  81:          ::= { transmission XXXX }
  81: warning - warning: flushing recent incorrect declaration, see previous error(s)
  82:    -- RFC Editor: please replace XXXX with IANA assigne value, and
  83:    -- delete this note.
  84: 
  85:    -- Top-level components of this MIB.
  86: 
  87:    -- Notifications
  88:    vplsNotifications OBJECT IDENTIFIER
  89:                                  ::= { vplsGenericDraft01MIB 0 }
  89: severe - unknown object identifier label `vplsGenericDraft01MIB'
  90:    -- Tables, Scalars
  91:    vplsObjects       OBJECT IDENTIFIER
  92:                                  ::= { vplsGenericDraft01MIB 1 }
  93:    -- Conformance
  94:    vplsConformance   OBJECT IDENTIFIER
  95:                                  ::= { vplsGenericDraft01MIB 2 }
  96: 
  97:    -- PW Virtual Connection Table
  98: 
  99:    vplsConfigIndexNext OBJECT-TYPE
  99: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 100:       SYNTAX            Unsigned32
 101:       MAX-ACCESS        read-only
 102:       STATUS            current
 102: error - invalid status `current' in SMIv1 MIB
 103:       DESCRIPTION
 104:           "This object contains an appropriate value to be used
 105:            for vplsConfigIndex when creating entries in the
 106:            vplsConfigTable. The value 0 indicates that no
 107:            unassigned entries are available.  To obtain the
 108:            value of vplsConfigIndex for a new entry in the
 109: 
 110:         draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB        Dec 22, 2006
 111: 
 112: 
 113: 
 114:            vplsConfigTable, the manager issues a management
 115:            protocol retrieval operation to obtain the current
 116:            value of vplsConfigIndex.  After each retrieval
 117:            operation, the agent should modify the value to
 118:            reflect the next unassigned index.  After a manager
 119:            retrieves a value the agent will determine through
 120:            its local policy when this index value will be made
 121:            available for reuse."
 122:       ::= { vplsObjects 1 }
 123: 
 124:       vplsConfigTable OBJECT-TYPE
 124: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 125:           SYNTAX          SEQUENCE OF VplsConfigEntry
 125: error - unknown type `VplsConfigEntry'
 126:           MAX-ACCESS      not-accessible
 127:           STATUS          current
 127: error - invalid status `current' in SMIv1 MIB
 128:           DESCRIPTION
 129:                "This table specifies information for configuring
 130:                 and monitoring Virtual Private Lan Services(VPLS).
 131:                 "
 132:           ::= { vplsObjects 2 }
 133: 
 134:       vplsConfigEntry OBJECT-TYPE
 134: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 135:           SYNTAX          VplsConfigEntry
 136:           MAX-ACCESS      not-accessible
 137:           STATUS          current
 137: error - invalid status `current' in SMIv1 MIB
 138:           DESCRIPTION
 139:            "A row in this table represents a Virtual Private Lan
 140:             Service(VPLS) in a packet network. It is indexed by
 141:             vplsConfigIndex, which uniquely identifies a single VPLS.
 142: 
 143:             A row is created by the operator or by the agent if a
 144:             VPLS service is created by non-SNMP application or
 145:             due to autodiscovery process.
 146: 
 147:             None of the read-create objects values can be
 148:             changed when vplsConfigRowStatus is in the active(1)
 149:             state. Changes are allowed when the vplsConfigRowStatus
 150:             is in notInService(2) or notReady(3) states only.
 151:             If the operator need to change one of the values
 152:             for an active row the vplsConfigRowStatus should be
 153:             first changed to notInService(2), the objects may
 154:             be changed now, and later to active(1) in order to
 155:             re-initiate the signaling process with the new
 156:             values in effect.
 157:             "
 158:           INDEX           { vplsConfigIndex }
 159:           ::= { vplsConfigTable 1 }
 160: 
 161:      VplsConfigEntry ::=
 162:         draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB        Dec 22, 2006
 162: severe - syntax error, unexpected LOWERCASE_IDENTIFIER
 163: 
 164: 
 165: 
 166:         SEQUENCE {
 167:          vplsConfigIndex                                Unsigned32,
 168:          vplsConfigName                                 SnmpAdminString,
 169:          vplsConfigDescr                                SnmpAdminString,
 170:          vplsConfigAdminStatus                          INTEGER,
 171:          vplsConfigMacLearning                          TruthValue,
 172:          vplsConfigDiscardUnknownDest                   TruthValue,
 173:          vplsConfigMacAging                             TruthValue,
 174:          vplsConfigFwdFullHighWatermark                 Unsigned32,
 175:          vplsConfigFwdFullLowWatermark                  Unsigned32,
 176:          vplsConfigRowStatus                            RowStatus,
 177:          vplsConfigMtu                                  Unsigned32,
 178:          vplsConfigVpnId                                VPNIdOrZero,
 179:          vplsConfigServiceType                          INTEGER,
 180:          vplsConfigStorageType                          StorageType
 181:           }
 181: warning - warning: flushing recent incorrect declaration, see previous error(s)
 182: 
 183:       vplsConfigIndex  OBJECT-TYPE
 183: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 184:           SYNTAX          Unsigned32 (1.. 2147483647)
 185:         
 186: 
 187:           MAX-ACCESS      not-accessible
 188:           STATUS          current
 188: error - invalid status `current' in SMIv1 MIB
 189:           DESCRIPTION
 190:                "Unique index for the conceptual row identifying
 191:                 a VPLS service."
 192:           ::= { vplsConfigEntry 1 }
 193: 
 194:       vplsConfigName  OBJECT-TYPE
 194: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 194: error - type `SnmpAdminString' of node `vplsConfigName' does not resolve to a known base type
 195:           SYNTAX          SnmpAdminString
 196:           MAX-ACCESS      read-create
 196: error - invalid access `read-create' in SMIv1 MIB
 196: error - unknown type `SnmpAdminString'
 197:           STATUS          current
 197: error - invalid status `current' in SMIv1 MIB
 198:           DESCRIPTION
 199:                "A textual name of the VPLS.
 200:                 If there is no local name, or this object is
 201:                 otherwise not applicable, then this object MUST
 202:                 contain a zero-length octet string."
 203:           DEFVAL           { "" }
 204:           ::= { vplsConfigEntry 2 }
 205: 
 206:       vplsConfigDescr  OBJECT-TYPE
 206: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 206: error - type `SnmpAdminString' of node `vplsConfigDescr' does not resolve to a known base type
 207:           SYNTAX          SnmpAdminString
 208:           MAX-ACCESS      read-create
 208: error - invalid access `read-create' in SMIv1 MIB
 209:           STATUS          current
 209: error - invalid status `current' in SMIv1 MIB
 210:           DESCRIPTION
 211:                "A textual string containing information about the
 212:                VPLS service. If there is no information for this VPLS
 213:                service, then this object MUST contain a zero-length
 214: 
 215:         draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB        Dec 22, 2006
 216: 
 217: 
 218: 
 219:                octet string."
 220:           DEFVAL           { "" }
 221:           ::= { vplsConfigEntry 3 }
 222: 
 223:       vplsConfigAdminStatus OBJECT-TYPE
 223: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 224:           SYNTAX          INTEGER {
 225:                               up(1),
 226:                               down(2),
 227:                               testing(3)   -- in some test mode
 228: 
 229:                           }
 230:           MAX-ACCESS      read-create
 230: error - invalid access `read-create' in SMIv1 MIB
 231:           STATUS          current
 231: error - invalid status `current' in SMIv1 MIB
 232:           DESCRIPTION
 233:                "The desired administrative state of the VPLS
 234:                 service. If the administrative status of the
 235:                 Vpls service is changed to enable then this
 236:                 service is able to utilize the pseudo wire to
 237:                 perform the tasks of a VPLS service.
 238:                 The testing(3) state indicates that no operational
 239:                 packets can be passed. "
 240:         
 241: 
 242:           DEFVAL           { down }
 243:           ::= { vplsConfigEntry 4 }
 244: 
 245:       vplsConfigMacLearning OBJECT-TYPE
 245: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 245: error - type `TruthValue' of node `vplsConfigMacLearning' does not resolve to a known base type
 246:           SYNTAX          TruthValue
 247:           MAX-ACCESS      read-create
 247: error - invalid access `read-create' in SMIv1 MIB
 247: error - unknown type `TruthValue'
 248:           STATUS          current
 248: error - invalid status `current' in SMIv1 MIB
 249:           DESCRIPTION
 250:                "This object specifies if MAC Learning is enabled
 251:                 in this service. If this object is true then Mac
 252:                 Learning is enabled. If false, then Mac Learning is
 253:                 disabled."
 254:           DEFVAL          { true }
 254: error - default value syntax does not match object syntax
 255:           ::= { vplsConfigEntry 6 }
 256: 
 257:       vplsConfigDiscardUnknownDest OBJECT-TYPE
 257: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 258:           SYNTAX          TruthValue
 259:           MAX-ACCESS      read-create
 259: error - invalid access `read-create' in SMIv1 MIB
 260:           STATUS          current
 260: error - invalid status `current' in SMIv1 MIB
 261:           DESCRIPTION
 262:                "If the value of this object is 'true', then frames
 263:                 received with an unknown destination MAC are discarded
 264:                 in this VPLS. If 'false', then the packets are
 265:                 processed."
 266:           DEFVAL          { false }
 266: error - default value syntax does not match object syntax
 267: 
 268:         draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB        Dec 22, 2006
 268: severe - syntax error, unexpected LOWERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
 269: 
 270: 
 271: 
 272:           ::= { vplsConfigEntry 7 }
 272: warning - warning: flushing recent incorrect declaration, see previous error(s)
 273: 
 274:       vplsConfigMacAging OBJECT-TYPE
 274: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 274: error - type `TruthValue' of node `vplsConfigMacAging' does not resolve to a known base type
 275:           SYNTAX          TruthValue
 276:           MAX-ACCESS      read-create
 276: error - invalid access `read-create' in SMIv1 MIB
 277:           STATUS          current
 277: error - invalid status `current' in SMIv1 MIB
 278:           DESCRIPTION
 279:                "If the value of this object is 'true'
 280:                 then the MAC ageing process is enabled in
 281:                 this VPLS. If 'false', then the MAC ageing process
 282:                 is disabled"
 283:           DEFVAL          { true }
 283: error - default value syntax does not match object syntax
 284:           ::= { vplsConfigEntry 8 }
 285: 
 286:       vplsConfigFwdFullHighWatermark OBJECT-TYPE
 286: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 287:           SYNTAX          Unsigned32 (0..100)
 288:           UNITS           "percentage"
 289:           MAX-ACCESS      read-create
 289: error - invalid access `read-create' in SMIv1 MIB
 290:           STATUS          current
 290: error - invalid status `current' in SMIv1 MIB
 291:           DESCRIPTION
 292:         
 293: 
 294:                "This object specifies the utilization of the
 295:                 forwarding database for this VPLS instance at
 296:                 which the vplsFwdFullAlarmRaised notification
 297:                 will be sent."
 298:           DEFVAL          { 95 }
 299:           ::= { vplsConfigEntry 10 }
 300: 
 301:       vplsConfigFwdFullLowWatermark OBJECT-TYPE
 301: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 302:           SYNTAX          Unsigned32 (0..100)
 303:           UNITS           "percentage"
 304:           MAX-ACCESS      read-create
 304: error - invalid access `read-create' in SMIv1 MIB
 305:           STATUS          current
 305: error - invalid status `current' in SMIv1 MIB
 306:           DESCRIPTION
 307:                "This object specifies the utilization of the
 308:                 forwarding database for this VPLS instance
 309:                 at which the vplsFwdFullAlarmCleared
 310:                 notification will be sent."
 311:           DEFVAL          { 90 }
 312:           ::= { vplsConfigEntry 11 }
 313: 
 314:       vplsConfigRowStatus OBJECT-TYPE
 314: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 314: error - type `RowStatus' of node `vplsConfigRowStatus' does not resolve to a known base type
 315:           SYNTAX          RowStatus
 316:           MAX-ACCESS      read-create
 316: error - invalid access `read-create' in SMIv1 MIB
 316: error - unknown type `RowStatus'
 317:           STATUS          current
 317: error - invalid status `current' in SMIv1 MIB
 318:           DESCRIPTION
 319:                "For creating, modifying, and deleting this row.
 320: 
 321:         draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB        Dec 22, 2006
 322: 
 323: 
 324: 
 325:                 None of the read-create objects in the
 326:                 conceptual rows may be changed when this
 327:                 object is in the active(1) state."
 328:           ::= { vplsConfigEntry 12 }
 329: 
 330:       vplsConfigMtu OBJECT-TYPE
 330: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 331:           SYNTAX          Unsigned32 (64..1518)
 332:           MAX-ACCESS      read-create
 332: error - invalid access `read-create' in SMIv1 MIB
 333:           STATUS          current
 333: error - invalid status `current' in SMIv1 MIB
 334:           DESCRIPTION
 335:                "The value of this object specifies the MTU of this
 336:                 vpls instance."
 337:           DEFVAL          { 1518 }
 338:           ::= { vplsConfigEntry 13 }
 339: 
 340:       vplsConfigVpnId OBJECT-TYPE
 340: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 340: error - type `VPNIdOrZero' of node `vplsConfigVpnId' does not resolve to a known base type
 341:           SYNTAX          VPNIdOrZero
 342:           MAX-ACCESS      read-only
 342: error - unknown type `VPNIdOrZero'
 343:           STATUS          current
 343: error - invalid status `current' in SMIv1 MIB
 344:           DESCRIPTION
 345:                "This objects indicates the IEEE 802-1990
 346:                 VPN ID of the associated VPLS service."
 347: -- Ed note: Should we import the VPNIdOrZero TC or
 348: --              define a new TC?
 349:           ::= { vplsConfigEntry 14 }
 350: 
 351:       vplsConfigServiceType OBJECT-TYPE
 351: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 352:           SYNTAX          INTEGER {
 353:                            vlan     (1),
 354:                            ethernet (2)
 355:                           }
 356:           MAX-ACCESS      read-create
 356: error - invalid access `read-create' in SMIv1 MIB
 357:           STATUS          current
 357: error - invalid status `current' in SMIv1 MIB
 358:           DESCRIPTION
 359:                "The value of this object specifies the type of 
 360:                 service emulated by this vpls instance."
 361:           DEFVAL          { vlan }
 362:           ::= { vplsConfigEntry 15 }
 363: 
 364:   vplsConfigStorageType OBJECT-TYPE   
 364: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 364: error - type `StorageType' of node `vplsConfigStorageType' does not resolve to a known base type
 365:           SYNTAX        StorageType  
 366:           MAX-ACCESS    read-create  
 366: error - invalid access `read-create' in SMIv1 MIB
 366: error - unknown type `StorageType'
 367:           STATUS        current  
 367: error - invalid status `current' in SMIv1 MIB
 368:           DESCRIPTION  
 369:                "This variable indicates the storage type for this row."  
 370:           DEFVAL { volatile }
 370: error - default value syntax does not match object syntax
 371:           ::= { vplsConfigEntry 16 }  
 372: 
 373:         draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB        Dec 22, 2006
 373: severe - syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECT
 374: 
 375: 
 376: 
 377: -- VPLS Status table
 378: 
 379:       vplsStatusTable OBJECT-TYPE
 380:           SYNTAX          SEQUENCE OF VplsStatusEntry
 381:           MAX-ACCESS      not-accessible
 382:           STATUS          current
 383:           DESCRIPTION
 384:         
 385: 
 386:                "This table provides information for monitoring
 387:                 Virtual Private Lan Services(VPLS).
 388:                 "
 389:           ::= { vplsObjects 3 }
 389: warning - warning: flushing recent incorrect declaration, see previous error(s)
 390: 
 391:       vplsStatusEntry OBJECT-TYPE
 391: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 391: error - row's parent node must be a table node
 392:           SYNTAX          VplsStatusEntry
 393:           MAX-ACCESS      not-accessible
 394:           STATUS          current
 394: error - invalid status `current' in SMIv1 MIB
 395:           DESCRIPTION
 396:            "A row in this table represents a Virtual Private Lan
 397:             Service(VPLS) in a packet network. It is indexed by
 398:             vplsConfigIndex, which uniquely identifies a single VPLS.
 399: 
 400:             A row in this table is automatically created by the agent
 401:             when a VPLS service is configured.
 402:             "
 403:           INDEX           { vplsConfigIndex }
 404:           ::= { vplsStatusTable 1 }
 404: severe - unknown object identifier label `vplsStatusTable'
 405: 
 406:      VplsStatusEntry ::=
 406: minor error - SEQUENCE element #2 `vplsStatusPeerCount' is not a child node under `vplsStatusEntry'
 407:         SEQUENCE {
 408:          vplsStatusOperStatus                        INTEGER,
 409:          vplsStatusPeerCount                         Counter32
 410:           }
 410: error - unknown type `Counter32'
 410: severe - unknown object identifier label `vplsStatusPeerCount'
 411: 
 412:       vplsStatusOperStatus OBJECT-TYPE
 412: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 413:           SYNTAX          INTEGER {
 414:                               other(0),
 415:                               up(1),
 416:                               down(2)
 417:                           }
 418:           MAX-ACCESS      read-only
 419:           STATUS          current
 419: error - invalid status `current' in SMIv1 MIB
 420:           DESCRIPTION
 421:                "The current operational state of this VPLS Service."
 422:           ::= { vplsStatusEntry 1 }
 423: 
 424:       vplsStatusPeerCount OBJECT-TYPE
 424: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 425:         draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB        Dec 22, 2006
 425: severe - syntax error, unexpected LOWERCASE_IDENTIFIER, expecting SYNTAX
 426: 
 427: 
 428: 
 429:           SYNTAX          Counter32
 430:           MAX-ACCESS      read-only
 431:           STATUS          current
 432:           DESCRIPTION
 433:                "This objects specifies the number of peers
 434:                 present in this vpls instance."
 435:           ::= { vplsStatusEntry 2 }
 435: warning - warning: flushing recent incorrect declaration, see previous error(s)
 436:         
 437: 
 438:       -- VPLS PW Binding Table
 439: 
 440:       vplsPwBindTable OBJECT-TYPE
 440: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 441:           SYNTAX          SEQUENCE OF VplsPwBindEntry
 442:           MAX-ACCESS      not-accessible
 443:           STATUS          current
 443: error - invalid status `current' in SMIv1 MIB
 444:           DESCRIPTION
 445:                "This table provides an association between a
 446:                 VPLS service and the corresponding Pseudo
 447:                 Wires. A service can have more than one Pseudo
 448:                 Wire association. Pseudo Wires are defined in
 449:                 the pwTable"
 450:           ::= { vplsObjects 4 }
 451: 
 452:       vplsPwBindEntry OBJECT-TYPE
 452: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 452: severe - illegal base type `PwIndexType' in index element `vplsPwBindIndex' of row vplsPwBindEntry
 453:           SYNTAX          VplsPwBindEntry
 454:           MAX-ACCESS      not-accessible
 455:           STATUS          current
 455: error - invalid status `current' in SMIv1 MIB
 456:           DESCRIPTION
 457:                "Each row represents an association between a
 458:                 VPLS instance and one or more Pseudo Wires
 459:                 defined in the pwTable. Each index is unique
 460:                 in describing an entry in this table. However
 461:                 both indexes are required to define the one
 462:                 to many association of service to
 463:                 pseudowire."
 464:           INDEX  { vplsConfigIndex, vplsPwBindIndex }
 464: severe - unknown object identifier label `vplsPwBindIndex'
 465:           ::= { vplsPwBindTable 1 }
 466: 
 467:       VplsPwBindEntry ::=
 467: minor error - SEQUENCE element #1 `vplsPwBindIndex' is not a child node under `vplsPwBindEntry'
 467: warning - warning: SEQUENCE element #2 `vplsPwBindConfigType' does not match order of columnar objects under `vplsPwBindEntry'
 468:           SEQUENCE {
 469:               vplsPwBindIndex                     PwIndexType,
 469: error - unknown type `PwIndexType'
 470:               vplsPwBindConfigType              INTEGER,
 471:               vplsPwBindType                  INTEGER,
 472:               vplsPwBindRowStatus             RowStatus,
 472: severe - unknown object identifier label `vplsPwBindRowStatus'
 473:               vplsPwBindStorageType             StorageType
 474:           }
 475: 
 476:       vplsPwBindIndex        OBJECT-TYPE
 476: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 477:         draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB        Dec 22, 2006
 477: severe - syntax error, unexpected LOWERCASE_IDENTIFIER, expecting SYNTAX
 478: 
 479: 
 480: 
 481:            SYNTAX        PwIndexType
 482:            MAX-ACCESS    not-accessible
 483:            STATUS        current
 484:            DESCRIPTION
 485:               "Secondary Index for the conceptual row identifying
 486:                a pseudowire within the PwEntry which MUST
 487:                match an entry from the PW-STD-MIB's PwTable
 488:                which represents an already-provisioned
 489:                pseuwowire that is then associated with this
 490:                VPLS instance."
 491:           ::= { vplsPwBindEntry 1 }
 491: warning - warning: flushing recent incorrect declaration, see previous error(s)
 492: 
 493:       vplsPwBindConfigType   OBJECT-TYPE
 493: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 493: change recommended -
warning: node `vplsPwBindConfigType' must be contained in at least one conformance group
 494:            SYNTAX          INTEGER {
 495:                                    manual        (1),
 496:                                    autodiscovery (2)
 497:                            }
 498:            MAX-ACCESS      read-create
 498: error - invalid access `read-create' in SMIv1 MIB
 499:            STATUS          current
 499: error - invalid status `current' in SMIv1 MIB
 500:            DESCRIPTION
 501:                 "The value of this object indicates
 502:                  whether the Pseudo Wire binding was created
 503:                  manually or via autodiscovery.
 504: 
 505:                  The value of this object must be
 506:                  specifed when the row is created and cannot
 507:                  be changed while the row status is active(1)"
 508:           ::= { vplsPwBindEntry 2 }
 509: 
 510:       vplsPwBindType   OBJECT-TYPE
 510: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 510: change recommended -
warning: node `vplsPwBindType' must be contained in at least one conformance group
 511:            SYNTAX          INTEGER {
 512:                                    mesh  (1),
 513:                                    spoke (2)
 514:                            }
 515:            MAX-ACCESS      read-create
 515: error - invalid access `read-create' in SMIv1 MIB
 516:            STATUS          current
 516: error - invalid status `current' in SMIv1 MIB
 517:            DESCRIPTION
 518:                 "The value of this object indicates
 519:                  whether the Pseudo Wire binding is of
 520:                  type mesh or spoke.
 521: 
 522:                  The value of this object must be
 523:                  specifed when the row is created and cannot
 524:                  be changed while the row status is active(1)"
 525:           ::= { vplsPwBindEntry 3 }
 526: 
 527:       vplsPwBindRowStatus  OBJECT-TYPE
 527: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 528:            SYNTAX          RowStatus
 529: 
 530:         draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB        Dec 22, 2006
 530: severe - syntax error, unexpected LOWERCASE_IDENTIFIER, expecting STATUS
 531: 
 532: 
 533: 
 534:            MAX-ACCESS      read-create
 535:            STATUS          current
 536:            DESCRIPTION
 537:                 "For creating, modifying, and deleting this row.
 538:                  None of the read-create objects in the
 539:                  conceptual rows may be changed when this
 540:                  object is in the active(1) state"
 541:           ::= { vplsPwBindEntry 4 }
 541: warning - warning: flushing recent incorrect declaration, see previous error(s)
 542: 
 543:       vplsPwBindStorageType OBJECT-TYPE   
 543: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 543: error - type `StorageType' of node `vplsPwBindStorageType' does not resolve to a known base type

 543: change recommended -
warning: node `vplsPwBindStorageType' must be contained in at least one conformance group
 544:            SYNTAX        StorageType  
 545:            MAX-ACCESS    read-create 
 545: error - invalid access `read-create' in SMIv1 MIB
 546:            STATUS        current  
 546: error - invalid status `current' in SMIv1 MIB
 547:            DESCRIPTION  
 548:                 "This variable indicates the storage type for this row."  
 549:            DEFVAL { volatile }
 549: error - default value syntax does not match object syntax
 550:            ::= { vplsPwBindEntry 5 }  
 551: 
 552:    vplsStatusNotifEnable  OBJECT-TYPE
 552: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 552: error - type `TruthValue' of node `vplsStatusNotifEnable' does not resolve to a known base type
 553:       SYNTAX      TruthValue
 554:       MAX-ACCESS  read-write
 555:       STATUS      current
 555: error - invalid status `current' in SMIv1 MIB
 556:       DESCRIPTION
 557:            "If this object is set to true(1), then it enables
 558:             the emission of vplsStatusChanged
 559:             notification; otherwise this notification is not
 560:             emitted."
 561:       REFERENCE
 562:            "See also [RFC3413] for explanation that
 563:             notifications are under the ultimate control of the
 564:             MIB module in this document."
 565:       DEFVAL { false }
 565: error - default value syntax does not match object syntax
 566:       ::= { vplsObjects 5 }
 567: 
 568:    vplsNotificationMaxRate OBJECT-TYPE
 568: error - macro `OBJECT-TYPE' has not been imported from module `RFC-1212'
 569:       SYNTAX       Unsigned32
 570:       MAX-ACCESS   read-write
 571:       STATUS       current
 571: error - invalid status `current' in SMIv1 MIB
 572:       DESCRIPTION
 573:            "This object indicates the maximum number of
 574:             notifications issued per second. If events occur
 575:             more rapidly, the implementation may simply fail to
 576:             emit these notifications during that period, or may
 577:             queue them until an appropriate time. A value of 0
 578:             means no throttling is applied and events may be
 579:             notified at the rate at which they occur."
 580:       DEFVAL       { 0 }
 581:       ::= { vplsObjects 6 }
 582:         draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB        Dec 22, 2006
 582: severe - syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECT
 583: 
 584: 
 585: 
 586: 
 587:       -- VPLS Service Notifications
 588: 
 589:       vplsStatusChanged NOTIFICATION-TYPE
 590:           OBJECTS {
 591:               vplsConfigVpnId,
 592:               vplsConfigAdminStatus,
 593:               vplsStatusOperStatus
 594:           }
 594: warning - warning: flushing recent incorrect declaration, see previous error(s)
 595:           STATUS          current
 595: severe - syntax error, unexpected STATUS
 596:           DESCRIPTION
 597:                "The vplsStatusChanged notification is generated
 598:                 when there is a change in the administrative or
 599:                 operating status of a VPLS service."
 600:           ::= { vplsNotifications 1 }
 600: warning - warning: flushing recent incorrect declaration, see previous error(s)
 601: 
 602:       vplsFwdFullAlarmRaised NOTIFICATION-TYPE
 602: error - macro `NOTIFICATION-TYPE' has not been imported from module `SNMPv2-SMI'
 603:           OBJECTS {
 604:               vplsConfigVpnId,
 605:               vplsConfigFwdFullHighWatermark,
 606:               vplsConfigFwdFullLowWatermark
 607:           }
 608:           STATUS          current
 608: error - invalid status `current' in SMIv1 MIB
 609:           DESCRIPTION
 610:                "The vplsFwdFullAlarmRaised notification is
 611:                 generated when the utilization of the Forwarding
 612:                 database is above the value specified by
 613:                 vplsConfigFwdFullHighWatermark."
 614:           ::= { vplsNotifications 2 }
 615: 
 616:       vplsFwdFullAlarmCleared NOTIFICATION-TYPE
 616: error - macro `NOTIFICATION-TYPE' has not been imported from module `SNMPv2-SMI'
 617:           OBJECTS {
 618:               vplsConfigVpnId,
 619:               vplsConfigFwdFullHighWatermark,
 620:               vplsConfigFwdFullLowWatermark
 621:           }
 622:           STATUS          current
 622: error - invalid status `current' in SMIv1 MIB
 623:           DESCRIPTION
 624:                "The vplsFwdFullAlarmCleared notification is
 625:                 generated when the utilization of the Forwarding
 626:                 database is below the value specified by
 627:                 vplsConfigFwdFullLowWatermark."
 628:           ::= { vplsNotifications 3 }
 629: 
 630:    -- Compliance requirement for read-only implementations.
 631: 
 632:    vplsCompliances
 633:      OBJECT IDENTIFIER ::= { vplsConformance 1 }
 634:         draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB        Dec 22, 2006
 634: severe - syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECT
 635: 
 636: 
 637: 
 638: 
 639:    vplsModuleFullCompliance MODULE-COMPLIANCE
 640:       STATUS current
 641:       DESCRIPTION
 642:            "Compliance requirement for implementations that
 643:             provide full support for VPLS-GENERIC-DRAFT-01-MIB.
 644:             Such devices can then be monitored and configured using 
 645:             this MIB module."
 646:       MODULE -- this module
 647: 
 648:           MANDATORY-GROUPS {
 649:                vplsGroup,
 650:                vplsPwBindGroup,
 651:                vplsNotificationGroup
 652:            }
 652: warning - warning: flushing recent incorrect declaration, see previous error(s)
 653: 
 654:       ::= { vplsCompliances 1 }
 654: severe - syntax error, unexpected COLON_COLON_EQUAL
 654: warning - warning: flushing recent incorrect declaration, see previous error(s)
 655: 
 656: 
 657:    vplsModuleReadOnlyCompliance MODULE-COMPLIANCE
 657: error - macro `MODULE-COMPLIANCE' has not been imported from module `SNMPv2-CONF'
 658:       STATUS current
 659:       DESCRIPTION
 660:            "Compliance requirement for implementations that only
 661:             provide read-only support for VPLS-GENERIC-DRAFT-01-MIB.
 662:             Such devices can then be monitored but cannot be
 663:             configured using this MIB modules."
 664: 
 665:       MODULE -- this module
 666: 
 667:           MANDATORY-GROUPS {
 668:                vplsGroup,
 669:                vplsPwBindGroup,
 669: severe - unknown object identifier label `vplsPwBindGroup'
 670:                vplsNotificationGroup
 671:            }
 672: 
 673:            OBJECT          vplsConfigName
 674:            MIN-ACCESS      read-only
 675:            DESCRIPTION
 676:                "Write access is not required."
 677:     
 678: 
 679:            OBJECT          vplsConfigDescr
 680:            MIN-ACCESS      read-only
 681:            DESCRIPTION
 682:                "Write access is not required."
 683: 
 684:            OBJECT          vplsConfigAdminStatus
 685:            MIN-ACCESS      read-only
 686: 
 687:         draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB        Dec 22, 2006
 687: severe - syntax error, unexpected LOWERCASE_IDENTIFIER, expecting DESCRIPTION
 688: 
 689: 
 690: 
 691:            DESCRIPTION
 692:                "Write access is not required."
 693: 
 694:            OBJECT          vplsConfigMacLearning
 695:            MIN-ACCESS      read-only
 696:            DESCRIPTION
 697:                "Write access is not required."
 698: 
 699:            OBJECT          vplsConfigDiscardUnknownDest
 700:            MIN-ACCESS      read-only
 701:            DESCRIPTION
 702:                "Write access is not required."
 703: 
 704:            OBJECT          vplsConfigMacAging
 705:            MIN-ACCESS      read-only
 706:            DESCRIPTION
 707:                "Write access is not required."
 708: 
 709:            OBJECT          vplsConfigFwdFullHighWatermark
 710:            MIN-ACCESS      read-only
 711:            DESCRIPTION
 712:                "Write access is not required."
 713: 
 714:            OBJECT          vplsConfigFwdFullLowWatermark
 715:            MIN-ACCESS      read-only
 716:            DESCRIPTION
 717:                "Write access is not required."
 718: 
 719:            OBJECT          vplsConfigRowStatus
 720:            MIN-ACCESS      read-only
 721:            DESCRIPTION
 722:                "Write access is not required."
 723: 
 724:            OBJECT          vplsConfigMtu
 725:            MIN-ACCESS      read-only
 726:            DESCRIPTION
 727:                "Write access is not required."
 728: 
 729:            OBJECT          vplsConfigServiceType
 730:            MIN-ACCESS      read-only
 731:            DESCRIPTION
 732:                "Write access is not required."
 733: 
 734:            OBJECT          vplsPwBindConfigType
 735:            MIN-ACCESS      read-only
 736:            DESCRIPTION
 737:                "Write access is not required."
 738: 
 739:         draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB        Dec 22, 2006
 740: 
 741: 
 742: 
 743:            OBJECT          vplsPwBindType
 744:            MIN-ACCESS      read-only
 745:            DESCRIPTION
 746:                "Write access is not required."
 747: 
 748:            OBJECT          vplsPwBindRowStatus
 749:            MIN-ACCESS      read-only
 750:            DESCRIPTION
 751:                "Write access is not required."
 752: 
 753:       ::= { vplsCompliances 2 }
 753: warning - warning: flushing recent incorrect declaration, see previous error(s)
 754: 
 755: -- Units of conformance.
 756: 
 757:       vplsGroups
 758:         OBJECT IDENTIFIER ::= { vplsConformance 2 }
 759:         
 760: 
 761:       vplsGroup OBJECT-GROUP
 761: error - macro `OBJECT-GROUP' has not been imported from module `SNMPv2-CONF'
 761: change recommended -
warning: current group `vplsGroup' includes mandatory object `vplsConfigName'

 761: change recommended -
warning: current group `vplsGroup' includes mandatory object `vplsConfigDescr'

 761: change recommended -
warning: current group `vplsGroup' includes mandatory object `vplsConfigAdminStatus'

 761: change recommended -
warning: current group `vplsGroup' includes mandatory object `vplsConfigMacLearning'

 761: change recommended -
warning: current group `vplsGroup' includes mandatory object `vplsConfigMacAging'

 761: change recommended -
warning: current group `vplsGroup' includes mandatory object `vplsConfigVpnId'

 761: change recommended -
warning: current group `vplsGroup' includes mandatory object `vplsConfigFwdFullHighWatermark'

 761: change recommended -
warning: current group `vplsGroup' includes mandatory object `vplsConfigFwdFullLowWatermark'

 761: change recommended -
warning: current group `vplsGroup' includes mandatory object `vplsConfigRowStatus'

 761: change recommended -
warning: current group `vplsGroup' includes mandatory object `vplsConfigIndexNext'

 761: change recommended -
warning: current group `vplsGroup' includes mandatory object `vplsConfigMtu'

 761: change recommended -
warning: current group `vplsGroup' includes mandatory object `vplsConfigServiceType'

 761: change recommended -
warning: current group `vplsGroup' includes mandatory object `vplsConfigStorageType'

 761: change recommended -
warning: current group `vplsGroup' includes mandatory object `vplsStatusOperStatus'

 761: change recommended -
warning: current group `vplsGroup' includes mandatory object `vplsStatusNotifEnable'

 761: change recommended -
warning: current group `vplsGroup' includes mandatory object `vplsNotificationMaxRate'

 761: warning - warning: current group `vplsGroup' is not referenced in this module
 762:           OBJECTS {
 763:               vplsConfigName,
 764:               vplsConfigDescr,
 765:               vplsConfigAdminStatus,
 766:               vplsConfigMacLearning,
 767:               vplsConfigDiscardUnknownDest,
 767: severe - unknown object identifier label `vplsConfigDiscardUnknownDest'
 768:               vplsConfigMacAging,
 769:               vplsConfigVpnId,
 770:               vplsConfigFwdFullHighWatermark,
 771:               vplsConfigFwdFullLowWatermark,
 772:               vplsConfigRowStatus,
 773:               vplsConfigIndexNext,
 774:               vplsConfigMtu,
 775:               vplsConfigServiceType,
 776:               vplsConfigStorageType,
 777: 
 778:               vplsStatusOperStatus,
 779:               vplsStatusPeerCount,
 780: 
 781:               vplsStatusNotifEnable,
 782:               vplsNotificationMaxRate
 783:           }
 784:           STATUS          current
 785:           DESCRIPTION
 786:                "The group of objects supporting
 787:                 management of L2VPN VPLS services"
 788:           ::= { vplsGroups 1 }
 789: 
 790:       vplsPwBindGroup OBJECT-GROUP
 790: error - macro `OBJECT-GROUP' has not been imported from module `SNMPv2-CONF'
 791:         draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB        Dec 22, 2006
 791: severe - syntax error, unexpected LOWERCASE_IDENTIFIER, expecting OBJECTS
 792: 
 793: 
 794: 
 795:           OBJECTS {
 796:               vplsPwBindConfigType,
 797:               vplsPwBindType,
 798:               vplsPwBindRowStatus,
 799:               vplsPwBindStorageType
 800:           }
 800: warning - warning: flushing recent incorrect declaration, see previous error(s)
 801:           STATUS          current
 801: severe - syntax error, unexpected STATUS
 802:           DESCRIPTION
 803:                "The group of objects supporting
 804:                 management of
 805:                 Pseudo Wire (PW) Binding to VPLS."
 806:           ::= { vplsGroups 2 }
 806: warning - warning: flushing recent incorrect declaration, see previous error(s)
 807: 
 808:       vplsNotificationGroup NOTIFICATION-GROUP
 808: error - macro `NOTIFICATION-GROUP' has not been imported from module `SNMPv2-CONF'
 808: change recommended -
warning: current group `vplsNotificationGroup' includes mandatory object `vplsFwdFullAlarmRaised'

 808: change recommended -
warning: current group `vplsNotificationGroup' includes mandatory object `vplsFwdFullAlarmCleared'

 808: warning - warning: current group `vplsNotificationGroup' is not referenced in this module
 809:           NOTIFICATIONS   {
 810:               vplsStatusChanged,
 810: severe - unknown object identifier label `vplsStatusChanged'
 811:               vplsFwdFullAlarmRaised,
 812:               vplsFwdFullAlarmCleared
 813:           }
 814:           STATUS          current
 815:           DESCRIPTION
 816:                "The group of notifications supporting
 817:                 the  Notifications generated for
 818:                 VPLS Services"
 819:           ::= { vplsGroups 3 }
 820:         
 821: 
 822:        END
 822: error - missing MODULE-IDENTITY clause in SMIv2 MIB
 823: 
 824: -- 
 825: --    Copyright (C) The IETF Trust (2007).
 826: -- 
 827: --    Copyright (C) The Internet Society (2007). This document is subject
 828: --    to the rights, licenses and restrictions contained in BCP 78, and
 829: --    except as set forth therein, the authors retain all their rights.
 830: -- 
 831: --    This document and the information contained herein are provided on an
 832: --    "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
 833: --    OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
 834: --    ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
 835: --    INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
 836: --    INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
 837: --    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 838: