idnits 2.17.1 draft-ietf-mpls-ldp-mib-06.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 3562 has weird spacing: '... (Since addin...' == Line 3944 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 (July 2000) is 8686 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 3811, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 3819, but no explicit reference was found in the text == Unused Reference: '21' is defined on line 3826, but no explicit reference was found in the text == Unused Reference: '23' is defined on line 3832, but no explicit reference was found in the text == Unused Reference: '24' is defined on line 3835, but no explicit reference was found in the text == Unused Reference: '26' is defined on line 3843, but no explicit reference was found in the text == Unused Reference: '27' is defined on line 3847, but no explicit reference was found in the text == Unused Reference: '28' is defined on line 3852, but no explicit reference was found in the text == Unused Reference: '30' is defined on line 3858, but no explicit reference was found in the text == Unused Reference: '31' is defined on line 3861, 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 (-11) exists of draft-ietf-mpls-ldp-08 -- Unexpected draft version: The latest known version of draft-ietf-mpls-framework is -05, but you're referring to -06. -- Possible downref: Normative reference to a draft: ref. '19' == Outdated reference: A later version (-07) exists of draft-ietf-mpls-arch-06 == 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-te-mib-03 == Outdated reference: A later version (-14) exists of draft-ietf-mpls-lsr-mib-05 -- Possible downref: Non-RFC (?) normative reference: ref. '27' ** Obsolete normative reference: RFC 2233 (ref. '29') (Obsoleted by RFC 2863) == Outdated reference: A later version (-08) exists of draft-ietf-mpls-label-encaps-07 Summary: 18 errors (**), 0 flaws (~~), 21 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Cucchiara 3 Internet-Draft Brix Networks 4 Expires January 2001 H. Sjostrand 5 Ericsson 6 J. Luciani 7 TollBridge Technologies 8 July 2000 10 Definitions of Managed Objects for 11 the Multiprotocol Label Switching, Label Distribution Protocol (LDP) 13 15 Status of this Memo 17 This document is an Internet-Draft and is in full conformance with 18 all provisions of Section 10 of RFC 2026. Internet-Drafts are 19 working documents of the Internet Engineering Task Force (IETF), its 20 areas, and its working groups. Note that other groups may also 21 distribute working documents as Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress". 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html 34 Distribution of this document is unlimited. Please send comments to 35 the Multiprotocol Label Switching (mpls) Working Group, mpls@uu.net. 37 Copyright Notice 39 Copyright (C) The Internet Society (1999, 2000). All Rights 40 Reserved. 42 Abstract 44 This memo defines a portion of the Management Information Base (MIB) 45 for use with network management protocols in the Internet community. 46 In particular, it describes managed objects for the Multiprotocol 47 Label Switching, Label Distribution Protocol (LDP). 49 Table of Contents 51 1 Introduction ................................................. 3 52 2 The SNMP Management Framework ................................ 3 53 3 Structure of the MIB ......................................... 5 54 3.1 Overview ................................................... 5 55 3.2 Future Considerations ...................................... 5 56 3.3 Interface Indexing ......................................... 5 57 3.4 Differences from the LDP Specification ..................... 6 58 3.5 Discussion of MIB Groups ................................... 6 59 3.6 The MPLS LDP General Group ................................. 6 60 3.6.1 The LDP Entity Table ..................................... 6 61 3.6.2 Changing Values After Session Establishment .............. 7 62 3.6.3 mplsLdpEntityAdminStatus and mplsLdpEntityRowStatus ...... 7 63 3.6.4 The LDP Entity Generic Objects ........................... 7 64 3.6.5 The LDP Entity ATM Objects ............................... 8 65 3.6.6 The LDP Entity Frame Relay Objects ....................... 8 66 3.6.7 The LDP Entity Statistics Table .......................... 8 67 3.6.8 The LDP Entity Peer Table ................................ 8 68 3.6.9 The LDP Hello Adjacencies Table .......................... 9 69 3.6.10 The LDP Session Table ................................... 9 70 3.6.11 The LDP ATM Session Table ............................... 9 71 3.6.12 The LDP Frame Relay Session Table ....................... 9 72 3.6.13 The LDP Session Statistics Table ........................ 9 73 3.6.14 The LDP Session Peer Address Table ...................... 9 74 3.6.15 The Mapping Tables ...................................... 9 75 3.6.15.1 The LDP Session In Label Map Table .................... 10 76 3.6.15.2 The LDP Session Out Label Map Table ................... 10 77 3.6.15.3 The LDP Session XC Map Table .......................... 10 78 3.6.16 The LDP FEC Table ....................................... 11 79 3.7 The LDP Notifications Group ................................ 11 80 3.7.1 LDP Notifications ........................................ 11 81 4 MPLS Label Distribution Protocol MIB Definitions ............. 11 82 5 Revision History ............................................. 71 83 5.1 Changes from .............. 71 84 5.2 Changes from .............. 72 85 5.3 Changes from .............. 75 86 5.4 Changes from .............. 76 87 5.5 Changes from .............. 77 88 5.6 Changes from .............. 78 89 6 Acknowledgments .............................................. 78 90 7 References ................................................... 80 91 8 Security Considerations ...................................... 82 92 9 Authors' Addresses ........................................... 83 93 10 Full Copyright Statement .................................... 83 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 [22]. 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. [32] 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 [29] 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 added 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 in order as there was a request from the working group and is 222 considered to be useful for network management. 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 [32]. 228 3.5. Discussion of MIB Groups 230 Currently, there are six groups: the MPLS LDP General Group, the MPLS 231 LDP ATM Group, the MPLS LDP Frame Relay Group, the MPLS Mapping Group 232 and the MPLS LDP Notifications Group. The MPLS LDP General Group and 233 the MPLS LDP Notifications Group should always be supported. The 234 MPLS LDP ATM Group is specific to ATM and should be supported only if 235 LDP is using ATM. Likewise, the MPLS LDP Frame Relay group is 236 specific to Frame Relay and should be supported only if LDP is using 237 Frame Relay. The MPLS LDP Mapping group should be supported if and 238 only if the LSR MIB is supported. 240 3.6. The MPLS LDP General Group 242 This group contains information about the specific LDP Entities which 243 are associated with this agent. Each LSR must have one LDP Entity. 245 3.6.1. The LDP Entity Table 247 The LDP Entity Table provides a way to configure the LSR for using 248 LDP. There must be at least one LDP Entity for the LSR to support 249 LDP. 251 Each entry/row in this table represents a single LDP Entity. 253 3.6.2. Changing Values After Session Establishment 255 It should be noted that special care should be taken if MIB objects 256 which are used in the MPLS LDP Session Initialization need to be 257 changed AFTER Session Initialization has occurred. For example, 258 currently there is no way to modify a Label Range once a session has 259 been established. Thus, in order to do this, the entire session with 260 the peer needs to be torn down. All related information learned 261 during this session needs to be removed from the MIB. Then and only 262 then is it safe to modify a Label Range. After modification, the LDP 263 Entity will need to go through the Session Initialization again, in 264 order to communicate the new Label Ranges to the Peer and establish 265 new sessions. 267 3.6.3. mplsLdpEntityAdminStatus and mplsLdpEntityRowStatus 269 The mplsLdpEntityAdminStatus object could be viewed as having a 270 subset of the functionality of the mplsLdpEntityRowStatus object. 271 For example, the AdminStatus object has states of enable(1) and 272 disable(2). Setting the mplsLdpEntityAdminStatus object to 273 disable(2) and setting the mplsLdpEntityRowStatus object to 274 notInService(2) are functionally the same. The motivation behind 275 keeping the mplsLdpEntityAdminStatus object is that there could be 276 situations where a user would be given write permission to the 277 mplsLdpEntityAdminStatus object, but would not be given write 278 permission to the mplsLdpEntityRowStatus object. Having write 279 permission to the mplsLdpEntityRowStatus object would mean that a 280 user would be able to destroy a row. This was the motivation for 281 keeping the two objects. 283 3.6.4. The LDP Entity Generic Objects 285 There exists two tables to configure LDP for using Generic Labels. 286 These tables are the mplsLdpEntityConfGenericLabelRangeTable and the 287 mplsLdpEntityConfGenericTable. The 288 mplsLdpEntityConfGenericLabelRangeTable is for configuring label 289 ranges for generic labels. The mplsLdpEntityConfGenericTable is used 290 for configuring generic labels. In order to reserve a range of 291 generic labels, there must be at least one row configured in the 292 mplsLdpEntityConfGenericLabelRangeTable. In order to configure a 293 label there must be at least one row in the 294 mplsLdpEntityConfGenericLabelRangeTable and one row in 295 mplsLdpEntityConfGenericTable. 297 3.6.5. The LDP Entity ATM Objects 299 There exists two tables to configure LDP for using ATM. These tables 300 are the mplsLdpEntityAtmParmsTable and the 301 mplsLdpEntityConfAtmLabelRangeTable. 303 The mplsLdpEntityAtmParmsTable provides a way to configure 304 information which would be contained in the 'Optional Parameter' 305 portion of an LDP PDU Initialization Message. 307 The mplsLdpEntityConfAtmLabelRangeTable provides a way to configure 308 information which would be contained in the 'ATM Label Range 309 Components' portion of an LDP PDU Intialization Message. 311 3.6.6. The LDP Entity Frame Relay Objects 313 There exists two tables to configure LDP for using Frame Relay. 314 These tables are the mplsLdpEntityFrameRelayParmsTable and the 315 mplsLdpEntityConfFrLabelRangeTable. 317 The mplsLdpEntityFrameRelayParmsTable 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 mplsLdpEntityConfFrLabelRangeTable provides a way to configure 322 information which would be contained in the portion of an LDP PDU 323 Intialization Message. 325 3.6.7. The LDP Entity Statistics Table 327 The LDP Entity Statistics Table will maintain counters related to an 328 LDP Entity. This Table should be a read-only table which contains 329 statistical information. 331 Each row in this table will be related to a single LDP Entity. 333 3.6.8. The LDP Entity Peer Table 335 The LDP Entity Peer Table is a read-only table which contains 336 information about LDP Peers known to LDP Entities. A row in this 337 table is related to one or more rows in the Hello Adjacency Table and 338 one or more rows in the Session Table. The information in the 339 Entity-Peer table is relevant to a Peer but is not the same 340 information that is used by the actual session(s) which are related 341 to this Peer. For example, the PathLimit information is gleaned from 342 the session initialization phase but is not part of a session if 343 there is a mismatch. In the event of a mismatch, then the session 344 will use the PathLimit set by the Entity (and not the Peer). 346 A separate table allows for a more comprehensive and coherent MIB 347 model. 349 3.6.9. The LDP Hello Adjacencies Table 351 This is a table of all adjacencies between all LPD Entities and all 352 LDP Peers. A Session may have one or more adjacencies. 354 3.6.10. The LDP Session Table 356 The LDP Session Table is a read-only table. Each entry in this table 357 represents a single session between an LDP Entity and a Peer. 359 3.6.11. The LDP ATM Session Table 361 The MPLS LDP ATM Session Table is a read-only table which contains 362 session information specific to ATM. 364 3.6.12. The LDP Frame Relay Session Table 366 The MPLS LDP Frame Relay Session Table is a read-only table which 367 contains session information specific to Frame Relay. 369 3.6.13. The LDP Session Statistics Table 371 The MPLS LDP Session Stats Table is a read-only table which contains 372 statistical information on sessions. 374 3.6.14. The LDP Session Peer Address Table 376 The MPLS LDP Session Peer Address Table is a table which 'extends' 377 the mplsLdpSessionTable. This table is a read-only table which 378 stores Addresses learned after session initialization via "Address 379 Message" advertisement. 381 3.6.15. The Mapping Tables 383 The LIB table was removed since it overlapped with the mplsXCTable in 384 the LSR MIB[25]. [ASIDE: the mplsXCTable contains all LIB entries, 385 not only those for LDP LSP but those for LSPs created by other mpls 386 protocols or statically configured. The removal of the LIB table has 387 necessitated a way to associate (or map) LDP sessions with certain 388 tables in the LSR MIB. For example, if a session is torn down, then 389 all related session information must be removed from the both LDP MIB 390 and the LSR MIB. The mplsInSegmentTable, the mplsOutSegmentTable and 391 the mplsXCTable in the LSR MIB could contain rows which were created 392 as a result of an LDP Session. Three mapping tables were added to 393 this MIB to map Sessions to the relevant tables in the LSR MIB. 394 These mapping tables are described in the next few subsections. 396 3.6.15.1. The LDP Session In Label Map Table 398 This table provides a way to map a session to the mplsInSegmentTable 399 in the LSR MIB [25]. When a session is torn down, this table 400 provides a way to clean up the necessary entries in the 401 mplsInSegmentTable. If an LSP is terminated on this LSR then there 402 will be an entry in the table which maps the session and the entry in 403 the mplsInSegmentTable. Please note, there may be entries which are 404 also effected by session teardown in the mplsXCTable. (The 405 relationship between the mplsInSegmentTable and the mplsXCTable and 406 cleanup scenarios will need to be handled by more than LDP.) 408 3.6.15.2. The LDP Session Out Label Map Table 410 This table provides a way to map a session to the mplsOutSegmentTable 411 in the LSR MIB [25]. When a session is torn down, this table 412 provides a way to clean up the necessary entries in the 413 mplsOutSegmentTable. If an LSP is created by this LSR then there 414 will be an entry in this table which maps the session and the entry 415 in the mplsOutSegmentTable. Please note, there may be entries which 416 are also effected by session teardown in the mplsXCTable. (The 417 relationship between the mplsOutSegmentTable and the mplsXCTable and 418 cleanup scenarios will need to be handled by more than LDP.) 420 3.6.15.3. The LDP Session XC Map Table 422 This table provides a way to map a session to the mplsXCTable in the 423 LSR MIB [25]. When a session is torn down, this table provides a way 424 to clean up the necessary entries in the mplsXCTable. If an LSP is 425 cross-connected on this LSR, then there will be an entry in this 426 table which maps the session and the entry in the mplsXCTable. Please 427 note, only true cross-connects are represented in the 428 mplsLdpSessionXCMapTable. 430 3.6.16. The LDP FEC Table 432 The FEC Table is a table which contains FEC (Forwarding Equivalence 433 Class) information. Each entry/row represents a single FEC Element. 434 There is also a FEC Mapping table which maps FECs associated with the 435 Cross-connects. 437 3.7. The LDP Notifications Group 439 3.7.1. LDP Notifications 441 Currently, there are several notifications which are specific for 442 LDP. These are described in this section. Also, there are objects 443 which enable/disable the sending of the traps. If the value is 444 enabled then the trap will be sent. Otherwise, if the value is 445 disabled, then the trap will not be sent. 447 The 'mplsLdpEntityFailedInitSessionTrapEnable' object is used to 448 enable or disable the sending of the If enabled, then this trap is 449 sent when the 'mplsLdpEntityFailedInitSessionThreshold' is exceeded. 450 This notification should indicate to the operator that there may be a 451 misconfigured mplsLdpEntityEntry because the session associated with 452 this Entity is not being established, and the Entity keeps trying to 453 establish the session. A side effect of this situation is that a row 454 in the mplsLdpSessionTable may not be reaching the operational state 455 as indicated by the 457 The object, 'mplsLdpEntityPVLimitMismatchTrapEnable' is used to 458 enable or disable the sending of the trap is sent when there is a 459 mismatch in the PathVectorLimits between the Entity and Peer during 460 session initialization between that Entity and that Peer. In this 461 situation a session could still be established between that entity 462 and that peer. The session uses the value which is configured as the 463 Entity's Path Vector Limit. However, a trap should be sent to 464 indicate that a mismatch occurred. For further details, please see 465 Section 3.5.3 of the LDP Specification [18]. 467 The object, 'mplsLdpSessionUpDownTrapEnable' is used to enable or 468 disable the sending of the 'mplsLdpSessionUp' and are sent when there 469 is an appropriate change in the change state (Up to Down for the 470 'mplsLdpSessionDown' trap, or Down to Up for the 'mplsLdpSessionUp' 471 trap). 473 4. MPLS Label Distribution Protocol MIB Definitions 475 MPLS-LDP-MIB DEFINITIONS ::= BEGIN 476 IMPORTS 477 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, 478 experimental, 479 Integer32, Counter32, Unsigned32 480 FROM SNMPv2-SMI 481 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 482 FROM SNMPv2-CONF 484 TEXTUAL-CONVENTION, RowStatus, TimeInterval, TruthValue, 485 TimeStamp, StorageType 486 FROM SNMPv2-TC 487 InterfaceIndex, InterfaceIndexOrZero 488 FROM IF-MIB 489 -- AtmInterfaceType, AtmVcIdentifier, 490 AtmVpIdentifier 491 FROM ATM-TC-MIB 492 AddressFamilyNumbers 493 FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB 494 ; 496 mplsLdpMIB MODULE-IDENTITY 497 LAST-UPDATED "200007131200Z" -- July 13, 2000 498 ORGANIZATION "Multiprotocol Label Switching (mpls) 499 Working Group" 500 CONTACT-INFO 501 "Joan Cucchiara (jcucchiara@brixnet.com) 502 Brix Networks 504 Hans Sjostrand (hans.sjostrand@etx.ericsson.se) 505 Ericsson 507 James V. Luciani (jluciani@tollbridgetech.com) 508 TollBridge Technologies" 509 DESCRIPTION 510 "This MIB contains managed object definitions for the 511 Multiprotocol Label Switching, Label Distribution 512 Protocol, LDP, as defined in draft-ietf-mpls-ldp-07.txt." 513 ::= { experimental XXXX} -- to be assigned 515 --**************************************************************** 516 -- MPLS LDP Textual Conventions 517 --**************************************************************** 518 -- 520 MplsLsrIdentifier ::= TEXTUAL-CONVENTION 521 STATUS current 522 DESCRIPTION 523 "The Label Switch Router (LSR) identifier 524 is the first 4 bytes or the IP Address component 525 of the Label Distribution Protocol (LDP) identifier." 527 SYNTAX OCTET STRING (SIZE (4)) 529 -- 530 -- A similar TC is also used in RFC2677.txt, perhaps 531 -- this should be made general and not MPLS specific. 532 -- 533 MplsLdpGenAddr ::= TEXTUAL-CONVENTION 534 STATUS current 535 DESCRIPTION 536 "The value of an network layer or data link 537 layer address." 538 SYNTAX OCTET STRING (SIZE (0..64)) 540 -- following Textual Convention was 541 -- originally copied from the LSR MIB. 543 -- It is reproduced here and modified slightly. 545 MplsLabel ::= TEXTUAL-CONVENTION 546 STATUS current 547 DESCRIPTION 548 "This value represents an MPLS label. 549 The label contents are specific to 550 the label being represented. 552 The label carried in an MPLS shim header 553 (for LDP, the Generic Label) is a 20-bit number 554 represented by 4 octets. Bits 0-19 contain a 555 label or a reserved label value. Bits 20-31 MUST 556 be zero. 558 The frame relay label can be either 10-bits or 559 23-bits depending on the DLCI field size and the 560 upper 22-bits or upper 9-bits must be zero, respectively. 562 For an ATM label the lower 16-bits represents the VCI, 563 the next 12-bits represents the VPI and the remaining 564 bits MUST be zero." 565 SYNTAX Integer32(0..2147483647) 567 MplsLdpIdentifier ::= TEXTUAL-CONVENTION 568 STATUS current 569 DESCRIPTION 570 "The LDP identifier is a six octet quantity 571 which is used to identify an Label Switch Router 572 (LSR) label space. 574 The first four octets encode an IP address 575 assigned to the LSR, and the last two octets 576 identify a specific label space within the LSR." 577 SYNTAX OCTET STRING (SIZE (6)) 579 MplsLdpLabelTypes ::= TEXTUAL-CONVENTION 580 STATUS current 581 DESCRIPTION 582 "The Layer 2 label types which are defined for 583 MPLS LDP are generic(1), atm(2), or frameRelay(3)." 584 SYNTAX INTEGER { 585 generic(1), 586 atm(2), 587 frameRelay(3) 588 } 590 -- This was taken from rfc2514.txt (AtmVcIdentifier) and 591 -- modified here for MPLS. 592 -- This TC agrees with draft-ietf-mpls-atm-04.txt 593 -- which specifies that VC values need to be greater than 594 -- 31, or in other words, 0-31 are reserved for other 595 -- uses by the ITU and ATM Forum. 596 MplsAtmVcIdentifier ::= TEXTUAL-CONVENTION 597 STATUS current 598 DESCRIPTION 599 "The VCI value for a VCL. The maximum VCI value 600 cannot exceed the value allowable by 601 atmInterfaceMaxVciBits defined in ATM-MIB. 602 The minimum value is 32, values 0 to 31 are 603 reserved for other uses by the ITU and ATM 604 Forum. 32 is typically the default value 605 for the Control VC." 606 SYNTAX INTEGER (32..65535) 608 -- Top-level structure of the MIB (the following is proposed) 609 mpls OBJECT IDENTIFIER ::= { mplsProtocols } 611 mplsProtocols OBJECT IDENTIFIER ::= { mplsLdpObjects } 612 -- under mplsProtocols will be LDP, CR-LDP, 613 -- and other MPLS "Protocols". 615 mplsLdpObjects OBJECT IDENTIFIER ::= { mplsLdpMIB 1 } 616 mplsLdpNotifications OBJECT IDENTIFIER ::= { mplsLdpMIB 2 } 617 mplsLdpConformance OBJECT IDENTIFIER ::= { mplsLdpMIB 3 } 619 --**************************************************************** 620 -- MPLS LDP Objects 621 --**************************************************************** 622 mplsLdpLsrObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 1 } 624 mplsLdpEntityObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 2 } 626 -- 627 -- The MPLS Label Distribution Protocol's 628 -- Label Switch Router Objects 629 -- 631 mplsLdpLsrId OBJECT-TYPE 632 SYNTAX MplsLsrIdentifier 633 MAX-ACCESS read-only 634 STATUS current 635 DESCRIPTION 636 "The LSR's Identifier." 637 ::= { mplsLdpLsrObjects 1 } 639 mplsLdpLsrLoopDetectionCapable OBJECT-TYPE 640 SYNTAX INTEGER { 641 none(1), 642 other(2), 643 hopCount(3), 644 pathVector(4), 645 hopCountAndPathVector(5) 646 } 647 MAX-ACCESS read-only 648 STATUS current 649 DESCRIPTION 650 "A indication of whether this LSR supports 651 loop detection. 653 none(1) -- Loop Detection is not supported 654 on this LSR. 656 other(2) -- Loop Detection is supported but 657 by a method other than those 658 listed below. 660 hopCount(3) -- Loop Detection is supported by 661 Hop Count only. 663 pathVector(4) -- Loop Detection is supported by 664 Path Vector only. 666 hopCountAndPathVector(5) -- Loop Detection is 667 supported by both Hop Count 668 And Path Vector. 670 Since Loop Detection is determined during 671 Session Initialization, an individual session 672 may not be running with loop detection. This 673 object simply gives an indication of whether or not the 674 LSR has the ability to support Loop Detection and 675 which types." 676 ::= { mplsLdpLsrObjects 2 } 678 -- 679 -- The MPLS Label Distribution Protocol Entity Objects 680 -- 682 mplsLdpEntityIndexNext OBJECT-TYPE 683 SYNTAX Unsigned32 (0..4294967295) 684 MAX-ACCESS read-only 685 STATUS current 686 DESCRIPTION 687 "This object contains an appropriate value to 688 be used for mplsLdpEntityIndex when creating 689 entries in the mplsLdpEntityTable. The value 690 0 indicates that no unassigned entries are 691 available. To obtain the mplsLdpEntityIndex 692 value for a new entry, the manager issues a 693 management protocol retrieval operation to obtain 694 the current value of this object. After each 695 retrieval, the agent should modify the value to 696 the next unassigned index." 697 ::= { mplsLdpEntityObjects 1 } 699 mplsLdpEntityTable OBJECT-TYPE 700 SYNTAX SEQUENCE OF MplsLdpEntityEntry 701 MAX-ACCESS not-accessible 702 STATUS current 703 DESCRIPTION 704 "This table contains information about the 705 MPLS Label Distribution Protocol Entities which 706 exist on this Label Switch Router (LSR)." 707 ::= { mplsLdpEntityObjects 2 } 709 mplsLdpEntityEntry OBJECT-TYPE 710 SYNTAX MplsLdpEntityEntry 711 MAX-ACCESS not-accessible 712 STATUS current 713 DESCRIPTION 714 "An entry in this table represents an LDP entity. 715 An entry can be created by a network administrator 716 or by an SNMP agent as instructed by LDP." 717 INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex } 718 ::= { mplsLdpEntityTable 1 } 720 MplsLdpEntityEntry ::= SEQUENCE { 721 mplsLdpEntityLdpId MplsLdpIdentifier, 722 mplsLdpEntityIndex Unsigned32, 723 mplsLdpEntityProtocolVersion Integer32, 724 mplsLdpEntityAdminStatus INTEGER, 725 mplsLdpEntityOperStatus INTEGER, 726 mplsLdpEntityWellKnownTcpDiscoveryPort Unsigned32, 727 mplsLdpEntityWellKnownUdpDiscoveryPort Unsigned32, 728 mplsLdpEntityMaxPduLength Unsigned32, 729 mplsLdpEntityKeepAliveHoldTimer Integer32, 730 mplsLdpEntityHelloHoldTimer Integer32, 731 mplsLdpEntityFailedInitSessionTrapEnable INTEGER, 732 mplsLdpEntityFailedInitSessionThreshold Integer32, 733 mplsLdpEntityLabelDistributionMethod INTEGER, 734 mplsLdpEntityLabelRetentionMode INTEGER, 735 mplsLdpEntityPVLimitMismatchTrapEnable INTEGER, 736 mplsLdpEntityPathVectorLimit Integer32, 737 mplsLdpEntityHopCountLimit Integer32, 738 mplsLdpEntityTargetedPeer TruthValue, 739 mplsLdpEntityTargetedPeerAddrType AddressFamilyNumbers, 740 mplsLdpEntityTargetedPeerAddr MplsLdpGenAddr, 741 mplsLdpEntityOptionalParameters MplsLdpLabelTypes, 742 mplsLdpEntityDiscontinuityTime TimeStamp, 743 mplsLdpEntityStorageType StorageType, 744 mplsLdpEntityRowStatus RowStatus 745 } 747 mplsLdpEntityLdpId OBJECT-TYPE 748 SYNTAX MplsLdpIdentifier 749 MAX-ACCESS not-accessible 750 STATUS current 751 DESCRIPTION 752 "The LDP identifier. 754 The first four octets encode an IP address 755 assigned to the LSR, and the last two octets 756 identify a specific label space within the 757 LSR." 758 REFERENCE 759 "LDP Specification, Section on LDP Identifiers." 760 ::= { mplsLdpEntityEntry 1 } 762 mplsLdpEntityIndex OBJECT-TYPE 763 SYNTAX Unsigned32 (1..4294967295) 764 MAX-ACCESS not-accessible 765 STATUS current 766 DESCRIPTION 767 "This index is used as a secondary index to uniquely 768 identify this row. Before creating a row in this table, 769 the 'mplsLdpEntityIndexNext' object should be retrieved. 770 That value should be used for the value of this index 771 when creating a row in this table. (NOTE: if a value 772 of zero (0) is retrieved, that indicates that no rows 773 can be created in this table at this time. 775 A secondary index (this object) is needed by some 776 but not all, LDP implementations. For example 777 in an LDP implementation which uses PPP, this 778 index may be needed." 779 ::= { mplsLdpEntityEntry 2 } 781 mplsLdpEntityProtocolVersion OBJECT-TYPE 782 SYNTAX Integer32 783 MAX-ACCESS read-create 784 STATUS current 785 DESCRIPTION 786 "The version number of the protocol. The value of 0 on a 787 read indicates that the version of the protocol is unknown. 788 Otherwise, the value of this object represents the version 789 of the LDP protocol." 790 DEFVAL { 1 } 791 ::= { mplsLdpEntityEntry 3 } 793 mplsLdpEntityAdminStatus OBJECT-TYPE 794 SYNTAX INTEGER { 795 enable(1), 796 disable(2) 797 } 798 MAX-ACCESS read-create 799 STATUS current 800 DESCRIPTION 801 "The administrative status of this LDP Entity. 802 If this object is changed from 'enable' to 'disable' 803 and this entity has already attempted to establish 804 contact with a Peer (which implies that the 805 'mplsLdpEntityRowStatus' object has been set to 806 'active'), then all contact with that 807 Peer is lost and all information from that Peer 808 needs to be removed from the MIB. 810 At this point the user is able to change values 811 which are related to this entity. 813 When the admin status is set back to 'up', then 814 this Entity will attempt to establish new sessions 815 with the Peer." 816 DEFVAL { enable } 817 ::= { mplsLdpEntityEntry 4 } 819 mplsLdpEntityOperStatus OBJECT-TYPE 820 SYNTAX INTEGER { 821 unknown(0), 822 enabled(1), 823 disabled(2) 824 } 825 MAX-ACCESS read-only 826 STATUS current 827 DESCRIPTION 828 "The operational status of this LDP Entity." 829 ::= { mplsLdpEntityEntry 5 } 831 mplsLdpEntityWellKnownTcpDiscoveryPort OBJECT-TYPE 832 SYNTAX Unsigned32 833 MAX-ACCESS read-create 834 STATUS current 835 DESCRIPTION 836 "The well known TCP Discovery Port for 837 LDP." 838 DEFVAL { 646 } 839 ::= { mplsLdpEntityEntry 6 } 841 mplsLdpEntityWellKnownUdpDiscoveryPort OBJECT-TYPE 842 SYNTAX Unsigned32 843 MAX-ACCESS read-create 844 STATUS current 845 DESCRIPTION 846 "The well known UDP Discovery Port for 847 LDP." 848 DEFVAL { 646 } 849 ::= { mplsLdpEntityEntry 7 } 851 mplsLdpEntityMaxPduLength OBJECT-TYPE 852 SYNTAX Unsigned32 (0..65535) 853 UNITS "octets" 854 MAX-ACCESS read-create 855 STATUS current 856 DESCRIPTION 857 "The maximum PDU Length that is sent in 858 the Common Session Parameters of an Initialization 859 Message. A value of 255 or less specifies the 860 default maximum length of 4096 octets." 861 REFERENCE 862 "See Section on the 'Initialization Message' in the 863 LDP Specification." 864 DEFVAL { 4096 } 865 ::= { mplsLdpEntityEntry 8 } 867 mplsLdpEntityKeepAliveHoldTimer OBJECT-TYPE 868 SYNTAX Integer32 (1..65535) 869 UNITS "seconds" 870 MAX-ACCESS read-create 871 STATUS current 872 DESCRIPTION 873 "The two octet value which is the proposed keep alive hold 874 timer for this LDP Entity." 875 DEFVAL { 40 } 876 ::= { mplsLdpEntityEntry 9 } 878 mplsLdpEntityHelloHoldTimer OBJECT-TYPE 879 SYNTAX Integer32 (0..65535) 880 UNITS "seconds" 881 MAX-ACCESS read-create 882 STATUS current 883 DESCRIPTION 884 "The two octet value which is the proposed Hello hold 885 timer for this LDP Entity. A value of 0 means use the 886 default, which is 15 seconds for Link Hellos and 45 887 seconds for Targeted Hellos. A value of 65535 means 888 infinite." 889 DEFVAL { 0 } 890 ::= { mplsLdpEntityEntry 10 } 892 mplsLdpEntityFailedInitSessionTrapEnable OBJECT-TYPE 893 SYNTAX INTEGER { 894 enabled(1), 895 disabled(2) 896 } 897 MAX-ACCESS read-create 898 STATUS current 899 DESCRIPTION 900 "Indicates whether the 901 'mplsLdpFailedInitSessionThresholdExceeded' 902 trap should be generated. 904 If the value of this object is 'enabled(1)' 905 then the trap will generated. If the value 906 of this object is 'disabled(2)' then the 907 trap will not be generated. The DEFVAL 908 is set to 'enabled(1)'." 909 DEFVAL { enabled } 910 ::= { mplsLdpEntityEntry 11 } 912 mplsLdpEntityFailedInitSessionThreshold OBJECT-TYPE 913 SYNTAX Integer32 914 MAX-ACCESS read-create 915 STATUS current 916 DESCRIPTION 917 "When attempting to establish a session with a 918 given Peer, the given LDP Entity should 919 send out the SNMP notification, 920 'mplsLdpFailedInitSessionThresholdExceeded', when 921 the number of Session Initialization messages sent 922 exceeds this threshold. 924 A value of 0 (zero) for this object 925 indicates that the threshold is infinity, and 926 the SNMP notification will never be sent 927 when the value of this object is 0 (zero)." 928 DEFVAL { 8 } 929 ::= { mplsLdpEntityEntry 12 } 931 mplsLdpEntityLabelDistributionMethod OBJECT-TYPE 932 SYNTAX INTEGER { 933 downstreamOnDemand(1), 934 downstreamUnsolicited(2) 935 } 936 MAX-ACCESS read-create 937 STATUS current 938 DESCRIPTION 939 "For any given LDP session, the method of 940 label distribution must be specified." 941 ::= { mplsLdpEntityEntry 13 } 943 mplsLdpEntityLabelRetentionMode OBJECT-TYPE 944 SYNTAX INTEGER { 945 conservative(1), 946 liberal(2) 947 } 948 MAX-ACCESS read-create 949 STATUS current 950 DESCRIPTION 951 "The LDP Entity can be configured to use either 952 conservative or liberal label retention mode. 954 If the value of this object is conservative(1) 955 then advertized label mappings are retained 956 only if they will be used to forward packets, 957 i.e. if label came from a valid next hop. 959 If the value of this object is liberal(2) 960 then all advertized label mappings are retained 961 whether they are from a valid next hop or not." 962 ::= { mplsLdpEntityEntry 14 } 964 mplsLdpEntityPVLimitMismatchTrapEnable OBJECT-TYPE 965 SYNTAX INTEGER { 966 enabled(1), 967 disabled(2) 968 } 969 MAX-ACCESS read-create 970 STATUS current 971 DESCRIPTION 972 "Indicates whether the 'mplsLdpPathVectorLimitMismatch' 973 trap should be generated. 975 If the value of this object is 'enabled(1)' 976 then the trap will generated. If the value 977 of this object is 'disabled(2)' then the 978 trap will not be generated. The DEFVAL 979 is set to 'enabled(1)'." 980 DEFVAL { enabled } 981 ::= { mplsLdpEntityEntry 15 } 983 mplsLdpEntityPathVectorLimit OBJECT-TYPE 984 SYNTAX Integer32 (0..255) 985 MAX-ACCESS read-create 986 STATUS current 987 DESCRIPTION 988 "If the value of this object is 0 (zero) then 989 Loop Dection for Path Vectors is disabled. 991 Otherwise, if this object has a value greater than 992 zero, then Loop Dection for Path Vectors is enabled, 993 and the Path Vector Limit is this value. 994 Also, the value of the object, 995 'mplsLdpLsrLoopDetectionCapable', must be set to 996 either 'pathVector(4)' or 'hopCountAndPathVector(5)', 997 if this object has a value greater than 0 (zero)." 998 ::= { mplsLdpEntityEntry 16 } 1000 mplsLdpEntityHopCountLimit OBJECT-TYPE 1001 SYNTAX Integer32 (0..255) 1002 MAX-ACCESS read-create 1003 STATUS current 1004 DESCRIPTION 1005 "If the value of this object is 0 (zero), 1006 then Loop Detection using Hop Counters is 1007 disabled. 1009 If the value of this object is greater than 1010 0 (zero) then Loop Detection using Hop 1011 Counters is enabled, and this object 1012 specifies this Entity's maximum allowable 1013 value for the Hop Count. 1014 Also, the value of the object 1015 mplsLdpLsrLoopDetectionCapable must be set 1016 to either 'hopCount(3)' or 1017 'hopCountAndPathVector(5)' if this object 1018 has a value greater than 0 (zero)." 1019 ::= { mplsLdpEntityEntry 17 } 1021 mplsLdpEntityTargetedPeer OBJECT-TYPE 1022 SYNTAX TruthValue 1023 MAX-ACCESS read-create 1024 STATUS current 1025 DESCRIPTION 1026 "If this LDP entity uses targeted peer then set 1027 this to true." 1028 DEFVAL { false } 1029 ::= { mplsLdpEntityEntry 18 } 1031 mplsLdpEntityTargetedPeerAddrType OBJECT-TYPE 1032 SYNTAX AddressFamilyNumbers 1033 MAX-ACCESS read-create 1034 STATUS current 1035 DESCRIPTION 1036 "The type of the internetwork layer address used for 1037 the Extended Discovery. This object indicates how 1038 the value of mplsLdpEntityTargetedPeerAddr is to 1039 be interpreted." 1040 ::= { mplsLdpEntityEntry 19 } 1042 mplsLdpEntityTargetedPeerAddr OBJECT-TYPE 1043 SYNTAX MplsLdpGenAddr 1044 MAX-ACCESS read-create 1045 STATUS current 1046 DESCRIPTION 1047 "The value of the internetwork layer address used for 1048 the Extended Discovery." 1049 ::= { mplsLdpEntityEntry 20 } 1051 mplsLdpEntityOptionalParameters OBJECT-TYPE 1052 SYNTAX MplsLdpLabelTypes 1053 MAX-ACCESS read-create 1054 STATUS current 1055 DESCRIPTION 1056 "Specifies the optional parameters for the LDP 1057 Initialization Message. If the value is generic(1) 1058 then no optional parameters will be sent in 1059 the LDP Initialization message associated with 1060 this Entity. 1062 If the value is atmParameters(2) then 1063 a row must be created in the mplsLdpEntityAtmParms 1064 Table, which corresponds to this entry. 1066 If the value is frameRelayParameters(3) then 1067 a row must be created in the mplsLdpEntityFrameRelayParms 1068 Table, which corresponds to this entry." 1069 ::= { mplsLdpEntityEntry 21 } 1071 mplsLdpEntityDiscontinuityTime OBJECT-TYPE 1072 SYNTAX TimeStamp 1073 MAX-ACCESS read-only 1074 STATUS current 1075 DESCRIPTION 1076 "The value of sysUpTime on the most recent occasion 1077 at which any one or more of this entity's counters 1078 suffered a discontinuity. The relevant counters are the 1079 specific instances associated with this entity of 1080 any Counter32, or Counter64 object contained 1081 in the 'mplsLdpEntityStatsTable'. If no such 1082 discontinuities have occurred since the last 1083 re-initialization of the local management 1084 subsytem, then this object contains a zero 1085 value." 1086 ::= { mplsLdpEntityEntry 22 } 1088 mplsLdpEntityStorageType OBJECT-TYPE 1089 SYNTAX StorageType 1090 MAX-ACCESS read-create 1091 STATUS current 1092 DESCRIPTION 1093 "The storage type for this entry." 1094 ::= { mplsLdpEntityEntry 23 } 1096 mplsLdpEntityRowStatus OBJECT-TYPE 1097 SYNTAX RowStatus 1098 MAX-ACCESS read-create 1099 STATUS current 1100 DESCRIPTION 1101 "An object that allows entries in this table to 1102 be created and deleted using the 1103 RowStatus convention. 1105 Once the 'mplsLdpEntityAdminStatus' object has 1106 the value of 'up' and this object has the value 1107 of 'active' then the Entity will atttempt to 1108 contact an LDP Peer. If the value of this object 1109 is changed to 'notInService', then the Entity looses 1110 contact with the LDP Peer and all information related 1111 to that Peer must be removed from the MIB. This has 1112 the same effect as changing 'mplsLdpEntityAdminStatus' 1113 from 'enable' to 'disable'. 1115 When this object is set to 'active' and the value of 1116 the 'mplsLdpEntityAdminStatus' is 'enable' then 1117 this Entity will attempt to contact the Peer and 1118 establish new sessions." 1119 ::= { mplsLdpEntityEntry 24 } 1121 -- 1122 -- Ldp Entity Objects for Generic Labels 1123 -- 1125 mplsLdpEntityGenericObjects OBJECT IDENTIFIER ::= 1126 { mplsLdpEntityObjects 3 } 1128 -- 1129 -- The MPLS LDP Entity Configurable Generic Label Range Table 1130 -- 1132 mplsLdpEntityConfGenericLabelRangeTable OBJECT-TYPE 1133 SYNTAX SEQUENCE OF MplsLdpEntityConfGenericLabelRangeEntry 1134 MAX-ACCESS not-accessible 1135 STATUS current 1136 DESCRIPTION 1137 "The MPLS LDP Entity Configurable Generic Label Range Table. 1138 The purpose of this table is to provide a mechanism 1139 for specifying a contiguous range of generic labels, 1140 or a 'label range' for LDP Entities. 1142 LDP Entities which use Generic Labels must have at least one 1143 entry in this table." 1144 ::= { mplsLdpEntityGenericObjects 1 } 1146 mplsLdpEntityConfGenericLabelRangeEntry OBJECT-TYPE 1147 SYNTAX MplsLdpEntityConfGenericLabelRangeEntry 1148 MAX-ACCESS not-accessible 1149 STATUS current 1150 DESCRIPTION 1151 "A row in the LDP Entity Configurable Generic Label 1152 Range Table. One entry in this table contains 1153 information on a single range of labels 1154 represented by the configured Upper and Lower 1155 Bounds pairs. NOTE: there is NO corresponding 1156 LDP message which relates to the information 1157 in this table, however, this table does provide 1158 a way for a user to 'reserve' a generic label 1159 range. 1161 NOTE: The ranges for a specific LDP Entity 1162 are UNIQUE and non-overlapping. 1164 A row will not be created unless a unique and 1165 non-overlapping range is specified. Thus, row 1166 creation implies a one-shot row creation of 1167 LDP EntityID and LowerBound and 1168 UpperBound." 1169 INDEX { mplsLdpEntityLdpId, 1170 mplsLdpEntityIndex, 1171 mplsLdpEntityConfGenericLabelRangeMinimum, 1172 mplsLdpEntityConfGenericLabelRangeMaximum 1173 } 1174 ::= { mplsLdpEntityConfGenericLabelRangeTable 1 } 1176 MplsLdpEntityConfGenericLabelRangeEntry ::= SEQUENCE { 1177 mplsLdpEntityConfGenericLabelRangeMinimum Unsigned32, 1178 mplsLdpEntityConfGenericLabelRangeMaximum Unsigned32, 1179 mplsLdpEntityConfGenericIfIndexOrZero InterfaceIndexOrZero, 1180 mplsLdpEntityConfGenericLabelRangeStorageType StorageType, 1181 mplsLdpEntityConfGenericLabelRangeRowStatus RowStatus 1182 } 1184 mplsLdpEntityConfGenericLabelRangeMinimum OBJECT-TYPE 1185 SYNTAX Unsigned32(0..1048575) 1186 MAX-ACCESS not-accessible 1187 STATUS current 1188 DESCRIPTION 1189 "The minimum label configured for this range." 1190 ::= { mplsLdpEntityConfGenericLabelRangeEntry 1 } 1192 mplsLdpEntityConfGenericLabelRangeMaximum OBJECT-TYPE 1193 SYNTAX Unsigned32(0..1048575) 1194 MAX-ACCESS not-accessible 1195 STATUS current 1196 DESCRIPTION 1197 "The maximum label configured for this range." 1198 ::= { mplsLdpEntityConfGenericLabelRangeEntry 2 } 1200 mplsLdpEntityConfGenericIfIndexOrZero OBJECT-TYPE 1201 SYNTAX InterfaceIndexOrZero 1202 MAX-ACCESS read-create 1203 STATUS current 1204 DESCRIPTION 1205 "This value represents either the InterfaceIndex of 1206 the 'ifLayer' where these Generic Label would be created, or 1207 0 (zero). The value of zero means that the InterfaceIndex 1208 is not known. For example, if the InterfaceIndex is 1209 created subsequent to the Generic Label's creation, then 1210 it would not be known. However, if the InterfaceIndex 1211 is known, then it must be represented by this value. 1213 If an InterfaceIndex becomes known, then the 1214 network management entity (e.g. SNMP agent) responsible 1215 for this object MUST change the value from 0 (zero) to the 1216 value of the InterfaceIndex. If this Generic Label is 1217 being used in forwarding data, then the value of this 1218 object MUST be the InterfaceIndex." 1219 ::= { mplsLdpEntityConfGenericLabelRangeEntry 3 } 1221 mplsLdpEntityConfGenericLabelRangeStorageType OBJECT-TYPE 1222 SYNTAX StorageType 1223 MAX-ACCESS read-create 1224 STATUS current 1225 DESCRIPTION 1226 "The storage type for this entry." 1227 ::= { mplsLdpEntityConfGenericLabelRangeEntry 4 } 1229 mplsLdpEntityConfGenericLabelRangeRowStatus OBJECT-TYPE 1230 SYNTAX RowStatus 1231 MAX-ACCESS read-create 1232 STATUS current 1233 DESCRIPTION 1234 "An object that allows entries in this 1235 table to be created and deleted using 1236 the RowStatus convention. 1238 There must exist at least one entry in this 1239 table for every LDP Entity that has a 1240 generic label configured. 1242 NOTE: This RowStatus object should 1243 have the same value of the 'mplsLdpEntityRowStatus' 1244 related to this entry." 1245 ::= { mplsLdpEntityConfGenericLabelRangeEntry 5 } 1247 -- 1248 -- MPLS Generic Table for configuring Generic Labels 1249 -- 1251 mplsLdpEntityConfGenericTable OBJECT-TYPE 1252 SYNTAX SEQUENCE OF MplsLdpEntityConfGenericEntry 1253 MAX-ACCESS not-accessible 1254 STATUS current 1255 DESCRIPTION 1256 "This table provides a way to configure Generic Labels 1257 associated with LDP entities on the LSR." 1258 ::= { mplsLdpEntityGenericObjects 2 } 1260 mplsLdpEntityConfGenericEntry OBJECT-TYPE 1261 SYNTAX MplsLdpEntityConfGenericEntry 1262 MAX-ACCESS not-accessible 1263 STATUS current 1264 DESCRIPTION 1265 "An entry in this table provides a way to configure 1266 a 'Generic Label' for LDP. 1268 An entry in the 'mplsLdpEntityTable' will only have 1269 associated entries in this Table if Generic Labels 1270 are configured for a specific 'mplsLdpEntityEntry'. 1271 Thus, not every 'mplsLdpEntityEntry' will have 1272 associated entries in this table. 1274 The InterfaceIndex value for a Generic Label is 1275 from the 'ifLayer' where the label is created. Likewise, 1276 the ifType of the interface is the 'ifLayer' where the 1277 label is created. For example, if an implementation 1278 creates the generic label at the ifLayer which 1279 has the 'ifType' of 'mpls', then the 1280 'mplsLdpConfGenericIfIndexOrZero' object 1281 should be set to the value of the InterfaceIndex 1282 for this 'ifLayer'. 1284 If the value of 'mplsLdpConfGenericIfIndexOrZero' is zero 1285 then the InterfaceIndex value of this object is not known. 1286 If this Generic Label is used, i.e. a session has been 1287 established successfully and data is forwarded using this 1288 label, then the value of the 1289 'mplsLdpConfGenericIfIndexOrZero' object MUST be 1290 updated by the network management entity 1291 (e.g. SNMP agent) to reflect the InterfaceIndex 1292 value for the 'ifLayer' that created the Generic Label. 1294 To summarize, not all implementations may assign ifIndices 1295 at a label's creation time, thus, an ifIndex value 1296 may not be known, until a subsequent time. However, 1297 once that ifIndex value is known, the 1298 'mplsLdpConfGenericIfIndexOrZero' object 1299 should be changed to reflect the ifIndex value." 1300 INDEX { mplsLdpEntityLdpId, 1301 mplsLdpEntityIndex, 1302 mplsLdpEntityConfGenericLabelRangeMinimum, 1303 mplsLdpEntityConfGenericLabelRangeMaximum, 1304 mplsLdpConfGenericLabel 1305 } 1306 ::= { mplsLdpEntityConfGenericTable 1 } 1308 MplsLdpEntityConfGenericEntry ::= SEQUENCE { 1309 mplsLdpConfGenericLabel Unsigned32, 1310 mplsLdpConfGenericStorageType StorageType, 1311 mplsLdpConfGenericRowStatus RowStatus 1312 } 1314 mplsLdpConfGenericLabel OBJECT-TYPE 1315 SYNTAX Unsigned32(0..1048575) 1316 MAX-ACCESS not-accessible 1317 STATUS current 1318 DESCRIPTION 1319 "The value of this object represents the Generic Label 1320 used in the Generic Label TLV." 1321 REFERENCE 1322 "Generic Label TLV Section of the LDP Specification." 1323 ::= { mplsLdpEntityConfGenericEntry 1 } 1325 mplsLdpConfGenericStorageType OBJECT-TYPE 1326 SYNTAX StorageType 1327 MAX-ACCESS read-create 1328 STATUS current 1329 DESCRIPTION 1330 "The storage type for this entry." 1331 ::= { mplsLdpEntityConfGenericEntry 2 } 1333 mplsLdpConfGenericRowStatus OBJECT-TYPE 1334 SYNTAX RowStatus 1335 MAX-ACCESS read-create 1336 STATUS current 1337 DESCRIPTION 1338 "An object that allows entries in this table to 1339 be created and deleted using the 1340 RowStatus convention. 1342 NOTE: This RowStatus object should 1343 have the same value of the 'mplsLdpEntityRowStatus' 1344 related to this entry." 1345 ::= { mplsLdpEntityConfGenericEntry 3 } 1347 -- 1348 -- Ldp Entity Objects for ATM 1349 -- 1351 mplsLdpEntityAtmObjects OBJECT IDENTIFIER ::= 1352 { mplsLdpEntityObjects 4 } 1354 mplsLdpEntityAtmParmsTable OBJECT-TYPE 1355 SYNTAX SEQUENCE OF MplsLdpEntityAtmParmsEntry 1356 MAX-ACCESS not-accessible 1357 STATUS current 1358 DESCRIPTION 1359 "This table contains information about the 1360 ATM specific information which could be used 1361 in the 'Optional Parameters' and other ATM specific 1362 information." 1363 ::= { mplsLdpEntityAtmObjects 1 } 1365 mplsLdpEntityAtmParmsEntry OBJECT-TYPE 1366 SYNTAX MplsLdpEntityAtmParmsEntry 1367 MAX-ACCESS not-accessible 1368 STATUS current 1369 DESCRIPTION 1370 "An entry in this table represents the ATM parameters 1371 and ATM information for this LDP entity." 1372 INDEX { mplsLdpEntityLdpId, 1373 mplsLdpEntityIndex 1374 } 1375 ::= { mplsLdpEntityAtmParmsTable 1 } 1377 MplsLdpEntityAtmParmsEntry ::= SEQUENCE { 1378 mplsLdpEntityAtmIfIndexOrZero InterfaceIndexOrZero, 1379 mplsLdpEntityAtmMergeCap INTEGER, 1380 mplsLdpEntityAtmLabelRangeComponents Unsigned32, 1381 mplsLdpEntityAtmVcDirectionality INTEGER, 1382 mplsLdpEntityAtmLsrConnectivity INTEGER, 1383 mplsLdpEntityDefaultControlVpi AtmVpIdentifier, 1384 mplsLdpEntityDefaultControlVci MplsAtmVcIdentifier, 1385 mplsLdpEntityUnlabTrafVpi AtmVpIdentifier, 1386 mplsLdpEntityUnlabTrafVci MplsAtmVcIdentifier, 1387 mplsLdpEntityAtmStorageType StorageType, 1388 mplsLdpEntityAtmRowStatus RowStatus 1389 } 1391 mplsLdpEntityAtmIfIndexOrZero OBJECT-TYPE 1392 SYNTAX InterfaceIndexOrZero 1393 MAX-ACCESS read-create 1394 STATUS current 1395 DESCRIPTION 1396 "This value represents either the InterfaceIndex of 1397 the 'ifLayer' where the ATM Labels 'owned' by this 1398 entry were created, or 0 (zero). The value of zero 1399 means that the InterfaceIndex is not known. For example, 1400 if the InterfaceIndex is created subsequent to the 1401 ATM Label's creation, then it would not be known. 1402 However, if the InterfaceIndex is known, then it must 1403 be represented by this value. 1405 If an InterfaceIndex becomes known, then the 1406 network management entity (e.g. SNMP agent) responsible 1407 for this object MUST change the value from 0 (zero) to the 1408 value of the InterfaceIndex. If an ATM Label is 1409 being used in forwarding data, then the value of this 1410 object MUST be the InterfaceIndex." 1411 ::= { mplsLdpEntityAtmParmsEntry 1 } 1413 mplsLdpEntityAtmMergeCap OBJECT-TYPE 1414 SYNTAX INTEGER { 1415 notSupported(0), 1416 vcMerge(2) 1417 } 1418 MAX-ACCESS read-create 1419 STATUS current 1420 DESCRIPTION 1421 "Denotes the Merge Capability of this Entity." 1422 ::= { mplsLdpEntityAtmParmsEntry 2 } 1424 mplsLdpEntityAtmLabelRangeComponents OBJECT-TYPE 1425 SYNTAX Unsigned32 (1..65535) 1426 MAX-ACCESS read-create 1427 STATUS current 1428 DESCRIPTION 1429 "Number of LabelRange Components in the Initialization 1430 message. This also represents the number of entries 1431 in the mplsLdpLabelRangeComponentsTable which correspond 1432 to this entry." 1433 ::= { mplsLdpEntityAtmParmsEntry 3 } 1435 mplsLdpEntityAtmVcDirectionality OBJECT-TYPE 1436 SYNTAX INTEGER { 1437 bidirectional(0), 1438 unidirectional(1) 1439 } 1440 MAX-ACCESS read-create 1441 STATUS current 1442 DESCRIPTION 1443 "If the value of this object is 'bidirectional(0)', 1444 a given VCI, within a given VPI, is used as a 1445 label for both directions independently. 1447 If the value of this object is 'unidirectional(1)', 1448 a given VCI within a VPI designates one direction." 1449 ::= { mplsLdpEntityAtmParmsEntry 4 } 1451 mplsLdpEntityAtmLsrConnectivity OBJECT-TYPE 1452 SYNTAX INTEGER { 1453 direct(1), 1454 indirect(2) 1456 } 1457 MAX-ACCESS read-create 1458 STATUS current 1459 DESCRIPTION 1460 "The peer LSR may be connected indirectly by means of an 1461 ATM VP so that the VPI values may be different on either 1462 endpoint so the label MUST be encoded entirely within the 1463 VCI field." 1464 REFERENCE 1465 "draft-ietf-mpls-atm-04.txt" 1466 DEFVAL { direct } 1467 ::= { mplsLdpEntityAtmParmsEntry 5 } 1469 mplsLdpEntityDefaultControlVpi OBJECT-TYPE 1470 SYNTAX AtmVpIdentifier 1471 MAX-ACCESS read-create 1472 STATUS current 1473 DESCRIPTION 1474 "The default VPI value for the non-MPLS connection. The 1475 default value of this is 0 (zero) but other values may 1476 be configured. This object allows a different value 1477 to be configured." 1478 REFERENCE 1479 "draft-ietf-mpls-atm-04.txt" 1480 DEFVAL 1481 { 0 } 1482 ::= { mplsLdpEntityAtmParmsEntry 6 } 1484 mplsLdpEntityDefaultControlVci OBJECT-TYPE 1485 SYNTAX MplsAtmVcIdentifier 1486 MAX-ACCESS read-create 1487 STATUS current 1488 DESCRIPTION 1489 "The Default VCI value for a non-MPLS connection. The 1490 default value of this is 32 but other values may be 1491 configured. This object allows a different value to 1492 be configured." 1493 REFERENCE 1494 "draft-ietf-mpls-atm-04.txt" 1495 DEFVAL 1496 { 32 } 1497 ::= { mplsLdpEntityAtmParmsEntry 7 } 1499 mplsLdpEntityUnlabTrafVpi OBJECT-TYPE 1500 SYNTAX AtmVpIdentifier 1501 MAX-ACCESS read-create 1502 STATUS current 1503 DESCRIPTION 1504 "VPI value of the VCC supporting unlabelled traffic. This 1505 non-MPLS connection is used to carry unlabelled (IP) 1506 packets." 1507 DEFVAL { 0 } 1508 ::= { mplsLdpEntityAtmParmsEntry 8 } 1510 mplsLdpEntityUnlabTrafVci OBJECT-TYPE 1511 SYNTAX MplsAtmVcIdentifier 1512 MAX-ACCESS read-create 1513 STATUS current 1514 DESCRIPTION 1515 "VCI value of the VCC supporting unlabelled traffic. 1516 This non-MPLS connection is used to carry unlabelled (IP) 1517 packets." 1518 DEFVAL { 32 } 1519 ::= { mplsLdpEntityAtmParmsEntry 9 } 1521 mplsLdpEntityAtmStorageType OBJECT-TYPE 1522 SYNTAX StorageType 1523 MAX-ACCESS read-create 1524 STATUS current 1525 DESCRIPTION 1526 "The storage type for this entry." 1527 ::= { mplsLdpEntityAtmParmsEntry 10 } 1529 mplsLdpEntityAtmRowStatus OBJECT-TYPE 1530 SYNTAX RowStatus 1531 MAX-ACCESS read-create 1532 STATUS current 1533 DESCRIPTION 1534 "An object that allows entries in this table to 1535 be created and deleted using the 1536 RowStatus convention. 1538 NOTE: This RowStatus object should 1539 have the same value of the 'mplsLdpEntityRowStatus' 1540 related to this entry." 1541 ::= { mplsLdpEntityAtmParmsEntry 11 } 1543 -- 1544 -- The MPLS LDP Entity Configurable ATM Label Range Table 1545 -- 1547 mplsLdpEntityConfAtmLabelRangeTable OBJECT-TYPE 1548 SYNTAX SEQUENCE OF MplsLdpEntityConfAtmLabelRangeEntry 1549 MAX-ACCESS not-accessible 1550 STATUS current 1551 DESCRIPTION 1552 "The MPLS LDP Entity Configurable ATM Label Range Table. 1553 The purpose of this table is to provide a mechanism 1554 for specifying a contiguous range of vpi's 1555 with a contiguous range of vci's, or a 'label range' 1556 for LDP Entities. 1558 LDP Entities which use ATM must have at least one 1559 entry in this table." 1560 ::= { mplsLdpEntityAtmObjects 2 } 1562 mplsLdpEntityConfAtmLabelRangeEntry OBJECT-TYPE 1563 SYNTAX MplsLdpEntityConfAtmLabelRangeEntry 1564 MAX-ACCESS not-accessible 1565 STATUS current 1566 DESCRIPTION 1567 "A row in the LDP Entity Configurable ATM Label 1568 Range Table. One entry in this table contains 1569 information on a single range of labels 1570 represented by the configured Upper and Lower 1571 Bounds VPI/VCI pairs. These are the same 1572 data used in the Initialization Message. 1574 NOTE: The ranges for a specific LDP Entity 1575 are UNIQUE and non-overlapping. For example, 1576 for a specific LDP Entity index, there could 1577 be one entry having ConfLowerBound vpi/vci == 0/32, and 1578 ConfUpperBound vpi/vci == 0/100, and a second entry 1579 for this same interface with ConfLowerBound 1580 vpi/vci == 0/101 and ConfUpperBound vpi/vci == 0/200. 1581 However, there could not be a third entry with 1582 ConfLowerBound vpi/vci == 0/200 and 1583 ConfUpperBound vpi/vci == 0/300 because this label 1584 range overlaps with the second entry (i.e. both 1585 entries now have 0/200). 1587 A row will not be created unless a unique and 1588 non-overlapping range is specified. Thus, row 1589 creation implies a one-shot row creation of 1590 LDP EntityID and ConfLowerBound vpi/vci and 1591 ConfUpperBound vpi/vci. At least one label 1592 range entry for a specific LDP Entity MUST 1593 include the default VPI/VCI values denoted 1594 in the LDP Entity Table." 1595 INDEX { mplsLdpEntityLdpId, 1596 mplsLdpEntityIndex, 1597 mplsLdpEntityConfAtmLabelRangeMinimumVpi, 1598 mplsLdpEntityConfAtmLabelRangeMinimumVci 1599 } 1600 ::= { mplsLdpEntityConfAtmLabelRangeTable 1 } 1602 MplsLdpEntityConfAtmLabelRangeEntry ::= SEQUENCE { 1603 mplsLdpEntityConfAtmLabelRangeMinimumVpi AtmVpIdentifier, 1604 mplsLdpEntityConfAtmLabelRangeMinimumVci MplsAtmVcIdentifier, 1605 mplsLdpEntityConfAtmLabelRangeMaximumVpi AtmVpIdentifier, 1606 mplsLdpEntityConfAtmLabelRangeMaximumVci MplsAtmVcIdentifier, 1607 mplsLdpEntityConfAtmLabelRangeStorageType StorageType, 1608 mplsLdpEntityConfAtmLabelRangeRowStatus RowStatus 1609 } 1611 mplsLdpEntityConfAtmLabelRangeMinimumVpi OBJECT-TYPE 1612 SYNTAX AtmVpIdentifier 1613 MAX-ACCESS not-accessible 1614 STATUS current 1615 DESCRIPTION 1616 "The minimum VPI number configured for this range." 1617 ::= { mplsLdpEntityConfAtmLabelRangeEntry 1 } 1619 mplsLdpEntityConfAtmLabelRangeMinimumVci OBJECT-TYPE 1620 SYNTAX MplsAtmVcIdentifier 1621 MAX-ACCESS not-accessible 1622 STATUS current 1623 DESCRIPTION 1624 "The minimum VCI number configured for this range." 1625 ::= { mplsLdpEntityConfAtmLabelRangeEntry 2 } 1627 mplsLdpEntityConfAtmLabelRangeMaximumVpi OBJECT-TYPE 1628 SYNTAX AtmVpIdentifier 1629 MAX-ACCESS read-create 1630 STATUS current 1631 DESCRIPTION 1632 "The maximum VPI number configured for this range." 1633 ::= { mplsLdpEntityConfAtmLabelRangeEntry 3 } 1635 mplsLdpEntityConfAtmLabelRangeMaximumVci OBJECT-TYPE 1636 SYNTAX MplsAtmVcIdentifier 1637 MAX-ACCESS read-create 1638 STATUS current 1639 DESCRIPTION 1640 "The maximum VCI number configured for this range." 1641 ::= { mplsLdpEntityConfAtmLabelRangeEntry 4 } 1643 mplsLdpEntityConfAtmLabelRangeStorageType OBJECT-TYPE 1644 SYNTAX StorageType 1645 MAX-ACCESS read-create 1646 STATUS current 1647 DESCRIPTION 1648 "The storage type for this entry." 1649 ::= { mplsLdpEntityConfAtmLabelRangeEntry 5 } 1651 mplsLdpEntityConfAtmLabelRangeRowStatus OBJECT-TYPE 1652 SYNTAX RowStatus 1653 MAX-ACCESS read-create 1654 STATUS current 1655 DESCRIPTION 1656 "An object that allows entries in this 1657 table to be created and deleted using 1658 the RowStatus convention. 1660 There must exist at least one entry in this 1661 table for every LDP Entity that has 1662 'mplsLdpEntityOptionalParameters' object with 1663 a value of 'atmSessionParameters'. 1665 NOTE: This RowStatus object should 1666 have the same value of the 'mplsLdpEntityRowStatus' 1667 related to this entry." 1668 ::= { mplsLdpEntityConfAtmLabelRangeEntry 6 } 1670 -- 1671 -- Ldp Entity Objects for Frame Relay 1672 -- 1674 mplsLdpEntityFrameRelayObjects OBJECT IDENTIFIER ::= 1675 { mplsLdpEntityObjects 5 } 1677 mplsLdpEntityFrameRelayParmsTable OBJECT-TYPE 1678 SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayParmsEntry 1679 MAX-ACCESS not-accessible 1680 STATUS current 1681 DESCRIPTION 1682 "This table contains information about the 1683 Optional Parameters to specify what this Entity is 1684 going to specify for Frame Relay specific 1685 LDP Intialization Messages." 1686 ::= { mplsLdpEntityFrameRelayObjects 1 } 1688 mplsLdpEntityFrameRelayParmsEntry OBJECT-TYPE 1689 SYNTAX MplsLdpEntityFrameRelayParmsEntry 1690 MAX-ACCESS not-accessible 1691 STATUS current 1692 DESCRIPTION 1693 "An entry in this table represents the Frame Relay 1694 optional parameters associated with the LDP entity." 1695 INDEX { mplsLdpEntityLdpId, 1696 mplsLdpEntityIndex 1697 } 1698 ::= { mplsLdpEntityFrameRelayParmsTable 1 } 1700 MplsLdpEntityFrameRelayParmsEntry ::= SEQUENCE { 1701 mplsLdpEntityFrIfIndexOrZero InterfaceIndexOrZero, 1702 mplsLdpEntityFrMergeCap INTEGER, 1703 mplsLdpEntityFrLabelRangeComponents Unsigned32, 1704 mplsLdpEntityFrLen INTEGER, 1705 mplsLdpEntityFrVcDirectionality INTEGER, 1706 mplsLdpEntityFrParmsStorageType StorageType, 1707 mplsLdpEntityFrParmsRowStatus RowStatus 1708 } 1710 mplsLdpEntityFrIfIndexOrZero OBJECT-TYPE 1711 SYNTAX InterfaceIndexOrZero 1712 MAX-ACCESS read-create 1713 STATUS current 1714 DESCRIPTION 1715 "This value represents either the InterfaceIndex of 1716 the 'ifLayer' where the Frame Relay Labels 'owned' by this 1717 entry were created, or 0 (zero). The value of zero 1718 means that the InterfaceIndex is not known. For example, 1719 if the InterfaceIndex is created subsequent to the 1720 Frame Relay Label's creation, then it would not be known. 1721 However, if the InterfaceIndex is known, then it must 1722 be represented by this value. 1724 If an InterfaceIndex becomes known, then the 1725 network management entity (e.g. SNMP agent) responsible 1726 for this object MUST change the value from 0 (zero) to the 1727 value of the InterfaceIndex. If an Frame Relay Label is 1728 being used in forwarding data, then the value of this 1729 object MUST be the InterfaceIndex." 1730 ::= { mplsLdpEntityFrameRelayParmsEntry 1 } 1732 mplsLdpEntityFrMergeCap OBJECT-TYPE 1733 SYNTAX INTEGER { 1734 notSupported(0), 1735 supported(1) 1736 } 1737 MAX-ACCESS read-create 1738 STATUS current 1739 DESCRIPTION 1740 "This represents whether or not Frame Relay merge 1741 capability is supported." 1742 ::= { mplsLdpEntityFrameRelayParmsEntry 2 } 1744 mplsLdpEntityFrLabelRangeComponents OBJECT-TYPE 1745 SYNTAX Unsigned32 (1..65535) 1746 MAX-ACCESS read-create 1747 STATUS current 1748 DESCRIPTION 1749 "Number of LabelRange Components in the Initialization 1750 message. This also represents the number of entries 1751 in the mplsLdpEntityConfFrLabelRangeTable which correspond 1752 to this entry." 1753 ::= { mplsLdpEntityFrameRelayParmsEntry 3 } 1755 mplsLdpEntityFrLen OBJECT-TYPE 1756 SYNTAX INTEGER { 1757 tenDlciBits(0), 1758 twentyThreeDlciBits(2) 1759 } 1760 MAX-ACCESS read-create 1761 STATUS current 1762 DESCRIPTION 1763 "This object specifies the DLCI bits." 1764 ::= { mplsLdpEntityFrameRelayParmsEntry 4 } 1766 mplsLdpEntityFrVcDirectionality OBJECT-TYPE 1767 SYNTAX INTEGER { 1768 bidirectional(0), 1769 unidirection(1) 1770 } 1771 MAX-ACCESS read-create 1772 STATUS current 1773 DESCRIPTION 1774 "If the value of this object is 'bidirectional(0)', then 1775 the LSR supports the use of a given DLCI as a label for 1776 both directions independently. If the value of 1777 this object is 'unidirectional(1)', then the LSR 1778 uses the given DLCI as a label in only one direction." 1779 ::= { mplsLdpEntityFrameRelayParmsEntry 5 } 1781 mplsLdpEntityFrParmsStorageType OBJECT-TYPE 1782 SYNTAX StorageType 1783 MAX-ACCESS read-create 1784 STATUS current 1785 DESCRIPTION 1786 "The storage type for this entry." 1787 ::= { mplsLdpEntityFrameRelayParmsEntry 6 } 1789 mplsLdpEntityFrParmsRowStatus OBJECT-TYPE 1790 SYNTAX RowStatus 1791 MAX-ACCESS read-create 1792 STATUS current 1793 DESCRIPTION 1794 "An object that allows entries in this table to 1795 be created and deleted using the 1796 RowStatus convention. 1798 NOTE: This RowStatus object should 1799 have the same value of the 'mplsLdpEntityRowStatus' 1800 related to this entry." 1801 ::= { mplsLdpEntityFrameRelayParmsEntry 7 } 1803 -- 1804 -- Frame Relay Label Range Components 1805 -- 1807 mplsLdpEntityConfFrLabelRangeTable OBJECT-TYPE 1808 SYNTAX SEQUENCE OF MplsLdpEntityConfFrLabelRangeEntry 1809 MAX-ACCESS not-accessible 1810 STATUS current 1811 DESCRIPTION 1812 "This table contains information about the 1813 Optional Parameters to specify what this Entity is 1814 going to specify for Frame Relay specific 1815 LDP Intialization Messages." 1816 ::= { mplsLdpEntityFrameRelayObjects 2 } 1818 mplsLdpEntityConfFrLabelRangeEntry OBJECT-TYPE 1819 SYNTAX MplsLdpEntityConfFrLabelRangeEntry 1820 MAX-ACCESS not-accessible 1821 STATUS current 1822 DESCRIPTION 1823 "An entry in this table represents the Frame Relay 1824 optional parameters associated with the LDP entity." 1825 INDEX { mplsLdpEntityLdpId, 1826 mplsLdpEntityIndex, 1827 mplsLdpConfFrMinimumDlci 1828 } 1829 ::= { mplsLdpEntityConfFrLabelRangeTable 1 } 1831 MplsLdpEntityConfFrLabelRangeEntry ::= SEQUENCE { 1832 mplsLdpConfFrMinimumDlci Integer32, 1833 mplsLdpConfFrMaximumDlci Integer32, 1834 mplsLdpConfFrStorageType StorageType, 1835 mplsLdpConfFrRowStatus RowStatus 1836 } 1838 mplsLdpConfFrMinimumDlci OBJECT-TYPE 1839 SYNTAX Integer32(0..4194303) 1840 MAX-ACCESS not-accessible 1841 STATUS current 1842 DESCRIPTION 1843 "The lower bound which is supported. This value should 1844 be the same as that in the Frame Relay Label Range 1845 Component's Minimum DLCI field." 1846 ::= { mplsLdpEntityConfFrLabelRangeEntry 1 } 1848 mplsLdpConfFrMaximumDlci OBJECT-TYPE 1849 SYNTAX Integer32 (0..4194303) 1850 MAX-ACCESS read-create 1851 STATUS current 1852 DESCRIPTION 1853 "The upper bound which is supported. This value should 1854 be the same as that in the Frame Relay Label Range 1855 Component's Maximum DLCI field." 1856 ::= { mplsLdpEntityConfFrLabelRangeEntry 2 } 1858 mplsLdpConfFrStorageType OBJECT-TYPE 1859 SYNTAX StorageType 1860 MAX-ACCESS read-create 1861 STATUS current 1862 DESCRIPTION 1863 "The storage type for this entry." 1864 ::= { mplsLdpEntityConfFrLabelRangeEntry 3 } 1866 mplsLdpConfFrRowStatus OBJECT-TYPE 1867 SYNTAX RowStatus 1868 MAX-ACCESS read-create 1869 STATUS current 1870 DESCRIPTION 1871 "An object that allows entries in this table to 1872 be created and deleted using the 1873 RowStatus convention. 1875 If the value of the object 1876 'mplsLdpEntityOptionalParameters' contains the 1877 value of 'frameRelaySessionParameters(3)' then 1878 there must be at least one corresponding entry 1879 in this table. 1881 NOTE: This RowStatus object should 1882 have the same value of the 'mplsLdpEntityRowStatus' 1883 related to this entry." 1884 ::= { mplsLdpEntityConfFrLabelRangeEntry 4 } 1886 -- 1887 -- The MPLS LDP Entity Statistics Table 1888 -- 1890 mplsLdpEntityStatsTable OBJECT-TYPE 1891 SYNTAX SEQUENCE OF MplsLdpEntityStatsEntry 1892 MAX-ACCESS not-accessible 1893 STATUS current 1894 DESCRIPTION 1895 "This table is a read-only table which augments 1896 the mplsLdpEntityTable. The purpose of this 1897 table is to keep statistical information about 1898 the LDP Entities on the LSR." 1899 ::= { mplsLdpEntityObjects 6 } 1901 mplsLdpEntityStatsEntry OBJECT-TYPE 1902 SYNTAX MplsLdpEntityStatsEntry 1903 MAX-ACCESS not-accessible 1904 STATUS current 1905 DESCRIPTION 1906 "A row in this table contains statistical information 1907 about an LDP Entity. Some counters contained in a 1908 row are for fatal errors received during a former 1909 LDP Session associated with this entry. For example, 1910 an Ldp Pdu received on a TCP connection for an 1911 LDP Session which contains a fatal error is counted 1912 here, because the session is terminated. 1913 If the error is NOT fatal (i.e. and the Session 1914 remains), then the error is counted in the 1915 mplsLdpSessionStatsEntry." 1916 AUGMENTS { mplsLdpEntityEntry } 1917 ::= { mplsLdpEntityStatsTable 1 } 1919 MplsLdpEntityStatsEntry ::= SEQUENCE { 1920 mplsLdpAttemptedSessions Counter32, 1921 mplsLdpSessionRejectedNoHelloErrors Counter32, 1922 mplsLdpSessionRejectedAdvertisementErrors Counter32, 1923 mplsLdpSessionRejectedMaxPduErrors Counter32, 1924 mplsLdpSessionRejectedLabelRangeErrors Counter32, 1925 mplsLdpBadLdpIdentifierErrors Counter32, 1926 mplsLdpBadPduLengthErrors Counter32, 1927 mplsLdpBadMessageLengthErrors Counter32, 1928 mplsLdpBadTlvLengthErrors Counter32, 1929 mplsLdpMalformedTlvValueErrors Counter32, 1930 mplsLdpKeepAliveTimerExpiredErrors Counter32, 1931 mplsLdpShutdownNotifReceived Counter32, 1932 mplsLdpShutdownNotifSent Counter32 1933 } 1935 mplsLdpAttemptedSessions OBJECT-TYPE 1936 SYNTAX Counter32 1937 MAX-ACCESS read-only 1938 STATUS current 1939 DESCRIPTION 1940 "A count of the total attempted sessions for 1941 this LDP Entity." 1942 ::= { mplsLdpEntityStatsEntry 1 } 1944 mplsLdpSessionRejectedNoHelloErrors OBJECT-TYPE 1945 SYNTAX Counter32 1946 MAX-ACCESS read-only 1947 STATUS current 1948 DESCRIPTION 1949 "A count of the Session Rejected/No Hello Error 1950 Notification Messages sent or received by 1951 this LDP Entity." 1952 ::= { mplsLdpEntityStatsEntry 2 } 1954 mplsLdpSessionRejectedAdvertisementErrors OBJECT-TYPE 1955 SYNTAX Counter32 1956 MAX-ACCESS read-only 1957 STATUS current 1958 DESCRIPTION 1959 "A count of the Session Rejected/Parameters 1960 Advertisement Mode Error Notification Messages sent 1961 or received by this LDP Entity." 1962 ::= { mplsLdpEntityStatsEntry 3 } 1964 mplsLdpSessionRejectedMaxPduErrors OBJECT-TYPE 1965 SYNTAX Counter32 1966 MAX-ACCESS read-only 1967 STATUS current 1968 DESCRIPTION 1969 "A count of the Session Rejected/Parameters 1970 Max Pdu Length Error Notification Messages sent 1971 or received by this LDP Entity." 1972 ::= { mplsLdpEntityStatsEntry 4 } 1974 mplsLdpSessionRejectedLabelRangeErrors OBJECT-TYPE 1975 SYNTAX Counter32 1976 MAX-ACCESS read-only 1977 STATUS current 1978 DESCRIPTION 1979 "A count of the Session Rejected/Parameters 1980 Label Range Notification Messages sent 1981 or received by this LDP Entity." 1982 ::= { mplsLdpEntityStatsEntry 5 } 1984 mplsLdpBadLdpIdentifierErrors OBJECT-TYPE 1985 SYNTAX Counter32 1986 MAX-ACCESS read-only 1987 STATUS current 1988 DESCRIPTION 1989 "This object counts the number of Bad LDP Identifier 1990 Fatal Errors detected by the session(s) 1991 (past and present) associated with this LDP Entity." 1992 REFERENCE 1993 "LDP Specification, Section 3.5.1.2." 1994 ::= { mplsLdpEntityStatsEntry 6 } 1996 mplsLdpBadPduLengthErrors OBJECT-TYPE 1997 SYNTAX Counter32 1998 MAX-ACCESS read-only 1999 STATUS current 2000 DESCRIPTION 2001 "This object counts the number of Bad Pdu Length 2002 Fatal Errors detected by the session(s) 2003 (past and present) associated with this LDP Entity." 2004 REFERENCE 2005 "LDP Specification, Section 3.5.1.2." 2006 ::= { mplsLdpEntityStatsEntry 7 } 2008 mplsLdpBadMessageLengthErrors OBJECT-TYPE 2009 SYNTAX Counter32 2010 MAX-ACCESS read-only 2011 STATUS current 2012 DESCRIPTION 2013 "This object counts the number of Bad Message 2014 Length Fatal Errors detected by the session(s) 2015 (past and present) associated with this LDP Entity." 2016 REFERENCE 2017 "LDP Specification, Section 3.5.1.2." 2018 ::= { mplsLdpEntityStatsEntry 8 } 2020 mplsLdpBadTlvLengthErrors OBJECT-TYPE 2021 SYNTAX Counter32 2022 MAX-ACCESS read-only 2023 STATUS current 2024 DESCRIPTION 2025 "This object counts the number of Bad TLV 2026 Length Fatal Errors detected by the session(s) 2027 (past and present) associated with this LDP Entity." 2028 REFERENCE 2029 "LDP Specification, Section 3.5.1.2." 2030 ::= { mplsLdpEntityStatsEntry 9 } 2032 mplsLdpMalformedTlvValueErrors OBJECT-TYPE 2033 SYNTAX Counter32 2034 MAX-ACCESS read-only 2035 STATUS current 2036 DESCRIPTION 2037 "This object counts the number of Malformed TLV 2038 Value Fatal Errors detected by the session(s) 2039 (past and present) associated with this 2040 LDP Entity." 2041 REFERENCE 2042 "LDP Specification, Section 3.5.1.2." 2043 ::= { mplsLdpEntityStatsEntry 10 } 2045 mplsLdpKeepAliveTimerExpiredErrors OBJECT-TYPE 2046 SYNTAX Counter32 2047 MAX-ACCESS read-only 2048 STATUS current 2049 DESCRIPTION 2050 "This object counts the number of Session Keep Alive 2051 Timer Expired Errors detected by the session(s) 2052 (past and present) associated with this LDP Entity." 2053 REFERENCE 2054 "LDP Specification, Section 3.5.1.2." 2055 ::= { mplsLdpEntityStatsEntry 11 } 2057 mplsLdpShutdownNotifReceived OBJECT-TYPE 2058 SYNTAX Counter32 2059 MAX-ACCESS read-only 2060 STATUS current 2061 DESCRIPTION 2062 "This object counts the number of Shutdown Notfications 2063 received related to session(s) (past and present) 2064 associated with this LDP Entity." 2065 ::= { mplsLdpEntityStatsEntry 12 } 2067 mplsLdpShutdownNotifSent OBJECT-TYPE 2068 SYNTAX Counter32 2069 MAX-ACCESS read-only 2070 STATUS current 2071 DESCRIPTION 2072 "This object counts the number of Shutdown Notfications 2073 sent related to session(s) (past and present) associated 2074 with this LDP Entity." 2075 ::= { mplsLdpEntityStatsEntry 13 } 2077 -- 2078 -- The MPLS LDP Peer Table 2079 -- 2081 mplsLdpSessionObjects OBJECT IDENTIFIER ::= 2082 { mplsLdpObjects 3 } 2084 mplsLdpPeerTable OBJECT-TYPE 2085 SYNTAX SEQUENCE OF MplsLdpPeerEntry 2086 MAX-ACCESS not-accessible 2087 STATUS current 2088 DESCRIPTION 2089 "Information about LDP peers known by Entities in 2090 the mplsLdpEntityTable. The information in this table 2091 is based on information from the Entity-Peer interaction 2092 during session initialization but is not appropriate 2093 for the mplsLdpSessionTable, because objects in this 2094 table may or may not be used in session establishment." 2095 ::= { mplsLdpSessionObjects 1 } 2097 mplsLdpPeerEntry OBJECT-TYPE 2098 SYNTAX MplsLdpPeerEntry 2099 MAX-ACCESS not-accessible 2100 STATUS current 2101 DESCRIPTION 2102 "Information about a single Peer which is related 2103 to a Session. NOTE: this table is used to 2104 augment the mplsLdpSessionTable." 2105 INDEX { mplsLdpEntityLdpId, 2106 mplsLdpEntityIndex, 2107 mplsLdpPeerLdpId } 2108 ::= { mplsLdpPeerTable 1 } 2110 MplsLdpPeerEntry ::= SEQUENCE { 2111 mplsLdpPeerLdpId MplsLdpIdentifier, 2112 mplsLdpPeerLabelDistributionMethod INTEGER, 2113 mplsLdpPeerLoopDetectionForPV INTEGER, 2114 mplsLdpPeerPathVectorLimit Integer32 2115 } 2117 mplsLdpPeerLdpId OBJECT-TYPE 2118 SYNTAX MplsLdpIdentifier 2119 MAX-ACCESS not-accessible 2120 STATUS current 2121 DESCRIPTION 2122 "The LDP identifier of this LDP Peer." 2123 ::= { mplsLdpPeerEntry 1 } 2125 mplsLdpPeerLabelDistributionMethod OBJECT-TYPE 2126 SYNTAX INTEGER { 2127 downstreamOnDemand(1), 2128 downstreamUnsolicited(2) 2129 } 2130 MAX-ACCESS read-only 2131 STATUS current 2132 DESCRIPTION 2133 "For any given LDP session, the method of 2134 label distribution must be specified." 2135 REFERENCE 2136 "draft-ietf-mpls-arch-06.txt [20]." 2137 ::= { mplsLdpPeerEntry 2 } 2139 mplsLdpPeerLoopDetectionForPV OBJECT-TYPE 2140 SYNTAX INTEGER { 2141 disabled(0), 2142 enabled(1) 2143 } 2144 MAX-ACCESS read-only 2145 STATUS current 2146 DESCRIPTION 2147 "An indication of whether loop detection based 2148 on path vectors is disabled or enabled for this Peer. 2150 If this object has a value of disabled(0), 2151 then loop detection is disabled. Otherwise, if this 2152 object has a value of enabled(1), then loop detection 2153 based on path vectors is enabled." 2154 ::= { mplsLdpPeerEntry 3 } 2156 mplsLdpPeerPathVectorLimit OBJECT-TYPE 2157 SYNTAX Integer32 (0..255) 2158 MAX-ACCESS read-only 2159 STATUS current 2160 DESCRIPTION 2161 "If the value of 'mplsLdpPeerLoopDetectionForPV' for 2162 this entry is 'enabled(1)', the this object represents 2163 that Path Vector Limit for this peer. 2165 If the value of 'mplsLdpPeerLoopDetectionForPV' for 2166 this entry is 'disabled(0)', then this value should 2167 be 0 (zero)." 2168 ::= { mplsLdpPeerEntry 4 } 2170 -- 2171 -- The MPLS LDP Hello Adjacency Table 2172 -- 2174 mplsLdpHelloAdjacencyObjects OBJECT IDENTIFIER ::= 2175 { mplsLdpSessionObjects 2 } 2177 mplsLdpHelloAdjacencyTable OBJECT-TYPE 2178 SYNTAX SEQUENCE OF MplsLdpHelloAdjacencyEntry 2179 MAX-ACCESS not-accessible 2180 STATUS current 2181 DESCRIPTION 2182 "A table of Hello Adjacencies for Sessions." 2183 ::= { mplsLdpHelloAdjacencyObjects 1 } 2185 mplsLdpHelloAdjacencyEntry OBJECT-TYPE 2186 SYNTAX MplsLdpHelloAdjacencyEntry 2187 MAX-ACCESS not-accessible 2188 STATUS current 2189 DESCRIPTION 2190 "Each row represents a single LDP Hello Adjacency. 2191 An LDP Session can have one or more Hello adjacencies." 2192 INDEX { mplsLdpEntityLdpId, 2193 mplsLdpEntityIndex, 2194 mplsLdpPeerLdpId, 2195 mplsLdpHelloAdjacencyIndex } 2196 ::= { mplsLdpHelloAdjacencyTable 1 } 2198 MplsLdpHelloAdjacencyEntry ::= SEQUENCE { 2199 mplsLdpHelloAdjacencyIndex Unsigned32, 2200 mplsLdpHelloAdjacencyHoldTimeRemaining TimeInterval, 2201 mplsLdpHelloAdjacencyType INTEGER 2202 } 2204 mplsLdpHelloAdjacencyIndex OBJECT-TYPE 2205 SYNTAX Unsigned32 (1..4294967295) 2206 MAX-ACCESS not-accessible 2207 STATUS current 2208 DESCRIPTION 2209 "An identifier for this specific adjacency." 2210 ::= { mplsLdpHelloAdjacencyEntry 1 } 2212 mplsLdpHelloAdjacencyHoldTimeRemaining OBJECT-TYPE 2213 SYNTAX TimeInterval 2214 MAX-ACCESS read-only 2215 STATUS current 2216 DESCRIPTION 2217 "The time remaining for this Hello Adjacency. 2218 This interval will change when the 'next' 2219 Hello message which corresponds to this 2220 Hello Adjacency is received." 2221 ::= { mplsLdpHelloAdjacencyEntry 2 } 2223 mplsLdpHelloAdjacencyType OBJECT-TYPE 2224 SYNTAX INTEGER { 2225 link(1), 2226 targeted(2) 2227 } 2228 MAX-ACCESS read-only 2229 STATUS current 2230 DESCRIPTION 2231 "This adjacency is the result of a 'link' 2232 hello if the value of this object is link(1). 2233 Otherwise, it is a result of a 'targeted' 2234 hello, targeted(2)." 2235 ::= { mplsLdpHelloAdjacencyEntry 3 } 2237 -- 2238 -- The MPLS LDP Sessions Table 2239 -- 2240 mplsLdpSessionUpDownTrapEnable OBJECT-TYPE 2241 SYNTAX INTEGER { 2242 enabled(1), 2243 disabled(2) 2244 } 2245 MAX-ACCESS read-write 2246 STATUS current 2247 DESCRIPTION 2248 "Indicates whether the traps, 'mplsLdpSessionUp' and 2249 'mplsLdpSessionDown' will be generated or not. 2251 If the value of this object is 'enabled(1)' 2252 then the traps will generated. If the value 2253 of this object is 'disabled(2)' then the 2254 traps will not be generated. The DEFVAL 2255 is set to 'disabled(1)'." 2256 DEFVAL { disabled } 2257 ::= { mplsLdpSessionObjects 3 } 2259 mplsLdpSessionTable OBJECT-TYPE 2260 SYNTAX SEQUENCE OF MplsLdpSessionEntry 2261 MAX-ACCESS not-accessible 2262 STATUS current 2263 DESCRIPTION 2264 "A table of Sessions between the LDP Entities and 2265 LDP Peers. Each row represents a single session." 2266 ::= { mplsLdpSessionObjects 4 } 2268 mplsLdpSessionEntry OBJECT-TYPE 2269 SYNTAX MplsLdpSessionEntry 2270 MAX-ACCESS not-accessible 2271 STATUS current 2272 DESCRIPTION 2273 "An entry in this table represents information on a 2274 single session between an LDP Entity and LDP Peer. 2275 The information contained in a row is read-only. 2277 Please note: the Path Vector Limit for the 2278 Session is the value which is configured in 2279 the corresponding mplsLdpEntityEntry. The 2280 Peer's Path Vector Limit is in noted in the 2281 mplsLdpPeerTable. 2283 Values which may differ from those configured are 2284 noted in the objects of this table, the 2285 mplsLdpAtmSessionTable and the 2286 mplsLdpFrameRelaySessionTable. A value will 2287 differ if it was negotiated between the 2288 Entity and the Peer. Values may or may not 2289 be negotiated. For example, if the values 2290 are the same then no negotiation takes place. 2291 If they are negotiated, then they may differ." 2292 AUGMENTS { mplsLdpPeerEntry } 2293 ::= { mplsLdpSessionTable 1 } 2295 MplsLdpSessionEntry ::= SEQUENCE { 2296 mplsLdpSessionState INTEGER, 2297 mplsLdpSessionProtocolVersion Integer32, 2298 mplsLdpSessionKeepAliveHoldTimeRemaining TimeInterval, 2299 mplsLdpSessionMaxPduLength Unsigned32, 2300 mplsLdpSessionDiscontinuityTime TimeStamp 2301 } 2303 mplsLdpSessionState OBJECT-TYPE 2304 SYNTAX INTEGER { 2305 nonexistent(1), 2306 initialized(2), 2307 openrec(3), 2308 opensent(4), 2309 operational(5) 2310 } 2311 MAX-ACCESS read-only 2312 STATUS current 2313 DESCRIPTION 2314 "The current state of the session, all of the 2315 states 1 - 5 are based on the state machine for 2316 session negotiation behavior." 2317 ::= { mplsLdpSessionEntry 1 } 2319 mplsLdpSessionProtocolVersion OBJECT-TYPE 2320 SYNTAX Integer32(1..65535) 2321 MAX-ACCESS read-only 2322 STATUS current 2323 DESCRIPTION 2324 "The version of the LDP Protocol which 2325 this session is using." 2326 ::= { mplsLdpSessionEntry 2 } 2328 mplsLdpSessionKeepAliveHoldTimeRemaining OBJECT-TYPE 2329 SYNTAX TimeInterval 2330 MAX-ACCESS read-only 2331 STATUS current 2332 DESCRIPTION 2333 "The keep alive hold time remaining for this session." 2334 ::= { mplsLdpSessionEntry 3 } 2336 mplsLdpSessionMaxPduLength OBJECT-TYPE 2337 SYNTAX Unsigned32 (1..65535) 2338 MAX-ACCESS read-only 2339 STATUS current 2340 DESCRIPTION 2341 "The value of maximum allowable length for LDP PDUs for 2342 this session. This value may have been negotiated during 2343 the Session Initialization." 2344 ::= { mplsLdpSessionEntry 4 } 2346 mplsLdpSessionDiscontinuityTime OBJECT-TYPE 2347 SYNTAX TimeStamp 2348 MAX-ACCESS read-only 2349 STATUS current 2350 DESCRIPTION 2351 "The value of sysUpTime on the most recent occasion at 2352 which any one or more of this session's counters 2353 suffered a discontinuity. The relevant counters are 2354 the specific instances associated with this session 2355 of any Counter32 or Counter64 object contained in the 2356 mplsLdpSessionStatsTable. If no such discontinuities have 2357 occurred since the last re-initialization of the local 2358 management subsystem, then this object contains a zero 2359 value. 2361 Also, an NMS can distinguish when a session 2362 between a given Entity and Peer goes away and then is 2363 're-established'. This value would change and 2364 thus indicate to the NMS that this is a 2365 different session." 2366 ::= { mplsLdpSessionEntry 5 } 2368 -- 2369 -- MPLS LDP ATM Session Information 2370 -- 2372 mplsLdpAtmSessionTable OBJECT-TYPE 2373 SYNTAX SEQUENCE OF MplsLdpAtmSessionEntry 2374 MAX-ACCESS not-accessible 2375 STATUS current 2376 DESCRIPTION 2377 "A table which relates Sessions in the 2378 'mplsLdpSessionTable' and their label 2379 range intersections. There could be one 2380 or more label range intersections between an 2381 LDP Entity and LDP Peer using ATM as the underlying 2382 media. Each row represents a single label range 2383 intersection. 2385 NOTE: this table cannot use the 'AUGMENTS' 2386 clause because there is not necessarily a one-to-one 2387 mapping between this table and the mplsLdpSessionTable." 2388 ::= { mplsLdpSessionObjects 5 } 2390 mplsLdpAtmSessionEntry OBJECT-TYPE 2391 SYNTAX MplsLdpAtmSessionEntry 2392 MAX-ACCESS not-accessible 2393 STATUS current 2394 DESCRIPTION 2395 "An entry in this table represents information on a 2396 single label range intersection between an LDP Entity 2397 and LDP Peer. 2399 The information contained in a row is read-only." 2400 INDEX { mplsLdpEntityLdpId, 2401 mplsLdpEntityIndex, 2402 mplsLdpPeerLdpId, 2403 mplsLdpSessionAtmLabelRangeLowerBoundVpi, 2404 mplsLdpSessionAtmLabelRangeLowerBoundVci 2406 } 2407 ::= { mplsLdpAtmSessionTable 1 } 2409 MplsLdpAtmSessionEntry ::= SEQUENCE { 2410 mplsLdpSessionAtmLabelRangeLowerBoundVpi AtmVpIdentifier, 2411 mplsLdpSessionAtmLabelRangeLowerBoundVci MplsAtmVcIdentifier, 2412 mplsLdpSessionAtmLabelRangeUpperBoundVpi AtmVpIdentifier, 2413 mplsLdpSessionAtmLabelRangeUpperBoundVci MplsAtmVcIdentifier 2414 } 2416 mplsLdpSessionAtmLabelRangeLowerBoundVpi OBJECT-TYPE 2417 SYNTAX AtmVpIdentifier 2418 MAX-ACCESS not-accessible 2419 STATUS current 2420 DESCRIPTION 2421 "The minimum VPI number for this range." 2422 ::= { mplsLdpAtmSessionEntry 1 } 2424 mplsLdpSessionAtmLabelRangeLowerBoundVci OBJECT-TYPE 2425 SYNTAX MplsAtmVcIdentifier 2426 MAX-ACCESS not-accessible 2427 STATUS current 2428 DESCRIPTION 2429 "The minimum VCI number for this range." 2430 ::= { mplsLdpAtmSessionEntry 2 } 2432 mplsLdpSessionAtmLabelRangeUpperBoundVpi OBJECT-TYPE 2433 SYNTAX AtmVpIdentifier 2434 MAX-ACCESS read-only 2435 STATUS current 2436 DESCRIPTION 2437 "The maximum VPI number for this range." 2438 ::= { mplsLdpAtmSessionEntry 3 } 2440 mplsLdpSessionAtmLabelRangeUpperBoundVci OBJECT-TYPE 2441 SYNTAX MplsAtmVcIdentifier 2442 MAX-ACCESS read-only 2443 STATUS current 2444 DESCRIPTION 2445 "The maximum VCI number for this range." 2446 ::= { mplsLdpAtmSessionEntry 4 } 2448 -- 2449 -- MPLS LDP Frame Relay Session Information 2450 -- 2452 mplsLdpFrameRelaySessionTable OBJECT-TYPE 2453 SYNTAX SEQUENCE OF MplsLdpFrameRelaySessionEntry 2454 MAX-ACCESS not-accessible 2455 STATUS current 2456 DESCRIPTION 2457 "A table of Frame Relay label range intersections 2458 between the LDP Entities and LDP Peers. 2459 Each row represents a single label range intersection. 2461 NOTE: this table cannot use the 'AUGMENTS' 2462 clause because there is not necessarily a one-to-one 2463 mapping between this table and the mplsLdpSessionTable." 2464 ::= { mplsLdpSessionObjects 6 } 2466 mplsLdpFrameRelaySessionEntry OBJECT-TYPE 2467 SYNTAX MplsLdpFrameRelaySessionEntry 2468 MAX-ACCESS not-accessible 2469 STATUS current 2470 DESCRIPTION 2471 "An entry in this table represents information on a 2472 single label range intersection between an 2473 LDP Entity and LDP Peer. 2475 The information contained in a row is read-only." 2476 INDEX { mplsLdpEntityLdpId, 2477 mplsLdpEntityIndex, 2478 mplsLdpPeerLdpId, 2479 mplsLdpFrSessionMinDlci 2480 } 2481 ::= { mplsLdpFrameRelaySessionTable 1 } 2483 MplsLdpFrameRelaySessionEntry ::= SEQUENCE { 2484 mplsLdpFrSessionMinDlci Integer32, 2485 mplsLdpFrSessionMaxDlci Integer32, 2486 mplsLdpFrSessionLen INTEGER 2487 } 2489 mplsLdpFrSessionMinDlci OBJECT-TYPE 2490 SYNTAX Integer32(0..4194303) 2491 MAX-ACCESS not-accessible 2492 STATUS current 2493 DESCRIPTION 2494 "The lower bound of DLCIs which are supported." 2495 ::= { mplsLdpFrameRelaySessionEntry 1 } 2497 mplsLdpFrSessionMaxDlci OBJECT-TYPE 2498 SYNTAX Integer32 (0..4194303) 2499 MAX-ACCESS read-only 2500 STATUS current 2501 DESCRIPTION 2502 "The upper bound of DLCIs which are supported." 2503 ::= { mplsLdpFrameRelaySessionEntry 2 } 2505 mplsLdpFrSessionLen OBJECT-TYPE 2506 SYNTAX INTEGER { 2507 tenDlciBits(0), 2508 twentyThreeDlciBits(2) 2509 } 2510 MAX-ACCESS read-only 2511 STATUS current 2512 DESCRIPTION 2513 "This object specifies the DLCI bits." 2514 ::= { mplsLdpFrameRelaySessionEntry 3 } 2516 -- 2517 -- The MPLS LDP Session Statistics Table 2518 -- 2520 mplsLdpSessionStatsTable OBJECT-TYPE 2521 SYNTAX SEQUENCE OF MplsLdpSessionStatsEntry 2522 MAX-ACCESS not-accessible 2523 STATUS current 2524 DESCRIPTION 2525 "A table of statistics for Sessions between 2526 LDP Entities and LDP Peers." 2527 ::= { mplsLdpSessionObjects 7 } 2529 mplsLdpSessionStatsEntry OBJECT-TYPE 2530 SYNTAX MplsLdpSessionStatsEntry 2531 MAX-ACCESS not-accessible 2532 STATUS current 2533 DESCRIPTION 2534 "An entry in this table represents statistical 2535 information on a single session between an LDP 2536 Entity and LDP Peer." 2537 AUGMENTS { mplsLdpPeerEntry } 2538 ::= { mplsLdpSessionStatsTable 1 } 2540 MplsLdpSessionStatsEntry ::= SEQUENCE { 2541 mplsLdpSessionStatsUnknownMessageTypeErrors Counter32, 2542 mplsLdpSessionStatsUnknownTlvErrors Counter32 2543 } 2545 mplsLdpSessionStatsUnknownMessageTypeErrors OBJECT-TYPE 2546 SYNTAX Counter32 2547 MAX-ACCESS read-only 2548 STATUS current 2549 DESCRIPTION 2550 "This object counts the number of Unknown Message Type 2551 Errors detected during this session. 2553 Discontinuities in the value of this counter can occur 2554 at re-initialization of the management system, and at 2555 other times as indicated by the value of 2556 mplsLdpSeeionDiscontinuityTime." 2557 ::= { mplsLdpSessionStatsEntry 1 } 2559 mplsLdpSessionStatsUnknownTlvErrors OBJECT-TYPE 2560 SYNTAX Counter32 2561 MAX-ACCESS read-only 2562 STATUS current 2563 DESCRIPTION 2564 "This object counts the number of Unknown TLV Errors 2565 detected during this session. 2567 Discontinuities in the value of this counter can occur 2568 at re-initialization of the management system, and at 2569 other times as indicated by the value of 2570 mplsLdpSeeionDiscontinuityTime." 2571 ::= { mplsLdpSessionStatsEntry 2 } 2573 -- 2574 -- Mpls FEC Table 2575 -- 2577 mplsFecTable OBJECT-TYPE 2578 SYNTAX SEQUENCE OF MplsFecEntry 2579 MAX-ACCESS not-accessible 2580 STATUS current 2581 DESCRIPTION 2582 "This table represents the FEC 2583 (Forwarding Equivalence Class) 2584 Information associated with an LSP." 2585 ::= { mplsLdpSessionObjects 8 } 2587 mplsFecEntry OBJECT-TYPE 2588 SYNTAX MplsFecEntry 2589 MAX-ACCESS not-accessible 2590 STATUS current 2591 DESCRIPTION 2592 "Each row represents a single FEC Element." 2593 INDEX { mplsFecIndex } 2594 ::= { mplsFecTable 1 } 2596 MplsFecEntry ::= SEQUENCE { 2597 mplsFecIndex Unsigned32, 2598 mplsFecType INTEGER, 2599 mplsFecAddressFamily AddressFamilyNumbers, 2600 mplsFecAddressLength Integer32, 2601 mplsFecAddress MplsLdpGenAddr, 2602 mplsFecStorageType StorageType, 2603 mplsFecRowStatus RowStatus 2604 } 2606 mplsFecIndex OBJECT-TYPE 2607 SYNTAX Unsigned32(1..4294967295) 2608 MAX-ACCESS not-accessible 2609 STATUS current 2610 DESCRIPTION 2611 "The index which uniquely identifies this entry." 2612 ::= { mplsFecEntry 1 } 2614 mplsFecType OBJECT-TYPE 2615 SYNTAX INTEGER { 2616 prefix(1), 2617 hostAddress(2) 2618 } 2619 MAX-ACCESS read-create 2620 STATUS current 2621 DESCRIPTION 2622 "The type of the FEC. If the value of this object 2623 is 'prefix(1)' then the FEC type described by this 2624 row is for address prefixes. 2626 If the value of this object is 'hostAddress(2)' then 2627 the FEC type described by this row is a host address." 2628 ::= { mplsFecEntry 2 } 2630 mplsFecAddressFamily OBJECT-TYPE 2631 SYNTAX AddressFamilyNumbers 2632 MAX-ACCESS read-create 2633 STATUS current 2634 DESCRIPTION 2635 "The value of this object is from the Address Family 2636 Numbers." 2637 ::= { mplsFecEntry 3 } 2639 mplsFecAddressLength OBJECT-TYPE 2640 SYNTAX Integer32(0..255) 2641 MAX-ACCESS read-create 2642 STATUS current 2643 DESCRIPTION 2644 "If the value of 'mplsFecType' is 'prefix(1)' 2645 then the value of this object is the length in 2646 bits of the address prefix represented by 2647 'mplsFecAddress', or if the length is zero then 2648 this is a special value which indicates that the 2649 prefix matches all addresses. In this case the 2650 prefix is also zero (i.e. 'mplsFecAddress' will 2651 have the value of zero.)" 2652 ::= { mplsFecEntry 4 } 2654 mplsFecAddress OBJECT-TYPE 2655 SYNTAX MplsLdpGenAddr 2656 MAX-ACCESS read-create 2657 STATUS current 2658 DESCRIPTION 2659 "If the value of 'mplsFecType' is 'prefix(1)' 2660 then the value of this object is the address prefix. 2661 If the value of the 'mplsFecAddressLength' 2662 is object is zero, then this object should also be 2663 zero." 2664 ::= { mplsFecEntry 5 } 2666 mplsFecStorageType OBJECT-TYPE 2667 SYNTAX StorageType 2668 MAX-ACCESS read-create 2669 STATUS current 2670 DESCRIPTION 2671 "The storage type for this entry." 2672 ::= { mplsFecEntry 6 } 2674 mplsFecRowStatus OBJECT-TYPE 2675 SYNTAX RowStatus 2676 MAX-ACCESS read-create 2677 STATUS current 2678 DESCRIPTION 2679 "An object that allows entries in this table to 2680 be created and deleted using the 2681 RowStatus convention." 2682 ::= { mplsFecEntry 7 } 2684 -- 2685 -- Mapping Tables between Sessions and the LSR MIB. 2686 -- 2688 -- 2689 -- SessionInLabels and InSegment 2690 -- 2692 mplsLdpSessionInLabelMapTable OBJECT-TYPE 2693 SYNTAX SEQUENCE OF MplsLdpSessionInLabelMapEntry 2694 MAX-ACCESS not-accessible 2695 STATUS current 2696 DESCRIPTION 2697 "A table of Session's Ingress Labels which 2698 are Mapped to the LSR MIB. 2699 Each row represents a single Ingress Label." 2700 ::= { mplsLdpSessionObjects 9 } 2702 mplsLdpSessionInLabelMapEntry OBJECT-TYPE 2703 SYNTAX MplsLdpSessionInLabelMapEntry 2704 MAX-ACCESS not-accessible 2705 STATUS current 2706 DESCRIPTION 2707 "An entry in this table represents information on a 2708 single session between an LDP Entity and LDP Peer. 2709 The information contained in a row is read-only." 2710 INDEX { mplsLdpEntityLdpId, 2711 mplsLdpEntityIndex, 2712 mplsLdpPeerLdpId, 2713 mplsLdpSessionInLabelIfIndex, 2714 mplsLdpSessionInLabel 2715 } 2716 ::= { mplsLdpSessionInLabelMapTable 1 } 2718 MplsLdpSessionInLabelMapEntry ::= SEQUENCE { 2719 mplsLdpSessionInLabelIfIndex InterfaceIndex, 2720 mplsLdpSessionInLabel MplsLabel, 2721 mplsLdpSessionInLabelType MplsLdpLabelTypes, 2722 mplsLdpSessionInLabelConnectionType INTEGER 2723 } 2725 mplsLdpSessionInLabelIfIndex OBJECT-TYPE 2726 SYNTAX InterfaceIndex 2727 MAX-ACCESS not-accessible 2728 STATUS current 2729 DESCRIPTION 2730 "The ifIndex of the 'mplsLdpSessionInLabel' which should 2731 have the same value as the 'mplsInSegmentIfIndex' in 2732 the LSR MIB." 2733 ::= { mplsLdpSessionInLabelMapEntry 1 } 2735 mplsLdpSessionInLabel OBJECT-TYPE 2736 SYNTAX MplsLabel 2737 MAX-ACCESS not-accessible 2738 STATUS current 2739 DESCRIPTION 2740 "The incoming label of this LSP. This has the same value 2741 as the 'mplsInSegmentLabel' in the LSR MIB." 2742 ::= { mplsLdpSessionInLabelMapEntry 2 } 2744 mplsLdpSessionInLabelType OBJECT-TYPE 2745 SYNTAX MplsLdpLabelTypes 2746 MAX-ACCESS read-only 2747 STATUS current 2748 DESCRIPTION 2749 "The Layer 2 Label Type for 'mplsLdpInLabel'." 2750 ::= { mplsLdpSessionInLabelMapEntry 3 } 2752 mplsLdpSessionInLabelConnectionType OBJECT-TYPE 2753 SYNTAX INTEGER { 2754 unknown(1), 2755 xconnect(2), 2756 terminates(3) 2757 } 2758 MAX-ACCESS read-only 2759 STATUS current 2760 DESCRIPTION 2761 "The type of LSP connection. 2762 The possible values are: 2764 unknown(1) -- this may be the value if the LSP 2765 is in a state of flux. It is 2766 considered to be a temporary 2767 situation. 2768 xconnect(2) -- if the mapping between the 2769 session and the insegment 2770 is associated with an LSP which 2771 is a true cross-connection. 2772 terminates(3) -- if the mapping between the 2773 session and the insegment 2774 is associated with an LSP which 2775 terminates on this LSR and is 2776 not a cross-connection." 2777 ::= { mplsLdpSessionInLabelMapEntry 4 } 2779 -- 2780 -- SessionOutLabels and OutSegment 2781 -- 2783 mplsLdpSessionOutLabelMapTable OBJECT-TYPE 2784 SYNTAX SEQUENCE OF MplsLdpSessionOutLabelMapEntry 2785 MAX-ACCESS not-accessible 2786 STATUS current 2787 DESCRIPTION 2788 "A table of Session's Egress Labels which 2789 are Mapped to the LSR MIB. 2790 Each row represents a single Egress Label." 2791 ::= { mplsLdpSessionObjects 10 } 2793 mplsLdpSessionOutLabelMapEntry OBJECT-TYPE 2794 SYNTAX MplsLdpSessionOutLabelMapEntry 2795 MAX-ACCESS not-accessible 2796 STATUS current 2797 DESCRIPTION 2798 "An entry in this table represents information on a 2799 single session between an LDP Entity and LDP Peer. 2800 The information contained in a row is read-only." 2801 INDEX { mplsLdpEntityLdpId, 2802 mplsLdpEntityIndex, 2803 mplsLdpPeerLdpId, 2804 mplsLdpSessionOutLabelIfIndex, 2805 mplsLdpSessionOutLabel 2806 } 2807 ::= { mplsLdpSessionOutLabelMapTable 1 } 2809 MplsLdpSessionOutLabelMapEntry ::= SEQUENCE { 2810 mplsLdpSessionOutLabelIfIndex InterfaceIndex, 2811 mplsLdpSessionOutLabel MplsLabel, 2812 mplsLdpSessionOutLabelType MplsLdpLabelTypes, 2813 mplsLdpSessionOutLabelConnectionType INTEGER, 2814 mplsLdpSessionOutSegmentIndex Integer32 2815 } 2817 mplsLdpSessionOutLabelIfIndex OBJECT-TYPE 2818 SYNTAX InterfaceIndex 2819 MAX-ACCESS not-accessible 2820 STATUS current 2821 DESCRIPTION 2822 "The ifIndex of the 'mplsLdpSessionOutLabel'." 2823 ::= { mplsLdpSessionOutLabelMapEntry 1 } 2825 mplsLdpSessionOutLabel OBJECT-TYPE 2826 SYNTAX MplsLabel 2827 MAX-ACCESS not-accessible 2828 STATUS current 2829 DESCRIPTION 2830 "The outgoing label of this LSP." 2831 ::= { mplsLdpSessionOutLabelMapEntry 2 } 2833 mplsLdpSessionOutLabelType OBJECT-TYPE 2834 SYNTAX MplsLdpLabelTypes 2835 MAX-ACCESS read-only 2836 STATUS current 2837 DESCRIPTION 2838 "The Layer 2 Label Type for 'mplsLdpOutLabel'." 2839 ::= { mplsLdpSessionOutLabelMapEntry 3 } 2841 mplsLdpSessionOutLabelConnectionType OBJECT-TYPE 2842 SYNTAX INTEGER { 2843 unknown(1), 2844 xconnect(2), 2845 starts(3) 2846 } 2847 MAX-ACCESS read-only 2848 STATUS current 2849 DESCRIPTION 2850 "The type of LSP connection. 2851 The possible values are: 2853 unknown(1) -- this may be the value if the LSP 2854 is in a state of flux. It is 2855 considered to be a temporary 2856 situation. 2857 xconnect(2) -- if the mapping between the 2858 session and the outsegment 2859 is associated with an LSP which 2860 is a true cross-connection. 2861 starts(3) -- if the mapping between the 2862 session and the insegment 2863 is associated with an LSP which 2864 starts on this LSR and is 2865 considered an ingress to the LSP." 2866 ::= { mplsLdpSessionOutLabelMapEntry 4 } 2868 mplsLdpSessionOutSegmentIndex OBJECT-TYPE 2869 SYNTAX Integer32(1..2147483647) 2870 MAX-ACCESS read-only 2871 STATUS current 2872 DESCRIPTION 2873 "This value should contain the same value as 2874 the 'mplsOutSegmentIndex' in the LSR MIB. 2876 NOTE: this value will never be zero, because 2877 this table only maps from Sessions to true 2878 outsegments." 2879 ::= { mplsLdpSessionOutLabelMapEntry 5 } 2881 -- 2882 -- Sessions and XConnects (LIB Information) 2883 -- 2885 mplsLdpSessionXCMapTable OBJECT-TYPE 2886 SYNTAX SEQUENCE OF MplsLdpSessionXCMapEntry 2887 MAX-ACCESS not-accessible 2888 STATUS current 2889 DESCRIPTION 2890 "A table of Session's Labels which 2891 are Mapped to the LSR MIB 's XConnect table. 2892 Each row represents a single cross connect." 2893 ::= { mplsLdpSessionObjects 11 } 2895 mplsLdpSessionXCMapEntry OBJECT-TYPE 2896 SYNTAX MplsLdpSessionXCMapEntry 2897 MAX-ACCESS not-accessible 2898 STATUS current 2899 DESCRIPTION 2900 "An entry in this table represents information on a 2901 single session between an LDP Entity and LDP Peer. 2902 The information contained in a row is read-only." 2903 INDEX { mplsLdpEntityLdpId, 2904 mplsLdpEntityIndex, 2905 mplsLdpPeerLdpId, 2906 mplsLdpSessionInLabelIfIndex, 2907 mplsLdpSessionInLabel, 2908 mplsLdpSessionOutLabelIfIndex, 2909 mplsLdpSessionOutLabel 2910 } 2911 ::= { mplsLdpSessionXCMapTable 1 } 2913 MplsLdpSessionXCMapEntry ::= SEQUENCE { 2914 mplsLdpSessionXCIndex Integer32 2915 } 2917 mplsLdpSessionXCIndex OBJECT-TYPE 2918 SYNTAX Integer32(1..2147483647) 2919 MAX-ACCESS read-only 2920 STATUS current 2921 DESCRIPTION 2922 "This value should contain the same value as 2923 the 'mplsXCIndex' in the LSR MIB. 2925 NOTE: this value will never be zero, because 2926 this table only maps from Sessions to true 2927 cross connects." 2928 ::= { mplsLdpSessionXCMapEntry 1 } 2930 -- 2931 -- XcrossConnectsFECs Table 2932 -- 2934 mplsXCsFecsTable OBJECT-TYPE 2935 SYNTAX SEQUENCE OF MplsXCsFecsEntry 2936 MAX-ACCESS not-accessible 2937 STATUS current 2938 DESCRIPTION 2939 "A table which shows the relationship between 2940 cross-connects and FECs. Each row represents 2941 a single cross connect to FEC association. 2942 This table is read-only." 2943 ::= { mplsLdpSessionObjects 13 } 2945 mplsXCsFecsEntry OBJECT-TYPE 2946 SYNTAX MplsXCsFecsEntry 2947 MAX-ACCESS not-accessible 2948 STATUS current 2949 DESCRIPTION 2950 "An entry represents a single cross connect 2951 to FEC association." 2952 INDEX { mplsLdpEntityLdpId, 2953 mplsLdpEntityIndex, 2954 mplsLdpPeerLdpId, 2955 mplsLdpSessionInLabelIfIndex, 2956 mplsLdpSessionInLabel, 2957 mplsLdpSessionOutLabelIfIndex, 2958 mplsLdpSessionOutLabel, 2959 mplsFecIndex 2960 } 2961 ::= { mplsXCsFecsTable 1 } 2963 MplsXCsFecsEntry ::= SEQUENCE { 2964 mplsXCFecOperStatus INTEGER, 2965 mplsXCFecOperStatusLastChange TimeStamp 2967 } 2969 mplsXCFecOperStatus OBJECT-TYPE 2970 SYNTAX INTEGER { 2971 unknown(1), 2972 inUse(2), 2973 notInUse(3) 2974 } 2975 MAX-ACCESS read-only 2976 STATUS current 2977 DESCRIPTION 2978 "An indication of the operational status of 2979 the FEC associated with this cross connect. 2981 unknown(1) - this is a temporary state which 2982 may indicate the LSP-FEC association 2983 is in a state of transition. 2985 inUse(2) - the FEC associated with the XC is 2986 currently being applied. 2988 notInUse(3) - the FEC associated with the XC is 2989 not being applied. Eventually, this 2990 entry may be aged out." 2991 ::= { mplsXCsFecsEntry 1 } 2993 mplsXCFecOperStatusLastChange OBJECT-TYPE 2994 SYNTAX TimeStamp 2995 MAX-ACCESS read-only 2996 STATUS current 2997 DESCRIPTION 2998 "This value of sysUpTime when the 2999 mplsXCFecOperStatus last changed state." 3000 ::= { mplsXCsFecsEntry 2 } 3002 -- 3003 -- Address Message/Address Withdraw Message Information 3004 -- 3005 -- This information is associated with a specific Session 3006 -- because Label Address Messages are sent after session 3007 -- initialization has taken place. 3008 -- 3010 mplsLdpSessionPeerAddressTable OBJECT-TYPE 3011 SYNTAX SEQUENCE OF MplsLdpSessionPeerAddressEntry 3012 MAX-ACCESS not-accessible 3013 STATUS current 3014 DESCRIPTION 3015 "This table 'extends' the mplsLdpSessionTable. 3016 This table is used to store Label Address Information 3017 from Label Address Messages received by this LSR from 3018 Peers. This table is read-only and should be updated 3019 when Label Withdraw Address Messages are received, i.e. 3020 Rows should be deleted as apropriate. 3022 NOTE: since more than one address may be contained 3023 in a Label Address Message, this table 'extends', 3024 rather than 'AUGMENTS' the mplsLdpSessionTable's 3025 information." 3026 ::= { mplsLdpSessionObjects 12 } 3028 mplsLdpSessionPeerAddressEntry OBJECT-TYPE 3029 SYNTAX MplsLdpSessionPeerAddressEntry 3030 MAX-ACCESS not-accessible 3031 STATUS current 3032 DESCRIPTION 3033 "An entry in this table represents information on 3034 session's for a single next hop address which was 3035 advertised in an Address Message from the LDP peer. 3036 The information contained in a row is read-only." 3037 INDEX { mplsLdpEntityLdpId, 3038 mplsLdpEntityIndex, 3039 mplsLdpPeerLdpId, 3040 mplsLdpSessionPeerAddressIndex 3041 } 3042 ::= { mplsLdpSessionPeerAddressTable 1 } 3044 MplsLdpSessionPeerAddressEntry ::= SEQUENCE { 3045 mplsLdpSessionPeerAddressIndex Unsigned32, 3046 mplsLdpSessionPeerNextHopAddressType AddressFamilyNumbers, 3047 mplsLdpSessionPeerNextHopAddress MplsLdpGenAddr 3048 } 3050 mplsLdpSessionPeerAddressIndex OBJECT-TYPE 3051 SYNTAX Unsigned32 (1..4294967295) 3052 MAX-ACCESS not-accessible 3053 STATUS current 3054 DESCRIPTION 3055 "An index which uniquely identifies this entry within 3056 a given session." 3057 ::= { mplsLdpSessionPeerAddressEntry 1 } 3059 mplsLdpSessionPeerNextHopAddressType OBJECT-TYPE 3060 SYNTAX AddressFamilyNumbers 3061 MAX-ACCESS read-only 3062 STATUS current 3063 DESCRIPTION 3064 "The internetwork layer address type of this Next Hop 3065 Address as specified in the Label Address Message 3066 associated with this Session. The value of this 3067 object indicates how to interpret the value of 3068 mplsLdpSessionPeerNextHopAddress." 3069 ::= { mplsLdpSessionPeerAddressEntry 2 } 3071 mplsLdpSessionPeerNextHopAddress OBJECT-TYPE 3072 SYNTAX MplsLdpGenAddr 3073 MAX-ACCESS read-only 3074 STATUS current 3075 DESCRIPTION 3076 "The value of the next hop address." 3077 REFERENCE 3078 "LDP Specification [18] defines only IPv4 for LDP Protocol 3079 Version 1, see section 3.4.3." 3080 ::= { mplsLdpSessionPeerAddressEntry 3 } 3082 -- 3083 -- Mpls Ldp FEC Table 3084 -- 3086 --- 3087 --- Notifications 3088 --- 3090 mplsLdpNotificationPrefix OBJECT IDENTIFIER ::= 3091 { mplsLdpNotifications 0 } 3093 mplsLdpFailedInitSessionThresholdExceeded NOTIFICATION-TYPE 3094 OBJECTS { 3095 mplsLdpEntityFailedInitSessionThreshold 3096 } 3097 STATUS current 3098 DESCRIPTION 3099 "This notification is generated when the value of 3100 the 'mplsLdpEntityFailedInitSessionTrapEnable' object 3101 is 'enabled(1)' and the value of the 3102 'mplsLdpEntityFailedInitSessionThreshold' object has 3103 been exceeded." 3104 ::= { mplsLdpNotificationPrefix 1 } 3106 mplsLdpPathVectorLimitMismatch NOTIFICATION-TYPE 3107 OBJECTS { 3108 mplsLdpEntityPathVectorLimit, 3109 mplsLdpPeerPathVectorLimit 3110 } 3111 STATUS current 3112 DESCRIPTION 3113 "This notification is generated when the value 3114 of the value of the 3115 'mplsLdpEntityFailedInitSessionTrapEnable' 3116 object is 'enabled(1)' and the 3117 'mplsLdpEntityPathVectorLimit' does NOT match 3118 the value of the 'mplsLdpPeerPathVectorLimit' for 3119 a specific Entity." 3120 REFERENCE 3121 "LDP Specification, Section 3.5.3." 3122 ::= { mplsLdpNotificationPrefix 2 } 3124 mplsLdpSessionUp NOTIFICATION-TYPE 3125 OBJECTS { 3126 mplsLdpSessionState 3127 } 3128 STATUS current 3129 DESCRIPTION 3130 "Generation of this trap occurs when the 3131 'mplsLdpSessionUpDownTrapEnable' object is 'enabled(1)' 3132 and the value of 'mplsLdpSessionState' changes from 3133 any state except 'nonexistent(1)' to 'operational(5)'." 3134 ::= { mplsLdpNotificationPrefix 3 } 3136 mplsLdpSessionDown NOTIFICATION-TYPE 3137 OBJECTS { 3138 mplsLdpSessionState 3139 } 3140 STATUS current 3141 DESCRIPTION 3142 "Generation of this trap occurs when the 3143 'mplsLdpSessionUpDownTrapEnable' object is 3144 'enabled(1)' and the value of 3145 'mplsLdpSessionState' changes from 3146 'operational(5)' to any other state." 3147 ::= { mplsLdpNotificationPrefix 4 } 3149 --**************************************************************** 3150 -- Module Conformance Statement 3151 --**************************************************************** 3153 mplsLdpGroups 3154 OBJECT IDENTIFIER ::= { mplsLdpConformance 1 } 3156 mplsLdpCompliances 3157 OBJECT IDENTIFIER ::= { mplsLdpConformance 2 } 3159 -- 3160 -- Compliance Statements 3161 -- 3163 mplsLdpModuleCompliance MODULE-COMPLIANCE 3164 STATUS current 3165 DESCRIPTION 3166 "The basic implentation requirements for agents that 3167 support the MPLS LDP MIB." 3168 MODULE -- this module 3169 MANDATORY-GROUPS { mplsLdpGeneralGroup, 3170 mplsLdpNotificationsGroup 3171 } 3172 GROUP mplsLdpAtmGroup 3173 DESCRIPTION 3174 "This group must be supported if ATM is used in the 3175 MPLS LDP implementation." 3177 GROUP mplsLdpFrameRelayGroup 3178 DESCRIPTION 3179 "This group must be supported if Frame Relay is used 3180 in the MPLS LDP implementation." 3182 GROUP mplsLdpMappingGroup 3183 DESCRIPTION 3184 "This group must be supported if the LSR MIB is 3185 implemented." 3186 ::= { mplsLdpCompliances 1 } 3188 -- units of conformance 3190 mplsLdpGeneralGroup OBJECT-GROUP 3191 OBJECTS { 3192 mplsLdpLsrId, 3193 mplsLdpLsrLoopDetectionCapable, 3194 mplsLdpEntityIndexNext, 3195 mplsLdpEntityProtocolVersion, 3196 mplsLdpEntityAdminStatus, 3197 mplsLdpEntityOperStatus, 3198 mplsLdpEntityWellKnownTcpDiscoveryPort, 3199 mplsLdpEntityWellKnownUdpDiscoveryPort, 3200 mplsLdpEntityMaxPduLength, 3201 mplsLdpEntityKeepAliveHoldTimer, 3202 mplsLdpEntityHelloHoldTimer, 3203 mplsLdpEntityFailedInitSessionTrapEnable, 3204 mplsLdpEntityFailedInitSessionThreshold, 3205 mplsLdpEntityLabelDistributionMethod, 3206 mplsLdpEntityLabelRetentionMode, 3207 mplsLdpEntityPVLimitMismatchTrapEnable, 3208 mplsLdpEntityPathVectorLimit, 3209 mplsLdpEntityHopCountLimit, 3210 mplsLdpEntityTargetedPeer, 3211 mplsLdpEntityTargetedPeerAddrType, 3212 mplsLdpEntityTargetedPeerAddr, 3213 mplsLdpEntityOptionalParameters, 3214 mplsLdpEntityDiscontinuityTime, 3215 mplsLdpEntityStorageType, 3216 mplsLdpEntityRowStatus, 3217 mplsLdpAttemptedSessions, 3218 mplsLdpSessionRejectedNoHelloErrors, 3219 mplsLdpSessionRejectedAdvertisementErrors, 3220 mplsLdpSessionRejectedMaxPduErrors, 3221 mplsLdpSessionRejectedLabelRangeErrors, 3222 mplsLdpBadLdpIdentifierErrors, 3223 mplsLdpBadPduLengthErrors, 3224 mplsLdpBadMessageLengthErrors, 3225 mplsLdpBadTlvLengthErrors, 3226 mplsLdpMalformedTlvValueErrors, 3227 mplsLdpKeepAliveTimerExpiredErrors, 3228 mplsLdpShutdownNotifReceived, 3229 mplsLdpShutdownNotifSent, 3230 mplsLdpPeerLabelDistributionMethod, 3231 mplsLdpPeerLoopDetectionForPV, 3232 mplsLdpPeerPathVectorLimit, 3233 mplsLdpHelloAdjacencyHoldTimeRemaining, 3234 mplsLdpHelloAdjacencyType, 3235 mplsLdpSessionUpDownTrapEnable, 3236 mplsLdpSessionState, 3237 mplsLdpSessionProtocolVersion, 3238 mplsLdpSessionKeepAliveHoldTimeRemaining, 3239 mplsLdpSessionMaxPduLength, 3240 mplsLdpSessionDiscontinuityTime, 3241 mplsLdpSessionStatsUnknownMessageTypeErrors, 3242 mplsLdpSessionStatsUnknownTlvErrors, 3243 mplsLdpSessionPeerNextHopAddressType, 3244 mplsLdpSessionPeerNextHopAddress 3245 } 3246 STATUS current 3247 DESCRIPTION 3248 "Objects that apply to all MPLS LDP implementations." 3249 ::= { mplsLdpGroups 1 } 3251 mplsLdpGenericGroup OBJECT-GROUP 3252 OBJECTS { 3253 mplsLdpEntityConfGenericIfIndexOrZero, 3254 mplsLdpEntityConfGenericLabelRangeStorageType, 3255 mplsLdpEntityConfGenericLabelRangeRowStatus, 3256 mplsLdpConfGenericStorageType, 3257 mplsLdpConfGenericRowStatus 3258 } 3259 STATUS current 3260 DESCRIPTION 3261 "Objects that apply to all MPLS LDP implementations 3262 using Generic Lables." 3263 ::= { mplsLdpGroups 2 } 3265 mplsLdpAtmGroup OBJECT-GROUP 3266 OBJECTS { 3267 mplsLdpEntityAtmIfIndexOrZero, 3268 mplsLdpEntityAtmMergeCap, 3269 mplsLdpEntityAtmLabelRangeComponents, 3270 mplsLdpEntityAtmVcDirectionality, 3271 mplsLdpEntityAtmLsrConnectivity, 3272 mplsLdpEntityDefaultControlVpi, 3273 mplsLdpEntityDefaultControlVci, 3274 mplsLdpEntityUnlabTrafVpi, 3275 mplsLdpEntityUnlabTrafVci, 3276 mplsLdpEntityAtmStorageType, 3277 mplsLdpEntityAtmRowStatus, 3278 mplsLdpEntityConfAtmLabelRangeMaximumVpi, 3279 mplsLdpEntityConfAtmLabelRangeMaximumVci, 3280 mplsLdpEntityConfAtmLabelRangeStorageType, 3281 mplsLdpEntityConfAtmLabelRangeRowStatus, 3282 mplsLdpSessionAtmLabelRangeUpperBoundVpi, 3283 mplsLdpSessionAtmLabelRangeUpperBoundVci 3285 } 3286 STATUS current 3287 DESCRIPTION 3288 "Objects that apply to all MPLS LDP implementations 3289 over ATM." 3290 ::= { mplsLdpGroups 3 } 3292 mplsLdpFrameRelayGroup OBJECT-GROUP 3293 OBJECTS { 3294 mplsLdpEntityFrIfIndexOrZero, 3295 mplsLdpEntityFrMergeCap, 3296 mplsLdpEntityFrLabelRangeComponents, 3297 mplsLdpEntityFrLen, 3298 mplsLdpEntityFrVcDirectionality, 3299 mplsLdpEntityFrParmsStorageType, 3300 mplsLdpEntityFrParmsRowStatus, 3301 mplsLdpConfFrMaximumDlci, 3302 mplsLdpConfFrStorageType, 3303 mplsLdpConfFrRowStatus, 3304 mplsLdpFrSessionMaxDlci, 3305 mplsLdpFrSessionLen 3306 } 3307 STATUS current 3308 DESCRIPTION 3309 "Objects that apply to all MPLS LDP implementations over 3310 Frame Relay." 3311 ::= { mplsLdpGroups 4 } 3313 mplsLdpMappingGroup OBJECT-GROUP 3314 OBJECTS { 3315 mplsLdpSessionInLabelType, 3316 mplsLdpSessionInLabelConnectionType, 3317 mplsLdpSessionOutLabelType, 3318 mplsLdpSessionOutLabelConnectionType, 3319 mplsLdpSessionOutSegmentIndex, 3320 mplsLdpSessionXCIndex, 3321 mplsFecType, 3322 mplsFecAddressFamily, 3323 mplsFecAddressLength, 3324 mplsFecAddress, 3325 mplsFecStorageType, 3326 mplsFecRowStatus, 3327 mplsXCFecOperStatus, 3328 mplsXCFecOperStatusLastChange 3329 } 3330 STATUS current 3331 DESCRIPTION 3332 "Objects that apply to all MPLS LDP implementations 3333 which support the relevant tables (mplsInSegmentTable, 3334 mplsOutSegmentTable and mplsXCTable) in the LSR MIB." 3335 ::= { mplsLdpGroups 5 } 3337 mplsLdpNotificationsGroup NOTIFICATION-GROUP 3338 NOTIFICATIONS { mplsLdpFailedInitSessionThresholdExceeded, 3339 mplsLdpPathVectorLimitMismatch, 3340 mplsLdpSessionUp, 3341 mplsLdpSessionDown 3342 } 3343 STATUS current 3344 DESCRIPTION 3345 "The notification(s) which an MPLS LDP implemention 3346 is required to implement." 3347 ::= { mplsLdpGroups 6 } 3349 END 3351 5. Revision History 3353 This section should be removed when this document is published as an 3354 RFC. 3356 5.1. Changes from 3358 The majority of changes in this revision are based on Last Call 3359 comments which were received during the last call from Thursday, 3360 March 9, 2000 to Friday, March 17, 2000, or slightly thereafter. 3361 Also, changes were made to agree with the latest specifications. 3362 These changes are described in this section. 3364 Changes due to draft-ietf-mpls-ldp-07.txt and draft-ietf-mpls-ldp- 3365 08.txt. Specifically, removing references to IPv4/IP and using router 3366 id, as appropriate. 3368 Removed vpMerge and vpAndVcMerge choices from the object, 3369 mplsLdpEntityAtmMergeCap. VP Merge is not described in [32]. 3371 * LIB Table was removed and replaced by 3 different mapping tables to 3372 map sessions to InSegment, OutSegment and XC tables in the LSR MIB. 3373 The conformance section was updated to include a Mapping Group which 3374 is to be implemented iff the LSR MIB is implemented. * front 3375 section, need to include something about the 3376 generic label table JOAN JOAN JOAN update the front section, need 3377 to add a section on how this differs from the LDP Specification with 3378 regard to Frame Relay and also the generic label range tables. * 3379 more on Row Creation/adminStatus/OperStatus in the LDP Entity 3380 and related tables. Need to probably do an algorithm type 3381 of thing 3383 Added a generic label range table. NOTE: there is NO corresponding 3384 LDP message which relates to the information in this table, however, 3385 this table does provide a way for a user to 'reserve' a generic label 3386 range. 3388 A new TEXTUAL-CONVENTION, MplsAtmVcIdentifier was added. This TC has 3389 the same upper bounds as AtmVcIdentifier (from rfc2514) except that 3390 the lower bound is 32 (and not 0). The lower bound is 32 since this 3391 value is specified by [32]. 3393 Removed the scalar object mplsLsrLabelRetentionMode and added 3394 mplsLdpEntityLabelRetentionMode. The change was made to allow 3395 configuring the retention mode on a per LDP Entity basis, as opposed 3396 for the entire LSR. 3398 Typo in section 3.5.2 was fixed. 3400 Typo in the mplsLdpSessionUp notification description was fixed. 3402 Section 'LDP Notifications' was expanded to cover both the 3403 'mplsLdpSessionUp' and 'mplsLdpSessionDown' traps. Also, the objects 3404 which enable and disable these traps have been described in this 3405 Section: 3407 The 'mplsLdpEntityHopCountLoopDetection' object and the 3408 'mplsLdpEntityHopCount' object have been combined into the new 3409 object, 'mplsLdpEntityHopCountLimit'. 3411 MplsLabel has been updated to reflect the VPI value of 12 bits and 3412 not 8. 3414 Added DEFVAL clause to the 'mplsLdpEntityWellKnownDiscoveryPort' 3415 object. The default value is 646. 3417 Added UNITS and DEFVAL clauses to the 'mplsLdpEntityMaxPduLength' 3418 object. The default value is 4096 and the units is octets. 3420 Added DEFVAL clause to 'mplsLdpEntityProtocolVersion' object. The 3421 default value is 1. 3423 Added DEFVAL clause to 'mplsLdpEntityKeepAliveHoldTimer' of 40 3424 seconds. 3426 Added DEFVAL clause to 'mplsLdpEntityFailedInitSessionThreshold' 3427 object. The default value is 8. 3429 The mplsLdpEntityWellKnownDiscoveryPort was changed into two objects, 3430 one for TCP and one for UDP. The names are 3432 Typo in the description for the 3434 The mplsLdpEntityPeerTable was (re-)named mplsLdpPeerTable. The 3435 mplsLdpSessionTable now AUGMENTs the mplsLdpPeerTable in order to 3436 show that these two tables are related. There has been wording added 3437 to the mplsLdpSessionEntry description and to the description for the 3438 mplsLdpPeerTable. 3440 5.2. Changes from 3442 Editorial changes, fixing typo's, fixing wrapping lines, etc. 3444 Updated references for latest drafts, and added [33] and [34] to 3445 Reference Section. 3447 Added to the Acknowledgements Section. 3449 Changed the SYNTAX and DESCRIPTION of the 3450 'mplsLdpLsrLoopDetectionCapable' object, so that it will also support 3451 the loop detection by hop count. 3453 Combined the 'mplsLdpEntityLoopDetectionForPV' and 3454 'mplsLdpEntityPathVectorLimit' objects. The functionality of the 3455 'mplsLdpEntityLoopDectionForPV' is now denoted by the value of 0 3456 (zero) in the 'mplsLdpEntityPathVectorLimit' object. This results in 3457 one less object 'mplsLdpEntityLoopDectionForPV' but does not 3458 sacrifice functionality. 3460 Changed 'mplsLdpLibLabelType' into two objects: 3461 'mplsLdpLibInLabelType' and differ from the egress label type. The 3462 MIB now reflects this. 3464 The following items were changed as a result of the Frame Relay Forum 3465 dropping support for 17-bit DLCIs: the MplsLabel TC description has 3466 been modified, and other Frame Relay Object descriptions were also 3467 modified (as specified in this section). 3469 The MplsLabel TC was also modified and reference 3. was added to the 3470 REFERENCE Clause. 3472 MplsLdpLabelTypes TC was modified to use an enum. 3474 InterfaceIndex support was added to the Entity information. This was 3475 specifically requested by several members of the working group. An 3476 additional table, mplsLdpEntityConfGenericTable as a way to configure 3477 Generic Labels, and an object, 'mplsLdpConfGenericIfIndexOrZero was 3478 added to map the InterfaceIndex used by Generic Labels. Objects were 3479 also added to the 'mplsLdpEntityAtmParmsTable' and the and 3480 'mplsLdpEntityFrIfIndex', respectively. 3482 Changed the name of the 'mplsLdpEntityMtu' object to be 3483 'mplsLdpEntityMaxPduLength' which is more consistent with the LDP 3484 Specification. Also, the description and SYNTAX were changed. 3486 Changed the SYNTAX of the 'mplsLdpSessionMaxPduLength' to unsigned32 3487 and changed the Range from (0..65535) to (1..65535). 3489 Added and improved the front section discussion on SNMP 3490 Notifications. 3492 Also, modified the DESCRIPTION clause of the 3494 Added objects to enable/disable the sending of traps: 3496 Added an object to enable/disable sending traps for Sessions changing 3497 from Up to Down, or Down to Up. 3499 Added notifications to generate traps from session changing from Up 3500 to Down, or Down to up. 3502 Added a StorageType object to the Entity and associated tables which 3503 are configurable. 3505 Added a Discontinuity Time object to the Entity Table, 3507 Added discussion on row creation in the Entity and other associated 3508 Entity tables. This is a new Section in the Front part of the 3509 document called: 3511 Removed the 'mplsLdpEntityControlMethod'. 3513 Made 'mplsLdpFecLspId' as part of the INDEX for the FEC table. This 3514 is to allow FECs to map to multiple LSPs. Also add a RowPointer to a 3515 row in the Session Table. 3517 Added an operation status object, 'mplsLdpLspOperStatus' and a last 3518 Change object, 'mplsLdpLspLastChangeto the LIB Table. This will be 3519 used to detect whether an LSP has changed its status. 3521 Changed the name of the mplsLdpPeerTable to the 3522 mplsLdpEntityPeerTable. This table contains information relevant to 3523 Peers which are known to specific Entities. The indexing of this 3524 table has also changed to include the Row in the Entity Table that 3525 this Peer is known by. The mplsLdpHelloAdjacencyTable and the 3526 mplsLdpSessionTable have been moved under this table. Since Hello 3527 Adjacencies are related to Entity-Peer information and Sessions are 3528 related to Entity-Peer information this was seen as a comprehensive 3529 and coherent modelling. Associated descriptions in the front section 3530 and in the tables have been changed to reflect this change. 3532 Moved the 'mplsLdpConfFrLen' object from the 3533 'mplsLdpEntityConfFrLabelRangeTable' to the 3534 'mplsLdpEntityFrameRelayParmsTable' since the Frame Relay 3535 interface/port can only use one header length at a time, i.e. a 3536 specific FR interface supports one address length for all VCs on that 3537 interface. Also, changed the object so that it only supports 10 and 3538 23 bit DLCI lengths. (The 17 bit length was dropped by the Frame 3539 Relay Forum and thus, is no longer required.) The name of this 3540 object was changed from 'mplsLdpConfFrLen' to 'mplsLdpEntityFrLen' to 3541 fit in with the 'mplsLdpEntityFrameRelayParmsTable'. 3543 Removed the seventeenDlciBits(1) value from the mplsLdpFrSessionLen 3544 object. (The 17 bit length was dropped by the Frame Relay Forum and 3545 thus, is no longer required.) 3547 Corrected the range of the 'mplsLdpEntityIndexNext' object to include 3548 0 (zero). 3550 5.3. Changes from 3552 Reworded the description of the mplsLdpAtmSessionTable to clarify 3553 that one or MORE label range intersection(s) is/are represented in 3554 this table. 3556 Reworded the description of the mplsLdpFrameRelaySessionTable to 3557 clarify that one or MORE label range intersection(s) is/are 3558 represented in this table. 3560 Added a new index, mplsLdpSessionPeerIndex, to the 3561 mplsLdpSessionPeerAddressTable. This new index uniquely identifies 3562 the entry within a given session. (Since adding 3563 mplsLdpSessionPeerNextHopAddressType, 3564 mplsLdpSessionPeerNextHopAddress to the INDEX clause of the 3565 mplsLdpSessionPeerAddressTable leaves a table with only indices and 3566 no objects, the work around was to add a new index which uniquely 3567 differentiates an entry within a given session.) 3569 Quite a few changes to the mplsLdpPeerTable. First, removed the 3570 mplsLdpPeerIndex from the mplsLdpPeerTable and other tables. This 3571 index served no purpose, so was removed. Second, removed the 3572 objects: mplsLdpPeerInternetworkAddrType, and 3573 mplsLdpPeerInternetworkAddr. Third, reworded the description of this 3574 table to include information which is known during Session 3575 Intialization attempts, the specific information has to do with Loop 3576 Dection based on Path Vectors. Since Section 3.5.3 of the LDP Spec 3577 when describing the PVLim says: "Although knowledge of a peer's path 3578 vector limit will not change an LSR's behavior, it does enable the 3579 LSR to alert an operator to a possible misconfiguration." and the 3580 object mplsLdpPeerPathVectorLimit is sent as a varbind in the 3581 mplsLdpPathVectorLimitMismatch notification. 3583 Removed the mplsLdpPeerIndex from the mplsLdpHelloAdjacencyTable. 3585 Removed the "IANA Address Family Numbers MIB" section. 3587 Updated the boiler.me from the ops web page dated Weds., Dec 22, 3588 1999. 3590 Updated the Security Section from the ops web page. 3592 Added the following objects to the mplsLdpEntityTable: 3593 mplsLdpEntityControlMethod, mplsLdpEntityLoopDectionForPV, and 3594 mplsLdpEntityPathVectorLimit. 3596 Removed mplsLdpSessionLabelAdvertisement, 3597 mplsLdpSessionLoopDetectionForPV, and mplsLdpSessionPathVectorLimit 3598 from the mplsLdpSessionTable. 3600 Changed the mplsLdpPathVectorLimitMismatch Notification to send 3601 mplsLdpEntityPathVectorLimit (instead of 3602 mplsLdpSessionPathVectorLimit). 3604 Copied the MplsLabel TC from draft-ietf-mpls-lsr-mib-00.txt and 3605 replaced the MplsLdpGenAddr for mplsLdpLibInLabel and 3606 mpslLdpLibOutLabel with MplsLabel. 3608 The mplsLdpSessionIndex was removed throughout the MIB. This was 3609 replaced by the object mplsLdpSessionDiscontinuityTime. The 3610 motivation was to reduce the number of indices. 3612 The descriptions for the objects in the mplsLdpSessionStatsTable, 3613 mplsLdpSessionStatsUnknownMessageTypeErrors and 3614 mplsLdpSessionStatsUnknownTlvErrors, have been updated to include a 3615 reference to the mplsLdpSessionDiscontinuityTime object. 3617 5.4. Changes from 3619 Added Scalar Objects: mplsLdpLsrLoopDetectionPresent, and 3620 mplsLdpEntityIndexNext. 3622 Added the following objects to the mplsLdpEntityTable: 3623 mplsLdpEntityProtocolVersion, mplsLdpEntityAdminStatus, 3624 mplsLdpEntityOperStatus, mplsLdpEntityTargetedPeer, 3625 mplsLdpEntityTargetedPeerAddrType, mplsLdpEntityTargetedPeerAddr, and 3626 mplsLdpEntityHelloHoldTimer. 3628 Changed the description of the mplsLdpEntityAtmParmsTable and added 3629 the following objects to this table: 3630 mplsLdpEntityAtmLsrConnectivity, mplsLdpEntityDefaultControlVpi, 3631 mplsLdpEntityDefaultControlVci, mplsLdpEntityUnlabTrafVpi, and 3632 mplsLdpEntityUnlabTrafVci. NOTE: the last four objects were in 3633 Version 01 of the MIB but were mistakenly omitted from Version 02. 3634 Now, they are back. 3636 Changed the indexing of the mplsLdpEntityConfAtmLabelRangeTable to 3637 include the minimum VPI/VCI. This is to ensure that indices in this 3638 table are unique. 3640 Changed the indexing of the mplsLdpEntityConfFrLabelRangeTable, to 3641 include the minimum DLCI value. This is to ensure that indices in 3642 this table are unique. 3644 Added [32] to Reference Section. 3646 5.5. Changes from 3648 The MIB was updated to correspond to draft-ietf-mpls-ldp-06.txt of 3649 the LDP Specification [18]. 3651 The front section was updated. 3653 The MIB was made to be less ATM-centric. Essentially, the ATM 3654 specific objects where removed from the tables and placed in ATM 3655 specific Tables. A "type" was added to the "base" tables and a row 3656 is to be created in the ATM/FR/etc. "type" table. Apropos 3657 compliance statements were added to reflect the separation of ATM and 3658 Frame Relay objects into their respective tables. 3660 Objects for Loop Detection were removed from describing the LDP 3661 implementation (i.e. the scalars were removed) and Loop Dection 3662 objects were added to the Session Table. (Although as the LDP 3663 Specification indicates loop detection should be for an LSR within a 3664 domain.) 3666 The following tables were added: mplsLdpEntityAtmParmsTable, 3667 mplsLdpEntityConfAtmLabelRangeTable, mplsLdpFrameRelayParmsTable, 3668 mplsLdpConfFrLabelRangeTable, mplsLdpAtmSessionTable, 3669 mpslLdpFrameRelaySessionTable, mplsLdpSessionPeerAddressTable, 3670 mplsLdpLibTable, and the mplsLdpFecTable. 3672 The following notifications were added: notification for Session 3673 removal. 3675 The following objects were removed from the Session Table: 3676 mplsLdpSessionRole was removed (this can be determined by comparing 3677 LSR Ids and does not need to be explicitely in the MIB.) ATM 3678 specific objects (mplsLdpSessionAtmLabelRangeLowerBoundVpi 3679 mplsLdpSessionAtmLabelRangeLowerBoundVci, 3680 mplsLdpSessionAtmLabelRangeUpperBoundVpi 3681 mplsLdpSessionAtmLabelRangeUpperBoundVci) were removed and put into a 3682 separate table. Frame Relay objects were added in a separate table. 3684 Hello Adjacency Table was updated. 3686 The objects, mplsLdpSessionRejectedParamErrors, 3687 mplsLdpSessionRejectedNoHelloErrors, mplsLdpBadLdpIdentifierErrors, 3688 mplsLdpBadPduLengthErrors, mplsLdpBadMessageLengthErrors, 3689 mplsLdpBadTlvLengthErrors, mplsLdpMalformedTlvValueErrors, 3690 mplsLdpKeepAliveTimerExpiredErrors, mplsLdpShutdownNotifReceived, and 3691 mplsLdpShutdownNotifSent were added to the mplsLdpEntityStatsTable. 3693 The mplsLdpSessionStatsTable was added to count statics based on a 3694 per Session basis. 3696 The mplLdpPeerConfAtmLabelRangeTable has been removed. There is no 3697 need to configure information for a Peer. All information for a peer 3698 is learned, thus peer information is read-only. 3700 (Editorial) References were updated to reflect the documents which 3701 this version was based on. 3703 5.6. Changes from 3705 Textual conventions were added for the LSR Identifier and the LDP 3706 Identifier. 3708 Top-level mib structure was added. The LDP MIB falls under a proposed 3709 hierarchy of mpls.mplsProtocols. 3711 The mib hierarchy within the LDP MIB was also changed. A new branch, 3712 under mpls.mplsProtocols.mplsLdpMIB.mplsLdpObjects was added. This 3713 branch is mplsLdpLsrObjects. Currently, this contains several new 3714 scalar objects: mplsLdpLsrID, mplsLdpLsrLoopDetectionPresent, 3715 mplsLdpLsrLoopDetectinAdminStatus, mplsLdpLsrPathVectorLimit, 3716 mplsLdpLsrHopCountLimit, mplsLdpLsrLoopPreventionPresent, 3717 mplsLdpLsrLoopPreventionAdminStatus, and 3718 mplsLdpLsrLabelRetentionMode. 3720 mplsLdpEntityTable is now indexed by mplsLdpEntityIdentifier, which 3721 is the LDP Identifier used in Session establishment. 3722 mplsLdpEntityLoopDetection and mplsLdpEntityLoopPrevention objects 3723 were removed from this table. 3725 The following objects were added to the mplsLdpEntityTable: 3726 mplsLdpEntityLabelSpaceType, mplsLdpEntityUnlabTrafVpi, 3727 mplsLdpEntityUnlabTrafVci, mplsLdpEntityMergeCapability, 3728 mplsLdpEntityVcDirectionality, and 3729 mplsLdpEntityLabelDistributionMethod. 3731 The following objects were added to the mplsLdpPeerEntityTable: 3732 mplsLdpPeerLabelDistributionMethod. 3734 The following object was removed from the mplsLdpEntityStatsTable: 3735 mplsLdpEntityEstablishedSessions. 3737 References were added and revised. 3739 6. Acknowledgments 3741 The authors would like to thank the following people: Leigh 3742 McLellan, Geetha Brown, Geping Chen and Charlan Zhou from Nortel 3743 Networks, and Zoltan Takacs and Bo Augustsson from Ericsson. Also, 3744 some members of the working group were very helpful with comments and 3745 corrections to the MIB; the authors would like to thank Adrian Farrel 3746 of Data Connection, and Alan Kullberg from Harris & Jeffries. 3748 7. References 3750 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 3751 for Describing SNMP Management Frameworks", RFC 2571, April 3752 1999. 3754 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 3755 of Management Information for TCP/IP-based Internets", STD 3756 16, RFC 1155, May 1990. 3758 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 3759 16, RFC 1212, March 1991. 3761 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 3762 SNMP", RFC 1215, March 1991. 3764 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3765 Rose, M., and S. Waldbusser, "Structure of Management 3766 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 3767 1999. 3769 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3770 Rose, M., and S. Waldbusser, "Textual Conventions for 3771 SMIv2", STD 58, RFC 2579, April 1999. 3773 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3774 Rose, M., and S. Waldbusser, "Conformance Statements for 3775 SMIv2", STD 58, RFC 2580, April 1999. 3777 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 3778 Network Management Protocol", STD 15, RFC 1157, May 1990. 3780 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3781 "Introduction to Community-based SNMPv2", RFC 1901, January 3782 1996. 3784 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3785 "Transport Mappings for Version 2 of the Simple Network 3786 Management Protocol (SNMPv2)", RFC 1906, January 1996. 3788 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 3789 Processing and Dispatching for the Simple Network Management 3790 Protocol (SNMP)", RFC 2572, April 1999. 3792 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 3793 (USM) for version 3 of the Simple Network Management 3794 Protocol (SNMPv3)", RFC 2574, April 1999. 3796 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3797 "Protocol Operations for Version 2 of the Simple Network 3798 Management Protocol (SNMPv2)", RFC 1905, January 1996. 3800 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 3801 RFC 2573, April 1999. 3803 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 3804 Access Control Model (VACM) for the Simple Network 3805 Management Protocol (SNMP)", RFC 2575, April 1999. 3807 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 3808 "Introduction to Version 3 of the Internet-standard Network 3809 Management Framework", RFC 2570, April 1999. 3811 [17] Narten, T., and H. Alvestrand, "Guidelines for Writing an IANA 3812 Considerations Section in RFCs.", RFC 2434, IBM, Maxware, October 3813 1998 3815 [18] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and B. 3816 Thomas, "LDP Specification.", draft-ietf-mpls-ldp-08.txt, June 3817 2000. 3819 [19] Callon, R., Doolan, P., Feldman, N., Fredette, A., Swallow, G., and 3820 A. Viswanathan, "A Framework for Multiprotocol Label Switching", 3821 draft-ietf-mpls-framework-06.txt, September 1999. 3823 [20] Rosen, E., Viswananthan, A., and R. Callon, "Multiprotocol Label 3824 Switching Architecture", draft-ietf-mpls-arch-06.txt, August 1999. 3826 [21] Jamoussi, B., editor, "Constraint-Based LSP Setup using LDP", 3827 draft-ietf-mpls-cr-ldp-04.txt, July 2000. 3829 [22] Bradner, S., "Key words for use in RFCs to Indicate Requirement 3830 Levels", BCP 14, RFC 2119, Harvard University, March 1997 3832 [23] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, 3833 RFC 2026, Harvard University, October 1996 3835 [24] Srinivansan, C., Viswanathan, A., and T. Nadeau "MPLS Traffic 3836 Engineering Management Information Base Using SMIv2", draft-ietf- 3837 mpls-te-mib-03.txt, March 2000. 3839 [25] Srinivansan, C., Viswanathan, A., and T. Nadeau "MPLS Label Switch 3840 Router Management Information Base Using SMIv2", draft-ietf-mpls- 3841 lsr-mib-05.txt, July 2000. 3843 [26] Greene, M., Cucchiara, J., and J. Luciani, "Definition of Managed 3844 Objects for the NBMA Next Hop Resolution Protocol (NHRP)", RFC 3845 2677, August 1999. 3847 [27] Internet Assigned Numbers Authority (IANA), ADDRESS FAMILY NUMBERS, 3848 (http://www.isi.edu/in-notes/iana/assignements/address-family- 3849 numbers), for MIB 3850 (ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib). 3852 [28] Noto, M., E. Spiegel, K. Tesink, "Definition of Textual Conventions 3853 and OBJECT-IDENTITIES for ATM Management", RFC 2514, February 1999. 3855 [29] McCloghrie, K., F. Kastenholz, "The Interfaces Group MIB using 3856 SMIv2", RFC 2233, November 1997. 3858 [30] Tesink, K. (ed.) "Definitions of Managed Objects for ATM 3859 Management", RFC 2515, February 1999. 3861 [31] Grossman, D., and J. Heinanen, "Multiprotocol Encapsulation over 3862 ATM Adaptation Layer 5", RFC 2684, September 1999. 3864 [32] Davie, B., J. Lawrence, K. McCloghrie, Y. Rekhter, E. Rosen, G. 3865 Swallow, and P. Doolan, "MPLS using LDP and ATM VC Switching", 3866 draft-ietf-mpls-atm-04.txt, June 2000. 3868 [33] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D., Fedorkow, G., 3869 Li, T., and A. Conta, "MPLS Label Stack Encoding", draft-ietf- 3870 mpls-label-encaps-07.txt, September 1999. 3872 [34] Conta, A., Doolan, P., and A. Malis, "Use of Label Switching on 3873 Frame Relay Networks Specification", draft-ietf-mpls-fr-06.txt, 3874 June 2000. 3876 8. Security Considerations 3878 There are a number of management objects defined in this MIB that have a 3879 MAX-ACCESS clause of read-write and/or read-create. Such objects may 3880 be considered sensitive or vulnerable in some network environments. 3881 The support for SET operations in a non-secure environment without 3882 proper protection can have a negative effect on network operations. 3884 There are a number of managed objects in this MIB that may contain 3885 sensitive information. These are contained in the mplsLdpEntityTable. 3886 The objects contained in this table are responsible for setting up or 3887 tearing down LSPs. 3889 It is thus important to control even GET access to these objects and 3890 possibly to even encrypt the values of these object when sending them 3891 over the network via SNMP. Not all versions of SNMP provide features 3892 for such a secure environment. 3894 SNMPv1 by itself is not a secure environment. Even if the network 3895 itself is secure (for example by using IPSec), even then, there is no 3896 control as to who on the secure network is allowed to access and 3897 GET/SET (read/change/create/delete) the objects in this MIB. 3899 It is recommended that the implementers consider the security 3900 features as provided by the SNMPv3 framework. Specifically, the use 3901 of the User-based Security Model RFC 2574 [RFC2574] and the View- 3902 based Access Control Model RFC 2575 [RFC2575] is recommended. 3904 It is then a customer/user responsibility to ensure that the SNMP 3905 entity giving access to an instance of this MIB, is properly 3906 configured to give access to the objects only to those principals 3907 (users) that have legitimate rights to indeed GET or SET 3908 (change/create/delete) them. 3910 9. Authors' Addresses 3912 James V. Luciani 3913 TollBridge Technologies 3914 PO BOX 1010 3915 Concord, MA 01742 3916 Email: jluciani@tollbridgetech.com 3918 Hans Sjostrand 3919 Ericsson 3920 Business Unit Datacom Networks and IP Services 3921 S-126 25 Stockholm, Sweden 3922 Phone: +46 8 719 9960 3923 Email: hans.sjostrand@etx.ericsson.se 3925 Joan Cucchiara 3926 Brix Networks 3927 300 Concord Ave. 3928 Billerica, MA 01821 3929 Phone: (978) 439-1523 3930 Email: jcucchiara@brixnet.com 3932 10. Full Copyright Statement 3934 Copyright (C) The Internet Society (1999, 2000). All Rights Reserved. 3936 This document and translations of it may be copied and furnished to 3937 others, and derivative works that comment on or otherwise explain it 3938 or assist in its implementation may be prepared, copied, published 3939 and distributed, in whole or in part, without restriction of any 3940 kind, provided that the above copyright notice and this paragraph are 3941 included on all such copies and derivative works. However, this 3942 document itself may not be modified in any way, such as by removing 3943 the copyright notice or references to the Internet Society or other 3944 Internet organizations, except as needed for the purpose of 3945 developing Internet standards in which case the procedures for 3946 copyrights defined in the Internet Standards process must be 3947 followed, or as required to translate it into languages other than 3948 English. 3950 The limited permissions granted above are perpetual and will not be 3951 revoked by the Internet Society or its successors or assigns. 3953 This document and the information contained herein is provided on an 3954 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 3955 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 3956 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 3957 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 3958 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.