1 MPLS-LDP-ATM-STD-MIB DEFINITIONS ::= BEGIN
4 OBJECT-TYPE, MODULE-IDENTITY,
6 FROM SNMPv2-SMI -- [RFC2578]
7 MODULE-COMPLIANCE, OBJECT-GROUP
8 FROM SNMPv2-CONF -- [RFC2580]
11 FROM SNMPv2-TC -- [RFC2579]
14 FROM IF-MIB -- [RFC2020]
17 FROM ATM-TC-MIB -- [RFC2514]
21 FROM MPLS-TC-STD-MIB -- [RFC3811]
26 FROM MPLS-LDP-STD-MIB -- [RFC3813]
30 mplsLdpAtmStdMIB MODULE-IDENTITY
31 LAST-UPDATED "200406030000Z" -- June 3, 2004
34 ORGANIZATION "Multiprotocol Label Switching (mpls)
37 "Joan Cucchiara (jcucchiara@mindspring.com)
38 Marconi Communications, Inc.
40 Hans Sjostrand (hans@ipunplugged.com)
43 James V. Luciani (james_luciani@mindspring.com)
44 Marconi Communications, Inc.
47 George Swallow, email: swallow@cisco.com
48 Loa Andersson, email: loa@pi.se
50 MPLS Working Group, email: mpls@uu.net
53 "Copyright (C) The Internet Society (2004). The
54 initial version of this MIB module was published
55 in RFC 3815. For full legal notices see the RFC
57 http://www.ietf.org/copyrights/ianamib.html
59 This MIB contains managed object definitions for
60 configuring and monitoring the Multiprotocol Label
61 Switching (MPLS), Label Distribution Protocol (LDP),
62 utilizing Asynchronous Transfer Mode (ATM) as the Layer 2
64 REVISION "200406030000Z" -- June 3, 2004
66 "Initial version published as part of RFC 3815."
70 --****************************************************************
72 mplsLdpAtmObjects OBJECT IDENTIFIER
73 ::= { mplsLdpAtmStdMIB 1 }
74 mplsLdpAtmConformance OBJECT IDENTIFIER
75 ::= { mplsLdpAtmStdMIB 2 }
77 --****************************************************************
78 -- MPLS LDP ATM Objects
79 --****************************************************************
81 -- Ldp Entity Objects for ATM
86 mplsLdpEntityAtmObjects OBJECT IDENTIFIER ::=
87 { mplsLdpAtmObjects 1 }
89 mplsLdpEntityAtmTable OBJECT-TYPE
90 SYNTAX SEQUENCE OF MplsLdpEntityAtmEntry
91 MAX-ACCESS not-accessible
94 "This table contains ATM specific information
95 which could be used in the
96 'Optional Parameters' and other ATM specific
99 This table 'sparse augments' the mplsLdpEntityTable
100 when ATM is the Layer 2 medium."
101 ::= { mplsLdpEntityAtmObjects 1 }
103 mplsLdpEntityAtmEntry OBJECT-TYPE
104 SYNTAX MplsLdpEntityAtmEntry
105 MAX-ACCESS not-accessible
108 "An entry in this table represents the ATM parameters
109 and ATM information for this LDP entity."
110 INDEX { mplsLdpEntityLdpId,
113 ::= { mplsLdpEntityAtmTable 1 }
116 MplsLdpEntityAtmEntry ::= SEQUENCE {
117 mplsLdpEntityAtmIfIndexOrZero InterfaceIndexOrZero,
118 mplsLdpEntityAtmMergeCap INTEGER,
119 mplsLdpEntityAtmLRComponents Unsigned32,
120 mplsLdpEntityAtmVcDirectionality INTEGER,
121 mplsLdpEntityAtmLsrConnectivity INTEGER,
122 mplsLdpEntityAtmDefaultControlVpi AtmVpIdentifier,
123 mplsLdpEntityAtmDefaultControlVci MplsAtmVcIdentifier,
124 mplsLdpEntityAtmUnlabTrafVpi AtmVpIdentifier,
125 mplsLdpEntityAtmUnlabTrafVci MplsAtmVcIdentifier,
126 mplsLdpEntityAtmStorageType StorageType,
127 mplsLdpEntityAtmRowStatus RowStatus
130 mplsLdpEntityAtmIfIndexOrZero OBJECT-TYPE
131 SYNTAX InterfaceIndexOrZero
135 MAX-ACCESS read-create
138 "This value represents either the InterfaceIndex
139 or 0 (zero). The value of zero means that the
140 InterfaceIndex is not known.
142 However, if the InterfaceIndex is known, then it must
143 be represented by this value.
145 If an InterfaceIndex becomes known, then the
146 network management entity (e.g., SNMP agent) responsible
147 for this object MUST change the value from 0 (zero) to the
148 value of the InterfaceIndex. If an ATM Label is
149 being used in forwarding data, then the value of this
150 object MUST be the InterfaceIndex."
151 ::= { mplsLdpEntityAtmEntry 1 }
153 mplsLdpEntityAtmMergeCap OBJECT-TYPE
160 MAX-ACCESS read-create
163 "Denotes the Merge Capability of this Entity.
164 This is the EXACT value for the ATM Session
165 Parameter, field M (for ATM Merge Capabilities).
166 The ATM Session Parameter is an optional
167 parameter in the Initialization Message.
169 The description from rfc3036.txt is:
171 'M, ATM Merge Capabilities
172 Specifies the merge capabilities of an ATM switch. The
173 following values are supported in this version of the
178 0 Merge not supported
181 3 VP & VC Merge supported
186 If the merge capabilities of the LSRs differ, then:
187 - Non-merge and VC-merge LSRs may freely interoperate.
189 - The interoperability of VP-merge-capable switches
190 with non-VP-merge-capable switches is a subject
191 for future study. When the LSRs differ on the
192 use of VP-merge, the session is established,
193 but VP merge is not used.'
195 Please refer to the following reference for a
196 complete description of this feature."
199 "RFC3036, LDP Specification, Section 3.5.3
200 Initialization Message."
201 ::= { mplsLdpEntityAtmEntry 2 }
203 mplsLdpEntityAtmLRComponents OBJECT-TYPE
204 SYNTAX Unsigned32 (1..65535)
208 "Number of Label Range Components in the Initialization
209 message. This also represents the number of entries
210 in the mplsLdpEntityAtmLRTable which correspond
213 This is the EXACT value for the ATM Session Parameter,
214 field N (for Number of label range components).
215 The ATM Session Parameter is an optional parameter
216 in the Initialization Message.
218 The description from rfc3036.txt is:
220 'N, Number of label range components
221 Specifies the number of ATM Label Range
222 Components included in the TLV.'
224 Please refer to the following reference for
225 a complete description of this feature."
227 "RFC3036, LDP Specification, Section 3.5.3
228 Initialization Message."
229 ::= { mplsLdpEntityAtmEntry 3 }
231 mplsLdpEntityAtmVcDirectionality OBJECT-TYPE
239 MAX-ACCESS read-create
242 "If the value of this object is 'bidirectional(0)',
243 a given VCI, within a given VPI, is used as a
244 label for both directions independently.
246 If the value of this object is 'unidirectional(1)',
247 a given VCI within a VPI designates one direction.
249 This is the EXACT value for the ATM Session Parameter,
250 field D (for VC Directionality). The ATM Session
251 Parameter is an optional parameter in the
252 Initialization Message.
254 The description from rfc3036.txt is:
256 'D, VC Directionality
257 A value of 0 specifies bidirectional VC capability,
258 meaning the LSR can (within a given VPI) support
259 the use of a given VCI as a label for both link
260 directions independently. A value of 1
261 specifies unidirectional VC capability, meaning
262 (within a given VPI) a given VCI may appear in
263 a label mapping for one direction on the link
264 only. When either or both of the peers
265 specifies unidirectional VC capability, both
266 LSRs use unidirectional VC label assignment for
267 the link as follows. The LSRs compare their
268 LDP Identifiers as unsigned integers. The LSR
269 with the larger LDP Identifier may assign
270 only odd-numbered VCIs in the VPI/VCI
271 range as labels. The system with the smaller
272 LDP Identifier may assign only even-numbered
273 VCIs in the VPI/VCI range as labels.'
275 Please refer to the following reference
276 for a complete description of this feature."
278 "RFC3036, LDP Specification, Section 3.5.3
279 Initialization Message."
280 ::= { mplsLdpEntityAtmEntry 4 }
282 mplsLdpEntityAtmLsrConnectivity OBJECT-TYPE
289 MAX-ACCESS read-create
292 "The peer LSR may be connected indirectly by means
293 of an ATM VP so that the VPI values may be different
294 on either endpoint so the label MUST be encoded
295 entirely within the VCI field."
297 ::= { mplsLdpEntityAtmEntry 5 }
299 mplsLdpEntityAtmDefaultControlVpi OBJECT-TYPE
300 SYNTAX AtmVpIdentifier
301 MAX-ACCESS read-create
304 "The default VPI value for the non-MPLS connection. The
305 default value of this is 0 (zero) but other values may
306 be configured. This object allows a different value
309 ::= { mplsLdpEntityAtmEntry 6 }
311 mplsLdpEntityAtmDefaultControlVci OBJECT-TYPE
312 SYNTAX MplsAtmVcIdentifier
313 MAX-ACCESS read-create
316 "The Default VCI value for a non-MPLS connection. The
317 default value of this is 32 but other values may be
318 configured. This object allows a different value to
321 ::= { mplsLdpEntityAtmEntry 7 }
323 mplsLdpEntityAtmUnlabTrafVpi OBJECT-TYPE
324 SYNTAX AtmVpIdentifier
325 MAX-ACCESS read-create
328 "VPI value of the VCC supporting unlabeled traffic. This
329 non-MPLS connection is used to carry unlabeled (IP)
330 packets. The default value is the same as the default
331 value of the 'mplsLdpEntityAtmDefaultControlVpi', however
332 another value may be configured."
334 ::= { mplsLdpEntityAtmEntry 8 }
337 mplsLdpEntityAtmUnlabTrafVci OBJECT-TYPE
338 SYNTAX MplsAtmVcIdentifier
339 MAX-ACCESS read-create
342 "VCI value of the VCC supporting unlabeled traffic.
343 This non-MPLS connection is used to carry unlabeled (IP)
344 packets. The default value is the same as the default
345 value of the 'mplsLdpEntityAtmDefaultControlVci', however
346 another value may be configured."
348 ::= { mplsLdpEntityAtmEntry 9 }
350 mplsLdpEntityAtmStorageType OBJECT-TYPE
352 MAX-ACCESS read-create
355 "The storage type for this conceptual row.
356 Conceptual rows having the value 'permanent(4)'
357 need not allow write-access to any columnar
359 DEFVAL { nonVolatile }
360 ::= { mplsLdpEntityAtmEntry 10 }
362 mplsLdpEntityAtmRowStatus OBJECT-TYPE
364 MAX-ACCESS read-create
367 "The status of this conceptual row. All writable
368 objects in this row may be modified at any time,
369 however, as described in detail in the section
370 entitled, 'Changing Values After Session
371 Establishment', and again described in the
372 DESCRIPTION clause of the mplsLdpEntityAdminStatus
373 object, if a session has been initiated with a Peer,
374 changing objects in this table will wreak havoc
375 with the session and interrupt traffic. To repeat again:
376 the recommended procedure is to set the
377 mplsLdpEntityAdminStatus to down, thereby explicitly
378 causing a session to be torn down. Then,
379 change objects in this entry, then set the
380 mplsLdpEntityAdminStatus to enable
381 which enables a new session to be initiated."
382 ::= { mplsLdpEntityAtmEntry 11 }
387 -- The MPLS LDP Entity ATM Label Range Table
390 mplsLdpEntityAtmLRTable OBJECT-TYPE
391 SYNTAX SEQUENCE OF MplsLdpEntityAtmLREntry
392 MAX-ACCESS not-accessible
395 "The MPLS LDP Entity ATM Label Range (LR) Table.
396 The purpose of this table is to provide a mechanism
397 for configuring a contiguous range of vpi's
398 with a contiguous range of vci's, or a 'label range'
401 LDP Entities which use ATM must have at least one
404 There must exist at least one entry in this
405 table for every LDP Entity that has
406 'mplsLdpEntityOptionalParameters' object with
407 a value of 'atmSessionParameters'."
408 ::= { mplsLdpEntityAtmObjects 2 }
410 mplsLdpEntityAtmLREntry OBJECT-TYPE
411 SYNTAX MplsLdpEntityAtmLREntry
412 MAX-ACCESS not-accessible
415 "A row in the LDP Entity ATM Label
416 Range Table. One entry in this table contains
417 information on a single range of labels
418 represented by the configured Upper and Lower
419 Bounds VPI/VCI pairs. These are the same
420 data used in the Initialization Message.
422 NOTE: The ranges for a specific LDP Entity
423 are UNIQUE and non-overlapping. For example,
424 for a specific LDP Entity index, there could
425 be one entry having LowerBound vpi/vci == 0/32, and
426 UpperBound vpi/vci == 0/100, and a second entry
427 for this same interface with LowerBound
428 vpi/vci == 0/101 and UpperBound vpi/vci == 0/200.
429 However, there could not be a third entry with
430 LowerBound vpi/vci == 0/200 and
431 UpperBound vpi/vci == 0/300 because this label
432 range overlaps with the second entry (i.e., both
433 entries now have 0/200).
437 A row will not become active unless a unique and
438 non-overlapping range is specified.
440 At least one label range entry for a
441 specific LDP Entity MUST
442 include the default VPI/VCI values denoted
443 in the LDP Entity Table.
445 A request to create a row with an overlapping
446 range should result in an inconsistentValue
448 INDEX { mplsLdpEntityLdpId,
450 mplsLdpEntityAtmLRMinVpi,
451 mplsLdpEntityAtmLRMinVci
453 ::= { mplsLdpEntityAtmLRTable 1 }
455 MplsLdpEntityAtmLREntry ::= SEQUENCE {
456 mplsLdpEntityAtmLRMinVpi AtmVpIdentifier,
457 mplsLdpEntityAtmLRMinVci MplsAtmVcIdentifier,
458 mplsLdpEntityAtmLRMaxVpi AtmVpIdentifier,
459 mplsLdpEntityAtmLRMaxVci MplsAtmVcIdentifier,
460 mplsLdpEntityAtmLRStorageType StorageType,
461 mplsLdpEntityAtmLRRowStatus RowStatus
464 mplsLdpEntityAtmLRMinVpi OBJECT-TYPE
465 SYNTAX AtmVpIdentifier
466 MAX-ACCESS not-accessible
469 "The minimum VPI number configured for this range.
470 The value of zero is a valid value for the VPI portion
472 ::= { mplsLdpEntityAtmLREntry 1 }
474 mplsLdpEntityAtmLRMinVci OBJECT-TYPE
475 SYNTAX MplsAtmVcIdentifier
476 MAX-ACCESS not-accessible
479 "The minimum VCI number configured for this range."
480 ::= { mplsLdpEntityAtmLREntry 2 }
482 mplsLdpEntityAtmLRMaxVpi OBJECT-TYPE
483 SYNTAX AtmVpIdentifier
484 MAX-ACCESS read-create
489 "The maximum VPI number configured for this range."
490 ::= { mplsLdpEntityAtmLREntry 3 }
492 mplsLdpEntityAtmLRMaxVci OBJECT-TYPE
493 SYNTAX MplsAtmVcIdentifier
494 MAX-ACCESS read-create
497 "The maximum VCI number configured for this range."
498 ::= { mplsLdpEntityAtmLREntry 4 }
500 mplsLdpEntityAtmLRStorageType OBJECT-TYPE
502 MAX-ACCESS read-create
505 "The storage type for this conceptual row.
506 Conceptual rows having the value 'permanent(4)'
507 need not allow write-access to any columnar
509 DEFVAL { nonVolatile }
510 ::= { mplsLdpEntityAtmLREntry 5 }
512 mplsLdpEntityAtmLRRowStatus OBJECT-TYPE
514 MAX-ACCESS read-create
517 "The status of this conceptual row. All writable
518 objects in this row may be modified at any time,
519 however, as described in detail in the section
520 entitled, 'Changing Values After Session
521 Establishment', and again described in the
522 DESCRIPTION clause of the
523 mplsLdpEntityAdminStatus object,
524 if a session has been initiated with a Peer,
525 changing objects in this table will
526 wreak havoc with the session and interrupt traffic.
527 To repeat again: the recommended procedure
528 is to set the mplsLdpEntityAdminStatus to
529 down, thereby explicitly causing a session
530 to be torn down. Then, change objects in this
531 entry, then set the mplsLdpEntityAdminStatus
532 to enable which enables a new session
534 ::= { mplsLdpEntityAtmLREntry 6 }
538 -- MPLS LDP ATM Session Information
541 mplsLdpAtmSessionObjects OBJECT IDENTIFIER ::=
542 { mplsLdpAtmObjects 2 }
544 mplsLdpAtmSessionTable OBJECT-TYPE
545 SYNTAX SEQUENCE OF MplsLdpAtmSessionEntry
546 MAX-ACCESS not-accessible
549 "A table which relates sessions in the
550 'mplsLdpSessionTable' and their label
551 range intersections. There could be one
552 or more label range intersections between an
553 LDP Entity and LDP Peer using ATM as the
554 underlying media. Each row represents
555 a single label range intersection.
557 This table cannot use the 'AUGMENTS'
558 clause because there is not necessarily
559 a one-to-one mapping between this table
560 and the mplsLdpSessionTable."
561 ::= { mplsLdpAtmSessionObjects 1 }
563 mplsLdpAtmSessionEntry OBJECT-TYPE
564 SYNTAX MplsLdpAtmSessionEntry
565 MAX-ACCESS not-accessible
568 "An entry in this table represents information on a
569 single label range intersection between an LDP Entity
572 The information contained in a row is read-only."
573 INDEX { mplsLdpEntityLdpId,
576 mplsLdpSessionAtmLRLowerBoundVpi,
577 mplsLdpSessionAtmLRLowerBoundVci
579 ::= { mplsLdpAtmSessionTable 1 }
581 MplsLdpAtmSessionEntry ::= SEQUENCE {
582 mplsLdpSessionAtmLRLowerBoundVpi AtmVpIdentifier,
583 mplsLdpSessionAtmLRLowerBoundVci MplsAtmVcIdentifier,
584 mplsLdpSessionAtmLRUpperBoundVpi AtmVpIdentifier,
587 mplsLdpSessionAtmLRUpperBoundVci MplsAtmVcIdentifier
590 mplsLdpSessionAtmLRLowerBoundVpi OBJECT-TYPE
591 SYNTAX AtmVpIdentifier
592 MAX-ACCESS not-accessible
595 "The minimum VPI number for this range."
596 ::= { mplsLdpAtmSessionEntry 1 }
598 mplsLdpSessionAtmLRLowerBoundVci OBJECT-TYPE
599 SYNTAX MplsAtmVcIdentifier
600 MAX-ACCESS not-accessible
603 "The minimum VCI number for this range."
604 ::= { mplsLdpAtmSessionEntry 2 }
606 mplsLdpSessionAtmLRUpperBoundVpi OBJECT-TYPE
607 SYNTAX AtmVpIdentifier
611 "The maximum VPI number for this range."
612 ::= { mplsLdpAtmSessionEntry 3 }
614 mplsLdpSessionAtmLRUpperBoundVci OBJECT-TYPE
615 SYNTAX MplsAtmVcIdentifier
619 "The maximum VCI number for this range."
620 ::= { mplsLdpAtmSessionEntry 4 }
622 --**************************************************************
623 -- Module Conformance Statement
624 --**************************************************************
627 OBJECT IDENTIFIER ::= { mplsLdpAtmConformance 1 }
629 mplsLdpAtmCompliances
630 OBJECT IDENTIFIER ::= { mplsLdpAtmConformance 2 }
637 mplsLdpAtmModuleFullCompliance MODULE-COMPLIANCE
640 "The Module is implemented with support for
641 read-create and read-write. In other words,
642 both monitoring and configuration
643 are available when using this MODULE-COMPLIANCE."
644 MODULE -- this module
650 OBJECT mplsLdpEntityAtmRowStatus
651 SYNTAX RowStatus { active(1) }
652 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
654 "Support for createAndWait and notInService is not required."
656 OBJECT mplsLdpEntityAtmLRRowStatus
657 SYNTAX RowStatus { active(1) }
658 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
660 "Support for createAndWait and notInService is not required."
662 ::= { mplsLdpAtmCompliances 1 }
665 -- Read-Only Compliance
668 mplsLdpAtmModuleReadOnlyCompliance MODULE-COMPLIANCE
671 "The Module is implemented with support for
672 read-only. In other words, only monitoring
673 is available by implementing this MODULE-COMPLIANCE."
674 MODULE -- this module
679 OBJECT mplsLdpEntityAtmIfIndexOrZero
682 "Write access is not required."
684 OBJECT mplsLdpEntityAtmMergeCap
689 "Write access is not required."
691 OBJECT mplsLdpEntityAtmVcDirectionality
694 "Write access is not required."
696 OBJECT mplsLdpEntityAtmLsrConnectivity
699 "Write access is not required."
701 OBJECT mplsLdpEntityAtmDefaultControlVpi
704 "Write access is not required."
706 OBJECT mplsLdpEntityAtmDefaultControlVci
709 "Write access is not required."
711 OBJECT mplsLdpEntityAtmUnlabTrafVpi
714 "Write access is not required."
716 OBJECT mplsLdpEntityAtmUnlabTrafVci
719 "Write access is not required."
721 OBJECT mplsLdpEntityAtmStorageType
724 "Write access is not required."
726 OBJECT mplsLdpEntityAtmRowStatus
727 SYNTAX RowStatus { active(1) }
730 "Write access is not required, and active is the
731 only status that needs to be supported."
733 OBJECT mplsLdpEntityAtmLRMaxVpi
738 "Write access is not required."
740 OBJECT mplsLdpEntityAtmLRMaxVci
743 "Write access is not required."
745 OBJECT mplsLdpEntityAtmLRStorageType
748 "Write access is not required."
750 OBJECT mplsLdpEntityAtmLRRowStatus
751 SYNTAX RowStatus { active(1) }
754 "Write access is not required, and active is the
755 only status that needs to be supported."
757 ::= { mplsLdpAtmCompliances 2 }
760 -- units of conformance
763 mplsLdpAtmGroup OBJECT-GROUP
765 mplsLdpEntityAtmIfIndexOrZero,
766 mplsLdpEntityAtmMergeCap,
767 mplsLdpEntityAtmLRComponents,
768 mplsLdpEntityAtmVcDirectionality,
769 mplsLdpEntityAtmLsrConnectivity,
770 mplsLdpEntityAtmDefaultControlVpi,
771 mplsLdpEntityAtmDefaultControlVci,
772 mplsLdpEntityAtmUnlabTrafVpi,
773 mplsLdpEntityAtmUnlabTrafVci,
774 mplsLdpEntityAtmStorageType,
775 mplsLdpEntityAtmRowStatus,
776 mplsLdpEntityAtmLRMaxVpi,
777 mplsLdpEntityAtmLRMaxVci,
778 mplsLdpEntityAtmLRStorageType,
779 mplsLdpEntityAtmLRRowStatus,
780 mplsLdpSessionAtmLRUpperBoundVpi,
781 mplsLdpSessionAtmLRUpperBoundVci
788 "Objects that apply to all MPLS LDP implementations
789 using ATM as the Layer 2."
790 ::= { mplsLdpAtmGroups 1 }