smilint output for ./MPLS-LDP-ATM-MIB


Message Severities
SeverityCount
error2
Message Types
TypeCount
bad-identifier-case (error)1
object-identifier-not-prefix (error)1

Messages:

MPLS-LDP-ATM-MIB

   1: -- extracted from draft-ietf-mpls-ldp-mib-10.txt
   2: -- at Fri May  2 06:12:55 2003
   3: 
   4:    MPLS-LDP-ATM-MIB DEFINITIONS ::= BEGIN
   5: 
   6: 
   7:    IMPORTS
   8:        OBJECT-TYPE, MODULE-IDENTITY,
   9:        Unsigned32
  10:            FROM SNMPv2-SMI
  11:        MODULE-COMPLIANCE, OBJECT-GROUP
  12:            FROM SNMPv2-CONF
  13: 
  14:        RowStatus,
  15:        StorageType
  16:            FROM SNMPv2-TC
  17: 
  18:        InterfaceIndexOrZero
  19:            FROM IF-MIB
  20: 
  21:        AtmVpIdentifier
  22:            FROM ATM-TC-MIB
  23: 
  24:        mplsMIB,
  25:        MplsAtmVcIdentifier
  26:            FROM MPLS-TC-MIB
  27: 
  28:        mplsLdpEntityLdpId,
  29:        mplsLdpEntityIndex,
  30:        mplsLdpPeerLdpId
  31:            FROM MPLS-LDP-MIB
  32: 
  33:        ;
  34: 
  35: 
  36:    mplsLdpAtmMIB MODULE-IDENTITY
  37:        LAST-UPDATED "200304221200Z"  -- 22 April 2003
  38:        ORGANIZATION "Multiprotocol Label Switching (mpls)
  39:                      Working Group"
  40:        CONTACT-INFO
  41:            "Joan Cucchiara (jcucchiara@artel.com)
  42:             Artel
  43: 
  44:             Hans Sjostrand (hans@ipunplugged.com)
  45:             ipUnplugged
  46: 
  47:             James V. Luciani (james_luciani@mindspring.com)
  48:             Consultant
  49: 
  50:             Working Group Chairs:
  51:             George Swallow,   email: swallow@cisco.com
  52:             Loa Andersson,    email: loa@pi.se
  53: 
  54:             MPLS Working Group, email: mpls@uu.net
  55:        "
  56:        DESCRIPTION
  57:            "Copyright (C) The Internet Society (2003).  This
  58:            version of this MIB module is part of RFCXXX; see
  59:            the RFC itself for full legal notices.
  60: 
  61:            This MIB contains managed object definitions for
  62:            configuring and monitoring the Multiprotocol Label
  63:            Switching (MPLS), Label Distribution Protocol (LDP),
  64:            utilizing Asynchronous Transfer Mode (ATM) as the Layer 2
  65:            media."
  66:        REVISION "200304221200Z"  -- 22 April 2003
  67:        DESCRIPTION
  68:            "Initial version published as part of RFC XXXX."
  69: 
  70:        -- Please see the IANA Considerations Section
  71:        -- the suggested mplsMIB subId is 5, e.g.
  72:        --  ::= { mplsMIB 5 }
  73: 
  74:        ::= { mplsMIB XXX } -- to be assigned by IANA
  74: error - `XXX' should start with a lower case letter
  74: error - Object identifier element `XXX' name only allowed as first element
  75: 
  76:    --****************************************************************
  77:    mplsLdpAtmObjects       OBJECT IDENTIFIER ::= { mplsLdpAtmMIB 1 }
  78:    mplsLdpAtmConformance   OBJECT IDENTIFIER ::= { mplsLdpAtmMIB 2 }
  79: 
  80:    --****************************************************************
  81:    -- MPLS LDP ATM Objects
  82:    --****************************************************************
  83: 
  84:    --
  85:    -- Ldp Entity Objects for ATM
  86:    --
  87: 
  88:    mplsLdpEntityAtmObjects  OBJECT IDENTIFIER ::=
  89:                                  { mplsLdpAtmObjects 1 }
  90: 
  91:    mplsLdpEntityAtmTable  OBJECT-TYPE
  92:        SYNTAX      SEQUENCE OF MplsLdpEntityAtmEntry
  93:        MAX-ACCESS  not-accessible
  94:        STATUS      current
  95:        DESCRIPTION
  96:            "This table contains information about the
  97:            ATM specific information which could be used
  98:            in the 'Optional Parameters' and other ATM specific
  99:            information.
 100: 
 101:            This table 'extends' the mplsLdpEntityTable when
 102:            ATM as the Layer 2 media."
 103:        ::= { mplsLdpEntityAtmObjects 1 }
 104: 
 105:    mplsLdpEntityAtmEntry OBJECT-TYPE
 106:        SYNTAX      MplsLdpEntityAtmEntry
 107:        MAX-ACCESS  not-accessible
 108:        STATUS      current
 109:        DESCRIPTION
 110:            "An entry in this table represents the ATM parameters
 111:            and ATM information for this LDP entity."
 112:        INDEX       {  mplsLdpEntityLdpId,
 113:                       mplsLdpEntityIndex
 114:                    }
 115:        ::= { mplsLdpEntityAtmTable 1 }
 116: 
 117: 
 118:    MplsLdpEntityAtmEntry ::= SEQUENCE {
 119:        mplsLdpEntityAtmIfIndexOrZero        InterfaceIndexOrZero,
 120:        mplsLdpEntityAtmMergeCap             INTEGER,
 121:        mplsLdpEntityAtmLRComponents         Unsigned32,
 122:        mplsLdpEntityAtmVcDirectionality     INTEGER,
 123:        mplsLdpEntityAtmLsrConnectivity      INTEGER,
 124:        mplsLdpEntityAtmDefaultControlVpi    AtmVpIdentifier,
 125:        mplsLdpEntityAtmDefaultControlVci    MplsAtmVcIdentifier,
 126:        mplsLdpEntityAtmUnlabTrafVpi         AtmVpIdentifier,
 127:        mplsLdpEntityAtmUnlabTrafVci         MplsAtmVcIdentifier,
 128:        mplsLdpEntityAtmStorageType          StorageType,
 129:        mplsLdpEntityAtmRowStatus            RowStatus
 130:    }
 131: 
 132: 
 133:    mplsLdpEntityAtmIfIndexOrZero  OBJECT-TYPE
 134:        SYNTAX      InterfaceIndexOrZero
 135:        MAX-ACCESS  read-create
 136:        STATUS      current
 137:        DESCRIPTION
 138:           "This value represents either the InterfaceIndex of
 139:           the 'ifLayer' where the ATM Labels 'owned' by this
 140:           entry were created, or 0 (zero).  The value of zero
 141:           means that the InterfaceIndex is not known.  For example,
 142:           if the InterfaceIndex is created subsequent to the
 143:           ATM Label's creation, then it would not be known.
 144:           However, if the InterfaceIndex is known, then it must
 145:           be represented by this value.
 146: 
 147:           If an InterfaceIndex becomes known, then the
 148:           network management entity (e.g. SNMP agent) responsible
 149:           for this object MUST change the value from 0 (zero) to the
 150:           value of the InterfaceIndex.  If an ATM Label is
 151:           being used in forwarding data, then the value of this
 152:           object MUST be the InterfaceIndex."
 153:        ::= { mplsLdpEntityAtmEntry 1 }
 154: 
 155: 
 156:    mplsLdpEntityAtmMergeCap OBJECT-TYPE
 157:        SYNTAX      INTEGER {
 158:                        notSupported(0),
 159:                        vpMerge(1),
 160:                        vcMerge(2),
 161:                        vpAndVcMerge(3)
 162:                    }
 163:        MAX-ACCESS  read-create
 164:        STATUS      current
 165:        DESCRIPTION
 166:            "Denotes the Merge Capability of this Entity.
 167:            This is the EXACT value for the ATM Session Parameter,
 168:            field M (for ATM Merge Capabilities).  The ATM Session Parameter
 169:            is an optional parameter in the Initialization Message.
 170: 
 171:            The description from rfc3036.txt is:
 172: 
 173:            'M, ATM Merge Capabilities
 174:               Specifies the merge capabilities of an ATM switch.  The
 175:               following values are supported in this version of the
 176:               specification:
 177: 
 178:                      Value          Meaning
 179: 
 180:                        0            Merge not supported
 181:                        1            VP Merge supported
 182:                        2            VC Merge supported
 183:                        3            VP & VC Merge supported
 184: 
 185:               If the merge capabilities of the LSRs differ, then:
 186:               -  Non-merge and VC-merge LSRs may freely interoperate.
 187: 
 188:               -  The interoperability of VP-merge-capable switches with non-
 189:                  VP-merge-capable switches is a subject for future study.
 190:                  When the LSRs differ on the use of VP-merge, the session is
 191:                  established, but VP merge is not used.'
 192: 
 193:               Please refer to the following reference for a complete
 194:               description of this feature."
 195:         REFERENCE
 196:            "[RFC3036] LDP Specification, Section 3.5.3 Initialization Message."
 197:        ::= { mplsLdpEntityAtmEntry 2 }
 198: 
 199:    mplsLdpEntityAtmLRComponents OBJECT-TYPE
 200:        SYNTAX      Unsigned32 (1..65535)
 201:        MAX-ACCESS  read-create
 202:        STATUS      current
 203:        DESCRIPTION
 204:            "Number of Label Range Components in the Initialization
 205:            message.  This also represents the number of entries
 206:            in the mplsLdpEntityAtmLRTable which correspond
 207:            to this entry.
 208: 
 209:            This is the EXACT value for the ATM Session Parameter,
 210:            field N (for Number of label range components).  The ATM
 211:            Session Parameter is an optional parameter in the Initialization
 212:            Message.
 213: 
 214:            The description from rfc3036.txt is:
 215:            'N, Number of label range components
 216:               Specifies the number of ATM Label Range Components
 217:               included in the TLV.'
 218: 
 219:             Please refer to the following reference for a complete
 220:             description of this feature."
 221:         REFERENCE
 222:            "[RFC3036] LDP Specification, Section 3.5.3 Initialization Message."
 223:        ::= { mplsLdpEntityAtmEntry 3 }
 224: 
 225:    mplsLdpEntityAtmVcDirectionality OBJECT-TYPE
 226:        SYNTAX      INTEGER {
 227:                               bidirectional(0),
 228:                               unidirectional(1)
 229:                            }
 230:        MAX-ACCESS  read-create
 231:        STATUS      current
 232:        DESCRIPTION
 233:            "If the value of this object is 'bidirectional(0)',
 234:            a given VCI, within a given VPI, is used as a
 235:            label for both directions independently.
 236: 
 237:            If the value of this object is 'unidirectional(1)',
 238:            a given VCI within a VPI designates one direction.
 239: 
 240:            This is the EXACT value for the ATM Session Parameter,
 241:            field D (for VC Directionality).  The ATM Session Parameter
 242:            is an optional parameter in the Initialization Message.
 243: 
 244:            The description from rfc3036.txt is:
 245: 
 246: 
 247:            'D, VC Directionality
 248:               A value of 0 specifies bidirectional VC capability, meaning the
 249:               LSR can (within a given VPI) support the use of a given VCI as
 250:               a label for both link directions independently.  A value of 1
 251:               specifies unidirectional VC capability, meaning (within a given
 252:               VPI) a given VCI may appear in a label mapping for one
 253:               direction on the link only.  When either or both of the peers
 254:               specifies unidirectional VC capability, both LSRs use
 255:               unidirectional VC label assignment for the link as follows.
 256:               The LSRs compare their LDP Identifiers as unsigned integers.
 257:               The LSR with the larger LDP Identifier may assign only odd-
 258:               numbered VCIs in the VPI/VCI range as labels.  The system with
 259:               the smaller LDP Identifier may assign only even-numbered VCIs
 260:               in the VPI/VCI range as labels.'
 261:               Please refer to the following reference for a complete
 262:               description of this feature."
 263:         REFERENCE
 264:            "[RFC3036] LDP Specification, Section 3.5.3 Initialization Message."
 265:        ::= { mplsLdpEntityAtmEntry 4 }
 266: 
 267:    mplsLdpEntityAtmLsrConnectivity OBJECT-TYPE
 268:        SYNTAX      INTEGER {
 269:                       direct(1),
 270:                       indirect(2)
 271:                    }
 272:        MAX-ACCESS  read-create
 273:        STATUS      current
 274:        DESCRIPTION
 275:            "The peer LSR may be connected indirectly by means of an
 276:            ATM VP so that the VPI values may be different on either
 277:            endpoint so the label MUST be encoded entirely within the
 278:            VCI field."
 279:        DEFVAL { direct }
 280:        ::= { mplsLdpEntityAtmEntry 5 }
 281: 
 282:    mplsLdpEntityAtmDefaultControlVpi OBJECT-TYPE
 283:        SYNTAX      AtmVpIdentifier
 284:        MAX-ACCESS  read-create
 285:        STATUS      current
 286:        DESCRIPTION
 287:            "The default VPI value for the non-MPLS connection.  The
 288:            default value of this is 0 (zero) but other values may
 289:            be configured.  This object allows a different value
 290:            to be configured."
 291:        DEFVAL { 0 }
 292:        ::= { mplsLdpEntityAtmEntry 6 }
 293: 
 294:    mplsLdpEntityAtmDefaultControlVci OBJECT-TYPE
 295:        SYNTAX      MplsAtmVcIdentifier
 296:        MAX-ACCESS  read-create
 297:        STATUS      current
 298:        DESCRIPTION
 299:            "The Default VCI value for a non-MPLS connection.  The
 300:            default value of this is 32 but other values may be
 301:            configured.  This object allows a different value to
 302:            be configured."
 303:        DEFVAL { 32 }
 304:        ::= { mplsLdpEntityAtmEntry 7 }
 305: 
 306:    mplsLdpEntityAtmUnlabTrafVpi OBJECT-TYPE
 307:        SYNTAX      AtmVpIdentifier
 308:        MAX-ACCESS  read-create
 309:        STATUS      current
 310:        DESCRIPTION
 311:            "VPI value of the VCC supporting unlabeled traffic.  This
 312:            non-MPLS connection is used to carry unlabeled (IP)
 313:            packets.  The default value is the same as the default
 314:            value of the 'mplsLdpEntityAtmDefaultControlVpi', however
 315:            another value may be configured."
 316:        DEFVAL  { 0 }
 317:        ::= { mplsLdpEntityAtmEntry 8 }
 318: 
 319:    mplsLdpEntityAtmUnlabTrafVci OBJECT-TYPE
 320:        SYNTAX      MplsAtmVcIdentifier
 321:        MAX-ACCESS  read-create
 322:        STATUS      current
 323:        DESCRIPTION
 324:            "VCI value of the VCC supporting unlabeled traffic.
 325:            This non-MPLS connection is used to carry unlabeled (IP)
 326:            packets. The default value is the same as the default
 327:            value of the 'mplsLdpEntityAtmDefaultControlVci', however
 328:            another value may be configured."
 329:        DEFVAL  { 32 }
 330:        ::= { mplsLdpEntityAtmEntry 9 }
 331: 
 332:    mplsLdpEntityAtmStorageType  OBJECT-TYPE
 333:        SYNTAX      StorageType
 334:        MAX-ACCESS  read-create
 335:        STATUS      current
 336:        DESCRIPTION
 337:            "The storage type for this conceptual row.  Conceptual rows
 338:            having the value 'permanent(4)' MAY allow write-access to any
 339:            columnar objects in the row, except for setting the
 340:            mplsLdpEntityAtmRowStatus to 'destroy(6)'."
 341:        DEFVAL { nonVolatile }
 342:        ::= { mplsLdpEntityAtmEntry 10 }
 343: 
 344:    mplsLdpEntityAtmRowStatus OBJECT-TYPE
 345:        SYNTAX      RowStatus
 346:        MAX-ACCESS  read-create
 347:        STATUS      current
 348:        DESCRIPTION
 349:            "The status of this conceptual row.  All writable objects in this
 350:             row may be modified at any time, however, as described in
 351:             detail in the section entitled, 'Changing Values After Session
 352:             Establishment', and again described in the
 353:             DESCRIPTION clause of the mplsLdpEntityAdminStatus object,
 354:             if a session has been initiated with a Peer,
 355:             changing objects in this table will
 356:             wreak havoc with the session and interrupt traffic.  To repeat again:
 357:             the recommended procedure is to set the mplsLdpEntityAdminStatus to
 358:             down, thereby explicitely causing a session to be torn down. Then,
 359:             change objects in this entry, then set the mplsLdpEntityAdminStatus
 360:             to enable which enables a NEW session to be initiated.
 361: 
 362:             NOTE:  This RowStatus object should
 363:             have the same value of the 'mplsLdpEntityRowStatus'
 364:             related to this entry."
 365:        ::= { mplsLdpEntityAtmEntry 11 }
 366: 
 367:    --
 368:    -- The MPLS LDP Entity ATM Label Range Table
 369:    --
 370: 
 371:    mplsLdpEntityAtmLRTable OBJECT-TYPE
 372:        SYNTAX SEQUENCE OF MplsLdpEntityAtmLREntry
 373:        MAX-ACCESS not-accessible
 374:        STATUS current
 375:        DESCRIPTION
 376:            "The MPLS LDP Entity ATM Label Range (LR) Table.
 377:            The purpose of this table is to provide a mechanism
 378:            for configuring a contiguous range of vpi's
 379:            with a contiguous range of vci's, or a 'label range'
 380:            for LDP Entities.
 381: 
 382:            LDP Entities which use ATM must have at least one
 383:            entry in this table."
 384:        ::= { mplsLdpEntityAtmObjects 2 }
 385: 
 386:    mplsLdpEntityAtmLREntry OBJECT-TYPE
 387:        SYNTAX MplsLdpEntityAtmLREntry
 388:        MAX-ACCESS not-accessible
 389:        STATUS current
 390:        DESCRIPTION
 391:            "A row in the LDP Entity ATM Label
 392:            Range Table.  One entry in this table contains
 393:            information on a single range of labels
 394:            represented by the configured Upper and Lower
 395:            Bounds VPI/VCI pairs.  These are the same
 396:            data used in the Initialization Message.
 397: 
 398:            NOTE:  The ranges for a specific LDP Entity
 399:            are UNIQUE and non-overlapping.  For example,
 400:            for a specific LDP Entity index, there could
 401:            be one entry having LowerBound vpi/vci == 0/32, and
 402:            UpperBound vpi/vci == 0/100, and a second entry
 403:            for this same interface with LowerBound
 404:            vpi/vci == 0/101 and UpperBound vpi/vci == 0/200.
 405:            However, there could not be a third entry with
 406:            LowerBound vpi/vci == 0/200 and
 407:            UpperBound vpi/vci == 0/300 because this label
 408:            range overlaps with the second entry (i.e. both
 409:            entries now have 0/200).
 410: 
 411:            A row will not be created unless a unique and
 412:            non-overlapping range is specified.  Thus, row
 413:            creation implies a one-shot row creation of
 414:            LDP EntityID and LowerBound vpi/vci and
 415:            UpperBound vpi/vci.  At least one label
 416:            range entry for a specific LDP Entity MUST
 417:            include the default VPI/VCI  values denoted
 418:            in the LDP Entity Table."
 419:        INDEX       {  mplsLdpEntityLdpId,
 420:                       mplsLdpEntityIndex,
 421:                       mplsLdpEntityAtmLRMinVpi,
 422:                       mplsLdpEntityAtmLRMinVci
 423:                    }
 424:        ::= { mplsLdpEntityAtmLRTable 1 }
 425: 
 426:    MplsLdpEntityAtmLREntry ::= SEQUENCE {
 427:        mplsLdpEntityAtmLRMinVpi       AtmVpIdentifier,
 428:        mplsLdpEntityAtmLRMinVci       MplsAtmVcIdentifier,
 429:        mplsLdpEntityAtmLRMaxVpi       AtmVpIdentifier,
 430:        mplsLdpEntityAtmLRMaxVci       MplsAtmVcIdentifier,
 431:        mplsLdpEntityAtmLRStorageType  StorageType,
 432:        mplsLdpEntityAtmLRRowStatus    RowStatus
 433:    }
 434: 
 435:    mplsLdpEntityAtmLRMinVpi OBJECT-TYPE
 436:        SYNTAX AtmVpIdentifier
 437:        MAX-ACCESS not-accessible
 438:        STATUS current
 439:        DESCRIPTION
 440:            "The minimum VPI number configured for this range.
 441:            The value of zero is a valid value for the VPI portion
 442:            of the label."
 443:        ::= { mplsLdpEntityAtmLREntry 1 }
 444: 
 445:    mplsLdpEntityAtmLRMinVci OBJECT-TYPE
 446:        SYNTAX MplsAtmVcIdentifier
 447:        MAX-ACCESS not-accessible
 448:        STATUS current
 449:        DESCRIPTION
 450:            "The minimum VCI number configured for this range."
 451:        ::= { mplsLdpEntityAtmLREntry 2 }
 452: 
 453:    mplsLdpEntityAtmLRMaxVpi OBJECT-TYPE
 454:        SYNTAX AtmVpIdentifier
 455:        MAX-ACCESS read-create
 456:        STATUS current
 457:        DESCRIPTION
 458:            "The maximum VPI number configured for this range."
 459:        ::= { mplsLdpEntityAtmLREntry 3 }
 460: 
 461:    mplsLdpEntityAtmLRMaxVci OBJECT-TYPE
 462:        SYNTAX MplsAtmVcIdentifier
 463:        MAX-ACCESS read-create
 464:        STATUS current
 465:        DESCRIPTION
 466:            "The maximum VCI number configured for this range."
 467:       ::= { mplsLdpEntityAtmLREntry 4 }
 468: 
 469:    mplsLdpEntityAtmLRStorageType  OBJECT-TYPE
 470:        SYNTAX      StorageType
 471:        MAX-ACCESS  read-create
 472:        STATUS      current
 473:        DESCRIPTION
 474:            "The storage type for this conceptual row.  Conceptual rows
 475:            having the value 'permanent(4)' need not allow write-access to any
 476:            columnar objects in the row."
 477:        DEFVAL { nonVolatile }
 478:        ::= { mplsLdpEntityAtmLREntry 5 }
 479: 
 480:    mplsLdpEntityAtmLRRowStatus OBJECT-TYPE
 481:        SYNTAX RowStatus
 482:        MAX-ACCESS read-create
 483:        STATUS current
 484:        DESCRIPTION
 485:            "The status of this conceptual row.  All writable objects in this
 486:             row may be modified at any time, however, as described in
 487:             detail in the section entitled, 'Changing Values After Session
 488:             Establishment', and again described in the
 489:             DESCRIPTION clause of the mplsLdpEntityAdminStatus object,
 490:             if a session has been initiated with a Peer,
 491:             changing objects in this table will
 492:             wreak havoc with the session and interrupt traffic.  To repeat again:
 493:             the recommended procedure is to set the mplsLdpEntityAdminStatus to
 494:             down, thereby explicitely causing a session to be torn down. Then,
 495:             change objects in this entry, then set the mplsLdpEntityAdminStatus
 496:             to enable which enables a NEW session to be initiated.
 497: 
 498:             There must exist at least one entry in this
 499:             table for every LDP Entity that has
 500:             'mplsLdpEntityOptionalParameters' object with
 501:             a value of 'atmSessionParameters'.
 502: 
 503:             NOTE:  This RowStatus object should
 504:             have the same value of the 'mplsLdpEntityRowStatus'
 505:             related to this entry."
 506:        ::= { mplsLdpEntityAtmLREntry 6 }
 507: 
 508:    --
 509:    -- MPLS LDP ATM Session Information
 510:    --
 511: 
 512:    mplsLdpAtmSesObjects OBJECT IDENTIFIER ::=
 513:                                   { mplsLdpAtmObjects 2 }
 514: 
 515:    mplsLdpAtmSesTable OBJECT-TYPE
 516:        SYNTAX      SEQUENCE OF MplsLdpAtmSesEntry
 517:        MAX-ACCESS  not-accessible
 518:        STATUS      current
 519:        DESCRIPTION
 520:            "A table which relates Sessions in the
 521:            'mplsLdpSessionTable' and their label
 522:            range intersections.  There could be one
 523:            or more label range intersections between an
 524:            LDP Entity and LDP Peer using ATM as the underlying
 525:            media. Each row represents a single label range
 526:            intersection.
 527: 
 528:            NOTE:  this table cannot use the 'AUGMENTS'
 529:            clause because there is not necessarily a one-to-one
 530:            mapping between this table and the mplsLdpSessionTable."
 531:        ::= { mplsLdpAtmSesObjects 1 }
 532: 
 533:    mplsLdpAtmSesEntry OBJECT-TYPE
 534:        SYNTAX      MplsLdpAtmSesEntry
 535:        MAX-ACCESS  not-accessible
 536:        STATUS      current
 537:        DESCRIPTION
 538:            "An entry in this table represents information on a
 539:            single label range intersection between an LDP Entity
 540:            and LDP Peer.
 541: 
 542:            The information contained in a row is read-only."
 543:        INDEX       { mplsLdpEntityLdpId,
 544:                      mplsLdpEntityIndex,
 545:                      mplsLdpPeerLdpId,
 546:                      mplsLdpSesAtmLRLowerBoundVpi,
 547:                      mplsLdpSesAtmLRLowerBoundVci
 548: 
 549:                    }
 550:        ::= { mplsLdpAtmSesTable 1 }
 551: 
 552:    MplsLdpAtmSesEntry ::= SEQUENCE {
 553:        mplsLdpSesAtmLRLowerBoundVpi     AtmVpIdentifier,
 554:        mplsLdpSesAtmLRLowerBoundVci     MplsAtmVcIdentifier,
 555:        mplsLdpSesAtmLRUpperBoundVpi     AtmVpIdentifier,
 556:        mplsLdpSesAtmLRUpperBoundVci     MplsAtmVcIdentifier
 557:    }
 558: 
 559:    mplsLdpSesAtmLRLowerBoundVpi OBJECT-TYPE
 560:        SYNTAX AtmVpIdentifier
 561:        MAX-ACCESS not-accessible
 562:        STATUS current
 563:        DESCRIPTION
 564:            "The minimum VPI number for this range."
 565:        ::= { mplsLdpAtmSesEntry 1 }
 566: 
 567:    mplsLdpSesAtmLRLowerBoundVci OBJECT-TYPE
 568:        SYNTAX MplsAtmVcIdentifier
 569:        MAX-ACCESS not-accessible
 570:        STATUS current
 571:        DESCRIPTION
 572:            "The minimum VCI number for this range."
 573:        ::= { mplsLdpAtmSesEntry 2 }
 574: 
 575:    mplsLdpSesAtmLRUpperBoundVpi OBJECT-TYPE
 576:        SYNTAX AtmVpIdentifier
 577:        MAX-ACCESS read-only
 578:        STATUS current
 579:        DESCRIPTION
 580:            "The maximum VPI number for this range."
 581:        ::= { mplsLdpAtmSesEntry 3 }
 582: 
 583:    mplsLdpSesAtmLRUpperBoundVci OBJECT-TYPE
 584:        SYNTAX MplsAtmVcIdentifier
 585:        MAX-ACCESS read-only
 586:        STATUS current
 587:        DESCRIPTION
 588:            "The maximum VCI number for this range."
 589:        ::= { mplsLdpAtmSesEntry 4 }
 590: 
 591:    --**************************************************************
 592:    -- Module Conformance Statement
 593:    --**************************************************************
 594: 
 595:    mplsLdpAtmGroups
 596:        OBJECT IDENTIFIER ::= { mplsLdpAtmConformance 1 }
 597: 
 598:    mplsLdpAtmCompliances
 599:        OBJECT IDENTIFIER ::= { mplsLdpAtmConformance 2 }
 600: 
 601:    --
 602:    -- Full Compliance
 603:    --
 604: 
 605:    mplsLdpAtmModuleFullCompliance MODULE-COMPLIANCE
 606:        STATUS current
 607:        DESCRIPTION
 608:            "The Module is implemented with support for
 609:            read-create and read-write.  In other words,
 610:            both monitoring and configuration
 611:            are available when using this MODULE-COMPLIANCE."
 612:        MODULE -- this module
 613:        MANDATORY-GROUPS    {
 614:                               mplsLdpAtmGroup
 615:                            }
 616: 
 617: 
 618:        OBJECT       mplsLdpEntityAtmRowStatus
 619:        SYNTAX       RowStatus { active(1) }
 620:        WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
 621:        DESCRIPTION
 622:           "Support for createAndWait and notInService is not required."
 623: 
 624:        OBJECT       mplsLdpEntityAtmLRRowStatus
 625:        SYNTAX       RowStatus { active(1) }
 626:        WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
 627:        DESCRIPTION
 628:           "Support for createAndWait and notInService is not required."
 629:        ::= { mplsLdpAtmCompliances 1 }
 630: 
 631: 
 632:    --
 633:    -- Read-Only Compliance
 634:    --
 635: 
 636:    mplsLdpAtmModuleReadOnlyCompliance MODULE-COMPLIANCE
 637:        STATUS current
 638:        DESCRIPTION
 639:            "The Module is implemented with support for
 640:            read-only.  In other words, only monitoring
 641:            is available by implementing this MODULE-COMPLIANCE."
 642:        MODULE -- this module
 643:        MANDATORY-GROUPS    {
 644:                               mplsLdpAtmGroup
 645:                            }
 646: 
 647:        OBJECT       mplsLdpEntityAtmIfIndexOrZero
 648:        MIN-ACCESS   read-only
 649:        DESCRIPTION
 650:           "Write access is not required."
 651: 
 652:        OBJECT       mplsLdpEntityAtmMergeCap
 653:        MIN-ACCESS   read-only
 654:        DESCRIPTION
 655:           "Write access is not required."
 656: 
 657:        OBJECT       mplsLdpEntityAtmLRComponents
 658:        MIN-ACCESS   read-only
 659:        DESCRIPTION
 660:           "Write access is not required."
 661: 
 662:        OBJECT       mplsLdpEntityAtmVcDirectionality
 663:        MIN-ACCESS   read-only
 664:        DESCRIPTION
 665:           "Write access is not required."
 666: 
 667:        OBJECT       mplsLdpEntityAtmLsrConnectivity
 668:        MIN-ACCESS   read-only
 669:        DESCRIPTION
 670:           "Write access is not required."
 671: 
 672:        OBJECT       mplsLdpEntityAtmDefaultControlVpi
 673:        MIN-ACCESS   read-only
 674:        DESCRIPTION
 675:           "Write access is not required."
 676: 
 677:        OBJECT       mplsLdpEntityAtmDefaultControlVci
 678:        MIN-ACCESS   read-only
 679:        DESCRIPTION
 680:           "Write access is not required."
 681: 
 682:        OBJECT       mplsLdpEntityAtmUnlabTrafVpi
 683:        MIN-ACCESS   read-only
 684:        DESCRIPTION
 685:           "Write access is not required."
 686: 
 687:        OBJECT       mplsLdpEntityAtmUnlabTrafVci
 688:        MIN-ACCESS   read-only
 689:        DESCRIPTION
 690:           "Write access is not required."
 691: 
 692:        OBJECT       mplsLdpEntityAtmStorageType
 693:        MIN-ACCESS   read-only
 694:        DESCRIPTION
 695:           "Write access is not required."
 696: 
 697: 
 698:        OBJECT       mplsLdpEntityAtmRowStatus
 699:        SYNTAX       RowStatus { active(1) }
 700:        MIN-ACCESS   read-only
 701:        DESCRIPTION
 702:           "Write access is not required, and active is the
 703:           only status that needs to be supported."
 704: 
 705:        OBJECT       mplsLdpEntityAtmLRMaxVpi
 706:        MIN-ACCESS   read-only
 707:        DESCRIPTION
 708:           "Write access is not required."
 709: 
 710:        OBJECT       mplsLdpEntityAtmLRMaxVci
 711:        MIN-ACCESS   read-only
 712:        DESCRIPTION
 713:           "Write access is not required."
 714: 
 715:        OBJECT       mplsLdpEntityAtmLRStorageType
 716:        MIN-ACCESS   read-only
 717:        DESCRIPTION
 718:           "Write access is not required."
 719: 
 720:        OBJECT       mplsLdpEntityAtmLRRowStatus
 721:        SYNTAX       RowStatus { active(1) }
 722:        MIN-ACCESS   read-only
 723:        DESCRIPTION
 724:           "Write access is not required, and active is the
 725:           only status that needs to be supported."
 726: 
 727:        ::= { mplsLdpAtmCompliances 2 }
 728: 
 729:    --
 730:    -- units of conformance
 731:    --
 732: 
 733:    mplsLdpAtmGroup OBJECT-GROUP
 734:        OBJECTS {
 735:        mplsLdpEntityAtmIfIndexOrZero,
 736:        mplsLdpEntityAtmMergeCap,
 737:        mplsLdpEntityAtmLRComponents,
 738:        mplsLdpEntityAtmVcDirectionality,
 739:        mplsLdpEntityAtmLsrConnectivity,
 740:        mplsLdpEntityAtmDefaultControlVpi,
 741:        mplsLdpEntityAtmDefaultControlVci,
 742:        mplsLdpEntityAtmUnlabTrafVpi,
 743:        mplsLdpEntityAtmUnlabTrafVci,
 744:        mplsLdpEntityAtmStorageType,
 745:        mplsLdpEntityAtmRowStatus,
 746:        mplsLdpEntityAtmLRMaxVpi,
 747:        mplsLdpEntityAtmLRMaxVci,
 748:        mplsLdpEntityAtmLRStorageType,
 749:        mplsLdpEntityAtmLRRowStatus,
 750:        mplsLdpSesAtmLRUpperBoundVpi,
 751:        mplsLdpSesAtmLRUpperBoundVci
 752: 
 753:        }
 754:        STATUS    current
 755:        DESCRIPTION
 756:            "Objects that apply to all MPLS LDP implementations
 757:            using ATM as the Layer 2."
 758:        ::= { mplsLdpAtmGroups 1 }
 759: 
 760: 
 761:    END
 762: 
 763: -- 
 764: --    Copyright (C) The Internet Society (2003). All Rights Reserved.
 765: -- 
 766: -- 
 767: --    This document and translations of it may be copied and furnished to
 768: --    others, and derivative works that comment on or otherwise explain it
 769: --    or assist in its implementation may be prepared, copied, published
 770: --    and distributed, in whole or in part, without restriction of any
 771: --    kind, provided that the above copyright notice and this paragraph are
 772: --    included on all such copies and derivative works.  However, this
 773: --    document itself may not be modified in any way, such as by removing
 774: --    the copyright notice or references to the Internet Society or other
 775: --    Internet organizations, except as needed for the  purpose of
 776: --    developing Internet standards in which case the procedures for
 777: --    copyrights defined in the Internet Standards process must be
 778: --    followed, or as required to translate it into languages other than
 779: --    English.
 780: -- 
 781: --    The limited permissions granted above are perpetual and will not be
 782: --    revoked by the Internet Society or its successors or assigns.
 783: -- 
 784: --    This document and the information contained herein is provided on an
 785: --    "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
 786: --    TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
 787: --    BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
 788: --    HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
 789: --    MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 790: