idnits 2.17.1 draft-ietf-mpls-ldp-mib-04.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 == The page length should not exceed 58 lines per page, but there was 20 longer pages, the longest (page 32) being 64 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 59 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. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 390 has weird spacing: '... label field...' == Line 393 has weird spacing: '... bits must ...' == Line 394 has weird spacing: '... on the size...' == Line 396 has weird spacing: '... must be z...' == Line 397 has weird spacing: '... the lower...' == (8 more instances...) -- 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 (January 2000) is 8868 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 2647, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 2656, but no explicit reference was found in the text == Unused Reference: '21' is defined on line 2665, but no explicit reference was found in the text == Unused Reference: '23' is defined on line 2671, but no explicit reference was found in the text == Unused Reference: '24' is defined on line 2674, but no explicit reference was found in the text == Unused Reference: '25' is defined on line 2678, but no explicit reference was found in the text == Unused Reference: '26' is defined on line 2682, but no explicit reference was found in the text == Unused Reference: '27' is defined on line 2686, but no explicit reference was found in the text == Unused Reference: '28' is defined on line 2691, but no explicit reference was found in the text == Unused Reference: '30' is defined on line 2697, but no explicit reference was found in the text == Unused Reference: '31' is defined on line 2700, 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: 17 errors (**), 0 flaws (~~), 28 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 Brix Networks 3 Expires July 2000 H. Sjostrand 4 Ericsson 5 J. Luciani 6 Nortel Networks 7 January 2000 9 Definitions of Managed Objects for 10 the Multiprotocol Label Switching, Label Distribution Protocol (LDP) 12 draft-ietf-mpls-ldp-mib-04.txt 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, .............. 50 75 5.2 Changes from .............. 51 76 5.3 Changes from .............. 52 77 5.4 Changes from .............. 53 78 6 TO DO List ................................................... 53 79 7 Acknowledgments .............................................. 54 80 8 References ................................................... 55 81 9 Security Considerations ...................................... 57 82 10 Authors' Addresses .......................................... 58 83 11 Full Copyright Statement .................................... 58 85 1. Introduction 87 This memo defines a portion of the Management Information Base (MIB) 88 for use with network management protocols in the Internet community. 89 In particular, it describes managed objects for the Multiprotocol 90 Label Switching, Label Distribution Protocol (LDP) [18]. 92 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 93 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 94 document are to be interpreted as described in RFC 2119 [22]. 96 2. The SNMP Management Framework 98 The SNMP Management Framework presently consists of five major 99 components: 101 o An overall architecture, described in RFC 2571 [RFC2571]. 103 o Mechanisms for describing and naming objects and events for the 104 purpose of management. The first version of this Structure of 105 Management Information (SMI) is called SMIv1 and described in 106 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 107 1215 [RFC1215]. The second version, called SMIv2, is described 108 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 109 STD 58, RFC 2580 [RFC2580]. 111 o Message protocols for transferring management information. The 112 first version of the SNMP message protocol is called SNMPv1 and 113 described in STD 15, RFC 1157 [RFC1157]. A second version of 114 the SNMP message protocol, which is not an Internet standards 115 track protocol, is called SNMPv2c and described in RFC 1901 116 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 117 message protocol is called SNMPv3 and described in RFC 1906 118 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 120 o Protocol operations for accessing management information. The 121 first set of protocol operations and associated PDU formats is 122 described in STD 15, RFC 1157 [RFC1157]. A second set of 123 protocol operations and associated PDU formats is described in 124 RFC 1905 [RFC1905]. 126 o A set of fundamental applications described in RFC 2573 127 [RFC2573] and the view-based access control mechanism described 128 in RFC 2575 [RFC2575]. 130 A more detailed introduction to the current SNMP Management Framework 131 can be found in RFC 2570 [RFC2570]. 133 Managed objects are accessed via a virtual information store, termed 134 the Management Information Base or MIB. Objects in the MIB are 135 defined using the mechanisms defined in the SMI. 137 This memo specifies a MIB module that is compliant to the SMIv2. A 138 MIB conforming to the SMIv1 can be produced through the appropriate 139 translations. The resulting translated MIB must be semantically 140 equivalent, except where objects or events are omitted because no 141 translation is possible (use of Counter64). Some machine readable 142 information in SMIv2 will be converted into textual descriptions in 143 SMIv1 during the translation process. However, this loss of machine 144 readable information is not considered to change the semantics of the 145 MIB. 147 3. Structure of the MIB 149 This memo defines a portion of the Management Information Base (MIB) 150 for use with network management protocols in the Internet community. 151 In particular, it describes managed objects for the Multiprotocol 152 Label Switching, Label Distribution Protocol (LDP) as defined in 153 [18]. 155 3.1. Overview 157 The MIB provides objects to configure/set-up potential LDP sessions 158 on a specific LSR. A table is used to configure potential LDP 159 Sessions, where each row in the table initiates an LDP Session. This 160 is the mplsLdpEntityTable. 162 Another table, the mplsLdpPeerTable, is a read-only table which 163 records information learned via discovery. Each row in the Peer 164 Table represents a peer. 166 A third table is used to show the actual sessions which have been, or 167 are in the process of being established. Each row represents a 168 specific session between an Entity (on this LSR) and a peer. The 169 following figure demonstrates these relationships: 171 Entity Peer 172 ------------ ------------ 173 | | | | 174 ------------ ------------- 175 | | -------------- | | 176 ------------ -----> | | <----- ------------ 177 -------------- 178 Session 180 3.2. Interface Indexing 182 Interface Indexes as specified in [29] are used in the MIB. The 183 descriptions of the ifIndexes denote which ifIndex is being used. 184 NOTE: the use of ifIndex is for actual existing connections. 186 3.3. Future Considerations 188 The following aspects are not addressed in this document: VPN issues 189 (i.e. potential MIB objects such as the VPN Identifier are not 190 included at this time), and lastly, multicast issues are not 191 discussed. 193 Some of these issues need further clarification before adding to the 194 MIB. 196 3.4. Discussion of MIB Groups 198 Currently, there are four groups: the MPLS LDP General Group, the 199 MPLS LDP ATM Group, the MPLS LDP Frame Relay Group and the MPLS LDP 200 Notifications Group. The MPLS LDP General Group and the MPLS LDP 201 Notifications Group should always be supported. The MPLS LDP ATM 202 Group is specific to ATM and should be supported only if LDP is using 203 ATM. Likewise, the MPLS LDP Frame Relay group is specific to Frame 204 Relay and should be supported only if LDP is using Frame Relay. 206 3.5. The MPLS LDP General Group 208 This group contains information about the specific LDP Entities which 209 are associated with this agent. Each LSR must have one LDP Entity. 211 3.5.1. The Label Distribution Protocol's Entity Table 213 The LDP Entity Table provides a way to configure the LSR for using 214 LDP. There must be at least one LDP Entity for the LSR to support 215 LDP. 217 Each entry/row in this table represents a single LDP Entity. 219 3.5.2. The Label Distribution Protocol's Entity ATM Objects 221 There exists two tables to configure LDP for using ATM. These tables 222 are the mplsLdpEntityAtmParmsTable and the 223 mplsLdpEntityConfAtmLabelRangeTable. 225 The mplsLdpEntityAtmParmsTable provides a way to configure 226 information which would be contained in the 'Optional Parameter' 227 portion of an LDP PDU Initialization Message. 229 The mplsLdpEntityConfAtmLabelRangeTable provides a way to configure 230 information which would be contained in the 'ATM Label Range 231 Components' portion of an LDP PDU Intialization Message. 233 3.5.3. The Label Distribution Protocol's Entity Frame Relay Objects 235 There exists two tables to configure LDP for using Frame Relay. 236 These tables are the mplsLdpEntityFrameRelayParmsTable and the 237 mplsLdpEntityConfFrLabelRangeTable. 239 The mplsLdpEntityFrameRelayParmsTable provides a way to configure 240 information which would be contained in the 'Optional Parameter' 241 portion of an LDP PDU Initialization Message. 243 The mplsLdpEntityConfFrLabelRangeTable provides a way to configure 244 information which would be contained in the portion of an LDP PDU 245 Intialization Message. 247 3.5.4. The Label Distribution Protocol's Entity Statistics Table 249 The LDP Entity Statistics Table will maintain counters related to an 250 LDP Entity. This Table should be a read-only table which contains 251 statistical information. 253 Each row in this table will be related to a single LDP Entity. 255 3.5.5. The LDP Peer Table 257 The LDP Peer Table is a read-only table which contains information 258 about LDP Peers and their associated Hello Adjacencies. Each row in 259 this table represents a Hello Adjacency. 261 3.5.6. The LDP Session Table 263 The LDP Session Table is a read-only table. Each entry in this table 264 represents a single session between an LDP Entity and a Peer. 266 3.5.7. The LDP ATM Session Table 268 The MPLS LDP ATM Session Table is a read-only table which contains 269 session information specific to ATM. 271 3.5.8. The LDP Frame Relay Session Table 273 The MPLS LDP Frame Relay Session Table is a read-only table which 274 contains session information specific to Frame Relay. 276 3.5.9. The LDP Session Statistics Table 278 The MPLS LDP Session Stats Table is a read-only table which contains 279 statistical information on sessions. 281 3.5.10. The LDP Session Peer Address Table 283 The MPLS LDP Session Peer Address Table is a table which 'extends' 284 the mplsLdpSessionTable. This table is a read-only table which 285 stores Addresses learned after session initialization via "Address 286 Message" advertisement. 288 3.5.11. The LDP Adjacencies Table 290 This is a table of all adjacencies between all LPD Entities and all 291 LDP Peers. A Session may have one or more adjacencies. 293 3.5.12. The LDP Label Information Base (LIB) Table 295 The MPLS LDP LIB Table is a read-only table which contains 296 information stored in the LIB. This table is indexed by a unique 297 number which could be used to represent the LSP segment related to 298 this LIB entry. The Lsp number corresponds to a FEC entry in the FEC 299 Table which is described next. 301 3.5.13. The LDP FEC Table 303 The FEC Table is a read-only table whic contains FEC (Forwarding 304 Equivalence Class) information. Each entry/row represents a single 305 FEC Element. 307 3.6. The LDP Notifications Group 309 3.6.1. LDP Notifications 311 Currently, there is one notification which will be sent when an LDP 312 attempts to initialize the same session beyond the configured 313 threshold. 315 4. MPLS Label Distribution Protocol MIB Definitions 317 MPLS-LDP-MIB DEFINITIONS ::= BEGIN 319 IMPORTS 320 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, 321 experimental, 322 Integer32, Counter32, Unsigned32 323 FROM SNMPv2-SMI 325 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 326 FROM SNMPv2-CONF 328 TEXTUAL-CONVENTION, RowStatus, TimeInterval, TruthValue, 329 TimeStamp 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 "0001281200Z" -- January 28, 2000 342 ORGANIZATION "Multiprotocol Label Switching (mpls) Working 343 Group" 344 CONTACT-INFO 345 "Joan Cucchiara (jcucchiara@brixnet.com) 346 Brix Networks 348 Hans Sjostrand (hans.sjostrand@etx.ericsson.se) 349 Ericsson 351 James V. Luciani (jluciani@nortelnetworks.com) 352 Nortel Networks" 353 DESCRIPTION 354 "This MIB contains managed object definitions for the 355 Multiprotocol Label Switching, Label Distribution 356 Protocol, LDP, as defined in draft-ietf-mpls-ldp-06.txt." 357 ::= { experimental XXXX} -- to be assigned 359 --******************************************************************** 360 -- MPLS LDP Textual Conventions 362 --******************************************************************** 363 -- 365 MplsLsrIdentifier ::= TEXTUAL-CONVENTION 366 STATUS current 367 DESCRIPTION 368 "The Label Switch Router (LSR) identifier 369 is the first 4 bytes or the IP Address component 370 of the Label Distribution Protocol (LDP) identifier." 371 SYNTAX OCTET STRING (SIZE (4)) 373 -- 374 -- A similar TC is also used in RFC2677.txt, perhaps 375 -- this should be made general and not MPLS specific. 376 -- 377 MplsLdpGenAddr ::= TEXTUAL-CONVENTION 378 STATUS current 379 DESCRIPTION 380 "The value of an network layer or data link layer address." 381 SYNTAX OCTET STRING (SIZE (0..64)) 383 -- following label is taken from the draft-ietf-mpls-lsr-mib-00.txt 384 -- It is reproduced here. 386 MplsLabel ::= TEXTUAL-CONVENTION 387 STATUS current 388 DESCRIPTION 389 "Represents an MPLS label. Note that the contents of 390 a label field are interpreted in an interface-type 391 specific fashion. For example, the label carried in 392 the MPLS shim header is 20 bits wide and the top 12 393 bits must be zero. The frame relay label can be 394 either 10, 17 or 23 bits wide depending on the size 395 of the DLCI field size and the top 22, 15, or 9 bits 396 must be zero, respectively. For an ATM interface, 397 the lowermost 16 bits are interpreted as the VCI, 398 the next 8 bits as the VPI and the remaining bits 399 must be zero. Also note the permissible label 400 values are also a function of the interface type. 401 For example, the value 3 has special semantics in 402 the control plane for an MPLS shim header label and 403 is not a valid label value in the datapath." 404 REFERENCE 405 "1. MPLS Label Stack Encoding, Rosen et al, draft- 406 ietf-mpls-label-encaps-04.txt, April 1999. 407 2. Use of Label Switching on Frame Relay Networks, 408 Conta et al, draft-ietf-mpls-fr-03.txt, Nov. 1998." 409 SYNTAX Integer32 411 MplsLdpIdentifier ::= TEXTUAL-CONVENTION 412 STATUS current 413 DESCRIPTION 414 "The LDP identifier is a six octet quantity 415 which is used to identify an Label Switch Router 416 (LSR) label space. 418 The first four octets encode an IP address 419 assigned to the LSR, and the last two octets 420 identify a specific label space within the LSR." 421 SYNTAX OCTET STRING (SIZE (6)) 423 MplsLdpLabelTypes ::= TEXTUAL-CONVENTION 424 STATUS current 425 DESCRIPTION 426 "The Layer 2 label types which are defined for 427 MPLS LDP are generic(1), atm(2), or frameRelay(3)." 428 SYNTAX INTEGER(1..3) 430 -- Top-level structure of the MIB (the following is proposed) 431 mpls OBJECT IDENTIFIER ::= { mplsProtocols } 433 mplsProtocols OBJECT IDENTIFIER ::= { mplsLdpObjects } 434 -- under mplsProtocols will be LDP, CR-LDP, 435 -- and other MPLS "Protocols". 437 mplsLdpObjects OBJECT IDENTIFIER ::= { mplsLdpMIB 1 } 438 mplsLdpNotifications OBJECT IDENTIFIER ::= { mplsLdpMIB 2 } 439 mplsLdpConformance OBJECT IDENTIFIER ::= { mplsLdpMIB 3 } 441 --**************************************************************** 442 -- MPLS LDP Objects 443 --**************************************************************** 445 mplsLdpLsrObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 1 } 447 mplsLdpEntityObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 2 } 449 -- 450 -- The MPLS Label Distribution Protocol Label Switch Router Objects 451 -- 453 mplsLdpLsrId OBJECT-TYPE 454 SYNTAX MplsLsrIdentifier 455 MAX-ACCESS read-only 456 STATUS current 457 DESCRIPTION 458 "The LSR's Identifier." 459 ::= { mplsLdpLsrObjects 1 } 461 mplsLdpLsrLabelRetentionMode OBJECT-TYPE 462 SYNTAX INTEGER { 463 conservative(1), 464 liberal(2) 465 } 466 MAX-ACCESS read-write 467 STATUS current 468 DESCRIPTION 469 "The LSR can be configured to use either 470 conservative or liberal label retention mode. 472 If the value of this object is conservative(1) 473 then advertized label mappings are retained 474 only if they will be used to forward packets, 475 i.e. if label came from a valid next hop. 477 If the value of this object is liberal(2) 478 then all advertized label mappings are retained 479 whether they are from a valid next hop or not." 480 ::= { mplsLdpLsrObjects 2 } 482 mplsLdpLsrLoopDetectionCapable OBJECT-TYPE 483 SYNTAX TruthValue 484 MAX-ACCESS read-only 485 STATUS current 486 DESCRIPTION 487 "A indication of whether this LSR supports 488 loop detection. A value of 'true' indicates 489 this LSR does support loop detection. A value 490 of 'false' indicates this LSR does not support 491 loop detection. Since Loop Detection is determined 492 during Session Initialization, an individual session 493 may not be running with loop detection enabled. This 494 object simply gives an indication of whether or not the 495 LSR has the ability to support Loop Detection." 496 ::= { mplsLdpLsrObjects 3 } 498 -- 499 -- The MPLS Label Distribution Protocol Entity Objects 500 -- 502 mplsLdpEntityIndexNext OBJECT-TYPE 503 SYNTAX Unsigned32 (1..4294967295) 504 MAX-ACCESS read-only 505 STATUS current 506 DESCRIPTION 507 "This object contains an appropriate value to 508 be used for mplsLdpEntityIndex when creating 509 entries in the mplsLdpEntityTable. The value 510 0 indicates that no unassigned entries are 511 available. To obtain the mplsLdpEntityIndex 512 value for a new entry, the manager issues a 513 management protocol retrieval operation to obtain 514 the current value of this object. After each 515 retrieval, the agent should modify the value to 516 the next unassigned index." 517 ::= { mplsLdpEntityObjects 1 } 519 mplsLdpEntityTable OBJECT-TYPE 520 SYNTAX SEQUENCE OF MplsLdpEntityEntry 521 MAX-ACCESS not-accessible 522 STATUS current 523 DESCRIPTION 524 "This table contains information about the 525 MPLS Label Distribution Protocol Entities which 526 exist on this Label Switch Router (LSR)." 527 ::= { mplsLdpEntityObjects 2 } 529 mplsLdpEntityEntry OBJECT-TYPE 530 SYNTAX MplsLdpEntityEntry 531 MAX-ACCESS not-accessible 532 STATUS current 533 DESCRIPTION 534 "An entry in this table represents an LDP entity. 535 An entry can be created by a network administrator 536 or by an SNMP agent as instructed by LDP." 537 INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex } 538 ::= { mplsLdpEntityTable 1 } 540 MplsLdpEntityEntry ::= SEQUENCE { 541 mplsLdpEntityLdpId MplsLdpIdentifier, 542 mplsLdpEntityIndex Unsigned32, 543 mplsLdpEntityProtocolVersion Integer32, 544 mplsLdpEntityAdminStatus INTEGER, 545 mplsLdpEntityOperStatus INTEGER, 546 mplsLdpEntityWellKnownDiscoveryPort Unsigned32, 547 mplsLdpEntityMtu Integer32, 548 mplsLdpEntityKeepAliveHoldTimer Integer32, 549 mplsLdpEntityHelloHoldTimer Integer32, 550 mplsLdpEntityFailedInitSessionThreshold Integer32, 551 mplsLdpEntityControlMethod INTEGER, 552 mplsLdpEntityLabelDistributionMethod INTEGER, 553 mplsLdpEntityLoopDetectionForPV INTEGER, 554 mplsLdpEntityPathVectorLimit Integer32, 555 mplsLdpEntityTargetedPeer TruthValue, 556 mplsLdpEntityTargetedPeerAddrType 557 AddressFamilyNumbers, 558 mplsLdpEntityTargetedPeerAddr MplsLdpGenAddr, 559 mplsLdpEntityOptionalParameters MplsLdpLabelTypes, 560 mplsLdpEntityRowStatus RowStatus 561 } 563 mplsLdpEntityLdpId OBJECT-TYPE 564 SYNTAX MplsLdpIdentifier 565 MAX-ACCESS not-accessible 566 STATUS current 567 DESCRIPTION 568 "The LDP identifier. 570 The first four octets encode an IP address 571 assigned to the LSR, and the last two octets 572 identify a specific label space within the 573 LSR." 574 REFERENCE 575 "LDP Specification, Section on LDP Identifiers." 576 ::= { mplsLdpEntityEntry 1 } 578 mplsLdpEntityIndex OBJECT-TYPE 579 SYNTAX Unsigned32 (1..4294967295) 580 MAX-ACCESS not-accessible 581 STATUS current 582 DESCRIPTION 583 "This index is used as a secondary index to uniquely 584 identify this row. Before creating a row in this table, 585 the 'mplsLdpEntityIndexNext' object should be retrieved. 586 That value should be used for the value of this index 587 when creating a row in this table. (NOTE: if a value 588 of zero (0) is retrieved, that indicates that no rows 589 can be created in this table at this time." 590 ::= { mplsLdpEntityEntry 2 } 592 mplsLdpEntityProtocolVersion OBJECT-TYPE 593 SYNTAX Integer32 594 MAX-ACCESS read-create 595 STATUS current 596 DESCRIPTION 597 "The version number of the protocol. The value of 0 on a 598 read indicates that the version of the protocol is unknown. 599 Otherwise, the value of this object represents the version 600 of the LDP protocol." 601 ::= { mplsLdpEntityEntry 3 } 603 mplsLdpEntityAdminStatus OBJECT-TYPE 604 SYNTAX INTEGER { 605 enable(1), 606 disable(2) 607 } 608 MAX-ACCESS read-create 609 STATUS current 610 DESCRIPTION 611 "The administrative status of this LDP Entity." 612 DEFVAL { enable } 613 ::= { mplsLdpEntityEntry 4 } 615 mplsLdpEntityOperStatus OBJECT-TYPE 616 SYNTAX INTEGER { 617 unknown(0), 618 enabled(1), 619 disabled(2) 620 } 622 MAX-ACCESS read-only 623 STATUS current 624 DESCRIPTION 625 "The operational status of this LDP Entity." 626 ::= { mplsLdpEntityEntry 5 } 628 mplsLdpEntityWellKnownDiscoveryPort OBJECT-TYPE 629 SYNTAX Unsigned32 630 MAX-ACCESS read-create 631 STATUS current 632 DESCRIPTION 633 "The well known LDP Discovery Port." 634 ::= { mplsLdpEntityEntry 6 } 636 mplsLdpEntityMtu OBJECT-TYPE 637 SYNTAX Integer32 (0..65535) 638 MAX-ACCESS read-create 639 STATUS current 640 DESCRIPTION 641 "The maximum transmission unit (MTU) that was configured 642 for this entity." 643 ::= { mplsLdpEntityEntry 7 } 645 mplsLdpEntityKeepAliveHoldTimer OBJECT-TYPE 646 SYNTAX Integer32 (1..65535) 647 UNITS "seconds" 648 MAX-ACCESS read-create 649 STATUS current 650 DESCRIPTION 651 "The two octet value which is the proposed keep alive hold 652 timer for this LDP Entity." 653 ::= { mplsLdpEntityEntry 8 } 655 mplsLdpEntityHelloHoldTimer OBJECT-TYPE 656 SYNTAX Integer32 (0..65535) 657 UNITS "seconds" 658 MAX-ACCESS read-create 659 STATUS current 660 DESCRIPTION 661 "The two octet value which is the proposed Hello hold 662 timer for this LDP Entity. A value of 0 means use the 663 default, 664 which is 15 seconds for Link Hellos and 45 seconds for 665 Targeted 666 Hellos. A value of 65535 means infinite." 667 DEFVAL { 0 } 668 ::= { mplsLdpEntityEntry 9 } 670 mplsLdpEntityFailedInitSessionThreshold OBJECT-TYPE 671 SYNTAX Integer32 672 MAX-ACCESS read-create 673 STATUS current 674 DESCRIPTION 675 "When attempting to establish a session with a 676 given Peer, the given LDP Entity should 677 send out a notification when exceeding this threshold. 678 A value of 0 (zero) for this object 679 indicates that the threshold is infinity. 680 In other words, a notification will not 681 be sent if the value of this object is 0 (zero)." 682 ::= { mplsLdpEntityEntry 10 } 684 mplsLdpEntityControlMethod OBJECT-TYPE 685 SYNTAX INTEGER { 686 independent(1), 687 ordered(2) 688 } 689 MAX-ACCESS read-create 690 STATUS current 691 DESCRIPTION 692 "This object indicates whether the LSR is operating 693 with independent or odered LSP control." 694 ::= { mplsLdpEntityEntry 11 } 696 mplsLdpEntityLabelDistributionMethod OBJECT-TYPE 697 SYNTAX INTEGER { 698 downstreamOnDemand(1), 699 downstreamUnsolicited(2) 700 } 701 MAX-ACCESS read-create 702 STATUS current 703 DESCRIPTION 704 "For any given LDP session, the method of 705 label distribution must be specified." 706 ::= { mplsLdpEntityEntry 12 } 708 mplsLdpEntityLoopDetectionForPV OBJECT-TYPE 709 SYNTAX INTEGER { 710 disabled(0), 711 enabled(1) 712 } 713 MAX-ACCESS read-create 714 STATUS current 715 DESCRIPTION 716 "An indication of whether loop detection based on path 717 vectors is 718 disabled or enabled for this Entity. 720 If this object has a value of disabled(0), 721 then loop detection is disabled. Otherwise, if this object 722 has 723 a value of enabled(1), then loop detection based on path 724 vectors 725 is enabled." 727 ::= { mplsLdpEntityEntry 13 } 729 mplsLdpEntityPathVectorLimit OBJECT-TYPE 730 SYNTAX Integer32 (0..255) 731 MAX-ACCESS read-create 732 STATUS current 733 DESCRIPTION 734 "If the value of 'mplsLdpEntityLoopDetectionForPV' for this 735 entry is 736 'enabled(1)', the this object represents that Path Vector 737 Limit 738 for this Entity. 740 If the value of 'mplsLdpEntityLoopDetectionForPV' for this 741 entry 742 is 'disabled(0)', then this value should be 0 (zero)." 743 ::= { mplsLdpEntityEntry 14 } 745 mplsLdpEntityTargetedPeer OBJECT-TYPE 746 SYNTAX TruthValue 747 MAX-ACCESS read-create 748 STATUS current 749 DESCRIPTION 750 "If this LDP entity uses targeted peer then set this to 751 true." 752 DEFVAL { false } 753 ::= { mplsLdpEntityEntry 15 } 755 mplsLdpEntityTargetedPeerAddrType OBJECT-TYPE 756 SYNTAX AddressFamilyNumbers 757 MAX-ACCESS read-create 758 STATUS current 759 DESCRIPTION 760 "The type of the internetwork layer address used for 761 the Extended Discovery. This object indicates how the value 762 of 763 mplsLdpEntityTargetedPeerAddr is to be interpreted." 764 ::= { mplsLdpEntityEntry 16 } 766 mplsLdpEntityTargetedPeerAddr OBJECT-TYPE 767 SYNTAX MplsLdpGenAddr 768 MAX-ACCESS read-create 769 STATUS current 770 DESCRIPTION 771 "The value of the internetwork layer address used for 772 the Extended Discovery." 773 ::= { mplsLdpEntityEntry 17 } 775 mplsLdpEntityOptionalParameters OBJECT-TYPE 776 SYNTAX MplsLdpLabelTypes 777 MAX-ACCESS read-create 778 STATUS current 779 DESCRIPTION 780 "Specifies the optional parameters for the LDP 781 Initialization Message. If the value is generic(1) 782 then no optional parameters will be sent in 783 the LDP Initialization message associated with 784 this Entity. 786 If the value is atmParameters(2) then 787 a row must be created in the mplsLdpEntityAtmParms 788 Table, which corresponds to this entry. 790 If the value is frameRelayParameters(3) then 791 a row must be created in the mplsLdpEntityFrameRelayParms 792 Table, which corresponds to this entry." 793 ::= { mplsLdpEntityEntry 18 } 795 mplsLdpEntityRowStatus OBJECT-TYPE 796 SYNTAX RowStatus 797 MAX-ACCESS read-create 798 STATUS current 799 DESCRIPTION 800 "An object that allows entries in this table to 801 be created and deleted using the 802 RowStatus convention." 803 ::= { mplsLdpEntityEntry 19 } 805 -- 806 -- Ldp Entity Objects for ATM 807 -- 809 mplsLdpEntityAtmObjects OBJECT IDENTIFIER ::= { 810 mplsLdpEntityObjects 3 } 812 mplsLdpEntityAtmParmsTable OBJECT-TYPE 813 SYNTAX SEQUENCE OF MplsLdpEntityAtmParmsEntry 814 MAX-ACCESS not-accessible 815 STATUS current 816 DESCRIPTION 817 "This table contains information about the 818 ATM specific information which could be used 819 in the 'Optional Parameters' and other ATM specific 820 information." 821 ::= { mplsLdpEntityAtmObjects 1 } 823 mplsLdpEntityAtmParmsEntry OBJECT-TYPE 824 SYNTAX MplsLdpEntityAtmParmsEntry 825 MAX-ACCESS not-accessible 826 STATUS current 827 DESCRIPTION 828 "An entry in this table represents the ATM parameters 829 and ATM information for this LDP entity." 830 INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex } 831 ::= { mplsLdpEntityAtmParmsTable 1 } 833 MplsLdpEntityAtmParmsEntry ::= SEQUENCE { 834 mplsLdpEntityAtmMergeCap INTEGER, 835 mplsLdpEntityAtmLabelRangeComponents Unsigned32, 836 mplsLdpEntityAtmVcDirectionality INTEGER, 837 mplsLdpEntityAtmLsrConnectivity INTEGER, 838 mplsLdpEntityDefaultControlVpi AtmVpIdentifier, 839 mplsLdpEntityDefaultControlVci AtmVcIdentifier, 840 mplsLdpEntityUnlabTrafVpi AtmVpIdentifier, 841 mplsLdpEntityUnlabTrafVci AtmVcIdentifier, 842 mplsLdpEntityAtmRowStatus RowStatus 843 } 845 mplsLdpEntityAtmMergeCap OBJECT-TYPE 846 SYNTAX INTEGER { 847 notSupported(0), 848 vpMerge(1), 849 vcMerge(2), 850 vpAndVcMerge(3) 851 } 852 MAX-ACCESS read-create 853 STATUS current 854 DESCRIPTION 855 "Denotes the Merge Capability of this Entity." 856 ::= { mplsLdpEntityAtmParmsEntry 1 } 858 mplsLdpEntityAtmLabelRangeComponents OBJECT-TYPE 859 SYNTAX Unsigned32 (1..65535) 860 MAX-ACCESS read-create 861 STATUS current 862 DESCRIPTION 863 "Number of LabelRange Components in the Initialization 864 message. This also represents the number of entries 865 in the mplsLdpLabelRangeComponentsTable which correspond 866 to this entry." 867 ::= { mplsLdpEntityAtmParmsEntry 2 } 869 mplsLdpEntityAtmVcDirectionality OBJECT-TYPE 870 SYNTAX INTEGER { 871 bidirectional(0), 872 unidirectional(1) 873 } 874 MAX-ACCESS read-create 875 STATUS current 876 DESCRIPTION 877 "If the value of this object is 'bidirectional(0)', 878 a given VCI, within a given VPI, is used as a 879 label for both directions independently. 881 If the value of this object is 'unidirectional(1)', 882 a given VCI within a VPI designates one direction." 883 ::= { mplsLdpEntityAtmParmsEntry 3 } 885 mplsLdpEntityAtmLsrConnectivity OBJECT-TYPE 886 SYNTAX INTEGER { 887 direct(1), 888 indirect(2) 889 } 890 MAX-ACCESS read-create 891 STATUS current 892 DESCRIPTION 893 "The peer LSR may be connected indirectly by means of an 894 ATM VP so that the VPI values may be different on either 895 endpoint so the label MUST be encoded entirely within the 896 VCI field." 897 REFERENCE 898 "draft-ietf-mpls-atm-02.txt, Section 7" 899 DEFVAL { direct } 900 ::= { mplsLdpEntityAtmParmsEntry 4 } 902 mplsLdpEntityDefaultControlVpi OBJECT-TYPE 903 SYNTAX AtmVpIdentifier 904 MAX-ACCESS read-create 905 STATUS current 906 DESCRIPTION 907 "The default VPI value for the non-MPLS connection. The 908 default value of this is 0 (zero) but other values may 909 be configured. This object allows a different value 910 to be configured." 911 REFERENCE 912 "draft-ietf-mpls-atm-02.txt, Section 7.1" 913 DEFVAL 914 { 0 } 915 ::= { mplsLdpEntityAtmParmsEntry 5 } 917 mplsLdpEntityDefaultControlVci OBJECT-TYPE 918 SYNTAX AtmVcIdentifier 919 MAX-ACCESS read-create 920 STATUS current 921 DESCRIPTION 922 "The Default VCI value for a non-MPLS connection. The 923 default value of this is 32 but other values may be 924 configured. This object allows a different value to 925 be configured." 926 REFERENCE 927 "draft-ietf-mpls-atm-02.txt, Section 7.1" 928 DEFVAL 929 { 32 } 930 ::= { mplsLdpEntityAtmParmsEntry 6 } 932 mplsLdpEntityUnlabTrafVpi OBJECT-TYPE 933 SYNTAX AtmVpIdentifier 934 MAX-ACCESS read-create 935 STATUS current 936 DESCRIPTION 937 "VPI value of the VCC supporting unlabelled traffic. This 938 non-MPLS connection is used to carry unlabelled (IP) 939 packets." 940 DEFVAL { 0 } 941 ::= { mplsLdpEntityAtmParmsEntry 7 } 943 mplsLdpEntityUnlabTrafVci OBJECT-TYPE 944 SYNTAX AtmVcIdentifier 945 MAX-ACCESS read-create 946 STATUS current 947 DESCRIPTION 948 "VCI value of the VCC supporting unlabelled traffic. 949 This non-MPLS connection is used to carry unlabelled (IP) 950 packets." 951 DEFVAL { 32 } 952 ::= { mplsLdpEntityAtmParmsEntry 8 } 954 mplsLdpEntityAtmRowStatus OBJECT-TYPE 955 SYNTAX RowStatus 956 MAX-ACCESS read-create 957 STATUS current 958 DESCRIPTION 959 "An object that allows entries in this table to 960 be created and deleted using the 961 RowStatus convention." 962 ::= { mplsLdpEntityAtmParmsEntry 9 } 964 -- 965 -- The MPLS LDP Entity Configurable ATM Label Range Table 966 -- 968 mplsLdpEntityConfAtmLabelRangeTable OBJECT-TYPE 969 SYNTAX SEQUENCE OF MplsLdpEntityConfAtmLabelRangeEntry 970 MAX-ACCESS not-accessible 971 STATUS current 972 DESCRIPTION 973 "The MPLS LDP Entity Configurable ATM Label Range Table. 974 The purpose of this table is to provide a mechanism 975 for specifying a contiguous range of vpi's 976 with a contiguous range of vci's, or a 'label range' 977 for LDP Entities. 979 LDP Entities which use ATM must have at least one 980 entry in this table." 981 ::= { mplsLdpEntityAtmObjects 2 } 983 mplsLdpEntityConfAtmLabelRangeEntry OBJECT-TYPE 984 SYNTAX MplsLdpEntityConfAtmLabelRangeEntry 985 MAX-ACCESS not-accessible 986 STATUS current 987 DESCRIPTION 988 "A row in the LDP Entity Configurable ATM Label 989 Range Table. One entry in this table contains 990 information on a single range of labels 991 represented by the configured Upper and Lower 992 Bounds VPI/VCI pairs. These are the same 993 data used in the Initialization Message. 995 NOTE: The ranges for a specific LDP Entity 996 are UNIQUE and non-overlapping. For example, 997 for a specific LDP Entity index, there could 998 be one entry having ConfLowerBound vpi/vci == 0/32, and 999 ConfUpperBound vpi/vci == 0/100, and a second entry for 1000 this 1001 same interface with ConfLowerBound vpi/vci == 0/101 and 1002 ConfUpperBound vpi/vci == 0/200. However, there could not 1003 be 1004 a third entry with ConfLowerBound vpi/vci == 0/200 and 1005 ConfUpperBound vpi/vci == 0/300 because this label range 1006 overlaps 1007 with the second entry (i.e. both entries now have 0/200). 1009 A row will not be created unless a unique and 1010 non-overlapping 1011 range is specified. Thus, row creation implies a one-shot 1012 row creation of LDP EntityID and ConfLowerBound vpi/vci and 1013 ConfUpperBound vpi/vci. At least one label range entry 1014 for a specific LDP Entity MUST include the default VPI/VCI 1015 values denoted in the LDP Entity Table." 1016 INDEX { mplsLdpEntityLdpId, 1017 mplsLdpEntityIndex, 1018 mplsLdpEntityConfAtmLabelRangeMinimumVpi, 1019 mplsLdpEntityConfAtmLabelRangeMinimumVci 1020 } 1021 ::= { mplsLdpEntityConfAtmLabelRangeTable 1 } 1023 MplsLdpEntityConfAtmLabelRangeEntry ::= SEQUENCE { 1024 mplsLdpEntityConfAtmLabelRangeMinimumVpi AtmVpIdentifier, 1025 mplsLdpEntityConfAtmLabelRangeMinimumVci AtmVcIdentifier, 1026 mplsLdpEntityConfAtmLabelRangeMaximumVpi AtmVpIdentifier, 1027 mplsLdpEntityConfAtmLabelRangeMaximumVci AtmVcIdentifier, 1028 mplsLdpEntityConfAtmLabelRangeRowStatus RowStatus 1029 } 1031 mplsLdpEntityConfAtmLabelRangeMinimumVpi OBJECT-TYPE 1032 SYNTAX AtmVpIdentifier 1033 MAX-ACCESS not-accessible 1034 STATUS current 1035 DESCRIPTION 1036 "The minimum VPI number configured for this range." 1037 ::= { mplsLdpEntityConfAtmLabelRangeEntry 1 } 1039 mplsLdpEntityConfAtmLabelRangeMinimumVci OBJECT-TYPE 1040 SYNTAX AtmVcIdentifier 1041 MAX-ACCESS not-accessible 1042 STATUS current 1043 DESCRIPTION 1044 "The minimum VCI number configured for this range." 1045 ::= { mplsLdpEntityConfAtmLabelRangeEntry 2 } 1047 mplsLdpEntityConfAtmLabelRangeMaximumVpi OBJECT-TYPE 1048 SYNTAX AtmVpIdentifier 1049 MAX-ACCESS read-create 1050 STATUS current 1051 DESCRIPTION 1052 "The maximum VPI number configured for this range." 1053 ::= { mplsLdpEntityConfAtmLabelRangeEntry 3 } 1055 mplsLdpEntityConfAtmLabelRangeMaximumVci OBJECT-TYPE 1056 SYNTAX AtmVcIdentifier 1057 MAX-ACCESS read-create 1058 STATUS current 1059 DESCRIPTION 1060 "The maximum VCI number configured for this range." 1061 ::= { mplsLdpEntityConfAtmLabelRangeEntry 4 } 1063 mplsLdpEntityConfAtmLabelRangeRowStatus OBJECT-TYPE 1064 SYNTAX RowStatus 1065 MAX-ACCESS read-create 1066 STATUS current 1067 DESCRIPTION 1068 "An object that allows entries in this 1069 table to be created and deleted using 1070 the RowStatus convention. 1072 There must exist at least one entry in this 1073 table for every LDP Entity that has 1074 'mplsLdpEntityOptionalParameters' object with 1075 a value of 'atmSessionParameters'." 1076 ::= { mplsLdpEntityConfAtmLabelRangeEntry 5 } 1078 -- 1079 -- Ldp Entity Objects for Frame Relay 1080 -- 1082 mplsLdpEntityFrameRelayObjects OBJECT IDENTIFIER ::= 1083 { mplsLdpEntityObjects 4 } 1085 mplsLdpEntityFrameRelayParmsTable OBJECT-TYPE 1086 SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayParmsEntry 1087 MAX-ACCESS not-accessible 1088 STATUS current 1089 DESCRIPTION 1090 "This table contains information about the 1091 Optional Parameters to specify what this Entity is 1092 going to specify for Frame Relay specific 1093 LDP Intialization Messages." 1094 ::= { mplsLdpEntityFrameRelayObjects 1 } 1096 mplsLdpEntityFrameRelayParmsEntry OBJECT-TYPE 1097 SYNTAX MplsLdpEntityFrameRelayParmsEntry 1098 MAX-ACCESS not-accessible 1099 STATUS current 1100 DESCRIPTION 1101 "An entry in this table represents the Frame Relay 1102 optional parameters associated with the LDP entity." 1103 INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex } 1104 ::= { mplsLdpEntityFrameRelayParmsTable 1 } 1106 MplsLdpEntityFrameRelayParmsEntry ::= SEQUENCE { 1107 mplsLdpEntityFrMergeCap INTEGER, 1108 mplsLdpEntityFrLabelRangeComponents Unsigned32, 1109 mplsLdpEntityFrVcDirectionality INTEGER, 1110 mplsLdpEntityFrParmsRowStatus RowStatus 1111 } 1113 mplsLdpEntityFrMergeCap OBJECT-TYPE 1114 SYNTAX INTEGER { 1115 notSupported(0), 1116 supported(1) 1117 } 1118 MAX-ACCESS read-create 1119 STATUS current 1120 DESCRIPTION 1121 "This represents whether or not Frame Relay merge 1122 capability 1123 is supported." 1124 ::= { mplsLdpEntityFrameRelayParmsEntry 1 } 1126 mplsLdpEntityFrLabelRangeComponents OBJECT-TYPE 1127 SYNTAX Unsigned32 (1..65535) 1128 MAX-ACCESS read-create 1129 STATUS current 1130 DESCRIPTION 1131 "Number of LabelRange Components in the Initialization 1132 message. This also represents the number of entries 1133 in the mplsLdpEntityConfFrLabelRangeTable which correspond 1134 to this entry." 1135 ::= { mplsLdpEntityFrameRelayParmsEntry 2 } 1137 mplsLdpEntityFrVcDirectionality OBJECT-TYPE 1138 SYNTAX INTEGER { 1139 bidirectional(0), 1140 unidirection(1) 1141 } 1142 MAX-ACCESS read-create 1143 STATUS current 1144 DESCRIPTION 1145 "If the value of this object is 'bidirectional(0)', then 1146 the LSR supports the use of a given DLCI as a label for 1147 both directions independently. If the value of this object 1148 is 'unidirectional(1)', then the LSR uses the given DLCI 1149 as a label in only one direction." 1150 ::= { mplsLdpEntityFrameRelayParmsEntry 3 } 1152 mplsLdpEntityFrParmsRowStatus OBJECT-TYPE 1153 SYNTAX RowStatus 1154 MAX-ACCESS read-create 1155 STATUS current 1156 DESCRIPTION 1157 "An object that allows entries in this table to 1158 be created and deleted using the 1159 RowStatus convention." 1160 ::= { mplsLdpEntityFrameRelayParmsEntry 4 } 1162 -- 1163 -- Frame Relay Label Range Components 1164 -- 1166 mplsLdpEntityConfFrLabelRangeTable OBJECT-TYPE 1167 SYNTAX SEQUENCE OF MplsLdpEntityConfFrLabelRangeEntry 1168 MAX-ACCESS not-accessible 1169 STATUS current 1170 DESCRIPTION 1171 "This table contains information about the 1172 Optional Parameters to specify what this Entity is 1173 going to specify for Frame Relay specific 1174 LDP Intialization Messages." 1175 ::= { mplsLdpEntityFrameRelayObjects 2 } 1177 mplsLdpEntityConfFrLabelRangeEntry OBJECT-TYPE 1178 SYNTAX MplsLdpEntityConfFrLabelRangeEntry 1179 MAX-ACCESS not-accessible 1180 STATUS current 1181 DESCRIPTION 1182 "An entry in this table represents the Frame Relay 1183 optional parameters associated with the LDP entity." 1184 INDEX { mplsLdpEntityLdpId, 1185 mplsLdpEntityIndex, 1186 mplsLdpConfFrMinimumDlci 1187 } 1189 ::= { mplsLdpEntityConfFrLabelRangeTable 1 } 1191 MplsLdpEntityConfFrLabelRangeEntry ::= SEQUENCE { 1192 mplsLdpConfFrMinimumDlci Integer32, 1193 mplsLdpConfFrMaximumDlci Integer32, 1194 mplsLdpConfFrLen INTEGER, 1195 mplsLdpConfFrRowStatus RowStatus 1196 } 1198 mplsLdpConfFrMinimumDlci OBJECT-TYPE 1199 SYNTAX Integer32(0..4194303) 1200 MAX-ACCESS not-accessible 1201 STATUS current 1202 DESCRIPTION 1203 "The lower bound which is supported. This value should 1204 be the same as that in the Frame Relay Label Range 1205 Component's 1206 Minimum DLCI field." 1207 ::= { mplsLdpEntityConfFrLabelRangeEntry 1 } 1209 mplsLdpConfFrMaximumDlci OBJECT-TYPE 1210 SYNTAX Integer32 (0..4194303) 1211 MAX-ACCESS read-create 1212 STATUS current 1213 DESCRIPTION 1214 "The upper bound which is supported. This value should 1215 be the same as that in the Frame Relay Label Range 1216 Component's 1217 Maximum DLCI field." 1218 ::= { mplsLdpEntityConfFrLabelRangeEntry 2 } 1220 mplsLdpConfFrLen OBJECT-TYPE 1221 SYNTAX INTEGER { 1222 tenDlciBits(0), 1223 seventeenDlciBits(1), 1224 twentyThreeDlciBits(2) 1225 } 1226 MAX-ACCESS read-create 1227 STATUS current 1228 DESCRIPTION 1229 "This object specifies the DLCI bits." 1230 ::= { mplsLdpEntityConfFrLabelRangeEntry 3 } 1232 mplsLdpConfFrRowStatus OBJECT-TYPE 1233 SYNTAX RowStatus 1234 MAX-ACCESS read-create 1235 STATUS current 1236 DESCRIPTION 1237 "An object that allows entries in this table to 1238 be created and deleted using the 1239 RowStatus convention. 1241 If the value of the object 1242 'mplsLdpEntityOptionalParameters' 1243 contains the value of 1244 'frameReleaySessionParameters(3)' then 1245 there must be at least one corresponding entry in this 1246 table." 1247 ::= { mplsLdpEntityConfFrLabelRangeEntry 4 } 1249 -- 1250 -- The MPLS LDP Entity Statistics Table 1251 -- 1253 mplsLdpEntityStatsTable OBJECT-TYPE 1254 SYNTAX SEQUENCE OF MplsLdpEntityStatsEntry 1255 MAX-ACCESS not-accessible 1256 STATUS current 1257 DESCRIPTION 1258 "This table is a read-only table which augments 1259 the mplsLdpEntityTable. The purpose of this 1260 table is to keep statistical information about 1261 the LDP Entities on the LSR." 1262 ::= { mplsLdpEntityObjects 5 } 1264 mplsLdpEntityStatsEntry OBJECT-TYPE 1265 SYNTAX MplsLdpEntityStatsEntry 1266 MAX-ACCESS not-accessible 1267 STATUS current 1268 DESCRIPTION 1269 "A row in this table contains statistical information 1270 about an LDP Entity. Some counters contained in a 1271 row are for fatal errors received during a former 1272 LDP Session associated with this entry. For example, 1273 an Ldp Pdu received on a TCP connection for an 1274 LDP Session which contains a fatal error is counted 1275 here, because the session is terminated. 1276 If the error is NOT fatal (i.e. and the Session 1277 remains), then the error is counted in the 1278 mplsLdpSessionStatsEntry." 1279 AUGMENTS { mplsLdpEntityEntry } 1280 ::= { mplsLdpEntityStatsTable 1 } 1282 MplsLdpEntityStatsEntry ::= SEQUENCE { 1283 mplsLdpAttemptedSessions Counter32, 1284 mplsLdpSessionRejectedNoHelloErrors Counter32, 1285 mplsLdpSessionRejectedAdvertisementErrors Counter32, 1286 mplsLdpSessionRejectedMaxPduErrors Counter32, 1287 mplsLdpSessionRejectedLabelRangeErrors Counter32, 1288 mplsLdpBadLdpIdentifierErrors Counter32, 1289 mplsLdpBadPduLengthErrors Counter32, 1290 mplsLdpBadMessageLengthErrors Counter32, 1291 mplsLdpBadTlvLengthErrors Counter32, 1292 mplsLdpMalformedTlvValueErrors Counter32, 1293 mplsLdpKeepAliveTimerExpiredErrors Counter32, 1294 mplsLdpShutdownNotifReceived Counter32, 1295 mplsLdpShutdownNotifSent Counter32 1296 } 1298 mplsLdpAttemptedSessions OBJECT-TYPE 1299 SYNTAX Counter32 1300 MAX-ACCESS read-only 1301 STATUS current 1302 DESCRIPTION 1303 "A count of the total attempted sessions for 1304 this LDP Entity." 1305 ::= { mplsLdpEntityStatsEntry 1 } 1307 mplsLdpSessionRejectedNoHelloErrors OBJECT-TYPE 1308 SYNTAX Counter32 1309 MAX-ACCESS read-only 1310 STATUS current 1311 DESCRIPTION 1312 "A count of the Session Rejected/No Hello Error 1313 Notification Messages sent or received by 1314 this LDP Entity." 1315 ::= { mplsLdpEntityStatsEntry 2 } 1317 mplsLdpSessionRejectedAdvertisementErrors OBJECT-TYPE 1318 SYNTAX Counter32 1319 MAX-ACCESS read-only 1320 STATUS current 1321 DESCRIPTION 1322 "A count of the Session Rejected/Parameters 1323 Advertisement Mode Error Notification Messages sent 1324 or received by this LDP Entity." 1325 ::= { mplsLdpEntityStatsEntry 3 } 1327 mplsLdpSessionRejectedMaxPduErrors OBJECT-TYPE 1328 SYNTAX Counter32 1329 MAX-ACCESS read-only 1330 STATUS current 1331 DESCRIPTION 1332 "A count of the Session Rejected/Parameters 1333 Max Pdu Length Error Notification Messages sent 1334 or received by this LDP Entity." 1335 ::= { mplsLdpEntityStatsEntry 4 } 1337 mplsLdpSessionRejectedLabelRangeErrors OBJECT-TYPE 1338 SYNTAX Counter32 1339 MAX-ACCESS read-only 1340 STATUS current 1341 DESCRIPTION 1342 "A count of the Session Rejected/Parameters 1343 Label Range Notification Notification Messages sent 1344 or received by this LDP Entity." 1345 ::= { mplsLdpEntityStatsEntry 5 } 1347 mplsLdpBadLdpIdentifierErrors OBJECT-TYPE 1348 SYNTAX Counter32 1349 MAX-ACCESS read-only 1350 STATUS current 1351 DESCRIPTION 1352 "This object counts the number of Bad LDP Identifier Fatal 1353 Errors detected by the session(s) (past and present) 1354 associated 1355 with this LDP Entity." 1356 REFERENCE 1357 "LDP Specification, Section 3.5.1.2." 1358 ::= { mplsLdpEntityStatsEntry 6 } 1360 mplsLdpBadPduLengthErrors OBJECT-TYPE 1361 SYNTAX Counter32 1362 MAX-ACCESS read-only 1363 STATUS current 1364 DESCRIPTION 1365 "This object counts the number of Bad Pdu Length Fatal 1366 Errors detected by the session(s) (past and present) 1367 associated 1368 with this LDP Entity." 1369 REFERENCE 1370 "LDP Specification, Section 3.5.1.2." 1371 ::= { mplsLdpEntityStatsEntry 7 } 1373 mplsLdpBadMessageLengthErrors OBJECT-TYPE 1374 SYNTAX Counter32 1375 MAX-ACCESS read-only 1376 STATUS current 1377 DESCRIPTION 1378 "This object counts the number of Bad Message Length Fatal 1379 Errors detected by the session(s) (past and present) 1380 associated 1381 with this LDP Entity." 1382 REFERENCE 1383 "LDP Specification, Section 3.5.1.2." 1384 ::= { mplsLdpEntityStatsEntry 8 } 1386 mplsLdpBadTlvLengthErrors OBJECT-TYPE 1387 SYNTAX Counter32 1388 MAX-ACCESS read-only 1389 STATUS current 1390 DESCRIPTION 1391 "This object counts the number of Bad TLV Length Fatal 1392 Errors detected by the session(s) (past and present) 1393 associated 1394 with this LDP Entity." 1396 REFERENCE 1397 "LDP Specification, Section 3.5.1.2." 1398 ::= { mplsLdpEntityStatsEntry 9 } 1400 mplsLdpMalformedTlvValueErrors OBJECT-TYPE 1401 SYNTAX Counter32 1402 MAX-ACCESS read-only 1403 STATUS current 1404 DESCRIPTION 1405 "This object counts the number of Malformed TLV Value Fatal 1406 Errors detected by the session(s) (past and present) 1407 associated 1408 with this LDP Entity." 1409 REFERENCE 1410 "LDP Specification, Section 3.5.1.2." 1411 ::= { mplsLdpEntityStatsEntry 10 } 1413 mplsLdpKeepAliveTimerExpiredErrors OBJECT-TYPE 1414 SYNTAX Counter32 1415 MAX-ACCESS read-only 1416 STATUS current 1417 DESCRIPTION 1418 "This object counts the number of Session Keep Alive Timer 1419 Expired Errors detected by the session(s) (past and 1420 present) 1421 associated with this LDP Entity." 1422 REFERENCE 1423 "LDP Specification, Section 3.5.1.2." 1424 ::= { mplsLdpEntityStatsEntry 11 } 1426 mplsLdpShutdownNotifReceived OBJECT-TYPE 1427 SYNTAX Counter32 1428 MAX-ACCESS read-only 1429 STATUS current 1430 DESCRIPTION 1431 "This object counts the number of Shutdown Notfications 1432 received related to session(s) (past and present) 1433 associated 1434 with this LDP Entity." 1435 ::= { mplsLdpEntityStatsEntry 12 } 1437 mplsLdpShutdownNotifSent OBJECT-TYPE 1438 SYNTAX Counter32 1439 MAX-ACCESS read-only 1440 STATUS current 1441 DESCRIPTION 1442 "This object counts the number of Shutdown Notfications 1443 sent related to session(s) (past and present) associated 1444 with this LDP Entity." 1445 ::= { mplsLdpEntityStatsEntry 13 } 1447 -- 1448 -- The MPLS LDP Peer Table 1449 -- 1451 mplsLdpPeerObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 3 } 1453 mplsLdpPeerTable OBJECT-TYPE 1454 SYNTAX SEQUENCE OF MplsLdpPeerEntry 1455 MAX-ACCESS not-accessible 1456 STATUS current 1457 DESCRIPTION 1458 "Information about LDP peers. This information is 1459 gathered either by the Discovery messages and/or by 1460 Session Intialization Messages." 1461 ::= { mplsLdpPeerObjects 1 } 1463 mplsLdpPeerEntry OBJECT-TYPE 1464 SYNTAX MplsLdpPeerEntry 1465 MAX-ACCESS not-accessible 1466 STATUS current 1467 DESCRIPTION 1468 "Information about a single Peer." 1469 INDEX { mplsLdpPeerLdpId } 1470 ::= { mplsLdpPeerTable 1 } 1472 MplsLdpPeerEntry ::= SEQUENCE { 1473 mplsLdpPeerLdpId MplsLdpIdentifier, 1474 mplsLdpPeerLabelDistributionMethod INTEGER, 1475 mplsLdpPeerLoopDetectionForPV INTEGER, 1476 mplsLdpPeerPathVectorLimit Integer32 1477 } 1479 mplsLdpPeerLdpId OBJECT-TYPE 1480 SYNTAX MplsLdpIdentifier 1481 MAX-ACCESS not-accessible 1482 STATUS current 1483 DESCRIPTION 1484 "The LDP identifier of this LDP Peer." 1485 ::= { mplsLdpPeerEntry 1 } 1487 mplsLdpPeerLabelDistributionMethod OBJECT-TYPE 1488 SYNTAX INTEGER { 1489 downstreamOnDemand(1), 1490 downstreamUnsolicited(2) 1491 } 1492 MAX-ACCESS read-only 1493 STATUS current 1494 DESCRIPTION 1495 "For any given LDP session, the method of 1496 label distribution must be specified." 1497 REFERENCE 1498 "draft-ietf-mpls-arch-06.txt [20]." 1499 ::= { mplsLdpPeerEntry 2 } 1501 mplsLdpPeerLoopDetectionForPV OBJECT-TYPE 1502 SYNTAX INTEGER { 1503 disabled(0), 1504 enabled(1) 1505 } 1506 MAX-ACCESS read-only 1507 STATUS current 1508 DESCRIPTION 1509 "An indication of whether loop detection based on path 1510 vectors is 1511 disabled or enabled for this Peer. 1513 If this object has a value of disabled(0), 1514 then loop detection is disabled. Otherwise, if this object 1515 has 1516 a value of enabled(1), then loop detection based on path 1517 vectors 1518 is enabled." 1519 ::= { mplsLdpPeerEntry 3 } 1521 mplsLdpPeerPathVectorLimit OBJECT-TYPE 1522 SYNTAX Integer32 (0..255) 1523 MAX-ACCESS read-only 1524 STATUS current 1525 DESCRIPTION 1526 "If the value of 'mplsLdpPeerLoopDetectionForPV' for this 1527 entry is 1528 'enabled(1)', the this object represents that Path Vector 1529 Limit 1530 for this peer. 1532 If the value of 'mplsLdpPeerLoopDetectionForPV' for this 1533 entry 1534 is 'disabled(0)', then this value should be 0 (zero)." 1535 ::= { mplsLdpPeerEntry 4 } 1537 -- 1538 -- The MPLS LDP Sessions Table 1539 -- 1541 mplsLdpSessionObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 4 } 1543 mplsLdpSessionTable OBJECT-TYPE 1544 SYNTAX SEQUENCE OF MplsLdpSessionEntry 1545 MAX-ACCESS not-accessible 1546 STATUS current 1547 DESCRIPTION 1548 "A table of Sessions between the LDP Entities and 1549 LDP Peers. Each row represents a single session." 1550 ::= { mplsLdpSessionObjects 1 } 1552 mplsLdpSessionEntry OBJECT-TYPE 1553 SYNTAX MplsLdpSessionEntry 1554 MAX-ACCESS not-accessible 1555 STATUS current 1556 DESCRIPTION 1557 "An entry in this table represents information on a 1558 single session between an LDP Entity and LDP Peer. 1559 The information contained in a row is read-only." 1560 INDEX { mplsLdpEntityLdpId, 1561 mplsLdpEntityIndex, 1562 mplsLdpPeerLdpId 1563 } 1564 ::= { mplsLdpSessionTable 1 } 1566 MplsLdpSessionEntry ::= SEQUENCE { 1567 mplsLdpSessionState INTEGER, 1568 mplsLdpSessionProtocolVersion Integer32, 1569 mplsLdpSessionKeepAliveHoldTimeRemaining TimeInterval, 1570 mplsLdpSessionMaxPduLength Integer32, 1571 mplsLdpSessionDiscontinuityTime TimeStamp 1572 } 1574 mplsLdpSessionState OBJECT-TYPE 1575 SYNTAX INTEGER { 1576 nonexistent(1), 1577 initialized(2), 1578 openrec(3), 1579 opensent(4), 1580 operational(5) 1581 } 1582 MAX-ACCESS read-only 1583 STATUS current 1584 DESCRIPTION 1585 "The current state of the session, all of the 1586 states 1 - 5 are based on the state machine for 1587 session negotiation behavior." 1588 ::= { mplsLdpSessionEntry 1 } 1590 mplsLdpSessionProtocolVersion OBJECT-TYPE 1591 SYNTAX Integer32(1..65535) 1592 MAX-ACCESS read-only 1593 STATUS current 1594 DESCRIPTION 1595 "The version of the LDP Protocol which 1596 this session is using." 1597 ::= { mplsLdpSessionEntry 2 } 1599 mplsLdpSessionKeepAliveHoldTimeRemaining OBJECT-TYPE 1600 SYNTAX TimeInterval 1601 MAX-ACCESS read-only 1602 STATUS current 1603 DESCRIPTION 1604 "The keep alive hold time remaining for this session." 1605 ::= { mplsLdpSessionEntry 3 } 1607 mplsLdpSessionMaxPduLength OBJECT-TYPE 1608 SYNTAX Integer32 (0..65535) 1609 MAX-ACCESS read-only 1610 STATUS current 1611 DESCRIPTION 1612 "The value of maximum allowable length for LDP PDUs for 1613 this session. This value may have been negotiated during 1614 the Session Initialization." 1615 ::= { mplsLdpSessionEntry 4 } 1617 mplsLdpSessionDiscontinuityTime OBJECT-TYPE 1618 SYNTAX TimeStamp 1619 MAX-ACCESS read-only 1620 STATUS current 1621 DESCRIPTION 1622 "The value of sysUpTime on the most recent occasion at 1623 which any one or more of this session's counters 1624 suffered a discontinuity. The relevant counters are 1625 the specific instances associated with this session 1626 of any Counter32 or Counter64 object contained in the 1627 mplsLdpSessionStatsTable. If no such discontinuities have 1628 occurred since the last re-initialization of the local 1629 management subsystem, then this object contains a zero 1630 value. 1632 Also, an NMS can distinguish when a session 1633 between a given Entity and Peer goes away and then is 1634 're-established'. This value would change and 1635 thus indicate to the NMS that this is a different session." 1636 ::= { mplsLdpSessionEntry 5 } 1638 -- 1639 -- MPLS LDP ATM Session Information 1640 -- 1642 mplsLdpAtmSessionTable OBJECT-TYPE 1643 SYNTAX SEQUENCE OF MplsLdpAtmSessionEntry 1644 MAX-ACCESS not-accessible 1645 STATUS current 1646 DESCRIPTION 1647 "A table which relates Sessions in the 1648 'mplsLdpSessionTable' 1649 and their label range intersections. There could 1650 be one or more label range intersections between an 1651 LDP Entity and LDP Peer using ATM as the underlying media. 1653 Each row represents a single label range intersection. 1655 NOTE: this table cannot use the 'AUGMENTS' 1656 clause because there is not necessarily a one-to-one 1657 mapping between this table and the mplsLdpSessionTable." 1658 ::= { mplsLdpSessionObjects 2 } 1660 mplsLdpAtmSessionEntry OBJECT-TYPE 1661 SYNTAX MplsLdpAtmSessionEntry 1662 MAX-ACCESS not-accessible 1663 STATUS current 1664 DESCRIPTION 1665 "An entry in this table represents information on a 1666 single label range intersection between an LDP Entity 1667 and LDP Peer. 1669 The information contained in a row is read-only." 1670 INDEX { mplsLdpEntityLdpId, 1671 mplsLdpEntityIndex, 1672 mplsLdpPeerLdpId, 1673 mplsLdpSessionAtmLabelRangeLowerBoundVpi, 1674 mplsLdpSessionAtmLabelRangeLowerBoundVci 1676 } 1677 ::= { mplsLdpAtmSessionTable 1 } 1679 MplsLdpAtmSessionEntry ::= SEQUENCE { 1680 mplsLdpSessionAtmLabelRangeLowerBoundVpi AtmVpIdentifier, 1681 mplsLdpSessionAtmLabelRangeLowerBoundVci AtmVcIdentifier, 1682 mplsLdpSessionAtmLabelRangeUpperBoundVpi AtmVpIdentifier, 1683 mplsLdpSessionAtmLabelRangeUpperBoundVci AtmVcIdentifier 1684 } 1686 mplsLdpSessionAtmLabelRangeLowerBoundVpi OBJECT-TYPE 1687 SYNTAX AtmVpIdentifier 1688 MAX-ACCESS not-accessible 1689 STATUS current 1690 DESCRIPTION 1691 "The minimum VPI number for this range." 1692 ::= { mplsLdpAtmSessionEntry 1 } 1694 mplsLdpSessionAtmLabelRangeLowerBoundVci OBJECT-TYPE 1695 SYNTAX AtmVcIdentifier 1696 MAX-ACCESS not-accessible 1697 STATUS current 1698 DESCRIPTION 1699 "The minimum VCI number for this range." 1700 ::= { mplsLdpAtmSessionEntry 2 } 1702 mplsLdpSessionAtmLabelRangeUpperBoundVpi OBJECT-TYPE 1703 SYNTAX AtmVpIdentifier 1704 MAX-ACCESS read-only 1705 STATUS current 1706 DESCRIPTION 1707 "The maximum VPI number for this range." 1708 ::= { mplsLdpAtmSessionEntry 3 } 1710 mplsLdpSessionAtmLabelRangeUpperBoundVci OBJECT-TYPE 1711 SYNTAX AtmVcIdentifier 1712 MAX-ACCESS read-only 1713 STATUS current 1714 DESCRIPTION 1715 "The maximum VCI number for this range." 1716 ::= { mplsLdpAtmSessionEntry 4 } 1718 -- 1719 -- MPLS LDP Frame Relay Session Information 1720 -- 1722 mplsLdpFrameRelaySessionTable OBJECT-TYPE 1723 SYNTAX SEQUENCE OF MplsLdpFrameRelaySessionEntry 1724 MAX-ACCESS not-accessible 1725 STATUS current 1726 DESCRIPTION 1727 "A table of Frame Relay label range intersections 1728 between the LDP Entities and LDP Peers. 1729 Each row represents a single label range intersection. 1731 NOTE: this table cannot use the 'AUGMENTS' 1732 clause because there is not necessarily a one-to-one 1733 mapping between this table and the mplsLdpSessionTable." 1734 ::= { mplsLdpSessionObjects 3 } 1736 mplsLdpFrameRelaySessionEntry OBJECT-TYPE 1737 SYNTAX MplsLdpFrameRelaySessionEntry 1738 MAX-ACCESS not-accessible 1739 STATUS current 1740 DESCRIPTION 1741 "An entry in this table represents information on a 1742 single label range intersection between an 1743 LDP Entity and LDP Peer. 1745 The information contained in a row is read-only." 1746 INDEX { mplsLdpEntityLdpId, 1747 mplsLdpEntityIndex, 1748 mplsLdpPeerLdpId, 1749 mplsLdpFrSessionMinDlci 1750 } 1751 ::= { mplsLdpFrameRelaySessionTable 1 } 1753 MplsLdpFrameRelaySessionEntry ::= SEQUENCE { 1754 mplsLdpFrSessionMinDlci Integer32, 1755 mplsLdpFrSessionMaxDlci Integer32, 1756 mplsLdpFrSessionLen INTEGER 1757 } 1759 mplsLdpFrSessionMinDlci OBJECT-TYPE 1760 SYNTAX Integer32(0..4194303) 1761 MAX-ACCESS not-accessible 1762 STATUS current 1763 DESCRIPTION 1764 "The lower bound of DLCIs which are supported." 1765 ::= { mplsLdpFrameRelaySessionEntry 1 } 1767 mplsLdpFrSessionMaxDlci OBJECT-TYPE 1768 SYNTAX Integer32 (0..4194303) 1769 MAX-ACCESS read-only 1770 STATUS current 1771 DESCRIPTION 1772 "The upper bound of DLCIs which are supported." 1773 ::= { mplsLdpFrameRelaySessionEntry 2 } 1775 mplsLdpFrSessionLen OBJECT-TYPE 1776 SYNTAX INTEGER { 1777 tenDlciBits(0), 1778 seventeenDlciBits(1), 1779 twentyThreeDlciBits(2) 1780 } 1781 MAX-ACCESS read-only 1782 STATUS current 1783 DESCRIPTION 1784 "This object specifies the DLCI bits." 1785 ::= { mplsLdpFrameRelaySessionEntry 3 } 1787 -- 1788 -- The MPLS LDP Session Statistics Table 1789 -- 1791 mplsLdpSessionStatsTable OBJECT-TYPE 1792 SYNTAX SEQUENCE OF MplsLdpSessionStatsEntry 1793 MAX-ACCESS not-accessible 1794 STATUS current 1795 DESCRIPTION 1796 "A table of Sessions between the LDP Entities and 1797 LDP Peers." 1798 ::= { mplsLdpSessionObjects 4 } 1800 mplsLdpSessionStatsEntry OBJECT-TYPE 1801 SYNTAX MplsLdpSessionStatsEntry 1802 MAX-ACCESS not-accessible 1803 STATUS current 1804 DESCRIPTION 1805 "An entry in this table represents statistical information 1806 on a 1807 single session between an LDP Entity and LDP Peer." 1808 AUGMENTS { mplsLdpSessionEntry } 1809 ::= { mplsLdpSessionStatsTable 1 } 1811 MplsLdpSessionStatsEntry ::= SEQUENCE { 1812 mplsLdpSessionStatsUnknownMessageTypeErrors Counter32, 1813 mplsLdpSessionStatsUnknownTlvErrors Counter32 1814 } 1816 mplsLdpSessionStatsUnknownMessageTypeErrors OBJECT-TYPE 1817 SYNTAX Counter32 1818 MAX-ACCESS read-only 1819 STATUS current 1820 DESCRIPTION 1821 "This object counts the number of Unknown Message Type 1822 Errors detected during this session. 1824 Discontinuities in the value of this counter can occur 1825 at re-initialization of the management system, and at 1826 other times as indicated by the value of 1827 mplsLdpSeeionDiscontinuityTime." 1828 ::= { mplsLdpSessionStatsEntry 1 } 1830 mplsLdpSessionStatsUnknownTlvErrors OBJECT-TYPE 1831 SYNTAX Counter32 1832 MAX-ACCESS read-only 1833 STATUS current 1834 DESCRIPTION 1835 "This object counts the number of Unknown TLV Errors 1836 detected during this session. 1838 Discontinuities in the value of this counter can occur 1839 at re-initialization of the management system, and at 1840 other times as indicated by the value of 1841 mplsLdpSeeionDiscontinuityTime." 1842 ::= { mplsLdpSessionStatsEntry 2 } 1844 -- 1845 -- Address Message/Address Withdraw Message Information 1846 -- 1847 -- This information is associated with a specific Session 1848 -- because Label Address Messages are sent after session 1849 -- initialization has taken place. 1851 -- 1853 mplsLdpSessionPeerAddressTable OBJECT-TYPE 1854 SYNTAX SEQUENCE OF MplsLdpSessionPeerAddressEntry 1855 MAX-ACCESS not-accessible 1856 STATUS current 1857 DESCRIPTION 1858 "This table 'extends' the mplsLdpSessionTable. 1859 This table is used to store Label Address Information 1860 from Label Address Messages received by this LSR from 1861 Peers. This table is read-only and should be updated 1862 when Label Withdraw Address Messages are received, i.e. 1863 Rows should be deleted as apropriate. 1865 NOTE: since more than one address may be contained 1866 in a Label Address Message, this table 'extends', 1867 rather than 'AUGMENTS' the mplsLdpSessionTable's 1868 information." 1869 ::= { mplsLdpSessionObjects 5 } 1871 mplsLdpSessionPeerAddressEntry OBJECT-TYPE 1872 SYNTAX MplsLdpSessionPeerAddressEntry 1873 MAX-ACCESS not-accessible 1874 STATUS current 1875 DESCRIPTION 1876 "An entry in this table represents information on 1877 session's for a single next hop address which was 1878 advertised in an Address Message from the LDP peer. 1879 The information contained in a row is read-only." 1880 INDEX { mplsLdpEntityLdpId, 1881 mplsLdpEntityIndex, 1882 mplsLdpPeerLdpId, 1883 mplsLdpSessionPeerAddressIndex 1884 } 1885 ::= { mplsLdpSessionPeerAddressTable 1 } 1887 MplsLdpSessionPeerAddressEntry ::= SEQUENCE { 1888 mplsLdpSessionPeerAddressIndex Unsigned32, 1889 mplsLdpSessionPeerNextHopAddressType AddressFamilyNumbers, 1890 mplsLdpSessionPeerNextHopAddress MplsLdpGenAddr 1891 } 1893 mplsLdpSessionPeerAddressIndex OBJECT-TYPE 1894 SYNTAX Unsigned32 (1..4294967295) 1895 MAX-ACCESS not-accessible 1896 STATUS current 1897 DESCRIPTION 1898 "An index which uniquely identifies this entry within 1899 a given session." 1900 ::= { mplsLdpSessionPeerAddressEntry 1 } 1902 mplsLdpSessionPeerNextHopAddressType OBJECT-TYPE 1903 SYNTAX AddressFamilyNumbers 1904 MAX-ACCESS read-only 1905 STATUS current 1906 DESCRIPTION 1907 "The internetwork layer address type of this Next Hop 1908 Address as specified in the Label Address Message 1909 associated 1910 with this Session. The value of this object indicates 1911 how to interpret the value of 1912 mplsLdpSessionPeerNextHopAddress." 1913 ::= { mplsLdpSessionPeerAddressEntry 2 } 1915 mplsLdpSessionPeerNextHopAddress OBJECT-TYPE 1916 SYNTAX MplsLdpGenAddr 1917 MAX-ACCESS read-only 1918 STATUS current 1919 DESCRIPTION 1920 "The value of the next hop address." 1921 REFERENCE 1922 "LDP Specification [18] defines only IPv4 for LDP Protocol 1923 Version 1, see section 3.4.3." 1924 ::= { mplsLdpSessionPeerAddressEntry 3 } 1926 -- 1927 -- The MPLS LDP Hello Adjacency Table 1928 -- 1930 mplsLdpHelloAdjacencyObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 1931 5 } 1933 mplsLdpHelloAdjacencyTable OBJECT-TYPE 1934 SYNTAX SEQUENCE OF MplsLdpHelloAdjacencyEntry 1935 MAX-ACCESS not-accessible 1936 STATUS current 1937 DESCRIPTION 1938 "A table of Hello Adjacencies for Sessions." 1939 ::= { mplsLdpHelloAdjacencyObjects 1 } 1941 mplsLdpHelloAdjacencyEntry OBJECT-TYPE 1942 SYNTAX MplsLdpHelloAdjacencyEntry 1943 MAX-ACCESS not-accessible 1944 STATUS current 1945 DESCRIPTION 1946 "Each row represents a single LDP Hello Adjacency. 1947 An LDP Session can have one or more Hello adjacencies." 1948 INDEX { mplsLdpEntityLdpId, 1949 mplsLdpEntityIndex, 1950 mplsLdpPeerLdpId, 1951 mplsLdpHelloAdjacencyIndex } 1952 ::= { mplsLdpHelloAdjacencyTable 1 } 1954 MplsLdpHelloAdjacencyEntry ::= SEQUENCE { 1955 mplsLdpHelloAdjacencyIndex Unsigned32, 1956 mplsLdpHelloAdjacencyHoldTimeRemaining TimeInterval, 1957 mplsLdpHelloAdjacencyType INTEGER 1958 } 1960 mplsLdpHelloAdjacencyIndex OBJECT-TYPE 1961 SYNTAX Unsigned32 (1..4294967295) 1962 MAX-ACCESS not-accessible 1963 STATUS current 1964 DESCRIPTION 1965 "An identifier for this specific adjacency." 1966 ::= { mplsLdpHelloAdjacencyEntry 1 } 1968 mplsLdpHelloAdjacencyHoldTimeRemaining OBJECT-TYPE 1969 SYNTAX TimeInterval 1970 MAX-ACCESS read-only 1971 STATUS current 1972 DESCRIPTION 1973 "The time remaining for this Hello Adjacency. 1974 This interval will change when the 'next' 1975 Hello message which corresponds to this 1976 Hello Adjacency is received." 1977 ::= { mplsLdpHelloAdjacencyEntry 2 } 1979 mplsLdpHelloAdjacencyType OBJECT-TYPE 1980 SYNTAX INTEGER { 1981 link(1), 1982 targeted(2) 1983 } 1984 MAX-ACCESS read-only 1985 STATUS current 1986 DESCRIPTION 1987 "This adjacency is the result of a 'link' 1988 hello if the value of this object is link(1). 1989 Otherwise, it is a result of a 'targeted' 1990 hello, targeted(2)." 1991 ::= { mplsLdpHelloAdjacencyEntry 3 } 1993 -- 1994 -- MPLS LDP LIB Table 1995 -- 1997 mplsLdpLibObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 6 } 1999 mplsLdpLibTable OBJECT-TYPE 2000 SYNTAX SEQUENCE OF MplsLdpLibEntry 2001 MAX-ACCESS not-accessible 2002 STATUS current 2003 DESCRIPTION 2004 "This table represents LIB (Label Information Base) 2005 Information. The table is read-only." 2006 ::= { mplsLdpLibObjects 1 } 2008 mplsLdpLibEntry OBJECT-TYPE 2009 SYNTAX MplsLdpLibEntry 2010 MAX-ACCESS not-accessible 2011 STATUS current 2012 DESCRIPTION 2013 "Each row represents a single LDP LIB entry." 2014 INDEX { mplsLdpLibLspId } 2015 ::= { mplsLdpLibTable 1 } 2017 MplsLdpLibEntry ::= SEQUENCE { 2018 mplsLdpLibLspId Unsigned32, 2019 mplsLdpLibLabelInIfIndex InterfaceIndex, 2020 mplsLdpLibLabelOutIfIndex InterfaceIndex, 2021 mplsLdpLibLabelType MplsLdpLabelTypes, 2022 mplsLdpLibInLabel MplsLabel, 2023 mplsLdpLibOutLabel MplsLabel 2024 } 2026 mplsLdpLibLspId OBJECT-TYPE 2027 SYNTAX Unsigned32 (1..4294967295) 2028 MAX-ACCESS not-accessible 2029 STATUS current 2030 DESCRIPTION 2031 "This number is used to uniquely identify this row, since 2032 this 2033 row is associated with a specific LSP, it may also be used 2034 to describe a unique number for an LSP. This number is 2035 used 2036 in the mplsLdpFecTable to identify which FECs or FEC is 2037 associated with this LIB entry." 2038 ::= { mplsLdpLibEntry 1 } 2040 mplsLdpLibLabelInIfIndex OBJECT-TYPE 2041 SYNTAX InterfaceIndex 2042 MAX-ACCESS read-only 2043 STATUS current 2044 DESCRIPTION 2045 "The ifIndex of the 'mplsLdpInLabel'." 2046 ::= { mplsLdpLibEntry 2 } 2048 mplsLdpLibLabelOutIfIndex OBJECT-TYPE 2049 SYNTAX InterfaceIndex 2050 MAX-ACCESS read-only 2051 STATUS current 2052 DESCRIPTION 2053 "The ifIndex of the 'mplsLdpOutLabel'." 2054 ::= { mplsLdpLibEntry 3 } 2056 mplsLdpLibLabelType OBJECT-TYPE 2057 SYNTAX MplsLdpLabelTypes 2058 MAX-ACCESS read-only 2059 STATUS current 2060 DESCRIPTION 2061 "The Layer 2 Label Type for 'mplsLdpInLabel' and 2062 'mplsLdpOutLabel'." 2063 ::= { mplsLdpLibEntry 4 } 2065 mplsLdpLibInLabel OBJECT-TYPE 2066 SYNTAX MplsLabel 2067 MAX-ACCESS read-only 2068 STATUS current 2069 DESCRIPTION 2070 "The incoming label of this LSP." 2071 ::= { mplsLdpLibEntry 5 } 2073 mplsLdpLibOutLabel OBJECT-TYPE 2074 SYNTAX MplsLabel 2075 MAX-ACCESS read-only 2076 STATUS current 2077 DESCRIPTION 2078 "The outgoing label of this LSP." 2079 ::= { mplsLdpLibEntry 6 } 2081 -- 2082 -- Mpls Ldp FEC Table 2083 -- 2085 mplsLdpFecTable OBJECT-TYPE 2086 SYNTAX SEQUENCE OF MplsLdpFecEntry 2087 MAX-ACCESS not-accessible 2088 STATUS current 2089 DESCRIPTION 2090 "This table represents the FEC 2091 (Forwarding Equivalence Class) 2092 Information associated with an LSP. 2093 The table is read-only." 2094 ::= { mplsLdpLibObjects 2 } 2096 mplsLdpFecEntry OBJECT-TYPE 2097 SYNTAX MplsLdpFecEntry 2098 MAX-ACCESS not-accessible 2099 STATUS current 2100 DESCRIPTION 2101 "Each row represents a single FEC Element." 2102 INDEX { mplsLdpFecType, 2103 mplsLdpFecAddressFamily, 2104 mplsLdpFecAddressLength, 2105 mplsLdpFecAddress } 2107 ::= { mplsLdpFecTable 1 } 2109 MplsLdpFecEntry ::= SEQUENCE { 2110 mplsLdpFecType INTEGER, 2111 mplsLdpFecAddressFamily AddressFamilyNumbers, 2112 mplsLdpFecAddressLength Integer32(0..255), 2113 mplsLdpFecAddress MplsLdpGenAddr, 2114 mplsLdpFecLspId Unsigned32 2115 } 2117 mplsLdpFecType OBJECT-TYPE 2118 SYNTAX INTEGER { 2119 prefix(1), 2120 hostAddress(2) 2121 } 2122 MAX-ACCESS not-accessible 2123 STATUS current 2124 DESCRIPTION 2125 "The type of the FEC. If the value of this object 2126 is 'prefix(1)' then the FEC type described by this 2127 row is for address prefixes. 2129 If the value of this object is 'hostAddress(2)' then 2130 the FEC type described by this row is a host address." 2131 ::= { mplsLdpFecEntry 1 } 2133 mplsLdpFecAddressFamily OBJECT-TYPE 2134 SYNTAX AddressFamilyNumbers 2135 MAX-ACCESS not-accessible 2136 STATUS current 2137 DESCRIPTION 2138 "The value of this object is from the Address Family 2139 Numbers." 2140 ::= { mplsLdpFecEntry 2 } 2142 mplsLdpFecAddressLength OBJECT-TYPE 2143 SYNTAX Integer32(0..255) 2144 MAX-ACCESS not-accessible 2145 STATUS current 2146 DESCRIPTION 2147 "If the value of 'mplsLdpFecType' is 'prefix(1)' 2148 then the value of this object is the length in 2149 bits of the address prefix represented by 2150 'mplsLdpFecAddress', or if the length is zero then 2151 this is a special value which indicates that the 2152 prefix matches all addresses. In this case the 2153 prefix is also zero (i.e. 'mplsLdpFecAddress' will 2154 have the value of zero.)" 2155 ::= { mplsLdpFecEntry 3 } 2157 mplsLdpFecAddress OBJECT-TYPE 2158 SYNTAX MplsLdpGenAddr 2159 MAX-ACCESS not-accessible 2160 STATUS current 2161 DESCRIPTION 2162 "If the value of 'mplsLdpFecType' is 'prefix(1)' 2163 then the value of this object is the address prefix. 2164 If the value of the 'mplsLdpFecAddressLength' 2165 is object is zero, then this object should also be 2166 zero." 2167 ::= { mplsLdpFecEntry 4 } 2169 mplsLdpFecLspId OBJECT-TYPE 2170 SYNTAX Unsigned32 (1..4294967295) 2171 MAX-ACCESS read-only 2172 STATUS current 2173 DESCRIPTION 2174 "This number represents the LSP which is related to 2175 this FEC. The value of this object should correspond 2176 to an entry in the MplsLdpLibTable, as denoted by 2177 the 'mplsLdpLibLspId' object. In other words, this 2178 object and the 'mplsLdpLibLspId' should have the same 2179 value." 2180 ::= { mplsLdpFecEntry 5 } 2182 --- 2183 --- Notifications 2184 --- 2186 mplsLdpNotificationPrefix OBJECT IDENTIFIER ::= 2187 { mplsLdpNotifications 0 } 2189 mplsLdpFailedInitSessionThresholdExceeded NOTIFICATION-TYPE 2190 OBJECTS { 2191 mplsLdpEntityFailedInitSessionThreshold 2192 } 2193 STATUS current 2194 DESCRIPTION 2195 "This notification is generated whenever the value 2196 of mplsLdpEntityFailedInitSessionThreshold is 2197 exceeded." 2198 ::= { mplsLdpNotificationPrefix 1 } 2200 mplsLdpPathVectorLimitMismatch NOTIFICATION-TYPE 2201 OBJECTS { 2202 mplsLdpEntityPathVectorLimit, 2203 mplsLdpPeerPathVectorLimit 2204 } 2205 STATUS current 2206 DESCRIPTION 2207 "This notification is generated when the value 2208 of mplsLdpSessionPathVectorLimit does NOT match 2209 the value of the mplsLdpPeerPathVectorLimit for 2210 the corresponding mplsLdpPeerEntry." 2211 REFERENCE 2212 "LDP Specification, Section 3.5.3." 2213 ::= { mplsLdpNotificationPrefix 2 } 2215 --******************************************************************** 2216 -- Module Conformance Statement 2218 --******************************************************************** 2220 mplsLdpGroups 2221 OBJECT IDENTIFIER ::= { mplsLdpConformance 1 } 2223 mplsLdpCompliances 2224 OBJECT IDENTIFIER ::= { mplsLdpConformance 2 } 2226 -- 2227 -- Compliance Statements 2228 -- 2230 mplsLdpModuleCompliance MODULE-COMPLIANCE 2231 STATUS current 2232 DESCRIPTION 2233 "The basic implentation requirements for agents that 2234 support 2235 the MPLS LDP MIB." 2236 MODULE -- this module 2237 MANDATORY-GROUPS { mplsLdpGeneralGroup, 2238 mplsLdpNotificationsGroup 2239 } 2240 GROUP mplsLdpAtmGroup 2241 DESCRIPTION 2242 "This group must be supported if ATM is used in the 2243 MPLS LDP implementation." 2245 GROUP mplsLdpFrameRelayGroup 2246 DESCRIPTION 2247 "This group must be supported if Frame Relay is used in the 2248 MPLS LDP implementation." 2249 ::= { mplsLdpCompliances 1 } 2251 -- units of conformance 2253 mplsLdpGeneralGroup OBJECT-GROUP 2254 OBJECTS { 2255 mplsLdpLsrId, 2256 mplsLdpLsrLabelRetentionMode, 2257 mplsLdpLsrLoopDetectionCapable, 2258 mplsLdpEntityIndexNext, 2259 mplsLdpEntityProtocolVersion, 2260 mplsLdpEntityAdminStatus, 2261 mplsLdpEntityOperStatus, 2262 mplsLdpEntityWellKnownDiscoveryPort, 2263 mplsLdpEntityMtu, 2264 mplsLdpEntityKeepAliveHoldTimer, 2265 mplsLdpEntityHelloHoldTimer, 2266 mplsLdpEntityFailedInitSessionThreshold, 2267 mplsLdpEntityControlMethod, 2268 mplsLdpEntityLabelDistributionMethod, 2269 mplsLdpEntityLoopDetectionForPV, 2270 mplsLdpEntityPathVectorLimit, 2271 mplsLdpEntityTargetedPeer, 2272 mplsLdpEntityTargetedPeerAddrType, 2273 mplsLdpEntityTargetedPeerAddr, 2274 mplsLdpEntityOptionalParameters, 2275 mplsLdpEntityRowStatus, 2276 mplsLdpAttemptedSessions, 2277 mplsLdpSessionRejectedNoHelloErrors, 2278 mplsLdpSessionRejectedAdvertisementErrors, 2279 mplsLdpSessionRejectedMaxPduErrors, 2280 mplsLdpSessionRejectedLabelRangeErrors, 2281 mplsLdpBadLdpIdentifierErrors, 2282 mplsLdpBadPduLengthErrors, 2283 mplsLdpBadMessageLengthErrors, 2284 mplsLdpBadTlvLengthErrors, 2285 mplsLdpMalformedTlvValueErrors, 2286 mplsLdpKeepAliveTimerExpiredErrors, 2287 mplsLdpShutdownNotifReceived, 2288 mplsLdpShutdownNotifSent, 2289 mplsLdpPeerLabelDistributionMethod, 2290 mplsLdpPeerLoopDetectionForPV, 2291 mplsLdpPeerPathVectorLimit, 2292 mplsLdpSessionState, 2293 mplsLdpSessionProtocolVersion, 2294 mplsLdpSessionKeepAliveHoldTimeRemaining, 2295 mplsLdpSessionMaxPduLength, 2296 mplsLdpSessionDiscontinuityTime, 2297 mplsLdpSessionStatsUnknownMessageTypeErrors, 2298 mplsLdpSessionStatsUnknownTlvErrors, 2299 mplsLdpSessionPeerNextHopAddressType, 2300 mplsLdpSessionPeerNextHopAddress, 2301 mplsLdpHelloAdjacencyHoldTimeRemaining, 2302 mplsLdpHelloAdjacencyType, 2303 mplsLdpLibLabelInIfIndex, 2304 mplsLdpLibLabelOutIfIndex, 2305 mplsLdpLibLabelType, 2306 mplsLdpLibInLabel, 2307 mplsLdpLibOutLabel, 2308 mplsLdpFecLspId 2310 } 2311 STATUS current 2312 DESCRIPTION 2313 "Objects that apply to all MPLS LDP implementations." 2314 ::= { mplsLdpGroups 1 } 2316 mplsLdpAtmGroup OBJECT-GROUP 2317 OBJECTS { 2318 mplsLdpEntityAtmMergeCap, 2319 mplsLdpEntityAtmLabelRangeComponents, 2320 mplsLdpEntityAtmVcDirectionality, 2321 mplsLdpEntityAtmLsrConnectivity, 2322 mplsLdpEntityDefaultControlVpi, 2323 mplsLdpEntityDefaultControlVci, 2324 mplsLdpEntityUnlabTrafVpi, 2325 mplsLdpEntityUnlabTrafVci, 2326 mplsLdpEntityAtmRowStatus, 2327 mplsLdpEntityConfAtmLabelRangeMaximumVpi, 2328 mplsLdpEntityConfAtmLabelRangeMaximumVci, 2329 mplsLdpEntityConfAtmLabelRangeRowStatus, 2330 mplsLdpSessionAtmLabelRangeUpperBoundVpi, 2331 mplsLdpSessionAtmLabelRangeUpperBoundVci 2333 } 2334 STATUS current 2335 DESCRIPTION 2336 "Objects that apply to all MPLS LDP implementations over 2337 ATM." 2338 ::= { mplsLdpGroups 2 } 2340 mplsLdpFrameRelayGroup OBJECT-GROUP 2341 OBJECTS { 2342 mplsLdpEntityFrMergeCap, 2343 mplsLdpEntityFrLabelRangeComponents, 2344 mplsLdpEntityFrVcDirectionality, 2345 mplsLdpEntityFrParmsRowStatus, 2346 mplsLdpConfFrMaximumDlci, 2347 mplsLdpConfFrLen, 2348 mplsLdpConfFrRowStatus, 2349 mplsLdpFrSessionMaxDlci, 2350 mplsLdpFrSessionLen 2351 } 2352 STATUS current 2353 DESCRIPTION 2354 "Objects that apply to all MPLS LDP implementations over 2355 Frame Relay." 2356 ::= { mplsLdpGroups 3 } 2358 mplsLdpNotificationsGroup NOTIFICATION-GROUP 2359 NOTIFICATIONS { mplsLdpFailedInitSessionThresholdExceeded, 2360 mplsLdpPathVectorLimitMismatch 2361 } 2362 STATUS current 2363 DESCRIPTION 2364 "The notification(s) which an MPLS LDP implemention 2365 is required to implement." 2366 ::= { mplsLdpGroups 4 } 2368 END 2370 5. Revision History 2372 This section should be removed when this document is published as an 2373 RFC. 2375 5.1. Changes from 2377 Reworded the description of the mplsLdpAtmSessionTable to clarify 2378 that one or MORE label range intersection(s) is/are represented in 2379 this table. 2381 Reworded the description of the mplsLdpFrameRelaySessionTable to 2382 clarify that one or MORE label range intersection(s) is/are 2383 represented in this table. 2385 Added a new index, mplsLdpSessionPeerIndex, to the 2386 mplsLdpSessionPeerAddressTable. This new index uniquely identifies 2387 the entry within a given session. (Since adding 2388 mplsLdpSessionPeerNextHopAddressType, 2389 mplsLdpSessionPeerNextHopAddress to the INDEX clause of the 2390 mplsLdpSessionPeerAddressTable leaves a table with only indices and 2391 no objects, the work around was to add a new index which uniquely 2392 differentiates an entry within a given session.) 2394 Quite a few changes to the mplsLdpPeerTable. First, removed the 2395 mplsLdpPeerIndex from the mplsLdpPeerTable and other tables. This 2396 index served no purpose, so was removed. Second, removed the 2397 objects: mplsLdpPeerInternetworkAddrType, and 2398 mplsLdpPeerInternetworkAddr. Third, reworded the description of this 2399 table to include information which is known during Session 2400 Intialization attempts, the specific information has to do with Loop 2401 Dection based on Path Vectors. Since Section 3.5.3 of the LDP Spec 2402 when describing the PVLim says: "Although knowledge of a peer's path 2403 vector limit will not change an LSR's behavior, it does enable the 2404 LSR to alert an operator to a possible misconfiguration." and the 2405 object mplsLdpPeerPathVectorLimit is sent as a varbind in the 2406 mplsLdpPathVectorLimitMismatch notification. 2408 Removed the mplsLdpPeerIndex from the mplsLdpHelloAdjacencyTable. 2410 Removed the "IANA Address Family Numbers MIB" section. 2412 Updated the boiler.me from the ops web page dated Weds., Dec 22, 2413 1999. 2415 Updated the Security Section from the ops web page. 2417 Added the following objects to the mplsLdpEntityTable: 2418 mplsLdpEntityControlMethod, mplsLdpEntityLoopDectionForPV, and 2419 mplsLdpEntityPathVectorLimit. 2421 Removed mplsLdpSessionLabelAdvertisement, 2422 mplsLdpSessionLoopDetectionForPV, and mplsLdpSessionPathVectorLimit 2423 from the mplsLdpSessionTable. 2425 Changed the mplsLdpPathVectorLimitMismatch Notification to send 2426 mplsLdpEntityPathVectorLimit (instead of 2427 mplsLdpSessionPathVectorLimit). 2429 Copied the MplsLabel TC from draft-ietf-mpls-lsr-mib-00.txt and 2430 replaced the MplsLdpGenAddr for mplsLdpLibInLabel and 2431 mpslLdpLibOutLabel with MplsLabel. 2433 The mplsLdpSessionIndex was removed throughout the MIB. This was 2434 replaced by the object mplsLdpSessionDiscontinuityTime. The 2435 motivation was to reduce the number of indices. 2437 The descriptions for the objects in the mplsLdpSessionStatsTable, 2438 mplsLdpSessionStatsUnknownMessageTypeErrors and 2439 mplsLdpSessionStatsUnknownTlvErrors, have been updated to include a 2440 reference to the mplsLdpSessionDiscontinuityTime object. 2442 5.2. Changes from 2444 Added Scalar Objects: mplsLdpLsrLoopDetectionPresent, and 2445 mplsLdpEntityIndexNext. 2447 Added the following objects to the mplsLdpEntityTable: 2448 mplsLdpEntityProtocolVersion, mplsLdpEntityAdminStatus, 2449 mplsLdpEntityOperStatus, mplsLdpEntityTargetedPeer, 2450 mplsLdpEntityTargetedPeerAddrType, mplsLdpEntityTargetedPeerAddr, and 2451 mplsLdpEntityHelloHoldTimer. 2453 Changed the description of the mplsLdpEntityAtmParmsTable and added 2454 the following objects to this table: 2455 mplsLdpEntityAtmLsrConnectivity, mplsLdpEntityDefaultControlVpi, 2456 mplsLdpEntityDefaultControlVci, mplsLdpEntityUnlabTrafVpi, and 2457 mplsLdpEntityUnlabTrafVci. NOTE: the last four objects were in 2458 Version 01 of the MIB but were mistakenly omitted from Version 02. 2459 Now, they are back. 2461 Changed the indexing of the mplsLdpEntityConfAtmLabelRangeTable to 2462 include the minimum VPI/VCI. This is to ensure that indices in this 2463 table are unique. 2465 Changed the indexing of the mplsLdpEntityConfFrLabelRangeTable, to 2466 include the minimum DLCI value. This is to ensure that indices in 2467 this table are unique. 2469 Added [32] to Reference Section. 2471 5.3. Changes from 2473 The MIB was updated to correspond to draft-ietf-mpls-ldp-06.txt of 2474 the LDP Specification [18]. 2476 The front section was updated. 2478 The MIB was made to be less ATM-centric. Essentially, the ATM 2479 specific objects where removed from the tables and placed in ATM 2480 specific Tables. A "type" was added to the "base" tables and a row 2481 is to be created in the ATM/FR/etc. "type" table. Apropos 2482 compliance statements were added to reflect the separation of ATM and 2483 Frame Relay objects into their respective tables. 2485 Objects for Loop Detection were removed from describing the LDP 2486 implementation (i.e. the scalars were removed) and Loop Dection 2487 objects were added to the Session Table. (Although as the LDP 2488 Specification indicates loop detection should be for an LSR within a 2489 domain.) 2491 The following tables were added: mplsLdpEntityAtmParmsTable, 2492 mplsLdpEntityConfAtmLabelRangeTable, mplsLdpFrameRelayParmsTable, 2493 mplsLdpConfFrLabelRangeTable, mplsLdpAtmSessionTable, 2494 mpslLdpFrameRelaySessionTable, mplsLdpSessionPeerAddressTable, 2495 mplsLdpLibTable, and the mplsLdpFecTable. 2497 The following notifications were added: notification for Session 2498 removal. 2500 The following objects were removed from the Session Table: 2501 mplsLdpSessionRole was removed (this can be determined by comparing 2502 LSR Ids and does not need to be explicitely in the MIB.) ATM 2503 specific objects (mplsLdpSessionAtmLabelRangeLowerBoundVpi 2504 mplsLdpSessionAtmLabelRangeLowerBoundVci, 2505 mplsLdpSessionAtmLabelRangeUpperBoundVpi 2506 mplsLdpSessionAtmLabelRangeUpperBoundVci) were removed and put into a 2507 separate table. Frame Relay objects were added in a separate table. 2509 Hello Adjacency Table was updated. 2511 The objects, mplsLdpSessionRejectedParamErrors, 2512 mplsLdpSessionRejectedNoHelloErrors, mplsLdpBadLdpIdentifierErrors, 2513 mplsLdpBadPduLengthErrors, mplsLdpBadMessageLengthErrors, 2514 mplsLdpBadTlvLengthErrors, mplsLdpMalformedTlvValueErrors, 2515 mplsLdpKeepAliveTimerExpiredErrors, mplsLdpShutdownNotifReceived, and 2516 mplsLdpShutdownNotifSent were added to the mplsLdpEntityStatsTable. 2518 The mplsLdpSessionStatsTable was added to count statics based on a 2519 per Session basis. 2521 The mplLdpPeerConfAtmLabelRangeTable has been removed. There is no 2522 need to configure information for a Peer. All information for a peer 2523 is learned, thus peer information is read-only. 2525 (Editorial) References were updated to reflect the documents which 2526 this version was based on. 2528 5.4. Changes from 2530 Textual conventions were added for the LSR Identifier and the LDP 2531 Identifier. 2533 Top-level mib structure was added. The LDP MIB falls under a proposed 2534 hierarchy of mpls.mplsProtocols. 2536 The mib hierarchy within the LDP MIB was also changed. A new branch, 2537 under mpls.mplsProtocols.mplsLdpMIB.mplsLdpObjects was added. This 2538 branch is mplsLdpLsrObjects. Currently, this contains several new 2539 scalar objects: mplsLdpLsrID, mplsLdpLsrLoopDetectionPresent, 2540 mplsLdpLsrLoopDetectinAdminStatus, mplsLdpLsrPathVectorLimit, 2541 mplsLdpLsrHopCountLimit, mplsLdpLsrLoopPreventionPresent, 2542 mplsLdpLsrLoopPreventionAdminStatus, and 2543 mplsLdpLsrLabelRetentionMode. 2545 mplsLdpEntityTable is now indexed by mplsLdpEntityIdentifier, which 2546 is the LDP Identifier used in Session establishment. 2547 mplsLdpEntityLoopDetection and mplsLdpEntityLoopPrevention objects 2548 were removed from this table. 2550 The following objects were added to the mplsLdpEntityTable: 2551 mplsLdpEntityLabelSpaceType, mplsLdpEntityUnlabTrafVpi, 2552 mplsLdpEntityUnlabTrafVci, mplsLdpEntityMergeCapability, 2553 mplsLdpEntityVcDirectionality, and 2554 mplsLdpEntityLabelDistributionMethod. 2556 The following objects were added to the mplsLdpPeerEntityTable: 2557 mplsLdpPeerLabelDistributionMethod. 2559 The following object was removed from the mplsLdpEntityStatsTable: 2560 mplsLdpEntityEstablishedSessions. 2562 References were added and revised. 2564 6. TO DO List 2566 This section should be removed when this document is published as an 2567 RFC. This section outlines the next areas the authors intend to 2568 address in subsequent revisions. 2570 o Remove the following sections prior to final publication: 2571 Revisions Section and this (TO DO List) Section. 2573 o Need to save all Labels in the LIB (not just ones used in 2574 forwarding) from Bob Thomas. 2576 o Updates as suggested by review of working group. 2578 7. Acknowledgments 2580 The authors would like to thank the following people: Leigh 2581 McLellan, Geetha Brown, Geping Chen and Charlan Zhou from Nortel 2582 Networks, and Zoltan Takacs and Bo Augustsson from Ericsson. 2584 8. References 2586 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 2587 for Describing SNMP Management Frameworks", RFC 2571, April 2588 1999. 2590 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 2591 of Management Information for TCP/IP-based Internets", STD 2592 16, RFC 1155, May 1990. 2594 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 2595 16, RFC 1212, March 1991. 2597 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 2598 SNMP", RFC 1215, March 1991. 2600 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2601 Rose, M., and S. Waldbusser, "Structure of Management 2602 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 2603 1999. 2605 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2606 Rose, M., and S. Waldbusser, "Textual Conventions for 2607 SMIv2", STD 58, RFC 2579, April 1999. 2609 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2610 Rose, M., and S. Waldbusser, "Conformance Statements for 2611 SMIv2", STD 58, RFC 2580, April 1999. 2613 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 2614 Network Management Protocol", STD 15, RFC 1157, May 1990. 2616 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2617 "Introduction to Community-based SNMPv2", RFC 1901, January 2618 1996. 2620 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2621 "Transport Mappings for Version 2 of the Simple Network 2622 Management Protocol (SNMPv2)", RFC 1906, January 1996. 2624 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 2625 Processing and Dispatching for the Simple Network Management 2626 Protocol (SNMP)", RFC 2572, April 1999. 2628 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 2629 (USM) for version 3 of the Simple Network Management 2630 Protocol (SNMPv3)", RFC 2574, April 1999. 2632 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2633 "Protocol Operations for Version 2 of the Simple Network 2634 Management Protocol (SNMPv2)", RFC 1905, January 1996. 2636 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 2637 RFC 2573, April 1999. 2639 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 2640 Access Control Model (VACM) for the Simple Network 2641 Management Protocol (SNMP)", RFC 2575, April 1999. 2643 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 2644 "Introduction to Version 3 of the Internet-standard Network 2645 Management Framework", RFC 2570, April 1999. 2647 [17] Narten, T., and H. Alvestrand, "Guidelines for Writing an IANA 2648 Considerations Section in RFCs.", RFC 2434, IBM, Maxware, October 2649 1998 2651 [18] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and Thomas, 2652 B., "LDP Specification.", draft-ietf-mpls-ldp-06.txt, Nortel 2653 Networks, Ennovate Networks, IBM, Nortel Networks, Cisco Systems 2654 October 1999 2656 [19] Callon, R., Doolan, P., Feldman, N., Fredette, A., Swallow, G., and 2657 A. Viswanathan, "A Framework for Multiprotocol Label Switching", 2658 draft-ietf-mpls-framework-04.txt, IronBridge Networks, Ennovate 2659 Networks, IBM, Nortel Networks, Cisco Systems, July 1999. 2661 [20] Rosen, E., Viswananthan, A., and R. Callon, "Multiprotocol Label 2662 Switching Architecture", draft-ietf-mpls-arch-06.txt, Cisco 2663 Systems, Lucent Technologies, and IronBridge Networks, August 1999. 2665 [21] Jamoussi, B., editor, "Constraint-Based LSP Setup using LDP", 2666 draft-ietf-mpls-cr-ldp-02.txt, August 1999. 2668 [22] Bradner, S., "Key words for use in RFCs to Indicate Requirement 2669 Levels", BCP 14, RFC 2119, Harvard University, March 1997 2671 [23] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, 2672 RFC 2026, Harvard University, October 1996 2674 [24] Srinivansan, C., and A. Viswanathan, "MPLS Traffic Engineering 2675 Management Information Base Using SMIv2", draft-ietf-mpls-te-mib- 2676 01.txt, Lucent Technologies, June 1999. 2678 [25] Srinivansan, C., and A. Viswanathan, "MPLS Label Switch Router 2679 Management Information Base Using SMIv2", draft-ietf-mpls-lsr-mib- 2680 00.txt, Lucent Technologies, June 1999. 2682 [26] Greene, M., J. Cucchiara, J. Luciani, "Definition of Managed 2683 Objects for the NBMA Next Hop Resolution Protocol (NHRP)", RFC 2684 2677, August 1999. 2686 [27] Internet Assigned Numbers Authority (IANA), ADDRESS FAMILY NUMBERS, 2687 (http://www.isi.edu/in-notes/iana/assignements/address-family- 2688 numbers), for MIB 2689 (ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib). 2691 [28] Noto, M., E. Spiegel, K. Tesink, "Definition of Textual Conventions 2692 and OBJECT-IDENTITIES for ATM Management", RFC 2514, February 1999. 2694 [29] McCloghrie, K., F. Kastenholz, "The Interfaces Group MIB using 2695 SMIv2", RFC 2233, November 1997. 2697 [30] Tesink, K. (ed.) "Definitions of Managed Objects for ATM 2698 Management", RFC 2515, February 1999. 2700 [31] Grossman, D., and J. Heinanen, "Multiprotocol Encapsulation over 2701 ATM Adaptation Layer 5", RFC 2684, September 1999. 2703 [32] Davie, B., J. Lawrence, K. McCloghrie, Y. Rekhter, E. Rosen, G. 2704 Swallow, and P. Doolan, "MPLS using LDP and ATM VC Switching", 2705 draft-ietf-mpls-atm-02.txt, April 1999. 2707 9. Security Considerations 2709 There are a number of management objects defined in this MIB that have a 2710 MAX-ACCESS clause of read-write and/or read-create. Such objects may 2711 be considered sensitive or vulnerable in some network environments. 2712 The support for SET operations in a non-secure environment without 2713 proper protection can have a negative effect on network operations. 2715 There are a number of managed objects in this MIB that may contain 2716 sensitive information. These are contained in the mplsLdpEntityTable. 2717 The objects contained in this table are responsible for setting up or 2718 tearing down LSPs. 2720 It is thus important to control even GET access to these objects and 2721 possibly to even encrypt the values of these object when sending them 2722 over the network via SNMP. Not all versions of SNMP provide features 2723 for such a secure environment. 2725 SNMPv1 by itself is not a secure environment. Even if the network 2726 itself is secure (for example by using IPSec), even then, there is no 2727 control as to who on the secure network is allowed to access and 2728 GET/SET (read/change/create/delete) the objects in this MIB. 2730 It is recommended that the implementers consider the security 2731 features as provided by the SNMPv3 framework. Specifically, the use 2732 of the User-based Security Model RFC 2574 [RFC2574] and the View- 2733 based Access Control Model RFC 2575 [RFC2575] is recommended. 2735 It is then a customer/user responsibility to ensure that the SNMP 2736 entity giving access to an instance of this MIB, is properly 2737 configured to give access to the objects only to those principals 2738 (users) that have legitimate rights to indeed GET or SET 2739 (change/create/delete) them. 2741 10. Authors' Addresses 2743 James V. Luciani 2744 Nortel Networks 2745 600 Technology Park Drive 2746 Billerica, MA 01821 2747 Phone: (978) 288-4734 2748 Email: jluciani@nortelnetworks.com 2750 Hans Sjostrand 2751 Ericsson 2752 Business Unit Datacom Networks and IP Services 2753 S-126 25 Stockholm, Sweden 2754 Phone: +46 8 719 9960 2755 Email: hans.sjostrand@etx.ericsson.se 2757 Joan Cucchiara 2758 Brix Networks 2759 300 Concord Ave. 2760 Billerica, MA 01821 2761 Phone: (978) 439-1523 2762 Email: jcucchiara@brixnet.com 2764 11. Full Copyright Statement 2766 Copyright (C) The Internet Society (1999). All Rights Reserved. 2768 This document and translations of it may be copied and furnished to 2769 others, and derivative works that comment on or otherwise explain it 2770 or assist in its implementation may be prepared, copied, published 2771 and distributed, in whole or in part, without restriction of any 2772 kind, provided that the above copyright notice and this paragraph are 2773 included on all such copies and derivative works. However, this 2774 document itself may not be modified in any way, such as by removing 2775 the copyright notice or references to the Internet Society or other 2776 Internet organizations, except as needed for the purpose of 2777 developing Internet standards in which case the procedures for 2778 copyrights defined in the Internet Standards process must be 2779 followed, or as required to translate it into languages other than 2780 English. 2782 The limited permissions granted above are perpetual and will not be 2783 revoked by the Internet Society or its successors or assigns. 2785 This document and the information contained herein is provided on an 2786 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2787 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2788 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2789 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2790 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.