idnits 2.17.1 draft-ietf-mpls-ldp-mib-10.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 98 instances of too long lines in the document, the longest one being 12 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 4402 has weird spacing: '...ndex is creat...' == Line 4596 has weird spacing: '...entence s/ini...' == Line 5163 has weird spacing: '... (Since addin...' == Line 5751 has weird spacing: '...for the purpo...' == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- 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 (April 2003) is 7653 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) == Missing Reference: 'RFC2434' is mentioned on line 5672, but not defined ** Obsolete undefined reference: RFC 2434 (Obsoleted by RFC 5226) == Unused Reference: 'RFC3037' is defined on line 5389, but no explicit reference was found in the text == Unused Reference: 'RFC3215' is defined on line 5392, but no explicit reference was found in the text == Unused Reference: 'RFC2115' is defined on line 5405, but no explicit reference was found in the text == Unused Reference: 'RFC2514' is defined on line 5408, but no explicit reference was found in the text == Unused Reference: 'RFC2515' is defined on line 5412, but no explicit reference was found in the text == Unused Reference: 'RFC3291' is defined on line 5421, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1700 (Obsoleted by RFC 3232) ** Obsolete normative reference: RFC 3036 (Obsoleted by RFC 5036) ** Downref: Normative reference to an Informational RFC: RFC 3037 ** Downref: Normative reference to an Informational RFC: RFC 3215 == Outdated reference: A later version (-14) exists of draft-ietf-mpls-lsr-mib-08 == Outdated reference: A later version (-10) exists of draft-ietf-mpls-tc-mib-06 -- Obsolete informational reference (is this intentional?): RFC 3291 (Obsoleted by RFC 4001) == Outdated reference: A later version (-09) exists of draft-ietf-mpls-mgmt-overview-03 Summary: 8 errors (**), 0 flaws (~~), 17 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group J. Cucchiara 2 Internet-Draft Artel 3 Expires October 2003 H. Sjostrand 4 IP Unplugged 5 J. Luciani 6 Consultant 7 April 2003 9 Definitions of Managed Objects for 10 the Multiprotocol Label Switching, Label Distribution Protocol (LDP) 12 14 Status of this Memo 16 This document is an Internet-Draft and is in full conformance with 17 all provisions of Section 10 of RFC 2026. Internet-Drafts are 18 working documents of the Internet Engineering Task Force (IETF), its 19 areas, and its working groups. Note that other groups may also 20 distribute working documents as Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress". 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html 33 Distribution of this document is unlimited. Please send comments to 34 the Multiprotocol Label Switching (mpls) Working Group, mpls@uu.net. 36 Copyright Notice 38 Copyright (C) The Internet Society (2003). All Rights Reserved. 40 Abstract 42 This memo defines a portion of the Management Information Base (MIB) 43 for use with network management protocols in the Internet community. 44 In particular, it describes managed objects for the Multiprotocol 45 Label Switching, Label Distribution Protocol (LDP). 47 Table of Contents 49 1 Introduction ................................................. 3 50 2 The Internet-Standard Management Framework ................... 3 51 3 Structure of the MIB ......................................... 4 52 3.1 Overview ................................................... 4 53 3.2 Future Considerations ...................................... 4 54 3.3 Interface Indexing ......................................... 5 55 3.4 Differences from the LDP Specification ..................... 5 56 3.5 The MPLS-LDP-MIB Module .................................... 5 57 3.5.1 The LDP Entity Table ..................................... 6 58 3.5.1.1 Changing Values After Session Establishment ............ 6 59 3.5.2 The LDP Entity Statistics Table .......................... 7 60 3.5.3 The LDP Peer Table ....................................... 7 61 3.5.4 The LDP Session Table .................................... 8 62 3.5.5 The LDP Session Statistics Table ......................... 8 63 3.5.6 The LDP Hello Adjacencies Table .......................... 8 64 3.5.7 The LDP LSP Table ........................................ 8 65 3.5.8 The FEC Table ............................................ 9 66 3.5.9 The LDP Session Peer Address Table ....................... 9 67 3.6 LDP Notifications .......................................... 10 68 4 MPLS Label Distribution Protocol MIB Definitions ............. 10 69 4.1 The MPLS-LDP-ATM-MIB Module ................................ 62 70 4.1.1 The LDP ATM Session Table ................................ 63 71 4.2 The MPLS-LDP-FRAME-RELAY-MIB Module ........................ 80 72 4.2.1 The LDP Frame Relay Session Table ........................ 80 73 4.3 The MPLS-LDP-GENERIC-MIB Module ............................ 94 74 5 Revision History ............................................. 103 75 5.1 Changes from .............. 103 76 5.1.1 Changes based on MIB Doctor Review Comments .............. 103 77 5.2 Changes from .............. 108 78 5.3 Changes from .............. 110 79 5.4 Changes from .............. 111 80 5.5 Changes from .............. 112 81 5.6 Changes from .............. 114 82 5.7 Changes from .............. 116 83 5.8 Changes from .............. 117 84 5.9 Changes from .............. 118 85 5.10 Changes from ............. 119 86 6 Acknowledgments .............................................. 120 87 7 Normative References ......................................... 121 88 8 Informative References ....................................... 123 89 9 Security Considerations ...................................... 123 90 9.1 Security Considerations for MPLS-LDP-MIB ................... 123 91 9.2 Security Considerations for MPLS-LDP-ATM-MIB ............... 125 92 9.3 Security Considerations for MPLS-LDP-FRAME-RELAY-MIB ....... 126 93 9.4 Security Considerations for MPLS-LDP-GENERIC-MIB ........... 127 94 10 IANA Considerations ......................................... 128 95 10.1 IANA Considerations for the MPLS-LDP-MIB Module ........... 129 96 10.2 IANA Considerations for the MPLS-LDP-ATM-MIB Module ....... 129 97 Module .................................................... 129 98 ........................................................... 129 99 11 Intellectual Property Notice ................................ 129 100 12 Authors' Addresses .......................................... 130 101 13 Full Copyright Statement .................................... 130 103 1. Introduction 105 This document defines 4 MIB Modules which together support the 106 configuration and monitoring of the Label Distribution Protocol 107 (LDP). The Label Distribution Protocol (LDP) [RFC3036] is one type 108 of Multiprotocol Label Switching (MPLS) protocols described in 109 [RFC3031] and [RFC3032]. Utilizing all 4 MIB Modules allows an 110 operator to configure LDP sessions using 3 different Layer 2 media. 111 The Layer 2 media supported by the MIB Modules are Ethernet, ATM and 112 Frame Relay as described in [RFC3036], [RFC3034] and [RFC3035]. 114 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 115 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 116 document are to be interpreted as described in RFC 2119 [RFC2119]. 118 2. The Internet-Standard Management Framework 120 For a detailed overview of the documents that describe the current 121 Internet-Standard Management Framework, please refer to section 7 of 122 RFC 3410 [RFC3410]. 124 Managed objects are accessed via a virtual information store, termed 125 the Management Information Base or MIB. MIB objects are generally 126 accessed through the Simple Network Management Protocol (SNMP). 127 Objects in the MIB are defined using the mechanisms defined in the 128 Structure of Management Information (SMI). This memo specifies a MIB 129 module that is compliant to the SMIv2, which is described in STD 58, 130 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 131 [RFC2580]. 133 3. Structure of the MIB 135 This section describes the structure of the LDP MIB. 137 3.1. Overview 139 There are 4 MIB Modules in this document. These MIB Modules are the 140 MPLS-LDP-MIB, the MPLS-LDP-GENERIC-MIB, the MPLS-LDP-ATM-MIB and the 141 MPLS-LDP-FRAME-RELAY-MIB. The MPLS-LDP-MIB defines objects which are 142 common to all LDP implementations. The MPLS-LDP-GENERIC-MIB defines 143 Layer 2 Per Platform Label Space objects for use with the MPLS-LDP- 144 MIB. The MPLS-LDP-ATM-MIB defines Layer 2 Asynchronous Transfer Mode 145 (ATM) objects for use with the MPLS-LDP-MIB. The MPLS-LDP-FRAME- 146 RELAY-MIB defines Layer 2 FRAME-RELAY objects for use with the MPLS- 147 LDP-MIB. 149 The MPLS-LDP-MIB Module MUST be implemented and at least one of the 150 Layer 2 MIB Modules MUST be implemented. As an example, if an LSR 151 implementation wants to support LDP utilizing a Layer 2 of Ethernet, 152 then the MPLS-LDP-MIB and the MPLS-LDP-GENERIC-MIB Modules would be 153 implemented. If an LSR implementation wants to support LDP utilizing 154 a Layer 2 of ATM, then the MPLS-LDP-MIB Module MUST be implemented 155 and the MPLS-LDP-ATM-MIB Module would be implemented. If an LSR 156 implementation wants to support LDP utilizing a Layer 2 of FRAME- 157 RELAY, then the MPLS-LDP-MIB Module would be implemented and the 158 MPLS-LDP-FRAME-RELAY-MIB Module would be implemented. An LDP 159 implementation that utilizes all 3 Layer 2 media (Ethernet, Frame- 160 Relay, ATM) would support all 4 MIB Modules. Each of the Modules 161 will be discussed in detail in the following sections. 163 There are 2 Compliance statements for each MIB Module. One which is 164 for FULL Compliance which includes configuration and monitoring via 165 SNMP. The other is a READ-ONLY Compliance which is only monitoring 166 via SNMP. 168 3.2. Future Considerations 170 The LDP Specification [RFC3036] does not specify the use of VPNs or 171 multicast for LDP, and thus, objects related to these areas have not 172 been included in the MIB. 174 This MIB does not include VP merge configuration either. [RFC2684] 175 does not yet describe this capability and so it has been excluded 176 from the MIB. 178 These areas need to be specified in the LDP Specification or other 179 specifications prior to being added in this or any other MIB. 181 3.3. Interface Indexing 183 Interface Indexes as specified in [RFC2863] are used in the MIB. The 184 descriptions of the ifIndexes denote which ifIndex is being used. 185 NOTE: the use of ifIndex is for actual existing connections. 187 3.4. Differences from the LDP Specification 189 Currently, there are 3 differences between this specification and the 190 LDP Specification. As previously mentioned, this MIB is almost 191 entirely based on the LDP specification. The differences are 192 documented here in the hope to avoid any confusion between the two 193 documents. 195 The first difference is that the LDP Entity Table contains some 196 DEFVAL clauses which are not specified explicitly in the LDP 197 Specification. These values, although not documented in the LDP 198 Specification are widely used by existing LDP MIB implementations and 199 thus, have been adopted within this MIB. Please note, they can 200 certainly be changed during row creation or a subsequent set request. 202 A second difference is the mplsLdpEntityConfGenericLabelRangeTable. 203 This table, although provided as a way to reserve a range of generic 204 labels, does not exist in the LDP Specification. It was added to the 205 MIB due to a request from the working group and because this table 206 was considered useful for reserving a range of generic labels. 208 The third difference is documented by the TEXTUAL-CONVENTION, 209 MplsAtmVcIdentifier which is in the MPLS-TC-MIB [MPLSTCMIB]. This TC 210 was added to restrict vci values to be greater than 31 as described 211 in RFC 3035 [RFC3035]. 213 3.5. The MPLS-LDP-MIB Module 215 This MIB Module contains objects which are common to all LDP 216 implementations. This MIB Module MUST always be implemented along 217 with one or more of the Layer 2 MIB Modules. 219 NOTE, this table allows the Label Edge Router (LER) or the Label 220 Switching router (LSR) to initiate and/or receive requests to 221 establish LDP sessions. As the LDP protocol distributes labels and 222 establishes sessions with Peers most of the tables in this MIB are 223 populated by the agent as instructed by the LDP protocol. The 224 exception is the mplsFecTable and the mplsLdpLspFecTable which can be 225 configured by the operator to specify Forwarding Equivalence Class 226 information for an LSP. 228 Each table in this MIB Module is described in the following 229 subsections. 231 3.5.1. The LDP Entity Table 233 The MPLS-LDP-MIB provides objects to configure/set-up potential LDP 234 sessions on a specific LSR. The mplsLdpEntityTable is used to 235 configure potential LDP Sessions, where each row in the table 236 represents a potential LDP Session. 238 Each entry/row in this table represents a single LDP Entity. There 239 is no maximum number of LDP Entities specified. However, there is an 240 mplsLdpEntityIndexNext object which should be retrieved by the 241 command generator prior to creating an LDP Entity. If the 242 mplsLdpEntityIndexNext object is zero, this indicates that the LSR is 243 not able to create another LDP Entity at that time. 245 3.5.1.1. Changing Values After Session Establishment 247 One way to manually modify a session's parameters is by using SNMP to 248 change the MIB objects related to that session. Please note special 249 care should be taken if MIB objects which are used in the MPLS LDP 250 Session Initialization need to be modified. If the modification of 251 any of these MIB variables takes place anytime after the start of 252 session intialization, then the entire session must be halted. Any 253 information learned by that session must be discarded. The objects 254 should then be modified, and session initialization started. 256 For example, assume that an operator wishes to change the 257 configuration of a Label Range which is used by a Session that has 258 already been established. The operator should change the 259 mplsLdpEntityAdminStatus to "disable(2)". Setting the 260 mplsLdpEntityAdminStatus to "disable(2)" will cause the session to be 261 torn down (i.e. this will signal to LDP that it should send out tear 262 down messages for that session). Also, all information related to 263 that session should be removed from this MIB by the Agent. This 264 includes Peer information (i.e. relevant row in the mplsPeerTable) 265 and Session statistics (i.e. releveant row in the mplsLdpSesTable). 266 Also, if the LSR MIB is implemented and the optional Mapping Table 267 objects are implemented, then all information related to the LSPs in 268 this session should be removed from these MIBs. [For more information 269 please see the section on "The Mapping Tables".] At this point, the 270 operator could modify the Label Range. Lastly, the operator should 271 set the mplsLdpEntityAdminStatus to "enable(1)". At this point 272 session initialization should occur. The LDP Entity goes through the 273 Session Initialization in order to communicate the new Label Ranges 274 to the Peer and establish new LSPs. 276 3.5.2. The LDP Entity Statistics Table 278 The mplsLpdEntityStatsTable is a read-only table which contains 279 statistical information related to failed attempts to establish 280 sessions. Each row in this table is related to a single LDP entity 281 and this table AUGMENTS an mplsLdpEntityEntry. This table could be 282 used to give insight into how to reconfigure values so that a session 283 could be successfully established. For example, if the 284 mplsLdpSesRejectedLRErrors Counter object was increasing, then this 285 would indicate that the Label Range (LR) may need to be adjusted. 287 3.5.3. The LDP Peer Table 289 The LDP Peer Table is a read-only table which contains information 290 about LDP Peers known to LDP Entities. In other words, the Peer 291 information is learned by LDP through initialization or discovery. 292 This table should be populated by the agent as directed by the LDP 293 protocol. 295 A row in this table is related to one or more rows in the Hello 296 Adjacency Table and related to a single row in the Session Table. 297 The values in the Peer table are specific to a Peer and may or may 298 not be the same values used in the session. The reason is that the 299 Peer and Entity negotiate certain values. The Entity's values are 300 configured in the mplsLdpEntityTable and the Peer's values are 301 learned (and placed into the mplsLdpPeerTable). The 302 mplsLdpSessionTable shows the values used in establishing the 303 session. 305 One example, of when the Peer's values and the Session's values may 306 differ is with the Peer's Path Limit information. The Peer's Path 307 Limit information is learned from the session initialization phase. 308 The actual value for the Path Vector Limit is the Peer's value and 309 may not be the same value that appears in the session. There could 310 be a mismatch in this value between the Entity and the Peer. In the 311 event of a mismatch, then the session will use the Path Limit set by 312 the Entity (and not the Peer). 314 The Peer Table information was placed in a separate table from the 315 Session information to allow for a more comprehensive and coherent 316 MIB model. 318 3.5.4. The LDP Session Table 320 The LDP Session Table is a read-only table. Each entry in this table 321 represents a single session between an LDP Entity and a Peer. The 322 mplsLdpSessionEntry AUGMENTS the mplsLdpPeerEntry. 324 The information in this table is learned during session 325 establishment. NOTE: rows in this table will appear during session 326 intialization. 328 3.5.5. The LDP Session Statistics Table 330 The MPLS LDP Session Stats Table is a read-only table which contains 331 statistical information on sessions. 333 3.5.6. The LDP Hello Adjacencies Table 335 This is a table of all adjacencies between all LDP Entities and all 336 LDP Peers. A Session may have one or more adjacencies. A session 337 should not have zero adjacencies, because this indicates that the 338 session has lost contact with the Peer. A session which has zero 339 Hello Adjacencies should be eventually removed. 341 3.5.7. The LDP LSP Table 343 The Label Information Base (LIB) contains information about labels 344 learned by the LSR. The LIB for LDP, CR-LDP and MPLS-RSVP (i.e. all 345 currently defined MPLS protocols) is represented in the LSR MIB 346 [LSRMIB]. The LIB is represented by the LSR MIB's mplsXCTable (mpls 347 Cross Connect Table), mplsInSegmentTable (mpls In Segment Table) and 348 the mplsOutSegmentTable (mpls Out Segment Table). The mplsXCTable 349 models the cross-connection of the ingress label with a specific 350 egress label. The mplsInSegmentTable stores the ingress label's 351 information, and the mplsOutSegmentTable stores the egress label's 352 information. 354 The LDP Session that created the LSP and the LSP's (ingress label, 355 egress label) pair along with other information is contained in the 356 LSR MIB's mplsXCTable, the mplsInSegmentTable and the 357 mplsOutSegmentTable. 359 In order to utilize the LSR MIB's mplsXCTable, mplsInSegmentTable and 360 mplsOutSegmentTable for LDP LSPs, there needs to be a mechanism to 361 associate LDP sessions with LDP LSPs created as a result of those LDP 362 sessions. The mplsInSegmentLdpLspTable and mplsOutSegmentLdpLspTable 363 in this MIB contain information to find the LDP LSP entries in the 364 mplsInSegmentTable, mplsOutSegmentTable and the mplsXCTable. 366 These two tables, the mplsInSegmentLdpLspTable and 367 mplsOutSegmentLdpLspTable, have been made optional in the conformance 368 section of the MIB. They only need to be supported if the LSR MIBs 369 mplsInSegmentTable, mplsOutSegmentTable and mplsXCTable are 370 implemented. 372 As discussed in the section, "Changing Values after Session 373 Establishment", if a session is torn down, then all the information 374 related to this session, must be removed from the both LDP MIB and, 375 if implemented, from the LSR MIB. 377 3.5.8. The FEC Table 379 The FEC Table is a table which contains FEC (Forwarding Equivalence 380 Class) information. Each entry/row represents a single FEC Element. 381 There is also an LDP LSP FEC Table, mplsLdpLspFecTable, which 382 associates FECs with the LSPs. 384 3.5.9. The LDP Session Peer Address Table 386 The MPLS LDP Session Peer Address Table is a table which extends the 387 mplsLdpSessionTable. This table is a read-only table which stores 388 Addresses learned after session initialization via Address Message 389 advertisement. 391 3.6. LDP Notifications 393 Currently, there are several notifications which are specific for 394 LDP. These are described in this section. 396 The mplsLdpInitSesThresholdExceeded notification indicates to the 397 operator that there may be a misconfigured mplsLdpEntityEntry because 398 the session associated with this Entity is not being established, and 399 the Entity keeps trying to establish the session. A side effect of 400 this situation is that a row in the mplsLdpSessionTable may not be 401 reaching the operational state as indicated by the mplsLdpSesState 402 object. If the value of mplsLdpEntityInitSesThreshold is 0 (zero) 403 then this is equal to specifying the value of infinity for the 404 threshold, and the mplsLdpInitSesThresholdExceeded notification will 405 never be sent. 407 The mplsLdpPathVectorLimitMismatch notification is generated when 408 there is a mismatch in the Path Vector Limits between the Entity and 409 Peer during session initialization. The session uses the value which 410 is configured as the Entity's Path Vector Limit. However, a 411 notification should be generated to indicate that a mismatch 412 occurred. For further details, please see Section 3.5.3 of the LDP 413 Specification [RFC3036]. 415 The mplsLdpSessionUp and mplsLdpSessionDown notifications are 416 generated when there is an appropriate change in the mplsLdpSesState 417 object, e.g. when sessions change state (Up to Down for the 418 mplsLdpSessionDown trap, or Down to Up for the mplsLdpSessionUp 419 trap). 421 4. MPLS Label Distribution Protocol MIB Definitions 423 MPLS-LDP-MIB DEFINITIONS ::= BEGIN 425 IMPORTS 426 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, 427 Integer32, Counter32, Unsigned32 428 FROM SNMPv2-SMI 429 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 430 FROM SNMPv2-CONF 432 RowStatus, TimeInterval, TruthValue, 433 TimeStamp, StorageType 434 FROM SNMPv2-TC 436 InterfaceIndexOrZero 437 FROM IF-MIB 439 InetAddressPrefixLength, 440 InetAddressType, 441 InetAddress, 442 InetPortNumber 443 FROM INET-ADDRESS-MIB 445 IndexInteger, 446 IndexIntegerNextFree 447 FROM DIFFSERV-MIB 449 mplsMIB, 450 MplsLabel, 451 MplsLabelDistributionMethod, 452 MplsLdpIdentifier, 453 MplsLdpLabelType, 454 MplsLspType, 455 MplsLsrIdentifier, 456 MplsRetentionMode 458 FROM MPLS-TC-MIB; 460 mplsLdpMIB MODULE-IDENTITY 461 LAST-UPDATED "200304221200Z" -- 22 April 2003 462 ORGANIZATION "Multiprotocol Label Switching (mpls) 463 Working Group" 464 CONTACT-INFO 466 "Joan Cucchiara (jcucchiara@artel.com) 467 Artel 469 Hans Sjostrand (hans@ipunplugged.com) 470 ipUnplugged 472 James V. Luciani (james_luciani@mindspring.com) 473 Consultant 475 Working Group Chairs: 476 George Swallow, email: swallow@cisco.com 477 Loa Andersson, email: loa@pi.se 479 MPLS Working Group, email: mpls@uu.net" 481 DESCRIPTION 482 "Copyright (C) The Internet Society (2003). This 483 version of this MIB module is part of RFCXXX; see 484 the RFC itself for full legal notices. 486 This MIB contains managed object definitions for the 487 'Multiprotocol Label Switching, Label Distribution 488 Protocol, LDP' document." 490 REVISION "200304221200Z" -- 22 April 2003 491 DESCRIPTION 492 "Initial version published as part of RFC XXXX." 494 -- Please see the IANA Considerations Section. 495 -- The requested mplsMIB subId is 4, e.g. 496 -- ::= { mplsMIB 4 } 498 ::= { mplsMIB XXX } -- to be assigned by IANA 500 --**************************************************************** 502 mplsLdpNotifications OBJECT IDENTIFIER ::= { mplsLdpMIB 0 } 503 mplsLdpObjects OBJECT IDENTIFIER ::= { mplsLdpMIB 1 } 504 mplsLdpConformance OBJECT IDENTIFIER ::= { mplsLdpMIB 2 } 506 --**************************************************************** 507 -- MPLS LDP Objects 508 --**************************************************************** 510 mplsLdpLsrObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 1 } 512 mplsLdpEntityObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 2 } 514 -- 515 -- The MPLS Label Distribution Protocol's 516 -- Label Switching Router Objects 517 -- 519 mplsLdpLsrId OBJECT-TYPE 520 SYNTAX MplsLsrIdentifier 521 MAX-ACCESS read-only 522 STATUS current 523 DESCRIPTION 524 "The LSR's Identifier." 525 ::= { mplsLdpLsrObjects 1 } 527 mplsLdpLsrLoopDetectionCapable OBJECT-TYPE 528 SYNTAX INTEGER { 529 none(1), 530 other(2), 531 hopCount(3), 532 pathVector(4), 533 hopCountAndPathVector(5) 534 } 535 MAX-ACCESS read-only 536 STATUS current 537 DESCRIPTION 538 "A indication of whether this 539 Label Switching Router supports 540 loop detection. 542 none(1) -- Loop Detection is not supported 543 on this LSR. 545 other(2) -- Loop Detection is supported but 546 by a method other than those 547 listed below. 549 hopCount(3) -- Loop Detection is supported by 550 Hop Count only. 552 pathVector(4) -- Loop Detection is supported by 553 Path Vector only. 555 hopCountAndPathVector(5) -- Loop Detection is 556 supported by both Hop Count 557 And Path Vector. 559 Since Loop Detection is determined during 560 Session Initialization, an individual session 561 may not be running with loop detection. This 562 object simply gives an indication of whether or not the 563 LSR has the ability to support Loop Detection and 564 which types." 565 ::= { mplsLdpLsrObjects 2 } 567 -- 568 -- The MPLS Label Distribution Protocol Entity Objects 569 -- 570 mplsLdpEntityLastChange OBJECT-TYPE 571 SYNTAX TimeStamp 572 MAX-ACCESS read-only 573 STATUS current 574 DESCRIPTION 575 "The value of sysUpTime at the time of the most 576 recent addition or deletion of an entry 577 to/from the mplsLdpEntityTable/mplsLdpEntityStatsTable, or 578 the most recent change in value of any objects in the 579 mplsLdpEntityTable. 581 If no such changes have occurred since the last 582 re-initialization of the local management subsystem, 583 then this object contains a zero value." 584 ::= { mplsLdpEntityObjects 1 } 586 mplsLdpEntityIndexNext OBJECT-TYPE 587 SYNTAX IndexIntegerNextFree 588 MAX-ACCESS read-only 589 STATUS current 590 DESCRIPTION 591 "This object contains an appropriate value to 592 be used for mplsLdpEntityIndex when creating 593 entries in the mplsLdpEntityTable. The value 594 0 indicates that no unassigned entries are 595 available." 596 ::= { mplsLdpEntityObjects 2 } 598 mplsLdpEntityTable OBJECT-TYPE 599 SYNTAX SEQUENCE OF MplsLdpEntityEntry 600 MAX-ACCESS not-accessible 601 STATUS current 602 DESCRIPTION 603 "This table contains information about the 604 MPLS Label Distribution Protocol Entities which 605 exist on this Label Switching Router (LSR) 606 or Label Edge Router (LER)." 607 ::= { mplsLdpEntityObjects 3 } 609 mplsLdpEntityEntry OBJECT-TYPE 610 SYNTAX MplsLdpEntityEntry 611 MAX-ACCESS not-accessible 612 STATUS current 613 DESCRIPTION 614 "An entry in this table represents an LDP entity. 616 An entry can be created by a network administrator 617 or by an SNMP agent as instructed by LDP." 618 INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex } 619 ::= { mplsLdpEntityTable 1 } 621 MplsLdpEntityEntry ::= SEQUENCE { 622 mplsLdpEntityLdpId MplsLdpIdentifier, 623 mplsLdpEntityIndex IndexInteger, 624 mplsLdpEntityProtocolVersion Unsigned32, 625 mplsLdpEntityAdminStatus INTEGER, 626 mplsLdpEntityOperStatus INTEGER, 627 mplsLdpEntityTcpDscPort InetPortNumber, 628 mplsLdpEntityUdpDscPort InetPortNumber, 629 mplsLdpEntityMaxPduLength Unsigned32, 630 mplsLdpEntityKeepAliveHoldTimer Unsigned32, 631 mplsLdpEntityHelloHoldTimer Unsigned32, 632 mplsLdpEntityInitSesThreshold Integer32, 633 mplsLdpEntityLabelDistMethod MplsLabelDistributionMethod, 634 mplsLdpEntityLabelRetentionMode MplsRetentionMode, 635 mplsLdpEntityPathVectorLimit Integer32, 636 mplsLdpEntityHopCountLimit Integer32, 637 mplsLdpEntityTransportAddrKind INTEGER, 638 mplsLdpEntityTargetPeer TruthValue, 639 mplsLdpEntityTargetPeerAddrType InetAddressType, 640 mplsLdpEntityTargetPeerAddr InetAddress, 641 mplsLdpEntityLabelType MplsLdpLabelType, 642 mplsLdpEntityDiscontinuityTime TimeStamp, 643 mplsLdpEntityStorageType StorageType, 644 mplsLdpEntityRowStatus RowStatus 645 } 647 mplsLdpEntityLdpId OBJECT-TYPE 648 SYNTAX MplsLdpIdentifier 649 MAX-ACCESS not-accessible 650 STATUS current 651 DESCRIPTION 652 "The LDP identifier." 653 REFERENCE 654 "[RFC3036] LDP Specification, Section on LDP Identifiers." 655 ::= { mplsLdpEntityEntry 1 } 657 mplsLdpEntityIndex OBJECT-TYPE 658 SYNTAX IndexInteger 659 MAX-ACCESS not-accessible 660 STATUS current 661 DESCRIPTION 662 "This index is used as a secondary index to uniquely 663 identify this row. Before creating a row in this table, 664 the 'mplsLdpEntityIndexNext' object should be retrieved. 665 That value should be used for the value of this index 666 when creating a row in this table. (NOTE: if a value 667 of zero (0) is retrieved, that indicates that no rows 668 can be created in this table at this time. 670 A secondary index (this object) is meaningful to some 671 but not all, LDP implementations. For example 672 in an LDP implementation which uses PPP would 673 use this index to differentiate PPP sub-links. 675 Another way to use this index is to give this the 676 value of ifIndex. However, this is dependant 677 on the implementation." 678 ::= { mplsLdpEntityEntry 2 } 680 mplsLdpEntityProtocolVersion OBJECT-TYPE 681 SYNTAX Unsigned32(1..65535) 682 MAX-ACCESS read-create 683 STATUS current 684 DESCRIPTION 685 "The version number of the LDP protocol which will be 686 used in the session initialization message. 688 Section 3.5.3 in the LDP Specification specifies 689 that the version of the LDP protocol is negotiated during 690 session establishment. The value of this object 691 represents the value that is sent in the initialization 692 message." 693 REFERENCE 694 "[RFC3036], LDP Specification, Section 3.5.3 Initialization 695 Message." 696 DEFVAL { 1 } 697 ::= { mplsLdpEntityEntry 3 } 699 mplsLdpEntityAdminStatus OBJECT-TYPE 700 SYNTAX INTEGER { 701 enable(1), 702 disable(2) 703 } 704 MAX-ACCESS read-create 705 STATUS current 706 DESCRIPTION 707 "The administrative status of this LDP Entity. 708 If this object is changed from 'enable' to 'disable' 709 and this entity has already attempted to establish 710 contact with a Peer, then all contact with that 711 Peer is lost and all information from that Peer 712 needs to be removed from the MIB. (This implies 713 that the network management subsystem should clean 714 up any related entry in the mplsLdpPeerTable. This 715 further implies that a 'tear-down' for that session 716 is issued and the session and all information related 717 to that session cease to exist). 719 At this point the operator is able to change values 720 which are related to this entity. 722 When the admin status is set back to 'enable', then 723 this Entity will attempt to establish a NEW session 724 with the Peer." 725 DEFVAL { enable } 726 ::= { mplsLdpEntityEntry 4 } 728 mplsLdpEntityOperStatus OBJECT-TYPE 729 SYNTAX INTEGER { 730 unknown(1), 731 enabled(2), 732 disabled(3) 733 } 734 MAX-ACCESS read-only 735 STATUS current 736 DESCRIPTION 737 "The operational status of this LDP Entity." 738 ::= { mplsLdpEntityEntry 5 } 740 mplsLdpEntityTcpDscPort OBJECT-TYPE 741 SYNTAX InetPortNumber 742 MAX-ACCESS read-create 743 STATUS current 744 DESCRIPTION 745 "The TCP Discovery Port for 746 LDP. The default value is the well-known 747 value of this port." 748 REFERENCE 749 "[RFC3036], LDP Specification, Section 2.4.1, 750 Basic Discovery Mechanism, Section 2.4.2, 751 Extended Discovery Mechanism, Section 752 3.10, Well-known Numbers, and Section 3.10.1. 753 UDP and TCP Ports." 754 DEFVAL { 646 } 755 ::= { mplsLdpEntityEntry 6 } 757 mplsLdpEntityUdpDscPort OBJECT-TYPE 758 SYNTAX InetPortNumber 759 MAX-ACCESS read-create 760 STATUS current 761 DESCRIPTION 762 "The UDP Discovery Port for 763 LDP. The default value is the 764 well-known value for this port." 765 REFERENCE 766 "[RFC3036], LDP Specification, Section 2.4.1, 767 Basic Discovery Mechanism, Section 2.4.2, 768 Extended Discovery Mechanism, Section 769 3.10, Well-known Numbers, and Section 3.10.1. 770 UDP and TCP Ports." 771 DEFVAL { 646 } 772 ::= { mplsLdpEntityEntry 7 } 774 mplsLdpEntityMaxPduLength OBJECT-TYPE 775 SYNTAX Unsigned32 (256..65535) 776 UNITS "octets" 777 MAX-ACCESS read-create 778 STATUS current 779 DESCRIPTION 780 "The maximum PDU Length that is sent in 781 the Common Session Parameters of an Initialization 782 Message. According to the LDP Specification [RFC3036] 783 a value of 255 or less specifies the 784 default maximum length of 4096 octets, this is why 785 the value of this object starts at 256. The operator 786 should explicitly choose the default value (i.e. 4096), 787 or some other value. 789 The receiving LSR MUST calculate the maximum PDU 790 length for the session by using the smaller of its and 791 its peer's proposals for Max PDU Length." 792 REFERENCE 793 "[RFC3036], LDP Specification, Section 3.5.3. 794 Initialization Message." 795 DEFVAL { 4096 } 796 ::= { mplsLdpEntityEntry 8 } 798 mplsLdpEntityKeepAliveHoldTimer OBJECT-TYPE 799 SYNTAX Unsigned32 (1..65535) 800 UNITS "seconds" 801 MAX-ACCESS read-create 802 STATUS current 803 DESCRIPTION 804 "The 16-bit integer value which is the proposed keep 805 alive hold timer for this LDP Entity." 806 DEFVAL { 40 } 807 ::= { mplsLdpEntityEntry 9 } 809 mplsLdpEntityHelloHoldTimer OBJECT-TYPE 810 SYNTAX Unsigned32 (0..65535) 811 UNITS "seconds" 812 MAX-ACCESS read-create 813 STATUS current 814 DESCRIPTION 815 "The 16-bit integer value which is the proposed Hello 816 hold timer for this LDP Entity. The Hello Hold time 817 in seconds. 819 An LSR maintains a record of Hellos received 820 from potential peers. This object represents 821 the Hold Time in the Common Hello Parameters TLV of 822 the Hello Message. 824 A value of 0 is a default value and should be 825 interpretted in conjunction with the 826 mplsLdpEntityTargetPeer object. 828 If the value of this object is 0: if the value of the 829 mplsLdpEntityTargetPeer object is false(2), then this 830 specifies that the Hold Time's actual default value is 831 15 seconds (i.e. the default Hold time for Link Hellos 832 is 15 seconds). Otherwise if the value of the 833 mplsLdpEntityTargetPeer object is true(1), then this 834 specifies that the Hold Time's actual default value is 835 45 seconds (i.e. the default Hold time for Targeted 836 Hellos is 45 seconds). 838 A value of 65535 means infinite (i.e. wait forever). 840 All other values represent the amount of time in 841 seconds to wait for a Hello Message. Setting the 842 hold time to a value smaller than 15 is not 843 recommended, although not forbidden according 844 to [RFC3036]." 845 REFERENCE 846 "[RFC3036], LDP Specification, Section 3.5.2., 847 Hello Message." 848 DEFVAL { 0 } 849 ::= { mplsLdpEntityEntry 10 } 851 mplsLdpEntityInitSesThreshold OBJECT-TYPE 852 SYNTAX Integer32(0..100) 853 MAX-ACCESS read-create 854 STATUS current 855 DESCRIPTION 856 "When attempting to establish a session with a 857 given Peer, the given LDP Entity should 858 send out the SNMP notification, 859 'mplsLdpInitSesThresholdExceeded', when 860 the number of Session Initialization messages sent 861 exceeds this threshold. The notification is 862 used to notify an operator when this Entity and 863 its Peer are possibily engaged in an endless 864 sequence of messages as each NAKs the other's 865 Initialization messages with Error Notification 866 messages. Setting this threshold which triggers 867 the notification is one way to 868 notify the operator. 870 A value of 0 (zero) for this object 871 indicates that the threshold is infinity, thus 872 the SNMP notification will never be generated." 873 REFERENCE 874 "[RFC3036], LDP Specification, 875 Section 2.5.3 Session Initialization." 876 DEFVAL { 8 } 877 ::= { mplsLdpEntityEntry 11 } 879 mplsLdpEntityLabelDistMethod OBJECT-TYPE 880 SYNTAX MplsLabelDistributionMethod 881 MAX-ACCESS read-create 882 STATUS current 883 DESCRIPTION 884 "For any given LDP session, the method of 885 label distribution must be specified." 886 ::= { mplsLdpEntityEntry 12 } 888 mplsLdpEntityLabelRetentionMode OBJECT-TYPE 889 SYNTAX MplsRetentionMode 890 MAX-ACCESS read-create 891 STATUS current 892 DESCRIPTION 893 "The LDP Entity can be configured to use either 894 conservative or liberal label retention mode. 896 If the value of this object is conservative(1) 897 then advertized label mappings are retained 898 only if they will be used to forward packets, 899 i.e. if label came from a valid next hop. 901 If the value of this object is liberal(2) 902 then all advertized label mappings are retained 903 whether they are from a valid next hop or not." 904 ::= { mplsLdpEntityEntry 13 } 906 mplsLdpEntityPathVectorLimit OBJECT-TYPE 907 SYNTAX Integer32 (0..255) 908 MAX-ACCESS read-create 909 STATUS current 910 DESCRIPTION 911 "If the value of this object is 0 (zero) then 912 Loop Dection for Path Vectors is disabled. 914 Otherwise, if this object has a value greater than 915 zero, then Loop Dection for Path Vectors is enabled, 916 and the Path Vector Limit is this value. 917 Also, the value of the object, 918 'mplsLdpLsrLoopDetectionCapable', must be set to 919 either 'pathVector(4)' or 'hopCountAndPathVector(5)', 920 if this object has a value greater than 0 (zero), 921 otherwise it is ignored." 922 REFERENCE 923 "[RFC3036], LDP Specification, Section 2.8 Loop Dection, 924 Section 3.4.5 Path Vector TLV." 925 ::= { mplsLdpEntityEntry 14 } 927 mplsLdpEntityHopCountLimit OBJECT-TYPE 928 SYNTAX Integer32 (0..255) 929 MAX-ACCESS read-create 930 STATUS current 931 DESCRIPTION 932 "If the value of this object is 0 (zero), 933 then Loop Detection using Hop Counters is 934 disabled. 936 If the value of this object is greater than 937 0 (zero) then Loop Detection using Hop 938 Counters is enabled, and this object 939 specifies this Entity's maximum allowable 940 value for the Hop Count. 941 Also, the value of the object 942 mplsLdpLsrLoopDetectionCapable must be set 943 to either 'hopCount(3)' or 944 'hopCountAndPathVector(5)' if this object 945 has a value greater than 0 (zero), otherwise 946 it is ignored." 947 DEFVAL { 0 } 948 ::= { mplsLdpEntityEntry 15 } 950 mplsLdpEntityTransportAddrKind OBJECT-TYPE 951 SYNTAX INTEGER { 952 interface(1), 953 loopback(2) 954 } 955 MAX-ACCESS read-create 956 STATUS current 957 DESCRIPTION 958 "This specifies whether the loopback or interface 959 address is to be used as the transport address 960 in the transport address TLV of the 961 hello message. 963 If the value is interface(1), then the IP 964 address of the interface from which hello 965 messages are sent is used as the transport 966 address in the hello message. 968 Otherwise, if the value is loopback(2), then the IP 969 address of the loopback interface is used as the 970 transport address in the hello message." 971 DEFVAL { loopback } 972 ::= { mplsLdpEntityEntry 16 } 974 mplsLdpEntityTargetPeer OBJECT-TYPE 975 SYNTAX TruthValue 976 MAX-ACCESS read-create 977 STATUS current 978 DESCRIPTION 979 "If this LDP entity uses targeted peer then set 980 this to true." 981 DEFVAL { false } 982 ::= { mplsLdpEntityEntry 17 } 984 mplsLdpEntityTargetPeerAddrType OBJECT-TYPE 985 SYNTAX InetAddressType 986 MAX-ACCESS read-create 987 STATUS current 988 DESCRIPTION 989 "The type of the internetwork layer address used for 990 the Extended Discovery. This object indicates how 991 the value of mplsLdpEntityTargetPeerAddr is to 992 be interpreted." 993 ::= { mplsLdpEntityEntry 18 } 995 mplsLdpEntityTargetPeerAddr OBJECT-TYPE 996 SYNTAX InetAddress 997 MAX-ACCESS read-create 998 STATUS current 999 DESCRIPTION 1000 "The value of the internetwork layer address used for 1001 the Extended Discovery." 1002 ::= { mplsLdpEntityEntry 19 } 1004 mplsLdpEntityLabelType OBJECT-TYPE 1005 SYNTAX MplsLdpLabelType 1006 MAX-ACCESS read-create 1007 STATUS current 1008 DESCRIPTION 1009 "Specifies the optional parameters for the LDP 1010 Initialization Message. If the value is generic(1) 1011 then no optional parameters will be sent in 1012 the LDP Initialization message associated with 1013 this Entity. 1015 If the value is atmParameters(2) then 1016 a row must be created in the mplsLdpEntityAtmParms 1017 Table, which corresponds to this entry. 1019 If the value is frameRelayParameters(3) then 1020 a row must be created in the mplsLdpEntityFrameRelayParms 1021 Table, which corresponds to this entry." 1022 REFERENCE 1023 "[RFC3036], LDP Specification, Section 3.5.3., 1024 Initialization Message." 1025 ::= { mplsLdpEntityEntry 20 } 1027 mplsLdpEntityDiscontinuityTime OBJECT-TYPE 1028 SYNTAX TimeStamp 1029 MAX-ACCESS read-only 1030 STATUS current 1031 DESCRIPTION 1032 "The value of sysUpTime on the most recent occasion 1033 at which any one or more of this entity's counters 1034 suffered a discontinuity. The relevant counters are the 1035 specific instances associated with this entity of 1036 any Counter32, or Counter64 object contained 1037 in the 'mplsLdpEntityStatsTable'. If no such 1038 discontinuities have occurred since the last 1039 re-initialization of the local management 1040 subsystem, then this object contains a zero 1041 value." 1042 ::= { mplsLdpEntityEntry 21 } 1044 mplsLdpEntityStorageType OBJECT-TYPE 1045 SYNTAX StorageType 1046 MAX-ACCESS read-create 1047 STATUS current 1048 DESCRIPTION 1049 "The storage type for this conceptual row. Conceptual rows 1050 having the value 'permanent(4)' MAY allow write-access to any 1051 columnar objects in the row, except for setting the 1052 mplsLdpEntityRowStatus to 'destroy(6)'." 1053 DEFVAL{ nonVolatile } 1054 ::= { mplsLdpEntityEntry 22 } 1056 mplsLdpEntityRowStatus OBJECT-TYPE 1057 SYNTAX RowStatus 1058 MAX-ACCESS read-create 1059 STATUS current 1060 DESCRIPTION 1061 "The status of this conceptual row. All writable objects in this 1062 row may be modified at any time, however, as described in 1063 detail in the section entitled, 'Changing Values After Session 1064 Establishment', and again described in the 1065 DESCRIPTION clause of the mplsLdpEntityAdminStatus object, if a 1066 session has been initiated with a Peer, changing objects 1067 in this table will wreak havoc with the session and interrupt 1068 traffic. To repeat again: the recommended procedure is to 1069 set the mplsLdpEntityAdminStatus to down, thereby 1070 explicitly causing a session to be torn down. Then, 1071 change objects in this entry, then set the mplsLdpEntityAdminStatus 1072 to enable which enables a NEW session to be initiated." 1074 ::= { mplsLdpEntityEntry 23 } 1076 -- 1077 -- The MPLS LDP Entity Statistics Table 1078 -- 1080 mplsLdpEntityStatsTable OBJECT-TYPE 1081 SYNTAX SEQUENCE OF MplsLdpEntityStatsEntry 1082 MAX-ACCESS not-accessible 1083 STATUS current 1084 DESCRIPTION 1085 "This table is a read-only table which augments 1086 the mplsLdpEntityTable. The purpose of this 1087 table is to keep statistical information about 1088 the LDP Entities on the LSR." 1089 ::= { mplsLdpEntityObjects 4 } 1091 mplsLdpEntityStatsEntry OBJECT-TYPE 1092 SYNTAX MplsLdpEntityStatsEntry 1093 MAX-ACCESS not-accessible 1094 STATUS current 1095 DESCRIPTION 1096 "A row in this table contains statistical information 1097 about an LDP Entity. Some counters contained in a 1098 row are for fatal errors received during a former 1099 LDP Session associated with this entry. For example, 1100 an Ldp Pdu received on a TCP connection during an 1101 LDP Session contains a fatal error. That 1102 error is counted here, because the 1103 session is terminated. 1105 If the error is NOT fatal (i.e. and the Session 1106 remains), then the error is counted in the 1107 mplsLdpSesStatsEntry." 1108 AUGMENTS { mplsLdpEntityEntry } 1109 ::= { mplsLdpEntityStatsTable 1 } 1111 MplsLdpEntityStatsEntry ::= SEQUENCE { 1112 mplsLdpEntityStatsSesAttempts Counter32, 1113 mplsLdpEntityStatsSesRejectedNoHelloErrors Counter32, 1114 mplsLdpEntityStatsSesRejectedAdErrors Counter32, 1115 mplsLdpEntityStatsSesRejectedMaxPduErrors Counter32, 1116 mplsLdpEntityStatsSesRejectedLRErrors Counter32, 1117 mplsLdpEntityStatsBadLdpIdentifierErrors Counter32, 1118 mplsLdpEntityStatsBadPduLengthErrors Counter32, 1119 mplsLdpEntityStatsBadMessageLengthErrors Counter32, 1120 mplsLdpEntityStatsBadTlvLengthErrors Counter32, 1121 mplsLdpEntityStatsMalformedTlvValueErrors Counter32, 1122 mplsLdpEntityStatsKeepAliveTimerExpErrors Counter32, 1123 mplsLdpEntityStatsShutdownReceivedNotifications Counter32, 1124 mplsLdpEntityStatsShutdownSentNotifications Counter32 1125 } 1127 mplsLdpEntityStatsSesAttempts OBJECT-TYPE 1128 SYNTAX Counter32 1129 MAX-ACCESS read-only 1130 STATUS current 1131 DESCRIPTION 1132 "A count of the total attempted sessions for 1133 this LDP Entity. 1135 Discontinuities in the value of this counter can occur 1136 at re-initialization of the management system, and at 1137 other times as indicated by the value of 1138 mplsLdpEntityDiscontinuityTime." 1139 ::= { mplsLdpEntityStatsEntry 1 } 1141 mplsLdpEntityStatsSesRejectedNoHelloErrors OBJECT-TYPE 1142 SYNTAX Counter32 1143 MAX-ACCESS read-only 1144 STATUS current 1145 DESCRIPTION 1146 "A count of the Session Rejected/No Hello Error 1147 Notification Messages sent or received by 1148 this LDP Entity. 1150 Discontinuities in the value of this counter can occur 1151 at re-initialization of the management system, and at 1152 other times as indicated by the value of 1153 mplsLdpEntityDiscontinuityTime." 1154 ::= { mplsLdpEntityStatsEntry 2 } 1156 mplsLdpEntityStatsSesRejectedAdErrors OBJECT-TYPE 1157 SYNTAX Counter32 1158 MAX-ACCESS read-only 1159 STATUS current 1160 DESCRIPTION 1161 "A count of the Session Rejected/Parameters 1162 Advertisement Mode Error Notification Messages sent 1163 or received by this LDP Entity. 1165 Discontinuities in the value of this counter can occur 1166 at re-initialization of the management system, and at 1167 other times as indicated by the value of 1168 mplsLdpEntityDiscontinuityTime." 1169 ::= { mplsLdpEntityStatsEntry 3 } 1171 mplsLdpEntityStatsSesRejectedMaxPduErrors OBJECT-TYPE 1172 SYNTAX Counter32 1173 MAX-ACCESS read-only 1174 STATUS current 1175 DESCRIPTION 1176 "A count of the Session Rejected/Parameters 1177 Max Pdu Length Error Notification Messages sent 1178 or received by this LDP Entity. 1180 Discontinuities in the value of this counter can occur 1181 at re-initialization of the management system, and at 1182 other times as indicated by the value of 1183 mplsLdpEntityDiscontinuityTime." 1184 ::= { mplsLdpEntityStatsEntry 4 } 1186 mplsLdpEntityStatsSesRejectedLRErrors OBJECT-TYPE 1187 SYNTAX Counter32 1188 MAX-ACCESS read-only 1189 STATUS current 1190 DESCRIPTION 1191 "A count of the Session Rejected/Parameters 1192 Label Range Notification Messages sent 1193 or received by this LDP Entity. 1195 Discontinuities in the value of this counter can occur 1196 at re-initialization of the management system, and at 1197 other times as indicated by the value of 1198 mplsLdpEntityDiscontinuityTime." 1199 ::= { mplsLdpEntityStatsEntry 5 } 1201 mplsLdpEntityStatsBadLdpIdentifierErrors OBJECT-TYPE 1202 SYNTAX Counter32 1203 MAX-ACCESS read-only 1204 STATUS current 1205 DESCRIPTION 1206 "This object counts the number of Bad LDP Identifier 1207 Fatal Errors detected by the session(s) 1208 (past and present) associated with this LDP Entity. 1210 Discontinuities in the value of this counter can occur 1211 at re-initialization of the management system, and at 1212 other times as indicated by the value of 1213 mplsLdpEntityDiscontinuityTime." 1214 REFERENCE 1215 "[RFC3036], LDP Specification, Section 3.5.1.2." 1216 ::= { mplsLdpEntityStatsEntry 6 } 1218 mplsLdpEntityStatsBadPduLengthErrors OBJECT-TYPE 1219 SYNTAX Counter32 1220 MAX-ACCESS read-only 1221 STATUS current 1222 DESCRIPTION 1223 "This object counts the number of Bad Pdu Length 1224 Fatal Errors detected by the session(s) 1225 (past and present) associated with this LDP Entity. 1227 Discontinuities in the value of this counter can occur 1228 at re-initialization of the management system, and at 1229 other times as indicated by the value of 1230 mplsLdpEntityDiscontinuityTime." 1231 REFERENCE 1232 "[RFC3036], LDP Specification, Section 3.5.1.2." 1233 ::= { mplsLdpEntityStatsEntry 7 } 1235 mplsLdpEntityStatsBadMessageLengthErrors OBJECT-TYPE 1236 SYNTAX Counter32 1237 MAX-ACCESS read-only 1238 STATUS current 1239 DESCRIPTION 1240 "This object counts the number of Bad Message 1241 Length Fatal Errors detected by the session(s) 1242 (past and present) associated with this LDP Entity. 1244 Discontinuities in the value of this counter can occur 1245 at re-initialization of the management system, and at 1246 other times as indicated by the value of 1247 mplsLdpEntityDiscontinuityTime." 1248 REFERENCE 1249 "[RFC3036], LDP Specification, Section 3.5.1.2." 1250 ::= { mplsLdpEntityStatsEntry 8 } 1252 mplsLdpEntityStatsBadTlvLengthErrors OBJECT-TYPE 1253 SYNTAX Counter32 1254 MAX-ACCESS read-only 1255 STATUS current 1256 DESCRIPTION 1257 "This object counts the number of Bad TLV 1258 Length Fatal Errors detected by the session(s) 1259 (past and present) associated with this LDP Entity. 1261 Discontinuities in the value of this counter can occur 1262 at re-initialization of the management system, and at 1263 other times as indicated by the value of 1264 mplsLdpEntityDiscontinuityTime." 1265 REFERENCE 1266 "[RFC3036], LDP Specification, Section 3.5.1.2." 1267 ::= { mplsLdpEntityStatsEntry 9 } 1269 mplsLdpEntityStatsMalformedTlvValueErrors OBJECT-TYPE 1270 SYNTAX Counter32 1271 MAX-ACCESS read-only 1272 STATUS current 1273 DESCRIPTION 1274 "This object counts the number of Malformed TLV 1275 Value Fatal Errors detected by the session(s) 1276 (past and present) associated with this 1277 LDP Entity. 1279 Discontinuities in the value of this counter can occur 1280 at re-initialization of the management system, and at 1281 other times as indicated by the value of 1282 mplsLdpEntityDiscontinuityTime." 1283 REFERENCE 1284 "[RFC3036], LDP Specification, Section 3.5.1.2." 1285 ::= { mplsLdpEntityStatsEntry 10 } 1287 mplsLdpEntityStatsKeepAliveTimerExpErrors OBJECT-TYPE 1288 SYNTAX Counter32 1289 MAX-ACCESS read-only 1290 STATUS current 1291 DESCRIPTION 1292 "This object counts the number of Session Keep Alive 1293 Timer Expired Errors detected by the session(s) 1294 (past and present) associated with this LDP Entity. 1296 Discontinuities in the value of this counter can occur 1297 at re-initialization of the management system, and at 1298 other times as indicated by the value of 1299 mplsLdpEntityDiscontinuityTime." 1300 REFERENCE 1301 "[RFC3036], LDP Specification, Section 3.5.1.2." 1303 ::= { mplsLdpEntityStatsEntry 11 } 1305 mplsLdpEntityStatsShutdownReceivedNotifications OBJECT-TYPE 1306 SYNTAX Counter32 1307 MAX-ACCESS read-only 1308 STATUS current 1309 DESCRIPTION 1310 "This object counts the number of Shutdown Notfications 1311 received related to session(s) (past and present) 1312 associated with this LDP Entity. 1314 Discontinuities in the value of this counter can occur 1315 at re-initialization of the management system, and at 1316 other times as indicated by the value of 1317 mplsLdpEntityDiscontinuityTime." 1318 ::= { mplsLdpEntityStatsEntry 12 } 1320 mplsLdpEntityStatsShutdownSentNotifications OBJECT-TYPE 1321 SYNTAX Counter32 1322 MAX-ACCESS read-only 1323 STATUS current 1324 DESCRIPTION 1325 "This object counts the number of Shutdown Notfications 1326 sent related to session(s) (past and present) associated 1327 with this LDP Entity. 1329 Discontinuities in the value of this counter can occur 1330 at re-initialization of the management system, and at 1331 other times as indicated by the value of 1332 mplsLdpEntityDiscontinuityTime." 1333 ::= { mplsLdpEntityStatsEntry 13 } 1335 -- 1336 -- The MPLS LDP Peer Table 1337 -- 1339 mplsLdpSesObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 3 } 1341 mplsLdpPeerLastChange OBJECT-TYPE 1342 SYNTAX TimeStamp 1343 MAX-ACCESS read-only 1344 STATUS current 1345 DESCRIPTION 1346 "The value of sysUpTime at the time of the most 1347 recent addition or deletion to/from the 1348 mplsLdpPeerTable/mplsLdpSesTable." 1349 ::= { mplsLdpSesObjects 1 } 1351 mplsLdpPeerTable OBJECT-TYPE 1352 SYNTAX SEQUENCE OF MplsLdpPeerEntry 1353 MAX-ACCESS not-accessible 1354 STATUS current 1355 DESCRIPTION 1356 "Information about LDP peers known by Entities in 1357 the mplsLdpEntityTable. The information in this table 1358 is based on information from the Entity-Peer interaction 1359 during session initialization but is not appropriate 1360 for the mplsLdpSesTable, because objects in this 1361 table may or may not be used in session establishment." 1362 ::= { mplsLdpSesObjects 2 } 1364 mplsLdpPeerEntry OBJECT-TYPE 1365 SYNTAX MplsLdpPeerEntry 1366 MAX-ACCESS not-accessible 1367 STATUS current 1368 DESCRIPTION 1369 "Information about a single Peer which is related 1370 to a Session. NOTE: this table is augmented by 1371 the mplsLdpSessionTable." 1372 INDEX { mplsLdpEntityLdpId, 1373 mplsLdpEntityIndex, 1374 mplsLdpPeerLdpId } 1375 ::= { mplsLdpPeerTable 1 } 1377 MplsLdpPeerEntry ::= SEQUENCE { 1378 mplsLdpPeerLdpId MplsLdpIdentifier, 1379 mplsLdpPeerLabelDistMethod MplsLabelDistributionMethod, 1380 mplsLdpPeerPathVectorLimit Integer32, 1381 mplsLdpPeerTransportAddrType InetAddressType, 1382 mplsLdpPeerTransportAddr InetAddress 1383 } 1385 mplsLdpPeerLdpId OBJECT-TYPE 1386 SYNTAX MplsLdpIdentifier 1387 MAX-ACCESS not-accessible 1388 STATUS current 1389 DESCRIPTION 1390 "The LDP identifier of this LDP Peer." 1391 ::= { mplsLdpPeerEntry 1 } 1393 mplsLdpPeerLabelDistMethod OBJECT-TYPE 1394 SYNTAX MplsLabelDistributionMethod 1395 MAX-ACCESS read-only 1396 STATUS current 1397 DESCRIPTION 1398 "For any given LDP session, the method of 1399 label distribution must be specified." 1400 ::= { mplsLdpPeerEntry 2 } 1402 mplsLdpPeerPathVectorLimit OBJECT-TYPE 1403 SYNTAX Integer32 (0..255) 1404 MAX-ACCESS read-only 1405 STATUS current 1406 DESCRIPTION 1407 "If the value of this object is 0 (zero) then 1408 Loop Dection for Path Vectors for this Peer 1409 is disabled. 1411 Otherwise, if this object has a value greater than 1412 zero, then Loop Dection for Path Vectors for this 1413 Peer is enabled and the Path Vector Limit is this value." 1414 REFERENCE 1415 "[RFC3036], LDP Specification, Section 2.8 Loop Dection, 1416 Section 3.4.5 Path Vector TLV." 1417 ::= { mplsLdpPeerEntry 3 } 1419 mplsLdpPeerTransportAddrType OBJECT-TYPE 1420 SYNTAX InetAddressType 1421 MAX-ACCESS read-only 1422 STATUS current 1423 DESCRIPTION 1424 "The object specifies how to interpret the address 1425 for the mplsLdpPeerTransportAddr object." 1426 REFERENCE 1427 "[RFC3036], LDP Specification, Section 2.5.2 1428 Transport Connection Establishment and 1429 Section 3.5.2.1 Hello Message Procedures." 1430 ::= { mplsLdpPeerEntry 4 } 1432 mplsLdpPeerTransportAddr OBJECT-TYPE 1433 SYNTAX InetAddress 1434 MAX-ACCESS read-only 1435 STATUS current 1436 DESCRIPTION 1437 "The transport address advertized by the peer 1438 in the hello message or the Hello source address." 1439 REFERENCE 1440 "[RFC3036], LDP Specification, Section 2.5.2 1441 Transport Connection Establishment and 1442 Section 3.5.2.1 Hello Message Procedures." 1443 ::= { mplsLdpPeerEntry 5 } 1445 -- 1446 -- The MPLS LDP Sessions Table 1447 -- 1449 mplsLdpSesTable OBJECT-TYPE 1450 SYNTAX SEQUENCE OF MplsLdpSesEntry 1451 MAX-ACCESS not-accessible 1452 STATUS current 1453 DESCRIPTION 1454 "A table of Sessions between the LDP Entities and 1455 LDP Peers. Each row represents a single session." 1456 ::= { mplsLdpSesObjects 3 } 1458 mplsLdpSesEntry OBJECT-TYPE 1459 SYNTAX MplsLdpSesEntry 1460 MAX-ACCESS not-accessible 1461 STATUS current 1462 DESCRIPTION 1463 "An entry in this table represents information on a 1464 single session between an LDP Entity and LDP Peer. 1465 The information contained in a row is read-only. 1467 Please note: the Path Vector Limit for the 1468 Session is the value which is configured in 1469 the corresponding mplsLdpEntityEntry. The 1470 Peer's Path Vector Limit is in noted in the 1471 mplsLdpPeerTable. 1473 Values which may differ from those configured are 1474 noted in the objects of this table, the 1475 mplsLdpAtmSesTable and the 1476 mplsLdpFrameRelaySesTable. A value will 1477 differ if it was negotiated between the 1478 Entity and the Peer. Values may or may not 1479 be negotiated. For example, if the values 1480 are the same then no negotiation takes place. 1481 If they are negotiated, then they may differ." 1482 AUGMENTS { mplsLdpPeerEntry } 1483 ::= { mplsLdpSesTable 1 } 1485 MplsLdpSesEntry ::= SEQUENCE { 1486 mplsLdpSesStateLastChange TimeStamp, 1487 mplsLdpSesState INTEGER, 1488 mplsLdpSesRole INTEGER, 1489 mplsLdpSesProtocolVersion Unsigned32, 1490 mplsLdpSesKeepAliveHoldTimeRem TimeInterval, 1491 mplsLdpSesKeepAliveTime Unsigned32, 1492 mplsLdpSesMaxPduLength Unsigned32, 1493 mplsLdpSesDiscontinuityTime TimeStamp 1494 } 1496 mplsLdpSesStateLastChange OBJECT-TYPE 1497 SYNTAX TimeStamp 1498 MAX-ACCESS read-only 1499 STATUS current 1500 DESCRIPTION 1501 "The value of sysUpTime at the time this Session entered 1502 its current state as denoted by the mplsLdpSesState object." 1503 ::= { mplsLdpSesEntry 1 } 1505 mplsLdpSesState OBJECT-TYPE 1506 SYNTAX INTEGER { 1507 nonexistent(1), 1508 initialized(2), 1509 openrec(3), 1510 opensent(4), 1511 operational(5) 1512 } 1513 MAX-ACCESS read-only 1514 STATUS current 1515 DESCRIPTION 1516 "The current state of the session, all of the 1517 states 1 to 5 are based on the state machine for 1518 session negotiation behavior." 1519 REFERENCE 1520 "[RFC3036], LDP Specification, Section 2.5.4, 1521 Initialization State Machine." 1522 ::= { mplsLdpSesEntry 2 } 1524 mplsLdpSesRole OBJECT-TYPE 1525 SYNTAX INTEGER { 1526 unknown(1), 1527 active(2), 1528 passive(3) 1530 } 1531 MAX-ACCESS read-only 1532 STATUS current 1533 DESCRIPTION 1534 "During session establishment the LSR takes either the 1535 active role or the passive role based on address 1536 comparisons. This object indicates whether this LSR 1537 was behaving in an active role or passive role during 1538 this sessions establishment. 1540 The value of unknown(1), indicates that the role is not 1541 able to be determined at the present time." 1542 REFERENCE 1543 "[RFC3036], LDP Specification, Section 2.5.3., 1544 Session Initialization" 1545 ::= { mplsLdpSesEntry 3 } 1547 mplsLdpSesProtocolVersion OBJECT-TYPE 1548 SYNTAX Unsigned32(1..65535) 1549 MAX-ACCESS read-only 1550 STATUS current 1551 DESCRIPTION 1552 "The version of the LDP Protocol which 1553 this session is using. This is the version of 1554 the LDP protocol which has been negotiated during 1555 session initialization." 1556 REFERENCE 1557 "[RFC3036], LDP Specification, Section 3.5.3, 1558 Initialization Message." 1559 ::= { mplsLdpSesEntry 4 } 1561 mplsLdpSesKeepAliveHoldTimeRem OBJECT-TYPE 1562 SYNTAX TimeInterval 1563 MAX-ACCESS read-only 1564 STATUS current 1565 DESCRIPTION 1566 "The keep alive hold time remaining for this session." 1567 ::= { mplsLdpSesEntry 5 } 1569 mplsLdpSesKeepAliveTime OBJECT-TYPE 1570 SYNTAX Unsigned32 1571 UNITS "seconds" 1572 MAX-ACCESS read-only 1573 STATUS current 1574 DESCRIPTION 1575 "The negotiated KeepAlive Time. This value is 1576 negotiated during session initialization." 1577 REFERENCE 1578 "[RFC3036], LDP Specification, Section 3.5.3, 1579 Initialization Message." 1580 ::= { mplsLdpSesEntry 6 } 1582 mplsLdpSesMaxPduLength OBJECT-TYPE 1583 SYNTAX Unsigned32 (1..65535) 1584 UNITS "octets" 1585 MAX-ACCESS read-only 1586 STATUS current 1587 DESCRIPTION 1588 "The value of maximum allowable length for LDP PDUs for 1589 this session. This value may have been negotiated during 1590 the Session Initialization. This object is related to 1591 the mplsLdpEntityMaxPduLength object. The 1592 mplsLdpEntityMaxPduLength object specifies the requested 1593 LDP PDU length, and this object reflects the negotiated 1594 LDP PDU length between the Entity and 1595 the Peer." 1596 REFERENCE 1597 "[RFC3036], LDP Specification, Section 3.5.3, 1598 Initialization Message." 1599 ::= { mplsLdpSesEntry 7 } 1601 mplsLdpSesDiscontinuityTime OBJECT-TYPE 1602 SYNTAX TimeStamp 1603 MAX-ACCESS read-only 1604 STATUS current 1605 DESCRIPTION 1606 "The value of sysUpTime on the most recent occasion at 1607 which any one or more of this session's counters 1608 suffered a discontinuity. The relevant counters are 1609 the specific instances associated with this session 1610 of any Counter32 or Counter64 object contained in the 1611 mplsLdpSesStatsTable. 1613 The initial value of this object is the value of 1614 sysUpTime when the entry was created in this table. 1616 Also, a command generator can distinguish when a session 1617 between a given Entity and Peer goes away and a new 1618 session is established. This value would change and 1619 thus indicate to the command generator that this is a 1620 different session." 1622 ::= { mplsLdpSesEntry 8 } 1624 -- 1625 -- The MPLS LDP Session Statistics Table 1626 -- 1628 mplsLdpSesStatsTable OBJECT-TYPE 1629 SYNTAX SEQUENCE OF MplsLdpSesStatsEntry 1630 MAX-ACCESS not-accessible 1631 STATUS current 1632 DESCRIPTION 1633 "A table of statistics for Sessions between 1634 LDP Entities and LDP Peers." 1635 ::= { mplsLdpSesObjects 4 } 1637 mplsLdpSesStatsEntry OBJECT-TYPE 1638 SYNTAX MplsLdpSesStatsEntry 1639 MAX-ACCESS not-accessible 1640 STATUS current 1641 DESCRIPTION 1642 "An entry in this table represents statistical 1643 information on a single session between an LDP 1644 Entity and LDP Peer." 1645 AUGMENTS { mplsLdpPeerEntry } 1646 ::= { mplsLdpSesStatsTable 1 } 1648 MplsLdpSesStatsEntry ::= SEQUENCE { 1649 mplsLdpSesStatsUnkMesTypeErrors Counter32, 1650 mplsLdpSesStatsUnkTlvErrors Counter32 1651 } 1653 mplsLdpSesStatsUnkMesTypeErrors OBJECT-TYPE 1654 SYNTAX Counter32 1655 MAX-ACCESS read-only 1656 STATUS current 1657 DESCRIPTION 1658 "This object counts the number of Unknown Message Type 1659 Errors detected during this session. 1661 Discontinuities in the value of this counter can occur 1662 at re-initialization of the management system, and at 1663 other times as indicated by the value of 1664 mplsLdpSesDiscontinuityTime." 1665 ::= { mplsLdpSesStatsEntry 1 } 1667 mplsLdpSesStatsUnkTlvErrors OBJECT-TYPE 1668 SYNTAX Counter32 1669 MAX-ACCESS read-only 1670 STATUS current 1671 DESCRIPTION 1672 "This object counts the number of Unknown TLV Errors 1673 detected during this session. 1675 Discontinuities in the value of this counter can occur 1676 at re-initialization of the management system, and at 1677 other times as indicated by the value of 1678 mplsLdpSessionDiscontinuityTime." 1679 ::= { mplsLdpSesStatsEntry 2 } 1681 -- 1682 -- The MPLS LDP Hello Adjacency Table 1683 -- 1685 mplsLdpHelloAdjacencyObjects OBJECT IDENTIFIER ::= 1686 { mplsLdpSesObjects 5 } 1688 mplsLdpHelloAdjacencyTable OBJECT-TYPE 1689 SYNTAX SEQUENCE OF MplsLdpHelloAdjacencyEntry 1690 MAX-ACCESS not-accessible 1691 STATUS current 1692 DESCRIPTION 1693 "A table of Hello Adjacencies for Sessions." 1694 ::= { mplsLdpHelloAdjacencyObjects 1 } 1696 mplsLdpHelloAdjacencyEntry OBJECT-TYPE 1697 SYNTAX MplsLdpHelloAdjacencyEntry 1698 MAX-ACCESS not-accessible 1699 STATUS current 1700 DESCRIPTION 1701 "Each row represents a single LDP Hello Adjacency. 1702 An LDP Session can have one or more Hello adjacencies." 1703 INDEX { mplsLdpEntityLdpId, 1704 mplsLdpEntityIndex, 1705 mplsLdpPeerLdpId, 1706 mplsLdpHelloAdjacencyIndex } 1707 ::= { mplsLdpHelloAdjacencyTable 1 } 1709 MplsLdpHelloAdjacencyEntry ::= SEQUENCE { 1710 mplsLdpHelloAdjacencyIndex Unsigned32, 1711 mplsLdpHelloAdjacencyHoldTimeRem TimeInterval, 1712 mplsLdpHelloAdjacencyHoldTime Unsigned32, 1713 mplsLdpHelloAdjacencyType INTEGER 1714 } 1716 mplsLdpHelloAdjacencyIndex OBJECT-TYPE 1717 SYNTAX Unsigned32 (1..4294967295) 1718 MAX-ACCESS not-accessible 1719 STATUS current 1720 DESCRIPTION 1721 "An identifier for this specific adjacency." 1722 ::= { mplsLdpHelloAdjacencyEntry 1 } 1724 mplsLdpHelloAdjacencyHoldTimeRem OBJECT-TYPE 1725 SYNTAX TimeInterval 1726 MAX-ACCESS read-only 1727 STATUS current 1728 DESCRIPTION 1729 "The time remaining for this Hello Adjacency. 1730 This interval will change when the 'next' 1731 Hello message which corresponds to this 1732 Hello Adjacency is received." 1733 ::= { mplsLdpHelloAdjacencyEntry 2 } 1735 mplsLdpHelloAdjacencyHoldTime OBJECT-TYPE 1736 SYNTAX Unsigned32 1737 MAX-ACCESS read-only 1738 STATUS current 1739 DESCRIPTION 1740 "The Hello hold time which is negotiated between 1741 the Entity and the Peer. 1743 A value of 0 means the default, 1744 which is 15 seconds for Link Hellos and 45 seconds 1745 for Targeted Hellos. A value of 0xffff indicates an 1746 infinite hold time." 1747 REFERENCE 1748 "[RFC3036] LDP Specification, Section 3.5.2 Hello Message" 1749 ::= { mplsLdpHelloAdjacencyEntry 3 } 1751 mplsLdpHelloAdjacencyType OBJECT-TYPE 1752 SYNTAX INTEGER { 1753 link(1), 1754 targeted(2) 1755 } 1756 MAX-ACCESS read-only 1757 STATUS current 1758 DESCRIPTION 1759 "This adjacency is the result of a 'link' 1760 hello if the value of this object is link(1). 1761 Otherwise, it is a result of a 'targeted' 1762 hello, targeted(2)." 1763 ::= { mplsLdpHelloAdjacencyEntry 4 } 1765 -- 1766 -- Session Label (LSP) Mapping to LSR MIB's In Segment LIB Information. 1767 -- 1769 -- 1770 -- NOTE: the next 2 tables map to the MPLS-LSR-MIB's MplsInSegmentTable 1771 -- and MplsOutSegmentTable. The cross-connect information is not 1772 -- represented here as it can be gleaned from the MPLS-LSR-MIB. 1773 -- 1775 mplsInSegmentLdpLspTable OBJECT-TYPE 1776 SYNTAX SEQUENCE OF MplsInSegmentLdpLspEntry 1777 MAX-ACCESS not-accessible 1778 STATUS current 1779 DESCRIPTION 1780 "A table of LDP LSP's which 1781 map to the InSegment Table in the 1782 the LSR MIB's." 1783 ::= { mplsLdpSesObjects 6 } 1785 mplsInSegmentLdpLspEntry OBJECT-TYPE 1786 SYNTAX MplsInSegmentLdpLspEntry 1787 MAX-ACCESS not-accessible 1788 STATUS current 1789 DESCRIPTION 1790 "An entry in this table represents information on a 1791 single LDP LSP which is represented by 1792 a session's index triple (mplsLdpEntityLdpId, 1793 mplsLdpEntityIndex, mplsLdpPeerLdpId) AND the 1794 index tuple (mplsInSegmentLdpLspIfIndex, 1795 mplsInSegmentLdpLspLabel). 1797 The information contained in a row is read-only." 1798 INDEX { mplsLdpEntityLdpId, 1799 mplsLdpEntityIndex, 1800 mplsLdpPeerLdpId, 1801 mplsInSegmentLdpLspIfIndex, 1802 mplsInSegmentLdpLspLabel 1803 } 1804 ::= { mplsInSegmentLdpLspTable 1 } 1806 MplsInSegmentLdpLspEntry ::= SEQUENCE { 1807 mplsInSegmentLdpLspIfIndex InterfaceIndexOrZero, 1808 mplsInSegmentLdpLspLabel MplsLabel, 1809 mplsInSegmentLdpLspLabelType MplsLdpLabelType, 1810 mplsInSegmentLdpLspType MplsLspType 1811 } 1813 mplsInSegmentLdpLspIfIndex OBJECT-TYPE 1814 SYNTAX InterfaceIndexOrZero 1815 MAX-ACCESS not-accessible 1816 STATUS current 1817 DESCRIPTION 1818 "The ifIndex value associated with this LSP which has the 1819 same value as the mplsInSegmentIfIndex in the MPLS-LSR-MIB's 1820 mplsInSegmentTable." 1821 ::= { mplsInSegmentLdpLspEntry 1 } 1823 mplsInSegmentLdpLspLabel OBJECT-TYPE 1824 SYNTAX MplsLabel 1825 MAX-ACCESS not-accessible 1826 STATUS current 1827 DESCRIPTION 1828 "The LDP label for this LSP. This is also the same value 1829 as the mplsInSegmentLabel index in the MPLS-LSR-MIB's 1830 mplsInSegmentTable." 1831 ::= { mplsInSegmentLdpLspEntry 2 } 1833 mplsInSegmentLdpLspLabelType OBJECT-TYPE 1834 SYNTAX MplsLdpLabelType 1835 MAX-ACCESS read-only 1836 STATUS current 1837 DESCRIPTION 1838 "The Layer 2 Label Type." 1839 ::= { mplsInSegmentLdpLspEntry 3 } 1841 mplsInSegmentLdpLspType OBJECT-TYPE 1842 SYNTAX MplsLspType 1843 MAX-ACCESS read-only 1844 STATUS current 1845 DESCRIPTION 1846 "The type of LSP connection." 1847 ::= { mplsInSegmentLdpLspEntry 4 } 1849 -- 1850 -- Session Label (LSP) Mapping to LSR MIB's Out Segment LIB Information. 1851 -- 1853 mplsOutSegmentLdpLspTable OBJECT-TYPE 1854 SYNTAX SEQUENCE OF MplsOutSegmentLdpLspEntry 1855 MAX-ACCESS not-accessible 1856 STATUS current 1857 DESCRIPTION 1858 "A table of LDP LSP's which 1859 map to the InSegment Table in the 1860 the LSR MIB's." 1861 ::= { mplsLdpSesObjects 7 } 1863 mplsOutSegmentLdpLspEntry OBJECT-TYPE 1864 SYNTAX MplsOutSegmentLdpLspEntry 1865 MAX-ACCESS not-accessible 1866 STATUS current 1867 DESCRIPTION 1868 "An entry in this table represents information on a 1869 single LDP LSP which is represented by 1870 a session's index triple (mplsLdpEntityLdpId, 1871 mplsLdpEntityIndex, mplsLdpPeerLdpId) AND the 1872 index tuple (mplsOutSegmentLdpLspIfIndex, 1873 mplsOutSegmentLdpLspLabel). 1875 The information contained in a row is read-only." 1876 INDEX { mplsLdpEntityLdpId, 1877 mplsLdpEntityIndex, 1878 mplsLdpPeerLdpId, 1879 mplsOutSegmentLdpLspIfIndex, 1880 mplsOutSegmentLdpLspLabel 1881 } 1882 ::= { mplsOutSegmentLdpLspTable 1 } 1884 MplsOutSegmentLdpLspEntry ::= SEQUENCE { 1885 mplsOutSegmentLdpLspIfIndex InterfaceIndexOrZero, 1886 mplsOutSegmentLdpLspLabel MplsLabel, 1887 mplsOutSegmentLdpLspLabelType MplsLdpLabelType, 1888 mplsOutSegmentLdpLspType MplsLspType 1889 } 1891 mplsOutSegmentLdpLspIfIndex OBJECT-TYPE 1892 SYNTAX InterfaceIndexOrZero 1893 MAX-ACCESS not-accessible 1894 STATUS current 1895 DESCRIPTION 1896 "The ifIndex value associated with this LSP which has the 1897 same value as the mplsOutSegmentIfIndex in the MPLS-LSR-MIB's 1898 mplsOutSegmentTable. NOTE: the value of zero represents 1899 the perPlatform label space." 1900 ::= { mplsOutSegmentLdpLspEntry 1 } 1902 mplsOutSegmentLdpLspLabel OBJECT-TYPE 1903 SYNTAX MplsLabel 1904 MAX-ACCESS not-accessible 1905 STATUS current 1906 DESCRIPTION 1907 "The LDP label for this LSP. This is also the same value 1908 as the mplsOutSegmentTopLabel in the MPLS-LSR-MIB's 1909 mplsOutSegmentTable." 1910 ::= { mplsOutSegmentLdpLspEntry 2 } 1912 mplsOutSegmentLdpLspLabelType OBJECT-TYPE 1913 SYNTAX MplsLdpLabelType 1914 MAX-ACCESS read-only 1915 STATUS current 1916 DESCRIPTION 1917 "The Layer 2 Label Type." 1918 ::= { mplsOutSegmentLdpLspEntry 3 } 1920 mplsOutSegmentLdpLspType OBJECT-TYPE 1921 SYNTAX MplsLspType 1922 MAX-ACCESS read-only 1923 STATUS current 1924 DESCRIPTION 1925 "The type of LSP connection." 1926 ::= { mplsOutSegmentLdpLspEntry 4 } 1928 -- 1929 -- Mpls FEC Table 1930 -- 1932 mplsFecObjects OBJECT IDENTIFIER ::= 1933 { mplsLdpSesObjects 8 } 1935 mplsFecIndexNext OBJECT-TYPE 1936 SYNTAX IndexIntegerNextFree 1937 MAX-ACCESS read-only 1938 STATUS current 1939 DESCRIPTION 1940 "This object contains an appropriate value to 1941 be used for mplsFecIndex when creating 1942 entries in the mplsFecTable. The value 1943 0 indicates that no unassigned entries are 1944 available." 1945 ::= { mplsFecObjects 1 } 1947 mplsFecTable OBJECT-TYPE 1948 SYNTAX SEQUENCE OF MplsFecEntry 1949 MAX-ACCESS not-accessible 1950 STATUS current 1951 DESCRIPTION 1952 "This table represents the FEC 1953 (Forwarding Equivalence Class) 1954 Information associated with an LSP." 1955 ::= { mplsFecObjects 2 } 1957 mplsFecEntry OBJECT-TYPE 1958 SYNTAX MplsFecEntry 1959 MAX-ACCESS not-accessible 1960 STATUS current 1961 DESCRIPTION 1962 "Each row represents a single FEC Element." 1963 INDEX { mplsFecIndex } 1964 ::= { mplsFecTable 1 } 1966 MplsFecEntry ::= SEQUENCE { 1967 mplsFecIndex IndexInteger, 1968 mplsFecType INTEGER, 1969 mplsFecAddrPrefixLength InetAddressPrefixLength, 1970 mplsFecAddrFamily InetAddressType, 1971 mplsFecAddr InetAddress, 1972 mplsFecStorageType StorageType, 1973 mplsFecRowStatus RowStatus 1974 } 1976 mplsFecIndex OBJECT-TYPE 1977 SYNTAX IndexInteger 1978 MAX-ACCESS not-accessible 1979 STATUS current 1980 DESCRIPTION 1981 "The index which uniquely identifies this entry." 1982 ::= { mplsFecEntry 1 } 1984 mplsFecType OBJECT-TYPE 1985 SYNTAX INTEGER { 1986 prefix(1), 1987 hostAddress(2) 1988 } 1989 MAX-ACCESS read-create 1990 STATUS current 1991 DESCRIPTION 1992 "The type of the FEC. If the value of this object 1993 is 'prefix(1)' then the FEC type described by this 1994 row is for address prefixes. 1996 If the value of this object is 'hostAddress(2)' then 1997 the FEC type described by this row is a host address." 1998 REFERENCE 1999 "[RFC3036], Section 3.4.1. FEC TLV." 2000 ::= { mplsFecEntry 2 } 2002 mplsFecAddrPrefixLength OBJECT-TYPE 2003 SYNTAX InetAddressPrefixLength 2004 MAX-ACCESS read-create 2005 STATUS current 2006 DESCRIPTION 2007 "If the value of the 'mplsFecType' is 'hostAddress(2)' 2008 then this object is undefined. 2010 If the value of 'mplsFecType' is 'prefix(1)' 2011 then the value of this object is the length in 2012 bits of the address prefix represented by 2013 'mplsFecAddr', or zero. If the value of this 2014 object is zero, this indicates that the 2015 prefix matches all addresses. In this case the 2016 prefix MUST also be zero (i.e. 'mplsFecAddr' will 2017 have the value of zero.)" 2018 REFERENCE 2019 "[RFC3036], Section 3.4.1. FEC TLV." 2020 DEFVAL { 0 } 2021 ::= { mplsFecEntry 3 } 2023 mplsFecAddrFamily OBJECT-TYPE 2024 SYNTAX InetAddressType 2025 MAX-ACCESS read-create 2026 STATUS current 2027 DESCRIPTION 2028 "The value of this object is the type of the address. The 2029 type of the address should then be looked up in the 2030 ADDRESS FAMILY NUMBERS [RFC1700] for the corresponding entry 2031 there and this value should be encoded in the FEC TLV." 2032 REFERENCE 2033 "[RFC3036], Section 3.4.1. FEC TLV." 2034 ::= { mplsFecEntry 4 } 2036 mplsFecAddr OBJECT-TYPE 2037 SYNTAX InetAddress 2038 MAX-ACCESS read-create 2039 STATUS current 2040 DESCRIPTION 2041 "The value of this object is the an address where the 2042 address type is specified by the 'mplsFecAddrFamily' object. 2044 This address is then used as either an address prefix, 2045 or as the host address as indicated by the 'mplsFecType' 2046 object. In other words, the FEC element is populated 2047 according to the Prefix FEC Element value encoding, or 2048 the Host Address FEC Element encoding." 2049 REFERENCE 2050 "[RFC3036], Section 3.4.1 FEC TLV." 2051 ::= { mplsFecEntry 5 } 2053 mplsFecStorageType OBJECT-TYPE 2054 SYNTAX StorageType 2055 MAX-ACCESS read-create 2056 STATUS current 2057 DESCRIPTION 2058 "The storage type for this conceptual row. Conceptual rows 2059 having the value 'permanent(4)' MAY allow write-access to 2060 any columnar objects in the row, except for setting the 2061 'mplsFecRowStatus' to 'destroy(6)'." 2062 DEFVAL { nonVolatile } 2063 ::= { mplsFecEntry 6 } 2065 mplsFecRowStatus OBJECT-TYPE 2066 SYNTAX RowStatus 2067 MAX-ACCESS read-create 2068 STATUS current 2069 DESCRIPTION 2070 "The status of this conceptual row. If the value of this 2071 object is 'active(1)', then none of the writable objects of 2072 this entry can be modified, except to set this object 2073 to 'destroy(6)'. 2075 NOTE: if this row is being referenced by any entry in the 2076 mplsLdpLspFecTable, then a request to destroy this row, will 2077 result in an inconsistentValue error." 2078 ::= { mplsFecEntry 7 } 2080 -- 2081 -- LDP LSP FEC Table 2082 -- 2084 mplsLdpLspFecTable OBJECT-TYPE 2085 SYNTAX SEQUENCE OF MplsLdpLspFecEntry 2086 MAX-ACCESS not-accessible 2087 STATUS current 2088 DESCRIPTION 2089 "A table which shows the relationship between 2090 LDP LSP's and FECs. Each row represents 2091 a single LSP to FEC association." 2092 ::= { mplsLdpSesObjects 9 } 2094 mplsLdpLspFecEntry OBJECT-TYPE 2095 SYNTAX MplsLdpLspFecEntry 2096 MAX-ACCESS not-accessible 2097 STATUS current 2098 DESCRIPTION 2099 "An entry represents a LDP LSP 2100 to FEC association." 2101 INDEX { mplsLdpEntityLdpId, 2102 mplsLdpEntityIndex, 2103 mplsLdpPeerLdpId, 2104 mplsLdpLspFecSegment, 2105 mplsLdpLspFecIfIndex, 2106 mplsLdpLspFecLabel, 2107 mplsLdpLspFecIndex 2108 } 2109 ::= { mplsLdpLspFecTable 1 } 2111 MplsLdpLspFecEntry ::= SEQUENCE { 2112 mplsLdpLspFecSegment INTEGER, 2113 mplsLdpLspFecIfIndex InterfaceIndexOrZero, 2114 mplsLdpLspFecLabel MplsLabel, 2115 mplsLdpLspFecIndex IndexInteger, 2116 mplsLdpLspFecOperStatus INTEGER, 2117 mplsLdpLspFecLastChange TimeStamp, 2118 mplsLdpLspFecStorageType StorageType, 2119 mplsLdpLspFecRowStatus RowStatus 2120 } 2121 mplsLdpLspFecSegment OBJECT-TYPE 2122 SYNTAX INTEGER { 2123 inSegment(1), 2124 outSegment(2) 2125 } 2126 MAX-ACCESS not-accessible 2127 STATUS current 2128 DESCRIPTION 2129 "If the value is inSegment(1), then this 2130 indicates that the following indices, 2131 mplsLdpLspFecIfIndex and mplsLdpLspFecLabel 2132 contain the same values as the mplsInSegmentLdpLspIfIndex 2133 and the mplsInSegmentLdpLspLabel. 2135 Otherwise, if the value of this object is 2136 outSegment(2), then this 2137 indicates that the following indices, 2138 mplsLdpLspFecIfIndex and mplsLdpLspFecLabel 2139 contain the same values as the mplsOutSegmentLdpLspIfIndex 2140 and the mplsOutSegmentLdpLspLabel." 2141 ::= { mplsLdpLspFecEntry 1 } 2143 mplsLdpLspFecIfIndex OBJECT-TYPE 2144 SYNTAX InterfaceIndexOrZero 2145 MAX-ACCESS not-accessible 2146 STATUS current 2147 DESCRIPTION 2148 "This index is either the mplsInSegmentLdpLspIfIndex 2149 or the mplsOutSegmentLdpLspIfIndex as indicated by 2150 the mplsLdpLspFecSegment." 2151 ::= { mplsLdpLspFecEntry 2 } 2153 mplsLdpLspFecLabel OBJECT-TYPE 2154 SYNTAX MplsLabel 2155 MAX-ACCESS not-accessible 2156 STATUS current 2157 DESCRIPTION 2158 "This index is either the mplsInSegmentLdpLspLabel 2159 or the mplsOutSegmentLdpLspLabel as indicated by 2160 the mplsLdpLspFecSegment." 2161 ::= { mplsLdpLspFecEntry 3 } 2163 mplsLdpLspFecIndex OBJECT-TYPE 2164 SYNTAX IndexInteger 2165 MAX-ACCESS not-accessible 2166 STATUS current 2167 DESCRIPTION 2168 "This index identifies the FEC entry in the 2169 mplsFecTable associated with this Session. 2170 In other words, the value of this index 2171 is the same as the value of the mplsFecIndex 2172 that denotes the FEC associated with this 2173 Session." 2174 ::= { mplsLdpLspFecEntry 4 } 2176 mplsLdpLspFecOperStatus OBJECT-TYPE 2177 SYNTAX INTEGER { 2178 unknown(1), 2179 inUse(2), 2180 notInUse(3) 2181 } 2182 MAX-ACCESS read-only 2183 STATUS current 2184 DESCRIPTION 2185 "An indication of the operational status of 2186 the FEC associated with LDP LSP. 2188 unknown(1) - this is a temporary state which 2189 may indicate the LSP-FEC association 2190 is in a state of transition. 2192 inUse(2) - the FEC associated with the LSP is 2193 currently being applied. 2195 notInUse(3) - the FEC associated with the LSP is 2196 not being applied. Eventually, this 2197 entry may be aged out." 2198 ::= { mplsLdpLspFecEntry 5 } 2200 mplsLdpLspFecLastChange OBJECT-TYPE 2201 SYNTAX TimeStamp 2202 MAX-ACCESS read-only 2203 STATUS current 2204 DESCRIPTION 2205 "This value of sysUpTime at the time of the most recent 2206 change to the mplsLdpLspFecOperStatus object." 2207 ::= { mplsLdpLspFecEntry 6 } 2209 mplsLdpLspFecStorageType OBJECT-TYPE 2210 SYNTAX StorageType 2211 MAX-ACCESS read-create 2212 STATUS current 2213 DESCRIPTION 2214 "The storage type for this conceptual row. Conceptual rows 2215 having the value 'permanent(4)' MAY allow write-access to 2216 any columnar objects in the row, except for setting the 2217 mplsLdpLspFecRowStatus' to 'destroy(6)'." 2218 DEFVAL { nonVolatile } 2219 ::= { mplsLdpLspFecEntry 7 } 2221 mplsLdpLspFecRowStatus OBJECT-TYPE 2222 SYNTAX RowStatus 2223 MAX-ACCESS read-create 2224 STATUS current 2225 DESCRIPTION 2226 "The status of this conceptual row. If the value of this 2227 object is 'active(1)', then none of the writable objects of 2228 this entry can be modified. 2230 The Agent should delete this row when the Session ceases to 2231 exist. If an operator wants to associate the session with 2232 a different FEC, the recommended 2233 procedure is (as described in detail in the section 2234 entitled, 'Changing Values After Session 2235 Establishment', and again described in the 2236 DESCRIPTION clause of the mplsLdpEntityAdminStatus object) 2237 is to set the mplsLdpEntityAdminStatus to down, thereby 2238 explicitly causing a session to be torn down. This will also 2239 cause this entry to be deleted. 2241 Then, set the mplsLdpEntityAdminStatus 2242 to enable which enables a NEW session to be initiated. 2243 Once the session is initiated, an entry may be added to this 2244 table to associate the new session with a FEC." 2245 ::= { mplsLdpLspFecEntry 8 } 2247 -- 2248 -- Address Message/Address Withdraw Message Information 2249 -- 2250 -- This information is associated with a specific Session 2251 -- because Label Address Messages are sent after session 2252 -- initialization has taken place. 2253 -- 2254 mplsLdpSesPeerAddrTable OBJECT-TYPE 2255 SYNTAX SEQUENCE OF MplsLdpSesPeerAddrEntry 2256 MAX-ACCESS not-accessible 2257 STATUS current 2258 DESCRIPTION 2259 "This table 'extends' the mplsLdpSessionTable. 2260 This table is used to store Label Address Information 2261 from Label Address Messages received by this LSR from 2262 Peers. This table is read-only and should be updated 2263 when Label Withdraw Address Messages are received, i.e. 2264 Rows should be deleted as apropriate. 2266 NOTE: since more than one address may be contained 2267 in a Label Address Message, this table 'extends', 2268 rather than 'AUGMENTS' the mplsLdpSessionTable's 2269 information." 2270 ::= { mplsLdpSesObjects 10 } 2272 mplsLdpSesPeerAddrEntry OBJECT-TYPE 2273 SYNTAX MplsLdpSesPeerAddrEntry 2274 MAX-ACCESS not-accessible 2275 STATUS current 2276 DESCRIPTION 2277 "An entry in this table represents information on 2278 a session's single next hop address which was 2279 advertised in an Address Message from the LDP peer. 2280 The information contained in a row is read-only." 2281 INDEX { mplsLdpEntityLdpId, 2282 mplsLdpEntityIndex, 2283 mplsLdpPeerLdpId, 2284 mplsLdpSesPeerAddrIndex 2285 } 2286 ::= { mplsLdpSesPeerAddrTable 1 } 2288 MplsLdpSesPeerAddrEntry ::= SEQUENCE { 2289 mplsLdpSesPeerAddrIndex Unsigned32, 2290 mplsLdpSesPeerNextHopAddrType InetAddressType, 2291 mplsLdpSesPeerNextHopAddr InetAddress 2292 } 2294 mplsLdpSesPeerAddrIndex OBJECT-TYPE 2295 SYNTAX Unsigned32 (1..4294967295) 2296 MAX-ACCESS not-accessible 2297 STATUS current 2298 DESCRIPTION 2299 "An index which uniquely identifies this entry within 2300 a given session." 2301 ::= { mplsLdpSesPeerAddrEntry 1 } 2303 mplsLdpSesPeerNextHopAddrType OBJECT-TYPE 2304 SYNTAX InetAddressType 2305 MAX-ACCESS read-only 2306 STATUS current 2307 DESCRIPTION 2308 "The internetwork layer address type of this Next Hop 2309 Address as specified in the Label Address Message 2310 associated with this Session. The value of this 2311 object indicates how to interpret the value of 2312 mplsLdpSesPeerNextHopAddress." 2313 ::= { mplsLdpSesPeerAddrEntry 2 } 2315 mplsLdpSesPeerNextHopAddr OBJECT-TYPE 2316 SYNTAX InetAddress 2317 MAX-ACCESS read-only 2318 STATUS current 2319 DESCRIPTION 2320 "The value of the next hop address." 2321 REFERENCE 2322 "[RFC3036], Section 2.7. LDP Identifiers and Next Hop Addresses" 2323 ::= { mplsLdpSesPeerAddrEntry 3 } 2325 --- 2326 --- Notifications 2327 --- 2329 mplsLdpInitSesThresholdExceeded NOTIFICATION-TYPE 2330 OBJECTS { 2331 mplsLdpEntityInitSesThreshold 2332 } 2333 STATUS current 2334 DESCRIPTION 2335 "This notification is generated when the value of 2336 the 'mplsLdpEntityInitSesThreshold' object 2337 is not zero, and the number of Session 2338 Initialization messages exceeds the value 2339 of the 'mplsLdpEntityInitSesThreshold' object." 2340 ::= { mplsLdpNotifications 1 } 2342 mplsLdpPathVectorLimitMismatch NOTIFICATION-TYPE 2343 OBJECTS { 2344 mplsLdpEntityPathVectorLimit, 2345 mplsLdpPeerPathVectorLimit 2346 } 2347 STATUS current 2348 DESCRIPTION 2349 "If this notification is enabled to generated, 2350 then this notification is sent when the 2351 'mplsLdpEntityPathVectorLimit' does NOT match 2352 the value of the 'mplsLdpPeerPathVectorLimit' for 2353 a specific Entity." 2354 REFERENCE 2355 "[RFC3036], LDP Specification, Section 3.5.3." 2356 ::= { mplsLdpNotifications 2 } 2358 mplsLdpSesUp NOTIFICATION-TYPE 2359 OBJECTS { 2360 mplsLdpSesState, 2361 mplsLdpSesDiscontinuityTime, 2362 mplsLdpSesStatsUnkMesTypeErrors, 2363 mplsLdpSesStatsUnkTlvErrors 2364 } 2365 STATUS current 2366 DESCRIPTION 2367 "If this notification is enabled to generated, 2368 then this notification is sent when the 2369 value of 'mplsLdpSesState' enters 2370 the 'operational(5)' state." 2371 ::= { mplsLdpNotifications 3 } 2373 mplsLdpSesDown NOTIFICATION-TYPE 2374 OBJECTS { 2375 mplsLdpSesState, 2376 mplsLdpSesDiscontinuityTime, 2377 mplsLdpSesStatsUnkMesTypeErrors, 2378 mplsLdpSesStatsUnkTlvErrors 2380 } 2381 STATUS current 2382 DESCRIPTION 2383 "If this notification is enabled to generated, 2384 then this notification is sent when the 2385 the value of 'mplsLdpSesState' leaves 2386 the 'operational(5)' state." 2387 ::= { mplsLdpNotifications 4 } 2389 --**************************************************************** 2390 -- Module Conformance Statement 2391 --**************************************************************** 2393 mplsLdpGroups 2394 OBJECT IDENTIFIER ::= { mplsLdpConformance 1 } 2396 mplsLdpCompliances 2397 OBJECT IDENTIFIER ::= { mplsLdpConformance 2 } 2399 -- 2400 -- Full Compliance 2401 -- 2403 mplsLdpModuleFullCompliance MODULE-COMPLIANCE 2404 STATUS current 2405 DESCRIPTION 2406 "The Module is implemented with support 2407 for read-create and read-write. In other 2408 words, both monitoring and configuration 2409 are available when using this MODULE-COMPLIANCE." 2411 MODULE -- this module 2412 MANDATORY-GROUPS { mplsLdpGeneralGroup, 2413 mplsLdpNotificationsGroup 2414 } 2416 GROUP mplsLdpLspGroup 2417 DESCRIPTION 2418 "This group must be supported if the LSR MIB is 2419 implemented, specifically the mplsInSegmentTable, 2420 the mplsOutSegmentTable or the mplsXCTable." 2422 OBJECT mplsLdpEntityTargetPeerAddrType 2423 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2424 DESCRIPTION 2425 "An implementation is only required to support 2426 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2428 OBJECT mplsLdpEntityTargetPeerAddr 2429 SYNTAX InetAddress (SIZE(0|4|16)) 2430 DESCRIPTION 2431 "An implementation is only required to support IPv4 and 2432 globally unique IPv6 addresses." 2434 OBJECT mplsLdpEntityRowStatus 2435 SYNTAX RowStatus { active(1) } 2436 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 2437 DESCRIPTION 2438 "Support for createAndWait and notInService is not 2439 required." 2441 OBJECT mplsFecAddrFamily 2442 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2443 DESCRIPTION 2444 "An implementation is only required to support 2445 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2447 OBJECT mplsFecAddr 2448 SYNTAX InetAddress (SIZE(0|4|16)) 2449 DESCRIPTION 2450 "An implementation is only required to support IPv4 and 2451 globally unique IPv6 addresses." 2453 OBJECT mplsFecRowStatus 2454 SYNTAX RowStatus { active(1) } 2455 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 2456 MIN-ACCESS read-only 2457 DESCRIPTION 2458 "Support for createAndWait and notInService is not 2459 required. Also, the entries in this table may be 2460 created by the agent, so strictly speaking 2461 read-create functionality is not necessary, but 2462 may be nice to have." 2464 OBJECT mplsLdpLspFecRowStatus 2465 SYNTAX RowStatus { active(1) } 2466 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 2467 MIN-ACCESS read-only 2468 DESCRIPTION 2469 "Support for createAndWait and notInService is not 2470 required. Also, the entries in this table may be 2471 created by the agent, so strictly speaking 2472 read-create functionality is not necessary, but 2473 may be nice to have." 2475 OBJECT mplsLdpSesPeerNextHopAddrType 2476 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2477 DESCRIPTION 2478 "An implementation is only required to support 2479 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2481 OBJECT mplsLdpSesPeerNextHopAddr 2482 SYNTAX InetAddress (SIZE(0|4|16)) 2483 DESCRIPTION 2484 "An implementation is only required to support IPv4 2485 and globally unique IPv6 addresses." 2487 ::= { mplsLdpCompliances 1 } 2489 -- 2490 -- Read-Only Compliance 2491 -- 2493 mplsLdpModuleReadOnlyCompliance MODULE-COMPLIANCE 2494 STATUS current 2495 DESCRIPTION 2496 "The Module is implemented with support 2497 for read-only. In other words, only monitoring 2498 is available by implementing this MODULE-COMPLIANCE." 2500 MODULE -- this module 2501 MANDATORY-GROUPS { mplsLdpGeneralGroup, 2502 mplsLdpNotificationsGroup 2503 } 2505 GROUP mplsLdpLspGroup 2506 DESCRIPTION 2507 "This group must be supported if the LSR MIB is 2508 implemented, specifically the mplsInSegmentTable, 2509 the mplsOutSegmentTable or the mplsXCTable." 2511 OBJECT mplsLdpEntityProtocolVersion 2512 MIN-ACCESS read-only 2513 DESCRIPTION 2514 "Write access is not required." 2516 OBJECT mplsLdpEntityAdminStatus 2517 MIN-ACCESS read-only 2518 DESCRIPTION 2519 "Write access is not required." 2521 OBJECT mplsLdpEntityTcpDscPort 2522 MIN-ACCESS read-only 2523 DESCRIPTION 2524 "Write access is not required." 2526 OBJECT mplsLdpEntityUdpDscPort 2527 MIN-ACCESS read-only 2528 DESCRIPTION 2529 "Write access is not required." 2531 OBJECT mplsLdpEntityMaxPduLength 2532 MIN-ACCESS read-only 2533 DESCRIPTION 2534 "Write access is not required." 2536 OBJECT mplsLdpEntityKeepAliveHoldTimer 2537 MIN-ACCESS read-only 2538 DESCRIPTION 2539 "Write access is not required." 2541 OBJECT mplsLdpEntityHelloHoldTimer 2542 MIN-ACCESS read-only 2543 DESCRIPTION 2544 "Write access is not required." 2546 OBJECT mplsLdpEntityInitSesThreshold 2547 MIN-ACCESS read-only 2548 DESCRIPTION 2549 "Write access is not required." 2551 OBJECT mplsLdpEntityLabelDistMethod 2552 MIN-ACCESS read-only 2553 DESCRIPTION 2554 "Write access is not required." 2556 OBJECT mplsLdpEntityLabelRetentionMode 2557 MIN-ACCESS read-only 2558 DESCRIPTION 2559 "Write access is not required." 2561 OBJECT mplsLdpEntityPathVectorLimit 2562 MIN-ACCESS read-only 2563 DESCRIPTION 2564 "Write access is not required." 2566 OBJECT mplsLdpEntityHopCountLimit 2567 MIN-ACCESS read-only 2568 DESCRIPTION 2569 "Write access is not required." 2571 OBJECT mplsLdpEntityTransportAddrKind 2572 MIN-ACCESS read-only 2573 DESCRIPTION 2574 "Write access is not required." 2576 OBJECT mplsLdpEntityTargetPeer 2577 MIN-ACCESS read-only 2578 DESCRIPTION 2579 "Write access is not required." 2581 OBJECT mplsLdpEntityTargetPeerAddrType 2582 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2583 MIN-ACCESS read-only 2584 DESCRIPTION 2585 "Write access is not required. 2586 An implementation is only required to support 2587 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2589 OBJECT mplsLdpEntityTargetPeerAddr 2590 SYNTAX InetAddress (SIZE(0|4|16)) 2591 MIN-ACCESS read-only 2592 DESCRIPTION 2593 "Write access is not required. 2594 An implementation is only required to support IPv4 and 2595 globally unique IPv6 addresses." 2597 OBJECT mplsLdpEntityLabelType 2598 MIN-ACCESS read-only 2599 DESCRIPTION 2600 "Write access is not required." 2602 OBJECT mplsLdpEntityStorageType 2603 MIN-ACCESS read-only 2604 DESCRIPTION 2605 "Write access is not required." 2607 OBJECT mplsLdpEntityRowStatus 2608 SYNTAX RowStatus { active(1) } 2609 MIN-ACCESS read-only 2610 DESCRIPTION 2611 "Write access is not required, and active is the 2612 only status that needs to be supported." 2614 OBJECT mplsFecType 2615 MIN-ACCESS read-only 2616 DESCRIPTION 2617 "Write access is not required." 2619 OBJECT mplsFecAddrPrefixLength 2620 MIN-ACCESS read-only 2621 DESCRIPTION 2622 "Write access is not required." 2624 OBJECT mplsFecAddrFamily 2625 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2626 MIN-ACCESS read-only 2627 DESCRIPTION 2628 "Write access is not required. 2629 An implementation is only required to support 2630 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2632 OBJECT mplsFecAddr 2633 SYNTAX InetAddress (SIZE(0|4|16)) 2634 MIN-ACCESS read-only 2635 DESCRIPTION 2636 "Write access is not required. 2637 An implementation is only required to support IPv4 and 2638 globally unique IPv6 addresses." 2640 OBJECT mplsFecStorageType 2641 MIN-ACCESS read-only 2642 DESCRIPTION 2643 "Write access is not required." 2645 OBJECT mplsFecRowStatus 2646 SYNTAX RowStatus { active(1) } 2647 MIN-ACCESS read-only 2648 DESCRIPTION 2649 "Write access is not required, and active is the 2650 only status that needs to be supported." 2652 OBJECT mplsLdpLspFecStorageType 2653 MIN-ACCESS read-only 2654 DESCRIPTION 2655 "Write access is not required." 2657 OBJECT mplsLdpLspFecRowStatus 2658 SYNTAX RowStatus { active(1) } 2659 MIN-ACCESS read-only 2660 DESCRIPTION 2661 "Write access is not required, and active is the 2662 only status that needs to be supported." 2664 OBJECT mplsLdpSesPeerNextHopAddrType 2665 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2666 DESCRIPTION 2667 "An implementation is only required to support 2668 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2670 OBJECT mplsLdpSesPeerNextHopAddr 2671 SYNTAX InetAddress (SIZE(0|4|16)) 2672 DESCRIPTION 2673 "An implementation is only required to support IPv4 2674 and globally unique IPv6 addresses." 2676 ::= { mplsLdpCompliances 2 } 2678 -- units of conformance 2680 mplsLdpGeneralGroup OBJECT-GROUP 2681 OBJECTS { 2682 mplsLdpLsrId, 2683 mplsLdpLsrLoopDetectionCapable, 2684 mplsLdpEntityLastChange, 2685 mplsLdpEntityIndexNext, 2686 mplsLdpEntityProtocolVersion, 2687 mplsLdpEntityAdminStatus, 2688 mplsLdpEntityOperStatus, 2689 mplsLdpEntityTcpDscPort, 2690 mplsLdpEntityUdpDscPort, 2691 mplsLdpEntityMaxPduLength, 2692 mplsLdpEntityKeepAliveHoldTimer, 2693 mplsLdpEntityHelloHoldTimer, 2694 mplsLdpEntityInitSesThreshold, 2695 mplsLdpEntityLabelDistMethod, 2696 mplsLdpEntityLabelRetentionMode, 2697 mplsLdpEntityPathVectorLimit, 2698 mplsLdpEntityHopCountLimit, 2699 mplsLdpEntityTransportAddrKind, 2700 mplsLdpEntityTargetPeer, 2701 mplsLdpEntityTargetPeerAddrType, 2702 mplsLdpEntityTargetPeerAddr, 2703 mplsLdpEntityLabelType, 2704 mplsLdpEntityDiscontinuityTime, 2705 mplsLdpEntityStorageType, 2706 mplsLdpEntityRowStatus, 2707 mplsLdpEntityStatsSesAttempts, 2708 mplsLdpEntityStatsSesRejectedNoHelloErrors, 2709 mplsLdpEntityStatsSesRejectedAdErrors, 2710 mplsLdpEntityStatsSesRejectedMaxPduErrors, 2711 mplsLdpEntityStatsSesRejectedLRErrors, 2712 mplsLdpEntityStatsBadLdpIdentifierErrors, 2713 mplsLdpEntityStatsBadPduLengthErrors, 2714 mplsLdpEntityStatsBadMessageLengthErrors, 2715 mplsLdpEntityStatsBadTlvLengthErrors, 2716 mplsLdpEntityStatsMalformedTlvValueErrors, 2717 mplsLdpEntityStatsKeepAliveTimerExpErrors, 2718 mplsLdpEntityStatsShutdownReceivedNotifications, 2719 mplsLdpEntityStatsShutdownSentNotifications, 2720 mplsLdpPeerLastChange, 2721 mplsLdpPeerLabelDistMethod, 2722 mplsLdpPeerPathVectorLimit, 2723 mplsLdpPeerTransportAddrType, 2724 mplsLdpPeerTransportAddr, 2725 mplsLdpHelloAdjacencyHoldTimeRem, 2726 mplsLdpHelloAdjacencyHoldTime, 2727 mplsLdpHelloAdjacencyType, 2728 mplsLdpSesStateLastChange, 2729 mplsLdpSesState, 2730 mplsLdpSesRole, 2731 mplsLdpSesProtocolVersion, 2732 mplsLdpSesKeepAliveHoldTimeRem, 2733 mplsLdpSesKeepAliveTime, 2734 mplsLdpSesMaxPduLength, 2735 mplsLdpSesDiscontinuityTime, 2736 mplsLdpSesStatsUnkMesTypeErrors, 2737 mplsLdpSesStatsUnkTlvErrors, 2738 mplsLdpSesPeerNextHopAddrType, 2739 mplsLdpSesPeerNextHopAddr, 2740 mplsFecIndexNext, 2741 mplsFecType, 2742 mplsFecAddrPrefixLength, 2743 mplsFecAddrFamily, 2744 mplsFecAddr, 2745 mplsFecStorageType, 2746 mplsFecRowStatus 2747 } 2748 STATUS current 2749 DESCRIPTION 2750 "Objects that apply to all MPLS LDP implementations." 2751 ::= { mplsLdpGroups 1 } 2753 mplsLdpLspGroup OBJECT-GROUP 2754 OBJECTS { 2755 mplsInSegmentLdpLspLabelType, 2756 mplsInSegmentLdpLspType, 2757 mplsOutSegmentLdpLspLabelType, 2758 mplsOutSegmentLdpLspType, 2759 mplsLdpLspFecOperStatus, 2760 mplsLdpLspFecLastChange, 2761 mplsLdpLspFecStorageType, 2762 mplsLdpLspFecRowStatus 2763 } 2764 STATUS current 2765 DESCRIPTION 2766 "These objects are optional and only need to be supported 2767 for LDP implementations which support the following 2768 tables in the LSR MIB: mplsInSegmentTable, 2769 mplsOutSegmentTable and mplsXCTable." 2770 ::= { mplsLdpGroups 2 } 2772 mplsLdpNotificationsGroup NOTIFICATION-GROUP 2773 NOTIFICATIONS { mplsLdpInitSesThresholdExceeded, 2774 mplsLdpPathVectorLimitMismatch, 2775 mplsLdpSesUp, 2776 mplsLdpSesDown 2777 } 2778 STATUS current 2779 DESCRIPTION 2780 "The notification(s) which an MPLS LDP implemention 2781 is required to implement." 2782 ::= { mplsLdpGroups 3 } 2784 END 2786 4.1. The MPLS-LDP-ATM-MIB Module 2788 This MIB Module MUST be supported if LDP uses ATM as the Layer 2 2789 media. There are three tables in this MIB Module. Two tables are 2790 for configuring LDP to use ATM. These tables are the 2791 mplsLdpEntityAtmParmsTable and the mplsLdpEntityAtmLabelRangeTable. 2793 The mplsLdpEntityAtmParmsTable provides a way to configure 2794 information which would be contained in the "Optional Parameter" 2795 portion of an LDP PDU Initialization Message. 2797 The mplsLdpEntityAtmLabelRangeTable provides a way to configure 2798 information which would be contained in the "ATM Label Range 2799 Components" portion of an LDP PDU Intialization Message, see 2800 [RFC3035] and [RFC3036]. 2802 4.1.1. The LDP ATM Session Table 2804 The MPLS LDP ATM Session Table is a read-only table which contains 2805 session information specific to ATM. 2807 MPLS-LDP-ATM-MIB DEFINITIONS ::= BEGIN 2809 IMPORTS 2810 OBJECT-TYPE, MODULE-IDENTITY, 2811 Unsigned32 2812 FROM SNMPv2-SMI 2813 MODULE-COMPLIANCE, OBJECT-GROUP 2814 FROM SNMPv2-CONF 2816 RowStatus, 2817 StorageType 2818 FROM SNMPv2-TC 2820 InterfaceIndexOrZero 2821 FROM IF-MIB 2823 AtmVpIdentifier 2824 FROM ATM-TC-MIB 2826 mplsMIB, 2827 MplsAtmVcIdentifier 2828 FROM MPLS-TC-MIB 2830 mplsLdpEntityLdpId, 2831 mplsLdpEntityIndex, 2832 mplsLdpPeerLdpId 2833 FROM MPLS-LDP-MIB 2835 ; 2837 mplsLdpAtmMIB MODULE-IDENTITY 2838 LAST-UPDATED "200304221200Z" -- 22 April 2003 2839 ORGANIZATION "Multiprotocol Label Switching (mpls) 2840 Working Group" 2841 CONTACT-INFO 2842 "Joan Cucchiara (jcucchiara@artel.com) 2843 Artel 2845 Hans Sjostrand (hans@ipunplugged.com) 2846 ipUnplugged 2848 James V. Luciani (james_luciani@mindspring.com) 2849 Consultant 2851 Working Group Chairs: 2852 George Swallow, email: swallow@cisco.com 2853 Loa Andersson, email: loa@pi.se 2855 MPLS Working Group, email: mpls@uu.net 2856 " 2857 DESCRIPTION 2858 "Copyright (C) The Internet Society (2003). This 2859 version of this MIB module is part of RFCXXX; see 2860 the RFC itself for full legal notices. 2862 This MIB contains managed object definitions for 2863 configuring and monitoring the Multiprotocol Label 2864 Switching (MPLS), Label Distribution Protocol (LDP), 2865 utilizing Asynchronous Transfer Mode (ATM) as the Layer 2 2866 media." 2867 REVISION "200304221200Z" -- 22 April 2003 2868 DESCRIPTION 2869 "Initial version published as part of RFC XXXX." 2871 -- Please see the IANA Considerations Section 2872 -- the suggested mplsMIB subId is 5, e.g. 2873 -- ::= { mplsMIB 5 } 2875 ::= { mplsMIB XXX } -- to be assigned by IANA 2877 --**************************************************************** 2878 mplsLdpAtmObjects OBJECT IDENTIFIER ::= { mplsLdpAtmMIB 1 } 2879 mplsLdpAtmConformance OBJECT IDENTIFIER ::= { mplsLdpAtmMIB 2 } 2881 --**************************************************************** 2882 -- MPLS LDP ATM Objects 2883 --**************************************************************** 2885 -- 2886 -- Ldp Entity Objects for ATM 2887 -- 2889 mplsLdpEntityAtmObjects OBJECT IDENTIFIER ::= 2890 { mplsLdpAtmObjects 1 } 2892 mplsLdpEntityAtmTable OBJECT-TYPE 2893 SYNTAX SEQUENCE OF MplsLdpEntityAtmEntry 2894 MAX-ACCESS not-accessible 2895 STATUS current 2896 DESCRIPTION 2897 "This table contains information about the 2898 ATM specific information which could be used 2899 in the 'Optional Parameters' and other ATM specific 2900 information. 2902 This table 'extends' the mplsLdpEntityTable when 2903 ATM as the Layer 2 media." 2904 ::= { mplsLdpEntityAtmObjects 1 } 2906 mplsLdpEntityAtmEntry OBJECT-TYPE 2907 SYNTAX MplsLdpEntityAtmEntry 2908 MAX-ACCESS not-accessible 2909 STATUS current 2910 DESCRIPTION 2911 "An entry in this table represents the ATM parameters 2912 and ATM information for this LDP entity." 2913 INDEX { mplsLdpEntityLdpId, 2914 mplsLdpEntityIndex 2915 } 2916 ::= { mplsLdpEntityAtmTable 1 } 2918 MplsLdpEntityAtmEntry ::= SEQUENCE { 2919 mplsLdpEntityAtmIfIndexOrZero InterfaceIndexOrZero, 2920 mplsLdpEntityAtmMergeCap INTEGER, 2921 mplsLdpEntityAtmLRComponents Unsigned32, 2922 mplsLdpEntityAtmVcDirectionality INTEGER, 2923 mplsLdpEntityAtmLsrConnectivity INTEGER, 2924 mplsLdpEntityAtmDefaultControlVpi AtmVpIdentifier, 2925 mplsLdpEntityAtmDefaultControlVci MplsAtmVcIdentifier, 2926 mplsLdpEntityAtmUnlabTrafVpi AtmVpIdentifier, 2927 mplsLdpEntityAtmUnlabTrafVci MplsAtmVcIdentifier, 2928 mplsLdpEntityAtmStorageType StorageType, 2929 mplsLdpEntityAtmRowStatus RowStatus 2930 } 2932 mplsLdpEntityAtmIfIndexOrZero OBJECT-TYPE 2933 SYNTAX InterfaceIndexOrZero 2934 MAX-ACCESS read-create 2935 STATUS current 2936 DESCRIPTION 2937 "This value represents either the InterfaceIndex of 2938 the 'ifLayer' where the ATM Labels 'owned' by this 2939 entry were created, or 0 (zero). The value of zero 2940 means that the InterfaceIndex is not known. For example, 2941 if the InterfaceIndex is created subsequent to the 2942 ATM Label's creation, then it would not be known. 2943 However, if the InterfaceIndex is known, then it must 2944 be represented by this value. 2946 If an InterfaceIndex becomes known, then the 2947 network management entity (e.g. SNMP agent) responsible 2948 for this object MUST change the value from 0 (zero) to the 2949 value of the InterfaceIndex. If an ATM Label is 2950 being used in forwarding data, then the value of this 2951 object MUST be the InterfaceIndex." 2952 ::= { mplsLdpEntityAtmEntry 1 } 2954 mplsLdpEntityAtmMergeCap OBJECT-TYPE 2955 SYNTAX INTEGER { 2956 notSupported(0), 2957 vpMerge(1), 2958 vcMerge(2), 2959 vpAndVcMerge(3) 2960 } 2961 MAX-ACCESS read-create 2962 STATUS current 2963 DESCRIPTION 2964 "Denotes the Merge Capability of this Entity. 2965 This is the EXACT value for the ATM Session Parameter, 2966 field M (for ATM Merge Capabilities). The ATM Session Parameter 2967 is an optional parameter in the Initialization Message. 2969 The description from rfc3036.txt is: 2971 'M, ATM Merge Capabilities 2972 Specifies the merge capabilities of an ATM switch. The 2973 following values are supported in this version of the 2974 specification: 2976 Value Meaning 2978 0 Merge not supported 2979 1 VP Merge supported 2980 2 VC Merge supported 2981 3 VP & VC Merge supported 2983 If the merge capabilities of the LSRs differ, then: 2984 - Non-merge and VC-merge LSRs may freely interoperate. 2986 - The interoperability of VP-merge-capable switches with non- 2987 VP-merge-capable switches is a subject for future study. 2988 When the LSRs differ on the use of VP-merge, the session is 2989 established, but VP merge is not used.' 2991 Please refer to the following reference for a complete 2992 description of this feature." 2993 REFERENCE 2994 "[RFC3036] LDP Specification, Section 3.5.3 Initialization Message." 2995 ::= { mplsLdpEntityAtmEntry 2 } 2997 mplsLdpEntityAtmLRComponents OBJECT-TYPE 2998 SYNTAX Unsigned32 (1..65535) 2999 MAX-ACCESS read-create 3000 STATUS current 3001 DESCRIPTION 3002 "Number of Label Range Components in the Initialization 3003 message. This also represents the number of entries 3004 in the mplsLdpEntityAtmLRTable which correspond 3005 to this entry. 3007 This is the EXACT value for the ATM Session Parameter, 3008 field N (for Number of label range components). The ATM 3009 Session Parameter is an optional parameter in the Initialization 3010 Message. 3012 The description from rfc3036.txt is: 3014 'N, Number of label range components 3015 Specifies the number of ATM Label Range Components 3016 included in the TLV.' 3018 Please refer to the following reference for a complete 3019 description of this feature." 3020 REFERENCE 3021 "[RFC3036] LDP Specification, Section 3.5.3 Initialization Message." 3022 ::= { mplsLdpEntityAtmEntry 3 } 3024 mplsLdpEntityAtmVcDirectionality OBJECT-TYPE 3025 SYNTAX INTEGER { 3026 bidirectional(0), 3027 unidirectional(1) 3028 } 3029 MAX-ACCESS read-create 3030 STATUS current 3031 DESCRIPTION 3032 "If the value of this object is 'bidirectional(0)', 3033 a given VCI, within a given VPI, is used as a 3034 label for both directions independently. 3036 If the value of this object is 'unidirectional(1)', 3037 a given VCI within a VPI designates one direction. 3039 This is the EXACT value for the ATM Session Parameter, 3040 field D (for VC Directionality). The ATM Session Parameter 3041 is an optional parameter in the Initialization Message. 3043 The description from rfc3036.txt is: 3045 'D, VC Directionality 3046 A value of 0 specifies bidirectional VC capability, meaning the 3047 LSR can (within a given VPI) support the use of a given VCI as 3048 a label for both link directions independently. A value of 1 3049 specifies unidirectional VC capability, meaning (within a given 3050 VPI) a given VCI may appear in a label mapping for one 3051 direction on the link only. When either or both of the peers 3052 specifies unidirectional VC capability, both LSRs use 3053 unidirectional VC label assignment for the link as follows. 3054 The LSRs compare their LDP Identifiers as unsigned integers. 3055 The LSR with the larger LDP Identifier may assign only odd- 3056 numbered VCIs in the VPI/VCI range as labels. The system with 3057 the smaller LDP Identifier may assign only even-numbered VCIs 3058 in the VPI/VCI range as labels.' 3059 Please refer to the following reference for a complete 3060 description of this feature." 3061 REFERENCE 3062 "[RFC3036] LDP Specification, Section 3.5.3 Initialization Message." 3063 ::= { mplsLdpEntityAtmEntry 4 } 3065 mplsLdpEntityAtmLsrConnectivity OBJECT-TYPE 3066 SYNTAX INTEGER { 3067 direct(1), 3068 indirect(2) 3069 } 3070 MAX-ACCESS read-create 3071 STATUS current 3072 DESCRIPTION 3073 "The peer LSR may be connected indirectly by means of an 3074 ATM VP so that the VPI values may be different on either 3075 endpoint so the label MUST be encoded entirely within the 3076 VCI field." 3077 DEFVAL { direct } 3078 ::= { mplsLdpEntityAtmEntry 5 } 3080 mplsLdpEntityAtmDefaultControlVpi OBJECT-TYPE 3081 SYNTAX AtmVpIdentifier 3082 MAX-ACCESS read-create 3083 STATUS current 3084 DESCRIPTION 3085 "The default VPI value for the non-MPLS connection. The 3086 default value of this is 0 (zero) but other values may 3087 be configured. This object allows a different value 3088 to be configured." 3089 DEFVAL { 0 } 3090 ::= { mplsLdpEntityAtmEntry 6 } 3092 mplsLdpEntityAtmDefaultControlVci OBJECT-TYPE 3093 SYNTAX MplsAtmVcIdentifier 3094 MAX-ACCESS read-create 3095 STATUS current 3096 DESCRIPTION 3097 "The Default VCI value for a non-MPLS connection. The 3098 default value of this is 32 but other values may be 3099 configured. This object allows a different value to 3100 be configured." 3101 DEFVAL { 32 } 3102 ::= { mplsLdpEntityAtmEntry 7 } 3104 mplsLdpEntityAtmUnlabTrafVpi OBJECT-TYPE 3105 SYNTAX AtmVpIdentifier 3106 MAX-ACCESS read-create 3107 STATUS current 3108 DESCRIPTION 3109 "VPI value of the VCC supporting unlabeled traffic. This 3110 non-MPLS connection is used to carry unlabeled (IP) 3111 packets. The default value is the same as the default 3112 value of the 'mplsLdpEntityAtmDefaultControlVpi', however 3113 another value may be configured." 3114 DEFVAL { 0 } 3115 ::= { mplsLdpEntityAtmEntry 8 } 3117 mplsLdpEntityAtmUnlabTrafVci OBJECT-TYPE 3118 SYNTAX MplsAtmVcIdentifier 3119 MAX-ACCESS read-create 3120 STATUS current 3121 DESCRIPTION 3122 "VCI value of the VCC supporting unlabeled traffic. 3123 This non-MPLS connection is used to carry unlabeled (IP) 3124 packets. The default value is the same as the default 3125 value of the 'mplsLdpEntityAtmDefaultControlVci', however 3126 another value may be configured." 3127 DEFVAL { 32 } 3128 ::= { mplsLdpEntityAtmEntry 9 } 3130 mplsLdpEntityAtmStorageType OBJECT-TYPE 3131 SYNTAX StorageType 3132 MAX-ACCESS read-create 3133 STATUS current 3134 DESCRIPTION 3135 "The storage type for this conceptual row. Conceptual rows 3136 having the value 'permanent(4)' MAY allow write-access to any 3137 columnar objects in the row, except for setting the 3138 mplsLdpEntityAtmRowStatus to 'destroy(6)'." 3139 DEFVAL { nonVolatile } 3140 ::= { mplsLdpEntityAtmEntry 10 } 3142 mplsLdpEntityAtmRowStatus OBJECT-TYPE 3143 SYNTAX RowStatus 3144 MAX-ACCESS read-create 3145 STATUS current 3146 DESCRIPTION 3147 "The status of this conceptual row. All writable objects in this 3148 row may be modified at any time, however, as described in 3149 detail in the section entitled, 'Changing Values After Session 3150 Establishment', and again described in the 3151 DESCRIPTION clause of the mplsLdpEntityAdminStatus object, 3152 if a session has been initiated with a Peer, 3153 changing objects in this table will 3154 wreak havoc with the session and interrupt traffic. To repeat again: 3155 the recommended procedure is to set the mplsLdpEntityAdminStatus to 3156 down, thereby explicitely causing a session to be torn down. Then, 3157 change objects in this entry, then set the mplsLdpEntityAdminStatus 3158 to enable which enables a NEW session to be initiated. 3160 NOTE: This RowStatus object should 3161 have the same value of the 'mplsLdpEntityRowStatus' 3162 related to this entry." 3163 ::= { mplsLdpEntityAtmEntry 11 } 3165 -- 3166 -- The MPLS LDP Entity ATM Label Range Table 3167 -- 3169 mplsLdpEntityAtmLRTable OBJECT-TYPE 3170 SYNTAX SEQUENCE OF MplsLdpEntityAtmLREntry 3171 MAX-ACCESS not-accessible 3172 STATUS current 3173 DESCRIPTION 3174 "The MPLS LDP Entity ATM Label Range (LR) Table. 3175 The purpose of this table is to provide a mechanism 3176 for configuring a contiguous range of vpi's 3177 with a contiguous range of vci's, or a 'label range' 3178 for LDP Entities. 3180 LDP Entities which use ATM must have at least one 3181 entry in this table." 3182 ::= { mplsLdpEntityAtmObjects 2 } 3184 mplsLdpEntityAtmLREntry OBJECT-TYPE 3185 SYNTAX MplsLdpEntityAtmLREntry 3186 MAX-ACCESS not-accessible 3187 STATUS current 3188 DESCRIPTION 3189 "A row in the LDP Entity ATM Label 3190 Range Table. One entry in this table contains 3191 information on a single range of labels 3192 represented by the configured Upper and Lower 3193 Bounds VPI/VCI pairs. These are the same 3194 data used in the Initialization Message. 3196 NOTE: The ranges for a specific LDP Entity 3197 are UNIQUE and non-overlapping. For example, 3198 for a specific LDP Entity index, there could 3199 be one entry having LowerBound vpi/vci == 0/32, and 3200 UpperBound vpi/vci == 0/100, and a second entry 3201 for this same interface with LowerBound 3202 vpi/vci == 0/101 and UpperBound vpi/vci == 0/200. 3203 However, there could not be a third entry with 3204 LowerBound vpi/vci == 0/200 and 3205 UpperBound vpi/vci == 0/300 because this label 3206 range overlaps with the second entry (i.e. both 3207 entries now have 0/200). 3209 A row will not be created unless a unique and 3210 non-overlapping range is specified. Thus, row 3211 creation implies a one-shot row creation of 3212 LDP EntityID and LowerBound vpi/vci and 3213 UpperBound vpi/vci. At least one label 3214 range entry for a specific LDP Entity MUST 3215 include the default VPI/VCI values denoted 3216 in the LDP Entity Table." 3217 INDEX { mplsLdpEntityLdpId, 3218 mplsLdpEntityIndex, 3219 mplsLdpEntityAtmLRMinVpi, 3220 mplsLdpEntityAtmLRMinVci 3221 } 3222 ::= { mplsLdpEntityAtmLRTable 1 } 3224 MplsLdpEntityAtmLREntry ::= SEQUENCE { 3225 mplsLdpEntityAtmLRMinVpi AtmVpIdentifier, 3226 mplsLdpEntityAtmLRMinVci MplsAtmVcIdentifier, 3227 mplsLdpEntityAtmLRMaxVpi AtmVpIdentifier, 3228 mplsLdpEntityAtmLRMaxVci MplsAtmVcIdentifier, 3229 mplsLdpEntityAtmLRStorageType StorageType, 3230 mplsLdpEntityAtmLRRowStatus RowStatus 3231 } 3233 mplsLdpEntityAtmLRMinVpi OBJECT-TYPE 3234 SYNTAX AtmVpIdentifier 3235 MAX-ACCESS not-accessible 3236 STATUS current 3237 DESCRIPTION 3238 "The minimum VPI number configured for this range. 3239 The value of zero is a valid value for the VPI portion 3240 of the label." 3241 ::= { mplsLdpEntityAtmLREntry 1 } 3243 mplsLdpEntityAtmLRMinVci OBJECT-TYPE 3244 SYNTAX MplsAtmVcIdentifier 3245 MAX-ACCESS not-accessible 3246 STATUS current 3247 DESCRIPTION 3248 "The minimum VCI number configured for this range." 3249 ::= { mplsLdpEntityAtmLREntry 2 } 3251 mplsLdpEntityAtmLRMaxVpi OBJECT-TYPE 3252 SYNTAX AtmVpIdentifier 3253 MAX-ACCESS read-create 3254 STATUS current 3255 DESCRIPTION 3256 "The maximum VPI number configured for this range." 3257 ::= { mplsLdpEntityAtmLREntry 3 } 3259 mplsLdpEntityAtmLRMaxVci OBJECT-TYPE 3260 SYNTAX MplsAtmVcIdentifier 3261 MAX-ACCESS read-create 3262 STATUS current 3263 DESCRIPTION 3264 "The maximum VCI number configured for this range." 3265 ::= { mplsLdpEntityAtmLREntry 4 } 3267 mplsLdpEntityAtmLRStorageType OBJECT-TYPE 3268 SYNTAX StorageType 3269 MAX-ACCESS read-create 3270 STATUS current 3271 DESCRIPTION 3272 "The storage type for this conceptual row. Conceptual rows 3273 having the value 'permanent(4)' need not allow write-access to any 3274 columnar objects in the row." 3275 DEFVAL { nonVolatile } 3276 ::= { mplsLdpEntityAtmLREntry 5 } 3278 mplsLdpEntityAtmLRRowStatus OBJECT-TYPE 3279 SYNTAX RowStatus 3280 MAX-ACCESS read-create 3281 STATUS current 3282 DESCRIPTION 3283 "The status of this conceptual row. All writable objects in this 3284 row may be modified at any time, however, as described in 3285 detail in the section entitled, 'Changing Values After Session 3286 Establishment', and again described in the 3287 DESCRIPTION clause of the mplsLdpEntityAdminStatus object, 3288 if a session has been initiated with a Peer, 3289 changing objects in this table will 3290 wreak havoc with the session and interrupt traffic. To repeat again: 3291 the recommended procedure is to set the mplsLdpEntityAdminStatus to 3292 down, thereby explicitely causing a session to be torn down. Then, 3293 change objects in this entry, then set the mplsLdpEntityAdminStatus 3294 to enable which enables a NEW session to be initiated. 3296 There must exist at least one entry in this 3297 table for every LDP Entity that has 3298 'mplsLdpEntityOptionalParameters' object with 3299 a value of 'atmSessionParameters'. 3301 NOTE: This RowStatus object should 3302 have the same value of the 'mplsLdpEntityRowStatus' 3303 related to this entry." 3304 ::= { mplsLdpEntityAtmLREntry 6 } 3306 -- 3307 -- MPLS LDP ATM Session Information 3308 -- 3310 mplsLdpAtmSesObjects OBJECT IDENTIFIER ::= 3311 { mplsLdpAtmObjects 2 } 3313 mplsLdpAtmSesTable OBJECT-TYPE 3314 SYNTAX SEQUENCE OF MplsLdpAtmSesEntry 3315 MAX-ACCESS not-accessible 3316 STATUS current 3317 DESCRIPTION 3318 "A table which relates Sessions in the 3319 'mplsLdpSessionTable' and their label 3320 range intersections. There could be one 3321 or more label range intersections between an 3322 LDP Entity and LDP Peer using ATM as the underlying 3323 media. Each row represents a single label range 3324 intersection. 3326 NOTE: this table cannot use the 'AUGMENTS' 3327 clause because there is not necessarily a one-to-one 3328 mapping between this table and the mplsLdpSessionTable." 3329 ::= { mplsLdpAtmSesObjects 1 } 3331 mplsLdpAtmSesEntry OBJECT-TYPE 3332 SYNTAX MplsLdpAtmSesEntry 3333 MAX-ACCESS not-accessible 3334 STATUS current 3335 DESCRIPTION 3336 "An entry in this table represents information on a 3337 single label range intersection between an LDP Entity 3338 and LDP Peer. 3340 The information contained in a row is read-only." 3341 INDEX { mplsLdpEntityLdpId, 3342 mplsLdpEntityIndex, 3343 mplsLdpPeerLdpId, 3344 mplsLdpSesAtmLRLowerBoundVpi, 3345 mplsLdpSesAtmLRLowerBoundVci 3347 } 3348 ::= { mplsLdpAtmSesTable 1 } 3350 MplsLdpAtmSesEntry ::= SEQUENCE { 3351 mplsLdpSesAtmLRLowerBoundVpi AtmVpIdentifier, 3352 mplsLdpSesAtmLRLowerBoundVci MplsAtmVcIdentifier, 3353 mplsLdpSesAtmLRUpperBoundVpi AtmVpIdentifier, 3354 mplsLdpSesAtmLRUpperBoundVci MplsAtmVcIdentifier 3355 } 3357 mplsLdpSesAtmLRLowerBoundVpi OBJECT-TYPE 3358 SYNTAX AtmVpIdentifier 3359 MAX-ACCESS not-accessible 3360 STATUS current 3361 DESCRIPTION 3362 "The minimum VPI number for this range." 3363 ::= { mplsLdpAtmSesEntry 1 } 3365 mplsLdpSesAtmLRLowerBoundVci OBJECT-TYPE 3366 SYNTAX MplsAtmVcIdentifier 3367 MAX-ACCESS not-accessible 3368 STATUS current 3369 DESCRIPTION 3370 "The minimum VCI number for this range." 3371 ::= { mplsLdpAtmSesEntry 2 } 3373 mplsLdpSesAtmLRUpperBoundVpi OBJECT-TYPE 3374 SYNTAX AtmVpIdentifier 3375 MAX-ACCESS read-only 3376 STATUS current 3377 DESCRIPTION 3378 "The maximum VPI number for this range." 3379 ::= { mplsLdpAtmSesEntry 3 } 3381 mplsLdpSesAtmLRUpperBoundVci OBJECT-TYPE 3382 SYNTAX MplsAtmVcIdentifier 3383 MAX-ACCESS read-only 3384 STATUS current 3385 DESCRIPTION 3386 "The maximum VCI number for this range." 3387 ::= { mplsLdpAtmSesEntry 4 } 3389 --************************************************************** 3390 -- Module Conformance Statement 3391 --************************************************************** 3393 mplsLdpAtmGroups 3394 OBJECT IDENTIFIER ::= { mplsLdpAtmConformance 1 } 3396 mplsLdpAtmCompliances 3397 OBJECT IDENTIFIER ::= { mplsLdpAtmConformance 2 } 3399 -- 3400 -- Full Compliance 3401 -- 3403 mplsLdpAtmModuleFullCompliance MODULE-COMPLIANCE 3404 STATUS current 3405 DESCRIPTION 3406 "The Module is implemented with support for 3407 read-create and read-write. In other words, 3408 both monitoring and configuration 3409 are available when using this MODULE-COMPLIANCE." 3410 MODULE -- this module 3411 MANDATORY-GROUPS { 3412 mplsLdpAtmGroup 3413 } 3415 OBJECT mplsLdpEntityAtmRowStatus 3416 SYNTAX RowStatus { active(1) } 3417 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 3418 DESCRIPTION 3419 "Support for createAndWait and notInService is not required." 3421 OBJECT mplsLdpEntityAtmLRRowStatus 3422 SYNTAX RowStatus { active(1) } 3423 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 3424 DESCRIPTION 3425 "Support for createAndWait and notInService is not required." 3427 ::= { mplsLdpAtmCompliances 1 } 3429 -- 3430 -- Read-Only Compliance 3431 -- 3433 mplsLdpAtmModuleReadOnlyCompliance MODULE-COMPLIANCE 3434 STATUS current 3435 DESCRIPTION 3436 "The Module is implemented with support for 3437 read-only. In other words, only monitoring 3438 is available by implementing this MODULE-COMPLIANCE." 3439 MODULE -- this module 3440 MANDATORY-GROUPS { 3441 mplsLdpAtmGroup 3442 } 3444 OBJECT mplsLdpEntityAtmIfIndexOrZero 3445 MIN-ACCESS read-only 3446 DESCRIPTION 3447 "Write access is not required." 3449 OBJECT mplsLdpEntityAtmMergeCap 3450 MIN-ACCESS read-only 3451 DESCRIPTION 3452 "Write access is not required." 3454 OBJECT mplsLdpEntityAtmLRComponents 3455 MIN-ACCESS read-only 3456 DESCRIPTION 3457 "Write access is not required." 3459 OBJECT mplsLdpEntityAtmVcDirectionality 3460 MIN-ACCESS read-only 3461 DESCRIPTION 3462 "Write access is not required." 3464 OBJECT mplsLdpEntityAtmLsrConnectivity 3465 MIN-ACCESS read-only 3466 DESCRIPTION 3467 "Write access is not required." 3469 OBJECT mplsLdpEntityAtmDefaultControlVpi 3470 MIN-ACCESS read-only 3471 DESCRIPTION 3472 "Write access is not required." 3474 OBJECT mplsLdpEntityAtmDefaultControlVci 3475 MIN-ACCESS read-only 3476 DESCRIPTION 3477 "Write access is not required." 3479 OBJECT mplsLdpEntityAtmUnlabTrafVpi 3480 MIN-ACCESS read-only 3481 DESCRIPTION 3482 "Write access is not required." 3484 OBJECT mplsLdpEntityAtmUnlabTrafVci 3485 MIN-ACCESS read-only 3486 DESCRIPTION 3487 "Write access is not required." 3489 OBJECT mplsLdpEntityAtmStorageType 3490 MIN-ACCESS read-only 3491 DESCRIPTION 3492 "Write access is not required." 3494 OBJECT mplsLdpEntityAtmRowStatus 3495 SYNTAX RowStatus { active(1) } 3496 MIN-ACCESS read-only 3497 DESCRIPTION 3498 "Write access is not required, and active is the 3499 only status that needs to be supported." 3501 OBJECT mplsLdpEntityAtmLRMaxVpi 3502 MIN-ACCESS read-only 3503 DESCRIPTION 3504 "Write access is not required." 3506 OBJECT mplsLdpEntityAtmLRMaxVci 3507 MIN-ACCESS read-only 3508 DESCRIPTION 3509 "Write access is not required." 3511 OBJECT mplsLdpEntityAtmLRStorageType 3512 MIN-ACCESS read-only 3513 DESCRIPTION 3514 "Write access is not required." 3516 OBJECT mplsLdpEntityAtmLRRowStatus 3517 SYNTAX RowStatus { active(1) } 3518 MIN-ACCESS read-only 3519 DESCRIPTION 3520 "Write access is not required, and active is the 3521 only status that needs to be supported." 3523 ::= { mplsLdpAtmCompliances 2 } 3525 -- 3526 -- units of conformance 3527 -- 3529 mplsLdpAtmGroup OBJECT-GROUP 3530 OBJECTS { 3531 mplsLdpEntityAtmIfIndexOrZero, 3532 mplsLdpEntityAtmMergeCap, 3533 mplsLdpEntityAtmLRComponents, 3534 mplsLdpEntityAtmVcDirectionality, 3535 mplsLdpEntityAtmLsrConnectivity, 3536 mplsLdpEntityAtmDefaultControlVpi, 3537 mplsLdpEntityAtmDefaultControlVci, 3538 mplsLdpEntityAtmUnlabTrafVpi, 3539 mplsLdpEntityAtmUnlabTrafVci, 3540 mplsLdpEntityAtmStorageType, 3541 mplsLdpEntityAtmRowStatus, 3542 mplsLdpEntityAtmLRMaxVpi, 3543 mplsLdpEntityAtmLRMaxVci, 3544 mplsLdpEntityAtmLRStorageType, 3545 mplsLdpEntityAtmLRRowStatus, 3546 mplsLdpSesAtmLRUpperBoundVpi, 3547 mplsLdpSesAtmLRUpperBoundVci 3549 } 3550 STATUS current 3551 DESCRIPTION 3552 "Objects that apply to all MPLS LDP implementations 3553 using ATM as the Layer 2." 3554 ::= { mplsLdpAtmGroups 1 } 3556 END 3558 4.2. The MPLS-LDP-FRAME-RELAY-MIB Module 3560 This MIB Module MUST be supported if LDP uses FRAME RELAY as the 3561 Layer 2 media. There are three tables in this MIB Module. Two 3562 tables are to configure LDP for using Frame Relay. These tables are 3563 the mplsLdpEntityFrameRelayParmsTable and the 3564 mplsLdpEntityFrameRelayLabelRangeTable. 3566 The mplsLdpEntityFrameRelayParmsTable provides a way to configure 3567 information which would be contained in the "Optional Parameter" 3568 portion of an LDP PDU Initialization Message. 3570 The mplsLdpEntityFrameRelayLabelRangeTable provides a way to 3571 configure information which would be contained in the "Frame Relay 3572 Label Range Components" portion of an LDP PDU Intialization Message, 3573 see [RFC3034] and [RFC3036]. 3575 4.2.1. The LDP Frame Relay Session Table 3577 The MPLS LDP Frame Relay Session Table is a read-only table which 3578 contains session information specific to Frame Relay. 3580 MPLS-LDP-FRAME-RELAY-MIB DEFINITIONS ::= BEGIN 3582 IMPORTS 3583 OBJECT-TYPE, 3584 MODULE-IDENTITY, 3585 Unsigned32 3586 FROM SNMPv2-SMI 3587 MODULE-COMPLIANCE, 3588 OBJECT-GROUP 3589 FROM SNMPv2-CONF 3591 RowStatus, 3592 StorageType 3593 FROM SNMPv2-TC 3595 DLCI 3596 FROM FRAME-RELAY-DTE-MIB 3598 InterfaceIndexOrZero 3599 FROM IF-MIB 3601 mplsMIB 3602 FROM MPLS-TC-MIB 3604 mplsLdpEntityLdpId, 3605 mplsLdpEntityIndex, 3606 mplsLdpPeerLdpId 3607 FROM MPLS-LDP-MIB 3609 ; 3611 mplsLdpFrameRelayMIB MODULE-IDENTITY 3612 LAST-UPDATED "200304221200Z" -- 22 April 2003 3613 ORGANIZATION "Multiprotocol Label Switching (mpls) 3614 Working Group" 3615 CONTACT-INFO 3616 "Joan Cucchiara (jcucchiara@artel.com) 3617 Artel 3619 Hans Sjostrand (hans@ipunplugged.com) 3620 ipUnplugged 3622 James V. Luciani (james_luciani@mindspring.com) 3623 Consultant 3625 Working Group Chairs: 3626 George Swallow, email: swallow@cisco.com 3627 Loa Andersson, email: loa@pi.se 3629 MPLS Working Group, email: mpls@uu.net 3630 " 3631 DESCRIPTION 3632 "Copyright (C) The Internet Society (2003). This 3633 version of this MIB module is part of RFCXXX; see 3634 the RFC itself for full legal notices. 3636 This MIB contains managed object definitions for 3637 configuring and monitoring the Multiprotocol Label 3638 Switching (MPLS), Label Distribution Protocol (LDP), 3639 utilizing Frame Relay as the Layer 2 media." 3640 REVISION "200304221200Z" -- 22 April 2003 3641 DESCRIPTION 3642 "Initial version published as part of RFC XXXX." 3644 -- Please see the IANA Considerations Section. 3645 -- The requested mplsMIB subId is 6, e.g. 3646 -- ::= { mplsMIB 6 } 3648 ::= { mplsMIB XXX } -- to be assigned by IANA 3650 --**************************************************************** 3652 mplsLdpFrameRelayObjects 3653 OBJECT IDENTIFIER ::= { mplsLdpFrameRelayMIB 1 } 3654 mplsLdpFrameRelayConformance 3655 OBJECT IDENTIFIER ::= { mplsLdpFrameRelayMIB 2 } 3657 --**************************************************************** 3658 -- MPLS LDP Frame Relay Objects 3659 --**************************************************************** 3661 -- 3662 -- Ldp Entity Objects for Frame Relay 3663 -- 3665 mplsLdpEntityFrameRelayObjects OBJECT IDENTIFIER ::= 3666 { mplsLdpFrameRelayObjects 1 } 3668 mplsLdpEntityFrameRelayTable OBJECT-TYPE 3669 SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayEntry 3670 MAX-ACCESS not-accessible 3671 STATUS current 3672 DESCRIPTION 3673 "This table contains information about the 3674 Optional Parameters to specify what this Entity is 3675 going to specify for Frame Relay specific 3676 LDP Intialization Messages." 3677 ::= { mplsLdpEntityFrameRelayObjects 1 } 3679 mplsLdpEntityFrameRelayEntry OBJECT-TYPE 3680 SYNTAX MplsLdpEntityFrameRelayEntry 3681 MAX-ACCESS not-accessible 3682 STATUS current 3683 DESCRIPTION 3684 "An entry in this table represents the Frame Relay 3685 optional parameters associated with the LDP entity." 3686 INDEX { mplsLdpEntityLdpId, 3687 mplsLdpEntityIndex 3688 } 3690 ::= { mplsLdpEntityFrameRelayTable 1 } 3692 MplsLdpEntityFrameRelayEntry ::= SEQUENCE { 3693 mplsLdpEntityFrameRelayIfIndexOrZero InterfaceIndexOrZero, 3694 mplsLdpEntityFrameRelayMergeCap INTEGER, 3695 mplsLdpEntityFrameRelayLRComponents Unsigned32, 3696 mplsLdpEntityFrameRelayVcDirectionality INTEGER, 3697 mplsLdpEntityFrameRelayStorageType StorageType, 3698 mplsLdpEntityFrameRelayRowStatus RowStatus 3699 } 3701 mplsLdpEntityFrameRelayIfIndexOrZero OBJECT-TYPE 3702 SYNTAX InterfaceIndexOrZero 3703 MAX-ACCESS read-create 3704 STATUS current 3705 DESCRIPTION 3706 "This value represents either the InterfaceIndex of 3707 the 'ifLayer' where the Frame Relay Labels 'owned' by this 3708 entry were created, or 0 (zero). The value of zero 3709 means that the InterfaceIndex is not known. For example, 3710 if the InterfaceIndex is created subsequent to the 3711 Frame Relay Label's creation, then it would not be known. 3712 However, if the InterfaceIndex is known, then it must 3713 be represented by this value. 3715 If an InterfaceIndex becomes known, then the 3716 network management entity (e.g. SNMP agent) responsible 3717 for this object MUST change the value from 0 (zero) to the 3718 value of the InterfaceIndex. If an Frame Relay Label is 3719 being used in forwarding data, then the value of this 3720 object MUST be the InterfaceIndex." 3721 ::= { mplsLdpEntityFrameRelayEntry 1 } 3723 mplsLdpEntityFrameRelayMergeCap OBJECT-TYPE 3724 SYNTAX INTEGER { 3725 notSupported(0), 3726 supported(1) 3727 } 3728 MAX-ACCESS read-create 3729 STATUS current 3730 DESCRIPTION 3731 "This represents whether or not the Frame Relay merge 3732 capability is supported. This is the EXACT value for the 3733 Frame Relay Session Parameter, field M (for Frame Relay 3734 Merge Capabilities). The Frame Relay Session Parameter 3735 is an optional parameter in the Initialization Message. 3737 The description from rfc3036.txt is: 3738 'M, Frame Relay Merge Capabilities 3739 Specifies the merge capabilities of a Frame Relay switch. The 3740 following values are supported in this version of the 3741 specification: 3743 Value Meaning 3745 0 Merge not supported 3746 1 Merge supported 3748 Non-merge and merge Frame Relay LSRs may freely interoperate.' 3750 Please refer to the following reference for a complete 3751 description of this feature." 3752 REFERENCE 3753 "[RFC3036] LDP Specification, Section 3.5.3 Initialization Message." 3754 ::= { mplsLdpEntityFrameRelayEntry 2 } 3756 mplsLdpEntityFrameRelayLRComponents OBJECT-TYPE 3757 SYNTAX Unsigned32 (1..65535) 3758 MAX-ACCESS read-create 3759 STATUS current 3760 DESCRIPTION 3761 "Number of Label Range Components in the Initialization 3762 message. This also represents the number of entries 3763 in the mplsLdpEntityFrameRelayLRTable which correspond 3764 to this entry. 3766 This is the EXACT value for the Frame Relay Session Parameter, 3767 field N (for Number of label range components). The Frame Relay 3768 Session Parameter is an optional parameter in the Initialization Message. 3770 The description from rfc3036.txt is: 3772 'N, Number of label range components 3773 Specifies the number of Frame Relay Label Range Components 3774 included in the TLV.' 3776 Please refer to the following reference for a complete 3777 description of this feature." 3778 REFERENCE 3779 "[RFC3036] LDP Specification, Section 3.5.3 Initialization Message." 3780 ::= { mplsLdpEntityFrameRelayEntry 3 } 3782 mplsLdpEntityFrameRelayVcDirectionality OBJECT-TYPE 3783 SYNTAX INTEGER { 3784 bidirectional(0), 3785 unidirection(1) 3786 } 3787 MAX-ACCESS read-create 3788 STATUS current 3789 DESCRIPTION 3790 "If the value of this object is 'bidirectional(0)', then 3791 the LSR supports the use of a given DLCI as a label for 3792 both directions independently. If the value of 3793 this object is 'unidirectional(1)', then the LSR 3794 uses the given DLCI as a label in only one direction. 3796 This is the EXACT value for the Frame Relay Session Parameter, 3797 field D (for VC Directionality). The Frame Relay Session Parameter 3798 is an optional parameter in the Initialization Message. 3800 The description from rfc3036.txt is: 3802 'D, VC Directionality 3803 A value of 0 specifies bidirectional VC capability, meaning the 3804 LSR can support the use of a given DLCI as a label for both 3805 link directions independently. A value of 1 specifies 3806 unidirectional VC capability, meaning a given DLCI may appear 3807 in a label mapping for one direction on the link only. When 3808 either or both of the peers specifies unidirectional VC 3809 capability, both LSRs use unidirectional VC label assignment 3810 for the link as follows. The LSRs compare their LDP 3811 Identifiers as unsigned integers. The LSR with the larger LDP 3812 Identifier may assign only odd-numbered DLCIs in the range as 3813 labels. The system with the smaller LDP Identifier may assign 3814 only even-numbered DLCIs in the range as labels.' 3816 Please refer to the following reference for a complete 3817 description of this feature." 3818 REFERENCE 3819 "[RFC3036] LDP Specification, Section 3.5.3 Initialization Message." 3820 ::= { mplsLdpEntityFrameRelayEntry 4 } 3822 mplsLdpEntityFrameRelayStorageType OBJECT-TYPE 3823 SYNTAX StorageType 3824 MAX-ACCESS read-create 3825 STATUS current 3826 DESCRIPTION 3827 "The storage type for this conceptual row. Conceptual rows 3828 having the value 'permanent(4)' MAY allow write-access to any 3829 columnar objects in the row, except for setting the 3830 mplsLdpEntityFrameRelayRowStatus to 'destroy(6)'." 3831 DEFVAL { nonVolatile } 3832 ::= { mplsLdpEntityFrameRelayEntry 5 } 3834 mplsLdpEntityFrameRelayRowStatus OBJECT-TYPE 3835 SYNTAX RowStatus 3836 MAX-ACCESS read-create 3837 STATUS current 3838 DESCRIPTION 3839 "The status of this conceptual row. All writable objects in this 3840 row may be modified at any time, however, as described in 3841 detail in the section entitled, 'Changing Values After Session 3842 Establishment', and again described in the 3843 DESCRIPTION clause of the mplsLdpEntityAdminStatus object, 3844 if a session has been initiated with a Peer, 3845 changing objects in this table will 3846 wreak havoc with the session and interrupt traffic. To repeat again: 3847 the recommended procedure is to set the mplsLdpEntityAdminStatus to 3848 down, thereby explicitely causing a session to be torn down. Then, 3849 change objects in this entry, then set the mplsLdpEntityAdminStatus 3850 to enable which enables a NEW session to be initiated. 3852 NOTE: This RowStatus object should 3853 have the same value of the 'mplsLdpEntityRowStatus' 3854 related to this entry." 3855 ::= { mplsLdpEntityFrameRelayEntry 6 } 3857 -- 3858 -- Frame Relay Label Range Components 3859 -- 3861 mplsLdpEntityFrameRelayLRTable OBJECT-TYPE 3862 SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayLREntry 3863 MAX-ACCESS not-accessible 3864 STATUS current 3865 DESCRIPTION 3866 "This table contains information about the 3867 Optional Parameters for the Frame Relay Session 3868 in the LDP Initialization Message, specifically 3869 it contains information about the Frame Relay 3870 Label Range Components." 3872 ::= { mplsLdpEntityFrameRelayObjects 2 } 3874 mplsLdpEntityFrameRelayLREntry OBJECT-TYPE 3875 SYNTAX MplsLdpEntityFrameRelayLREntry 3876 MAX-ACCESS not-accessible 3877 STATUS current 3878 DESCRIPTION 3879 "An entry in this table represents the Frame Relay 3880 Label Range Component associated with the LDP entity." 3881 INDEX { mplsLdpEntityLdpId, 3882 mplsLdpEntityIndex, 3883 mplsLdpEntityFrameRelayLRMinDlci 3884 } 3885 ::= { mplsLdpEntityFrameRelayLRTable 1 } 3887 MplsLdpEntityFrameRelayLREntry ::= SEQUENCE { 3888 mplsLdpEntityFrameRelayLRMinDlci DLCI, 3889 mplsLdpEntityFrameRelayLRMaxDlci DLCI, 3890 mplsLdpEntityFrameRelayLRLen INTEGER, 3891 mplsLdpEntityFrameRelayLRStorageType StorageType, 3892 mplsLdpEntityFrameRelayLRRowStatus RowStatus 3893 } 3895 mplsLdpEntityFrameRelayLRMinDlci OBJECT-TYPE 3896 SYNTAX DLCI 3897 MAX-ACCESS not-accessible 3898 STATUS current 3899 DESCRIPTION 3900 "The lower bound which is supported. This value should 3901 be the same as that in the Frame Relay Label Range 3902 Component's Minimum DLCI field. The value of zero 3903 is valid for the minimum DLCI field of the label." 3904 REFERENCE 3905 "[RFC 3034] Use of Label Switching on Frame Relay Networks 3906 Specification." 3907 ::= { mplsLdpEntityFrameRelayLREntry 1 } 3909 mplsLdpEntityFrameRelayLRMaxDlci OBJECT-TYPE 3910 SYNTAX DLCI 3911 MAX-ACCESS read-create 3912 STATUS current 3913 DESCRIPTION 3914 "The upper bound which is supported. This value should 3915 be the same as that in the Frame Relay Label Range 3916 Component's Maximum DLCI field." 3917 ::= { mplsLdpEntityFrameRelayLREntry 2 } 3919 mplsLdpEntityFrameRelayLRLen OBJECT-TYPE 3920 SYNTAX INTEGER { 3921 tenDlciBits(0), 3922 twentyThreeDlciBits(2) 3923 } 3924 MAX-ACCESS read-create 3925 STATUS current 3926 DESCRIPTION 3927 "This object specifies the length of the DLCI bits. 3929 This is the EXACT value for the Len field of the 3930 Frame Relay Label Range Component. 3932 The description from rfc3036.txt is: 3934 'Len 3935 This field specifies the number of bits of the DLCI. The 3936 following values are supported: 3938 Len DLCI bits 3940 0 10 3941 2 23 3943 Len values 1 and 3 are reserved.' 3945 Please refer to the following reference for a complete 3946 description of this feature." 3947 REFERENCE 3948 "[RFC3036] LDP Specification, Section 3.5.3 Initialization Message." 3949 ::= { mplsLdpEntityFrameRelayLREntry 3 } 3951 mplsLdpEntityFrameRelayLRStorageType OBJECT-TYPE 3952 SYNTAX StorageType 3953 MAX-ACCESS read-create 3954 STATUS current 3955 DESCRIPTION 3956 "The storage type for this conceptual row. Conceptual rows 3957 having the value 'permanent(4)' MAY allow write-access to any 3958 columnar objects in the row, except for setting the 3959 mplsLdpEntityFrameRelayLRRowStatus to 'destroy(6)'." 3960 DEFVAL { nonVolatile } 3961 ::= { mplsLdpEntityFrameRelayLREntry 4 } 3963 mplsLdpEntityFrameRelayLRRowStatus OBJECT-TYPE 3964 SYNTAX RowStatus 3965 MAX-ACCESS read-create 3966 STATUS current 3967 DESCRIPTION 3968 "The status of this conceptual row. All writable objects in this 3969 row may be modified at any time, however, as described in 3970 detail in the section entitled, 'Changing Values After Session 3971 Establishment', and again described in the 3972 DESCRIPTION clause of the mplsLdpEntityAdminStatus object, 3973 if a session has been initiated with a Peer, 3974 changing objects in this table will 3975 wreak havoc with the session and interrupt traffic. To repeat again: 3976 the recommended procedure is to set the mplsLdpEntityAdminStatus to 3977 down, thereby explicitely causing a session to be torn down. Then, 3978 change objects in this entry, then set the mplsLdpEntityAdminStatus 3979 to enable which enables a NEW session to be initiated. 3981 If the value of the object 3982 'mplsLdpEntityOptionalParameters' contains the 3983 value of 'frameRelaySessionParameters(3)' then 3984 there must be at least one corresponding entry 3985 in this table. 3987 NOTE: This RowStatus object should 3988 have the same value of the 'mplsLdpEntityRowStatus' 3989 related to this entry." 3990 ::= { mplsLdpEntityFrameRelayLREntry 5 } 3992 -- 3993 -- MPLS LDP Frame Relay Session Information 3994 -- 3996 mplsLdpFrameRelaySesObjects OBJECT IDENTIFIER ::= 3997 { mplsLdpFrameRelayObjects 2 } 3999 mplsLdpFrameRelaySesTable OBJECT-TYPE 4000 SYNTAX SEQUENCE OF MplsLdpFrameRelaySesEntry 4001 MAX-ACCESS not-accessible 4002 STATUS current 4003 DESCRIPTION 4004 "A table of Frame Relay label range intersections 4005 between the LDP Entities and LDP Peers. 4006 Each row represents a single label range intersection. 4008 NOTE: this table cannot use the 'AUGMENTS' 4009 clause because there is not necessarily a one-to-one 4010 mapping between this table and the mplsLdpSessionTable." 4011 ::= { mplsLdpFrameRelaySesObjects 1 } 4013 mplsLdpFrameRelaySesEntry OBJECT-TYPE 4014 SYNTAX MplsLdpFrameRelaySesEntry 4015 MAX-ACCESS not-accessible 4016 STATUS current 4017 DESCRIPTION 4018 "An entry in this table represents information on a 4019 single label range intersection between an 4020 LDP Entity and LDP Peer. 4022 The information contained in a row is read-only." 4023 INDEX { mplsLdpEntityLdpId, 4024 mplsLdpEntityIndex, 4025 mplsLdpPeerLdpId, 4026 mplsLdpFrameRelaySesMinDlci 4027 } 4028 ::= { mplsLdpFrameRelaySesTable 1 } 4030 MplsLdpFrameRelaySesEntry ::= SEQUENCE { 4031 mplsLdpFrameRelaySesMinDlci DLCI, 4032 mplsLdpFrameRelaySesMaxDlci DLCI, 4033 mplsLdpFrameRelaySesLen INTEGER 4034 } 4036 mplsLdpFrameRelaySesMinDlci OBJECT-TYPE 4037 SYNTAX DLCI 4038 MAX-ACCESS not-accessible 4039 STATUS current 4040 DESCRIPTION 4041 "The lower bound of DLCIs which are supported. 4042 The value of zero is a valid value for the 4043 minimum DLCI field of the label." 4044 REFERENCE 4045 "[RFC 3034] Use of Label Switching on Frame Relay Networks 4046 Specification." 4047 ::= { mplsLdpFrameRelaySesEntry 1 } 4049 mplsLdpFrameRelaySesMaxDlci OBJECT-TYPE 4050 SYNTAX DLCI 4051 MAX-ACCESS read-only 4052 STATUS current 4053 DESCRIPTION 4054 "The upper bound of DLCIs which are supported." 4055 ::= { mplsLdpFrameRelaySesEntry 2 } 4057 mplsLdpFrameRelaySesLen OBJECT-TYPE 4058 SYNTAX INTEGER { 4059 tenDlciBits(0), 4060 twentyThreeDlciBits(2) 4061 } 4062 MAX-ACCESS read-only 4063 STATUS current 4064 DESCRIPTION 4065 "This object specifies the DLCI bits." 4066 ::= { mplsLdpFrameRelaySesEntry 3 } 4068 --**************************************************************** 4069 -- Module Conformance Statement 4070 --**************************************************************** 4072 mplsLdpFrameRelayGroups 4073 OBJECT IDENTIFIER ::= { mplsLdpFrameRelayConformance 1 } 4075 mplsLdpFrameRelayCompliances 4076 OBJECT IDENTIFIER ::= { mplsLdpFrameRelayConformance 2 } 4078 -- 4079 -- Full Compliance 4080 -- 4082 mplsLdpFrameRelayModuleFullCompliance MODULE-COMPLIANCE 4083 STATUS current 4084 DESCRIPTION 4085 "The Module is implemented with support for 4086 read-create and read-write. In other words, 4087 both monitoring and configuration 4088 are available when using this MODULE-COMPLIANCE." 4089 MODULE -- this module 4090 MANDATORY-GROUPS { 4091 mplsLdpFrameRelayGroup 4092 } 4094 OBJECT mplsLdpEntityFrameRelayRowStatus 4095 SYNTAX RowStatus { active(1) } 4096 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 4097 DESCRIPTION 4098 "Support for createAndWait and notInService is not required." 4100 OBJECT mplsLdpEntityFrameRelayLRRowStatus 4101 SYNTAX RowStatus { active(1) } 4102 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 4103 DESCRIPTION 4104 "Support for createAndWait and notInService is not required." 4106 ::= { mplsLdpFrameRelayCompliances 1 } 4108 -- 4109 -- Read-Only Compliance 4110 -- 4112 mplsLdpFrameRelayModuleReadOnlyCompliance MODULE-COMPLIANCE 4113 STATUS current 4114 DESCRIPTION 4115 "The Module is implemented with support for 4116 read-only. In other words, only monitoring 4117 is available by implementing this MODULE-COMPLIANCE." 4118 MODULE -- this module 4119 MANDATORY-GROUPS { 4120 mplsLdpFrameRelayGroup 4121 } 4123 OBJECT mplsLdpEntityFrameRelayIfIndexOrZero 4124 MIN-ACCESS read-only 4125 DESCRIPTION 4126 "Write access is not required." 4128 OBJECT mplsLdpEntityFrameRelayMergeCap 4129 MIN-ACCESS read-only 4130 DESCRIPTION 4131 "Write access is not required." 4133 OBJECT mplsLdpEntityFrameRelayLRComponents 4134 MIN-ACCESS read-only 4135 DESCRIPTION 4136 "Write access is not required." 4138 OBJECT mplsLdpEntityFrameRelayVcDirectionality 4139 MIN-ACCESS read-only 4140 DESCRIPTION 4141 "Write access is not required." 4143 OBJECT mplsLdpEntityFrameRelayStorageType 4144 MIN-ACCESS read-only 4145 DESCRIPTION 4146 "Write access is not required." 4148 OBJECT mplsLdpEntityFrameRelayRowStatus 4149 SYNTAX RowStatus { active(1) } 4150 MIN-ACCESS read-only 4151 DESCRIPTION 4152 "Write access is not required, and active is the 4153 only status that needs to be supported." 4155 OBJECT mplsLdpEntityFrameRelayLRMaxDlci 4156 MIN-ACCESS read-only 4157 DESCRIPTION 4158 "Write access is not required." 4160 OBJECT mplsLdpEntityFrameRelayLRLen 4161 MIN-ACCESS read-only 4162 DESCRIPTION 4163 "Write access is not required." 4165 OBJECT mplsLdpEntityFrameRelayLRStorageType 4166 MIN-ACCESS read-only 4167 DESCRIPTION 4168 "Write access is not required." 4170 OBJECT mplsLdpEntityFrameRelayLRRowStatus 4171 SYNTAX RowStatus { active(1) } 4172 MIN-ACCESS read-only 4173 DESCRIPTION 4174 "Write access is not required, and active is the 4175 only status that needs to be supported." 4176 ::= { mplsLdpFrameRelayCompliances 2 } 4178 -- 4179 -- units of conformance 4180 -- 4182 mplsLdpFrameRelayGroup OBJECT-GROUP 4183 OBJECTS { 4184 mplsLdpEntityFrameRelayIfIndexOrZero, 4185 mplsLdpEntityFrameRelayMergeCap, 4186 mplsLdpEntityFrameRelayLRComponents, 4187 mplsLdpEntityFrameRelayVcDirectionality, 4188 mplsLdpEntityFrameRelayStorageType, 4189 mplsLdpEntityFrameRelayRowStatus, 4190 mplsLdpEntityFrameRelayLRMaxDlci, 4191 mplsLdpEntityFrameRelayLRLen, 4192 mplsLdpEntityFrameRelayLRStorageType, 4193 mplsLdpEntityFrameRelayLRRowStatus, 4194 mplsLdpFrameRelaySesMaxDlci, 4195 mplsLdpFrameRelaySesLen 4196 } 4197 STATUS current 4198 DESCRIPTION 4199 "Objects that apply to all MPLS LDP implementations over 4200 Frame Relay." 4201 ::= { mplsLdpFrameRelayGroups 1 } 4203 END 4205 4.3. The MPLS-LDP-GENERIC-MIB Module 4207 This MIB Module MUST be supported if LDP uses a Per Platform Label 4208 Space. This MIB Module contains a Label Range (LR) table for 4209 configuring Mpls Generic Label Ranges. This table is 4210 mplsLdpEntityGenericLabelRangeTable. Although the LDP Specification 4211 does not provide a way for configuring Label Ranges for Generic 4212 Labels, the MIB does provide a way to reserve a range of generic 4213 labels because this was thought to be useful by the working group. 4215 MPLS-LDP-GENERIC-MIB DEFINITIONS ::= BEGIN 4217 IMPORTS 4219 OBJECT-TYPE, 4220 MODULE-IDENTITY, 4221 Unsigned32 4222 FROM SNMPv2-SMI 4224 MODULE-COMPLIANCE, 4225 OBJECT-GROUP 4226 FROM SNMPv2-CONF 4228 RowStatus, 4229 StorageType 4230 FROM SNMPv2-TC 4232 InterfaceIndexOrZero 4233 FROM IF-MIB 4235 mplsMIB 4236 FROM MPLS-TC-MIB 4238 mplsLdpEntityLdpId, 4239 mplsLdpEntityIndex 4240 FROM MPLS-LDP-MIB 4241 ; 4243 mplsLdpGenericMIB MODULE-IDENTITY 4244 LAST-UPDATED "200204221200Z" -- 22 April 2003 4245 ORGANIZATION "Multiprotocol Label Switching (mpls) 4246 Working Group" 4247 CONTACT-INFO 4248 "Joan Cucchiara (jcucchiara@artel.com) 4249 Artel 4251 Hans Sjostrand (hans@ipunplugged.com) 4252 ipUnplugged 4254 James V. Luciani (james_luciani@mindspring.com) 4255 Consultant 4257 Working Group Chairs: 4258 George Swallow, email: swallow@cisco.com 4259 Loa Andersson, email: loa@pi.se 4261 MPLS Working Group, email: mpls@uu.net 4262 " 4263 DESCRIPTION 4264 "Copyright (C) The Internet Society (2003). This 4265 version of this MIB module is part of RFCXXX; see 4266 the RFC itself for full legal notices. 4268 This MIB contains managed object definitions for 4269 configuring and monitoring the Multiprotocol Label 4270 Switching (MPLS), Label Distribution Protocol (LDP), 4271 utilizing ethernet as the Layer 2 media." 4272 REVISION "200304221200Z" -- 22 April 2003 4273 DESCRIPTION 4274 "Initial version published as part of RFC XXXX." 4276 -- Please see the IANA Considerations Section. 4277 -- The requested mplsMIB subId is 7, e.g. 4278 -- ::= { mplsMIB 7 } 4280 ::= { mplsMIB XXX } -- to be assigned by IANA 4282 --**************************************************************** 4284 mplsLdpGenericObjects 4285 OBJECT IDENTIFIER ::= { mplsLdpGenericMIB 1 } 4286 mplsLdpGenericConformance 4287 OBJECT IDENTIFIER ::= { mplsLdpGenericMIB 2 } 4289 --**************************************************************** 4290 -- MPLS LDP GENERIC Objects 4291 --**************************************************************** 4293 -- 4294 -- Ldp Entity Objects for Generic Labels 4295 -- 4297 mplsLdpEntityGenericObjects OBJECT IDENTIFIER ::= 4298 { mplsLdpGenericObjects 1 } 4300 -- 4301 -- The MPLS LDP Entity Generic Label Range Table 4302 -- 4304 mplsLdpEntityGenericLRTable OBJECT-TYPE 4305 SYNTAX SEQUENCE OF MplsLdpEntityGenericLREntry 4306 MAX-ACCESS not-accessible 4307 STATUS current 4308 DESCRIPTION 4309 "The MPLS LDP Entity Generic Label Range (LR) 4310 Table. 4312 The purpose of this table is to provide a mechanism 4313 for configurating a contiguous range of generic labels, 4314 or a 'label range' for LDP Entities. 4316 LDP Entities which use Generic Labels must have at least 4317 one entry in this table. In other words, this table 4318 'extends' the mpldLdpEntityTable for Generic Labels." 4319 ::= { mplsLdpEntityGenericObjects 1 } 4321 mplsLdpEntityGenericLREntry OBJECT-TYPE 4322 SYNTAX MplsLdpEntityGenericLREntry 4323 MAX-ACCESS not-accessible 4324 STATUS current 4325 DESCRIPTION 4326 "A row in the LDP Entity Generic Label 4327 Range (LR) Table. One entry in this table contains 4328 information on a single range of labels 4329 represented by the configured Upper and Lower 4330 Bounds pairs. NOTE: there is NO corresponding 4331 LDP message which relates to the information 4332 in this table, however, this table does provide 4333 a way for a user to 'reserve' a generic label 4334 range. 4336 NOTE: The ranges for a specific LDP Entity 4337 are UNIQUE and non-overlapping. 4339 A row will not be created unless a unique and 4340 non-overlapping range is specified." 4341 INDEX { mplsLdpEntityLdpId, 4342 mplsLdpEntityIndex, 4343 mplsLdpEntityGenericLRMin, 4344 mplsLdpEntityGenericLRMax 4345 } 4346 ::= { mplsLdpEntityGenericLRTable 1 } 4348 MplsLdpEntityGenericLREntry ::= SEQUENCE { 4349 mplsLdpEntityGenericLRMin Unsigned32, 4350 mplsLdpEntityGenericLRMax Unsigned32, 4351 mplsLdpEntityGenericLabelSpace INTEGER, 4352 mplsLdpEntityGenericIfIndexOrZero InterfaceIndexOrZero, 4353 mplsLdpEntityGenericLRStorageType StorageType, 4354 mplsLdpEntityGenericLRRowStatus RowStatus 4355 } 4357 mplsLdpEntityGenericLRMin OBJECT-TYPE 4358 SYNTAX Unsigned32(0..1048575) 4359 MAX-ACCESS not-accessible 4360 STATUS current 4361 DESCRIPTION 4362 "The minimum label configured for this range." 4363 ::= { mplsLdpEntityGenericLREntry 1 } 4365 mplsLdpEntityGenericLRMax OBJECT-TYPE 4366 SYNTAX Unsigned32(0..1048575) 4367 MAX-ACCESS not-accessible 4368 STATUS current 4369 DESCRIPTION 4370 "The maximum label configured for this range." 4371 ::= { mplsLdpEntityGenericLREntry 2 } 4373 mplsLdpEntityGenericLabelSpace OBJECT-TYPE 4374 SYNTAX INTEGER { 4375 perPlatform(1), 4376 perInterface(2) 4377 } 4378 MAX-ACCESS read-create 4379 STATUS current 4380 DESCRIPTION 4381 "This value of this object is perPlatform(1), then 4382 this means that the label space type is 4383 per platform. 4385 If this object is perInterface(2), then this 4386 means that the label space type is per Interface." 4387 REFERENCE 4388 "[RFC3036], LDP Specification, Section 2.2.1, 4389 Label Spaces." 4390 DEFVAL { perPlatform } 4391 ::= { mplsLdpEntityGenericLREntry 3 } 4393 mplsLdpEntityGenericIfIndexOrZero OBJECT-TYPE 4394 SYNTAX InterfaceIndexOrZero 4395 MAX-ACCESS read-create 4396 STATUS current 4397 DESCRIPTION 4398 "This value represents either the InterfaceIndex of 4399 the 'ifLayer' where these Generic Label would be created, 4400 or 0 (zero). The value of zero means that the 4401 InterfaceIndex is not known. For example, if 4402 the InterfaceIndex is created subsequent to 4403 the Generic Label's creation, then it would not be 4404 known. However, if the InterfaceIndex 4405 is known, then it must be represented by this value. 4407 If an InterfaceIndex becomes known, then the 4408 network management entity (e.g. SNMP agent) responsible 4409 for this object MUST change the value from 0 (zero) to the 4410 value of the InterfaceIndex." 4411 ::= { mplsLdpEntityGenericLREntry 4 } 4413 mplsLdpEntityGenericLRStorageType OBJECT-TYPE 4414 SYNTAX StorageType 4415 MAX-ACCESS read-create 4416 STATUS current 4417 DESCRIPTION 4418 "The storage type for this conceptual row. Conceptual rows 4419 having the value 'permanent(4)' need not allow write-access to any 4420 columnar objects in the row." 4421 DEFVAL { nonVolatile } 4422 ::= { mplsLdpEntityGenericLREntry 5 } 4424 mplsLdpEntityGenericLRRowStatus OBJECT-TYPE 4425 SYNTAX RowStatus 4426 MAX-ACCESS read-create 4427 STATUS current 4428 DESCRIPTION 4429 "The status of this conceptual row. All writable objects in this 4430 row may be modified at any time, however, as described in 4431 detail in the section entitled, 'Changing Values After Session 4432 Establishment', and again described in the 4433 DESCRIPTION clause of the mplsLdpEntityAdminStatus object, 4434 if a session has been initiated with a Peer, 4435 changing objects in this table will 4436 wreak havoc with the session and interrupt traffic. To repeat again: 4437 the recommended procedure is to set the mplsLdpEntityAdminStatus to 4438 down, thereby explicitely causing a session to be torn down. Then, 4439 change objects in this entry, then set the mplsLdpEntityAdminStatus 4440 to enable which enables a NEW session to be initiated. 4442 There must exist at least one entry in this 4443 table for every LDP Entity that has a 4444 generic label configured. 4446 NOTE: This RowStatus object should 4447 have the same value of the 'mplsLdpEntityRowStatus' 4448 related to this entry." 4449 ::= { mplsLdpEntityGenericLREntry 6 } 4451 --**************************************************************** 4452 -- Module Conformance Statement 4453 --**************************************************************** 4455 mplsLdpGenericGroups 4456 OBJECT IDENTIFIER ::= { mplsLdpGenericConformance 1 } 4458 mplsLdpGenericCompliances 4459 OBJECT IDENTIFIER ::= { mplsLdpGenericConformance 2 } 4461 -- 4462 -- Full Compliance 4463 -- 4465 mplsLdpGenericModuleFullCompliance MODULE-COMPLIANCE 4466 STATUS current 4467 DESCRIPTION 4468 "The Module is implemented with support for 4469 read-create and read-write. In other words, 4470 both monitoring and configuration 4471 are available when using this MODULE-COMPLIANCE." 4472 MODULE -- this module 4473 MANDATORY-GROUPS { 4474 mplsLdpGenericGroup 4475 } 4477 OBJECT mplsLdpEntityGenericLRRowStatus 4478 SYNTAX RowStatus { active(1) } 4479 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 4480 DESCRIPTION 4481 "Support for createAndWait and notInService is not required." 4483 ::= { mplsLdpGenericCompliances 1 } 4485 -- 4486 -- Read-Only Compliance 4487 -- 4489 mplsLdpGenericModuleReadOnlyCompliance MODULE-COMPLIANCE 4490 STATUS current 4491 DESCRIPTION 4492 "The Module is implemented with support for 4493 read-only. In other words, only monitoring 4494 is available by implementing this MODULE-COMPLIANCE." 4495 MODULE -- this module 4496 MANDATORY-GROUPS { 4497 mplsLdpGenericGroup 4498 } 4500 OBJECT mplsLdpEntityGenericLabelSpace 4501 MIN-ACCESS read-only 4502 DESCRIPTION 4503 "Write access is not required." 4505 OBJECT mplsLdpEntityGenericIfIndexOrZero 4506 MIN-ACCESS read-only 4507 DESCRIPTION 4508 "Write access is not required." 4510 OBJECT mplsLdpEntityGenericLRStorageType 4511 MIN-ACCESS read-only 4512 DESCRIPTION 4513 "Write access is not required." 4515 OBJECT mplsLdpEntityGenericLRRowStatus 4516 SYNTAX RowStatus { active(1) } 4517 MIN-ACCESS read-only 4518 DESCRIPTION 4519 "Write access is not required, and active is the 4520 only status that needs to be supported." 4522 ::= { mplsLdpGenericCompliances 2 } 4524 -- 4525 -- units of conformance 4526 -- 4528 mplsLdpGenericGroup OBJECT-GROUP 4529 OBJECTS { 4530 mplsLdpEntityGenericLabelSpace, 4531 mplsLdpEntityGenericIfIndexOrZero, 4532 mplsLdpEntityGenericLRStorageType, 4533 mplsLdpEntityGenericLRRowStatus 4534 } 4535 STATUS current 4536 DESCRIPTION 4537 "Objects that apply to all MPLS LDP implementations 4538 using Generic Lables." 4540 ::= { mplsLdpGenericGroups 1 } 4542 END 4544 5. Revision History 4546 NOTE TO RFC-Editor: before publishing this document as an RFC, 4547 please remove this Revision History (change log) section. sp 4549 5.1. Changes from 4551 Added the new MIB boiler plate and associated MIB reference changes. 4553 Reworked the OID tree structure so that the Modules only have the 4554 mplsMIB subid dependency. This was discussed in mpls wg email 4555 (discussion was mostly between Bert, Tom and Joan). 4557 Added IANA Considerations section. This contains 4 subsections, one 4558 per MIB module. 4560 Updated and added new references as needed. 4562 Changed mplsMIB subid values to agree with the latest "Multiprotocol 4563 Label Switching (MPLS) Management Overview" document, [MPLSMGMT]. 4565 Moved MIB modules around so that they would appear in subId order. 4566 The Generic MIB module is shown last, since the subid is 7 (which is 4567 the last (and largest) subid requested by IANA. 4569 5.1.1. Changes based on MIB Doctor Review Comments 4571 The following changes are based on comments from the MIB DR Review. 4572 The comments are from email to the mpls working group dated, Dec 6, 4573 2002. These comments are quoted and prefaced by "REQ: comment goes 4574 here", and then followed by our resolution. 4576 "REQ: - missing IPR section". RSP: it has been added. 4578 "REQ: - Security considerations probably needs more work 4579 Security ADs want you to explain what the vulnerabilities/risks 4580 are and what to do against them. 4581 Also for read only objects, pls list each (group of) object(s) 4582 and explain what sensitivity attributes they have". RSP: Done. We 4583 added subsections here since the Security template is MIB Module 4584 based and it seemed to us more clear to do a subsection per MIB 4585 Module. 4587 "REQ: - pls do the consistency checking for descriptors and all 4588 that". RSP: believe this to be done. Changed Gen to Generic 4589 everywhere, changed Fr to FrameRelay, changed RO to ReadOnly. 4590 Changed Sessions to Ses everywhere. Reviewed tables to make sure 4591 they were prefixed consistently. Added more references, used more 4592 TCs and other stuff. 4594 "REQ: - sect 3.5 1st sentence, s/would be/are/ ??". RSP: done. 4596 "REQ: - sect 3.5 2nd para first sentence s/initiation/initiate/ ". 4597 RSP: done. 4599 "REQ: - section 3.5.2 s/mpsl/mpls/". RSP: done. 4601 "REQ: - mplsXxxIndexNext 4602 See my comments on FTN MIB and LSR MIB on these type of objects 4603 Best to use something aka rfc3289 ". RSP: We have imported the 4604 IndexInteger and IndexIntegerNextFree TCs (from rfc3289.txt). NOTE: 4605 we do not like the names of these TCs because they use the term 4606 Integer when the values are Unsigned32. Would prefer new TCs with 4607 IndexUnsigned32 and IndexUnsigned32NextFree. 4609 "REQ:- RowStatus and StorageType objects 4610 see my comments about similar objects in LSR MIB 4611 for StorageType might also want to add a DEFVAL ". RSP: Added 4612 descriptive text to the RowStatus objects to specify which columns 4613 can be changed when row is active. Added descriptive text to the 4614 StorageType objects to specify what happens when the StorageType is 4615 permanent. Also added DEFVALs for the StorageType objects. 4617 "REQ: - mplsLdpNotifications ... { mplsLdpMib 2 } 4618 why not { mplsLdpMib 0} so that it is right away the prefix? 4619 I believe LSR MIB does it that way now. You may want to do 4620 it consistently for all notifications. 4621 I can live with either way, but prefer them to be shorter OIDs.". 4622 RSP: We changed this to follow what LSR MIB does (i.e. 4623 mplsLdpNotifications 0) for shorter OIDs..PP "REQ: - 4624 mplsXxxLastChange 4625 does that time stamp only get changed if an addition/deletion takes 4626 place? Not if something gets changed via a SNMP SET command? 4627 I think I'd prefer to also see changes (modifications) via SET. 4628 But in any event, be very explicit about if those are included or 4629 not.". RSP: All Last change object DESCRIPTIONs have been 4630 updated to be very specific. 4632 "REQ:- mplsLdpLspType 4633 All that stuff in the DESCRIPTION clause is just a repeat of the 4634 TC DESCRIPTION clause. Seems not needed to me. What if a value 4635 gets added later... how do you stay in sync?". RSP: This has 4636 been fixed. 4638 "REQ: - mplsFecAddrLength 4639 Should that be of SYNTAX InetAddressPrefixLength as per RFC3291?". 4640 RSP: yes, fixed. 4642 "REQ: - mplsFecAddrFamily and mplsFecAddr 4643 These are strange. The DESCRIPTIONS are certainly not meeting the 4644 requirements as specified in RFC3291. At other places you do it 4645 correct, so you do understand what is required I think.". RSP: 4646 changed to have a better descriptions. Should note that the TLVs in 4647 the LDP Specification use Address Family Numbers and are still 4648 referring to RFC1700. 4650 "REQ: - mplsLdpLspFecTable claims to be a read-only table. 4651 Yet you have a read-create RowStatus object in it.". RSP: fixed. 4653 "REQ: - mplsLdpSessionUp and mplsLdpSessionDown 4654 Is it not better to just have one notification, namely a 4655 mplsLdpSessionStateChange and then the mplsLdpSesState object will 4656 explain what the change is?". RSP: We prefer to leave it this 4657 way. There are some 3rd Party applications that try to resolve 4658 Notifications, so you see one for down, then resolve this by seeing 4659 another one for up. Granted, these 3rd party apps could be coded to 4660 parse the varbind within the trap, but then this requires coding 4661 whereas having 2 distinct notifications is easier on the developer. 4662 Granted, this maybe makes the MIB design more cumbersome. If this is 4663 a blocking issue, then we will change it. 4665 "REQ:- COMPLIANCE section. I hope that INT ADs are OK with making 4666 IPv6 4667 addresses optional. Is that cause current LDP only supports IPv4? 4668 If so you may want to add that as an explanation.". RSP: IPv6 4669 was made mandatory, also supported in MPLS LDP Spec (rfc3036.txt). 4671 Continue with MIB Dr Comments for the MPLS-LDP-GENERIC-MIB. 4673 "REQ:- same on mplsXXXIndexNext and RowStatus and STorageType 4674 objects". RSP: These hdescriptions have been updated. It should 4675 be noted, that these should be EXACTLY the same as the 4676 mplsLdpEntityTable since the LabelRange Tables extend the Entity 4677 Table. "REQ:- this looks wierd: 4678 ::= { mplsMib 6 } -- to be assigned 4679 use cc instead of 6 if you want IANA to assign, and do tell 4680 -- to be assigned by IANA 4681 and write something about it in an IANA Considerations Section if 4682 this is what you want.". RSP: Added more comments, and added an 4683 IANA Considerations Section. "REQ:- mplsGenModuleROCompliance 4684 I would call it mplsGenModuleReadOnlyCompliance 4685 You have used ReadOnly and Full in other places/mib modules and 4686 it is good to be clear and consistent". RSP: done. 4688 MIB Doctor Review comments for ATM. 4690 "REQ:- s/Moduel/Module/". RSP: done. 4692 "REQ:- same on mplsXXXIndexNext and RowStatus and STorageType 4693 objects". RSP: done. 4695 "REQ:- this looks wierd: 4696 ::= { mplsMib 4 } -- to be assigned 4697 use cc instead of 4 if you want IANA to assign, and do tell 4698 -- to be assigned by IANA 4699 and write something about it in an IANA Considerations Section if 4700 this is what you want.". RSP: done. 4702 "REQ:- See earlier remark on Notifications (use zero instead of 2 4703 right away)". RSP:Removed this branch because there aren't any 4704 notifications in this MIB module. 4706 "REQ:- There are still some INTEGER enumerations that start with zero 4707 It is not a BLOCKING problem... but if acceptable, pls make it 4708 start 4709 at 1 (as you have done vor various others of these enumerations)". 4710 RSP: We would rather leave these enums starting with zero. (There are 4711 2 of them in the ATM Module). The reason for leaving them is because 4712 the value zero is what the protocol uses. We have added REFERENCES 4713 to these objects and more info in the descriptions themselves. We 4714 believe it is in the best interest of developers to start enums at 4715 zero. The INET-ADDRESS-MIB uses the value zero, and since we are 4716 already required to use that MIB, there is precedence for zero in an 4717 enum where it makes sense. We believe the value of zero makes sense 4718 for where it is being used in this MIB module. 4720 "REQ:- mplsXxxxROCompliance -> better mplsXxxxReadOnlyCompliance". 4721 RSP: done. 4723 "REQ:- some formatting problems with DEFVAL lines being split on 2 4724 lines?". RSP: fixed. 4726 MIB Doctor Review comments for FrameRelay 4728 "REQ:- consistency in descriptors (FrameRelay vs FR etc)". RSP: 4729 done. "REQ:- same on mplsXXXIndexNext and RowStatus and STorageType 4730 objects". RSP: done. "REQ:- this looks wierd: 4731 ::= { mplsMib 5 } -- to be assigned 4732 use cc instead of 5 if you want IANA to assign, and do tell 4733 -- to be assigned by IANA 4734 and write something about it in an IANA Considerations Section if 4735 this is what you want.". RSP: done. "REQ:- See earlier remark 4736 on Notifications (use zero instead of 2 right away)". RSP:Removed 4737 this branch because there aren't any notifications in this MIB 4738 module. 4740 "REQ:- There are still some INTEGER enumerations that start with zero 4741 It is not a BLOCKING problem... but if acceptable, pls make it 4742 start 4743 at 1 (as you have done vor various others of these enumerations)". 4744 RSP: We would rather leave these enums starting with zero. (There are 4745 4 of them in the Frame Relay Module). The reason for leaving them is 4746 because the value zero is what the protocol uses. We have added 4747 REFERENCES to these objects and more info in the descriptions 4748 themselves. We believe it is in the best interest of developers to 4749 start enums at zero. The INET-ADDRESS-MIB uses the value zero, and 4750 since we are already required to use that MIB, there is precedence 4751 for zero in an enum where it makes sense. We believe the value of 4752 zero makes sense for where it is being used in this MIB module. 4754 "REQ:- mplsLdpEntityFrLRComponents OBJECT-TYPE 4755 SYNTAX Unsigned32 (1..65535) 4756 MAX-ACCESS read-create 4757 STATUS current 4758 DESCRIPTION 4759 "Number of LabelRange Components in the Initialization 4760 message. This also represents the number of entries 4761 in the mplsLdpEntityConfFrLRTable which correspond 4762 to this entry." 4763 Where is this mplsLdpEntityConfFrLRTable ??". RSP: fixed. 4764 "REQ:- I see the xxxDlci index objects start at zero. 4765 Pls add to DESCRIPTION clauses why zero must be an index.". RSP: 4766 Since we are using DLCI and the value of zero is valid for a DLCI. A 4767 statement was added about this. Also, used the DLCI TC from 4768 rfc2115.txt to make this more clear. NOTE: the MPLS-LDP-ATM-MIB 4769 module uses an index of the VP which can also take on the value of 4770 zero. A statement was added to this Index also. "REQ:- 4771 mplsXxxxROCompliance -> better mplsXxxxReadOnlyCompliance". RSP: 4773 done. 4775 5.2. Changes from 4777 The following changes are from the IESG MIB review. 4779 Changed "Label Switch Router" to "Label Switching Router". 4781 Spelling errors fixed (unlabelled, atttempt, subsytem). 4783 Changed some of the enums to start at 1, instead of zero: 4784 mplsLdpPeerLoopDetectionForPV and mplsLdpEntityOperStatus. 4786 Added REFERENCE clauses. 4788 Added a timestamp object for mplsLdpSesState changes. 4790 Changed NMS to command generator as defined in RFC2571. 4792 Added a lastChange objects: mplsLdpEntityLastChange and 4793 mplsLdpPeerLastChange. 4795 Added TEXTUAL-CONVENTIONS for MplsLabelDistributionMethod and 4796 MplsRetentionMode. These TCs have been incorporated into draft-ietf- 4797 mpls-tc-mib-04.txt. 4799 Divided up the one MIB MODULE into 3 additional modules for a total 4800 of 4 MIB MODULES: 1) mplsLdpMIB, 2) mplsLdpGenericMIB which includes 4801 objects pertaining to Ethernet as the L2, 3) mplsLdpAtmMIB which 4802 includes objects pertaining to ATM as the L2, and 4) 4803 mplsLdpFrameRelayMIB which includes objects pertaining to Frame Relay 4804 as the L2. 4806 Also, reduced the number of objects by creating the mplsLdpLspTable 4807 and removing the Mapping tables. 4809 In section 3.1 changed "where each row in the table initiates" to 4810 "where each row in the table represents". 4812 Updated Reference Section and divided them into Normative vs. 4813 Informative. 4815 Removed the MplsGenAddress TC and used the INET-ADDRESS-MIB's 4816 InetAddress TC. Objects using this TC are: 4818 mplsLdpEntityTargetPeerAddr, mplsFecAddr, and 4819 mplsLdpSesPeerNextHopAddr and are noted in the conformance statements 4820 supporting: unknown(0), ipv4(1), and ipv6(2). 4822 Removed AddressFamilyNumbers TC and used InetAddressType TC from the 4823 INET-ADDRESS-MIB. One of the MIB compilers as a warning because 4824 apparently one is expected to use InetAddressType and InetAddress 4825 together (although, think this restriction is too restrictive). Also, 4826 removed the reference for the Address Family Numbers MIB. 4828 Changed the name TargPeer to TargetPeer. 4830 Removed the Enable/Disable trap objects: 4831 mplsLdpEntityPVLMisTrapEnable, and mplsLdpSesUpDownTrapEnable. RFC 4832 2573 should be used to eable/disable traps. 4834 Removed the import for "transmission" and instead, imported "mplsMIB 4835 from the MPLS-TC-MIB". 4837 Changed mplsLdpEntityPVL to mplsLdpEntityPathVectorLimit and updated 4838 the DESCRIPTION clause. Also, the PVL abbreviation was expanded to 4839 PathVectorLimit for other objects. 4841 Combined the objects: mplsLdpPeerLoopDectionForPV and mplsLdpPeerPVL 4842 into one object: mplsLdpPeerPathVectorLimit and updated the 4843 DESCRIPTION clause. 4845 mplsLdpEntityTcpDscPort uses InetPortNumber TC from the INET-ADDRESS- 4846 MIB. Likewise, mplsLdpEntityUdpDscPort uses the InetPortNumber TC 4847 from the INET-ADDRESS-MIB. Also a REFERENCE clause was added. 4849 The mplsLdpEntityMaxPduLength object has the SYNTAX range changed to 4850 start at 256. Also the DESCRIPTION clause was updated. 4852 The mplsLdpSesMaxPduLen object's name was changed to 4853 mplsLdpSesMaxPduLength and a UNITS clause was added, and the 4854 DESCRIPTION clause was updated. This object is related to the 4855 mplsLdpEntityMaxPduLength object. 4857 The mplsLdpEntityKeepAliveHoldTimer and mplsLdpEntityHelloHoldTimer 4858 DESCRIPTION clause was changed from "The two octet value" to "The 4859 16-bit integer value". 4861 The mplsLdpEntityHelloHoldTimer object's DESCRIPTION clause was 4862 updated. 4864 A range of Integer32(0..100) was added to the SYNTAX clause of the 4865 mplsLdpEntityInitSesThreshold object. Also, the DESCRIPTION clause 4866 of this object was updated. 4868 The mplsLdpEntityOptionalParameters object was renamed to 4869 mplsLdpEntityLabelType. 4871 Updated the mplsLdpEntityAdminStatus and mplsLdpEntityRowStatus 4872 objects. RowStatus now reflects the status of the row, and Admin 4873 status controls enabling/disabling the entry. 4875 Updated the DESCRIPTION clauses for the objects in the 4876 mplsLdpEntityStatsTable to refer to the 4877 mplsLdpEntityDiscontinuityTime object. 4879 Changed StorType to StorageType. 4881 5.3. Changes from 4883 There were three types of changes: the first change was that all the 4884 MPLS Textual Conventions from this MIB, the LSR and MPLS-TE MIBs were 4885 moved into a new document [MPLSTCMIB], "draft-ietf-mpls-tc- 4886 mib-00.txt". The Textual Conventions are now IMPORTED from 4887 [MPLSTCMIB]. The second type of change was updates based on comments 4888 from the IESG. These changes will be discussed below. The third 4889 type of changes were based on minor editorial changes from the co- 4890 authors. 4892 The "Introduction" and "Structure of the MIB" sections were reworded 4893 since they were repetitive. 4895 The "Overview" was rearranged. 4897 References were added to "The LDP Entity ATM Objects" and "The LDP 4898 Entity Frame Relay Objects" Sections. 4900 The Working Group mailing list and Chairs were added to the CONTACT- 4901 INFO. 4903 Updated the DESCRIPTION clause for the "mplsLdpEntityLdpId" object. 4905 Updated the mplsLdpEntityProtocolVersion to include a range 4906 (1..65535). 4908 Updated the "References" Section. 4910 Running the MIB through the smilint MIB compiler showed that some 4911 object names were longer than 32 characters, these were shortened to 4912 32 characters or fewer. 4914 The following changes were from the co-authors. 4916 Other minor editorial changes such as fixing typographical errors, 4917 and removing MIB comments which are no longer meaningful. 4919 Page 17 (also page 46) the description was enhanced to describe the 4920 version field in the LDP header from RFC3036. 4922 Removed WellKnown from the tcp and upd port names. It's the ports 4923 that get set, and the default value is the well known (actually the 4924 registered) port number. 4926 mplsLdpEntityInitSesTrapEnable object is useless and was removed 4927 since setting mplsLdpEntityInitSesThreshold=0 acheives the same 4928 thing. Also removed it from the descriptive text in section 3. 4930 Page 47, mplsLdpSessionDiscontinuityTime The initial value of this 4931 was changed to be sysUpTime instead of zero. sysUpTime for when the 4932 session starts is more meaningful and was added to the Session 4933 Up/Down Traps also. Also, added the Session specific stats to the 4934 up/down traps. 4936 5.4. Changes from 4938 All changes were from the second last call which took place Thursday, 4939 July 20th, until Thursday, July 27th, 2000 and are described in the 4940 remainder of this section. 4942 Remove the reference to the MPLS framework document. 4944 Add an mplsFecIndexNext type of object. 4946 Change the conformance of the FEC table objects to be part of the 4947 mplsLdpGeneralGroup. 4949 The mplsLdpEntityConfGenericTable is no longer needed because the 4950 functionality has been absorbed by the 4951 mplsLdpEntityConfGenericLabelRangeTable. The 4952 mplsLdpEntityConfGenericTable has been removed and the front section 4953 was updated accordingly. 4955 Other editorial issues, updating references, typos and so forth. 4957 5.5. Changes from 4959 The majority of changes in this revision are based on Last Call 4960 comments which were received during the last call from Thursday, 4961 March 9, 2000 to Friday, March 17, 2000, or slightly thereafter. 4962 Also, changes were made to agree with the latest specifications. 4963 These changes are described in this section. 4965 Changes due to draft-ietf-mpls-ldp-07.txt and draft-ietf-mpls- 4966 ldp-08.txt. Specifically, removing references to IPv4/IP and using 4967 router id, as appropriate. 4969 Removed vpMerge and vpAndVcMerge choices from the object, 4970 mplsLdpEntityAtmMergeCap. VP Merge is not described in [RFC3036]. 4972 The LIB Table was removed and replaced by mapping tables to map LDP 4973 LSPs created by LDP sessions to the mplsInSegment, mplsOutSegment and 4974 mplsXC tables in the LSR MIB. The conformance section was updated 4975 to include a Mapping Group which is to be implemented iff these LSR 4976 MIB tables (mplsInSegmentTable, mplsOutSegmentTable and mplsXCTable) 4977 are implemented. 4979 The front section was updated to include information on the Generic 4980 label table. 4982 Added more in the front section on on Row 4983 Creation/adminStatus/OperStatus in the LDP Entity and related tables. 4985 Added a generic label range table. NOTE: there is NO corresponding 4986 LDP message which relates to the information in this table, however, 4987 this table does provide a way for a user to 'reserve' a generic label 4988 range. 4990 A new TEXTUAL-CONVENTION, MplsAtmVcIdentifier was added. This TC has 4991 the same upper bounds as AtmVcIdentifier (from rfc2514) except that 4992 the lower bound is 32 (and not 0). The lower bound is 32 since this 4993 value is specified by [RFC3035]. 4995 Removed the scalar object mplsLsrLabelRetentionMode and added 4996 mplsLdpEntityLabelRetentionMode. The change was made to allow 4997 configuring the retention mode on a per LDP Entity basis, as opposed 4998 for the entire LSR. 5000 Typo in section 3.5.2 was fixed. 5002 Typo in the mplsLdpSessionUp notification description was fixed. 5004 Section 'LDP Notifications' was expanded to cover both the 5005 'mplsLdpSessionUp' and 'mplsLdpSessionDown' traps. Also, the objects 5006 which enable and disable these traps have been described in this 5007 Section: 5009 The 'mplsLdpEntityHopCountLoopDetection' object and the 5010 'mplsLdpEntityHopCount' object have been combined into the new 5011 object, 'mplsLdpEntityHopCountLimit'. 5013 MplsLabel has been updated to reflect the VPI value of 12 bits and 5014 not 8. 5016 Added DEFVAL clause to the 'mplsLdpEntityWellKnownDiscoveryPort' 5017 object. The default value is 646. 5019 Added UNITS and DEFVAL clauses to the 'mplsLdpEntityMaxPduLength' 5020 object. The default value is 4096 and the units is octets. 5022 Added DEFVAL clause to 'mplsLdpEntityProtocolVersion' object. The 5023 default value is 1. 5025 Added DEFVAL clause to 'mplsLdpEntityKeepAliveHoldTimer' of 40 5026 seconds. 5028 Added DEFVAL clause to 'mplsLdpEntityInitSesThreshold' object. The 5029 default value is 8. 5031 The mplsLdpEntityWellKnownDiscoveryPort was changed into two objects, 5032 one for TCP and one for UDP. The names are 5034 Typo in the description for the 5036 The mplsLdpEntityPeerTable was (re-)named mplsLdpPeerTable. The 5037 mplsLdpSessionTable now AUGMENTs the mplsLdpPeerTable in order to 5038 show that these two tables are related. There has been wording added 5039 to the mplsLdpSessionEntry description and to the description for the 5040 mplsLdpPeerTable. 5042 5.6. Changes from 5044 Editorial changes, fixing typo's, fixing wrapping lines, etc. 5046 Updated references for latest drafts, and added [RFC3032] and 5047 [RFC3034] to Reference Section. 5049 Added to the Acknowledgements Section. 5051 Changed the SYNTAX and DESCRIPTION of the 5052 'mplsLdpLsrLoopDetectionCapable' object, so that it will also support 5053 the loop detection by hop count. 5055 Combined the 'mplsLdpEntityLoopDetectionForPV' and 'mplsLdpEntityPVL' 5056 objects. The functionality of the 'mplsLdpEntityLoopDectionForPV' is 5057 now denoted by the value of 0 (zero) in the 'mplsLdpEntityPVL' 5058 object. This results in one less object 5059 'mplsLdpEntityLoopDectionForPV' but does not sacrifice functionality. 5061 Changed 'mplsLdpLibLabelType' into two objects: 5062 'mplsLdpLibInLabelType' and differ from the egress label type. The 5063 MIB now reflects this. 5065 The following items were changed as a result of the Frame Relay Forum 5066 dropping support for 17-bit DLCIs: the MplsLabel TC description has 5067 been modified, and other Frame Relay Object descriptions were also 5068 modified (as specified in this section). 5070 The MplsLabel TC was also modified and reference 3. was added to the 5071 REFERENCE Clause. 5073 MplsLdpLabelTypes TC was modified to use an enum. 5075 InterfaceIndex support was added to the Entity information. This was 5076 specifically requested by several members of the working group. An 5077 additional table, mplsLdpEntityConfGenericTable as a way to configure 5078 Generic Labels, and an object, 'mplsLdpConfGenericIfIndexOrZero was 5079 added to map the InterfaceIndex used by Generic Labels. Objects were 5080 also added to the 'mplsLdpEntityAtmParmsTable' and the and 5081 'mplsLdpEntityFrIfIndex', respectively. 5083 Changed the name of the 'mplsLdpEntityMtu' object to be 5084 'mplsLdpEntityMaxPduLength' which is more consistent with the LDP 5085 Specification. Also, the description and SYNTAX were changed. 5087 Changed the SYNTAX of the 'mplsLdpSessionMaxPduLength' to unsigned32 5088 and changed the Range from (0..65535) to (1..65535). 5090 Added and improved the front section discussion on SNMP 5091 Notifications. 5093 Also, modified the DESCRIPTION clause of the 5095 Added objects to enable/disable the sending of traps: 5097 Added an object to enable/disable sending traps for Sessions changing 5098 from Up to Down, or Down to Up. 5100 Added notifications to generate traps from session changing from Up 5101 to Down, or Down to up. 5103 Added a StorageType object to the Entity and associated tables which 5104 are configurable. 5106 Added a Discontinuity Time object to the Entity Table, 5108 Added discussion on row creation in the Entity and other associated 5109 Entity tables. This is a new Section in the Front part of the 5110 document called: 5112 Removed the 'mplsLdpEntityControlMethod'. 5114 Made 'mplsLdpFecLspId' as part of the INDEX for the FEC table. This 5115 is to allow FECs to map to multiple LSPs. Also add a RowPointer to a 5116 row in the Session Table. 5118 Added an operation status object, 'mplsLdpLspOperStatus' and a last 5119 Change object, 'mplsLdpLspLastChangeto the LIB Table. This will be 5120 used to detect whether an LSP has changed its status. 5122 Changed the name of the mplsLdpPeerTable to the 5123 mplsLdpEntityPeerTable. This table contains information relevant to 5124 Peers which are known to specific Entities. The indexing of this 5125 table has also changed to include the Row in the Entity Table that 5126 this Peer is known by. The mplsLdpHelloAdjacencyTable and the 5127 mplsLdpSessionTable have been moved under this table. Since Hello 5128 Adjacencies are related to Entity-Peer information and Sessions are 5129 related to Entity-Peer information this was seen as a comprehensive 5130 and coherent modelling. Associated descriptions in the front section 5131 and in the tables have been changed to reflect this change. 5133 Moved the 'mplsLdpConfFrLen' object from the 5134 'mplsLdpEntityConfFrLabelRangeTable' to the 5135 'mplsLdpEntityFrameRelayParmsTable' since the Frame Relay 5136 interface/port can only use one header length at a time, i.e. a 5137 specific FR interface supports one address length for all VCs on that 5138 interface. Also, changed the object so that it only supports 10 and 5139 23 bit DLCI lengths. (The 17 bit length was dropped by the Frame 5140 Relay Forum and thus, is no longer required.) The name of this 5141 object was changed from 'mplsLdpConfFrLen' to 'mplsLdpEntityFrLen' to 5142 fit in with the 'mplsLdpEntityFrameRelayParmsTable'. 5144 Removed the seventeenDlciBits(1) value from the mplsLdpFrSessionLen 5145 object. (The 17 bit length was dropped by the Frame Relay Forum and 5146 thus, is no longer required.) 5148 Corrected the range of the 'mplsLdpEntityIndexNext' object to include 5149 0 (zero). 5151 5.7. Changes from 5153 Reworded the description of the mplsLdpAtmSessionTable to clarify 5154 that one or MORE label range intersection(s) is/are represented in 5155 this table. 5157 Reworded the description of the mplsLdpFrameRelaySessionTable to 5158 clarify that one or MORE label range intersection(s) is/are 5159 represented in this table. 5161 Added a new index, mplsLdpSessionPeerIndex, to the 5162 mplsLdpSessionPeerAddressTable. This new index uniquely identifies 5163 the entry within a given session. (Since adding 5164 mplsLdpSessionPeerNextHopAddressType, 5165 mplsLdpSessionPeerNextHopAddress to the INDEX clause of the 5166 mplsLdpSessionPeerAddressTable leaves a table with only indices and 5167 no objects, the work around was to add a new index which uniquely 5168 differentiates an entry within a given session.) 5170 Quite a few changes to the mplsLdpPeerTable. First, removed the 5171 mplsLdpPeerIndex from the mplsLdpPeerTable and other tables. This 5172 index served no purpose, so was removed. Second, removed the 5173 objects: mplsLdpPeerInternetworkAddrType, and 5174 mplsLdpPeerInternetworkAddr. Third, reworded the description of this 5175 table to include information which is known during Session 5176 Intialization attempts, the specific information has to do with Loop 5177 Dection based on Path Vectors. Since Section 3.5.3 of the LDP Spec 5178 when describing the PVLim says: "Although knowledge of a peer's path 5179 vector limit will not change an LSR's behavior, it does enable the 5180 LSR to alert an operator to a possible misconfiguration." and the 5181 object mplsLdpPeerPVL is sent as a varbind in the mplsLdpPVLMismatch 5182 notification. 5184 Removed the mplsLdpPeerIndex from the mplsLdpHelloAdjacencyTable. 5186 Removed the "IANA Address Family Numbers" MIB section. 5188 Updated the boiler.me from the ops web page dated Weds., Dec 22, 5189 1999. 5191 Updated the Security Section from the ops web page. 5193 Added the following objects to the mplsLdpEntityTable: 5194 mplsLdpEntityControlMethod, mplsLdpEntityLoopDectionForPV, and 5195 mplsLdpEntityPathVectorLimit. 5197 Removed mplsLdpSessionLabelAdvertisement, 5198 mplsLdpSessionLoopDetectionForPV, and mplsLdpSessionPathVectorLimit 5199 from the mplsLdpSessionTable. 5201 Changed the mplsLdpPathVectorLimitMismatch Notification to send 5202 mplsLdpEntityPathVectorLimit (instead of 5203 mplsLdpSessionPathVectorLimit). 5205 Copied the MplsLabel TC from draft-ietf-mpls-lsr-mib-00.txt and 5206 replaced the MplsLdpGenAddr for mplsLdpLibInLabel and 5207 mplsLdpLibOutLabel with MplsLabel. 5209 The mplsLdpSessionIndex was removed throughout the MIB. This was 5210 replaced by the object mplsLdpSessionDiscontinuityTime. The 5211 motivation was to reduce the number of indices. 5213 The descriptions for the objects in the mplsLdpSessionStatsTable, 5214 mplsLdpSessionStatsUnknownMessageTypeErrors and 5215 mplsLdpSessionStatsUnknownTlvErrors, have been updated to include a 5216 reference to the mplsLdpSessionDiscontinuityTime object. 5218 5.8. Changes from 5220 Added Scalar Objects: mplsLdpLsrLoopDetectionPresent, and 5221 mplsLdpEntityIndexNext. 5223 Added the following objects to the mplsLdpEntityTable: 5225 mplsLdpEntityProtocolVersion, mplsLdpEntityAdminStatus, 5226 mplsLdpEntityOperStatus, mplsLdpEntityTargetedPeer, 5227 mplsLdpEntityTargetedPeerAddrType, mplsLdpEntityTargetedPeerAddr, and 5228 mplsLdpEntityHelloHoldTimer. 5230 Changed the description of the mplsLdpEntityAtmParmsTable and added 5231 the following objects to this table: mplsLdpEntityAtmLsrConnectivity, 5232 mplsLdpEntityDefaultControlVpi, mplsLdpEntityDefaultControlVci, 5233 mplsLdpEntityUnlabTrafVpi, and mplsLdpEntityUnlabTrafVci. NOTE: the 5234 last four objects were in Version 01 of the MIB but were mistakenly 5235 omitted from Version 02. Now, they are back. 5237 Changed the indexing of the mplsLdpEntityConfAtmLabelRangeTable to 5238 include the minimum VPI/VCI. This is to ensure that indices in this 5239 table are unique. 5241 Changed the indexing of the mplsLdpEntityConfFrLabelRangeTable, to 5242 include the minimum DLCI value. This is to ensure that indices in 5243 this table are unique. 5245 Added [RFC3036] to Reference Section. 5247 5.9. Changes from 5249 The MIB was updated to correspond to draft-ietf-mpls-ldp-06.txt of 5250 the LDP Specification [RFC3036]. 5252 The front section was updated. 5254 The MIB was made to be less ATM-centric. Essentially, the ATM 5255 specific objects where removed from the tables and placed in ATM 5256 specific Tables. A type was added to the base tables and a row is to 5257 be created in the ATM/FR/etc. type table. Apropos compliance 5258 statements were added to reflect the separation of ATM and Frame 5259 Relay objects into their respective tables. 5261 Objects for Loop Detection were removed from describing the LDP 5262 implementation (i.e. the scalars were removed) and Loop Dection 5263 objects were added to the Session Table. (Although as the LDP 5264 Specification indicates loop detection should be for an LSR within a 5265 domain.) 5267 The following tables were added: mplsLdpEntityAtmParmsTable, 5268 mplsLdpEntityConfAtmLabelRangeTable, mplsLdpFrameRelayParmsTable, 5269 mplsLdpConfFrLabelRangeTable, mplsLdpAtmSessionTable, 5270 mplsLdpFrameRelaySessionTable, mplsLdpSessionPeerAddressTable, 5271 mplsLdpLibTable, and the mplsLdpFecTable. 5273 The following notifications were added: notification for Session 5274 removal. 5276 The following objects were removed from the Session Table: 5277 mplsLdpSessionRole was removed (this can be determined by comparing 5278 LSR Ids and does not need to be explicitly in the MIB.) ATM specific 5279 objects (mplsLdpSessionAtmLabelRangeLowerBoundVpi 5280 mplsLdpSessionAtmLabelRangeLowerBoundVci, 5281 mplsLdpSessionAtmLabelRangeUpperBoundVpi 5282 mplsLdpSessionAtmLabelRangeUpperBoundVci) were removed and put into a 5283 separate table. Frame Relay objects were added in a separate table. 5285 Hello Adjacency Table was updated. 5287 The objects, mplsLdpSessionRejectedParamErrors, 5288 mplsLdpSessionRejectedNoHelloErrors, mplsLdpBadLdpIdentifierErrors, 5289 mplsLdpBadPduLengthErrors, mplsLdpBadMessageLengthErrors, 5290 mplsLdpBadTlvLengthErrors, mplsLdpMalformedTlvValueErrors, 5291 mplsLdpKeepAliveTimerExpiredErrors, mplsLdpShutdownNotifReceived, and 5292 mplsLdpShutdownNotifSent were added to the mplsLdpEntityStatsTable. 5294 The mplsLdpSessionStatsTable was added to count statics based on a 5295 per Session basis. 5297 The mplLdpPeerConfAtmLabelRangeTable has been removed. There is no 5298 need to configure information for a Peer. All information for a peer 5299 is learned, thus peer information is read-only. 5301 (Editorial) References were updated to reflect the documents which 5302 this version was based on. 5304 5.10. Changes from 5306 Textual conventions were added for the LSR Identifier and the LDP 5307 Identifier. 5309 Top-level mib structure was added. The LDP MIB falls under a proposed 5310 hierarchy of mpls.mplsProtocols. 5312 The mib hierarchy within the LDP MIB was also changed. A new branch, 5313 under mpls.mplsProtocols.mplsLdpMIB.mplsLdpObjects was added. This 5314 branch is mplsLdpLsrObjects. Currently, this contains several new 5315 scalar objects: mplsLdpLsrID, mplsLdpLsrLoopDetectionPresent, 5316 mplsLdpLsrLoopDetectinAdminStatus, mplsLdpLsrPathVectorLimit, 5317 mplsLdpLsrHopCountLimit, mplsLdpLsrLoopPreventionPresent, 5318 mplsLdpLsrLoopPreventionAdminStatus, and 5319 mplsLdpLsrLabelRetentionMode. 5321 mplsLdpEntityTable is now indexed by mplsLdpEntityIdentifier, which 5322 is the LDP Identifier used in Session establishment. 5323 mplsLdpEntityLoopDetection and mplsLdpEntityLoopPrevention objects 5324 were removed from this table. 5326 The following objects were added to the mplsLdpEntityTable: 5327 mplsLdpEntityLabelSpaceType, mplsLdpEntityUnlabTrafVpi, 5328 mplsLdpEntityUnlabTrafVci, mplsLdpEntityMergeCapability, 5329 mplsLdpEntityVcDirectionality, and 5330 mplsLdpEntityLabelDistributionMethod. 5332 The following objects were added to the mplsLdpPeerEntityTable: 5333 mplsLdpPeerLabelDistributionMethod. 5335 The following object was removed from the mplsLdpEntityStatsTable: 5336 mplsLdpEntityEstablishedSessions. 5338 References were added and revised. 5340 6. Acknowledgments 5342 The authors would like to thank the following people: Leigh 5343 McLellan, Geetha Brown, Geping Chen and Charlan Zhou from Nortel 5344 Networks, and Zoltan Takacs and Bo Augustsson from Ericsson. Also, 5345 some members of the working group were very helpful with comments and 5346 corrections to the MIB; the authors would like to thank Adrian Farrel 5347 of Movaz Networks, and Alan Kullberg from NetPlane Systems. 5349 7. Normative References 5351 [RFC1700] Reynolds, J. and J. Postel, "ASSIGNED NUMBERS", STD 2, RFC 5352 1700, October 1994. 5354 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 5355 Requirement Levels", BCP 14, RFC 2119, Harvard University, 5356 March 1997 5358 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 5359 Rose, M. and S. Waldbusser, "Structure of Management 5360 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 5361 1999. 5363 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 5364 Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", 5365 STD 58, RFC 2579, April 1999. 5367 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 5368 Rose, M. and S. Waldbusser, "Conformance Statements for 5369 SMIv2", STD 58, RFC 2580, April 1999. 5371 [RFC3031] Rosen, E., Viswananthan, A., and R. Callon, "Multiprotocol 5372 Label Switching Architecture", RFC 3031, January 2001. 5374 [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., Farinacci, 5375 D., Li, T. and A. Conta, "MPLS Label Stack Encoding", RFC 5376 3032, January 2001. 5378 [RFC3034] Conta, A., Doolan, P., and A. Malis, "Use of Label Switching 5379 on Frame Relay Networks Specification", RFC 3034, January 5380 2001. 5382 [RFC3035] Davie, B., Lawrence, J., McCloghrie, K., Rosen, E., Swallow, 5383 G., Rekhter, Y. and P. Doolan, "MPLS using LDP and ATM VC 5384 Switching", RFC 3035, January 2001. 5386 [RFC3036] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and B. 5387 Thomas, "LDP Specification", RFC 3036, January 2001. 5389 [RFC3037] Thomas, B. and E. Gray, "LDP Applicability", RFC 3037, 5390 January 2001. 5392 [RFC3215] Boscher, C., Cheval, P., Wu L. and E. Gray, "LDP State 5393 Machine", RFC 3215, January 2002. 5395 [LSRMIB] Srinivansan, C., Viswanathan, A., and T. Nadeau "MPLS Label 5396 Switching Router Management Information Base Using SMIv2", 5397 draft-ietf-mpls-lsr-mib-08.txt, January 2002. 5399 [MPLSTCMIB] Nadeau, T., J. Cucchiara, (Eds.) "Definitions of Textual 5400 Conventions for Multiprotocol Label Switching Management", 5401 draft-ietf-mpls-tc-mib-06.txt, March 2003. 5403 8. Informative References 5405 [RFC2115] Brown, C., and F. Baker, "Management Information Base for 5406 Frame Relay DTEs Using SMIv2", RFC 2115, September 1997. 5408 [RFC2514] Noto, M., E. Spiegel, K. Tesink, editors, "Definition of 5409 Textual Conventions and OBJECT-IDENTITIES for ATM 5410 Management", RFC 2514, February 1999. 5412 [RFC2515] Tesink, K. (ed.) "Definitions of Managed Objects for ATM 5413 Management", RFC 2515, February 1999. 5415 [RFC2863] McCloghrie, K., F. Kastenholz, "The Interfaces Group MIB 5416 using SMIv2", RFC 2863, June 2000. 5418 [RFC2684] Grossman, D., and J. Heinanen, "Multiprotocol Encapsulation 5419 over ATM Adaptation Layer 5", RFC 2684, September 1999. 5421 [RFC3291] Daniele, M., Haberman, B., Routhier, S. and J. 5422 Schoenwaelder, "Textual Coventions for Internet Network 5423 Addresses", RFC 3291, May 2002. 5425 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 5426 "Introduction and Applicability Statements for Internet- 5427 Standard Management Framework", RFC 3410, December 2002. 5429 [MPLSMGMT] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol 5430 Label Switching (MPLS) Management Overview", draft-ietf- 5431 mpls-mgmt-overview-03.txt, February 2003. 5433 9. Security Considerations 5435 This Security Considerations section consists of 4 subsections, one 5436 for each of the MIB Modules in this document. 5438 9.1. Security Considerations for MPLS-LDP-MIB 5440 There are a number of management objects defined in this MIB module 5441 with a MAX-ACCESS clause of read-write and/or read-create. Such 5442 objects may be considered sensitive or vulnerable in some network 5443 environments. The support for SET operations in a non-secure 5444 environment without proper protection can have a negative effect on 5445 network operations. These are the tables and objects and their 5446 sensitivity/vulnerability: 5448 o the mplsLdpEntityTable contains objects to provision potential 5449 LDP sessions on the Label Switching Router (LSR) or Label Edge 5450 Router (LER). The mplsLdpLspFecTable contains objects which 5451 associate an LSP with a FEC. Unauthorized access to objects in 5452 these tables, could result in disruption of traffic on the 5453 network. This is especially true if an LDP session has been 5454 established. The use of stronger mechanisms such as SNMPv3 5455 security should be considered where possible. Specifically, 5456 SNMPv3 VACM and USM MUST be used with any v3 agent which 5457 implements this MIB. Administrators should consider whether 5458 read access to these objects should be allowed, since read 5459 access may be undesirable under certain circumstances. 5461 Some of the readable objects in this MIB module "i.e., objects with a 5462 MAX-ACCESS other than not-accessible" may be considered sensitive or 5463 vulnerable in some network environments. It is thus important to 5464 control even GET and/or NOTIFY access to these objects and possibly 5465 to even encrypt the values of these objects when sending them over 5466 the network via SNMP. These are the tables and objects and their 5467 sensitivity/vulnerability: 5469 o the mplsLdpEntityTable, mplsLdpPeerTable, mplsLdpSesTable and 5470 mplsLdpSesStatsTable collectively show the LDP LSP network 5471 topology. If an Administrator does not want to reveal the LDP 5472 LSP topology of the network, then these tables should be 5473 considered sensitive/vulnerable. 5475 SNMP versions prior to SNMPv3 did not include adequate security. 5476 Even if the network itself is secure "for example by using IPSec", 5477 even then, there is no control as to who on the secure network is 5478 allowed to access and GET/SET "read/change/create/delete" the objects 5479 in this MIB module. 5481 It is RECOMMENDED that implementers consider the security features as 5482 provided by the SNMPv3 framework "see [RFC3410], section 8", 5483 including full support for the SNMPv3 cryptographic mechanisms "for 5484 authentication and privacy". 5486 Further, deployment of SNMP versions prior to SNMPv3 is NOT 5487 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 5488 enable cryptographic security. It is then a customer/operator 5489 responsibility to ensure that the SNMP entity giving access to an 5490 instance of this MIB module, is properly configured to give access to 5491 the objects only to those principals "users" that have legitimate 5492 rights to indeed GET or SET "change/create/delete" them. 5494 9.2. Security Considerations for MPLS-LDP-ATM-MIB 5496 There are a number of management objects defined in this MIB module 5497 with a MAX-ACCESS clause of read-write and/or read-create. Such 5498 objects may be considered sensitive or vulnerable in some network 5499 environments. The support for SET operations in a non-secure 5500 environment without proper protection can have a negative effect on 5501 network operations. These are the tables and objects and their 5502 sensitivity/vulnerability: 5504 o the mplsLdpEntityAtmTable and mplsLdpEntityAtmLRTable contain 5505 objects to provision potential LDP sessions on the Label 5506 Switching Router (LSR) or Label Edge Router (LER) over Layer 2 5507 of ATM. These tables extend the mplsLdpEntityTable in the MPLS- 5508 LDP-MIB. Unauthorized access to objects in these tables, could 5509 result in disruption of traffic on the network. This is 5510 especially true if an LDP session has been established. The use 5511 of stronger mechanisms such as SNMPv3 security should be 5512 considered where possible. Specifically, SNMPv3 VACM and USM 5513 MUST be used with any v3 agent which implements this MIB. 5514 Administrators should consider whether read access to these 5515 objects should be allowed, since read access may be undesirable 5516 under certain circumstances. 5518 Some of the readable objects in this MIB module "i.e., objects with a 5519 MAX-ACCESS other than not-accessible" may be considered sensitive or 5520 vulnerable in some network environments. It is thus important to 5521 control even GET and/or NOTIFY access to these objects and possibly 5522 to even encrypt the values of these objects when sending them over 5523 the network via SNMP. These are the tables and objects and their 5524 sensitivity/vulnerability: 5526 o the mplsLdpEntityAtmTable and mplsLdpEntityAtmLRTable show the 5527 Label Ranges for ATM. If an Administrator does not want to 5528 reveal this information then these tables should be considered 5529 sensitive/vulnerable and treated accordingly. 5531 SNMP versions prior to SNMPv3 did not include adequate security. 5532 Even if the network itself is secure "for example by using IPSec", 5533 even then, there is no control as to who on the secure network is 5534 allowed to access and GET/SET "read/change/create/delete" the objects 5535 in this MIB module. 5537 It is RECOMMENDED that implementers consider the security features as 5538 provided by the SNMPv3 framework "see [RFC3410], section 8", 5539 including full support for the SNMPv3 cryptographic mechanisms "for 5540 authentication and privacy". 5542 Further, deployment of SNMP versions prior to SNMPv3 is NOT 5543 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 5544 enable cryptographic security. It is then a customer/operator 5545 responsibility to ensure that the SNMP entity giving access to an 5546 instance of this MIB module, is properly configured to give access to 5547 the objects only to those principals "users" that have legitimate 5548 rights to indeed GET or SET "change/create/delete" them. 5550 9.3. Security Considerations for MPLS-LDP-FRAME-RELAY-MIB 5552 There are a number of management objects defined in this MIB module 5553 with a MAX-ACCESS clause of read-write and/or read-create. Such 5554 objects may be considered sensitive or vulnerable in some network 5555 environments. The support for SET operations in a non-secure 5556 environment without proper protection can have a negative effect on 5557 network operations. These are the tables and objects and their 5558 sensitivity/vulnerability: 5560 o the mplsLdpEntityFrameRelayTable and 5561 mplsLdpEntityFrameRelayLRTable contain objects to provision 5562 potential LDP sessions on the Label Switching Router (LSR) or 5563 Label Edge Router (LER) over Layer 2 of Frame Relay. These 5564 tables extend the mplsLdpEntityTable in the MPLS-LDP-MIB. 5565 Unauthorized access to objects in these tables, could result in 5566 disruption of traffic on the network. This is especially true 5567 if an LDP session has been established. The use of stronger 5568 mechanisms such as SNMPv3 security should be considered where 5569 possible. Specifically, SNMPv3 VACM and USM MUST be used with 5570 any v3 agent which implements this MIB. Administrators should 5571 consider whether read access to these objects should be allowed, 5572 since read access may be undesirable under certain 5573 circumstances. 5575 Some of the readable objects in this MIB module "i.e., objects with a 5576 MAX-ACCESS other than not-accessible" may be considered sensitive or 5577 vulnerable in some network environments. It is thus important to 5578 control even GET and/or NOTIFY access to these objects and possibly 5579 to even encrypt the values of these objects when sending them over 5580 the network via SNMP. These are the tables and objects and their 5581 sensitivity/vulnerability: 5583 o the mplsLdpEntityFrameRelayTable and 5584 mplsLdpEntityFrameRelayLRTable show the Label Ranges for Frame 5585 Relay. If an Administrator does not want to reveal this 5586 information then these tables should be considered 5587 sensitive/vulnerable and treated accordingly. 5589 SNMP versions prior to SNMPv3 did not include adequate security. 5590 Even if the network itself is secure "for example by using IPSec", 5591 even then, there is no control as to who on the secure network is 5592 allowed to access and GET/SET "read/change/create/delete" the objects 5593 in this MIB module. 5595 It is RECOMMENDED that implementers consider the security features as 5596 provided by the SNMPv3 framework "see [RFC3410], section 8", 5597 including full support for the SNMPv3 cryptographic mechanisms "for 5598 authentication and privacy". 5600 Further, deployment of SNMP versions prior to SNMPv3 is NOT 5601 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 5602 enable cryptographic security. It is then a customer/operator 5603 responsibility to ensure that the SNMP entity giving access to an 5604 instance of this MIB module, is properly configured to give access to 5605 the objects only to those principals "users" that have legitimate 5606 rights to indeed GET or SET "change/create/delete" them. 5608 9.4. Security Considerations for MPLS-LDP-GENERIC-MIB 5610 There are a number of management objects defined in this MIB module 5611 with a MAX-ACCESS clause of read-write and/or read-create. Such 5612 objects may be considered sensitive or vulnerable in some network 5613 environments. The support for SET operations in a non-secure 5614 environment without proper protection can have a negative effect on 5615 network operations. These are the tables and objects and their 5616 sensitivity/vulnerability: 5618 o the mplsLdpEntityGenericLRTable contains objects to provision 5619 potential LDP sessions on the Label Switching Router (LSR) or 5620 Label Edge Router (LER) over Layer 2 of Ethernet. This table 5621 extends the mplsLdpEntityTable in the MPLS-LDP-MIB. 5622 Unauthorized access to objects in these tables, could result in 5623 disruption of traffic on the network. This is especially true 5624 if an LDP session has been established. The use of stronger 5625 mechanisms such as SNMPv3 security should be considered where 5626 possible. Specifically, SNMPv3 VACM and USM MUST be used with 5627 any v3 agent which implements this MIB. Administrators should 5628 consider whether read access to these objects should be allowed, 5629 since read access may be undesirable under certain 5630 circumstances. 5632 Some of the readable objects in this MIB module "i.e., objects with a 5633 MAX-ACCESS other than not-accessible" may be considered sensitive or 5634 vulnerable in some network environments. It is thus important to 5635 control even GET and/or NOTIFY access to these objects and possibly 5636 to even encrypt the values of these objects when sending them over 5637 the network via SNMP. These are the tables and objects and their 5638 sensitivity/vulnerability: 5640 o the mplsLdpEntityGenericLRTable shows the Label Ranges for 5641 ethernet. If an Administrator does not want to reveal this 5642 information then these tables should be considered 5643 sensitive/vulnerable and treated accordingly. 5645 SNMP versions prior to SNMPv3 did not include adequate security. 5646 Even if the network itself is secure "for example by using IPSec", 5647 even then, there is no control as to who on the secure network is 5648 allowed to access and GET/SET "read/change/create/delete" the objects 5649 in this MIB module. 5651 It is RECOMMENDED that implementers consider the security features as 5652 provided by the SNMPv3 framework "see [RFC3410], section 8", 5653 including full support for the SNMPv3 cryptographic mechanisms "for 5654 authentication and privacy". 5656 Further, deployment of SNMP versions prior to SNMPv3 is NOT 5657 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 5658 enable cryptographic security. It is then a customer/operator 5659 responsibility to ensure that the SNMP entity giving access to an 5660 instance of this MIB module, is properly configured to give access to 5661 the objects only to those principals "users" that have legitimate 5662 rights to indeed GET or SET "change/create/delete" them. 5664 10. IANA Considerations 5666 As described in [MPLSMGMT] and as stated in the MPLS-TC-MIB 5667 [MPLSTCMIB], MPLS related standards track MIB modules should be 5668 rooted under the mplsMIB subtree. There are 4 MPLS MIB Modules 5669 contained in this document, each of the following "IANA 5670 Considerations" subsections requests IANA for a new assignment under 5671 the mplsMIB subtree. New assignments can only be made via a 5672 Standards Action as specified in [RFC2434]. 5674 10.1. IANA Considerations for the MPLS-LDP-MIB Module 5676 The IANA is requested to assign { mplsMIB 4 } to the MPLS-LDP-MIB 5677 module specified in this document. 5679 10.2. IANA Considerations for the MPLS-LDP-ATM-MIB Module 5681 The IANA is requested to assign { mplsMIB 5 } to the MPLS-LDP-ATM-MIB 5682 module specified in this document. 5684 10.3. IANA Considerations for the MPLS-LDP-FRAME-RELAY-MIB Module 5686 The IANA is requested to assign { mplsMIB 6 } to the MPLS-LDP-FRAME- 5687 RELAY-MIB module specified in this document. 5689 10.4. IANA Considerations for the MPLS-LDP-GENERIC-MIB Module 5691 The IANA is requested to assign { mplsMIB 7 } to the MPLS-LDP- 5692 GENERIC-MIB module specified in this document. 5694 11. Intellectual Property Notice 5696 The IETF takes no position regarding the validity or scope of any 5697 intellectual property or other rights that might be claimed to 5698 pertain to the implementation or use of the technology described in 5699 this document or the extent to which any license under such rights 5700 might or might not be available; neither does it represent that it 5701 has made any effort to identify any such rights. Information on the 5702 IETF's procedures with respect to rights in standards-track and 5703 standards-related documentation can be found in BCP-11 [RFC2028]. 5704 Copies of claims of rights made available for publication and any 5705 assurances of licenses to be made available, or the result of an 5706 attempt made to obtain a general license or permission for the use of 5707 such proprietary rights by implementors or users of this 5708 specification can be obtained from the IETF Secretariat. 5710 The IETF invites any interested party to bring to its attention any 5711 copyrights, patents or patent applications, or other proprietary 5712 rights that may cover technology that may be required to practice 5713 this standard. Please address the information to the IETF Executive 5714 Director. 5716 12. Authors' Addresses 5718 James V. Luciani 5719 Consultant 5720 PO Box 1010 5721 Concord, MA 01742 5722 USA 5723 Email: james_luciani@mindspring.com 5725 Hans Sjostrand 5726 ipUnplugged 5727 P.O. Box 101 60 5728 S-121 28 Stockholm, Sweden 5729 Phone: +46 8 725 5930 5730 Email: hans@ipunplugged.com 5732 Joan Cucchiara 5733 Artel 5734 237 Cedar Hill Street 5735 Marlborough, MA 01752 5736 Phone: +1-508-303-8200 x302 5737 Email: jcucchiara@artel.com 5739 13. Full Copyright Statement 5741 Copyright (C) The Internet Society (2003). All Rights Reserved. 5743 This document and translations of it may be copied and furnished to 5744 others, and derivative works that comment on or otherwise explain it 5745 or assist in its implementation may be prepared, copied, published 5746 and distributed, in whole or in part, without restriction of any 5747 kind, provided that the above copyright notice and this paragraph are 5748 included on all such copies and derivative works. However, this 5749 document itself may not be modified in any way, such as by removing 5750 the copyright notice or references to the Internet Society or other 5751 Internet organizations, except as needed for the purpose of 5752 developing Internet standards in which case the procedures for 5753 copyrights defined in the Internet Standards process must be 5754 followed, or as required to translate it into languages other than 5755 English. 5757 The limited permissions granted above are perpetual and will not be 5758 revoked by the Internet Society or its successors or assigns. 5760 This document and the information contained herein is provided on an 5761 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 5762 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 5763 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 5764 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 5765 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.