idnits 2.17.1 draft-ietf-mpls-ldp-mib-03.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 56 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 43 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 2615 has weird spacing: '...for the purpo...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 1999) is 8931 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 2513, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 2522, but no explicit reference was found in the text == Unused Reference: '21' is defined on line 2531, but no explicit reference was found in the text == Unused Reference: '23' is defined on line 2537, but no explicit reference was found in the text == Unused Reference: '24' is defined on line 2540, but no explicit reference was found in the text == Unused Reference: '25' is defined on line 2544, but no explicit reference was found in the text == Unused Reference: '27' is defined on line 2552, but no explicit reference was found in the text == Unused Reference: '28' is defined on line 2557, but no explicit reference was found in the text == Unused Reference: '30' is defined on line 2563, but no explicit reference was found in the text == Unused Reference: '31' is defined on line 2566, 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-06 == Outdated reference: A later version (-05) exists of draft-ietf-mpls-framework-04 -- 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-02 == Outdated reference: A later version (-14) exists of draft-ietf-mpls-te-mib-01 == Outdated reference: A later version (-14) exists of draft-ietf-mpls-lsr-mib-00 -- Possible downref: Non-RFC (?) normative reference: ref. '27' ** Obsolete normative reference: RFC 2233 (ref. '29') (Obsoleted by RFC 2863) == Outdated reference: A later version (-04) exists of draft-ietf-mpls-atm-02 Summary: 18 errors (**), 0 flaws (~~), 21 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group J. Cucchiara 2 Internet-Draft IronBridge Networks 3 Expires April 2000 H. Sjostrand 4 Ericsson 5 J. Luciani 6 Nortel Networks 7 October 1999 9 Definitions of Managed Objects for 10 the Multiprotocol Label Switching, Label Distribution Protocol (LDP) 12 14 Status of this Memo 16 This document is an Internet-Draft and is in full conformance with 17 all provisions of Section 10 of RFC 2026. Internet-Drafts are 18 working documents of the Internet Engineering Task Force (IETF), its 19 areas, and its working groups. Note that other groups may also 20 distribute working documents as Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress". 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html 33 Distribution of this document is unlimited. Please send comments to 34 the Multiprotocol Label Switching (mpls) Working Group, 35 . 37 Copyright Notice 39 Copyright (C) The Internet Society (1999). All Rights Reserved. 41 Abstract 43 This memo defines a portion of the Management Information Base (MIB) 44 for use with network management protocols in the Internet community. 45 In particular, it describes managed objects for the Multiprotocol 46 Label Switching, Label Distribution Protocol (LDP). 48 Table of Contents 50 1 Introduction ................................................. 3 51 2 The SNMP Management Framework ................................ 3 52 3 Structure of the MIB ......................................... 5 53 3.1 Overview ................................................... 5 54 3.2 Interface Indexing ......................................... 5 55 3.3 Future Considerations ...................................... 5 56 3.4 Discussion of MIB Groups ................................... 6 57 3.5 The MPLS LDP General Group ................................. 6 58 3.5.1 The Label Distribution Protocol's Entity Table ........... 6 59 3.5.2 The Label Distribution Protocol's Entity ATM Objects ..... 6 60 Objects ................................................... 6 61 Table ..................................................... 7 62 3.5.5 The LDP Peer Table ....................................... 7 63 3.5.6 The LDP Session Table .................................... 7 64 3.5.7 The LDP ATM Session Table ................................ 7 65 3.5.8 The LDP Frame Relay Session Table ........................ 7 66 3.5.9 The LDP Session Statistics Table ......................... 7 67 3.5.10 The LDP Session Peer Address Table ...................... 8 68 3.5.11 The LDP Adjacencies Table ............................... 8 69 3.5.12 The LDP Label Information Base (LIB) Table .............. 8 70 3.5.13 The LDP FEC Table ....................................... 8 71 3.6 The LDP Notifications Group ................................ 8 72 3.6.1 LDP Notifications ........................................ 8 73 4 MPLS Label Distribution Protocol MIB Definitions ............. 8 74 5 Revision History ............................................. 49 75 5.1 Changes from .............. 49 76 5.2 Changes from .............. 49 77 5.3 Changes from .............. 50 78 6 TO DO List ................................................... 51 79 7 Acknowledgments .............................................. 51 80 8 References ................................................... 52 81 9 Security Considerations ...................................... 54 82 10 Authors' Addresses .......................................... 54 83 11 Full Copyright Statement .................................... 55 84 12 IANA Address Family Numbers MIB ............................. 55 86 1. Introduction 88 This memo defines a portion of the Management Information Base (MIB) 89 for use with network management protocols in the Internet community. 90 In particular, it describes managed objects for the Multiprotocol 91 Label Switching, Label Distribution Protocol (LDP) [18]. 93 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 94 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 95 document are to be interpreted as described in RFC 2119 [22]. 97 2. The SNMP Management Framework 99 The SNMP Management Framework presently consists of five major 100 components: 102 o An overall architecture, described in RFC 2571 [RFC2571]. 104 o Mechanisms for describing and naming objects and events for the 105 purpose of management. The first version of this Structure of 106 Management Information (SMI) is called SMIv1 and described in 107 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 108 1215 [RFC1215]. The second version, called SMIv2, is described 109 in STD 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580 110 [RFC2580]. 112 o Message protocols for transferring management information. The 113 first version of the SNMP message protocol is called SNMPv1 and 114 described in STD 15, RFC 1157 [RFC1157]. A second version of the 115 SNMP message protocol, which is not an Internet standards track 116 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] 117 and RFC 1906 [RFC1906]. The third version of the message 118 protocol is called SNMPv3 and described in RFC 1906 [RFC1906], 119 RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 121 o Protocol operations for accessing management information. The 122 first set of protocol operations and associated PDU formats is 123 described in STD 15, RFC 1157 [RFC1157]. A second set of 124 protocol operations and associated PDU formats is described in 125 RFC 1905 [RFC1905]. 127 o A set of fundamental applications described in RFC 2573 128 [RFC2573] and the view-based access control mechanism described 129 in RFC 2575 [RFC2575]. 131 A more detailed introduction to the current SNMP Management Framework 132 can be found in RFC 2570 [RFC2570]. 134 Managed objects are accessed via a virtual information store, termed 135 the Management Information Base or MIB. Objects in the MIB are 136 defined using the mechanisms defined in the SMI. 138 This memo specifies a MIB module that is compliant to the SMIv2. A 139 MIB conforming to the SMIv1 can be produced through the appropriate 140 translations. The resulting translated MIB must be semantically 141 equivalent, except where objects or events are omitted because no 142 translation is possible (use of Counter64). Some machine readable 143 information in SMIv2 will be converted into textual descriptions in 144 SMIv1 during the translation process. However, this loss of machine 145 readable information is not considered to change the semantics of the 146 MIB. 148 3. Structure of the MIB 150 This memo defines a portion of the Management Information Base (MIB) 151 for use with network management protocols in the Internet community. 152 In particular, it describes managed objects for the Multiprotocol 153 Label Switching, Label Distribution Protocol (LDP) as defined in 154 [18]. 156 3.1. Overview 158 The MIB provides objects to configure/set-up potential LDP sessions 159 on a specific LSR. A table is used to configure potential LDP 160 Sessions, where each row in the table initiates an LDP Session. This 161 is the mplsLdpEntityTable. 163 Another table, the mplsLdpPeerTable, is a read-only table which 164 records information learned via discovery. Each row in the Peer 165 Table represents a peer. 167 A third table is used to show the actual sessions which have been, or 168 are in the process of being established. Each row represents a 169 specific session between an Entity (on this LSR) and a peer. The 170 following figure demonstrates these relationships: 172 Entity Peer 173 ------------ ------------ 174 | | | | 175 ------------ ------------- 176 | | -------------- | | 177 ------------ -----> | | <----- ------------ 178 -------------- 179 Session 181 3.2. Interface Indexing 183 Interface Indexes as specified in [29] are used in the MIB. The 184 descriptions of the ifIndexes denote which ifIndex is being used. 185 NOTE: the use of ifIndex is for actual existing connections. 187 3.3. Future Considerations 189 The following aspects are not addressed in this document: VPN issues 190 (i.e. potential MIB objects such as the VPN Identifier are not 191 included at this time), and lastly, multicast issues are not 192 discussed. 194 Some of these issues need further clarification before adding to the 195 MIB. 197 3.4. Discussion of MIB Groups 199 Currently, there are four groups: the MPLS LDP General Group, the 200 MPLS LDP ATM Group, the MPLS LDP Frame Relay Group and the MPLS LDP 201 Notifications Group. The MPLS LDP General Group and the MPLS LDP 202 Notifications Group should always be supported. The MPLS LDP ATM 203 Group is specific to ATM and should be supported only if LDP is using 204 ATM. Likewise, the MPLS LDP Frame Relay group is specific to Frame 205 Relay and should be supported only if LDP is using Frame Relay. 207 3.5. The MPLS LDP General Group 209 This group contains information about the specific LDP Entities which 210 are associated with this agent. Each LSR must have one LDP Entity. 212 3.5.1. The Label Distribution Protocol's Entity Table 214 The LDP Entity Table provides a way to configure the LSR for using 215 LDP. There must be at least one LDP Entity for the LSR to support 216 LDP. 218 Each entry/row in this table represents a single LDP Entity. 220 3.5.2. The Label Distribution Protocol's Entity ATM Objects 222 There exists two tables to configure LDP for using ATM. These tables 223 are the mplsLdpEntityAtmParmsTable and the 224 mplsLdpEntityConfAtmLabelRangeTable. 226 The mplsLdpEntityAtmParmsTable provides a way to configure 227 information which would be contained in the 'Optional Paramer' 228 portion of an LDP PDU Initialization Message. 230 The mplsLdpEntityConfAtmLabelRangeTable provides a way to configure 231 information which would be contained in the 'ATM Label Range 232 Components' portion of an LDP PDU Intialization Message. 234 3.5.3. The Label Distribution Protocol's Entity Frame Relay Objects 236 There exists two tables to configure LDP for using Frame Relay. 237 These tables are the mplsLdpEntityFrameRelayParmsTable and the 238 mplsLdpEntityConfFrLabelRangeTable. 240 The mplsLdpEntityFrameRelayParmsTable provides a way to configure 241 information which would be contained in the 'Optional Paramer' 242 portion of an LDP PDU Initialization Message. 244 The mplsLdpEntityConfFrLabelRangeTable provides a way to configure 245 information which would be contained in the portion of an LDP PDU 246 Intialization Message. 248 3.5.4. The Label Distribution Protocol's Entity Statistics Table 250 The LDP Entity Statistics Table will maintain counters related to an 251 LDP Entity. This Table should be a read-only table which contains 252 statistical information. 254 Each row in this table will be related to a single LDP Entity. 256 3.5.5. The LDP Peer Table 258 The LDP Peer Table is a read-only table which contains information 259 about LDP Peers. Each row in this table represents an LDP Peer which 260 is known to an LDP Entity. 262 3.5.6. The LDP Session Table 264 The LDP Session Table is a read-only table. Each entry in this table 265 represents a single session between an LDP Entity and a Peer. 267 3.5.7. The LDP ATM Session Table 269 The MPLS LDP ATM Session Table is a read-only table which contains 270 session information specific to ATM. 272 3.5.8. The LDP Frame Relay Session Table 274 The MPLS LDP Frame Relay Session Table is a read-only table which 275 contains session information specific to Frame Relay. 277 3.5.9. The LDP Session Statistics Table 279 The MPLS LDP Session Stats Table is a read-only table which contains 280 statistical information on sessions. 282 3.5.10. The LDP Session Peer Address Table 284 The MPLS LDP Session Peer Address Table is a table which 'extends' 285 the mplsLdpSessionTable. This table is a read-only table which 286 stores Addresses learned after session initialization via "Address 287 Message" advertisement. 289 3.5.11. The LDP Adjacencies Table 291 This is a table of all adjacencies between all LPD Entities and all 292 LDP Peers. A Session may have one or more adjacencies. 294 3.5.12. The LDP Label Information Base (LIB) Table 296 The MPLS LDP LIB Table is a read-only table which contains 297 information stored in the LIB. This table is indexed by a unique 298 number which could be used to represent the LSP segment related to 299 this LIB entry. The Lsp number corresponds to a FEC entry in the FEC 300 Table which is described next. 302 3.5.13. The LDP FEC Table 304 The FEC Table is a read-only table whic contains FEC (Forwarding 305 Equivalence Class) information. Each entry/row represents a single 306 FEC Element. 308 3.6. The LDP Notifications Group 310 3.6.1. LDP Notifications 312 Currently, there is one notification which will be sent when an LDP 313 attempts to initialize the same session beyond the configured 314 threshold. 316 4. MPLS Label Distribution Protocol MIB Definitions 318 MPLS-LDP-MIB DEFINITIONS ::= BEGIN 320 IMPORTS 321 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, 322 experimental, 323 Integer32, Counter32, Unsigned32 324 FROM SNMPv2-SMI 326 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 327 FROM SNMPv2-CONF 329 TEXTUAL-CONVENTION, RowStatus, TimeInterval, TruthValue 330 FROM SNMPv2-TC 331 InterfaceIndex 332 FROM IF-MIB 333 -- AtmInterfaceType, 334 AtmVcIdentifier, AtmVpIdentifier 335 FROM ATM-TC-MIB 336 AddressFamilyNumbers 337 FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB 338 ; 340 mplsLdpMIB MODULE-IDENTITY 341 LAST-UPDATED "9910211200Z" -- October 21, 1999 342 ORGANIZATION "Multiprotocol Label Switching (mpls) Working Group" 343 CONTACT-INFO 344 "Joan Cucchiara (joan@ironbridgenetworks.com) 345 IronBridge Networks 347 Hans Sjostrand (hans.sjostrand@etx.ericsson.se) 348 Ericsson 350 James V. Luciani (luciani@baynetworks.com) 351 Nortel Networks" 352 DESCRIPTION 353 "This MIB contains managed object definitions for the 354 Multiprotocol Label Switching, Label Distribution 355 Protocol, LDP, as defined in draft-ietf-mpls-ldp-06.txt." 356 ::= { experimental XXXX } -- to be assigned 358 --******************************************************************** 359 -- MPLS LDP Textual Conventions 360 --******************************************************************** 361 -- 363 MplsLsrIdentifier ::= TEXTUAL-CONVENTION 364 STATUS current 365 DESCRIPTION 366 "The Label Switch Router (LSR) identifier 367 is the first 4 bytes or the IP Address component 368 of the Label Distribution Protocol (LDP) identifier." 369 SYNTAX OCTET STRING (SIZE (4)) 371 -- 372 -- A similar TC is also used in RFC2677.txt, perhaps 373 -- this should be made general and not MPLS specific. 374 -- 375 MplsLdpGenAddr ::= TEXTUAL-CONVENTION 376 STATUS current 377 DESCRIPTION 378 "The value of an network layer or data link layer address." 379 SYNTAX OCTET STRING (SIZE (0..64)) 381 MplsLdpIdentifier ::= TEXTUAL-CONVENTION 382 STATUS current 383 DESCRIPTION 384 "The LDP identifier is a six octet quantity 385 which is used to identify an Label Switch Router 386 (LSR) label space. 388 The first four octets encode an IP address 389 assigned to the LSR, and the last two octets 390 identify a specific label space within the LSR." 391 SYNTAX OCTET STRING (SIZE (6)) 393 MplsLdpLabelTypes ::= TEXTUAL-CONVENTION 394 STATUS current 395 DESCRIPTION 396 "The Layer 2 label types which are defined for 397 MPLS LDP are generic(1), atm(2), or frameRelay(3)." 398 SYNTAX INTEGER(1..3) 400 -- Top-level structure of the MIB (the following is proposed) 401 mpls OBJECT IDENTIFIER ::= { mplsProtocols } 403 mplsProtocols OBJECT IDENTIFIER ::= { mplsLdpObjects } 404 -- under mplsProtocols will be LDP, CR-LDP, 405 -- and other MPLS "Protocols". 407 mplsLdpObjects OBJECT IDENTIFIER ::= { mplsLdpMIB 1 } 408 mplsLdpNotifications OBJECT IDENTIFIER ::= { mplsLdpMIB 2 } 409 mplsLdpConformance OBJECT IDENTIFIER ::= { mplsLdpMIB 3 } 411 --**************************************************************** 412 -- MPLS LDP Objects 413 --**************************************************************** 415 mplsLdpLsrObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 1 } 417 mplsLdpEntityObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 2 } 419 -- 420 -- The MPLS Label Distribution Protocol Label Switch Router Objects 421 -- 423 mplsLdpLsrId OBJECT-TYPE 424 SYNTAX MplsLsrIdentifier 425 MAX-ACCESS read-only 426 STATUS current 427 DESCRIPTION 428 "The LSR's Identifier." 429 ::= { mplsLdpLsrObjects 1 } 431 mplsLdpLsrLabelRetentionMode OBJECT-TYPE 432 SYNTAX INTEGER { 433 conservative(1), 434 liberal(2) 435 } 436 MAX-ACCESS read-write 437 STATUS current 438 DESCRIPTION 439 "The LSR can be configured to use either 440 conservative or liberal label retention mode. 442 If the value of this object is conservative(1) 443 then advertized label mappings are retained 444 only if they will be used to forward packets, 445 i.e. if label came from a valid next hop. 447 If the value of this object is liberal(2) 448 then all advertized label mappings are retained 449 whether they are from a valid next hop or not." 450 ::= { mplsLdpLsrObjects 2 } 452 mplsLdpLsrLoopDetectionCapable OBJECT-TYPE 453 SYNTAX TruthValue 454 MAX-ACCESS read-only 455 STATUS current 456 DESCRIPTION 457 "A indication of whether this LSR supports 458 loop detection. A value of 'true' indicates 459 this LSR does support loop detection. A value 460 of 'false' indicates this LSR does not support 461 loop detection. Since Loop Detection is determined 462 during Session Initialization, an individual session 463 may not be running with loop detection enabled. This 464 object simply gives an indication of whether or not the 465 LSR has the ability to support Loop Detection." 466 ::= { mplsLdpLsrObjects 3 } 468 -- 469 -- The MPLS Label Distribution Protocol Entity Objects 470 -- 471 mplsLdpEntityIndexNext OBJECT-TYPE 472 SYNTAX Unsigned32 (1..4294967295) 473 MAX-ACCESS read-only 474 STATUS current 475 DESCRIPTION 476 "This object contains an appropriate value to 477 be used for mplsLdpEntityIndex when creating 478 entries in the mplsLdpEntityTable. The value 479 0 indicates that no unassigned entries are 480 available. To obtain the mplsLdpEntityIndex 481 value for a new entry, the manager issues a 482 management protocol retrieval operation to obtain 483 the current value of this object. After each 484 retrieval, the agent should modify the value to 485 the next unassigned index." 486 ::= { mplsLdpEntityObjects 1 } 488 mplsLdpEntityTable OBJECT-TYPE 489 SYNTAX SEQUENCE OF MplsLdpEntityEntry 490 MAX-ACCESS not-accessible 491 STATUS current 492 DESCRIPTION 493 "This table contains information about the 494 MPLS Label Distribution Protocol Entities which 495 exist on this Label Switch Router (LSR)." 496 ::= { mplsLdpEntityObjects 2 } 498 mplsLdpEntityEntry OBJECT-TYPE 499 SYNTAX MplsLdpEntityEntry 500 MAX-ACCESS not-accessible 501 STATUS current 502 DESCRIPTION 503 "An entry in this table represents an LDP entity. 504 An entry can be created by a network administrator 505 or by an SNMP agent as instructed by LDP." 506 INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex } 507 ::= { mplsLdpEntityTable 1 } 509 MplsLdpEntityEntry ::= SEQUENCE { 510 mplsLdpEntityLdpId MplsLdpIdentifier, 511 mplsLdpEntityIndex Unsigned32, 512 mplsLdpEntityProtocolVersion Integer32, 513 mplsLdpEntityAdminStatus INTEGER, 514 mplsLdpEntityOperStatus INTEGER, 515 mplsLdpEntityWellKnownDiscoveryPort Unsigned32, 516 mplsLdpEntityMtu Integer32, 517 mplsLdpEntityKeepAliveHoldTimer Integer32, 518 mplsLdpEntityHelloHoldTimer Integer32, 519 mplsLdpEntityFailedInitSessionThreshold Integer32, 520 mplsLdpEntityLabelDistributionMethod INTEGER, 521 mplsLdpEntityTargetedPeer TruthValue, 522 mplsLdpEntityTargetedPeerAddrType AddressFamilyNumbers, 523 mplsLdpEntityTargetedPeerAddr MplsLdpGenAddr, 524 mplsLdpEntityOptionalParameters MplsLdpLabelTypes, 525 mplsLdpEntityRowStatus RowStatus 526 } 528 mplsLdpEntityLdpId OBJECT-TYPE 529 SYNTAX MplsLdpIdentifier 530 MAX-ACCESS not-accessible 531 STATUS current 532 DESCRIPTION 533 "The LDP identifier. 535 The first four octets encode an IP address 536 assigned to the LSR, and the last two octets 537 identify a specific label space within the 538 LSR." 539 REFERENCE 540 "LDP Specification, Section on LDP Identifiers." 541 ::= { mplsLdpEntityEntry 1 } 543 mplsLdpEntityIndex OBJECT-TYPE 544 SYNTAX Unsigned32 (1..4294967295) 545 MAX-ACCESS not-accessible 546 STATUS current 547 DESCRIPTION 548 "This index is used as a secondary index to uniquely 549 identify this row. Before creating a row in this table, 550 the 'mplsLdpEntityIndexNext' object should be retrieved. 551 That value should be used for the value of this index 552 when creating a row in this table. (NOTE: if a value 553 of zero (0) is retrieved, that indicates that no rows 554 can be created in this table at this time." 555 ::= { mplsLdpEntityEntry 2 } 557 mplsLdpEntityProtocolVersion OBJECT-TYPE 558 SYNTAX Integer32 559 MAX-ACCESS read-create 560 STATUS current 561 DESCRIPTION 562 "The version number of the protocol. The value of 0 on a 563 read indicates that the version of the protocol is unknown. 564 Otherwise, the value of this object represents the version 565 of the LDP protocol." 566 ::= { mplsLdpEntityEntry 3 } 568 mplsLdpEntityAdminStatus OBJECT-TYPE 569 SYNTAX INTEGER { 570 enable(1), 571 disable(2) 572 } 573 MAX-ACCESS read-create 574 STATUS current 575 DESCRIPTION 576 "The administrative status of this LDP Entity." 577 DEFVAL { enable } 578 ::= { mplsLdpEntityEntry 4 } 580 mplsLdpEntityOperStatus OBJECT-TYPE 581 SYNTAX INTEGER { 582 unknown(0), 583 enabled(1), 584 disabled(2) 585 } 586 MAX-ACCESS read-only 587 STATUS current 588 DESCRIPTION 589 "The operational status of this LDP Entity." 590 ::= { mplsLdpEntityEntry 5 } 592 mplsLdpEntityWellKnownDiscoveryPort OBJECT-TYPE 593 SYNTAX Unsigned32 594 MAX-ACCESS read-create 595 STATUS current 596 DESCRIPTION 597 "The well known LDP Discovery Port." 598 ::= { mplsLdpEntityEntry 6 } 600 mplsLdpEntityMtu OBJECT-TYPE 601 SYNTAX Integer32 (0..65535) 602 MAX-ACCESS read-create 603 STATUS current 604 DESCRIPTION 605 "The maximum transmission unit (MTU) that was configured 606 for this entity." 607 ::= { mplsLdpEntityEntry 7 } 609 mplsLdpEntityKeepAliveHoldTimer OBJECT-TYPE 610 SYNTAX Integer32 (1..65535) 611 UNITS "seconds" 612 MAX-ACCESS read-create 613 STATUS current 614 DESCRIPTION 615 "The two octet value which is the proposed keep alive hold 616 timer for this LDP Entity." 617 ::= { mplsLdpEntityEntry 8 } 619 mplsLdpEntityHelloHoldTimer OBJECT-TYPE 620 SYNTAX Integer32 (0..65535) 621 UNITS "seconds" 622 MAX-ACCESS read-create 623 STATUS current 624 DESCRIPTION 625 "The two octet value which is the proposed Hello hold 626 timer for this LDP Entity. A value of 0 means use the default, 627 which is 15 seconds for Link Hellos and 45 seconds for Targeted 628 Hellos. A value of 65535 means infinite." 629 DEFVAL { 0 } 630 ::= { mplsLdpEntityEntry 9 } 632 mplsLdpEntityFailedInitSessionThreshold OBJECT-TYPE 633 SYNTAX Integer32 634 MAX-ACCESS read-create 635 STATUS current 636 DESCRIPTION 637 "When attempting to establish a session with a 638 given Peer, the given LDP Entity should 639 send out a notification when exceeding this threshold. 640 A value of 0 (zero) for this object 641 indicates that the threshold is infinity. 642 In other words, a notification will not 643 be sent if the value of this object is 0 (zero)." 644 ::= { mplsLdpEntityEntry 10 } 646 mplsLdpEntityLabelDistributionMethod OBJECT-TYPE 647 SYNTAX INTEGER { 648 downstreamOnDemand(1), 649 downstreamUnsolicited(2) 650 } 651 MAX-ACCESS read-create 652 STATUS current 653 DESCRIPTION 654 "For any given LDP session, the method of 655 label distribution must be specified." 656 ::= { mplsLdpEntityEntry 11 } 658 mplsLdpEntityTargetedPeer OBJECT-TYPE 659 SYNTAX TruthValue 660 MAX-ACCESS read-create 661 STATUS current 662 DESCRIPTION 663 "If this LDP entity uses targeted peer then set this to true." 664 DEFVAL { false } 665 ::= { mplsLdpEntityEntry 12 } 667 mplsLdpEntityTargetedPeerAddrType OBJECT-TYPE 668 SYNTAX AddressFamilyNumbers 669 MAX-ACCESS read-create 670 STATUS current 671 DESCRIPTION 672 "The type of the internetwork layer address used for 673 the Extended Discovery. This object indicates how the value of 674 mplsLdpEntityTargetedPeerAddr is to be interpreted." 675 ::= { mplsLdpEntityEntry 13 } 677 mplsLdpEntityTargetedPeerAddr OBJECT-TYPE 678 SYNTAX MplsLdpGenAddr 679 MAX-ACCESS read-create 680 STATUS current 681 DESCRIPTION 682 "The value of the internetwork layer address used for 683 the Extended Discovery." 684 ::= { mplsLdpEntityEntry 14 } 686 mplsLdpEntityOptionalParameters OBJECT-TYPE 687 SYNTAX MplsLdpLabelTypes 688 MAX-ACCESS read-create 689 STATUS current 690 DESCRIPTION 691 "Specifies the optional parameters for the LDP 692 Initialization Message. If the value is generic(1) 693 then no optional parameters will be sent in 694 the LDP Initialization message associated with 695 this Entity. 697 If the value is atmParameters(2) then 698 a row must be created in the mplsLdpEntityAtmParms 699 Table, which corresponds to this entry. 701 If the value is frameRelayParameters(3) then 702 a row must be created in the mplsLdpEntityFrameRelayParms 703 Table, which corresponds to this entry." 704 ::= { mplsLdpEntityEntry 15 } 706 mplsLdpEntityRowStatus OBJECT-TYPE 707 SYNTAX RowStatus 708 MAX-ACCESS read-create 709 STATUS current 710 DESCRIPTION 711 "An object that allows entries in this table to 712 be created and deleted using the 713 RowStatus convention." 714 ::= { mplsLdpEntityEntry 16 } 716 -- 717 -- Ldp Entity Objects for ATM 718 -- 720 mplsLdpEntityAtmObjects OBJECT IDENTIFIER ::= { mplsLdpEntityObjects 3 721 } 723 mplsLdpEntityAtmParmsTable OBJECT-TYPE 724 SYNTAX SEQUENCE OF MplsLdpEntityAtmParmsEntry 725 MAX-ACCESS not-accessible 726 STATUS current 727 DESCRIPTION 728 "This table contains information about the 729 ATM specific information which could be used 730 in the 'Optional Parameters' and other ATM specific 731 information." 732 ::= { mplsLdpEntityAtmObjects 1 } 734 mplsLdpEntityAtmParmsEntry OBJECT-TYPE 735 SYNTAX MplsLdpEntityAtmParmsEntry 736 MAX-ACCESS not-accessible 737 STATUS current 738 DESCRIPTION 739 "An entry in this table represents the ATM parameters 740 and ATM information for this LDP entity." 741 INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex } 742 ::= { mplsLdpEntityAtmParmsTable 1 } 744 MplsLdpEntityAtmParmsEntry ::= SEQUENCE { 745 mplsLdpEntityAtmMergeCap INTEGER, 746 mplsLdpEntityAtmLabelRangeComponents Unsigned32, 747 mplsLdpEntityAtmVcDirectionality INTEGER, 748 mplsLdpEntityAtmLsrConnectivity INTEGER, 749 mplsLdpEntityDefaultControlVpi AtmVpIdentifier, 750 mplsLdpEntityDefaultControlVci AtmVcIdentifier, 751 mplsLdpEntityUnlabTrafVpi AtmVpIdentifier, 752 mplsLdpEntityUnlabTrafVci AtmVcIdentifier, 753 mplsLdpEntityAtmRowStatus RowStatus 754 } 756 mplsLdpEntityAtmMergeCap OBJECT-TYPE 757 SYNTAX INTEGER { 758 notSupported(0), 759 vpMerge(1), 760 vcMerge(2), 761 vpAndVcMerge(3) 762 } 763 MAX-ACCESS read-create 764 STATUS current 765 DESCRIPTION 766 "Denotes the Merge Capability of this Entity." 767 ::= { mplsLdpEntityAtmParmsEntry 1 } 769 mplsLdpEntityAtmLabelRangeComponents OBJECT-TYPE 770 SYNTAX Unsigned32 (1..65535) 771 MAX-ACCESS read-create 772 STATUS current 773 DESCRIPTION 774 "Number of LabelRange Components in the Initialization 775 message. This also represents the number of entries 776 in the mplsLdpLabelRangeComponentsTable which correspond 777 to this entry." 778 ::= { mplsLdpEntityAtmParmsEntry 2 } 780 mplsLdpEntityAtmVcDirectionality OBJECT-TYPE 781 SYNTAX INTEGER { 782 bidirectional(0), 783 unidirectional(1) 784 } 785 MAX-ACCESS read-create 786 STATUS current 787 DESCRIPTION 788 "If the value of this object is 'bidirectional(0)', 789 a given VCI, within a given VPI, is used as a 790 label for both directions independently. 792 If the value of this object is 'unidirectional(1)', 793 a given VCI within a VPI designates one direction." 794 ::= { mplsLdpEntityAtmParmsEntry 3 } 796 mplsLdpEntityAtmLsrConnectivity OBJECT-TYPE 797 SYNTAX INTEGER { 798 direct(1), 799 indirect(2) 800 } 801 MAX-ACCESS read-create 802 STATUS current 803 DESCRIPTION 804 "The peer LSR may be connected indirectly by means of an 805 ATM VP so that the VPI values may be different on either 806 endpoint so the label MUST be encoded entirely within the 807 VCI field." 808 REFERENCE 809 "draft-ietf-mpls-atm-02.txt, Section 7" 810 DEFVAL { direct } 811 ::= { mplsLdpEntityAtmParmsEntry 4 } 813 mplsLdpEntityDefaultControlVpi OBJECT-TYPE 814 SYNTAX AtmVpIdentifier 815 MAX-ACCESS read-create 816 STATUS current 817 DESCRIPTION 818 "The default VPI value for the non-MPLS connection. The 819 default value of this is 0 (zero) but other values may 820 be configured. This object allows a different value 821 to be configured." 822 REFERENCE 823 "draft-ietf-mpls-atm-02.txt, Section 7.1" 824 DEFVAL 825 { 0 } 826 ::= { mplsLdpEntityAtmParmsEntry 5 } 828 mplsLdpEntityDefaultControlVci OBJECT-TYPE 829 SYNTAX AtmVcIdentifier 830 MAX-ACCESS read-create 831 STATUS current 832 DESCRIPTION 833 "The Default VCI value for a non-MPLS connection. The 834 default value of this is 32 but other values may be 835 configured. This object allows a different value to 836 be configured." 837 REFERENCE 838 "draft-ietf-mpls-atm-02.txt, Section 7.1" 839 DEFVAL 840 { 32 } 841 ::= { mplsLdpEntityAtmParmsEntry 6 } 843 mplsLdpEntityUnlabTrafVpi OBJECT-TYPE 844 SYNTAX AtmVpIdentifier 845 MAX-ACCESS read-create 846 STATUS current 847 DESCRIPTION 848 "VPI value of the VCC supporting unlabelled traffic. This 849 non-MPLS connection is used to carry unlabelled (IP) packets." 850 DEFVAL { 0 } 851 ::= { mplsLdpEntityAtmParmsEntry 7 } 853 mplsLdpEntityUnlabTrafVci OBJECT-TYPE 854 SYNTAX AtmVcIdentifier 855 MAX-ACCESS read-create 856 STATUS current 857 DESCRIPTION 858 "VCI value of the VCC supporting unlabelled traffic. 859 This non-MPLS connection is used to carry unlabelled (IP) 860 packets." 861 DEFVAL { 32 } 862 ::= { mplsLdpEntityAtmParmsEntry 8 } 864 mplsLdpEntityAtmRowStatus OBJECT-TYPE 865 SYNTAX RowStatus 866 MAX-ACCESS read-create 867 STATUS current 868 DESCRIPTION 869 "An object that allows entries in this table to 870 be created and deleted using the 871 RowStatus convention." 872 ::= { mplsLdpEntityAtmParmsEntry 9 } 874 -- 875 -- The MPLS LDP Entity Configurable ATM Label Range Table 876 -- 878 mplsLdpEntityConfAtmLabelRangeTable OBJECT-TYPE 879 SYNTAX SEQUENCE OF MplsLdpEntityConfAtmLabelRangeEntry 880 MAX-ACCESS not-accessible 881 STATUS current 882 DESCRIPTION 883 "The MPLS LDP Entity Configurable ATM Label Range Table. 884 The purpose of this table is to provide a mechanism 885 for specifying a contiguous range of vpi's 886 with a contiguous range of vci's, or a 'label range' 887 for LDP Entities. 889 LDP Entities which use ATM must have at least one 890 entry in this table." 891 ::= { mplsLdpEntityAtmObjects 2 } 893 mplsLdpEntityConfAtmLabelRangeEntry OBJECT-TYPE 894 SYNTAX MplsLdpEntityConfAtmLabelRangeEntry 895 MAX-ACCESS not-accessible 896 STATUS current 897 DESCRIPTION 898 "A row in the LDP Entity Configurable ATM Label 899 Range Table. One entry in this table contains 900 information on a single range of labels 901 represented by the configured Upper and Lower 902 Bounds VPI/VCI pairs. These are the same 903 data used in the Initialization Message. 905 NOTE: The ranges for a specific LDP Entity 906 are UNIQUE and non-overlapping. For example, 907 for a specific LDP Entity index, there could 908 be one entry having ConfLowerBound vpi/vci == 0/32, and 909 ConfUpperBound vpi/vci == 0/100, and a second entry for this 910 same interface with ConfLowerBound vpi/vci == 0/101 and 911 ConfUpperBound vpi/vci == 0/200. However, there could not be 912 a third entry with ConfLowerBound vpi/vci == 0/200 and 913 ConfUpperBound vpi/vci == 0/300 because this label range 914 overlaps 915 with the second entry (i.e. both entries now have 0/200). 917 A row will not be created unless a unique and non-overlapping 918 range is specified. Thus, row creation implies a one-shot 919 row creation of LDP EntityID and ConfLowerBound vpi/vci and 920 ConfUpperBound vpi/vci. At least one label range entry 921 for a specific LDP Entity MUST include the default VPI/VCI 922 values denoted in the LDP Entity Table." 923 INDEX { mplsLdpEntityLdpId, 924 mplsLdpEntityIndex, 925 mplsLdpEntityConfAtmLabelRangeMinimumVpi, 926 mplsLdpEntityConfAtmLabelRangeMinimumVci 927 } 928 ::= { mplsLdpEntityConfAtmLabelRangeTable 1 } 930 MplsLdpEntityConfAtmLabelRangeEntry ::= SEQUENCE { 931 mplsLdpEntityConfAtmLabelRangeMinimumVpi AtmVpIdentifier, 932 mplsLdpEntityConfAtmLabelRangeMinimumVci AtmVcIdentifier, 933 mplsLdpEntityConfAtmLabelRangeMaximumVpi AtmVpIdentifier, 934 mplsLdpEntityConfAtmLabelRangeMaximumVci AtmVcIdentifier, 935 mplsLdpEntityConfAtmLabelRangeRowStatus RowStatus 936 } 938 mplsLdpEntityConfAtmLabelRangeMinimumVpi OBJECT-TYPE 939 SYNTAX AtmVpIdentifier 940 MAX-ACCESS not-accessible 941 STATUS current 942 DESCRIPTION 943 "The minimum VPI number configured for this range." 944 ::= { mplsLdpEntityConfAtmLabelRangeEntry 1 } 946 mplsLdpEntityConfAtmLabelRangeMinimumVci OBJECT-TYPE 947 SYNTAX AtmVcIdentifier 948 MAX-ACCESS not-accessible 949 STATUS current 950 DESCRIPTION 951 "The minimum VCI number configured for this range." 952 ::= { mplsLdpEntityConfAtmLabelRangeEntry 2 } 954 mplsLdpEntityConfAtmLabelRangeMaximumVpi OBJECT-TYPE 955 SYNTAX AtmVpIdentifier 956 MAX-ACCESS read-create 957 STATUS current 958 DESCRIPTION 959 "The maximum VPI number configured for this range." 960 ::= { mplsLdpEntityConfAtmLabelRangeEntry 3 } 962 mplsLdpEntityConfAtmLabelRangeMaximumVci OBJECT-TYPE 963 SYNTAX AtmVcIdentifier 964 MAX-ACCESS read-create 965 STATUS current 966 DESCRIPTION 967 "The maximum VCI number configured for this range." 969 ::= { mplsLdpEntityConfAtmLabelRangeEntry 4 } 971 mplsLdpEntityConfAtmLabelRangeRowStatus OBJECT-TYPE 972 SYNTAX RowStatus 973 MAX-ACCESS read-create 974 STATUS current 975 DESCRIPTION 976 "An object that allows entries in this 977 table to be created and deleted using 978 the RowStatus convention. 980 There must exist at least one entry in this 981 table for every LDP Entity that has 982 'mplsLdpEntityOptionalParameters' object with 983 a value of 'atmSessionParameters'." 984 ::= { mplsLdpEntityConfAtmLabelRangeEntry 5 } 986 -- 987 -- Ldp Entity Objects for Frame Relay 988 -- 990 mplsLdpEntityFrameRelayObjects OBJECT IDENTIFIER ::= 991 { mplsLdpEntityObjects 4 } 993 mplsLdpEntityFrameRelayParmsTable OBJECT-TYPE 994 SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayParmsEntry 995 MAX-ACCESS not-accessible 996 STATUS current 997 DESCRIPTION 998 "This table contains information about the 999 Optional Parameters to specify what this Entity is 1000 going to specify for Frame Relay specific 1001 LDP Intialization Messages." 1002 ::= { mplsLdpEntityFrameRelayObjects 1 } 1004 mplsLdpEntityFrameRelayParmsEntry OBJECT-TYPE 1005 SYNTAX MplsLdpEntityFrameRelayParmsEntry 1006 MAX-ACCESS not-accessible 1007 STATUS current 1008 DESCRIPTION 1009 "An entry in this table represents the Frame Relay 1010 optional parameters associated with the LDP entity." 1011 INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex } 1012 ::= { mplsLdpEntityFrameRelayParmsTable 1 } 1014 MplsLdpEntityFrameRelayParmsEntry ::= SEQUENCE { 1015 mplsLdpEntityFrMergeCap INTEGER, 1016 mplsLdpEntityFrLabelRangeComponents Unsigned32, 1017 mplsLdpEntityFrVcDirectionality INTEGER, 1018 mplsLdpEntityFrParmsRowStatus RowStatus 1019 } 1021 mplsLdpEntityFrMergeCap OBJECT-TYPE 1022 SYNTAX INTEGER { 1023 notSupported(0), 1024 supported(1) 1025 } 1026 MAX-ACCESS read-create 1027 STATUS current 1028 DESCRIPTION 1029 "This represents whether or not Frame Relay merge capability 1030 is supported." 1031 ::= { mplsLdpEntityFrameRelayParmsEntry 1 } 1033 mplsLdpEntityFrLabelRangeComponents OBJECT-TYPE 1034 SYNTAX Unsigned32 (1..65535) 1035 MAX-ACCESS read-create 1036 STATUS current 1037 DESCRIPTION 1038 "Number of LabelRange Components in the Initialization 1039 message. This also represents the number of entries 1040 in the mplsLdpEntityConfFrLabelRangeTable which correspond 1041 to this entry." 1042 ::= { mplsLdpEntityFrameRelayParmsEntry 2 } 1044 mplsLdpEntityFrVcDirectionality OBJECT-TYPE 1045 SYNTAX INTEGER { 1046 bidirectional(0), 1047 unidirection(1) 1048 } 1049 MAX-ACCESS read-create 1050 STATUS current 1051 DESCRIPTION 1052 "If the value of this object is 'bidirectional(0)', then 1053 the LSR supports the use of a given DLCI as a label for 1054 both directions independently. If the value of this object 1055 is 'unidirectional(1)', then the LSR uses the given DLCI 1056 as a label in only one direction." 1057 ::= { mplsLdpEntityFrameRelayParmsEntry 3 } 1059 mplsLdpEntityFrParmsRowStatus OBJECT-TYPE 1060 SYNTAX RowStatus 1061 MAX-ACCESS read-create 1062 STATUS current 1063 DESCRIPTION 1064 "An object that allows entries in this table to 1065 be created and deleted using the 1066 RowStatus convention." 1067 ::= { mplsLdpEntityFrameRelayParmsEntry 4 } 1069 -- 1070 -- Frame Relay Label Range Components 1071 -- 1073 mplsLdpEntityConfFrLabelRangeTable OBJECT-TYPE 1074 SYNTAX SEQUENCE OF MplsLdpEntityConfFrLabelRangeEntry 1075 MAX-ACCESS not-accessible 1076 STATUS current 1077 DESCRIPTION 1078 "This table contains information about the 1079 Optional Parameters to specify what this Entity is 1080 going to specify for Frame Relay specific 1081 LDP Intialization Messages." 1082 ::= { mplsLdpEntityFrameRelayObjects 2 } 1084 mplsLdpEntityConfFrLabelRangeEntry OBJECT-TYPE 1085 SYNTAX MplsLdpEntityConfFrLabelRangeEntry 1086 MAX-ACCESS not-accessible 1087 STATUS current 1088 DESCRIPTION 1089 "An entry in this table represents the Frame Relay 1090 optional parameters associated with the LDP entity." 1091 INDEX { mplsLdpEntityLdpId, 1092 mplsLdpEntityIndex, 1093 mplsLdpConfFrMinimumDlci 1094 } 1095 ::= { mplsLdpEntityConfFrLabelRangeTable 1 } 1097 MplsLdpEntityConfFrLabelRangeEntry ::= SEQUENCE { 1098 mplsLdpConfFrMinimumDlci Integer32, 1099 mplsLdpConfFrMaximumDlci Integer32, 1100 mplsLdpConfFrLen INTEGER, 1101 mplsLdpConfFrRowStatus RowStatus 1102 } 1104 mplsLdpConfFrMinimumDlci OBJECT-TYPE 1105 SYNTAX Integer32(0..4194303) 1106 MAX-ACCESS not-accessible 1107 STATUS current 1108 DESCRIPTION 1109 "The lower bound which is supported. This value should 1110 be the same as that in the Frame Relay Label Range Component's 1111 Minimum DLCI field." 1112 ::= { mplsLdpEntityConfFrLabelRangeEntry 1 } 1114 mplsLdpConfFrMaximumDlci OBJECT-TYPE 1115 SYNTAX Integer32 (0..4194303) 1116 MAX-ACCESS read-create 1117 STATUS current 1118 DESCRIPTION 1119 "The upper bound which is supported. This value should 1120 be the same as that in the Frame Relay Label Range Component's 1121 Maximum DLCI field." 1122 ::= { mplsLdpEntityConfFrLabelRangeEntry 2 } 1124 mplsLdpConfFrLen OBJECT-TYPE 1125 SYNTAX INTEGER { 1126 tenDlciBits(0), 1127 seventeenDlciBits(1), 1128 twentyThreeDlciBits(2) 1129 } 1130 MAX-ACCESS read-create 1131 STATUS current 1132 DESCRIPTION 1133 "This object specifies the DLCI bits." 1134 ::= { mplsLdpEntityConfFrLabelRangeEntry 3 } 1136 mplsLdpConfFrRowStatus OBJECT-TYPE 1137 SYNTAX RowStatus 1138 MAX-ACCESS read-create 1139 STATUS current 1140 DESCRIPTION 1141 "An object that allows entries in this table to 1142 be created and deleted using the 1143 RowStatus convention. 1145 If the value of the object 1146 'mplsLdpEntityOptionalParameters' 1147 contains the value of 'frameReleaySessionParameters(3)' 1148 then 1149 there must be at least one corresponding entry in this 1150 table." 1151 ::= { mplsLdpEntityConfFrLabelRangeEntry 4 } 1153 -- 1154 -- The MPLS LDP Entity Statistics Table 1155 -- 1157 mplsLdpEntityStatsTable OBJECT-TYPE 1158 SYNTAX SEQUENCE OF MplsLdpEntityStatsEntry 1159 MAX-ACCESS not-accessible 1160 STATUS current 1161 DESCRIPTION 1162 "This table is a read-only table which augments 1163 the mplsLdpEntityTable. The purpose of this 1164 table is to keep statistical information about 1165 the LDP Entities on the LSR." 1166 ::= { mplsLdpEntityObjects 5 } 1168 mplsLdpEntityStatsEntry OBJECT-TYPE 1169 SYNTAX MplsLdpEntityStatsEntry 1170 MAX-ACCESS not-accessible 1171 STATUS current 1172 DESCRIPTION 1173 "A row in this table contains statistical information 1174 about an LDP Entity. Some counters contained in a 1175 row are for fatal errors received during a former 1176 LDP Session associated with this entry. For example, 1177 an Ldp Pdu received on a TCP connection for an 1178 LDP Session which contains a fatal error is counted 1179 here, because the session is terminated. 1180 If the error is NOT fatal (i.e. and the Session 1181 remains), then the error is counted in the 1182 mplsLdpSessionStatsEntry." 1183 AUGMENTS { mplsLdpEntityEntry } 1184 ::= { mplsLdpEntityStatsTable 1 } 1186 MplsLdpEntityStatsEntry ::= SEQUENCE { 1187 mplsLdpAttemptedSessions Counter32, 1188 mplsLdpSessionRejectedNoHelloErrors Counter32, 1189 mplsLdpSessionRejectedAdvertisementErrors Counter32, 1190 mplsLdpSessionRejectedMaxPduErrors Counter32, 1191 mplsLdpSessionRejectedLabelRangeErrors Counter32, 1192 mplsLdpBadLdpIdentifierErrors Counter32, 1193 mplsLdpBadPduLengthErrors Counter32, 1194 mplsLdpBadMessageLengthErrors Counter32, 1195 mplsLdpBadTlvLengthErrors Counter32, 1196 mplsLdpMalformedTlvValueErrors Counter32, 1197 mplsLdpKeepAliveTimerExpiredErrors Counter32, 1198 mplsLdpShutdownNotifReceived Counter32, 1199 mplsLdpShutdownNotifSent Counter32 1200 } 1202 mplsLdpAttemptedSessions OBJECT-TYPE 1203 SYNTAX Counter32 1204 MAX-ACCESS read-only 1205 STATUS current 1206 DESCRIPTION 1207 "A count of the total attempted sessions for 1208 this LDP Entity." 1209 ::= { mplsLdpEntityStatsEntry 1 } 1211 mplsLdpSessionRejectedNoHelloErrors OBJECT-TYPE 1212 SYNTAX Counter32 1213 MAX-ACCESS read-only 1214 STATUS current 1215 DESCRIPTION 1216 "A count of the Session Rejected/No Hello Error 1217 Notification Messages sent or received by 1218 this LDP Entity." 1219 ::= { mplsLdpEntityStatsEntry 2 } 1221 mplsLdpSessionRejectedAdvertisementErrors OBJECT-TYPE 1222 SYNTAX Counter32 1223 MAX-ACCESS read-only 1224 STATUS current 1225 DESCRIPTION 1226 "A count of the Session Rejected/Parameters 1227 Advertisement Mode Error Notification Messages sent 1228 or received by this LDP Entity." 1229 ::= { mplsLdpEntityStatsEntry 3 } 1231 mplsLdpSessionRejectedMaxPduErrors OBJECT-TYPE 1232 SYNTAX Counter32 1233 MAX-ACCESS read-only 1234 STATUS current 1235 DESCRIPTION 1236 "A count of the Session Rejected/Parameters 1237 Max Pdu Length Error Notification Messages sent 1238 or received by this LDP Entity." 1239 ::= { mplsLdpEntityStatsEntry 4 } 1241 mplsLdpSessionRejectedLabelRangeErrors OBJECT-TYPE 1242 SYNTAX Counter32 1243 MAX-ACCESS read-only 1244 STATUS current 1245 DESCRIPTION 1246 "A count of the Session Rejected/Parameters 1247 Label Range Notification Notification Messages sent 1248 or received by this LDP Entity." 1249 ::= { mplsLdpEntityStatsEntry 5 } 1251 mplsLdpBadLdpIdentifierErrors OBJECT-TYPE 1252 SYNTAX Counter32 1253 MAX-ACCESS read-only 1254 STATUS current 1255 DESCRIPTION 1256 "This object counts the number of Bad LDP Identifier Fatal 1257 Errors detected by the session(s) (past and present) associated 1258 with this LDP Entity." 1259 REFERENCE 1260 "LDP Specification, Section 3.5.1.2." 1261 ::= { mplsLdpEntityStatsEntry 6 } 1263 mplsLdpBadPduLengthErrors OBJECT-TYPE 1264 SYNTAX Counter32 1265 MAX-ACCESS read-only 1266 STATUS current 1267 DESCRIPTION 1268 "This object counts the number of Bad Pdu Length Fatal 1269 Errors detected by the session(s) (past and present) associated 1270 with this LDP Entity." 1271 REFERENCE 1272 "LDP Specification, Section 3.5.1.2." 1273 ::= { mplsLdpEntityStatsEntry 7 } 1275 mplsLdpBadMessageLengthErrors OBJECT-TYPE 1276 SYNTAX Counter32 1277 MAX-ACCESS read-only 1278 STATUS current 1279 DESCRIPTION 1280 "This object counts the number of Bad Message Length Fatal 1281 Errors detected by the session(s) (past and present) associated 1282 with this LDP Entity." 1283 REFERENCE 1284 "LDP Specification, Section 3.5.1.2." 1285 ::= { mplsLdpEntityStatsEntry 8 } 1287 mplsLdpBadTlvLengthErrors OBJECT-TYPE 1288 SYNTAX Counter32 1289 MAX-ACCESS read-only 1290 STATUS current 1291 DESCRIPTION 1292 "This object counts the number of Bad TLV Length Fatal 1293 Errors detected by the session(s) (past and present) associated 1294 with this LDP Entity." 1295 REFERENCE 1296 "LDP Specification, Section 3.5.1.2." 1297 ::= { mplsLdpEntityStatsEntry 9 } 1299 mplsLdpMalformedTlvValueErrors OBJECT-TYPE 1300 SYNTAX Counter32 1301 MAX-ACCESS read-only 1302 STATUS current 1303 DESCRIPTION 1304 "This object counts the number of Malformed TLV Value Fatal 1305 Errors detected by the session(s) (past and present) associated 1306 with this LDP Entity." 1307 REFERENCE 1308 "LDP Specification, Section 3.5.1.2." 1309 ::= { mplsLdpEntityStatsEntry 10 } 1311 mplsLdpKeepAliveTimerExpiredErrors OBJECT-TYPE 1312 SYNTAX Counter32 1313 MAX-ACCESS read-only 1314 STATUS current 1315 DESCRIPTION 1316 "This object counts the number of Session Keep Alive Timer 1317 Expired Errors detected by the session(s) (past and present) 1318 associated with this LDP Entity." 1320 REFERENCE 1321 "LDP Specification, Section 3.5.1.2." 1322 ::= { mplsLdpEntityStatsEntry 11 } 1324 mplsLdpShutdownNotifReceived OBJECT-TYPE 1325 SYNTAX Counter32 1326 MAX-ACCESS read-only 1327 STATUS current 1328 DESCRIPTION 1329 "This object counts the number of Shutdown Notfications 1330 received related to session(s) (past and present) associated 1331 with this LDP Entity." 1332 ::= { mplsLdpEntityStatsEntry 12 } 1334 mplsLdpShutdownNotifSent OBJECT-TYPE 1335 SYNTAX Counter32 1336 MAX-ACCESS read-only 1337 STATUS current 1338 DESCRIPTION 1339 "This object counts the number of Shutdown Notfications 1340 sent related to session(s) (past and present) associated 1341 with this LDP Entity." 1342 ::= { mplsLdpEntityStatsEntry 13 } 1344 -- 1345 -- The MPLS LDP Peer Table 1346 -- 1348 mplsLdpPeerObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 3 } 1350 mplsLdpPeerTable OBJECT-TYPE 1351 SYNTAX SEQUENCE OF MplsLdpPeerEntry 1352 MAX-ACCESS not-accessible 1353 STATUS current 1354 DESCRIPTION 1355 "Information about LDP peers which have been discovered 1356 by the LDP Entities that are managed by this agent." 1357 ::= { mplsLdpPeerObjects 1 } 1359 mplsLdpPeerEntry OBJECT-TYPE 1360 SYNTAX MplsLdpPeerEntry 1361 MAX-ACCESS not-accessible 1362 STATUS current 1363 DESCRIPTION 1364 "Information about a single Peer." 1365 INDEX { mplsLdpPeerLdpId, 1366 mplsLdpPeerIndex } 1367 ::= { mplsLdpPeerTable 1 } 1369 MplsLdpPeerEntry ::= SEQUENCE { 1370 mplsLdpPeerLdpId MplsLdpIdentifier, 1371 mplsLdpPeerIndex Unsigned32, 1372 mplsLdpPeerInternetworkAddrType AddressFamilyNumbers, 1373 mplsLdpPeerInternetworkAddr MplsLdpGenAddr, 1374 mplsLdpPeerLabelDistributionMethod INTEGER, 1375 mplsLdpPeerLoopDetectionForPV INTEGER, 1376 mplsLdpPeerPathVectorLimit Integer32 1377 } 1379 mplsLdpPeerLdpId OBJECT-TYPE 1380 SYNTAX MplsLdpIdentifier 1381 MAX-ACCESS not-accessible 1382 STATUS current 1383 DESCRIPTION 1384 "The LDP identifier of this LDP Peer." 1385 ::= { mplsLdpPeerEntry 1 } 1387 mplsLdpPeerIndex OBJECT-TYPE 1388 SYNTAX Unsigned32 (1..4294967295) 1389 MAX-ACCESS not-accessible 1390 STATUS current 1391 DESCRIPTION 1392 "An identifier for the LDP peer that is unique within the 1393 scope of table. This index is a secondary index which 1394 along with the mplsLdpPeerLdpId, uniquely identifies 1395 this entry." 1396 ::= { mplsLdpPeerEntry 2 } 1398 mplsLdpPeerInternetworkAddrType OBJECT-TYPE 1399 SYNTAX AddressFamilyNumbers 1400 MAX-ACCESS read-only 1401 STATUS current 1402 DESCRIPTION 1403 "The type of the internetwork layer address of this 1404 LDP peer. This object indicates how the value of 1405 mplsLdpPeerInternetworkAddr is to be interpreted." 1406 ::= { mplsLdpPeerEntry 3 } 1408 mplsLdpPeerInternetworkAddr OBJECT-TYPE 1409 SYNTAX MplsLdpGenAddr 1410 MAX-ACCESS read-only 1411 STATUS current 1412 DESCRIPTION 1413 "The value of the internetwork layer address of this LDP peer." 1414 ::= { mplsLdpPeerEntry 4 } 1416 mplsLdpPeerLabelDistributionMethod OBJECT-TYPE 1417 SYNTAX INTEGER { 1418 downstreamOnDemand(1), 1419 downstreamUnsolicited(2) 1420 } 1421 MAX-ACCESS read-only 1422 STATUS current 1423 DESCRIPTION 1424 "For any given LDP session, the method of 1425 label distribution must be specified." 1426 REFERENCE 1427 "draft-ietf-mpls-arch-06.txt [20]." 1428 ::= { mplsLdpPeerEntry 5 } 1430 mplsLdpPeerLoopDetectionForPV OBJECT-TYPE 1431 SYNTAX INTEGER { 1432 disabled(0), 1433 enabled(1) 1434 } 1435 MAX-ACCESS read-only 1436 STATUS current 1437 DESCRIPTION 1438 "An indication of whether loop detection based on path vectors 1439 is 1440 disabled or enabled for this Peer. 1442 If this object has a value of disabled(0), 1443 then loop detection is disabled. Otherwise, if this object has 1444 a value of enabled(1), then loop detection based on path 1445 vectors 1446 is enabled." 1447 ::= { mplsLdpPeerEntry 6 } 1449 mplsLdpPeerPathVectorLimit OBJECT-TYPE 1450 SYNTAX Integer32 (0..255) 1451 MAX-ACCESS read-only 1452 STATUS current 1453 DESCRIPTION 1454 "If the value of 'mplsLdpPeerLoopDetectionForPV' for this entry 1455 is 1456 'enabled(1)', the this object represents that Path Vector Limit 1457 for this peer. 1459 If the value of 'mplsLdpPeerLoopDetectionForPV' for this entry 1460 is 'disabled(0)', then this value should be 0 (zero)." 1461 ::= { mplsLdpPeerEntry 7 } 1463 -- 1464 -- The MPLS LDP Sessions Table 1465 -- 1467 mplsLdpSessionObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 4 } 1469 mplsLdpSessionTable OBJECT-TYPE 1470 SYNTAX SEQUENCE OF MplsLdpSessionEntry 1471 MAX-ACCESS not-accessible 1472 STATUS current 1473 DESCRIPTION 1474 "A table of Sessions between the LDP Entities and 1475 LDP Peers. Each row represents a single session." 1476 ::= { mplsLdpSessionObjects 1 } 1478 mplsLdpSessionEntry OBJECT-TYPE 1479 SYNTAX MplsLdpSessionEntry 1480 MAX-ACCESS not-accessible 1481 STATUS current 1482 DESCRIPTION 1483 "An entry in this table represents information on a 1484 single session between an LDP Entity and LDP Peer. 1485 The information contained in a row is read-only." 1486 INDEX { mplsLdpEntityLdpId, 1487 mplsLdpEntityIndex, 1488 mplsLdpPeerLdpId, 1489 mplsLdpPeerIndex, 1490 mplsLdpSessionIndex 1491 } 1492 ::= { mplsLdpSessionTable 1 } 1494 MplsLdpSessionEntry ::= SEQUENCE { 1495 mplsLdpSessionIndex Unsigned32, 1496 mplsLdpSessionState INTEGER, 1497 mplsLdpSessionProtocolVersion Integer32, 1498 mplsLdpSessionKeepAliveHoldTimeRemaining TimeInterval, 1499 mplsLdpSessionLabelAdvertisement INTEGER, 1500 mplsLdpSessionLoopDetectionForPV INTEGER, 1501 mplsLdpSessionPathVectorLimit Integer32, 1502 mplsLdpSessionMaxPduLength Integer32 1503 } 1505 mplsLdpSessionIndex OBJECT-TYPE 1506 SYNTAX Unsigned32 (1..4294967295) 1507 MAX-ACCESS not-accessible 1508 STATUS current 1509 DESCRIPTION 1510 "An unique identifier for this entry such that it 1511 identifies a specific LDP Session. The motivation for 1512 this index is so an NMS can distinguish when a session 1513 between a given Entity and Peer goes away and then is 1514 're-established'. This index value would change and 1515 thus indicate to the NMS that this is a different session." 1516 ::= { mplsLdpSessionEntry 1 } 1518 mplsLdpSessionState OBJECT-TYPE 1519 SYNTAX INTEGER { 1520 nonexistent(1), 1521 initialized(2), 1522 openrec(3), 1523 opensent(4), 1524 operational(5) 1525 } 1526 MAX-ACCESS read-only 1527 STATUS current 1528 DESCRIPTION 1529 "The current state of the session, all of the 1530 states 1 - 5 are based on the state machine for 1531 session negotiation behavior." 1532 ::= { mplsLdpSessionEntry 2 } 1534 mplsLdpSessionProtocolVersion OBJECT-TYPE 1535 SYNTAX Integer32(1..65535) 1536 MAX-ACCESS read-only 1537 STATUS current 1538 DESCRIPTION 1539 "The version of the LDP Protocol which 1540 this session is using." 1541 ::= { mplsLdpSessionEntry 3 } 1543 mplsLdpSessionKeepAliveHoldTimeRemaining OBJECT-TYPE 1544 SYNTAX TimeInterval 1545 MAX-ACCESS read-only 1546 STATUS current 1547 DESCRIPTION 1548 "The keep alive hold time remaining for this session." 1549 ::= { mplsLdpSessionEntry 4 } 1551 mplsLdpSessionLabelAdvertisement OBJECT-TYPE 1552 SYNTAX INTEGER { 1553 downStreamUnsolicited(0), 1554 downStreamOnDemand(1) 1555 } 1556 MAX-ACCESS read-only 1557 STATUS current 1558 DESCRIPTION 1559 "The label advertisement discipline used for this Session." 1560 ::= { mplsLdpSessionEntry 5 } 1562 mplsLdpSessionLoopDetectionForPV OBJECT-TYPE 1563 SYNTAX INTEGER { 1564 disabled(0), 1565 enabled(1) 1566 } 1567 MAX-ACCESS read-only 1568 STATUS current 1569 DESCRIPTION 1570 "An indication of whether loop detection based on path vectors 1571 is 1572 disabled or enabled for this session. 1574 If this object has a value of disabled(0), 1575 then loop detection is disabled. Otherwise, if this object has 1576 a value of enabled(1), then loop detection based on path 1577 vectors 1578 is enabled." 1579 ::= { mplsLdpSessionEntry 6 } 1581 mplsLdpSessionPathVectorLimit OBJECT-TYPE 1582 SYNTAX Integer32 (0..255) 1583 MAX-ACCESS read-only 1584 STATUS current 1585 DESCRIPTION 1586 "If the value of 'mplsLdpSessionLoopDetectionForPV' for this 1587 entry is 1588 'enabled(1)', the this object represents the Path Vector Limit 1589 for this session. 1591 If the value of 'mplsLdpSessionLoopDetectionForPV' for this 1592 entry 1593 is 'disabled(0)', then this value should be 0 (zero)." 1594 ::= { mplsLdpSessionEntry 7 } 1596 mplsLdpSessionMaxPduLength OBJECT-TYPE 1597 SYNTAX Integer32 (0..65535) 1598 MAX-ACCESS read-only 1599 STATUS current 1600 DESCRIPTION 1601 "The value of maximum allowable length for LDP PDUs for 1602 this session. This value may have been negotiated during 1603 the Session Initialization." 1604 ::= { mplsLdpSessionEntry 8 } 1606 -- 1607 -- MPLS LDP ATM Session Information 1608 -- 1610 mplsLdpAtmSessionTable OBJECT-TYPE 1611 SYNTAX SEQUENCE OF MplsLdpAtmSessionEntry 1612 MAX-ACCESS not-accessible 1613 STATUS current 1614 DESCRIPTION 1615 "A table of Sessions between the LDP Entities and 1616 LDP Peers using ATM as the underlying media. 1617 Each row represents a single session. 1619 NOTE: this table cannot use the 'AUGMENTS' 1620 clause because there is not necessarily a one-to-one 1621 mapping between this table and the mplsLdpSessionTable." 1622 ::= { mplsLdpSessionObjects 2 } 1624 mplsLdpAtmSessionEntry OBJECT-TYPE 1625 SYNTAX MplsLdpAtmSessionEntry 1626 MAX-ACCESS not-accessible 1627 STATUS current 1628 DESCRIPTION 1629 "An entry in this table represents information on a 1630 single session between an LDP Entity and LDP Peer. 1631 The information contained in a row is read-only." 1632 INDEX { mplsLdpEntityLdpId, 1633 mplsLdpEntityIndex, 1634 mplsLdpPeerLdpId, 1635 mplsLdpPeerIndex, 1636 mplsLdpSessionIndex, 1637 mplsLdpSessionAtmLabelRangeLowerBoundVpi, 1638 mplsLdpSessionAtmLabelRangeLowerBoundVci 1640 } 1641 ::= { mplsLdpAtmSessionTable 1 } 1643 MplsLdpAtmSessionEntry ::= SEQUENCE { 1644 mplsLdpSessionAtmLabelRangeLowerBoundVpi AtmVpIdentifier, 1645 mplsLdpSessionAtmLabelRangeLowerBoundVci AtmVcIdentifier, 1646 mplsLdpSessionAtmLabelRangeUpperBoundVpi AtmVpIdentifier, 1647 mplsLdpSessionAtmLabelRangeUpperBoundVci AtmVcIdentifier 1648 } 1650 mplsLdpSessionAtmLabelRangeLowerBoundVpi OBJECT-TYPE 1651 SYNTAX AtmVpIdentifier 1652 MAX-ACCESS not-accessible 1653 STATUS current 1654 DESCRIPTION 1655 "The minimum VPI number for this range." 1656 ::= { mplsLdpAtmSessionEntry 1 } 1658 mplsLdpSessionAtmLabelRangeLowerBoundVci OBJECT-TYPE 1659 SYNTAX AtmVcIdentifier 1660 MAX-ACCESS not-accessible 1661 STATUS current 1662 DESCRIPTION 1663 "The minimum VCI number for this range." 1664 ::= { mplsLdpAtmSessionEntry 2 } 1666 mplsLdpSessionAtmLabelRangeUpperBoundVpi OBJECT-TYPE 1667 SYNTAX AtmVpIdentifier 1668 MAX-ACCESS read-only 1669 STATUS current 1670 DESCRIPTION 1671 "The maximum VPI number for this range." 1672 ::= { mplsLdpAtmSessionEntry 3 } 1674 mplsLdpSessionAtmLabelRangeUpperBoundVci OBJECT-TYPE 1675 SYNTAX AtmVcIdentifier 1676 MAX-ACCESS read-only 1677 STATUS current 1678 DESCRIPTION 1679 "The maximum VCI number for this range." 1680 ::= { mplsLdpAtmSessionEntry 4 } 1682 -- 1683 -- MPLS LDP Frame Relay Session Information 1684 -- 1686 mplsLdpFrameRelaySessionTable OBJECT-TYPE 1687 SYNTAX SEQUENCE OF MplsLdpFrameRelaySessionEntry 1688 MAX-ACCESS not-accessible 1689 STATUS current 1690 DESCRIPTION 1691 "A table of Sessions between the LDP Entities and 1692 LDP Peers using Frame Relay as the underlying media. 1693 Each row represents a single session. 1695 NOTE: this table cannot use the 'AUGMENTS' 1696 clause because there is not necessarily a one-to-one 1697 mapping between this table and the mplsLdpSessionTable." 1698 ::= { mplsLdpSessionObjects 3 } 1700 mplsLdpFrameRelaySessionEntry OBJECT-TYPE 1701 SYNTAX MplsLdpFrameRelaySessionEntry 1702 MAX-ACCESS not-accessible 1703 STATUS current 1704 DESCRIPTION 1705 "An entry in this table represents information on a 1706 single session between an LDP Entity and LDP Peer. 1707 The information contained in a row is read-only." 1708 INDEX { mplsLdpEntityLdpId, 1709 mplsLdpEntityIndex, 1710 mplsLdpPeerLdpId, 1711 mplsLdpPeerIndex, 1712 mplsLdpSessionIndex, 1713 mplsLdpFrSessionMinDlci 1714 } 1715 ::= { mplsLdpFrameRelaySessionTable 1 } 1717 MplsLdpFrameRelaySessionEntry ::= SEQUENCE { 1718 mplsLdpFrSessionMinDlci Integer32, 1719 mplsLdpFrSessionMaxDlci Integer32, 1720 mplsLdpFrSessionLen INTEGER 1721 } 1723 mplsLdpFrSessionMinDlci OBJECT-TYPE 1724 SYNTAX Integer32(0..4194303) 1725 MAX-ACCESS not-accessible 1726 STATUS current 1727 DESCRIPTION 1728 "The lower bound of DLCIs which are supported." 1729 ::= { mplsLdpFrameRelaySessionEntry 1 } 1731 mplsLdpFrSessionMaxDlci OBJECT-TYPE 1732 SYNTAX Integer32 (0..4194303) 1733 MAX-ACCESS read-only 1734 STATUS current 1735 DESCRIPTION 1736 "The upper bound of DLCIs which are supported." 1737 ::= { mplsLdpFrameRelaySessionEntry 2 } 1739 mplsLdpFrSessionLen OBJECT-TYPE 1740 SYNTAX INTEGER { 1741 tenDlciBits(0), 1742 seventeenDlciBits(1), 1743 twentyThreeDlciBits(2) 1744 } 1745 MAX-ACCESS read-only 1746 STATUS current 1747 DESCRIPTION 1748 "This object specifies the DLCI bits." 1749 ::= { mplsLdpFrameRelaySessionEntry 3 } 1751 -- 1752 -- The MPLS LDP Session Statistics Table 1753 -- 1755 mplsLdpSessionStatsTable OBJECT-TYPE 1756 SYNTAX SEQUENCE OF MplsLdpSessionStatsEntry 1757 MAX-ACCESS not-accessible 1758 STATUS current 1759 DESCRIPTION 1760 "A table of Sessions between the LDP Entities and 1761 LDP Peers." 1762 ::= { mplsLdpSessionObjects 4 } 1764 mplsLdpSessionStatsEntry OBJECT-TYPE 1765 SYNTAX MplsLdpSessionStatsEntry 1766 MAX-ACCESS not-accessible 1767 STATUS current 1768 DESCRIPTION 1769 "An entry in this table represents statistical information on a 1770 single session between an LDP Entity and LDP Peer." 1771 AUGMENTS { mplsLdpSessionEntry } 1772 ::= { mplsLdpSessionStatsTable 1 } 1774 MplsLdpSessionStatsEntry ::= SEQUENCE { 1775 mplsLdpSessionStatsUnknownMessageTypeErrors Counter32, 1776 mplsLdpSessionStatsUnknownTlvErrors Counter32 1777 } 1779 mplsLdpSessionStatsUnknownMessageTypeErrors OBJECT-TYPE 1780 SYNTAX Counter32 1781 MAX-ACCESS read-only 1782 STATUS current 1783 DESCRIPTION 1784 "This object counts the number of Unknown Message Type 1785 Errors detected during this session." 1786 ::= { mplsLdpSessionStatsEntry 1 } 1788 mplsLdpSessionStatsUnknownTlvErrors OBJECT-TYPE 1789 SYNTAX Counter32 1790 MAX-ACCESS read-only 1791 STATUS current 1792 DESCRIPTION 1793 "This object counts the number of Unknown TLV Errors 1794 detected during this session." 1795 ::= { mplsLdpSessionStatsEntry 2 } 1797 -- 1798 -- Address Message/Address Withdraw Message Information 1799 -- 1800 -- This information is associated with a specific Session 1801 -- because Label Address Messages are sent after session 1802 -- initialization has taken place. 1803 -- 1805 mplsLdpSessionPeerAddressTable OBJECT-TYPE 1806 SYNTAX SEQUENCE OF MplsLdpSessionPeerAddressEntry 1807 MAX-ACCESS not-accessible 1808 STATUS current 1809 DESCRIPTION 1810 "This table 'extends' the mplsLdpSessionTable. 1811 This table is used to store Label Address Information 1812 from Label Address Message received by this LSR from 1813 Peers. This table is read-only and should be updated 1814 when Label Withdraw Address Messages are received, i.e. 1815 Rows should be deleted as apropriate. 1817 NOTE: since more than one address may be contained 1818 in a Label Address Message, this table 'extends', 1819 rather than 'AUGMENTS' the mplsLdpSessionTable's 1820 information." 1821 ::= { mplsLdpSessionObjects 5 } 1823 mplsLdpSessionPeerAddressEntry OBJECT-TYPE 1824 SYNTAX MplsLdpSessionPeerAddressEntry 1825 MAX-ACCESS not-accessible 1826 STATUS current 1827 DESCRIPTION 1828 "An entry in this table represents information on 1829 session's for a single next hop address which was 1830 advertised in an Address Message from the LDP peer. 1831 The information contained in a row is read-only." 1832 INDEX { mplsLdpEntityLdpId, 1833 mplsLdpEntityIndex, 1834 mplsLdpPeerLdpId, 1835 mplsLdpPeerIndex, 1836 mplsLdpSessionIndex 1837 } 1838 ::= { mplsLdpSessionPeerAddressTable 1 } 1840 MplsLdpSessionPeerAddressEntry ::= SEQUENCE { 1841 mplsLdpSessionPeerNextHopAddressType AddressFamilyNumbers, 1842 mplsLdpSessionPeerNextHopAddress MplsLdpGenAddr 1843 } 1845 mplsLdpSessionPeerNextHopAddressType OBJECT-TYPE 1846 SYNTAX AddressFamilyNumbers 1847 MAX-ACCESS read-only 1848 STATUS current 1849 DESCRIPTION 1850 "The internetwork layer address type of this Next Hop 1851 Address as specified in the Label Address Message associated 1852 with this Session. The value of this object indicates 1853 how to interpret the value of 1854 mplsLdpSessionPeerNextHopAddress." 1855 ::= { mplsLdpSessionPeerAddressEntry 1 } 1857 mplsLdpSessionPeerNextHopAddress OBJECT-TYPE 1858 SYNTAX MplsLdpGenAddr 1859 MAX-ACCESS read-only 1860 STATUS current 1861 DESCRIPTION 1862 "The value of the next hop address." 1863 REFERENCE 1864 "LDP Specification [18] defines only IPv4 for LDP Protocol 1865 Version 1, see section 3.4.3." 1866 ::= { mplsLdpSessionPeerAddressEntry 2 } 1868 -- 1869 -- The MPLS LDP Hello Adjacency Table 1870 -- 1872 mplsLdpHelloAdjacencyObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 5 } 1874 mplsLdpHelloAdjacencyTable OBJECT-TYPE 1875 SYNTAX SEQUENCE OF MplsLdpHelloAdjacencyEntry 1876 MAX-ACCESS not-accessible 1877 STATUS current 1878 DESCRIPTION 1879 "A table of Hello Adjacencies for Sessions." 1880 ::= { mplsLdpHelloAdjacencyObjects 1 } 1882 mplsLdpHelloAdjacencyEntry OBJECT-TYPE 1883 SYNTAX MplsLdpHelloAdjacencyEntry 1884 MAX-ACCESS not-accessible 1885 STATUS current 1886 DESCRIPTION 1887 "Each row represents a single LDP Hello Adjacency. 1888 An LDP Session can have one or more Hello adjacencies." 1889 INDEX { mplsLdpEntityLdpId, 1890 mplsLdpEntityIndex, 1891 mplsLdpPeerLdpId, 1892 mplsLdpPeerIndex, 1893 mplsLdpHelloAdjacencyIndex } 1894 ::= { mplsLdpHelloAdjacencyTable 1 } 1896 MplsLdpHelloAdjacencyEntry ::= SEQUENCE { 1897 mplsLdpHelloAdjacencyIndex Unsigned32, 1898 mplsLdpHelloAdjacencyHoldTimeRemaining TimeInterval, 1899 mplsLdpHelloAdjacencyType INTEGER 1900 } 1902 mplsLdpHelloAdjacencyIndex OBJECT-TYPE 1903 SYNTAX Unsigned32 (1..4294967295) 1904 MAX-ACCESS not-accessible 1905 STATUS current 1906 DESCRIPTION 1907 "An identifier for this specific adjacency." 1908 ::= { mplsLdpHelloAdjacencyEntry 1 } 1910 mplsLdpHelloAdjacencyHoldTimeRemaining OBJECT-TYPE 1911 SYNTAX TimeInterval 1912 MAX-ACCESS read-only 1913 STATUS current 1914 DESCRIPTION 1915 "The time remaining for this Hello Adjacency. 1916 This interval will change when the 'next' 1917 Hello message which corresponds to this 1918 Hello Adjacency is received." 1919 ::= { mplsLdpHelloAdjacencyEntry 2 } 1921 mplsLdpHelloAdjacencyType OBJECT-TYPE 1922 SYNTAX INTEGER { 1923 link(1), 1924 targeted(2) 1925 } 1926 MAX-ACCESS read-only 1927 STATUS current 1928 DESCRIPTION 1929 "This adjacency is the result of a 'link' 1930 hello if the value of this object is link(1). 1931 Otherwise, it is a result of a 'targeted' 1932 hello, targeted(2)." 1933 ::= { mplsLdpHelloAdjacencyEntry 3 } 1935 -- 1936 -- MPLS LDP LIB Table 1937 -- 1939 mplsLdpLibObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 6 } 1941 mplsLdpLibTable OBJECT-TYPE 1942 SYNTAX SEQUENCE OF MplsLdpLibEntry 1943 MAX-ACCESS not-accessible 1944 STATUS current 1945 DESCRIPTION 1946 "This table represents LIB (Label Information Base) 1947 Information. The table is read-only." 1948 ::= { mplsLdpLibObjects 1 } 1950 mplsLdpLibEntry OBJECT-TYPE 1951 SYNTAX MplsLdpLibEntry 1952 MAX-ACCESS not-accessible 1953 STATUS current 1954 DESCRIPTION 1955 "Each row represents a single LDP LIB entry." 1956 INDEX { mplsLdpLibLspId } 1957 ::= { mplsLdpLibTable 1 } 1959 MplsLdpLibEntry ::= SEQUENCE { 1960 mplsLdpLibLspId Unsigned32, 1961 mplsLdpLibLabelInIfIndex InterfaceIndex, 1962 mplsLdpLibLabelOutIfIndex InterfaceIndex, 1963 mplsLdpLibLabelType MplsLdpLabelTypes, 1964 mplsLdpLibInLabel MplsLdpGenAddr, 1965 mplsLdpLibOutLabel MplsLdpGenAddr 1966 } 1967 mplsLdpLibLspId OBJECT-TYPE 1968 SYNTAX Unsigned32 (1..4294967295) 1969 MAX-ACCESS not-accessible 1970 STATUS current 1971 DESCRIPTION 1972 "This number is used to uniquely identify this row, since this 1973 row is associated with a specific LSP, it may also be used 1974 to describe a unique number for an LSP. This number is used 1975 in the mplsLdpFecTable to identify which FECs or FEC is 1976 associated with this LIB entry." 1977 ::= { mplsLdpLibEntry 1 } 1979 mplsLdpLibLabelInIfIndex OBJECT-TYPE 1980 SYNTAX InterfaceIndex 1981 MAX-ACCESS read-only 1982 STATUS current 1983 DESCRIPTION 1984 "The ifIndex of the 'mplsLdpInLabel'." 1985 ::= { mplsLdpLibEntry 2 } 1987 mplsLdpLibLabelOutIfIndex OBJECT-TYPE 1988 SYNTAX InterfaceIndex 1989 MAX-ACCESS read-only 1990 STATUS current 1991 DESCRIPTION 1992 "The ifIndex of the 'mplsLdpOutLabel'." 1993 ::= { mplsLdpLibEntry 3 } 1995 mplsLdpLibLabelType OBJECT-TYPE 1996 SYNTAX MplsLdpLabelTypes 1997 MAX-ACCESS read-only 1998 STATUS current 1999 DESCRIPTION 2000 "The Layer 2 Label Type for 'mplsLdpInLabel' and 2001 'mplsLdpOutLabel'." 2002 ::= { mplsLdpLibEntry 4 } 2004 mplsLdpLibInLabel OBJECT-TYPE 2005 SYNTAX MplsLdpGenAddr 2006 MAX-ACCESS read-only 2007 STATUS current 2008 DESCRIPTION 2009 "The incoming label of this LSP." 2010 ::= { mplsLdpLibEntry 5 } 2012 mplsLdpLibOutLabel OBJECT-TYPE 2013 SYNTAX MplsLdpGenAddr 2014 MAX-ACCESS read-only 2015 STATUS current 2016 DESCRIPTION 2017 "The outgoing label of this LSP." 2018 ::= { mplsLdpLibEntry 6 } 2020 -- 2021 -- Mpls Ldp FEC Table 2022 -- 2024 mplsLdpFecTable OBJECT-TYPE 2025 SYNTAX SEQUENCE OF MplsLdpFecEntry 2026 MAX-ACCESS not-accessible 2027 STATUS current 2028 DESCRIPTION 2029 "This table represents the FEC 2030 (Forwarding Equivalence Class) 2031 Information associated with an LSP. 2032 The table is read-only." 2033 ::= { mplsLdpLibObjects 2 } 2035 mplsLdpFecEntry OBJECT-TYPE 2036 SYNTAX MplsLdpFecEntry 2037 MAX-ACCESS not-accessible 2038 STATUS current 2039 DESCRIPTION 2040 "Each row represents a single FEC Element." 2041 INDEX { mplsLdpFecType, 2042 mplsLdpFecAddressFamily, 2043 mplsLdpFecAddressLength, 2044 mplsLdpFecAddress } 2045 ::= { mplsLdpFecTable 1 } 2047 MplsLdpFecEntry ::= SEQUENCE { 2048 mplsLdpFecType INTEGER, 2049 mplsLdpFecAddressFamily AddressFamilyNumbers, 2050 mplsLdpFecAddressLength Integer32(0..255), 2051 mplsLdpFecAddress MplsLdpGenAddr, 2052 mplsLdpFecLspId Unsigned32 2053 } 2055 mplsLdpFecType OBJECT-TYPE 2056 SYNTAX INTEGER { 2057 prefix(1), 2058 hostAddress(2) 2059 } 2060 MAX-ACCESS not-accessible 2061 STATUS current 2062 DESCRIPTION 2063 "The type of the FEC. If the value of this object 2064 is 'prefix(1)' then the FEC type described by this 2065 row is for address prefixes. 2067 If the value of this object is 'hostAddress(2)' then 2068 the FEC type described by this row is a host address." 2069 ::= { mplsLdpFecEntry 1 } 2071 mplsLdpFecAddressFamily OBJECT-TYPE 2072 SYNTAX AddressFamilyNumbers 2073 MAX-ACCESS not-accessible 2074 STATUS current 2075 DESCRIPTION 2076 "The value of this object is from the Address Family 2077 Numbers." 2078 ::= { mplsLdpFecEntry 2 } 2080 mplsLdpFecAddressLength OBJECT-TYPE 2081 SYNTAX Integer32(0..255) 2082 MAX-ACCESS not-accessible 2083 STATUS current 2084 DESCRIPTION 2085 "If the value of 'mplsLdpFecType' is 'prefix(1)' 2086 then the value of this object is the length in 2087 bits of the address prefix represented by 2088 'mplsLdpFecAddress', or if the length is zero then 2089 this is a special value which indicates that the 2090 prefix matches all addresses. In this case the 2091 prefix is also zero (i.e. 'mplsLdpFecAddress' will 2092 have the value of zero.)" 2093 ::= { mplsLdpFecEntry 3 } 2095 mplsLdpFecAddress OBJECT-TYPE 2096 SYNTAX MplsLdpGenAddr 2097 MAX-ACCESS not-accessible 2098 STATUS current 2099 DESCRIPTION 2100 "If the value of 'mplsLdpFecType' is 'prefix(1)' 2101 then the value of this object is the address prefix. 2102 If the value of the 'mplsLdpFecAddressLength' 2103 is object is zero, then this object should also be 2104 zero." 2105 ::= { mplsLdpFecEntry 4 } 2107 mplsLdpFecLspId OBJECT-TYPE 2108 SYNTAX Unsigned32 (1..4294967295) 2109 MAX-ACCESS read-only 2110 STATUS current 2111 DESCRIPTION 2112 "This number represents the LSP which is related to 2113 this FEC. The value of this object should correspond 2114 to an entry in the MplsLdpLibTable, as denoted by 2115 the 'mplsLdpLibLspId' object. In other words, this 2116 object and the 'mplsLdpLibLspId' should have the same 2117 value." 2118 ::= { mplsLdpFecEntry 5 } 2120 --- 2121 --- Notifications 2122 --- 2124 mplsLdpNotificationPrefix OBJECT IDENTIFIER ::= 2125 { mplsLdpNotifications 0 } 2127 mplsLdpFailedInitSessionThresholdExceeded NOTIFICATION-TYPE 2128 OBJECTS { 2129 mplsLdpEntityFailedInitSessionThreshold 2130 } 2131 STATUS current 2132 DESCRIPTION 2133 "This notification is generated whenever the value 2134 of mplsLdpEntityFailedInitSessionThreshold is 2135 exceeded." 2136 ::= { mplsLdpNotificationPrefix 1 } 2138 mplsLdpPathVectorLimitMismatch NOTIFICATION-TYPE 2139 OBJECTS { 2140 mplsLdpPeerPathVectorLimit, 2141 mplsLdpSessionPathVectorLimit 2142 } 2143 STATUS current 2144 DESCRIPTION 2145 "This notification is generated when the value 2146 of mplsLdpSessionPathVectorLimit does NOT match 2147 the value of the mplsLdpPeerPathVectorLimit for 2148 the corresponding mplsLdpPeerEntry." 2149 REFERENCE 2150 "LDP Specification, Section 3.5.3." 2151 ::= { mplsLdpNotificationPrefix 2 } 2153 --******************************************************************** 2154 -- Module Conformance Statement 2155 --******************************************************************** 2157 mplsLdpGroups 2158 OBJECT IDENTIFIER ::= { mplsLdpConformance 1 } 2160 mplsLdpCompliances 2161 OBJECT IDENTIFIER ::= { mplsLdpConformance 2 } 2163 -- 2164 -- Compliance Statements 2165 -- 2167 mplsLdpModuleCompliance MODULE-COMPLIANCE 2168 STATUS current 2169 DESCRIPTION 2170 "The basic implentation requirements for agents that support 2171 the MPLS LDP MIB." 2172 MODULE -- this module 2173 MANDATORY-GROUPS { mplsLdpGeneralGroup, 2174 mplsLdpNotificationsGroup 2175 } 2176 GROUP mplsLdpAtmGroup 2177 DESCRIPTION 2178 "This group must be supported if ATM is used in the 2179 MPLS LDP implementation." 2181 GROUP mplsLdpFrameRelayGroup 2182 DESCRIPTION 2183 "This group must be supported if Frame Relay is used in the 2184 MPLS LDP implementation." 2185 ::= { mplsLdpCompliances 1 } 2187 -- units of conformance 2189 mplsLdpGeneralGroup OBJECT-GROUP 2190 OBJECTS { 2191 mplsLdpLsrId, 2192 mplsLdpLsrLabelRetentionMode, 2193 mplsLdpLsrLoopDetectionCapable, 2194 mplsLdpEntityIndexNext, 2195 mplsLdpEntityProtocolVersion, 2196 mplsLdpEntityAdminStatus, 2197 mplsLdpEntityOperStatus, 2198 mplsLdpEntityWellKnownDiscoveryPort, 2199 mplsLdpEntityMtu, 2200 mplsLdpEntityKeepAliveHoldTimer, 2201 mplsLdpEntityHelloHoldTimer, 2202 mplsLdpEntityFailedInitSessionThreshold, 2203 mplsLdpEntityLabelDistributionMethod, 2204 mplsLdpEntityTargetedPeer, 2205 mplsLdpEntityTargetedPeerAddrType, 2206 mplsLdpEntityTargetedPeerAddr, 2207 mplsLdpEntityOptionalParameters, 2208 mplsLdpEntityRowStatus, 2209 mplsLdpAttemptedSessions, 2210 mplsLdpSessionRejectedNoHelloErrors, 2211 mplsLdpSessionRejectedAdvertisementErrors, 2212 mplsLdpSessionRejectedMaxPduErrors, 2213 mplsLdpSessionRejectedLabelRangeErrors, 2214 mplsLdpBadLdpIdentifierErrors, 2215 mplsLdpBadPduLengthErrors, 2216 mplsLdpBadMessageLengthErrors, 2217 mplsLdpBadTlvLengthErrors, 2218 mplsLdpMalformedTlvValueErrors, 2219 mplsLdpKeepAliveTimerExpiredErrors, 2220 mplsLdpShutdownNotifReceived, 2221 mplsLdpShutdownNotifSent, 2222 mplsLdpPeerInternetworkAddrType, 2223 mplsLdpPeerInternetworkAddr, 2224 mplsLdpPeerLabelDistributionMethod, 2225 mplsLdpPeerLoopDetectionForPV, 2226 mplsLdpPeerPathVectorLimit, 2227 mplsLdpSessionState, 2228 mplsLdpSessionProtocolVersion, 2229 mplsLdpSessionKeepAliveHoldTimeRemaining, 2230 mplsLdpSessionLabelAdvertisement, 2231 mplsLdpSessionLoopDetectionForPV, 2232 mplsLdpSessionPathVectorLimit, 2233 mplsLdpSessionMaxPduLength, 2234 mplsLdpSessionStatsUnknownMessageTypeErrors, 2235 mplsLdpSessionStatsUnknownTlvErrors, 2236 mplsLdpSessionPeerNextHopAddressType, 2237 mplsLdpSessionPeerNextHopAddress, 2238 mplsLdpHelloAdjacencyHoldTimeRemaining, 2239 mplsLdpHelloAdjacencyType, 2240 mplsLdpLibLabelInIfIndex, 2241 mplsLdpLibLabelOutIfIndex, 2242 mplsLdpLibLabelType, 2243 mplsLdpLibInLabel, 2244 mplsLdpLibOutLabel, 2245 mplsLdpFecLspId 2247 } 2248 STATUS current 2249 DESCRIPTION 2250 "Objects that apply to all MPLS LDP implementations." 2251 ::= { mplsLdpGroups 1 } 2253 mplsLdpAtmGroup OBJECT-GROUP 2254 OBJECTS { 2255 mplsLdpEntityAtmMergeCap, 2256 mplsLdpEntityAtmLabelRangeComponents, 2257 mplsLdpEntityAtmVcDirectionality, 2258 mplsLdpEntityAtmLsrConnectivity, 2259 mplsLdpEntityDefaultControlVpi, 2260 mplsLdpEntityDefaultControlVci, 2261 mplsLdpEntityUnlabTrafVpi, 2262 mplsLdpEntityUnlabTrafVci, 2263 mplsLdpEntityAtmRowStatus, 2264 mplsLdpEntityConfAtmLabelRangeMaximumVpi, 2265 mplsLdpEntityConfAtmLabelRangeMaximumVci, 2266 mplsLdpEntityConfAtmLabelRangeRowStatus, 2267 mplsLdpSessionAtmLabelRangeUpperBoundVpi, 2268 mplsLdpSessionAtmLabelRangeUpperBoundVci 2270 } 2271 STATUS current 2272 DESCRIPTION 2273 "Objects that apply to all MPLS LDP implementations over ATM." 2274 ::= { mplsLdpGroups 2 } 2276 mplsLdpFrameRelayGroup OBJECT-GROUP 2277 OBJECTS { 2278 mplsLdpEntityFrMergeCap, 2279 mplsLdpEntityFrLabelRangeComponents, 2280 mplsLdpEntityFrVcDirectionality, 2281 mplsLdpEntityFrParmsRowStatus, 2282 mplsLdpConfFrMaximumDlci, 2283 mplsLdpConfFrLen, 2284 mplsLdpConfFrRowStatus, 2285 mplsLdpFrSessionMaxDlci, 2286 mplsLdpFrSessionLen 2287 } 2288 STATUS current 2289 DESCRIPTION 2290 "Objects that apply to all MPLS LDP implementations over 2291 Frame Relay." 2292 ::= { mplsLdpGroups 3 } 2294 mplsLdpNotificationsGroup NOTIFICATION-GROUP 2295 NOTIFICATIONS { mplsLdpFailedInitSessionThresholdExceeded, 2296 mplsLdpPathVectorLimitMismatch 2297 } 2298 STATUS current 2299 DESCRIPTION 2300 "The notification(s) which an MPLS LDP implemention 2301 is required to implement." 2302 ::= { mplsLdpGroups 4 } 2304 END 2306 5. Revision History 2308 This section should be removed when this document is published as an 2309 RFC. 2311 5.1. Changes from 2313 Added Scalar Objects: mplsLdpLsrLoopDetectionPresent, and 2314 mplsLdpEntityIndexNext. 2316 Added the following objects to the mplsLdpEntityTable: 2317 mplsLdpEntityProtocolVersion, mplsLdpEntityAdminStatus, 2318 mplsLdpEntityOperStatus, mplsLdpEntityTargetedPeer, 2319 mplsLdpEntityTargetedPeerAddrType, mplsLdpEntityTargetedPeerAddr, and 2320 mplsLdpEntityHelloHoldTimer. 2322 Changed the description of the mplsLdpEntityAtmParmsTable and added 2323 the following objects to this table: 2324 mplsLdpEntityAtmLsrConnectivity, mplsLdpEntityDefaultControlVpi, 2325 mplsLdpEntityDefaultControlVci, mplsLdpEntityUnlabTrafVpi, and 2326 mplsLdpEntityUnlabTrafVci. NOTE: the last four objects were in 2327 Version 01 of the MIB but were mistakenly omitted from Version 02. 2328 Now, they are back. 2330 Changed the indexing of the mplsLdpEntityConfAtmLabelRangeTable to 2331 include the minimum VPI/VCI. This is to ensure that indices in this 2332 table are unique. 2334 Changed the indexing of the mplsLdpEntityConfFrLabelRangeTable, to 2335 include the minimum DLCI value. This is to ensure that indices in 2336 this table are unique. 2338 Added [32] to Reference Section. 2340 5.2. Changes from 2342 The MIB was updated to correspond to draft-ietf-mpls-ldp-06.txt of 2343 the LDP Specification [18]. 2345 The front section was updated. 2347 The MIB was made to be less ATM-centric. Essentially, the ATM 2348 specific objects where removed from the tables and placed in ATM 2349 specific Tables. A "type" was added to the "base" tables and a row 2350 is to be created in the ATM/FR/etc. "type" table. Apropos 2351 compliance statements were added to reflect the separation of ATM and 2352 Frame Relay objects into their respective tables. 2354 Objects for Loop Detection were removed from describing the LDP 2355 implementation (i.e. the scalars were removed) and Loop Dection 2356 objects were added to the Session Table. (Although as the LDP 2357 Specification indicates loop detection should be for an LSR within a 2358 domain.) 2360 The following tables were added: mplsLdpEntityAtmParmsTable, 2361 mplsLdpEntityConfAtmLabelRangeTable, mplsLdpFrameRelayParmsTable, 2362 mplsLdpConfFrLabelRangeTable, mplsLdpAtmSessionTable, 2363 mpslLdpFrameRelaySessionTable, mplsLdpSessionPeerAddressTable, 2364 mplsLdpLibTable, and the mplsLdpFecTable. 2366 The following notifications were added: notification for Session 2367 removal. 2369 The following objects were removed from the Session Table: 2370 mplsLdpSessionRole was removed (this can be determined by comparing 2371 LSR Ids and does not need to be explicitely in the MIB.) ATM 2372 specific objects (mplsLdpSessionAtmLabelRangeLowerBoundVpi 2373 mplsLdpSessionAtmLabelRangeLowerBoundVci, 2374 mplsLdpSessionAtmLabelRangeUpperBoundVpi 2375 mplsLdpSessionAtmLabelRangeUpperBoundVci) were removed and put into a 2376 separate table. Frame Relay objects were added in a separate table. 2378 Hello Adjacency Table was updated. 2380 The objects, mplsLdpSessionRejectedParamErrors, 2381 mplsLdpSessionRejectedNoHelloErrors, mplsLdpBadLdpIdentifierErrors, 2382 mplsLdpBadPduLengthErrors, mplsLdpBadMessageLengthErrors, 2383 mplsLdpBadTlvLengthErrors, mplsLdpMalformedTlvValueErrors, 2384 mplsLdpKeepAliveTimerExpiredErrors, mplsLdpShutdownNotifReceived, and 2385 mplsLdpShutdownNotifSent were added to the mplsLdpEntityStatsTable. 2387 The mplsLdpSessionStatsTable was added to count statics based on a 2388 per Session basis. 2390 The mplLdpPeerConfAtmLabelRangeTable has been removed. There is no 2391 need to configure information for a Peer. All information for a peer 2392 is learned, thus peer information is read-only. 2394 (Editorial) References were updated to reflect the documents which 2395 this version was based on. 2397 5.3. Changes from 2399 Textual conventions were added for the LSR Identifier and the LDP 2400 Identifier. 2402 Top-level mib structure was added. The LDP MIB falls under a proposed 2403 hierarchy of mpls.mplsProtocols. 2405 The mib hierarchy within the LDP MIB was also changed. A new branch, 2406 under mpls.mplsProtocols.mplsLdpMIB.mplsLdpObjects was added. This 2407 branch is mplsLdpLsrObjects. Currently, this contains several new 2408 scalar objects: mplsLdpLsrID, mplsLdpLsrLoopDetectionPresent, 2409 mplsLdpLsrLoopDetectinAdminStatus, mplsLdpLsrPathVectorLimit, 2410 mplsLdpLsrHopCountLimit, mplsLdpLsrLoopPreventionPresent, 2411 mplsLdpLsrLoopPreventionAdminStatus, and 2412 mplsLdpLsrLabelRetentionMode. 2414 mplsLdpEntityTable is now indexed by mplsLdpEntityIdentifier, which 2415 is the LDP Identifier used in Session establishment. 2416 mplsLdpEntityLoopDetection and mplsLdpEntityLoopPrevention objects 2417 were removed from this table. 2419 The following objects were added to the mplsLdpEntityTable: 2420 mplsLdpEntityLabelSpaceType, mplsLdpEntityUnlabTrafVpi, 2421 mplsLdpEntityUnlabTrafVci, mplsLdpEntityMergeCapability, 2422 mplsLdpEntityVcDirectionality, and 2423 mplsLdpEntityLabelDistributionMethod. 2425 The following objects were added to the mplsLdpPeerEntityTable: 2426 mplsLdpPeerLabelDistributionMethod. 2428 The following object was removed from the mplsLdpEntityStatsTable: 2429 mplsLdpEntityEstablishedSessions. 2431 References were added and revised. 2433 6. TO DO List 2435 This section should be removed when this document is published as an 2436 RFC. This section outlines the next areas the authors intend to 2437 address in subsequent revisions. 2439 o Remove the following sections prior to final publication: IANA 2440 Considerations Section, Revisions Section and this (TO DO List) 2441 Section. 2443 o Updates as suggested by review of working group. 2445 7. Acknowledgments 2447 The authors would like to thank the following people: Leigh 2448 McLellan, Geetha Brown, Geping Chen and Charlan Zhou from Nortel 2449 Networks, and Zoltan Takacs and Bo Augustsson from Ericsson. 2451 8. References 2453 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 2454 for Describing SNMP Management Frameworks", RFC 2571, April 2455 1999 2457 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 2458 of Management Information for TCP/IP-based Internets", STD 2459 16, RFC 1155, May 1990 2461 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 2462 16, RFC 1212, March 1991 2464 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 2465 SNMP", RFC 1215, March 1991 2467 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2468 Rose, M., and S. Waldbusser, "Structure of Management 2469 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999 2471 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2472 Rose, M., and S. Waldbusser, "Textual Conventions for 2473 SMIv2", STD 58, RFC 2579, April 1999 2475 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2476 Rose, M., and S. Waldbusser, "Conformance Statements for 2477 SMIv2", STD 58, RFC 2580, April 1999 2479 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 2480 Network Management Protocol", STD 15, RFC 1157, May 1990. 2482 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2483 "Introduction to Community-based SNMPv2", RFC 1901, January 2484 1996. 2486 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2487 "Transport Mappings for Version 2 of the Simple Network 2488 Management Protocol (SNMPv2)", RFC 1906, January 1996. 2490 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 2491 Processing and Dispatching for the Simple Network Management 2492 Protocol (SNMP)", RFC 2572, April 1999 2494 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 2495 (USM) for version 3 of the Simple Network Management 2496 Protocol (SNMPv3)", RFC 2574, April 1999 2498 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2499 "Protocol Operations for Version 2 of the Simple Network 2500 Management Protocol (SNMPv2)", RFC 1905, January 1996. 2502 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 2503 RFC 2573, April 1999 2505 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 2506 Access Control Model (VACM) for the Simple Network 2507 Management Protocol (SNMP)", RFC 2575, April 1999 2509 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 2510 "Introduction to Version 3 of the Internet-standard Network 2511 Management Framework", RFC 2570, April 1999 2513 [17] Narten, T., and H. Alvestrand, "Guidelines for Writing an IANA 2514 Considerations Section in RFCs.", RFC 2434, IBM, Maxware, October 2515 1998 2517 [18] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and Thomas, 2518 B., "LDP Specification.", draft-ietf-mpls-ldp-06.txt, Nortel 2519 Networks, Ennovate Networks, IBM, Nortel Networks, Cisco Systems 2520 October 1999 2522 [19] Callon, R., Doolan, P., Feldman, N., Fredette, A., Swallow, G., and 2523 A. Viswanathan, "A Framework for Multiprotocol Label Switching", 2524 draft-ietf-mpls-framework-04.txt, IronBridge Networks, Ennovate 2525 Networks, IBM, Nortel Networks, Cisco Systems, July 1999. 2527 [20] Rosen, E., Viswananthan, A., and R. Callon, "Multiprotocol Label 2528 Switching Architecture", draft-ietf-mpls-arch-06.txt, Cisco 2529 Systems, Lucent Technologies, and IronBridge Networks, August 1999. 2531 [21] Jamoussi, B., editor, "Constraint-Based LSP Setup using LDP", 2532 draft-ietf-mpls-cr-ldp-02.txt, August 1999. 2534 [22] Bradner, S., "Key words for use in RFCs to Indicate Requirement 2535 Levels", BCP 14, RFC 2119, Harvard University, March 1997 2537 [23] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, 2538 RFC 2026, Harvard University, October 1996 2540 [24] Srinivansan, C., and A. Viswanathan, "MPLS Traffic Engineering 2541 Management Information Base Using SMIv2", draft-ietf-mpls-te-mib- 2542 01.txt, Lucent Technologies, June 1999. 2544 [25] Srinivansan, C., and A. Viswanathan, "MPLS Label Switch Router 2545 Management Information Base Using SMIv2", draft-ietf-mpls-lsr-mib- 2546 00.txt, Lucent Technologies, June 1999. 2548 [26] Greene, M., J. Cucchiara, J. Luciani, "Definition of Managed 2549 Objects for the NBMA Next Hop Resolution Protocol (NHRP)", RFC 2550 2677, August 1999. 2552 [27] Internet Assigned Numbers Authority (IANA), ADDRESS FAMILY NUMBERS, 2553 (http://www.isi.edu/in-notes/iana/assignements/address-family- 2554 numbers), for MIB 2555 (ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib). 2557 [28] Noto, M., E. Spiegel, K. Tesink, "Definition of Textual Conventions 2558 and OBJECT-IDENTITIES for ATM Management", RFC 2514, February 1999. 2560 [29] McCloghrie, K., F. Kastenholz, "The Interfaces Group MIB using 2561 SMIv2", RFC 2233, November 1997. 2563 [30] Tesink, K. (ed.) "Definitions of Managed Objects for ATM 2564 Management", RFC 2515, February 1999. 2566 [31] Grossman, D., and J. Heinanen, "Multiprotocol Encapsulation over 2567 ATM Adaptation Layer 5", RFC 2684, September 1999. 2569 [32] Davie, B., J. Lawrence, K. McCloghrie, Y. Rekhter, E. Rosen, G. 2570 Swallow, and P. Doolan, "MPLS using LDP and ATM VC Switching", 2571 draft-ietf-mpls-atm-02.txt, April 1999. 2573 9. Security Considerations 2575 Assuming that secure network management (such as SNMP v3) is 2576 implemented, the objects represented in this MIB do not pose a threat 2577 to the security of the network. 2579 10. Authors' Addresses 2581 James V. Luciani 2582 Nortel Networks 2583 3 Federal Street 2584 Mail Stop: BL3-03 2585 Billerica, MA 01821 2586 Phone: (978) 288-4734 2587 Email: luciani@baynetworks.com 2589 Hans Sjostrand 2590 Ericsson 2591 Business Unit Datacom Networks and IP Services 2592 S-126 25 Stockholm, Sweden 2593 Phone: +46 8 719 9960 2594 Email: hans.sjostrand@etx.ericsson.se 2596 Joan Cucchiara 2597 IronBridge Networks 2598 55 Hayden Ave., Suite 1000 2599 Lexington, MA 02421 2600 Phone: (781) 372-8236 2601 Email: joan@ironbridgenetworks.com 2603 11. Full Copyright Statement 2605 Copyright (C) The Internet Society (1999). All Rights Reserved. 2607 This document and translations of it may be copied and furnished to 2608 others, and derivative works that comment on or otherwise explain it 2609 or assist in its implementation may be prepared, copied, published 2610 and distributed, in whole or in part, without restriction of any 2611 kind, provided that the above copyright notice and this paragraph are 2612 included on all such copies and derivative works. However, this 2613 document itself may not be modified in any way, such as by removing 2614 the copyright notice or references to the Internet Society or other 2615 Internet organizations, except as needed for the purpose of 2616 developing Internet standards in which case the procedures for 2617 copyrights defined in the Internet Standards process must be 2618 followed, or as required to translate it into languages other than 2619 English. 2621 The limited permissions granted above are perpetual and will not be 2622 revoked by the Internet Society or its successors or assigns. 2624 This document and the information contained herein is provided on an 2625 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2626 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2627 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2628 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2629 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2631 12. IANA Address Family Numbers MIB 2633 This section is copied verbatim from the RFC2677 [26]. This section 2634 will be removed in future versions of this draft. This section was 2635 copied here for convenience, as it is IMPORTED into the LDP MIB. 2637 The Internet Assigned Numbers Authority (IANA) has been and continues 2638 to be responsible for maintaining the ADDRESS FAMILY NUMBERS 2639 (http://www.isi.edu/in-notes/iana/assignments/address-family-numbers) 2640 name space assignments. The IANA has placed this list in a MIB 2641 module, such that it may be imported into other MIBs. The motivation 2642 for doing this is to allow MIBs to not have to change when a new 2643 assignment is made to the ADDRESS FAMILY NUMBERS. This is very 2644 similar to the motivation behind the IANAifType-MIB. 2646 Any additions or changes to the list of ADDRESS FAMILY NUMBERS 2647 registered via IANA will be done as they have in the past and this 2648 document does not propose any changes to the ADDRESS FAMILY NUMBERS 2649 other than to place them into a MIB, which can be found via anonymous 2650 FTP at: ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib.