idnits 2.17.1 draft-ietf-mpls-ldp-mib-11.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 48 instances of too long lines in the document, the longest one being 6 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 3395 has weird spacing: '...erlying media...' == Line 4482 has weird spacing: '...ndex is creat...' == Line 4512 has weird spacing: '...ibed in detai...' == Line 4687 has weird spacing: '...entence s/ini...' == Line 5252 has weird spacing: '... (Since addin...' == (1 more instance...) == 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 (June 2003) is 7593 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 5716, but not defined ** Obsolete undefined reference: RFC 2434 (Obsoleted by RFC 5226) == Unused Reference: 'RFC2115' is defined on line 5511, but no explicit reference was found in the text == Unused Reference: 'RFC2514' is defined on line 5514, but no explicit reference was found in the text == Unused Reference: 'RFC3037' is defined on line 5487, but no explicit reference was found in the text == Unused Reference: 'RFC3215' is defined on line 5490, but no explicit reference was found in the text == Unused Reference: 'RFC3289' is defined on line 5493, but no explicit reference was found in the text == Unused Reference: 'RFC3291' is defined on line 5497, 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 ** Obsolete normative reference: RFC 3291 (Obsoleted by RFC 4001) == Outdated reference: A later version (-14) exists of draft-ietf-mpls-lsr-mib-09 == Outdated reference: A later version (-10) exists of draft-ietf-mpls-tc-mib-06 == Outdated reference: A later version (-09) exists of draft-ietf-mpls-mgmt-overview-04 Summary: 9 errors (**), 0 flaws (~~), 19 warnings (==), 2 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 December 2003 H. Sjostrand 4 IP Unplugged 5 J. Luciani 6 Consultant 7 June 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-STD-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 3.7 LDP Notification Frequency ................................. 10 69 4 MPLS Label Distribution Protocol MIB Definitions ............. 10 70 4.1 The MPLS-LDP-ATM-STD-MIB Module ............................ 64 71 4.1.1 The LDP ATM Session Table ................................ 64 72 4.2 The MPLS-LDP-FRAME-RELAY-STD-MIB Module .................... 81 73 4.2.1 The LDP Frame Relay Session Table ........................ 82 74 4.3 The MPLS-LDP-GENERIC-STD-MIB Module ........................ 96 75 5 Revision History ............................................. 104 76 5.1 Changes from .............. 104 77 5.2 Changes from .............. 104 78 5.2.1 Changes based on MIB Doctor Review Comments .............. 104 79 5.3 Changes from .............. 109 80 5.4 Changes from .............. 111 81 5.5 Changes from .............. 112 82 5.6 Changes from .............. 113 83 5.7 Changes from .............. 115 84 5.8 Changes from .............. 117 85 5.9 Changes from .............. 119 86 5.10 Changes from ............. 119 87 5.11 Changes from ............. 120 88 6 Acknowledgments .............................................. 121 89 7 Normative References ......................................... 122 90 8 Informative References ....................................... 124 91 9 Security Considerations ...................................... 124 92 9.1 Security Considerations for MPLS-LDP-STD-MIB ............... 124 93 9.2 Security Considerations for MPLS-LDP-ATM-STD-MIB ........... 125 94 ........................................................... 126 95 9.4 Security Considerations for MPLS-LDP-GENERIC-STD-MIB ....... 127 96 9.5 Additional Security Considerations ......................... 128 97 10 IANA Considerations ......................................... 128 98 10.1 IANA Considerations for the MPLS-LDP-STD-MIB Module ....... 128 99 ........................................................... 129 100 ...................................................... 129 101 Module .................................................... 129 102 11 Intellectual Property Notice ................................ 129 103 12 Authors' Addresses .......................................... 129 104 13 Full Copyright Statement .................................... 130 106 1. Introduction 108 This document defines 4 MIB Modules which together support the 109 configuration and monitoring of the Label Distribution Protocol 110 (LDP). The Label Distribution Protocol (LDP) [RFC3036] is one type 111 of Multiprotocol Label Switching (MPLS) protocols described in 112 [RFC3031] and [RFC3032]. Utilizing all 4 MIB Modules allows an 113 operator to configure LDP sessions using 3 different Layer 2 media. 114 The Layer 2 media supported by the MIB Modules are Ethernet, ATM and 115 Frame Relay as described in [RFC3036], [RFC3034] and [RFC3035]. 117 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 118 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 119 document are to be interpreted as described in RFC 2119 [RFC2119]. 121 2. The Internet-Standard Management Framework 123 For a detailed overview of the documents that describe the current 124 Internet-Standard Management Framework, please refer to section 7 of 125 RFC 3410 [RFC3410]. 127 Managed objects are accessed via a virtual information store, termed 128 the Management Information Base or MIB. MIB objects are generally 129 accessed through the Simple Network Management Protocol (SNMP). 130 Objects in the MIB are defined using the mechanisms defined in the 131 Structure of Management Information (SMI). This memo specifies a MIB 132 module that is compliant to the SMIv2, which is described in STD 58, 133 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 134 [RFC2580]. 136 3. Structure of the MIB 138 This section describes the structure of the LDP MIB. 140 3.1. Overview 142 There are 4 MIB Modules in this document. These MIB Modules are the 143 MPLS-LDP-STD-MIB, the MPLS-LDP-GENERIC-STD-MIB, the MPLS-LDP-ATM-STD- 144 MIB and the MPLS-LDP-FRAME-RELAY-STD-MIB. The MPLS-LDP-STD-MIB 145 defines objects which are common to all LDP implementations. The 146 MPLS-LDP-GENERIC-STD-MIB defines Layer 2 Per Platform Label Space 147 objects for use with the MPLS-LDP-STD-MIB. The MPLS-LDP-ATM-STD-MIB 148 defines Layer 2 Asynchronous Transfer Mode (ATM) objects for use with 149 the MPLS-LDP-STD-MIB. The MPLS-LDP-FRAME-RELAY-STD-MIB defines Layer 150 2 FRAME-RELAY objects for use with the MPLS-LDP-STD-MIB. 152 The MPLS-LDP-STD-MIB Module MUST be implemented and at least one of 153 the Layer 2 MIB Modules MUST be implemented. As an example, if an 154 Label Switching Router (LSR) or Label Edge Router (LER) 155 implementation intends to support LDP utilizing a Layer 2 of 156 Ethernet, then the MPLS-LDP-STD-MIB and the MPLS-LDP-GENERIC-STD-MIB 157 Modules MUST implemented. If an LSR/LER implementation intends to 158 support LDP utilizing a Layer 2 of ATM, then the MPLS-LDP-STD-MIB 159 Module and the MPLS-LDP-ATM-MIB Module MUST be implemented. If an 160 LSR/LER implementation intends to support LDP utilizing a Layer 2 of 161 FRAME-RELAY, then the MPLS-LDP-STD-MIB Module and the MPLS-LDP-FRAME- 162 RELAY-STD-MIB Module MUST be implemented. An LDP implementation that 163 utilizes all three Layer 2 media (Ethernet, Frame-Relay, ATM) MUST 164 support all 4 MIB Modules. Each of the Modules will be discussed in 165 detail in the following sections. 167 There are 2 Compliance statements for each MIB Module. One which is 168 for full compliance which includes configuration and monitoring via 169 SNMP. The other is a read-only compliance which allows SNMP to 170 monitor. 172 3.2. Future Considerations 174 The LDP Specification [RFC3036] does not specify the use of VPNs or 175 multicast for LDP, and thus, objects related to these areas have not 176 been included. 178 [RFC2684] does not describe VP merge capability and so this feature 179 has not been included. 181 These areas need to be specified in the LDP Specification or other 182 specifications prior to being added in this or any other MIB 183 document. 185 3.3. Interface Indexing 187 Interface Indexes as specified in [RFC2863] are used in these MIB 188 Modules. The descriptions of the ifIndexes denote which ifIndex is 189 being used. The use of ifIndex is for actual existing connections. 191 3.4. Differences from the LDP Specification 193 Currently, there are 3 differences between this specification and the 194 LDP Specification. As previously mentioned, this document is almost 195 entirely based on the LDP specification. The differences are 196 documented here. 198 The first difference is that the LDP Entity Table contains some 199 DEFVAL clauses which are not specified explicitly in the LDP 200 Specification. These values, although not documented in the LDP 201 Specification are widely used by existing LDP MIB implementations and 202 thus, have been adopted within this MPLS-LDP-STD-MIB. Please note, 203 they can certainly be changed during row creation or a subsequent set 204 request. 206 A second difference is the mplsLdpEntityConfGenericLRTable in the 207 MPLS-LDP-GENERIC-STD-MIB Module. This table, although provided as a 208 way to reserve a range of generic labels, does not exist in the LDP 209 Specification. It was added to the MIB due to a request from the 210 working group and because this table was considered useful for 211 reserving a range of generic labels. 213 The third difference is documented by the TEXTUAL-CONVENTION, 214 MplsAtmVcIdentifier which is in the MPLS-TC-MIB [MPLSTCMIB]. This TC 215 was added to restrict vci values to be greater than 31 as described 216 in RFC 3035 [RFC3035]. 218 3.5. The MPLS-LDP-STD-MIB Module 220 This MIB Module contains objects which are common to all LDP 221 implementations. This MIB Module MUST always be implemented along 222 with one or more of the Layer 2 MIB Modules. 224 This table allows the Label Edge Router (LER) or the Label Switching 225 router (LSR) to initiate and/or receive requests to establish LDP 226 sessions. As the LDP protocol distributes labels and establishes 227 sessions with Peers most of the tables in this MIB are populated by 228 the agent as instructed by the LDP protocol. The exception is the 229 mplsFecTable and the mplsLdpLspFecTable which can be configured by 230 the operator to specify Forwarding Equivalence Class information for 231 an LSP. 233 Each table in the MPLS-LDP-STD-MIB Module is described in the 234 following subsections. 236 3.5.1. The LDP Entity Table 238 The MPLS-LDP-STD-MIB provides objects to configure or allow potential 239 LDP sessions on a specific LSR/LER. The mplsLdpEntityTable is used 240 to configure potential LDP Sessions, where each row in the table 241 represents a potential LDP Session. 243 Each entry/row in this table represents a single LDP Entity. There 244 is no maximum number of LDP Entities specified. However, there is an 245 mplsLdpEntityIndexNext object which should be retrieved by the 246 command generator prior to creating an LDP Entity. If the 247 mplsLdpEntityIndexNext object is zero, this indicates that the LSR is 248 not able to create another LDP Entity at that time. 250 3.5.1.1. Changing Values After Session Establishment 252 One way to manually modify a session's parameters is by using SNMP to 253 change the MIB objects related to that session. Please note, special 254 care should be taken if MIB objects which are used in the MPLS LDP 255 Session Initialization need to be modified. If the modification of 256 any of these MIB variables takes place anytime after the start of 257 session intialization, then the entire session must be halted. Any 258 information learned by that session must be discarded. The objects 259 should then be modified, and session initialization started. 260 Assuming that the configuration was done correctly, then a new 261 session will be created. 263 For example, assume that an operator wishes to change the 264 configuration of a Label Range which is used by a Session that has 265 already been established. The operator should change the 266 mplsLdpEntityAdminStatus to "disable(2)". Setting the 267 mplsLdpEntityAdminStatus to "disable(2)" will cause the session to be 268 torn down (i.e. this will signal to LDP that it should send out tear 269 down messages for that session). Also, all information related to 270 that session should be removed from this MIB by the Agent. This 271 includes Peer information (i.e. relevant row in the mplsPeerTable) 272 and Session statistics (i.e. releveant row in the 273 mplsLdpSessionTable). Also, if the LSR MIB is implemented and the 274 optional Mapping Table objects are implemented, then all information 275 related to the LSPs in this session should be removed from these 276 MIBs. [For more information please see the section on "The Mapping 277 Tables".] At this point, the operator could modify the Label Range. 278 Lastly, the operator should set the mplsLdpEntityAdminStatus to 279 "enable(1)". At this point session initialization should occur. The 280 LDP Entity goes through the Session Initialization in order to 281 communicate the new Label Ranges to the Peer and establish new LSPs. 283 3.5.2. The LDP Entity Statistics Table 285 The mplsLpdEntityStatsTable is a read-only table which contains 286 statistical information related to failed attempts to establish 287 sessions. Each row in this table is related to a single LDP entity 288 and this table AUGMENTS an mplsLdpEntityEntry. This table could be 289 used to give insight into how to reconfigure values so that a session 290 could be successfully established. For example, if the 291 mplsLdpSesRejectedLRErrors Counter object was increasing, then this 292 would indicate that the Label Range (LR) may need to be adjusted. 294 3.5.3. The LDP Peer Table 296 The LDP Peer Table is a read-only table which contains information 297 about LDP Peers known to LDP Entities. In other words, the Peer 298 information is learned by LDP through initialization or discovery. 299 This table should be populated by the agent as directed by the LDP 300 protocol. 302 A row in this table is related to one or more rows in the Hello 303 Adjacency Table and related to a single row in the Session Table. 304 The values in the Peer table are specific to a Peer and may or may 305 not be the same values used in the session. The reason is that the 306 Peer and Entity negotiate certain values. The Entity's values are 307 configured in the mplsLdpEntityTable and the Peer's values are 308 learned (and placed into the mplsLdpPeerTable). The 309 mplsLdpSessionTable shows the values used in establishing the 310 session. 312 One example, of when the Peer's values and the Session's values may 313 differ is with the Peer's Path Limit information. The Peer's Path 314 Limit information is learned from the session initialization phase. 315 The actual value for the Path Vector Limit is the Peer's value and 316 may not be the same value that appears in the session. There could 317 be a mismatch in this value between the Entity and the Peer. In the 318 event of a mismatch, then the session will use the Path Limit set by 319 the Entity (and not the Peer). 321 The Peer Table information was placed in a separate table from the 322 Session information to allow for a more comprehensive and coherent 323 MIB model. 325 3.5.4. The LDP Session Table 327 The LDP Session Table is a read-only table. Each entry in this table 328 represents a single session between an LDP Entity and a Peer. The 329 mplsLdpSessionEntry AUGMENTS the mplsLdpPeerEntry. 331 The information in this table is learned during session 332 establishment. NOTE: rows in this table will appear during session 333 intialization. 335 3.5.5. The LDP Session Statistics Table 337 The MPLS LDP Session Stats Table is a read-only table which contains 338 statistical information on sessions. 340 3.5.6. The LDP Hello Adjacencies Table 342 This is a table of all adjacencies between all LDP Entities and all 343 LDP Peers. A Session may have one or more adjacencies. A session 344 should not have zero adjacencies, because this indicates that the 345 session has lost contact with the Peer. A session which has zero 346 Hello Adjacencies should be eventually removed. 348 3.5.7. The LDP LSP Table 350 The Label Information Base (LIB) contains information about labels 351 learned by the LSR. The LIB for LDP, CR-LDP and MPLS-RSVP (i.e. all 352 currently defined MPLS protocols) is represented in the LSR MIB 353 [LSRMIB]. The LIB is represented by the LSR MIB's mplsXCTable (mpls 354 Cross Connect Table), mplsInSegmentTable (mpls In Segment Table) and 355 the mplsOutSegmentTable (mpls Out Segment Table). The mplsXCTable 356 models the cross-connection of the ingress label with a specific 357 egress label. The mplsInSegmentTable stores the ingress label's 358 information, and the mplsOutSegmentTable stores the egress label's 359 information. 361 The LDP Session that created the LSP and the LSP's (ingress label, 362 egress label) pair along with other information is contained in the 363 LSR MIB's mplsXCTable, the mplsInSegmentTable and the 364 mplsOutSegmentTable. 366 In order to utilize the LSR MIB's mplsXCTable, mplsInSegmentTable and 367 mplsOutSegmentTable for LDP LSPs, there needs to be a mechanism to 368 associate LDP sessions with LDP LSPs created as a result of those LDP 369 sessions. The mplsInSegmentLdpLspTable and mplsOutSegmentLdpLspTable 370 in this MIB contain information to find the LDP LSP entries in the 371 mplsInSegmentTable, mplsOutSegmentTable and the mplsXCTable. 373 These two tables, the mplsInSegmentLdpLspTable and 374 mplsOutSegmentLdpLspTable, have been made optional in the conformance 375 section of the MIB. They only need to be supported if the LSR MIBs 376 mplsInSegmentTable, mplsOutSegmentTable and mplsXCTable are 377 implemented. 379 As discussed in the section, "Changing Values after Session 380 Establishment", if a session is torn down, then all the information 381 related to this session, must be removed from the both LDP MIB and, 382 if implemented, from the LSR MIB. 384 3.5.8. The FEC Table 386 The FEC Table is a table which contains FEC (Forwarding Equivalence 387 Class) information. Each entry/row represents a single FEC Element. 388 There is also an LDP LSP FEC Table, mplsLdpLspFecTable, which 389 associates FECs with the LSPs. 391 3.5.9. The LDP Session Peer Address Table 393 The MPLS LDP Session Peer Address Table is a table which extends the 394 mplsLdpSessionTable. This table is a read-only table which stores 395 Addresses learned after session initialization via Address Message 396 advertisement. 398 3.6. LDP Notifications 400 Currently, there are several notifications which are specific for 401 LDP. These are described in this section. 403 The mplsLdpInitSesThresholdExceeded notification indicates to the 404 operator that there may be a misconfigured mplsLdpEntityEntry because 405 the session associated with this Entity is not being established, and 406 the Entity keeps trying to establish the session. A side effect of 407 this situation is that a row in the mplsLdpSessionTable may not be 408 reaching the operational state as indicated by the 409 mplsLdpSessionState object. If the value of 410 mplsLdpEntityInitSessionThreshold is 0 (zero) then this is equal to 411 specifying the value of infinity for the threshold, and the 412 mplsLdpInitSessionThresholdExceeded notification will never be sent. 414 The mplsLdpPathVectorLimitMismatch notification is generated when 415 there is a mismatch in the Path Vector Limits between the Entity and 416 Peer during session initialization. The session uses the value which 417 is configured as the Entity's Path Vector Limit. However, a 418 notification should be generated to indicate that a mismatch 419 occurred. For further details, please see Section 3.5.3 of the LDP 420 Specification [RFC3036]. 422 The mplsLdpSessionUp and mplsLdpSessionDown notifications are 423 generated when there is an appropriate change in the 424 mplsLdpSessionState object, e.g. when sessions change state (Up to 425 Down for the mplsLdpSessionDown trap, or Down to Up for the 426 mplsLdpSessionUp trap). 428 3.7. LDP Notification Frequency 430 LDP Notifications are expected to be few in number when LDP is 431 ubiquitously deployed in a relatively stable network. An NMS that is 432 receiving these notifications should not be overwhelmed by the 433 frequency of LDP notifications. If this assertion proves to be 434 inaccurate, then a throttling object to throttle these notifications 435 may be added to future versions of the MPLS-LDP-STD-MIB. 437 4. MPLS Label Distribution Protocol MIB Definitions 439 MPLS-LDP-STD-MIB DEFINITIONS ::= BEGIN 441 IMPORTS 442 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, 443 Integer32, Counter32, Unsigned32 444 FROM SNMPv2-SMI 445 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 446 FROM SNMPv2-CONF 448 RowStatus, TimeInterval, TruthValue, 449 TimeStamp, StorageType 450 FROM SNMPv2-TC 452 InterfaceIndexOrZero 453 FROM IF-MIB 455 InetAddressPrefixLength, 456 InetAddressType, 457 InetAddress, 458 InetPortNumber 459 FROM INET-ADDRESS-MIB 461 IndexInteger, 462 IndexIntegerNextFree 463 FROM DIFFSERV-MIB 465 mplsStdMIB, 466 MplsLabel, 467 MplsLabelDistributionMethod, 468 MplsLdpIdentifier, 469 MplsLdpLabelType, 470 MplsLspType, 471 MplsLsrIdentifier, 472 MplsRetentionMode 473 FROM MPLS-TC-STD-MIB; 475 mplsLdpStdMIB MODULE-IDENTITY 476 LAST-UPDATED "200306091200Z" -- 9 June 2003 477 ORGANIZATION "Multiprotocol Label Switching (mpls) 478 Working Group" 479 CONTACT-INFO 481 "Joan Cucchiara (jcucchiara@artel.com) 482 Artel 484 Hans Sjostrand (hans@ipunplugged.com) 485 ipUnplugged 486 James V. Luciani (james_luciani@mindspring.com) 487 Consultant 489 Working Group Chairs: 490 George Swallow, email: swallow@cisco.com 491 Loa Andersson, email: loa@pi.se 493 MPLS Working Group, email: mpls@uu.net" 495 DESCRIPTION 496 "Copyright (C) The Internet Society (2003). This 497 version of this MIB module is part of RFCXXX; see 498 the RFC itself for full legal notices. 500 This MIB contains managed object definitions for the 501 'Multiprotocol Label Switching, Label Distribution 502 Protocol, LDP' document." 504 REVISION "200306091200Z" -- 9 June 2003 505 DESCRIPTION 506 "Initial version published as part of RFC XXXX." 508 -- Please see the IANA Considerations Section. 509 -- The requested mplsStdMIB subId is 4, e.g. 510 -- ::= { mplsStdMIB 4 } 512 ::= { mplsStdMIB XXX } -- to be assigned by IANA 514 --**************************************************************** 516 mplsLdpNotifications OBJECT IDENTIFIER ::= { mplsLdpStdMIB 0 } 517 mplsLdpObjects OBJECT IDENTIFIER ::= { mplsLdpStdMIB 1 } 518 mplsLdpConformance OBJECT IDENTIFIER ::= { mplsLdpStdMIB 2 } 520 --**************************************************************** 521 -- MPLS LDP Objects 522 --**************************************************************** 524 mplsLdpLsrObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 1 } 526 mplsLdpEntityObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 2 } 528 -- 529 -- The MPLS Label Distribution Protocol's 530 -- Label Switching Router Objects 531 -- 532 mplsLdpLsrId OBJECT-TYPE 533 SYNTAX MplsLsrIdentifier 534 MAX-ACCESS read-only 535 STATUS current 536 DESCRIPTION 537 "The LSR's Identifier." 538 ::= { mplsLdpLsrObjects 1 } 540 mplsLdpLsrLoopDetectionCapable OBJECT-TYPE 541 SYNTAX INTEGER { 542 none(1), 543 other(2), 544 hopCount(3), 545 pathVector(4), 546 hopCountAndPathVector(5) 547 } 548 MAX-ACCESS read-only 549 STATUS current 550 DESCRIPTION 551 "A indication of whether this 552 Label Switching Router supports 553 loop detection. 555 none(1) -- Loop Detection is not supported 556 on this LSR. 558 other(2) -- Loop Detection is supported but 559 by a method other than those 560 listed below. 562 hopCount(3) -- Loop Detection is supported by 563 Hop Count only. 565 pathVector(4) -- Loop Detection is supported by 566 Path Vector only. 568 hopCountAndPathVector(5) -- Loop Detection is 569 supported by both Hop Count 570 And Path Vector. 572 Since Loop Detection is determined during 573 Session Initialization, an individual session 574 may not be running with loop detection. This 575 object simply gives an indication of whether or not the 576 LSR has the ability to support Loop Detection and 577 which types." 579 ::= { mplsLdpLsrObjects 2 } 581 -- 582 -- The MPLS Label Distribution Protocol Entity Objects 583 -- 585 mplsLdpEntityLastChange OBJECT-TYPE 586 SYNTAX TimeStamp 587 MAX-ACCESS read-only 588 STATUS current 589 DESCRIPTION 590 "The value of sysUpTime at the time of the most 591 recent addition or deletion of an entry 592 to/from the mplsLdpEntityTable/mplsLdpEntityStatsTable, or 593 the most recent change in value of any objects in the 594 mplsLdpEntityTable. 596 If no such changes have occurred since the last 597 re-initialization of the local management subsystem, 598 then this object contains a zero value." 599 ::= { mplsLdpEntityObjects 1 } 601 mplsLdpEntityIndexNext OBJECT-TYPE 602 SYNTAX IndexIntegerNextFree 603 MAX-ACCESS read-only 604 STATUS current 605 DESCRIPTION 606 "This object contains an appropriate value to 607 be used for mplsLdpEntityIndex when creating 608 entries in the mplsLdpEntityTable. The value 609 0 indicates that no unassigned entries are 610 available." 611 ::= { mplsLdpEntityObjects 2 } 613 mplsLdpEntityTable OBJECT-TYPE 614 SYNTAX SEQUENCE OF MplsLdpEntityEntry 615 MAX-ACCESS not-accessible 616 STATUS current 617 DESCRIPTION 618 "This table contains information about the 619 MPLS Label Distribution Protocol Entities which 620 exist on this Label Switching Router (LSR) 621 or Label Edge Router (LER)." 623 ::= { mplsLdpEntityObjects 3 } 625 mplsLdpEntityEntry OBJECT-TYPE 626 SYNTAX MplsLdpEntityEntry 627 MAX-ACCESS not-accessible 628 STATUS current 629 DESCRIPTION 630 "An entry in this table represents an LDP entity. 631 An entry can be created by a network administrator 632 or by an SNMP agent as instructed by LDP." 633 INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex } 634 ::= { mplsLdpEntityTable 1 } 636 MplsLdpEntityEntry ::= SEQUENCE { 637 mplsLdpEntityLdpId MplsLdpIdentifier, 638 mplsLdpEntityIndex IndexInteger, 639 mplsLdpEntityProtocolVersion Unsigned32, 640 mplsLdpEntityAdminStatus INTEGER, 641 mplsLdpEntityOperStatus INTEGER, 642 mplsLdpEntityTcpDscPort InetPortNumber, 643 mplsLdpEntityUdpDscPort InetPortNumber, 644 mplsLdpEntityMaxPduLength Unsigned32, 645 mplsLdpEntityKeepAliveHoldTimer Unsigned32, 646 mplsLdpEntityHelloHoldTimer Unsigned32, 647 mplsLdpEntityInitSessionThreshold Integer32, 648 mplsLdpEntityLabelDistMethod MplsLabelDistributionMethod, 649 mplsLdpEntityLabelRetentionMode MplsRetentionMode, 650 mplsLdpEntityPathVectorLimit Integer32, 651 mplsLdpEntityHopCountLimit Integer32, 652 mplsLdpEntityTransportAddrKind INTEGER, 653 mplsLdpEntityTargetPeer TruthValue, 654 mplsLdpEntityTargetPeerAddrType InetAddressType, 655 mplsLdpEntityTargetPeerAddr InetAddress, 656 mplsLdpEntityLabelType MplsLdpLabelType, 657 mplsLdpEntityDiscontinuityTime TimeStamp, 658 mplsLdpEntityStorageType StorageType, 659 mplsLdpEntityRowStatus RowStatus 660 } 662 mplsLdpEntityLdpId OBJECT-TYPE 663 SYNTAX MplsLdpIdentifier 664 MAX-ACCESS not-accessible 665 STATUS current 666 DESCRIPTION 667 "The LDP identifier." 669 REFERENCE 670 "RFC3036, LDP Specification, Section on LDP Identifiers." 671 ::= { mplsLdpEntityEntry 1 } 673 mplsLdpEntityIndex OBJECT-TYPE 674 SYNTAX IndexInteger 675 MAX-ACCESS not-accessible 676 STATUS current 677 DESCRIPTION 678 "This index is used as a secondary index to uniquely 679 identify this row. Before creating a row in this table, 680 the 'mplsLdpEntityIndexNext' object should be retrieved. 681 That value should be used for the value of this index 682 when creating a row in this table. (NOTE: if a value 683 of zero (0) is retrieved, that indicates that no rows 684 can be created in this table at this time. 686 A secondary index (this object) is meaningful to some 687 but not all, LDP implementations. For example 688 in an LDP implementation which uses PPP would 689 use this index to differentiate PPP sub-links. 691 Another way to use this index is to give this the 692 value of ifIndex. However, this is dependant 693 on the implementation." 694 ::= { mplsLdpEntityEntry 2 } 696 mplsLdpEntityProtocolVersion OBJECT-TYPE 697 SYNTAX Unsigned32(1..65535) 698 MAX-ACCESS read-create 699 STATUS current 700 DESCRIPTION 701 "The version number of the LDP protocol which will be 702 used in the session initialization message. 704 Section 3.5.3 in the LDP Specification specifies 705 that the version of the LDP protocol is negotiated during 706 session establishment. The value of this object 707 represents the value that is sent in the initialization 708 message." 709 REFERENCE 710 "RFC3036, LDP Specification, Section 3.5.3 Initialization 711 Message." 712 DEFVAL { 1 } 713 ::= { mplsLdpEntityEntry 3 } 715 mplsLdpEntityAdminStatus OBJECT-TYPE 716 SYNTAX INTEGER { 717 enable(1), 718 disable(2) 719 } 720 MAX-ACCESS read-create 721 STATUS current 722 DESCRIPTION 723 "The administrative status of this LDP Entity. 724 If this object is changed from 'enable' to 'disable' 725 and this entity has already attempted to establish 726 contact with a Peer, then all contact with that 727 Peer is lost and all information from that Peer 728 needs to be removed from the MIB. (This implies 729 that the network management subsystem should clean 730 up any related entry in the mplsLdpPeerTable. This 731 further implies that a 'tear-down' for that session 732 is issued and the session and all information related 733 to that session cease to exist). 735 At this point the operator is able to change values 736 which are related to this entity. 738 When the admin status is set back to 'enable', then 739 this Entity will attempt to establish a new session 740 with the Peer." 741 DEFVAL { enable } 742 ::= { mplsLdpEntityEntry 4 } 744 mplsLdpEntityOperStatus OBJECT-TYPE 745 SYNTAX INTEGER { 746 unknown(1), 747 enabled(2), 748 disabled(3) 749 } 750 MAX-ACCESS read-only 751 STATUS current 752 DESCRIPTION 753 "The operational status of this LDP Entity." 754 ::= { mplsLdpEntityEntry 5 } 756 mplsLdpEntityTcpDscPort OBJECT-TYPE 757 SYNTAX InetPortNumber 758 MAX-ACCESS read-create 759 STATUS current 760 DESCRIPTION 761 "The TCP Discovery Port for 762 LDP. The default value is the well-known 763 value of this port." 764 REFERENCE 765 "RFC3036, LDP Specification, Section 2.4.1, 766 Basic Discovery Mechanism, Section 2.4.2, 767 Extended Discovery Mechanism, Section 768 3.10, Well-known Numbers, and Section 3.10.1. 769 UDP and TCP Ports." 770 DEFVAL { 646 } 771 ::= { mplsLdpEntityEntry 6 } 773 mplsLdpEntityUdpDscPort OBJECT-TYPE 774 SYNTAX InetPortNumber 775 MAX-ACCESS read-create 776 STATUS current 777 DESCRIPTION 778 "The UDP Discovery Port for 779 LDP. The default value is the 780 well-known value for this port." 781 REFERENCE 782 "RFC3036, LDP Specification, Section 2.4.1, 783 Basic Discovery Mechanism, Section 2.4.2, 784 Extended Discovery Mechanism, Section 785 3.10, Well-known Numbers, and Section 3.10.1. 786 UDP and TCP Ports." 787 DEFVAL { 646 } 788 ::= { mplsLdpEntityEntry 7 } 790 mplsLdpEntityMaxPduLength OBJECT-TYPE 791 SYNTAX Unsigned32 (256..65535) 792 UNITS "octets" 793 MAX-ACCESS read-create 794 STATUS current 795 DESCRIPTION 796 "The maximum PDU Length that is sent in 797 the Common Session Parameters of an Initialization 798 Message. According to the LDP Specification [RFC3036] 799 a value of 255 or less specifies the 800 default maximum length of 4096 octets, this is why 801 the value of this object starts at 256. The operator 802 should explicitly choose the default value (i.e. 4096), 803 or some other value. 805 The receiving LSR MUST calculate the maximum PDU 806 length for the session by using the smaller of its and 807 its peer's proposals for Max PDU Length." 808 REFERENCE 809 "RFC3036, LDP Specification, Section 3.5.3. 810 Initialization Message." 811 DEFVAL { 4096 } 812 ::= { mplsLdpEntityEntry 8 } 814 mplsLdpEntityKeepAliveHoldTimer OBJECT-TYPE 815 SYNTAX Unsigned32 (1..65535) 816 UNITS "seconds" 817 MAX-ACCESS read-create 818 STATUS current 819 DESCRIPTION 820 "The 16-bit integer value which is the proposed keep 821 alive hold timer for this LDP Entity." 822 DEFVAL { 40 } 823 ::= { mplsLdpEntityEntry 9 } 825 mplsLdpEntityHelloHoldTimer OBJECT-TYPE 826 SYNTAX Unsigned32 (0..65535) 827 UNITS "seconds" 828 MAX-ACCESS read-create 829 STATUS current 830 DESCRIPTION 831 "The 16-bit integer value which is the proposed Hello 832 hold timer for this LDP Entity. The Hello Hold time 833 in seconds. 835 An LSR maintains a record of Hellos received 836 from potential peers. This object represents 837 the Hold Time in the Common Hello Parameters TLV of 838 the Hello Message. 840 A value of 0 is a default value and should be 841 interpretted in conjunction with the 842 mplsLdpEntityTargetPeer object. 844 If the value of this object is 0: if the value of the 845 mplsLdpEntityTargetPeer object is false(2), then this 846 specifies that the Hold Time's actual default value is 847 15 seconds (i.e. the default Hold time for Link Hellos 848 is 15 seconds). Otherwise if the value of the 849 mplsLdpEntityTargetPeer object is true(1), then this 850 specifies that the Hold Time's actual default value is 851 45 seconds (i.e. the default Hold time for Targeted 852 Hellos is 45 seconds). 854 A value of 65535 means infinite (i.e. wait forever). 856 All other values represent the amount of time in 857 seconds to wait for a Hello Message. Setting the 858 hold time to a value smaller than 15 is not 859 recommended, although not forbidden according 860 to RFC3036." 861 REFERENCE 862 "RFC3036, LDP Specification, Section 3.5.2., 863 Hello Message." 864 DEFVAL { 0 } 865 ::= { mplsLdpEntityEntry 10 } 867 mplsLdpEntityInitSessionThreshold OBJECT-TYPE 868 SYNTAX Integer32(0..100) 869 MAX-ACCESS read-create 870 STATUS current 871 DESCRIPTION 872 "When attempting to establish a session with a 873 given Peer, the given LDP Entity should 874 send out the SNMP notification, 875 'mplsLdpInitSesThresholdExceeded', when 876 the number of Session Initialization messages sent 877 exceeds this threshold. The notification is 878 used to notify an operator when this Entity and 879 its Peer are possibily engaged in an endless 880 sequence of messages as each NAKs the other's 881 Initialization messages with Error Notification 882 messages. Setting this threshold which triggers 883 the notification is one way to 884 notify the operator. 886 A value of 0 (zero) for this object 887 indicates that the threshold is infinity, thus 888 the SNMP notification will never be generated." 889 REFERENCE 890 "RFC3036, LDP Specification, 891 Section 2.5.3 Session Initialization." 892 DEFVAL { 8 } 893 ::= { mplsLdpEntityEntry 11 } 895 mplsLdpEntityLabelDistMethod OBJECT-TYPE 896 SYNTAX MplsLabelDistributionMethod 897 MAX-ACCESS read-create 898 STATUS current 899 DESCRIPTION 900 "For any given LDP session, the method of 901 label distribution must be specified." 902 ::= { mplsLdpEntityEntry 12 } 904 mplsLdpEntityLabelRetentionMode OBJECT-TYPE 905 SYNTAX MplsRetentionMode 906 MAX-ACCESS read-create 907 STATUS current 908 DESCRIPTION 909 "The LDP Entity can be configured to use either 910 conservative or liberal label retention mode. 912 If the value of this object is conservative(1) 913 then advertized label mappings are retained 914 only if they will be used to forward packets, 915 i.e. if label came from a valid next hop. 917 If the value of this object is liberal(2) 918 then all advertized label mappings are retained 919 whether they are from a valid next hop or not." 920 ::= { mplsLdpEntityEntry 13 } 922 mplsLdpEntityPathVectorLimit OBJECT-TYPE 923 SYNTAX Integer32 (0..255) 924 MAX-ACCESS read-create 925 STATUS current 926 DESCRIPTION 927 "If the value of this object is 0 (zero) then 928 Loop Dection for Path Vectors is disabled. 930 Otherwise, if this object has a value greater than 931 zero, then Loop Dection for Path Vectors is enabled, 932 and the Path Vector Limit is this value. 933 Also, the value of the object, 934 'mplsLdpLsrLoopDetectionCapable', must be set to 935 either 'pathVector(4)' or 'hopCountAndPathVector(5)', 936 if this object has a value greater than 0 (zero), 937 otherwise it is ignored." 938 REFERENCE 939 "RFC3036, LDP Specification, Section 2.8 Loop Dection, 940 Section 3.4.5 Path Vector TLV." 941 ::= { mplsLdpEntityEntry 14 } 943 mplsLdpEntityHopCountLimit OBJECT-TYPE 944 SYNTAX Integer32 (0..255) 945 MAX-ACCESS read-create 946 STATUS current 947 DESCRIPTION 948 "If the value of this object is 0 (zero), 949 then Loop Detection using Hop Counters is 950 disabled. 952 If the value of this object is greater than 953 0 (zero) then Loop Detection using Hop 954 Counters is enabled, and this object 955 specifies this Entity's maximum allowable 956 value for the Hop Count. 957 Also, the value of the object 958 mplsLdpLsrLoopDetectionCapable must be set 959 to either 'hopCount(3)' or 960 'hopCountAndPathVector(5)' if this object 961 has a value greater than 0 (zero), otherwise 962 it is ignored." 963 DEFVAL { 0 } 964 ::= { mplsLdpEntityEntry 15 } 966 mplsLdpEntityTransportAddrKind OBJECT-TYPE 967 SYNTAX INTEGER { 968 interface(1), 969 loopback(2) 970 } 971 MAX-ACCESS read-create 972 STATUS current 973 DESCRIPTION 974 "This specifies whether the loopback or interface 975 address is to be used as the transport address 976 in the transport address TLV of the 977 hello message. 979 If the value is interface(1), then the IP 980 address of the interface from which hello 981 messages are sent is used as the transport 982 address in the hello message. 984 Otherwise, if the value is loopback(2), then the IP 985 address of the loopback interface is used as the 986 transport address in the hello message." 987 DEFVAL { loopback } 988 ::= { mplsLdpEntityEntry 16 } 990 mplsLdpEntityTargetPeer OBJECT-TYPE 991 SYNTAX TruthValue 992 MAX-ACCESS read-create 993 STATUS current 994 DESCRIPTION 995 "If this LDP entity uses targeted peer then set 996 this to true." 997 DEFVAL { false } 998 ::= { mplsLdpEntityEntry 17 } 1000 mplsLdpEntityTargetPeerAddrType OBJECT-TYPE 1001 SYNTAX InetAddressType 1002 MAX-ACCESS read-create 1003 STATUS current 1004 DESCRIPTION 1005 "The type of the internetwork layer address used for 1006 the Extended Discovery. This object indicates how 1007 the value of mplsLdpEntityTargetPeerAddr is to 1008 be interpreted." 1009 ::= { mplsLdpEntityEntry 18 } 1011 mplsLdpEntityTargetPeerAddr OBJECT-TYPE 1012 SYNTAX InetAddress 1013 MAX-ACCESS read-create 1014 STATUS current 1015 DESCRIPTION 1016 "The value of the internetwork layer address used for 1017 the Extended Discovery." 1018 ::= { mplsLdpEntityEntry 19 } 1020 mplsLdpEntityLabelType OBJECT-TYPE 1021 SYNTAX MplsLdpLabelType 1022 MAX-ACCESS read-create 1023 STATUS current 1024 DESCRIPTION 1025 "Specifies the optional parameters for the LDP 1026 Initialization Message. If the value is generic(1) 1027 then no optional parameters will be sent in 1028 the LDP Initialization message associated with 1029 this Entity. 1031 If the value is atmParameters(2) then 1032 a row must be created in the mplsLdpEntityAtmParms 1033 Table, which corresponds to this entry. 1035 If the value is frameRelayParameters(3) then 1036 a row must be created in the mplsLdpEntityFrameRelayParms 1037 Table, which corresponds to this entry." 1038 REFERENCE 1039 "RFC3036, LDP Specification, Section 3.5.3., 1040 Initialization Message." 1041 ::= { mplsLdpEntityEntry 20 } 1043 mplsLdpEntityDiscontinuityTime OBJECT-TYPE 1044 SYNTAX TimeStamp 1045 MAX-ACCESS read-only 1046 STATUS current 1047 DESCRIPTION 1048 "The value of sysUpTime on the most recent occasion 1049 at which any one or more of this entity's counters 1050 suffered a discontinuity. The relevant counters are the 1051 specific instances associated with this entity of 1052 any Counter32, or Counter64 object contained 1053 in the 'mplsLdpEntityStatsTable'. If no such 1054 discontinuities have occurred since the last 1055 re-initialization of the local management 1056 subsystem, then this object contains a zero 1057 value." 1058 ::= { mplsLdpEntityEntry 21 } 1060 mplsLdpEntityStorageType OBJECT-TYPE 1061 SYNTAX StorageType 1062 MAX-ACCESS read-create 1063 STATUS current 1064 DESCRIPTION 1065 "The storage type for this conceptual row. 1066 Conceptual rows having the value 'permanent(4)' 1067 need not allow write-access to any columnar 1068 objects in the row." 1069 DEFVAL{ nonVolatile } 1070 ::= { mplsLdpEntityEntry 22 } 1072 mplsLdpEntityRowStatus OBJECT-TYPE 1073 SYNTAX RowStatus 1074 MAX-ACCESS read-create 1075 STATUS current 1076 DESCRIPTION 1077 "The status of this conceptual row. All writable 1078 objects in this row may be modified at any 1079 time, however, as described in detail in 1080 the section entitled, 'Changing Values After 1081 Session Establishment', and again described 1082 in the DESCRIPTION clause of the 1083 mplsLdpEntityAdminStatus object, if a session 1084 has been initiated with a Peer, changing objects 1085 in this table will wreak havoc with the session 1086 and interrupt traffic. To repeat again: 1087 the recommended procedure is to 1088 set the mplsLdpEntityAdminStatus to down, thereby 1089 explicitly causing a session to be torn down. Then, 1090 change objects in this entry, then set 1091 the mplsLdpEntityAdminStatus to enable, 1092 which enables a new session to be initiated." 1093 ::= { mplsLdpEntityEntry 23 } 1095 -- 1096 -- The MPLS LDP Entity Statistics Table 1097 -- 1099 mplsLdpEntityStatsTable OBJECT-TYPE 1100 SYNTAX SEQUENCE OF MplsLdpEntityStatsEntry 1101 MAX-ACCESS not-accessible 1102 STATUS current 1103 DESCRIPTION 1104 "This table is a read-only table which augments 1105 the mplsLdpEntityTable. The purpose of this 1106 table is to keep statistical information about 1107 the LDP Entities on the LSR." 1108 ::= { mplsLdpEntityObjects 4 } 1110 mplsLdpEntityStatsEntry OBJECT-TYPE 1111 SYNTAX MplsLdpEntityStatsEntry 1112 MAX-ACCESS not-accessible 1113 STATUS current 1114 DESCRIPTION 1115 "A row in this table contains statistical information 1116 about an LDP Entity. Some counters contained in a 1117 row are for fatal errors received during a former 1118 LDP Session associated with this entry. For example, 1119 an Ldp Pdu received on a TCP connection during an 1120 LDP Session contains a fatal error. That 1121 error is counted here, because the 1122 session is terminated. 1124 If the error is NOT fatal (i.e. and the Session 1125 remains), then the error is counted in the 1126 mplsLdpSesStatsEntry." 1127 AUGMENTS { mplsLdpEntityEntry } 1128 ::= { mplsLdpEntityStatsTable 1 } 1130 MplsLdpEntityStatsEntry ::= SEQUENCE { 1131 mplsLdpEntityStatsSessionAttempts Counter32, 1132 mplsLdpEntityStatsSessionRejectedNoHelloErrors Counter32, 1133 mplsLdpEntityStatsSessionRejectedAdErrors Counter32, 1134 mplsLdpEntityStatsSessionRejectedMaxPduErrors Counter32, 1135 mplsLdpEntityStatsSessionRejectedLRErrors Counter32, 1136 mplsLdpEntityStatsBadLdpIdentifierErrors Counter32, 1137 mplsLdpEntityStatsBadPduLengthErrors Counter32, 1138 mplsLdpEntityStatsBadMessageLengthErrors Counter32, 1139 mplsLdpEntityStatsBadTlvLengthErrors Counter32, 1140 mplsLdpEntityStatsMalformedTlvValueErrors Counter32, 1141 mplsLdpEntityStatsKeepAliveTimerExpErrors Counter32, 1142 mplsLdpEntityStatsShutdownReceivedNotifications Counter32, 1143 mplsLdpEntityStatsShutdownSentNotifications Counter32 1144 } 1146 mplsLdpEntityStatsSessionAttempts OBJECT-TYPE 1147 SYNTAX Counter32 1148 MAX-ACCESS read-only 1149 STATUS current 1150 DESCRIPTION 1151 "A count of the total attempted sessions for 1152 this LDP Entity. 1154 Discontinuities in the value of this counter can occur 1155 at re-initialization of the management system, and at 1156 other times as indicated by the value of 1157 mplsLdpEntityDiscontinuityTime." 1158 ::= { mplsLdpEntityStatsEntry 1 } 1160 mplsLdpEntityStatsSessionRejectedNoHelloErrors OBJECT-TYPE 1161 SYNTAX Counter32 1162 MAX-ACCESS read-only 1163 STATUS current 1164 DESCRIPTION 1165 "A count of the Session Rejected/No Hello Error 1166 Notification Messages sent or received by 1167 this LDP Entity. 1169 Discontinuities in the value of this counter can occur 1170 at re-initialization of the management system, and at 1171 other times as indicated by the value of 1172 mplsLdpEntityDiscontinuityTime." 1173 ::= { mplsLdpEntityStatsEntry 2 } 1175 mplsLdpEntityStatsSessionRejectedAdErrors OBJECT-TYPE 1176 SYNTAX Counter32 1177 MAX-ACCESS read-only 1178 STATUS current 1179 DESCRIPTION 1180 "A count of the Session Rejected/Parameters 1181 Advertisement Mode Error Notification Messages sent 1182 or received by this LDP Entity. 1184 Discontinuities in the value of this counter can occur 1185 at re-initialization of the management system, and at 1186 other times as indicated by the value of 1187 mplsLdpEntityDiscontinuityTime." 1188 ::= { mplsLdpEntityStatsEntry 3 } 1190 mplsLdpEntityStatsSessionRejectedMaxPduErrors OBJECT-TYPE 1191 SYNTAX Counter32 1192 MAX-ACCESS read-only 1193 STATUS current 1194 DESCRIPTION 1195 "A count of the Session Rejected/Parameters 1196 Max Pdu Length Error Notification Messages sent 1197 or received by this LDP Entity. 1199 Discontinuities in the value of this counter can occur 1200 at re-initialization of the management system, and at 1201 other times as indicated by the value of 1202 mplsLdpEntityDiscontinuityTime." 1203 ::= { mplsLdpEntityStatsEntry 4 } 1205 mplsLdpEntityStatsSessionRejectedLRErrors OBJECT-TYPE 1206 SYNTAX Counter32 1207 MAX-ACCESS read-only 1208 STATUS current 1209 DESCRIPTION 1210 "A count of the Session Rejected/Parameters 1211 Label Range Notification Messages sent 1212 or received by this LDP Entity. 1214 Discontinuities in the value of this counter can occur 1215 at re-initialization of the management system, and at 1216 other times as indicated by the value of 1217 mplsLdpEntityDiscontinuityTime." 1218 ::= { mplsLdpEntityStatsEntry 5 } 1220 mplsLdpEntityStatsBadLdpIdentifierErrors OBJECT-TYPE 1221 SYNTAX Counter32 1222 MAX-ACCESS read-only 1223 STATUS current 1224 DESCRIPTION 1225 "This object counts the number of Bad LDP Identifier 1226 Fatal Errors detected by the session(s) 1227 (past and present) associated with this LDP Entity. 1229 Discontinuities in the value of this counter can occur 1230 at re-initialization of the management system, and at 1231 other times as indicated by the value of 1232 mplsLdpEntityDiscontinuityTime." 1233 REFERENCE 1234 "RFC3036, LDP Specification, Section 3.5.1.2." 1235 ::= { mplsLdpEntityStatsEntry 6 } 1237 mplsLdpEntityStatsBadPduLengthErrors OBJECT-TYPE 1238 SYNTAX Counter32 1239 MAX-ACCESS read-only 1240 STATUS current 1241 DESCRIPTION 1242 "This object counts the number of Bad Pdu Length 1243 Fatal Errors detected by the session(s) 1244 (past and present) associated with this LDP Entity. 1246 Discontinuities in the value of this counter can occur 1247 at re-initialization of the management system, and at 1248 other times as indicated by the value of 1249 mplsLdpEntityDiscontinuityTime." 1250 REFERENCE 1251 "RFC3036, LDP Specification, Section 3.5.1.2." 1252 ::= { mplsLdpEntityStatsEntry 7 } 1254 mplsLdpEntityStatsBadMessageLengthErrors OBJECT-TYPE 1255 SYNTAX Counter32 1256 MAX-ACCESS read-only 1257 STATUS current 1258 DESCRIPTION 1259 "This object counts the number of Bad Message 1260 Length Fatal Errors detected by the session(s) 1261 (past and present) associated with this LDP Entity. 1263 Discontinuities in the value of this counter can occur 1264 at re-initialization of the management system, and at 1265 other times as indicated by the value of 1266 mplsLdpEntityDiscontinuityTime." 1267 REFERENCE 1268 "RFC3036, LDP Specification, Section 3.5.1.2." 1269 ::= { mplsLdpEntityStatsEntry 8 } 1271 mplsLdpEntityStatsBadTlvLengthErrors OBJECT-TYPE 1272 SYNTAX Counter32 1273 MAX-ACCESS read-only 1274 STATUS current 1275 DESCRIPTION 1276 "This object counts the number of Bad TLV 1277 Length Fatal Errors detected by the session(s) 1278 (past and present) associated with this LDP Entity. 1280 Discontinuities in the value of this counter can occur 1281 at re-initialization of the management system, and at 1282 other times as indicated by the value of 1283 mplsLdpEntityDiscontinuityTime." 1284 REFERENCE 1285 "RFC3036, LDP Specification, Section 3.5.1.2." 1286 ::= { mplsLdpEntityStatsEntry 9 } 1288 mplsLdpEntityStatsMalformedTlvValueErrors OBJECT-TYPE 1289 SYNTAX Counter32 1290 MAX-ACCESS read-only 1291 STATUS current 1292 DESCRIPTION 1293 "This object counts the number of Malformed TLV 1294 Value Fatal Errors detected by the session(s) 1295 (past and present) associated with this 1296 LDP Entity. 1298 Discontinuities in the value of this counter can occur 1299 at re-initialization of the management system, and at 1300 other times as indicated by the value of 1301 mplsLdpEntityDiscontinuityTime." 1302 REFERENCE 1303 "RFC3036, LDP Specification, Section 3.5.1.2." 1304 ::= { mplsLdpEntityStatsEntry 10 } 1306 mplsLdpEntityStatsKeepAliveTimerExpErrors OBJECT-TYPE 1307 SYNTAX Counter32 1308 MAX-ACCESS read-only 1309 STATUS current 1310 DESCRIPTION 1311 "This object counts the number of Session Keep Alive 1312 Timer Expired Errors detected by the session(s) 1313 (past and present) associated with this LDP Entity. 1315 Discontinuities in the value of this counter can occur 1316 at re-initialization of the management system, and at 1317 other times as indicated by the value of 1318 mplsLdpEntityDiscontinuityTime." 1319 REFERENCE 1320 "RFC3036, LDP Specification, Section 3.5.1.2." 1321 ::= { mplsLdpEntityStatsEntry 11 } 1323 mplsLdpEntityStatsShutdownReceivedNotifications OBJECT-TYPE 1324 SYNTAX Counter32 1325 MAX-ACCESS read-only 1326 STATUS current 1327 DESCRIPTION 1328 "This object counts the number of Shutdown Notfications 1329 received related to session(s) (past and present) 1330 associated with this LDP Entity. 1332 Discontinuities in the value of this counter can occur 1333 at re-initialization of the management system, and at 1334 other times as indicated by the value of 1335 mplsLdpEntityDiscontinuityTime." 1336 ::= { mplsLdpEntityStatsEntry 12 } 1338 mplsLdpEntityStatsShutdownSentNotifications OBJECT-TYPE 1339 SYNTAX Counter32 1340 MAX-ACCESS read-only 1341 STATUS current 1342 DESCRIPTION 1343 "This object counts the number of Shutdown Notfications 1344 sent related to session(s) (past and present) associated 1345 with this LDP Entity. 1347 Discontinuities in the value of this counter can occur 1348 at re-initialization of the management system, and at 1349 other times as indicated by the value of 1350 mplsLdpEntityDiscontinuityTime." 1351 ::= { mplsLdpEntityStatsEntry 13 } 1353 -- 1354 -- The MPLS LDP Peer Table 1355 -- 1357 mplsLdpSessionObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 3 } 1359 mplsLdpPeerLastChange OBJECT-TYPE 1360 SYNTAX TimeStamp 1361 MAX-ACCESS read-only 1362 STATUS current 1363 DESCRIPTION 1364 "The value of sysUpTime at the time of the most 1365 recent addition or deletion to/from the 1366 mplsLdpPeerTable/mplsLdpSessionTable." 1367 ::= { mplsLdpSessionObjects 1 } 1369 mplsLdpPeerTable OBJECT-TYPE 1370 SYNTAX SEQUENCE OF MplsLdpPeerEntry 1371 MAX-ACCESS not-accessible 1372 STATUS current 1373 DESCRIPTION 1374 "Information about LDP peers known by Entities in 1375 the mplsLdpEntityTable. The information in this table 1376 is based on information from the Entity-Peer interaction 1377 during session initialization but is not appropriate 1378 for the mplsLdpSessionTable, because objects in this 1379 table may or may not be used in session establishment." 1380 ::= { mplsLdpSessionObjects 2 } 1382 mplsLdpPeerEntry OBJECT-TYPE 1383 SYNTAX MplsLdpPeerEntry 1384 MAX-ACCESS not-accessible 1385 STATUS current 1386 DESCRIPTION 1387 "Information about a single Peer which is related 1388 to a Session. This table is augmented by 1389 the mplsLdpSessionTable." 1390 INDEX { mplsLdpEntityLdpId, 1391 mplsLdpEntityIndex, 1392 mplsLdpPeerLdpId } 1393 ::= { mplsLdpPeerTable 1 } 1395 MplsLdpPeerEntry ::= SEQUENCE { 1396 mplsLdpPeerLdpId MplsLdpIdentifier, 1397 mplsLdpPeerLabelDistMethod MplsLabelDistributionMethod, 1398 mplsLdpPeerPathVectorLimit Integer32, 1399 mplsLdpPeerTransportAddrType InetAddressType, 1400 mplsLdpPeerTransportAddr InetAddress 1401 } 1403 mplsLdpPeerLdpId OBJECT-TYPE 1404 SYNTAX MplsLdpIdentifier 1405 MAX-ACCESS not-accessible 1406 STATUS current 1407 DESCRIPTION 1408 "The LDP identifier of this LDP Peer." 1409 ::= { mplsLdpPeerEntry 1 } 1411 mplsLdpPeerLabelDistMethod OBJECT-TYPE 1412 SYNTAX MplsLabelDistributionMethod 1413 MAX-ACCESS read-only 1414 STATUS current 1415 DESCRIPTION 1416 "For any given LDP session, the method of 1417 label distribution must be specified." 1418 ::= { mplsLdpPeerEntry 2 } 1420 mplsLdpPeerPathVectorLimit OBJECT-TYPE 1421 SYNTAX Integer32 (0..255) 1422 MAX-ACCESS read-only 1423 STATUS current 1424 DESCRIPTION 1425 "If the value of this object is 0 (zero) then 1426 Loop Dection for Path Vectors for this Peer 1427 is disabled. 1429 Otherwise, if this object has a value greater than 1430 zero, then Loop Dection for Path Vectors for this 1431 Peer is enabled and the Path Vector Limit is this value." 1432 REFERENCE 1433 "RFC3036, LDP Specification, Section 2.8 Loop Dection, 1434 Section 3.4.5 Path Vector TLV." 1435 ::= { mplsLdpPeerEntry 3 } 1437 mplsLdpPeerTransportAddrType OBJECT-TYPE 1438 SYNTAX InetAddressType 1439 MAX-ACCESS read-only 1440 STATUS current 1441 DESCRIPTION 1442 "The type of the Internet address for the 1443 mplsLdpPeerTransportAddr object. The LDP 1444 specification describes this as being either 1445 an IPv4 Transport Address or IPv6 Transport 1446 Address which is ued in opening the LDP session's 1447 TCP connection, or if the optional TLV is not 1448 present, then this is the IPv4/IPv6 source 1449 address for the UPD packet carrying the Hellos." 1450 REFERENCE 1451 "RFC3036, LDP Specification, Section 2.5.2 1452 Transport Connection Establishment and 1453 Section 3.5.2.1 Hello Message Procedures." 1454 ::= { mplsLdpPeerEntry 4 } 1456 mplsLdpPeerTransportAddr OBJECT-TYPE 1457 SYNTAX InetAddress 1458 MAX-ACCESS read-only 1459 STATUS current 1460 DESCRIPTION 1461 "The Internet address advertised by the peer 1462 in the hello message or the Hello source address. 1464 The type of this address is determined by the 1465 value of the mplsLdpPeerTransportAddrType 1466 object." 1467 REFERENCE 1468 "RFC3036, LDP Specification, Section 2.5.2 1469 Transport Connection Establishment and 1470 Section 3.5.2.1 Hello Message Procedures." 1471 ::= { mplsLdpPeerEntry 5 } 1473 -- 1474 -- The MPLS LDP Sessions Table 1475 -- 1477 mplsLdpSessionTable OBJECT-TYPE 1478 SYNTAX SEQUENCE OF MplsLdpSessionEntry 1479 MAX-ACCESS not-accessible 1480 STATUS current 1481 DESCRIPTION 1482 "A table of Sessions between the LDP Entities and 1483 LDP Peers. Each row represents a single session." 1484 ::= { mplsLdpSessionObjects 3 } 1486 mplsLdpSessionEntry OBJECT-TYPE 1487 SYNTAX MplsLdpSessionEntry 1488 MAX-ACCESS not-accessible 1489 STATUS current 1490 DESCRIPTION 1491 "An entry in this table represents information on a 1492 single session between an LDP Entity and LDP Peer. 1493 The information contained in a row is read-only. 1495 Please note: the Path Vector Limit for the 1496 Session is the value which is configured in 1497 the corresponding mplsLdpEntityEntry. The 1498 Peer's Path Vector Limit is in the 1499 mplsLdpPeerPathVectorLimit object in the 1500 mplsLdpPeerTable. 1502 Values which may differ from those configured are 1503 noted in the objects of this table, the 1504 mplsLdpAtmSessionTable and the 1505 mplsLdpFrameRelaySessionTable. A value will 1506 differ if it was negotiated between the 1507 Entity and the Peer. Values may or may not 1508 be negotiated. For example, if the values 1509 are the same then no negotiation takes place. 1510 If they are negotiated, then they may differ." 1511 AUGMENTS { mplsLdpPeerEntry } 1512 ::= { mplsLdpSessionTable 1 } 1514 MplsLdpSessionEntry ::= SEQUENCE { 1515 mplsLdpSessionStateLastChange TimeStamp, 1516 mplsLdpSessionState INTEGER, 1517 mplsLdpSessionRole INTEGER, 1518 mplsLdpSessionProtocolVersion Unsigned32, 1519 mplsLdpSessionKeepAliveHoldTimeRem TimeInterval, 1520 mplsLdpSessionKeepAliveTime Unsigned32, 1521 mplsLdpSessionMaxPduLength Unsigned32, 1522 mplsLdpSessionDiscontinuityTime TimeStamp 1523 } 1525 mplsLdpSessionStateLastChange OBJECT-TYPE 1526 SYNTAX TimeStamp 1527 MAX-ACCESS read-only 1528 STATUS current 1529 DESCRIPTION 1530 "The value of sysUpTime at the time this Session entered 1531 its current state as denoted by the mplsLdpSessionState object." 1532 ::= { mplsLdpSessionEntry 1 } 1534 mplsLdpSessionState OBJECT-TYPE 1535 SYNTAX INTEGER { 1536 nonexistent(1), 1537 initialized(2), 1538 openrec(3), 1539 opensent(4), 1540 operational(5) 1541 } 1542 MAX-ACCESS read-only 1543 STATUS current 1544 DESCRIPTION 1545 "The current state of the session, all of the 1546 states 1 to 5 are based on the state machine for 1547 session negotiation behavior." 1548 REFERENCE 1549 "RFC3036, LDP Specification, Section 2.5.4, 1550 Initialization State Machine." 1551 ::= { mplsLdpSessionEntry 2 } 1553 mplsLdpSessionRole OBJECT-TYPE 1554 SYNTAX INTEGER { 1555 unknown(1), 1556 active(2), 1557 passive(3) 1558 } 1559 MAX-ACCESS read-only 1560 STATUS current 1561 DESCRIPTION 1562 "During session establishment the LSR/LER takes either the 1563 active role or the passive role based on address 1564 comparisons. This object indicates whether this LSR/LER 1565 was behaving in an active role or passive role during 1566 this session's establishment. 1568 The value of unknown(1), indicates that the role is not 1569 able to be determined at the present time." 1570 REFERENCE 1571 "RFC3036, LDP Specification, Section 2.5.3., 1572 Session Initialization" 1573 ::= { mplsLdpSessionEntry 3 } 1575 mplsLdpSessionProtocolVersion OBJECT-TYPE 1576 SYNTAX Unsigned32(1..65535) 1577 MAX-ACCESS read-only 1578 STATUS current 1579 DESCRIPTION 1580 "The version of the LDP Protocol which 1581 this session is using. This is the version of 1582 the LDP protocol which has been negotiated during 1583 session initialization." 1584 REFERENCE 1585 "RFC3036, LDP Specification, Section 3.5.3, 1586 Initialization Message." 1587 ::= { mplsLdpSessionEntry 4 } 1589 mplsLdpSessionKeepAliveHoldTimeRem OBJECT-TYPE 1590 SYNTAX TimeInterval 1591 MAX-ACCESS read-only 1592 STATUS current 1593 DESCRIPTION 1594 "The keep alive hold time remaining for 1595 this session." 1596 ::= { mplsLdpSessionEntry 5 } 1598 mplsLdpSessionKeepAliveTime OBJECT-TYPE 1599 SYNTAX Unsigned32 (1..65535) 1600 UNITS "seconds" 1601 MAX-ACCESS read-only 1602 STATUS current 1603 DESCRIPTION 1604 "The negotiated KeepAlive Time which 1605 represents the amount of seconds between 1606 keep alive messages. The 1607 mplsLdpEntityKeepAliveHoldTimer 1608 related to this Session is the 1609 value that was proposed as the 1610 KeepAlive Time for this session. 1612 This value is negotiated during 1613 session initialization between 1614 the entity's proposed value 1615 (i.e. the value configured in 1616 mplsLdpEntityKeepAliveHoldTimer) 1617 and the peer's proposed 1618 KeepAlive Hold Timer value. 1619 This value is the smaller 1620 of the two proposed values." 1621 REFERENCE 1622 "RFC3036, LDP Specification, Section 3.5.3, 1623 Initialization Message." 1624 ::= { mplsLdpSessionEntry 6 } 1626 mplsLdpSessionMaxPduLength OBJECT-TYPE 1627 SYNTAX Unsigned32 (1..65535) 1628 UNITS "octets" 1629 MAX-ACCESS read-only 1630 STATUS current 1631 DESCRIPTION 1632 "The value of maximum allowable length for LDP PDUs for 1633 this session. This value may have been negotiated during 1634 the Session Initialization. This object is related to 1635 the mplsLdpEntityMaxPduLength object. The 1636 mplsLdpEntityMaxPduLength object specifies the requested 1637 LDP PDU length, and this object reflects the negotiated 1638 LDP PDU length between the Entity and 1639 the Peer." 1640 REFERENCE 1641 "RFC3036, LDP Specification, Section 3.5.3, 1642 Initialization Message." 1643 ::= { mplsLdpSessionEntry 7 } 1645 mplsLdpSessionDiscontinuityTime OBJECT-TYPE 1646 SYNTAX TimeStamp 1647 MAX-ACCESS read-only 1648 STATUS current 1649 DESCRIPTION 1650 "The value of sysUpTime on the most recent occasion at 1651 which any one or more of this session's counters 1652 suffered a discontinuity. The relevant counters are 1653 the specific instances associated with this session 1654 of any Counter32 or Counter64 object contained in the 1655 mplsLdpSessionStatsTable. 1657 The initial value of this object is the value of 1658 sysUpTime when the entry was created in this table. 1660 Also, a command generator can distinguish when a session 1661 between a given Entity and Peer goes away and a new 1662 session is established. This value would change and 1663 thus indicate to the command generator that this is a 1664 different session." 1665 ::= { mplsLdpSessionEntry 8 } 1667 -- 1668 -- The MPLS LDP Session Statistics Table 1669 -- 1670 mplsLdpSessionStatsTable OBJECT-TYPE 1671 SYNTAX SEQUENCE OF MplsLdpSessionStatsEntry 1672 MAX-ACCESS not-accessible 1673 STATUS current 1674 DESCRIPTION 1675 "A table of statistics for Sessions between 1676 LDP Entities and LDP Peers." 1677 ::= { mplsLdpSessionObjects 4 } 1679 mplsLdpSessionStatsEntry OBJECT-TYPE 1680 SYNTAX MplsLdpSessionStatsEntry 1681 MAX-ACCESS not-accessible 1682 STATUS current 1683 DESCRIPTION 1684 "An entry in this table represents statistical 1685 information on a single session between an LDP 1686 Entity and LDP Peer." 1687 AUGMENTS { mplsLdpPeerEntry } 1688 ::= { mplsLdpSessionStatsTable 1 } 1690 MplsLdpSessionStatsEntry ::= SEQUENCE { 1691 mplsLdpSessionStatsUnknownMesTypeErrors Counter32, 1692 mplsLdpSessionStatsUnknownTlvErrors Counter32 1693 } 1695 mplsLdpSessionStatsUnknownMesTypeErrors OBJECT-TYPE 1696 SYNTAX Counter32 1697 MAX-ACCESS read-only 1698 STATUS current 1699 DESCRIPTION 1700 "This object counts the number of Unknown Message Type 1701 Errors detected during this session. 1703 Discontinuities in the value of this counter can occur 1704 at re-initialization of the management system, and at 1705 other times as indicated by the value of 1706 mplsLdpSessionDiscontinuityTime." 1707 ::= { mplsLdpSessionStatsEntry 1 } 1709 mplsLdpSessionStatsUnknownTlvErrors OBJECT-TYPE 1710 SYNTAX Counter32 1711 MAX-ACCESS read-only 1712 STATUS current 1713 DESCRIPTION 1714 "This object counts the number of Unknown TLV Errors 1715 detected during this session. 1717 Discontinuities in the value of this counter can occur 1718 at re-initialization of the management system, and at 1719 other times as indicated by the value of 1720 mplsLdpSessionDiscontinuityTime." 1721 ::= { mplsLdpSessionStatsEntry 2 } 1723 -- 1724 -- The MPLS LDP Hello Adjacency Table 1725 -- 1727 mplsLdpHelloAdjacencyObjects OBJECT IDENTIFIER ::= 1728 { mplsLdpSessionObjects 5 } 1730 mplsLdpHelloAdjacencyTable OBJECT-TYPE 1731 SYNTAX SEQUENCE OF MplsLdpHelloAdjacencyEntry 1732 MAX-ACCESS not-accessible 1733 STATUS current 1734 DESCRIPTION 1735 "A table of Hello Adjacencies for Sessions." 1736 ::= { mplsLdpHelloAdjacencyObjects 1 } 1738 mplsLdpHelloAdjacencyEntry OBJECT-TYPE 1739 SYNTAX MplsLdpHelloAdjacencyEntry 1740 MAX-ACCESS not-accessible 1741 STATUS current 1742 DESCRIPTION 1743 "Each row represents a single LDP Hello Adjacency. 1744 An LDP Session can have one or more Hello adjacencies." 1745 INDEX { mplsLdpEntityLdpId, 1746 mplsLdpEntityIndex, 1747 mplsLdpPeerLdpId, 1748 mplsLdpHelloAdjacencyIndex } 1749 ::= { mplsLdpHelloAdjacencyTable 1 } 1751 MplsLdpHelloAdjacencyEntry ::= SEQUENCE { 1752 mplsLdpHelloAdjacencyIndex Unsigned32, 1753 mplsLdpHelloAdjacencyHoldTimeRem TimeInterval, 1754 mplsLdpHelloAdjacencyHoldTime Unsigned32, 1755 mplsLdpHelloAdjacencyType INTEGER 1756 } 1758 mplsLdpHelloAdjacencyIndex OBJECT-TYPE 1759 SYNTAX Unsigned32 (1..4294967295) 1760 MAX-ACCESS not-accessible 1761 STATUS current 1762 DESCRIPTION 1763 "An identifier for this specific adjacency." 1764 ::= { mplsLdpHelloAdjacencyEntry 1 } 1766 mplsLdpHelloAdjacencyHoldTimeRem OBJECT-TYPE 1767 SYNTAX TimeInterval 1768 UNITS "seconds" 1769 MAX-ACCESS read-only 1770 STATUS current 1771 DESCRIPTION 1772 "If the value of this object is 65535, 1773 this means that the hold time is infinite 1774 (i.e. wait forever). 1776 Otherwise, the time remaining for 1777 this Hello Adjacency to receive its 1778 next Hello message. 1780 This interval will change when the 'next' 1781 Hello message which corresponds to this 1782 Hello Adjacency is received unless it 1783 is infinite." 1784 ::= { mplsLdpHelloAdjacencyEntry 2 } 1786 mplsLdpHelloAdjacencyHoldTime OBJECT-TYPE 1787 SYNTAX Unsigned32 (0..65535) 1788 MAX-ACCESS read-only 1789 STATUS current 1790 DESCRIPTION 1791 "The Hello hold time which is negotiated between 1792 the Entity and the Peer. The entity associated 1793 with this Hello Adjacency issues a proposed 1794 Hello Hold Time value in the 1795 mplsLdpEntityHelloHoldTimer object. The peer 1796 also proposes a value and this object represents 1797 the negotiated value. 1799 A value of 0 means the default, 1800 which is 15 seconds for Link Hellos 1801 and 45 seconds for Targeted Hellos. 1802 A value of 65535 indicates an 1803 infinite hold time." 1804 REFERENCE 1805 "RFC3036, LDP Specification, Section 3.5.2 Hello Message" 1806 ::= { mplsLdpHelloAdjacencyEntry 3 } 1808 mplsLdpHelloAdjacencyType OBJECT-TYPE 1809 SYNTAX INTEGER { 1810 link(1), 1811 targeted(2) 1812 } 1813 MAX-ACCESS read-only 1814 STATUS current 1815 DESCRIPTION 1816 "This adjacency is the result of a 'link' 1817 hello if the value of this object is link(1). 1818 Otherwise, it is a result of a 'targeted' 1819 hello, targeted(2)." 1820 ::= { mplsLdpHelloAdjacencyEntry 4 } 1822 -- 1823 -- Session Label (LSP) Mapping to LSR MIB's In Segment LIB Information. 1824 -- 1826 -- 1827 -- NOTE: the next 2 tables map to the MPLS-LSR-MIB's MplsInSegmentTable 1828 -- and MplsOutSegmentTable. The cross-connect information is not 1829 -- represented here as it can be gleaned from the MPLS-LSR-MIB. 1830 -- 1832 mplsInSegmentLdpLspTable OBJECT-TYPE 1833 SYNTAX SEQUENCE OF MplsInSegmentLdpLspEntry 1834 MAX-ACCESS not-accessible 1835 STATUS current 1836 DESCRIPTION 1837 "A table of LDP LSP's which 1838 map to the InSegment Table in the 1839 the LSR MIB's." 1840 ::= { mplsLdpSessionObjects 6 } 1842 mplsInSegmentLdpLspEntry OBJECT-TYPE 1843 SYNTAX MplsInSegmentLdpLspEntry 1844 MAX-ACCESS not-accessible 1845 STATUS current 1846 DESCRIPTION 1847 "An entry in this table represents information on a 1848 single LDP LSP which is represented by 1849 a session's index triple (mplsLdpEntityLdpId, 1850 mplsLdpEntityIndex, mplsLdpPeerLdpId) AND the 1851 index tuple (mplsInSegmentLdpLspIfIndex, 1852 mplsInSegmentLdpLspLabel). 1854 The information contained in a row is read-only." 1855 INDEX { mplsLdpEntityLdpId, 1856 mplsLdpEntityIndex, 1857 mplsLdpPeerLdpId, 1858 mplsInSegmentLdpLspIfIndex, 1859 mplsInSegmentLdpLspLabel 1860 } 1861 ::= { mplsInSegmentLdpLspTable 1 } 1863 MplsInSegmentLdpLspEntry ::= SEQUENCE { 1864 mplsInSegmentLdpLspIfIndex InterfaceIndexOrZero, 1865 mplsInSegmentLdpLspLabel MplsLabel, 1866 mplsInSegmentLdpLspLabelType MplsLdpLabelType, 1867 mplsInSegmentLdpLspType MplsLspType 1868 } 1870 mplsInSegmentLdpLspIfIndex OBJECT-TYPE 1871 SYNTAX InterfaceIndexOrZero 1872 MAX-ACCESS not-accessible 1873 STATUS current 1874 DESCRIPTION 1875 "The ifIndex value associated with this LSP which has the 1876 same value as the mplsInSegmentIfIndex in the MPLS-LSR-MIB's 1877 mplsInSegmentTable." 1878 ::= { mplsInSegmentLdpLspEntry 1 } 1880 mplsInSegmentLdpLspLabel OBJECT-TYPE 1881 SYNTAX MplsLabel 1882 MAX-ACCESS not-accessible 1883 STATUS current 1884 DESCRIPTION 1885 "The LDP label for this LSP. This is also the same value 1886 as the mplsInSegmentLabel index in the MPLS-LSR-MIB's 1887 mplsInSegmentTable." 1888 ::= { mplsInSegmentLdpLspEntry 2 } 1890 mplsInSegmentLdpLspLabelType OBJECT-TYPE 1891 SYNTAX MplsLdpLabelType 1892 MAX-ACCESS read-only 1893 STATUS current 1894 DESCRIPTION 1895 "The Layer 2 Label Type." 1896 ::= { mplsInSegmentLdpLspEntry 3 } 1898 mplsInSegmentLdpLspType OBJECT-TYPE 1899 SYNTAX MplsLspType 1900 MAX-ACCESS read-only 1901 STATUS current 1902 DESCRIPTION 1903 "The type of LSP connection." 1904 ::= { mplsInSegmentLdpLspEntry 4 } 1906 -- 1907 -- Session Label (LSP) Mapping to LSR MIB's Out Segment LIB Information. 1908 -- 1910 mplsOutSegmentLdpLspTable OBJECT-TYPE 1911 SYNTAX SEQUENCE OF MplsOutSegmentLdpLspEntry 1912 MAX-ACCESS not-accessible 1913 STATUS current 1914 DESCRIPTION 1915 "A table of LDP LSP's which 1916 map to the mplsOutSegmentTable in the 1917 the LSR MIB." 1918 ::= { mplsLdpSessionObjects 7 } 1920 mplsOutSegmentLdpLspEntry OBJECT-TYPE 1921 SYNTAX MplsOutSegmentLdpLspEntry 1922 MAX-ACCESS not-accessible 1923 STATUS current 1924 DESCRIPTION 1925 "An entry in this table represents information on a 1926 single LDP LSP which is represented by 1927 a session's index triple (mplsLdpEntityLdpId, 1928 mplsLdpEntityIndex, mplsLdpPeerLdpId) AND the 1929 index tuple (mplsOutSegmentLdpLspIfIndex, 1930 mplsOutSegmentLdpLspLabel). 1932 The information contained in a row is read-only." 1933 INDEX { mplsLdpEntityLdpId, 1934 mplsLdpEntityIndex, 1935 mplsLdpPeerLdpId, 1936 mplsOutSegmentLdpLspIfIndex, 1937 mplsOutSegmentLdpLspLabel 1938 } 1939 ::= { mplsOutSegmentLdpLspTable 1 } 1941 MplsOutSegmentLdpLspEntry ::= SEQUENCE { 1942 mplsOutSegmentLdpLspIfIndex InterfaceIndexOrZero, 1943 mplsOutSegmentLdpLspLabel MplsLabel, 1944 mplsOutSegmentLdpLspLabelType MplsLdpLabelType, 1945 mplsOutSegmentLdpLspType MplsLspType 1946 } 1948 mplsOutSegmentLdpLspIfIndex OBJECT-TYPE 1949 SYNTAX InterfaceIndexOrZero 1950 MAX-ACCESS not-accessible 1951 STATUS current 1952 DESCRIPTION 1953 "The ifIndex value associated with this LSP which has the 1954 same value as the mplsOutSegmentIfIndex in the MPLS-LSR-MIB's 1955 mplsOutSegmentTable. NOTE: the value of zero represents 1956 the perPlatform label space." 1957 ::= { mplsOutSegmentLdpLspEntry 1 } 1959 mplsOutSegmentLdpLspLabel OBJECT-TYPE 1960 SYNTAX MplsLabel 1961 MAX-ACCESS not-accessible 1962 STATUS current 1963 DESCRIPTION 1964 "The LDP label for this LSP. This is also the same value 1965 as the mplsOutSegmentTopLabel in the MPLS-LSR-MIB's 1966 mplsOutSegmentTable." 1967 ::= { mplsOutSegmentLdpLspEntry 2 } 1969 mplsOutSegmentLdpLspLabelType OBJECT-TYPE 1970 SYNTAX MplsLdpLabelType 1971 MAX-ACCESS read-only 1972 STATUS current 1973 DESCRIPTION 1974 "The Layer 2 Label Type." 1975 ::= { mplsOutSegmentLdpLspEntry 3 } 1977 mplsOutSegmentLdpLspType OBJECT-TYPE 1978 SYNTAX MplsLspType 1979 MAX-ACCESS read-only 1980 STATUS current 1981 DESCRIPTION 1982 "The type of LSP connection." 1983 ::= { mplsOutSegmentLdpLspEntry 4 } 1985 -- 1986 -- Mpls FEC Table 1987 -- 1989 mplsFecObjects OBJECT IDENTIFIER ::= 1990 { mplsLdpSessionObjects 8 } 1992 mplsFecIndexNext OBJECT-TYPE 1993 SYNTAX IndexIntegerNextFree 1994 MAX-ACCESS read-only 1995 STATUS current 1996 DESCRIPTION 1997 "This object contains an appropriate value to 1998 be used for mplsFecIndex when creating 1999 entries in the mplsFecTable. The value 2000 0 indicates that no unassigned entries are 2001 available." 2002 ::= { mplsFecObjects 1 } 2004 mplsFecTable OBJECT-TYPE 2005 SYNTAX SEQUENCE OF MplsFecEntry 2006 MAX-ACCESS not-accessible 2007 STATUS current 2008 DESCRIPTION 2009 "This table represents the FEC 2010 (Forwarding Equivalence Class) 2011 Information associated with an LSP." 2012 ::= { mplsFecObjects 2 } 2014 mplsFecEntry OBJECT-TYPE 2015 SYNTAX MplsFecEntry 2016 MAX-ACCESS not-accessible 2017 STATUS current 2018 DESCRIPTION 2019 "Each row represents a single FEC Element." 2020 INDEX { mplsFecIndex } 2021 ::= { mplsFecTable 1 } 2023 MplsFecEntry ::= SEQUENCE { 2024 mplsFecIndex IndexInteger, 2025 mplsFecType INTEGER, 2026 mplsFecAddrPrefixLength InetAddressPrefixLength, 2027 mplsFecAddrFamily InetAddressType, 2028 mplsFecAddr InetAddress, 2029 mplsFecStorageType StorageType, 2030 mplsFecRowStatus RowStatus 2032 } 2034 mplsFecIndex OBJECT-TYPE 2035 SYNTAX IndexInteger 2036 MAX-ACCESS not-accessible 2037 STATUS current 2038 DESCRIPTION 2039 "The index which uniquely identifies this entry." 2040 ::= { mplsFecEntry 1 } 2042 mplsFecType OBJECT-TYPE 2043 SYNTAX INTEGER { 2044 prefix(1), 2045 hostAddress(2) 2046 } 2047 MAX-ACCESS read-create 2048 STATUS current 2049 DESCRIPTION 2050 "The type of the FEC. If the value of this object 2051 is 'prefix(1)' then the FEC type described by this 2052 row is for address prefixes. 2054 If the value of this object is 'hostAddress(2)' then 2055 the FEC type described by this row is a host address." 2056 REFERENCE 2057 "RFC3036, Section 3.4.1. FEC TLV." 2058 ::= { mplsFecEntry 2 } 2060 mplsFecAddrPrefixLength OBJECT-TYPE 2061 SYNTAX InetAddressPrefixLength 2062 MAX-ACCESS read-create 2063 STATUS current 2064 DESCRIPTION 2065 "If the value of the 'mplsFecType' is 'hostAddress(2)' 2066 then this object is undefined. 2068 If the value of 'mplsFecType' is 'prefix(1)' 2069 then the value of this object is the length in 2070 bits of the address prefix represented by 2071 'mplsFecAddr', or zero. If the value of this 2072 object is zero, this indicates that the 2073 prefix matches all addresses. In this case the 2074 prefix MUST also be zero (i.e. 'mplsFecAddr' will 2075 have the value of zero.)" 2076 REFERENCE 2077 "RFC3036, Section 3.4.1. FEC TLV." 2079 DEFVAL { 0 } 2080 ::= { mplsFecEntry 3 } 2082 mplsFecAddrFamily OBJECT-TYPE 2083 SYNTAX InetAddressType 2084 MAX-ACCESS read-create 2085 STATUS current 2086 DESCRIPTION 2087 "The value of this object is the type of the address. The 2088 type of the address should then be looked up in the 2089 ADDRESS FAMILY NUMBERS [RFC1700] for the corresponding entry 2090 there and this value should be encoded in the FEC TLV." 2091 REFERENCE 2092 "RFC3036, Section 3.4.1. FEC TLV." 2093 ::= { mplsFecEntry 4 } 2095 mplsFecAddr OBJECT-TYPE 2096 SYNTAX InetAddress 2097 MAX-ACCESS read-create 2098 STATUS current 2099 DESCRIPTION 2100 "The value of this object is the an address where the 2101 address type is specified by the 'mplsFecAddrFamily' object. 2103 This address is then used as either an address prefix, 2104 or as the host address as indicated by the 'mplsFecType' 2105 object. In other words, the FEC element is populated 2106 according to the Prefix FEC Element value encoding, or 2107 the Host Address FEC Element encoding." 2108 REFERENCE 2109 "RFC3036, Section 3.4.1 FEC TLV." 2110 ::= { mplsFecEntry 5 } 2112 mplsFecStorageType OBJECT-TYPE 2113 SYNTAX StorageType 2114 MAX-ACCESS read-create 2115 STATUS current 2116 DESCRIPTION 2117 "The storage type for this conceptual row. 2118 Conceptual rows having the value 'permanent(4)' 2119 need not allow write-access to any columnar 2120 objects in the row." 2121 DEFVAL { nonVolatile } 2122 ::= { mplsFecEntry 6 } 2124 mplsFecRowStatus OBJECT-TYPE 2125 SYNTAX RowStatus 2126 MAX-ACCESS read-create 2127 STATUS current 2128 DESCRIPTION 2129 "The status of this conceptual row. If the value of this 2130 object is 'active(1)', then none of the writable objects of 2131 this entry can be modified, except to set this object 2132 to 'destroy(6)'. 2134 NOTE: if this row is being referenced by any entry in the 2135 mplsLdpLspFecTable, then a request to destroy this row, will 2136 result in an inconsistentValue error." 2137 ::= { mplsFecEntry 7 } 2139 -- 2140 -- LDP LSP FEC Table 2141 -- 2143 mplsLdpLspFecTable OBJECT-TYPE 2144 SYNTAX SEQUENCE OF MplsLdpLspFecEntry 2145 MAX-ACCESS not-accessible 2146 STATUS current 2147 DESCRIPTION 2148 "A table which shows the relationship between 2149 LDP LSP's and FECs. Each row represents 2150 a single LSP to FEC association." 2151 ::= { mplsLdpSessionObjects 9 } 2153 mplsLdpLspFecEntry OBJECT-TYPE 2154 SYNTAX MplsLdpLspFecEntry 2155 MAX-ACCESS not-accessible 2156 STATUS current 2157 DESCRIPTION 2158 "An entry represents a LDP LSP 2159 to FEC association." 2160 INDEX { mplsLdpEntityLdpId, 2161 mplsLdpEntityIndex, 2162 mplsLdpPeerLdpId, 2163 mplsLdpLspFecSegment, 2164 mplsLdpLspFecIfIndex, 2165 mplsLdpLspFecLabel, 2166 mplsLdpLspFecIndex 2167 } 2168 ::= { mplsLdpLspFecTable 1 } 2170 MplsLdpLspFecEntry ::= SEQUENCE { 2171 mplsLdpLspFecSegment INTEGER, 2172 mplsLdpLspFecIfIndex InterfaceIndexOrZero, 2173 mplsLdpLspFecLabel MplsLabel, 2174 mplsLdpLspFecIndex IndexInteger, 2175 mplsLdpLspFecOperStatus INTEGER, 2176 mplsLdpLspFecLastChange TimeStamp, 2177 mplsLdpLspFecStorageType StorageType, 2178 mplsLdpLspFecRowStatus RowStatus 2179 } 2181 mplsLdpLspFecSegment OBJECT-TYPE 2182 SYNTAX INTEGER { 2183 inSegment(1), 2184 outSegment(2) 2185 } 2186 MAX-ACCESS not-accessible 2187 STATUS current 2188 DESCRIPTION 2189 "If the value is inSegment(1), then this 2190 indicates that the following indices, 2191 mplsLdpLspFecIfIndex and mplsLdpLspFecLabel 2192 contain the same values as the mplsInSegmentLdpLspIfIndex 2193 and the mplsInSegmentLdpLspLabel. 2195 Otherwise, if the value of this object is 2196 outSegment(2), then this 2197 indicates that the following indices, 2198 mplsLdpLspFecIfIndex and mplsLdpLspFecLabel 2199 contain the same values as the mplsOutSegmentLdpLspIfIndex 2200 and the mplsOutSegmentLdpLspLabel." 2201 ::= { mplsLdpLspFecEntry 1 } 2203 mplsLdpLspFecIfIndex OBJECT-TYPE 2204 SYNTAX InterfaceIndexOrZero 2205 MAX-ACCESS not-accessible 2206 STATUS current 2207 DESCRIPTION 2208 "This index is either the mplsInSegmentLdpLspIfIndex 2209 or the mplsOutSegmentLdpLspIfIndex as indicated by 2210 the mplsLdpLspFecSegment." 2211 ::= { mplsLdpLspFecEntry 2 } 2213 mplsLdpLspFecLabel OBJECT-TYPE 2214 SYNTAX MplsLabel 2215 MAX-ACCESS not-accessible 2216 STATUS current 2217 DESCRIPTION 2218 "This index is either the mplsInSegmentLdpLspLabel 2219 or the mplsOutSegmentLdpLspLabel as indicated by 2220 the mplsLdpLspFecSegment." 2221 ::= { mplsLdpLspFecEntry 3 } 2223 mplsLdpLspFecIndex OBJECT-TYPE 2224 SYNTAX IndexInteger 2225 MAX-ACCESS not-accessible 2226 STATUS current 2227 DESCRIPTION 2228 "This index identifies the FEC entry in the 2229 mplsFecTable associated with this session. 2230 In other words, the value of this index 2231 is the same as the value of the mplsFecIndex 2232 that denotes the FEC associated with this 2233 Session." 2234 ::= { mplsLdpLspFecEntry 4 } 2236 mplsLdpLspFecOperStatus OBJECT-TYPE 2237 SYNTAX INTEGER { 2238 unknown(1), 2239 inUse(2), 2240 notInUse(3) 2241 } 2242 MAX-ACCESS read-only 2243 STATUS current 2244 DESCRIPTION 2245 "An indication of the operational status of 2246 the FEC associated with LDP LSP. 2248 unknown(1) - this is a temporary state which 2249 may indicate the LSP-FEC association 2250 is in a state of transition. 2252 inUse(2) - the FEC associated with the LSP is 2253 currently being applied. 2255 notInUse(3) - the FEC associated with the LSP is 2256 not being applied. Eventually, this 2257 entry may be aged out." 2259 ::= { mplsLdpLspFecEntry 5 } 2261 mplsLdpLspFecLastChange OBJECT-TYPE 2262 SYNTAX TimeStamp 2263 MAX-ACCESS read-only 2264 STATUS current 2265 DESCRIPTION 2266 "This value of sysUpTime at the time of the most recent 2267 change to the mplsLdpLspFecOperStatus object." 2268 ::= { mplsLdpLspFecEntry 6 } 2270 mplsLdpLspFecStorageType OBJECT-TYPE 2271 SYNTAX StorageType 2272 MAX-ACCESS read-create 2273 STATUS current 2274 DESCRIPTION 2275 "The storage type for this conceptual row. 2276 Conceptual rows having the value 'permanent(4)' 2277 need not allow write-access to any columnar 2278 objects in the row." 2279 DEFVAL { nonVolatile } 2280 ::= { mplsLdpLspFecEntry 7 } 2282 mplsLdpLspFecRowStatus OBJECT-TYPE 2283 SYNTAX RowStatus 2284 MAX-ACCESS read-create 2285 STATUS current 2286 DESCRIPTION 2287 "The status of this conceptual row. If the 2288 value of this object is 'active(1)', then 2289 none of the writable objects of this entry 2290 can be modified. 2292 The Agent should delete this row when 2293 the session ceases to exist. If an 2294 operator wants to associate the session with 2295 a different FEC, the recommended 2296 procedure is (as described in detail in the section 2297 entitled, 'Changing Values After Session 2298 Establishment', and again described in the 2299 DESCRIPTION clause of the 2300 mplsLdpEntityAdminStatus object) 2301 is to set the mplsLdpEntityAdminStatus to 2302 down, thereby explicitly causing a session 2303 to be torn down. This will also 2304 cause this entry to be deleted. 2306 Then, set the mplsLdpEntityAdminStatus 2307 to enable which enables a new session to be initiated. 2308 Once the session is initiated, an entry may be added to this 2309 table to associate the new session with a FEC." 2310 ::= { mplsLdpLspFecEntry 8 } 2312 -- 2313 -- Address Message/Address Withdraw Message Information 2314 -- 2315 -- This information is associated with a specific Session 2316 -- because Label Address Messages are sent after session 2317 -- initialization has taken place. 2318 -- 2320 mplsLdpSessionPeerAddrTable OBJECT-TYPE 2321 SYNTAX SEQUENCE OF MplsLdpSessionPeerAddrEntry 2322 MAX-ACCESS not-accessible 2323 STATUS current 2324 DESCRIPTION 2325 "This table 'extends' the mplsLdpSessionTable. 2326 This table is used to store Label Address Information 2327 from Label Address Messages received by this LSR from 2328 Peers. This table is read-only and should be updated 2329 when Label Withdraw Address Messages are received, i.e. 2330 Rows should be deleted as apropriate. 2332 NOTE: since more than one address may be contained 2333 in a Label Address Message, this table 'extends', 2334 rather than 'AUGMENTS' the mplsLdpSessionTable's 2335 information." 2336 ::= { mplsLdpSessionObjects 10 } 2338 mplsLdpSessionPeerAddrEntry OBJECT-TYPE 2339 SYNTAX MplsLdpSessionPeerAddrEntry 2340 MAX-ACCESS not-accessible 2341 STATUS current 2342 DESCRIPTION 2343 "An entry in this table represents information on 2344 a session's single next hop address which was 2345 advertised in an Address Message from the LDP peer. 2346 The information contained in a row is read-only." 2347 INDEX { mplsLdpEntityLdpId, 2348 mplsLdpEntityIndex, 2349 mplsLdpPeerLdpId, 2350 mplsLdpSessionPeerAddrIndex 2351 } 2352 ::= { mplsLdpSessionPeerAddrTable 1 } 2354 MplsLdpSessionPeerAddrEntry ::= SEQUENCE { 2355 mplsLdpSessionPeerAddrIndex Unsigned32, 2356 mplsLdpSessionPeerNextHopAddrType InetAddressType, 2357 mplsLdpSessionPeerNextHopAddr InetAddress 2358 } 2360 mplsLdpSessionPeerAddrIndex OBJECT-TYPE 2361 SYNTAX Unsigned32 (1..4294967295) 2362 MAX-ACCESS not-accessible 2363 STATUS current 2364 DESCRIPTION 2365 "An index which uniquely identifies this entry within 2366 a given session." 2367 ::= { mplsLdpSessionPeerAddrEntry 1 } 2369 mplsLdpSessionPeerNextHopAddrType OBJECT-TYPE 2370 SYNTAX InetAddressType 2371 MAX-ACCESS read-only 2372 STATUS current 2373 DESCRIPTION 2374 "The internetwork layer address type of this Next Hop 2375 Address as specified in the Label Address Message 2376 associated with this Session. The value of this 2377 object indicates how to interpret the value of 2378 mplsLdpSessionPeerNextHopAddr." 2379 ::= { mplsLdpSessionPeerAddrEntry 2 } 2381 mplsLdpSessionPeerNextHopAddr OBJECT-TYPE 2382 SYNTAX InetAddress 2383 MAX-ACCESS read-only 2384 STATUS current 2385 DESCRIPTION 2386 "The value of the next hop address." 2387 REFERENCE 2388 "RFC3036, Section 2.7. LDP Identifiers 2389 and Next Hop Addresses" 2390 ::= { mplsLdpSessionPeerAddrEntry 3 } 2392 --- 2393 --- Notifications 2394 --- 2395 mplsLdpInitSessionThresholdExceeded NOTIFICATION-TYPE 2396 OBJECTS { 2397 mplsLdpEntityInitSessionThreshold 2398 } 2399 STATUS current 2400 DESCRIPTION 2401 "This notification is generated when the value of 2402 the 'mplsLdpEntityInitSessionThreshold' object 2403 is not zero, and the number of Session 2404 Initialization messages exceeds the value 2405 of the 'mplsLdpEntityInitSessionThreshold' object." 2406 ::= { mplsLdpNotifications 1 } 2408 mplsLdpPathVectorLimitMismatch NOTIFICATION-TYPE 2409 OBJECTS { 2410 mplsLdpEntityPathVectorLimit, 2411 mplsLdpPeerPathVectorLimit 2412 } 2413 STATUS current 2414 DESCRIPTION 2415 "This notification is sent when the 2416 'mplsLdpEntityPathVectorLimit' does NOT match 2417 the value of the 'mplsLdpPeerPathVectorLimit' for 2418 a specific Entity." 2419 REFERENCE 2420 "RFC3036, LDP Specification, Section 3.5.3." 2421 ::= { mplsLdpNotifications 2 } 2423 mplsLdpSessionUp NOTIFICATION-TYPE 2424 OBJECTS { 2425 mplsLdpSessionState, 2426 mplsLdpSessionDiscontinuityTime, 2427 mplsLdpSessionStatsUnknownMesTypeErrors, 2428 mplsLdpSessionStatsUnknownTlvErrors 2429 } 2430 STATUS current 2431 DESCRIPTION 2432 "If this notification is enabled to generated, 2433 then this notification is sent when the 2434 value of 'mplsLdpSessionState' enters 2435 the 'operational(5)' state." 2436 ::= { mplsLdpNotifications 3 } 2438 mplsLdpSessionDown NOTIFICATION-TYPE 2439 OBJECTS { 2440 mplsLdpSessionState, 2441 mplsLdpSessionDiscontinuityTime, 2442 mplsLdpSessionStatsUnknownMesTypeErrors, 2443 mplsLdpSessionStatsUnknownTlvErrors 2445 } 2446 STATUS current 2447 DESCRIPTION 2448 "This notification is sent when the 2449 the value of 'mplsLdpSessionState' leaves 2450 the 'operational(5)' state." 2451 ::= { mplsLdpNotifications 4 } 2453 --**************************************************************** 2454 -- Module Conformance Statement 2455 --**************************************************************** 2457 mplsLdpGroups 2458 OBJECT IDENTIFIER ::= { mplsLdpConformance 1 } 2460 mplsLdpCompliances 2461 OBJECT IDENTIFIER ::= { mplsLdpConformance 2 } 2463 -- 2464 -- Full Compliance 2465 -- 2467 mplsLdpModuleFullCompliance MODULE-COMPLIANCE 2468 STATUS current 2469 DESCRIPTION 2470 "The Module is implemented with support 2471 for read-create and read-write. In other 2472 words, both monitoring and configuration 2473 are available when using this MODULE-COMPLIANCE." 2475 MODULE -- this module 2476 MANDATORY-GROUPS { mplsLdpGeneralGroup, 2477 mplsLdpNotificationsGroup 2478 } 2480 GROUP mplsLdpLspGroup 2481 DESCRIPTION 2482 "This group must be supported if the LSR MIB is 2483 implemented, specifically the mplsInSegmentTable, 2484 the mplsOutSegmentTable or the mplsXCTable." 2486 OBJECT mplsLdpEntityTargetPeerAddrType 2487 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2488 DESCRIPTION 2489 "An implementation is only required to support 2490 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2492 OBJECT mplsLdpEntityTargetPeerAddr 2493 SYNTAX InetAddress (SIZE(0|4|16)) 2494 DESCRIPTION 2495 "An implementation is only required to support IPv4 and 2496 globally unique IPv6 addresses." 2498 OBJECT mplsLdpEntityRowStatus 2499 SYNTAX RowStatus { active(1) } 2500 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 2501 DESCRIPTION 2502 "Support for createAndWait and notInService is not 2503 required." 2505 OBJECT mplsFecAddrFamily 2506 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2507 DESCRIPTION 2508 "An implementation is only required to support 2509 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2511 OBJECT mplsFecAddr 2512 SYNTAX InetAddress (SIZE(0|4|16)) 2513 DESCRIPTION 2514 "An implementation is only required to support IPv4 and 2515 globally unique IPv6 addresses." 2517 OBJECT mplsFecRowStatus 2518 SYNTAX RowStatus { active(1) } 2519 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 2520 MIN-ACCESS read-only 2521 DESCRIPTION 2522 "Support for createAndWait and notInService is not 2523 required. Also, the entries in this table may be 2524 created by the agent, so strictly speaking 2525 read-create functionality is not necessary, but 2526 may be nice to have." 2528 OBJECT mplsLdpLspFecRowStatus 2529 SYNTAX RowStatus { active(1) } 2530 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 2531 MIN-ACCESS read-only 2532 DESCRIPTION 2533 "Support for createAndWait and notInService is not 2534 required. Also, the entries in this table may be 2535 created by the agent, so strictly speaking 2536 read-create functionality is not necessary, but 2537 may be nice to have." 2539 OBJECT mplsLdpSessionPeerNextHopAddrType 2540 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2541 DESCRIPTION 2542 "An implementation is only required to support 2543 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2545 OBJECT mplsLdpSessionPeerNextHopAddr 2546 SYNTAX InetAddress (SIZE(0|4|16)) 2547 DESCRIPTION 2548 "An implementation is only required to support IPv4 2549 and globally unique IPv6 addresses." 2551 ::= { mplsLdpCompliances 1 } 2553 -- 2554 -- Read-Only Compliance 2555 -- 2557 mplsLdpModuleReadOnlyCompliance MODULE-COMPLIANCE 2558 STATUS current 2559 DESCRIPTION 2560 "The Module is implemented with support 2561 for read-only. In other words, only monitoring 2562 is available by implementing this MODULE-COMPLIANCE." 2564 MODULE -- this module 2565 MANDATORY-GROUPS { mplsLdpGeneralGroup, 2566 mplsLdpNotificationsGroup 2567 } 2569 GROUP mplsLdpLspGroup 2570 DESCRIPTION 2571 "This group must be supported if the LSR MIB is 2572 implemented, specifically the mplsInSegmentTable, 2573 the mplsOutSegmentTable or the mplsXCTable." 2575 OBJECT mplsLdpEntityProtocolVersion 2576 MIN-ACCESS read-only 2577 DESCRIPTION 2578 "Write access is not required." 2580 OBJECT mplsLdpEntityAdminStatus 2581 MIN-ACCESS read-only 2582 DESCRIPTION 2583 "Write access is not required." 2585 OBJECT mplsLdpEntityTcpDscPort 2586 MIN-ACCESS read-only 2587 DESCRIPTION 2588 "Write access is not required." 2590 OBJECT mplsLdpEntityUdpDscPort 2591 MIN-ACCESS read-only 2592 DESCRIPTION 2593 "Write access is not required." 2595 OBJECT mplsLdpEntityMaxPduLength 2596 MIN-ACCESS read-only 2597 DESCRIPTION 2598 "Write access is not required." 2600 OBJECT mplsLdpEntityKeepAliveHoldTimer 2601 MIN-ACCESS read-only 2602 DESCRIPTION 2603 "Write access is not required." 2605 OBJECT mplsLdpEntityHelloHoldTimer 2606 MIN-ACCESS read-only 2607 DESCRIPTION 2608 "Write access is not required." 2610 OBJECT mplsLdpEntityInitSessionThreshold 2611 MIN-ACCESS read-only 2612 DESCRIPTION 2613 "Write access is not required." 2615 OBJECT mplsLdpEntityLabelDistMethod 2616 MIN-ACCESS read-only 2617 DESCRIPTION 2618 "Write access is not required." 2620 OBJECT mplsLdpEntityLabelRetentionMode 2621 MIN-ACCESS read-only 2622 DESCRIPTION 2623 "Write access is not required." 2625 OBJECT mplsLdpEntityPathVectorLimit 2626 MIN-ACCESS read-only 2627 DESCRIPTION 2628 "Write access is not required." 2630 OBJECT mplsLdpEntityHopCountLimit 2631 MIN-ACCESS read-only 2632 DESCRIPTION 2633 "Write access is not required." 2635 OBJECT mplsLdpEntityTransportAddrKind 2636 MIN-ACCESS read-only 2637 DESCRIPTION 2638 "Write access is not required." 2640 OBJECT mplsLdpEntityTargetPeer 2641 MIN-ACCESS read-only 2642 DESCRIPTION 2643 "Write access is not required." 2645 OBJECT mplsLdpEntityTargetPeerAddrType 2646 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2647 MIN-ACCESS read-only 2648 DESCRIPTION 2649 "Write access is not required. 2650 An implementation is only required to support 2651 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2653 OBJECT mplsLdpEntityTargetPeerAddr 2654 SYNTAX InetAddress (SIZE(0|4|16)) 2655 MIN-ACCESS read-only 2656 DESCRIPTION 2657 "Write access is not required. 2658 An implementation is only required to support IPv4 and 2659 globally unique IPv6 addresses." 2661 OBJECT mplsLdpEntityLabelType 2662 MIN-ACCESS read-only 2663 DESCRIPTION 2664 "Write access is not required." 2666 OBJECT mplsLdpEntityStorageType 2667 MIN-ACCESS read-only 2668 DESCRIPTION 2669 "Write access is not required." 2671 OBJECT mplsLdpEntityRowStatus 2672 SYNTAX RowStatus { active(1) } 2673 MIN-ACCESS read-only 2674 DESCRIPTION 2675 "Write access is not required, and active is the 2676 only status that needs to be supported." 2678 OBJECT mplsFecType 2679 MIN-ACCESS read-only 2680 DESCRIPTION 2681 "Write access is not required." 2683 OBJECT mplsFecAddrPrefixLength 2684 MIN-ACCESS read-only 2685 DESCRIPTION 2686 "Write access is not required." 2688 OBJECT mplsFecAddrFamily 2689 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2690 MIN-ACCESS read-only 2691 DESCRIPTION 2692 "Write access is not required. 2693 An implementation is only required to support 2694 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2696 OBJECT mplsFecAddr 2697 SYNTAX InetAddress (SIZE(0|4|16)) 2698 MIN-ACCESS read-only 2699 DESCRIPTION 2700 "Write access is not required. 2701 An implementation is only required to support IPv4 and 2702 globally unique IPv6 addresses." 2704 OBJECT mplsFecStorageType 2705 MIN-ACCESS read-only 2706 DESCRIPTION 2707 "Write access is not required." 2709 OBJECT mplsFecRowStatus 2710 SYNTAX RowStatus { active(1) } 2711 MIN-ACCESS read-only 2712 DESCRIPTION 2713 "Write access is not required, and active is the 2714 only status that needs to be supported." 2716 OBJECT mplsLdpLspFecStorageType 2717 MIN-ACCESS read-only 2718 DESCRIPTION 2719 "Write access is not required." 2721 OBJECT mplsLdpLspFecRowStatus 2722 SYNTAX RowStatus { active(1) } 2723 MIN-ACCESS read-only 2724 DESCRIPTION 2725 "Write access is not required, and active is the 2726 only status that needs to be supported." 2728 OBJECT mplsLdpSessionPeerNextHopAddrType 2729 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2730 DESCRIPTION 2731 "An implementation is only required to support 2732 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2734 OBJECT mplsLdpSessionPeerNextHopAddr 2735 SYNTAX InetAddress (SIZE(0|4|16)) 2736 DESCRIPTION 2737 "An implementation is only required to support IPv4 2738 and globally unique IPv6 addresses." 2740 ::= { mplsLdpCompliances 2 } 2742 -- units of conformance 2744 mplsLdpGeneralGroup OBJECT-GROUP 2745 OBJECTS { 2746 mplsLdpLsrId, 2747 mplsLdpLsrLoopDetectionCapable, 2748 mplsLdpEntityLastChange, 2749 mplsLdpEntityIndexNext, 2750 mplsLdpEntityProtocolVersion, 2751 mplsLdpEntityAdminStatus, 2752 mplsLdpEntityOperStatus, 2753 mplsLdpEntityTcpDscPort, 2754 mplsLdpEntityUdpDscPort, 2755 mplsLdpEntityMaxPduLength, 2756 mplsLdpEntityKeepAliveHoldTimer, 2757 mplsLdpEntityHelloHoldTimer, 2758 mplsLdpEntityInitSessionThreshold, 2759 mplsLdpEntityLabelDistMethod, 2760 mplsLdpEntityLabelRetentionMode, 2761 mplsLdpEntityPathVectorLimit, 2762 mplsLdpEntityHopCountLimit, 2763 mplsLdpEntityTransportAddrKind, 2764 mplsLdpEntityTargetPeer, 2765 mplsLdpEntityTargetPeerAddrType, 2766 mplsLdpEntityTargetPeerAddr, 2767 mplsLdpEntityLabelType, 2768 mplsLdpEntityDiscontinuityTime, 2769 mplsLdpEntityStorageType, 2770 mplsLdpEntityRowStatus, 2771 mplsLdpEntityStatsSessionAttempts, 2772 mplsLdpEntityStatsSessionRejectedNoHelloErrors, 2773 mplsLdpEntityStatsSessionRejectedAdErrors, 2774 mplsLdpEntityStatsSessionRejectedMaxPduErrors, 2775 mplsLdpEntityStatsSessionRejectedLRErrors, 2776 mplsLdpEntityStatsBadLdpIdentifierErrors, 2777 mplsLdpEntityStatsBadPduLengthErrors, 2778 mplsLdpEntityStatsBadMessageLengthErrors, 2779 mplsLdpEntityStatsBadTlvLengthErrors, 2780 mplsLdpEntityStatsMalformedTlvValueErrors, 2781 mplsLdpEntityStatsKeepAliveTimerExpErrors, 2782 mplsLdpEntityStatsShutdownReceivedNotifications, 2783 mplsLdpEntityStatsShutdownSentNotifications, 2784 mplsLdpPeerLastChange, 2785 mplsLdpPeerLabelDistMethod, 2786 mplsLdpPeerPathVectorLimit, 2787 mplsLdpPeerTransportAddrType, 2788 mplsLdpPeerTransportAddr, 2789 mplsLdpHelloAdjacencyHoldTimeRem, 2790 mplsLdpHelloAdjacencyHoldTime, 2791 mplsLdpHelloAdjacencyType, 2792 mplsLdpSessionStateLastChange, 2793 mplsLdpSessionState, 2794 mplsLdpSessionRole, 2795 mplsLdpSessionProtocolVersion, 2796 mplsLdpSessionKeepAliveHoldTimeRem, 2797 mplsLdpSessionKeepAliveTime, 2798 mplsLdpSessionMaxPduLength, 2799 mplsLdpSessionDiscontinuityTime, 2800 mplsLdpSessionStatsUnknownMesTypeErrors, 2801 mplsLdpSessionStatsUnknownTlvErrors, 2802 mplsLdpSessionPeerNextHopAddrType, 2803 mplsLdpSessionPeerNextHopAddr, 2804 mplsFecIndexNext, 2805 mplsFecType, 2806 mplsFecAddrPrefixLength, 2807 mplsFecAddrFamily, 2808 mplsFecAddr, 2809 mplsFecStorageType, 2810 mplsFecRowStatus 2811 } 2812 STATUS current 2813 DESCRIPTION 2814 "Objects that apply to all MPLS LDP implementations." 2815 ::= { mplsLdpGroups 1 } 2817 mplsLdpLspGroup OBJECT-GROUP 2818 OBJECTS { 2819 mplsInSegmentLdpLspLabelType, 2820 mplsInSegmentLdpLspType, 2821 mplsOutSegmentLdpLspLabelType, 2822 mplsOutSegmentLdpLspType, 2823 mplsLdpLspFecOperStatus, 2824 mplsLdpLspFecLastChange, 2825 mplsLdpLspFecStorageType, 2826 mplsLdpLspFecRowStatus 2827 } 2828 STATUS current 2829 DESCRIPTION 2830 "These objects are for LDP implementations 2831 which interface to the Label Information Base (LIB) 2832 in the MPLS-LSR-STD-MIB. The LIB is 2833 represented in the mplsInSegmentTable, 2834 mplsOutSegmentTable and mplsXCTable." 2835 ::= { mplsLdpGroups 2 } 2837 mplsLdpNotificationsGroup NOTIFICATION-GROUP 2838 NOTIFICATIONS { mplsLdpInitSessionThresholdExceeded, 2839 mplsLdpPathVectorLimitMismatch, 2840 mplsLdpSessionUp, 2841 mplsLdpSessionDown 2842 } 2843 STATUS current 2844 DESCRIPTION 2845 "The notification for an MPLS LDP implemention." 2846 ::= { mplsLdpGroups 3 } 2848 END 2850 4.1. The MPLS-LDP-ATM-STD-MIB Module 2852 This MIB Module MUST be supported if LDP uses ATM as the Layer 2 2853 media. There are three tables in this MIB Module. Two tables are 2854 for configuring LDP to use ATM. These tables are the 2855 mplsLdpEntityAtmTable and the mplsLdpEntityAtmLRTable. 2857 The mplsLdpEntityAtmTable provides a way to configure information 2858 which would be contained in the "Optional Parameter" portion of an 2859 LDP PDU Initialization Message. 2861 The mplsLdpEntityAtmLRTable provides a way to configure information 2862 which would be contained in the "ATM Label Range Components" portion 2863 of an LDP PDU Intialization Message, see [RFC3035] and [RFC3036]. 2865 4.1.1. The LDP ATM Session Table 2867 The MPLS LDP ATM Session Table is a read-only table which contains 2868 session information specific to ATM. 2870 MPLS-LDP-ATM-STD-MIB DEFINITIONS ::= BEGIN 2872 IMPORTS 2873 OBJECT-TYPE, MODULE-IDENTITY, 2874 Unsigned32 2875 FROM SNMPv2-SMI 2876 MODULE-COMPLIANCE, OBJECT-GROUP 2877 FROM SNMPv2-CONF 2879 RowStatus, 2880 StorageType 2881 FROM SNMPv2-TC 2883 InterfaceIndexOrZero 2884 FROM IF-MIB 2886 AtmVpIdentifier 2887 FROM ATM-TC-MIB 2889 mplsStdMIB, 2890 MplsAtmVcIdentifier 2891 FROM MPLS-TC-STD-MIB 2893 mplsLdpEntityLdpId, 2894 mplsLdpEntityIndex, 2895 mplsLdpPeerLdpId 2896 FROM MPLS-LDP-STD-MIB 2898 ; 2900 mplsLdpAtmStdMIB MODULE-IDENTITY 2901 LAST-UPDATED "200306091200Z" -- 9 June 2003 2902 ORGANIZATION "Multiprotocol Label Switching (mpls) 2903 Working Group" 2904 CONTACT-INFO 2905 "Joan Cucchiara (jcucchiara@artel.com) 2906 Artel 2908 Hans Sjostrand (hans@ipunplugged.com) 2909 ipUnplugged 2911 James V. Luciani (james_luciani@mindspring.com) 2912 Consultant 2914 Working Group Chairs: 2915 George Swallow, email: swallow@cisco.com 2916 Loa Andersson, email: loa@pi.se 2918 MPLS Working Group, email: mpls@uu.net 2919 " 2920 DESCRIPTION 2921 "Copyright (C) The Internet Society (2003). This 2922 version of this MIB module is part of RFCXXX; see 2923 the RFC itself for full legal notices. 2925 This MIB contains managed object definitions for 2926 configuring and monitoring the Multiprotocol Label 2927 Switching (MPLS), Label Distribution Protocol (LDP), 2928 utilizing Asynchronous Transfer Mode (ATM) as the Layer 2 2929 media." 2930 REVISION "200306091200Z" -- 9 June 2003 2931 DESCRIPTION 2932 "Initial version published as part of RFC XXXX." 2934 -- Please see the IANA Considerations Section 2935 -- the suggested mplsStdMIB subId is 5, e.g. 2936 -- ::= { mplsStdMIB 5 } 2938 ::= { mplsStdMIB XXX } -- to be assigned by IANA 2940 --**************************************************************** 2942 mplsLdpAtmObjects OBJECT IDENTIFIER 2943 ::= { mplsLdpAtmStdMIB 1 } 2944 mplsLdpAtmConformance OBJECT IDENTIFIER 2945 ::= { mplsLdpAtmStdMIB 2 } 2947 --**************************************************************** 2948 -- MPLS LDP ATM Objects 2949 --**************************************************************** 2951 -- 2952 -- Ldp Entity Objects for ATM 2953 -- 2955 mplsLdpEntityAtmObjects OBJECT IDENTIFIER ::= 2956 { mplsLdpAtmObjects 1 } 2958 mplsLdpEntityAtmTable OBJECT-TYPE 2959 SYNTAX SEQUENCE OF MplsLdpEntityAtmEntry 2960 MAX-ACCESS not-accessible 2961 STATUS current 2962 DESCRIPTION 2963 "This table contains information about the 2964 ATM specific information which could be used 2965 in the 'Optional Parameters' and other ATM 2966 specific information. 2968 This table 'sparse augments' the mplsLdpEntityTable 2969 when ATM as the Layer 2 media." 2970 ::= { mplsLdpEntityAtmObjects 1 } 2972 mplsLdpEntityAtmEntry OBJECT-TYPE 2973 SYNTAX MplsLdpEntityAtmEntry 2974 MAX-ACCESS not-accessible 2975 STATUS current 2976 DESCRIPTION 2977 "An entry in this table represents the ATM parameters 2978 and ATM information for this LDP entity." 2979 INDEX { mplsLdpEntityLdpId, 2980 mplsLdpEntityIndex 2981 } 2982 ::= { mplsLdpEntityAtmTable 1 } 2984 MplsLdpEntityAtmEntry ::= SEQUENCE { 2985 mplsLdpEntityAtmIfIndexOrZero InterfaceIndexOrZero, 2986 mplsLdpEntityAtmMergeCap INTEGER, 2987 mplsLdpEntityAtmLRComponents Unsigned32, 2988 mplsLdpEntityAtmVcDirectionality INTEGER, 2989 mplsLdpEntityAtmLsrConnectivity INTEGER, 2990 mplsLdpEntityAtmDefaultControlVpi AtmVpIdentifier, 2991 mplsLdpEntityAtmDefaultControlVci MplsAtmVcIdentifier, 2992 mplsLdpEntityAtmUnlabTrafVpi AtmVpIdentifier, 2993 mplsLdpEntityAtmUnlabTrafVci MplsAtmVcIdentifier, 2994 mplsLdpEntityAtmStorageType StorageType, 2995 mplsLdpEntityAtmRowStatus RowStatus 2996 } 2998 mplsLdpEntityAtmIfIndexOrZero OBJECT-TYPE 2999 SYNTAX InterfaceIndexOrZero 3000 MAX-ACCESS read-create 3001 STATUS current 3002 DESCRIPTION 3003 "This value represents either the InterfaceIndex of 3004 the 'ifLayer' where the ATM Labels 'owned' by this 3005 entry were created, or 0 (zero). The value of zero 3006 means that the InterfaceIndex is not known. For example, 3007 if the InterfaceIndex is created subsequent to the 3008 ATM Label's creation, then it would not be known. 3009 However, if the InterfaceIndex is known, then it must 3010 be represented by this value. 3012 If an InterfaceIndex becomes known, then the 3013 network management entity (e.g. SNMP agent) responsible 3014 for this object MUST change the value from 0 (zero) to the 3015 value of the InterfaceIndex. If an ATM Label is 3016 being used in forwarding data, then the value of this 3017 object MUST be the InterfaceIndex." 3018 ::= { mplsLdpEntityAtmEntry 1 } 3020 mplsLdpEntityAtmMergeCap OBJECT-TYPE 3021 SYNTAX INTEGER { 3022 notSupported(0), 3023 vpMerge(1), 3024 vcMerge(2), 3025 vpAndVcMerge(3) 3026 } 3027 MAX-ACCESS read-create 3028 STATUS current 3029 DESCRIPTION 3030 "Denotes the Merge Capability of this Entity. 3031 This is the EXACT value for the ATM Session Parameter, 3032 field M (for ATM Merge Capabilities). The ATM Session Parameter 3033 is an optional parameter in the Initialization Message. 3035 The description from rfc3036.txt is: 3037 'M, ATM Merge Capabilities 3038 Specifies the merge capabilities of an ATM switch. The 3039 following values are supported in this version of the 3040 specification: 3042 Value Meaning 3044 0 Merge not supported 3045 1 VP Merge supported 3046 2 VC Merge supported 3047 3 VP & VC Merge supported 3049 If the merge capabilities of the LSRs differ, then: 3050 - Non-merge and VC-merge LSRs may freely interoperate. 3052 - The interoperability of VP-merge-capable switches with non- 3053 VP-merge-capable switches is a subject for future study. 3054 When the LSRs differ on the use of VP-merge, the session is 3055 established, but VP merge is not used.' 3057 Please refer to the following reference for a complete 3058 description of this feature." 3059 REFERENCE 3060 "RFC3036, LDP Specification, Section 3.5.3 Initialization Message." 3062 ::= { mplsLdpEntityAtmEntry 2 } 3064 mplsLdpEntityAtmLRComponents OBJECT-TYPE 3065 SYNTAX Unsigned32 (1..65535) 3066 MAX-ACCESS read-create 3067 STATUS current 3068 DESCRIPTION 3069 "Number of Label Range Components in the Initialization 3070 message. This also represents the number of entries 3071 in the mplsLdpEntityAtmLRTable which correspond 3072 to this entry. 3074 This is the EXACT value for the ATM Session Parameter, 3075 field N (for Number of label range components). The ATM 3076 Session Parameter is an optional parameter in the Initialization 3077 Message. 3079 The description from rfc3036.txt is: 3081 'N, Number of label range components 3082 Specifies the number of ATM Label Range Components 3083 included in the TLV.' 3085 Please refer to the following reference for a complete 3086 description of this feature." 3087 REFERENCE 3088 "RFC3036, LDP Specification, Section 3.5.3 Initialization Message." 3089 ::= { mplsLdpEntityAtmEntry 3 } 3091 mplsLdpEntityAtmVcDirectionality OBJECT-TYPE 3092 SYNTAX INTEGER { 3093 bidirectional(0), 3094 unidirectional(1) 3095 } 3096 MAX-ACCESS read-create 3097 STATUS current 3098 DESCRIPTION 3099 "If the value of this object is 'bidirectional(0)', 3100 a given VCI, within a given VPI, is used as a 3101 label for both directions independently. 3103 If the value of this object is 'unidirectional(1)', 3104 a given VCI within a VPI designates one direction. 3106 This is the EXACT value for the ATM Session Parameter, 3107 field D (for VC Directionality). The ATM Session Parameter 3108 is an optional parameter in the Initialization Message. 3110 The description from rfc3036.txt is: 3112 'D, VC Directionality 3113 A value of 0 specifies bidirectional VC capability, meaning the 3114 LSR can (within a given VPI) support the use of a given VCI as 3115 a label for both link directions independently. A value of 1 3116 specifies unidirectional VC capability, meaning (within a given 3117 VPI) a given VCI may appear in a label mapping for one 3118 direction on the link only. When either or both of the peers 3119 specifies unidirectional VC capability, both LSRs use 3120 unidirectional VC label assignment for the link as follows. 3121 The LSRs compare their LDP Identifiers as unsigned integers. 3122 The LSR with the larger LDP Identifier may assign only odd- 3123 numbered VCIs in the VPI/VCI range as labels. The system with 3124 the smaller LDP Identifier may assign only even-numbered VCIs 3125 in the VPI/VCI range as labels.' 3127 Please refer to the following reference for a complete 3128 description of this feature." 3129 REFERENCE 3130 "RFC3036, LDP Specification, Section 3.5.3 Initialization Message." 3131 ::= { mplsLdpEntityAtmEntry 4 } 3133 mplsLdpEntityAtmLsrConnectivity OBJECT-TYPE 3134 SYNTAX INTEGER { 3135 direct(1), 3136 indirect(2) 3137 } 3138 MAX-ACCESS read-create 3139 STATUS current 3140 DESCRIPTION 3141 "The peer LSR may be connected indirectly by means of an 3142 ATM VP so that the VPI values may be different on either 3143 endpoint so the label MUST be encoded entirely within the 3144 VCI field." 3145 DEFVAL { direct } 3146 ::= { mplsLdpEntityAtmEntry 5 } 3148 mplsLdpEntityAtmDefaultControlVpi OBJECT-TYPE 3149 SYNTAX AtmVpIdentifier 3150 MAX-ACCESS read-create 3151 STATUS current 3152 DESCRIPTION 3153 "The default VPI value for the non-MPLS connection. The 3154 default value of this is 0 (zero) but other values may 3155 be configured. This object allows a different value 3156 to be configured." 3157 DEFVAL { 0 } 3158 ::= { mplsLdpEntityAtmEntry 6 } 3160 mplsLdpEntityAtmDefaultControlVci OBJECT-TYPE 3161 SYNTAX MplsAtmVcIdentifier 3162 MAX-ACCESS read-create 3163 STATUS current 3164 DESCRIPTION 3165 "The Default VCI value for a non-MPLS connection. The 3166 default value of this is 32 but other values may be 3167 configured. This object allows a different value to 3168 be configured." 3169 DEFVAL { 32 } 3170 ::= { mplsLdpEntityAtmEntry 7 } 3172 mplsLdpEntityAtmUnlabTrafVpi OBJECT-TYPE 3173 SYNTAX AtmVpIdentifier 3174 MAX-ACCESS read-create 3175 STATUS current 3176 DESCRIPTION 3177 "VPI value of the VCC supporting unlabeled traffic. This 3178 non-MPLS connection is used to carry unlabeled (IP) 3179 packets. The default value is the same as the default 3180 value of the 'mplsLdpEntityAtmDefaultControlVpi', however 3181 another value may be configured." 3182 DEFVAL { 0 } 3183 ::= { mplsLdpEntityAtmEntry 8 } 3185 mplsLdpEntityAtmUnlabTrafVci OBJECT-TYPE 3186 SYNTAX MplsAtmVcIdentifier 3187 MAX-ACCESS read-create 3188 STATUS current 3189 DESCRIPTION 3190 "VCI value of the VCC supporting unlabeled traffic. 3191 This non-MPLS connection is used to carry unlabeled (IP) 3192 packets. The default value is the same as the default 3193 value of the 'mplsLdpEntityAtmDefaultControlVci', however 3194 another value may be configured." 3195 DEFVAL { 32 } 3196 ::= { mplsLdpEntityAtmEntry 9 } 3198 mplsLdpEntityAtmStorageType OBJECT-TYPE 3199 SYNTAX StorageType 3200 MAX-ACCESS read-create 3201 STATUS current 3202 DESCRIPTION 3203 "The storage type for this conceptual row. 3204 Conceptual rows having the value 'permanent(4)' 3205 need not allow write-access to any columnar 3206 objects in the row." 3207 DEFVAL { nonVolatile } 3208 ::= { mplsLdpEntityAtmEntry 10 } 3210 mplsLdpEntityAtmRowStatus OBJECT-TYPE 3211 SYNTAX RowStatus 3212 MAX-ACCESS read-create 3213 STATUS current 3214 DESCRIPTION 3215 "The status of this conceptual row. All writable 3216 objects in this row may be modified at any time, 3217 however, as described in detail in the section 3218 entitled, 'Changing Values After Session 3219 Establishment', and again described in the 3220 DESCRIPTION clause of the mplsLdpEntityAdminStatus 3221 object, if a session has been initiated with a Peer, 3222 changing objects in this table will wreak havoc 3223 with the session and interrupt traffic. To repeat again: 3224 the recommended procedure is to set the 3225 mplsLdpEntityAdminStatus to down, thereby explicitly 3226 causing a session to be torn down. Then, 3227 change objects in this entry, then set the 3228 mplsLdpEntityAdminStatus to enable 3229 which enables a new session to be initiated." 3230 ::= { mplsLdpEntityAtmEntry 11 } 3232 -- 3233 -- The MPLS LDP Entity ATM Label Range Table 3234 -- 3236 mplsLdpEntityAtmLRTable OBJECT-TYPE 3237 SYNTAX SEQUENCE OF MplsLdpEntityAtmLREntry 3238 MAX-ACCESS not-accessible 3239 STATUS current 3240 DESCRIPTION 3241 "The MPLS LDP Entity ATM Label Range (LR) Table. 3242 The purpose of this table is to provide a mechanism 3243 for configuring a contiguous range of vpi's 3244 with a contiguous range of vci's, or a 'label range' 3245 for LDP Entities. 3247 LDP Entities which use ATM must have at least one 3248 entry in this table. 3250 There must exist at least one entry in this 3251 table for every LDP Entity that has 3252 'mplsLdpEntityOptionalParameters' object with 3253 a value of 'atmSessionParameters'." 3254 ::= { mplsLdpEntityAtmObjects 2 } 3256 mplsLdpEntityAtmLREntry OBJECT-TYPE 3257 SYNTAX MplsLdpEntityAtmLREntry 3258 MAX-ACCESS not-accessible 3259 STATUS current 3260 DESCRIPTION 3261 "A row in the LDP Entity ATM Label 3262 Range Table. One entry in this table contains 3263 information on a single range of labels 3264 represented by the configured Upper and Lower 3265 Bounds VPI/VCI pairs. These are the same 3266 data used in the Initialization Message. 3268 NOTE: The ranges for a specific LDP Entity 3269 are UNIQUE and non-overlapping. For example, 3270 for a specific LDP Entity index, there could 3271 be one entry having LowerBound vpi/vci == 0/32, and 3272 UpperBound vpi/vci == 0/100, and a second entry 3273 for this same interface with LowerBound 3274 vpi/vci == 0/101 and UpperBound vpi/vci == 0/200. 3275 However, there could not be a third entry with 3276 LowerBound vpi/vci == 0/200 and 3277 UpperBound vpi/vci == 0/300 because this label 3278 range overlaps with the second entry (i.e. both 3279 entries now have 0/200). 3281 A row will not be created unless a unique and 3282 non-overlapping range is specified. Thus, row 3283 creation implies a one-shot row creation of 3284 LDP EntityID and LowerBound vpi/vci and 3285 UpperBound vpi/vci. At least one label 3286 range entry for a specific LDP Entity MUST 3287 include the default VPI/VCI values denoted 3288 in the LDP Entity Table. 3290 A request to create a row with an overlapping 3291 range should result in an inconsistentValue 3292 error." 3293 INDEX { mplsLdpEntityLdpId, 3294 mplsLdpEntityIndex, 3295 mplsLdpEntityAtmLRMinVpi, 3296 mplsLdpEntityAtmLRMinVci 3297 } 3298 ::= { mplsLdpEntityAtmLRTable 1 } 3300 MplsLdpEntityAtmLREntry ::= SEQUENCE { 3301 mplsLdpEntityAtmLRMinVpi AtmVpIdentifier, 3302 mplsLdpEntityAtmLRMinVci MplsAtmVcIdentifier, 3303 mplsLdpEntityAtmLRMaxVpi AtmVpIdentifier, 3304 mplsLdpEntityAtmLRMaxVci MplsAtmVcIdentifier, 3305 mplsLdpEntityAtmLRStorageType StorageType, 3306 mplsLdpEntityAtmLRRowStatus RowStatus 3307 } 3309 mplsLdpEntityAtmLRMinVpi OBJECT-TYPE 3310 SYNTAX AtmVpIdentifier 3311 MAX-ACCESS not-accessible 3312 STATUS current 3313 DESCRIPTION 3314 "The minimum VPI number configured for this range. 3315 The value of zero is a valid value for the VPI portion 3316 of the label." 3317 ::= { mplsLdpEntityAtmLREntry 1 } 3319 mplsLdpEntityAtmLRMinVci OBJECT-TYPE 3320 SYNTAX MplsAtmVcIdentifier 3321 MAX-ACCESS not-accessible 3322 STATUS current 3323 DESCRIPTION 3324 "The minimum VCI number configured for this range." 3325 ::= { mplsLdpEntityAtmLREntry 2 } 3327 mplsLdpEntityAtmLRMaxVpi OBJECT-TYPE 3328 SYNTAX AtmVpIdentifier 3329 MAX-ACCESS read-create 3330 STATUS current 3331 DESCRIPTION 3332 "The maximum VPI number configured for this range." 3333 ::= { mplsLdpEntityAtmLREntry 3 } 3335 mplsLdpEntityAtmLRMaxVci OBJECT-TYPE 3336 SYNTAX MplsAtmVcIdentifier 3337 MAX-ACCESS read-create 3338 STATUS current 3339 DESCRIPTION 3340 "The maximum VCI number configured for this range." 3341 ::= { mplsLdpEntityAtmLREntry 4 } 3343 mplsLdpEntityAtmLRStorageType OBJECT-TYPE 3344 SYNTAX StorageType 3345 MAX-ACCESS read-create 3346 STATUS current 3347 DESCRIPTION 3348 "The storage type for this conceptual row. 3349 Conceptual rows having the value 'permanent(4)' 3350 need not allow write-access to any columnar 3351 objects in the row." 3352 DEFVAL { nonVolatile } 3353 ::= { mplsLdpEntityAtmLREntry 5 } 3355 mplsLdpEntityAtmLRRowStatus OBJECT-TYPE 3356 SYNTAX RowStatus 3357 MAX-ACCESS read-create 3358 STATUS current 3359 DESCRIPTION 3360 "The status of this conceptual row. All writable 3361 objects in this row may be modified at any time, 3362 however, as described in detail in the section 3363 entitled, 'Changing Values After Session 3364 Establishment', and again described in the 3365 DESCRIPTION clause of the 3366 mplsLdpEntityAdminStatus object, 3367 if a session has been initiated with a Peer, 3368 changing objects in this table will 3369 wreak havoc with the session and interrupt traffic. 3370 To repeat again: the recommended procedure 3371 is to set the mplsLdpEntityAdminStatus to 3372 down, thereby explicitly causing a session 3373 to be torn down. Then, change objects in this 3374 entry, then set the mplsLdpEntityAdminStatus 3375 to enable which enables a new session 3376 to be initiated." 3377 ::= { mplsLdpEntityAtmLREntry 6 } 3379 -- 3380 -- MPLS LDP ATM Session Information 3381 -- 3382 mplsLdpAtmSessionObjects OBJECT IDENTIFIER ::= 3383 { mplsLdpAtmObjects 2 } 3385 mplsLdpAtmSessionTable OBJECT-TYPE 3386 SYNTAX SEQUENCE OF MplsLdpAtmSessionEntry 3387 MAX-ACCESS not-accessible 3388 STATUS current 3389 DESCRIPTION 3390 "A table which relates sessions in the 3391 'mplsLdpSessionTable' and their label 3392 range intersections. There could be one 3393 or more label range intersections between an 3394 LDP Entity and LDP Peer using ATM as the 3395 underlying media. Each row represents 3396 a single label range intersection. 3398 This table cannot use the 'AUGMENTS' 3399 clause because there is not necessarily 3400 a one-to-one mapping between this table 3401 and the mplsLdpSessionTable." 3402 ::= { mplsLdpAtmSessionObjects 1 } 3404 mplsLdpAtmSessionEntry OBJECT-TYPE 3405 SYNTAX MplsLdpAtmSessionEntry 3406 MAX-ACCESS not-accessible 3407 STATUS current 3408 DESCRIPTION 3409 "An entry in this table represents information on a 3410 single label range intersection between an LDP Entity 3411 and LDP Peer. 3413 The information contained in a row is read-only." 3414 INDEX { mplsLdpEntityLdpId, 3415 mplsLdpEntityIndex, 3416 mplsLdpPeerLdpId, 3417 mplsLdpSessionAtmLRLowerBoundVpi, 3418 mplsLdpSessionAtmLRLowerBoundVci 3420 } 3421 ::= { mplsLdpAtmSessionTable 1 } 3423 MplsLdpAtmSessionEntry ::= SEQUENCE { 3424 mplsLdpSessionAtmLRLowerBoundVpi AtmVpIdentifier, 3425 mplsLdpSessionAtmLRLowerBoundVci MplsAtmVcIdentifier, 3426 mplsLdpSessionAtmLRUpperBoundVpi AtmVpIdentifier, 3427 mplsLdpSessionAtmLRUpperBoundVci MplsAtmVcIdentifier 3429 } 3431 mplsLdpSessionAtmLRLowerBoundVpi OBJECT-TYPE 3432 SYNTAX AtmVpIdentifier 3433 MAX-ACCESS not-accessible 3434 STATUS current 3435 DESCRIPTION 3436 "The minimum VPI number for this range." 3437 ::= { mplsLdpAtmSessionEntry 1 } 3439 mplsLdpSessionAtmLRLowerBoundVci OBJECT-TYPE 3440 SYNTAX MplsAtmVcIdentifier 3441 MAX-ACCESS not-accessible 3442 STATUS current 3443 DESCRIPTION 3444 "The minimum VCI number for this range." 3445 ::= { mplsLdpAtmSessionEntry 2 } 3447 mplsLdpSessionAtmLRUpperBoundVpi OBJECT-TYPE 3448 SYNTAX AtmVpIdentifier 3449 MAX-ACCESS read-only 3450 STATUS current 3451 DESCRIPTION 3452 "The maximum VPI number for this range." 3453 ::= { mplsLdpAtmSessionEntry 3 } 3455 mplsLdpSessionAtmLRUpperBoundVci OBJECT-TYPE 3456 SYNTAX MplsAtmVcIdentifier 3457 MAX-ACCESS read-only 3458 STATUS current 3459 DESCRIPTION 3460 "The maximum VCI number for this range." 3461 ::= { mplsLdpAtmSessionEntry 4 } 3463 --************************************************************** 3464 -- Module Conformance Statement 3465 --************************************************************** 3467 mplsLdpAtmGroups 3468 OBJECT IDENTIFIER ::= { mplsLdpAtmConformance 1 } 3470 mplsLdpAtmCompliances 3471 OBJECT IDENTIFIER ::= { mplsLdpAtmConformance 2 } 3473 -- 3474 -- Full Compliance 3475 -- 3477 mplsLdpAtmModuleFullCompliance MODULE-COMPLIANCE 3478 STATUS current 3479 DESCRIPTION 3480 "The Module is implemented with support for 3481 read-create and read-write. In other words, 3482 both monitoring and configuration 3483 are available when using this MODULE-COMPLIANCE." 3484 MODULE -- this module 3485 MANDATORY-GROUPS { 3486 mplsLdpAtmGroup 3487 } 3489 OBJECT mplsLdpEntityAtmRowStatus 3490 SYNTAX RowStatus { active(1) } 3491 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 3492 DESCRIPTION 3493 "Support for createAndWait and notInService is not required." 3495 OBJECT mplsLdpEntityAtmLRRowStatus 3496 SYNTAX RowStatus { active(1) } 3497 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 3498 DESCRIPTION 3499 "Support for createAndWait and notInService is not required." 3501 ::= { mplsLdpAtmCompliances 1 } 3503 -- 3504 -- Read-Only Compliance 3505 -- 3507 mplsLdpAtmModuleReadOnlyCompliance MODULE-COMPLIANCE 3508 STATUS current 3509 DESCRIPTION 3510 "The Module is implemented with support for 3511 read-only. In other words, only monitoring 3512 is available by implementing this MODULE-COMPLIANCE." 3513 MODULE -- this module 3514 MANDATORY-GROUPS { 3515 mplsLdpAtmGroup 3516 } 3518 OBJECT mplsLdpEntityAtmIfIndexOrZero 3519 MIN-ACCESS read-only 3520 DESCRIPTION 3521 "Write access is not required." 3523 OBJECT mplsLdpEntityAtmMergeCap 3524 MIN-ACCESS read-only 3525 DESCRIPTION 3526 "Write access is not required." 3528 OBJECT mplsLdpEntityAtmLRComponents 3529 MIN-ACCESS read-only 3530 DESCRIPTION 3531 "Write access is not required." 3533 OBJECT mplsLdpEntityAtmVcDirectionality 3534 MIN-ACCESS read-only 3535 DESCRIPTION 3536 "Write access is not required." 3538 OBJECT mplsLdpEntityAtmLsrConnectivity 3539 MIN-ACCESS read-only 3540 DESCRIPTION 3541 "Write access is not required." 3543 OBJECT mplsLdpEntityAtmDefaultControlVpi 3544 MIN-ACCESS read-only 3545 DESCRIPTION 3546 "Write access is not required." 3548 OBJECT mplsLdpEntityAtmDefaultControlVci 3549 MIN-ACCESS read-only 3550 DESCRIPTION 3551 "Write access is not required." 3553 OBJECT mplsLdpEntityAtmUnlabTrafVpi 3554 MIN-ACCESS read-only 3555 DESCRIPTION 3556 "Write access is not required." 3558 OBJECT mplsLdpEntityAtmUnlabTrafVci 3559 MIN-ACCESS read-only 3560 DESCRIPTION 3561 "Write access is not required." 3563 OBJECT mplsLdpEntityAtmStorageType 3564 MIN-ACCESS read-only 3565 DESCRIPTION 3566 "Write access is not required." 3568 OBJECT mplsLdpEntityAtmRowStatus 3569 SYNTAX RowStatus { active(1) } 3570 MIN-ACCESS read-only 3571 DESCRIPTION 3572 "Write access is not required, and active is the 3573 only status that needs to be supported." 3575 OBJECT mplsLdpEntityAtmLRMaxVpi 3576 MIN-ACCESS read-only 3577 DESCRIPTION 3578 "Write access is not required." 3580 OBJECT mplsLdpEntityAtmLRMaxVci 3581 MIN-ACCESS read-only 3582 DESCRIPTION 3583 "Write access is not required." 3585 OBJECT mplsLdpEntityAtmLRStorageType 3586 MIN-ACCESS read-only 3587 DESCRIPTION 3588 "Write access is not required." 3590 OBJECT mplsLdpEntityAtmLRRowStatus 3591 SYNTAX RowStatus { active(1) } 3592 MIN-ACCESS read-only 3593 DESCRIPTION 3594 "Write access is not required, and active is the 3595 only status that needs to be supported." 3597 ::= { mplsLdpAtmCompliances 2 } 3599 -- 3600 -- units of conformance 3601 -- 3603 mplsLdpAtmGroup OBJECT-GROUP 3604 OBJECTS { 3605 mplsLdpEntityAtmIfIndexOrZero, 3606 mplsLdpEntityAtmMergeCap, 3607 mplsLdpEntityAtmLRComponents, 3608 mplsLdpEntityAtmVcDirectionality, 3609 mplsLdpEntityAtmLsrConnectivity, 3610 mplsLdpEntityAtmDefaultControlVpi, 3611 mplsLdpEntityAtmDefaultControlVci, 3612 mplsLdpEntityAtmUnlabTrafVpi, 3613 mplsLdpEntityAtmUnlabTrafVci, 3614 mplsLdpEntityAtmStorageType, 3615 mplsLdpEntityAtmRowStatus, 3616 mplsLdpEntityAtmLRMaxVpi, 3617 mplsLdpEntityAtmLRMaxVci, 3618 mplsLdpEntityAtmLRStorageType, 3619 mplsLdpEntityAtmLRRowStatus, 3620 mplsLdpSessionAtmLRUpperBoundVpi, 3621 mplsLdpSessionAtmLRUpperBoundVci 3623 } 3624 STATUS current 3625 DESCRIPTION 3626 "Objects that apply to all MPLS LDP implementations 3627 using ATM as the Layer 2." 3628 ::= { mplsLdpAtmGroups 1 } 3630 END 3632 4.2. The MPLS-LDP-FRAME-RELAY-STD-MIB Module 3634 This MIB Module MUST be supported if LDP uses FRAME RELAY as the 3635 Layer 2 media. There are three tables in this MIB Module. Two 3636 tables are to configure LDP for using Frame Relay. These tables are 3637 the mplsLdpEntityFrameRelayTable and the 3638 mplsLdpEntityFrameRelayLRTable. 3640 The mplsLdpEntityFrameRelayTable provides a way to configure 3641 information which would be contained in the "Optional Parameter" 3642 portion of an LDP PDU Initialization Message. 3644 The mplsLdpEntityFrameRelayLRTable provides a way to configure 3645 information which would be contained in the "Frame Relay Label Range 3646 Components" portion of an LDP PDU Intialization Message, see 3647 [RFC3034] and [RFC3036]. 3649 4.2.1. The LDP Frame Relay Session Table 3651 The MPLS LDP Frame Relay Session Table is a read-only table which 3652 contains session information specific to Frame Relay. 3654 MPLS-LDP-FRAME-RELAY-STD-MIB DEFINITIONS ::= BEGIN 3656 IMPORTS 3657 OBJECT-TYPE, 3658 MODULE-IDENTITY, 3659 Unsigned32 3660 FROM SNMPv2-SMI 3661 MODULE-COMPLIANCE, 3662 OBJECT-GROUP 3663 FROM SNMPv2-CONF 3665 RowStatus, 3666 StorageType 3667 FROM SNMPv2-TC 3669 DLCI 3670 FROM FRAME-RELAY-DTE-MIB 3672 InterfaceIndexOrZero 3673 FROM IF-MIB 3675 mplsStdMIB 3676 FROM MPLS-TC-STD-MIB 3678 mplsLdpEntityLdpId, 3679 mplsLdpEntityIndex, 3680 mplsLdpPeerLdpId 3681 FROM MPLS-LDP-STD-MIB 3683 ; 3685 mplsLdpFrameRelayStdMIB MODULE-IDENTITY 3686 LAST-UPDATED "200306091200Z" -- 9 June 2003 3687 ORGANIZATION "Multiprotocol Label Switching (mpls) 3688 Working Group" 3689 CONTACT-INFO 3690 "Joan Cucchiara (jcucchiara@artel.com) 3691 Artel 3693 Hans Sjostrand (hans@ipunplugged.com) 3694 ipUnplugged 3696 James V. Luciani (james_luciani@mindspring.com) 3697 Consultant 3699 Working Group Chairs: 3700 George Swallow, email: swallow@cisco.com 3701 Loa Andersson, email: loa@pi.se 3703 MPLS Working Group, email: mpls@uu.net 3704 " 3705 DESCRIPTION 3706 "Copyright (C) The Internet Society (2003). This 3707 version of this MIB module is part of RFCXXX; see 3708 the RFC itself for full legal notices. 3710 This MIB contains managed object definitions for 3711 configuring and monitoring the Multiprotocol Label 3712 Switching (MPLS), Label Distribution Protocol (LDP), 3713 utilizing Frame Relay as the Layer 2 media." 3714 REVISION "200306091200Z" -- 9 June 2003 3715 DESCRIPTION 3716 "Initial version published as part of RFC XXXX." 3718 -- Please see the IANA Considerations Section. 3719 -- The requested mplsStdMIB subId is 6, e.g. 3720 -- ::= { mplsStdMIB 6 } 3722 ::= { mplsStdMIB XXX } -- to be assigned by IANA 3724 --**************************************************************** 3726 mplsLdpFrameRelayObjects OBJECT IDENTIFIER 3727 ::= { mplsLdpFrameRelayStdMIB 1 } 3729 mplsLdpFrameRelayConformance OBJECT IDENTIFIER 3730 ::= { mplsLdpFrameRelayStdMIB 2 } 3732 --**************************************************************** 3733 -- MPLS LDP Frame Relay Objects 3734 --**************************************************************** 3736 -- 3737 -- Ldp Entity Objects for Frame Relay 3738 -- 3740 mplsLdpEntityFrameRelayObjects OBJECT IDENTIFIER ::= 3741 { mplsLdpFrameRelayObjects 1 } 3743 mplsLdpEntityFrameRelayTable OBJECT-TYPE 3744 SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayEntry 3745 MAX-ACCESS not-accessible 3746 STATUS current 3747 DESCRIPTION 3748 "This table contains information about the 3749 Optional Parameters to specify what this Entity is 3750 going to specify for Frame Relay specific 3751 LDP Intialization Messages." 3752 ::= { mplsLdpEntityFrameRelayObjects 1 } 3754 mplsLdpEntityFrameRelayEntry OBJECT-TYPE 3755 SYNTAX MplsLdpEntityFrameRelayEntry 3756 MAX-ACCESS not-accessible 3757 STATUS current 3758 DESCRIPTION 3759 "An entry in this table represents the Frame Relay 3760 optional parameters associated with the LDP entity." 3761 INDEX { mplsLdpEntityLdpId, 3762 mplsLdpEntityIndex 3763 } 3764 ::= { mplsLdpEntityFrameRelayTable 1 } 3766 MplsLdpEntityFrameRelayEntry ::= SEQUENCE { 3767 mplsLdpEntityFrameRelayIfIndexOrZero InterfaceIndexOrZero, 3768 mplsLdpEntityFrameRelayMergeCap INTEGER, 3769 mplsLdpEntityFrameRelayLRComponents Unsigned32, 3770 mplsLdpEntityFrameRelayVcDirectionality INTEGER, 3771 mplsLdpEntityFrameRelayStorageType StorageType, 3772 mplsLdpEntityFrameRelayRowStatus RowStatus 3773 } 3775 mplsLdpEntityFrameRelayIfIndexOrZero OBJECT-TYPE 3776 SYNTAX InterfaceIndexOrZero 3777 MAX-ACCESS read-create 3778 STATUS current 3779 DESCRIPTION 3780 "This value represents either the InterfaceIndex of 3781 the 'ifLayer' where the Frame Relay Labels 'owned' by this 3782 entry were created, or 0 (zero). The value of zero 3783 means that the InterfaceIndex is not known. For example, 3784 if the InterfaceIndex is created subsequent to the 3785 Frame Relay Label's creation, then it would not be known. 3786 However, if the InterfaceIndex is known, then it must 3787 be represented by this value. 3789 If an InterfaceIndex becomes known, then the 3790 network management entity (e.g. SNMP agent) responsible 3791 for this object MUST change the value from 0 (zero) to the 3792 value of the InterfaceIndex. If an Frame Relay Label is 3793 being used in forwarding data, then the value of this 3794 object MUST be the InterfaceIndex." 3795 ::= { mplsLdpEntityFrameRelayEntry 1 } 3797 mplsLdpEntityFrameRelayMergeCap OBJECT-TYPE 3798 SYNTAX INTEGER { 3799 notSupported(0), 3800 supported(1) 3801 } 3802 MAX-ACCESS read-create 3803 STATUS current 3804 DESCRIPTION 3805 "This represents whether or not the Frame Relay merge 3806 capability is supported. This is the EXACT value for the 3807 Frame Relay Session Parameter, field M (for Frame Relay 3808 Merge Capabilities). The Frame Relay Session Parameter 3809 is an optional parameter in the Initialization Message. 3811 The description from rfc3036.txt is: 3812 'M, Frame Relay Merge Capabilities 3813 Specifies the merge capabilities of a Frame Relay switch. The 3814 following values are supported in this version of the 3815 specification: 3817 Value Meaning 3819 0 Merge not supported 3820 1 Merge supported 3822 Non-merge and merge Frame Relay LSRs may freely interoperate.' 3824 Please refer to the following reference for a complete 3825 description of this feature." 3827 REFERENCE 3828 "RFC3036, LDP Specification, Section 3.5.3 Initialization Message." 3829 ::= { mplsLdpEntityFrameRelayEntry 2 } 3831 mplsLdpEntityFrameRelayLRComponents OBJECT-TYPE 3832 SYNTAX Unsigned32 (1..65535) 3833 MAX-ACCESS read-create 3834 STATUS current 3835 DESCRIPTION 3836 "Number of Label Range Components in the Initialization 3837 message. This also represents the number of entries 3838 in the mplsLdpEntityFrameRelayLRTable which correspond 3839 to this entry. 3841 This is the EXACT value for the Frame Relay Session Parameter, 3842 field N (for Number of label range components). The Frame Relay 3843 Session Parameter is an optional parameter in 3844 the Initialization Message. 3846 The description from rfc3036.txt is: 3848 'N, Number of label range components 3849 Specifies the number of Frame Relay Label Range Components 3850 included in the TLV.' 3852 Please refer to the following reference for a complete 3853 description of this feature." 3854 REFERENCE 3855 "RFC3036, LDP Specification, Section 3.5.3 Initialization Message." 3856 ::= { mplsLdpEntityFrameRelayEntry 3 } 3858 mplsLdpEntityFrameRelayVcDirectionality OBJECT-TYPE 3859 SYNTAX INTEGER { 3860 bidirectional(0), 3861 unidirection(1) 3862 } 3863 MAX-ACCESS read-create 3864 STATUS current 3865 DESCRIPTION 3866 "If the value of this object is 'bidirectional(0)', then 3867 the LSR supports the use of a given DLCI as a label for 3868 both directions independently. If the value of 3869 this object is 'unidirectional(1)', then the LSR 3870 uses the given DLCI as a label in only one direction. 3872 This is the EXACT value for the Frame Relay Session Parameter, 3873 field D (for VC Directionality). The Frame Relay Session Parameter 3874 is an optional parameter in the Initialization Message. 3876 The description from rfc3036.txt is: 3878 'D, VC Directionality 3879 A value of 0 specifies bidirectional VC capability, meaning the 3880 LSR can support the use of a given DLCI as a label for both 3881 link directions independently. A value of 1 specifies 3882 unidirectional VC capability, meaning a given DLCI may appear 3883 in a label mapping for one direction on the link only. When 3884 either or both of the peers specifies unidirectional VC 3885 capability, both LSRs use unidirectional VC label assignment 3886 for the link as follows. The LSRs compare their LDP 3887 Identifiers as unsigned integers. The LSR with the larger LDP 3888 Identifier may assign only odd-numbered DLCIs in the range as 3889 labels. The system with the smaller LDP Identifier may assign 3890 only even-numbered DLCIs in the range as labels.' 3892 Please refer to the following reference for a complete 3893 description of this feature." 3894 REFERENCE 3895 "RFC3036, LDP Specification, Section 3.5.3 Initialization Message." 3896 ::= { mplsLdpEntityFrameRelayEntry 4 } 3898 mplsLdpEntityFrameRelayStorageType OBJECT-TYPE 3899 SYNTAX StorageType 3900 MAX-ACCESS read-create 3901 STATUS current 3902 DESCRIPTION 3903 "The storage type for this conceptual row. 3904 Conceptual rows having the value 'permanent(4)' 3905 need not allow write-access to any columnar 3906 objects in the row." 3907 DEFVAL { nonVolatile } 3908 ::= { mplsLdpEntityFrameRelayEntry 5 } 3910 mplsLdpEntityFrameRelayRowStatus OBJECT-TYPE 3911 SYNTAX RowStatus 3912 MAX-ACCESS read-create 3913 STATUS current 3914 DESCRIPTION 3915 "The status of this conceptual row. All writable 3916 objects in this row may be modified at any time, 3917 however, as described in detail in the section 3918 entitled, 'Changing Values After Session 3919 Establishment', and again described in the 3920 DESCRIPTION clause of the 3921 mplsLdpEntityAdminStatus object, 3922 if a session has been initiated with a Peer, 3923 changing objects in this table will 3924 wreak havoc with the session and interrupt 3925 traffic. To repeat again: 3926 the recommended procedure is to set the 3927 mplsLdpEntityAdminStatus to 3928 down, thereby explicitly causing a 3929 session to be torn down. Then, 3930 change objects in this entry, then set 3931 the mplsLdpEntityAdminStatus 3932 to enable which enables a new session 3933 to be initiated." 3934 ::= { mplsLdpEntityFrameRelayEntry 6 } 3936 -- 3937 -- Frame Relay Label Range Components 3938 -- 3940 mplsLdpEntityFrameRelayLRTable OBJECT-TYPE 3941 SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayLREntry 3942 MAX-ACCESS not-accessible 3943 STATUS current 3944 DESCRIPTION 3945 "This table contains information about the 3946 Optional Parameters for the Frame Relay Session 3947 in the LDP Initialization Message, specifically 3948 it contains information about the Frame Relay 3949 Label Range Components. 3951 If the value of the object 3952 'mplsLdpEntityOptionalParameters' contains the 3953 value of 'frameRelaySessionParameters(3)' then 3954 there must be at least one corresponding entry 3955 in this table." 3956 ::= { mplsLdpEntityFrameRelayObjects 2 } 3958 mplsLdpEntityFrameRelayLREntry OBJECT-TYPE 3959 SYNTAX MplsLdpEntityFrameRelayLREntry 3960 MAX-ACCESS not-accessible 3961 STATUS current 3962 DESCRIPTION 3963 "An entry in this table represents the Frame Relay 3964 Label Range Component associated with the LDP entity." 3965 INDEX { mplsLdpEntityLdpId, 3966 mplsLdpEntityIndex, 3967 mplsLdpEntityFrameRelayLRMinDlci 3968 } 3969 ::= { mplsLdpEntityFrameRelayLRTable 1 } 3971 MplsLdpEntityFrameRelayLREntry ::= SEQUENCE { 3972 mplsLdpEntityFrameRelayLRMinDlci DLCI, 3973 mplsLdpEntityFrameRelayLRMaxDlci DLCI, 3974 mplsLdpEntityFrameRelayLRLen INTEGER, 3975 mplsLdpEntityFrameRelayLRStorageType StorageType, 3976 mplsLdpEntityFrameRelayLRRowStatus RowStatus 3977 } 3979 mplsLdpEntityFrameRelayLRMinDlci OBJECT-TYPE 3980 SYNTAX DLCI 3981 MAX-ACCESS not-accessible 3982 STATUS current 3983 DESCRIPTION 3984 "The lower bound which is supported. This value should 3985 be the same as that in the Frame Relay Label Range 3986 Component's Minimum DLCI field. The value of zero 3987 is valid for the minimum DLCI field of the label." 3988 REFERENCE 3989 "RFC3034, Use of Label Switching on Frame Relay Networks 3990 Specification." 3991 ::= { mplsLdpEntityFrameRelayLREntry 1 } 3993 mplsLdpEntityFrameRelayLRMaxDlci OBJECT-TYPE 3994 SYNTAX DLCI 3995 MAX-ACCESS read-create 3996 STATUS current 3997 DESCRIPTION 3998 "The upper bound which is supported. This value should 3999 be the same as that in the Frame Relay Label Range 4000 Component's Maximum DLCI field." 4001 ::= { mplsLdpEntityFrameRelayLREntry 2 } 4003 mplsLdpEntityFrameRelayLRLen OBJECT-TYPE 4004 SYNTAX INTEGER { 4005 tenDlciBits(0), 4006 twentyThreeDlciBits(2) 4008 } 4009 MAX-ACCESS read-create 4010 STATUS current 4011 DESCRIPTION 4012 "This object specifies the length of the DLCI bits. 4014 This is the EXACT value for the Len field of the 4015 Frame Relay Label Range Component. 4017 The description from rfc3036.txt is: 4019 'Len 4020 This field specifies the number of bits of the DLCI. The 4021 following values are supported: 4023 Len DLCI bits 4025 0 10 4026 2 23 4028 Len values 1 and 3 are reserved.' 4030 Please refer to the following reference for a complete 4031 description of this feature." 4032 REFERENCE 4033 "RFC3036, LDP Specification, Section 3.5.3 Initialization Message." 4034 ::= { mplsLdpEntityFrameRelayLREntry 3 } 4036 mplsLdpEntityFrameRelayLRStorageType OBJECT-TYPE 4037 SYNTAX StorageType 4038 MAX-ACCESS read-create 4039 STATUS current 4040 DESCRIPTION 4041 "The storage type for this conceptual row. 4042 Conceptual rows having the value 'permanent(4)' 4043 need not allow write-access to any columnar 4044 objects in the row." 4045 DEFVAL { nonVolatile } 4046 ::= { mplsLdpEntityFrameRelayLREntry 4 } 4048 mplsLdpEntityFrameRelayLRRowStatus OBJECT-TYPE 4049 SYNTAX RowStatus 4050 MAX-ACCESS read-create 4051 STATUS current 4052 DESCRIPTION 4053 "The status of this conceptual row. All writable 4054 objects in this row may be modified at any time, 4055 however, as described in detail in the section 4056 entitled, 'Changing Values After Session 4057 Establishment', and again described in the 4058 DESCRIPTION clause of the 4059 mplsLdpEntityAdminStatus object, 4060 if a session has been initiated with a Peer, 4061 changing objects in this table will 4062 wreak havoc with the session and interrupt 4063 traffic. To repeat again: 4064 the recommended procedure is to set the 4065 mplsLdpEntityAdminStatus to down, thereby 4066 explicitly causing a session to be torn down. Then, 4067 change objects in this entry, then set the 4068 mplsLdpEntityAdminStatus to enable which enables 4069 a new session to be initiated." 4070 ::= { mplsLdpEntityFrameRelayLREntry 5 } 4072 -- 4073 -- MPLS LDP Frame Relay Session Information 4074 -- 4076 mplsLdpFrameRelaySessionObjects OBJECT IDENTIFIER ::= 4077 { mplsLdpFrameRelayObjects 2 } 4079 mplsLdpFrameRelaySessionTable OBJECT-TYPE 4080 SYNTAX SEQUENCE OF MplsLdpFrameRelaySessionEntry 4081 MAX-ACCESS not-accessible 4082 STATUS current 4083 DESCRIPTION 4084 "A table of Frame Relay label range intersections 4085 between the LDP Entities and LDP Peers. 4086 Each row represents a single label range intersection. 4088 NOTE: this table cannot use the 'AUGMENTS' 4089 clause because there is not necessarily a one-to-one 4090 mapping between this table and the mplsLdpSessionTable." 4091 ::= { mplsLdpFrameRelaySessionObjects 1 } 4093 mplsLdpFrameRelaySessionEntry OBJECT-TYPE 4094 SYNTAX MplsLdpFrameRelaySessionEntry 4095 MAX-ACCESS not-accessible 4096 STATUS current 4097 DESCRIPTION 4098 "An entry in this table represents information on a 4099 single label range intersection between an 4100 LDP Entity and LDP Peer. 4102 The information contained in a row is read-only." 4103 INDEX { mplsLdpEntityLdpId, 4104 mplsLdpEntityIndex, 4105 mplsLdpPeerLdpId, 4106 mplsLdpFrameRelaySessionMinDlci 4107 } 4108 ::= { mplsLdpFrameRelaySessionTable 1 } 4110 MplsLdpFrameRelaySessionEntry ::= SEQUENCE { 4111 mplsLdpFrameRelaySessionMinDlci DLCI, 4112 mplsLdpFrameRelaySessionMaxDlci DLCI, 4113 mplsLdpFrameRelaySessionLen INTEGER 4114 } 4116 mplsLdpFrameRelaySessionMinDlci OBJECT-TYPE 4117 SYNTAX DLCI 4118 MAX-ACCESS not-accessible 4119 STATUS current 4120 DESCRIPTION 4121 "The lower bound of DLCIs which are supported. 4122 The value of zero is a valid value for the 4123 minimum DLCI field of the label." 4124 REFERENCE 4125 "RFC3034, Use of Label Switching on Frame Relay Networks 4126 Specification." 4127 ::= { mplsLdpFrameRelaySessionEntry 1 } 4129 mplsLdpFrameRelaySessionMaxDlci OBJECT-TYPE 4130 SYNTAX DLCI 4131 MAX-ACCESS read-only 4132 STATUS current 4133 DESCRIPTION 4134 "The upper bound of DLCIs which are supported." 4135 ::= { mplsLdpFrameRelaySessionEntry 2 } 4137 mplsLdpFrameRelaySessionLen OBJECT-TYPE 4138 SYNTAX INTEGER { 4139 tenDlciBits(0), 4140 twentyThreeDlciBits(2) 4142 } 4143 MAX-ACCESS read-only 4144 STATUS current 4145 DESCRIPTION 4146 "This object specifies the DLCI bits." 4147 ::= { mplsLdpFrameRelaySessionEntry 3 } 4149 --**************************************************************** 4150 -- Module Conformance Statement 4151 --**************************************************************** 4153 mplsLdpFrameRelayGroups 4154 OBJECT IDENTIFIER ::= { mplsLdpFrameRelayConformance 1 } 4156 mplsLdpFrameRelayCompliances 4157 OBJECT IDENTIFIER ::= { mplsLdpFrameRelayConformance 2 } 4159 -- 4160 -- Full Compliance 4161 -- 4163 mplsLdpFrameRelayModuleFullCompliance MODULE-COMPLIANCE 4164 STATUS current 4165 DESCRIPTION 4166 "The Module is implemented with support for 4167 read-create and read-write. In other words, 4168 both monitoring and configuration 4169 are available when using this MODULE-COMPLIANCE." 4170 MODULE -- this module 4171 MANDATORY-GROUPS { 4172 mplsLdpFrameRelayGroup 4173 } 4175 OBJECT mplsLdpEntityFrameRelayRowStatus 4176 SYNTAX RowStatus { active(1) } 4177 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 4178 DESCRIPTION 4179 "Support for createAndWait and notInService is not required." 4181 OBJECT mplsLdpEntityFrameRelayLRRowStatus 4182 SYNTAX RowStatus { active(1) } 4183 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 4184 DESCRIPTION 4185 "Support for createAndWait and notInService is not required." 4187 ::= { mplsLdpFrameRelayCompliances 1 } 4189 -- 4190 -- Read-Only Compliance 4191 -- 4193 mplsLdpFrameRelayModuleReadOnlyCompliance MODULE-COMPLIANCE 4194 STATUS current 4195 DESCRIPTION 4196 "The Module is implemented with support for 4197 read-only. In other words, only monitoring 4198 is available by implementing this MODULE-COMPLIANCE." 4199 MODULE -- this module 4200 MANDATORY-GROUPS { 4201 mplsLdpFrameRelayGroup 4202 } 4204 OBJECT mplsLdpEntityFrameRelayIfIndexOrZero 4205 MIN-ACCESS read-only 4206 DESCRIPTION 4207 "Write access is not required." 4209 OBJECT mplsLdpEntityFrameRelayMergeCap 4210 MIN-ACCESS read-only 4211 DESCRIPTION 4212 "Write access is not required." 4214 OBJECT mplsLdpEntityFrameRelayLRComponents 4215 MIN-ACCESS read-only 4216 DESCRIPTION 4217 "Write access is not required." 4219 OBJECT mplsLdpEntityFrameRelayVcDirectionality 4220 MIN-ACCESS read-only 4221 DESCRIPTION 4222 "Write access is not required." 4224 OBJECT mplsLdpEntityFrameRelayStorageType 4225 MIN-ACCESS read-only 4226 DESCRIPTION 4227 "Write access is not required." 4229 OBJECT mplsLdpEntityFrameRelayRowStatus 4230 SYNTAX RowStatus { active(1) } 4231 MIN-ACCESS read-only 4232 DESCRIPTION 4233 "Write access is not required, and active is the 4234 only status that needs to be supported." 4236 OBJECT mplsLdpEntityFrameRelayLRMaxDlci 4237 MIN-ACCESS read-only 4238 DESCRIPTION 4239 "Write access is not required." 4241 OBJECT mplsLdpEntityFrameRelayLRLen 4242 MIN-ACCESS read-only 4243 DESCRIPTION 4244 "Write access is not required." 4246 OBJECT mplsLdpEntityFrameRelayLRStorageType 4247 MIN-ACCESS read-only 4248 DESCRIPTION 4249 "Write access is not required." 4251 OBJECT mplsLdpEntityFrameRelayLRRowStatus 4252 SYNTAX RowStatus { active(1) } 4253 MIN-ACCESS read-only 4254 DESCRIPTION 4255 "Write access is not required, and active is the 4256 only status that needs to be supported." 4257 ::= { mplsLdpFrameRelayCompliances 2 } 4259 -- 4260 -- units of conformance 4261 -- 4263 mplsLdpFrameRelayGroup OBJECT-GROUP 4264 OBJECTS { 4265 mplsLdpEntityFrameRelayIfIndexOrZero, 4266 mplsLdpEntityFrameRelayMergeCap, 4267 mplsLdpEntityFrameRelayLRComponents, 4268 mplsLdpEntityFrameRelayVcDirectionality, 4269 mplsLdpEntityFrameRelayStorageType, 4270 mplsLdpEntityFrameRelayRowStatus, 4271 mplsLdpEntityFrameRelayLRMaxDlci, 4272 mplsLdpEntityFrameRelayLRLen, 4273 mplsLdpEntityFrameRelayLRStorageType, 4274 mplsLdpEntityFrameRelayLRRowStatus, 4275 mplsLdpFrameRelaySessionMaxDlci, 4276 mplsLdpFrameRelaySessionLen 4277 } 4278 STATUS current 4279 DESCRIPTION 4280 "Objects that apply to all MPLS LDP implementations 4281 using Frame Relay as the Layer 2." 4282 ::= { mplsLdpFrameRelayGroups 1 } 4284 END 4286 4.3. The MPLS-LDP-GENERIC-STD-MIB Module 4288 This MIB Module MUST be supported if LDP uses a Per Platform Label 4289 Space. This MIB Module contains a Label Range (LR) table for 4290 configuring Mpls Generic Label Ranges. This table is 4291 mplsLdpEntityGenericLRTable. Although the LDP Specification does not 4292 provide a way for configuring Label Ranges for Generic Labels, the 4293 MIB does provide a way to reserve a range of generic labels because 4294 this was thought to be useful by the working group. 4296 MPLS-LDP-GENERIC-STD-MIB DEFINITIONS ::= BEGIN 4298 IMPORTS 4300 OBJECT-TYPE, 4301 MODULE-IDENTITY, 4302 Unsigned32 4303 FROM SNMPv2-SMI 4305 MODULE-COMPLIANCE, 4306 OBJECT-GROUP 4307 FROM SNMPv2-CONF 4309 RowStatus, 4310 StorageType 4311 FROM SNMPv2-TC 4313 InterfaceIndexOrZero 4314 FROM IF-MIB 4316 mplsStdMIB 4317 FROM MPLS-TC-STD-MIB 4319 mplsLdpEntityLdpId, 4320 mplsLdpEntityIndex 4321 FROM MPLS-LDP-STD-MIB 4322 ; 4324 mplsLdpGenericStdMIB MODULE-IDENTITY 4325 LAST-UPDATED "200306091200Z" -- 9 June 2003 4326 ORGANIZATION "Multiprotocol Label Switching (mpls) 4327 Working Group" 4328 CONTACT-INFO 4329 "Joan Cucchiara (jcucchiara@artel.com) 4330 Artel 4332 Hans Sjostrand (hans@ipunplugged.com) 4333 ipUnplugged 4335 James V. Luciani (james_luciani@mindspring.com) 4336 Consultant 4338 Working Group Chairs: 4339 George Swallow, email: swallow@cisco.com 4340 Loa Andersson, email: loa@pi.se 4342 MPLS Working Group, email: mpls@uu.net 4343 " 4344 DESCRIPTION 4345 "Copyright (C) The Internet Society (2003). This 4346 version of this MIB module is part of RFCXXX; see 4347 the RFC itself for full legal notices. 4349 This MIB contains managed object definitions for 4350 configuring and monitoring the Multiprotocol Label 4351 Switching (MPLS), Label Distribution Protocol (LDP), 4352 utilizing ethernet as the Layer 2 media." 4353 REVISION "200306091200Z" -- 9 June 2003 4354 DESCRIPTION 4355 "Initial version published as part of RFC XXXX." 4357 -- Please see the IANA Considerations Section. 4358 -- The requested mplsStdMIB subId is 7, e.g. 4359 -- ::= { mplsStdMIB 7 } 4361 ::= { mplsStdMIB XXX } -- to be assigned by IANA 4363 --**************************************************************** 4364 mplsLdpGenericObjects 4365 OBJECT IDENTIFIER ::= { mplsLdpGenericStdMIB 1 } 4366 mplsLdpGenericConformance 4367 OBJECT IDENTIFIER ::= { mplsLdpGenericStdMIB 2 } 4369 --**************************************************************** 4370 -- MPLS LDP GENERIC Objects 4371 --**************************************************************** 4373 -- 4374 -- Ldp Entity Objects for Generic Labels 4375 -- 4377 mplsLdpEntityGenericObjects OBJECT IDENTIFIER ::= 4378 { mplsLdpGenericObjects 1 } 4380 -- 4381 -- The MPLS LDP Entity Generic Label Range Table 4382 -- 4384 mplsLdpEntityGenericLRTable OBJECT-TYPE 4385 SYNTAX SEQUENCE OF MplsLdpEntityGenericLREntry 4386 MAX-ACCESS not-accessible 4387 STATUS current 4388 DESCRIPTION 4389 "The MPLS LDP Entity Generic Label Range (LR) 4390 Table. 4392 The purpose of this table is to provide a mechanism 4393 for configurating a contiguous range of generic labels, 4394 or a 'label range' for LDP Entities. 4396 LDP Entities which use Generic Labels must have at least 4397 one entry in this table. In other words, this table 4398 'extends' the mpldLdpEntityTable for Generic Labels." 4399 ::= { mplsLdpEntityGenericObjects 1 } 4401 mplsLdpEntityGenericLREntry OBJECT-TYPE 4402 SYNTAX MplsLdpEntityGenericLREntry 4403 MAX-ACCESS not-accessible 4404 STATUS current 4405 DESCRIPTION 4406 "A row in the LDP Entity Generic Label 4407 Range (LR) Table. One entry in this table contains 4408 information on a single range of labels 4409 represented by the configured Upper and Lower 4410 Bounds pairs. NOTE: there is NO corresponding 4411 LDP message which relates to the information 4412 in this table, however, this table does provide 4413 a way for a user to 'reserve' a generic label 4414 range. 4416 NOTE: The ranges for a specific LDP Entity 4417 are UNIQUE and non-overlapping. 4419 A row will not be created unless a unique and 4420 non-overlapping range is specified." 4421 INDEX { mplsLdpEntityLdpId, 4422 mplsLdpEntityIndex, 4423 mplsLdpEntityGenericLRMin, 4424 mplsLdpEntityGenericLRMax 4425 } 4426 ::= { mplsLdpEntityGenericLRTable 1 } 4428 MplsLdpEntityGenericLREntry ::= SEQUENCE { 4429 mplsLdpEntityGenericLRMin Unsigned32, 4430 mplsLdpEntityGenericLRMax Unsigned32, 4431 mplsLdpEntityGenericLabelSpace INTEGER, 4432 mplsLdpEntityGenericIfIndexOrZero InterfaceIndexOrZero, 4433 mplsLdpEntityGenericLRStorageType StorageType, 4434 mplsLdpEntityGenericLRRowStatus RowStatus 4435 } 4437 mplsLdpEntityGenericLRMin OBJECT-TYPE 4438 SYNTAX Unsigned32(0..1048575) 4439 MAX-ACCESS not-accessible 4440 STATUS current 4441 DESCRIPTION 4442 "The minimum label configured for this range." 4443 ::= { mplsLdpEntityGenericLREntry 1 } 4445 mplsLdpEntityGenericLRMax OBJECT-TYPE 4446 SYNTAX Unsigned32(0..1048575) 4447 MAX-ACCESS not-accessible 4448 STATUS current 4449 DESCRIPTION 4450 "The maximum label configured for this range." 4451 ::= { mplsLdpEntityGenericLREntry 2 } 4453 mplsLdpEntityGenericLabelSpace OBJECT-TYPE 4454 SYNTAX INTEGER { 4455 perPlatform(1), 4456 perInterface(2) 4457 } 4458 MAX-ACCESS read-create 4459 STATUS current 4460 DESCRIPTION 4461 "This value of this object is perPlatform(1), then 4462 this means that the label space type is 4463 per platform. 4465 If this object is perInterface(2), then this 4466 means that the label space type is per Interface." 4467 REFERENCE 4468 "RFC3036, LDP Specification, Section 2.2.1, 4469 Label Spaces." 4470 DEFVAL { perPlatform } 4471 ::= { mplsLdpEntityGenericLREntry 3 } 4473 mplsLdpEntityGenericIfIndexOrZero OBJECT-TYPE 4474 SYNTAX InterfaceIndexOrZero 4475 MAX-ACCESS read-create 4476 STATUS current 4477 DESCRIPTION 4478 "This value represents either the InterfaceIndex of 4479 the 'ifLayer' where these Generic Label would be created, 4480 or 0 (zero). The value of zero means that the 4481 InterfaceIndex is not known. For example, if 4482 the InterfaceIndex is created subsequent to 4483 the Generic Label's creation, then it would not be 4484 known. However, if the InterfaceIndex 4485 is known, then it must be represented by this value. 4487 If an InterfaceIndex becomes known, then the 4488 network management entity (e.g. SNMP agent) responsible 4489 for this object MUST change the value from 0 (zero) to the 4490 value of the InterfaceIndex." 4491 ::= { mplsLdpEntityGenericLREntry 4 } 4493 mplsLdpEntityGenericLRStorageType OBJECT-TYPE 4494 SYNTAX StorageType 4495 MAX-ACCESS read-create 4496 STATUS current 4497 DESCRIPTION 4498 "The storage type for this conceptual row. 4499 Conceptual rows having the value 'permanent(4)' 4500 need not allow write-access to any columnar 4501 objects in the row." 4502 DEFVAL { nonVolatile } 4503 ::= { mplsLdpEntityGenericLREntry 5 } 4505 mplsLdpEntityGenericLRRowStatus OBJECT-TYPE 4506 SYNTAX RowStatus 4507 MAX-ACCESS read-create 4508 STATUS current 4509 DESCRIPTION 4510 "The status of this conceptual row. All writable 4511 objects in this row may be modified at any time, 4512 however, as described in detail in the section 4513 entitled, 'Changing Values After Session 4514 Establishment', and again described in the 4515 DESCRIPTION clause of the mplsLdpEntityAdminStatus object, 4516 if a session has been initiated with a Peer, 4517 changing objects in this table will 4518 wreak havoc with the session and interrupt traffic. 4519 To repeat again: the recommended procedure is 4520 to set the mplsLdpEntityAdminStatus to 4521 down, thereby explicitly causing a 4522 session to be torn down. Then, change objects 4523 in this entry, then set the mplsLdpEntityAdminStatus 4524 to enable which enables a new session to be initiated. 4526 There must exist at least one entry in this 4527 table for every LDP Entity that has a 4528 generic label configured." 4529 ::= { mplsLdpEntityGenericLREntry 6 } 4531 --**************************************************************** 4532 -- Module Conformance Statement 4533 --**************************************************************** 4535 mplsLdpGenericGroups 4536 OBJECT IDENTIFIER ::= { mplsLdpGenericConformance 1 } 4538 mplsLdpGenericCompliances 4539 OBJECT IDENTIFIER ::= { mplsLdpGenericConformance 2 } 4541 -- 4542 -- Full Compliance 4543 -- 4545 mplsLdpGenericModuleFullCompliance MODULE-COMPLIANCE 4546 STATUS current 4547 DESCRIPTION 4548 "The Module is implemented with support for 4549 read-create and read-write. In other words, 4550 both monitoring and configuration 4551 are available when using this MODULE-COMPLIANCE." 4552 MODULE -- this module 4553 MANDATORY-GROUPS { 4554 mplsLdpGenericGroup 4555 } 4557 OBJECT mplsLdpEntityGenericLRRowStatus 4558 SYNTAX RowStatus { active(1) } 4559 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 4560 DESCRIPTION 4561 "Support for createAndWait and notInService is not required." 4563 ::= { mplsLdpGenericCompliances 1 } 4565 -- 4566 -- Read-Only Compliance 4567 -- 4569 mplsLdpGenericModuleReadOnlyCompliance MODULE-COMPLIANCE 4570 STATUS current 4571 DESCRIPTION 4572 "The Module is implemented with support for 4573 read-only. In other words, only monitoring 4574 is available by implementing this MODULE-COMPLIANCE." 4575 MODULE -- this module 4576 MANDATORY-GROUPS { 4577 mplsLdpGenericGroup 4578 } 4580 OBJECT mplsLdpEntityGenericLabelSpace 4581 MIN-ACCESS read-only 4582 DESCRIPTION 4583 "Write access is not required." 4585 OBJECT mplsLdpEntityGenericIfIndexOrZero 4586 MIN-ACCESS read-only 4587 DESCRIPTION 4588 "Write access is not required." 4590 OBJECT mplsLdpEntityGenericLRStorageType 4591 MIN-ACCESS read-only 4592 DESCRIPTION 4593 "Write access is not required." 4595 OBJECT mplsLdpEntityGenericLRRowStatus 4596 SYNTAX RowStatus { active(1) } 4597 MIN-ACCESS read-only 4598 DESCRIPTION 4599 "Write access is not required, and active is the 4600 only status that needs to be supported." 4602 ::= { mplsLdpGenericCompliances 2 } 4604 -- 4605 -- units of conformance 4606 -- 4608 mplsLdpGenericGroup OBJECT-GROUP 4609 OBJECTS { 4610 mplsLdpEntityGenericLabelSpace, 4611 mplsLdpEntityGenericIfIndexOrZero, 4612 mplsLdpEntityGenericLRStorageType, 4613 mplsLdpEntityGenericLRRowStatus 4614 } 4615 STATUS current 4616 DESCRIPTION 4617 "Objects that apply to all MPLS LDP implementations 4618 using Generic Labels as the Layer 2." 4619 ::= { mplsLdpGenericGroups 1 } 4621 END 4623 5. Revision History 4625 NOTE TO RFC-Editor: before publishing this document as an RFC, 4626 please remove this Revision History (change log) section. sp 4628 5.1. Changes from 4630 Renamed the MIB module to include Std and also updated the IANA 4631 Considerations Section to use mplsStdMIB. 4633 Updated per Bert's email May 9th, with 2 exceptions: 1) did not yet 4634 update #3 from that email and 2) did not yet review all the 4635 InetAddressType and InetAddress objects to make sure that 4636 descriptions were per rfc3291. 4638 Changed Ses to Session for clarity. 4640 5.2. Changes from 4642 Added the new MIB boiler plate and associated MIB reference changes. 4644 Reworked the OID tree structure so that the Modules only have the 4645 mplsMIB subid dependency. This was discussed in mpls wg email 4646 (discussion was mostly between Bert, Tom and Joan). 4648 Added IANA Considerations section. This contains 4 subsections, one 4649 per MIB module. 4651 Updated and added new references as needed. 4653 Changed mplsMIB subid values to agree with the latest "Multiprotocol 4654 Label Switching (MPLS) Management Overview" document, [MPLSMGMT]. 4656 Moved MIB modules around so that they would appear in subId order. 4657 The Generic MIB module is shown last, since the subid is 7 (which is 4658 the last (and largest) subid requested by IANA. 4660 5.2.1. Changes based on MIB Doctor Review Comments 4662 The following changes are based on comments from the MIB DR Review. 4663 The comments are from email to the mpls working group dated, Dec 6, 4664 2002. These comments are quoted and prefaced by "REQ: comment goes 4665 here", and then followed by our resolution. 4667 "REQ: - missing IPR section". RSP: it has been added. 4669 "REQ: - Security considerations probably needs more work 4670 Security ADs want you to explain what the vulnerabilities/risks 4671 are and what to do against them. 4672 Also for read only objects, pls list each (group of) object(s) 4673 and explain what sensitivity attributes they have". RSP: Done. We 4674 added subsections here since the Security template is MIB Module 4675 based and it seemed to us more clear to do a subsection per MIB 4676 Module. 4678 "REQ: - pls do the consistency checking for descriptors and all 4679 that". RSP: believe this to be done. Changed Gen to Generic 4680 everywhere, changed Fr to FrameRelay, changed RO to ReadOnly. 4681 Changed Sessions to Ses everywhere. Reviewed tables to make sure 4682 they were prefixed consistently. Added more references, used more 4683 TCs and other stuff. 4685 "REQ: - sect 3.5 1st sentence, s/would be/are/ ??". RSP: done. 4687 "REQ: - sect 3.5 2nd para first sentence s/initiation/initiate/ ". 4688 RSP: done. 4690 "REQ: - section 3.5.2 s/mpsl/mpls/". RSP: done. 4692 "REQ: - mplsXxxIndexNext 4693 See my comments on FTN MIB and LSR MIB on these type of objects 4694 Best to use something aka rfc3289 ". RSP: We have imported the 4695 IndexInteger and IndexIntegerNextFree TCs (from rfc3289.txt). NOTE: 4696 we do not like the names of these TCs because they use the term 4697 Integer when the values are Unsigned32. Would prefer new TCs with 4698 IndexUnsigned32 and IndexUnsigned32NextFree. 4700 "REQ:- RowStatus and StorageType objects 4701 see my comments about similar objects in LSR MIB 4702 for StorageType might also want to add a DEFVAL ". RSP: Added 4703 descriptive text to the RowStatus objects to specify which columns 4704 can be changed when row is active. Added descriptive text to the 4705 StorageType objects to specify what happens when the StorageType is 4706 permanent. Also added DEFVALs for the StorageType objects. 4708 "REQ: - mplsLdpNotifications ... { mplsLdpMib 2 } 4709 why not { mplsLdpMib 0} so that it is right away the prefix? 4710 I believe LSR MIB does it that way now. You may want to do 4711 it consistently for all notifications. 4712 I can live with either way, but prefer them to be shorter OIDs.". 4714 RSP: We changed this to follow what LSR MIB does (i.e. 4715 mplsLdpNotifications 0) for shorter OIDs..PP "REQ: - 4716 mplsXxxLastChange 4717 does that time stamp only get changed if an addition/deletion takes 4718 place? Not if something gets changed via a SNMP SET command? 4719 I think I'd prefer to also see changes (modifications) via SET. 4720 But in any event, be very explicit about if those are included or 4721 not.". RSP: All Last change object DESCRIPTIONs have been 4722 updated to be very specific. 4724 "REQ:- mplsLdpLspType 4725 All that stuff in the DESCRIPTION clause is just a repeat of the 4726 TC DESCRIPTION clause. Seems not needed to me. What if a value 4727 gets added later... how do you stay in sync?". RSP: This has 4728 been fixed. 4730 "REQ: - mplsFecAddrLength 4731 Should that be of SYNTAX InetAddressPrefixLength as per RFC3291?". 4732 RSP: yes, fixed. 4734 "REQ: - mplsFecAddrFamily and mplsFecAddr 4735 These are strange. The DESCRIPTIONS are certainly not meeting the 4736 requirements as specified in RFC3291. At other places you do it 4737 correct, so you do understand what is required I think.". RSP: 4738 changed to have a better descriptions. Should note that the TLVs in 4739 the LDP Specification use Address Family Numbers and are still 4740 referring to RFC1700. 4742 "REQ: - mplsLdpLspFecTable claims to be a read-only table. 4743 Yet you have a read-create RowStatus object in it.". RSP: fixed. 4745 "REQ: - mplsLdpSessionUp and mplsLdpSessionDown 4746 Is it not better to just have one notification, namely a 4747 mplsLdpSessionStateChange and then the mplsLdpSesState object will 4748 explain what the change is?". RSP: We prefer to leave it this 4749 way. There are some 3rd Party applications that try to resolve 4750 Notifications, so you see one for down, then resolve this by seeing 4751 another one for up. Granted, these 3rd party apps could be coded to 4752 parse the varbind within the trap, but then this requires coding 4753 whereas having 2 distinct notifications is easier on the developer. 4754 Granted, this maybe makes the MIB design more cumbersome. If this is 4755 a blocking issue, then we will change it. 4757 "REQ:- COMPLIANCE section. I hope that INT ADs are OK with making 4758 IPv6 4759 addresses optional. Is that cause current LDP only supports IPv4? 4760 If so you may want to add that as an explanation.". RSP: IPv6 4761 was made mandatory, also supported in MPLS LDP Spec (rfc3036.txt). 4763 Continue with MIB Dr Comments for the MPLS-LDP-GENERIC-MIB. 4765 "REQ:- same on mplsXXXIndexNext and RowStatus and STorageType 4766 objects". RSP: These hdescriptions have been updated. It should 4767 be noted, that these should be EXACTLY the same as the 4768 mplsLdpEntityTable since the Label Range Tables extend the Entity 4769 Table. "REQ:- this looks wierd: 4770 ::= { mplsMib 6 } -- to be assigned 4771 use cc instead of 6 if you want IANA to assign, and do tell 4772 -- to be assigned by IANA 4773 and write something about it in an IANA Considerations Section if 4774 this is what you want.". RSP: Added more comments, and added an 4775 IANA Considerations Section. "REQ:- mplsGenModuleROCompliance 4776 I would call it mplsGenModuleReadOnlyCompliance 4777 You have used ReadOnly and Full in other places/mib modules and 4778 it is good to be clear and consistent". RSP: done. 4780 MIB Doctor Review comments for ATM. 4782 "REQ:- s/Moduel/Module/". RSP: done. 4784 "REQ:- same on mplsXXXIndexNext and RowStatus and STorageType 4785 objects". RSP: done. 4787 "REQ:- this looks wierd: 4788 ::= { mplsMib 4 } -- to be assigned 4789 use cc instead of 4 if you want IANA to assign, and do tell 4790 -- to be assigned by IANA 4791 and write something about it in an IANA Considerations Section if 4792 this is what you want.". RSP: done. 4794 "REQ:- See earlier remark on Notifications (use zero instead of 2 4795 right away)". RSP:Removed this branch because there aren't any 4796 notifications in this MIB module. 4798 "REQ:- There are still some INTEGER enumerations that start with zero 4799 It is not a BLOCKING problem... but if acceptable, pls make it 4800 start 4801 at 1 (as you have done vor various others of these enumerations)". 4802 RSP: We would rather leave these enums starting with zero. (There are 4803 2 of them in the ATM Module). The reason for leaving them is because 4804 the value zero is what the protocol uses. We have added REFERENCES 4805 to these objects and more info in the descriptions themselves. We 4806 believe it is in the best interest of developers to start enums at 4807 zero. The INET-ADDRESS-MIB uses the value zero, and since we are 4808 already required to use that MIB, there is precedence for zero in an 4809 enum where it makes sense. We believe the value of zero makes sense 4810 for where it is being used in this MIB module. 4812 "REQ:- mplsXxxxROCompliance -> better mplsXxxxReadOnlyCompliance". 4813 RSP: done. 4815 "REQ:- some formatting problems with DEFVAL lines being split on 2 4816 lines?". RSP: fixed. 4818 MIB Doctor Review comments for FrameRelay 4820 "REQ:- consistency in descriptors (FrameRelay vs FR etc)". RSP: 4821 done. "REQ:- same on mplsXXXIndexNext and RowStatus and STorageType 4822 objects". RSP: done. "REQ:- this looks wierd: 4823 ::= { mplsMib 5 } -- to be assigned 4824 use cc instead of 5 if you want IANA to assign, and do tell 4825 -- to be assigned by IANA 4826 and write something about it in an IANA Considerations Section if 4827 this is what you want.". RSP: done. "REQ:- See earlier remark 4828 on Notifications (use zero instead of 2 right away)". RSP:Removed 4829 this branch because there aren't any notifications in this MIB 4830 module. 4832 "REQ:- There are still some INTEGER enumerations that start with zero 4833 It is not a BLOCKING problem... but if acceptable, pls make it 4834 start 4835 at 1 (as you have done vor various others of these enumerations)". 4836 RSP: We would rather leave these enums starting with zero. (There are 4837 4 of them in the Frame Relay Module). The reason for leaving them is 4838 because the value zero is what the protocol uses. We have added 4839 REFERENCES to these objects and more info in the descriptions 4840 themselves. We believe it is in the best interest of developers to 4841 start enums at zero. The INET-ADDRESS-MIB uses the value zero, and 4842 since we are already required to use that MIB, there is precedence 4843 for zero in an enum where it makes sense. We believe the value of 4844 zero makes sense for where it is being used in this MIB module. 4846 "REQ:- mplsLdpEntityFrLRComponents OBJECT-TYPE 4847 SYNTAX Unsigned32 (1..65535) 4848 MAX-ACCESS read-create 4849 STATUS current 4850 DESCRIPTION 4851 "Number of Label Range Components in the Initialization 4852 message. This also represents the number of entries 4853 in the mplsLdpEntityConfFrLRTable which correspond 4854 to this entry." 4855 Where is this mplsLdpEntityConfFrLRTable ??". RSP: fixed. 4856 "REQ:- I see the xxxDlci index objects start at zero. 4857 Pls add to DESCRIPTION clauses why zero must be an index.". RSP: 4858 Since we are using DLCI and the value of zero is valid for a DLCI. A 4859 statement was added about this. Also, used the DLCI TC from 4860 rfc2115.txt to make this more clear. NOTE: the MPLS-LDP-ATM-MIB 4861 module uses an index of the VP which can also take on the value of 4862 zero. A statement was added to this Index also. "REQ:- 4863 mplsXxxxROCompliance -> better mplsXxxxReadOnlyCompliance". RSP: 4864 done. 4866 5.3. Changes from 4868 The following changes are from the IESG MIB review. 4870 Changed "Label Switch Router" to "Label Switching Router". 4872 Spelling errors fixed (unlabelled, atttempt, subsytem). 4874 Changed some of the enums to start at 1, instead of zero: 4875 mplsLdpPeerLoopDetectionForPV and mplsLdpEntityOperStatus. 4877 Added REFERENCE clauses. 4879 Added a timestamp object for mplsLdpSesState changes. 4881 Changed NMS to command generator as defined in RFC2571. 4883 Added a lastChange objects: mplsLdpEntityLastChange and 4884 mplsLdpPeerLastChange. 4886 Added TEXTUAL-CONVENTIONS for MplsLabelDistributionMethod and 4887 MplsRetentionMode. These TCs have been incorporated into draft-ietf- 4888 mpls-tc-mib-04.txt. 4890 Divided up the one MIB MODULE into 3 additional modules for a total 4891 of 4 MIB MODULES: 1) mplsLdpMIB, 2) mplsLdpGenericMIB which includes 4892 objects pertaining to Ethernet as the L2, 3) mplsLdpAtmMIB which 4893 includes objects pertaining to ATM as the L2, and 4) 4894 mplsLdpFrameRelayMIB which includes objects pertaining to Frame Relay 4895 as the L2. 4897 Also, reduced the number of objects by creating the mplsLdpLspTable 4898 and removing the Mapping tables. 4900 In section 3.1 changed "where each row in the table initiates" to 4901 "where each row in the table represents". 4903 Updated Reference Section and divided them into Normative vs. 4904 Informative. 4906 Removed the MplsGenAddress TC and used the INET-ADDRESS-MIB's 4907 InetAddress TC. Objects using this TC are: 4908 mplsLdpEntityTargetPeerAddr, mplsFecAddr, and 4909 mplsLdpSesPeerNextHopAddr and are noted in the conformance statements 4910 supporting: unknown(0), ipv4(1), and ipv6(2). 4912 Removed AddressFamilyNumbers TC and used InetAddressType TC from the 4913 INET-ADDRESS-MIB. One of the MIB compilers as a warning because 4914 apparently one is expected to use InetAddressType and InetAddress 4915 together (although, think this restriction is too restrictive). Also, 4916 removed the reference for the Address Family Numbers MIB. 4918 Changed the name TargPeer to TargetPeer. 4920 Removed the Enable/Disable trap objects: 4921 mplsLdpEntityPVLMisTrapEnable, and mplsLdpSesUpDownTrapEnable. RFC 4922 2573 should be used to eable/disable traps. 4924 Removed the import for "transmission" and instead, imported "mplsMIB 4925 from the MPLS-TC-MIB". 4927 Changed mplsLdpEntityPVL to mplsLdpEntityPathVectorLimit and updated 4928 the DESCRIPTION clause. Also, the PVL abbreviation was expanded to 4929 PathVectorLimit for other objects. 4931 Combined the objects: mplsLdpPeerLoopDectionForPV and mplsLdpPeerPVL 4932 into one object: mplsLdpPeerPathVectorLimit and updated the 4933 DESCRIPTION clause. 4935 mplsLdpEntityTcpDscPort uses InetPortNumber TC from the INET-ADDRESS- 4936 MIB. Likewise, mplsLdpEntityUdpDscPort uses the InetPortNumber TC 4937 from the INET-ADDRESS-MIB. Also a REFERENCE clause was added. 4939 The mplsLdpEntityMaxPduLength object has the SYNTAX range changed to 4940 start at 256. Also the DESCRIPTION clause was updated. 4942 The mplsLdpSesMaxPduLen object's name was changed to 4943 mplsLdpSesMaxPduLength and a UNITS clause was added, and the 4944 DESCRIPTION clause was updated. This object is related to the 4945 mplsLdpEntityMaxPduLength object. 4947 The mplsLdpEntityKeepAliveHoldTimer and mplsLdpEntityHelloHoldTimer 4948 DESCRIPTION clause was changed from "The two octet value" to "The 4949 16-bit integer value". 4951 The mplsLdpEntityHelloHoldTimer object's DESCRIPTION clause was 4952 updated. 4954 A range of Integer32(0..100) was added to the SYNTAX clause of the 4955 mplsLdpEntityInitSesThreshold object. Also, the DESCRIPTION clause 4956 of this object was updated. 4958 The mplsLdpEntityOptionalParameters object was renamed to 4959 mplsLdpEntityLabelType. 4961 Updated the mplsLdpEntityAdminStatus and mplsLdpEntityRowStatus 4962 objects. RowStatus now reflects the status of the row, and Admin 4963 status controls enabling/disabling the entry. 4965 Updated the DESCRIPTION clauses for the objects in the 4966 mplsLdpEntityStatsTable to refer to the 4967 mplsLdpEntityDiscontinuityTime object. 4969 Changed StorType to StorageType. 4971 5.4. Changes from 4973 There were three types of changes: the first change was that all the 4974 MPLS Textual Conventions from this MIB, the LSR and MPLS-TE MIBs were 4975 moved into a new document [MPLSTCMIB], "draft-ietf-mpls-tc- 4976 mib-00.txt". The Textual Conventions are now IMPORTED from 4977 [MPLSTCMIB]. The second type of change was updates based on comments 4978 from the IESG. These changes will be discussed below. The third 4979 type of changes were based on minor editorial changes from the co- 4980 authors. 4982 The "Introduction" and "Structure of the MIB" sections were reworded 4983 since they were repetitive. 4985 The "Overview" was rearranged. 4987 References were added to "The LDP Entity ATM Objects" and "The LDP 4988 Entity Frame Relay Objects" Sections. 4990 The Working Group mailing list and Chairs were added to the CONTACT- 4991 INFO. 4993 Updated the DESCRIPTION clause for the "mplsLdpEntityLdpId" object. 4995 Updated the mplsLdpEntityProtocolVersion to include a range 4996 (1..65535). 4998 Updated the "References" Section. 5000 Running the MIB through the smilint MIB compiler showed that some 5001 object names were longer than 32 characters, these were shortened to 5002 32 characters or fewer. 5004 The following changes were from the co-authors. 5006 Other minor editorial changes such as fixing typographical errors, 5007 and removing MIB comments which are no longer meaningful. 5009 Page 17 (also page 46) the description was enhanced to describe the 5010 version field in the LDP header from RFC3036. 5012 Removed WellKnown from the tcp and upd port names. It's the ports 5013 that get set, and the default value is the well known (actually the 5014 registered) port number. 5016 mplsLdpEntityInitSesTrapEnable object is useless and was removed 5017 since setting mplsLdpEntityInitSesThreshold=0 acheives the same 5018 thing. Also removed it from the descriptive text in section 3. 5020 Page 47, mplsLdpSessionDiscontinuityTime The initial value of this 5021 was changed to be sysUpTime instead of zero. sysUpTime for when the 5022 session starts is more meaningful and was added to the Session 5023 Up/Down Traps also. Also, added the Session specific stats to the 5024 up/down traps. 5026 5.5. Changes from 5028 All changes were from the second last call which took place Thursday, 5029 July 20th, until Thursday, July 27th, 2000 and are described in the 5030 remainder of this section. 5032 Remove the reference to the MPLS framework document. 5034 Add an mplsFecIndexNext type of object. 5036 Change the conformance of the FEC table objects to be part of the 5037 mplsLdpGeneralGroup. 5039 The mplsLdpEntityConfGenericTable is no longer needed because the 5040 functionality has been absorbed by the 5041 mplsLdpEntityConfGenericLabelRangeTable. The 5042 mplsLdpEntityConfGenericTable has been removed and the front section 5043 was updated accordingly. 5045 Other editorial issues, updating references, typos and so forth. 5047 5.6. Changes from 5049 The majority of changes in this revision are based on Last Call 5050 comments which were received during the last call from Thursday, 5051 March 9, 2000 to Friday, March 17, 2000, or slightly thereafter. 5052 Also, changes were made to agree with the latest specifications. 5053 These changes are described in this section. 5055 Changes due to draft-ietf-mpls-ldp-07.txt and draft-ietf-mpls- 5056 ldp-08.txt. Specifically, removing references to IPv4/IP and using 5057 router id, as appropriate. 5059 Removed vpMerge and vpAndVcMerge choices from the object, 5060 mplsLdpEntityAtmMergeCap. VP Merge is not described in [RFC3036]. 5062 The LIB Table was removed and replaced by mapping tables to map LDP 5063 LSPs created by LDP sessions to the mplsInSegment, mplsOutSegment and 5064 mplsXC tables in the LSR MIB. The conformance section was updated 5065 to include a Mapping Group which is to be implemented iff these LSR 5066 MIB tables (mplsInSegmentTable, mplsOutSegmentTable and mplsXCTable) 5067 are implemented. 5069 The front section was updated to include information on the Generic 5070 label table. 5072 Added more in the front section on on Row 5073 Creation/adminStatus/OperStatus in the LDP Entity and related tables. 5075 Added a generic label range table. NOTE: there is NO corresponding 5076 LDP message which relates to the information in this table, however, 5077 this table does provide a way for a user to 'reserve' a generic label 5078 range. 5080 A new TEXTUAL-CONVENTION, MplsAtmVcIdentifier was added. This TC has 5081 the same upper bounds as AtmVcIdentifier (from rfc2514) except that 5082 the lower bound is 32 (and not 0). The lower bound is 32 since this 5083 value is specified by [RFC3035]. 5085 Removed the scalar object mplsLsrLabelRetentionMode and added 5086 mplsLdpEntityLabelRetentionMode. The change was made to allow 5087 configuring the retention mode on a per LDP Entity basis, as opposed 5088 for the entire LSR. 5090 Typo in section 3.5.2 was fixed. 5092 Typo in the mplsLdpSessionUp notification description was fixed. 5094 Section 'LDP Notifications' was expanded to cover both the 5095 'mplsLdpSessionUp' and 'mplsLdpSessionDown' traps. Also, the objects 5096 which enable and disable these traps have been described in this 5097 Section: 5099 The 'mplsLdpEntityHopCountLoopDetection' object and the 5100 'mplsLdpEntityHopCount' object have been combined into the new 5101 object, 'mplsLdpEntityHopCountLimit'. 5103 MplsLabel has been updated to reflect the VPI value of 12 bits and 5104 not 8. 5106 Added DEFVAL clause to the 'mplsLdpEntityWellKnownDiscoveryPort' 5107 object. The default value is 646. 5109 Added UNITS and DEFVAL clauses to the 'mplsLdpEntityMaxPduLength' 5110 object. The default value is 4096 and the units is octets. 5112 Added DEFVAL clause to 'mplsLdpEntityProtocolVersion' object. The 5113 default value is 1. 5115 Added DEFVAL clause to 'mplsLdpEntityKeepAliveHoldTimer' of 40 5116 seconds. 5118 Added DEFVAL clause to 'mplsLdpEntityInitSesThreshold' object. The 5119 default value is 8. 5121 The mplsLdpEntityWellKnownDiscoveryPort was changed into two objects, 5122 one for TCP and one for UDP. The names are 5124 Typo in the description for the 5125 The mplsLdpEntityPeerTable was (re-)named mplsLdpPeerTable. The 5126 mplsLdpSessionTable now AUGMENTs the mplsLdpPeerTable in order to 5127 show that these two tables are related. There has been wording added 5128 to the mplsLdpSessionEntry description and to the description for the 5129 mplsLdpPeerTable. 5131 5.7. Changes from 5133 Editorial changes, fixing typo's, fixing wrapping lines, etc. 5135 Updated references for latest drafts, and added [RFC3032] and 5136 [RFC3034] to Reference Section. 5138 Added to the Acknowledgements Section. 5140 Changed the SYNTAX and DESCRIPTION of the 5141 'mplsLdpLsrLoopDetectionCapable' object, so that it will also support 5142 the loop detection by hop count. 5144 Combined the 'mplsLdpEntityLoopDetectionForPV' and 'mplsLdpEntityPVL' 5145 objects. The functionality of the 'mplsLdpEntityLoopDectionForPV' is 5146 now denoted by the value of 0 (zero) in the 'mplsLdpEntityPVL' 5147 object. This results in one less object 5148 'mplsLdpEntityLoopDectionForPV' but does not sacrifice functionality. 5150 Changed 'mplsLdpLibLabelType' into two objects: 5151 'mplsLdpLibInLabelType' and differ from the egress label type. The 5152 MIB now reflects this. 5154 The following items were changed as a result of the Frame Relay Forum 5155 dropping support for 17-bit DLCIs: the MplsLabel TC description has 5156 been modified, and other Frame Relay Object descriptions were also 5157 modified (as specified in this section). 5159 The MplsLabel TC was also modified and reference 3. was added to the 5160 REFERENCE Clause. 5162 MplsLdpLabelTypes TC was modified to use an enum. 5164 InterfaceIndex support was added to the Entity information. This was 5165 specifically requested by several members of the working group. An 5166 additional table, mplsLdpEntityConfGenericTable as a way to configure 5167 Generic Labels, and an object, 'mplsLdpConfGenericIfIndexOrZero was 5168 added to map the InterfaceIndex used by Generic Labels. Objects were 5169 also added to the 'mplsLdpEntityAtmParmsTable' and the and 5170 'mplsLdpEntityFrIfIndex', respectively. 5172 Changed the name of the 'mplsLdpEntityMtu' object to be 5173 'mplsLdpEntityMaxPduLength' which is more consistent with the LDP 5174 Specification. Also, the description and SYNTAX were changed. 5176 Changed the SYNTAX of the 'mplsLdpSessionMaxPduLength' to unsigned32 5177 and changed the Range from (0..65535) to (1..65535). 5179 Added and improved the front section discussion on SNMP 5180 Notifications. 5182 Also, modified the DESCRIPTION clause of the 5184 Added objects to enable/disable the sending of traps: 5186 Added an object to enable/disable sending traps for Sessions changing 5187 from Up to Down, or Down to Up. 5189 Added notifications to generate traps from session changing from Up 5190 to Down, or Down to up. 5192 Added a StorageType object to the Entity and associated tables which 5193 are configurable. 5195 Added a Discontinuity Time object to the Entity Table, 5197 Added discussion on row creation in the Entity and other associated 5198 Entity tables. This is a new Section in the Front part of the 5199 document called: 5201 Removed the 'mplsLdpEntityControlMethod'. 5203 Made 'mplsLdpFecLspId' as part of the INDEX for the FEC table. This 5204 is to allow FECs to map to multiple LSPs. Also add a RowPointer to a 5205 row in the Session Table. 5207 Added an operation status object, 'mplsLdpLspOperStatus' and a last 5208 Change object, 'mplsLdpLspLastChangeto the LIB Table. This will be 5209 used to detect whether an LSP has changed its status. 5211 Changed the name of the mplsLdpPeerTable to the 5212 mplsLdpEntityPeerTable. This table contains information relevant to 5213 Peers which are known to specific Entities. The indexing of this 5214 table has also changed to include the Row in the Entity Table that 5215 this Peer is known by. The mplsLdpHelloAdjacencyTable and the 5216 mplsLdpSessionTable have been moved under this table. Since Hello 5217 Adjacencies are related to Entity-Peer information and Sessions are 5218 related to Entity-Peer information this was seen as a comprehensive 5219 and coherent modelling. Associated descriptions in the front section 5220 and in the tables have been changed to reflect this change. 5222 Moved the 'mplsLdpConfFrLen' object from the 5223 'mplsLdpEntityConfFrLabelRangeTable' to the 5224 'mplsLdpEntityFrameRelayParmsTable' since the Frame Relay 5225 interface/port can only use one header length at a time, i.e. a 5226 specific FR interface supports one address length for all VCs on that 5227 interface. Also, changed the object so that it only supports 10 and 5228 23 bit DLCI lengths. (The 17 bit length was dropped by the Frame 5229 Relay Forum and thus, is no longer required.) The name of this 5230 object was changed from 'mplsLdpConfFrLen' to 'mplsLdpEntityFrLen' to 5231 fit in with the 'mplsLdpEntityFrameRelayParmsTable'. 5233 Removed the seventeenDlciBits(1) value from the mplsLdpFrSessionLen 5234 object. (The 17 bit length was dropped by the Frame Relay Forum and 5235 thus, is no longer required.) 5237 Corrected the range of the 'mplsLdpEntityIndexNext' object to include 5238 0 (zero). 5240 5.8. Changes from 5242 Reworded the description of the mplsLdpAtmSessionTable to clarify 5243 that one or MORE label range intersection(s) is/are represented in 5244 this table. 5246 Reworded the description of the mplsLdpFrameRelaySessionTable to 5247 clarify that one or MORE label range intersection(s) is/are 5248 represented in this table. 5250 Added a new index, mplsLdpSessionPeerIndex, to the 5251 mplsLdpSessionPeerAddressTable. This new index uniquely identifies 5252 the entry within a given session. (Since adding 5253 mplsLdpSessionPeerNextHopAddressType, 5254 mplsLdpSessionPeerNextHopAddress to the INDEX clause of the 5255 mplsLdpSessionPeerAddressTable leaves a table with only indices and 5256 no objects, the work around was to add a new index which uniquely 5257 differentiates an entry within a given session.) 5259 Quite a few changes to the mplsLdpPeerTable. First, removed the 5260 mplsLdpPeerIndex from the mplsLdpPeerTable and other tables. This 5261 index served no purpose, so was removed. Second, removed the 5262 objects: mplsLdpPeerInternetworkAddrType, and 5263 mplsLdpPeerInternetworkAddr. Third, reworded the description of this 5264 table to include information which is known during Session 5265 Intialization attempts, the specific information has to do with Loop 5266 Dection based on Path Vectors. Since Section 3.5.3 of the LDP Spec 5267 when describing the PVLim says: "Although knowledge of a peer's path 5268 vector limit will not change an LSR's behavior, it does enable the 5269 LSR to alert an operator to a possible misconfiguration." and the 5270 object mplsLdpPeerPVL is sent as a varbind in the mplsLdpPVLMismatch 5271 notification. 5273 Removed the mplsLdpPeerIndex from the mplsLdpHelloAdjacencyTable. 5275 Removed the "IANA Address Family Numbers" MIB section. 5277 Updated the boiler.me from the ops web page dated Weds., Dec 22, 5278 1999. 5280 Updated the Security Section from the ops web page. 5282 Added the following objects to the mplsLdpEntityTable: 5283 mplsLdpEntityControlMethod, mplsLdpEntityLoopDectionForPV, and 5284 mplsLdpEntityPathVectorLimit. 5286 Removed mplsLdpSessionLabelAdvertisement, 5287 mplsLdpSessionLoopDetectionForPV, and mplsLdpSessionPathVectorLimit 5288 from the mplsLdpSessionTable. 5290 Changed the mplsLdpPathVectorLimitMismatch Notification to send 5291 mplsLdpEntityPathVectorLimit (instead of 5292 mplsLdpSessionPathVectorLimit). 5294 Copied the MplsLabel TC from draft-ietf-mpls-lsr-mib-00.txt and 5295 replaced the MplsLdpGenAddr for mplsLdpLibInLabel and 5296 mplsLdpLibOutLabel with MplsLabel. 5298 The mplsLdpSessionIndex was removed throughout the MIB. This was 5299 replaced by the object mplsLdpSessionDiscontinuityTime. The 5300 motivation was to reduce the number of indices. 5302 The descriptions for the objects in the mplsLdpSessionStatsTable, 5303 mplsLdpSessionStatsUnknownMessageTypeErrors and 5304 mplsLdpSessionStatsUnknownTlvErrors, have been updated to include a 5305 reference to the mplsLdpSessionDiscontinuityTime object. 5307 5.9. Changes from 5309 Added Scalar Objects: mplsLdpLsrLoopDetectionPresent, and 5310 mplsLdpEntityIndexNext. 5312 Added the following objects to the mplsLdpEntityTable: 5313 mplsLdpEntityProtocolVersion, mplsLdpEntityAdminStatus, 5314 mplsLdpEntityOperStatus, mplsLdpEntityTargetedPeer, 5315 mplsLdpEntityTargetedPeerAddrType, mplsLdpEntityTargetedPeerAddr, and 5316 mplsLdpEntityHelloHoldTimer. 5318 Changed the description of the mplsLdpEntityAtmParmsTable and added 5319 the following objects to this table: mplsLdpEntityAtmLsrConnectivity, 5320 mplsLdpEntityDefaultControlVpi, mplsLdpEntityDefaultControlVci, 5321 mplsLdpEntityUnlabTrafVpi, and mplsLdpEntityUnlabTrafVci. NOTE: the 5322 last four objects were in Version 01 of the MIB but were mistakenly 5323 omitted from Version 02. Now, they are back. 5325 Changed the indexing of the mplsLdpEntityConfAtmLabelRangeTable to 5326 include the minimum VPI/VCI. This is to ensure that indices in this 5327 table are unique. 5329 Changed the indexing of the mplsLdpEntityConfFrLabelRangeTable, to 5330 include the minimum DLCI value. This is to ensure that indices in 5331 this table are unique. 5333 Added [RFC3036] to Reference Section. 5335 5.10. Changes from 5337 The MIB was updated to correspond to draft-ietf-mpls-ldp-06.txt of 5338 the LDP Specification [RFC3036]. 5340 The front section was updated. 5342 The MIB was made to be less ATM-centric. Essentially, the ATM 5343 specific objects where removed from the tables and placed in ATM 5344 specific Tables. A type was added to the base tables and a row is to 5345 be created in the ATM/FR/etc. type table. Apropos compliance 5346 statements were added to reflect the separation of ATM and Frame 5347 Relay objects into their respective tables. 5349 Objects for Loop Detection were removed from describing the LDP 5350 implementation (i.e. the scalars were removed) and Loop Dection 5351 objects were added to the Session Table. (Although as the LDP 5352 Specification indicates loop detection should be for an LSR within a 5353 domain.) 5355 The following tables were added: mplsLdpEntityAtmParmsTable, 5356 mplsLdpEntityConfAtmLabelRangeTable, mplsLdpFrameRelayParmsTable, 5357 mplsLdpConfFrLabelRangeTable, mplsLdpAtmSessionTable, 5358 mplsLdpFrameRelaySessionTable, mplsLdpSessionPeerAddressTable, 5359 mplsLdpLibTable, and the mplsLdpFecTable. 5361 The following notifications were added: notification for Session 5362 removal. 5364 The following objects were removed from the Session Table: 5365 mplsLdpSessionRole was removed (this can be determined by comparing 5366 LSR Ids and does not need to be explicitly in the MIB.) ATM specific 5367 objects (mplsLdpSessionAtmLabelRangeLowerBoundVpi 5368 mplsLdpSessionAtmLabelRangeLowerBoundVci, 5369 mplsLdpSessionAtmLabelRangeUpperBoundVpi 5370 mplsLdpSessionAtmLabelRangeUpperBoundVci) were removed and put into a 5371 separate table. Frame Relay objects were added in a separate table. 5373 Hello Adjacency Table was updated. 5375 The objects, mplsLdpSessionRejectedParamErrors, 5376 mplsLdpSessionRejectedNoHelloErrors, mplsLdpBadLdpIdentifierErrors, 5377 mplsLdpBadPduLengthErrors, mplsLdpBadMessageLengthErrors, 5378 mplsLdpBadTlvLengthErrors, mplsLdpMalformedTlvValueErrors, 5379 mplsLdpKeepAliveTimerExpiredErrors, mplsLdpShutdownNotifReceived, and 5380 mplsLdpShutdownNotifSent were added to the mplsLdpEntityStatsTable. 5382 The mplsLdpSessionStatsTable was added to count statics based on a 5383 per Session basis. 5385 The mplLdpPeerConfAtmLabelRangeTable has been removed. There is no 5386 need to configure information for a Peer. All information for a peer 5387 is learned, thus peer information is read-only. 5389 (Editorial) References were updated to reflect the documents which 5390 this version was based on. 5392 5.11. Changes from 5394 Textual conventions were added for the LSR Identifier and the LDP 5395 Identifier. 5397 Top-level mib structure was added. The LDP MIB falls under a proposed 5398 hierarchy of mpls.mplsProtocols. 5400 The mib hierarchy within the LDP MIB was also changed. A new branch, 5401 under mpls.mplsProtocols.mplsLdpMIB.mplsLdpObjects was added. This 5402 branch is mplsLdpLsrObjects. Currently, this contains several new 5403 scalar objects: mplsLdpLsrID, mplsLdpLsrLoopDetectionPresent, 5404 mplsLdpLsrLoopDetectinAdminStatus, mplsLdpLsrPathVectorLimit, 5405 mplsLdpLsrHopCountLimit, mplsLdpLsrLoopPreventionPresent, 5406 mplsLdpLsrLoopPreventionAdminStatus, and 5407 mplsLdpLsrLabelRetentionMode. 5409 mplsLdpEntityTable is now indexed by mplsLdpEntityIdentifier, which 5410 is the LDP Identifier used in Session establishment. 5411 mplsLdpEntityLoopDetection and mplsLdpEntityLoopPrevention objects 5412 were removed from this table. 5414 The following objects were added to the mplsLdpEntityTable: 5415 mplsLdpEntityLabelSpaceType, mplsLdpEntityUnlabTrafVpi, 5416 mplsLdpEntityUnlabTrafVci, mplsLdpEntityMergeCapability, 5417 mplsLdpEntityVcDirectionality, and 5418 mplsLdpEntityLabelDistributionMethod. 5420 The following objects were added to the mplsLdpPeerEntityTable: 5421 mplsLdpPeerLabelDistributionMethod. 5423 The following object was removed from the mplsLdpEntityStatsTable: 5424 mplsLdpEntityEstablishedSessions. 5426 References were added and revised. 5428 6. Acknowledgments 5430 The authors would like to thank the following people: Leigh 5431 McLellan, Geetha Brown, Geping Chen and Charlan Zhou from Nortel 5432 Networks, and Zoltan Takacs and Bo Augustsson from Ericsson. Also, 5433 some members of the working group were very helpful with comments and 5434 corrections to the MIB; the authors would like to thank Adrian Farrel 5435 of Movaz Networks, and Alan Kullberg from NetPlane Systems. 5437 7. Normative References 5439 [RFC1700] Reynolds, J. and J. Postel, "ASSIGNED NUMBERS", STD 2, RFC 5440 1700, October 1994. 5442 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 5443 Requirement Levels", BCP 14, RFC 2119, Harvard University, 5444 March 1997 5446 [RFC2115] Brown, C., and F. Baker, "Management Information Base for 5447 Frame Relay DTEs Using SMIv2", RFC 2115, September 1997. 5449 [RFC2514] Noto, M., E. Spiegel, K. Tesink, editors, "Definition of 5450 Textual Conventions and OBJECT-IDENTITIES for ATM 5451 Management", RFC 2514, February 1999. 5453 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 5454 Rose, M. and S. Waldbusser, "Structure of Management 5455 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 5456 1999. 5458 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 5459 Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", 5460 STD 58, RFC 2579, April 1999. 5462 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 5463 Rose, M. and S. Waldbusser, "Conformance Statements for 5464 SMIv2", STD 58, RFC 2580, April 1999. 5466 [RFC2863] McCloghrie, K., F. Kastenholz, "The Interfaces Group MIB 5467 using SMIv2", RFC 2863, June 2000. 5469 [RFC3031] Rosen, E., Viswananthan, A., and R. Callon, "Multiprotocol 5470 Label Switching Architecture", RFC 3031, January 2001. 5472 [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., Farinacci, 5473 D., Li, T. and A. Conta, "MPLS Label Stack Encoding", RFC 5474 3032, January 2001. 5476 [RFC3034] Conta, A., Doolan, P., and A. Malis, "Use of Label Switching 5477 on Frame Relay Networks Specification", RFC 3034, January 5478 2001. 5480 [RFC3035] Davie, B., Lawrence, J., McCloghrie, K., Rosen, E., Swallow, 5481 G., Rekhter, Y. and P. Doolan, "MPLS using LDP and ATM VC 5482 Switching", RFC 3035, January 2001. 5484 [RFC3036] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and B. 5485 Thomas, "LDP Specification", RFC 3036, January 2001. 5487 [RFC3037] Thomas, B. and E. Gray, "LDP Applicability", RFC 3037, 5488 January 2001. 5490 [RFC3215] Boscher, C., Cheval, P., Wu L. and E. Gray, "LDP State 5491 Machine", RFC 3215, January 2002. 5493 [RFC3289] Baker, F., Chan, K. and A. Smith, "Management Information 5494 Base for the Differentiated Services Architecture", RFC 5495 3289, May 2002. 5497 [RFC3291] Daniele, M., Haberman, B., Routhier, S. and J. 5498 Schoenwaelder, "Textual Coventions for Internet Network 5499 Addresses", RFC 3291, May 2002. 5501 [LSRMIB] Srinivansan, C., Viswanathan, A., and T. Nadeau "MPLS Label 5502 Switching Router Management Information Base Using SMIv2", 5503 draft-ietf-mpls-lsr-mib-09.txt, October 2003. 5505 [MPLSTCMIB] Nadeau, T., J. Cucchiara, (Eds.) "Definitions of Textual 5506 Conventions for Multiprotocol Label Switching Management", 5507 draft-ietf-mpls-tc-mib-06.txt, March 2003. 5509 8. Informative References 5511 [RFC2115] Brown, C., and F. Baker, "Management Information Base for 5512 Frame Relay DTEs Using SMIv2", RFC 2115, September 1997. 5514 [RFC2514] Noto, M., E. Spiegel, K. Tesink, editors, "Definition of 5515 Textual Conventions and OBJECT-IDENTITIES for ATM 5516 Management", RFC 2514, February 1999. 5518 [RFC2684] Grossman, D., and J. Heinanen, "Multiprotocol Encapsulation 5519 over ATM Adaptation Layer 5", RFC 2684, September 1999. 5521 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 5522 "Introduction and Applicability Statements for Internet- 5523 Standard Management Framework", RFC 3410, December 2002. 5525 [MPLSMGMT] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol 5526 Label Switching (MPLS) Management Overview", draft-ietf- 5527 mpls-mgmt-overview-04.txt, May 2003. 5529 9. Security Considerations 5531 This Security Considerations section consists of 4 subsections, one 5532 for each of the MIB Modules in this document. 5534 9.1. Security Considerations for MPLS-LDP-STD-MIB 5536 There are a number of management objects defined in this MIB module 5537 with a MAX-ACCESS clause of read-write and/or read-create. Such 5538 objects may be considered sensitive or vulnerable in some network 5539 environments. The support for SET operations in a non-secure 5540 environment without proper protection can have a negative effect on 5541 network operations. These are the tables and objects and their 5542 sensitivity/vulnerability: 5544 o the mplsLdpEntityTable contains objects to provision potential 5545 LDP sessions on the Label Switching Router (LSR) or Label Edge 5546 Router (LER). The mplsLdpLspFecTable contains objects which 5547 associate an LSP with a FEC. Unauthorized access to objects in 5548 these tables, could result in disruption of traffic on the 5549 network. This is especially true if an LDP session has been 5550 established. The use of stronger mechanisms such as SNMPv3 5551 security should be considered where possible. Specifically, 5552 SNMPv3 VACM and USM MUST be used with any v3 agent which 5553 implements this MIB. Administrators should consider whether 5554 read access to these objects should be allowed, since read 5555 access may be undesirable under certain circumstances. 5557 Some of the readable objects in this MIB module "i.e., objects with a 5558 MAX-ACCESS other than not-accessible" may be considered sensitive or 5559 vulnerable in some network environments. It is thus important to 5560 control even GET and/or NOTIFY access to these objects and possibly 5561 to even encrypt the values of these objects when sending them over 5562 the network via SNMP. These are the tables and objects and their 5563 sensitivity/vulnerability: 5565 o the mplsLdpEntityTable, mplsLdpPeerTable, mplsLdpSesTable and 5566 mplsLdpSesStatsTable collectively show the LDP LSP network 5567 topology. If an Administrator does not want to reveal the LDP 5568 LSP topology of the network, then these tables should be 5569 considered sensitive/vulnerable. 5571 9.2. Security Considerations for MPLS-LDP-ATM-STD-MIB 5573 There are a number of management objects defined in this MIB module 5574 with a MAX-ACCESS clause of read-write and/or read-create. Such 5575 objects may be considered sensitive or vulnerable in some network 5576 environments. The support for SET operations in a non-secure 5577 environment without proper protection can have a negative effect on 5578 network operations. These are the tables and objects and their 5579 sensitivity/vulnerability: 5581 o the mplsLdpEntityAtmTable and mplsLdpEntityAtmLRTable contain 5582 objects to provision potential LDP sessions on the Label 5583 Switching Router (LSR) or Label Edge Router (LER) over Layer 2 5584 of ATM. These tables extend the mplsLdpEntityTable in the MPLS- 5585 LDP-MIB. Unauthorized access to objects in these tables, could 5586 result in disruption of traffic on the network. This is 5587 especially true if an LDP session has been established. The use 5588 of stronger mechanisms such as SNMPv3 security should be 5589 considered where possible. Specifically, SNMPv3 VACM and USM 5590 MUST be used with any v3 agent which implements this MIB. 5591 Administrators should consider whether read access to these 5592 objects should be allowed, since read access may be undesirable 5593 under certain circumstances. 5595 Some of the readable objects in this MIB module "i.e., objects with a 5596 MAX-ACCESS other than not-accessible" may be considered sensitive or 5597 vulnerable in some network environments. It is thus important to 5598 control even GET and/or NOTIFY access to these objects and possibly 5599 to even encrypt the values of these objects when sending them over 5600 the network via SNMP. These are the tables and objects and their 5601 sensitivity/vulnerability: 5603 o the mplsLdpEntityAtmTable and mplsLdpEntityAtmLRTable show the 5604 Label Ranges for ATM. If an Administrator does not want to 5605 reveal this information then these tables should be considered 5606 sensitive/vulnerable and treated accordingly. 5608 9.3. Security Considerations for MPLS-LDP-FRAME-RELAY-STD-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 mplsLdpEntityFrameRelayTable and 5619 mplsLdpEntityFrameRelayLRTable contain objects to provision 5620 potential LDP sessions on the Label Switching Router (LSR) or 5621 Label Edge Router (LER) over Layer 2 of Frame Relay. These 5622 tables extend the mplsLdpEntityTable in the MPLS-LDP-MIB. 5623 Unauthorized access to objects in these tables, could result in 5624 disruption of traffic on the network. This is especially true 5625 if an LDP session has been established. The use of stronger 5626 mechanisms such as SNMPv3 security should be considered where 5627 possible. Specifically, SNMPv3 VACM and USM MUST be used with 5628 any v3 agent which implements this MIB. Administrators should 5629 consider whether read access to these objects should be allowed, 5630 since read access may be undesirable under certain 5631 circumstances. 5633 Some of the readable objects in this MIB module "i.e., objects with a 5634 MAX-ACCESS other than not-accessible" may be considered sensitive or 5635 vulnerable in some network environments. It is thus important to 5636 control even GET and/or NOTIFY access to these objects and possibly 5637 to even encrypt the values of these objects when sending them over 5638 the network via SNMP. These are the tables and objects and their 5639 sensitivity/vulnerability: 5641 o the mplsLdpEntityFrameRelayTable and 5642 mplsLdpEntityFrameRelayLRTable show the Label Ranges for Frame 5643 Relay. If an Administrator does not want to reveal this 5644 information then these tables should be considered 5645 sensitive/vulnerable and treated accordingly. 5647 9.4. Security Considerations for MPLS-LDP-GENERIC-STD-MIB 5649 There are a number of management objects defined in this MIB module 5650 with a MAX-ACCESS clause of read-write and/or read-create. Such 5651 objects may be considered sensitive or vulnerable in some network 5652 environments. The support for SET operations in a non-secure 5653 environment without proper protection can have a negative effect on 5654 network operations. These are the tables and objects and their 5655 sensitivity/vulnerability: 5657 o the mplsLdpEntityGenericLRTable contains objects to provision 5658 potential LDP sessions on the Label Switching Router (LSR) or 5659 Label Edge Router (LER) over Layer 2 of Ethernet. This table 5660 extends the mplsLdpEntityTable in the MPLS-LDP-MIB. 5661 Unauthorized access to objects in these tables, could result in 5662 disruption of traffic on the network. This is especially true 5663 if an LDP session has been established. The use of stronger 5664 mechanisms such as SNMPv3 security should be considered where 5665 possible. Specifically, SNMPv3 VACM and USM MUST be used with 5666 any v3 agent which implements this MIB. Administrators should 5667 consider whether read access to these objects should be allowed, 5668 since read access may be undesirable under certain 5669 circumstances. 5671 Some of the readable objects in this MIB module "i.e., objects with a 5672 MAX-ACCESS other than not-accessible" may be considered sensitive or 5673 vulnerable in some network environments. It is thus important to 5674 control even GET and/or NOTIFY access to these objects and possibly 5675 to even encrypt the values of these objects when sending them over 5676 the network via SNMP. These are the tables and objects and their 5677 sensitivity/vulnerability: 5679 o the mplsLdpEntityGenericLRTable shows the Label Ranges for 5680 ethernet. If an Administrator does not want to reveal this 5681 information then these tables should be considered 5682 sensitive/vulnerable and treated accordingly. 5684 9.5. Additional Security Considerations 5686 The following paragraphs describe additional security considerations 5687 which are applicable to all 4 of the MIB Modules in this document. 5689 SNMP versions prior to SNMPv3 did not include adequate security. 5690 Even if the network itself is secure "for example by using IPSec", 5691 even then, there is no control as to who on the secure network is 5692 allowed to access and GET/SET "read/change/create/delete" the objects 5693 in this MIB module. 5695 It is RECOMMENDED that implementers consider the security features as 5696 provided by the SNMPv3 framework "see [RFC3410], section 8", 5697 including full support for the SNMPv3 cryptographic mechanisms "for 5698 authentication and privacy". 5700 Further, deployment of SNMP versions prior to SNMPv3 is NOT 5701 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 5702 enable cryptographic security. It is then a customer/operator 5703 responsibility to ensure that the SNMP entity giving access to an 5704 instance of this MIB module, is properly configured to give access to 5705 the objects only to those principals "users" that have legitimate 5706 rights to indeed GET or SET "change/create/delete" them. 5708 10. IANA Considerations 5710 As described in [MPLSMGMT] and as requested in the MPLS-TC-STD-MIB 5711 [MPLSTCMIB], MPLS related standards track MIB modules should be 5712 rooted under the mplsStdMIB subtree. There are 4 MPLS MIB Modules 5713 contained in this document, each of the following "IANA 5714 Considerations" subsections requests IANA for a new assignment under 5715 the mplsStdMIB subtree. New assignments can only be made via a 5716 Standards Action as specified in [RFC2434]. 5718 10.1. IANA Considerations for the MPLS-LDP-STD-MIB Module 5720 The IANA is requested to assign { mplsStdMIB 4 } to the MPLS-LDP-STD- 5721 MIB module specified in this document. 5723 10.2. IANA Considerations for the MPLS-LDP-ATM-STD-MIB Module 5725 The IANA is requested to assign { mplsStdMIB 5 } to the MPLS-LDP-ATM- 5726 STD-MIB module specified in this document. 5728 10.3. IANA Considerations for the MPLS-LDP-FRAME-RELAY-STD-MIB Module 5730 The IANA is requested to assign { mplsStdMIB 6 } to the MPLS-LDP- 5731 FRAME-RELAY-STD-MIB module specified in this document. 5733 10.4. IANA Considerations for the MPLS-LDP-GENERIC-STD-MIB Module 5735 The IANA is requested to assign { mplsStdMIB 7 } to the MPLS-LDP- 5736 GENERIC-STD-MIB module specified in this document. 5738 11. Intellectual Property Notice 5740 The IETF takes no position regarding the validity or scope of any 5741 intellectual property or other rights that might be claimed to 5742 pertain to the implementation or use of the technology described in 5743 this document or the extent to which any license under such rights 5744 might or might not be available; neither does it represent that it 5745 has made any effort to identify any such rights. Information on the 5746 IETF's procedures with respect to rights in standards-track and 5747 standards-related documentation can be found in BCP-11 [RFC2028]. 5748 Copies of claims of rights made available for publication and any 5749 assurances of licenses to be made available, or the result of an 5750 attempt made to obtain a general license or permission for the use of 5751 such proprietary rights by implementors or users of this 5752 specification can be obtained from the IETF Secretariat. 5754 The IETF invites any interested party to bring to its attention any 5755 copyrights, patents or patent applications, or other proprietary 5756 rights that may cover technology that may be required to practice 5757 this standard. Please address the information to the IETF Executive 5758 Director. 5760 12. Authors' Addresses 5762 James V. Luciani 5763 Consultant 5764 PO Box 1010 5765 Concord, MA 01742 5766 USA 5767 Email: james_luciani@mindspring.com 5769 Hans Sjostrand 5770 ipUnplugged 5771 P.O. Box 101 60 5772 S-121 28 Stockholm, Sweden 5773 Phone: +46 8 725 5930 5774 Email: hans@ipunplugged.com 5776 Joan Cucchiara 5777 Artel 5778 237 Cedar Hill Street 5779 Marlborough, MA 01752 5780 Phone: +1-508-303-8200 x302 5781 Email: jcucchiara@artel.com 5783 13. Full Copyright Statement 5785 Copyright (C) The Internet Society (2003). All Rights Reserved. 5787 This document and translations of it may be copied and furnished to 5788 others, and derivative works that comment on or otherwise explain it 5789 or assist in its implementation may be prepared, copied, published 5790 and distributed, in whole or in part, without restriction of any 5791 kind, provided that the above copyright notice and this paragraph are 5792 included on all such copies and derivative works. However, this 5793 document itself may not be modified in any way, such as by removing 5794 the copyright notice or references to the Internet Society or other 5795 Internet organizations, except as needed for the purpose of 5796 developing Internet standards in which case the procedures for 5797 copyrights defined in the Internet Standards process must be 5798 followed, or as required to translate it into languages other than 5799 English. 5801 The limited permissions granted above are perpetual and will not be 5802 revoked by the Internet Society or its successors or assigns. 5804 This document and the information contained herein is provided on an 5805 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 5806 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 5807 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 5808 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 5809 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.