idnits 2.17.1 draft-ietf-mpls-ldp-mib-08.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.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 3 instances of too long lines in the document, the longest one being 2 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 3551 has weird spacing: '... (Since addin...' == Line 3941 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 (August 2001) is 8290 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: '17' is defined on line 3800, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 3807, but no explicit reference was found in the text == Unused Reference: '20' is defined on line 3810, but no explicit reference was found in the text == Unused Reference: '22' is defined on line 3816, but no explicit reference was found in the text == Unused Reference: '24' is defined on line 3823, but no explicit reference was found in the text == Unused Reference: '25' is defined on line 3827, but no explicit reference was found in the text == Unused Reference: '26' is defined on line 3832, but no explicit reference was found in the text == Unused Reference: '28' is defined on line 3839, but no explicit reference was found in the text == Unused Reference: '29' is defined on line 3842, but no explicit reference was found in the text == Unused Reference: '33' is defined on line 3856, but no explicit reference was found in the text == Unused Reference: '34' is defined on line 3859, but no explicit reference was found in the text == Unused Reference: '35' is defined on line 3862, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** 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 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2434 (ref. '17') (Obsoleted by RFC 5226) ** Obsolete normative reference: RFC 3036 (ref. '18') (Obsoleted by RFC 5036) == Outdated reference: A later version (-06) exists of draft-ietf-mpls-cr-ldp-05 == Outdated reference: A later version (-14) exists of draft-ietf-mpls-lsr-mib-07 -- Possible downref: Non-RFC (?) normative reference: ref. '25' ** Downref: Normative reference to an Informational draft: draft-ietf-mpls-ldp-state (ref. '33') ** Downref: Normative reference to an Informational RFC: RFC 3037 (ref. '34') ** Obsolete normative reference: RFC 2851 (ref. '35') (Obsoleted by RFC 3291) -- Possible downref: Non-RFC (?) normative reference: ref. '36' Summary: 21 errors (**), 0 flaws (~~), 18 warnings (==), 4 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 February 2002 H. Sjostrand 4 IP Unplugged 5 J. Luciani 6 Crescent Networks 7 August 2001 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 (2001). 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 ......................................... 5 55 3.4 Differences from the LDP Specification ..................... 5 56 3.5 Discussion of MIB Groups ................................... 6 57 3.6 The MPLS LDP General Group ................................. 6 58 3.6.1 The LDP Entity Table ..................................... 6 59 3.6.2 Changing Values After Session Establishment .............. 7 60 3.6.3 mplsLdpEntityAdminStatus and mplsLdpEntityRowStatus ...... 7 61 3.6.4 The LDP Entity Generic Objects ........................... 8 62 3.6.5 The LDP Entity ATM Objects ............................... 8 63 3.6.6 The LDP Entity Frame Relay Objects ....................... 8 64 3.6.7 The LDP Entity Statistics Table .......................... 8 65 3.6.8 The LDP Peer Table ....................................... 9 66 3.6.9 The LDP Hello Adjacencies Table .......................... 9 67 3.6.10 The LDP Session Table ................................... 9 68 3.6.11 The LDP ATM Session Table ............................... 9 69 3.6.12 The LDP Frame Relay Session Table ....................... 9 70 3.6.13 The LDP Session Statistics Table ........................ 10 71 3.6.14 The LDP Session Peer Address Table ...................... 10 72 3.6.15 The Mapping Tables ...................................... 10 73 3.6.15.1 The LDP Session In Label Map Table .................... 11 74 3.6.15.2 The LDP Session Out Label Map Table ................... 11 75 3.6.15.3 The LDP Session XC Map Table .......................... 11 76 3.6.16 The FEC Table ........................................... 12 77 3.7 The LDP Notifications Group ................................ 12 78 3.7.1 LDP Notifications ........................................ 12 79 4 MPLS Label Distribution Protocol MIB Definitions ............. 13 80 5 Revision History ............................................. 69 81 5.1 Changes from .............. 69 82 5.2 Changes from .............. 70 83 5.3 Changes from .............. 70 84 5.4 Changes from .............. 72 85 5.5 Changes from .............. 74 86 5.6 Changes from .............. 75 87 5.7 Changes from .............. 76 88 5.8 Changes from .............. 77 89 6 Acknowledgments .............................................. 78 90 7 References ................................................... 79 91 8 Security Considerations ...................................... 81 92 9 Authors' Addresses ........................................... 82 93 10 Full Copyright Statement .................................... 83 95 1. Introduction 97 This document defines a MIB for the Label Distribution Protocol 98 (LDP). The Label Distribution Protocol (LDP) [18] is one of the MPLS 99 protocols. This MIB allows a user to configure LDP sessions as well 100 as monitor all LDP sessions on the device. This MIB also supports 101 configuration for LDP using IP, ATM or FrameRelay media. 103 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 104 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 105 document are to be interpreted as described in RFC 2119 [21]. 107 2. The SNMP Management Framework 109 The SNMP Management Framework presently consists of five major 110 components: 112 o An overall architecture, described in RFC 2571 [RFC2571]. 114 o Mechanisms for describing and naming objects and events for the 115 purpose of management. The first version of this Structure of 116 Management Information (SMI) is called SMIv1 and described in 117 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 118 1215 [RFC1215]. The second version, called SMIv2, is described 119 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 120 STD 58, RFC 2580 [RFC2580]. 122 o Message protocols for transferring management information. The 123 first version of the SNMP message protocol is called SNMPv1 and 124 described in STD 15, RFC 1157 [RFC1157]. A second version of 125 the SNMP message protocol, which is not an Internet standards 126 track protocol, is called SNMPv2c and described in RFC 1901 127 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 128 message protocol is called SNMPv3 and described in RFC 1906 129 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 131 o Protocol operations for accessing management information. The 132 first set of protocol operations and associated PDU formats is 133 described in STD 15, RFC 1157 [RFC1157]. A second set of 134 protocol operations and associated PDU formats is described in 135 RFC 1905 [RFC1905]. 137 o A set of fundamental applications described in RFC 2573 138 [RFC2573] and the view-based access control mechanism described 139 in RFC 2575 [RFC2575]. 141 A more detailed introduction to the current SNMP Management Framework 142 can be found in RFC 2570 [RFC2570]. 144 Managed objects are accessed via a virtual information store, termed 145 the Management Information Base or MIB. Objects in the MIB are 146 defined using the mechanisms defined in the SMI. 148 This memo specifies a MIB module that is compliant to the SMIv2. A 149 MIB conforming to the SMIv1 can be produced through the appropriate 150 translations. The resulting translated MIB must be semantically 151 equivalent, except where objects or events are omitted because no 152 translation is possible (use of Counter64). Some machine readable 153 information in SMIv2 will be converted into textual descriptions in 154 SMIv1 during the translation process. However, this loss of machine 155 readable information is not considered to change the semantics of the 156 MIB. 158 3. Structure of the MIB 160 This section describes the structure of the LDP MIB. 162 3.1. Overview 164 The MIB provides objects to configure/set-up potential LDP sessions 165 on a specific LSR. A table is used to configure potential LDP 166 Sessions, where each row in the table initiates a potential LDP 167 Session. This is the mplsLdpEntityTable. 169 Another table, the mplsLdpPeerTable, is a read-only table which 170 records information learned via discovery or from the session 171 initialization message. Each row in the Peer Table represents an LDP 172 Peer. This table contains information which is specific to the 173 Entity-Peer interactions but is not appropriate for the 174 mplsLdpSessionTable. In other words, the Peer table contains 175 information which is useful but is not strictly part of the Session. 177 A third table is used to show the actual sessions which have been, or 178 are in the process of being established. Each row represents a 179 specific session between an Entity (on this LSR) and a peer. 181 3.2. Future Considerations 183 The LDP Specification [18] does not specify the use of VPNs or 184 multicast for LDP, and thus, objects related to these areas have not 185 been included in the MIB. 187 This MIB does not include VP merge configuration either. [30] does 188 not yet describe this capability and so it has been excluded from the 189 MIB. 191 These areas need to be specified in the LDP Specification prior to 192 being added in this or any other MIB. 194 3.3. Interface Indexing 196 Interface Indexes as specified in [27] are used in the MIB. The 197 descriptions of the ifIndexes denote which ifIndex is being used. 198 NOTE: the use of ifIndex is for actual existing connections. 200 3.4. Differences from the LDP Specification 202 Currently, there are 3 differences between this specification and the 203 LDP Specification. As previously mentioned, this MIB is almost 204 entirely based on the LDP specification. The differences are 205 documented here in the hope to avoid any confusion between the two 206 documents. 208 The first difference is that the LDP Entity Table contains some 209 DEFVAL clauses which are not specified explicitely in the LDP 210 Specification. These values, although not documented in the LDP 211 Specification are widely used by existing LDP MIB implementations and 212 thus, have been adopted within this MIB. Please note, they can 213 certainly be changed during row creation or a subsequent set request. 215 A second difference is the mplsLdpEntityConfGenericLabelRangeTable. 216 This table, although provided as a way to reserve a range of generic 217 labels, does not exist in the LDP Specification. It was added to the 218 MIB due to a request from the working group and because this table 219 was considered useful for reserving a range of generic labels. 221 The third difference is documented by the TEXTUAL-CONVENTION, 222 MplsAtmVcIdentifier which is in the MPLS-TC-MIB [36]. This TC was 223 added to restrict vci values to be greater than 31 as described in 224 RFC 3032 [30]. 226 3.5. Discussion of MIB Groups 228 Currently, there are six groups: the MPLS LDP General Group, the MPLS 229 LDP Generic Group, the MPLS LDP ATM Group, the MPLS LDP Frame Relay 230 Group, the MPLS Mapping Group and the MPLS LDP Notifications Group. 231 The MPLS LDP General Group and the MPLS LDP Notifications Group 232 should always be supported. The MPLS LDP Generic Group is specific 233 to Generic labels and should be supported only if LDP is using 234 Generic Labels. The MPLS LDP ATM Group is specific to ATM and should 235 be supported only if LDP is using ATM. Likewise, the MPLS LDP Frame 236 Relay group is specific to Frame Relay and should be supported only 237 if LDP is using Frame Relay. The MPLS LDP Mapping group should be 238 supported if and only if the tables, mplsInSegmentTable, 239 mplsOutSegmentTable and mplsXCTable from the LSR MIB are supported. 241 3.6. The MPLS LDP General Group 243 This group contains information about the specific LDP Entities which 244 are associated with this agent. Each LSR must have at least one LDP 245 Entity. 247 3.6.1. The LDP Entity Table 249 The LDP Entity Table provides a way to configure the LSR for using 250 LDP. There must be at least one LDP Entity for the LSR to support 251 LDP. 253 Each entry/row in this table represents a single LDP Entity. 255 3.6.2. Changing Values After Session Establishment 257 According to the LDP specification [18] there is no way to manually 258 modify a session once session initialization starts. One way to 259 manually modify a session's parameters is by using SNMP to change the 260 MIB objects related to that session. Please note special care should 261 be taken if MIB objects which are used in the MPLS LDP Session 262 Initialization need to be modified. If the modification of any of 263 these MIB variables takes place anytime after the start of session 264 intialization, then the entire session must be halted. Any 265 information learned by that session must be discarded. The objects 266 should then be modified, and session initialization started. 268 For example, assume that a user wishes to change the configuration of 269 a Label Range which is used by a Session that has already been 270 established. The user should change the mplsLdpEntityAdminStatus to 271 "disable(2)". Setting the mplsLdpEntityAdminStatus to "disable(2)" 272 will cause the session to be torn down and all LSPs established due 273 to that session will also be torn down. Also, all information 274 related to that session should be removed from this MIB, and if the 275 LSR MIB is implemented and the optional Mapping Table objects are 276 implemented, then all information related to the LSPs in this session 277 should be removed from these MIBs. [For more information please see 278 the section on "The Mapping Tables".] At this point, the user could 279 modify the Label Range. Lastly, the user should set the 280 mplsLdpEntityAdminStatus to "enable(1)". At this point session 281 initialization should occur. The LDP Entity goes through the Session 282 Initialization in order to communicate the new Label Ranges to the 283 Peer and establish new LSPs. 285 3.6.3. mplsLdpEntityAdminStatus and mplsLdpEntityRowStatus 287 The mplsLdpEntityAdminStatus object could be viewed as having a 288 subset of the functionality of the mplsLdpEntityRowStatus object. 289 For example, the AdminStatus object has states of enable(1) and 290 disable(2). Setting the mplsLdpEntityAdminStatus object to 291 disable(2) and setting the mplsLdpEntityRowStatus object to 292 notInService(2) are functionally the same. The motivation behind 293 keeping the mplsLdpEntityAdminStatus object is that there could be 294 situations where a user would be given write permission to the 295 mplsLdpEntityAdminStatus object, but would not be given write 296 permission to the mplsLdpEntityRowStatus object. Having write 297 permission to the mplsLdpEntityRowStatus object would mean that a 298 user would be able to destroy a row. This was the motivation for 299 keeping the two objects. 301 3.6.4. The LDP Entity Generic Objects 303 The mplsLdpEntityConfGenericLabelRangeTable is for configuring LDP 304 for using Generic Labels ranges. Although the LDP Specification does 305 not provide a way for configuring Label Ranges for Generic Labels, 306 the MIB does provide a way to reserve a range of generic labels 307 because this may be useful for LDP implementations which deploy 308 generic labels. 310 3.6.5. The LDP Entity ATM Objects 312 There exists two tables to configure LDP for using ATM. These tables 313 are the mplsLdpEntityAtmParmsTable and the 314 mplsLdpEntityConfAtmLabelRangeTable. 316 The mplsLdpEntityAtmParmsTable provides a way to configure 317 information which would be contained in the 'Optional Parameter' 318 portion of an LDP PDU Initialization Message. 320 The mplsLdpEntityConfAtmLabelRangeTable provides a way to configure 321 information which would be contained in the 'ATM Label Range 322 Components portion of an LDP PDU Intialization Message, see [30] and 323 [18]. 325 3.6.6. The LDP Entity Frame Relay Objects 327 There exists two tables to configure LDP for using Frame Relay. 328 These tables are the mplsLdpEntityFrameRelayParmsTable and the 329 mplsLdpEntityConfFrLabelRangeTable. 331 The mplsLdpEntityFrameRelayParmsTable provides a way to configure 332 information which would be contained in the 'Optional Parameter' 333 portion of an LDP PDU Initialization Message. 335 The mplsLdpEntityConfFrLabelRangeTable provides a way to configure 336 information which would be contained in the Frame Relay Label Range 337 Components portion of an LDP PDU Intialization Message, see [32] and 338 [18]. 340 3.6.7. The LDP Entity Statistics Table 342 The mplsLpdEntityStatsTable is a read-only table which contains 343 statistical information related to failed attempts to establish 344 sessions. Each row in this table is related to a single LDP entity 345 and this table AUGMENTS an mplsLdpEntityEntry. This table could be 346 used to give insight into how to reconfigure values so that a session 347 could be successfully established. For example, if the 348 mpslLdpSessionRejectedLabelRangeErrors Counter object was increasing, 349 then this would indicate that the label range may need to be 350 adjusted. 352 3.6.8. The LDP Peer Table 354 The LDP Peer Table is a read-only table which contains information 355 about LDP Peers known to LDP Entities. A row in this table is related 356 to one or more rows in the Hello Adjacency Table and related to a 357 single row in the Session Table. The values in the Peer table are 358 relevant to a Peer and may or may not be the same values used in the 359 session. For example, the Peer's PathLimit information is learned 360 from the session initialization phase. The actual value for the 361 PathVectorLimit is the Peer's value and may not be part of the 362 session. There could be a mismatch in this value between the Entity 363 and the Peer. In the event of a mismatch, then the session will use 364 the PathLimit set by the Entity (and not the Peer). 366 A separate table allows for a more comprehensive and coherent MIB 367 model. 369 3.6.9. The LDP Hello Adjacencies Table 371 This is a table of all adjacencies between all LDP Entities and all 372 LDP Peers. A Session may have one or more adjacencies. 374 3.6.10. The LDP Session Table 376 The LDP Session Table is a read-only table. Each entry in this table 377 represents a single session between an LDP Entity and a Peer. The 378 mplsLdpPeerEntry AUGMENTS entries in this table. 380 3.6.11. The LDP ATM Session Table 382 The MPLS LDP ATM Session Table is a read-only table which contains 383 session information specific to ATM. 385 3.6.12. The LDP Frame Relay Session Table 387 The MPLS LDP Frame Relay Session Table is a read-only table which 388 contains session information specific to Frame Relay. 390 3.6.13. The LDP Session Statistics Table 392 The MPLS LDP Session Stats Table is a read-only table which contains 393 statistical information on sessions. 395 3.6.14. The LDP Session Peer Address Table 397 The MPLS LDP Session Peer Address Table is a table which extends the 398 mplsLdpSessionTable. This table is a read-only table which stores 399 Addresses learned after session initialization via Address Message 400 advertisement. 402 3.6.15. The Mapping Tables 404 The Label Information Base (LIB) contains information about labels 405 learned by the LSR. The LIB for LDP, CR-LDP and MPLS-RSVP (i.e. all 406 currently defined MPLS protocols) is represented in the LSR MIB [23]. 407 The LIB is represented by the LSR MIB's mplsXCTable (mpls Cross 408 Connect Table), mplsInSegmentTable (mpls In Segment (ingress label) 409 Table) and the mplsOutSegmentTable (mpls Out Segment (egress label) 410 Table). The mplsXCTable models the cross-connection of the ingress 411 label with a specific egress-label. The mplsInSegmentTable stores 412 the ingress label's information, and the mplsOutSegmentTable stores 413 the egress label's information. 415 The LDP Session that created the LSP and the LSP's (ingress label, 416 egress label) pair along with other information is contained in the 417 LSR MIB's mplsXCTable, the mplsInSegmentTable and the 418 mplsOutSegmentTable. 420 In order to utilize the LSR MIB's mplsXCTable, mplsInSegmentTable and 421 mplsOutSegmentTable for LDP sessions, there needed to be a mechanism 422 to associate (or map) LDP sessions with LDP LSPs created as a result 423 of those LDP sessions. The mapping tables in this MIB 424 (mplsLdpSesInLabelMapTable, mplsLdpSesOutLabelMapTable and 425 mplsLdpSesXCMapTable) are used to associate LDP LSP information in 426 this MIB, with the relevant entries in the LSR MIB. 428 The mplsInSegmentTable, the mplsOutSegmentTable and the mplsXCTable 429 in the LSR MIB could contain rows which were created as a result of 430 an LDP LSPs. Three mapping tables were added to this MIB to map LDP 431 Sessions to these tables in the LSR MIB. These mapping tables are 432 described in the next few subsections. Please note, these mapping 433 tables are optional and need only to be implemented if the 434 mplsInSegmentTable, mplsOutSegmentTable and mplsXCTable from the LSR 435 MIB are implemented. 437 In order to expedite development, these mapping objects have been 438 made optional in the conformance section of the MIB. 440 As discussed in the section, "Changing Values after Session 441 Establishment", if a session is torn down, then all the information 442 related to this session, must be removed from the both LDP MIB and, 443 if implemented, from the LSR MIB. 445 3.6.15.1. The LDP Session In Label Map Table 447 The mplsLdpSesInLabelMapTable provides a way to map LDP LSPs in the 448 LSR MIB's mplsInSegmentTable to the LDP session which created them in 449 this MIB's mplsLdpSessionTable. When a session is torn down, the 450 mapping table, mplsLdpSesInLabelMapTable, provides a way to clean up 451 the related LDP entries in the mplsInSegmentTable. If an LSP is 452 terminated on this LSR then there will be an entry in the mapping 453 table which maps the session and the entry in the mplsInSegmentTable. 454 Please note, there may be entries which are also effected by session 455 teardown in the mplsXCTable. (The relationship between the 456 mplsInSegmentTable and the mplsXCTable and cleanup scenarios will 457 need to be handled and are outside of the scope of this MIB.) 459 This table is optional and only needs to be implemented if the LSR 460 MIB's mplsInSegmentTable and/or mplsXCTable are implemented. 462 3.6.15.2. The LDP Session Out Label Map Table 464 The mplsLdpSesOutLabelMapTable provides a way to map a LDP LSPs in 465 the LSR MIB's mplsOutSegmentTable to the LDP session which created 466 them in this MIB's mplsLdpSessionTable. When a session is torn down, 467 the mapping table, mplsLdpSesOutLabelMapTable, provides a way to 468 clean up the related LDP entries in the mplsOutSegmentTable. If an 469 LSP is created by this LSR then there will be an entry in this table 470 which maps the session and the entry in the mplsOutSegmentTable. 471 Please note, there may be entries which are also effected by session 472 teardown in the mplsXCTable. (The relationship between the 473 mplsOutSegmentTable and the mplsXCTable and cleanup scenarios will 474 need to be handled and are outside the scope of this MIB.) 476 This table is optional and only needs to be implemented if the LSR 477 MIB's mplsOutSegmentTable and/or mplsXCTable are implemented. 479 3.6.15.3. The LDP Session XC Map Table 481 The mplsLdpSesXCMapTable provides a way to map LDP LSPs in the LSR 482 MIB's mplsXCTable to the LDP session which created them in this MIB's 483 mplsLdpSessionTable. When a session is torn down, the mapping table, 484 mplsLdpSesXCMapTable, provides a way to clean up the related LDP 485 entries in the mplsXCTable. If an LSP is cross-connected on this 486 LSR, then there will be an entry in this mapping table which maps the 487 session and the entry in the mplsXCTable. Please note, only true 488 cross-connects are represented in the mplsLdpSesXCMapTable. 490 This table is optional and only needs to be implemented if the LSR 491 MIB's mplsXCTable is implemented. 493 3.6.16. The FEC Table 495 The FEC Table is a table which contains FEC (Forwarding Equivalence 496 Class) information. Each entry/row represents a single FEC Element. 497 There is also a FEC Mapping table which maps FECs associated with the 498 Cross-connects. 500 3.7. The LDP Notifications Group 502 3.7.1. LDP Notifications 504 Currently, there are several notifications which are specific for 505 LDP. These are described in this section. 507 The mplsLdpInitSesThresholdExceeded notification indicates to the 508 operator that there may be a misconfigured mplsLdpEntityEntry because 509 the session associated with this Entity is not being established, and 510 the Entity keeps trying to establish the session. A side effect of 511 this situation is that a row in the mplsLdpSessionTable may not be 512 reaching the operational state as indicated by the mplsLdpSesState 513 object. If the value of mplsLdpEntityInitSesThreshold is 0 (zero) 514 then this is equal to specifying the value of inifinity for the 515 threshold, and the mplsLdpInitSesThresholdExceeded Trap will never be 516 sent. 518 The object, mplsLdpEntityPVLMisTrapEnabled is used to enable or 519 disable the sending of the mplsLdpPVLMismatch trap. If enabled, then 520 this trap is sent when there is a mismatch in the Path Vector Limits 521 between the Entity and Peer during session initialization between 522 that Entity and that Peer. In this situation a session could still be 523 established between that entity and that peer. The session uses the 524 value which is configured as the Entity's Path Vector Limit. 525 However, a trap should be sent to indicate that a mismatch occurred. 526 For further details, please see Section 3.5.3 of the LDP 527 Specification [18]. 529 The object, mplsLdpSesUpDownTrapEnable is used to enable or disable 530 the sending of the mplsLdpSessionUp and mplsLdpSessionDown traps. If 531 enabled, then these traps are sent when there is an appropriate 532 change in the mplsLdpSesState object, e.g. when sessions change state 533 (Up to Down for the mplsLdpSessionDown trap, or Down to Up for the 534 mplsLdpSessionUp trap). 536 4. MPLS Label Distribution Protocol MIB Definitions 538 MPLS-LDP-MIB DEFINITIONS ::= BEGIN 540 IMPORTS 541 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, 542 transmission, 543 Integer32, Counter32, Unsigned32 544 FROM SNMPv2-SMI 545 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 546 FROM SNMPv2-CONF 548 RowStatus, TimeInterval, TruthValue, 549 TimeStamp, StorageType 550 FROM SNMPv2-TC 551 InterfaceIndex, InterfaceIndexOrZero 552 FROM IF-MIB 553 AtmVpIdentifier 554 FROM ATM-TC-MIB 555 AddressFamilyNumbers 556 FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB 557 MplsAtmVcIdentifier, MplsLabel, 558 MplsLdpGenAddr, MplsLdpIdentifier, 559 MplsLdpLabelTypes, MplsLsrIdentifier 560 FROM MPLS-TC-MIB 561 ; 563 mplsLdpMIB MODULE-IDENTITY 564 LAST-UPDATED "200108161200Z" -- August 16, 2001 565 ORGANIZATION "Multiprotocol Label Switching (mpls) 566 Working Group" 567 CONTACT-INFO 568 "Joan Cucchiara (jcucchiara@crescentnetworks.com) 569 Crescent Networks 571 Hans Sjostrand (hans@ipunplugged.com) 572 ipUnplugged 574 James V. Luciani (jluciani@crescentnetworks.com) 575 Crescent Networks 577 Working Group Chairs: 578 George Swallow, email: swallow@cisco.com 579 Vijay Srinivasan, email: vijay@cosinecom.com 580 MPLS Working Group, email: mpls@uu.net 581 " 582 DESCRIPTION 583 "This MIB contains managed object definitions for the 584 'Multiprotocol Label Switching, Label Distribution 585 Protocol, LDP' document." 586 ::= { mplsMIB XXXX} -- to be assigned 588 --**************************************************************** 590 mplsMIB OBJECT IDENTIFIER ::= { transmission xxxx } 592 mplsLdpObjects OBJECT IDENTIFIER ::= { mplsLdpMIB 1 } 593 mplsLdpNotifications OBJECT IDENTIFIER ::= { mplsLdpMIB 2 } 594 mplsLdpConformance OBJECT IDENTIFIER ::= { mplsLdpMIB 3 } 596 --**************************************************************** 597 -- MPLS LDP Objects 598 --**************************************************************** 600 mplsLdpLsrObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 1 } 602 mplsLdpEntityObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 2 } 604 -- 605 -- The MPLS Label Distribution Protocol's 606 -- Label Switch Router Objects 607 -- 609 mplsLdpLsrId OBJECT-TYPE 610 SYNTAX MplsLsrIdentifier 611 MAX-ACCESS read-only 612 STATUS current 613 DESCRIPTION 614 "The LSR's Identifier." 615 ::= { mplsLdpLsrObjects 1 } 617 mplsLdpLsrLoopDetectionCapable OBJECT-TYPE 618 SYNTAX INTEGER { 619 none(1), 620 other(2), 621 hopCount(3), 622 pathVector(4), 623 hopCountAndPathVector(5) 624 } 625 MAX-ACCESS read-only 626 STATUS current 627 DESCRIPTION 628 "A indication of whether this 629 Label Switch Router supports 630 loop detection. 632 none(1) -- Loop Detection is not supported 633 on this LSR. 635 other(2) -- Loop Detection is supported but 636 by a method other than those 637 listed below. 639 hopCount(3) -- Loop Detection is supported by 640 Hop Count only. 642 pathVector(4) -- Loop Detection is supported by 643 Path Vector only. 645 hopCountAndPathVector(5) -- Loop Detection is 646 supported by both Hop Count 647 And Path Vector. 649 Since Loop Detection is determined during 650 Session Initialization, an individual session 651 may not be running with loop detection. This 652 object simply gives an indication of whether or not the 653 LSR has the ability to support Loop Detection and 654 which types." 655 ::= { mplsLdpLsrObjects 2 } 657 -- 658 -- The MPLS Label Distribution Protocol Entity Objects 659 -- 661 mplsLdpEntityIndexNext OBJECT-TYPE 662 SYNTAX Unsigned32 (0..4294967295) 663 MAX-ACCESS read-only 664 STATUS current 665 DESCRIPTION 666 "This object contains an appropriate value to 667 be used for mplsLdpEntityIndex when creating 668 entries in the mplsLdpEntityTable. The value 669 0 indicates that no unassigned entries are 670 available. To obtain the mplsLdpEntityIndex 671 value for a new entry, the manager issues a 672 management protocol retrieval operation to obtain 673 the current value of this object. After each 674 retrieval, the agent should modify the value to 675 the next unassigned index." 676 ::= { mplsLdpEntityObjects 1 } 678 mplsLdpEntityTable OBJECT-TYPE 679 SYNTAX SEQUENCE OF MplsLdpEntityEntry 680 MAX-ACCESS not-accessible 681 STATUS current 682 DESCRIPTION 683 "This table contains information about the 684 MPLS Label Distribution Protocol Entities which 685 exist on this Label Switch Router (LSR)." 686 ::= { mplsLdpEntityObjects 2 } 688 mplsLdpEntityEntry OBJECT-TYPE 689 SYNTAX MplsLdpEntityEntry 690 MAX-ACCESS not-accessible 691 STATUS current 692 DESCRIPTION 693 "An entry in this table represents an LDP entity. 694 An entry can be created by a network administrator 695 or by an SNMP agent as instructed by LDP." 696 INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex } 697 ::= { mplsLdpEntityTable 1 } 699 MplsLdpEntityEntry ::= SEQUENCE { 700 mplsLdpEntityLdpId MplsLdpIdentifier, 701 mplsLdpEntityIndex Unsigned32, 702 mplsLdpEntityProtocolVersion Integer32, 703 mplsLdpEntityAdminStatus INTEGER, 704 mplsLdpEntityOperStatus INTEGER, 705 mplsLdpEntityTcpDscPort Unsigned32, 706 mplsLdpEntityUdpDscPort Unsigned32, 707 mplsLdpEntityMaxPduLength Unsigned32, 708 mplsLdpEntityKeepAliveHoldTimer Integer32, 709 mplsLdpEntityHelloHoldTimer Integer32, 710 mplsLdpEntityInitSesThreshold Integer32, 711 mplsLdpEntityLabelDistMethod INTEGER, 712 mplsLdpEntityLabelRetentionMode INTEGER, 713 mplsLdpEntityPVLMisTrapEnable INTEGER, 714 mplsLdpEntityPVL Integer32, 715 mplsLdpEntityHopCountLimit Integer32, 716 mplsLdpEntityTargPeer TruthValue, 717 mplsLdpEntityTargPeerAddrType AddressFamilyNumbers, 718 mplsLdpEntityTargPeerAddr MplsLdpGenAddr, 719 mplsLdpEntityOptionalParameters MplsLdpLabelTypes, 720 mplsLdpEntityDiscontinuityTime TimeStamp, 721 mplsLdpEntityStorType StorageType, 722 mplsLdpEntityRowStatus RowStatus 723 } 725 mplsLdpEntityLdpId OBJECT-TYPE 726 SYNTAX MplsLdpIdentifier 727 MAX-ACCESS not-accessible 728 STATUS current 729 DESCRIPTION 730 "The LDP identifier." 731 REFERENCE 732 "LDP Specification, Section on LDP Identifiers." 733 ::= { mplsLdpEntityEntry 1 } 735 mplsLdpEntityIndex OBJECT-TYPE 736 SYNTAX Unsigned32 (1..4294967295) 737 MAX-ACCESS not-accessible 738 STATUS current 739 DESCRIPTION 740 "This index is used as a secondary index to uniquely 741 identify this row. Before creating a row in this table, 742 the 'mplsLdpEntityIndexNext' object should be retrieved. 743 That value should be used for the value of this index 744 when creating a row in this table. (NOTE: if a value 745 of zero (0) is retrieved, that indicates that no rows 746 can be created in this table at this time. 748 A secondary index (this object) is meaningful to some 749 but not all, LDP implementations. For example 750 in an LDP implementation which uses PPP would 751 use this index to differentiate PPP sub-links." 752 ::= { mplsLdpEntityEntry 2 } 754 mplsLdpEntityProtocolVersion OBJECT-TYPE 755 SYNTAX Integer32(1..65535) 756 MAX-ACCESS read-create 757 STATUS current 758 DESCRIPTION 759 "The version number of the LDP protocol which will be 760 used in the session initialization message. 762 Section 3.5.3 in the LDP Specification specifies 763 that the version of the LDP protocol is negotiated during 764 session establishment. The value of this object 765 represents the value that is sent in the initialization 766 message." 767 REFERENCE 768 "See RFC 3036, LDP Specification, Section 3.5.3 Initialization 769 Message." 770 DEFVAL { 1 } 771 ::= { mplsLdpEntityEntry 3 } 773 mplsLdpEntityAdminStatus OBJECT-TYPE 774 SYNTAX INTEGER { 775 enable(1), 776 disable(2) 778 } 779 MAX-ACCESS read-create 780 STATUS current 781 DESCRIPTION 782 "The administrative status of this LDP Entity. 783 If this object is changed from 'enable' to 'disable' 784 and this entity has already attempted to establish 785 contact with a Peer (which implies that the 786 'mplsLdpEntityRowStatus' object has been set to 787 'active'), then all contact with that 788 Peer is lost and all information from that Peer 789 needs to be removed from the MIB. 791 At this point the user is able to change values 792 which are related to this entity. 794 When the admin status is set back to 'up', then 795 this Entity will attempt to establish new sessions 796 with the Peer." 797 DEFVAL { enable } 798 ::= { mplsLdpEntityEntry 4 } 800 mplsLdpEntityOperStatus OBJECT-TYPE 801 SYNTAX INTEGER { 802 unknown(0), 803 enabled(1), 804 disabled(2) 805 } 806 MAX-ACCESS read-only 807 STATUS current 808 DESCRIPTION 809 "The operational status of this LDP Entity." 810 ::= { mplsLdpEntityEntry 5 } 812 mplsLdpEntityTcpDscPort OBJECT-TYPE 813 SYNTAX Unsigned32 814 MAX-ACCESS read-create 815 STATUS current 816 DESCRIPTION 817 "The TCP Discovery Port for 818 LDP. The default value is the well-known 819 value of this port." 820 DEFVAL { 646 } 821 ::= { mplsLdpEntityEntry 6 } 823 mplsLdpEntityUdpDscPort OBJECT-TYPE 824 SYNTAX Unsigned32 825 MAX-ACCESS read-create 826 STATUS current 827 DESCRIPTION 828 "The UDP Discovery Port for 829 LDP. The default value is the 830 well-known value for this port." 831 DEFVAL { 646 } 832 ::= { mplsLdpEntityEntry 7 } 834 mplsLdpEntityMaxPduLength OBJECT-TYPE 835 SYNTAX Unsigned32 (0..65535) 836 UNITS "octets" 837 MAX-ACCESS read-create 838 STATUS current 839 DESCRIPTION 840 "The maximum PDU Length that is sent in 841 the Common Session Parameters of an Initialization 842 Message. A value of 255 or less specifies the 843 default maximum length of 4096 octets." 844 REFERENCE 845 "See Section on the 'Initialization Message' in the 846 LDP Specification." 847 DEFVAL { 4096 } 848 ::= { mplsLdpEntityEntry 8 } 850 mplsLdpEntityKeepAliveHoldTimer OBJECT-TYPE 851 SYNTAX Integer32 (1..65535) 852 UNITS "seconds" 853 MAX-ACCESS read-create 854 STATUS current 855 DESCRIPTION 856 "The two octet value which is the proposed keep alive hold 857 timer for this LDP Entity." 858 DEFVAL { 40 } 859 ::= { mplsLdpEntityEntry 9 } 861 mplsLdpEntityHelloHoldTimer OBJECT-TYPE 862 SYNTAX Integer32 (0..65535) 863 UNITS "seconds" 864 MAX-ACCESS read-create 865 STATUS current 866 DESCRIPTION 867 "The two octet value which is the proposed Hello hold 868 timer for this LDP Entity. A value of 0 means use the 869 default, which is 15 seconds for Link Hellos and 45 870 seconds for Targeted Hellos. A value of 65535 means 871 infinite." 872 DEFVAL { 0 } 873 ::= { mplsLdpEntityEntry 10 } 875 mplsLdpEntityInitSesThreshold OBJECT-TYPE 876 SYNTAX Integer32 877 MAX-ACCESS read-create 878 STATUS current 879 DESCRIPTION 880 "When attempting to establish a session with a 881 given Peer, the given LDP Entity should 882 send out the SNMP notification, 883 'mplsLdpInitSesThresholdExceeded', when 884 the number of Session Initialization messages sent 885 exceeds this threshold. The notification is 886 used to notify an operator when this Entity and 887 its Peer are possibily engaged in an endless 888 sequence of messages as each NAKs the other's 889 Initialization messages with Error Notification 890 messages. Setting this threshold which triggers 891 the notification is one way to 892 notify the operator. 894 A value of 0 (zero) for this object 895 indicates that the threshold is infinity, and 896 the SNMP notification will never be sent 897 when the value of this object is 0 (zero)." 898 REFERENCE 899 "RFC 3036, Section 2.5.3 Session Initialization." 900 DEFVAL { 8 } 901 ::= { mplsLdpEntityEntry 11 } 903 mplsLdpEntityLabelDistMethod OBJECT-TYPE 904 SYNTAX INTEGER { 905 downstreamOnDemand(1), 906 downstreamUnsolicited(2) 907 } 908 MAX-ACCESS read-create 909 STATUS current 910 DESCRIPTION 911 "For any given LDP session, the method of 912 label distribution must be specified." 913 ::= { mplsLdpEntityEntry 12 } 915 mplsLdpEntityLabelRetentionMode OBJECT-TYPE 916 SYNTAX INTEGER { 917 conservative(1), 918 liberal(2) 919 } 920 MAX-ACCESS read-create 921 STATUS current 922 DESCRIPTION 923 "The LDP Entity can be configured to use either 924 conservative or liberal label retention mode. 926 If the value of this object is conservative(1) 927 then advertized label mappings are retained 928 only if they will be used to forward packets, 929 i.e. if label came from a valid next hop. 931 If the value of this object is liberal(2) 932 then all advertized label mappings are retained 933 whether they are from a valid next hop or not." 934 ::= { mplsLdpEntityEntry 13 } 936 mplsLdpEntityPVLMisTrapEnable OBJECT-TYPE 937 SYNTAX INTEGER { 938 enabled(1), 939 disabled(2) 940 } 941 MAX-ACCESS read-create 942 STATUS current 943 DESCRIPTION 944 "Indicates whether the 'mplsLdpPVLMismatch' 945 trap should be generated. 947 If the value of this object is 'enabled(1)' 948 then the trap will generated. If the value 949 of this object is 'disabled(2)' then the 950 trap will not be generated. The DEFVAL 951 is set to 'enabled(1)'." 952 DEFVAL { enabled } 953 ::= { mplsLdpEntityEntry 14 } 955 mplsLdpEntityPVL OBJECT-TYPE 956 SYNTAX Integer32 (0..255) 957 MAX-ACCESS read-create 958 STATUS current 959 DESCRIPTION 960 "If the value of this object is 0 (zero) then 961 Loop Dection for Path Vectors is disabled. 963 Otherwise, if this object has a value greater than 964 zero, then Loop Dection for Path Vectors is enabled, 965 and the Path Vector Limit is this value. 966 Also, the value of the object, 967 'mplsLdpLsrLoopDetectionCapable', must be set to 968 either 'pathVector(4)' or 'hopCountAndPathVector(5)', 969 if this object has a value greater than 0 (zero)." 970 ::= { mplsLdpEntityEntry 15 } 972 mplsLdpEntityHopCountLimit OBJECT-TYPE 973 SYNTAX Integer32 (0..255) 974 MAX-ACCESS read-create 975 STATUS current 976 DESCRIPTION 977 "If the value of this object is 0 (zero), 978 then Loop Detection using Hop Counters is 979 disabled. 981 If the value of this object is greater than 982 0 (zero) then Loop Detection using Hop 983 Counters is enabled, and this object 984 specifies this Entity's maximum allowable 985 value for the Hop Count. 986 Also, the value of the object 987 mplsLdpLsrLoopDetectionCapable must be set 988 to either 'hopCount(3)' or 989 'hopCountAndPathVector(5)' if this object 990 has a value greater than 0 (zero)." 991 ::= { mplsLdpEntityEntry 16 } 993 mplsLdpEntityTargPeer OBJECT-TYPE 994 SYNTAX TruthValue 995 MAX-ACCESS read-create 996 STATUS current 997 DESCRIPTION 998 "If this LDP entity uses targeted peer then set 999 this to true." 1000 DEFVAL { false } 1001 ::= { mplsLdpEntityEntry 17 } 1003 mplsLdpEntityTargPeerAddrType OBJECT-TYPE 1004 SYNTAX AddressFamilyNumbers 1005 MAX-ACCESS read-create 1006 STATUS current 1007 DESCRIPTION 1008 "The type of the internetwork layer address used for 1009 the Extended Discovery. This object indicates how 1010 the value of mplsLdpEntityTargPeerAddr is to 1011 be interpreted." 1012 ::= { mplsLdpEntityEntry 18 } 1014 mplsLdpEntityTargPeerAddr OBJECT-TYPE 1015 SYNTAX MplsLdpGenAddr 1016 MAX-ACCESS read-create 1017 STATUS current 1018 DESCRIPTION 1019 "The value of the internetwork layer address used for 1020 the Extended Discovery." 1021 ::= { mplsLdpEntityEntry 19 } 1023 mplsLdpEntityOptionalParameters OBJECT-TYPE 1024 SYNTAX MplsLdpLabelTypes 1025 MAX-ACCESS read-create 1026 STATUS current 1027 DESCRIPTION 1028 "Specifies the optional parameters for the LDP 1029 Initialization Message. If the value is generic(1) 1030 then no optional parameters will be sent in 1031 the LDP Initialization message associated with 1032 this Entity. 1034 If the value is atmParameters(2) then 1035 a row must be created in the mplsLdpEntityAtmParms 1036 Table, which corresponds to this entry. 1038 If the value is frameRelayParameters(3) then 1039 a row must be created in the mplsLdpEntityFrameRelayParms 1040 Table, which corresponds to this entry." 1041 ::= { mplsLdpEntityEntry 20 } 1043 mplsLdpEntityDiscontinuityTime OBJECT-TYPE 1044 SYNTAX TimeStamp 1045 MAX-ACCESS read-only 1046 STATUS current 1047 DESCRIPTION 1048 "The value of sysUpTime on the most recent occasion 1049 at which any one or more of this entity's counters 1050 suffered a discontinuity. The relevant counters are the 1051 specific instances associated with this entity of 1052 any Counter32, or Counter64 object contained 1053 in the 'mplsLdpEntityStatsTable'. If no such 1054 discontinuities have occurred since the last 1055 re-initialization of the local management 1056 subsytem, then this object contains a zero 1057 value." 1058 ::= { mplsLdpEntityEntry 21 } 1060 mplsLdpEntityStorType OBJECT-TYPE 1061 SYNTAX StorageType 1062 MAX-ACCESS read-create 1063 STATUS current 1064 DESCRIPTION 1065 "The storage type for this entry." 1066 ::= { mplsLdpEntityEntry 22 } 1068 mplsLdpEntityRowStatus OBJECT-TYPE 1069 SYNTAX RowStatus 1070 MAX-ACCESS read-create 1071 STATUS current 1072 DESCRIPTION 1073 "An object that allows entries in this table to 1074 be created and deleted using the 1075 RowStatus convention. 1077 Once the 'mplsLdpEntityAdminStatus' object has 1078 the value of 'up' and this object has the value 1079 of 'active' then the Entity will atttempt to 1080 contact an LDP Peer. If the value of this object 1081 is changed to 'notInService', then the Entity looses 1082 contact with the LDP Peer and all information related 1083 to that Peer must be removed from the MIB. This has 1084 the same effect as changing 'mplsLdpEntityAdminStatus' 1085 from 'enable' to 'disable'. 1087 When this object is set to 'active' and the value of 1088 the 'mplsLdpEntityAdminStatus' is 'enable' then 1089 this Entity will attempt to contact the Peer and 1090 establish new sessions." 1091 ::= { mplsLdpEntityEntry 23 } 1093 -- 1094 -- Ldp Entity Objects for Generic Labels 1095 -- 1097 mplsLdpEntityGenericObjects OBJECT IDENTIFIER ::= 1098 { mplsLdpEntityObjects 3 } 1100 -- 1101 -- The MPLS LDP Entity Configurable Generic Label Range Table 1102 -- 1104 mplsLdpEntityConfGenLRTable OBJECT-TYPE 1105 SYNTAX SEQUENCE OF MplsLdpEntityConfGenLREntry 1106 MAX-ACCESS not-accessible 1107 STATUS current 1108 DESCRIPTION 1109 "The MPLS LDP Entity Configurable Generic Label Range Table. 1110 The purpose of this table is to provide a mechanism 1111 for specifying a contiguous range of generic labels, 1112 or a 'label range' for LDP Entities. 1114 LDP Entities which use Generic Labels must have at least one 1115 entry in this table." 1116 ::= { mplsLdpEntityGenericObjects 1 } 1118 mplsLdpEntityConfGenLREntry OBJECT-TYPE 1119 SYNTAX MplsLdpEntityConfGenLREntry 1120 MAX-ACCESS not-accessible 1121 STATUS current 1122 DESCRIPTION 1123 "A row in the LDP Entity Configurable Generic Label 1124 Range Table. One entry in this table contains 1125 information on a single range of labels 1126 represented by the configured Upper and Lower 1127 Bounds pairs. NOTE: there is NO corresponding 1128 LDP message which relates to the information 1129 in this table, however, this table does provide 1130 a way for a user to 'reserve' a generic label 1131 range. 1133 NOTE: The ranges for a specific LDP Entity 1134 are UNIQUE and non-overlapping. 1136 A row will not be created unless a unique and 1137 non-overlapping range is specified." 1138 INDEX { mplsLdpEntityLdpId, 1139 mplsLdpEntityIndex, 1140 mplsLdpEntityConfGenLRMin, 1141 mplsLdpEntityConfGenLRMax 1142 } 1143 ::= { mplsLdpEntityConfGenLRTable 1 } 1145 MplsLdpEntityConfGenLREntry ::= SEQUENCE { 1146 mplsLdpEntityConfGenLRMin Unsigned32, 1147 mplsLdpEntityConfGenLRMax Unsigned32, 1148 mplsLdpEntityConfGenIfIndxOrZero InterfaceIndexOrZero, 1149 mplsLdpEntityConfGenLRStorType StorageType, 1150 mplsLdpEntityConfGenLRRowStatus RowStatus 1151 } 1153 mplsLdpEntityConfGenLRMin OBJECT-TYPE 1154 SYNTAX Unsigned32(0..1048575) 1155 MAX-ACCESS not-accessible 1156 STATUS current 1157 DESCRIPTION 1158 "The minimum label configured for this range." 1159 ::= { mplsLdpEntityConfGenLREntry 1 } 1161 mplsLdpEntityConfGenLRMax OBJECT-TYPE 1162 SYNTAX Unsigned32(0..1048575) 1163 MAX-ACCESS not-accessible 1164 STATUS current 1165 DESCRIPTION 1166 "The maximum label configured for this range." 1167 ::= { mplsLdpEntityConfGenLREntry 2 } 1169 mplsLdpEntityConfGenIfIndxOrZero OBJECT-TYPE 1170 SYNTAX InterfaceIndexOrZero 1171 MAX-ACCESS read-create 1172 STATUS current 1173 DESCRIPTION 1174 "This value represents either the InterfaceIndex of 1175 the 'ifLayer' where these Generic Label would be created, or 1176 0 (zero). The value of zero means that the InterfaceIndex 1177 is not known. For example, if the InterfaceIndex is 1178 created subsequent to the Generic Label's creation, then 1179 it would not be known. However, if the InterfaceIndex 1180 is known, then it must be represented by this value. 1182 If an InterfaceIndex becomes known, then the 1183 network management entity (e.g. SNMP agent) responsible 1184 for this object MUST change the value from 0 (zero) to the 1185 value of the InterfaceIndex." 1186 ::= { mplsLdpEntityConfGenLREntry 3 } 1188 mplsLdpEntityConfGenLRStorType OBJECT-TYPE 1189 SYNTAX StorageType 1190 MAX-ACCESS read-create 1191 STATUS current 1192 DESCRIPTION 1193 "The storage type for this entry." 1194 ::= { mplsLdpEntityConfGenLREntry 4 } 1196 mplsLdpEntityConfGenLRRowStatus OBJECT-TYPE 1197 SYNTAX RowStatus 1198 MAX-ACCESS read-create 1199 STATUS current 1200 DESCRIPTION 1201 "An object that allows entries in this 1202 table to be created and deleted using 1203 the RowStatus convention. 1205 There must exist at least one entry in this 1206 table for every LDP Entity that has a 1207 generic label configured. 1209 NOTE: This RowStatus object should 1210 have the same value of the 'mplsLdpEntityRowStatus' 1211 related to this entry." 1212 ::= { mplsLdpEntityConfGenLREntry 5 } 1214 -- 1215 -- Ldp Entity Objects for ATM 1216 -- 1218 mplsLdpEntityAtmObjects OBJECT IDENTIFIER ::= 1219 { mplsLdpEntityObjects 4 } 1221 mplsLdpEntityAtmParmsTable OBJECT-TYPE 1222 SYNTAX SEQUENCE OF MplsLdpEntityAtmParmsEntry 1223 MAX-ACCESS not-accessible 1224 STATUS current 1225 DESCRIPTION 1226 "This table contains information about the 1227 ATM specific information which could be used 1228 in the 'Optional Parameters' and other ATM specific 1229 information." 1230 ::= { mplsLdpEntityAtmObjects 1 } 1232 mplsLdpEntityAtmParmsEntry OBJECT-TYPE 1233 SYNTAX MplsLdpEntityAtmParmsEntry 1234 MAX-ACCESS not-accessible 1235 STATUS current 1236 DESCRIPTION 1237 "An entry in this table represents the ATM parameters 1238 and ATM information for this LDP entity." 1239 INDEX { mplsLdpEntityLdpId, 1240 mplsLdpEntityIndex 1241 } 1242 ::= { mplsLdpEntityAtmParmsTable 1 } 1244 MplsLdpEntityAtmParmsEntry ::= SEQUENCE { 1245 mplsLdpEntityAtmIfIndxOrZero InterfaceIndexOrZero, 1246 mplsLdpEntityAtmMergeCap INTEGER, 1247 mplsLdpEntityAtmLRComponents Unsigned32, 1248 mplsLdpEntityAtmVcDirectionality INTEGER, 1249 mplsLdpEntityAtmLsrConnectivity INTEGER, 1250 mplsLdpEntityDefaultControlVpi AtmVpIdentifier, 1251 mplsLdpEntityDefaultControlVci MplsAtmVcIdentifier, 1252 mplsLdpEntityUnlabTrafVpi AtmVpIdentifier, 1253 mplsLdpEntityUnlabTrafVci MplsAtmVcIdentifier, 1254 mplsLdpEntityAtmStorType StorageType, 1255 mplsLdpEntityAtmRowStatus RowStatus 1256 } 1258 mplsLdpEntityAtmIfIndxOrZero OBJECT-TYPE 1259 SYNTAX InterfaceIndexOrZero 1260 MAX-ACCESS read-create 1261 STATUS current 1262 DESCRIPTION 1263 "This value represents either the InterfaceIndex of 1264 the 'ifLayer' where the ATM Labels 'owned' by this 1265 entry were created, or 0 (zero). The value of zero 1266 means that the InterfaceIndex is not known. For example, 1267 if the InterfaceIndex is created subsequent to the 1268 ATM Label's creation, then it would not be known. 1269 However, if the InterfaceIndex is known, then it must 1270 be represented by this value. 1272 If an InterfaceIndex becomes known, then the 1273 network management entity (e.g. SNMP agent) responsible 1274 for this object MUST change the value from 0 (zero) to the 1275 value of the InterfaceIndex. If an ATM Label is 1276 being used in forwarding data, then the value of this 1277 object MUST be the InterfaceIndex." 1278 ::= { mplsLdpEntityAtmParmsEntry 1 } 1280 mplsLdpEntityAtmMergeCap OBJECT-TYPE 1281 SYNTAX INTEGER { 1282 notSupported(0), 1283 vcMerge(2) 1284 } 1285 MAX-ACCESS read-create 1286 STATUS current 1287 DESCRIPTION 1288 "Denotes the Merge Capability of this Entity." 1289 ::= { mplsLdpEntityAtmParmsEntry 2 } 1291 mplsLdpEntityAtmLRComponents OBJECT-TYPE 1292 SYNTAX Unsigned32 (1..65535) 1293 MAX-ACCESS read-create 1294 STATUS current 1295 DESCRIPTION 1296 "Number of Label Range Components in the Initialization 1297 message. This also represents the number of entries 1298 in the mplsLdpEntityConfAtmLRTable which correspond 1299 to this entry." 1300 ::= { mplsLdpEntityAtmParmsEntry 3 } 1302 mplsLdpEntityAtmVcDirectionality OBJECT-TYPE 1303 SYNTAX INTEGER { 1304 bidirectional(0), 1305 unidirectional(1) 1306 } 1307 MAX-ACCESS read-create 1308 STATUS current 1309 DESCRIPTION 1310 "If the value of this object is 'bidirectional(0)', 1311 a given VCI, within a given VPI, is used as a 1312 label for both directions independently. 1314 If the value of this object is 'unidirectional(1)', 1315 a given VCI within a VPI designates one direction." 1317 ::= { mplsLdpEntityAtmParmsEntry 4 } 1319 mplsLdpEntityAtmLsrConnectivity OBJECT-TYPE 1320 SYNTAX INTEGER { 1321 direct(1), 1322 indirect(2) 1323 } 1324 MAX-ACCESS read-create 1325 STATUS current 1326 DESCRIPTION 1327 "The peer LSR may be connected indirectly by means of an 1328 ATM VP so that the VPI values may be different on either 1329 endpoint so the label MUST be encoded entirely within the 1330 VCI field." 1331 DEFVAL { direct } 1332 ::= { mplsLdpEntityAtmParmsEntry 5 } 1334 mplsLdpEntityDefaultControlVpi OBJECT-TYPE 1335 SYNTAX AtmVpIdentifier 1336 MAX-ACCESS read-create 1337 STATUS current 1338 DESCRIPTION 1339 "The default VPI value for the non-MPLS connection. The 1340 default value of this is 0 (zero) but other values may 1341 be configured. This object allows a different value 1342 to be configured." 1343 DEFVAL 1344 { 0 } 1345 ::= { mplsLdpEntityAtmParmsEntry 6 } 1347 mplsLdpEntityDefaultControlVci OBJECT-TYPE 1348 SYNTAX MplsAtmVcIdentifier 1349 MAX-ACCESS read-create 1350 STATUS current 1351 DESCRIPTION 1352 "The Default VCI value for a non-MPLS connection. The 1353 default value of this is 32 but other values may be 1354 configured. This object allows a different value to 1355 be configured." 1356 DEFVAL 1357 { 32 } 1358 ::= { mplsLdpEntityAtmParmsEntry 7 } 1360 mplsLdpEntityUnlabTrafVpi OBJECT-TYPE 1361 SYNTAX AtmVpIdentifier 1362 MAX-ACCESS read-create 1363 STATUS current 1364 DESCRIPTION 1365 "VPI value of the VCC supporting unlabelled traffic. This 1366 non-MPLS connection is used to carry unlabelled (IP) 1367 packets. The default value is the same as the default 1368 value of the 'mplsLdpEntityDefaultControlVpi', however 1369 another value may be configured." 1370 DEFVAL { 0 } 1371 ::= { mplsLdpEntityAtmParmsEntry 8 } 1373 mplsLdpEntityUnlabTrafVci OBJECT-TYPE 1374 SYNTAX MplsAtmVcIdentifier 1375 MAX-ACCESS read-create 1376 STATUS current 1377 DESCRIPTION 1378 "VCI value of the VCC supporting unlabelled traffic. 1379 This non-MPLS connection is used to carry unlabelled (IP) 1380 packets. The default value is the same as the default 1381 value of the 'mplsLdpEntityDefaultControlVci', however 1382 another value may be configured." 1383 DEFVAL { 32 } 1384 ::= { mplsLdpEntityAtmParmsEntry 9 } 1386 mplsLdpEntityAtmStorType OBJECT-TYPE 1387 SYNTAX StorageType 1388 MAX-ACCESS read-create 1389 STATUS current 1390 DESCRIPTION 1391 "The storage type for this entry." 1392 ::= { mplsLdpEntityAtmParmsEntry 10 } 1394 mplsLdpEntityAtmRowStatus OBJECT-TYPE 1395 SYNTAX RowStatus 1396 MAX-ACCESS read-create 1397 STATUS current 1398 DESCRIPTION 1399 "An object that allows entries in this table to 1400 be created and deleted using the 1401 RowStatus convention. 1403 NOTE: This RowStatus object should 1404 have the same value of the 'mplsLdpEntityRowStatus' 1405 related to this entry." 1406 ::= { mplsLdpEntityAtmParmsEntry 11 } 1408 -- 1409 -- The MPLS LDP Entity Configurable ATM Label Range Table 1410 -- 1412 mplsLdpEntityConfAtmLRTable OBJECT-TYPE 1413 SYNTAX SEQUENCE OF MplsLdpEntityConfAtmLREntry 1414 MAX-ACCESS not-accessible 1415 STATUS current 1416 DESCRIPTION 1417 "The MPLS LDP Entity Configurable ATM Label Range Table. 1418 The purpose of this table is to provide a mechanism 1419 for specifying a contiguous range of vpi's 1420 with a contiguous range of vci's, or a 'label range' 1421 for LDP Entities. 1423 LDP Entities which use ATM must have at least one 1424 entry in this table." 1425 ::= { mplsLdpEntityAtmObjects 2 } 1427 mplsLdpEntityConfAtmLREntry OBJECT-TYPE 1428 SYNTAX MplsLdpEntityConfAtmLREntry 1429 MAX-ACCESS not-accessible 1430 STATUS current 1431 DESCRIPTION 1432 "A row in the LDP Entity Configurable ATM Label 1433 Range Table. One entry in this table contains 1434 information on a single range of labels 1435 represented by the configured Upper and Lower 1436 Bounds VPI/VCI pairs. These are the same 1437 data used in the Initialization Message. 1439 NOTE: The ranges for a specific LDP Entity 1440 are UNIQUE and non-overlapping. For example, 1441 for a specific LDP Entity index, there could 1442 be one entry having ConfLowerBound vpi/vci == 0/32, and 1443 ConfUpperBound vpi/vci == 0/100, and a second entry 1444 for this same interface with ConfLowerBound 1445 vpi/vci == 0/101 and ConfUpperBound vpi/vci == 0/200. 1446 However, there could not be a third entry with 1447 ConfLowerBound vpi/vci == 0/200 and 1448 ConfUpperBound vpi/vci == 0/300 because this label 1449 range overlaps with the second entry (i.e. both 1450 entries now have 0/200). 1452 A row will not be created unless a unique and 1453 non-overlapping range is specified. Thus, row 1454 creation implies a one-shot row creation of 1455 LDP EntityID and ConfLowerBound vpi/vci and 1456 ConfUpperBound vpi/vci. At least one label 1457 range entry for a specific LDP Entity MUST 1458 include the default VPI/VCI values denoted 1459 in the LDP Entity Table." 1460 INDEX { mplsLdpEntityLdpId, 1461 mplsLdpEntityIndex, 1462 mplsLdpEntityConfAtmLRMinVpi, 1463 mplsLdpEntityConfAtmLRMinVci 1464 } 1465 ::= { mplsLdpEntityConfAtmLRTable 1 } 1467 MplsLdpEntityConfAtmLREntry ::= SEQUENCE { 1468 mplsLdpEntityConfAtmLRMinVpi AtmVpIdentifier, 1469 mplsLdpEntityConfAtmLRMinVci MplsAtmVcIdentifier, 1470 mplsLdpEntityConfAtmLRMaxVpi AtmVpIdentifier, 1471 mplsLdpEntityConfAtmLRMaxVci MplsAtmVcIdentifier, 1472 mplsLdpEntityConfAtmLRStorType StorageType, 1473 mplsLdpEntityConfAtmLRRowStatus RowStatus 1474 } 1476 mplsLdpEntityConfAtmLRMinVpi OBJECT-TYPE 1477 SYNTAX AtmVpIdentifier 1478 MAX-ACCESS not-accessible 1479 STATUS current 1480 DESCRIPTION 1481 "The minimum VPI number configured for this range." 1482 ::= { mplsLdpEntityConfAtmLREntry 1 } 1484 mplsLdpEntityConfAtmLRMinVci OBJECT-TYPE 1485 SYNTAX MplsAtmVcIdentifier 1486 MAX-ACCESS not-accessible 1487 STATUS current 1488 DESCRIPTION 1489 "The minimum VCI number configured for this range." 1490 ::= { mplsLdpEntityConfAtmLREntry 2 } 1492 mplsLdpEntityConfAtmLRMaxVpi OBJECT-TYPE 1493 SYNTAX AtmVpIdentifier 1494 MAX-ACCESS read-create 1495 STATUS current 1496 DESCRIPTION 1497 "The maximum VPI number configured for this range." 1498 ::= { mplsLdpEntityConfAtmLREntry 3 } 1500 mplsLdpEntityConfAtmLRMaxVci OBJECT-TYPE 1501 SYNTAX MplsAtmVcIdentifier 1502 MAX-ACCESS read-create 1503 STATUS current 1504 DESCRIPTION 1505 "The maximum VCI number configured for this range." 1506 ::= { mplsLdpEntityConfAtmLREntry 4 } 1508 mplsLdpEntityConfAtmLRStorType OBJECT-TYPE 1509 SYNTAX StorageType 1510 MAX-ACCESS read-create 1511 STATUS current 1512 DESCRIPTION 1513 "The storage type for this entry." 1514 ::= { mplsLdpEntityConfAtmLREntry 5 } 1516 mplsLdpEntityConfAtmLRRowStatus OBJECT-TYPE 1517 SYNTAX RowStatus 1518 MAX-ACCESS read-create 1519 STATUS current 1520 DESCRIPTION 1521 "An object that allows entries in this 1522 table to be created and deleted using 1523 the RowStatus convention. 1525 There must exist at least one entry in this 1526 table for every LDP Entity that has 1527 'mplsLdpEntityOptionalParameters' object with 1528 a value of 'atmSessionParameters'. 1530 NOTE: This RowStatus object should 1531 have the same value of the 'mplsLdpEntityRowStatus' 1532 related to this entry." 1533 ::= { mplsLdpEntityConfAtmLREntry 6 } 1535 -- 1536 -- Ldp Entity Objects for Frame Relay 1537 -- 1539 mplsLdpEntityFrameRelayObjects OBJECT IDENTIFIER ::= 1540 { mplsLdpEntityObjects 5 } 1542 mplsLdpEntityFrParmsTable OBJECT-TYPE 1543 SYNTAX SEQUENCE OF MplsLdpEntityFrParmsEntry 1544 MAX-ACCESS not-accessible 1545 STATUS current 1546 DESCRIPTION 1547 "This table contains information about the 1548 Optional Parameters to specify what this Entity is 1549 going to specify for Frame Relay specific 1550 LDP Intialization Messages." 1551 ::= { mplsLdpEntityFrameRelayObjects 1 } 1553 mplsLdpEntityFrParmsEntry OBJECT-TYPE 1554 SYNTAX MplsLdpEntityFrParmsEntry 1555 MAX-ACCESS not-accessible 1556 STATUS current 1557 DESCRIPTION 1558 "An entry in this table represents the Frame Relay 1559 optional parameters associated with the LDP entity." 1560 INDEX { mplsLdpEntityLdpId, 1561 mplsLdpEntityIndex 1562 } 1563 ::= { mplsLdpEntityFrParmsTable 1 } 1565 MplsLdpEntityFrParmsEntry ::= SEQUENCE { 1566 mplsLdpEntityFrIfIndxOrZero InterfaceIndexOrZero, 1567 mplsLdpEntityFrMergeCap INTEGER, 1568 mplsLdpEntityFrLRComponents Unsigned32, 1569 mplsLdpEntityFrLen INTEGER, 1570 mplsLdpEntityFrVcDirectionality INTEGER, 1571 mplsLdpEntityFrParmsStorType StorageType, 1572 mplsLdpEntityFrParmsRowStatus RowStatus 1573 } 1575 mplsLdpEntityFrIfIndxOrZero OBJECT-TYPE 1576 SYNTAX InterfaceIndexOrZero 1577 MAX-ACCESS read-create 1578 STATUS current 1579 DESCRIPTION 1580 "This value represents either the InterfaceIndex of 1581 the 'ifLayer' where the Frame Relay Labels 'owned' by this 1582 entry were created, or 0 (zero). The value of zero 1583 means that the InterfaceIndex is not known. For example, 1584 if the InterfaceIndex is created subsequent to the 1585 Frame Relay Label's creation, then it would not be known. 1586 However, if the InterfaceIndex is known, then it must 1587 be represented by this value. 1589 If an InterfaceIndex becomes known, then the 1590 network management entity (e.g. SNMP agent) responsible 1591 for this object MUST change the value from 0 (zero) to the 1592 value of the InterfaceIndex. If an Frame Relay Label is 1593 being used in forwarding data, then the value of this 1594 object MUST be the InterfaceIndex." 1595 ::= { mplsLdpEntityFrParmsEntry 1 } 1597 mplsLdpEntityFrMergeCap OBJECT-TYPE 1598 SYNTAX INTEGER { 1599 notSupported(0), 1600 supported(1) 1601 } 1602 MAX-ACCESS read-create 1603 STATUS current 1604 DESCRIPTION 1605 "This represents whether or not Frame Relay merge 1606 capability is supported." 1607 ::= { mplsLdpEntityFrParmsEntry 2 } 1609 mplsLdpEntityFrLRComponents OBJECT-TYPE 1610 SYNTAX Unsigned32 (1..65535) 1611 MAX-ACCESS read-create 1612 STATUS current 1613 DESCRIPTION 1614 "Number of LabelRange Components in the Initialization 1615 message. This also represents the number of entries 1616 in the mplsLdpEntityConfFrLRTable which correspond 1617 to this entry." 1618 ::= { mplsLdpEntityFrParmsEntry 3 } 1620 mplsLdpEntityFrLen OBJECT-TYPE 1621 SYNTAX INTEGER { 1622 tenDlciBits(0), 1623 twentyThreeDlciBits(2) 1624 } 1625 MAX-ACCESS read-create 1626 STATUS current 1627 DESCRIPTION 1628 "This object specifies the DLCI bits." 1629 ::= { mplsLdpEntityFrParmsEntry 4 } 1631 mplsLdpEntityFrVcDirectionality OBJECT-TYPE 1632 SYNTAX INTEGER { 1633 bidirectional(0), 1634 unidirection(1) 1635 } 1636 MAX-ACCESS read-create 1637 STATUS current 1638 DESCRIPTION 1639 "If the value of this object is 'bidirectional(0)', then 1640 the LSR supports the use of a given DLCI as a label for 1641 both directions independently. If the value of 1642 this object is 'unidirectional(1)', then the LSR 1643 uses the given DLCI as a label in only one direction." 1644 ::= { mplsLdpEntityFrParmsEntry 5 } 1646 mplsLdpEntityFrParmsStorType OBJECT-TYPE 1647 SYNTAX StorageType 1648 MAX-ACCESS read-create 1649 STATUS current 1650 DESCRIPTION 1651 "The storage type for this entry." 1652 ::= { mplsLdpEntityFrParmsEntry 6 } 1654 mplsLdpEntityFrParmsRowStatus OBJECT-TYPE 1655 SYNTAX RowStatus 1656 MAX-ACCESS read-create 1657 STATUS current 1658 DESCRIPTION 1659 "An object that allows entries in this table to 1660 be created and deleted using the 1661 RowStatus convention. 1663 NOTE: This RowStatus object should 1664 have the same value of the 'mplsLdpEntityRowStatus' 1665 related to this entry." 1666 ::= { mplsLdpEntityFrParmsEntry 7 } 1668 -- 1669 -- Frame Relay Label Range Components 1670 -- 1672 mplsLdpEntityConfFrLRTable OBJECT-TYPE 1673 SYNTAX SEQUENCE OF MplsLdpEntityConfFrLREntry 1674 MAX-ACCESS not-accessible 1675 STATUS current 1676 DESCRIPTION 1677 "This table contains information about the 1678 Optional Parameters to specify what this Entity is 1679 going to specify for Frame Relay specific 1680 LDP Intialization Messages." 1681 ::= { mplsLdpEntityFrameRelayObjects 2 } 1683 mplsLdpEntityConfFrLREntry OBJECT-TYPE 1684 SYNTAX MplsLdpEntityConfFrLREntry 1685 MAX-ACCESS not-accessible 1686 STATUS current 1687 DESCRIPTION 1688 "An entry in this table represents the Frame Relay 1689 optional parameters associated with the LDP entity." 1690 INDEX { mplsLdpEntityLdpId, 1691 mplsLdpEntityIndex, 1692 mplsLdpConfFrMinDlci 1693 } 1694 ::= { mplsLdpEntityConfFrLRTable 1 } 1696 MplsLdpEntityConfFrLREntry ::= SEQUENCE { 1697 mplsLdpConfFrMinDlci Integer32, 1698 mplsLdpConfFrMaxDlci Integer32, 1699 mplsLdpConfFrStorType StorageType, 1700 mplsLdpConfFrRowStatus RowStatus 1701 } 1703 mplsLdpConfFrMinDlci OBJECT-TYPE 1704 SYNTAX Integer32(0..4194303) 1705 MAX-ACCESS not-accessible 1706 STATUS current 1707 DESCRIPTION 1708 "The lower bound which is supported. This value should 1709 be the same as that in the Frame Relay Label Range 1710 Component's Minimum DLCI field." 1711 ::= { mplsLdpEntityConfFrLREntry 1 } 1713 mplsLdpConfFrMaxDlci OBJECT-TYPE 1714 SYNTAX Integer32 (0..4194303) 1715 MAX-ACCESS read-create 1716 STATUS current 1717 DESCRIPTION 1718 "The upper bound which is supported. This value should 1719 be the same as that in the Frame Relay Label Range 1720 Component's Maximum DLCI field." 1721 ::= { mplsLdpEntityConfFrLREntry 2 } 1723 mplsLdpConfFrStorType OBJECT-TYPE 1724 SYNTAX StorageType 1725 MAX-ACCESS read-create 1726 STATUS current 1727 DESCRIPTION 1728 "The storage type for this entry." 1729 ::= { mplsLdpEntityConfFrLREntry 3 } 1731 mplsLdpConfFrRowStatus OBJECT-TYPE 1732 SYNTAX RowStatus 1733 MAX-ACCESS read-create 1734 STATUS current 1735 DESCRIPTION 1736 "An object that allows entries in this table to 1737 be created and deleted using the 1738 RowStatus convention. 1740 If the value of the object 1741 'mplsLdpEntityOptionalParameters' contains the 1742 value of 'frameRelaySessionParameters(3)' then 1743 there must be at least one corresponding entry 1744 in this table. 1746 NOTE: This RowStatus object should 1747 have the same value of the 'mplsLdpEntityRowStatus' 1748 related to this entry." 1749 ::= { mplsLdpEntityConfFrLREntry 4 } 1751 -- 1752 -- The MPLS LDP Entity Statistics Table 1753 -- 1755 mplsLdpEntityStatsTable OBJECT-TYPE 1756 SYNTAX SEQUENCE OF MplsLdpEntityStatsEntry 1757 MAX-ACCESS not-accessible 1758 STATUS current 1759 DESCRIPTION 1760 "This table is a read-only table which augments 1761 the mplsLdpEntityTable. The purpose of this 1762 table is to keep statistical information about 1763 the LDP Entities on the LSR." 1764 ::= { mplsLdpEntityObjects 6 } 1766 mplsLdpEntityStatsEntry OBJECT-TYPE 1767 SYNTAX MplsLdpEntityStatsEntry 1768 MAX-ACCESS not-accessible 1769 STATUS current 1770 DESCRIPTION 1771 "A row in this table contains statistical information 1772 about an LDP Entity. Some counters contained in a 1773 row are for fatal errors received during a former 1774 LDP Session associated with this entry. For example, 1775 an Ldp Pdu received on a TCP connection during an 1776 LDP Session contains a fatal error. That 1777 error is counted here, because the 1778 session is terminated. 1780 If the error is NOT fatal (i.e. and the Session 1781 remains), then the error is counted in the 1782 mplsLdpSesStatsEntry." 1783 AUGMENTS { mplsLdpEntityEntry } 1784 ::= { mplsLdpEntityStatsTable 1 } 1786 MplsLdpEntityStatsEntry ::= SEQUENCE { 1787 mplsLdpAttemptedSessions Counter32, 1788 mplsLdpSesRejectedNoHelloErrors Counter32, 1789 mplsLdpSesRejectedAdErrors Counter32, 1790 mplsLdpSesRejectedMaxPduErrors Counter32, 1791 mplsLdpSesRejectedLRErrors Counter32, 1792 mplsLdpBadLdpIdentifierErrors Counter32, 1793 mplsLdpBadPduLengthErrors Counter32, 1794 mplsLdpBadMessageLengthErrors Counter32, 1795 mplsLdpBadTlvLengthErrors Counter32, 1796 mplsLdpMalformedTlvValueErrors Counter32, 1797 mplsLdpKeepAliveTimerExpErrors Counter32, 1798 mplsLdpShutdownNotifReceived Counter32, 1799 mplsLdpShutdownNotifSent Counter32 1800 } 1802 mplsLdpAttemptedSessions OBJECT-TYPE 1803 SYNTAX Counter32 1804 MAX-ACCESS read-only 1805 STATUS current 1806 DESCRIPTION 1807 "A count of the total attempted sessions for 1808 this LDP Entity." 1809 ::= { mplsLdpEntityStatsEntry 1 } 1811 mplsLdpSesRejectedNoHelloErrors OBJECT-TYPE 1812 SYNTAX Counter32 1813 MAX-ACCESS read-only 1814 STATUS current 1815 DESCRIPTION 1816 "A count of the Session Rejected/No Hello Error 1817 Notification Messages sent or received by 1818 this LDP Entity." 1819 ::= { mplsLdpEntityStatsEntry 2 } 1821 mplsLdpSesRejectedAdErrors OBJECT-TYPE 1822 SYNTAX Counter32 1823 MAX-ACCESS read-only 1824 STATUS current 1825 DESCRIPTION 1826 "A count of the Session Rejected/Parameters 1827 Advertisement Mode Error Notification Messages sent 1828 or received by this LDP Entity." 1829 ::= { mplsLdpEntityStatsEntry 3 } 1831 mplsLdpSesRejectedMaxPduErrors OBJECT-TYPE 1832 SYNTAX Counter32 1833 MAX-ACCESS read-only 1834 STATUS current 1835 DESCRIPTION 1836 "A count of the Session Rejected/Parameters 1837 Max Pdu Length Error Notification Messages sent 1838 or received by this LDP Entity." 1839 ::= { mplsLdpEntityStatsEntry 4 } 1841 mplsLdpSesRejectedLRErrors OBJECT-TYPE 1842 SYNTAX Counter32 1843 MAX-ACCESS read-only 1844 STATUS current 1845 DESCRIPTION 1846 "A count of the Session Rejected/Parameters 1847 Label Range Notification Messages sent 1848 or received by this LDP Entity." 1849 ::= { mplsLdpEntityStatsEntry 5 } 1851 mplsLdpBadLdpIdentifierErrors OBJECT-TYPE 1852 SYNTAX Counter32 1853 MAX-ACCESS read-only 1854 STATUS current 1855 DESCRIPTION 1856 "This object counts the number of Bad LDP Identifier 1857 Fatal Errors detected by the session(s) 1858 (past and present) associated with this LDP Entity." 1860 REFERENCE 1861 "LDP Specification, Section 3.5.1.2." 1862 ::= { mplsLdpEntityStatsEntry 6 } 1864 mplsLdpBadPduLengthErrors OBJECT-TYPE 1865 SYNTAX Counter32 1866 MAX-ACCESS read-only 1867 STATUS current 1868 DESCRIPTION 1869 "This object counts the number of Bad Pdu Length 1870 Fatal Errors detected by the session(s) 1871 (past and present) associated with this LDP Entity." 1872 REFERENCE 1873 "LDP Specification, Section 3.5.1.2." 1874 ::= { mplsLdpEntityStatsEntry 7 } 1876 mplsLdpBadMessageLengthErrors OBJECT-TYPE 1877 SYNTAX Counter32 1878 MAX-ACCESS read-only 1879 STATUS current 1880 DESCRIPTION 1881 "This object counts the number of Bad Message 1882 Length Fatal Errors detected by the session(s) 1883 (past and present) associated with this LDP Entity." 1884 REFERENCE 1885 "LDP Specification, Section 3.5.1.2." 1886 ::= { mplsLdpEntityStatsEntry 8 } 1888 mplsLdpBadTlvLengthErrors OBJECT-TYPE 1889 SYNTAX Counter32 1890 MAX-ACCESS read-only 1891 STATUS current 1892 DESCRIPTION 1893 "This object counts the number of Bad TLV 1894 Length Fatal Errors detected by the session(s) 1895 (past and present) associated with this LDP Entity." 1896 REFERENCE 1897 "LDP Specification, Section 3.5.1.2." 1898 ::= { mplsLdpEntityStatsEntry 9 } 1900 mplsLdpMalformedTlvValueErrors OBJECT-TYPE 1901 SYNTAX Counter32 1902 MAX-ACCESS read-only 1903 STATUS current 1904 DESCRIPTION 1905 "This object counts the number of Malformed TLV 1906 Value Fatal Errors detected by the session(s) 1907 (past and present) associated with this 1908 LDP Entity." 1909 REFERENCE 1910 "LDP Specification, Section 3.5.1.2." 1911 ::= { mplsLdpEntityStatsEntry 10 } 1913 mplsLdpKeepAliveTimerExpErrors OBJECT-TYPE 1914 SYNTAX Counter32 1915 MAX-ACCESS read-only 1916 STATUS current 1917 DESCRIPTION 1918 "This object counts the number of Session Keep Alive 1919 Timer Expired Errors detected by the session(s) 1920 (past and present) associated with this LDP Entity." 1921 REFERENCE 1922 "LDP Specification, Section 3.5.1.2." 1923 ::= { mplsLdpEntityStatsEntry 11 } 1925 mplsLdpShutdownNotifReceived OBJECT-TYPE 1926 SYNTAX Counter32 1927 MAX-ACCESS read-only 1928 STATUS current 1929 DESCRIPTION 1930 "This object counts the number of Shutdown Notfications 1931 received related to session(s) (past and present) 1932 associated with this LDP Entity." 1933 ::= { mplsLdpEntityStatsEntry 12 } 1935 mplsLdpShutdownNotifSent OBJECT-TYPE 1936 SYNTAX Counter32 1937 MAX-ACCESS read-only 1938 STATUS current 1939 DESCRIPTION 1940 "This object counts the number of Shutdown Notfications 1941 sent related to session(s) (past and present) associated 1942 with this LDP Entity." 1943 ::= { mplsLdpEntityStatsEntry 13 } 1945 -- 1946 -- The MPLS LDP Peer Table 1947 -- 1949 mplsLdpSessionObjects OBJECT IDENTIFIER ::= 1950 { mplsLdpObjects 3 } 1952 mplsLdpPeerTable OBJECT-TYPE 1953 SYNTAX SEQUENCE OF MplsLdpPeerEntry 1954 MAX-ACCESS not-accessible 1955 STATUS current 1956 DESCRIPTION 1957 "Information about LDP peers known by Entities in 1958 the mplsLdpEntityTable. The information in this table 1959 is based on information from the Entity-Peer interaction 1960 during session initialization but is not appropriate 1961 for the mplsLdpSessionTable, because objects in this 1962 table may or may not be used in session establishment." 1963 ::= { mplsLdpSessionObjects 1 } 1965 mplsLdpPeerEntry OBJECT-TYPE 1966 SYNTAX MplsLdpPeerEntry 1967 MAX-ACCESS not-accessible 1968 STATUS current 1969 DESCRIPTION 1970 "Information about a single Peer which is related 1971 to a Session. NOTE: this table is augmented by 1972 the mplsLdpSessionTable." 1973 INDEX { mplsLdpEntityLdpId, 1974 mplsLdpEntityIndex, 1975 mplsLdpPeerLdpId } 1976 ::= { mplsLdpPeerTable 1 } 1978 MplsLdpPeerEntry ::= SEQUENCE { 1979 mplsLdpPeerLdpId MplsLdpIdentifier, 1980 mplsLdpPeerLabelDistMethod INTEGER, 1981 mplsLdpPeerLoopDetectionForPV INTEGER, 1982 mplsLdpPeerPVL Integer32 1983 } 1985 mplsLdpPeerLdpId OBJECT-TYPE 1986 SYNTAX MplsLdpIdentifier 1987 MAX-ACCESS not-accessible 1988 STATUS current 1989 DESCRIPTION 1990 "The LDP identifier of this LDP Peer." 1991 ::= { mplsLdpPeerEntry 1 } 1993 mplsLdpPeerLabelDistMethod OBJECT-TYPE 1994 SYNTAX INTEGER { 1995 downstreamOnDemand(1), 1996 downstreamUnsolicited(2) 1997 } 1998 MAX-ACCESS read-only 1999 STATUS current 2000 DESCRIPTION 2001 "For any given LDP session, the method of 2002 label distribution must be specified." 2003 ::= { mplsLdpPeerEntry 2 } 2005 mplsLdpPeerLoopDetectionForPV OBJECT-TYPE 2006 SYNTAX INTEGER { 2007 disabled(0), 2008 enabled(1) 2010 } 2011 MAX-ACCESS read-only 2012 STATUS current 2013 DESCRIPTION 2014 "An indication of whether loop detection based 2015 on path vectors is disabled or enabled for this Peer. 2017 If this object has a value of disabled(0), 2018 then loop detection is disabled. Otherwise, if this 2019 object has a value of enabled(1), then loop detection 2020 based on path vectors is enabled." 2021 ::= { mplsLdpPeerEntry 3 } 2023 mplsLdpPeerPVL OBJECT-TYPE 2024 SYNTAX Integer32 (0..255) 2025 MAX-ACCESS read-only 2026 STATUS current 2027 DESCRIPTION 2028 "If the value of 'mplsLdpPeerLoopDetectionForPV' for 2029 this entry is 'enabled(1)', the this object represents 2030 that Path Vector Limit for this peer. 2032 If the value of 'mplsLdpPeerLoopDetectionForPV' for 2033 this entry is 'disabled(0)', then this value should 2034 be 0 (zero)." 2035 ::= { mplsLdpPeerEntry 4 } 2037 -- 2038 -- The MPLS LDP Hello Adjacency Table 2039 -- 2041 mplsLdpHelloAdjacencyObjects OBJECT IDENTIFIER ::= 2042 { mplsLdpSessionObjects 2 } 2044 mplsLdpHelloAdjacencyTable OBJECT-TYPE 2045 SYNTAX SEQUENCE OF MplsLdpHelloAdjacencyEntry 2046 MAX-ACCESS not-accessible 2047 STATUS current 2048 DESCRIPTION 2049 "A table of Hello Adjacencies for Sessions." 2050 ::= { mplsLdpHelloAdjacencyObjects 1 } 2052 mplsLdpHelloAdjacencyEntry OBJECT-TYPE 2053 SYNTAX MplsLdpHelloAdjacencyEntry 2054 MAX-ACCESS not-accessible 2055 STATUS current 2056 DESCRIPTION 2057 "Each row represents a single LDP Hello Adjacency. 2058 An LDP Session can have one or more Hello adjacencies." 2059 INDEX { mplsLdpEntityLdpId, 2060 mplsLdpEntityIndex, 2061 mplsLdpPeerLdpId, 2062 mplsLdpHelloAdjIndex } 2063 ::= { mplsLdpHelloAdjacencyTable 1 } 2065 MplsLdpHelloAdjacencyEntry ::= SEQUENCE { 2066 mplsLdpHelloAdjIndex Unsigned32, 2067 mplsLdpHelloAdjHoldTimeRem TimeInterval, 2068 mplsLdpHelloAdjType INTEGER 2069 } 2071 mplsLdpHelloAdjIndex OBJECT-TYPE 2072 SYNTAX Unsigned32 (1..4294967295) 2073 MAX-ACCESS not-accessible 2074 STATUS current 2075 DESCRIPTION 2076 "An identifier for this specific adjacency." 2077 ::= { mplsLdpHelloAdjacencyEntry 1 } 2079 mplsLdpHelloAdjHoldTimeRem OBJECT-TYPE 2080 SYNTAX TimeInterval 2081 MAX-ACCESS read-only 2082 STATUS current 2083 DESCRIPTION 2084 "The time remaining for this Hello Adjacency. 2085 This interval will change when the 'next' 2086 Hello message which corresponds to this 2087 Hello Adjacency is received." 2088 ::= { mplsLdpHelloAdjacencyEntry 2 } 2090 mplsLdpHelloAdjType OBJECT-TYPE 2091 SYNTAX INTEGER { 2092 link(1), 2093 targeted(2) 2094 } 2095 MAX-ACCESS read-only 2096 STATUS current 2097 DESCRIPTION 2098 "This adjacency is the result of a 'link' 2099 hello if the value of this object is link(1). 2100 Otherwise, it is a result of a 'targeted' 2101 hello, targeted(2)." 2102 ::= { mplsLdpHelloAdjacencyEntry 3 } 2104 -- 2105 -- The MPLS LDP Sessions Table 2106 -- 2108 mplsLdpSesUpDownTrapEnable OBJECT-TYPE 2109 SYNTAX INTEGER { 2110 enabled(1), 2111 disabled(2) 2112 } 2113 MAX-ACCESS read-write 2114 STATUS current 2115 DESCRIPTION 2116 "Indicates whether the traps, 'mplsLdpSesUp' and 2117 'mplsLdpSesDown' will be generated or not. 2119 If the value of this object is 'enabled(1)' 2120 then the traps will generated. If the value 2121 of this object is 'disabled(2)' then the 2122 traps will not be generated. The DEFVAL 2123 is set to 'disabled(2)'." 2124 DEFVAL { disabled } 2125 ::= { mplsLdpSessionObjects 3 } 2127 mplsLdpSessionTable OBJECT-TYPE 2128 SYNTAX SEQUENCE OF MplsLdpSessionEntry 2129 MAX-ACCESS not-accessible 2130 STATUS current 2131 DESCRIPTION 2132 "A table of Sessions between the LDP Entities and 2133 LDP Peers. Each row represents a single session." 2134 ::= { mplsLdpSessionObjects 4 } 2136 mplsLdpSessionEntry OBJECT-TYPE 2137 SYNTAX MplsLdpSessionEntry 2138 MAX-ACCESS not-accessible 2139 STATUS current 2140 DESCRIPTION 2141 "An entry in this table represents information on a 2142 single session between an LDP Entity and LDP Peer. 2143 The information contained in a row is read-only. 2145 Please note: the Path Vector Limit for the 2146 Session is the value which is configured in 2147 the corresponding mplsLdpEntityEntry. The 2148 Peer's Path Vector Limit is in noted in the 2149 mplsLdpPeerTable. 2151 Values which may differ from those configured are 2152 noted in the objects of this table, the 2153 mplsLdpAtmSessionTable and the 2154 mplsLdpFrameRelaySessionTable. A value will 2155 differ if it was negotiated between the 2156 Entity and the Peer. Values may or may not 2157 be negotiated. For example, if the values 2158 are the same then no negotiation takes place. 2159 If they are negotiated, then they may differ." 2160 AUGMENTS { mplsLdpPeerEntry } 2161 ::= { mplsLdpSessionTable 1 } 2163 MplsLdpSessionEntry ::= SEQUENCE { 2164 mplsLdpSesState INTEGER, 2165 mplsLdpSesProtocolVersion Integer32, 2166 mplsLdpSesKeepAliveHoldTimeRem TimeInterval, 2167 mplsLdpSesMaxPduLen Unsigned32, 2168 mplsLdpSesDiscontinuityTime TimeStamp 2169 } 2171 mplsLdpSesState OBJECT-TYPE 2172 SYNTAX INTEGER { 2173 nonexistent(1), 2174 initialized(2), 2175 openrec(3), 2176 opensent(4), 2177 operational(5) 2178 } 2179 MAX-ACCESS read-only 2180 STATUS current 2181 DESCRIPTION 2182 "The current state of the session, all of the 2183 states 1 - 5 are based on the state machine for 2184 session negotiation behavior." 2185 ::= { mplsLdpSessionEntry 1 } 2187 mplsLdpSesProtocolVersion OBJECT-TYPE 2188 SYNTAX Integer32(1..65535) 2189 MAX-ACCESS read-only 2190 STATUS current 2191 DESCRIPTION 2192 "The version of the LDP Protocol which 2193 this session is using. This is the version of 2194 the LDP protocol which has been negotiated during 2195 session initialization." 2196 REFERENCE 2197 "RFC 3036, LDP Specification, Section 3.5.3 Initialization 2198 Message." 2199 ::= { mplsLdpSessionEntry 2 } 2201 mplsLdpSesKeepAliveHoldTimeRem OBJECT-TYPE 2202 SYNTAX TimeInterval 2203 MAX-ACCESS read-only 2204 STATUS current 2205 DESCRIPTION 2206 "The keep alive hold time remaining for this session." 2207 ::= { mplsLdpSessionEntry 3 } 2209 mplsLdpSesMaxPduLen OBJECT-TYPE 2210 SYNTAX Unsigned32 (1..65535) 2211 MAX-ACCESS read-only 2212 STATUS current 2213 DESCRIPTION 2214 "The value of maximum allowable length for LDP PDUs for 2215 this session. This value may have been negotiated during 2216 the Session Initialization." 2217 ::= { mplsLdpSessionEntry 4 } 2219 mplsLdpSesDiscontinuityTime OBJECT-TYPE 2220 SYNTAX TimeStamp 2221 MAX-ACCESS read-only 2222 STATUS current 2223 DESCRIPTION 2224 "The value of sysUpTime on the most recent occasion at 2225 which any one or more of this session's counters 2226 suffered a discontinuity. The relevant counters are 2227 the specific instances associated with this session 2228 of any Counter32 or Counter64 object contained in the 2229 mplsLdpSessionStatsTable. 2231 The initial value of this object is the value of 2232 sysUpTime when the entry was created in this table. 2234 Also, an NMS can distinguish when a session 2235 between a given Entity and Peer goes away and then is 2236 're-established'. This value would change and 2237 thus indicate to the NMS that this is a 2238 different session." 2239 ::= { mplsLdpSessionEntry 5 } 2241 -- 2242 -- MPLS LDP ATM Session Information 2243 -- 2245 mplsLdpAtmSesTable OBJECT-TYPE 2246 SYNTAX SEQUENCE OF MplsLdpAtmSesEntry 2247 MAX-ACCESS not-accessible 2248 STATUS current 2249 DESCRIPTION 2250 "A table which relates Sessions in the 2251 'mplsLdpSessionTable' and their label 2252 range intersections. There could be one 2253 or more label range intersections between an 2254 LDP Entity and LDP Peer using ATM as the underlying 2255 media. Each row represents a single label range 2256 intersection. 2258 NOTE: this table cannot use the 'AUGMENTS' 2259 clause because there is not necessarily a one-to-one 2260 mapping between this table and the mplsLdpSessionTable." 2261 ::= { mplsLdpSessionObjects 5 } 2263 mplsLdpAtmSesEntry OBJECT-TYPE 2264 SYNTAX MplsLdpAtmSesEntry 2265 MAX-ACCESS not-accessible 2266 STATUS current 2267 DESCRIPTION 2268 "An entry in this table represents information on a 2269 single label range intersection between an LDP Entity 2270 and LDP Peer. 2272 The information contained in a row is read-only." 2273 INDEX { mplsLdpEntityLdpId, 2274 mplsLdpEntityIndex, 2275 mplsLdpPeerLdpId, 2276 mplsLdpSesAtmLRLowerBoundVpi, 2277 mplsLdpSesAtmLRLowerBoundVci 2279 } 2280 ::= { mplsLdpAtmSesTable 1 } 2282 MplsLdpAtmSesEntry ::= SEQUENCE { 2283 mplsLdpSesAtmLRLowerBoundVpi AtmVpIdentifier, 2284 mplsLdpSesAtmLRLowerBoundVci MplsAtmVcIdentifier, 2285 mplsLdpSesAtmLRUpperBoundVpi AtmVpIdentifier, 2286 mplsLdpSesAtmLRUpperBoundVci MplsAtmVcIdentifier 2287 } 2289 mplsLdpSesAtmLRLowerBoundVpi OBJECT-TYPE 2290 SYNTAX AtmVpIdentifier 2291 MAX-ACCESS not-accessible 2292 STATUS current 2293 DESCRIPTION 2294 "The minimum VPI number for this range." 2295 ::= { mplsLdpAtmSesEntry 1 } 2297 mplsLdpSesAtmLRLowerBoundVci OBJECT-TYPE 2298 SYNTAX MplsAtmVcIdentifier 2299 MAX-ACCESS not-accessible 2300 STATUS current 2301 DESCRIPTION 2302 "The minimum VCI number for this range." 2304 ::= { mplsLdpAtmSesEntry 2 } 2306 mplsLdpSesAtmLRUpperBoundVpi OBJECT-TYPE 2307 SYNTAX AtmVpIdentifier 2308 MAX-ACCESS read-only 2309 STATUS current 2310 DESCRIPTION 2311 "The maximum VPI number for this range." 2312 ::= { mplsLdpAtmSesEntry 3 } 2314 mplsLdpSesAtmLRUpperBoundVci OBJECT-TYPE 2315 SYNTAX MplsAtmVcIdentifier 2316 MAX-ACCESS read-only 2317 STATUS current 2318 DESCRIPTION 2319 "The maximum VCI number for this range." 2320 ::= { mplsLdpAtmSesEntry 4 } 2322 -- 2323 -- MPLS LDP Frame Relay Session Information 2324 -- 2326 mplsLdpFrameRelaySesTable OBJECT-TYPE 2327 SYNTAX SEQUENCE OF MplsLdpFrameRelaySesEntry 2328 MAX-ACCESS not-accessible 2329 STATUS current 2330 DESCRIPTION 2331 "A table of Frame Relay label range intersections 2332 between the LDP Entities and LDP Peers. 2333 Each row represents a single label range intersection. 2335 NOTE: this table cannot use the 'AUGMENTS' 2336 clause because there is not necessarily a one-to-one 2337 mapping between this table and the mplsLdpSessionTable." 2338 ::= { mplsLdpSessionObjects 6 } 2340 mplsLdpFrameRelaySesEntry OBJECT-TYPE 2341 SYNTAX MplsLdpFrameRelaySesEntry 2342 MAX-ACCESS not-accessible 2343 STATUS current 2344 DESCRIPTION 2345 "An entry in this table represents information on a 2346 single label range intersection between an 2347 LDP Entity and LDP Peer. 2349 The information contained in a row is read-only." 2350 INDEX { mplsLdpEntityLdpId, 2351 mplsLdpEntityIndex, 2352 mplsLdpPeerLdpId, 2353 mplsLdpFrSesMinDlci 2354 } 2355 ::= { mplsLdpFrameRelaySesTable 1 } 2357 MplsLdpFrameRelaySesEntry ::= SEQUENCE { 2358 mplsLdpFrSesMinDlci Integer32, 2359 mplsLdpFrSesMaxDlci Integer32, 2360 mplsLdpFrSesLen INTEGER 2361 } 2363 mplsLdpFrSesMinDlci OBJECT-TYPE 2364 SYNTAX Integer32(0..4194303) 2365 MAX-ACCESS not-accessible 2366 STATUS current 2367 DESCRIPTION 2368 "The lower bound of DLCIs which are supported." 2369 ::= { mplsLdpFrameRelaySesEntry 1 } 2371 mplsLdpFrSesMaxDlci OBJECT-TYPE 2372 SYNTAX Integer32 (0..4194303) 2373 MAX-ACCESS read-only 2374 STATUS current 2375 DESCRIPTION 2376 "The upper bound of DLCIs which are supported." 2377 ::= { mplsLdpFrameRelaySesEntry 2 } 2379 mplsLdpFrSesLen OBJECT-TYPE 2380 SYNTAX INTEGER { 2381 tenDlciBits(0), 2382 twentyThreeDlciBits(2) 2383 } 2384 MAX-ACCESS read-only 2385 STATUS current 2386 DESCRIPTION 2387 "This object specifies the DLCI bits." 2388 ::= { mplsLdpFrameRelaySesEntry 3 } 2390 -- 2391 -- The MPLS LDP Session Statistics Table 2392 -- 2394 mplsLdpSesStatsTable OBJECT-TYPE 2395 SYNTAX SEQUENCE OF MplsLdpSesStatsEntry 2396 MAX-ACCESS not-accessible 2397 STATUS current 2398 DESCRIPTION 2399 "A table of statistics for Sessions between 2400 LDP Entities and LDP Peers." 2401 ::= { mplsLdpSessionObjects 7 } 2403 mplsLdpSesStatsEntry OBJECT-TYPE 2404 SYNTAX MplsLdpSesStatsEntry 2405 MAX-ACCESS not-accessible 2406 STATUS current 2407 DESCRIPTION 2408 "An entry in this table represents statistical 2409 information on a single session between an LDP 2410 Entity and LDP Peer." 2411 AUGMENTS { mplsLdpPeerEntry } 2412 ::= { mplsLdpSesStatsTable 1 } 2414 MplsLdpSesStatsEntry ::= SEQUENCE { 2415 mplsLdpSesStatsUnkMesTypeErrors Counter32, 2416 mplsLdpSesStatsUnkTlvErrors Counter32 2417 } 2419 mplsLdpSesStatsUnkMesTypeErrors OBJECT-TYPE 2420 SYNTAX Counter32 2421 MAX-ACCESS read-only 2422 STATUS current 2423 DESCRIPTION 2424 "This object counts the number of Unknown Message Type 2425 Errors detected during this session. 2427 Discontinuities in the value of this counter can occur 2428 at re-initialization of the management system, and at 2429 other times as indicated by the value of 2430 mplsLdpSesDiscontinuityTime." 2431 ::= { mplsLdpSesStatsEntry 1 } 2433 mplsLdpSesStatsUnkTlvErrors OBJECT-TYPE 2434 SYNTAX Counter32 2435 MAX-ACCESS read-only 2436 STATUS current 2437 DESCRIPTION 2438 "This object counts the number of Unknown TLV Errors 2439 detected during this session. 2441 Discontinuities in the value of this counter can occur 2442 at re-initialization of the management system, and at 2443 other times as indicated by the value of 2444 mplsLdpSessionDiscontinuityTime." 2445 ::= { mplsLdpSesStatsEntry 2 } 2447 -- 2448 -- Mpls FEC Table 2449 -- 2451 mplsFecObjects OBJECT IDENTIFIER ::= 2452 { mplsLdpSessionObjects 8 } 2454 mplsFecIndexNext OBJECT-TYPE 2455 SYNTAX Unsigned32 (0..4294967295) 2456 MAX-ACCESS read-only 2457 STATUS current 2458 DESCRIPTION 2459 "This object contains an appropriate value to 2460 be used for mplsFecIndex when creating 2461 entries in the mplsFecTable. The value 2462 0 indicates that no unassigned entries are 2463 available. To obtain the mplsFecIndex 2464 value for a new entry, the manager issues a 2465 management protocol retrieval operation to obtain 2466 the current value of this object. After each 2467 retrieval, the agent should modify the value to 2468 the next unassigned index." 2469 ::= { mplsFecObjects 1 } 2471 mplsFecTable OBJECT-TYPE 2472 SYNTAX SEQUENCE OF MplsFecEntry 2473 MAX-ACCESS not-accessible 2474 STATUS current 2475 DESCRIPTION 2476 "This table represents the FEC 2477 (Forwarding Equivalence Class) 2478 Information associated with an LSP." 2479 ::= { mplsFecObjects 2 } 2481 mplsFecEntry OBJECT-TYPE 2482 SYNTAX MplsFecEntry 2483 MAX-ACCESS not-accessible 2484 STATUS current 2485 DESCRIPTION 2486 "Each row represents a single FEC Element." 2487 INDEX { mplsFecIndex } 2488 ::= { mplsFecTable 1 } 2490 MplsFecEntry ::= SEQUENCE { 2491 mplsFecIndex Unsigned32, 2492 mplsFecType INTEGER, 2493 mplsFecAddrLength Integer32, 2494 mplsFecAddrFamily AddressFamilyNumbers, 2495 mplsFecAddr MplsLdpGenAddr, 2496 mplsFecStorType StorageType, 2497 mplsFecRowStatus RowStatus 2498 } 2500 mplsFecIndex OBJECT-TYPE 2501 SYNTAX Unsigned32(1..4294967295) 2502 MAX-ACCESS not-accessible 2503 STATUS current 2504 DESCRIPTION 2505 "The index which uniquely identifies this entry." 2506 ::= { mplsFecEntry 1 } 2508 mplsFecType OBJECT-TYPE 2509 SYNTAX INTEGER { 2510 prefix(1), 2511 hostAddress(2) 2512 } 2513 MAX-ACCESS read-create 2514 STATUS current 2515 DESCRIPTION 2516 "The type of the FEC. If the value of this object 2517 is 'prefix(1)' then the FEC type described by this 2518 row is for address prefixes. 2520 If the value of this object is 'hostAddress(2)' then 2521 the FEC type described by this row is a host address." 2522 ::= { mplsFecEntry 2 } 2524 mplsFecAddrLength OBJECT-TYPE 2525 SYNTAX Integer32(0..255) 2526 MAX-ACCESS read-create 2527 STATUS current 2528 DESCRIPTION 2529 "If the value of 'mplsFecType' is 'prefix(1)' 2530 then the value of this object is the length in 2531 bits of the address prefix represented by 2532 'mplsFecAddr', or if the length is zero then 2533 this is a special value which indicates that the 2534 prefix matches all addresses. In this case the 2535 prefix is also zero (i.e. 'mplsFecAddr' will 2536 have the value of zero.)" 2537 ::= { mplsFecEntry 3 } 2539 mplsFecAddrFamily OBJECT-TYPE 2540 SYNTAX AddressFamilyNumbers 2541 MAX-ACCESS read-create 2542 STATUS current 2543 DESCRIPTION 2544 "The value of this object is from the Address Family 2545 Numbers." 2547 ::= { mplsFecEntry 4 } 2549 mplsFecAddr OBJECT-TYPE 2550 SYNTAX MplsLdpGenAddr 2551 MAX-ACCESS read-create 2552 STATUS current 2553 DESCRIPTION 2554 "If the value of 'mplsFecType' is 'prefix(1)' 2555 then the value of this object is the address prefix. 2556 If the value of the 'mplsFecAddrLength' 2557 is object is zero, then this object should also be 2558 zero. 2560 If the value of the 'mplsFecType' is 'host(2)' 2561 then this is the host address." 2562 ::= { mplsFecEntry 5 } 2564 mplsFecStorType OBJECT-TYPE 2565 SYNTAX StorageType 2566 MAX-ACCESS read-create 2567 STATUS current 2568 DESCRIPTION 2569 "The storage type for this entry." 2570 ::= { mplsFecEntry 6 } 2572 mplsFecRowStatus OBJECT-TYPE 2573 SYNTAX RowStatus 2574 MAX-ACCESS read-create 2575 STATUS current 2576 DESCRIPTION 2577 "An object that allows entries in this table to 2578 be created and deleted using the 2579 RowStatus convention." 2580 ::= { mplsFecEntry 7 } 2582 -- 2583 -- Mapping Tables between Sessions and the LSR MIB. 2584 -- 2586 -- 2587 -- SessionInLabels and InSegment 2588 -- 2590 mplsLdpSesInLabelMapTable OBJECT-TYPE 2591 SYNTAX SEQUENCE OF MplsLdpSesInLabelMapEntry 2592 MAX-ACCESS not-accessible 2593 STATUS current 2594 DESCRIPTION 2595 "A table of Session's Ingress Labels which 2596 are Mapped to the LSR MIB's mplsInSegmentTable. 2597 Each row represents a single Ingress Label." 2598 ::= { mplsLdpSessionObjects 9 } 2600 mplsLdpSesInLabelMapEntry OBJECT-TYPE 2601 SYNTAX MplsLdpSesInLabelMapEntry 2602 MAX-ACCESS not-accessible 2603 STATUS current 2604 DESCRIPTION 2605 "An entry in this table represents information on a 2606 single LDP LSP which is represented by 2607 a session's index triple (mplsLdpEntityLdpId, 2608 mplsLdpEntityIndex, mplsLdpPeerLdpId) AND the 2609 index tuple (mplsLdpSessionInLabel, mplsInSegmentIfIndex) 2610 from the LSR MIB's mplsInSegmentTable. 2611 The information contained in a row is read-only." 2612 INDEX { mplsLdpEntityLdpId, 2613 mplsLdpEntityIndex, 2614 mplsLdpPeerLdpId, 2615 mplsLdpSesInLabelIfIndex, 2616 mplsLdpSesInLabel 2617 } 2618 ::= { mplsLdpSesInLabelMapTable 1 } 2620 MplsLdpSesInLabelMapEntry ::= SEQUENCE { 2621 mplsLdpSesInLabelIfIndex InterfaceIndex, 2622 mplsLdpSesInLabel MplsLabel, 2623 mplsLdpSesInLabelType MplsLdpLabelTypes, 2624 mplsLdpSesInLabelConnType INTEGER 2625 } 2627 mplsLdpSesInLabelIfIndex OBJECT-TYPE 2628 SYNTAX InterfaceIndex 2629 MAX-ACCESS not-accessible 2630 STATUS current 2631 DESCRIPTION 2632 "The ifIndex of the 'mplsLdpSesInLabel' which should 2633 have the same value as the 'mplsInSegmentIfIndex' in 2634 the LSR MIB." 2635 ::= { mplsLdpSesInLabelMapEntry 1 } 2637 mplsLdpSesInLabel OBJECT-TYPE 2638 SYNTAX MplsLabel 2639 MAX-ACCESS not-accessible 2640 STATUS current 2641 DESCRIPTION 2642 "The incoming label of this LSP. This has the same value 2643 as the 'mplsInSegmentLabel' in the LSR MIB." 2645 ::= { mplsLdpSesInLabelMapEntry 2 } 2647 mplsLdpSesInLabelType OBJECT-TYPE 2648 SYNTAX MplsLdpLabelTypes 2649 MAX-ACCESS read-only 2650 STATUS current 2651 DESCRIPTION 2652 "The Layer 2 Label Type for 'mplsLdpInLabel'." 2653 ::= { mplsLdpSesInLabelMapEntry 3 } 2655 mplsLdpSesInLabelConnType OBJECT-TYPE 2656 SYNTAX INTEGER { 2657 unknown(1), 2658 xconnect(2), 2659 terminates(3) 2660 } 2661 MAX-ACCESS read-only 2662 STATUS current 2663 DESCRIPTION 2664 "The type of LSP connection. 2665 The possible values are: 2667 unknown(1) -- this may be the value if the LSP 2668 is in a state of flux. It is 2669 considered to be a temporary 2670 situation. 2671 xconnect(2) -- if the mapping between the 2672 session and the insegment 2673 is associated with an LSP which 2674 is a true cross-connection. 2675 terminates(3) -- if the mapping between the 2676 session and the insegment 2677 is associated with an LSP which 2678 terminates on this LSR and is 2679 not a cross-connection." 2680 ::= { mplsLdpSesInLabelMapEntry 4 } 2682 -- 2683 -- SessionOutLabels and OutSegment 2684 -- 2686 mplsLdpSesOutLabelMapTable OBJECT-TYPE 2687 SYNTAX SEQUENCE OF MplsLdpSesOutLabelMapEntry 2688 MAX-ACCESS not-accessible 2689 STATUS current 2690 DESCRIPTION 2691 "A table of Session's Egress Labels which 2692 are Mapped to the LSR MIB. 2693 Each row represents a single Egress Label." 2695 ::= { mplsLdpSessionObjects 10 } 2697 mplsLdpSesOutLabelMapEntry OBJECT-TYPE 2698 SYNTAX MplsLdpSesOutLabelMapEntry 2699 MAX-ACCESS not-accessible 2700 STATUS current 2701 DESCRIPTION 2702 "An entry in this table represents information on a 2703 single session between an LDP Entity and LDP Peer. 2704 The information contained in a row is read-only." 2705 INDEX { mplsLdpEntityLdpId, 2706 mplsLdpEntityIndex, 2707 mplsLdpPeerLdpId, 2708 mplsLdpSesOutLabelIfIndex, 2709 mplsLdpSesOutLabel 2710 } 2711 ::= { mplsLdpSesOutLabelMapTable 1 } 2713 MplsLdpSesOutLabelMapEntry ::= SEQUENCE { 2714 mplsLdpSesOutLabelIfIndex InterfaceIndex, 2715 mplsLdpSesOutLabel MplsLabel, 2716 mplsLdpSesOutLabelType MplsLdpLabelTypes, 2717 mplsLdpSesOutLabelConnType INTEGER, 2718 mplsLdpSesOutSegmentIndex Integer32 2719 } 2721 mplsLdpSesOutLabelIfIndex OBJECT-TYPE 2722 SYNTAX InterfaceIndex 2723 MAX-ACCESS not-accessible 2724 STATUS current 2725 DESCRIPTION 2726 "The ifIndex of the 'mplsLdpSesOutLabel'." 2727 ::= { mplsLdpSesOutLabelMapEntry 1 } 2729 mplsLdpSesOutLabel OBJECT-TYPE 2730 SYNTAX MplsLabel 2731 MAX-ACCESS not-accessible 2732 STATUS current 2733 DESCRIPTION 2734 "The outgoing label of this LSP." 2735 ::= { mplsLdpSesOutLabelMapEntry 2 } 2737 mplsLdpSesOutLabelType OBJECT-TYPE 2738 SYNTAX MplsLdpLabelTypes 2739 MAX-ACCESS read-only 2740 STATUS current 2741 DESCRIPTION 2742 "The Layer 2 Label Type for 'mplsLdpOutLabel'." 2743 ::= { mplsLdpSesOutLabelMapEntry 3 } 2745 mplsLdpSesOutLabelConnType OBJECT-TYPE 2746 SYNTAX INTEGER { 2747 unknown(1), 2748 xconnect(2), 2749 starts(3) 2750 } 2751 MAX-ACCESS read-only 2752 STATUS current 2753 DESCRIPTION 2754 "The type of LSP connection. 2755 The possible values are: 2757 unknown(1) -- this may be the value if the LSP 2758 is in a state of flux. It is 2759 considered to be a temporary 2760 situation. 2761 xconnect(2) -- if the mapping between the 2762 session and the outsegment 2763 is associated with an LSP which 2764 is a true cross-connection. 2765 starts(3) -- if the mapping between the 2766 session and the insegment 2767 is associated with an LSP which 2768 starts on this LSR and is 2769 considered an ingress to the LSP." 2770 ::= { mplsLdpSesOutLabelMapEntry 4 } 2772 mplsLdpSesOutSegmentIndex OBJECT-TYPE 2773 SYNTAX Integer32(1..2147483647) 2774 MAX-ACCESS read-only 2775 STATUS current 2776 DESCRIPTION 2777 "This value should contain the same value as 2778 the 'mplsOutSegmentIndex' in the LSR MIB. 2780 NOTE: this value will never be zero, because 2781 this table only maps from Sessions to true 2782 outsegments." 2783 ::= { mplsLdpSesOutLabelMapEntry 5 } 2785 -- 2786 -- Sessions and XConnects (LIB Information) 2787 -- 2789 mplsLdpSesXCMapTable OBJECT-TYPE 2790 SYNTAX SEQUENCE OF MplsLdpSesXCMapEntry 2791 MAX-ACCESS not-accessible 2792 STATUS current 2793 DESCRIPTION 2794 "A table of Session's Labels which 2795 are Mapped to the LSR MIB 's XConnect table. 2796 Each row represents a single cross connect." 2797 ::= { mplsLdpSessionObjects 11 } 2799 mplsLdpSesXCMapEntry OBJECT-TYPE 2800 SYNTAX MplsLdpSesXCMapEntry 2801 MAX-ACCESS not-accessible 2802 STATUS current 2803 DESCRIPTION 2804 "An entry in this table represents information on a 2805 single session between an LDP Entity and LDP Peer. 2806 The information contained in a row is read-only." 2807 INDEX { mplsLdpEntityLdpId, 2808 mplsLdpEntityIndex, 2809 mplsLdpPeerLdpId, 2810 mplsLdpSesInLabelIfIndex, 2811 mplsLdpSesInLabel, 2812 mplsLdpSesOutLabelIfIndex, 2813 mplsLdpSesOutLabel 2814 } 2815 ::= { mplsLdpSesXCMapTable 1 } 2817 MplsLdpSesXCMapEntry ::= SEQUENCE { 2818 mplsLdpSesXCIndex Integer32 2819 } 2821 mplsLdpSesXCIndex OBJECT-TYPE 2822 SYNTAX Integer32(1..2147483647) 2823 MAX-ACCESS read-only 2824 STATUS current 2825 DESCRIPTION 2826 "This value should contain the same value as 2827 the 'mplsXCIndex' in the LSR MIB. 2829 NOTE: this value will never be zero, because 2830 this table only maps from Sessions to true 2831 cross connects." 2832 ::= { mplsLdpSesXCMapEntry 1 } 2834 -- 2835 -- XcrossConnectsFECs Table 2836 -- 2838 mplsXCsFecsTable OBJECT-TYPE 2839 SYNTAX SEQUENCE OF MplsXCsFecsEntry 2840 MAX-ACCESS not-accessible 2841 STATUS current 2842 DESCRIPTION 2843 "A table which shows the relationship between 2844 cross-connects and FECs. Each row represents 2845 a single cross connect to FEC association. 2846 This table is read-only." 2847 ::= { mplsLdpSessionObjects 13 } 2849 mplsXCsFecsEntry OBJECT-TYPE 2850 SYNTAX MplsXCsFecsEntry 2851 MAX-ACCESS not-accessible 2852 STATUS current 2853 DESCRIPTION 2854 "An entry represents a single cross connect 2855 to FEC association." 2856 INDEX { mplsLdpEntityLdpId, 2857 mplsLdpEntityIndex, 2858 mplsLdpPeerLdpId, 2859 mplsLdpSesInLabelIfIndex, 2860 mplsLdpSesInLabel, 2861 mplsLdpSesOutLabelIfIndex, 2862 mplsLdpSesOutLabel, 2863 mplsFecIndex 2864 } 2865 ::= { mplsXCsFecsTable 1 } 2867 MplsXCsFecsEntry ::= SEQUENCE { 2868 mplsXCFecOperStatus INTEGER, 2869 mplsXCFecOperStatusLastChange TimeStamp 2871 } 2873 mplsXCFecOperStatus OBJECT-TYPE 2874 SYNTAX INTEGER { 2875 unknown(1), 2876 inUse(2), 2877 notInUse(3) 2878 } 2879 MAX-ACCESS read-only 2880 STATUS current 2881 DESCRIPTION 2882 "An indication of the operational status of 2883 the FEC associated with this cross connect. 2885 unknown(1) - this is a temporary state which 2886 may indicate the LSP-FEC association 2887 is in a state of transition. 2889 inUse(2) - the FEC associated with the XC is 2890 currently being applied. 2892 notInUse(3) - the FEC associated with the XC is 2893 not being applied. Eventually, this 2894 entry may be aged out." 2895 ::= { mplsXCsFecsEntry 1 } 2897 mplsXCFecOperStatusLastChange OBJECT-TYPE 2898 SYNTAX TimeStamp 2899 MAX-ACCESS read-only 2900 STATUS current 2901 DESCRIPTION 2902 "This value of sysUpTime when the 2903 mplsXCFecOperStatus last changed state." 2904 ::= { mplsXCsFecsEntry 2 } 2906 -- 2907 -- Address Message/Address Withdraw Message Information 2908 -- 2909 -- This information is associated with a specific Session 2910 -- because Label Address Messages are sent after session 2911 -- initialization has taken place. 2912 -- 2914 mplsLdpSesPeerAddrTable OBJECT-TYPE 2915 SYNTAX SEQUENCE OF MplsLdpSesPeerAddrEntry 2916 MAX-ACCESS not-accessible 2917 STATUS current 2918 DESCRIPTION 2919 "This table 'extends' the mplsLdpSessionTable. 2920 This table is used to store Label Address Information 2921 from Label Address Messages received by this LSR from 2922 Peers. This table is read-only and should be updated 2923 when Label Withdraw Address Messages are received, i.e. 2924 Rows should be deleted as apropriate. 2926 NOTE: since more than one address may be contained 2927 in a Label Address Message, this table 'extends', 2928 rather than 'AUGMENTS' the mplsLdpSessionTable's 2929 information." 2930 ::= { mplsLdpSessionObjects 12 } 2932 mplsLdpSesPeerAddrEntry OBJECT-TYPE 2933 SYNTAX MplsLdpSesPeerAddrEntry 2934 MAX-ACCESS not-accessible 2935 STATUS current 2936 DESCRIPTION 2937 "An entry in this table represents information on 2938 session's for a single next hop address which was 2939 advertised in an Address Message from the LDP peer. 2940 The information contained in a row is read-only." 2942 INDEX { mplsLdpEntityLdpId, 2943 mplsLdpEntityIndex, 2944 mplsLdpPeerLdpId, 2945 mplsLdpSesPeerAddrIndex 2946 } 2947 ::= { mplsLdpSesPeerAddrTable 1 } 2949 MplsLdpSesPeerAddrEntry ::= SEQUENCE { 2950 mplsLdpSesPeerAddrIndex Unsigned32, 2951 mplsLdpSesPeerNextHopAddrType AddressFamilyNumbers, 2952 mplsLdpSesPeerNextHopAddr MplsLdpGenAddr 2953 } 2955 mplsLdpSesPeerAddrIndex OBJECT-TYPE 2956 SYNTAX Unsigned32 (1..4294967295) 2957 MAX-ACCESS not-accessible 2958 STATUS current 2959 DESCRIPTION 2960 "An index which uniquely identifies this entry within 2961 a given session." 2962 ::= { mplsLdpSesPeerAddrEntry 1 } 2964 mplsLdpSesPeerNextHopAddrType OBJECT-TYPE 2965 SYNTAX AddressFamilyNumbers 2966 MAX-ACCESS read-only 2967 STATUS current 2968 DESCRIPTION 2969 "The internetwork layer address type of this Next Hop 2970 Address as specified in the Label Address Message 2971 associated with this Session. The value of this 2972 object indicates how to interpret the value of 2973 mplsLdpSessionPeerNextHopAddress." 2974 ::= { mplsLdpSesPeerAddrEntry 2 } 2976 mplsLdpSesPeerNextHopAddr OBJECT-TYPE 2977 SYNTAX MplsLdpGenAddr 2978 MAX-ACCESS read-only 2979 STATUS current 2980 DESCRIPTION 2981 "The value of the next hop address." 2982 REFERENCE 2983 "LDP Specification [18] defines only IPv4 for LDP Protocol 2984 Version 1, see section 3.4.3." 2985 ::= { mplsLdpSesPeerAddrEntry 3 } 2987 --- 2988 --- Notifications 2989 --- 2990 mplsLdpNotificationPrefix OBJECT IDENTIFIER ::= 2991 { mplsLdpNotifications 0 } 2993 mplsLdpInitSesThresholdExceeded NOTIFICATION-TYPE 2994 OBJECTS { 2995 mplsLdpEntityInitSesThreshold 2996 } 2997 STATUS current 2998 DESCRIPTION 2999 "This notification is generated when the value of 3000 the 'mplsLdpEntityInitSesThreshold' object 3001 is not zero, and the number of Session 3002 Initialization messages exceeds the value 3003 of the 'mplsLdpEntityInitSesThreshold' object." 3004 ::= { mplsLdpNotificationPrefix 1 } 3006 mplsLdpPVLMismatch NOTIFICATION-TYPE 3007 OBJECTS { 3008 mplsLdpEntityPVL, 3009 mplsLdpPeerPVL 3010 } 3011 STATUS current 3012 DESCRIPTION 3013 "This notification is generated when the value 3014 of the value of the 3015 'mplsLdpEntityPVLMisTrapEnable' 3016 object is 'enabled(1)' and the 3017 'mplsLdpEntityPVL' does NOT match 3018 the value of the 'mplsLdpPeerPVL' for 3019 a specific Entity." 3020 REFERENCE 3021 "LDP Specification, Section 3.5.3." 3022 ::= { mplsLdpNotificationPrefix 2 } 3024 mplsLdpSessionUp NOTIFICATION-TYPE 3025 OBJECTS { 3026 mplsLdpSesState, 3027 mplsLdpSesDiscontinuityTime, 3028 mplsLdpSesStatsUnkMesTypeErrors, 3029 mplsLdpSesStatsUnkTlvErrors 3030 } 3031 STATUS current 3032 DESCRIPTION 3033 "Generation of this trap occurs when the 3034 'mplsLdpSesUpDownTrapEnable' object is 'enabled(1)' 3035 and the value of 'mplsLdpSesState' enters 3036 the 'operational(5)' state." 3037 ::= { mplsLdpNotificationPrefix 3 } 3039 mplsLdpSessionDown NOTIFICATION-TYPE 3040 OBJECTS { 3041 mplsLdpSesState, 3042 mplsLdpSesDiscontinuityTime, 3043 mplsLdpSesStatsUnkMesTypeErrors, 3044 mplsLdpSesStatsUnkTlvErrors 3046 } 3047 STATUS current 3048 DESCRIPTION 3049 "Generation of this trap occurs when the 3050 'mplsLdpSesUpDownTrapEnable' object is 3051 'enabled(1)' and the value of 3052 'mplsLdpSesState' leaves the 'operational(5)' 3053 state." 3054 ::= { mplsLdpNotificationPrefix 4 } 3056 --**************************************************************** 3057 -- Module Conformance Statement 3058 --**************************************************************** 3060 mplsLdpGroups 3061 OBJECT IDENTIFIER ::= { mplsLdpConformance 1 } 3063 mplsLdpCompliances 3064 OBJECT IDENTIFIER ::= { mplsLdpConformance 2 } 3066 -- 3067 -- Compliance Statements 3068 -- 3070 mplsLdpModuleCompliance MODULE-COMPLIANCE 3071 STATUS current 3072 DESCRIPTION 3073 "The basic implementation requirements for agents that 3074 support the MPLS LDP MIB." 3075 MODULE -- this module 3076 MANDATORY-GROUPS { mplsLdpGeneralGroup, 3077 mplsLdpNotificationsGroup 3078 } 3080 GROUP mplsLdpGenericGroup 3081 DESCRIPTION 3082 "This group must be supported if Generic Labels 3083 are used in the MPLS LDP implementation." 3085 GROUP mplsLdpAtmGroup 3086 DESCRIPTION 3087 "This group must be supported if ATM is used in the 3088 MPLS LDP implementation." 3090 GROUP mplsLdpFrameRelayGroup 3091 DESCRIPTION 3092 "This group must be supported if Frame Relay is used 3093 in the MPLS LDP implementation." 3095 GROUP mplsLdpMappingGroup 3096 DESCRIPTION 3097 "This group must be supported if the LSR MIB is 3098 implemented, specifically the mplsInSegmentTable, 3099 the mplsOutSegmentTable or the mplsXCTable." 3101 ::= { mplsLdpCompliances 1 } 3103 -- units of conformance 3105 mplsLdpGeneralGroup OBJECT-GROUP 3106 OBJECTS { 3107 mplsLdpLsrId, 3108 mplsLdpLsrLoopDetectionCapable, 3109 mplsLdpEntityIndexNext, 3110 mplsLdpEntityProtocolVersion, 3111 mplsLdpEntityAdminStatus, 3112 mplsLdpEntityOperStatus, 3113 mplsLdpEntityTcpDscPort, 3114 mplsLdpEntityUdpDscPort, 3115 mplsLdpEntityMaxPduLength, 3116 mplsLdpEntityKeepAliveHoldTimer, 3117 mplsLdpEntityHelloHoldTimer, 3118 mplsLdpEntityInitSesThreshold, 3119 mplsLdpEntityLabelDistMethod, 3120 mplsLdpEntityLabelRetentionMode, 3121 mplsLdpEntityPVLMisTrapEnable, 3122 mplsLdpEntityPVL, 3123 mplsLdpEntityHopCountLimit, 3124 mplsLdpEntityTargPeer, 3125 mplsLdpEntityTargPeerAddrType, 3126 mplsLdpEntityTargPeerAddr, 3127 mplsLdpEntityOptionalParameters, 3128 mplsLdpEntityDiscontinuityTime, 3129 mplsLdpEntityStorType, 3130 mplsLdpEntityRowStatus, 3131 mplsLdpAttemptedSessions, 3132 mplsLdpSesRejectedNoHelloErrors, 3133 mplsLdpSesRejectedAdErrors, 3134 mplsLdpSesRejectedMaxPduErrors, 3135 mplsLdpSesRejectedLRErrors, 3136 mplsLdpBadLdpIdentifierErrors, 3137 mplsLdpBadPduLengthErrors, 3138 mplsLdpBadMessageLengthErrors, 3139 mplsLdpBadTlvLengthErrors, 3140 mplsLdpMalformedTlvValueErrors, 3141 mplsLdpKeepAliveTimerExpErrors, 3142 mplsLdpShutdownNotifReceived, 3143 mplsLdpShutdownNotifSent, 3144 mplsLdpPeerLabelDistMethod, 3145 mplsLdpPeerLoopDetectionForPV, 3146 mplsLdpPeerPVL, 3147 mplsLdpHelloAdjHoldTimeRem, 3148 mplsLdpHelloAdjType, 3149 mplsLdpSesUpDownTrapEnable, 3150 mplsLdpSesState, 3151 mplsLdpSesProtocolVersion, 3152 mplsLdpSesKeepAliveHoldTimeRem, 3153 mplsLdpSesMaxPduLen, 3154 mplsLdpSesDiscontinuityTime, 3155 mplsLdpSesStatsUnkMesTypeErrors, 3156 mplsLdpSesStatsUnkTlvErrors, 3157 mplsLdpSesPeerNextHopAddrType, 3158 mplsLdpSesPeerNextHopAddr, 3159 mplsFecIndexNext, 3160 mplsFecType, 3161 mplsFecAddrFamily, 3162 mplsFecAddrLength, 3163 mplsFecAddr, 3164 mplsFecStorType, 3165 mplsFecRowStatus 3166 } 3167 STATUS current 3168 DESCRIPTION 3169 "Objects that apply to all MPLS LDP implementations." 3170 ::= { mplsLdpGroups 1 } 3172 mplsLdpGenericGroup OBJECT-GROUP 3173 OBJECTS { 3174 mplsLdpEntityConfGenIfIndxOrZero, 3175 mplsLdpEntityConfGenLRStorType, 3176 mplsLdpEntityConfGenLRRowStatus 3177 } 3178 STATUS current 3179 DESCRIPTION 3180 "Objects that apply to all MPLS LDP implementations 3181 using Generic Lables." 3182 ::= { mplsLdpGroups 2 } 3184 mplsLdpAtmGroup OBJECT-GROUP 3185 OBJECTS { 3186 mplsLdpEntityAtmIfIndxOrZero, 3187 mplsLdpEntityAtmMergeCap, 3188 mplsLdpEntityAtmLRComponents, 3189 mplsLdpEntityAtmVcDirectionality, 3190 mplsLdpEntityAtmLsrConnectivity, 3191 mplsLdpEntityDefaultControlVpi, 3192 mplsLdpEntityDefaultControlVci, 3193 mplsLdpEntityUnlabTrafVpi, 3194 mplsLdpEntityUnlabTrafVci, 3195 mplsLdpEntityAtmStorType, 3196 mplsLdpEntityAtmRowStatus, 3197 mplsLdpEntityConfAtmLRMaxVpi, 3198 mplsLdpEntityConfAtmLRMaxVci, 3199 mplsLdpEntityConfAtmLRStorType, 3200 mplsLdpEntityConfAtmLRRowStatus, 3201 mplsLdpSesAtmLRUpperBoundVpi, 3202 mplsLdpSesAtmLRUpperBoundVci 3204 } 3205 STATUS current 3206 DESCRIPTION 3207 "Objects that apply to all MPLS LDP implementations 3208 over ATM." 3209 ::= { mplsLdpGroups 3 } 3211 mplsLdpFrameRelayGroup OBJECT-GROUP 3212 OBJECTS { 3213 mplsLdpEntityFrIfIndxOrZero, 3214 mplsLdpEntityFrMergeCap, 3215 mplsLdpEntityFrLRComponents, 3216 mplsLdpEntityFrLen, 3217 mplsLdpEntityFrVcDirectionality, 3218 mplsLdpEntityFrParmsStorType, 3219 mplsLdpEntityFrParmsRowStatus, 3220 mplsLdpConfFrMaxDlci, 3221 mplsLdpConfFrStorType, 3222 mplsLdpConfFrRowStatus, 3223 mplsLdpFrSesMaxDlci, 3224 mplsLdpFrSesLen 3225 } 3226 STATUS current 3227 DESCRIPTION 3228 "Objects that apply to all MPLS LDP implementations over 3229 Frame Relay." 3230 ::= { mplsLdpGroups 4 } 3232 mplsLdpMappingGroup OBJECT-GROUP 3233 OBJECTS { 3234 mplsLdpSesInLabelType, 3235 mplsLdpSesInLabelConnType, 3236 mplsLdpSesOutLabelType, 3237 mplsLdpSesOutLabelConnType, 3238 mplsLdpSesOutSegmentIndex, 3239 mplsLdpSesXCIndex, 3240 mplsXCFecOperStatus, 3241 mplsXCFecOperStatusLastChange 3242 } 3243 STATUS current 3244 DESCRIPTION 3245 "These objects are optional and only need to be supported 3246 for LDP implementations which support the 3247 tables, mplsInSegmentTable, mplsOutSegmentTable 3248 and mplsXCTable, in the LSR MIB." 3249 ::= { mplsLdpGroups 5 } 3251 mplsLdpNotificationsGroup NOTIFICATION-GROUP 3252 NOTIFICATIONS { mplsLdpInitSesThresholdExceeded, 3253 mplsLdpPVLMismatch, 3254 mplsLdpSessionUp, 3255 mplsLdpSessionDown 3256 } 3257 STATUS current 3258 DESCRIPTION 3259 "The notification(s) which an MPLS LDP implemention 3260 is required to implement." 3261 ::= { mplsLdpGroups 6 } 3263 END 3265 5. Revision History 3267 This section should be removed when this document is published as an 3268 RFC. 3270 5.1. Changes from 3272 There were three types of changes: the first change was that all the 3273 MPLS Textual Conventions from this MIB, the LSR and MPLS-TE MIBs were 3274 moved into a new document [36], "draft-ietf-mpls-tc-mib-00.txt". The 3275 Textual Conventions are now IMPORTED from [36]. The second type of 3276 change was updates based on comments from the IESG. These changes 3277 will be discussed below. The third type of changes were based on 3278 minor editorial changes from the co-authors. 3280 The "Introduction" and "Structure of the MIB" sections were reworded 3281 since they were repetitive. 3283 The "Overview" was rearranged. 3285 References were added to "The LDP Entity ATM Objects" and "The LDP 3286 Entity Frame Relay Objects" Sections. 3288 The Working Group mailing list and Chairs were added to the CONTACT- 3289 INFO. 3291 Updated the DESCRIPTION clause for the "mplsLdpEntityLdpId" object. 3293 Updated the mplsLdpEntityProtocolVersion to include a range 3294 (1..65535). 3296 Updated the "References" Section. 3298 Running the MIB through the smilint MIB compiler showed that some 3299 object names were longer than 32 characters, these were shortened to 3300 32 characters or fewer. 3302 The following changes were from the co-authors. 3304 Other minor editorial changes such as fixing typographical errors, 3305 and removing MIB comments which are no longer meaningful. 3307 Page 17 (also page 46) the description was enhanced to describe the 3308 version field in the LDP header from RFC3036. 3310 Removed WellKnown from the tcp and upd port names. It's the ports 3311 that get set, and the default value is the well known (actually the 3312 registered) port number. 3314 mplsLdpEntityInitSesTrapEnable object is useless and was removed 3315 since setting mplsLdpEntityInitSesThreshold=0 acheives the same 3316 thing. Also removed it from the descriptive text in section 3. 3318 Page 47, mplsLdpSessionDiscontinuityTime The initial value of this 3319 was changed to be sysUpTime instead of zero. sysUpTime for when the 3320 session starts is more meaningful and was added to the Session 3321 Up/Down Traps also. Also, added the Session specific stats to the 3322 up/down traps. 3324 5.2. Changes from 3326 All changes were from the second last call which took place Thursday, 3327 July 20th, until Thursday, July 27th, 2000 and are described in the 3328 remainder of this section. 3330 Remove the reference to the MPLS framework document. 3332 Add an mplsFecIndexNext type of object. 3334 Change the conformance of the FEC table objects to be part of the 3335 mplsLdpGeneralGroup. 3337 The mplsLdpEntityConfGenericTable is no longer needed because the 3338 functionality has been absorbed by the 3339 mplsLdpEntityConfGenericLabelRangeTable. The 3340 mplsLdpEntityConfGenericTable has been removed and the front section 3341 was updated accordingly. 3343 Other editorial issues, updating references, typos and so forth. 3345 5.3. Changes from 3347 The majority of changes in this revision are based on Last Call 3348 comments which were received during the last call from Thursday, 3349 March 9, 2000 to Friday, March 17, 2000, or slightly thereafter. 3350 Also, changes were made to agree with the latest specifications. 3351 These changes are described in this section. 3353 Changes due to draft-ietf-mpls-ldp-07.txt and draft-ietf-mpls-ldp- 3354 08.txt. Specifically, removing references to IPv4/IP and using router 3355 id, as appropriate. 3357 Removed vpMerge and vpAndVcMerge choices from the object, 3358 mplsLdpEntityAtmMergeCap. VP Merge is not described in [30]. 3360 The LIB Table was removed and replaced by mapping tables to map LDP 3361 LSPs created by LDP sessions to the mplsInSegment, mplsOutSegment and 3362 mplsXC tables in the LSR MIB. The conformance section was updated 3363 to include a Mapping Group which is to be implemented iff these LSR 3364 MIB tables (mplsInSegmentTable, mplsOutSegmentTable and mplsXCTable) 3365 are implemented. 3367 The front section was updated to include information on the Generic 3368 label table. 3370 Added more in the front section on on Row 3371 Creation/adminStatus/OperStatus in the LDP Entity and related tables. 3373 Added a generic label range table. NOTE: there is NO corresponding 3374 LDP message which relates to the information in this table, however, 3375 this table does provide a way for a user to 'reserve' a generic label 3376 range. 3378 A new TEXTUAL-CONVENTION, MplsAtmVcIdentifier was added. This TC has 3379 the same upper bounds as AtmVcIdentifier (from rfc2514) except that 3380 the lower bound is 32 (and not 0). The lower bound is 32 since this 3381 value is specified by [30]. 3383 Removed the scalar object mplsLsrLabelRetentionMode and added 3384 mplsLdpEntityLabelRetentionMode. The change was made to allow 3385 configuring the retention mode on a per LDP Entity basis, as opposed 3386 for the entire LSR. 3388 Typo in section 3.5.2 was fixed. 3390 Typo in the mplsLdpSessionUp notification description was fixed. 3392 Section 'LDP Notifications' was expanded to cover both the 3393 'mplsLdpSessionUp' and 'mplsLdpSessionDown' traps. Also, the objects 3394 which enable and disable these traps have been described in this 3395 Section: 3397 The 'mplsLdpEntityHopCountLoopDetection' object and the 3398 'mplsLdpEntityHopCount' object have been combined into the new 3399 object, 'mplsLdpEntityHopCountLimit'. 3401 MplsLabel has been updated to reflect the VPI value of 12 bits and 3402 not 8. 3404 Added DEFVAL clause to the 'mplsLdpEntityWellKnownDiscoveryPort' 3405 object. The default value is 646. 3407 Added UNITS and DEFVAL clauses to the 'mplsLdpEntityMaxPduLength' 3408 object. The default value is 4096 and the units is octets. 3410 Added DEFVAL clause to 'mplsLdpEntityProtocolVersion' object. The 3411 default value is 1. 3413 Added DEFVAL clause to 'mplsLdpEntityKeepAliveHoldTimer' of 40 3414 seconds. 3416 Added DEFVAL clause to 'mplsLdpEntityInitSesThreshold' object. The 3417 default value is 8. 3419 The mplsLdpEntityWellKnownDiscoveryPort was changed into two objects, 3420 one for TCP and one for UDP. The names are 3422 Typo in the description for the 3424 The mplsLdpEntityPeerTable was (re-)named mplsLdpPeerTable. The 3425 mplsLdpSessionTable now AUGMENTs the mplsLdpPeerTable in order to 3426 show that these two tables are related. There has been wording added 3427 to the mplsLdpSessionEntry description and to the description for the 3428 mplsLdpPeerTable. 3430 5.4. Changes from 3432 Editorial changes, fixing typo's, fixing wrapping lines, etc. 3434 Updated references for latest drafts, and added [31] and [32] to 3435 Reference Section. 3437 Added to the Acknowledgements Section. 3439 Changed the SYNTAX and DESCRIPTION of the 3440 'mplsLdpLsrLoopDetectionCapable' object, so that it will also support 3441 the loop detection by hop count. 3443 Combined the 'mplsLdpEntityLoopDetectionForPV' and 'mplsLdpEntityPVL' 3444 objects. The functionality of the 'mplsLdpEntityLoopDectionForPV' is 3445 now denoted by the value of 0 (zero) in the 'mplsLdpEntityPVL' 3446 object. This results in one less object 3447 'mplsLdpEntityLoopDectionForPV' but does not sacrifice functionality. 3449 Changed 'mplsLdpLibLabelType' into two objects: 3450 'mplsLdpLibInLabelType' and differ from the egress label type. The 3451 MIB now reflects this. 3453 The following items were changed as a result of the Frame Relay Forum 3454 dropping support for 17-bit DLCIs: the MplsLabel TC description has 3455 been modified, and other Frame Relay Object descriptions were also 3456 modified (as specified in this section). 3458 The MplsLabel TC was also modified and reference 3. was added to the 3459 REFERENCE Clause. 3461 MplsLdpLabelTypes TC was modified to use an enum. 3463 InterfaceIndex support was added to the Entity information. This was 3464 specifically requested by several members of the working group. An 3465 additional table, mplsLdpEntityConfGenericTable as a way to configure 3466 Generic Labels, and an object, 'mplsLdpConfGenericIfIndexOrZero was 3467 added to map the InterfaceIndex used by Generic Labels. Objects were 3468 also added to the 'mplsLdpEntityAtmParmsTable' and the and 3469 'mplsLdpEntityFrIfIndex', respectively. 3471 Changed the name of the 'mplsLdpEntityMtu' object to be 3472 'mplsLdpEntityMaxPduLength' which is more consistent with the LDP 3473 Specification. Also, the description and SYNTAX were changed. 3475 Changed the SYNTAX of the 'mplsLdpSessionMaxPduLength' to unsigned32 3476 and changed the Range from (0..65535) to (1..65535). 3478 Added and improved the front section discussion on SNMP 3479 Notifications. 3481 Also, modified the DESCRIPTION clause of the 3483 Added objects to enable/disable the sending of traps: 3485 Added an object to enable/disable sending traps for Sessions changing 3486 from Up to Down, or Down to Up. 3488 Added notifications to generate traps from session changing from Up 3489 to Down, or Down to up. 3491 Added a StorageType object to the Entity and associated tables which 3492 are configurable. 3494 Added a Discontinuity Time object to the Entity Table, 3496 Added discussion on row creation in the Entity and other associated 3497 Entity tables. This is a new Section in the Front part of the 3498 document called: 3500 Removed the 'mplsLdpEntityControlMethod'. 3502 Made 'mplsLdpFecLspId' as part of the INDEX for the FEC table. This 3503 is to allow FECs to map to multiple LSPs. Also add a RowPointer to a 3504 row in the Session Table. 3506 Added an operation status object, 'mplsLdpLspOperStatus' and a last 3507 Change object, 'mplsLdpLspLastChangeto the LIB Table. This will be 3508 used to detect whether an LSP has changed its status. 3510 Changed the name of the mplsLdpPeerTable to the 3511 mplsLdpEntityPeerTable. This table contains information relevant to 3512 Peers which are known to specific Entities. The indexing of this 3513 table has also changed to include the Row in the Entity Table that 3514 this Peer is known by. The mplsLdpHelloAdjacencyTable and the 3515 mplsLdpSessionTable have been moved under this table. Since Hello 3516 Adjacencies are related to Entity-Peer information and Sessions are 3517 related to Entity-Peer information this was seen as a comprehensive 3518 and coherent modelling. Associated descriptions in the front section 3519 and in the tables have been changed to reflect this change. 3521 Moved the 'mplsLdpConfFrLen' object from the 3522 'mplsLdpEntityConfFrLabelRangeTable' to the 3523 'mplsLdpEntityFrameRelayParmsTable' since the Frame Relay 3524 interface/port can only use one header length at a time, i.e. a 3525 specific FR interface supports one address length for all VCs on that 3526 interface. Also, changed the object so that it only supports 10 and 3527 23 bit DLCI lengths. (The 17 bit length was dropped by the Frame 3528 Relay Forum and thus, is no longer required.) The name of this 3529 object was changed from 'mplsLdpConfFrLen' to 'mplsLdpEntityFrLen' to 3530 fit in with the 'mplsLdpEntityFrameRelayParmsTable'. 3532 Removed the seventeenDlciBits(1) value from the mplsLdpFrSessionLen 3533 object. (The 17 bit length was dropped by the Frame Relay Forum and 3534 thus, is no longer required.) 3536 Corrected the range of the 'mplsLdpEntityIndexNext' object to include 3537 0 (zero). 3539 5.5. Changes from 3541 Reworded the description of the mplsLdpAtmSessionTable to clarify 3542 that one or MORE label range intersection(s) is/are represented in 3543 this table. 3545 Reworded the description of the mplsLdpFrameRelaySessionTable to 3546 clarify that one or MORE label range intersection(s) is/are 3547 represented in this table. 3549 Added a new index, mplsLdpSessionPeerIndex, to the 3550 mplsLdpSessionPeerAddressTable. This new index uniquely identifies 3551 the entry within a given session. (Since adding 3552 mplsLdpSessionPeerNextHopAddressType, 3553 mplsLdpSessionPeerNextHopAddress to the INDEX clause of the 3554 mplsLdpSessionPeerAddressTable leaves a table with only indices and 3555 no objects, the work around was to add a new index which uniquely 3556 differentiates an entry within a given session.) 3558 Quite a few changes to the mplsLdpPeerTable. First, removed the 3559 mplsLdpPeerIndex from the mplsLdpPeerTable and other tables. This 3560 index served no purpose, so was removed. Second, removed the 3561 objects: mplsLdpPeerInternetworkAddrType, and 3562 mplsLdpPeerInternetworkAddr. Third, reworded the description of this 3563 table to include information which is known during Session 3564 Intialization attempts, the specific information has to do with Loop 3565 Dection based on Path Vectors. Since Section 3.5.3 of the LDP Spec 3566 when describing the PVLim says: "Although knowledge of a peer's path 3567 vector limit will not change an LSR's behavior, it does enable the 3568 LSR to alert an operator to a possible misconfiguration." and the 3569 object mplsLdpPeerPVL is sent as a varbind in the mplsLdpPVLMismatch 3570 notification. 3572 Removed the mplsLdpPeerIndex from the mplsLdpHelloAdjacencyTable. 3574 Removed the "IANA Address Family Numbers" MIB section. 3576 Updated the boiler.me from the ops web page dated Weds., Dec 22, 3577 1999. 3579 Updated the Security Section from the ops web page. 3581 Added the following objects to the mplsLdpEntityTable: 3582 mplsLdpEntityControlMethod, mplsLdpEntityLoopDectionForPV, and 3583 mplsLdpEntityPathVectorLimit. 3585 Removed mplsLdpSessionLabelAdvertisement, 3586 mplsLdpSessionLoopDetectionForPV, and mplsLdpSessionPathVectorLimit 3587 from the mplsLdpSessionTable. 3589 Changed the mplsLdpPathVectorLimitMismatch Notification to send 3590 mplsLdpEntityPathVectorLimit (instead of 3591 mplsLdpSessionPathVectorLimit). 3593 Copied the MplsLabel TC from draft-ietf-mpls-lsr-mib-00.txt and 3594 replaced the MplsLdpGenAddr for mplsLdpLibInLabel and 3595 mpslLdpLibOutLabel with MplsLabel. 3597 The mplsLdpSessionIndex was removed throughout the MIB. This was 3598 replaced by the object mplsLdpSessionDiscontinuityTime. The 3599 motivation was to reduce the number of indices. 3601 The descriptions for the objects in the mplsLdpSessionStatsTable, 3602 mplsLdpSessionStatsUnknownMessageTypeErrors and 3603 mplsLdpSessionStatsUnknownTlvErrors, have been updated to include a 3604 reference to the mplsLdpSessionDiscontinuityTime object. 3606 5.6. Changes from 3608 Added Scalar Objects: mplsLdpLsrLoopDetectionPresent, and 3609 mplsLdpEntityIndexNext. 3611 Added the following objects to the mplsLdpEntityTable: 3612 mplsLdpEntityProtocolVersion, mplsLdpEntityAdminStatus, 3613 mplsLdpEntityOperStatus, mplsLdpEntityTargetedPeer, 3614 mplsLdpEntityTargetedPeerAddrType, mplsLdpEntityTargetedPeerAddr, and 3615 mplsLdpEntityHelloHoldTimer. 3617 Changed the description of the mplsLdpEntityAtmParmsTable and added 3618 the following objects to this table: 3619 mplsLdpEntityAtmLsrConnectivity, mplsLdpEntityDefaultControlVpi, 3620 mplsLdpEntityDefaultControlVci, mplsLdpEntityUnlabTrafVpi, and 3621 mplsLdpEntityUnlabTrafVci. NOTE: the last four objects were in 3622 Version 01 of the MIB but were mistakenly omitted from Version 02. 3623 Now, they are back. 3625 Changed the indexing of the mplsLdpEntityConfAtmLabelRangeTable to 3626 include the minimum VPI/VCI. This is to ensure that indices in this 3627 table are unique. 3629 Changed the indexing of the mplsLdpEntityConfFrLabelRangeTable, to 3630 include the minimum DLCI value. This is to ensure that indices in 3631 this table are unique. 3633 Added [30] to Reference Section. 3635 5.7. Changes from 3637 The MIB was updated to correspond to draft-ietf-mpls-ldp-06.txt of 3638 the LDP Specification [18]. 3640 The front section was updated. 3642 The MIB was made to be less ATM-centric. Essentially, the ATM 3643 specific objects where removed from the tables and placed in ATM 3644 specific Tables. A type was added to the base tables and a row is to 3645 be created in the ATM/FR/etc. type table. Apropos compliance 3646 statements were added to reflect the separation of ATM and Frame 3647 Relay objects into their respective tables. 3649 Objects for Loop Detection were removed from describing the LDP 3650 implementation (i.e. the scalars were removed) and Loop Dection 3651 objects were added to the Session Table. (Although as the LDP 3652 Specification indicates loop detection should be for an LSR within a 3653 domain.) 3655 The following tables were added: mplsLdpEntityAtmParmsTable, 3656 mplsLdpEntityConfAtmLabelRangeTable, mplsLdpFrameRelayParmsTable, 3657 mplsLdpConfFrLabelRangeTable, mplsLdpAtmSessionTable, 3658 mpslLdpFrameRelaySessionTable, mplsLdpSessionPeerAddressTable, 3659 mplsLdpLibTable, and the mplsLdpFecTable. 3661 The following notifications were added: notification for Session 3662 removal. 3664 The following objects were removed from the Session Table: 3665 mplsLdpSessionRole was removed (this can be determined by comparing 3666 LSR Ids and does not need to be explicitely in the MIB.) ATM 3667 specific objects (mplsLdpSessionAtmLabelRangeLowerBoundVpi 3668 mplsLdpSessionAtmLabelRangeLowerBoundVci, 3669 mplsLdpSessionAtmLabelRangeUpperBoundVpi 3670 mplsLdpSessionAtmLabelRangeUpperBoundVci) were removed and put into a 3671 separate table. Frame Relay objects were added in a separate table. 3673 Hello Adjacency Table was updated. 3675 The objects, mplsLdpSessionRejectedParamErrors, 3676 mplsLdpSessionRejectedNoHelloErrors, mplsLdpBadLdpIdentifierErrors, 3677 mplsLdpBadPduLengthErrors, mplsLdpBadMessageLengthErrors, 3678 mplsLdpBadTlvLengthErrors, mplsLdpMalformedTlvValueErrors, 3679 mplsLdpKeepAliveTimerExpiredErrors, mplsLdpShutdownNotifReceived, and 3680 mplsLdpShutdownNotifSent were added to the mplsLdpEntityStatsTable. 3682 The mplsLdpSessionStatsTable was added to count statics based on a 3683 per Session basis. 3685 The mplLdpPeerConfAtmLabelRangeTable has been removed. There is no 3686 need to configure information for a Peer. All information for a peer 3687 is learned, thus peer information is read-only. 3689 (Editorial) References were updated to reflect the documents which 3690 this version was based on. 3692 5.8. Changes from 3694 Textual conventions were added for the LSR Identifier and the LDP 3695 Identifier. 3697 Top-level mib structure was added. The LDP MIB falls under a proposed 3698 hierarchy of mpls.mplsProtocols. 3700 The mib hierarchy within the LDP MIB was also changed. A new branch, 3701 under mpls.mplsProtocols.mplsLdpMIB.mplsLdpObjects was added. This 3702 branch is mplsLdpLsrObjects. Currently, this contains several new 3703 scalar objects: mplsLdpLsrID, mplsLdpLsrLoopDetectionPresent, 3704 mplsLdpLsrLoopDetectinAdminStatus, mplsLdpLsrPathVectorLimit, 3705 mplsLdpLsrHopCountLimit, mplsLdpLsrLoopPreventionPresent, 3706 mplsLdpLsrLoopPreventionAdminStatus, and 3707 mplsLdpLsrLabelRetentionMode. 3709 mplsLdpEntityTable is now indexed by mplsLdpEntityIdentifier, which 3710 is the LDP Identifier used in Session establishment. 3711 mplsLdpEntityLoopDetection and mplsLdpEntityLoopPrevention objects 3712 were removed from this table. 3714 The following objects were added to the mplsLdpEntityTable: 3715 mplsLdpEntityLabelSpaceType, mplsLdpEntityUnlabTrafVpi, 3716 mplsLdpEntityUnlabTrafVci, mplsLdpEntityMergeCapability, 3717 mplsLdpEntityVcDirectionality, and 3718 mplsLdpEntityLabelDistributionMethod. 3720 The following objects were added to the mplsLdpPeerEntityTable: 3721 mplsLdpPeerLabelDistributionMethod. 3723 The following object was removed from the mplsLdpEntityStatsTable: 3724 mplsLdpEntityEstablishedSessions. 3726 References were added and revised. 3728 6. Acknowledgments 3730 The authors would like to thank the following people: Leigh 3731 McLellan, Geetha Brown, Geping Chen and Charlan Zhou from Nortel 3732 Networks, and Zoltan Takacs and Bo Augustsson from Ericsson. Also, 3733 some members of the working group were very helpful with comments and 3734 corrections to the MIB; the authors would like to thank Adrian Farrel 3735 of Movaz Networks, and Alan Kullberg from NetPlane Systems. 3737 7. References 3739 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 3740 for Describing SNMP Management Frameworks", RFC 2571, April 3741 1999. 3743 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 3744 of Management Information for TCP/IP-based Internets", STD 3745 16, RFC 1155, May 1990. 3747 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 3748 16, RFC 1212, March 1991. 3750 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 3751 SNMP", RFC 1215, March 1991. 3753 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3754 Rose, M., and S. Waldbusser, "Structure of Management 3755 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 3756 1999. 3758 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3759 Rose, M., and S. Waldbusser, "Textual Conventions for 3760 SMIv2", STD 58, RFC 2579, April 1999. 3762 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3763 Rose, M., and S. Waldbusser, "Conformance Statements for 3764 SMIv2", STD 58, RFC 2580, April 1999. 3766 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 3767 Network Management Protocol", STD 15, RFC 1157, May 1990. 3769 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3770 "Introduction to Community-based SNMPv2", RFC 1901, January 3771 1996. 3773 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3774 "Transport Mappings for Version 2 of the Simple Network 3775 Management Protocol (SNMPv2)", RFC 1906, January 1996. 3777 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 3778 Processing and Dispatching for the Simple Network Management 3779 Protocol (SNMP)", RFC 2572, April 1999. 3781 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 3782 (USM) for version 3 of the Simple Network Management 3783 Protocol (SNMPv3)", RFC 2574, April 1999. 3785 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3786 "Protocol Operations for Version 2 of the Simple Network 3787 Management Protocol (SNMPv2)", RFC 1905, January 1996. 3789 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 3790 RFC 2573, April 1999. 3792 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 3793 Access Control Model (VACM) for the Simple Network 3794 Management Protocol (SNMP)", RFC 2575, April 1999. 3796 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 3797 "Introduction to Version 3 of the Internet-standard Network 3798 Management Framework", RFC 2570, April 1999. 3800 [17] Narten, T., and H. Alvestrand, "Guidelines for Writing an IANA 3801 Considerations Section in RFCs.", RFC 2434, IBM, Maxware, October 3802 1998 3804 [18] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and B. 3805 Thomas, "LDP Specification", RFC 3036, January 2001. 3807 [19] Rosen, E., Viswananthan, A., and R. Callon, "Multiprotocol Label 3808 Switching Architecture", RFC 3031, January 2001. 3810 [20] Jamoussi, B., editor, "Constraint-Based LSP Setup using LDP", 3811 draft-ietf-mpls-cr-ldp-05.txt, February 2001. 3813 [21] Bradner, S., "Key words for use in RFCs to Indicate Requirement 3814 Levels", BCP 14, RFC 2119, Harvard University, March 1997 3816 [22] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, 3817 RFC 2026, Harvard University, October 1996 3819 [23] Srinivansan, C., Viswanathan, A., and T. Nadeau "MPLS Label Switch 3820 Router Management Information Base Using SMIv2", draft-ietf-mpls- 3821 lsr-mib-07.txt, January 2001. 3823 [24] Greene, M., Cucchiara, J., and J. Luciani, "Definition of Managed 3824 Objects for the NBMA Next Hop Resolution Protocol (NHRP)", RFC 3825 2677, August 1999. 3827 [25] Internet Assigned Numbers Authority (IANA), ADDRESS FAMILY NUMBERS, 3828 (http://www.isi.edu/in-notes/iana/assignments/address-family- 3829 numbers), for MIB 3830 (ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib). 3832 [26] Noto, M., E. Spiegel, K. Tesink, editors, "Definition of Textual 3833 Conventions and OBJECT-IDENTITIES for ATM Management", RFC 2514, 3834 February 1999. 3836 [27] McCloghrie, K., F. Kastenholz, "The Interfaces Group MIB using 3837 SMIv2", RFC 2863, June 2000. 3839 [28] Tesink, K. (ed.) "Definitions of Managed Objects for ATM 3840 Management", RFC 2515, February 1999. 3842 [29] Grossman, D., and J. Heinanen, "Multiprotocol Encapsulation over 3843 ATM Adaptation Layer 5", RFC 2684, September 1999. 3845 [30] Davie, B., Lawrence, J., McCloghrie, K., Rosen, E., Swallow, G., 3846 Rekhter, Y. and P. Doolan, "MPLS using LDP and ATM VC Switching", 3847 RFC 3035, January 2001. 3849 [31] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., Farinacci, D., 3850 Li, T. and A. Conta, "MPLS Label Stack Encoding", RFC 3032, January 3851 2001. 3853 [32] Conta, A., Doolan, P., and A. Malis, "Use of Label Switching on 3854 Frame Relay Networks Specification", RFC 3034, January 2001. 3856 [33] Boscher, C., Cheval, P., Wu L. and E. Gray, "LDP State Machine", 3857 draft-ietf-mpls-ldp-state-04.txt, March 2000. 3859 [34] Thomas, B. and E. Gray, "LDP Applicability", RFC 3037, January 3860 2001. 3862 [35] Daniele, M., Haberman, B., Routhier, S. and J. Schoenwaelder, 3863 "Textual Coventions for Internet Network Addresses", RFC 2851, June 3864 2000. 3866 [36] Nadeau, T., Cucchiara, J., Srinivasan, C., Viswanathan, A. and H. 3867 Sjostrand, "Definitions of Textual Conventions and OBJECT- 3868 IDENTITIES for Multi-Protocol Label Switching Management", April 3869 2001. 3871 8. Security Considerations 3873 There are a number of management objects defined in this MIB that have a 3874 MAX-ACCESS clause of read-write and/or read-create. Such objects may 3875 be considered sensitive or vulnerable in some network environments. 3876 The support for SET operations in a non-secure environment without 3877 proper protection can have a negative effect on network operations. 3879 There are a number of managed objects in this MIB that may contain 3880 sensitive information. These are contained in the mplsLdpEntityTable. 3881 The objects contained in this table are responsible for setting up or 3882 tearing down LSPs. 3884 It is thus important to control even GET access to these objects and 3885 possibly to even encrypt the values of these object when sending them 3886 over the network via SNMP. Not all versions of SNMP provide features 3887 for such a secure environment. 3889 SNMPv1 by itself is not a secure environment. Even if the network 3890 itself is secure (for example by using IPSec), even then, there is no 3891 control as to who on the secure network is allowed to access and 3892 GET/SET (read/change/create/delete) the objects in this MIB. 3894 It is recommended that the implementers consider the security 3895 features as provided by the SNMPv3 framework. Specifically, the use 3896 of the User-based Security Model RFC 2574 [RFC2574] and the View- 3897 based Access Control Model RFC 2575 [RFC2575] is recommended. 3899 It is then a customer/user responsibility to ensure that the SNMP 3900 entity giving access to an instance of this MIB, is properly 3901 configured to give access to the objects only to those principals 3902 (users) that have legitimate rights to indeed GET or SET 3903 (change/create/delete) them. 3905 9. Authors' Addresses 3907 James V. Luciani 3908 Crescent Networks 3909 900 Chelmsford Street 3910 Lowell, MA 01851 3911 USA 3912 Email: jluciani@crescentnetworks.com 3914 Hans Sjostrand 3915 ipUnplugged 3916 P.O. Box 101 60 3917 S-121 28 Stockholm, Sweden 3918 Phone: +46 8 725 5930 3919 Email: hans@ipunplugged.com 3921 Joan Cucchiara 3922 Crescent Networks 3923 900 Chelmsford Street 3924 Lowell, MA 01851 3925 USA 3926 Phone: (978) 275-3183 3927 Email: jcucchiara@crescentnetworks.com 3929 10. Full Copyright Statement 3931 Copyright (C) The Internet Society (2001). All Rights Reserved. 3933 This document and translations of it may be copied and furnished to 3934 others, and derivative works that comment on or otherwise explain it 3935 or assist in its implementation may be prepared, copied, published 3936 and distributed, in whole or in part, without restriction of any 3937 kind, provided that the above copyright notice and this paragraph are 3938 included on all such copies and derivative works. However, this 3939 document itself may not be modified in any way, such as by removing 3940 the copyright notice or references to the Internet Society or other 3941 Internet organizations, except as needed for the purpose of 3942 developing Internet standards in which case the procedures for 3943 copyrights defined in the Internet Standards process must be 3944 followed, or as required to translate it into languages other than 3945 English. 3947 The limited permissions granted above are perpetual and will not be 3948 revoked by the Internet Society or its successors or assigns. 3950 This document and the information contained herein is provided on an 3951 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 3952 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 3953 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 3954 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 3955 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.