1 MPLS-LDP-FRAME-RELAY-STD-MIB DEFINITIONS ::= BEGIN
7 FROM SNMPv2-SMI -- [RFC2578]
10 FROM SNMPv2-CONF -- [RFC2580]
16 FROM SNMPv2-TC -- [RFC2579]
19 FROM FRAME-RELAY-DTE-MIB -- [RFC2115]
22 FROM IF-MIB -- [RFC2020]
25 FROM MPLS-TC-STD-MIB -- [RFC3811]
30 FROM MPLS-LDP-STD-MIB -- [RFC3813]
33 mplsLdpFrameRelayStdMIB MODULE-IDENTITY
34 LAST-UPDATED "200406030000Z" -- June 3, 2004
35 ORGANIZATION "Multiprotocol Label Switching (mpls)
38 "Joan Cucchiara (jcucchiara@mindspring.com)
39 Marconi Communications, Inc.
41 Hans Sjostrand (hans@ipunplugged.com)
44 James V. Luciani (james_luciani@mindspring.com)
45 Marconi Communications, Inc.
48 George Swallow, email: swallow@cisco.com
49 Loa Andersson, email: loa@pi.se
51 MPLS Working Group, email: mpls@uu.net
54 "Copyright (C) The Internet Society (year). The
55 initial version of this MIB module was published
56 in RFC 3815. For full legal notices see the RFC
58 http://www.ietf.org/copyrights/ianamib.html
60 This MIB contains managed object definitions for
61 configuring and monitoring the Multiprotocol Label
62 Switching (MPLS), Label Distribution Protocol (LDP),
63 utilizing Frame Relay as the Layer 2 media."
67 REVISION "200406030000Z" -- June 6, 2004
69 "Initial version published as part of RFC 3815."
73 --****************************************************************
75 mplsLdpFrameRelayObjects OBJECT IDENTIFIER
76 ::= { mplsLdpFrameRelayStdMIB 1 }
78 mplsLdpFrameRelayConformance OBJECT IDENTIFIER
79 ::= { mplsLdpFrameRelayStdMIB 2 }
81 --****************************************************************
82 -- MPLS LDP Frame Relay Objects
83 --****************************************************************
86 -- Ldp Entity Objects for Frame Relay
89 mplsLdpEntityFrameRelayObjects OBJECT IDENTIFIER ::=
90 { mplsLdpFrameRelayObjects 1 }
92 mplsLdpEntityFrameRelayTable OBJECT-TYPE
93 SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayEntry
94 MAX-ACCESS not-accessible
97 "This table contains Frame Relay specific
98 information which could be used in the
99 'Optional Parameters' and other Frame Relay
100 specific information.
102 This table 'sparse augments' the mplsLdpEntityTable
103 when Frame Relay is the Layer 2 medium."
104 ::= { mplsLdpEntityFrameRelayObjects 1 }
106 mplsLdpEntityFrameRelayEntry OBJECT-TYPE
107 SYNTAX MplsLdpEntityFrameRelayEntry
108 MAX-ACCESS not-accessible
111 "An entry in this table represents the Frame Relay
112 optional parameters associated with the LDP entity."
113 INDEX { mplsLdpEntityLdpId,
118 ::= { mplsLdpEntityFrameRelayTable 1 }
120 MplsLdpEntityFrameRelayEntry ::= SEQUENCE {
121 mplsLdpEntityFrameRelayIfIndexOrZero InterfaceIndexOrZero,
122 mplsLdpEntityFrameRelayMergeCap INTEGER,
123 mplsLdpEntityFrameRelayLRComponents Unsigned32,
124 mplsLdpEntityFrameRelayVcDirectionality INTEGER,
125 mplsLdpEntityFrameRelayStorageType StorageType,
126 mplsLdpEntityFrameRelayRowStatus RowStatus
129 mplsLdpEntityFrameRelayIfIndexOrZero OBJECT-TYPE
130 SYNTAX InterfaceIndexOrZero
131 MAX-ACCESS read-create
134 "This value represents either the InterfaceIndex of
135 the 'ifLayer' where the Frame Relay Labels 'owned' by this
136 entry were created, or 0 (zero). The value of zero
137 means that the InterfaceIndex is not known. For example,
138 if the InterfaceIndex is created subsequent to the
139 Frame Relay Label's creation, then it would not be known.
140 However, if the InterfaceIndex is known, then it must
141 be represented by this value.
143 If an InterfaceIndex becomes known, then the
144 network management entity (e.g., SNMP agent) responsible
145 for this object MUST change the value from 0 (zero) to the
146 value of the InterfaceIndex. If an Frame Relay Label is
147 being used in forwarding data, then the value of this
148 object MUST be the InterfaceIndex."
149 ::= { mplsLdpEntityFrameRelayEntry 1 }
151 mplsLdpEntityFrameRelayMergeCap OBJECT-TYPE
156 MAX-ACCESS read-create
159 "This represents whether or not the Frame Relay merge
160 capability is supported. This is the EXACT value for the
161 Frame Relay Session Parameter, field M (for Frame Relay
162 Merge Capabilities). The Frame Relay Session Parameter
163 is an optional parameter in the Initialization Message.
168 The description from rfc3036.txt is:
169 'M, Frame Relay Merge Capabilities
170 Specifies the merge capabilities of a Frame
171 Relay switch. The following values are
172 supported in this version of the
177 0 Merge not supported
180 Non-merge and merge Frame Relay LSRs may
181 freely interoperate.'
183 Please refer to the following reference for a
184 complete description of this feature."
186 "RFC3036, LDP Specification, Section 3.5.3
187 Initialization Message."
188 ::= { mplsLdpEntityFrameRelayEntry 2 }
190 mplsLdpEntityFrameRelayLRComponents OBJECT-TYPE
191 SYNTAX Unsigned32 (1..65535)
195 "Number of Label Range Components in the Initialization
196 message. This also represents the number of entries
197 in the mplsLdpEntityFrameRelayLRTable which correspond
200 This is the EXACT value for the Frame Relay Session
201 Parameter, field N (for Number of label range
202 components). The Frame Relay Session Parameter
203 is an optional parameter in the Initialization
206 The description from rfc3036.txt is:
208 'N, Number of label range components
209 Specifies the number of Frame Relay Label
210 Range Components included in the TLV.'
212 Please refer to the following reference for a
213 complete description of this feature."
215 "RFC3036, LDP Specification, Section 3.5.3
219 Initialization Message."
220 ::= { mplsLdpEntityFrameRelayEntry 3 }
222 mplsLdpEntityFrameRelayVcDirectionality OBJECT-TYPE
227 MAX-ACCESS read-create
230 "If the value of this object is 'bidirectional(0)', then
231 the LSR supports the use of a given DLCI as a label for
232 both directions independently. If the value of
233 this object is 'unidirectional(1)', then the LSR
234 uses the given DLCI as a label in only one direction.
236 This is the EXACT value for the Frame Relay Session
237 Parameter, field D (for VC Directionality). The
238 Frame Relay Session Parameter is an optional
239 parameter in the Initialization Message.
241 The description from rfc3036.txt is:
243 'D, VC Directionality
244 A value of 0 specifies bidirectional VC capability,
245 meaning the LSR can support the use of a given
246 DLCI as a label for both link directions
247 independently. A value of 1 specifies
248 unidirectional VC capability, meaning a given
249 DLCI may appear in a label mapping for one
250 direction on the link only. When either or both
251 of the peers specifies unidirectional VC
252 capability, both LSRs use unidirectional VC
253 label assignment for the link as follows. The
254 LSRs compare their LDP Identifiers as unsigned
255 integers. The LSR with the larger LDP
256 Identifier may assign only odd-numbered DLCIs
257 in the range as labels. The system with the
258 smaller LDP Identifier may assign only
259 even-numbered DLCIs in the range as labels.'
261 Please refer to the following reference for a
262 complete description of this feature."
264 "RFC3036, LDP Specification, Section 3.5.3
265 Initialization Message."
266 ::= { mplsLdpEntityFrameRelayEntry 4 }
269 mplsLdpEntityFrameRelayStorageType OBJECT-TYPE
271 MAX-ACCESS read-create
274 "The storage type for this conceptual row.
275 Conceptual rows having the value 'permanent(4)'
276 need not allow write-access to any columnar
278 DEFVAL { nonVolatile }
279 ::= { mplsLdpEntityFrameRelayEntry 5 }
281 mplsLdpEntityFrameRelayRowStatus OBJECT-TYPE
283 MAX-ACCESS read-create
286 "The status of this conceptual row. All writable
287 objects in this row may be modified at any time,
288 however, as described in detail in the section
289 entitled, 'Changing Values After Session
290 Establishment', and again described in the
291 DESCRIPTION clause of the
292 mplsLdpEntityAdminStatus object,
293 if a session has been initiated with a Peer,
294 changing objects in this table will
295 wreak havoc with the session and interrupt
296 traffic. To repeat again:
297 the recommended procedure is to set the
298 mplsLdpEntityAdminStatus to
299 down, thereby explicitly causing a
300 session to be torn down. Then,
301 change objects in this entry, then set
302 the mplsLdpEntityAdminStatus
303 to enable which enables a new session
305 ::= { mplsLdpEntityFrameRelayEntry 6 }
308 -- Frame Relay Label Range Components
311 mplsLdpEntityFrameRelayLRTable OBJECT-TYPE
312 SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayLREntry
313 MAX-ACCESS not-accessible
316 "This table contains information about the
319 Optional Parameters for the Frame Relay Session
320 in the LDP Initialization Message, specifically
321 it contains information about the Frame Relay
322 Label Range Components.
324 If the value of the object
325 'mplsLdpEntityOptionalParameters' contains the
326 value of 'frameRelaySessionParameters(3)' then
327 there must be at least one corresponding entry
329 ::= { mplsLdpEntityFrameRelayObjects 2 }
331 mplsLdpEntityFrameRelayLREntry OBJECT-TYPE
332 SYNTAX MplsLdpEntityFrameRelayLREntry
333 MAX-ACCESS not-accessible
336 "An entry in this table represents the Frame Relay
337 Label Range Component associated with the LDP entity."
338 INDEX { mplsLdpEntityLdpId,
340 mplsLdpEntityFrameRelayLRMinDlci
342 ::= { mplsLdpEntityFrameRelayLRTable 1 }
344 MplsLdpEntityFrameRelayLREntry ::= SEQUENCE {
345 mplsLdpEntityFrameRelayLRMinDlci DLCI,
346 mplsLdpEntityFrameRelayLRMaxDlci DLCI,
347 mplsLdpEntityFrameRelayLRLen INTEGER,
348 mplsLdpEntityFrameRelayLRStorageType StorageType,
349 mplsLdpEntityFrameRelayLRRowStatus RowStatus
352 mplsLdpEntityFrameRelayLRMinDlci OBJECT-TYPE
354 MAX-ACCESS not-accessible
357 "The lower bound which is supported. This value
358 should be the same as that in the Frame Relay Label
359 Range Component's Minimum DLCI field. The value
360 of zero is valid for the minimum DLCI field of
363 "RFC3034, Use of Label Switching on Frame Relay
364 Networks Specification."
365 ::= { mplsLdpEntityFrameRelayLREntry 1 }
369 mplsLdpEntityFrameRelayLRMaxDlci OBJECT-TYPE
371 MAX-ACCESS read-create
374 "The upper bound which is supported. This value
375 should be the same as that in the Frame Relay Label
376 Range Component's Maximum DLCI field."
377 ::= { mplsLdpEntityFrameRelayLREntry 2 }
379 mplsLdpEntityFrameRelayLRLen OBJECT-TYPE
382 twentyThreeDlciBits(2)
384 MAX-ACCESS read-create
387 "This object specifies the length of the DLCI bits.
389 This is the EXACT value for the Len field of the
390 Frame Relay Label Range Component.
392 The description from rfc3036.txt is:
395 This field specifies the number of bits of the DLCI.
396 The following values are supported:
403 Len values 1 and 3 are reserved.'
405 Please refer to the following reference for a complete
406 description of this feature."
408 "RFC3036, LDP Specification, Section 3.5.3
409 Initialization Message."
410 ::= { mplsLdpEntityFrameRelayLREntry 3 }
412 mplsLdpEntityFrameRelayLRStorageType OBJECT-TYPE
414 MAX-ACCESS read-create
419 "The storage type for this conceptual row.
420 Conceptual rows having the value 'permanent(4)'
421 need not allow write-access to any columnar
423 DEFVAL { nonVolatile }
424 ::= { mplsLdpEntityFrameRelayLREntry 4 }
426 mplsLdpEntityFrameRelayLRRowStatus OBJECT-TYPE
428 MAX-ACCESS read-create
431 "The status of this conceptual row. All writable
432 objects in this row may be modified at any time,
433 however, as described in detail in the section
434 entitled, 'Changing Values After Session
435 Establishment', and again described in the
436 DESCRIPTION clause of the
437 mplsLdpEntityAdminStatus object,
438 if a session has been initiated with a Peer,
439 changing objects in this table will
440 wreak havoc with the session and interrupt
441 traffic. To repeat again:
442 the recommended procedure is to set the
443 mplsLdpEntityAdminStatus to down, thereby
444 explicitly causing a session to be torn down. Then,
445 change objects in this entry, then set the
446 mplsLdpEntityAdminStatus to enable which enables
447 a new session to be initiated."
448 ::= { mplsLdpEntityFrameRelayLREntry 5 }
451 -- MPLS LDP Frame Relay Session Information
454 mplsLdpFrameRelaySessionObjects OBJECT IDENTIFIER ::=
455 { mplsLdpFrameRelayObjects 2 }
457 mplsLdpFrameRelaySessionTable OBJECT-TYPE
458 SYNTAX SEQUENCE OF MplsLdpFrameRelaySessionEntry
459 MAX-ACCESS not-accessible
462 "A table of Frame Relay label range intersections
463 between the LDP Entities and LDP Peers.
464 Each row represents a single label range intersection.
466 NOTE: this table cannot use the 'AUGMENTS'
469 clause because there is not necessarily a one-to-one
470 mapping between this table and the
471 mplsLdpSessionTable."
472 ::= { mplsLdpFrameRelaySessionObjects 1 }
474 mplsLdpFrameRelaySessionEntry OBJECT-TYPE
475 SYNTAX MplsLdpFrameRelaySessionEntry
476 MAX-ACCESS not-accessible
479 "An entry in this table represents information on a
480 single label range intersection between an
481 LDP Entity and LDP Peer.
483 The information contained in a row is read-only."
484 INDEX { mplsLdpEntityLdpId,
487 mplsLdpFrameRelaySessionMinDlci
489 ::= { mplsLdpFrameRelaySessionTable 1 }
491 MplsLdpFrameRelaySessionEntry ::= SEQUENCE {
492 mplsLdpFrameRelaySessionMinDlci DLCI,
493 mplsLdpFrameRelaySessionMaxDlci DLCI,
494 mplsLdpFrameRelaySessionLen INTEGER
497 mplsLdpFrameRelaySessionMinDlci OBJECT-TYPE
499 MAX-ACCESS not-accessible
502 "The lower bound of DLCIs which are supported.
503 The value of zero is a valid value for the
504 minimum DLCI field of the label."
506 "RFC3034, Use of Label Switching on Frame Relay
507 Networks Specification."
508 ::= { mplsLdpFrameRelaySessionEntry 1 }
510 mplsLdpFrameRelaySessionMaxDlci OBJECT-TYPE
515 "The upper bound of DLCIs which are supported."
516 ::= { mplsLdpFrameRelaySessionEntry 2 }
519 mplsLdpFrameRelaySessionLen OBJECT-TYPE
522 twentyThreeDlciBits(2)
527 "This object specifies the DLCI bits."
528 ::= { mplsLdpFrameRelaySessionEntry 3 }
530 --****************************************************************
531 -- Module Conformance Statement
532 --****************************************************************
534 mplsLdpFrameRelayGroups
535 OBJECT IDENTIFIER ::= { mplsLdpFrameRelayConformance 1 }
537 mplsLdpFrameRelayCompliances
538 OBJECT IDENTIFIER ::= { mplsLdpFrameRelayConformance 2 }
544 mplsLdpFrameRelayModuleFullCompliance MODULE-COMPLIANCE
547 "The Module is implemented with support for
548 read-create and read-write. In other words,
549 both monitoring and configuration
550 are available when using this MODULE-COMPLIANCE."
551 MODULE -- this module
553 mplsLdpFrameRelayGroup
556 OBJECT mplsLdpEntityFrameRelayRowStatus
557 SYNTAX RowStatus { active(1) }
558 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
560 "Support for createAndWait and notInService is not required."
562 OBJECT mplsLdpEntityFrameRelayLRRowStatus
563 SYNTAX RowStatus { active(1) }
564 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
566 "Support for createAndWait and notInService is not required."
569 ::= { mplsLdpFrameRelayCompliances 1 }
572 -- Read-Only Compliance
575 mplsLdpFrameRelayModuleReadOnlyCompliance MODULE-COMPLIANCE
578 "The Module is implemented with support for
579 read-only. In other words, only monitoring
580 is available by implementing this MODULE-COMPLIANCE."
581 MODULE -- this module
583 mplsLdpFrameRelayGroup
586 OBJECT mplsLdpEntityFrameRelayIfIndexOrZero
589 "Write access is not required."
591 OBJECT mplsLdpEntityFrameRelayMergeCap
594 "Write access is not required."
596 OBJECT mplsLdpEntityFrameRelayVcDirectionality
599 "Write access is not required."
601 OBJECT mplsLdpEntityFrameRelayStorageType
604 "Write access is not required."
606 OBJECT mplsLdpEntityFrameRelayRowStatus
607 SYNTAX RowStatus { active(1) }
610 "Write access is not required, and active is the
611 only status that needs to be supported."
613 OBJECT mplsLdpEntityFrameRelayLRMaxDlci
616 "Write access is not required."
619 OBJECT mplsLdpEntityFrameRelayLRLen
622 "Write access is not required."
624 OBJECT mplsLdpEntityFrameRelayLRStorageType
627 "Write access is not required."
629 OBJECT mplsLdpEntityFrameRelayLRRowStatus
630 SYNTAX RowStatus { active(1) }
633 "Write access is not required, and active is the
634 only status that needs to be supported."
635 ::= { mplsLdpFrameRelayCompliances 2 }
638 -- units of conformance
641 mplsLdpFrameRelayGroup OBJECT-GROUP
643 mplsLdpEntityFrameRelayIfIndexOrZero,
644 mplsLdpEntityFrameRelayMergeCap,
645 mplsLdpEntityFrameRelayLRComponents,
646 mplsLdpEntityFrameRelayVcDirectionality,
647 mplsLdpEntityFrameRelayStorageType,
648 mplsLdpEntityFrameRelayRowStatus,
649 mplsLdpEntityFrameRelayLRMaxDlci,
650 mplsLdpEntityFrameRelayLRLen,
651 mplsLdpEntityFrameRelayLRStorageType,
652 mplsLdpEntityFrameRelayLRRowStatus,
653 mplsLdpFrameRelaySessionMaxDlci,
654 mplsLdpFrameRelaySessionLen
658 "Objects that apply to all MPLS LDP implementations
659 using Frame Relay as the Layer 2."
660 ::= { mplsLdpFrameRelayGroups 1 }