idnits 2.17.1 draft-ietf-mpls-ldp-mib-09.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 2724 has weird spacing: '...ndex is creat...' == Line 4419 has weird spacing: '... (Since addin...' == Line 4795 has weird spacing: '...for the purpo...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 2002) is 7836 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC3291' is defined on line 4654, but no explicit reference was found in the text == Unused Reference: 'RFC2514' is defined on line 4693, but no explicit reference was found in the text == Unused Reference: 'RFC2515' is defined on line 4700, but no explicit reference was found in the text == Unused Reference: 'RFC3215' is defined on line 4718, but no explicit reference was found in the text == Unused Reference: 'RFC3037' is defined on line 4721, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 3036 (Obsoleted by RFC 5036) ** Obsolete normative reference: RFC 3291 (Obsoleted by RFC 4001) == Outdated reference: A later version (-14) exists of draft-ietf-mpls-lsr-mib-08 == Outdated reference: A later version (-10) exists of draft-ietf-mpls-tc-mib-04 -- Obsolete informational reference (is this intentional?): RFC 2570 (Obsoleted by RFC 3410) Summary: 12 errors (**), 0 flaws (~~), 12 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group J. Cucchiara 2 Internet-Draft Crescent Networks 3 Expires April 2003 H. Sjostrand 4 IP Unplugged 5 J. Luciani 6 Crescent Networks 7 October 2002 9 Definitions of Managed Objects for 10 the Multiprotocol Label Switching, Label Distribution Protocol (LDP) 12 14 Status of this Memo 16 This document is an Internet-Draft and is in full conformance with 17 all provisions of Section 10 of RFC 2026. Internet-Drafts are 18 working documents of the Internet Engineering Task Force (IETF), its 19 areas, and its working groups. Note that other groups may also 20 distribute working documents as Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress". 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html 33 Distribution of this document is unlimited. Please send comments to 34 the Multiprotocol Label Switching (mpls) Working Group, mpls@uu.net. 36 Copyright Notice 38 Copyright (C) The Internet Society (2002). All Rights Reserved. 40 Abstract 42 This memo defines a portion of the Management Information Base (MIB) 43 for use with network management protocols in the Internet community. 44 In particular, it describes managed objects for the Multiprotocol 45 Label Switching, Label Distribution Protocol (LDP). 47 Table of Contents 49 1 Introduction ................................................. 3 50 2 The SNMP Management Framework ................................ 3 51 3 Structure of the MIB ......................................... 5 52 3.1 Overview ................................................... 5 53 3.2 Future Considerations ...................................... 5 54 3.3 Interface Indexing ......................................... 6 55 3.4 Differences from the LDP Specification ..................... 6 56 3.5 The MPLS-LDP-MIB Module .................................... 6 57 3.5.1 The LDP Entity Table ..................................... 7 58 3.5.1.1 Changing Values After Session Establishment ............ 7 59 3.5.2 The LDP Entity Statistics Table .......................... 8 60 3.5.3 The LDP Peer Table ....................................... 8 61 3.5.4 The LDP Session Table .................................... 8 62 3.5.5 The LDP Session Statistics Table ......................... 9 63 3.5.6 The LDP Hello Adjacencies Table .......................... 9 64 3.5.7 The LDP LSP Table ........................................ 9 65 3.5.8 The FEC Table ............................................ 10 66 3.5.9 The LDP Session Peer Address Table ....................... 10 67 3.6 LDP Notifications .......................................... 10 68 4 MPLS Label Distribution Protocol MIB Definitions ............. 11 69 4.1 The MPLS-LDP-GENERIC-MIB Module ............................ 54 70 4.2 The MPLS-LDP-ATM-MIB Module ................................ 60 71 4.2.1 The LDP ATM Session Table ................................ 60 72 4.3 The MPLS-LDP-FRAME-RELAY-MIB Module ........................ 73 73 4.3.1 The LDP Frame Relay Session Table ........................ 74 74 5 Revision History ............................................. 85 75 5.1 Changes from .............. 85 76 5.2 Changes from .............. 87 77 5.3 Changes from .............. 88 78 5.4 Changes from .............. 88 79 5.5 Changes from .............. 90 80 5.6 Changes from .............. 92 81 5.7 Changes from .............. 94 82 5.8 Changes from .............. 94 83 5.9 Changes from .............. 95 84 6 Acknowledgments .............................................. 96 85 7 Normative References ......................................... 97 86 8 Informative References ....................................... 99 87 9 Security Considerations ...................................... 100 88 10 Authors' Addresses .......................................... 100 89 11 Full Copyright Statement .................................... 101 91 1. Introduction 93 This document defines 4 MIB Modules which together support the 94 configuration and monitoring of the Label Distribution Protocol 95 (LDP). The Label Distribution Protocol (LDP) [RFC3036] is one type 96 of Multi Protocol Label Switching (MPLS) protocols described in 97 [RFC3031] and [RFC3032]. Utilizing all 4 MIB Modules allows an 98 operator to configure LDP sessions using Layer 2 media of Ethernet, 99 ATM and Frame Relay as described in [RFC3036], [RFC3034] and 100 [RFC3035]. 102 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 103 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 104 document are to be interpreted as described in RFC 2119 [RFC2119]. 106 2. The SNMP Management Framework 108 The SNMP Management Framework presently consists of five major 109 components: 111 o An overall architecture, described in RFC 2571 [RFC2571]. 113 o Mechanisms for describing and naming objects and events for the 114 purpose of management. The first version of this Structure of 115 Management Information (SMI) is called SMIv1 and described in 116 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 117 1215 [RFC1215]. The second version, called SMIv2, is described 118 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 119 STD 58, RFC 2580 [RFC2580]. 121 o Message protocols for transferring management information. The 122 first version of the SNMP message protocol is called SNMPv1 and 123 described in STD 15, RFC 1157 [RFC1157]. A second version of 124 the SNMP message protocol, which is not an Internet standards 125 track protocol, is called SNMPv2c and described in RFC 1901 126 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 127 message protocol is called SNMPv3 and described in RFC 1906 128 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 130 o Protocol operations for accessing management information. The 131 first set of protocol operations and associated PDU formats is 132 described in STD 15, RFC 1157 [RFC1157]. A second set of 133 protocol operations and associated PDU formats is described in 134 RFC 1905 [RFC1905]. 136 o A set of fundamental applications described in RFC 2573 137 [RFC2573] and the view-based access control mechanism described 138 in RFC 2575 [RFC2575]. 140 A more detailed introduction to the current SNMP Management Framework 141 can be found in RFC 2570 [RFC2570]. 143 Managed objects are accessed via a virtual information store, termed 144 the Management Information Base or MIB. Objects in the MIB are 145 defined using the mechanisms defined in the SMI. 147 This memo specifies a MIB module that is compliant to the SMIv2. A 148 MIB conforming to the SMIv1 can be produced through the appropriate 149 translations. The resulting translated MIB must be semantically 150 equivalent, except where objects or events are omitted because no 151 translation is possible (use of Counter64). Some machine readable 152 information in SMIv2 will be converted into textual descriptions in 153 SMIv1 during the translation process. However, this loss of machine 154 readable information is not considered to change the semantics of the 155 MIB. 157 3. Structure of the MIB 159 This section describes the structure of the LDP MIB. 161 3.1. Overview 163 There are 4 MIB Modules in this document. These MIB Modules are the 164 MPLS-LDP-MIB, the MPLS-LDP-GENERIC-MIB, the MPLS-LDP-ATM-MIB and the 165 MPLS-LDP-FRAME-RELAY-MIB. The MPLS-LDP-MIB defines objects which are 166 specific to LDP without any Layer 2 objects. The MPLS-LDP-GENERIC- 167 MIB defines Layer 2 Per Platform Label Space objects for use with the 168 MPLS-LDP-MIB. The MPLS-LDP-ATM-MIB defines Layer 2 Asynchronous 169 Transfer Mode (ATM) objects for use with the MPLS-LDP-MIB. The 170 MPLS-LDP-FRAME-RELAY-MIB defines Layer 2 FRAME-RELAY objects for use 171 with the MPLS-LDP-MIB. 173 The MPLS-LDP-MIB Module MUST be supported and at least one of the 174 Layer 2 MIB Modules MUST be supported. As an example, if an LSR 175 implementation wants to support LDP utilizing a Layer 2 of Ethernet, 176 then the MPLS-LDP-GENERIC-MIB Module would be supported. If an LSR 177 implementation wants to support LDP utilizing a Layer 2 of ATM, then 178 the MPLS-LDP-ATM-MIB Module would be supported. If an LSR 179 implementation wants to support LDP utilizing a Layer 2 of FRAME- 180 RELAY, then the MPLS-LDP-FRAME-RELAY-MIB Module would be supported. 181 An LDP implementation that utilizes all 3 Layer 2 media (Ethernet, 182 Frame-Relay, ATM) would support all 4 MIB Modules. Each of the 183 Modules will be discussed in detail in the following sections. 185 There are 2 Compliance statements for each MIB Module. One which is 186 for FULL Compliance which includes configuration and monitoring via 187 SNMP. The other is a READ-ONLY Compliance which is only monitoring 188 via SNMP. 190 3.2. Future Considerations 192 The LDP Specification [RFC3036] does not specify the use of VPNs or 193 multicast for LDP, and thus, objects related to these areas have not 194 been included in the MIB. 196 This MIB does not include VP merge configuration either. [RFC2684] 197 does not yet describe this capability and so it has been excluded 198 from the MIB. 200 These areas need to be specified in the LDP Specification prior to 201 being added in this or any other MIB. 203 3.3. Interface Indexing 205 Interface Indexes as specified in [RFC2863] are used in the MIB. The 206 descriptions of the ifIndexes denote which ifIndex is being used. 207 NOTE: the use of ifIndex is for actual existing connections. 209 3.4. Differences from the LDP Specification 211 Currently, there are 3 differences between this specification and the 212 LDP Specification. As previously mentioned, this MIB is almost 213 entirely based on the LDP specification. The differences are 214 documented here in the hope to avoid any confusion between the two 215 documents. 217 The first difference is that the LDP Entity Table contains some 218 DEFVAL clauses which are not specified explicitely in the LDP 219 Specification. These values, although not documented in the LDP 220 Specification are widely used by existing LDP MIB implementations and 221 thus, have been adopted within this MIB. Please note, they can 222 certainly be changed during row creation or a subsequent set request. 224 A second difference is the mplsLdpEntityConfGenericLabelRangeTable. 225 This table, although provided as a way to reserve a range of generic 226 labels, does not exist in the LDP Specification. It was added to the 227 MIB due to a request from the working group and because this table 228 was considered useful for reserving a range of generic labels. 230 The third difference is documented by the TEXTUAL-CONVENTION, 231 MplsAtmVcIdentifier which is in the MPLS-TC-MIB [MPLSTCMIB]. This TC 232 was added to restrict vci values to be greater than 31 as described 233 in RFC 3035 [RFC3035]. 235 3.5. The MPLS-LDP-MIB Module 237 This MIB Module contains objects which would be common to all LDP 238 implementations. This MIB Module MUST always be implemented along 239 with one or more of the other Layer 2 MIB Modules. 241 NOTE, this table allows the LSR to initiation and receive requests to 242 establish LDP sessions. As the LDP protocol distributes labels and 243 establishes sessions with Peers most of the tables in this MIB are 244 populated by the agent as instructed by the LDP protocol. The 245 exception is the mplsFecTable and the mplsLdpLspFecTable which can be 246 configured by the operator to specify Forwarding Equivalence Class 247 information for an LSP. 249 Each table in this MIB Module is described in the following 250 subsections. 252 3.5.1. The LDP Entity Table 254 The MPLS-LDP-MIB provides objects to configure/set-up potential LDP 255 sessions on a specific LSR. The mplsLdpEntityTable is used to 256 configure potential LDP Sessions, where each row in the table 257 represents a potential LDP Session. 259 Each entry/row in this table represents a single LDP Entity. There 260 is no maximum number of LDP Entities specified. However, there is an 261 mplsLdpEntityIndexNext object which should be retrieved by the 262 command generator prior to creating an LDP Entity. If the 263 mplsLdpEntityIndexNext object is zero, this indicates that the LSR is 264 not able to create another LDP Entity at that time. 266 3.5.1.1. Changing Values After Session Establishment 268 One way to manually modify a session's parameters is by using SNMP to 269 change the MIB objects related to that session. Please note special 270 care should be taken if MIB objects which are used in the MPLS LDP 271 Session Initialization need to be modified. If the modification of 272 any of these MIB variables takes place anytime after the start of 273 session intialization, then the entire session must be halted. Any 274 information learned by that session must be discarded. The objects 275 should then be modified, and session initialization started. 277 For example, assume that an operator wishes to change the 278 configuration of a Label Range which is used by a Session that has 279 already been established. The operator should change the 280 mplsLdpEntityAdminStatus to "disable(2)". Setting the 281 mplsLdpEntityAdminStatus to "disable(2)" will cause the session to be 282 torn down (i.e. this will signal to LDP that it should send out tear 283 down messages for that session). Also, all information related to 284 that session should be removed from this MIB by the Agent. This 285 includes Peer information (i.e. relevant row in the mplsPeerTable) 286 and Session statistics (i.e. releveant row in the mplsLdpSesTable). 287 Also, if the LSR MIB is implemented and the optional Mapping Table 288 objects are implemented, then all information related to the LSPs in 289 this session should be removed from these MIBs. [For more information 290 please see the section on "The Mapping Tables".] At this point, the 291 operator could modify the Label Range. Lastly, the operator should 292 set the mplsLdpEntityAdminStatus to "enable(1)". At this point 293 session initialization should occur. The LDP Entity goes through the 294 Session Initialization in order to communicate the new Label Ranges 295 to the Peer and establish new LSPs. 297 3.5.2. The LDP Entity Statistics Table 299 The mplsLpdEntityStatsTable is a read-only table which contains 300 statistical information related to failed attempts to establish 301 sessions. Each row in this table is related to a single LDP entity 302 and this table AUGMENTS an mplsLdpEntityEntry. This table could be 303 used to give insight into how to reconfigure values so that a session 304 could be successfully established. For example, if the 305 mpslLdpSesRejectedLRErrors Counter object was increasing, then this 306 would indicate that the Label Range (LR) may need to be adjusted. 308 3.5.3. The LDP Peer Table 310 The LDP Peer Table is a read-only table which contains information 311 about LDP Peers known to LDP Entities. In other words, the Peer 312 information is learned by LDP through initialization or discovery. 313 This table should be populated by the agent as directed by the LDP 314 protocol. 316 A row in this table is related to one or more rows in the Hello 317 Adjacency Table and related to a single row in the Session Table. The 318 values in the Peer table are specific to a Peer and may or may not be 319 the same values used in the session. The reason is that the Peer and 320 Entity negotiate certain values. The Entity's values are configured 321 in the mplsLdpEntityTable and the Peer's values are learned (and 322 placed into the mplsLdpPeerTable). The mplsLdpSessionTable shows the 323 values used in establishing the session. 325 One example, of when the Peer's values and the Session's values may 326 differ is with the Peer's Path Limit information. The Peer's Path 327 Limit information is learned from the session initialization phase. 328 The actual value for the Path Vector Limit is the Peer's value and 329 may not be the same value that appears in the session. There could 330 be a mismatch in this value between the Entity and the Peer. In the 331 event of a mismatch, then the session will use the Path Limit set by 332 the Entity (and not the Peer). 334 The Peer Table information was placed in a separate table from the 335 Session information to allow for a more comprehensive and coherent 336 MIB model. 338 3.5.4. The LDP Session Table 340 The LDP Session Table is a read-only table. Each entry in this table 341 represents a single session between an LDP Entity and a Peer. The 342 mplsLdpSessionEntry AUGMENTS the mplsLdpPeerEntry. 344 The information in this table is learned during session 345 establishment. NOTE: rows in this table will appear during session 346 intialization. 348 3.5.5. The LDP Session Statistics Table 350 The MPLS LDP Session Stats Table is a read-only table which contains 351 statistical information on sessions. 353 3.5.6. The LDP Hello Adjacencies Table 355 This is a table of all adjacencies between all LDP Entities and all 356 LDP Peers. A Session may have one or more adjacencies. A session 357 should not have zero adjacencies, because this indicates that the 358 session has lost contact with the Peer. A session which has zero 359 Hello Adjacencies should be eventually removed. 361 3.5.7. The LDP LSP Table 363 The Label Information Base (LIB) contains information about labels 364 learned by the LSR. The LIB for LDP, CR-LDP and MPLS-RSVP (i.e. all 365 currently defined MPLS protocols) is represented in the LSR MIB 366 [LSRMIB]. The LIB is represented by the LSR MIB's mplsXCTable (mpls 367 Cross Connect Table), mplsInSegmentTable (mpls In Segment Table) and 368 the mplsOutSegmentTable (mpls Out Segment Table). The mplsXCTable 369 models the cross-connection of the ingress label with a specific 370 egress label. The mplsInSegmentTable stores the ingress label's 371 information, and the mplsOutSegmentTable stores the egress label's 372 information. 374 The LDP Session that created the LSP and the LSP's (ingress label, 375 egress label) pair along with other information is contained in the 376 LSR MIB's mplsXCTable, the mplsInSegmentTable and the 377 mplsOutSegmentTable. 379 In order to utilize the LSR MIB's mplsXCTable, mplsInSegmentTable and 380 mplsOutSegmentTable for LDP LSPs, there needs to be a mechanism to 381 associate LDP sessions with LDP LSPs created as a result of those LDP 382 sessions. The mplsLdpLspTable in this MIB contains RowPointers which 383 point to instances of objects in the LSR MIB's mplsXCTable, 384 mplsInSegmentTable and mplsOutSegmentTable. 386 In order to expedite development, these RowPointer objects have been 387 made optional in the conformance section of the MIB. They only need 388 to be supported if the LSR MIBs mplsInSegmentTable, 389 mplsOutSegmentTable and mplsXCTable are implemented. 391 As discussed in the section, "Changing Values after Session 392 Establishment", if a session is torn down, then all the information 393 related to this session, must be removed from the both LDP MIB and, 394 if implemented, from the LSR MIB. 396 3.5.8. The FEC Table 398 The FEC Table is a table which contains FEC (Forwarding Equivalence 399 Class) information. Each entry/row represents a single FEC Element. 400 There is also an LDP LSP FEC Table, mplsLdpLspFecTable, which 401 associates FECs with the LSPs. 403 3.5.9. The LDP Session Peer Address Table 405 The MPLS LDP Session Peer Address Table is a table which extends the 406 mplsLdpSessionTable. This table is a read-only table which stores 407 Addresses learned after session initialization via Address Message 408 advertisement. 410 3.6. LDP Notifications 412 Currently, there are several notifications which are specific for 413 LDP. These are described in this section. 415 The mplsLdpInitSesThresholdExceeded notification indicates to the 416 operator that there may be a misconfigured mplsLdpEntityEntry because 417 the session associated with this Entity is not being established, and 418 the Entity keeps trying to establish the session. A side effect of 419 this situation is that a row in the mplsLdpSessionTable may not be 420 reaching the operational state as indicated by the mplsLdpSesState 421 object. If the value of mplsLdpEntityInitSesThreshold is 0 (zero) 422 then this is equal to specifying the value of infinity for the 423 threshold, and the mplsLdpInitSesThresholdExceeded notification will 424 never be sent. 426 The mplsLdpPathVectorLimitMismatch notification is generated when 427 there is a mismatch in the Path Vector Limits between the Entity and 428 Peer during session initialization. The session uses the value which 429 is configured as the Entity's Path Vector Limit. However, a 430 notification should be generated to indicate that a mismatch 431 occurred. For further details, please see Section 3.5.3 of the LDP 432 Specification [RFC3036]. 434 The mplsLdpSessionUp and mplsLdpSessionDown notifications are 435 generated when there is an appropriate change in the mplsLdpSesState 436 object, e.g. when sessions change state (Up to Down for the 437 mplsLdpSessionDown trap, or Down to Up for the mplsLdpSessionUp 438 trap). 440 4. MPLS Label Distribution Protocol MIB Definitions 442 MPLS-LDP-MIB DEFINITIONS ::= BEGIN 444 IMPORTS 445 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, 446 Integer32, Counter32, Unsigned32 447 FROM SNMPv2-SMI 448 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 449 FROM SNMPv2-CONF 451 RowPointer, RowStatus, TimeInterval, TruthValue, 452 TimeStamp, StorageType 453 FROM SNMPv2-TC 455 InterfaceIndex 456 FROM IF-MIB 458 InetAddressType, 459 InetAddress, 460 InetPortNumber 461 FROM INET-ADDRESS-MIB 463 mplsMIB, 464 MplsLabel, 465 MplsLabelDistributionMethod, 466 MplsLdpIdentifier, 467 MplsLdpLabelType, 468 MplsLspType, 469 MplsLsrIdentifier, 470 MplsRetentionMode 472 FROM MPLS-TC-MIB 473 ; 475 mplsLdpMIB MODULE-IDENTITY 476 LAST-UPDATED "200208081200Z" -- 8 August 2002 477 ORGANIZATION "Multiprotocol Label Switching (mpls) 478 Working Group" 479 CONTACT-INFO 480 "Joan Cucchiara (jcucchiara@crescentnetworks.com) 481 Crescent Networks 483 Hans Sjostrand (hans@ipunplugged.com) 484 ipUnplugged 486 James V. Luciani (jluciani@crescentnetworks.com) 487 Crescent Networks 488 Working Group Chairs: 489 George Swallow, email: swallow@cisco.com 490 Loa Andersson, email: loa.andersson@utfors.se 492 MPLS Working Group, email: mpls@uu.net 493 " 494 DESCRIPTION 495 "This MIB contains managed object definitions for the 496 'Multiprotocol Label Switching, Label Distribution 497 Protocol, LDP' document." 499 REVISION "200208081200Z" -- 8 August 2002 500 DESCRIPTION 501 "Initial version published as part of RFC XXXX." 503 ::= { mplsMIB 3 } -- to be assigned 505 --**************************************************************** 507 mplsLdpObjects OBJECT IDENTIFIER ::= { mplsLdpMIB 1 } 508 mplsLdpNotifications OBJECT IDENTIFIER ::= { mplsLdpMIB 2 } 509 mplsLdpConformance OBJECT IDENTIFIER ::= { mplsLdpMIB 3 } 511 --**************************************************************** 512 -- MPLS LDP Objects 513 --**************************************************************** 515 mplsLdpLsrObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 1 } 517 mplsLdpEntityObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 2 } 519 -- 520 -- The MPLS Label Distribution Protocol's 521 -- Label Switching Router Objects 522 -- 524 mplsLdpLsrId OBJECT-TYPE 525 SYNTAX MplsLsrIdentifier 526 MAX-ACCESS read-only 527 STATUS current 528 DESCRIPTION 529 "The LSR's Identifier." 530 ::= { mplsLdpLsrObjects 1 } 532 mplsLdpLsrLoopDetectionCapable OBJECT-TYPE 533 SYNTAX INTEGER { 534 none(1), 535 other(2), 536 hopCount(3), 537 pathVector(4), 538 hopCountAndPathVector(5) 539 } 540 MAX-ACCESS read-only 541 STATUS current 542 DESCRIPTION 543 "A indication of whether this 544 Label Switching Router supports 545 loop detection. 547 none(1) -- Loop Detection is not supported 548 on this LSR. 550 other(2) -- Loop Detection is supported but 551 by a method other than those 552 listed below. 554 hopCount(3) -- Loop Detection is supported by 555 Hop Count only. 557 pathVector(4) -- Loop Detection is supported by 558 Path Vector only. 560 hopCountAndPathVector(5) -- Loop Detection is 561 supported by both Hop Count 562 And Path Vector. 564 Since Loop Detection is determined during 565 Session Initialization, an individual session 566 may not be running with loop detection. This 567 object simply gives an indication of whether or not the 568 LSR has the ability to support Loop Detection and 569 which types." 570 ::= { mplsLdpLsrObjects 2 } 572 -- 573 -- The MPLS Label Distribution Protocol Entity Objects 574 -- 576 mplsLdpEntityLastChange OBJECT-TYPE 577 SYNTAX TimeStamp 578 MAX-ACCESS read-only 579 STATUS current 580 DESCRIPTION 581 "The value of sysUpTime at the time of the most 582 recent addition or deletion of an entry 583 to the mplsLdpEntityTable/mplsLdpEntityStatsTable. 585 If no such changes have occurred since the last 586 re-initialization of the local management subsystem, 587 then this object contains a zero value." 588 ::= { mplsLdpEntityObjects 1 } 590 mplsLdpEntityIndexNext OBJECT-TYPE 591 SYNTAX Unsigned32 (0..4294967295) 592 MAX-ACCESS read-only 593 STATUS current 594 DESCRIPTION 595 "This object contains an appropriate value to 596 be used for mplsLdpEntityIndex when creating 597 entries in the mplsLdpEntityTable. The value 598 0 indicates that no unassigned entries are 599 available. To obtain the mplsLdpEntityIndex 600 value for a new entry, the manager issues a 601 management protocol retrieval operation to obtain 602 the current value of this object. After each 603 retrieval, the agent should modify the value to 604 the next unassigned index." 605 ::= { mplsLdpEntityObjects 2 } 607 mplsLdpEntityTable OBJECT-TYPE 608 SYNTAX SEQUENCE OF MplsLdpEntityEntry 609 MAX-ACCESS not-accessible 610 STATUS current 611 DESCRIPTION 612 "This table contains information about the 613 MPLS Label Distribution Protocol Entities which 614 exist on this Label Switching Router (LSR)." 615 ::= { mplsLdpEntityObjects 3 } 617 mplsLdpEntityEntry OBJECT-TYPE 618 SYNTAX MplsLdpEntityEntry 619 MAX-ACCESS not-accessible 620 STATUS current 621 DESCRIPTION 622 "An entry in this table represents an LDP entity. 623 An entry can be created by a network administrator 624 or by an SNMP agent as instructed by LDP." 625 INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex } 626 ::= { mplsLdpEntityTable 1 } 628 MplsLdpEntityEntry ::= SEQUENCE { 629 mplsLdpEntityLdpId MplsLdpIdentifier, 630 mplsLdpEntityIndex Unsigned32, 631 mplsLdpEntityProtocolVersion Integer32, 632 mplsLdpEntityAdminStatus INTEGER, 633 mplsLdpEntityOperStatus INTEGER, 634 mplsLdpEntityTcpDscPort InetPortNumber, 635 mplsLdpEntityUdpDscPort InetPortNumber, 636 mplsLdpEntityMaxPduLength Unsigned32, 637 mplsLdpEntityKeepAliveHoldTimer Integer32, 638 mplsLdpEntityHelloHoldTimer Integer32, 639 mplsLdpEntityInitSesThreshold Integer32, 640 mplsLdpEntityLabelDistMethod MplsLabelDistributionMethod, 641 mplsLdpEntityLabelRetentionMode MplsRetentionMode, 642 mplsLdpEntityPathVectorLimit Integer32, 643 mplsLdpEntityHopCountLimit Integer32, 644 mplsLdpEntityTargetPeer TruthValue, 645 mplsLdpEntityTargetPeerAddrType InetAddressType, 646 mplsLdpEntityTargetPeerAddr InetAddress, 647 mplsLdpEntityLabelType MplsLdpLabelType, 648 mplsLdpEntityDiscontinuityTime TimeStamp, 649 mplsLdpEntityStorageType StorageType, 650 mplsLdpEntityRowStatus RowStatus 651 } 653 mplsLdpEntityLdpId OBJECT-TYPE 654 SYNTAX MplsLdpIdentifier 655 MAX-ACCESS not-accessible 656 STATUS current 657 DESCRIPTION 658 "The LDP identifier." 659 REFERENCE 660 "[RFC3036] LDP Specification, Section on LDP Identifiers." 661 ::= { mplsLdpEntityEntry 1 } 663 mplsLdpEntityIndex OBJECT-TYPE 664 SYNTAX Unsigned32 (1..4294967295) 665 MAX-ACCESS not-accessible 666 STATUS current 667 DESCRIPTION 668 "This index is used as a secondary index to uniquely 669 identify this row. Before creating a row in this table, 670 the 'mplsLdpEntityIndexNext' object should be retrieved. 671 That value should be used for the value of this index 672 when creating a row in this table. (NOTE: if a value 673 of zero (0) is retrieved, that indicates that no rows 674 can be created in this table at this time. 676 A secondary index (this object) is meaningful to some 677 but not all, LDP implementations. For example 678 in an LDP implementation which uses PPP would 679 use this index to differentiate PPP sub-links. 681 Another way to use this index is to give this the 682 value of ifIndex. However, this is dependant 683 on the implementation." 685 ::= { mplsLdpEntityEntry 2 } 687 mplsLdpEntityProtocolVersion OBJECT-TYPE 688 SYNTAX Integer32(1..65535) 689 MAX-ACCESS read-create 690 STATUS current 691 DESCRIPTION 692 "The version number of the LDP protocol which will be 693 used in the session initialization message. 695 Section 3.5.3 in the LDP Specification specifies 696 that the version of the LDP protocol is negotiated during 697 session establishment. The value of this object 698 represents the value that is sent in the initialization 699 message." 700 REFERENCE 701 "[RFC3036], LDP Specification, Section 3.5.3 Initialization 702 Message." 703 DEFVAL { 1 } 704 ::= { mplsLdpEntityEntry 3 } 706 mplsLdpEntityAdminStatus OBJECT-TYPE 707 SYNTAX INTEGER { 708 enable(1), 709 disable(2) 710 } 711 MAX-ACCESS read-create 712 STATUS current 713 DESCRIPTION 714 "The administrative status of this LDP Entity. 715 If this object is changed from 'enable' to 'disable' 716 and this entity has already attempted to establish 717 contact with a Peer, then all contact with that 718 Peer is lost and all information from that Peer 719 needs to be removed from the MIB. (This implies 720 that the network management subsystem should clean 721 up any related entry in the mplsLdpPeerTable). 723 At this point the user is able to change values 724 which are related to this entity. 726 When the admin status is set back to 'up', then 727 this Entity will attempt to establish a new session 728 with the Peer." 729 DEFVAL { enable } 730 ::= { mplsLdpEntityEntry 4 } 732 mplsLdpEntityOperStatus OBJECT-TYPE 733 SYNTAX INTEGER { 734 unknown(1), 735 enabled(2), 736 disabled(3) 737 } 738 MAX-ACCESS read-only 739 STATUS current 740 DESCRIPTION 741 "The operational status of this LDP Entity." 742 ::= { mplsLdpEntityEntry 5 } 744 mplsLdpEntityTcpDscPort OBJECT-TYPE 745 SYNTAX InetPortNumber 746 MAX-ACCESS read-create 747 STATUS current 748 DESCRIPTION 749 "The TCP Discovery Port for 750 LDP. The default value is the well-known 751 value of this port." 752 REFERENCE 753 "[RFC3036], LDP Specification, Section 2.4.1, 754 Basic Discovery Mechanism, Section 2.4.2, 755 Extended Discovery Mechanism, Section 756 3.10, Well-known Numbers, and Section 3.10.1. 757 UDP and TCP Ports." 758 DEFVAL { 646 } 759 ::= { mplsLdpEntityEntry 6 } 761 mplsLdpEntityUdpDscPort OBJECT-TYPE 762 SYNTAX InetPortNumber 763 MAX-ACCESS read-create 764 STATUS current 765 DESCRIPTION 766 "The UDP Discovery Port for 767 LDP. The default value is the 768 well-known value for this port." 769 REFERENCE 770 "[RFC3036], LDP Specification, Section 2.4.1, 771 Basic Discovery Mechanism, Section 2.4.2, 772 Extended Discovery Mechanism, Section 773 3.10, Well-known Numbers, and Section 3.10.1. 774 UDP and TCP Ports." 775 DEFVAL { 646 } 776 ::= { mplsLdpEntityEntry 7 } 778 mplsLdpEntityMaxPduLength OBJECT-TYPE 779 SYNTAX Unsigned32 (256..65535) 780 UNITS "octets" 781 MAX-ACCESS read-create 782 STATUS current 783 DESCRIPTION 784 "The maximum PDU Length that is sent in 785 the Common Session Parameters of an Initialization 786 Message. According to the LDP Specification [RFC3036] 787 a value of 255 or less specifies the 788 default maximum length of 4096 octets, this is why 789 the value of this object starts at 256. The operator 790 should explicitely choose the default value (i.e. 4096), 791 or some other value. 793 The receiving LSR MUST calculate the maximum PDU 794 length for the session by using the smaller of its and 795 its peer's proposals for Max PDU Length." 796 REFERENCE 797 "[RFC3036], LDP Specification, Section 3.5.3. 798 Initialization Message." 799 DEFVAL { 4096 } 800 ::= { mplsLdpEntityEntry 8 } 802 mplsLdpEntityKeepAliveHoldTimer OBJECT-TYPE 803 SYNTAX Integer32 (1..65535) 804 UNITS "seconds" 805 MAX-ACCESS read-create 806 STATUS current 807 DESCRIPTION 808 "The 16-bit integer value which is the proposed keep 809 alive hold timer for this LDP Entity." 810 DEFVAL { 40 } 811 ::= { mplsLdpEntityEntry 9 } 813 mplsLdpEntityHelloHoldTimer OBJECT-TYPE 814 SYNTAX Integer32 (0..65535) 815 UNITS "seconds" 816 MAX-ACCESS read-create 817 STATUS current 818 DESCRIPTION 819 "The 16-bit integer value which is the proposed Hello 820 hold timer for this LDP Entity. The Hello Hold time 821 in seconds. 823 An LSR maintains a record of Hellos received 824 from potential peers. This object represents 825 the Hold Time in the Common Hello Parameters TLV of 826 the Hello Message. 828 A value of 0 is a default value and should be 829 interpretted in conjunction with the 830 mplsLdpEntityTargetPeer object. 832 If the value of this object is 0: if the value of the 833 mplsLdpEntityTargetPeer object is false(2), then this 834 specifies that the Hold Time's actual default value is 835 15 seconds (i.e. the default Hold time for Link Hellos 836 is 15 seconds). Otherwise if the value of the 837 mplsLdpEntityTargetPeer object is true(1), then this 838 specifies that the Hold Time's actual default value is 839 45 seconds (i.e. the default Hold time for Targeted 840 Hellos is 45 seconds). 842 A value of 65535 means infinite (i.e. wait forever). 844 All other values represent the amount of time in 845 seconds to wait for a Hello Message. Setting the 846 hold time to a value smaller than 15 is not 847 recommended, although not forbidden according 848 to [RFC3036]." 849 REFERENCE 850 "[RFC3036], LDP Specification, Section 3.5.2., 851 Hello Message." 852 DEFVAL { 0 } 853 ::= { mplsLdpEntityEntry 10 } 855 mplsLdpEntityInitSesThreshold OBJECT-TYPE 856 SYNTAX Integer32(0..100) 857 MAX-ACCESS read-create 858 STATUS current 859 DESCRIPTION 860 "When attempting to establish a session with a 861 given Peer, the given LDP Entity should 862 send out the SNMP notification, 863 'mplsLdpInitSesThresholdExceeded', when 864 the number of Session Initialization messages sent 865 exceeds this threshold. The notification is 866 used to notify an operator when this Entity and 867 its Peer are possibily engaged in an endless 868 sequence of messages as each NAKs the other's 869 Initialization messages with Error Notification 870 messages. Setting this threshold which triggers 871 the notification is one way to 872 notify the operator. 874 A value of 0 (zero) for this object 875 indicates that the threshold is infinity, thus 876 the SNMP notification will never be generated." 877 REFERENCE 878 "[RFC3036], LDP Specification, 879 Section 2.5.3 Session Initialization." 880 DEFVAL { 8 } 881 ::= { mplsLdpEntityEntry 11 } 883 mplsLdpEntityLabelDistMethod OBJECT-TYPE 884 SYNTAX MplsLabelDistributionMethod 885 MAX-ACCESS read-create 886 STATUS current 887 DESCRIPTION 888 "For any given LDP session, the method of 889 label distribution must be specified." 890 ::= { mplsLdpEntityEntry 12 } 892 mplsLdpEntityLabelRetentionMode OBJECT-TYPE 893 SYNTAX MplsRetentionMode 894 MAX-ACCESS read-create 895 STATUS current 896 DESCRIPTION 897 "The LDP Entity can be configured to use either 898 conservative or liberal label retention mode. 900 If the value of this object is conservative(1) 901 then advertized label mappings are retained 902 only if they will be used to forward packets, 903 i.e. if label came from a valid next hop. 905 If the value of this object is liberal(2) 906 then all advertized label mappings are retained 907 whether they are from a valid next hop or not." 908 ::= { mplsLdpEntityEntry 13 } 910 mplsLdpEntityPathVectorLimit OBJECT-TYPE 911 SYNTAX Integer32 (0..255) 912 MAX-ACCESS read-create 913 STATUS current 914 DESCRIPTION 915 "If the value of this object is 0 (zero) then 916 Loop Dection for Path Vectors is disabled. 918 Otherwise, if this object has a value greater than 919 zero, then Loop Dection for Path Vectors is enabled, 920 and the Path Vector Limit is this value. 921 Also, the value of the object, 922 'mplsLdpLsrLoopDetectionCapable', must be set to 923 either 'pathVector(4)' or 'hopCountAndPathVector(5)', 924 if this object has a value greater than 0 (zero), 925 otherwise it is ignored." 926 REFERENCE 927 "[RFC3036], LDP Specification, Section 2.8 Loop Dection, 928 Section 3.4.5 Path Vector TLV." 929 ::= { mplsLdpEntityEntry 14 } 931 mplsLdpEntityHopCountLimit OBJECT-TYPE 932 SYNTAX Integer32 (0..255) 933 MAX-ACCESS read-create 934 STATUS current 935 DESCRIPTION 936 "If the value of this object is 0 (zero), 937 then Loop Detection using Hop Counters is 938 disabled. 940 If the value of this object is greater than 941 0 (zero) then Loop Detection using Hop 942 Counters is enabled, and this object 943 specifies this Entity's maximum allowable 944 value for the Hop Count. 945 Also, the value of the object 946 mplsLdpLsrLoopDetectionCapable must be set 947 to either 'hopCount(3)' or 948 'hopCountAndPathVector(5)' if this object 949 has a value greater than 0 (zero), otherwise 950 it is ignored." 951 DEFVAL { 0 } 952 ::= { mplsLdpEntityEntry 15 } 954 mplsLdpEntityTargetPeer OBJECT-TYPE 955 SYNTAX TruthValue 956 MAX-ACCESS read-create 957 STATUS current 958 DESCRIPTION 959 "If this LDP entity uses targeted peer then set 960 this to true." 961 DEFVAL { false } 962 ::= { mplsLdpEntityEntry 16 } 964 mplsLdpEntityTargetPeerAddrType OBJECT-TYPE 965 SYNTAX InetAddressType 966 MAX-ACCESS read-create 967 STATUS current 968 DESCRIPTION 969 "The type of the internetwork layer address used for 970 the Extended Discovery. This object indicates how 971 the value of mplsLdpEntityTargetPeerAddr is to 972 be interpreted." 973 ::= { mplsLdpEntityEntry 17 } 975 mplsLdpEntityTargetPeerAddr OBJECT-TYPE 976 SYNTAX InetAddress 977 MAX-ACCESS read-create 978 STATUS current 979 DESCRIPTION 980 "The value of the internetwork layer address used for 981 the Extended Discovery." 982 ::= { mplsLdpEntityEntry 18 } 984 mplsLdpEntityLabelType OBJECT-TYPE 985 SYNTAX MplsLdpLabelType 986 MAX-ACCESS read-create 987 STATUS current 988 DESCRIPTION 989 "Specifies the optional parameters for the LDP 990 Initialization Message. If the value is generic(1) 991 then no optional parameters will be sent in 992 the LDP Initialization message associated with 993 this Entity. 995 If the value is atmParameters(2) then 996 a row must be created in the mplsLdpEntityAtmParms 997 Table, which corresponds to this entry. 999 If the value is frameRelayParameters(3) then 1000 a row must be created in the mplsLdpEntityFrameRelayParms 1001 Table, which corresponds to this entry." 1002 REFERENCE 1003 "[RFC3036], LDP Specification, Section 3.5.3., 1004 Initialization Message." 1005 ::= { mplsLdpEntityEntry 19 } 1007 mplsLdpEntityDiscontinuityTime OBJECT-TYPE 1008 SYNTAX TimeStamp 1009 MAX-ACCESS read-only 1010 STATUS current 1011 DESCRIPTION 1012 "The value of sysUpTime on the most recent occasion 1013 at which any one or more of this entity's counters 1014 suffered a discontinuity. The relevant counters are the 1015 specific instances associated with this entity of 1016 any Counter32, or Counter64 object contained 1017 in the 'mplsLdpEntityStatsTable'. If no such 1018 discontinuities have occurred since the last 1019 re-initialization of the local management 1020 subsystem, then this object contains a zero 1021 value." 1022 ::= { mplsLdpEntityEntry 20 } 1024 mplsLdpEntityStorageType OBJECT-TYPE 1025 SYNTAX StorageType 1026 MAX-ACCESS read-create 1027 STATUS current 1028 DESCRIPTION 1029 "The storage type for this entry." 1030 ::= { mplsLdpEntityEntry 21 } 1032 mplsLdpEntityRowStatus OBJECT-TYPE 1033 SYNTAX RowStatus 1034 MAX-ACCESS read-create 1035 STATUS current 1036 DESCRIPTION 1037 "An object that allows entries in this table to 1038 be created and deleted using the 1039 RowStatus convention." 1040 ::= { mplsLdpEntityEntry 22 } 1042 -- 1043 -- The MPLS LDP Entity Statistics Table 1044 -- 1046 mplsLdpEntityStatsTable OBJECT-TYPE 1047 SYNTAX SEQUENCE OF MplsLdpEntityStatsEntry 1048 MAX-ACCESS not-accessible 1049 STATUS current 1050 DESCRIPTION 1051 "This table is a read-only table which augments 1052 the mplsLdpEntityTable. The purpose of this 1053 table is to keep statistical information about 1054 the LDP Entities on the LSR." 1055 ::= { mplsLdpEntityObjects 4 } 1057 mplsLdpEntityStatsEntry OBJECT-TYPE 1058 SYNTAX MplsLdpEntityStatsEntry 1059 MAX-ACCESS not-accessible 1060 STATUS current 1061 DESCRIPTION 1062 "A row in this table contains statistical information 1063 about an LDP Entity. Some counters contained in a 1064 row are for fatal errors received during a former 1065 LDP Session associated with this entry. For example, 1066 an Ldp Pdu received on a TCP connection during an 1067 LDP Session contains a fatal error. That 1068 error is counted here, because the 1069 session is terminated. 1071 If the error is NOT fatal (i.e. and the Session 1072 remains), then the error is counted in the 1073 mplsLdpSesStatsEntry." 1074 AUGMENTS { mplsLdpEntityEntry } 1075 ::= { mplsLdpEntityStatsTable 1 } 1077 MplsLdpEntityStatsEntry ::= SEQUENCE { 1078 mplsLdpAttemptedSessions Counter32, 1079 mplsLdpSesRejectedNoHelloErrors Counter32, 1080 mplsLdpSesRejectedAdErrors Counter32, 1081 mplsLdpSesRejectedMaxPduErrors Counter32, 1082 mplsLdpSesRejectedLRErrors Counter32, 1083 mplsLdpBadLdpIdentifierErrors Counter32, 1084 mplsLdpBadPduLengthErrors Counter32, 1085 mplsLdpBadMessageLengthErrors Counter32, 1086 mplsLdpBadTlvLengthErrors Counter32, 1087 mplsLdpMalformedTlvValueErrors Counter32, 1088 mplsLdpKeepAliveTimerExpErrors Counter32, 1089 mplsLdpShutdownNotifReceived Counter32, 1090 mplsLdpShutdownNotifSent Counter32 1091 } 1093 mplsLdpAttemptedSessions OBJECT-TYPE 1094 SYNTAX Counter32 1095 MAX-ACCESS read-only 1096 STATUS current 1097 DESCRIPTION 1098 "A count of the total attempted sessions for 1099 this LDP Entity. 1101 Discontinuities in the value of this counter can occur 1102 at re-initialization of the management system, and at 1103 other times as indicated by the value of 1104 mplsLdpEntityDiscontinuityTime." 1105 ::= { mplsLdpEntityStatsEntry 1 } 1107 mplsLdpSesRejectedNoHelloErrors OBJECT-TYPE 1108 SYNTAX Counter32 1109 MAX-ACCESS read-only 1110 STATUS current 1111 DESCRIPTION 1112 "A count of the Session Rejected/No Hello Error 1113 Notification Messages sent or received by 1114 this LDP Entity. 1116 Discontinuities in the value of this counter can occur 1117 at re-initialization of the management system, and at 1118 other times as indicated by the value of 1119 mplsLdpEntityDiscontinuityTime." 1120 ::= { mplsLdpEntityStatsEntry 2 } 1122 mplsLdpSesRejectedAdErrors OBJECT-TYPE 1123 SYNTAX Counter32 1124 MAX-ACCESS read-only 1125 STATUS current 1126 DESCRIPTION 1127 "A count of the Session Rejected/Parameters 1128 Advertisement Mode Error Notification Messages sent 1129 or received by this LDP Entity. 1131 Discontinuities in the value of this counter can occur 1132 at re-initialization of the management system, and at 1133 other times as indicated by the value of 1134 mplsLdpEntityDiscontinuityTime." 1135 ::= { mplsLdpEntityStatsEntry 3 } 1137 mplsLdpSesRejectedMaxPduErrors OBJECT-TYPE 1138 SYNTAX Counter32 1139 MAX-ACCESS read-only 1140 STATUS current 1141 DESCRIPTION 1142 "A count of the Session Rejected/Parameters 1143 Max Pdu Length Error Notification Messages sent 1144 or received by this LDP Entity. 1146 Discontinuities in the value of this counter can occur 1147 at re-initialization of the management system, and at 1148 other times as indicated by the value of 1149 mplsLdpEntityDiscontinuityTime." 1150 ::= { mplsLdpEntityStatsEntry 4 } 1152 mplsLdpSesRejectedLRErrors OBJECT-TYPE 1153 SYNTAX Counter32 1154 MAX-ACCESS read-only 1155 STATUS current 1156 DESCRIPTION 1157 "A count of the Session Rejected/Parameters 1158 Label Range Notification Messages sent 1159 or received by this LDP Entity. 1161 Discontinuities in the value of this counter can occur 1162 at re-initialization of the management system, and at 1163 other times as indicated by the value of 1164 mplsLdpEntityDiscontinuityTime." 1165 ::= { mplsLdpEntityStatsEntry 5 } 1167 mplsLdpBadLdpIdentifierErrors OBJECT-TYPE 1168 SYNTAX Counter32 1169 MAX-ACCESS read-only 1170 STATUS current 1171 DESCRIPTION 1172 "This object counts the number of Bad LDP Identifier 1173 Fatal Errors detected by the session(s) 1174 (past and present) associated with this LDP Entity. 1176 Discontinuities in the value of this counter can occur 1177 at re-initialization of the management system, and at 1178 other times as indicated by the value of 1179 mplsLdpEntityDiscontinuityTime." 1181 REFERENCE 1182 "[RFC3036], LDP Specification, Section 3.5.1.2." 1183 ::= { mplsLdpEntityStatsEntry 6 } 1185 mplsLdpBadPduLengthErrors OBJECT-TYPE 1186 SYNTAX Counter32 1187 MAX-ACCESS read-only 1188 STATUS current 1189 DESCRIPTION 1190 "This object counts the number of Bad Pdu Length 1191 Fatal Errors detected by the session(s) 1192 (past and present) associated with this LDP Entity. 1194 Discontinuities in the value of this counter can occur 1195 at re-initialization of the management system, and at 1196 other times as indicated by the value of 1197 mplsLdpEntityDiscontinuityTime." 1198 REFERENCE 1199 "[RFC3036], LDP Specification, Section 3.5.1.2." 1200 ::= { mplsLdpEntityStatsEntry 7 } 1202 mplsLdpBadMessageLengthErrors OBJECT-TYPE 1203 SYNTAX Counter32 1204 MAX-ACCESS read-only 1205 STATUS current 1206 DESCRIPTION 1207 "This object counts the number of Bad Message 1208 Length Fatal Errors detected by the session(s) 1209 (past and present) associated with this LDP Entity. 1211 Discontinuities in the value of this counter can occur 1212 at re-initialization of the management system, and at 1213 other times as indicated by the value of 1214 mplsLdpEntityDiscontinuityTime." 1215 REFERENCE 1216 "[RFC3036], LDP Specification, Section 3.5.1.2." 1217 ::= { mplsLdpEntityStatsEntry 8 } 1219 mplsLdpBadTlvLengthErrors OBJECT-TYPE 1220 SYNTAX Counter32 1221 MAX-ACCESS read-only 1222 STATUS current 1223 DESCRIPTION 1224 "This object counts the number of Bad TLV 1225 Length Fatal Errors detected by the session(s) 1226 (past and present) associated with this LDP Entity. 1228 Discontinuities in the value of this counter can occur 1229 at re-initialization of the management system, and at 1230 other times as indicated by the value of 1231 mplsLdpEntityDiscontinuityTime." 1232 REFERENCE 1233 "[RFC3036], LDP Specification, Section 3.5.1.2." 1234 ::= { mplsLdpEntityStatsEntry 9 } 1236 mplsLdpMalformedTlvValueErrors OBJECT-TYPE 1237 SYNTAX Counter32 1238 MAX-ACCESS read-only 1239 STATUS current 1240 DESCRIPTION 1241 "This object counts the number of Malformed TLV 1242 Value Fatal Errors detected by the session(s) 1243 (past and present) associated with this 1244 LDP Entity. 1246 Discontinuities in the value of this counter can occur 1247 at re-initialization of the management system, and at 1248 other times as indicated by the value of 1249 mplsLdpEntityDiscontinuityTime." 1250 REFERENCE 1251 "[RFC3036], LDP Specification, Section 3.5.1.2." 1252 ::= { mplsLdpEntityStatsEntry 10 } 1254 mplsLdpKeepAliveTimerExpErrors OBJECT-TYPE 1255 SYNTAX Counter32 1256 MAX-ACCESS read-only 1257 STATUS current 1258 DESCRIPTION 1259 "This object counts the number of Session Keep Alive 1260 Timer Expired Errors detected by the session(s) 1261 (past and present) associated with this LDP Entity. 1263 Discontinuities in the value of this counter can occur 1264 at re-initialization of the management system, and at 1265 other times as indicated by the value of 1266 mplsLdpEntityDiscontinuityTime." 1267 REFERENCE 1268 "[RFC3036], LDP Specification, Section 3.5.1.2." 1269 ::= { mplsLdpEntityStatsEntry 11 } 1271 mplsLdpShutdownNotifReceived OBJECT-TYPE 1272 SYNTAX Counter32 1273 MAX-ACCESS read-only 1274 STATUS current 1275 DESCRIPTION 1276 "This object counts the number of Shutdown Notfications 1277 received related to session(s) (past and present) 1278 associated with this LDP Entity. 1280 Discontinuities in the value of this counter can occur 1281 at re-initialization of the management system, and at 1282 other times as indicated by the value of 1283 mplsLdpEntityDiscontinuityTime." 1284 ::= { mplsLdpEntityStatsEntry 12 } 1286 mplsLdpShutdownNotifSent OBJECT-TYPE 1287 SYNTAX Counter32 1288 MAX-ACCESS read-only 1289 STATUS current 1290 DESCRIPTION 1291 "This object counts the number of Shutdown Notfications 1292 sent related to session(s) (past and present) associated 1293 with this LDP Entity. 1295 Discontinuities in the value of this counter can occur 1296 at re-initialization of the management system, and at 1297 other times as indicated by the value of 1298 mplsLdpEntityDiscontinuityTime." 1299 ::= { mplsLdpEntityStatsEntry 13 } 1301 -- 1302 -- The MPLS LDP Peer Table 1303 -- 1305 mplsLdpSessionObjects OBJECT IDENTIFIER ::= 1306 { mplsLdpObjects 3 } 1308 mplsLdpPeerLastChange OBJECT-TYPE 1309 SYNTAX TimeStamp 1310 MAX-ACCESS read-only 1311 STATUS current 1312 DESCRIPTION 1313 "The value of sysUpTime at the time of the most 1314 recent addition or deletion to the 1315 mplsLdpPeerTable/mplsLdpSessionTable." 1316 ::= { mplsLdpSessionObjects 1 } 1318 mplsLdpPeerTable OBJECT-TYPE 1319 SYNTAX SEQUENCE OF MplsLdpPeerEntry 1320 MAX-ACCESS not-accessible 1321 STATUS current 1322 DESCRIPTION 1323 "Information about LDP peers known by Entities in 1324 the mplsLdpEntityTable. The information in this table 1325 is based on information from the Entity-Peer interaction 1326 during session initialization but is not appropriate 1327 for the mplsLdpSessionTable, because objects in this 1328 table may or may not be used in session establishment." 1330 ::= { mplsLdpSessionObjects 2 } 1332 mplsLdpPeerEntry OBJECT-TYPE 1333 SYNTAX MplsLdpPeerEntry 1334 MAX-ACCESS not-accessible 1335 STATUS current 1336 DESCRIPTION 1337 "Information about a single Peer which is related 1338 to a Session. NOTE: this table is augmented by 1339 the mplsLdpSessionTable." 1340 INDEX { mplsLdpEntityLdpId, 1341 mplsLdpEntityIndex, 1342 mplsLdpPeerLdpId } 1343 ::= { mplsLdpPeerTable 1 } 1345 MplsLdpPeerEntry ::= SEQUENCE { 1346 mplsLdpPeerLdpId MplsLdpIdentifier, 1347 mplsLdpPeerLabelDistMethod MplsLabelDistributionMethod, 1348 mplsLdpPeerPathVectorLimit Integer32 1349 } 1351 mplsLdpPeerLdpId OBJECT-TYPE 1352 SYNTAX MplsLdpIdentifier 1353 MAX-ACCESS not-accessible 1354 STATUS current 1355 DESCRIPTION 1356 "The LDP identifier of this LDP Peer." 1357 ::= { mplsLdpPeerEntry 1 } 1359 mplsLdpPeerLabelDistMethod OBJECT-TYPE 1360 SYNTAX MplsLabelDistributionMethod 1361 MAX-ACCESS read-only 1362 STATUS current 1363 DESCRIPTION 1364 "For any given LDP session, the method of 1365 label distribution must be specified." 1366 ::= { mplsLdpPeerEntry 2 } 1368 mplsLdpPeerPathVectorLimit OBJECT-TYPE 1369 SYNTAX Integer32 (0..255) 1370 MAX-ACCESS read-only 1371 STATUS current 1372 DESCRIPTION 1373 "If the value of this object is 0 (zero) then 1374 Loop Dection for Path Vectors for this Peer 1375 is disabled. 1377 Otherwise, if this object has a value greater than 1378 zero, then Loop Dection for Path Vectors for this 1379 Peer is enabled and the Path Vector Limit is this value." 1381 REFERENCE 1382 "[RFC3036], LDP Specification, Section 2.8 Loop Dection, 1383 Section 3.4.5 Path Vector TLV." 1384 ::= { mplsLdpPeerEntry 3 } 1386 -- 1387 -- The MPLS LDP Sessions Table 1388 -- 1390 mplsLdpSessionTable OBJECT-TYPE 1391 SYNTAX SEQUENCE OF MplsLdpSessionEntry 1392 MAX-ACCESS not-accessible 1393 STATUS current 1394 DESCRIPTION 1395 "A table of Sessions between the LDP Entities and 1396 LDP Peers. Each row represents a single session." 1397 ::= { mplsLdpSessionObjects 3 } 1399 mplsLdpSessionEntry OBJECT-TYPE 1400 SYNTAX MplsLdpSessionEntry 1401 MAX-ACCESS not-accessible 1402 STATUS current 1403 DESCRIPTION 1404 "An entry in this table represents information on a 1405 single session between an LDP Entity and LDP Peer. 1406 The information contained in a row is read-only. 1408 Please note: the Path Vector Limit for the 1409 Session is the value which is configured in 1410 the corresponding mplsLdpEntityEntry. The 1411 Peer's Path Vector Limit is in noted in the 1412 mplsLdpPeerTable. 1414 Values which may differ from those configured are 1415 noted in the objects of this table, the 1416 mplsLdpAtmSesTable and the 1417 mplsLdpFrameRelaySesTable. A value will 1418 differ if it was negotiated between the 1419 Entity and the Peer. Values may or may not 1420 be negotiated. For example, if the values 1421 are the same then no negotiation takes place. 1422 If they are negotiated, then they may differ." 1423 AUGMENTS { mplsLdpPeerEntry } 1424 ::= { mplsLdpSessionTable 1 } 1426 MplsLdpSessionEntry ::= SEQUENCE { 1427 mplsLdpSesStateLastChange TimeStamp, 1428 mplsLdpSesState INTEGER, 1429 mplsLdpSesProtocolVersion Integer32, 1430 mplsLdpSesKeepAliveHoldTimeRem TimeInterval, 1431 mplsLdpSesMaxPduLength Unsigned32, 1432 mplsLdpSesDiscontinuityTime TimeStamp 1433 } 1435 mplsLdpSesStateLastChange OBJECT-TYPE 1436 SYNTAX TimeStamp 1437 MAX-ACCESS read-only 1438 STATUS current 1439 DESCRIPTION 1440 "The value of this object is sysUpTime when the 1441 most recent change in the mplsLdpSesState 1442 object occurred. When the entry is created, then 1443 this object has the value of sysUpTime when the 1444 entry was created." 1445 ::= { mplsLdpSessionEntry 1 } 1447 mplsLdpSesState OBJECT-TYPE 1448 SYNTAX INTEGER { 1449 nonexistent(1), 1450 initialized(2), 1451 openrec(3), 1452 opensent(4), 1453 operational(5) 1454 } 1455 MAX-ACCESS read-only 1456 STATUS current 1457 DESCRIPTION 1458 "The current state of the session, all of the 1459 states 1 to 5 are based on the state machine for 1460 session negotiation behavior." 1461 REFERENCE 1462 "[RFC3036], LDP Specification, Section 2.5.4, 1463 Initialization State Machine." 1464 ::= { mplsLdpSessionEntry 2 } 1466 mplsLdpSesProtocolVersion OBJECT-TYPE 1467 SYNTAX Integer32(1..65535) 1468 MAX-ACCESS read-only 1469 STATUS current 1470 DESCRIPTION 1471 "The version of the LDP Protocol which 1472 this session is using. This is the version of 1473 the LDP protocol which has been negotiated during 1474 session initialization." 1475 REFERENCE 1476 "[RFC3036], LDP Specification, Section 3.5.3, 1477 Initialization Message." 1478 ::= { mplsLdpSessionEntry 3 } 1480 mplsLdpSesKeepAliveHoldTimeRem OBJECT-TYPE 1481 SYNTAX TimeInterval 1482 MAX-ACCESS read-only 1483 STATUS current 1484 DESCRIPTION 1485 "The keep alive hold time remaining for this session." 1486 ::= { mplsLdpSessionEntry 4 } 1488 mplsLdpSesMaxPduLength OBJECT-TYPE 1489 SYNTAX Unsigned32 (1..65535) 1490 UNITS "octets" 1491 MAX-ACCESS read-only 1492 STATUS current 1493 DESCRIPTION 1494 "The value of maximum allowable length for LDP PDUs for 1495 this session. This value may have been negotiated during 1496 the Session Initialization. This object is related to 1497 the mplsLdpEntityMaxPduLength object. The 1498 mplsLdpEntityMaxPduLength object specifies the requested 1499 LDP PDU length, and this object reflects the negotiated 1500 LDP PDU length between the Entity and 1501 the Peer." 1502 ::= { mplsLdpSessionEntry 5 } 1504 mplsLdpSesDiscontinuityTime OBJECT-TYPE 1505 SYNTAX TimeStamp 1506 MAX-ACCESS read-only 1507 STATUS current 1508 DESCRIPTION 1509 "The value of sysUpTime on the most recent occasion at 1510 which any one or more of this session's counters 1511 suffered a discontinuity. The relevant counters are 1512 the specific instances associated with this session 1513 of any Counter32 or Counter64 object contained in the 1514 mplsLdpSessionStatsTable. 1516 The initial value of this object is the value of 1517 sysUpTime when the entry was created in this table. 1519 Also, a command generator can distinguish when a session 1520 between a given Entity and Peer goes away and then is 1521 're-established'. This value would change and 1522 thus indicate to the command generator that this is a 1523 different session." 1524 ::= { mplsLdpSessionEntry 6 } 1526 -- 1527 -- The MPLS LDP Session Statistics Table 1528 -- 1529 mplsLdpSesStatsTable OBJECT-TYPE 1530 SYNTAX SEQUENCE OF MplsLdpSesStatsEntry 1531 MAX-ACCESS not-accessible 1532 STATUS current 1533 DESCRIPTION 1534 "A table of statistics for Sessions between 1535 LDP Entities and LDP Peers." 1536 ::= { mplsLdpSessionObjects 4 } 1538 mplsLdpSesStatsEntry OBJECT-TYPE 1539 SYNTAX MplsLdpSesStatsEntry 1540 MAX-ACCESS not-accessible 1541 STATUS current 1542 DESCRIPTION 1543 "An entry in this table represents statistical 1544 information on a single session between an LDP 1545 Entity and LDP Peer." 1546 AUGMENTS { mplsLdpPeerEntry } 1547 ::= { mplsLdpSesStatsTable 1 } 1549 MplsLdpSesStatsEntry ::= SEQUENCE { 1550 mplsLdpSesStatsUnkMesTypeErrors Counter32, 1551 mplsLdpSesStatsUnkTlvErrors Counter32 1552 } 1554 mplsLdpSesStatsUnkMesTypeErrors OBJECT-TYPE 1555 SYNTAX Counter32 1556 MAX-ACCESS read-only 1557 STATUS current 1558 DESCRIPTION 1559 "This object counts the number of Unknown Message Type 1560 Errors detected during this session. 1562 Discontinuities in the value of this counter can occur 1563 at re-initialization of the management system, and at 1564 other times as indicated by the value of 1565 mplsLdpSesDiscontinuityTime." 1566 ::= { mplsLdpSesStatsEntry 1 } 1568 mplsLdpSesStatsUnkTlvErrors OBJECT-TYPE 1569 SYNTAX Counter32 1570 MAX-ACCESS read-only 1571 STATUS current 1572 DESCRIPTION 1573 "This object counts the number of Unknown TLV Errors 1574 detected during this session. 1576 Discontinuities in the value of this counter can occur 1577 at re-initialization of the management system, and at 1578 other times as indicated by the value of 1579 mplsLdpSessionDiscontinuityTime." 1580 ::= { mplsLdpSesStatsEntry 2 } 1582 -- 1583 -- The MPLS LDP Hello Adjacency Table 1584 -- 1586 mplsLdpHelloAdjacencyObjects OBJECT IDENTIFIER ::= 1587 { mplsLdpSessionObjects 5 } 1589 mplsLdpHelloAdjacencyTable OBJECT-TYPE 1590 SYNTAX SEQUENCE OF MplsLdpHelloAdjacencyEntry 1591 MAX-ACCESS not-accessible 1592 STATUS current 1593 DESCRIPTION 1594 "A table of Hello Adjacencies for Sessions." 1595 ::= { mplsLdpHelloAdjacencyObjects 1 } 1597 mplsLdpHelloAdjacencyEntry OBJECT-TYPE 1598 SYNTAX MplsLdpHelloAdjacencyEntry 1599 MAX-ACCESS not-accessible 1600 STATUS current 1601 DESCRIPTION 1602 "Each row represents a single LDP Hello Adjacency. 1603 An LDP Session can have one or more Hello adjacencies." 1604 INDEX { mplsLdpEntityLdpId, 1605 mplsLdpEntityIndex, 1606 mplsLdpPeerLdpId, 1607 mplsLdpHelloAdjIndex } 1608 ::= { mplsLdpHelloAdjacencyTable 1 } 1610 MplsLdpHelloAdjacencyEntry ::= SEQUENCE { 1611 mplsLdpHelloAdjIndex Unsigned32, 1612 mplsLdpHelloAdjHoldTimeRem TimeInterval, 1613 mplsLdpHelloAdjType INTEGER 1614 } 1616 mplsLdpHelloAdjIndex OBJECT-TYPE 1617 SYNTAX Unsigned32 (1..4294967295) 1618 MAX-ACCESS not-accessible 1619 STATUS current 1620 DESCRIPTION 1621 "An identifier for this specific adjacency." 1622 ::= { mplsLdpHelloAdjacencyEntry 1 } 1624 mplsLdpHelloAdjHoldTimeRem OBJECT-TYPE 1625 SYNTAX TimeInterval 1626 MAX-ACCESS read-only 1627 STATUS current 1628 DESCRIPTION 1629 "The time remaining for this Hello Adjacency. 1630 This interval will change when the 'next' 1631 Hello message which corresponds to this 1632 Hello Adjacency is received." 1633 ::= { mplsLdpHelloAdjacencyEntry 2 } 1635 mplsLdpHelloAdjType OBJECT-TYPE 1636 SYNTAX INTEGER { 1637 link(1), 1638 targeted(2) 1639 } 1640 MAX-ACCESS read-only 1641 STATUS current 1642 DESCRIPTION 1643 "This adjacency is the result of a 'link' 1644 hello if the value of this object is link(1). 1645 Otherwise, it is a result of a 'targeted' 1646 hello, targeted(2)." 1647 ::= { mplsLdpHelloAdjacencyEntry 3 } 1649 -- 1650 -- Session Label (LSP) Mapping to LSR MIB's LIB Information. 1651 -- 1653 mplsLdpLspTable OBJECT-TYPE 1654 SYNTAX SEQUENCE OF MplsLdpLspEntry 1655 MAX-ACCESS not-accessible 1656 STATUS current 1657 DESCRIPTION 1658 "A table of LDP LSP's which 1659 map to a Segment Table in the 1660 the LSR MIB's (either the mplsInSegmentTable 1661 or mplsOutSegmentTable) AND to the 1662 LSR MIB's mplsXCTable." 1663 ::= { mplsLdpSessionObjects 6 } 1665 mplsLdpLspEntry OBJECT-TYPE 1666 SYNTAX MplsLdpLspEntry 1667 MAX-ACCESS not-accessible 1668 STATUS current 1669 DESCRIPTION 1670 "An entry in this table represents information on a 1671 single LDP LSP which is represented by 1672 a session's index triple (mplsLdpEntityLdpId, 1673 mplsLdpEntityIndex, mplsLdpPeerLdpId) AND the 1674 index tuple (mplsLdpLspIfIndex, mplsLdpLspLabel). 1676 The information contained in a row is read-only." 1678 INDEX { mplsLdpEntityLdpId, 1679 mplsLdpEntityIndex, 1680 mplsLdpPeerLdpId, 1681 mplsLdpLspIfIndex, 1682 mplsLdpLspLabel 1683 } 1684 ::= { mplsLdpLspTable 1 } 1686 MplsLdpLspEntry ::= SEQUENCE { 1687 mplsLdpLspIfIndex InterfaceIndex, 1688 mplsLdpLspLabel MplsLabel, 1689 mplsLdpLspLabelType MplsLdpLabelType, 1690 mplsLdpLspType MplsLspType, 1691 mplsLdpLspLsrInSegmentPointer RowPointer, 1692 mplsLdpLspLsrOutSegmentPointer RowPointer, 1693 mplsLdpLspLsrXCPointer RowPointer 1694 } 1696 mplsLdpLspIfIndex OBJECT-TYPE 1697 SYNTAX InterfaceIndex 1698 MAX-ACCESS not-accessible 1699 STATUS current 1700 DESCRIPTION 1701 "The ifIndex value associated with this LSP." 1702 ::= { mplsLdpLspEntry 1 } 1704 mplsLdpLspLabel OBJECT-TYPE 1705 SYNTAX MplsLabel 1706 MAX-ACCESS not-accessible 1707 STATUS current 1708 DESCRIPTION 1709 "The LDP label for this LSP." 1710 ::= { mplsLdpLspEntry 2 } 1712 mplsLdpLspLabelType OBJECT-TYPE 1713 SYNTAX MplsLdpLabelType 1714 MAX-ACCESS read-only 1715 STATUS current 1716 DESCRIPTION 1717 "The Layer 2 Label Type." 1718 ::= { mplsLdpLspEntry 3 } 1720 mplsLdpLspType OBJECT-TYPE 1721 SYNTAX MplsLspType 1722 MAX-ACCESS read-only 1723 STATUS current 1724 DESCRIPTION 1725 "The type of LSP connection. 1726 The possible values are: 1728 unknown(1) -- if the LSP is not known 1729 to be one of the following. 1731 terminatingLsp(2) -- if the LSP terminates 1732 on the LSR, then this 1733 is an ingressing LSP 1734 which ends on the LSR, 1736 originatingLsp(3) -- if the LSP originates 1737 from the LSR, then this 1738 is an egressing LSP which is 1739 the head-end of the LSP, 1741 crossConnectingLsp(4) -- if the LSP ingresses 1742 and egresses on the LSR, 1743 then it is cross-connecting 1744 on that LSR." 1745 ::= { mplsLdpLspEntry 4 } 1747 mplsLdpLspLsrInSegmentPointer OBJECT-TYPE 1748 SYNTAX RowPointer 1749 MAX-ACCESS read-only 1750 STATUS current 1751 DESCRIPTION 1752 "If this LSP terminates or is cross-connecting 1753 on this LSR, then this RowPointer should point 1754 to an instance of an object in the 1755 mplsLsrInSegmentTable. In other words if 1756 the value of mplsLdpLspType is 1757 terminatingLsp(2) or crossConnectingLsp(4), 1758 then this should point to an instance of an object 1759 in the LSR-MIB's mplsInSegmentTable. 1761 Otherwise, a value of zeroDotzero indicates that 1762 this LSP has no corresponding mplsInSegmentEntry." 1763 ::= { mplsLdpLspEntry 5 } 1765 mplsLdpLspLsrOutSegmentPointer OBJECT-TYPE 1766 SYNTAX RowPointer 1767 MAX-ACCESS read-only 1768 STATUS current 1769 DESCRIPTION 1770 "If this LSP originates or is cross-connecting 1771 on this LSR, then this RowPointer should point 1772 to an instance of an object in the LSR-MIB's 1773 mplsOutSegmentTable. In other words if 1774 the value of mplsLdpLspType is 1775 originatingLsp(3) or crossConnectingLsp(4), 1776 then this should point to an instance of an object 1777 in the LSR-MIB's mplsOutSegmentTable. 1779 Otherwise, a value of zeroDotzero indicates that 1780 this LSP has no corresponding mplsOutSegmentEntry." 1781 ::= { mplsLdpLspEntry 6 } 1783 mplsLdpLspLsrXCPointer OBJECT-TYPE 1784 SYNTAX RowPointer 1785 MAX-ACCESS read-only 1786 STATUS current 1787 DESCRIPTION 1788 "If this LSP is cross-connecting on this LSR, 1789 then this RowPointer should point 1790 to an instance of an object in the 1791 LSR-MIB's mplsXCTable. In other words if 1792 the value of mplsLdpLspType is crossConnectingLsp(4), 1793 then this should point to an instance of an object 1794 in the LSR-MIB's mplsXCTable. 1796 Otherwise, a value of zeroDotzero indicates that 1797 this LSP has no corresponding mplsXCEntry." 1798 ::= { mplsLdpLspEntry 7 } 1800 -- 1801 -- Mpls FEC Table 1802 -- 1804 mplsFecObjects OBJECT IDENTIFIER ::= 1805 { mplsLdpSessionObjects 7 } 1807 mplsFecIndexNext OBJECT-TYPE 1808 SYNTAX Unsigned32 (0..4294967295) 1809 MAX-ACCESS read-only 1810 STATUS current 1811 DESCRIPTION 1812 "This object contains an appropriate value to 1813 be used for mplsFecIndex when creating 1814 entries in the mplsFecTable. The value 1815 0 indicates that no unassigned entries are 1816 available. To obtain the mplsFecIndex 1817 value for a new entry, the manager issues a 1818 management protocol retrieval operation to obtain 1819 the current value of this object. After each 1820 retrieval, the agent should modify the value to 1821 the next unassigned index." 1822 ::= { mplsFecObjects 1 } 1824 mplsFecTable OBJECT-TYPE 1825 SYNTAX SEQUENCE OF MplsFecEntry 1826 MAX-ACCESS not-accessible 1827 STATUS current 1828 DESCRIPTION 1829 "This table represents the FEC 1830 (Forwarding Equivalence Class) 1831 Information associated with an LSP." 1832 ::= { mplsFecObjects 2 } 1834 mplsFecEntry OBJECT-TYPE 1835 SYNTAX MplsFecEntry 1836 MAX-ACCESS not-accessible 1837 STATUS current 1838 DESCRIPTION 1839 "Each row represents a single FEC Element." 1840 INDEX { mplsFecIndex } 1841 ::= { mplsFecTable 1 } 1843 MplsFecEntry ::= SEQUENCE { 1844 mplsFecIndex Unsigned32, 1845 mplsFecType INTEGER, 1846 mplsFecAddrLength Integer32, 1847 mplsFecAddrFamily InetAddressType, 1848 mplsFecAddr InetAddress, 1849 mplsFecStorageType StorageType, 1850 mplsFecRowStatus RowStatus 1851 } 1853 mplsFecIndex OBJECT-TYPE 1854 SYNTAX Unsigned32(1..4294967295) 1855 MAX-ACCESS not-accessible 1856 STATUS current 1857 DESCRIPTION 1858 "The index which uniquely identifies this entry." 1859 ::= { mplsFecEntry 1 } 1861 mplsFecType OBJECT-TYPE 1862 SYNTAX INTEGER { 1863 prefix(1), 1864 hostAddress(2) 1865 } 1866 MAX-ACCESS read-create 1867 STATUS current 1868 DESCRIPTION 1869 "The type of the FEC. If the value of this object 1870 is 'prefix(1)' then the FEC type described by this 1871 row is for address prefixes. 1873 If the value of this object is 'hostAddress(2)' then 1874 the FEC type described by this row is a host address." 1875 ::= { mplsFecEntry 2 } 1877 mplsFecAddrLength OBJECT-TYPE 1878 SYNTAX Integer32(0..255) 1879 MAX-ACCESS read-create 1880 STATUS current 1881 DESCRIPTION 1882 "If the value of 'mplsFecType' is 'prefix(1)' 1883 then the value of this object is the length in 1884 bits of the address prefix represented by 1885 'mplsFecAddr', or if the length is zero then 1886 this is a special value which indicates that the 1887 prefix matches all addresses. In this case the 1888 prefix is also zero (i.e. 'mplsFecAddr' will 1889 have the value of zero.)" 1890 DEFVAL { 0 } 1891 ::= { mplsFecEntry 3 } 1893 mplsFecAddrFamily OBJECT-TYPE 1894 SYNTAX InetAddressType 1895 MAX-ACCESS read-create 1896 STATUS current 1897 DESCRIPTION 1898 "The value of this object is from the Address Family 1899 Numbers." 1900 ::= { mplsFecEntry 4 } 1902 mplsFecAddr OBJECT-TYPE 1903 SYNTAX InetAddress 1904 MAX-ACCESS read-create 1905 STATUS current 1906 DESCRIPTION 1907 "If the value of 'mplsFecType' is 'prefix(1)' 1908 then the value of this object is the address prefix. 1909 If the value of the 'mplsFecAddrLength' 1910 is object is zero, then this object should also be 1911 zero. 1913 If the value of the 'mplsFecType' is 'hostAddress(2)' 1914 then this is the host address." 1915 ::= { mplsFecEntry 5 } 1917 mplsFecStorageType OBJECT-TYPE 1918 SYNTAX StorageType 1919 MAX-ACCESS read-create 1920 STATUS current 1921 DESCRIPTION 1922 "The storage type for this entry." 1923 ::= { mplsFecEntry 6 } 1925 mplsFecRowStatus OBJECT-TYPE 1926 SYNTAX RowStatus 1927 MAX-ACCESS read-create 1928 STATUS current 1929 DESCRIPTION 1930 "An object that allows entries in this table to 1931 be created and deleted using the 1932 RowStatus convention." 1933 ::= { mplsFecEntry 7 } 1935 -- 1936 -- LDP LSP FEC Table 1937 -- 1939 mplsLdpLspFecTable OBJECT-TYPE 1940 SYNTAX SEQUENCE OF MplsLdpLspFecEntry 1941 MAX-ACCESS not-accessible 1942 STATUS current 1943 DESCRIPTION 1944 "A table which shows the relationship between 1945 LDP LSP's and FECs. Each row represents 1946 a single LSP to FEC association. 1947 This table is read-only." 1948 ::= { mplsLdpSessionObjects 8 } 1950 mplsLdpLspFecEntry OBJECT-TYPE 1951 SYNTAX MplsLdpLspFecEntry 1952 MAX-ACCESS not-accessible 1953 STATUS current 1954 DESCRIPTION 1955 "An entry represents a LDP LSP 1956 to FEC association." 1957 INDEX { mplsLdpEntityLdpId, 1958 mplsLdpEntityIndex, 1959 mplsLdpPeerLdpId, 1960 mplsLdpLspIfIndex, 1961 mplsLdpLspLabel, 1962 mplsFecIndex 1963 } 1964 ::= { mplsLdpLspFecTable 1 } 1966 MplsLdpLspFecEntry ::= SEQUENCE { 1967 mplsLdpLspFecOperStatus INTEGER, 1968 mplsLdpLspFecLastChange TimeStamp, 1969 mplsLdpLspFecRowStatus RowStatus 1970 } 1972 mplsLdpLspFecOperStatus OBJECT-TYPE 1973 SYNTAX INTEGER { 1974 unknown(1), 1975 inUse(2), 1976 notInUse(3) 1977 } 1978 MAX-ACCESS read-only 1979 STATUS current 1980 DESCRIPTION 1981 "An indication of the operational status of 1982 the FEC associated with LDP LSP. 1984 unknown(1) - this is a temporary state which 1985 may indicate the LSP-FEC association 1986 is in a state of transition. 1988 inUse(2) - the FEC associated with the LSP is 1989 currently being applied. 1991 notInUse(3) - the FEC associated with the LSP is 1992 not being applied. Eventually, this 1993 entry may be aged out." 1994 ::= { mplsLdpLspFecEntry 1 } 1996 mplsLdpLspFecLastChange OBJECT-TYPE 1997 SYNTAX TimeStamp 1998 MAX-ACCESS read-only 1999 STATUS current 2000 DESCRIPTION 2001 "This value of sysUpTime when the 2002 mplsLdpLspFecOperStatus last changed state." 2003 ::= { mplsLdpLspFecEntry 2 } 2005 mplsLdpLspFecRowStatus OBJECT-TYPE 2006 SYNTAX RowStatus 2007 MAX-ACCESS read-create 2008 STATUS current 2009 DESCRIPTION 2010 "An object that allows entries in this table to 2011 be created and deleted using the 2012 RowStatus convention." 2013 ::= { mplsLdpLspFecEntry 3 } 2015 -- 2016 -- Address Message/Address Withdraw Message Information 2017 -- 2018 -- This information is associated with a specific Session 2019 -- because Label Address Messages are sent after session 2020 -- initialization has taken place. 2021 -- 2023 mplsLdpSesPeerAddrTable OBJECT-TYPE 2024 SYNTAX SEQUENCE OF MplsLdpSesPeerAddrEntry 2025 MAX-ACCESS not-accessible 2026 STATUS current 2027 DESCRIPTION 2028 "This table 'extends' the mplsLdpSessionTable. 2029 This table is used to store Label Address Information 2030 from Label Address Messages received by this LSR from 2031 Peers. This table is read-only and should be updated 2032 when Label Withdraw Address Messages are received, i.e. 2033 Rows should be deleted as apropriate. 2035 NOTE: since more than one address may be contained 2036 in a Label Address Message, this table 'extends', 2037 rather than 'AUGMENTS' the mplsLdpSessionTable's 2038 information." 2039 ::= { mplsLdpSessionObjects 9 } 2041 mplsLdpSesPeerAddrEntry OBJECT-TYPE 2042 SYNTAX MplsLdpSesPeerAddrEntry 2043 MAX-ACCESS not-accessible 2044 STATUS current 2045 DESCRIPTION 2046 "An entry in this table represents information on 2047 session's for a single next hop address which was 2048 advertised in an Address Message from the LDP peer. 2049 The information contained in a row is read-only." 2050 INDEX { mplsLdpEntityLdpId, 2051 mplsLdpEntityIndex, 2052 mplsLdpPeerLdpId, 2053 mplsLdpSesPeerAddrIndex 2054 } 2055 ::= { mplsLdpSesPeerAddrTable 1 } 2057 MplsLdpSesPeerAddrEntry ::= SEQUENCE { 2058 mplsLdpSesPeerAddrIndex Unsigned32, 2059 mplsLdpSesPeerNextHopAddrType InetAddressType, 2060 mplsLdpSesPeerNextHopAddr InetAddress 2061 } 2063 mplsLdpSesPeerAddrIndex OBJECT-TYPE 2064 SYNTAX Unsigned32 (1..4294967295) 2065 MAX-ACCESS not-accessible 2066 STATUS current 2067 DESCRIPTION 2068 "An index which uniquely identifies this entry within 2069 a given session." 2070 ::= { mplsLdpSesPeerAddrEntry 1 } 2072 mplsLdpSesPeerNextHopAddrType OBJECT-TYPE 2073 SYNTAX InetAddressType 2074 MAX-ACCESS read-only 2075 STATUS current 2076 DESCRIPTION 2077 "The internetwork layer address type of this Next Hop 2078 Address as specified in the Label Address Message 2079 associated with this Session. The value of this 2080 object indicates how to interpret the value of 2081 mplsLdpSessionPeerNextHopAddress." 2082 ::= { mplsLdpSesPeerAddrEntry 2 } 2084 mplsLdpSesPeerNextHopAddr OBJECT-TYPE 2085 SYNTAX InetAddress 2086 MAX-ACCESS read-only 2087 STATUS current 2088 DESCRIPTION 2089 "The value of the next hop address." 2090 REFERENCE 2091 "[RFC3036], LDP Specification defines only IPv4 for 2092 LDP Protocol Version 1, see section 3.4.3." 2093 ::= { mplsLdpSesPeerAddrEntry 3 } 2095 --- 2096 --- Notifications 2097 --- 2099 mplsLdpNotificationPrefix OBJECT IDENTIFIER ::= 2100 { mplsLdpNotifications 0 } 2102 mplsLdpInitSesThresholdExceeded NOTIFICATION-TYPE 2103 OBJECTS { 2104 mplsLdpEntityInitSesThreshold 2105 } 2106 STATUS current 2107 DESCRIPTION 2108 "This notification is generated when the value of 2109 the 'mplsLdpEntityInitSesThreshold' object 2110 is not zero, and the number of Session 2111 Initialization messages exceeds the value 2112 of the 'mplsLdpEntityInitSesThreshold' object." 2113 ::= { mplsLdpNotificationPrefix 1 } 2115 mplsLdpPathVectorLimitMismatch NOTIFICATION-TYPE 2116 OBJECTS { 2117 mplsLdpEntityPathVectorLimit, 2118 mplsLdpPeerPathVectorLimit 2119 } 2120 STATUS current 2121 DESCRIPTION 2122 "If this notification is enabled to generated, 2123 then this notification is sent when the 2124 'mplsLdpEntityPathVectorLimit' does NOT match 2125 the value of the 'mplsLdpPeerPathVectorLimit' for 2126 a specific Entity." 2127 REFERENCE 2128 "[RFC3036], LDP Specification, Section 3.5.3." 2129 ::= { mplsLdpNotificationPrefix 2 } 2131 mplsLdpSessionUp NOTIFICATION-TYPE 2132 OBJECTS { 2133 mplsLdpSesState, 2134 mplsLdpSesDiscontinuityTime, 2135 mplsLdpSesStatsUnkMesTypeErrors, 2136 mplsLdpSesStatsUnkTlvErrors 2137 } 2138 STATUS current 2139 DESCRIPTION 2140 "If this notification is enabled to generated, 2141 then this notification is sent when the 2142 value of 'mplsLdpSesState' enters 2143 the 'operational(5)' state." 2144 ::= { mplsLdpNotificationPrefix 3 } 2146 mplsLdpSessionDown NOTIFICATION-TYPE 2147 OBJECTS { 2148 mplsLdpSesState, 2149 mplsLdpSesDiscontinuityTime, 2150 mplsLdpSesStatsUnkMesTypeErrors, 2151 mplsLdpSesStatsUnkTlvErrors 2153 } 2154 STATUS current 2155 DESCRIPTION 2156 "If this notification is enabled to generated, 2157 then this notification is sent when the 2158 the value of 'mplsLdpSesState' leaves 2159 the 'operational(5)' state." 2160 ::= { mplsLdpNotificationPrefix 4 } 2162 --**************************************************************** 2163 -- Module Conformance Statement 2164 --**************************************************************** 2166 mplsLdpGroups 2167 OBJECT IDENTIFIER ::= { mplsLdpConformance 1 } 2169 mplsLdpCompliances 2170 OBJECT IDENTIFIER ::= { mplsLdpConformance 2 } 2172 -- 2173 -- Full Compliance 2174 -- 2176 mplsLdpModuleFullCompliance MODULE-COMPLIANCE 2177 STATUS current 2178 DESCRIPTION 2179 "The Module is implemented with support 2180 for read-create and read-write. In other 2181 words, both monitoring and configuration 2182 are available when using this MODULE-COMPLIANCE." 2184 MODULE -- this module 2185 MANDATORY-GROUPS { mplsLdpGeneralGroup, 2186 mplsLdpLspGroup, 2187 mplsLdpNotificationsGroup 2188 } 2190 GROUP mplsLdpLsrGroup 2191 DESCRIPTION 2192 "This group must be supported if the LSR MIB is 2193 implemented, specifically the mplsInSegmentTable, 2194 the mplsOutSegmentTable or the mplsXCTable." 2196 OBJECT mplsLdpEntityTargetPeerAddrType 2197 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2198 DESCRIPTION 2199 "An implementation is only required to support 2200 'unknown(0)', and IPv4 addresses. Supporting 2201 IPv6 addresses is optional." 2203 OBJECT mplsLdpEntityTargetPeerAddr 2204 SYNTAX InetAddress (SIZE(0|4|16)) 2205 DESCRIPTION 2206 "An implementation is only required to support IPv4 and 2207 may optionally support IPv6 addresses." 2209 OBJECT mplsLdpEntityRowStatus 2210 SYNTAX RowStatus { active(1) } 2211 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 2212 DESCRIPTION 2213 "Support for createAndWait and notInService is not 2214 required." 2216 OBJECT mplsFecAddrFamily 2217 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2218 DESCRIPTION 2219 "An implementation is only required to support 2220 'unknown(0)', and IPv4 addresses. Supporting 2221 IPv6 addresses is optional." 2223 OBJECT mplsFecAddr 2224 SYNTAX InetAddress (SIZE(0|4|16)) 2225 DESCRIPTION 2226 "An implementation is only required to support IPv4 and 2227 may optionally support IPv6 addresses." 2229 OBJECT mplsFecRowStatus 2230 SYNTAX RowStatus { active(1) } 2231 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 2232 MIN-ACCESS read-only 2233 DESCRIPTION 2234 "Support for createAndWait and notInService is not 2235 required. Also, the entries in this table may be 2236 created by the agent, so strictly speaking 2237 read-create functionality is not necessary, but 2238 may be nice to have." 2240 OBJECT mplsLdpLspFecRowStatus 2241 SYNTAX RowStatus { active(1) } 2242 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 2243 MIN-ACCESS read-only 2244 DESCRIPTION 2245 "Support for createAndWait and notInService is not 2246 required. Also, the entries in this table may be 2247 created by the agent, so strictly speaking 2248 read-create functionality is not necessary, but 2249 may be nice to have." 2251 OBJECT mplsLdpSesPeerNextHopAddrType 2252 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2253 DESCRIPTION 2254 "An implementation is only required to support 2255 'unknown(0)', and IPv4 addresses. Supporting 2256 IPv6 addresses is optional." 2258 OBJECT mplsLdpSesPeerNextHopAddr 2259 SYNTAX InetAddress (SIZE(0|4|16)) 2260 DESCRIPTION 2261 "An implementation is only required to support IPv4 2262 and may optionally support IPv6 addresses." 2264 ::= { mplsLdpCompliances 1 } 2266 -- 2267 -- Read-Only Compliance 2268 -- 2269 mplsLdpModuleReadOnlyCompliance MODULE-COMPLIANCE 2270 STATUS current 2271 DESCRIPTION 2272 "The Module is implemented with support 2273 for read-only. In other words, only monitoring 2274 is available by implementing this MODULE-COMPLIANCE." 2276 MODULE -- this module 2277 MANDATORY-GROUPS { mplsLdpGeneralGroup, 2278 mplsLdpLspGroup, 2279 mplsLdpNotificationsGroup 2280 } 2282 GROUP mplsLdpLsrGroup 2283 DESCRIPTION 2284 "This group must be supported if the LSR MIB is 2285 implemented, specifically the mplsInSegmentTable, 2286 the mplsOutSegmentTable or the mplsXCTable." 2288 OBJECT mplsLdpEntityProtocolVersion 2289 MIN-ACCESS read-only 2290 DESCRIPTION 2291 "Write access is not required." 2293 OBJECT mplsLdpEntityAdminStatus 2294 MIN-ACCESS read-only 2295 DESCRIPTION 2296 "Write access is not required." 2298 OBJECT mplsLdpEntityTcpDscPort 2299 MIN-ACCESS read-only 2300 DESCRIPTION 2301 "Write access is not required." 2303 OBJECT mplsLdpEntityUdpDscPort 2304 MIN-ACCESS read-only 2305 DESCRIPTION 2306 "Write access is not required." 2308 OBJECT mplsLdpEntityMaxPduLength 2309 MIN-ACCESS read-only 2310 DESCRIPTION 2311 "Write access is not required." 2313 OBJECT mplsLdpEntityKeepAliveHoldTimer 2314 MIN-ACCESS read-only 2315 DESCRIPTION 2316 "Write access is not required." 2318 OBJECT mplsLdpEntityHelloHoldTimer 2319 MIN-ACCESS read-only 2320 DESCRIPTION 2321 "Write access is not required." 2323 OBJECT mplsLdpEntityInitSesThreshold 2324 MIN-ACCESS read-only 2325 DESCRIPTION 2326 "Write access is not required." 2328 OBJECT mplsLdpEntityLabelDistMethod 2329 MIN-ACCESS read-only 2330 DESCRIPTION 2331 "Write access is not required." 2333 OBJECT mplsLdpEntityLabelRetentionMode 2334 MIN-ACCESS read-only 2335 DESCRIPTION 2336 "Write access is not required." 2338 OBJECT mplsLdpEntityPathVectorLimit 2339 MIN-ACCESS read-only 2340 DESCRIPTION 2341 "Write access is not required." 2343 OBJECT mplsLdpEntityHopCountLimit 2344 MIN-ACCESS read-only 2345 DESCRIPTION 2346 "Write access is not required." 2348 OBJECT mplsLdpEntityTargetPeer 2349 MIN-ACCESS read-only 2350 DESCRIPTION 2351 "Write access is not required." 2353 OBJECT mplsLdpEntityTargetPeerAddrType 2354 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2355 MIN-ACCESS read-only 2356 DESCRIPTION 2357 "Write access is not required. 2358 An implementation is only required to support 2359 'unknown(0)', and IPv4 addresses. Supporting 2360 IPv6 addresses is optional." 2362 OBJECT mplsLdpEntityTargetPeerAddr 2363 SYNTAX InetAddress (SIZE(0|4|16)) 2364 MIN-ACCESS read-only 2365 DESCRIPTION 2366 "Write access is not required. 2367 An implementation is only required to support IPv4 and 2368 may optionally support IPv6 addresses." 2370 OBJECT mplsLdpEntityLabelType 2371 MIN-ACCESS read-only 2372 DESCRIPTION 2373 "Write access is not required." 2375 OBJECT mplsLdpEntityStorageType 2376 MIN-ACCESS read-only 2377 DESCRIPTION 2378 "Write access is not required." 2380 OBJECT mplsLdpEntityRowStatus 2381 SYNTAX RowStatus { active(1) } 2382 MIN-ACCESS read-only 2383 DESCRIPTION 2384 "Write access is not required, and active is the 2385 only status that needs to be supported." 2387 OBJECT mplsFecType 2388 MIN-ACCESS read-only 2389 DESCRIPTION 2390 "Write access is not required." 2392 OBJECT mplsFecAddrLength 2393 MIN-ACCESS read-only 2394 DESCRIPTION 2395 "Write access is not required." 2397 OBJECT mplsFecAddrFamily 2398 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2399 MIN-ACCESS read-only 2400 DESCRIPTION 2401 "Write access is not required. 2402 An implementation is only required to support 2403 'unknown(0)', and IPv4 addresses. Supporting 2404 IPv6 addresses is optional." 2406 OBJECT mplsFecAddr 2407 SYNTAX InetAddress (SIZE(0|4|16)) 2408 MIN-ACCESS read-only 2409 DESCRIPTION 2410 "Write access is not required. 2411 An implementation is only required to support IPv4 and 2412 may optionally support IPv6 addresses." 2414 OBJECT mplsFecStorageType 2415 MIN-ACCESS read-only 2416 DESCRIPTION 2417 "Write access is not required." 2419 OBJECT mplsFecRowStatus 2420 SYNTAX RowStatus { active(1) } 2421 MIN-ACCESS read-only 2422 DESCRIPTION 2423 "Write access is not required, and active is the 2424 only status that needs to be supported." 2426 OBJECT mplsLdpLspFecRowStatus 2427 SYNTAX RowStatus { active(1) } 2428 MIN-ACCESS read-only 2429 DESCRIPTION 2430 "Write access is not required, and active is the 2431 only status that needs to be supported." 2433 OBJECT mplsLdpSesPeerNextHopAddrType 2434 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2435 DESCRIPTION 2436 "An implementation is only required to support 2437 'unknown(0)', and IPv4 addresses. Supporting 2438 IPv6 addresses is optional." 2440 OBJECT mplsLdpSesPeerNextHopAddr 2441 SYNTAX InetAddress (SIZE(0|4|16)) 2442 DESCRIPTION 2443 "An implementation is only required to support IPv4 2444 and may optionally support IPv6 addresses." 2446 ::= { mplsLdpCompliances 2 } 2448 -- units of conformance 2450 mplsLdpGeneralGroup OBJECT-GROUP 2451 OBJECTS { 2452 mplsLdpLsrId, 2453 mplsLdpLsrLoopDetectionCapable, 2454 mplsLdpEntityLastChange, 2455 mplsLdpEntityIndexNext, 2456 mplsLdpEntityProtocolVersion, 2457 mplsLdpEntityAdminStatus, 2458 mplsLdpEntityOperStatus, 2459 mplsLdpEntityTcpDscPort, 2460 mplsLdpEntityUdpDscPort, 2461 mplsLdpEntityMaxPduLength, 2462 mplsLdpEntityKeepAliveHoldTimer, 2463 mplsLdpEntityHelloHoldTimer, 2464 mplsLdpEntityInitSesThreshold, 2465 mplsLdpEntityLabelDistMethod, 2466 mplsLdpEntityLabelRetentionMode, 2467 mplsLdpEntityPathVectorLimit, 2468 mplsLdpEntityHopCountLimit, 2469 mplsLdpEntityTargetPeer, 2470 mplsLdpEntityTargetPeerAddrType, 2471 mplsLdpEntityTargetPeerAddr, 2472 mplsLdpEntityLabelType, 2473 mplsLdpEntityDiscontinuityTime, 2474 mplsLdpEntityStorageType, 2475 mplsLdpEntityRowStatus, 2476 mplsLdpAttemptedSessions, 2477 mplsLdpSesRejectedNoHelloErrors, 2478 mplsLdpSesRejectedAdErrors, 2479 mplsLdpSesRejectedMaxPduErrors, 2480 mplsLdpSesRejectedLRErrors, 2481 mplsLdpBadLdpIdentifierErrors, 2482 mplsLdpBadPduLengthErrors, 2483 mplsLdpBadMessageLengthErrors, 2484 mplsLdpBadTlvLengthErrors, 2485 mplsLdpMalformedTlvValueErrors, 2486 mplsLdpKeepAliveTimerExpErrors, 2487 mplsLdpShutdownNotifReceived, 2488 mplsLdpShutdownNotifSent, 2489 mplsLdpPeerLastChange, 2490 mplsLdpPeerLabelDistMethod, 2491 mplsLdpPeerPathVectorLimit, 2492 mplsLdpHelloAdjHoldTimeRem, 2493 mplsLdpHelloAdjType, 2494 mplsLdpSesStateLastChange, 2495 mplsLdpSesState, 2496 mplsLdpSesProtocolVersion, 2497 mplsLdpSesKeepAliveHoldTimeRem, 2498 mplsLdpSesMaxPduLength, 2499 mplsLdpSesDiscontinuityTime, 2500 mplsLdpSesStatsUnkMesTypeErrors, 2501 mplsLdpSesStatsUnkTlvErrors, 2502 mplsLdpSesPeerNextHopAddrType, 2503 mplsLdpSesPeerNextHopAddr, 2504 mplsFecIndexNext, 2505 mplsFecType, 2506 mplsFecAddrFamily, 2507 mplsFecAddrLength, 2508 mplsFecAddr, 2509 mplsFecStorageType, 2510 mplsFecRowStatus, 2511 mplsLdpLspFecOperStatus, 2512 mplsLdpLspFecLastChange, 2513 mplsLdpLspFecRowStatus 2514 } 2515 STATUS current 2516 DESCRIPTION 2517 "Objects that apply to all MPLS LDP implementations." 2518 ::= { mplsLdpGroups 1 } 2520 mplsLdpLspGroup OBJECT-GROUP 2521 OBJECTS { 2522 mplsLdpLspLabelType, 2523 mplsLdpLspType 2524 } 2525 STATUS current 2526 DESCRIPTION 2527 "These objects are specific to LDP LSPs." 2528 ::= { mplsLdpGroups 2 } 2530 mplsLdpLsrGroup OBJECT-GROUP 2531 OBJECTS { 2532 mplsLdpLspLsrInSegmentPointer, 2533 mplsLdpLspLsrOutSegmentPointer, 2534 mplsLdpLspLsrXCPointer 2535 } 2536 STATUS current 2537 DESCRIPTION 2538 "These objects are optional and only need to be supported 2539 for LDP implementations which support the following 2540 tables in the LSR MIB: mplsInSegmentTable, 2541 mplsOutSegmentTable and mplsXCTable." 2542 ::= { mplsLdpGroups 3 } 2544 mplsLdpNotificationsGroup NOTIFICATION-GROUP 2545 NOTIFICATIONS { mplsLdpInitSesThresholdExceeded, 2546 mplsLdpPathVectorLimitMismatch, 2547 mplsLdpSessionUp, 2548 mplsLdpSessionDown 2549 } 2550 STATUS current 2551 DESCRIPTION 2552 "The notification(s) which an MPLS LDP implemention 2553 is required to implement." 2554 ::= { mplsLdpGroups 4 } 2556 END 2558 4.1. The MPLS-LDP-GENERIC-MIB Module 2560 This MIB Module MUST be supported if LDP uses a Per Platform Label 2561 Space. This MIB Module contains a Label Range (LR) table for 2562 configuring Mpls Generic Label Ranges. This table is 2563 mplsLdpEntityGenericLabelRangeTable. Although the LDP Specification 2564 does not provide a way for configuring Label Ranges for Generic 2565 Labels, the MIB does provide a way to reserve a range of generic 2566 labels because this was thought to be useful by the working group. 2568 MPLS-LDP-GENERIC-MIB DEFINITIONS ::= BEGIN 2570 IMPORTS 2572 OBJECT-TYPE, 2573 MODULE-IDENTITY, 2574 Unsigned32 2575 FROM SNMPv2-SMI 2577 MODULE-COMPLIANCE, 2578 OBJECT-GROUP 2579 FROM SNMPv2-CONF 2581 RowStatus, 2582 StorageType 2583 FROM SNMPv2-TC 2585 InterfaceIndexOrZero 2586 FROM IF-MIB 2588 mplsMIB 2589 FROM MPLS-TC-MIB 2591 mplsLdpEntityObjects, 2592 mplsLdpEntityLdpId, 2593 mplsLdpEntityIndex 2594 FROM MPLS-LDP-MIB 2595 ; 2597 mplsLdpGenericMIB MODULE-IDENTITY 2598 LAST-UPDATED "200208081200Z" -- 8 August 2002 2599 ORGANIZATION "Multiprotocol Label Switching (mpls) 2600 Working Group" 2601 CONTACT-INFO 2602 "Joan Cucchiara (jcucchiara@crescentnetworks.com) 2603 Crescent Networks 2604 Hans Sjostrand (hans@ipunplugged.com) 2605 ipUnplugged 2607 James V. Luciani (jluciani@crescentnetworks.com) 2608 Crescent Networks 2610 Working Group Chairs: 2611 George Swallow, email: swallow@cisco.com 2612 Loa Andersson, email: loa.andersson@utfors.se 2614 MPLS Working Group, email: mpls@uu.net 2615 " 2616 DESCRIPTION 2617 "This MIB contains managed object definitions for the 2618 'Multiprotocol Label Switching, Label Distribution 2619 Protocol, LDP' document which use as their Layer 2 2620 ethernet." 2621 REVISION "200208081200Z" -- 8 August 2002 2622 DESCRIPTION 2623 "Initial version published as part of RFC XXXX." 2625 ::= { mplsMIB 6 } -- to be assigned 2627 --**************************************************************** 2629 mplsLdpGenericObjects 2630 OBJECT IDENTIFIER ::= { mplsLdpGenericMIB 1 } 2631 mplsLdpGenericConformance 2632 OBJECT IDENTIFIER ::= { mplsLdpGenericMIB 3 } 2634 --**************************************************************** 2635 -- MPLS LDP GENERIC Objects 2636 --**************************************************************** 2638 -- 2639 -- Ldp Entity Objects for Generic Labels 2640 -- 2642 mplsLdpEntityGenericObjects OBJECT IDENTIFIER ::= 2643 { mplsLdpEntityObjects 5 } 2645 -- 2646 -- The MPLS LDP Entity Generic Label Range Table 2647 -- 2649 mplsLdpEntityGenLRTable OBJECT-TYPE 2650 SYNTAX SEQUENCE OF MplsLdpEntityGenLREntry 2651 MAX-ACCESS not-accessible 2652 STATUS current 2653 DESCRIPTION 2654 "The MPLS LDP Entity Generic Label Range 2655 Table. 2657 The purpose of this table is to provide a mechanism 2658 for configurating a contiguous range of generic labels, 2659 or a 'label range' for LDP Entities. 2661 LDP Entities which use Generic Labels must have at least 2662 one entry in this table." 2663 ::= { mplsLdpEntityGenericObjects 1 } 2665 mplsLdpEntityGenLREntry OBJECT-TYPE 2666 SYNTAX MplsLdpEntityGenLREntry 2667 MAX-ACCESS not-accessible 2668 STATUS current 2669 DESCRIPTION 2670 "A row in the LDP Entity Generic Label 2671 Range Table. One entry in this table contains 2672 information on a single range of labels 2673 represented by the configured Upper and Lower 2674 Bounds pairs. NOTE: there is NO corresponding 2675 LDP message which relates to the information 2676 in this table, however, this table does provide 2677 a way for a user to 'reserve' a generic label 2678 range. 2680 NOTE: The ranges for a specific LDP Entity 2681 are UNIQUE and non-overlapping. 2683 A row will not be created unless a unique and 2684 non-overlapping range is specified." 2685 INDEX { mplsLdpEntityLdpId, 2686 mplsLdpEntityIndex, 2687 mplsLdpEntityGenLRMin, 2688 mplsLdpEntityGenLRMax 2689 } 2690 ::= { mplsLdpEntityGenLRTable 1 } 2692 MplsLdpEntityGenLREntry ::= SEQUENCE { 2693 mplsLdpEntityGenLRMin Unsigned32, 2694 mplsLdpEntityGenLRMax Unsigned32, 2695 mplsLdpEntityGenIfIndexOrZero InterfaceIndexOrZero, 2696 mplsLdpEntityGenLRStorageType StorageType, 2697 mplsLdpEntityGenLRRowStatus RowStatus 2698 } 2699 mplsLdpEntityGenLRMin OBJECT-TYPE 2700 SYNTAX Unsigned32(0..1048575) 2701 MAX-ACCESS not-accessible 2702 STATUS current 2703 DESCRIPTION 2704 "The minimum label configured for this range." 2705 ::= { mplsLdpEntityGenLREntry 1 } 2707 mplsLdpEntityGenLRMax OBJECT-TYPE 2708 SYNTAX Unsigned32(0..1048575) 2709 MAX-ACCESS not-accessible 2710 STATUS current 2711 DESCRIPTION 2712 "The maximum label configured for this range." 2713 ::= { mplsLdpEntityGenLREntry 2 } 2715 mplsLdpEntityGenIfIndexOrZero OBJECT-TYPE 2716 SYNTAX InterfaceIndexOrZero 2717 MAX-ACCESS read-create 2718 STATUS current 2719 DESCRIPTION 2720 "This value represents either the InterfaceIndex of 2721 the 'ifLayer' where these Generic Label would be created, 2722 or 0 (zero). The value of zero means that the 2723 InterfaceIndex is not known. For example, if 2724 the InterfaceIndex is created subsequent to 2725 the Generic Label's creation, then it would not be 2726 known. However, if the InterfaceIndex 2727 is known, then it must be represented by this value. 2729 If an InterfaceIndex becomes known, then the 2730 network management entity (e.g. SNMP agent) responsible 2731 for this object MUST change the value from 0 (zero) to the 2732 value of the InterfaceIndex." 2733 ::= { mplsLdpEntityGenLREntry 3 } 2735 mplsLdpEntityGenLRStorageType OBJECT-TYPE 2736 SYNTAX StorageType 2737 MAX-ACCESS read-create 2738 STATUS current 2739 DESCRIPTION 2740 "The storage type for this entry." 2741 ::= { mplsLdpEntityGenLREntry 4 } 2743 mplsLdpEntityGenLRRowStatus OBJECT-TYPE 2744 SYNTAX RowStatus 2745 MAX-ACCESS read-create 2746 STATUS current 2747 DESCRIPTION 2748 "An object that allows entries in this 2749 table to be created and deleted using 2750 the RowStatus convention. 2752 There must exist at least one entry in this 2753 table for every LDP Entity that has a 2754 generic label configured. 2756 NOTE: This RowStatus object should 2757 have the same value of the 'mplsLdpEntityRowStatus' 2758 related to this entry." 2759 ::= { mplsLdpEntityGenLREntry 5 } 2761 --**************************************************************** 2762 -- Module Conformance Statement 2763 --**************************************************************** 2765 mplsLdpGenericGroups 2766 OBJECT IDENTIFIER ::= { mplsLdpGenericConformance 1 } 2768 mplsLdpGenericCompliances 2769 OBJECT IDENTIFIER ::= { mplsLdpGenericConformance 2 } 2771 -- 2772 -- Full Compliance 2773 -- 2775 mplsLdpGenModuleFullCompliance MODULE-COMPLIANCE 2776 STATUS current 2777 DESCRIPTION 2778 "The Module is implemented with support for 2779 read-create and read-write. In other words, 2780 both monitoring and configuration 2781 are available when using this MODULE-COMPLIANCE." 2782 MODULE -- this module 2783 MANDATORY-GROUPS { 2784 mplsLdpGenericGroup 2785 } 2787 OBJECT mplsLdpEntityGenLRRowStatus 2788 SYNTAX RowStatus { active(1) } 2789 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 2790 DESCRIPTION 2791 "Support for createAndWait and notInService is not required." 2793 ::= { mplsLdpGenericCompliances 1 } 2795 -- 2796 -- Read-Only Compliance 2797 -- 2799 mplsLdpGenModuleROCompliance MODULE-COMPLIANCE 2800 STATUS current 2801 DESCRIPTION 2802 "The Module is implemented with support for 2803 read-only. In other words, only monitoring 2804 is available by implementing this MODULE-COMPLIANCE." 2805 MODULE -- this module 2806 MANDATORY-GROUPS { 2807 mplsLdpGenericGroup 2808 } 2810 OBJECT mplsLdpEntityGenIfIndexOrZero 2811 MIN-ACCESS read-only 2812 DESCRIPTION 2813 "Write access is not required." 2815 OBJECT mplsLdpEntityGenLRStorageType 2816 MIN-ACCESS read-only 2817 DESCRIPTION 2818 "Write access is not required." 2820 OBJECT mplsLdpEntityGenLRRowStatus 2821 SYNTAX RowStatus { active(1) } 2822 MIN-ACCESS read-only 2823 DESCRIPTION 2824 "Write access is not required, and active is the 2825 only status that needs to be supported." 2827 ::= { mplsLdpGenericCompliances 2 } 2829 -- 2830 -- units of conformance 2831 -- 2833 mplsLdpGenericGroup OBJECT-GROUP 2834 OBJECTS { 2835 mplsLdpEntityGenIfIndexOrZero, 2836 mplsLdpEntityGenLRStorageType, 2837 mplsLdpEntityGenLRRowStatus 2838 } 2839 STATUS current 2840 DESCRIPTION 2841 "Objects that apply to all MPLS LDP implementations 2842 using Generic Lables." 2843 ::= { mplsLdpGenericGroups 1 } 2845 END 2847 4.2. The MPLS-LDP-ATM-MIB Module 2849 This MIB Module MUST be supported if LDP uses ATM as the Layer 2 2850 media. There are three tables in this MIB Moduel. Two tables are 2851 for configuring LDP to use ATM. These tables are the 2852 mplsLdpEntityAtmParmsTable and the mplsLdpEntityAtmLabelRangeTable. 2854 The mplsLdpEntityAtmParmsTable provides a way to configure 2855 information which would be contained in the "Optional Parameter" 2856 portion of an LDP PDU Initialization Message. 2858 The mplsLdpEntityAtmLabelRangeTable provides a way to configure 2859 information which would be contained in the "ATM Label Range 2860 Components" portion of an LDP PDU Intialization Message, see 2861 [RFC3035] and [RFC3036]. 2863 4.2.1. The LDP ATM Session Table 2865 The MPLS LDP ATM Session Table is a read-only table which contains 2866 session information specific to ATM. 2868 MPLS-LDP-ATM-MIB DEFINITIONS ::= BEGIN 2870 IMPORTS 2871 OBJECT-TYPE, MODULE-IDENTITY, 2872 Unsigned32 2873 FROM SNMPv2-SMI 2874 MODULE-COMPLIANCE, OBJECT-GROUP 2875 FROM SNMPv2-CONF 2877 RowStatus, 2878 StorageType 2879 FROM SNMPv2-TC 2881 InterfaceIndexOrZero 2882 FROM IF-MIB 2884 AtmVpIdentifier 2885 FROM ATM-TC-MIB 2887 mplsMIB, 2888 MplsAtmVcIdentifier 2889 FROM MPLS-TC-MIB 2891 mplsLdpEntityObjects, 2892 mplsLdpSessionObjects, 2893 mplsLdpEntityLdpId, 2894 mplsLdpEntityIndex, 2895 mplsLdpPeerLdpId 2896 FROM MPLS-LDP-MIB 2898 ; 2900 mplsLdpAtmMIB MODULE-IDENTITY 2901 LAST-UPDATED "200208081200Z" -- 8 August 2002 2902 ORGANIZATION "Multiprotocol Label Switching (mpls) 2903 Working Group" 2904 CONTACT-INFO 2905 "Joan Cucchiara (jcucchiara@crescentnetworks.com) 2906 Crescent Networks 2908 Hans Sjostrand (hans@ipunplugged.com) 2909 ipUnplugged 2911 James V. Luciani (jluciani@crescentnetworks.com) 2912 Crescent Networks 2914 Working Group Chairs: 2915 George Swallow, email: swallow@cisco.com 2916 Loa Andersson, email: loa.anderssson@utfors.se 2918 MPLS Working Group, email: mpls@uu.net 2919 " 2920 DESCRIPTION 2921 "This MIB contains managed object definitions for the 2922 'Multiprotocol Label Switching, Label Distribution 2923 Protocol, LDP' document." 2924 REVISION "200208081200Z" -- 8 August 2002 2925 DESCRIPTION 2926 "Initial version published as part of RFC XXXX." 2928 ::= { mplsMIB 4 } -- to be assigned 2930 --**************************************************************** 2931 mplsLdpAtmObjects OBJECT IDENTIFIER ::= { mplsLdpAtmMIB 1 } 2932 mplsLdpAtmNotifications OBJECT IDENTIFIER ::= { mplsLdpAtmMIB 2 } 2933 mplsLdpAtmConformance OBJECT IDENTIFIER ::= { mplsLdpAtmMIB 3 } 2935 --**************************************************************** 2936 -- MPLS LDP Frame Relay Objects 2937 --**************************************************************** 2939 -- 2940 -- Ldp Entity Objects for ATM 2941 -- 2943 mplsLdpEntityAtmObjects OBJECT IDENTIFIER ::= 2944 { mplsLdpEntityObjects 6 } 2946 mplsLdpEntityAtmParmsTable OBJECT-TYPE 2947 SYNTAX SEQUENCE OF MplsLdpEntityAtmParmsEntry 2948 MAX-ACCESS not-accessible 2949 STATUS current 2950 DESCRIPTION 2951 "This table contains information about the 2952 ATM specific information which could be used 2953 in the 'Optional Parameters' and other ATM specific 2954 information." 2955 ::= { mplsLdpEntityAtmObjects 1 } 2957 mplsLdpEntityAtmParmsEntry OBJECT-TYPE 2958 SYNTAX MplsLdpEntityAtmParmsEntry 2959 MAX-ACCESS not-accessible 2960 STATUS current 2961 DESCRIPTION 2962 "An entry in this table represents the ATM parameters 2963 and ATM information for this LDP entity." 2964 INDEX { mplsLdpEntityLdpId, 2965 mplsLdpEntityIndex 2966 } 2967 ::= { mplsLdpEntityAtmParmsTable 1 } 2969 MplsLdpEntityAtmParmsEntry ::= SEQUENCE { 2970 mplsLdpEntityAtmIfIndexOrZero InterfaceIndexOrZero, 2971 mplsLdpEntityAtmMergeCap INTEGER, 2972 mplsLdpEntityAtmLRComponents Unsigned32, 2973 mplsLdpEntityAtmVcDirectionality INTEGER, 2974 mplsLdpEntityAtmLsrConnectivity INTEGER, 2975 mplsLdpEntityDefaultControlVpi AtmVpIdentifier, 2976 mplsLdpEntityDefaultControlVci MplsAtmVcIdentifier, 2977 mplsLdpEntityUnlabTrafVpi AtmVpIdentifier, 2978 mplsLdpEntityUnlabTrafVci MplsAtmVcIdentifier, 2979 mplsLdpEntityAtmStorageType StorageType, 2980 mplsLdpEntityAtmRowStatus RowStatus 2981 } 2983 mplsLdpEntityAtmIfIndexOrZero OBJECT-TYPE 2984 SYNTAX InterfaceIndexOrZero 2985 MAX-ACCESS read-create 2986 STATUS current 2987 DESCRIPTION 2988 "This value represents either the InterfaceIndex of 2989 the 'ifLayer' where the ATM Labels 'owned' by this 2990 entry were created, or 0 (zero). The value of zero 2991 means that the InterfaceIndex is not known. For example, 2992 if the InterfaceIndex is created subsequent to the 2993 ATM Label's creation, then it would not be known. 2994 However, if the InterfaceIndex is known, then it must 2995 be represented by this value. 2997 If an InterfaceIndex becomes known, then the 2998 network management entity (e.g. SNMP agent) responsible 2999 for this object MUST change the value from 0 (zero) to the 3000 value of the InterfaceIndex. If an ATM Label is 3001 being used in forwarding data, then the value of this 3002 object MUST be the InterfaceIndex." 3003 ::= { mplsLdpEntityAtmParmsEntry 1 } 3005 mplsLdpEntityAtmMergeCap OBJECT-TYPE 3006 SYNTAX INTEGER { 3007 notSupported(0), 3008 vcMerge(2) 3009 } 3010 MAX-ACCESS read-create 3011 STATUS current 3012 DESCRIPTION 3013 "Denotes the Merge Capability of this Entity." 3014 ::= { mplsLdpEntityAtmParmsEntry 2 } 3016 mplsLdpEntityAtmLRComponents OBJECT-TYPE 3017 SYNTAX Unsigned32 (1..65535) 3018 MAX-ACCESS read-create 3019 STATUS current 3020 DESCRIPTION 3021 "Number of Label Range Components in the Initialization 3022 message. This also represents the number of entries 3023 in the mplsLdpEntityAtmLRTable which correspond 3024 to this entry." 3025 ::= { mplsLdpEntityAtmParmsEntry 3 } 3027 mplsLdpEntityAtmVcDirectionality OBJECT-TYPE 3028 SYNTAX INTEGER { 3029 bidirectional(0), 3030 unidirectional(1) 3031 } 3032 MAX-ACCESS read-create 3033 STATUS current 3034 DESCRIPTION 3035 "If the value of this object is 'bidirectional(0)', 3036 a given VCI, within a given VPI, is used as a 3037 label for both directions independently. 3039 If the value of this object is 'unidirectional(1)', 3040 a given VCI within a VPI designates one direction." 3041 ::= { mplsLdpEntityAtmParmsEntry 4 } 3043 mplsLdpEntityAtmLsrConnectivity OBJECT-TYPE 3044 SYNTAX INTEGER { 3045 direct(1), 3046 indirect(2) 3047 } 3048 MAX-ACCESS read-create 3049 STATUS current 3050 DESCRIPTION 3051 "The peer LSR may be connected indirectly by means of an 3052 ATM VP so that the VPI values may be different on either 3053 endpoint so the label MUST be encoded entirely within the 3054 VCI field." 3055 DEFVAL { direct } 3056 ::= { mplsLdpEntityAtmParmsEntry 5 } 3058 mplsLdpEntityDefaultControlVpi OBJECT-TYPE 3059 SYNTAX AtmVpIdentifier 3060 MAX-ACCESS read-create 3061 STATUS current 3062 DESCRIPTION 3063 "The default VPI value for the non-MPLS connection. The 3064 default value of this is 0 (zero) but other values may 3065 be configured. This object allows a different value 3066 to be configured." 3067 DEFVAL 3068 { 0 } 3069 ::= { mplsLdpEntityAtmParmsEntry 6 } 3071 mplsLdpEntityDefaultControlVci OBJECT-TYPE 3072 SYNTAX MplsAtmVcIdentifier 3073 MAX-ACCESS read-create 3074 STATUS current 3075 DESCRIPTION 3076 "The Default VCI value for a non-MPLS connection. The 3077 default value of this is 32 but other values may be 3078 configured. This object allows a different value to 3079 be configured." 3080 DEFVAL 3081 { 32 } 3082 ::= { mplsLdpEntityAtmParmsEntry 7 } 3084 mplsLdpEntityUnlabTrafVpi OBJECT-TYPE 3085 SYNTAX AtmVpIdentifier 3086 MAX-ACCESS read-create 3087 STATUS current 3088 DESCRIPTION 3089 "VPI value of the VCC supporting unlabeled traffic. This 3090 non-MPLS connection is used to carry unlabeled (IP) 3091 packets. The default value is the same as the default 3092 value of the 'mplsLdpEntityDefaultControlVpi', however 3093 another value may be configured." 3094 DEFVAL { 0 } 3095 ::= { mplsLdpEntityAtmParmsEntry 8 } 3097 mplsLdpEntityUnlabTrafVci OBJECT-TYPE 3098 SYNTAX MplsAtmVcIdentifier 3099 MAX-ACCESS read-create 3100 STATUS current 3101 DESCRIPTION 3102 "VCI value of the VCC supporting unlabeled traffic. 3103 This non-MPLS connection is used to carry unlabeled (IP) 3104 packets. The default value is the same as the default 3105 value of the 'mplsLdpEntityDefaultControlVci', however 3106 another value may be configured." 3107 DEFVAL { 32 } 3108 ::= { mplsLdpEntityAtmParmsEntry 9 } 3110 mplsLdpEntityAtmStorageType OBJECT-TYPE 3111 SYNTAX StorageType 3112 MAX-ACCESS read-create 3113 STATUS current 3114 DESCRIPTION 3115 "The storage type for this entry." 3116 ::= { mplsLdpEntityAtmParmsEntry 10 } 3118 mplsLdpEntityAtmRowStatus OBJECT-TYPE 3119 SYNTAX RowStatus 3120 MAX-ACCESS read-create 3121 STATUS current 3122 DESCRIPTION 3123 "An object that allows entries in this table to 3124 be created and deleted using the 3125 RowStatus convention. 3127 NOTE: This RowStatus object should 3128 have the same value of the 'mplsLdpEntityRowStatus' 3129 related to this entry." 3130 ::= { mplsLdpEntityAtmParmsEntry 11 } 3132 -- 3133 -- The MPLS LDP Entity ATM Label Range Table 3134 -- 3136 mplsLdpEntityAtmLRTable OBJECT-TYPE 3137 SYNTAX SEQUENCE OF MplsLdpEntityAtmLREntry 3138 MAX-ACCESS not-accessible 3139 STATUS current 3140 DESCRIPTION 3141 "The MPLS LDP Entity ATM Label Range Table. 3142 The purpose of this table is to provide a mechanism 3143 for configuring a contiguous range of vpi's 3144 with a contiguous range of vci's, or a 'label range' 3145 for LDP Entities. 3147 LDP Entities which use ATM must have at least one 3148 entry in this table." 3149 ::= { mplsLdpEntityAtmObjects 2 } 3151 mplsLdpEntityAtmLREntry OBJECT-TYPE 3152 SYNTAX MplsLdpEntityAtmLREntry 3153 MAX-ACCESS not-accessible 3154 STATUS current 3155 DESCRIPTION 3156 "A row in the LDP Entity ATM Label 3157 Range Table. One entry in this table contains 3158 information on a single range of labels 3159 represented by the configured Upper and Lower 3160 Bounds VPI/VCI pairs. These are the same 3161 data used in the Initialization Message. 3163 NOTE: The ranges for a specific LDP Entity 3164 are UNIQUE and non-overlapping. For example, 3165 for a specific LDP Entity index, there could 3166 be one entry having LowerBound vpi/vci == 0/32, and 3167 UpperBound vpi/vci == 0/100, and a second entry 3168 for this same interface with LowerBound 3169 vpi/vci == 0/101 and UpperBound vpi/vci == 0/200. 3170 However, there could not be a third entry with 3171 LowerBound vpi/vci == 0/200 and 3172 UpperBound vpi/vci == 0/300 because this label 3173 range overlaps with the second entry (i.e. both 3174 entries now have 0/200). 3176 A row will not be created unless a unique and 3177 non-overlapping range is specified. Thus, row 3178 creation implies a one-shot row creation of 3179 LDP EntityID and LowerBound vpi/vci and 3180 UpperBound vpi/vci. At least one label 3181 range entry for a specific LDP Entity MUST 3182 include the default VPI/VCI values denoted 3183 in the LDP Entity Table." 3184 INDEX { mplsLdpEntityLdpId, 3185 mplsLdpEntityIndex, 3186 mplsLdpEntityAtmLRMinVpi, 3187 mplsLdpEntityAtmLRMinVci 3188 } 3189 ::= { mplsLdpEntityAtmLRTable 1 } 3191 MplsLdpEntityAtmLREntry ::= SEQUENCE { 3192 mplsLdpEntityAtmLRMinVpi AtmVpIdentifier, 3193 mplsLdpEntityAtmLRMinVci MplsAtmVcIdentifier, 3194 mplsLdpEntityAtmLRMaxVpi AtmVpIdentifier, 3195 mplsLdpEntityAtmLRMaxVci MplsAtmVcIdentifier, 3196 mplsLdpEntityAtmLRStorageType StorageType, 3197 mplsLdpEntityAtmLRRowStatus RowStatus 3198 } 3200 mplsLdpEntityAtmLRMinVpi OBJECT-TYPE 3201 SYNTAX AtmVpIdentifier 3202 MAX-ACCESS not-accessible 3203 STATUS current 3204 DESCRIPTION 3205 "The minimum VPI number configured for this range." 3206 ::= { mplsLdpEntityAtmLREntry 1 } 3208 mplsLdpEntityAtmLRMinVci OBJECT-TYPE 3209 SYNTAX MplsAtmVcIdentifier 3210 MAX-ACCESS not-accessible 3211 STATUS current 3212 DESCRIPTION 3213 "The minimum VCI number configured for this range." 3214 ::= { mplsLdpEntityAtmLREntry 2 } 3216 mplsLdpEntityAtmLRMaxVpi OBJECT-TYPE 3217 SYNTAX AtmVpIdentifier 3218 MAX-ACCESS read-create 3219 STATUS current 3220 DESCRIPTION 3221 "The maximum VPI number configured for this range." 3222 ::= { mplsLdpEntityAtmLREntry 3 } 3224 mplsLdpEntityAtmLRMaxVci OBJECT-TYPE 3225 SYNTAX MplsAtmVcIdentifier 3226 MAX-ACCESS read-create 3227 STATUS current 3228 DESCRIPTION 3229 "The maximum VCI number configured for this range." 3230 ::= { mplsLdpEntityAtmLREntry 4 } 3232 mplsLdpEntityAtmLRStorageType OBJECT-TYPE 3233 SYNTAX StorageType 3234 MAX-ACCESS read-create 3235 STATUS current 3236 DESCRIPTION 3237 "The storage type for this entry." 3238 ::= { mplsLdpEntityAtmLREntry 5 } 3240 mplsLdpEntityAtmLRRowStatus OBJECT-TYPE 3241 SYNTAX RowStatus 3242 MAX-ACCESS read-create 3243 STATUS current 3244 DESCRIPTION 3245 "An object that allows entries in this 3246 table to be created and deleted using 3247 the RowStatus convention. 3249 There must exist at least one entry in this 3250 table for every LDP Entity that has 3251 'mplsLdpEntityOptionalParameters' object with 3252 a value of 'atmSessionParameters'. 3254 NOTE: This RowStatus object should 3255 have the same value of the 'mplsLdpEntityRowStatus' 3256 related to this entry." 3257 ::= { mplsLdpEntityAtmLREntry 6 } 3259 -- 3260 -- MPLS LDP ATM Session Information 3261 -- 3263 mplsLdpAtmSesTable OBJECT-TYPE 3264 SYNTAX SEQUENCE OF MplsLdpAtmSesEntry 3265 MAX-ACCESS not-accessible 3266 STATUS current 3267 DESCRIPTION 3268 "A table which relates Sessions in the 3269 'mplsLdpSessionTable' and their label 3270 range intersections. There could be one 3271 or more label range intersections between an 3272 LDP Entity and LDP Peer using ATM as the underlying 3273 media. Each row represents a single label range 3274 intersection. 3276 NOTE: this table cannot use the 'AUGMENTS' 3277 clause because there is not necessarily a one-to-one 3278 mapping between this table and the mplsLdpSessionTable." 3279 ::= { mplsLdpSessionObjects 10 } 3281 mplsLdpAtmSesEntry OBJECT-TYPE 3282 SYNTAX MplsLdpAtmSesEntry 3283 MAX-ACCESS not-accessible 3284 STATUS current 3285 DESCRIPTION 3286 "An entry in this table represents information on a 3287 single label range intersection between an LDP Entity 3288 and LDP Peer. 3290 The information contained in a row is read-only." 3291 INDEX { mplsLdpEntityLdpId, 3292 mplsLdpEntityIndex, 3293 mplsLdpPeerLdpId, 3294 mplsLdpSesAtmLRLowerBoundVpi, 3295 mplsLdpSesAtmLRLowerBoundVci 3297 } 3298 ::= { mplsLdpAtmSesTable 1 } 3300 MplsLdpAtmSesEntry ::= SEQUENCE { 3301 mplsLdpSesAtmLRLowerBoundVpi AtmVpIdentifier, 3302 mplsLdpSesAtmLRLowerBoundVci MplsAtmVcIdentifier, 3303 mplsLdpSesAtmLRUpperBoundVpi AtmVpIdentifier, 3304 mplsLdpSesAtmLRUpperBoundVci MplsAtmVcIdentifier 3305 } 3307 mplsLdpSesAtmLRLowerBoundVpi OBJECT-TYPE 3308 SYNTAX AtmVpIdentifier 3309 MAX-ACCESS not-accessible 3310 STATUS current 3311 DESCRIPTION 3312 "The minimum VPI number for this range." 3313 ::= { mplsLdpAtmSesEntry 1 } 3315 mplsLdpSesAtmLRLowerBoundVci OBJECT-TYPE 3316 SYNTAX MplsAtmVcIdentifier 3317 MAX-ACCESS not-accessible 3318 STATUS current 3319 DESCRIPTION 3320 "The minimum VCI number for this range." 3321 ::= { mplsLdpAtmSesEntry 2 } 3323 mplsLdpSesAtmLRUpperBoundVpi OBJECT-TYPE 3324 SYNTAX AtmVpIdentifier 3325 MAX-ACCESS read-only 3326 STATUS current 3327 DESCRIPTION 3328 "The maximum VPI number for this range." 3329 ::= { mplsLdpAtmSesEntry 3 } 3331 mplsLdpSesAtmLRUpperBoundVci OBJECT-TYPE 3332 SYNTAX MplsAtmVcIdentifier 3333 MAX-ACCESS read-only 3334 STATUS current 3335 DESCRIPTION 3336 "The maximum VCI number for this range." 3337 ::= { mplsLdpAtmSesEntry 4 } 3339 --************************************************************** 3340 -- Module Conformance Statement 3341 --************************************************************** 3343 mplsLdpAtmGroups 3344 OBJECT IDENTIFIER ::= { mplsLdpAtmConformance 1 } 3346 mplsLdpAtmCompliances 3347 OBJECT IDENTIFIER ::= { mplsLdpAtmConformance 2 } 3349 -- 3350 -- Full Compliance 3351 -- 3353 mplsLdpAtmModuleFullCompliance MODULE-COMPLIANCE 3354 STATUS current 3355 DESCRIPTION 3356 "The Module is implemented with support for 3357 read-create and read-write. In other words, 3358 both monitoring and configuration 3359 are available when using this MODULE-COMPLIANCE." 3360 MODULE -- this module 3361 MANDATORY-GROUPS { 3362 mplsLdpAtmGroup 3363 } 3365 OBJECT mplsLdpEntityAtmRowStatus 3366 SYNTAX RowStatus { active(1) } 3367 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 3368 DESCRIPTION 3369 "Support for createAndWait and notInService is not required." 3371 OBJECT mplsLdpEntityAtmLRRowStatus 3372 SYNTAX RowStatus { active(1) } 3373 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 3374 DESCRIPTION 3375 "Support for createAndWait and notInService is not required." 3377 ::= { mplsLdpAtmCompliances 1 } 3379 -- 3380 -- Read-Only Compliance 3381 -- 3383 mplsLdpAtmModuleROCompliance MODULE-COMPLIANCE 3384 STATUS current 3385 DESCRIPTION 3386 "The Module is implemented with support for 3387 read-only. In other words, only monitoring 3388 is available by implementing this MODULE-COMPLIANCE." 3389 MODULE -- this module 3390 MANDATORY-GROUPS { 3391 mplsLdpAtmGroup 3392 } 3394 OBJECT mplsLdpEntityAtmIfIndexOrZero 3395 MIN-ACCESS read-only 3396 DESCRIPTION 3397 "Write access is not required." 3399 OBJECT mplsLdpEntityAtmMergeCap 3400 MIN-ACCESS read-only 3401 DESCRIPTION 3402 "Write access is not required." 3404 OBJECT mplsLdpEntityAtmLRComponents 3405 MIN-ACCESS read-only 3406 DESCRIPTION 3407 "Write access is not required." 3409 OBJECT mplsLdpEntityAtmVcDirectionality 3410 MIN-ACCESS read-only 3411 DESCRIPTION 3412 "Write access is not required." 3414 OBJECT mplsLdpEntityAtmLsrConnectivity 3415 MIN-ACCESS read-only 3416 DESCRIPTION 3417 "Write access is not required." 3419 OBJECT mplsLdpEntityDefaultControlVpi 3420 MIN-ACCESS read-only 3421 DESCRIPTION 3422 "Write access is not required." 3424 OBJECT mplsLdpEntityDefaultControlVci 3425 MIN-ACCESS read-only 3426 DESCRIPTION 3427 "Write access is not required." 3429 OBJECT mplsLdpEntityUnlabTrafVpi 3430 MIN-ACCESS read-only 3431 DESCRIPTION 3432 "Write access is not required." 3434 OBJECT mplsLdpEntityUnlabTrafVci 3435 MIN-ACCESS read-only 3436 DESCRIPTION 3437 "Write access is not required." 3439 OBJECT mplsLdpEntityAtmStorageType 3440 MIN-ACCESS read-only 3441 DESCRIPTION 3442 "Write access is not required." 3444 OBJECT mplsLdpEntityAtmRowStatus 3445 SYNTAX RowStatus { active(1) } 3446 MIN-ACCESS read-only 3447 DESCRIPTION 3448 "Write access is not required, and active is the 3449 only status that needs to be supported." 3451 OBJECT mplsLdpEntityAtmLRMaxVpi 3452 MIN-ACCESS read-only 3453 DESCRIPTION 3454 "Write access is not required." 3456 OBJECT mplsLdpEntityAtmLRMaxVci 3457 MIN-ACCESS read-only 3458 DESCRIPTION 3459 "Write access is not required." 3461 OBJECT mplsLdpEntityAtmLRStorageType 3462 MIN-ACCESS read-only 3463 DESCRIPTION 3464 "Write access is not required." 3466 OBJECT mplsLdpEntityAtmLRRowStatus 3467 SYNTAX RowStatus { active(1) } 3468 MIN-ACCESS read-only 3469 DESCRIPTION 3470 "Write access is not required, and active is the 3471 only status that needs to be supported." 3473 ::= { mplsLdpAtmCompliances 2 } 3475 -- 3476 -- units of conformance 3477 -- 3479 mplsLdpAtmGroup OBJECT-GROUP 3480 OBJECTS { 3481 mplsLdpEntityAtmIfIndexOrZero, 3482 mplsLdpEntityAtmMergeCap, 3483 mplsLdpEntityAtmLRComponents, 3484 mplsLdpEntityAtmVcDirectionality, 3485 mplsLdpEntityAtmLsrConnectivity, 3486 mplsLdpEntityDefaultControlVpi, 3487 mplsLdpEntityDefaultControlVci, 3488 mplsLdpEntityUnlabTrafVpi, 3489 mplsLdpEntityUnlabTrafVci, 3490 mplsLdpEntityAtmStorageType, 3491 mplsLdpEntityAtmRowStatus, 3492 mplsLdpEntityAtmLRMaxVpi, 3493 mplsLdpEntityAtmLRMaxVci, 3494 mplsLdpEntityAtmLRStorageType, 3495 mplsLdpEntityAtmLRRowStatus, 3496 mplsLdpSesAtmLRUpperBoundVpi, 3497 mplsLdpSesAtmLRUpperBoundVci 3499 } 3500 STATUS current 3501 DESCRIPTION 3502 "Objects that apply to all MPLS LDP implementations 3503 using ATM as the Layer 2." 3504 ::= { mplsLdpAtmGroups 1 } 3506 END 3508 4.3. The MPLS-LDP-FRAME-RELAY-MIB Module 3510 This MIB Module MUST be supported if LDP uses FRAME RELAY as the 3511 Layer 2 media. There are three tables in this MIB Moduel. Two 3512 tables are to configure LDP for using Frame Relay. These tables are 3513 the mplsLdpEntityFrameRelayParmsTable and the 3514 mplsLdpEntityFrLabelRangeTable. 3516 The mplsLdpEntityFrameRelayParmsTable provides a way to configure 3517 information which would be contained in the "Optional Parameter" 3518 portion of an LDP PDU Initialization Message. 3520 The mplsLdpEntityFrLabelRangeTable provides a way to configure 3521 information which would be contained in the "Frame Relay Label Range 3522 Components" portion of an LDP PDU Intialization Message, see 3523 [RFC3034] and [RFC3036]. 3525 4.3.1. The LDP Frame Relay Session Table 3527 The MPLS LDP Frame Relay Session Table is a read-only table which 3528 contains session information specific to Frame Relay. 3530 MPLS-LDP-FRAME-RELAY-MIB DEFINITIONS ::= BEGIN 3532 IMPORTS 3533 OBJECT-TYPE, 3534 MODULE-IDENTITY, 3535 Integer32, 3536 Unsigned32 3537 FROM SNMPv2-SMI 3538 MODULE-COMPLIANCE, 3539 OBJECT-GROUP 3540 FROM SNMPv2-CONF 3542 RowStatus, 3543 StorageType 3544 FROM SNMPv2-TC 3546 InterfaceIndexOrZero 3547 FROM IF-MIB 3549 mplsMIB 3550 FROM MPLS-TC-MIB 3552 mplsLdpEntityObjects, 3553 mplsLdpSessionObjects, 3554 mplsLdpEntityLdpId, 3555 mplsLdpEntityIndex, 3556 mplsLdpPeerLdpId 3557 FROM MPLS-LDP-MIB 3559 ; 3561 mplsLdpFrameRelayMIB MODULE-IDENTITY 3562 LAST-UPDATED "200208081200Z" -- 8 August 2002 3563 ORGANIZATION "Multiprotocol Label Switching (mpls) 3564 Working Group" 3565 CONTACT-INFO 3566 "Joan Cucchiara (jcucchiara@crescentnetworks.com) 3567 Crescent Networks 3569 Hans Sjostrand (hans@ipunplugged.com) 3570 ipUnplugged 3572 James V. Luciani (jluciani@crescentnetworks.com) 3573 Crescent Networks 3575 Working Group Chairs: 3576 George Swallow, email: swallow@cisco.com 3577 Loa Andersson, email: loa.andersson@utfors.se 3579 MPLS Working Group, email: mpls@uu.net 3580 " 3581 DESCRIPTION 3582 "This MIB contains managed object definitions for the 3583 'Multiprotocol Label Switching, Label Distribution 3584 Protocol, LDP' document." 3585 REVISION "200208081200Z" -- 8 August 2002 3586 DESCRIPTION 3587 "Initial version published as part of RFC XXXX." 3589 ::= { mplsMIB 5 } -- to be assigned 3591 --**************************************************************** 3593 mplsLdpFrameRelayObjects 3594 OBJECT IDENTIFIER ::= { mplsLdpFrameRelayMIB 1 } 3595 mplsLdpFrameRelayNotifications 3596 OBJECT IDENTIFIER ::= { mplsLdpFrameRelayMIB 2 } 3597 mplsLdpFrameRelayConformance 3598 OBJECT IDENTIFIER ::= { mplsLdpFrameRelayMIB 3 } 3600 --**************************************************************** 3601 -- MPLS LDP Frame Relay Objects 3602 --**************************************************************** 3604 -- 3605 -- Ldp Entity Objects for Frame Relay 3606 -- 3608 mplsLdpEntityFrameRelayObjects OBJECT IDENTIFIER ::= 3609 { mplsLdpEntityObjects 7 } 3611 mplsLdpEntityFrParmsTable OBJECT-TYPE 3612 SYNTAX SEQUENCE OF MplsLdpEntityFrParmsEntry 3613 MAX-ACCESS not-accessible 3614 STATUS current 3615 DESCRIPTION 3616 "This table contains information about the 3617 Optional Parameters to specify what this Entity is 3618 going to specify for Frame Relay specific 3619 LDP Intialization Messages." 3620 ::= { mplsLdpEntityFrameRelayObjects 1 } 3622 mplsLdpEntityFrParmsEntry OBJECT-TYPE 3623 SYNTAX MplsLdpEntityFrParmsEntry 3624 MAX-ACCESS not-accessible 3625 STATUS current 3626 DESCRIPTION 3627 "An entry in this table represents the Frame Relay 3628 optional parameters associated with the LDP entity." 3629 INDEX { mplsLdpEntityLdpId, 3630 mplsLdpEntityIndex 3631 } 3632 ::= { mplsLdpEntityFrParmsTable 1 } 3634 MplsLdpEntityFrParmsEntry ::= SEQUENCE { 3635 mplsLdpEntityFrIfIndexOrZero InterfaceIndexOrZero, 3636 mplsLdpEntityFrMergeCap INTEGER, 3637 mplsLdpEntityFrLRComponents Unsigned32, 3638 mplsLdpEntityFrLength INTEGER, 3639 mplsLdpEntityFrVcDirectionality INTEGER, 3640 mplsLdpEntityFrStorageType StorageType, 3641 mplsLdpEntityFrRowStatus RowStatus 3642 } 3644 mplsLdpEntityFrIfIndexOrZero OBJECT-TYPE 3645 SYNTAX InterfaceIndexOrZero 3646 MAX-ACCESS read-create 3647 STATUS current 3648 DESCRIPTION 3649 "This value represents either the InterfaceIndex of 3650 the 'ifLayer' where the Frame Relay Labels 'owned' by this 3651 entry were created, or 0 (zero). The value of zero 3652 means that the InterfaceIndex is not known. For example, 3653 if the InterfaceIndex is created subsequent to the 3654 Frame Relay Label's creation, then it would not be known. 3655 However, if the InterfaceIndex is known, then it must 3656 be represented by this value. 3658 If an InterfaceIndex becomes known, then the 3659 network management entity (e.g. SNMP agent) responsible 3660 for this object MUST change the value from 0 (zero) to the 3661 value of the InterfaceIndex. If an Frame Relay Label is 3662 being used in forwarding data, then the value of this 3663 object MUST be the InterfaceIndex." 3665 ::= { mplsLdpEntityFrParmsEntry 1 } 3667 mplsLdpEntityFrMergeCap OBJECT-TYPE 3668 SYNTAX INTEGER { 3669 notSupported(0), 3670 supported(1) 3671 } 3672 MAX-ACCESS read-create 3673 STATUS current 3674 DESCRIPTION 3675 "This represents whether or not Frame Relay merge 3676 capability is supported." 3677 ::= { mplsLdpEntityFrParmsEntry 2 } 3679 mplsLdpEntityFrLRComponents OBJECT-TYPE 3680 SYNTAX Unsigned32 (1..65535) 3681 MAX-ACCESS read-create 3682 STATUS current 3683 DESCRIPTION 3684 "Number of LabelRange Components in the Initialization 3685 message. This also represents the number of entries 3686 in the mplsLdpEntityConfFrLRTable which correspond 3687 to this entry." 3688 ::= { mplsLdpEntityFrParmsEntry 3 } 3690 mplsLdpEntityFrLength OBJECT-TYPE 3691 SYNTAX INTEGER { 3692 tenDlciBits(0), 3693 twentyThreeDlciBits(2) 3694 } 3695 MAX-ACCESS read-create 3696 STATUS current 3697 DESCRIPTION 3698 "This object specifies the length of the DLCI bits." 3699 ::= { mplsLdpEntityFrParmsEntry 4 } 3701 mplsLdpEntityFrVcDirectionality OBJECT-TYPE 3702 SYNTAX INTEGER { 3703 bidirectional(0), 3704 unidirection(1) 3705 } 3706 MAX-ACCESS read-create 3707 STATUS current 3708 DESCRIPTION 3709 "If the value of this object is 'bidirectional(0)', then 3710 the LSR supports the use of a given DLCI as a label for 3711 both directions independently. If the value of 3712 this object is 'unidirectional(1)', then the LSR 3713 uses the given DLCI as a label in only one direction." 3714 ::= { mplsLdpEntityFrParmsEntry 5 } 3716 mplsLdpEntityFrStorageType OBJECT-TYPE 3717 SYNTAX StorageType 3718 MAX-ACCESS read-create 3719 STATUS current 3720 DESCRIPTION 3721 "The storage type for this entry." 3722 ::= { mplsLdpEntityFrParmsEntry 6 } 3724 mplsLdpEntityFrRowStatus OBJECT-TYPE 3725 SYNTAX RowStatus 3726 MAX-ACCESS read-create 3727 STATUS current 3728 DESCRIPTION 3729 "An object that allows entries in this table to 3730 be created and deleted using the 3731 RowStatus convention. 3733 NOTE: This RowStatus object should 3734 have the same value of the 'mplsLdpEntityRowStatus' 3735 related to this entry." 3736 ::= { mplsLdpEntityFrParmsEntry 7 } 3738 -- 3739 -- Frame Relay Label Range Components 3740 -- 3742 mplsLdpEntityFrLRTable OBJECT-TYPE 3743 SYNTAX SEQUENCE OF MplsLdpEntityFrLREntry 3744 MAX-ACCESS not-accessible 3745 STATUS current 3746 DESCRIPTION 3747 "This table contains information about the 3748 Optional Parameters to specify what this Entity is 3749 going to specify for Frame Relay specific 3750 LDP Intialization Messages." 3751 ::= { mplsLdpEntityFrameRelayObjects 2 } 3753 mplsLdpEntityFrLREntry OBJECT-TYPE 3754 SYNTAX MplsLdpEntityFrLREntry 3755 MAX-ACCESS not-accessible 3756 STATUS current 3757 DESCRIPTION 3758 "An entry in this table represents the Frame Relay 3759 optional parameters associated with the LDP entity." 3760 INDEX { mplsLdpEntityLdpId, 3761 mplsLdpEntityIndex, 3762 mplsLdpEntityFrLRMinDlci 3763 } 3765 ::= { mplsLdpEntityFrLRTable 1 } 3767 MplsLdpEntityFrLREntry ::= SEQUENCE { 3768 mplsLdpEntityFrLRMinDlci Integer32, 3769 mplsLdpEntityFrLRMaxDlci Integer32, 3770 mplsLdpEntityFrLRStorageType StorageType, 3771 mplsLdpEntityFrLRRowStatus RowStatus 3772 } 3774 mplsLdpEntityFrLRMinDlci OBJECT-TYPE 3775 SYNTAX Integer32(0..4194303) 3776 MAX-ACCESS not-accessible 3777 STATUS current 3778 DESCRIPTION 3779 "The lower bound which is supported. This value should 3780 be the same as that in the Frame Relay Label Range 3781 Component's Minimum DLCI field." 3782 ::= { mplsLdpEntityFrLREntry 1 } 3784 mplsLdpEntityFrLRMaxDlci OBJECT-TYPE 3785 SYNTAX Integer32 (0..4194303) 3786 MAX-ACCESS read-create 3787 STATUS current 3788 DESCRIPTION 3789 "The upper bound which is supported. This value should 3790 be the same as that in the Frame Relay Label Range 3791 Component's Maximum DLCI field." 3792 ::= { mplsLdpEntityFrLREntry 2 } 3794 mplsLdpEntityFrLRStorageType OBJECT-TYPE 3795 SYNTAX StorageType 3796 MAX-ACCESS read-create 3797 STATUS current 3798 DESCRIPTION 3799 "The storage type for this entry." 3800 ::= { mplsLdpEntityFrLREntry 3 } 3802 mplsLdpEntityFrLRRowStatus OBJECT-TYPE 3803 SYNTAX RowStatus 3804 MAX-ACCESS read-create 3805 STATUS current 3806 DESCRIPTION 3807 "An object that allows entries in this table to 3808 be created and deleted using the 3809 RowStatus convention. 3811 If the value of the object 3812 'mplsLdpEntityOptionalParameters' contains the 3813 value of 'frameRelaySessionParameters(3)' then 3814 there must be at least one corresponding entry 3815 in this table. 3817 NOTE: This RowStatus object should 3818 have the same value of the 'mplsLdpEntityRowStatus' 3819 related to this entry." 3820 ::= { mplsLdpEntityFrLREntry 4 } 3822 -- 3823 -- MPLS LDP Frame Relay Session Information 3824 -- 3826 mplsLdpFrameRelaySesTable OBJECT-TYPE 3827 SYNTAX SEQUENCE OF MplsLdpFrameRelaySesEntry 3828 MAX-ACCESS not-accessible 3829 STATUS current 3830 DESCRIPTION 3831 "A table of Frame Relay label range intersections 3832 between the LDP Entities and LDP Peers. 3833 Each row represents a single label range intersection. 3835 NOTE: this table cannot use the 'AUGMENTS' 3836 clause because there is not necessarily a one-to-one 3837 mapping between this table and the mplsLdpSessionTable." 3838 ::= { mplsLdpSessionObjects 11 } 3840 mplsLdpFrameRelaySesEntry OBJECT-TYPE 3841 SYNTAX MplsLdpFrameRelaySesEntry 3842 MAX-ACCESS not-accessible 3843 STATUS current 3844 DESCRIPTION 3845 "An entry in this table represents information on a 3846 single label range intersection between an 3847 LDP Entity and LDP Peer. 3849 The information contained in a row is read-only." 3850 INDEX { mplsLdpEntityLdpId, 3851 mplsLdpEntityIndex, 3852 mplsLdpPeerLdpId, 3853 mplsLdpFrSesMinDlci 3854 } 3855 ::= { mplsLdpFrameRelaySesTable 1 } 3857 MplsLdpFrameRelaySesEntry ::= SEQUENCE { 3858 mplsLdpFrSesMinDlci Integer32, 3859 mplsLdpFrSesMaxDlci Integer32, 3860 mplsLdpFrSesLength INTEGER 3861 } 3862 mplsLdpFrSesMinDlci OBJECT-TYPE 3863 SYNTAX Integer32(0..4194303) 3864 MAX-ACCESS not-accessible 3865 STATUS current 3866 DESCRIPTION 3867 "The lower bound of DLCIs which are supported." 3868 ::= { mplsLdpFrameRelaySesEntry 1 } 3870 mplsLdpFrSesMaxDlci OBJECT-TYPE 3871 SYNTAX Integer32 (0..4194303) 3872 MAX-ACCESS read-only 3873 STATUS current 3874 DESCRIPTION 3875 "The upper bound of DLCIs which are supported." 3876 ::= { mplsLdpFrameRelaySesEntry 2 } 3878 mplsLdpFrSesLength OBJECT-TYPE 3879 SYNTAX INTEGER { 3880 tenDlciBits(0), 3881 twentyThreeDlciBits(2) 3882 } 3883 MAX-ACCESS read-only 3884 STATUS current 3885 DESCRIPTION 3886 "This object specifies the DLCI bits." 3887 ::= { mplsLdpFrameRelaySesEntry 3 } 3889 --**************************************************************** 3890 -- Module Conformance Statement 3891 --**************************************************************** 3893 mplsLdpFrameRelayGroups 3894 OBJECT IDENTIFIER ::= { mplsLdpFrameRelayConformance 1 } 3896 mplsLdpFrameRelayCompliances 3897 OBJECT IDENTIFIER ::= { mplsLdpFrameRelayConformance 2 } 3899 -- 3900 -- Full Compliance 3901 -- 3903 mplsLdpFrModuleFullCompliance MODULE-COMPLIANCE 3904 STATUS current 3905 DESCRIPTION 3906 "The Module is implemented with support for 3907 read-create and read-write. In other words, 3908 both monitoring and configuration 3909 are available when using this MODULE-COMPLIANCE." 3911 MODULE -- this module 3912 MANDATORY-GROUPS { 3913 mplsLdpFrameRelayGroup 3914 } 3916 OBJECT mplsLdpEntityFrRowStatus 3917 SYNTAX RowStatus { active(1) } 3918 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 3919 DESCRIPTION 3920 "Support for createAndWait and notInService is not required." 3922 OBJECT mplsLdpEntityFrLRRowStatus 3923 SYNTAX RowStatus { active(1) } 3924 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 3925 DESCRIPTION 3926 "Support for createAndWait and notInService is not required." 3928 ::= { mplsLdpFrameRelayCompliances 1 } 3930 -- 3931 -- Read-Only Compliance 3932 -- 3934 mplsLdpFrModuleROCompliance MODULE-COMPLIANCE 3935 STATUS current 3936 DESCRIPTION 3937 "The Module is implemented with support for 3938 read-only. In other words, only monitoring 3939 is available by implementing this MODULE-COMPLIANCE." 3940 MODULE -- this module 3941 MANDATORY-GROUPS { 3942 mplsLdpFrameRelayGroup 3943 } 3945 OBJECT mplsLdpEntityFrIfIndexOrZero 3946 MIN-ACCESS read-only 3947 DESCRIPTION 3948 "Write access is not required." 3950 OBJECT mplsLdpEntityFrMergeCap 3951 MIN-ACCESS read-only 3952 DESCRIPTION 3953 "Write access is not required." 3955 OBJECT mplsLdpEntityFrLRComponents 3956 MIN-ACCESS read-only 3957 DESCRIPTION 3958 "Write access is not required." 3960 OBJECT mplsLdpEntityFrLength 3961 MIN-ACCESS read-only 3962 DESCRIPTION 3963 "Write access is not required." 3965 OBJECT mplsLdpEntityFrVcDirectionality 3966 MIN-ACCESS read-only 3967 DESCRIPTION 3968 "Write access is not required." 3970 OBJECT mplsLdpEntityFrStorageType 3971 MIN-ACCESS read-only 3972 DESCRIPTION 3973 "Write access is not required." 3975 OBJECT mplsLdpEntityFrRowStatus 3976 SYNTAX RowStatus { active(1) } 3977 MIN-ACCESS read-only 3978 DESCRIPTION 3979 "Write access is not required, and active is the 3980 only status that needs to be supported." 3982 OBJECT mplsLdpEntityFrLRMaxDlci 3983 MIN-ACCESS read-only 3984 DESCRIPTION 3985 "Write access is not required." 3987 OBJECT mplsLdpEntityFrLRStorageType 3988 MIN-ACCESS read-only 3989 DESCRIPTION 3990 "Write access is not required." 3992 OBJECT mplsLdpEntityFrLRRowStatus 3993 SYNTAX RowStatus { active(1) } 3994 MIN-ACCESS read-only 3995 DESCRIPTION 3996 "Write access is not required, and active is the 3997 only status that needs to be supported." 3998 ::= { mplsLdpFrameRelayCompliances 2 } 4000 -- 4001 -- units of conformance 4002 -- 4004 mplsLdpFrameRelayGroup OBJECT-GROUP 4005 OBJECTS { 4006 mplsLdpEntityFrIfIndexOrZero, 4007 mplsLdpEntityFrMergeCap, 4008 mplsLdpEntityFrLRComponents, 4009 mplsLdpEntityFrLength, 4010 mplsLdpEntityFrVcDirectionality, 4011 mplsLdpEntityFrStorageType, 4012 mplsLdpEntityFrRowStatus, 4013 mplsLdpEntityFrLRMaxDlci, 4014 mplsLdpEntityFrLRStorageType, 4015 mplsLdpEntityFrLRRowStatus, 4016 mplsLdpFrSesMaxDlci, 4017 mplsLdpFrSesLength 4018 } 4019 STATUS current 4020 DESCRIPTION 4021 "Objects that apply to all MPLS LDP implementations over 4022 Frame Relay." 4023 ::= { mplsLdpFrameRelayGroups 1 } 4025 END 4027 5. Revision History 4029 NOTE TO RFC-Editor: before publishing this document as an RFC, 4030 please remove this Revision History (change log) section. 4032 5.1. Changes from 4034 The following changes are from the IESG MIB review. 4036 Changed "Label Switch Router" to "Label Switching Router". 4038 Spelling errors fixed (unlabelled, atttempt, subsytem). 4040 Changed some of the enums to start at 1, instead of zero: 4041 mplsLdpPeerLoopDetectionForPV and mplsLdpEntityOperStatus. 4043 Added REFERENCE clauses. 4045 Added a timestamp object for mplsLdpSesState changes. 4047 Changed NMS to command generator as defined in RFC2571. 4049 Added a lastChange objects: mplsLdpEntityLastChange and 4050 mplsLdpPeerLastChange. 4052 Added TEXTUAL-CONVENTIONS for MplsLabelDistributionMethod and 4053 MplsRetentionMode. These TCs have been incorporated into draft- 4054 ietf-mpls-tc-mib-04.txt. 4056 Divided up the one MIB MODULE into 3 additional modules for a total 4057 of 4 MIB MODULES: 1) mplsLdpMIB, 2) mplsLdpGenericMIB which includes 4058 objects pertaining to Ethernet as the L2, 3) mplsLdpAtmMIB which 4059 includes objects pertaining to ATM as the L2, and 4) 4060 mplsLdpFrameRelayMIB which includes objects pertaining to Frame Relay 4061 as the L2. 4063 Also, reduced the number of objects by creating the mplsLdpLspTable 4064 and removing the Mapping tables. 4066 In section 3.1 changed "where each row in the table initiates" to 4067 "where each row in the table represents". 4069 Updated Reference Section and divided them into Normative vs. 4070 Informative. 4072 Removed the MplsGenAddress TC and used the INET-ADDRESS-MIB's 4073 InetAddress TC. Objects using this TC are: 4074 mplsLdpEntityTargetPeerAddr, mplsFecAddr, and 4075 mplsLdpSesPeerNextHopAddr and are noted in the conformance statements 4076 supporting: unknown(0), ipv4(1), and ipv6(2). 4078 Removed AddressFamilyNumbers TC and used InetAddressType TC from the 4079 INET-ADDRESS-MIB. One of the MIB compilers as a warning because 4080 apparently one is expected to use InetAddressType and InetAddress 4081 together (although, think this restriction is too restrictive). Also, 4082 removed the reference for the Address Family Numbers MIB. 4084 Changed the name TargPeer to TargetPeer. 4086 Removed the Enable/Disable trap objects: 4087 mplsLdpEntityPVLMisTrapEnable, and mplsLdpSesUpDownTrapEnable. RFC 4088 2573 should be used to eable/disable traps. 4090 Removed the import for "transmission" and instead, imported "mplsMIB 4091 from the MPLS-TC-MIB". 4093 Changed mplsLdpEntityPVL to mplsLdpEntityPathVectorLimit and updated 4094 the DESCRIPTION clause. Also, the PVL abbreviation was expanded to 4095 PathVectorLimit for other objects. 4097 Combined the objects: mplsLdpPeerLoopDectionForPV and mplsLdpPeerPVL 4098 into one object: mplsLdpPeerPathVectorLimit and updated the 4099 DESCRIPTION clause. 4101 mplsLdpEntityTcpDscPort uses InetPortNumber TC from the INET- 4102 ADDRESS-MIB. Likewise, mplsLdpEntityUdpDscPort uses the 4103 InetPortNumber TC from the INET-ADDRESS-MIB. Also a REFERENCE clause 4104 was added. 4106 The mplsLdpEntityMaxPduLength object has the SYNTAX range changed to 4107 start at 256. Also the DESCRIPTION clause was updated. 4109 The mplsLdpSesMaxPduLen object's name was changed to 4110 mplsLdpSesMaxPduLength and a UNITS clause was added, and the 4111 DESCRIPTION clause was updated. This object is related to the 4112 mplsLdpEntityMaxPduLength object. 4114 The mplsLdpEntityKeepAliveHoldTimer and mplsLdpEntityHelloHoldTimer 4115 DESCRIPTION clause was changed from "The two octet value" to "The 4116 16-bit integer value". 4118 The mplsLdpEntityHelloHoldTimer object's DESCRIPTION clause was 4119 updated. 4121 A range of Integer32(0..100) was added to the SYNTAX clause of the 4122 mplsLdpEntityInitSesThreshold object. Also, the DESCRIPTION clause 4123 of this object was updated. 4125 The mplsLdpEntityOptionalParameters object was renamed to 4126 mplsLdpEntityLabelType. 4128 Updated the mplsLdpEntityAdminStatus and mplsLdpEntityRowStatus 4129 objects. RowStatus now reflects the status of the row, and Admin 4130 status controls enabling/disabling the entry. 4132 Updated the DESCRIPTION clauses for the objects in the 4133 mplsLdpEntityStatsTable to refer to the 4134 mplsLdpEntityDiscontinuityTime object. 4136 Changed StorType to StorageType. 4138 5.2. Changes from 4140 There were three types of changes: the first change was that all the 4141 MPLS Textual Conventions from this MIB, the LSR and MPLS-TE MIBs were 4142 moved into a new document [MPLSTCMIB], "draft-ietf-mpls-tc-mib- 4143 00.txt". The Textual Conventions are now IMPORTED from [MPLSTCMIB]. 4144 The second type of change was updates based on comments from the 4145 IESG. These changes will be discussed below. The third type of 4146 changes were based on minor editorial changes from the co-authors. 4148 The "Introduction" and "Structure of the MIB" sections were reworded 4149 since they were repetitive. 4151 The "Overview" was rearranged. 4153 References were added to "The LDP Entity ATM Objects" and "The LDP 4154 Entity Frame Relay Objects" Sections. 4156 The Working Group mailing list and Chairs were added to the CONTACT- 4157 INFO. 4159 Updated the DESCRIPTION clause for the "mplsLdpEntityLdpId" object. 4161 Updated the mplsLdpEntityProtocolVersion to include a range 4162 (1..65535). 4164 Updated the "References" Section. 4166 Running the MIB through the smilint MIB compiler showed that some 4167 object names were longer than 32 characters, these were shortened to 4168 32 characters or fewer. 4170 The following changes were from the co-authors. 4172 Other minor editorial changes such as fixing typographical errors, 4173 and removing MIB comments which are no longer meaningful. 4175 Page 17 (also page 46) the description was enhanced to describe the 4176 version field in the LDP header from RFC3036. 4178 Removed WellKnown from the tcp and upd port names. It's the ports 4179 that get set, and the default value is the well known (actually the 4180 registered) port number. 4182 mplsLdpEntityInitSesTrapEnable object is useless and was removed 4183 since setting mplsLdpEntityInitSesThreshold=0 acheives the same 4184 thing. Also removed it from the descriptive text in section 3. 4186 Page 47, mplsLdpSessionDiscontinuityTime The initial value of this 4187 was changed to be sysUpTime instead of zero. sysUpTime for when the 4188 session starts is more meaningful and was added to the Session 4189 Up/Down Traps also. Also, added the Session specific stats to the 4190 up/down traps. 4192 5.3. Changes from 4194 All changes were from the second last call which took place Thursday, 4195 July 20th, until Thursday, July 27th, 2000 and are described in the 4196 remainder of this section. 4198 Remove the reference to the MPLS framework document. 4200 Add an mplsFecIndexNext type of object. 4202 Change the conformance of the FEC table objects to be part of the 4203 mplsLdpGeneralGroup. 4205 The mplsLdpEntityConfGenericTable is no longer needed because the 4206 functionality has been absorbed by the 4207 mplsLdpEntityConfGenericLabelRangeTable. The 4208 mplsLdpEntityConfGenericTable has been removed and the front section 4209 was updated accordingly. 4211 Other editorial issues, updating references, typos and so forth. 4213 5.4. Changes from 4215 The majority of changes in this revision are based on Last Call 4216 comments which were received during the last call from Thursday, 4217 March 9, 2000 to Friday, March 17, 2000, or slightly thereafter. 4218 Also, changes were made to agree with the latest specifications. 4219 These changes are described in this section. 4221 Changes due to draft-ietf-mpls-ldp-07.txt and draft-ietf-mpls-ldp- 4222 08.txt. Specifically, removing references to IPv4/IP and using router 4223 id, as appropriate. 4225 Removed vpMerge and vpAndVcMerge choices from the object, 4226 mplsLdpEntityAtmMergeCap. VP Merge is not described in [RFC3036]. 4228 The LIB Table was removed and replaced by mapping tables to map LDP 4229 LSPs created by LDP sessions to the mplsInSegment, mplsOutSegment and 4230 mplsXC tables in the LSR MIB. The conformance section was updated 4231 to include a Mapping Group which is to be implemented iff these LSR 4232 MIB tables (mplsInSegmentTable, mplsOutSegmentTable and mplsXCTable) 4233 are implemented. 4235 The front section was updated to include information on the Generic 4236 label table. 4238 Added more in the front section on on Row 4239 Creation/adminStatus/OperStatus in the LDP Entity and related tables. 4241 Added a generic label range table. NOTE: there is NO corresponding 4242 LDP message which relates to the information in this table, however, 4243 this table does provide a way for a user to 'reserve' a generic label 4244 range. 4246 A new TEXTUAL-CONVENTION, MplsAtmVcIdentifier was added. This TC has 4247 the same upper bounds as AtmVcIdentifier (from rfc2514) except that 4248 the lower bound is 32 (and not 0). The lower bound is 32 since this 4249 value is specified by [RFC3035]. 4251 Removed the scalar object mplsLsrLabelRetentionMode and added 4252 mplsLdpEntityLabelRetentionMode. The change was made to allow 4253 configuring the retention mode on a per LDP Entity basis, as opposed 4254 for the entire LSR. 4256 Typo in section 3.5.2 was fixed. 4258 Typo in the mplsLdpSessionUp notification description was fixed. 4260 Section 'LDP Notifications' was expanded to cover both the 4261 'mplsLdpSessionUp' and 'mplsLdpSessionDown' traps. Also, the objects 4262 which enable and disable these traps have been described in this 4263 Section: 4265 The 'mplsLdpEntityHopCountLoopDetection' object and the 4266 'mplsLdpEntityHopCount' object have been combined into the new 4267 object, 'mplsLdpEntityHopCountLimit'. 4269 MplsLabel has been updated to reflect the VPI value of 12 bits and 4270 not 8. 4272 Added DEFVAL clause to the 'mplsLdpEntityWellKnownDiscoveryPort' 4273 object. The default value is 646. 4275 Added UNITS and DEFVAL clauses to the 'mplsLdpEntityMaxPduLength' 4276 object. The default value is 4096 and the units is octets. 4278 Added DEFVAL clause to 'mplsLdpEntityProtocolVersion' object. The 4279 default value is 1. 4281 Added DEFVAL clause to 'mplsLdpEntityKeepAliveHoldTimer' of 40 4282 seconds. 4284 Added DEFVAL clause to 'mplsLdpEntityInitSesThreshold' object. The 4285 default value is 8. 4287 The mplsLdpEntityWellKnownDiscoveryPort was changed into two objects, 4288 one for TCP and one for UDP. The names are 4290 Typo in the description for the 4292 The mplsLdpEntityPeerTable was (re-)named mplsLdpPeerTable. The 4293 mplsLdpSessionTable now AUGMENTs the mplsLdpPeerTable in order to 4294 show that these two tables are related. There has been wording added 4295 to the mplsLdpSessionEntry description and to the description for the 4296 mplsLdpPeerTable. 4298 5.5. Changes from 4300 Editorial changes, fixing typo's, fixing wrapping lines, etc. 4302 Updated references for latest drafts, and added [RFC3032] and 4303 [RFC3034] to Reference Section. 4305 Added to the Acknowledgements Section. 4307 Changed the SYNTAX and DESCRIPTION of the 4308 'mplsLdpLsrLoopDetectionCapable' object, so that it will also support 4309 the loop detection by hop count. 4311 Combined the 'mplsLdpEntityLoopDetectionForPV' and 'mplsLdpEntityPVL' 4312 objects. The functionality of the 'mplsLdpEntityLoopDectionForPV' is 4313 now denoted by the value of 0 (zero) in the 'mplsLdpEntityPVL' 4314 object. This results in one less object 4315 'mplsLdpEntityLoopDectionForPV' but does not sacrifice functionality. 4317 Changed 'mplsLdpLibLabelType' into two objects: 4318 'mplsLdpLibInLabelType' and differ from the egress label type. The 4319 MIB now reflects this. 4321 The following items were changed as a result of the Frame Relay Forum 4322 dropping support for 17-bit DLCIs: the MplsLabel TC description has 4323 been modified, and other Frame Relay Object descriptions were also 4324 modified (as specified in this section). 4326 The MplsLabel TC was also modified and reference 3. was added to the 4327 REFERENCE Clause. 4329 MplsLdpLabelTypes TC was modified to use an enum. 4331 InterfaceIndex support was added to the Entity information. This was 4332 specifically requested by several members of the working group. An 4333 additional table, mplsLdpEntityConfGenericTable as a way to configure 4334 Generic Labels, and an object, 'mplsLdpConfGenericIfIndexOrZero was 4335 added to map the InterfaceIndex used by Generic Labels. Objects were 4336 also added to the 'mplsLdpEntityAtmParmsTable' and the and 4337 'mplsLdpEntityFrIfIndex', respectively. 4339 Changed the name of the 'mplsLdpEntityMtu' object to be 4340 'mplsLdpEntityMaxPduLength' which is more consistent with the LDP 4341 Specification. Also, the description and SYNTAX were changed. 4343 Changed the SYNTAX of the 'mplsLdpSessionMaxPduLength' to unsigned32 4344 and changed the Range from (0..65535) to (1..65535). 4346 Added and improved the front section discussion on SNMP 4347 Notifications. 4349 Also, modified the DESCRIPTION clause of the 4351 Added objects to enable/disable the sending of traps: 4353 Added an object to enable/disable sending traps for Sessions changing 4354 from Up to Down, or Down to Up. 4356 Added notifications to generate traps from session changing from Up 4357 to Down, or Down to up. 4359 Added a StorageType object to the Entity and associated tables which 4360 are configurable. 4362 Added a Discontinuity Time object to the Entity Table, 4364 Added discussion on row creation in the Entity and other associated 4365 Entity tables. This is a new Section in the Front part of the 4366 document called: 4368 Removed the 'mplsLdpEntityControlMethod'. 4370 Made 'mplsLdpFecLspId' as part of the INDEX for the FEC table. This 4371 is to allow FECs to map to multiple LSPs. Also add a RowPointer to a 4372 row in the Session Table. 4374 Added an operation status object, 'mplsLdpLspOperStatus' and a last 4375 Change object, 'mplsLdpLspLastChangeto the LIB Table. This will be 4376 used to detect whether an LSP has changed its status. 4378 Changed the name of the mplsLdpPeerTable to the 4379 mplsLdpEntityPeerTable. This table contains information relevant to 4380 Peers which are known to specific Entities. The indexing of this 4381 table has also changed to include the Row in the Entity Table that 4382 this Peer is known by. The mplsLdpHelloAdjacencyTable and the 4383 mplsLdpSessionTable have been moved under this table. Since Hello 4384 Adjacencies are related to Entity-Peer information and Sessions are 4385 related to Entity-Peer information this was seen as a comprehensive 4386 and coherent modelling. Associated descriptions in the front section 4387 and in the tables have been changed to reflect this change. 4389 Moved the 'mplsLdpConfFrLen' object from the 4390 'mplsLdpEntityConfFrLabelRangeTable' to the 4391 'mplsLdpEntityFrameRelayParmsTable' since the Frame Relay 4392 interface/port can only use one header length at a time, i.e. a 4393 specific FR interface supports one address length for all VCs on that 4394 interface. Also, changed the object so that it only supports 10 and 4395 23 bit DLCI lengths. (The 17 bit length was dropped by the Frame 4396 Relay Forum and thus, is no longer required.) The name of this 4397 object was changed from 'mplsLdpConfFrLen' to 'mplsLdpEntityFrLen' to 4398 fit in with the 'mplsLdpEntityFrameRelayParmsTable'. 4400 Removed the seventeenDlciBits(1) value from the mplsLdpFrSessionLen 4401 object. (The 17 bit length was dropped by the Frame Relay Forum and 4402 thus, is no longer required.) 4404 Corrected the range of the 'mplsLdpEntityIndexNext' object to include 4405 0 (zero). 4407 5.6. Changes from 4409 Reworded the description of the mplsLdpAtmSessionTable to clarify 4410 that one or MORE label range intersection(s) is/are represented in 4411 this table. 4413 Reworded the description of the mplsLdpFrameRelaySessionTable to 4414 clarify that one or MORE label range intersection(s) is/are 4415 represented in this table. 4417 Added a new index, mplsLdpSessionPeerIndex, to the 4418 mplsLdpSessionPeerAddressTable. This new index uniquely identifies 4419 the entry within a given session. (Since adding 4420 mplsLdpSessionPeerNextHopAddressType, 4421 mplsLdpSessionPeerNextHopAddress to the INDEX clause of the 4422 mplsLdpSessionPeerAddressTable leaves a table with only indices and 4423 no objects, the work around was to add a new index which uniquely 4424 differentiates an entry within a given session.) 4426 Quite a few changes to the mplsLdpPeerTable. First, removed the 4427 mplsLdpPeerIndex from the mplsLdpPeerTable and other tables. This 4428 index served no purpose, so was removed. Second, removed the 4429 objects: mplsLdpPeerInternetworkAddrType, and 4430 mplsLdpPeerInternetworkAddr. Third, reworded the description of this 4431 table to include information which is known during Session 4432 Intialization attempts, the specific information has to do with Loop 4433 Dection based on Path Vectors. Since Section 3.5.3 of the LDP Spec 4434 when describing the PVLim says: "Although knowledge of a peer's path 4435 vector limit will not change an LSR's behavior, it does enable the 4436 LSR to alert an operator to a possible misconfiguration." and the 4437 object mplsLdpPeerPVL is sent as a varbind in the mplsLdpPVLMismatch 4438 notification. 4440 Removed the mplsLdpPeerIndex from the mplsLdpHelloAdjacencyTable. 4442 Removed the "IANA Address Family Numbers" MIB section. 4444 Updated the boiler.me from the ops web page dated Weds., Dec 22, 4445 1999. 4447 Updated the Security Section from the ops web page. 4449 Added the following objects to the mplsLdpEntityTable: 4450 mplsLdpEntityControlMethod, mplsLdpEntityLoopDectionForPV, and 4451 mplsLdpEntityPathVectorLimit. 4453 Removed mplsLdpSessionLabelAdvertisement, 4454 mplsLdpSessionLoopDetectionForPV, and mplsLdpSessionPathVectorLimit 4455 from the mplsLdpSessionTable. 4457 Changed the mplsLdpPathVectorLimitMismatch Notification to send 4458 mplsLdpEntityPathVectorLimit (instead of 4459 mplsLdpSessionPathVectorLimit). 4461 Copied the MplsLabel TC from draft-ietf-mpls-lsr-mib-00.txt and 4462 replaced the MplsLdpGenAddr for mplsLdpLibInLabel and 4463 mpslLdpLibOutLabel with MplsLabel. 4465 The mplsLdpSessionIndex was removed throughout the MIB. This was 4466 replaced by the object mplsLdpSessionDiscontinuityTime. The 4467 motivation was to reduce the number of indices. 4469 The descriptions for the objects in the mplsLdpSessionStatsTable, 4470 mplsLdpSessionStatsUnknownMessageTypeErrors and 4471 mplsLdpSessionStatsUnknownTlvErrors, have been updated to include a 4472 reference to the mplsLdpSessionDiscontinuityTime object. 4474 5.7. Changes from 4476 Added Scalar Objects: mplsLdpLsrLoopDetectionPresent, and 4477 mplsLdpEntityIndexNext. 4479 Added the following objects to the mplsLdpEntityTable: 4480 mplsLdpEntityProtocolVersion, mplsLdpEntityAdminStatus, 4481 mplsLdpEntityOperStatus, mplsLdpEntityTargetedPeer, 4482 mplsLdpEntityTargetedPeerAddrType, mplsLdpEntityTargetedPeerAddr, and 4483 mplsLdpEntityHelloHoldTimer. 4485 Changed the description of the mplsLdpEntityAtmParmsTable and added 4486 the following objects to this table: 4487 mplsLdpEntityAtmLsrConnectivity, mplsLdpEntityDefaultControlVpi, 4488 mplsLdpEntityDefaultControlVci, mplsLdpEntityUnlabTrafVpi, and 4489 mplsLdpEntityUnlabTrafVci. NOTE: the last four objects were in 4490 Version 01 of the MIB but were mistakenly omitted from Version 02. 4491 Now, they are back. 4493 Changed the indexing of the mplsLdpEntityConfAtmLabelRangeTable to 4494 include the minimum VPI/VCI. This is to ensure that indices in this 4495 table are unique. 4497 Changed the indexing of the mplsLdpEntityConfFrLabelRangeTable, to 4498 include the minimum DLCI value. This is to ensure that indices in 4499 this table are unique. 4501 Added [RFC3036] to Reference Section. 4503 5.8. Changes from 4505 The MIB was updated to correspond to draft-ietf-mpls-ldp-06.txt of 4506 the LDP Specification [RFC3036]. 4508 The front section was updated. 4510 The MIB was made to be less ATM-centric. Essentially, the ATM 4511 specific objects where removed from the tables and placed in ATM 4512 specific Tables. A type was added to the base tables and a row is to 4513 be created in the ATM/FR/etc. type table. Apropos compliance 4514 statements were added to reflect the separation of ATM and Frame 4515 Relay objects into their respective tables. 4517 Objects for Loop Detection were removed from describing the LDP 4518 implementation (i.e. the scalars were removed) and Loop Dection 4519 objects were added to the Session Table. (Although as the LDP 4520 Specification indicates loop detection should be for an LSR within a 4521 domain.) 4523 The following tables were added: mplsLdpEntityAtmParmsTable, 4524 mplsLdpEntityConfAtmLabelRangeTable, mplsLdpFrameRelayParmsTable, 4525 mplsLdpConfFrLabelRangeTable, mplsLdpAtmSessionTable, 4526 mpslLdpFrameRelaySessionTable, mplsLdpSessionPeerAddressTable, 4527 mplsLdpLibTable, and the mplsLdpFecTable. 4529 The following notifications were added: notification for Session 4530 removal. 4532 The following objects were removed from the Session Table: 4533 mplsLdpSessionRole was removed (this can be determined by comparing 4534 LSR Ids and does not need to be explicitely in the MIB.) ATM 4535 specific objects (mplsLdpSessionAtmLabelRangeLowerBoundVpi 4536 mplsLdpSessionAtmLabelRangeLowerBoundVci, 4537 mplsLdpSessionAtmLabelRangeUpperBoundVpi 4538 mplsLdpSessionAtmLabelRangeUpperBoundVci) were removed and put into a 4539 separate table. Frame Relay objects were added in a separate table. 4541 Hello Adjacency Table was updated. 4543 The objects, mplsLdpSessionRejectedParamErrors, 4544 mplsLdpSessionRejectedNoHelloErrors, mplsLdpBadLdpIdentifierErrors, 4545 mplsLdpBadPduLengthErrors, mplsLdpBadMessageLengthErrors, 4546 mplsLdpBadTlvLengthErrors, mplsLdpMalformedTlvValueErrors, 4547 mplsLdpKeepAliveTimerExpiredErrors, mplsLdpShutdownNotifReceived, and 4548 mplsLdpShutdownNotifSent were added to the mplsLdpEntityStatsTable. 4550 The mplsLdpSessionStatsTable was added to count statics based on a 4551 per Session basis. 4553 The mplLdpPeerConfAtmLabelRangeTable has been removed. There is no 4554 need to configure information for a Peer. All information for a peer 4555 is learned, thus peer information is read-only. 4557 (Editorial) References were updated to reflect the documents which 4558 this version was based on. 4560 5.9. Changes from 4562 Textual conventions were added for the LSR Identifier and the LDP 4563 Identifier. 4565 Top-level mib structure was added. The LDP MIB falls under a proposed 4566 hierarchy of mpls.mplsProtocols. 4568 The mib hierarchy within the LDP MIB was also changed. A new branch, 4569 under mpls.mplsProtocols.mplsLdpMIB.mplsLdpObjects was added. This 4570 branch is mplsLdpLsrObjects. Currently, this contains several new 4571 scalar objects: mplsLdpLsrID, mplsLdpLsrLoopDetectionPresent, 4572 mplsLdpLsrLoopDetectinAdminStatus, mplsLdpLsrPathVectorLimit, 4573 mplsLdpLsrHopCountLimit, mplsLdpLsrLoopPreventionPresent, 4574 mplsLdpLsrLoopPreventionAdminStatus, and 4575 mplsLdpLsrLabelRetentionMode. 4577 mplsLdpEntityTable is now indexed by mplsLdpEntityIdentifier, which 4578 is the LDP Identifier used in Session establishment. 4579 mplsLdpEntityLoopDetection and mplsLdpEntityLoopPrevention objects 4580 were removed from this table. 4582 The following objects were added to the mplsLdpEntityTable: 4583 mplsLdpEntityLabelSpaceType, mplsLdpEntityUnlabTrafVpi, 4584 mplsLdpEntityUnlabTrafVci, mplsLdpEntityMergeCapability, 4585 mplsLdpEntityVcDirectionality, and 4586 mplsLdpEntityLabelDistributionMethod. 4588 The following objects were added to the mplsLdpPeerEntityTable: 4589 mplsLdpPeerLabelDistributionMethod. 4591 The following object was removed from the mplsLdpEntityStatsTable: 4592 mplsLdpEntityEstablishedSessions. 4594 References were added and revised. 4596 6. Acknowledgments 4598 The authors would like to thank the following people: Leigh 4599 McLellan, Geetha Brown, Geping Chen and Charlan Zhou from Nortel 4600 Networks, and Zoltan Takacs and Bo Augustsson from Ericsson. Also, 4601 some members of the working group were very helpful with comments and 4602 corrections to the MIB; the authors would like to thank Adrian Farrel 4603 of Movaz Networks, and Alan Kullberg from NetPlane Systems. 4605 7. Normative References 4607 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 4608 Requirement Levels", BCP 14, RFC 2119, Harvard University, 4609 March 1997 4611 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 4612 for Describing SNMP Management Frameworks", RFC 2571, April 4613 1999. 4615 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4616 Rose, M., and S. Waldbusser, "Structure of Management 4617 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 4618 1999. 4620 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4621 Rose, M., and S. Waldbusser, "Textual Conventions for 4622 SMIv2", STD 58, RFC 2579, April 1999. 4624 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4625 Rose, M., and S. Waldbusser, "Conformance Statements for 4626 SMIv2", STD 58, RFC 2580, April 1999. 4628 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 4629 "Transport Mappings for Version 2 of the Simple Network 4630 Management Protocol (SNMPv2)", RFC 1906, January 1996. 4632 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 4633 Processing and Dispatching for the Simple Network Management 4634 Protocol (SNMP)", RFC 2572, April 1999. 4636 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 4637 (USM) for version 3 of the Simple Network Management 4638 Protocol (SNMPv3)", RFC 2574, April 1999. 4640 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 4641 "Protocol Operations for Version 2 of the Simple Network 4642 Management Protocol (SNMPv2)", RFC 1905, January 1996. 4644 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 4645 RFC 2573, April 1999. 4647 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 4648 Access Control Model (VACM) for the Simple Network 4649 Management Protocol (SNMP)", RFC 2575, April 1999. 4651 [RFC3036] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and B. 4652 Thomas, "LDP Specification", RFC 3036, January 2001. 4654 [RFC3291] Daniele, M., Haberman, B., Routhier, S. and J. 4655 Schoenwaelder, "Textual Coventions for Internet Network 4656 Addresses", RFC 3291, May 2002. 4658 [LSRMIB] Srinivansan, C., Viswanathan, A., and T. Nadeau "MPLS Label 4659 Switching Router Management Information Base Using SMIv2", 4660 draft-ietf-mpls-lsr-mib-08.txt, January 2002. 4662 [MPLSTCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C., Viswanathan, A. 4663 and H. Sjostrand, "Definitions of Textual Conventions for 4664 Multiprotocol Label Switching Management", draft-ietf-mpls- 4665 tc-mib-04.txt, October 2002. 4667 8. Informative References 4669 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 4670 of Management Information for TCP/IP-based Internets", STD 4671 16, RFC 1155, May 1990. 4673 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 4674 16, RFC 1212, March 1991. 4676 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 4677 SNMP", RFC 1215, March 1991. 4679 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 4680 Network Management Protocol", STD 15, RFC 1157, May 1990. 4682 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 4683 "Introduction to Community-based SNMPv2", RFC 1901, January 4684 1996. 4686 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 4687 "Introduction to Version 3 of the Internet-standard Network 4688 Management Framework", RFC 2570, April 1999. 4690 [RFC3031] Rosen, E., Viswananthan, A., and R. Callon, "Multiprotocol 4691 Label Switching Architecture", RFC 3031, January 2001. 4693 [RFC2514] Noto, M., E. Spiegel, K. Tesink, editors, "Definition of 4694 Textual Conventions and OBJECT-IDENTITIES for ATM 4695 Management", RFC 2514, February 1999. 4697 [RFC2863] McCloghrie, K., F. Kastenholz, "The Interfaces Group MIB 4698 using SMIv2", RFC 2863, June 2000. 4700 [RFC2515] Tesink, K. (ed.) "Definitions of Managed Objects for ATM 4701 Management", RFC 2515, February 1999. 4703 [RFC3035] Davie, B., Lawrence, J., McCloghrie, K., Rosen, E., Swallow, 4704 G., Rekhter, Y. and P. Doolan, "MPLS using LDP and ATM VC 4705 Switching", RFC 3035, January 2001. 4707 [RFC2684] Grossman, D., and J. Heinanen, "Multiprotocol Encapsulation 4708 over ATM Adaptation Layer 5", RFC 2684, September 1999. 4710 [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., Farinacci, 4711 D., Li, T. and A. Conta, "MPLS Label Stack Encoding", RFC 4712 3032, January 2001. 4714 [RFC3034] Conta, A., Doolan, P., and A. Malis, "Use of Label Switching 4715 on Frame Relay Networks Specification", RFC 3034, January 4716 2001. 4718 [RFC3215] Boscher, C., Cheval, P., Wu L. and E. Gray, "LDP State 4719 Machine", RFC 3215, January 2002. 4721 [RFC3037] Thomas, B. and E. Gray, "LDP Applicability", RFC 3037, 4722 January 2001. 4724 9. Security Considerations 4726 There are a number of management objects defined in this MIB that 4727 have a MAX-ACCESS clause of read-write and/or read-create. Such 4728 objects may be considered sensitive or vulnerable in some network 4729 environments. The support for SET operations in a non-secure 4730 environment without proper protection can have a negative effect on 4731 network operations. 4733 There are a number of managed objects in this MIB that may contain 4734 sensitive information. These are contained in the mplsLdpEntityTable. 4735 The objects contained in this table are responsible for setting up or 4736 tearing down LSPs. 4738 It is thus important to control even GET access to these objects and 4739 possibly to even encrypt the values of these object when sending them 4740 over the network via SNMP. Not all versions of SNMP provide features 4741 for such a secure environment. 4743 SNMPv1 by itself is not a secure environment. Even if the network 4744 itself is secure (for example by using IPSec), even then, there is no 4745 control as to who on the secure network is allowed to access and 4746 GET/SET (read/change/create/delete) the objects in this MIB. 4748 It is recommended that the implementers consider the security 4749 features as provided by the SNMPv3 framework. Specifically, the use 4750 of the User-based Security Model RFC 2574 [RFC2574] and the View- 4751 based Access Control Model RFC 2575 [RFC2575] is recommended. 4753 It is then a customer/user responsibility to ensure that the SNMP 4754 entity giving access to an instance of this MIB, is properly 4755 configured to give access to the objects only to those principals 4756 (users) that have legitimate rights to indeed GET or SET 4757 (change/create/delete) them. 4759 10. Authors' Addresses 4761 James V. Luciani 4762 Crescent Networks 4763 900 Chelmsford Street 4764 Lowell, MA 01851 4765 USA 4766 Email: jluciani@crescentnetworks.com 4768 Hans Sjostrand 4769 ipUnplugged 4770 P.O. Box 101 60 4771 S-121 28 Stockholm, Sweden 4772 Phone: +46 8 725 5930 4773 Email: hans@ipunplugged.com 4775 Joan Cucchiara 4776 Crescent Networks 4777 900 Chelmsford Street 4778 Lowell, MA 01851 4779 USA 4780 Phone: +1 978 275-3183 4781 Email: jcucchiara@crescentnetworks.com 4783 11. Full Copyright Statement 4785 Copyright (C) The Internet Society (2002). All Rights Reserved. 4787 This document and translations of it may be copied and furnished to 4788 others, and derivative works that comment on or otherwise explain it 4789 or assist in its implementation may be prepared, copied, published 4790 and distributed, in whole or in part, without restriction of any 4791 kind, provided that the above copyright notice and this paragraph are 4792 included on all such copies and derivative works. However, this 4793 document itself may not be modified in any way, such as by removing 4794 the copyright notice or references to the Internet Society or other 4795 Internet organizations, except as needed for the purpose of 4796 developing Internet standards in which case the procedures for 4797 copyrights defined in the Internet Standards process must be 4798 followed, or as required to translate it into languages other than 4799 English. 4801 The limited permissions granted above are perpetual and will not be 4802 revoked by the Internet Society or its successors or assigns. 4804 This document and the information contained herein is provided on an 4805 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 4806 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 4807 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 4808 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 4809 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.