idnits 2.17.1 draft-ietf-mpls-ldp-mib-07.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 == It seems as if not all pages are separated by form feeds - found 0 form feeds but 84 pages 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 5 instances of too long lines in the document, the longest one being 4 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 3574 has weird spacing: '... (Since addin...' == Line 3962 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 2000) is 8654 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 3824, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 3832, but no explicit reference was found in the text == Unused Reference: '20' is defined on line 3835, but no explicit reference was found in the text == Unused Reference: '22' is defined on line 3841, but no explicit reference was found in the text == Unused Reference: '24' is defined on line 3848, but no explicit reference was found in the text == Unused Reference: '25' is defined on line 3852, but no explicit reference was found in the text == Unused Reference: '26' is defined on line 3857, but no explicit reference was found in the text == Unused Reference: '28' is defined on line 3863, but no explicit reference was found in the text == Unused Reference: '29' is defined on line 3866, but no explicit reference was found in the text == Unused Reference: '33' is defined on line 3881, but no explicit reference was found in the text == Unused Reference: '34' is defined on line 3884, but no explicit reference was found in the text == Unused Reference: '35' is defined on line 3887, 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) == Outdated reference: A later version (-06) exists of draft-ietf-mpls-cr-ldp-04 == Outdated reference: A later version (-14) exists of draft-ietf-mpls-lsr-mib-06 -- Possible downref: Non-RFC (?) normative reference: ref. '25' ** Obsolete normative reference: RFC 2233 (ref. '27') (Obsoleted by RFC 2863) == Outdated reference: A later version (-04) exists of draft-ietf-mpls-ldp-state-03 ** Downref: Normative reference to an Informational draft: draft-ietf-mpls-ldp-state (ref. '33') ** Downref: Normative reference to an Informational draft: draft-ietf-mpls-ldp-applic (ref. '34') ** Obsolete normative reference: RFC 2851 (ref. '35') (Obsoleted by RFC 3291) Summary: 21 errors (**), 0 flaws (~~), 20 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group J. Cucchiara 2 Internet-Draft Brix Networks 3 Expires February 2001 H. Sjostrand 4 Ericsson 5 J. Luciani 6 TollBridge Technologies 7 August 2000 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 (1999, 2000). All Rights 39 Reserved. 41 Abstract 43 This memo defines a portion of the Management Information Base (MIB) 44 for use with network management protocols in the Internet community. 45 In particular, it describes managed objects for the Multiprotocol 46 Label Switching, Label Distribution Protocol (LDP). 48 Table of Contents 50 1 Introduction ................................................. 3 51 2 The SNMP Management Framework ................................ 3 52 3 Structure of the MIB ......................................... 5 53 3.1 Overview ................................................... 5 54 3.2 Future Considerations ...................................... 5 55 3.3 Interface Indexing ......................................... 5 56 3.4 Differences from the LDP Specification ..................... 6 57 3.5 Discussion of MIB Groups ................................... 6 58 3.6 The MPLS LDP General Group ................................. 6 59 3.6.1 The LDP Entity Table ..................................... 7 60 3.6.2 Changing Values After Session Establishment .............. 7 61 3.6.3 mplsLdpEntityAdminStatus and mplsLdpEntityRowStatus ...... 7 62 3.6.4 The LDP Entity Generic Objects ........................... 8 63 3.6.5 The LDP Entity ATM Objects ............................... 8 64 3.6.6 The LDP Entity Frame Relay Objects ....................... 8 65 3.6.7 The LDP Entity Statistics Table .......................... 9 66 3.6.8 The LDP Peer Table ....................................... 9 67 3.6.9 The LDP Hello Adjacencies Table .......................... 9 68 3.6.10 The LDP Session Table ................................... 9 69 3.6.11 The LDP ATM Session Table ............................... 9 70 3.6.12 The LDP Frame Relay Session Table ....................... 10 71 3.6.13 The LDP Session Statistics Table ........................ 10 72 3.6.14 The LDP Session Peer Address Table ...................... 10 73 3.6.15 The Mapping Tables ...................................... 10 74 3.6.15.1 The LDP Session In Label Map Table .................... 11 75 3.6.15.2 The LDP Session Out Label Map Table ................... 11 76 3.6.15.3 The LDP Session XC Map Table .......................... 11 77 3.6.16 The FEC Table ........................................... 12 78 3.7 The LDP Notifications Group ................................ 12 79 3.7.1 LDP Notifications ........................................ 12 80 4 MPLS Label Distribution Protocol MIB Definitions ............. 13 81 5 Revision History ............................................. 71 82 5.1 Changes from .............. 71 83 5.2 Changes from .............. 71 84 5.3 Changes from .............. 73 85 5.4 Changes from .............. 75 86 5.5 Changes from .............. 76 87 5.6 Changes from .............. 77 88 5.7 Changes from .............. 78 89 6 Acknowledgments .............................................. 79 90 7 References ................................................... 80 91 8 Security Considerations ...................................... 82 92 9 Authors' Addresses ........................................... 83 93 10 Full Copyright Statement .................................... 84 95 1. Introduction 97 This memo defines a portion of the Management Information Base (MIB) 98 for use with network management protocols in the Internet community. 99 In particular, it describes managed objects for the Multiprotocol 100 Label Switching, Label Distribution Protocol (LDP) [18]. 102 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 103 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 104 document are to be interpreted as described in RFC 2119 [21]. 106 2. The SNMP Management Framework 108 The SNMP Management Framework presently consists of five major 109 components: 111 o An overall architecture, described in RFC 2571 [RFC2571]. 113 o Mechanisms for describing and naming objects and events for the 114 purpose of management. The first version of this Structure of 115 Management Information (SMI) is called SMIv1 and described in 116 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 117 1215 [RFC1215]. The second version, called SMIv2, is described 118 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 119 STD 58, RFC 2580 [RFC2580]. 121 o Message protocols for transferring management information. The 122 first version of the SNMP message protocol is called SNMPv1 and 123 described in STD 15, RFC 1157 [RFC1157]. A second version of 124 the SNMP message protocol, which is not an Internet standards 125 track protocol, is called SNMPv2c and described in RFC 1901 126 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 127 message protocol is called SNMPv3 and described in RFC 1906 128 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 130 o Protocol operations for accessing management information. The 131 first set of protocol operations and associated PDU formats is 132 described in STD 15, RFC 1157 [RFC1157]. A second set of 133 protocol operations and associated PDU formats is described in 134 RFC 1905 [RFC1905]. 136 o A set of fundamental applications described in RFC 2573 137 [RFC2573] and the view-based access control mechanism described 138 in RFC 2575 [RFC2575]. 140 A more detailed introduction to the current SNMP Management Framework 141 can be found in RFC 2570 [RFC2570]. 143 Managed objects are accessed via a virtual information store, termed 144 the Management Information Base or MIB. Objects in the MIB are 145 defined using the mechanisms defined in the SMI. 147 This memo specifies a MIB module that is compliant to the SMIv2. A 148 MIB conforming to the SMIv1 can be produced through the appropriate 149 translations. The resulting translated MIB must be semantically 150 equivalent, except where objects or events are omitted because no 151 translation is possible (use of Counter64). Some machine readable 152 information in SMIv2 will be converted into textual descriptions in 153 SMIv1 during the translation process. However, this loss of machine 154 readable information is not considered to change the semantics of the 155 MIB. 157 3. Structure of the MIB 159 This memo defines a portion of the Management Information Base (MIB) 160 for use with network management protocols in the Internet community. 161 In particular, it describes managed objects for the Multiprotocol 162 Label Switching, Label Distribution Protocol (LDP) as defined in 163 [18]. 165 3.1. Overview 167 The MIB provides objects to configure/set-up potential LDP sessions 168 on a specific LSR. A table is used to configure potential LDP 169 Sessions, where each row in the table initiates an LDP Session. This 170 is the mplsLdpEntityTable. 172 Another table, the mplsLdpPeerTable, is a read-only table which 173 records information learned via discovery or from the session 174 initialization message. Each row in the Peer Table represents a peer 175 which is known to a specific Entity. This table carries information 176 which is specific to the Entity-Peer interactions but is not 177 appropriate for the mplsLdpSessionTable. 179 A third table is used to show the actual sessions which have been, or 180 are in the process of being established. Each row represents a 181 specific session between an Entity (on this LSR) and a peer. 183 3.2. Future Considerations 185 The LDP Specification [18] does not specify the use of VPNs or 186 multicast for LDP, and thus, objects related to these areas have not 187 been included in the MIB. 189 This MIB does not include VP merge configuration either. [30] does 190 not yet describe this capability and so it has been excluded from the 191 MIB. 193 These areas need to be specified in the LDP Specification prior to 194 being added in this or any other MIB. 196 3.3. Interface Indexing 198 Interface Indexes as specified in [27] are used in the MIB. The 199 descriptions of the ifIndexes denote which ifIndex is being used. 200 NOTE: the use of ifIndex is for actual existing connections. 202 3.4. Differences from the LDP Specification 204 Currently, there are 3 differences between this specification and the 205 LDP Specification. As previously mentioned, this MIB is almost 206 entirely based on the LDP specification. The differences are 207 documented here in the hope to avoid any confusion between the two 208 documents. 210 The first difference is that the LDP Entity Table contains some 211 DEFVAL clauses which are not specified explicitely in the LDP 212 Specification. These values, although not documented in the LDP 213 Specification are widely used by existing LDP MIB implementations and 214 thus, have been adopted within this MIB. Please note, they can 215 certainly be changed during row creation or a subsequent "set 216 request". 218 A second difference is the mplsLdpEntityConfGenericLabelRangeTable. 219 This table, although provided as a way to reserve a range of generic 220 labels, does not exist in the LDP Specification. It was added to the 221 MIB due to a request from the working group and because this table 222 was considered useful for reserving a range of generic labels. 224 The third difference is documented by the TEXTUAL-CONVENTION, 225 MplsAtmVcIdentifier. This TC was added to restrict vci values to be 226 greater than 31 as described in [30]. 228 3.5. Discussion of MIB Groups 230 Currently, there are six groups: the MPLS LDP General Group, the MPLS 231 LDP Generic Group, the MPLS LDP ATM Group, the MPLS LDP Frame Relay 232 Group, the MPLS Mapping Group and the MPLS LDP Notifications Group. 233 The MPLS LDP General Group and the MPLS LDP Notifications Group 234 should always be supported. The MPLS LDP Generic Group is specific 235 to Generic labels and should be supported only if LDP is using 236 Generic Labels. The MPLS LDP ATM Group is specific to ATM and should 237 be supported only if LDP is using ATM. Likewise, the MPLS LDP Frame 238 Relay group is specific to Frame Relay and should be supported only 239 if LDP is using Frame Relay. The MPLS LDP Mapping group should be 240 supported if and only if the tables, mplsInSegmentTable, 241 mplsOutSegmentTable and mplsXCTable from the LSR MIB are supported. 243 3.6. The MPLS LDP General Group 245 This group contains information about the specific LDP Entities which 246 are associated with this agent. Each LSR must have one LDP Entity. 248 3.6.1. The LDP Entity Table 250 The LDP Entity Table provides a way to configure the LSR for using 251 LDP. There must be at least one LDP Entity for the LSR to support 252 LDP. 254 Each entry/row in this table represents a single LDP Entity. 256 3.6.2. Changing Values After Session Establishment 258 According to the LDP specification [18] there is no way to manually 259 modify a session once session initialization starts. One way to 260 manually modify a session's parameters is by using SNMP to change the 261 MIB objects related to that session. Please note special care should 262 be taken if MIB objects which are used in the MPLS LDP Session 263 Initialization need to be modified. If the modification of any of 264 these MIB variables takes place anytime after the start of session 265 intialization, then the entire session must be halted. Any 266 information learned by that session must be discarded. The objects 267 should then be modified, and session initialization started. 269 For example, assume that a user wishes to change the configuration of 270 a Label Range which is used by a Session that has already been 271 established. The user should change the mplsLdpEntityAdminStatus to 272 'disable(2)'. Setting the mplsLdpEntityAdminStatus to 'disable(2)' 273 will cause the session to be torn down and all LSPs established due 274 to that session will also be torn down. Also, all information 275 related to that session should be removed from this MIB, and if the 276 LSR MIB is implemented and the optional Mapping Table objects are 277 implemented, then all information related to the LSPs in this session 278 should be removed from these MIBs. [For more information please see 279 the section on "The Mapping Tables".] At this point, the user could 280 modify the Label Range. Lastly, the user should set the 281 mplsLdpEntityAdminStatus to 'enable(1)'. At this point session 282 initialization should occur. The LDP Entity goes through the Session 283 Initialization in order to communicate the new Label Ranges to the 284 Peer and establish new LSPs. 286 3.6.3. mplsLdpEntityAdminStatus and mplsLdpEntityRowStatus 288 The mplsLdpEntityAdminStatus object could be viewed as having a 289 subset of the functionality of the mplsLdpEntityRowStatus object. 290 For example, the AdminStatus object has states of enable(1) and 291 disable(2). Setting the mplsLdpEntityAdminStatus object to 292 disable(2) and setting the mplsLdpEntityRowStatus object to 293 notInService(2) are functionally the same. The motivation behind 294 keeping the mplsLdpEntityAdminStatus object is that there could be 295 situations where a user would be given write permission to the 296 mplsLdpEntityAdminStatus object, but would not be given write 297 permission to the mplsLdpEntityRowStatus object. Having write 298 permission to the mplsLdpEntityRowStatus object would mean that a 299 user would be able to destroy a row. This was the motivation for 300 keeping the two objects. 302 3.6.4. The LDP Entity Generic Objects 304 The mplsLdpEntityConfGenericLabelRangeTable is for configuring LDP 305 for using Generic Labels ranges. Although the LDP Specification does 306 not provide a way for configuring Label Ranges for Generic Labels, 307 the MIB does provide a way to reserve a range of generic labels 308 because this may be useful for LDP implementations which deploy 309 generic labels. Also, this was requested by the MPLS working group. 311 3.6.5. The LDP Entity ATM Objects 313 There exists two tables to configure LDP for using ATM. These tables 314 are the mplsLdpEntityAtmParmsTable and the 315 mplsLdpEntityConfAtmLabelRangeTable. 317 The mplsLdpEntityAtmParmsTable provides a way to configure 318 information which would be contained in the 'Optional Parameter' 319 portion of an LDP PDU Initialization Message. 321 The mplsLdpEntityConfAtmLabelRangeTable provides a way to configure 322 information which would be contained in the 'ATM Label Range 323 Components' portion of an LDP PDU Intialization Message. 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 portion of an LDP PDU 337 Intialization Message. 339 3.6.7. The LDP Entity Statistics Table 341 The LDP Entity Statistics Table is a read-only table which contains 342 statistical information related to failed sessions. Each row in this 343 table is related to a single LDP entity and this table AUGMENTS an 344 mplsLdpEntityEntry. The purpose of this table is to count errors 345 related to session failures. This table could be used to give insite 346 into how to reconfigure values so that a session could be 347 successfully established. 349 3.6.8. The LDP Peer Table 351 The LDP Peer Table is a read-only table which contains information 352 about LDP Peers known to LDP Entities. A row in this table is related 353 to one or more rows in the Hello Adjacency Table and related to a 354 single row in the Session Table. The values in the Peer table are 355 relevant to a Peer and may or may not be the same values used in the 356 session. For example, the Peer's PathLimit information is learned 357 from the session initialization phase. The actual value for the 358 PathVectorLimit is the Peer's value and may not be part of the 359 session. There could be a mismatch in this value between the Entity 360 and the Peer. In the event of a mismatch, then the session will use 361 the PathLimit set by the Entity (and not the Peer). 363 A separate table allows for a more comprehensive and coherent MIB 364 model. 366 3.6.9. The LDP Hello Adjacencies Table 368 This is a table of all adjacencies between all LDP Entities and all 369 LDP Peers. A Session may have one or more adjacencies. 371 3.6.10. The LDP Session Table 373 The LDP Session Table is a read-only table. Each entry in this table 374 represents a single session between an LDP Entity and a Peer. The 375 mplsLdpPeerEntry AUGMENTS entries in this table. 377 3.6.11. The LDP ATM Session Table 379 The MPLS LDP ATM Session Table is a read-only table which contains 380 session information specific to ATM. 382 3.6.12. The LDP Frame Relay Session Table 384 The MPLS LDP Frame Relay Session Table is a read-only table which 385 contains session information specific to Frame Relay. 387 3.6.13. The LDP Session Statistics Table 389 The MPLS LDP Session Stats Table is a read-only table which contains 390 statistical information on sessions. 392 3.6.14. The LDP Session Peer Address Table 394 The MPLS LDP Session Peer Address Table is a table which 'extends' 395 the mplsLdpSessionTable. This table is a read-only table which 396 stores Addresses learned after session initialization via "Address 397 Message" advertisement. 399 3.6.15. The Mapping Tables 401 Originally, this MIB contained a LIB (Label Information Base) table. 402 The LIB table's entry contained information relating an LDP Session 403 to one of its LSPs. In other words, the LDP Session that created the 404 LSP and the LSP's (ingress label, egress label) pair along with other 405 information. The request came from the authors' of the LSR MIB [23] 406 to remove the LIB table from this MIB and to 'point' to the LSR MIB's 407 mplsXCTable. [ASIDE: the mplsXCTable contains LIB information for 408 LSPs created statically or created by any MPLS protocols (LDP, CR-LDP 409 and MPLS-RSVP) whereas the LIB table which was presented in this MIB 410 was only concerned with LIB information for LSPs created by the LDP 411 protocol.] The removal of the LDP MIB's LIB table has necessitated a 412 way to associate (or map) LDP sessions with LDP LSPs created as a 413 result of those LDP sessions. 415 As discussed in the section, "Changing Values after Session 416 Establishment", if a session is torn down, then all the information 417 related to this session, must be removed from the both LDP MIB and, 418 if implemented, from the LSR MIB. 420 The mplsInSegmentTable, the mplsOutSegmentTable and the mplsXCTable 421 in the LSR MIB could contain rows which were created as a result of 422 an LDP LSPs. Three mapping tables were added to this MIB to map LDP 423 Sessions to these tables in the LSR MIB. These mapping tables are 424 described in the next few subsections. Please note, these mapping 425 tables are optional and need only to be implemented if the 426 mplsInSegmentTable, mplsOutSegmentTable and mplsXCTable are from the 427 LSR MIB are implemented. 429 In order to expedite development, these mapping objects have been 430 made optional in the conformance section of the MIB. 432 3.6.15.1. The LDP Session In Label Map Table 434 The mplsLdpSessionInLabelMapTable provides a way to map LDP LSPs in 435 the LSR MIB's mplsInSegmentTable to the LDP session which created 436 them in this MIB's mplsLdpSessionTable. When a session is torn down, 437 the mapping table, mplsLdpSessionInLabelMapTable, provides a way to 438 clean up the related LDP entries in the mplsInSegmentTable. If an 439 LSP is terminated on this LSR then there will be an entry in the 440 mapping table which maps the session and the entry in the 441 mplsInSegmentTable. Please note, there may be entries which are also 442 effected by session teardown in the mplsXCTable. (The relationship 443 between the mplsInSegmentTable and the mplsXCTable and cleanup 444 scenarios will need to be handled and are outside of the scope of 445 this MIB.) 447 This table is optional and only needs to be implemented if the LSR 448 MIB's mplsInSegmentTable and/or mplsXCTable are implemented. 450 3.6.15.2. The LDP Session Out Label Map Table 452 The mplsLdpSessionOutLabelMapTable provides a way to map a LDP LSPs 453 in the LSR MIB's mplsOutSegmentTable to the LDP session which created 454 them in this MIB's mplsLdpSessionTable. When a session is torn down, 455 the mapping table, mplsLdpSessionOutLabelMapTable, provides a way to 456 clean up the related LDP entries in the mplsOutSegmentTable. If an 457 LSP is created by this LSR then there will be an entry in this table 458 which maps the session and the entry in the mplsOutSegmentTable. 459 Please note, there may be entries which are also effected by session 460 teardown in the mplsXCTable. (The relationship between the 461 mplsOutSegmentTable and the mplsXCTable and cleanup scenarios will 462 need to be handled and are outside the scope of this MIB.) 464 This table is optional and only needs to be implemented if the LSR 465 MIB's mplsOutSegmentTable and/or mplsXCTable are implemented. 467 3.6.15.3. The LDP Session XC Map Table 469 The mplsLdpSessionXCMapTable provides a way to map LDP LSPs in the 470 LSR MIB's mplsXCTable to the LDP session which created them in this 471 MIB's mplsLdpSessionTable. When a session is torn down, the mapping 472 table, mplsLdpSessionXCMapTable, provides a way to clean up the 473 related LDP entries in the mplsXCTable. If an LSP is cross-connected 474 on this LSR, then there will be an entry in this mapping table which 475 maps the session and the entry in the mplsXCTable. Please note, only 476 true cross-connects are represented in the mplsLdpSessionXCMapTable. 478 This table is optional and only needs to be implemented if the LSR 479 MIB's mplsXCTable is implemented. 481 3.6.16. The FEC Table 483 The FEC Table is a table which contains FEC (Forwarding Equivalence 484 Class) information. Each entry/row represents a single FEC Element. 485 There is also a FEC Mapping table which maps FECs associated with the 486 Cross-connects. 488 3.7. The LDP Notifications Group 490 3.7.1. LDP Notifications 492 Currently, there are several notifications which are specific for 493 LDP. These are described in this section. Also, there are objects 494 which enable/disable the sending of the traps. If the value is 495 enabled then the trap will be sent. Otherwise, if the value is 496 disabled, then the trap will not be sent. 498 The 'mplsLdpEntityFailedInitSessionTrapEnable' object is used to 499 enable or disable the sending of the If enabled, then this trap is 500 sent when the 'mplsLdpEntityFailedInitSessionThreshold' is exceeded. 501 This notification should indicate to the operator that there may be a 502 misconfigured mplsLdpEntityEntry because the session associated with 503 this Entity is not being established, and the Entity keeps trying to 504 establish the session. A side effect of this situation is that a row 505 in the mplsLdpSessionTable may not be reaching the operational state 506 as indicated by the 508 The object, 'mplsLdpEntityPVLimitMismatchTrapEnable' is used to 509 enable or disable the sending of the trap is sent when there is a 510 mismatch in the PathVectorLimits between the Entity and Peer during 511 session initialization between that Entity and that Peer. In this 512 situation a session could still be established between that entity 513 and that peer. The session uses the value which is configured as the 514 Entity's Path Vector Limit. However, a trap should be sent to 515 indicate that a mismatch occurred. For further details, please see 516 Section 3.5.3 of the LDP Specification [18]. 518 The object, 'mplsLdpSessionUpDownTrapEnable' is used to enable or 519 disable the sending of the 'mplsLdpSessionUp' and are sent when there 520 is an appropriate change in the change state (Up to Down for the 521 'mplsLdpSessionDown' trap, or Down to Up for the 'mplsLdpSessionUp' 522 trap). 524 4. MPLS Label Distribution Protocol MIB Definitions 526 MPLS-LDP-MIB DEFINITIONS ::= BEGIN 528 IMPORTS 529 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, 530 experimental, 531 Integer32, Counter32, Unsigned32 532 FROM SNMPv2-SMI 533 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 534 FROM SNMPv2-CONF 536 TEXTUAL-CONVENTION, RowStatus, TimeInterval, TruthValue, 537 TimeStamp, StorageType 538 FROM SNMPv2-TC 539 InterfaceIndex, InterfaceIndexOrZero 540 FROM IF-MIB 541 -- AtmInterfaceType, AtmVcIdentifier, 542 AtmVpIdentifier 543 FROM ATM-TC-MIB 544 AddressFamilyNumbers 545 FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB 546 ; 548 mplsLdpMIB MODULE-IDENTITY 549 LAST-UPDATED "200008291200Z" -- August 29, 2000 550 ORGANIZATION "Multiprotocol Label Switching (mpls) 551 Working Group" 552 CONTACT-INFO 553 "Joan Cucchiara (jcucchiara@brixnet.com) 554 Brix Networks 556 Hans Sjostrand (hans.sjostrand@ericsson.com) 557 Ericsson 559 James V. Luciani (jluciani@tollbridgetech.com) 560 TollBridge Technologies" 561 DESCRIPTION 562 "This MIB contains managed object definitions for the 563 'Multiprotocol Label Switching, Label Distribution 564 Protocol, LDP' document." 565 ::= { experimental XXXX} -- to be assigned 567 --**************************************************************** 568 -- MPLS LDP Textual Conventions 569 --**************************************************************** 570 -- 572 MplsLsrIdentifier ::= TEXTUAL-CONVENTION 573 STATUS current 574 DESCRIPTION 575 "The Label Switch Router (LSR) identifier 576 is the first 4 bytes or the Router Id component 577 of the Label Distribution Protocol (LDP) identifier." 578 SYNTAX OCTET STRING (SIZE (4)) 580 -- 581 -- A similar TC is also used in RFC2677.txt. NOTE: since 582 -- MPLS's goal is to be any layer2 over any layer3, this 583 -- MIB makes every attempt to define a TC which would 584 -- satisfy L2 and L3 address sizes for now and in 585 -- the future. 0..64 seems was adopted from RFC2677. 586 -- 588 MplsLdpGenAddr ::= TEXTUAL-CONVENTION 589 STATUS current 590 DESCRIPTION 591 "The value of an network layer or data link 592 layer address." 593 SYNTAX OCTET STRING (SIZE (0..64)) 595 -- following Textual Convention was 596 -- originally copied from the LSR MIB. 598 -- It is reproduced here and modified slightly. 600 MplsLabel ::= TEXTUAL-CONVENTION 601 STATUS current 602 DESCRIPTION 603 "This value represents an MPLS label. 604 The label contents are specific to 605 the label being represented. 607 The label carried in an MPLS shim header 608 (for LDP, the Generic Label) is a 20-bit number 609 represented by 4 octets. Bits 0-19 contain a 610 label or a reserved label value. Bits 20-31 MUST 611 be zero. 613 The frame relay label can be either 10-bits or 614 23-bits depending on the DLCI field size and the 615 upper 22-bits or upper 9-bits must be zero, respectively. 617 For an ATM label the lower 16-bits represents the VCI, 618 the next 12-bits represents the VPI and the remaining 619 bits MUST be zero." 620 SYNTAX Integer32(0..2147483647) 622 MplsLdpIdentifier ::= TEXTUAL-CONVENTION 623 STATUS current 624 DESCRIPTION 625 "The LDP identifier is a six octet quantity 626 which is used to identify an Label Switch Router 627 (LSR) label space. 629 The first four octets encode an IP address 630 assigned to the LSR, and the last two octets 631 identify a specific label space within the LSR." 632 SYNTAX OCTET STRING (SIZE (6)) 634 MplsLdpLabelTypes ::= TEXTUAL-CONVENTION 635 STATUS current 636 DESCRIPTION 637 "The Layer 2 label types which are defined for 638 MPLS LDP are generic(1), atm(2), or frameRelay(3)." 639 SYNTAX INTEGER { 640 generic(1), 641 atm(2), 642 frameRelay(3) 643 } 645 -- This was taken from rfc2514.txt (AtmVcIdentifier) and 646 -- modified here for MPLS. 647 -- This TC agrees with "MPLS using LDP and ATM VC Switching" 648 -- document which specifies that VC values need 649 -- to be greater than 31, or in other words, 0-31 are 650 -- reserved for other uses by the ITU and ATM Forum. 651 MplsAtmVcIdentifier ::= TEXTUAL-CONVENTION 652 STATUS current 653 DESCRIPTION 654 "The VCI value for a VCL. The maximum VCI value 655 cannot exceed the value allowable by 656 atmInterfaceMaxVciBits defined in ATM-MIB. 657 The minimum value is 32, values 0 to 31 are 658 reserved for other uses by the ITU and ATM 659 Forum. 32 is typically the default value 660 for the Control VC." 661 SYNTAX Integer32 (32..65535) 663 -- Top-level structure of the MIB (the following is proposed) 664 mpls OBJECT IDENTIFIER ::= { mplsProtocols } 666 mplsProtocols OBJECT IDENTIFIER ::= { mplsLdpObjects } 667 -- under mplsProtocols will be LDP, CR-LDP, 668 -- and other MPLS "Protocols". 670 mplsLdpObjects OBJECT IDENTIFIER ::= { mplsLdpMIB 1 } 671 mplsLdpNotifications OBJECT IDENTIFIER ::= { mplsLdpMIB 2 } 672 mplsLdpConformance OBJECT IDENTIFIER ::= { mplsLdpMIB 3 } 674 --**************************************************************** 675 -- MPLS LDP Objects 676 --**************************************************************** 678 mplsLdpLsrObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 1 } 680 mplsLdpEntityObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 2 } 682 -- 683 -- The MPLS Label Distribution Protocol's 684 -- Label Switch Router Objects 685 -- 687 mplsLdpLsrId OBJECT-TYPE 688 SYNTAX MplsLsrIdentifier 689 MAX-ACCESS read-only 690 STATUS current 691 DESCRIPTION 692 "The LSR's Identifier." 693 ::= { mplsLdpLsrObjects 1 } 695 mplsLdpLsrLoopDetectionCapable OBJECT-TYPE 696 SYNTAX INTEGER { 697 none(1), 698 other(2), 699 hopCount(3), 700 pathVector(4), 701 hopCountAndPathVector(5) 702 } 703 MAX-ACCESS read-only 704 STATUS current 705 DESCRIPTION 706 "A indication of whether this LSR supports 707 loop detection. 709 none(1) -- Loop Detection is not supported 710 on this LSR. 712 other(2) -- Loop Detection is supported but 713 by a method other than those 714 listed below. 716 hopCount(3) -- Loop Detection is supported by 717 Hop Count only. 719 pathVector(4) -- Loop Detection is supported by 720 Path Vector only. 722 hopCountAndPathVector(5) -- Loop Detection is 723 supported by both Hop Count 724 And Path Vector. 726 Since Loop Detection is determined during 727 Session Initialization, an individual session 728 may not be running with loop detection. This 729 object simply gives an indication of whether or not the 730 LSR has the ability to support Loop Detection and 731 which types." 732 ::= { mplsLdpLsrObjects 2 } 734 -- 735 -- The MPLS Label Distribution Protocol Entity Objects 736 -- 738 mplsLdpEntityIndexNext OBJECT-TYPE 739 SYNTAX Unsigned32 (0..4294967295) 740 MAX-ACCESS read-only 741 STATUS current 742 DESCRIPTION 743 "This object contains an appropriate value to 744 be used for mplsLdpEntityIndex when creating 745 entries in the mplsLdpEntityTable. The value 746 0 indicates that no unassigned entries are 747 available. To obtain the mplsLdpEntityIndex 748 value for a new entry, the manager issues a 749 management protocol retrieval operation to obtain 750 the current value of this object. After each 751 retrieval, the agent should modify the value to 752 the next unassigned index." 753 ::= { mplsLdpEntityObjects 1 } 755 mplsLdpEntityTable OBJECT-TYPE 756 SYNTAX SEQUENCE OF MplsLdpEntityEntry 757 MAX-ACCESS not-accessible 758 STATUS current 759 DESCRIPTION 760 "This table contains information about the 761 MPLS Label Distribution Protocol Entities which 762 exist on this Label Switch Router (LSR)." 763 ::= { mplsLdpEntityObjects 2 } 765 mplsLdpEntityEntry OBJECT-TYPE 766 SYNTAX MplsLdpEntityEntry 767 MAX-ACCESS not-accessible 768 STATUS current 769 DESCRIPTION 770 "An entry in this table represents an LDP entity. 771 An entry can be created by a network administrator 772 or by an SNMP agent as instructed by LDP." 773 INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex } 774 ::= { mplsLdpEntityTable 1 } 776 MplsLdpEntityEntry ::= SEQUENCE { 777 mplsLdpEntityLdpId MplsLdpIdentifier, 778 mplsLdpEntityIndex Unsigned32, 779 mplsLdpEntityProtocolVersion Integer32, 780 mplsLdpEntityAdminStatus INTEGER, 781 mplsLdpEntityOperStatus INTEGER, 782 mplsLdpEntityWellKnownTcpDiscoveryPort Unsigned32, 783 mplsLdpEntityWellKnownUdpDiscoveryPort Unsigned32, 784 mplsLdpEntityMaxPduLength Unsigned32, 785 mplsLdpEntityKeepAliveHoldTimer Integer32, 786 mplsLdpEntityHelloHoldTimer Integer32, 787 mplsLdpEntityFailedInitSessionTrapEnable INTEGER, 788 mplsLdpEntityFailedInitSessionThreshold Integer32, 789 mplsLdpEntityLabelDistributionMethod INTEGER, 790 mplsLdpEntityLabelRetentionMode INTEGER, 791 mplsLdpEntityPVLimitMismatchTrapEnable INTEGER, 792 mplsLdpEntityPathVectorLimit Integer32, 793 mplsLdpEntityHopCountLimit Integer32, 794 mplsLdpEntityTargetedPeer TruthValue, 795 mplsLdpEntityTargetedPeerAddrType AddressFamilyNumbers, 796 mplsLdpEntityTargetedPeerAddr MplsLdpGenAddr, 797 mplsLdpEntityOptionalParameters MplsLdpLabelTypes, 798 mplsLdpEntityDiscontinuityTime TimeStamp, 799 mplsLdpEntityStorageType StorageType, 800 mplsLdpEntityRowStatus RowStatus 801 } 803 mplsLdpEntityLdpId OBJECT-TYPE 804 SYNTAX MplsLdpIdentifier 805 MAX-ACCESS not-accessible 806 STATUS current 807 DESCRIPTION 808 "The LDP identifier. 810 The first four octets encode an IP address 811 assigned to the LSR, and the last two octets 812 identify a specific label space within the 813 LSR." 814 REFERENCE 815 "LDP Specification, Section on LDP Identifiers." 817 ::= { mplsLdpEntityEntry 1 } 819 mplsLdpEntityIndex OBJECT-TYPE 820 SYNTAX Unsigned32 (1..4294967295) 821 MAX-ACCESS not-accessible 822 STATUS current 823 DESCRIPTION 824 "This index is used as a secondary index to uniquely 825 identify this row. Before creating a row in this table, 826 the 'mplsLdpEntityIndexNext' object should be retrieved. 827 That value should be used for the value of this index 828 when creating a row in this table. (NOTE: if a value 829 of zero (0) is retrieved, that indicates that no rows 830 can be created in this table at this time. 832 A secondary index (this object) is needed by some 833 but not all, LDP implementations. For example 834 in an LDP implementation which uses PPP, this 835 index may be needed." 836 ::= { mplsLdpEntityEntry 2 } 838 mplsLdpEntityProtocolVersion OBJECT-TYPE 839 SYNTAX Integer32 840 MAX-ACCESS read-create 841 STATUS current 842 DESCRIPTION 843 "The version number of the protocol. The value of 0 on a 844 read indicates that the version of the protocol is unknown. 845 Otherwise, the value of this object represents the version 846 of the LDP protocol." 847 DEFVAL { 1 } 848 ::= { mplsLdpEntityEntry 3 } 850 mplsLdpEntityAdminStatus OBJECT-TYPE 851 SYNTAX INTEGER { 852 enable(1), 853 disable(2) 854 } 855 MAX-ACCESS read-create 856 STATUS current 857 DESCRIPTION 858 "The administrative status of this LDP Entity. 859 If this object is changed from 'enable' to 'disable' 860 and this entity has already attempted to establish 861 contact with a Peer (which implies that the 862 'mplsLdpEntityRowStatus' object has been set to 863 'active'), then all contact with that 864 Peer is lost and all information from that Peer 865 needs to be removed from the MIB. 867 At this point the user is able to change values 868 which are related to this entity. 870 When the admin status is set back to 'up', then 871 this Entity will attempt to establish new sessions 872 with the Peer." 873 DEFVAL { enable } 874 ::= { mplsLdpEntityEntry 4 } 876 mplsLdpEntityOperStatus OBJECT-TYPE 877 SYNTAX INTEGER { 878 unknown(0), 879 enabled(1), 880 disabled(2) 881 } 882 MAX-ACCESS read-only 883 STATUS current 884 DESCRIPTION 885 "The operational status of this LDP Entity." 886 ::= { mplsLdpEntityEntry 5 } 888 mplsLdpEntityWellKnownTcpDiscoveryPort OBJECT-TYPE 889 SYNTAX Unsigned32 890 MAX-ACCESS read-create 891 STATUS current 892 DESCRIPTION 893 "The well known TCP Discovery Port for 894 LDP." 895 DEFVAL { 646 } 896 ::= { mplsLdpEntityEntry 6 } 898 mplsLdpEntityWellKnownUdpDiscoveryPort OBJECT-TYPE 899 SYNTAX Unsigned32 900 MAX-ACCESS read-create 901 STATUS current 902 DESCRIPTION 903 "The well known UDP Discovery Port for 904 LDP." 905 DEFVAL { 646 } 906 ::= { mplsLdpEntityEntry 7 } 908 mplsLdpEntityMaxPduLength OBJECT-TYPE 909 SYNTAX Unsigned32 (0..65535) 910 UNITS "octets" 911 MAX-ACCESS read-create 912 STATUS current 913 DESCRIPTION 914 "The maximum PDU Length that is sent in 915 the Common Session Parameters of an Initialization 916 Message. A value of 255 or less specifies the 917 default maximum length of 4096 octets." 918 REFERENCE 919 "See Section on the 'Initialization Message' in the 920 LDP Specification." 921 DEFVAL { 4096 } 922 ::= { mplsLdpEntityEntry 8 } 924 mplsLdpEntityKeepAliveHoldTimer OBJECT-TYPE 925 SYNTAX Integer32 (1..65535) 926 UNITS "seconds" 927 MAX-ACCESS read-create 928 STATUS current 929 DESCRIPTION 930 "The two octet value which is the proposed keep alive hold 931 timer for this LDP Entity." 932 DEFVAL { 40 } 933 ::= { mplsLdpEntityEntry 9 } 935 mplsLdpEntityHelloHoldTimer OBJECT-TYPE 936 SYNTAX Integer32 (0..65535) 937 UNITS "seconds" 938 MAX-ACCESS read-create 939 STATUS current 940 DESCRIPTION 941 "The two octet value which is the proposed Hello hold 942 timer for this LDP Entity. A value of 0 means use the 943 default, which is 15 seconds for Link Hellos and 45 944 seconds for Targeted Hellos. A value of 65535 means 945 infinite." 946 DEFVAL { 0 } 947 ::= { mplsLdpEntityEntry 10 } 949 mplsLdpEntityFailedInitSessionTrapEnable OBJECT-TYPE 950 SYNTAX INTEGER { 951 enabled(1), 952 disabled(2) 953 } 954 MAX-ACCESS read-create 955 STATUS current 956 DESCRIPTION 957 "Indicates whether the 958 'mplsLdpFailedInitSessionThresholdExceeded' 959 trap should be generated. 961 If the value of this object is 'enabled(1)' 962 then the trap will generated. If the value 963 of this object is 'disabled(2)' then the 964 trap will not be generated. The DEFVAL 965 is set to 'enabled(1)'." 967 DEFVAL { enabled } 968 ::= { mplsLdpEntityEntry 11 } 970 mplsLdpEntityFailedInitSessionThreshold OBJECT-TYPE 971 SYNTAX Integer32 972 MAX-ACCESS read-create 973 STATUS current 974 DESCRIPTION 975 "When attempting to establish a session with a 976 given Peer, the given LDP Entity should 977 send out the SNMP notification, 978 'mplsLdpFailedInitSessionThresholdExceeded', when 979 the number of Session Initialization messages sent 980 exceeds this threshold. 982 A value of 0 (zero) for this object 983 indicates that the threshold is infinity, and 984 the SNMP notification will never be sent 985 when the value of this object is 0 (zero)." 986 DEFVAL { 8 } 987 ::= { mplsLdpEntityEntry 12 } 989 mplsLdpEntityLabelDistributionMethod OBJECT-TYPE 990 SYNTAX INTEGER { 991 downstreamOnDemand(1), 992 downstreamUnsolicited(2) 993 } 994 MAX-ACCESS read-create 995 STATUS current 996 DESCRIPTION 997 "For any given LDP session, the method of 998 label distribution must be specified." 999 ::= { mplsLdpEntityEntry 13 } 1001 mplsLdpEntityLabelRetentionMode OBJECT-TYPE 1002 SYNTAX INTEGER { 1003 conservative(1), 1004 liberal(2) 1005 } 1006 MAX-ACCESS read-create 1007 STATUS current 1008 DESCRIPTION 1009 "The LDP Entity can be configured to use either 1010 conservative or liberal label retention mode. 1012 If the value of this object is conservative(1) 1013 then advertized label mappings are retained 1014 only if they will be used to forward packets, 1015 i.e. if label came from a valid next hop. 1017 If the value of this object is liberal(2) 1018 then all advertized label mappings are retained 1019 whether they are from a valid next hop or not." 1020 ::= { mplsLdpEntityEntry 14 } 1022 mplsLdpEntityPVLimitMismatchTrapEnable OBJECT-TYPE 1023 SYNTAX INTEGER { 1024 enabled(1), 1025 disabled(2) 1026 } 1027 MAX-ACCESS read-create 1028 STATUS current 1029 DESCRIPTION 1030 "Indicates whether the 'mplsLdpPathVectorLimitMismatch' 1031 trap should be generated. 1033 If the value of this object is 'enabled(1)' 1034 then the trap will generated. If the value 1035 of this object is 'disabled(2)' then the 1036 trap will not be generated. The DEFVAL 1037 is set to 'enabled(1)'." 1038 DEFVAL { enabled } 1039 ::= { mplsLdpEntityEntry 15 } 1041 mplsLdpEntityPathVectorLimit OBJECT-TYPE 1042 SYNTAX Integer32 (0..255) 1043 MAX-ACCESS read-create 1044 STATUS current 1045 DESCRIPTION 1046 "If the value of this object is 0 (zero) then 1047 Loop Dection for Path Vectors is disabled. 1049 Otherwise, if this object has a value greater than 1050 zero, then Loop Dection for Path Vectors is enabled, 1051 and the Path Vector Limit is this value. 1052 Also, the value of the object, 1053 'mplsLdpLsrLoopDetectionCapable', must be set to 1054 either 'pathVector(4)' or 'hopCountAndPathVector(5)', 1055 if this object has a value greater than 0 (zero)." 1056 ::= { mplsLdpEntityEntry 16 } 1058 mplsLdpEntityHopCountLimit OBJECT-TYPE 1059 SYNTAX Integer32 (0..255) 1060 MAX-ACCESS read-create 1061 STATUS current 1062 DESCRIPTION 1063 "If the value of this object is 0 (zero), 1064 then Loop Detection using Hop Counters is 1065 disabled. 1067 If the value of this object is greater than 1068 0 (zero) then Loop Detection using Hop 1069 Counters is enabled, and this object 1070 specifies this Entity's maximum allowable 1071 value for the Hop Count. 1072 Also, the value of the object 1073 mplsLdpLsrLoopDetectionCapable must be set 1074 to either 'hopCount(3)' or 1075 'hopCountAndPathVector(5)' if this object 1076 has a value greater than 0 (zero)." 1077 ::= { mplsLdpEntityEntry 17 } 1079 mplsLdpEntityTargetedPeer OBJECT-TYPE 1080 SYNTAX TruthValue 1081 MAX-ACCESS read-create 1082 STATUS current 1083 DESCRIPTION 1084 "If this LDP entity uses targeted peer then set 1085 this to true." 1086 DEFVAL { false } 1087 ::= { mplsLdpEntityEntry 18 } 1089 mplsLdpEntityTargetedPeerAddrType OBJECT-TYPE 1090 SYNTAX AddressFamilyNumbers 1091 MAX-ACCESS read-create 1092 STATUS current 1093 DESCRIPTION 1094 "The type of the internetwork layer address used for 1095 the Extended Discovery. This object indicates how 1096 the value of mplsLdpEntityTargetedPeerAddr is to 1097 be interpreted." 1098 ::= { mplsLdpEntityEntry 19 } 1100 mplsLdpEntityTargetedPeerAddr OBJECT-TYPE 1101 SYNTAX MplsLdpGenAddr 1102 MAX-ACCESS read-create 1103 STATUS current 1104 DESCRIPTION 1105 "The value of the internetwork layer address used for 1106 the Extended Discovery." 1107 ::= { mplsLdpEntityEntry 20 } 1109 mplsLdpEntityOptionalParameters OBJECT-TYPE 1110 SYNTAX MplsLdpLabelTypes 1111 MAX-ACCESS read-create 1112 STATUS current 1113 DESCRIPTION 1114 "Specifies the optional parameters for the LDP 1115 Initialization Message. If the value is generic(1) 1116 then no optional parameters will be sent in 1117 the LDP Initialization message associated with 1118 this Entity. 1120 If the value is atmParameters(2) then 1121 a row must be created in the mplsLdpEntityAtmParms 1122 Table, which corresponds to this entry. 1124 If the value is frameRelayParameters(3) then 1125 a row must be created in the mplsLdpEntityFrameRelayParms 1126 Table, which corresponds to this entry." 1127 ::= { mplsLdpEntityEntry 21 } 1129 mplsLdpEntityDiscontinuityTime OBJECT-TYPE 1130 SYNTAX TimeStamp 1131 MAX-ACCESS read-only 1132 STATUS current 1133 DESCRIPTION 1134 "The value of sysUpTime on the most recent occasion 1135 at which any one or more of this entity's counters 1136 suffered a discontinuity. The relevant counters are the 1137 specific instances associated with this entity of 1138 any Counter32, or Counter64 object contained 1139 in the 'mplsLdpEntityStatsTable'. If no such 1140 discontinuities have occurred since the last 1141 re-initialization of the local management 1142 subsytem, then this object contains a zero 1143 value." 1144 ::= { mplsLdpEntityEntry 22 } 1146 mplsLdpEntityStorageType OBJECT-TYPE 1147 SYNTAX StorageType 1148 MAX-ACCESS read-create 1149 STATUS current 1150 DESCRIPTION 1151 "The storage type for this entry." 1152 ::= { mplsLdpEntityEntry 23 } 1154 mplsLdpEntityRowStatus OBJECT-TYPE 1155 SYNTAX RowStatus 1156 MAX-ACCESS read-create 1157 STATUS current 1158 DESCRIPTION 1159 "An object that allows entries in this table to 1160 be created and deleted using the 1161 RowStatus convention. 1163 Once the 'mplsLdpEntityAdminStatus' object has 1164 the value of 'up' and this object has the value 1165 of 'active' then the Entity will atttempt to 1166 contact an LDP Peer. If the value of this object 1167 is changed to 'notInService', then the Entity looses 1168 contact with the LDP Peer and all information related 1169 to that Peer must be removed from the MIB. This has 1170 the same effect as changing 'mplsLdpEntityAdminStatus' 1171 from 'enable' to 'disable'. 1173 When this object is set to 'active' and the value of 1174 the 'mplsLdpEntityAdminStatus' is 'enable' then 1175 this Entity will attempt to contact the Peer and 1176 establish new sessions." 1177 ::= { mplsLdpEntityEntry 24 } 1179 -- 1180 -- Ldp Entity Objects for Generic Labels 1181 -- 1183 mplsLdpEntityGenericObjects OBJECT IDENTIFIER ::= 1184 { mplsLdpEntityObjects 3 } 1186 -- 1187 -- The MPLS LDP Entity Configurable Generic Label Range Table 1188 -- 1190 mplsLdpEntityConfGenericLabelRangeTable OBJECT-TYPE 1191 SYNTAX SEQUENCE OF MplsLdpEntityConfGenericLabelRangeEntry 1192 MAX-ACCESS not-accessible 1193 STATUS current 1194 DESCRIPTION 1195 "The MPLS LDP Entity Configurable Generic Label Range Table. 1196 The purpose of this table is to provide a mechanism 1197 for specifying a contiguous range of generic labels, 1198 or a 'label range' for LDP Entities. 1200 LDP Entities which use Generic Labels must have at least one 1201 entry in this table." 1202 ::= { mplsLdpEntityGenericObjects 1 } 1204 mplsLdpEntityConfGenericLabelRangeEntry OBJECT-TYPE 1205 SYNTAX MplsLdpEntityConfGenericLabelRangeEntry 1206 MAX-ACCESS not-accessible 1207 STATUS current 1208 DESCRIPTION 1209 "A row in the LDP Entity Configurable Generic Label 1210 Range Table. One entry in this table contains 1211 information on a single range of labels 1212 represented by the configured Upper and Lower 1213 Bounds pairs. NOTE: there is NO corresponding 1214 LDP message which relates to the information 1215 in this table, however, this table does provide 1216 a way for a user to 'reserve' a generic label 1217 range. 1219 NOTE: The ranges for a specific LDP Entity 1220 are UNIQUE and non-overlapping. 1222 A row will not be created unless a unique and 1223 non-overlapping range is specified. Thus, row 1224 creation implies a one-shot row creation of 1225 LDP EntityID and LowerBound and 1226 UpperBound." 1227 INDEX { mplsLdpEntityLdpId, 1228 mplsLdpEntityIndex, 1229 mplsLdpEntityConfGenericLabelRangeMinimum, 1230 mplsLdpEntityConfGenericLabelRangeMaximum 1231 } 1232 ::= { mplsLdpEntityConfGenericLabelRangeTable 1 } 1234 MplsLdpEntityConfGenericLabelRangeEntry ::= SEQUENCE { 1235 mplsLdpEntityConfGenericLabelRangeMinimum Unsigned32, 1236 mplsLdpEntityConfGenericLabelRangeMaximum Unsigned32, 1237 mplsLdpEntityConfGenericIfIndexOrZero InterfaceIndexOrZero, 1238 mplsLdpEntityConfGenericLabelRangeStorageType StorageType, 1239 mplsLdpEntityConfGenericLabelRangeRowStatus RowStatus 1240 } 1242 mplsLdpEntityConfGenericLabelRangeMinimum OBJECT-TYPE 1243 SYNTAX Unsigned32(0..1048575) 1244 MAX-ACCESS not-accessible 1245 STATUS current 1246 DESCRIPTION 1247 "The minimum label configured for this range." 1248 ::= { mplsLdpEntityConfGenericLabelRangeEntry 1 } 1250 mplsLdpEntityConfGenericLabelRangeMaximum OBJECT-TYPE 1251 SYNTAX Unsigned32(0..1048575) 1252 MAX-ACCESS not-accessible 1253 STATUS current 1254 DESCRIPTION 1255 "The maximum label configured for this range." 1256 ::= { mplsLdpEntityConfGenericLabelRangeEntry 2 } 1258 mplsLdpEntityConfGenericIfIndexOrZero 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 these Generic Label would be created, or 1265 0 (zero). The value of zero means that the InterfaceIndex 1266 is not known. For example, if the InterfaceIndex is 1267 created subsequent to the Generic Label's creation, then 1268 it would not be known. However, if the InterfaceIndex 1269 is known, then it must be represented by this value. 1271 If an InterfaceIndex becomes known, then the 1272 network management entity (e.g. SNMP agent) responsible 1273 for this object MUST change the value from 0 (zero) to the 1274 value of the InterfaceIndex. If this Generic Label is 1275 being used in forwarding data, then the value of this 1276 object MUST be the InterfaceIndex." 1277 ::= { mplsLdpEntityConfGenericLabelRangeEntry 3 } 1279 mplsLdpEntityConfGenericLabelRangeStorageType OBJECT-TYPE 1280 SYNTAX StorageType 1281 MAX-ACCESS read-create 1282 STATUS current 1283 DESCRIPTION 1284 "The storage type for this entry." 1285 ::= { mplsLdpEntityConfGenericLabelRangeEntry 4 } 1287 mplsLdpEntityConfGenericLabelRangeRowStatus OBJECT-TYPE 1288 SYNTAX RowStatus 1289 MAX-ACCESS read-create 1290 STATUS current 1291 DESCRIPTION 1292 "An object that allows entries in this 1293 table to be created and deleted using 1294 the RowStatus convention. 1296 There must exist at least one entry in this 1297 table for every LDP Entity that has a 1298 generic label configured. 1300 NOTE: This RowStatus object should 1301 have the same value of the 'mplsLdpEntityRowStatus' 1302 related to this entry." 1303 ::= { mplsLdpEntityConfGenericLabelRangeEntry 5 } 1305 -- 1306 -- Ldp Entity Objects for ATM 1307 -- 1308 mplsLdpEntityAtmObjects OBJECT IDENTIFIER ::= 1309 { mplsLdpEntityObjects 4 } 1311 mplsLdpEntityAtmParmsTable OBJECT-TYPE 1312 SYNTAX SEQUENCE OF MplsLdpEntityAtmParmsEntry 1313 MAX-ACCESS not-accessible 1314 STATUS current 1315 DESCRIPTION 1316 "This table contains information about the 1317 ATM specific information which could be used 1318 in the 'Optional Parameters' and other ATM specific 1319 information." 1320 ::= { mplsLdpEntityAtmObjects 1 } 1322 mplsLdpEntityAtmParmsEntry OBJECT-TYPE 1323 SYNTAX MplsLdpEntityAtmParmsEntry 1324 MAX-ACCESS not-accessible 1325 STATUS current 1326 DESCRIPTION 1327 "An entry in this table represents the ATM parameters 1328 and ATM information for this LDP entity." 1329 INDEX { mplsLdpEntityLdpId, 1330 mplsLdpEntityIndex 1331 } 1332 ::= { mplsLdpEntityAtmParmsTable 1 } 1334 MplsLdpEntityAtmParmsEntry ::= SEQUENCE { 1335 mplsLdpEntityAtmIfIndexOrZero InterfaceIndexOrZero, 1336 mplsLdpEntityAtmMergeCap INTEGER, 1337 mplsLdpEntityAtmLabelRangeComponents Unsigned32, 1338 mplsLdpEntityAtmVcDirectionality INTEGER, 1339 mplsLdpEntityAtmLsrConnectivity INTEGER, 1340 mplsLdpEntityDefaultControlVpi AtmVpIdentifier, 1341 mplsLdpEntityDefaultControlVci MplsAtmVcIdentifier, 1342 mplsLdpEntityUnlabTrafVpi AtmVpIdentifier, 1343 mplsLdpEntityUnlabTrafVci MplsAtmVcIdentifier, 1344 mplsLdpEntityAtmStorageType StorageType, 1345 mplsLdpEntityAtmRowStatus RowStatus 1346 } 1348 mplsLdpEntityAtmIfIndexOrZero OBJECT-TYPE 1349 SYNTAX InterfaceIndexOrZero 1350 MAX-ACCESS read-create 1351 STATUS current 1352 DESCRIPTION 1353 "This value represents either the InterfaceIndex of 1354 the 'ifLayer' where the ATM Labels 'owned' by this 1355 entry were created, or 0 (zero). The value of zero 1356 means that the InterfaceIndex is not known. For example, 1357 if the InterfaceIndex is created subsequent to the 1358 ATM Label's creation, then it would not be known. 1359 However, if the InterfaceIndex is known, then it must 1360 be represented by this value. 1362 If an InterfaceIndex becomes known, then the 1363 network management entity (e.g. SNMP agent) responsible 1364 for this object MUST change the value from 0 (zero) to the 1365 value of the InterfaceIndex. If an ATM Label is 1366 being used in forwarding data, then the value of this 1367 object MUST be the InterfaceIndex." 1368 ::= { mplsLdpEntityAtmParmsEntry 1 } 1370 mplsLdpEntityAtmMergeCap OBJECT-TYPE 1371 SYNTAX INTEGER { 1372 notSupported(0), 1373 vcMerge(2) 1374 } 1375 MAX-ACCESS read-create 1376 STATUS current 1377 DESCRIPTION 1378 "Denotes the Merge Capability of this Entity." 1379 ::= { mplsLdpEntityAtmParmsEntry 2 } 1381 mplsLdpEntityAtmLabelRangeComponents OBJECT-TYPE 1382 SYNTAX Unsigned32 (1..65535) 1383 MAX-ACCESS read-create 1384 STATUS current 1385 DESCRIPTION 1386 "Number of LabelRange Components in the Initialization 1387 message. This also represents the number of entries 1388 in the mplsLdpLabelRangeComponentsTable which correspond 1389 to this entry." 1390 ::= { mplsLdpEntityAtmParmsEntry 3 } 1392 mplsLdpEntityAtmVcDirectionality OBJECT-TYPE 1393 SYNTAX INTEGER { 1394 bidirectional(0), 1395 unidirectional(1) 1396 } 1397 MAX-ACCESS read-create 1398 STATUS current 1399 DESCRIPTION 1400 "If the value of this object is 'bidirectional(0)', 1401 a given VCI, within a given VPI, is used as a 1402 label for both directions independently. 1404 If the value of this object is 'unidirectional(1)', 1405 a given VCI within a VPI designates one direction." 1406 ::= { mplsLdpEntityAtmParmsEntry 4 } 1408 mplsLdpEntityAtmLsrConnectivity OBJECT-TYPE 1409 SYNTAX INTEGER { 1410 direct(1), 1411 indirect(2) 1412 } 1413 MAX-ACCESS read-create 1414 STATUS current 1415 DESCRIPTION 1416 "The peer LSR may be connected indirectly by means of an 1417 ATM VP so that the VPI values may be different on either 1418 endpoint so the label MUST be encoded entirely within the 1419 VCI field." 1420 DEFVAL { direct } 1421 ::= { mplsLdpEntityAtmParmsEntry 5 } 1423 mplsLdpEntityDefaultControlVpi OBJECT-TYPE 1424 SYNTAX AtmVpIdentifier 1425 MAX-ACCESS read-create 1426 STATUS current 1427 DESCRIPTION 1428 "The default VPI value for the non-MPLS connection. The 1429 default value of this is 0 (zero) but other values may 1430 be configured. This object allows a different value 1431 to be configured." 1432 DEFVAL 1433 { 0 } 1434 ::= { mplsLdpEntityAtmParmsEntry 6 } 1436 mplsLdpEntityDefaultControlVci OBJECT-TYPE 1437 SYNTAX MplsAtmVcIdentifier 1438 MAX-ACCESS read-create 1439 STATUS current 1440 DESCRIPTION 1441 "The Default VCI value for a non-MPLS connection. The 1442 default value of this is 32 but other values may be 1443 configured. This object allows a different value to 1444 be configured." 1445 DEFVAL 1446 { 32 } 1447 ::= { mplsLdpEntityAtmParmsEntry 7 } 1449 mplsLdpEntityUnlabTrafVpi OBJECT-TYPE 1450 SYNTAX AtmVpIdentifier 1451 MAX-ACCESS read-create 1452 STATUS current 1453 DESCRIPTION 1454 "VPI value of the VCC supporting unlabelled traffic. This 1455 non-MPLS connection is used to carry unlabelled (IP) 1456 packets. The default value is the same as the default 1457 value of the 'mplsLdpEntityDefaultControlVpi', however 1458 another value may be configured." 1459 DEFVAL { 0 } 1460 ::= { mplsLdpEntityAtmParmsEntry 8 } 1462 mplsLdpEntityUnlabTrafVci OBJECT-TYPE 1463 SYNTAX MplsAtmVcIdentifier 1464 MAX-ACCESS read-create 1465 STATUS current 1466 DESCRIPTION 1467 "VCI value of the VCC supporting unlabelled traffic. 1468 This non-MPLS connection is used to carry unlabelled (IP) 1469 packets. The default value is the same as the default 1470 value of the 'mplsLdpEntityDefaultControlVci', however 1471 another value may be configured." 1472 DEFVAL { 32 } 1473 ::= { mplsLdpEntityAtmParmsEntry 9 } 1475 mplsLdpEntityAtmStorageType OBJECT-TYPE 1476 SYNTAX StorageType 1477 MAX-ACCESS read-create 1478 STATUS current 1479 DESCRIPTION 1480 "The storage type for this entry." 1481 ::= { mplsLdpEntityAtmParmsEntry 10 } 1483 mplsLdpEntityAtmRowStatus OBJECT-TYPE 1484 SYNTAX RowStatus 1485 MAX-ACCESS read-create 1486 STATUS current 1487 DESCRIPTION 1488 "An object that allows entries in this table to 1489 be created and deleted using the 1490 RowStatus convention. 1492 NOTE: This RowStatus object should 1493 have the same value of the 'mplsLdpEntityRowStatus' 1494 related to this entry." 1495 ::= { mplsLdpEntityAtmParmsEntry 11 } 1497 -- 1498 -- The MPLS LDP Entity Configurable ATM Label Range Table 1499 -- 1501 mplsLdpEntityConfAtmLabelRangeTable OBJECT-TYPE 1502 SYNTAX SEQUENCE OF MplsLdpEntityConfAtmLabelRangeEntry 1503 MAX-ACCESS not-accessible 1504 STATUS current 1505 DESCRIPTION 1506 "The MPLS LDP Entity Configurable ATM Label Range Table. 1507 The purpose of this table is to provide a mechanism 1508 for specifying a contiguous range of vpi's 1509 with a contiguous range of vci's, or a 'label range' 1510 for LDP Entities. 1512 LDP Entities which use ATM must have at least one 1513 entry in this table." 1514 ::= { mplsLdpEntityAtmObjects 2 } 1516 mplsLdpEntityConfAtmLabelRangeEntry OBJECT-TYPE 1517 SYNTAX MplsLdpEntityConfAtmLabelRangeEntry 1518 MAX-ACCESS not-accessible 1519 STATUS current 1520 DESCRIPTION 1521 "A row in the LDP Entity Configurable ATM Label 1522 Range Table. One entry in this table contains 1523 information on a single range of labels 1524 represented by the configured Upper and Lower 1525 Bounds VPI/VCI pairs. These are the same 1526 data used in the Initialization Message. 1528 NOTE: The ranges for a specific LDP Entity 1529 are UNIQUE and non-overlapping. For example, 1530 for a specific LDP Entity index, there could 1531 be one entry having ConfLowerBound vpi/vci == 0/32, and 1532 ConfUpperBound vpi/vci == 0/100, and a second entry 1533 for this same interface with ConfLowerBound 1534 vpi/vci == 0/101 and ConfUpperBound vpi/vci == 0/200. 1535 However, there could not be a third entry with 1536 ConfLowerBound vpi/vci == 0/200 and 1537 ConfUpperBound vpi/vci == 0/300 because this label 1538 range overlaps with the second entry (i.e. both 1539 entries now have 0/200). 1541 A row will not be created unless a unique and 1542 non-overlapping range is specified. Thus, row 1543 creation implies a one-shot row creation of 1544 LDP EntityID and ConfLowerBound vpi/vci and 1545 ConfUpperBound vpi/vci. At least one label 1546 range entry for a specific LDP Entity MUST 1547 include the default VPI/VCI values denoted 1548 in the LDP Entity Table." 1549 INDEX { mplsLdpEntityLdpId, 1550 mplsLdpEntityIndex, 1551 mplsLdpEntityConfAtmLabelRangeMinimumVpi, 1552 mplsLdpEntityConfAtmLabelRangeMinimumVci 1553 } 1554 ::= { mplsLdpEntityConfAtmLabelRangeTable 1 } 1556 MplsLdpEntityConfAtmLabelRangeEntry ::= SEQUENCE { 1557 mplsLdpEntityConfAtmLabelRangeMinimumVpi AtmVpIdentifier, 1558 mplsLdpEntityConfAtmLabelRangeMinimumVci MplsAtmVcIdentifier, 1559 mplsLdpEntityConfAtmLabelRangeMaximumVpi AtmVpIdentifier, 1560 mplsLdpEntityConfAtmLabelRangeMaximumVci MplsAtmVcIdentifier, 1561 mplsLdpEntityConfAtmLabelRangeStorageType StorageType, 1562 mplsLdpEntityConfAtmLabelRangeRowStatus RowStatus 1563 } 1565 mplsLdpEntityConfAtmLabelRangeMinimumVpi OBJECT-TYPE 1566 SYNTAX AtmVpIdentifier 1567 MAX-ACCESS not-accessible 1568 STATUS current 1569 DESCRIPTION 1570 "The minimum VPI number configured for this range." 1571 ::= { mplsLdpEntityConfAtmLabelRangeEntry 1 } 1573 mplsLdpEntityConfAtmLabelRangeMinimumVci OBJECT-TYPE 1574 SYNTAX MplsAtmVcIdentifier 1575 MAX-ACCESS not-accessible 1576 STATUS current 1577 DESCRIPTION 1578 "The minimum VCI number configured for this range." 1579 ::= { mplsLdpEntityConfAtmLabelRangeEntry 2 } 1581 mplsLdpEntityConfAtmLabelRangeMaximumVpi OBJECT-TYPE 1582 SYNTAX AtmVpIdentifier 1583 MAX-ACCESS read-create 1584 STATUS current 1585 DESCRIPTION 1586 "The maximum VPI number configured for this range." 1587 ::= { mplsLdpEntityConfAtmLabelRangeEntry 3 } 1589 mplsLdpEntityConfAtmLabelRangeMaximumVci OBJECT-TYPE 1590 SYNTAX MplsAtmVcIdentifier 1591 MAX-ACCESS read-create 1592 STATUS current 1593 DESCRIPTION 1594 "The maximum VCI number configured for this range." 1595 ::= { mplsLdpEntityConfAtmLabelRangeEntry 4 } 1597 mplsLdpEntityConfAtmLabelRangeStorageType OBJECT-TYPE 1598 SYNTAX StorageType 1599 MAX-ACCESS read-create 1600 STATUS current 1601 DESCRIPTION 1602 "The storage type for this entry." 1603 ::= { mplsLdpEntityConfAtmLabelRangeEntry 5 } 1605 mplsLdpEntityConfAtmLabelRangeRowStatus OBJECT-TYPE 1606 SYNTAX RowStatus 1607 MAX-ACCESS read-create 1608 STATUS current 1609 DESCRIPTION 1610 "An object that allows entries in this 1611 table to be created and deleted using 1612 the RowStatus convention. 1614 There must exist at least one entry in this 1615 table for every LDP Entity that has 1616 'mplsLdpEntityOptionalParameters' object with 1617 a value of 'atmSessionParameters'. 1619 NOTE: This RowStatus object should 1620 have the same value of the 'mplsLdpEntityRowStatus' 1621 related to this entry." 1622 ::= { mplsLdpEntityConfAtmLabelRangeEntry 6 } 1624 -- 1625 -- Ldp Entity Objects for Frame Relay 1626 -- 1628 mplsLdpEntityFrameRelayObjects OBJECT IDENTIFIER ::= 1629 { mplsLdpEntityObjects 5 } 1631 mplsLdpEntityFrameRelayParmsTable OBJECT-TYPE 1632 SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayParmsEntry 1633 MAX-ACCESS not-accessible 1634 STATUS current 1635 DESCRIPTION 1636 "This table contains information about the 1637 Optional Parameters to specify what this Entity is 1638 going to specify for Frame Relay specific 1639 LDP Intialization Messages." 1640 ::= { mplsLdpEntityFrameRelayObjects 1 } 1642 mplsLdpEntityFrameRelayParmsEntry OBJECT-TYPE 1643 SYNTAX MplsLdpEntityFrameRelayParmsEntry 1644 MAX-ACCESS not-accessible 1645 STATUS current 1646 DESCRIPTION 1647 "An entry in this table represents the Frame Relay 1648 optional parameters associated with the LDP entity." 1649 INDEX { mplsLdpEntityLdpId, 1650 mplsLdpEntityIndex 1651 } 1652 ::= { mplsLdpEntityFrameRelayParmsTable 1 } 1654 MplsLdpEntityFrameRelayParmsEntry ::= SEQUENCE { 1655 mplsLdpEntityFrIfIndexOrZero InterfaceIndexOrZero, 1656 mplsLdpEntityFrMergeCap INTEGER, 1657 mplsLdpEntityFrLabelRangeComponents Unsigned32, 1658 mplsLdpEntityFrLen INTEGER, 1659 mplsLdpEntityFrVcDirectionality INTEGER, 1660 mplsLdpEntityFrParmsStorageType StorageType, 1661 mplsLdpEntityFrParmsRowStatus RowStatus 1662 } 1664 mplsLdpEntityFrIfIndexOrZero OBJECT-TYPE 1665 SYNTAX InterfaceIndexOrZero 1666 MAX-ACCESS read-create 1667 STATUS current 1668 DESCRIPTION 1669 "This value represents either the InterfaceIndex of 1670 the 'ifLayer' where the Frame Relay Labels 'owned' by this 1671 entry were created, or 0 (zero). The value of zero 1672 means that the InterfaceIndex is not known. For example, 1673 if the InterfaceIndex is created subsequent to the 1674 Frame Relay Label's creation, then it would not be known. 1675 However, if the InterfaceIndex is known, then it must 1676 be represented by this value. 1678 If an InterfaceIndex becomes known, then the 1679 network management entity (e.g. SNMP agent) responsible 1680 for this object MUST change the value from 0 (zero) to the 1681 value of the InterfaceIndex. If an Frame Relay Label is 1682 being used in forwarding data, then the value of this 1683 object MUST be the InterfaceIndex." 1684 ::= { mplsLdpEntityFrameRelayParmsEntry 1 } 1686 mplsLdpEntityFrMergeCap OBJECT-TYPE 1687 SYNTAX INTEGER { 1688 notSupported(0), 1689 supported(1) 1690 } 1691 MAX-ACCESS read-create 1692 STATUS current 1693 DESCRIPTION 1694 "This represents whether or not Frame Relay merge 1695 capability is supported." 1696 ::= { mplsLdpEntityFrameRelayParmsEntry 2 } 1698 mplsLdpEntityFrLabelRangeComponents OBJECT-TYPE 1699 SYNTAX Unsigned32 (1..65535) 1700 MAX-ACCESS read-create 1701 STATUS current 1702 DESCRIPTION 1703 "Number of LabelRange Components in the Initialization 1704 message. This also represents the number of entries 1705 in the mplsLdpEntityConfFrLabelRangeTable which correspond 1706 to this entry." 1707 ::= { mplsLdpEntityFrameRelayParmsEntry 3 } 1709 mplsLdpEntityFrLen OBJECT-TYPE 1710 SYNTAX INTEGER { 1711 tenDlciBits(0), 1712 twentyThreeDlciBits(2) 1713 } 1714 MAX-ACCESS read-create 1715 STATUS current 1716 DESCRIPTION 1717 "This object specifies the DLCI bits." 1718 ::= { mplsLdpEntityFrameRelayParmsEntry 4 } 1720 mplsLdpEntityFrVcDirectionality OBJECT-TYPE 1721 SYNTAX INTEGER { 1722 bidirectional(0), 1723 unidirection(1) 1724 } 1725 MAX-ACCESS read-create 1726 STATUS current 1727 DESCRIPTION 1728 "If the value of this object is 'bidirectional(0)', then 1729 the LSR supports the use of a given DLCI as a label for 1730 both directions independently. If the value of 1731 this object is 'unidirectional(1)', then the LSR 1732 uses the given DLCI as a label in only one direction." 1733 ::= { mplsLdpEntityFrameRelayParmsEntry 5 } 1735 mplsLdpEntityFrParmsStorageType OBJECT-TYPE 1736 SYNTAX StorageType 1737 MAX-ACCESS read-create 1738 STATUS current 1739 DESCRIPTION 1740 "The storage type for this entry." 1741 ::= { mplsLdpEntityFrameRelayParmsEntry 6 } 1743 mplsLdpEntityFrParmsRowStatus OBJECT-TYPE 1744 SYNTAX RowStatus 1745 MAX-ACCESS read-create 1746 STATUS current 1747 DESCRIPTION 1748 "An object that allows entries in this table to 1749 be created and deleted using the 1750 RowStatus convention. 1752 NOTE: This RowStatus object should 1753 have the same value of the 'mplsLdpEntityRowStatus' 1754 related to this entry." 1755 ::= { mplsLdpEntityFrameRelayParmsEntry 7 } 1757 -- 1758 -- Frame Relay Label Range Components 1759 -- 1761 mplsLdpEntityConfFrLabelRangeTable OBJECT-TYPE 1762 SYNTAX SEQUENCE OF MplsLdpEntityConfFrLabelRangeEntry 1763 MAX-ACCESS not-accessible 1764 STATUS current 1765 DESCRIPTION 1766 "This table contains information about the 1767 Optional Parameters to specify what this Entity is 1768 going to specify for Frame Relay specific 1769 LDP Intialization Messages." 1770 ::= { mplsLdpEntityFrameRelayObjects 2 } 1772 mplsLdpEntityConfFrLabelRangeEntry OBJECT-TYPE 1773 SYNTAX MplsLdpEntityConfFrLabelRangeEntry 1774 MAX-ACCESS not-accessible 1775 STATUS current 1776 DESCRIPTION 1777 "An entry in this table represents the Frame Relay 1778 optional parameters associated with the LDP entity." 1779 INDEX { mplsLdpEntityLdpId, 1780 mplsLdpEntityIndex, 1781 mplsLdpConfFrMinimumDlci 1782 } 1783 ::= { mplsLdpEntityConfFrLabelRangeTable 1 } 1785 MplsLdpEntityConfFrLabelRangeEntry ::= SEQUENCE { 1786 mplsLdpConfFrMinimumDlci Integer32, 1787 mplsLdpConfFrMaximumDlci Integer32, 1788 mplsLdpConfFrStorageType StorageType, 1789 mplsLdpConfFrRowStatus RowStatus 1790 } 1792 mplsLdpConfFrMinimumDlci OBJECT-TYPE 1793 SYNTAX Integer32(0..4194303) 1794 MAX-ACCESS not-accessible 1795 STATUS current 1796 DESCRIPTION 1797 "The lower bound which is supported. This value should 1798 be the same as that in the Frame Relay Label Range 1799 Component's Minimum DLCI field." 1800 ::= { mplsLdpEntityConfFrLabelRangeEntry 1 } 1802 mplsLdpConfFrMaximumDlci OBJECT-TYPE 1803 SYNTAX Integer32 (0..4194303) 1804 MAX-ACCESS read-create 1805 STATUS current 1806 DESCRIPTION 1807 "The upper bound which is supported. This value should 1808 be the same as that in the Frame Relay Label Range 1809 Component's Maximum DLCI field." 1810 ::= { mplsLdpEntityConfFrLabelRangeEntry 2 } 1812 mplsLdpConfFrStorageType OBJECT-TYPE 1813 SYNTAX StorageType 1814 MAX-ACCESS read-create 1815 STATUS current 1816 DESCRIPTION 1817 "The storage type for this entry." 1818 ::= { mplsLdpEntityConfFrLabelRangeEntry 3 } 1820 mplsLdpConfFrRowStatus OBJECT-TYPE 1821 SYNTAX RowStatus 1822 MAX-ACCESS read-create 1823 STATUS current 1824 DESCRIPTION 1825 "An object that allows entries in this table to 1826 be created and deleted using the 1827 RowStatus convention. 1829 If the value of the object 1830 'mplsLdpEntityOptionalParameters' contains the 1831 value of 'frameRelaySessionParameters(3)' then 1832 there must be at least one corresponding entry 1833 in this table. 1835 NOTE: This RowStatus object should 1836 have the same value of the 'mplsLdpEntityRowStatus' 1837 related to this entry." 1838 ::= { mplsLdpEntityConfFrLabelRangeEntry 4 } 1840 -- 1841 -- The MPLS LDP Entity Statistics Table 1842 -- 1844 mplsLdpEntityStatsTable OBJECT-TYPE 1845 SYNTAX SEQUENCE OF MplsLdpEntityStatsEntry 1846 MAX-ACCESS not-accessible 1847 STATUS current 1848 DESCRIPTION 1849 "This table is a read-only table which augments 1850 the mplsLdpEntityTable. The purpose of this 1851 table is to keep statistical information about 1852 the LDP Entities on the LSR." 1853 ::= { mplsLdpEntityObjects 6 } 1855 mplsLdpEntityStatsEntry OBJECT-TYPE 1856 SYNTAX MplsLdpEntityStatsEntry 1857 MAX-ACCESS not-accessible 1858 STATUS current 1859 DESCRIPTION 1860 "A row in this table contains statistical information 1861 about an LDP Entity. Some counters contained in a 1862 row are for fatal errors received during a former 1863 LDP Session associated with this entry. For example, 1864 an Ldp Pdu received on a TCP connection during an 1865 LDP Session contains a fatal error. That 1866 error is counted here, because the 1867 session is terminated. 1869 If the error is NOT fatal (i.e. and the Session 1870 remains), then the error is counted in the 1871 mplsLdpSessionStatsEntry." 1872 AUGMENTS { mplsLdpEntityEntry } 1873 ::= { mplsLdpEntityStatsTable 1 } 1875 MplsLdpEntityStatsEntry ::= SEQUENCE { 1876 mplsLdpAttemptedSessions Counter32, 1877 mplsLdpSessionRejectedNoHelloErrors Counter32, 1878 mplsLdpSessionRejectedAdvertisementErrors Counter32, 1879 mplsLdpSessionRejectedMaxPduErrors Counter32, 1880 mplsLdpSessionRejectedLabelRangeErrors Counter32, 1881 mplsLdpBadLdpIdentifierErrors Counter32, 1882 mplsLdpBadPduLengthErrors Counter32, 1883 mplsLdpBadMessageLengthErrors Counter32, 1884 mplsLdpBadTlvLengthErrors Counter32, 1885 mplsLdpMalformedTlvValueErrors Counter32, 1886 mplsLdpKeepAliveTimerExpiredErrors Counter32, 1887 mplsLdpShutdownNotifReceived Counter32, 1888 mplsLdpShutdownNotifSent Counter32 1889 } 1891 mplsLdpAttemptedSessions OBJECT-TYPE 1892 SYNTAX Counter32 1893 MAX-ACCESS read-only 1894 STATUS current 1895 DESCRIPTION 1896 "A count of the total attempted sessions for 1897 this LDP Entity." 1898 ::= { mplsLdpEntityStatsEntry 1 } 1900 mplsLdpSessionRejectedNoHelloErrors OBJECT-TYPE 1901 SYNTAX Counter32 1902 MAX-ACCESS read-only 1903 STATUS current 1904 DESCRIPTION 1905 "A count of the Session Rejected/No Hello Error 1906 Notification Messages sent or received by 1907 this LDP Entity." 1908 ::= { mplsLdpEntityStatsEntry 2 } 1910 mplsLdpSessionRejectedAdvertisementErrors OBJECT-TYPE 1911 SYNTAX Counter32 1912 MAX-ACCESS read-only 1913 STATUS current 1914 DESCRIPTION 1915 "A count of the Session Rejected/Parameters 1916 Advertisement Mode Error Notification Messages sent 1917 or received by this LDP Entity." 1918 ::= { mplsLdpEntityStatsEntry 3 } 1920 mplsLdpSessionRejectedMaxPduErrors OBJECT-TYPE 1921 SYNTAX Counter32 1922 MAX-ACCESS read-only 1923 STATUS current 1924 DESCRIPTION 1925 "A count of the Session Rejected/Parameters 1926 Max Pdu Length Error Notification Messages sent 1927 or received by this LDP Entity." 1928 ::= { mplsLdpEntityStatsEntry 4 } 1930 mplsLdpSessionRejectedLabelRangeErrors OBJECT-TYPE 1931 SYNTAX Counter32 1932 MAX-ACCESS read-only 1933 STATUS current 1934 DESCRIPTION 1935 "A count of the Session Rejected/Parameters 1936 Label Range Notification Messages sent 1937 or received by this LDP Entity." 1938 ::= { mplsLdpEntityStatsEntry 5 } 1940 mplsLdpBadLdpIdentifierErrors OBJECT-TYPE 1941 SYNTAX Counter32 1942 MAX-ACCESS read-only 1943 STATUS current 1944 DESCRIPTION 1945 "This object counts the number of Bad LDP Identifier 1946 Fatal Errors detected by the session(s) 1947 (past and present) associated with this LDP Entity." 1949 REFERENCE 1950 "LDP Specification, Section 3.5.1.2." 1951 ::= { mplsLdpEntityStatsEntry 6 } 1953 mplsLdpBadPduLengthErrors OBJECT-TYPE 1954 SYNTAX Counter32 1955 MAX-ACCESS read-only 1956 STATUS current 1957 DESCRIPTION 1958 "This object counts the number of Bad Pdu Length 1959 Fatal Errors detected by the session(s) 1960 (past and present) associated with this LDP Entity." 1961 REFERENCE 1962 "LDP Specification, Section 3.5.1.2." 1963 ::= { mplsLdpEntityStatsEntry 7 } 1965 mplsLdpBadMessageLengthErrors OBJECT-TYPE 1966 SYNTAX Counter32 1967 MAX-ACCESS read-only 1968 STATUS current 1969 DESCRIPTION 1970 "This object counts the number of Bad Message 1971 Length Fatal Errors detected by the session(s) 1972 (past and present) associated with this LDP Entity." 1973 REFERENCE 1974 "LDP Specification, Section 3.5.1.2." 1975 ::= { mplsLdpEntityStatsEntry 8 } 1977 mplsLdpBadTlvLengthErrors OBJECT-TYPE 1978 SYNTAX Counter32 1979 MAX-ACCESS read-only 1980 STATUS current 1981 DESCRIPTION 1982 "This object counts the number of Bad TLV 1983 Length Fatal Errors detected by the session(s) 1984 (past and present) associated with this LDP Entity." 1985 REFERENCE 1986 "LDP Specification, Section 3.5.1.2." 1987 ::= { mplsLdpEntityStatsEntry 9 } 1989 mplsLdpMalformedTlvValueErrors OBJECT-TYPE 1990 SYNTAX Counter32 1991 MAX-ACCESS read-only 1992 STATUS current 1993 DESCRIPTION 1994 "This object counts the number of Malformed TLV 1995 Value Fatal Errors detected by the session(s) 1996 (past and present) associated with this 1997 LDP Entity." 1998 REFERENCE 1999 "LDP Specification, Section 3.5.1.2." 2000 ::= { mplsLdpEntityStatsEntry 10 } 2002 mplsLdpKeepAliveTimerExpiredErrors OBJECT-TYPE 2003 SYNTAX Counter32 2004 MAX-ACCESS read-only 2005 STATUS current 2006 DESCRIPTION 2007 "This object counts the number of Session Keep Alive 2008 Timer Expired Errors detected by the session(s) 2009 (past and present) associated with this LDP Entity." 2010 REFERENCE 2011 "LDP Specification, Section 3.5.1.2." 2012 ::= { mplsLdpEntityStatsEntry 11 } 2014 mplsLdpShutdownNotifReceived OBJECT-TYPE 2015 SYNTAX Counter32 2016 MAX-ACCESS read-only 2017 STATUS current 2018 DESCRIPTION 2019 "This object counts the number of Shutdown Notfications 2020 received related to session(s) (past and present) 2021 associated with this LDP Entity." 2022 ::= { mplsLdpEntityStatsEntry 12 } 2024 mplsLdpShutdownNotifSent OBJECT-TYPE 2025 SYNTAX Counter32 2026 MAX-ACCESS read-only 2027 STATUS current 2028 DESCRIPTION 2029 "This object counts the number of Shutdown Notfications 2030 sent related to session(s) (past and present) associated 2031 with this LDP Entity." 2032 ::= { mplsLdpEntityStatsEntry 13 } 2034 -- 2035 -- The MPLS LDP Peer Table 2036 -- 2038 mplsLdpSessionObjects OBJECT IDENTIFIER ::= 2039 { mplsLdpObjects 3 } 2041 mplsLdpPeerTable OBJECT-TYPE 2042 SYNTAX SEQUENCE OF MplsLdpPeerEntry 2043 MAX-ACCESS not-accessible 2044 STATUS current 2045 DESCRIPTION 2046 "Information about LDP peers known by Entities in 2047 the mplsLdpEntityTable. The information in this table 2048 is based on information from the Entity-Peer interaction 2049 during session initialization but is not appropriate 2050 for the mplsLdpSessionTable, because objects in this 2051 table may or may not be used in session establishment." 2052 ::= { mplsLdpSessionObjects 1 } 2054 mplsLdpPeerEntry OBJECT-TYPE 2055 SYNTAX MplsLdpPeerEntry 2056 MAX-ACCESS not-accessible 2057 STATUS current 2058 DESCRIPTION 2059 "Information about a single Peer which is related 2060 to a Session. NOTE: this table is used to 2061 augment the mplsLdpSessionTable." 2062 INDEX { mplsLdpEntityLdpId, 2063 mplsLdpEntityIndex, 2064 mplsLdpPeerLdpId } 2065 ::= { mplsLdpPeerTable 1 } 2067 MplsLdpPeerEntry ::= SEQUENCE { 2068 mplsLdpPeerLdpId MplsLdpIdentifier, 2069 mplsLdpPeerLabelDistributionMethod INTEGER, 2070 mplsLdpPeerLoopDetectionForPV INTEGER, 2071 mplsLdpPeerPathVectorLimit Integer32 2072 } 2074 mplsLdpPeerLdpId OBJECT-TYPE 2075 SYNTAX MplsLdpIdentifier 2076 MAX-ACCESS not-accessible 2077 STATUS current 2078 DESCRIPTION 2079 "The LDP identifier of this LDP Peer." 2080 ::= { mplsLdpPeerEntry 1 } 2082 mplsLdpPeerLabelDistributionMethod OBJECT-TYPE 2083 SYNTAX INTEGER { 2084 downstreamOnDemand(1), 2085 downstreamUnsolicited(2) 2086 } 2087 MAX-ACCESS read-only 2088 STATUS current 2089 DESCRIPTION 2090 "For any given LDP session, the method of 2091 label distribution must be specified." 2092 ::= { mplsLdpPeerEntry 2 } 2094 mplsLdpPeerLoopDetectionForPV OBJECT-TYPE 2095 SYNTAX INTEGER { 2096 disabled(0), 2097 enabled(1) 2099 } 2100 MAX-ACCESS read-only 2101 STATUS current 2102 DESCRIPTION 2103 "An indication of whether loop detection based 2104 on path vectors is disabled or enabled for this Peer. 2106 If this object has a value of disabled(0), 2107 then loop detection is disabled. Otherwise, if this 2108 object has a value of enabled(1), then loop detection 2109 based on path vectors is enabled." 2110 ::= { mplsLdpPeerEntry 3 } 2112 mplsLdpPeerPathVectorLimit OBJECT-TYPE 2113 SYNTAX Integer32 (0..255) 2114 MAX-ACCESS read-only 2115 STATUS current 2116 DESCRIPTION 2117 "If the value of 'mplsLdpPeerLoopDetectionForPV' for 2118 this entry is 'enabled(1)', the this object represents 2119 that Path Vector Limit for this peer. 2121 If the value of 'mplsLdpPeerLoopDetectionForPV' for 2122 this entry is 'disabled(0)', then this value should 2123 be 0 (zero)." 2124 ::= { mplsLdpPeerEntry 4 } 2126 -- 2127 -- The MPLS LDP Hello Adjacency Table 2128 -- 2130 mplsLdpHelloAdjacencyObjects OBJECT IDENTIFIER ::= 2131 { mplsLdpSessionObjects 2 } 2133 mplsLdpHelloAdjacencyTable OBJECT-TYPE 2134 SYNTAX SEQUENCE OF MplsLdpHelloAdjacencyEntry 2135 MAX-ACCESS not-accessible 2136 STATUS current 2137 DESCRIPTION 2138 "A table of Hello Adjacencies for Sessions." 2139 ::= { mplsLdpHelloAdjacencyObjects 1 } 2141 mplsLdpHelloAdjacencyEntry OBJECT-TYPE 2142 SYNTAX MplsLdpHelloAdjacencyEntry 2143 MAX-ACCESS not-accessible 2144 STATUS current 2145 DESCRIPTION 2146 "Each row represents a single LDP Hello Adjacency. 2147 An LDP Session can have one or more Hello adjacencies." 2148 INDEX { mplsLdpEntityLdpId, 2149 mplsLdpEntityIndex, 2150 mplsLdpPeerLdpId, 2151 mplsLdpHelloAdjacencyIndex } 2152 ::= { mplsLdpHelloAdjacencyTable 1 } 2154 MplsLdpHelloAdjacencyEntry ::= SEQUENCE { 2155 mplsLdpHelloAdjacencyIndex Unsigned32, 2156 mplsLdpHelloAdjacencyHoldTimeRemaining TimeInterval, 2157 mplsLdpHelloAdjacencyType INTEGER 2158 } 2160 mplsLdpHelloAdjacencyIndex OBJECT-TYPE 2161 SYNTAX Unsigned32 (1..4294967295) 2162 MAX-ACCESS not-accessible 2163 STATUS current 2164 DESCRIPTION 2165 "An identifier for this specific adjacency." 2166 ::= { mplsLdpHelloAdjacencyEntry 1 } 2168 mplsLdpHelloAdjacencyHoldTimeRemaining OBJECT-TYPE 2169 SYNTAX TimeInterval 2170 MAX-ACCESS read-only 2171 STATUS current 2172 DESCRIPTION 2173 "The time remaining for this Hello Adjacency. 2174 This interval will change when the 'next' 2175 Hello message which corresponds to this 2176 Hello Adjacency is received." 2177 ::= { mplsLdpHelloAdjacencyEntry 2 } 2179 mplsLdpHelloAdjacencyType OBJECT-TYPE 2180 SYNTAX INTEGER { 2181 link(1), 2182 targeted(2) 2183 } 2184 MAX-ACCESS read-only 2185 STATUS current 2186 DESCRIPTION 2187 "This adjacency is the result of a 'link' 2188 hello if the value of this object is link(1). 2189 Otherwise, it is a result of a 'targeted' 2190 hello, targeted(2)." 2191 ::= { mplsLdpHelloAdjacencyEntry 3 } 2193 -- 2194 -- The MPLS LDP Sessions Table 2195 -- 2197 mplsLdpSessionUpDownTrapEnable OBJECT-TYPE 2198 SYNTAX INTEGER { 2199 enabled(1), 2200 disabled(2) 2201 } 2202 MAX-ACCESS read-write 2203 STATUS current 2204 DESCRIPTION 2205 "Indicates whether the traps, 'mplsLdpSessionUp' and 2206 'mplsLdpSessionDown' will be generated or not. 2208 If the value of this object is 'enabled(1)' 2209 then the traps will generated. If the value 2210 of this object is 'disabled(2)' then the 2211 traps will not be generated. The DEFVAL 2212 is set to 'disabled(2)'." 2213 DEFVAL { disabled } 2214 ::= { mplsLdpSessionObjects 3 } 2216 mplsLdpSessionTable OBJECT-TYPE 2217 SYNTAX SEQUENCE OF MplsLdpSessionEntry 2218 MAX-ACCESS not-accessible 2219 STATUS current 2220 DESCRIPTION 2221 "A table of Sessions between the LDP Entities and 2222 LDP Peers. Each row represents a single session." 2223 ::= { mplsLdpSessionObjects 4 } 2225 mplsLdpSessionEntry OBJECT-TYPE 2226 SYNTAX MplsLdpSessionEntry 2227 MAX-ACCESS not-accessible 2228 STATUS current 2229 DESCRIPTION 2230 "An entry in this table represents information on a 2231 single session between an LDP Entity and LDP Peer. 2232 The information contained in a row is read-only. 2234 Please note: the Path Vector Limit for the 2235 Session is the value which is configured in 2236 the corresponding mplsLdpEntityEntry. The 2237 Peer's Path Vector Limit is in noted in the 2238 mplsLdpPeerTable. 2240 Values which may differ from those configured are 2241 noted in the objects of this table, the 2242 mplsLdpAtmSessionTable and the 2243 mplsLdpFrameRelaySessionTable. A value will 2244 differ if it was negotiated between the 2245 Entity and the Peer. Values may or may not 2246 be negotiated. For example, if the values 2247 are the same then no negotiation takes place. 2248 If they are negotiated, then they may differ." 2249 AUGMENTS { mplsLdpPeerEntry } 2250 ::= { mplsLdpSessionTable 1 } 2252 MplsLdpSessionEntry ::= SEQUENCE { 2253 mplsLdpSessionState INTEGER, 2254 mplsLdpSessionProtocolVersion Integer32, 2255 mplsLdpSessionKeepAliveHoldTimeRemaining TimeInterval, 2256 mplsLdpSessionMaxPduLength Unsigned32, 2257 mplsLdpSessionDiscontinuityTime TimeStamp 2258 } 2260 mplsLdpSessionState OBJECT-TYPE 2261 SYNTAX INTEGER { 2262 nonexistent(1), 2263 initialized(2), 2264 openrec(3), 2265 opensent(4), 2266 operational(5) 2267 } 2268 MAX-ACCESS read-only 2269 STATUS current 2270 DESCRIPTION 2271 "The current state of the session, all of the 2272 states 1 - 5 are based on the state machine for 2273 session negotiation behavior." 2274 ::= { mplsLdpSessionEntry 1 } 2276 mplsLdpSessionProtocolVersion OBJECT-TYPE 2277 SYNTAX Integer32(1..65535) 2278 MAX-ACCESS read-only 2279 STATUS current 2280 DESCRIPTION 2281 "The version of the LDP Protocol which 2282 this session is using." 2283 ::= { mplsLdpSessionEntry 2 } 2285 mplsLdpSessionKeepAliveHoldTimeRemaining OBJECT-TYPE 2286 SYNTAX TimeInterval 2287 MAX-ACCESS read-only 2288 STATUS current 2289 DESCRIPTION 2290 "The keep alive hold time remaining for this session." 2292 ::= { mplsLdpSessionEntry 3 } 2294 mplsLdpSessionMaxPduLength OBJECT-TYPE 2295 SYNTAX Unsigned32 (1..65535) 2296 MAX-ACCESS read-only 2297 STATUS current 2298 DESCRIPTION 2299 "The value of maximum allowable length for LDP PDUs for 2300 this session. This value may have been negotiated during 2301 the Session Initialization." 2302 ::= { mplsLdpSessionEntry 4 } 2304 mplsLdpSessionDiscontinuityTime OBJECT-TYPE 2305 SYNTAX TimeStamp 2306 MAX-ACCESS read-only 2307 STATUS current 2308 DESCRIPTION 2309 "The value of sysUpTime on the most recent occasion at 2310 which any one or more of this session's counters 2311 suffered a discontinuity. The relevant counters are 2312 the specific instances associated with this session 2313 of any Counter32 or Counter64 object contained in the 2314 mplsLdpSessionStatsTable. If no such discontinuities have 2315 occurred since the last re-initialization of the local 2316 management subsystem, then this object contains a zero 2317 value. 2319 Also, an NMS can distinguish when a session 2320 between a given Entity and Peer goes away and then is 2321 're-established'. This value would change and 2322 thus indicate to the NMS that this is a 2323 different session." 2324 ::= { mplsLdpSessionEntry 5 } 2326 -- 2327 -- MPLS LDP ATM Session Information 2328 -- 2330 mplsLdpAtmSessionTable OBJECT-TYPE 2331 SYNTAX SEQUENCE OF MplsLdpAtmSessionEntry 2332 MAX-ACCESS not-accessible 2333 STATUS current 2334 DESCRIPTION 2335 "A table which relates Sessions in the 2336 'mplsLdpSessionTable' and their label 2337 range intersections. There could be one 2338 or more label range intersections between an 2339 LDP Entity and LDP Peer using ATM as the underlying 2340 media. Each row represents a single label range 2341 intersection. 2343 NOTE: this table cannot use the 'AUGMENTS' 2344 clause because there is not necessarily a one-to-one 2345 mapping between this table and the mplsLdpSessionTable." 2346 ::= { mplsLdpSessionObjects 5 } 2348 mplsLdpAtmSessionEntry OBJECT-TYPE 2349 SYNTAX MplsLdpAtmSessionEntry 2350 MAX-ACCESS not-accessible 2351 STATUS current 2352 DESCRIPTION 2353 "An entry in this table represents information on a 2354 single label range intersection between an LDP Entity 2355 and LDP Peer. 2357 The information contained in a row is read-only." 2358 INDEX { mplsLdpEntityLdpId, 2359 mplsLdpEntityIndex, 2360 mplsLdpPeerLdpId, 2361 mplsLdpSessionAtmLabelRangeLowerBoundVpi, 2362 mplsLdpSessionAtmLabelRangeLowerBoundVci 2364 } 2365 ::= { mplsLdpAtmSessionTable 1 } 2367 MplsLdpAtmSessionEntry ::= SEQUENCE { 2368 mplsLdpSessionAtmLabelRangeLowerBoundVpi AtmVpIdentifier, 2369 mplsLdpSessionAtmLabelRangeLowerBoundVci MplsAtmVcIdentifier, 2370 mplsLdpSessionAtmLabelRangeUpperBoundVpi AtmVpIdentifier, 2371 mplsLdpSessionAtmLabelRangeUpperBoundVci MplsAtmVcIdentifier 2372 } 2374 mplsLdpSessionAtmLabelRangeLowerBoundVpi OBJECT-TYPE 2375 SYNTAX AtmVpIdentifier 2376 MAX-ACCESS not-accessible 2377 STATUS current 2378 DESCRIPTION 2379 "The minimum VPI number for this range." 2380 ::= { mplsLdpAtmSessionEntry 1 } 2382 mplsLdpSessionAtmLabelRangeLowerBoundVci OBJECT-TYPE 2383 SYNTAX MplsAtmVcIdentifier 2384 MAX-ACCESS not-accessible 2385 STATUS current 2386 DESCRIPTION 2387 "The minimum VCI number for this range." 2388 ::= { mplsLdpAtmSessionEntry 2 } 2390 mplsLdpSessionAtmLabelRangeUpperBoundVpi OBJECT-TYPE 2391 SYNTAX AtmVpIdentifier 2392 MAX-ACCESS read-only 2393 STATUS current 2394 DESCRIPTION 2395 "The maximum VPI number for this range." 2396 ::= { mplsLdpAtmSessionEntry 3 } 2398 mplsLdpSessionAtmLabelRangeUpperBoundVci OBJECT-TYPE 2399 SYNTAX MplsAtmVcIdentifier 2400 MAX-ACCESS read-only 2401 STATUS current 2402 DESCRIPTION 2403 "The maximum VCI number for this range." 2404 ::= { mplsLdpAtmSessionEntry 4 } 2406 -- 2407 -- MPLS LDP Frame Relay Session Information 2408 -- 2410 mplsLdpFrameRelaySessionTable OBJECT-TYPE 2411 SYNTAX SEQUENCE OF MplsLdpFrameRelaySessionEntry 2412 MAX-ACCESS not-accessible 2413 STATUS current 2414 DESCRIPTION 2415 "A table of Frame Relay label range intersections 2416 between the LDP Entities and LDP Peers. 2417 Each row represents a single label range intersection. 2419 NOTE: this table cannot use the 'AUGMENTS' 2420 clause because there is not necessarily a one-to-one 2421 mapping between this table and the mplsLdpSessionTable." 2422 ::= { mplsLdpSessionObjects 6 } 2424 mplsLdpFrameRelaySessionEntry OBJECT-TYPE 2425 SYNTAX MplsLdpFrameRelaySessionEntry 2426 MAX-ACCESS not-accessible 2427 STATUS current 2428 DESCRIPTION 2429 "An entry in this table represents information on a 2430 single label range intersection between an 2431 LDP Entity and LDP Peer. 2433 The information contained in a row is read-only." 2434 INDEX { mplsLdpEntityLdpId, 2435 mplsLdpEntityIndex, 2436 mplsLdpPeerLdpId, 2437 mplsLdpFrSessionMinDlci 2438 } 2439 ::= { mplsLdpFrameRelaySessionTable 1 } 2441 MplsLdpFrameRelaySessionEntry ::= SEQUENCE { 2442 mplsLdpFrSessionMinDlci Integer32, 2443 mplsLdpFrSessionMaxDlci Integer32, 2444 mplsLdpFrSessionLen INTEGER 2445 } 2447 mplsLdpFrSessionMinDlci OBJECT-TYPE 2448 SYNTAX Integer32(0..4194303) 2449 MAX-ACCESS not-accessible 2450 STATUS current 2451 DESCRIPTION 2452 "The lower bound of DLCIs which are supported." 2453 ::= { mplsLdpFrameRelaySessionEntry 1 } 2455 mplsLdpFrSessionMaxDlci OBJECT-TYPE 2456 SYNTAX Integer32 (0..4194303) 2457 MAX-ACCESS read-only 2458 STATUS current 2459 DESCRIPTION 2460 "The upper bound of DLCIs which are supported." 2461 ::= { mplsLdpFrameRelaySessionEntry 2 } 2463 mplsLdpFrSessionLen OBJECT-TYPE 2464 SYNTAX INTEGER { 2465 tenDlciBits(0), 2466 twentyThreeDlciBits(2) 2467 } 2468 MAX-ACCESS read-only 2469 STATUS current 2470 DESCRIPTION 2471 "This object specifies the DLCI bits." 2472 ::= { mplsLdpFrameRelaySessionEntry 3 } 2474 -- 2475 -- The MPLS LDP Session Statistics Table 2476 -- 2478 mplsLdpSessionStatsTable OBJECT-TYPE 2479 SYNTAX SEQUENCE OF MplsLdpSessionStatsEntry 2480 MAX-ACCESS not-accessible 2481 STATUS current 2482 DESCRIPTION 2483 "A table of statistics for Sessions between 2484 LDP Entities and LDP Peers." 2485 ::= { mplsLdpSessionObjects 7 } 2487 mplsLdpSessionStatsEntry OBJECT-TYPE 2488 SYNTAX MplsLdpSessionStatsEntry 2489 MAX-ACCESS not-accessible 2490 STATUS current 2491 DESCRIPTION 2492 "An entry in this table represents statistical 2493 information on a single session between an LDP 2494 Entity and LDP Peer." 2495 AUGMENTS { mplsLdpPeerEntry } 2496 ::= { mplsLdpSessionStatsTable 1 } 2498 MplsLdpSessionStatsEntry ::= SEQUENCE { 2499 mplsLdpSessionStatsUnknownMessageTypeErrors Counter32, 2500 mplsLdpSessionStatsUnknownTlvErrors Counter32 2501 } 2503 mplsLdpSessionStatsUnknownMessageTypeErrors OBJECT-TYPE 2504 SYNTAX Counter32 2505 MAX-ACCESS read-only 2506 STATUS current 2507 DESCRIPTION 2508 "This object counts the number of Unknown Message Type 2509 Errors detected during this session. 2511 Discontinuities in the value of this counter can occur 2512 at re-initialization of the management system, and at 2513 other times as indicated by the value of 2514 mplsLdpSeeionDiscontinuityTime." 2515 ::= { mplsLdpSessionStatsEntry 1 } 2517 mplsLdpSessionStatsUnknownTlvErrors OBJECT-TYPE 2518 SYNTAX Counter32 2519 MAX-ACCESS read-only 2520 STATUS current 2521 DESCRIPTION 2522 "This object counts the number of Unknown TLV Errors 2523 detected during this session. 2525 Discontinuities in the value of this counter can occur 2526 at re-initialization of the management system, and at 2527 other times as indicated by the value of 2528 mplsLdpSeeionDiscontinuityTime." 2529 ::= { mplsLdpSessionStatsEntry 2 } 2531 -- 2532 -- Mpls FEC Table 2533 -- 2534 mplsFecObjects OBJECT IDENTIFIER ::= 2535 { mplsLdpSessionObjects 8 } 2537 mplsFecIndexNext OBJECT-TYPE 2538 SYNTAX Unsigned32 (0..4294967295) 2539 MAX-ACCESS read-only 2540 STATUS current 2541 DESCRIPTION 2542 "This object contains an appropriate value to 2543 be used for mplsFecIndex when creating 2544 entries in the mplsFecTable. The value 2545 0 indicates that no unassigned entries are 2546 available. To obtain the mplsFecIndex 2547 value for a new entry, the manager issues a 2548 management protocol retrieval operation to obtain 2549 the current value of this object. After each 2550 retrieval, the agent should modify the value to 2551 the next unassigned index." 2552 ::= { mplsFecObjects 1 } 2554 mplsFecTable OBJECT-TYPE 2555 SYNTAX SEQUENCE OF MplsFecEntry 2556 MAX-ACCESS not-accessible 2557 STATUS current 2558 DESCRIPTION 2559 "This table represents the FEC 2560 (Forwarding Equivalence Class) 2561 Information associated with an LSP." 2562 ::= { mplsFecObjects 2 } 2564 mplsFecEntry OBJECT-TYPE 2565 SYNTAX MplsFecEntry 2566 MAX-ACCESS not-accessible 2567 STATUS current 2568 DESCRIPTION 2569 "Each row represents a single FEC Element." 2570 INDEX { mplsFecIndex } 2571 ::= { mplsFecTable 1 } 2573 MplsFecEntry ::= SEQUENCE { 2574 mplsFecIndex Unsigned32, 2575 mplsFecType INTEGER, 2576 mplsFecAddressLength Integer32, 2577 mplsFecAddressFamily AddressFamilyNumbers, 2578 mplsFecAddress MplsLdpGenAddr, 2579 mplsFecStorageType StorageType, 2580 mplsFecRowStatus RowStatus 2581 } 2582 mplsFecIndex OBJECT-TYPE 2583 SYNTAX Unsigned32(1..4294967295) 2584 MAX-ACCESS not-accessible 2585 STATUS current 2586 DESCRIPTION 2587 "The index which uniquely identifies this entry." 2588 ::= { mplsFecEntry 1 } 2590 mplsFecType OBJECT-TYPE 2591 SYNTAX INTEGER { 2592 prefix(1), 2593 hostAddress(2) 2594 } 2595 MAX-ACCESS read-create 2596 STATUS current 2597 DESCRIPTION 2598 "The type of the FEC. If the value of this object 2599 is 'prefix(1)' then the FEC type described by this 2600 row is for address prefixes. 2602 If the value of this object is 'hostAddress(2)' then 2603 the FEC type described by this row is a host address." 2604 ::= { mplsFecEntry 2 } 2606 mplsFecAddressLength OBJECT-TYPE 2607 SYNTAX Integer32(0..255) 2608 MAX-ACCESS read-create 2609 STATUS current 2610 DESCRIPTION 2611 "If the value of 'mplsFecType' is 'prefix(1)' 2612 then the value of this object is the length in 2613 bits of the address prefix represented by 2614 'mplsFecAddress', or if the length is zero then 2615 this is a special value which indicates that the 2616 prefix matches all addresses. In this case the 2617 prefix is also zero (i.e. 'mplsFecAddress' will 2618 have the value of zero.)" 2619 ::= { mplsFecEntry 3 } 2621 mplsFecAddressFamily OBJECT-TYPE 2622 SYNTAX AddressFamilyNumbers 2623 MAX-ACCESS read-create 2624 STATUS current 2625 DESCRIPTION 2626 "The value of this object is from the Address Family 2627 Numbers." 2628 ::= { mplsFecEntry 4 } 2630 mplsFecAddress OBJECT-TYPE 2631 SYNTAX MplsLdpGenAddr 2632 MAX-ACCESS read-create 2633 STATUS current 2634 DESCRIPTION 2635 "If the value of 'mplsFecType' is 'prefix(1)' 2636 then the value of this object is the address prefix. 2637 If the value of the 'mplsFecAddressLength' 2638 is object is zero, then this object should also be 2639 zero. 2641 If the value of the 'mplsFecType' is 'host(2)' 2642 then this is the host address." 2643 ::= { mplsFecEntry 5 } 2645 mplsFecStorageType OBJECT-TYPE 2646 SYNTAX StorageType 2647 MAX-ACCESS read-create 2648 STATUS current 2649 DESCRIPTION 2650 "The storage type for this entry." 2651 ::= { mplsFecEntry 6 } 2653 mplsFecRowStatus OBJECT-TYPE 2654 SYNTAX RowStatus 2655 MAX-ACCESS read-create 2656 STATUS current 2657 DESCRIPTION 2658 "An object that allows entries in this table to 2659 be created and deleted using the 2660 RowStatus convention." 2661 ::= { mplsFecEntry 7 } 2663 -- 2664 -- Mapping Tables between Sessions and the LSR MIB. 2665 -- 2667 -- 2668 -- SessionInLabels and InSegment 2669 -- 2671 mplsLdpSessionInLabelMapTable OBJECT-TYPE 2672 SYNTAX SEQUENCE OF MplsLdpSessionInLabelMapEntry 2673 MAX-ACCESS not-accessible 2674 STATUS current 2675 DESCRIPTION 2676 "A table of Session's Ingress Labels which 2677 are Mapped to the LSR MIB's mplsInSegmentTable. 2678 Each row represents a single Ingress Label." 2680 ::= { mplsLdpSessionObjects 9 } 2682 mplsLdpSessionInLabelMapEntry OBJECT-TYPE 2683 SYNTAX MplsLdpSessionInLabelMapEntry 2684 MAX-ACCESS not-accessible 2685 STATUS current 2686 DESCRIPTION 2687 "An entry in this table represents information on a 2688 single LDP LSP which is represented by 2689 a session's index triple (mplsLdpEntityLdpId, 2690 mplsLdpEntityIndex, mplsLdpPeerLdpId) AND the 2691 index tuple (mplsLdpSessionInLabel, mplsInSegmentIfIndex) 2692 from the LSR MIB's mplsInSegmentTable. 2693 The information contained in a row is read-only." 2694 INDEX { mplsLdpEntityLdpId, 2695 mplsLdpEntityIndex, 2696 mplsLdpPeerLdpId, 2697 mplsLdpSessionInLabelIfIndex, 2698 mplsLdpSessionInLabel 2699 } 2700 ::= { mplsLdpSessionInLabelMapTable 1 } 2702 MplsLdpSessionInLabelMapEntry ::= SEQUENCE { 2703 mplsLdpSessionInLabelIfIndex InterfaceIndex, 2704 mplsLdpSessionInLabel MplsLabel, 2705 mplsLdpSessionInLabelType MplsLdpLabelTypes, 2706 mplsLdpSessionInLabelConnectionType INTEGER 2707 } 2709 mplsLdpSessionInLabelIfIndex OBJECT-TYPE 2710 SYNTAX InterfaceIndex 2711 MAX-ACCESS not-accessible 2712 STATUS current 2713 DESCRIPTION 2714 "The ifIndex of the 'mplsLdpSessionInLabel' which should 2715 have the same value as the 'mplsInSegmentIfIndex' in 2716 the LSR MIB." 2717 ::= { mplsLdpSessionInLabelMapEntry 1 } 2719 mplsLdpSessionInLabel OBJECT-TYPE 2720 SYNTAX MplsLabel 2721 MAX-ACCESS not-accessible 2722 STATUS current 2723 DESCRIPTION 2724 "The incoming label of this LSP. This has the same value 2725 as the 'mplsInSegmentLabel' in the LSR MIB." 2726 ::= { mplsLdpSessionInLabelMapEntry 2 } 2728 mplsLdpSessionInLabelType OBJECT-TYPE 2729 SYNTAX MplsLdpLabelTypes 2730 MAX-ACCESS read-only 2731 STATUS current 2732 DESCRIPTION 2733 "The Layer 2 Label Type for 'mplsLdpInLabel'." 2734 ::= { mplsLdpSessionInLabelMapEntry 3 } 2736 mplsLdpSessionInLabelConnectionType OBJECT-TYPE 2737 SYNTAX INTEGER { 2738 unknown(1), 2739 xconnect(2), 2740 terminates(3) 2741 } 2742 MAX-ACCESS read-only 2743 STATUS current 2744 DESCRIPTION 2745 "The type of LSP connection. 2746 The possible values are: 2748 unknown(1) -- this may be the value if the LSP 2749 is in a state of flux. It is 2750 considered to be a temporary 2751 situation. 2752 xconnect(2) -- if the mapping between the 2753 session and the insegment 2754 is associated with an LSP which 2755 is a true cross-connection. 2756 terminates(3) -- if the mapping between the 2757 session and the insegment 2758 is associated with an LSP which 2759 terminates on this LSR and is 2760 not a cross-connection." 2761 ::= { mplsLdpSessionInLabelMapEntry 4 } 2763 -- 2764 -- SessionOutLabels and OutSegment 2765 -- 2767 mplsLdpSessionOutLabelMapTable OBJECT-TYPE 2768 SYNTAX SEQUENCE OF MplsLdpSessionOutLabelMapEntry 2769 MAX-ACCESS not-accessible 2770 STATUS current 2771 DESCRIPTION 2772 "A table of Session's Egress Labels which 2773 are Mapped to the LSR MIB. 2774 Each row represents a single Egress Label." 2775 ::= { mplsLdpSessionObjects 10 } 2777 mplsLdpSessionOutLabelMapEntry OBJECT-TYPE 2778 SYNTAX MplsLdpSessionOutLabelMapEntry 2779 MAX-ACCESS not-accessible 2780 STATUS current 2781 DESCRIPTION 2782 "An entry in this table represents information on a 2783 single session between an LDP Entity and LDP Peer. 2784 The information contained in a row is read-only." 2785 INDEX { mplsLdpEntityLdpId, 2786 mplsLdpEntityIndex, 2787 mplsLdpPeerLdpId, 2788 mplsLdpSessionOutLabelIfIndex, 2789 mplsLdpSessionOutLabel 2790 } 2791 ::= { mplsLdpSessionOutLabelMapTable 1 } 2793 MplsLdpSessionOutLabelMapEntry ::= SEQUENCE { 2794 mplsLdpSessionOutLabelIfIndex InterfaceIndex, 2795 mplsLdpSessionOutLabel MplsLabel, 2796 mplsLdpSessionOutLabelType MplsLdpLabelTypes, 2797 mplsLdpSessionOutLabelConnectionType INTEGER, 2798 mplsLdpSessionOutSegmentIndex Integer32 2799 } 2801 mplsLdpSessionOutLabelIfIndex OBJECT-TYPE 2802 SYNTAX InterfaceIndex 2803 MAX-ACCESS not-accessible 2804 STATUS current 2805 DESCRIPTION 2806 "The ifIndex of the 'mplsLdpSessionOutLabel'." 2807 ::= { mplsLdpSessionOutLabelMapEntry 1 } 2809 mplsLdpSessionOutLabel OBJECT-TYPE 2810 SYNTAX MplsLabel 2811 MAX-ACCESS not-accessible 2812 STATUS current 2813 DESCRIPTION 2814 "The outgoing label of this LSP." 2815 ::= { mplsLdpSessionOutLabelMapEntry 2 } 2817 mplsLdpSessionOutLabelType OBJECT-TYPE 2818 SYNTAX MplsLdpLabelTypes 2819 MAX-ACCESS read-only 2820 STATUS current 2821 DESCRIPTION 2822 "The Layer 2 Label Type for 'mplsLdpOutLabel'." 2823 ::= { mplsLdpSessionOutLabelMapEntry 3 } 2825 mplsLdpSessionOutLabelConnectionType OBJECT-TYPE 2826 SYNTAX INTEGER { 2827 unknown(1), 2828 xconnect(2), 2829 starts(3) 2830 } 2831 MAX-ACCESS read-only 2832 STATUS current 2833 DESCRIPTION 2834 "The type of LSP connection. 2835 The possible values are: 2837 unknown(1) -- this may be the value if the LSP 2838 is in a state of flux. It is 2839 considered to be a temporary 2840 situation. 2841 xconnect(2) -- if the mapping between the 2842 session and the outsegment 2843 is associated with an LSP which 2844 is a true cross-connection. 2845 starts(3) -- if the mapping between the 2846 session and the insegment 2847 is associated with an LSP which 2848 starts on this LSR and is 2849 considered an ingress to the LSP." 2850 ::= { mplsLdpSessionOutLabelMapEntry 4 } 2852 mplsLdpSessionOutSegmentIndex OBJECT-TYPE 2853 SYNTAX Integer32(1..2147483647) 2854 MAX-ACCESS read-only 2855 STATUS current 2856 DESCRIPTION 2857 "This value should contain the same value as 2858 the 'mplsOutSegmentIndex' in the LSR MIB. 2860 NOTE: this value will never be zero, because 2861 this table only maps from Sessions to true 2862 outsegments." 2863 ::= { mplsLdpSessionOutLabelMapEntry 5 } 2865 -- 2866 -- Sessions and XConnects (LIB Information) 2867 -- 2869 mplsLdpSessionXCMapTable OBJECT-TYPE 2870 SYNTAX SEQUENCE OF MplsLdpSessionXCMapEntry 2871 MAX-ACCESS not-accessible 2872 STATUS current 2873 DESCRIPTION 2874 "A table of Session's Labels which 2875 are Mapped to the LSR MIB 's XConnect table. 2876 Each row represents a single cross connect." 2878 ::= { mplsLdpSessionObjects 11 } 2880 mplsLdpSessionXCMapEntry OBJECT-TYPE 2881 SYNTAX MplsLdpSessionXCMapEntry 2882 MAX-ACCESS not-accessible 2883 STATUS current 2884 DESCRIPTION 2885 "An entry in this table represents information on a 2886 single session between an LDP Entity and LDP Peer. 2887 The information contained in a row is read-only." 2888 INDEX { mplsLdpEntityLdpId, 2889 mplsLdpEntityIndex, 2890 mplsLdpPeerLdpId, 2891 mplsLdpSessionInLabelIfIndex, 2892 mplsLdpSessionInLabel, 2893 mplsLdpSessionOutLabelIfIndex, 2894 mplsLdpSessionOutLabel 2895 } 2896 ::= { mplsLdpSessionXCMapTable 1 } 2898 MplsLdpSessionXCMapEntry ::= SEQUENCE { 2899 mplsLdpSessionXCIndex Integer32 2900 } 2902 mplsLdpSessionXCIndex OBJECT-TYPE 2903 SYNTAX Integer32(1..2147483647) 2904 MAX-ACCESS read-only 2905 STATUS current 2906 DESCRIPTION 2907 "This value should contain the same value as 2908 the 'mplsXCIndex' in the LSR MIB. 2910 NOTE: this value will never be zero, because 2911 this table only maps from Sessions to true 2912 cross connects." 2913 ::= { mplsLdpSessionXCMapEntry 1 } 2915 -- 2916 -- XcrossConnectsFECs Table 2917 -- 2919 mplsXCsFecsTable OBJECT-TYPE 2920 SYNTAX SEQUENCE OF MplsXCsFecsEntry 2921 MAX-ACCESS not-accessible 2922 STATUS current 2923 DESCRIPTION 2924 "A table which shows the relationship between 2925 cross-connects and FECs. Each row represents 2926 a single cross connect to FEC association. 2927 This table is read-only." 2928 ::= { mplsLdpSessionObjects 13 } 2930 mplsXCsFecsEntry OBJECT-TYPE 2931 SYNTAX MplsXCsFecsEntry 2932 MAX-ACCESS not-accessible 2933 STATUS current 2934 DESCRIPTION 2935 "An entry represents a single cross connect 2936 to FEC association." 2937 INDEX { mplsLdpEntityLdpId, 2938 mplsLdpEntityIndex, 2939 mplsLdpPeerLdpId, 2940 mplsLdpSessionInLabelIfIndex, 2941 mplsLdpSessionInLabel, 2942 mplsLdpSessionOutLabelIfIndex, 2943 mplsLdpSessionOutLabel, 2944 mplsFecIndex 2945 } 2946 ::= { mplsXCsFecsTable 1 } 2948 MplsXCsFecsEntry ::= SEQUENCE { 2949 mplsXCFecOperStatus INTEGER, 2950 mplsXCFecOperStatusLastChange TimeStamp 2952 } 2954 mplsXCFecOperStatus OBJECT-TYPE 2955 SYNTAX INTEGER { 2956 unknown(1), 2957 inUse(2), 2958 notInUse(3) 2959 } 2960 MAX-ACCESS read-only 2961 STATUS current 2962 DESCRIPTION 2963 "An indication of the operational status of 2964 the FEC associated with this cross connect. 2966 unknown(1) - this is a temporary state which 2967 may indicate the LSP-FEC association 2968 is in a state of transition. 2970 inUse(2) - the FEC associated with the XC is 2971 currently being applied. 2973 notInUse(3) - the FEC associated with the XC is 2974 not being applied. Eventually, this 2975 entry may be aged out." 2977 ::= { mplsXCsFecsEntry 1 } 2979 mplsXCFecOperStatusLastChange OBJECT-TYPE 2980 SYNTAX TimeStamp 2981 MAX-ACCESS read-only 2982 STATUS current 2983 DESCRIPTION 2984 "This value of sysUpTime when the 2985 mplsXCFecOperStatus last changed state." 2986 ::= { mplsXCsFecsEntry 2 } 2988 -- 2989 -- Address Message/Address Withdraw Message Information 2990 -- 2991 -- This information is associated with a specific Session 2992 -- because Label Address Messages are sent after session 2993 -- initialization has taken place. 2994 -- 2996 mplsLdpSessionPeerAddressTable OBJECT-TYPE 2997 SYNTAX SEQUENCE OF MplsLdpSessionPeerAddressEntry 2998 MAX-ACCESS not-accessible 2999 STATUS current 3000 DESCRIPTION 3001 "This table 'extends' the mplsLdpSessionTable. 3002 This table is used to store Label Address Information 3003 from Label Address Messages received by this LSR from 3004 Peers. This table is read-only and should be updated 3005 when Label Withdraw Address Messages are received, i.e. 3006 Rows should be deleted as apropriate. 3008 NOTE: since more than one address may be contained 3009 in a Label Address Message, this table 'extends', 3010 rather than 'AUGMENTS' the mplsLdpSessionTable's 3011 information." 3012 ::= { mplsLdpSessionObjects 12 } 3014 mplsLdpSessionPeerAddressEntry OBJECT-TYPE 3015 SYNTAX MplsLdpSessionPeerAddressEntry 3016 MAX-ACCESS not-accessible 3017 STATUS current 3018 DESCRIPTION 3019 "An entry in this table represents information on 3020 session's for a single next hop address which was 3021 advertised in an Address Message from the LDP peer. 3022 The information contained in a row is read-only." 3023 INDEX { mplsLdpEntityLdpId, 3024 mplsLdpEntityIndex, 3025 mplsLdpPeerLdpId, 3026 mplsLdpSessionPeerAddressIndex 3027 } 3028 ::= { mplsLdpSessionPeerAddressTable 1 } 3030 MplsLdpSessionPeerAddressEntry ::= SEQUENCE { 3031 mplsLdpSessionPeerAddressIndex Unsigned32, 3032 mplsLdpSessionPeerNextHopAddressType AddressFamilyNumbers, 3033 mplsLdpSessionPeerNextHopAddress MplsLdpGenAddr 3034 } 3036 mplsLdpSessionPeerAddressIndex OBJECT-TYPE 3037 SYNTAX Unsigned32 (1..4294967295) 3038 MAX-ACCESS not-accessible 3039 STATUS current 3040 DESCRIPTION 3041 "An index which uniquely identifies this entry within 3042 a given session." 3043 ::= { mplsLdpSessionPeerAddressEntry 1 } 3045 mplsLdpSessionPeerNextHopAddressType OBJECT-TYPE 3046 SYNTAX AddressFamilyNumbers 3047 MAX-ACCESS read-only 3048 STATUS current 3049 DESCRIPTION 3050 "The internetwork layer address type of this Next Hop 3051 Address as specified in the Label Address Message 3052 associated with this Session. The value of this 3053 object indicates how to interpret the value of 3054 mplsLdpSessionPeerNextHopAddress." 3055 ::= { mplsLdpSessionPeerAddressEntry 2 } 3057 mplsLdpSessionPeerNextHopAddress OBJECT-TYPE 3058 SYNTAX MplsLdpGenAddr 3059 MAX-ACCESS read-only 3060 STATUS current 3061 DESCRIPTION 3062 "The value of the next hop address." 3063 REFERENCE 3064 "LDP Specification [18] defines only IPv4 for LDP Protocol 3065 Version 1, see section 3.4.3." 3066 ::= { mplsLdpSessionPeerAddressEntry 3 } 3068 --- 3069 --- Notifications 3070 --- 3072 mplsLdpNotificationPrefix OBJECT IDENTIFIER ::= 3073 { mplsLdpNotifications 0 } 3075 mplsLdpFailedInitSessionThresholdExceeded NOTIFICATION-TYPE 3076 OBJECTS { 3077 mplsLdpEntityFailedInitSessionThreshold 3078 } 3079 STATUS current 3080 DESCRIPTION 3081 "This notification is generated when the value of 3082 the 'mplsLdpEntityFailedInitSessionTrapEnable' object 3083 is 'enabled(1)' and the value of the 3084 'mplsLdpEntityFailedInitSessionThreshold' object has 3085 been exceeded." 3086 ::= { mplsLdpNotificationPrefix 1 } 3088 mplsLdpPathVectorLimitMismatch NOTIFICATION-TYPE 3089 OBJECTS { 3090 mplsLdpEntityPathVectorLimit, 3091 mplsLdpPeerPathVectorLimit 3092 } 3093 STATUS current 3094 DESCRIPTION 3095 "This notification is generated when the value 3096 of the value of the 3097 'mplsLdpEntityFailedInitSessionTrapEnable' 3098 object is 'enabled(1)' and the 3099 'mplsLdpEntityPathVectorLimit' does NOT match 3100 the value of the 'mplsLdpPeerPathVectorLimit' for 3101 a specific Entity." 3102 REFERENCE 3103 "LDP Specification, Section 3.5.3." 3104 ::= { mplsLdpNotificationPrefix 2 } 3106 mplsLdpSessionUp NOTIFICATION-TYPE 3107 OBJECTS { 3108 mplsLdpSessionState 3109 } 3110 STATUS current 3111 DESCRIPTION 3112 "Generation of this trap occurs when the 3113 'mplsLdpSessionUpDownTrapEnable' object is 'enabled(1)' 3114 and the value of 'mplsLdpSessionState' changes from 3115 any state except 'nonexistent(1)' to 'operational(5)'." 3116 ::= { mplsLdpNotificationPrefix 3 } 3118 mplsLdpSessionDown NOTIFICATION-TYPE 3119 OBJECTS { 3120 mplsLdpSessionState 3121 } 3122 STATUS current 3123 DESCRIPTION 3124 "Generation of this trap occurs when the 3125 'mplsLdpSessionUpDownTrapEnable' object is 3126 'enabled(1)' and the value of 3127 'mplsLdpSessionState' changes from 3128 'operational(5)' to any other state." 3129 ::= { mplsLdpNotificationPrefix 4 } 3131 --**************************************************************** 3132 -- Module Conformance Statement 3133 --**************************************************************** 3135 mplsLdpGroups 3136 OBJECT IDENTIFIER ::= { mplsLdpConformance 1 } 3138 mplsLdpCompliances 3139 OBJECT IDENTIFIER ::= { mplsLdpConformance 2 } 3141 -- 3142 -- Compliance Statements 3143 -- 3145 mplsLdpModuleCompliance MODULE-COMPLIANCE 3146 STATUS current 3147 DESCRIPTION 3148 "The basic implentation requirements for agents that 3149 support the MPLS LDP MIB." 3150 MODULE -- this module 3151 MANDATORY-GROUPS { mplsLdpGeneralGroup, 3152 mplsLdpNotificationsGroup 3153 } 3155 GROUP mplsLdpGenericGroup 3156 DESCRIPTION 3157 "This group must be supported if Generic Labels 3158 are used in the MPLS LDP implementation." 3160 GROUP mplsLdpAtmGroup 3161 DESCRIPTION 3162 "This group must be supported if ATM is used in the 3163 MPLS LDP implementation." 3165 GROUP mplsLdpFrameRelayGroup 3166 DESCRIPTION 3167 "This group must be supported if Frame Relay is used 3168 in the MPLS LDP implementation." 3170 GROUP mplsLdpMappingGroup 3171 DESCRIPTION 3172 "This group must be supported if the LSR MIB is 3173 implemented, specifically the mplsInSegmentTable, 3174 the mplsOutSegmentTable or the mplsXCTable." 3176 ::= { mplsLdpCompliances 1 } 3178 -- units of conformance 3180 mplsLdpGeneralGroup OBJECT-GROUP 3181 OBJECTS { 3182 mplsLdpLsrId, 3183 mplsLdpLsrLoopDetectionCapable, 3184 mplsLdpEntityIndexNext, 3185 mplsLdpEntityProtocolVersion, 3186 mplsLdpEntityAdminStatus, 3187 mplsLdpEntityOperStatus, 3188 mplsLdpEntityWellKnownTcpDiscoveryPort, 3189 mplsLdpEntityWellKnownUdpDiscoveryPort, 3190 mplsLdpEntityMaxPduLength, 3191 mplsLdpEntityKeepAliveHoldTimer, 3192 mplsLdpEntityHelloHoldTimer, 3193 mplsLdpEntityFailedInitSessionTrapEnable, 3194 mplsLdpEntityFailedInitSessionThreshold, 3195 mplsLdpEntityLabelDistributionMethod, 3196 mplsLdpEntityLabelRetentionMode, 3197 mplsLdpEntityPVLimitMismatchTrapEnable, 3198 mplsLdpEntityPathVectorLimit, 3199 mplsLdpEntityHopCountLimit, 3200 mplsLdpEntityTargetedPeer, 3201 mplsLdpEntityTargetedPeerAddrType, 3202 mplsLdpEntityTargetedPeerAddr, 3203 mplsLdpEntityOptionalParameters, 3204 mplsLdpEntityDiscontinuityTime, 3205 mplsLdpEntityStorageType, 3206 mplsLdpEntityRowStatus, 3207 mplsLdpAttemptedSessions, 3208 mplsLdpSessionRejectedNoHelloErrors, 3209 mplsLdpSessionRejectedAdvertisementErrors, 3210 mplsLdpSessionRejectedMaxPduErrors, 3211 mplsLdpSessionRejectedLabelRangeErrors, 3212 mplsLdpBadLdpIdentifierErrors, 3213 mplsLdpBadPduLengthErrors, 3214 mplsLdpBadMessageLengthErrors, 3215 mplsLdpBadTlvLengthErrors, 3216 mplsLdpMalformedTlvValueErrors, 3217 mplsLdpKeepAliveTimerExpiredErrors, 3218 mplsLdpShutdownNotifReceived, 3219 mplsLdpShutdownNotifSent, 3220 mplsLdpPeerLabelDistributionMethod, 3221 mplsLdpPeerLoopDetectionForPV, 3222 mplsLdpPeerPathVectorLimit, 3223 mplsLdpHelloAdjacencyHoldTimeRemaining, 3224 mplsLdpHelloAdjacencyType, 3225 mplsLdpSessionUpDownTrapEnable, 3226 mplsLdpSessionState, 3227 mplsLdpSessionProtocolVersion, 3228 mplsLdpSessionKeepAliveHoldTimeRemaining, 3229 mplsLdpSessionMaxPduLength, 3230 mplsLdpSessionDiscontinuityTime, 3231 mplsLdpSessionStatsUnknownMessageTypeErrors, 3232 mplsLdpSessionStatsUnknownTlvErrors, 3233 mplsLdpSessionPeerNextHopAddressType, 3234 mplsLdpSessionPeerNextHopAddress, 3235 mplsFecIndexNext, 3236 mplsFecType, 3237 mplsFecAddressFamily, 3238 mplsFecAddressLength, 3239 mplsFecAddress, 3240 mplsFecStorageType, 3241 mplsFecRowStatus 3242 } 3243 STATUS current 3244 DESCRIPTION 3245 "Objects that apply to all MPLS LDP implementations." 3246 ::= { mplsLdpGroups 1 } 3248 mplsLdpGenericGroup OBJECT-GROUP 3249 OBJECTS { 3250 mplsLdpEntityConfGenericIfIndexOrZero, 3251 mplsLdpEntityConfGenericLabelRangeStorageType, 3252 mplsLdpEntityConfGenericLabelRangeRowStatus 3253 } 3254 STATUS current 3255 DESCRIPTION 3256 "Objects that apply to all MPLS LDP implementations 3257 using Generic Lables." 3258 ::= { mplsLdpGroups 2 } 3260 mplsLdpAtmGroup OBJECT-GROUP 3261 OBJECTS { 3262 mplsLdpEntityAtmIfIndexOrZero, 3263 mplsLdpEntityAtmMergeCap, 3264 mplsLdpEntityAtmLabelRangeComponents, 3265 mplsLdpEntityAtmVcDirectionality, 3266 mplsLdpEntityAtmLsrConnectivity, 3267 mplsLdpEntityDefaultControlVpi, 3268 mplsLdpEntityDefaultControlVci, 3269 mplsLdpEntityUnlabTrafVpi, 3270 mplsLdpEntityUnlabTrafVci, 3271 mplsLdpEntityAtmStorageType, 3272 mplsLdpEntityAtmRowStatus, 3273 mplsLdpEntityConfAtmLabelRangeMaximumVpi, 3274 mplsLdpEntityConfAtmLabelRangeMaximumVci, 3275 mplsLdpEntityConfAtmLabelRangeStorageType, 3276 mplsLdpEntityConfAtmLabelRangeRowStatus, 3277 mplsLdpSessionAtmLabelRangeUpperBoundVpi, 3278 mplsLdpSessionAtmLabelRangeUpperBoundVci 3280 } 3281 STATUS current 3282 DESCRIPTION 3283 "Objects that apply to all MPLS LDP implementations 3284 over ATM." 3285 ::= { mplsLdpGroups 3 } 3287 mplsLdpFrameRelayGroup OBJECT-GROUP 3288 OBJECTS { 3289 mplsLdpEntityFrIfIndexOrZero, 3290 mplsLdpEntityFrMergeCap, 3291 mplsLdpEntityFrLabelRangeComponents, 3292 mplsLdpEntityFrLen, 3293 mplsLdpEntityFrVcDirectionality, 3294 mplsLdpEntityFrParmsStorageType, 3295 mplsLdpEntityFrParmsRowStatus, 3296 mplsLdpConfFrMaximumDlci, 3297 mplsLdpConfFrStorageType, 3298 mplsLdpConfFrRowStatus, 3299 mplsLdpFrSessionMaxDlci, 3300 mplsLdpFrSessionLen 3301 } 3302 STATUS current 3303 DESCRIPTION 3304 "Objects that apply to all MPLS LDP implementations over 3305 Frame Relay." 3306 ::= { mplsLdpGroups 4 } 3308 mplsLdpMappingGroup OBJECT-GROUP 3309 OBJECTS { 3310 mplsLdpSessionInLabelType, 3311 mplsLdpSessionInLabelConnectionType, 3312 mplsLdpSessionOutLabelType, 3313 mplsLdpSessionOutLabelConnectionType, 3314 mplsLdpSessionOutSegmentIndex, 3315 mplsLdpSessionXCIndex, 3316 mplsXCFecOperStatus, 3317 mplsXCFecOperStatusLastChange 3318 } 3319 STATUS current 3320 DESCRIPTION 3321 "These objects are optional and only need to be supported 3322 for LDP implementations which support the 3323 tables, mplsInSegmentTable, mplsOutSegmentTable 3324 and mplsXCTable, in the LSR MIB." 3325 ::= { mplsLdpGroups 5 } 3327 mplsLdpNotificationsGroup NOTIFICATION-GROUP 3328 NOTIFICATIONS { mplsLdpFailedInitSessionThresholdExceeded, 3329 mplsLdpPathVectorLimitMismatch, 3330 mplsLdpSessionUp, 3331 mplsLdpSessionDown 3332 } 3333 STATUS current 3334 DESCRIPTION 3335 "The notification(s) which an MPLS LDP implemention 3336 is required to implement." 3337 ::= { mplsLdpGroups 6 } 3339 END 3341 5. Revision History 3343 This section should be removed when this document is published as an 3344 RFC. 3346 5.1. Changes from 3348 All changes were from the second last call which took place Thursday, 3349 July 20th, until Thursday, July 27th, 2000 and are described in the 3350 remainder of this section. 3352 Remove the reference to the MPLS framework document. 3354 Add an mplsFecIndexNext type of object. 3356 Change the conformance of the FEC table objects to be part of the 3357 mplsLdpGeneralGroup. 3359 The mplsLdpEntityConfGenericTable is no longer needed because the 3360 functionality has been absorbed by the 3361 mplsLdpEntityConfGenericLabelRangeTable. The 3362 mplsLdpEntityConfGenericTable has been removed and the front section 3363 was updated accordingly. 3365 Other editorial issues, updating references, typos and so forth. 3367 5.2. Changes from 3369 The majority of changes in this revision are based on Last Call 3370 comments which were received during the last call from Thursday, 3371 March 9, 2000 to Friday, March 17, 2000, or slightly thereafter. 3372 Also, changes were made to agree with the latest specifications. 3373 These changes are described in this section. 3375 Changes due to draft-ietf-mpls-ldp-07.txt and draft-ietf-mpls-ldp- 3376 08.txt. Specifically, removing references to IPv4/IP and using router 3377 id, as appropriate. 3379 Removed vpMerge and vpAndVcMerge choices from the object, 3380 mplsLdpEntityAtmMergeCap. VP Merge is not described in [30]. 3382 The LIB Table was removed and replaced by mapping tables to map LDP 3383 LSPs created by LDP sessions to the mplsInSegment, mplsOutSegment and 3384 mplsXC tables in the LSR MIB. The conformance section was updated 3385 to include a Mapping Group which is to be implemented iff these LSR 3386 MIB tables (mplsInSegmentTable, mplsOutSegmentTable and mplsXCTable) 3387 are implemented. 3389 The front section was updated to include information on the Generic 3390 label table. 3392 Added more in the front section on on Row 3393 Creation/adminStatus/OperStatus in the LDP Entity and related tables. 3395 Added a generic label range table. NOTE: there is NO corresponding 3396 LDP message which relates to the information in this table, however, 3397 this table does provide a way for a user to 'reserve' a generic label 3398 range. 3400 A new TEXTUAL-CONVENTION, MplsAtmVcIdentifier was added. This TC has 3401 the same upper bounds as AtmVcIdentifier (from rfc2514) except that 3402 the lower bound is 32 (and not 0). The lower bound is 32 since this 3403 value is specified by [30]. 3405 Removed the scalar object mplsLsrLabelRetentionMode and added 3406 mplsLdpEntityLabelRetentionMode. The change was made to allow 3407 configuring the retention mode on a per LDP Entity basis, as opposed 3408 for the entire LSR. 3410 Typo in section 3.5.2 was fixed. 3412 Typo in the mplsLdpSessionUp notification description was fixed. 3414 Section 'LDP Notifications' was expanded to cover both the 3415 'mplsLdpSessionUp' and 'mplsLdpSessionDown' traps. Also, the objects 3416 which enable and disable these traps have been described in this 3417 Section: 3419 The 'mplsLdpEntityHopCountLoopDetection' object and the 3420 'mplsLdpEntityHopCount' object have been combined into the new 3421 object, 'mplsLdpEntityHopCountLimit'. 3423 MplsLabel has been updated to reflect the VPI value of 12 bits and 3424 not 8. 3426 Added DEFVAL clause to the 'mplsLdpEntityWellKnownDiscoveryPort' 3427 object. The default value is 646. 3429 Added UNITS and DEFVAL clauses to the 'mplsLdpEntityMaxPduLength' 3430 object. The default value is 4096 and the units is octets. 3432 Added DEFVAL clause to 'mplsLdpEntityProtocolVersion' object. The 3433 default value is 1. 3435 Added DEFVAL clause to 'mplsLdpEntityKeepAliveHoldTimer' of 40 3436 seconds. 3438 Added DEFVAL clause to 'mplsLdpEntityFailedInitSessionThreshold' 3439 object. The default value is 8. 3441 The mplsLdpEntityWellKnownDiscoveryPort was changed into two objects, 3442 one for TCP and one for UDP. The names are 3444 Typo in the description for the 3446 The mplsLdpEntityPeerTable was (re-)named mplsLdpPeerTable. The 3447 mplsLdpSessionTable now AUGMENTs the mplsLdpPeerTable in order to 3448 show that these two tables are related. There has been wording added 3449 to the mplsLdpSessionEntry description and to the description for the 3450 mplsLdpPeerTable. 3452 5.3. Changes from 3454 Editorial changes, fixing typo's, fixing wrapping lines, etc. 3456 Updated references for latest drafts, and added [31] and [32] to 3457 Reference Section. 3459 Added to the Acknowledgements Section. 3461 Changed the SYNTAX and DESCRIPTION of the 3462 'mplsLdpLsrLoopDetectionCapable' object, so that it will also support 3463 the loop detection by hop count. 3465 Combined the 'mplsLdpEntityLoopDetectionForPV' and 3466 'mplsLdpEntityPathVectorLimit' objects. The functionality of the 3467 'mplsLdpEntityLoopDectionForPV' is now denoted by the value of 0 3468 (zero) in the 'mplsLdpEntityPathVectorLimit' object. This results in 3469 one less object 'mplsLdpEntityLoopDectionForPV' but does not 3470 sacrifice functionality. 3472 Changed 'mplsLdpLibLabelType' into two objects: 3473 'mplsLdpLibInLabelType' and differ from the egress label type. The 3474 MIB now reflects this. 3476 The following items were changed as a result of the Frame Relay Forum 3477 dropping support for 17-bit DLCIs: the MplsLabel TC description has 3478 been modified, and other Frame Relay Object descriptions were also 3479 modified (as specified in this section). 3481 The MplsLabel TC was also modified and reference 3. was added to the 3482 REFERENCE Clause. 3484 MplsLdpLabelTypes TC was modified to use an enum. 3486 InterfaceIndex support was added to the Entity information. This was 3487 specifically requested by several members of the working group. An 3488 additional table, mplsLdpEntityConfGenericTable as a way to configure 3489 Generic Labels, and an object, 'mplsLdpConfGenericIfIndexOrZero was 3490 added to map the InterfaceIndex used by Generic Labels. Objects were 3491 also added to the 'mplsLdpEntityAtmParmsTable' and the and 3492 'mplsLdpEntityFrIfIndex', respectively. 3494 Changed the name of the 'mplsLdpEntityMtu' object to be 3495 'mplsLdpEntityMaxPduLength' which is more consistent with the LDP 3496 Specification. Also, the description and SYNTAX were changed. 3498 Changed the SYNTAX of the 'mplsLdpSessionMaxPduLength' to unsigned32 3499 and changed the Range from (0..65535) to (1..65535). 3501 Added and improved the front section discussion on SNMP 3502 Notifications. 3504 Also, modified the DESCRIPTION clause of the 3506 Added objects to enable/disable the sending of traps: 3508 Added an object to enable/disable sending traps for Sessions changing 3509 from Up to Down, or Down to Up. 3511 Added notifications to generate traps from session changing from Up 3512 to Down, or Down to up. 3514 Added a StorageType object to the Entity and associated tables which 3515 are configurable. 3517 Added a Discontinuity Time object to the Entity Table, 3519 Added discussion on row creation in the Entity and other associated 3520 Entity tables. This is a new Section in the Front part of the 3521 document called: 3523 Removed the 'mplsLdpEntityControlMethod'. 3525 Made 'mplsLdpFecLspId' as part of the INDEX for the FEC table. This 3526 is to allow FECs to map to multiple LSPs. Also add a RowPointer to a 3527 row in the Session Table. 3529 Added an operation status object, 'mplsLdpLspOperStatus' and a last 3530 Change object, 'mplsLdpLspLastChangeto the LIB Table. This will be 3531 used to detect whether an LSP has changed its status. 3533 Changed the name of the mplsLdpPeerTable to the 3534 mplsLdpEntityPeerTable. This table contains information relevant to 3535 Peers which are known to specific Entities. The indexing of this 3536 table has also changed to include the Row in the Entity Table that 3537 this Peer is known by. The mplsLdpHelloAdjacencyTable and the 3538 mplsLdpSessionTable have been moved under this table. Since Hello 3539 Adjacencies are related to Entity-Peer information and Sessions are 3540 related to Entity-Peer information this was seen as a comprehensive 3541 and coherent modelling. Associated descriptions in the front section 3542 and in the tables have been changed to reflect this change. 3544 Moved the 'mplsLdpConfFrLen' object from the 3545 'mplsLdpEntityConfFrLabelRangeTable' to the 3546 'mplsLdpEntityFrameRelayParmsTable' since the Frame Relay 3547 interface/port can only use one header length at a time, i.e. a 3548 specific FR interface supports one address length for all VCs on that 3549 interface. Also, changed the object so that it only supports 10 and 3550 23 bit DLCI lengths. (The 17 bit length was dropped by the Frame 3551 Relay Forum and thus, is no longer required.) The name of this 3552 object was changed from 'mplsLdpConfFrLen' to 'mplsLdpEntityFrLen' to 3553 fit in with the 'mplsLdpEntityFrameRelayParmsTable'. 3555 Removed the seventeenDlciBits(1) value from the mplsLdpFrSessionLen 3556 object. (The 17 bit length was dropped by the Frame Relay Forum and 3557 thus, is no longer required.) 3559 Corrected the range of the 'mplsLdpEntityIndexNext' object to include 3560 0 (zero). 3562 5.4. Changes from 3564 Reworded the description of the mplsLdpAtmSessionTable to clarify 3565 that one or MORE label range intersection(s) is/are represented in 3566 this table. 3568 Reworded the description of the mplsLdpFrameRelaySessionTable to 3569 clarify that one or MORE label range intersection(s) is/are 3570 represented in this table. 3572 Added a new index, mplsLdpSessionPeerIndex, to the 3573 mplsLdpSessionPeerAddressTable. This new index uniquely identifies 3574 the entry within a given session. (Since adding 3575 mplsLdpSessionPeerNextHopAddressType, 3576 mplsLdpSessionPeerNextHopAddress to the INDEX clause of the 3577 mplsLdpSessionPeerAddressTable leaves a table with only indices and 3578 no objects, the work around was to add a new index which uniquely 3579 differentiates an entry within a given session.) 3581 Quite a few changes to the mplsLdpPeerTable. First, removed the 3582 mplsLdpPeerIndex from the mplsLdpPeerTable and other tables. This 3583 index served no purpose, so was removed. Second, removed the 3584 objects: mplsLdpPeerInternetworkAddrType, and 3585 mplsLdpPeerInternetworkAddr. Third, reworded the description of this 3586 table to include information which is known during Session 3587 Intialization attempts, the specific information has to do with Loop 3588 Dection based on Path Vectors. Since Section 3.5.3 of the LDP Spec 3589 when describing the PVLim says: "Although knowledge of a peer's path 3590 vector limit will not change an LSR's behavior, it does enable the 3591 LSR to alert an operator to a possible misconfiguration." and the 3592 object mplsLdpPeerPathVectorLimit is sent as a varbind in the 3593 mplsLdpPathVectorLimitMismatch notification. 3595 Removed the mplsLdpPeerIndex from the mplsLdpHelloAdjacencyTable. 3597 Removed the "IANA Address Family Numbers MIB" section. 3599 Updated the boiler.me from the ops web page dated Weds., Dec 22, 3600 1999. 3602 Updated the Security Section from the ops web page. 3604 Added the following objects to the mplsLdpEntityTable: 3605 mplsLdpEntityControlMethod, mplsLdpEntityLoopDectionForPV, and 3606 mplsLdpEntityPathVectorLimit. 3608 Removed mplsLdpSessionLabelAdvertisement, 3609 mplsLdpSessionLoopDetectionForPV, and mplsLdpSessionPathVectorLimit 3610 from the mplsLdpSessionTable. 3612 Changed the mplsLdpPathVectorLimitMismatch Notification to send 3613 mplsLdpEntityPathVectorLimit (instead of 3614 mplsLdpSessionPathVectorLimit). 3616 Copied the MplsLabel TC from draft-ietf-mpls-lsr-mib-00.txt and 3617 replaced the MplsLdpGenAddr for mplsLdpLibInLabel and 3618 mpslLdpLibOutLabel with MplsLabel. 3620 The mplsLdpSessionIndex was removed throughout the MIB. This was 3621 replaced by the object mplsLdpSessionDiscontinuityTime. The 3622 motivation was to reduce the number of indices. 3624 The descriptions for the objects in the mplsLdpSessionStatsTable, 3625 mplsLdpSessionStatsUnknownMessageTypeErrors and 3626 mplsLdpSessionStatsUnknownTlvErrors, have been updated to include a 3627 reference to the mplsLdpSessionDiscontinuityTime object. 3629 5.5. Changes from 3631 Added Scalar Objects: mplsLdpLsrLoopDetectionPresent, and 3632 mplsLdpEntityIndexNext. 3634 Added the following objects to the mplsLdpEntityTable: 3635 mplsLdpEntityProtocolVersion, mplsLdpEntityAdminStatus, 3636 mplsLdpEntityOperStatus, mplsLdpEntityTargetedPeer, 3637 mplsLdpEntityTargetedPeerAddrType, mplsLdpEntityTargetedPeerAddr, and 3638 mplsLdpEntityHelloHoldTimer. 3640 Changed the description of the mplsLdpEntityAtmParmsTable and added 3641 the following objects to this table: 3642 mplsLdpEntityAtmLsrConnectivity, mplsLdpEntityDefaultControlVpi, 3643 mplsLdpEntityDefaultControlVci, mplsLdpEntityUnlabTrafVpi, and 3644 mplsLdpEntityUnlabTrafVci. NOTE: the last four objects were in 3645 Version 01 of the MIB but were mistakenly omitted from Version 02. 3646 Now, they are back. 3648 Changed the indexing of the mplsLdpEntityConfAtmLabelRangeTable to 3649 include the minimum VPI/VCI. This is to ensure that indices in this 3650 table are unique. 3652 Changed the indexing of the mplsLdpEntityConfFrLabelRangeTable, to 3653 include the minimum DLCI value. This is to ensure that indices in 3654 this table are unique. 3656 Added [30] to Reference Section. 3658 5.6. Changes from 3660 The MIB was updated to correspond to draft-ietf-mpls-ldp-06.txt of 3661 the LDP Specification [18]. 3663 The front section was updated. 3665 The MIB was made to be less ATM-centric. Essentially, the ATM 3666 specific objects where removed from the tables and placed in ATM 3667 specific Tables. A "type" was added to the "base" tables and a row 3668 is to be created in the ATM/FR/etc. "type" table. Apropos 3669 compliance statements were added to reflect the separation of ATM and 3670 Frame Relay objects into their respective tables. 3672 Objects for Loop Detection were removed from describing the LDP 3673 implementation (i.e. the scalars were removed) and Loop Dection 3674 objects were added to the Session Table. (Although as the LDP 3675 Specification indicates loop detection should be for an LSR within a 3676 domain.) 3678 The following tables were added: mplsLdpEntityAtmParmsTable, 3679 mplsLdpEntityConfAtmLabelRangeTable, mplsLdpFrameRelayParmsTable, 3680 mplsLdpConfFrLabelRangeTable, mplsLdpAtmSessionTable, 3681 mpslLdpFrameRelaySessionTable, mplsLdpSessionPeerAddressTable, 3682 mplsLdpLibTable, and the mplsLdpFecTable. 3684 The following notifications were added: notification for Session 3685 removal. 3687 The following objects were removed from the Session Table: 3688 mplsLdpSessionRole was removed (this can be determined by comparing 3689 LSR Ids and does not need to be explicitely in the MIB.) ATM 3690 specific objects (mplsLdpSessionAtmLabelRangeLowerBoundVpi 3691 mplsLdpSessionAtmLabelRangeLowerBoundVci, 3692 mplsLdpSessionAtmLabelRangeUpperBoundVpi 3693 mplsLdpSessionAtmLabelRangeUpperBoundVci) were removed and put into a 3694 separate table. Frame Relay objects were added in a separate table. 3696 Hello Adjacency Table was updated. 3698 The objects, mplsLdpSessionRejectedParamErrors, 3699 mplsLdpSessionRejectedNoHelloErrors, mplsLdpBadLdpIdentifierErrors, 3700 mplsLdpBadPduLengthErrors, mplsLdpBadMessageLengthErrors, 3701 mplsLdpBadTlvLengthErrors, mplsLdpMalformedTlvValueErrors, 3702 mplsLdpKeepAliveTimerExpiredErrors, mplsLdpShutdownNotifReceived, and 3703 mplsLdpShutdownNotifSent were added to the mplsLdpEntityStatsTable. 3705 The mplsLdpSessionStatsTable was added to count statics based on a 3706 per Session basis. 3708 The mplLdpPeerConfAtmLabelRangeTable has been removed. There is no 3709 need to configure information for a Peer. All information for a peer 3710 is learned, thus peer information is read-only. 3712 (Editorial) References were updated to reflect the documents which 3713 this version was based on. 3715 5.7. Changes from 3717 Textual conventions were added for the LSR Identifier and the LDP 3718 Identifier. 3720 Top-level mib structure was added. The LDP MIB falls under a proposed 3721 hierarchy of mpls.mplsProtocols. 3723 The mib hierarchy within the LDP MIB was also changed. A new branch, 3724 under mpls.mplsProtocols.mplsLdpMIB.mplsLdpObjects was added. This 3725 branch is mplsLdpLsrObjects. Currently, this contains several new 3726 scalar objects: mplsLdpLsrID, mplsLdpLsrLoopDetectionPresent, 3727 mplsLdpLsrLoopDetectinAdminStatus, mplsLdpLsrPathVectorLimit, 3728 mplsLdpLsrHopCountLimit, mplsLdpLsrLoopPreventionPresent, 3729 mplsLdpLsrLoopPreventionAdminStatus, and 3730 mplsLdpLsrLabelRetentionMode. 3732 mplsLdpEntityTable is now indexed by mplsLdpEntityIdentifier, which 3733 is the LDP Identifier used in Session establishment. 3735 mplsLdpEntityLoopDetection and mplsLdpEntityLoopPrevention objects 3736 were removed from this table. 3738 The following objects were added to the mplsLdpEntityTable: 3739 mplsLdpEntityLabelSpaceType, mplsLdpEntityUnlabTrafVpi, 3740 mplsLdpEntityUnlabTrafVci, mplsLdpEntityMergeCapability, 3741 mplsLdpEntityVcDirectionality, and 3742 mplsLdpEntityLabelDistributionMethod. 3744 The following objects were added to the mplsLdpPeerEntityTable: 3745 mplsLdpPeerLabelDistributionMethod. 3747 The following object was removed from the mplsLdpEntityStatsTable: 3748 mplsLdpEntityEstablishedSessions. 3750 References were added and revised. 3752 6. Acknowledgments 3754 The authors would like to thank the following people: Leigh 3755 McLellan, Geetha Brown, Geping Chen and Charlan Zhou from Nortel 3756 Networks, and Zoltan Takacs and Bo Augustsson from Ericsson. Also, 3757 some members of the working group were very helpful with comments and 3758 corrections to the MIB; the authors would like to thank Adrian Farrel 3759 of Data Connection, and Alan Kullberg from Harris & Jeffries. 3761 7. References 3763 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 3764 for Describing SNMP Management Frameworks", RFC 2571, April 3765 1999. 3767 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 3768 of Management Information for TCP/IP-based Internets", STD 3769 16, RFC 1155, May 1990. 3771 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 3772 16, RFC 1212, March 1991. 3774 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 3775 SNMP", RFC 1215, March 1991. 3777 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3778 Rose, M., and S. Waldbusser, "Structure of Management 3779 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 3780 1999. 3782 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3783 Rose, M., and S. Waldbusser, "Textual Conventions for 3784 SMIv2", STD 58, RFC 2579, April 1999. 3786 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3787 Rose, M., and S. Waldbusser, "Conformance Statements for 3788 SMIv2", STD 58, RFC 2580, April 1999. 3790 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 3791 Network Management Protocol", STD 15, RFC 1157, May 1990. 3793 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3794 "Introduction to Community-based SNMPv2", RFC 1901, January 3795 1996. 3797 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3798 "Transport Mappings for Version 2 of the Simple Network 3799 Management Protocol (SNMPv2)", RFC 1906, January 1996. 3801 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 3802 Processing and Dispatching for the Simple Network Management 3803 Protocol (SNMP)", RFC 2572, April 1999. 3805 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 3806 (USM) for version 3 of the Simple Network Management 3807 Protocol (SNMPv3)", RFC 2574, April 1999. 3809 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3810 "Protocol Operations for Version 2 of the Simple Network 3811 Management Protocol (SNMPv2)", RFC 1905, January 1996. 3813 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 3814 RFC 2573, April 1999. 3816 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 3817 Access Control Model (VACM) for the Simple Network 3818 Management Protocol (SNMP)", RFC 2575, April 1999. 3820 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 3821 "Introduction to Version 3 of the Internet-standard Network 3822 Management Framework", RFC 2570, April 1999. 3824 [17] Narten, T., and H. Alvestrand, "Guidelines for Writing an IANA 3825 Considerations Section in RFCs.", RFC 2434, IBM, Maxware, October 3826 1998 3828 [18] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and B. 3829 Thomas, "LDP Specification.", draft-ietf-mpls-ldp-11.txt, August 3830 2000. 3832 [19] Rosen, E., Viswananthan, A., and R. Callon, "Multiprotocol Label 3833 Switching Architecture", draft-ietf-mpls-arch-07.txt, July 2000. 3835 [20] Jamoussi, B., editor, "Constraint-Based LSP Setup using LDP", 3836 draft-ietf-mpls-cr-ldp-04.txt, July 2000. 3838 [21] Bradner, S., "Key words for use in RFCs to Indicate Requirement 3839 Levels", BCP 14, RFC 2119, Harvard University, March 1997 3841 [22] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, 3842 RFC 2026, Harvard University, October 1996 3844 [23] Srinivansan, C., Viswanathan, A., and T. Nadeau "MPLS Label Switch 3845 Router Management Information Base Using SMIv2", draft-ietf-mpls- 3846 lsr-mib-06.txt, July 2000. 3848 [24] Greene, M., Cucchiara, J., and J. Luciani, "Definition of Managed 3849 Objects for the NBMA Next Hop Resolution Protocol (NHRP)", RFC 3850 2677, August 1999. 3852 [25] Internet Assigned Numbers Authority (IANA), ADDRESS FAMILY NUMBERS, 3853 (http://www.isi.edu/in-notes/iana/assignments/address-family- 3854 numbers), for MIB 3855 (ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib). 3857 [26] Noto, M., E. Spiegel, K. Tesink, "Definition of Textual Conventions 3858 and OBJECT-IDENTITIES for ATM Management", RFC 2514, February 1999. 3860 [27] McCloghrie, K., F. Kastenholz, "The Interfaces Group MIB using 3861 SMIv2", RFC 2233, November 1997. 3863 [28] Tesink, K. (ed.) "Definitions of Managed Objects for ATM 3864 Management", RFC 2515, February 1999. 3866 [29] Grossman, D., and J. Heinanen, "Multiprotocol Encapsulation over 3867 ATM Adaptation Layer 5", RFC 2684, September 1999. 3869 [30] Davie, B., Lawrence, J., McCloghrie, K., Rekhter, Y., Rosen, E., 3870 Swallow, G. and P. Doolan, "MPLS using LDP and ATM VC Switching", 3871 draft-ietf-mpls-atm-04.txt, June 2000. 3873 [31] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D., Fedorkow, G., 3874 Li, T. and A. Conta, "MPLS Label Stack Encoding", draft-ietf-mpls- 3875 label-encaps-08.txt, July 2000. 3877 [32] Conta, A., Doolan, P., and A. Malis, "Use of Label Switching on 3878 Frame Relay Networks Specification", draft-ietf-mpls-fr-06.txt, 3879 June 2000. 3881 [33] Boscher, C., Cheval, P., Liwen, W. and E. Gray, "LDP State 3882 Machine", draft-ietf-mpls-ldp-state-03.txt, January 2000. 3884 [34] Thomas, B. and E. Gray, "LDP Applicability", draft-ietf-mpls-ldp- 3885 applic-02.txt, August 2000. 3887 [35] Daniele, M., Haberman, B., Routhier, S. and J. Schoenwaelder, 3888 "Textual Coventions for Internet Network Addresses", RFC 2851, June 3889 2000. 3891 8. Security Considerations 3893 There are a number of management objects defined in this MIB that have a 3894 MAX-ACCESS clause of read-write and/or read-create. Such objects may 3895 be considered sensitive or vulnerable in some network environments. 3896 The support for SET operations in a non-secure environment without 3897 proper protection can have a negative effect on network operations. 3899 There are a number of managed objects in this MIB that may contain 3900 sensitive information. These are contained in the mplsLdpEntityTable. 3901 The objects contained in this table are responsible for setting up or 3902 tearing down LSPs. 3904 It is thus important to control even GET access to these objects and 3905 possibly to even encrypt the values of these object when sending them 3906 over the network via SNMP. Not all versions of SNMP provide features 3907 for such a secure environment. 3909 SNMPv1 by itself is not a secure environment. Even if the network 3910 itself is secure (for example by using IPSec), even then, there is no 3911 control as to who on the secure network is allowed to access and 3912 GET/SET (read/change/create/delete) the objects in this MIB. 3914 It is recommended that the implementers consider the security 3915 features as provided by the SNMPv3 framework. Specifically, the use 3916 of the User-based Security Model RFC 2574 [RFC2574] and the View- 3917 based Access Control Model RFC 2575 [RFC2575] is recommended. 3919 It is then a customer/user responsibility to ensure that the SNMP 3920 entity giving access to an instance of this MIB, is properly 3921 configured to give access to the objects only to those principals 3922 (users) that have legitimate rights to indeed GET or SET 3923 (change/create/delete) them. 3925 9. Authors' Addresses 3927 James V. Luciani 3928 TollBridge Technologies 3929 PO BOX 1010 3930 Concord, MA 01742 3931 USA 3932 Phone: (978) 266-2854 3933 Email: jluciani@tollbridgetech.com 3935 Hans Sjostrand 3936 Ericsson Telecom AB 3937 Business Unit Data Backbone and Optical Networks 3938 S-126 25 Stockholm, Sweden 3939 Phone: +46 8 719 9960 3940 Email: hans.sjostrand@ericsson.com 3942 Joan Cucchiara 3943 Brix Networks 3944 300 Concord Ave. 3945 Billerica, MA 01821 3946 USA 3947 Phone: (978) 439-1523 3948 Email: jcucchiara@brixnet.com 3950 10. Full Copyright Statement 3952 Copyright (C) The Internet Society (1999, 2000). All Rights Reserved. 3954 This document and translations of it may be copied and furnished to 3955 others, and derivative works that comment on or otherwise explain it 3956 or assist in its implementation may be prepared, copied, published 3957 and distributed, in whole or in part, without restriction of any 3958 kind, provided that the above copyright notice and this paragraph are 3959 included on all such copies and derivative works. However, this 3960 document itself may not be modified in any way, such as by removing 3961 the copyright notice or references to the Internet Society or other 3962 Internet organizations, except as needed for the purpose of 3963 developing Internet standards in which case the procedures for 3964 copyrights defined in the Internet Standards process must be 3965 followed, or as required to translate it into languages other than 3966 English. 3968 The limited permissions granted above are perpetual and will not be 3969 revoked by the Internet Society or its successors or assigns. 3971 This document and the information contained herein is provided on an 3972 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 3973 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 3974 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 3975 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 3976 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.