idnits 2.17.1 draft-ietf-mpls-ldp-mib-12.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 40 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 3444 has weird spacing: '...erlying media...' == Line 4560 has weird spacing: '...ibed in detai...' == Line 4748 has weird spacing: '...entence s/ini...' == Line 5314 has weird spacing: '... (Since addin...' == Line 5864 has weird spacing: '...for the purpo...' == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 2003) is 7621 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: 'RFC2573' is mentioned on line 434, but not defined ** Obsolete undefined reference: RFC 2573 (Obsoleted by RFC 3413) == Missing Reference: 'RFC2434' is mentioned on line 5786, but not defined ** Obsolete undefined reference: RFC 2434 (Obsoleted by RFC 5226) == Unused Reference: 'RFC2115' is defined on line 5516, but no explicit reference was found in the text == Unused Reference: 'RFC2514' is defined on line 5523, but no explicit reference was found in the text == Unused Reference: 'RFC3037' is defined on line 5561, but no explicit reference was found in the text == Unused Reference: 'RFC3215' is defined on line 5564, but no explicit reference was found in the text == Unused Reference: 'RFC3289' is defined on line 5567, but no explicit reference was found in the text == Unused Reference: 'RFC3291' is defined on line 5571, but no explicit reference was found in the text == Unused Reference: 'RFC2026' is defined on line 5585, but no explicit reference was found in the text ** 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-11 == Outdated reference: A later version (-10) exists of draft-ietf-mpls-tc-mib-08 == Outdated reference: A later version (-09) exists of draft-ietf-mpls-mgmt-overview-06 Summary: 9 errors (**), 0 flaws (~~), 20 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 Modules ................................. 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 ................................ 6 57 3.5.1 LDP Scalar Objects ....................................... 6 58 3.5.2 The LDP Entity Table ..................................... 6 59 3.5.2.1 Changing Values After Session Establishment ............ 7 60 3.5.3 The LDP Entity Statistics Table .......................... 8 61 3.5.4 The LDP Peer Table ....................................... 8 62 3.5.5 The LDP Session Table .................................... 9 63 3.5.6 The LDP Session Statistics Table ......................... 9 64 3.5.7 The LDP Hello Adjacency Table ............................ 9 65 3.5.8 The LDP LSP Table ........................................ 9 66 3.5.9 The FEC Table ............................................ 10 67 3.5.10 The LDP Session Peer Address Table ...................... 10 68 3.6 LDP Notifications .......................................... 10 69 3.7 LDP Notification Frequency ................................. 11 70 4 MPLS Label Distribution Protocol MIB Definitions ............. 11 71 4.1 The MPLS-LDP-ATM-STD-MIB Module ............................ 65 72 4.1.1 The LDP Entity ATM Table ................................. 65 73 4.1.2 The LDP Entity ATM Label Range Table ..................... 65 74 4.1.3 The LDP ATM Session Table ................................ 65 75 4.2 The MPLS-LDP-FRAME-RELAY-STD-MIB Module .................... 82 76 4.2.1 The LDP Entity Frame Relay Table ........................ 82 77 4.2.2 The LDP Entity Frame Relay Label Range Table ............. 83 78 4.2.3 The LDP Frame Relay Session Table ........................ 83 79 4.3 The MPLS-LDP-GENERIC-STD-MIB Module ........................ 97 80 5 Revision History ............................................. 105 81 5.1 Changes from .............. 105 82 5.2 Changes from .............. 105 83 5.3 Changes from .............. 105 84 5.3.1 Changes based on MIB Doctor Review Comments .............. 106 85 5.4 Changes from .............. 110 86 5.5 Changes from .............. 113 87 5.6 Changes from .............. 114 88 5.7 Changes from .............. 114 89 5.8 Changes from .............. 116 90 5.9 Changes from .............. 118 91 5.10 Changes from ............. 120 92 5.11 Changes from ............. 121 93 5.12 Changes from ............. 122 94 6 Acknowledgments .............................................. 124 95 7 Normative References ......................................... 125 96 8 Informative References ....................................... 127 97 9 Security Considerations ...................................... 127 98 9.1 Security Considerations for MPLS-LDP-STD-MIB ............... 127 99 9.2 Security Considerations for MPLS-LDP-ATM-STD-MIB ........... 128 100 9.3 Security Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB ... 129 101 9.4 Security Considerations for MPLS-LDP-GENERIC-STD-MIB ....... 130 102 9.5 Additional Security Considerations ......................... 130 103 10 IANA Considerations ......................................... 131 104 10.1 IANA Considerations for MPLS-LDP-STD-MIB .................. 131 105 10.2 IANA Considerations for MPLS-LDP-ATM-STD-MIB .............. 131 106 10.3 IANA Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB ...... 131 107 10.4 IANA Considerations for MPLS-LDP-GENERIC-STD-MIB .......... 132 108 11 Intellectual Property Notice ................................ 132 109 12 Authors' Addresses .......................................... 132 110 13 Full Copyright Statement .................................... 133 112 1. Introduction 114 This document defines 4 MIB Modules which together support the 115 configuration and monitoring of the Label Distribution Protocol 116 (LDP). The Label Distribution Protocol (LDP) [RFC3036] is one type 117 of Multiprotocol Label Switching (MPLS) protocols described in 118 [RFC3031] and [RFC3032]. Utilizing all 4 MIB Modules allows an 119 operator to configure LDP sessions using 3 different Layer 2 media. 120 The Layer 2 media supported by the MIB Modules are Ethernet, ATM and 121 Frame Relay as described in [RFC3036], [RFC3034] and [RFC3035]. 123 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 124 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 125 document are to be interpreted as described in RFC 2119 [RFC2119]. 127 2. The Internet-Standard Management Framework 129 For a detailed overview of the documents that describe the current 130 Internet-Standard Management Framework, please refer to section 7 of 131 RFC 3410 [RFC3410]. 133 Managed objects are accessed via a virtual information store, termed 134 the Management Information Base or MIB. MIB objects are generally 135 accessed through the Simple Network Management Protocol (SNMP). 136 Objects in the MIB are defined using the mechanisms defined in the 137 Structure of Management Information (SMI). This memo specifies a MIB 138 module that is compliant to the SMIv2, which is described in STD 58, 139 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 140 [RFC2580]. 142 3. Structure of the MIB Modules 144 This section describes the structure of the LDP MIB Modules. 146 3.1. Overview 148 There are 4 MIB Modules in this document. These MIB Modules are the 149 MPLS-LDP-STD-MIB, the MPLS-LDP-GENERIC-STD-MIB, the MPLS-LDP-ATM-STD- 150 MIB and the MPLS-LDP-FRAME-RELAY-STD-MIB. The MPLS-LDP-STD-MIB 151 defines objects which are common to all LDP implementations. The 152 MPLS-LDP-GENERIC-STD-MIB defines Layer 2 Per Platform Label Space 153 objects for use with the MPLS-LDP-STD-MIB. The MPLS-LDP-ATM-STD-MIB 154 defines Layer 2 Asynchronous Transfer Mode (ATM) objects for use with 155 the MPLS-LDP-STD-MIB. The MPLS-LDP-FRAME-RELAY-STD-MIB defines Layer 156 2 FRAME-RELAY objects for use with the MPLS-LDP-STD-MIB. 158 The MPLS-LDP-STD-MIB Module MUST be implemented and at least one of 159 the Layer 2 MIB Modules MUST be implemented by an Agent developer on 160 an Label Switching Router (LSR) or Label Edge Router (LER). As an 161 example, if an Label Switching Router (LSR) or Label Edge Router 162 (LER) implementation intends to support LDP utilizing a Layer 2 of 163 Ethernet, then the MPLS-LDP-STD-MIB and the MPLS-LDP-GENERIC-STD-MIB 164 Modules MUST implemented. If an LSR/LER implementation intends to 165 support LDP utilizing a Layer 2 of ATM, then the MPLS-LDP-STD-MIB 166 Module and the MPLS-LDP-ATM-MIB Module MUST be implemented. If an 167 LSR/LER implementation intends to support LDP utilizing a Layer 2 of 168 FRAME-RELAY, then the MPLS-LDP-STD-MIB Module and the MPLS-LDP-FRAME- 169 RELAY-STD-MIB Module MUST be implemented. An LDP implementation that 170 utilizes all three Layer 2 media (Ethernet, Frame-Relay, ATM) MUST 171 support all 4 MIB Modules. Each of the Modules will be discussed in 172 detail in the following sections. 174 There are 2 compliance statements for each MIB Module. One 175 compliance statement is for full compliance which allows both 176 configuration and monitoring via SNMP. The other compliance 177 statement is for read-only compliance which allows only monitoring 178 via SNMP. 180 3.2. Future Considerations 182 The LDP Specification [RFC3036] does not specify the use of VPNs or 183 multicast for LDP, and thus, objects related to these areas have not 184 been included. 186 [RFC2684] does not describe VP merge capability and so this feature 187 has not been included. 189 These areas need to be specified in the LDP Specification or other 190 specifications prior to being added in this or any other MIB 191 document. 193 3.3. Interface Indexing 195 Interface Indexes as specified in [RFC2863] are used in these MIB 196 Modules. The descriptions of the ifIndexes denote which ifIndex is 197 being used. The use of ifIndex is for actual existing connections. 199 3.4. Differences from the LDP Specification 201 Currently, there are 3 differences between this specification and the 202 LDP Specification. As described in the Introduction, this document 203 is almost entirely based on the LDP specification. The differences 204 are documented here. 206 The first difference is that the LDP Entity Table contains some 207 DEFVAL clauses which are not specified explicitly in the LDP 208 Specification. These values, although not documented in the LDP 209 Specification, are widely used by existing LDP MIB implementations 210 and thus, have been adopted within this MPLS-LDP-STD-MIB module. 211 Please note, they can certainly be changed during row creation or a 212 subsequent SET request. 214 A second difference is the mplsLdpEntityConfGenericLRTable in the 215 MPLS-LDP-GENERIC-STD-MIB Module. This table, although provided as a 216 way to reserve a range of generic labels, does not exist in the LDP 217 Specification. It was added to the MIB due to a request from the 218 working group and because this table was considered useful for 219 reserving a range of generic labels. 221 The third difference is documented by the TEXTUAL-CONVENTION, 222 MplsAtmVcIdentifier which is in the MPLS-TC-MIB [MPLSTCMIB]. This TC 223 was added to restrict vci values to be greater than 31 as described 224 in RFC 3035 [RFC3035]. 226 3.5. The MPLS-LDP-STD-MIB Module 228 This MIB Module contains objects which are common to all LDP 229 implementations. This MIB Module MUST always be implemented along 230 with one or more of the Layer 2 MIB Modules. 232 This table allows the Label Edge Router (LER) or the Label Switching 233 Router (LSR) to initiate and/or receive requests to establish LDP 234 sessions. As the LDP protocol distributes labels and establishes 235 sessions with Peers most of the tables in this module are populated 236 by the agent as instructed by the LDP protocol. The exception is the 237 mplsFecTable and the mplsLdpLspFecTable which can be configured by 238 the operator to specify Forwarding Equivalence Class information for 239 an LSP. 241 Some scalars and each table in the MPLS-LDP-STD-MIB Module is 242 described in the following subsections. 244 3.5.1. LDP Scalar Objects 246 There are several scalar objects in the LDP MIB module. The 247 mplsLdpLsrId is a read-only scalar object which reports Lable 248 Switching Router's (LSR's) Identifier. This MUST be a globally 249 unique value, such as the 32-bit router ID assigned to the LSR. 251 The mplsLdpLsrLoopDetectionCapable scalar object denotes whether the 252 LSR is capable of supporting loop detection and if so, which form of 253 loop detection. 255 There are two LastChange scalar objects, mplsLdpEntityLastChange and 256 mplsLdpPeerLastChange. These objects give an indication of there was 257 a change in the number of entries in the table, or if any of the 258 values in the respective tables changed. Please see the object's 259 description for more details. 261 The mplsLdpEntityIndexNext scalar object is described in the next 262 section. 264 3.5.2. The LDP Entity Table 266 The MPLS-LDP-STD-MIB provides objects to configure/set-up potential 267 LDP sessions on a specific LSR/LER. The mplsLdpEntityTable is used 268 to configure information which is used by the LDP protocol to setup 269 potential LDP Sessions. 271 Each entry/row in this table represents a single LDP Entity. There 272 is no maximum number of LDP Entities specified. However, there is an 273 mplsLdpEntityIndexNext object which should be retrieved by the 274 command generator prior to creating an LDP Entity. If the 275 mplsLdpEntityIndexNext object is zero, this indicates that the 276 LSR/LER is not able to create another LDP Entity at that time. 278 3.5.2.1. Changing Values After Session Establishment 280 One way to manually modify a session's parameters is by using SNMP to 281 change the MIB objects related to that session. Please note, special 282 care should be taken if MIB objects which are used in the MPLS LDP 283 Session Initialization need to be modified. If the modification of 284 any of these MIB variables takes place anytime after the start of 285 session intialization, then the entire session must be halted. Any 286 information learned by that session must be discarded. The objects 287 should then be modified, and session initialization started. 288 Assuming that the configuration was done correctly, then a new 289 session will be created. 291 For example, assume that an operator wishes to change the 292 configuration of a Label Range which is used by a Session that has 293 already been established. The operator should change the 294 mplsLdpEntityAdminStatus to "disable(2)". Setting the 295 mplsLdpEntityAdminStatus to "disable(2)" will cause the session to be 296 torn down (i.e. this will signal to LDP that it should send out tear 297 down messages for that session). Also, all information related to 298 that session should be removed from this MIB by the Agent. This 299 includes Peer information (i.e. relevant row in the mplsPeerTable) 300 and Session statistics (i.e. relevant row in the 301 mplsLdpSessionTable). Also, if the MPLS-LSR-STD-MIB module [LSRMIB] 302 is implemented and the optional Mapping Table objects are 303 implemented, then all information related to the LSPs in this session 304 should be removed from these MIB modules. [For more information 305 please see the section on "The Mapping Tables".] At this point, the 306 operator could modify the Label Range. Lastly, the operator should 307 set the mplsLdpEntityAdminStatus to "enable(1)". At this point 308 session initialization should occur. The LDP Entity goes through the 309 Session Initialization in order to communicate the new Label Ranges 310 to the Peer and establish new LSPs. 312 3.5.3. The LDP Entity Statistics Table 314 The mplsLpdEntityStatsTable is a read-only table which contains 315 statistical information related to failed attempts to establish 316 sessions. Each row in this table AUGMENTS an mplsLdpEntityEntry. 317 This table could be used to give insight into how to reconfigure 318 values so that a session could be successfully established. For 319 example, if the mplsLdpEntityStatsSessionRejectedLRErrors Counter 320 object was increasing, then this would indicate that the Label Range 321 (LR) may need to be adjusted. 323 3.5.4. The LDP Peer Table 325 The mplsLdpPeerTable is a read-only table which contains information 326 about LDP Peers known to LDP Entities. In other words, the Peer 327 information is learned by LDP through initialization or discovery. 328 This table should be populated by the agent as directed by the LDP 329 protocol. 331 A row in this table is related to one or more rows in the Hello 332 Adjacency Table and related to a single row in the Session Table. 333 The values in the Peer table are specific to a Peer and may or may 334 not be the same values used in the session. The reason is that the 335 Peer and Entity negotiate certain values. The Entity's values are 336 configured in the mplsLdpEntityTable and the Peer's values are 337 learned (and placed into the mplsLdpPeerTable). The 338 mplsLdpSessionTable shows the values used in establishing the 339 session. 341 One example, of when the Peer's values and the Session's values may 342 differ is with the Peer's Path Limit information. The Peer's Path 343 Limit information is learned from the session initialization phase. 344 The actual value for the Path Vector Limit is the Peer's value and 345 may not be the same value that appears in the session. There could 346 be a mismatch in this value between the Entity and the Peer. In the 347 event of a mismatch, then the session will use the Path Limit set by 348 the Entity (and not the Peer). 350 The Peer Table information was placed in a separate table from the 351 Session information to allow for a more comprehensive and coherent 352 MIB model. 354 3.5.5. The LDP Session Table 356 The LDP Session Table is a read-only table. Each entry in this table 357 represents a single session between an LDP Entity and a Peer. The 358 mplsLdpSessionEntry AUGMENTS the mplsLdpPeerEntry. 360 The information in this table is learned during session 361 establishment. NOTE: rows in this table will appear during session 362 intialization. 364 3.5.6. The LDP Session Statistics Table 366 The mplsLdpSessionStatsTable is a read-only table which contains 367 statistical information on sessions. This table AUGMENTS the 368 mplsLdpPeerTable. 370 3.5.7. The LDP Hello Adjacency Table 372 This is a table of all adjacencies between all LDP Entities and all 373 LDP Peers. A Session may have one or more adjacencies. A session 374 should not have zero adjacencies, because this indicates that the 375 session has lost contact with the Peer. A session which has zero 376 Hello Adjacencies should be removed. 378 3.5.8. The LDP LSP Table 380 The Label Information Base (LIB) contains information about labels 381 learned by the LSR. The LIB for LDP, CR-LDP and MPLS-RSVP (i.e. all 382 currently defined MPLS protocols) is represented in the LSR MIB 383 [LSRMIB]. The LIB is represented by the LSR MIB's mplsXCTable (mpls 384 Cross Connect Table), mplsInSegmentTable (mpls In Segment Table) and 385 the mplsOutSegmentTable (mpls Out Segment Table). The mplsXCTable 386 models the cross-connection of the incoming label with a specific 387 outgoing label. The mplsInSegmentTable stores the incoming label's 388 information, and the mplsOutSegmentTable stores the outgoing label's 389 information. 391 The LDP Session that created the LSP and the LSP's (incoming label, 392 outgoing label) pair along with other information is contained in the 393 MPLS-LSR-STD-MIB module's mplsXCTable, the mplsInSegmentTable and the 394 mplsOutSegmentTable. 396 In order to utilize the MPLS-LSR-STD-MIB module's mplsXCTable, 397 mplsInSegmentTable and mplsOutSegmentTable for LDP LSPs, there needs 398 to be a mechanism to associate LDP sessions with LDP LSPs created as 399 a result of those LDP sessions. The mplsInSegmentLdpLspTable and 400 mplsOutSegmentLdpLspTable in this MIB contain information to find the 401 LDP LSP entries in the mplsInSegmentTable, mplsOutSegmentTable and 402 the mplsXCTable. 404 These two tables, the mplsInSegmentLdpLspTable and 405 mplsOutSegmentLdpLspTable, have been made optional in the conformance 406 section of the MIB. They only need to be supported if the LSR MIBs 407 mplsInSegmentTable, mplsOutSegmentTable and mplsXCTable are 408 implemented. 410 As discussed in the section, "Changing Values after Session 411 Establishment", if a session is torn down, then all the information 412 related to this session, must be removed from the both LDP MIB and, 413 if implemented, from the LSR MIB. 415 3.5.9. The FEC Table 417 The FEC Table is a table which contains FEC (Forwarding Equivalence 418 Class) information. Each entry/row represents a single FEC Element. 419 There is also an LDP LSP FEC Table, mplsLdpLspFecTable, which 420 associates FECs with the LSPs. 422 3.5.10. The LDP Session Peer Address Table 424 The MPLS LDP Session Peer Address Table is a table which extends the 425 mplsLdpSessionTable. This table is a read-only table which stores 426 Addresses learned after session initialization via Address Message 427 advertisement. 429 3.6. LDP Notifications 431 Currently, there are several notifications which are specific for 432 LDP. These are described in this section. There are no objects 433 which enable or disable notifications from being generated. RFC 2573 434 [RFC2573] contains MIB modules which can be implemented that will 435 enable or disable these notifications from being generated. 437 The mplsLdpInitSessionThresholdExceeded notification indicates to the 438 operator that there may be a misconfigured mplsLdpEntityEntry because 439 the session associated with this Entity is not being established, and 440 the Entity keeps trying to establish the session. A side effect of 441 this situation is that a row in the mplsLdpSessionTable may not be 442 reaching the operational state as indicated by the 443 mplsLdpSessionState object. If the value of 444 mplsLdpEntityInitSessionThreshold is 0 (zero) then this is equal to 445 specifying the value of infinity for the threshold, and the 446 mplsLdpInitSessionThresholdExceeded notification will never be sent. 448 The mplsLdpPathVectorLimitMismatch notification is generated when 449 there is a mismatch in the Path Vector Limits between the Entity and 450 Peer during session initialization. The session uses the value which 451 is configured as the Entity's Path Vector Limit. However, a 452 notification should be generated to indicate that a mismatch 453 occurred. For further details, please see Section 3.5.3 of the LDP 454 Specification [RFC3036]. 456 The mplsLdpSessionUp and mplsLdpSessionDown notifications are 457 generated when there is an appropriate change in the 458 mplsLdpSessionState object, e.g. when sessions change state (Up to 459 Down for the mplsLdpSessionDown notification, or Down to Up for the 460 mplsLdpSessionUp notification). There was discussion about combining 461 these two notifications into a single notification, however, some NMS 462 applications can utilize two different notifications, rather than 463 having to parse the varbind list of a single notification. For 464 example, the SessionDown is matched to a SessionUp notification more 465 easily by some NMS applications, than having to parse a Varbind list 466 in a SessionChange type of notification. 468 3.7. LDP Notification Frequency 470 LDP Notifications are expected to be few in number when LDP is 471 ubiquitously deployed in a relatively stable network. A notification 472 receiver, e.g. an NMS, that receives these notifications should not 473 be overwhelmed by the frequency of LDP notifications. If this 474 assertion proves to be inaccurate, then a throttling object to 475 throttle these notifications may be added to future versions of the 476 MPLS-LDP-STD-MIB. 478 4. MPLS Label Distribution Protocol MIB Definitions 480 MPLS-LDP-STD-MIB DEFINITIONS ::= BEGIN 482 IMPORTS 483 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, 484 Integer32, Counter32, Unsigned32 485 FROM SNMPv2-SMI 486 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 487 FROM SNMPv2-CONF 489 RowStatus, TimeInterval, TruthValue, 490 TimeStamp, StorageType 491 FROM SNMPv2-TC 493 InetAddressPrefixLength, 494 InetAddressType, 495 InetAddress, 496 InetPortNumber 497 FROM INET-ADDRESS-MIB 499 IndexInteger, 500 IndexIntegerNextFree 501 FROM DIFFSERV-MIB 503 mplsStdMIB, 504 MplsLabelDistributionMethod, 505 MplsLdpIdentifier, 506 MplsLdpLabelType, 507 MplsLspType, 508 MplsLsrIdentifier, 509 MplsRetentionMode 510 FROM MPLS-TC-STD-MIB 512 MplsIndexType 513 FROM MPLS-LSR-STD-MIB; 515 mplsLdpStdMIB MODULE-IDENTITY 516 LAST-UPDATED "200306281200Z" -- 28 June 2003 517 ORGANIZATION "Multiprotocol Label Switching (mpls) 518 Working Group" 519 CONTACT-INFO 521 "Joan Cucchiara (jcucchiara@artel.com) 522 Artel 524 Hans Sjostrand (hans@ipunplugged.com) 525 ipUnplugged 527 James V. Luciani (james_luciani@mindspring.com) 528 Consultant 530 Working Group Chairs: 531 George Swallow, email: swallow@cisco.com 532 Loa Andersson, email: loa@pi.se 534 MPLS Working Group, email: mpls@uu.net" 536 DESCRIPTION 537 "Copyright (C) The Internet Society (2003). This 538 version of this MIB module is part of RFCXXX; see 539 the RFC itself for full legal notices. 541 This MIB contains managed object definitions for the 542 'Multiprotocol Label Switching, Label Distribution 543 Protocol, LDP' document." 545 REVISION "200306281200Z" -- 28 June 2003 546 DESCRIPTION 547 "Initial version published as part of RFC XXXX." 549 -- Please see the IANA Considerations Section. 550 -- The requested mplsStdMIB subId is 4, e.g. 551 -- ::= { mplsStdMIB 4 } 553 ::= { mplsStdMIB XXX } -- to be assigned by IANA 555 --**************************************************************** 557 mplsLdpNotifications OBJECT IDENTIFIER ::= { mplsLdpStdMIB 0 } 558 mplsLdpObjects OBJECT IDENTIFIER ::= { mplsLdpStdMIB 1 } 559 mplsLdpConformance OBJECT IDENTIFIER ::= { mplsLdpStdMIB 2 } 561 --**************************************************************** 562 -- MPLS LDP Objects 563 --**************************************************************** 565 mplsLdpLsrObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 1 } 567 mplsLdpEntityObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 2 } 569 -- 570 -- The MPLS Label Distribution Protocol's 571 -- Label Switching Router Objects 572 -- 573 mplsLdpLsrId OBJECT-TYPE 574 SYNTAX MplsLsrIdentifier 575 MAX-ACCESS read-only 576 STATUS current 577 DESCRIPTION 578 "The Label Switching Router's Identifier." 579 ::= { mplsLdpLsrObjects 1 } 581 mplsLdpLsrLoopDetectionCapable OBJECT-TYPE 582 SYNTAX INTEGER { 583 none(1), 584 other(2), 585 hopCount(3), 586 pathVector(4), 587 hopCountAndPathVector(5) 588 } 589 MAX-ACCESS read-only 590 STATUS current 591 DESCRIPTION 592 "A indication of whether this 593 Label Switching Router supports 594 loop detection. 596 none(1) -- Loop Detection is not supported 597 on this LSR. 599 other(2) -- Loop Detection is supported but 600 by a method other than those 601 listed below. 603 hopCount(3) -- Loop Detection is supported by 604 Hop Count only. 606 pathVector(4) -- Loop Detection is supported by 607 Path Vector only. 609 hopCountAndPathVector(5) -- Loop Detection is 610 supported by both Hop Count 611 And Path Vector. 613 Since Loop Detection is determined during 614 Session Initialization, an individual session 615 may not be running with loop detection. This 616 object simply gives an indication of whether or not the 617 LSR has the ability to support Loop Detection and 618 which types." 620 ::= { mplsLdpLsrObjects 2 } 622 -- 623 -- The MPLS Label Distribution Protocol Entity Objects 624 -- 626 mplsLdpEntityLastChange OBJECT-TYPE 627 SYNTAX TimeStamp 628 MAX-ACCESS read-only 629 STATUS current 630 DESCRIPTION 631 "The value of sysUpTime at the time of the most 632 recent addition or deletion of an entry 633 to/from the mplsLdpEntityTable/mplsLdpEntityStatsTable, or 634 the most recent change in value of any objects in the 635 mplsLdpEntityTable. 637 If no such changes have occurred since the last 638 re-initialization of the local management subsystem, 639 then this object contains a zero value." 640 ::= { mplsLdpEntityObjects 1 } 642 mplsLdpEntityIndexNext OBJECT-TYPE 643 SYNTAX IndexIntegerNextFree 644 MAX-ACCESS read-only 645 STATUS current 646 DESCRIPTION 647 "This object contains an appropriate value to 648 be used for mplsLdpEntityIndex when creating 649 entries in the mplsLdpEntityTable. The value 650 0 indicates that no unassigned entries are 651 available." 652 ::= { mplsLdpEntityObjects 2 } 654 mplsLdpEntityTable OBJECT-TYPE 655 SYNTAX SEQUENCE OF MplsLdpEntityEntry 656 MAX-ACCESS not-accessible 657 STATUS current 658 DESCRIPTION 659 "This table contains information about the 660 MPLS Label Distribution Protocol Entities which 661 exist on this Label Switching Router (LSR) 662 or Label Edge Router (LER)." 664 ::= { mplsLdpEntityObjects 3 } 666 mplsLdpEntityEntry OBJECT-TYPE 667 SYNTAX MplsLdpEntityEntry 668 MAX-ACCESS not-accessible 669 STATUS current 670 DESCRIPTION 671 "An entry in this table represents an LDP entity. 672 An entry can be created by a network administrator 673 or by an SNMP agent as instructed by LDP." 674 INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex } 675 ::= { mplsLdpEntityTable 1 } 677 MplsLdpEntityEntry ::= SEQUENCE { 678 mplsLdpEntityLdpId MplsLdpIdentifier, 679 mplsLdpEntityIndex IndexInteger, 680 mplsLdpEntityProtocolVersion Unsigned32, 681 mplsLdpEntityAdminStatus INTEGER, 682 mplsLdpEntityOperStatus INTEGER, 683 mplsLdpEntityTcpDscPort InetPortNumber, 684 mplsLdpEntityUdpDscPort InetPortNumber, 685 mplsLdpEntityMaxPduLength Unsigned32, 686 mplsLdpEntityKeepAliveHoldTimer Unsigned32, 687 mplsLdpEntityHelloHoldTimer Unsigned32, 688 mplsLdpEntityInitSessionThreshold Integer32, 689 mplsLdpEntityLabelDistMethod MplsLabelDistributionMethod, 690 mplsLdpEntityLabelRetentionMode MplsRetentionMode, 691 mplsLdpEntityPathVectorLimit Integer32, 692 mplsLdpEntityHopCountLimit Integer32, 693 mplsLdpEntityTransportAddrKind INTEGER, 694 mplsLdpEntityTargetPeer TruthValue, 695 mplsLdpEntityTargetPeerAddrType InetAddressType, 696 mplsLdpEntityTargetPeerAddr InetAddress, 697 mplsLdpEntityLabelType MplsLdpLabelType, 698 mplsLdpEntityDiscontinuityTime TimeStamp, 699 mplsLdpEntityStorageType StorageType, 700 mplsLdpEntityRowStatus RowStatus 701 } 703 mplsLdpEntityLdpId OBJECT-TYPE 704 SYNTAX MplsLdpIdentifier 705 MAX-ACCESS not-accessible 706 STATUS current 707 DESCRIPTION 708 "The LDP identifier." 710 REFERENCE 711 "RFC3036, LDP Specification, Section on LDP Identifiers." 712 ::= { mplsLdpEntityEntry 1 } 714 mplsLdpEntityIndex OBJECT-TYPE 715 SYNTAX IndexInteger 716 MAX-ACCESS not-accessible 717 STATUS current 718 DESCRIPTION 719 "This index is used as a secondary index to uniquely 720 identify this row. Before creating a row in this table, 721 the 'mplsLdpEntityIndexNext' object should be retrieved. 722 That value should be used for the value of this index 723 when creating a row in this table. NOTE: if a value 724 of zero (0) is retrieved, that indicates that no rows 725 can be created in this table at this time. 727 A secondary index (this object) is meaningful to some 728 but not all, LDP implementations. For example 729 an LDP implementation which uses PPP would 730 use this index to differentiate PPP sub-links. 732 Another way to use this index is to give this the 733 value of ifIndex. However, this is dependant 734 on the implementation." 735 ::= { mplsLdpEntityEntry 2 } 737 mplsLdpEntityProtocolVersion OBJECT-TYPE 738 SYNTAX Unsigned32(1..65535) 739 MAX-ACCESS read-create 740 STATUS current 741 DESCRIPTION 742 "The version number of the LDP protocol which will be 743 used in the session initialization message. 745 Section 3.5.3 in the LDP Specification specifies 746 that the version of the LDP protocol is negotiated during 747 session establishment. The value of this object 748 represents the value that is sent in the initialization 749 message." 750 REFERENCE 751 "RFC3036, LDP Specification, Section 3.5.3 Initialization 752 Message." 753 DEFVAL { 1 } 754 ::= { mplsLdpEntityEntry 3 } 756 mplsLdpEntityAdminStatus OBJECT-TYPE 757 SYNTAX INTEGER { 758 enable(1), 759 disable(2) 760 } 761 MAX-ACCESS read-create 762 STATUS current 763 DESCRIPTION 764 "The administrative status of this LDP Entity. 765 If this object is changed from 'enable' to 'disable' 766 and this entity has already attempted to establish 767 contact with a Peer, then all contact with that 768 Peer is lost and all information from that Peer 769 needs to be removed from the MIB. (This implies 770 that the network management subsystem should clean 771 up any related entry in the mplsLdpPeerTable. This 772 further implies that a 'tear-down' for that session 773 is issued and the session and all information related 774 to that session cease to exist). 776 At this point the operator is able to change values 777 which are related to this entity. 779 When the admin status is set back to 'enable', then 780 this Entity will attempt to establish a new session 781 with the Peer." 782 DEFVAL { enable } 783 ::= { mplsLdpEntityEntry 4 } 785 mplsLdpEntityOperStatus OBJECT-TYPE 786 SYNTAX INTEGER { 787 unknown(1), 788 enabled(2), 789 disabled(3) 790 } 791 MAX-ACCESS read-only 792 STATUS current 793 DESCRIPTION 794 "The operational status of this LDP Entity. 796 The value of unknown(1) indicates that the 797 operational status cannot be determined at 798 this time. The value of unknown should be 799 a transient condition before changing 800 to enabled(2) or disabled(3)." 802 ::= { mplsLdpEntityEntry 5 } 804 mplsLdpEntityTcpDscPort OBJECT-TYPE 805 SYNTAX InetPortNumber 806 MAX-ACCESS read-create 807 STATUS current 808 DESCRIPTION 809 "The TCP Discovery Port for 810 LDP. The default value is the well-known 811 value of this port." 812 REFERENCE 813 "RFC3036, LDP Specification, Section 2.4.1, 814 Basic Discovery Mechanism, Section 2.4.2, 815 Extended Discovery Mechanism, Section 816 3.10, Well-known Numbers, and Section 3.10.1. 817 UDP and TCP Ports." 818 DEFVAL { 646 } 819 ::= { mplsLdpEntityEntry 6 } 821 mplsLdpEntityUdpDscPort OBJECT-TYPE 822 SYNTAX InetPortNumber 823 MAX-ACCESS read-create 824 STATUS current 825 DESCRIPTION 826 "The UDP Discovery Port for 827 LDP. The default value is the 828 well-known value for this port." 829 REFERENCE 830 "RFC3036, LDP Specification, Section 2.4.1, 831 Basic Discovery Mechanism, Section 2.4.2, 832 Extended Discovery Mechanism, Section 833 3.10, Well-known Numbers, and Section 3.10.1. 834 UDP and TCP Ports." 835 DEFVAL { 646 } 836 ::= { mplsLdpEntityEntry 7 } 838 mplsLdpEntityMaxPduLength OBJECT-TYPE 839 SYNTAX Unsigned32 (256..65535) 840 UNITS "octets" 841 MAX-ACCESS read-create 842 STATUS current 843 DESCRIPTION 844 "The maximum PDU Length that is sent in 845 the Common Session Parameters of an Initialization 846 Message. According to the LDP Specification [RFC3036] 847 a value of 255 or less specifies the 848 default maximum length of 4096 octets, this is why 849 the value of this object starts at 256. The operator 850 should explicitly choose the default value (i.e. 4096), 851 or some other value. 853 The receiving LSR MUST calculate the maximum PDU 854 length for the session by using the smaller of its and 855 its peer's proposals for Max PDU Length." 856 REFERENCE 857 "RFC3036, LDP Specification, Section 3.5.3. 858 Initialization Message." 859 DEFVAL { 4096 } 860 ::= { mplsLdpEntityEntry 8 } 862 mplsLdpEntityKeepAliveHoldTimer OBJECT-TYPE 863 SYNTAX Unsigned32 (1..65535) 864 UNITS "seconds" 865 MAX-ACCESS read-create 866 STATUS current 867 DESCRIPTION 868 "The 16-bit integer value which is the proposed keep 869 alive hold timer for this LDP Entity." 870 DEFVAL { 40 } 871 ::= { mplsLdpEntityEntry 9 } 873 mplsLdpEntityHelloHoldTimer OBJECT-TYPE 874 SYNTAX Unsigned32 (0..65535) 875 UNITS "seconds" 876 MAX-ACCESS read-create 877 STATUS current 878 DESCRIPTION 879 "The 16-bit integer value which is the proposed Hello 880 hold timer for this LDP Entity. The Hello Hold time 881 in seconds. 883 An LSR maintains a record of Hellos received 884 from potential peers. This object represents 885 the Hold Time in the Common Hello Parameters TLV of 886 the Hello Message. 888 A value of 0 is a default value and should be 889 interpretted in conjunction with the 890 mplsLdpEntityTargetPeer object. 892 If the value of this object is 0: if the value of the 893 mplsLdpEntityTargetPeer object is false(2), then this 894 specifies that the Hold Time's actual default value is 895 15 seconds (i.e. the default Hold time for Link Hellos 896 is 15 seconds). Otherwise if the value of the 897 mplsLdpEntityTargetPeer object is true(1), then this 898 specifies that the Hold Time's actual default value is 899 45 seconds (i.e. the default Hold time for Targeted 900 Hellos is 45 seconds). 902 A value of 65535 means infinite (i.e. wait forever). 904 All other values represent the amount of time in 905 seconds to wait for a Hello Message. Setting the 906 hold time to a value smaller than 15 is not 907 recommended, although not forbidden according 908 to RFC3036." 909 REFERENCE 910 "RFC3036, LDP Specification, Section 3.5.2., 911 Hello Message." 912 DEFVAL { 0 } 913 ::= { mplsLdpEntityEntry 10 } 915 mplsLdpEntityInitSessionThreshold OBJECT-TYPE 916 SYNTAX Integer32(0..100) 917 MAX-ACCESS read-create 918 STATUS current 919 DESCRIPTION 920 "When attempting to establish a session with 921 a given Peer, the given LDP Entity should 922 send out the SNMP notification, 923 'mplsLdpInitSessionThresholdExceeded', when 924 the number of Session Initialization messages 925 sent exceeds this threshold. 927 The notification is used to notify an 928 operator when this Entity and its Peer are 929 possibily engaged in an endless sequence 930 of messages as each NAKs the other's 931 Initialization messages with Error Notification 932 messages. Setting this threshold which triggers 933 the notification is one way to notify the 934 operator. The notification should be generated 935 each time this threshold is exceeded and 936 for every subsequent Initialization message 937 which is NAK'd with an Error Notification 938 message after this threshold is exceeded. 940 A value of 0 (zero) for this object 941 indicates that the threshold is infinity, thus 942 the SNMP notification will never be generated." 943 REFERENCE 944 "RFC3036, LDP Specification, 945 Section 2.5.3 Session Initialization." 946 DEFVAL { 8 } 947 ::= { mplsLdpEntityEntry 11 } 949 mplsLdpEntityLabelDistMethod OBJECT-TYPE 950 SYNTAX MplsLabelDistributionMethod 951 MAX-ACCESS read-create 952 STATUS current 953 DESCRIPTION 954 "For any given LDP session, the method of 955 label distribution must be specified." 956 ::= { mplsLdpEntityEntry 12 } 958 mplsLdpEntityLabelRetentionMode OBJECT-TYPE 959 SYNTAX MplsRetentionMode 960 MAX-ACCESS read-create 961 STATUS current 962 DESCRIPTION 963 "The LDP Entity can be configured to use either 964 conservative or liberal label retention mode. 966 If the value of this object is conservative(1) 967 then advertized label mappings are retained 968 only if they will be used to forward packets, 969 i.e. if label came from a valid next hop. 971 If the value of this object is liberal(2) 972 then all advertized label mappings are retained 973 whether they are from a valid next hop or not." 974 ::= { mplsLdpEntityEntry 13 } 976 mplsLdpEntityPathVectorLimit OBJECT-TYPE 977 SYNTAX Integer32 (0..255) 978 MAX-ACCESS read-create 979 STATUS current 980 DESCRIPTION 981 "If the value of this object is 0 (zero) then 982 Loop Dection for Path Vectors is disabled. 984 Otherwise, if this object has a value greater than 985 zero, then Loop Dection for Path Vectors is enabled, 986 and the Path Vector Limit is this value. 987 Also, the value of the object, 988 'mplsLdpLsrLoopDetectionCapable', must be set to 989 either 'pathVector(4)' or 'hopCountAndPathVector(5)', 990 if this object has a value greater than 0 (zero), 991 otherwise it is ignored." 992 REFERENCE 993 "RFC3036, LDP Specification, Section 2.8 Loop Dection, 994 Section 3.4.5 Path Vector TLV." 995 ::= { mplsLdpEntityEntry 14 } 997 mplsLdpEntityHopCountLimit OBJECT-TYPE 998 SYNTAX Integer32 (0..255) 999 MAX-ACCESS read-create 1000 STATUS current 1001 DESCRIPTION 1002 "If the value of this object is 0 (zero), 1003 then Loop Detection using Hop Counters is 1004 disabled. 1006 If the value of this object is greater than 1007 0 (zero) then Loop Detection using Hop 1008 Counters is enabled, and this object 1009 specifies this Entity's maximum allowable 1010 value for the Hop Count. 1011 Also, the value of the object 1012 mplsLdpLsrLoopDetectionCapable must be set 1013 to either 'hopCount(3)' or 1014 'hopCountAndPathVector(5)' if this object 1015 has a value greater than 0 (zero), otherwise 1016 it is ignored." 1017 DEFVAL { 0 } 1018 ::= { mplsLdpEntityEntry 15 } 1020 mplsLdpEntityTransportAddrKind OBJECT-TYPE 1021 SYNTAX INTEGER { 1022 interface(1), 1023 loopback(2) 1024 } 1025 MAX-ACCESS read-create 1026 STATUS current 1027 DESCRIPTION 1028 "This specifies whether the loopback or interface 1029 address is to be used as the transport address 1030 in the transport address TLV of the 1031 hello message. 1033 If the value is interface(1), then the IP 1034 address of the interface from which hello 1035 messages are sent is used as the transport 1036 address in the hello message. 1038 Otherwise, if the value is loopback(2), then the IP 1039 address of the loopback interface is used as the 1040 transport address in the hello message." 1041 DEFVAL { loopback } 1042 ::= { mplsLdpEntityEntry 16 } 1044 mplsLdpEntityTargetPeer OBJECT-TYPE 1045 SYNTAX TruthValue 1046 MAX-ACCESS read-create 1047 STATUS current 1048 DESCRIPTION 1049 "If this LDP entity uses targeted peer then set 1050 this to true." 1051 DEFVAL { false } 1052 ::= { mplsLdpEntityEntry 17 } 1054 mplsLdpEntityTargetPeerAddrType OBJECT-TYPE 1055 SYNTAX InetAddressType 1056 MAX-ACCESS read-create 1057 STATUS current 1058 DESCRIPTION 1059 "The type of the internetwork layer address used for 1060 the Extended Discovery. This object indicates how 1061 the value of mplsLdpEntityTargetPeerAddr is to 1062 be interpreted." 1063 ::= { mplsLdpEntityEntry 18 } 1065 mplsLdpEntityTargetPeerAddr OBJECT-TYPE 1066 SYNTAX InetAddress 1067 MAX-ACCESS read-create 1068 STATUS current 1069 DESCRIPTION 1070 "The value of the internetwork layer address 1071 used for the Extended Discovery. The value of 1072 mplsLdpEntityTargetPeerAddrType specifies how 1073 this address is to be intepreted." 1074 ::= { mplsLdpEntityEntry 19 } 1076 mplsLdpEntityLabelType OBJECT-TYPE 1077 SYNTAX MplsLdpLabelType 1078 MAX-ACCESS read-create 1079 STATUS current 1080 DESCRIPTION 1081 "Specifies the optional parameters for the LDP 1082 Initialization Message. 1084 If the value is generic(1) then no 1085 optional parameters will be sent in 1086 the LDP Initialization message associated 1087 with this Entity. 1089 If the value is atmParameters(2) then 1090 a row must be created in the 1091 mplsLdpEntityAtmTable, which 1092 corresponds to this entry. 1094 If the value is frameRelayParameters(3) then 1095 a row must be created in the 1096 mplsLdpEntityFrameRelayTable, which 1097 corresponds to this entry." 1098 REFERENCE 1099 "RFC3036, LDP Specification, Section 3.5.3., 1100 Initialization Message." 1101 ::= { mplsLdpEntityEntry 20 } 1103 mplsLdpEntityDiscontinuityTime OBJECT-TYPE 1104 SYNTAX TimeStamp 1105 MAX-ACCESS read-only 1106 STATUS current 1107 DESCRIPTION 1108 "The value of sysUpTime on the most recent occasion 1109 at which any one or more of this entity's counters 1110 suffered a discontinuity. The relevant counters 1111 are the specific instances associated with this 1112 entity of any Counter32 object contained 1113 in the 'mplsLdpEntityStatsTable'. If no such 1114 discontinuities have occurred since the last 1115 re-initialization of the local management 1116 subsystem, then this object contains a zero 1117 value." 1118 ::= { mplsLdpEntityEntry 21 } 1120 mplsLdpEntityStorageType OBJECT-TYPE 1121 SYNTAX StorageType 1122 MAX-ACCESS read-create 1123 STATUS current 1124 DESCRIPTION 1125 "The storage type for this conceptual row. 1126 Conceptual rows having the value 'permanent(4)' 1127 need not allow write-access to any columnar 1128 objects in the row." 1129 DEFVAL{ nonVolatile } 1130 ::= { mplsLdpEntityEntry 22 } 1132 mplsLdpEntityRowStatus OBJECT-TYPE 1133 SYNTAX RowStatus 1134 MAX-ACCESS read-create 1135 STATUS current 1136 DESCRIPTION 1137 "The status of this conceptual row. All writable 1138 objects in this row may be modified at any 1139 time, however, as described in detail in 1140 the section entitled, 'Changing Values After 1141 Session Establishment', and again described 1142 in the DESCRIPTION clause of the 1143 mplsLdpEntityAdminStatus object, if a session 1144 has been initiated with a Peer, changing objects 1145 in this table will wreak havoc with the session 1146 and interrupt traffic. To repeat again: 1147 the recommended procedure is to 1148 set the mplsLdpEntityAdminStatus to down, thereby 1149 explicitly causing a session to be torn down. Then, 1150 change objects in this entry, then set 1151 the mplsLdpEntityAdminStatus to enable, 1152 which enables a new session to be initiated." 1153 ::= { mplsLdpEntityEntry 23 } 1155 -- 1156 -- The MPLS LDP Entity Statistics Table 1157 -- 1159 mplsLdpEntityStatsTable OBJECT-TYPE 1160 SYNTAX SEQUENCE OF MplsLdpEntityStatsEntry 1161 MAX-ACCESS not-accessible 1162 STATUS current 1163 DESCRIPTION 1164 "This table is a read-only table which augments 1165 the mplsLdpEntityTable. The purpose of this 1166 table is to keep statistical information about 1167 the LDP Entities on the LSR." 1168 ::= { mplsLdpEntityObjects 4 } 1170 mplsLdpEntityStatsEntry OBJECT-TYPE 1171 SYNTAX MplsLdpEntityStatsEntry 1172 MAX-ACCESS not-accessible 1173 STATUS current 1174 DESCRIPTION 1175 "A row in this table contains statistical information 1176 about an LDP Entity. Some counters contained in a 1177 row are for fatal errors received during a former 1178 LDP Session associated with this entry. For example, 1179 an LDP PDU received on a TCP connection during an 1180 LDP Session contains a fatal error. That 1181 error is counted here, because the 1182 session is terminated. 1184 If the error is NOT fatal (i.e. the Session 1185 remains), then the error is counted in the 1186 mplsLdpSessionStatsEntry." 1187 AUGMENTS { mplsLdpEntityEntry } 1188 ::= { mplsLdpEntityStatsTable 1 } 1190 MplsLdpEntityStatsEntry ::= SEQUENCE { 1191 mplsLdpEntityStatsSessionAttempts Counter32, 1192 mplsLdpEntityStatsSessionRejectedNoHelloErrors Counter32, 1193 mplsLdpEntityStatsSessionRejectedAdErrors Counter32, 1194 mplsLdpEntityStatsSessionRejectedMaxPduErrors Counter32, 1195 mplsLdpEntityStatsSessionRejectedLRErrors Counter32, 1196 mplsLdpEntityStatsBadLdpIdentifierErrors Counter32, 1197 mplsLdpEntityStatsBadPduLengthErrors Counter32, 1198 mplsLdpEntityStatsBadMessageLengthErrors Counter32, 1199 mplsLdpEntityStatsBadTlvLengthErrors Counter32, 1200 mplsLdpEntityStatsMalformedTlvValueErrors Counter32, 1201 mplsLdpEntityStatsKeepAliveTimerExpErrors Counter32, 1202 mplsLdpEntityStatsShutdownReceivedNotifications Counter32, 1203 mplsLdpEntityStatsShutdownSentNotifications Counter32 1204 } 1206 mplsLdpEntityStatsSessionAttempts OBJECT-TYPE 1207 SYNTAX Counter32 1208 MAX-ACCESS read-only 1209 STATUS current 1210 DESCRIPTION 1211 "A count of the Session Initialization messages 1212 which were sent or received by this LDP Entity and 1213 were NAK'd. In other words, this counter counts 1214 the number of session initializations that failed. 1216 Discontinuities in the value of this counter can occur 1217 at re-initialization of the management system, and at 1218 other times as indicated by the value of 1219 mplsLdpEntityDiscontinuityTime." 1220 ::= { mplsLdpEntityStatsEntry 1 } 1222 mplsLdpEntityStatsSessionRejectedNoHelloErrors OBJECT-TYPE 1223 SYNTAX Counter32 1224 MAX-ACCESS read-only 1225 STATUS current 1226 DESCRIPTION 1227 "A count of the Session Rejected/No Hello Error 1228 Notification Messages sent or received by 1229 this LDP Entity. 1231 Discontinuities in the value of this counter can occur 1232 at re-initialization of the management system, and at 1233 other times as indicated by the value of 1234 mplsLdpEntityDiscontinuityTime." 1235 ::= { mplsLdpEntityStatsEntry 2 } 1237 mplsLdpEntityStatsSessionRejectedAdErrors OBJECT-TYPE 1238 SYNTAX Counter32 1239 MAX-ACCESS read-only 1240 STATUS current 1241 DESCRIPTION 1242 "A count of the Session Rejected/Parameters 1243 Advertisement Mode Error Notification Messages sent 1244 or received by 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 ::= { mplsLdpEntityStatsEntry 3 } 1252 mplsLdpEntityStatsSessionRejectedMaxPduErrors OBJECT-TYPE 1253 SYNTAX Counter32 1254 MAX-ACCESS read-only 1255 STATUS current 1256 DESCRIPTION 1257 "A count of the Session Rejected/Parameters 1258 Max Pdu Length Error Notification Messages sent 1259 or received by this LDP Entity. 1261 Discontinuities in the value of this counter can occur 1262 at re-initialization of the management system, and at 1263 other times as indicated by the value of 1264 mplsLdpEntityDiscontinuityTime." 1265 ::= { mplsLdpEntityStatsEntry 4 } 1267 mplsLdpEntityStatsSessionRejectedLRErrors OBJECT-TYPE 1268 SYNTAX Counter32 1269 MAX-ACCESS read-only 1270 STATUS current 1271 DESCRIPTION 1272 "A count of the Session Rejected/Parameters 1273 Label Range Notification Messages sent 1274 or received by this LDP Entity. 1276 Discontinuities in the value of this counter can occur 1277 at re-initialization of the management system, and at 1278 other times as indicated by the value of 1279 mplsLdpEntityDiscontinuityTime." 1280 ::= { mplsLdpEntityStatsEntry 5 } 1282 mplsLdpEntityStatsBadLdpIdentifierErrors OBJECT-TYPE 1283 SYNTAX Counter32 1284 MAX-ACCESS read-only 1285 STATUS current 1286 DESCRIPTION 1287 "This object counts the number of Bad LDP Identifier 1288 Fatal Errors detected by the session(s) 1289 (past and present) associated with this LDP Entity. 1291 Discontinuities in the value of this counter can occur 1292 at re-initialization of the management system, and at 1293 other times as indicated by the value of 1294 mplsLdpEntityDiscontinuityTime." 1295 REFERENCE 1296 "RFC3036, LDP Specification, Section 3.5.1.2." 1297 ::= { mplsLdpEntityStatsEntry 6 } 1299 mplsLdpEntityStatsBadPduLengthErrors OBJECT-TYPE 1300 SYNTAX Counter32 1301 MAX-ACCESS read-only 1302 STATUS current 1303 DESCRIPTION 1304 "This object counts the number of Bad PDU Length 1305 Fatal Errors detected by the session(s) 1306 (past and present) associated with this LDP Entity. 1308 Discontinuities in the value of this counter can occur 1309 at re-initialization of the management system, and at 1310 other times as indicated by the value of 1311 mplsLdpEntityDiscontinuityTime." 1312 REFERENCE 1313 "RFC3036, LDP Specification, Section 3.5.1.2." 1314 ::= { mplsLdpEntityStatsEntry 7 } 1316 mplsLdpEntityStatsBadMessageLengthErrors OBJECT-TYPE 1317 SYNTAX Counter32 1318 MAX-ACCESS read-only 1319 STATUS current 1320 DESCRIPTION 1321 "This object counts the number of Bad Message 1322 Length Fatal Errors detected by the session(s) 1323 (past and present) associated with this LDP Entity. 1325 Discontinuities in the value of this counter can occur 1326 at re-initialization of the management system, and at 1327 other times as indicated by the value of 1328 mplsLdpEntityDiscontinuityTime." 1329 REFERENCE 1330 "RFC3036, LDP Specification, Section 3.5.1.2." 1331 ::= { mplsLdpEntityStatsEntry 8 } 1333 mplsLdpEntityStatsBadTlvLengthErrors OBJECT-TYPE 1334 SYNTAX Counter32 1335 MAX-ACCESS read-only 1336 STATUS current 1337 DESCRIPTION 1338 "This object counts the number of Bad TLV 1339 Length Fatal Errors detected by the session(s) 1340 (past and present) associated with this LDP Entity. 1342 Discontinuities in the value of this counter can occur 1343 at re-initialization of the management system, and at 1344 other times as indicated by the value of 1345 mplsLdpEntityDiscontinuityTime." 1346 REFERENCE 1347 "RFC3036, LDP Specification, Section 3.5.1.2." 1348 ::= { mplsLdpEntityStatsEntry 9 } 1350 mplsLdpEntityStatsMalformedTlvValueErrors OBJECT-TYPE 1351 SYNTAX Counter32 1352 MAX-ACCESS read-only 1353 STATUS current 1354 DESCRIPTION 1355 "This object counts the number of Malformed TLV 1356 Value Fatal Errors detected by the session(s) 1357 (past and present) associated with this 1358 LDP Entity. 1360 Discontinuities in the value of this counter can occur 1361 at re-initialization of the management system, and at 1362 other times as indicated by the value of 1363 mplsLdpEntityDiscontinuityTime." 1364 REFERENCE 1365 "RFC3036, LDP Specification, Section 3.5.1.2." 1366 ::= { mplsLdpEntityStatsEntry 10 } 1368 mplsLdpEntityStatsKeepAliveTimerExpErrors OBJECT-TYPE 1369 SYNTAX Counter32 1370 MAX-ACCESS read-only 1371 STATUS current 1372 DESCRIPTION 1373 "This object counts the number of Session Keep Alive 1374 Timer Expired Errors detected by the session(s) 1375 (past and present) associated with this LDP Entity. 1377 Discontinuities in the value of this counter can occur 1378 at re-initialization of the management system, and at 1379 other times as indicated by the value of 1380 mplsLdpEntityDiscontinuityTime." 1381 REFERENCE 1382 "RFC3036, LDP Specification, Section 3.5.1.2." 1383 ::= { mplsLdpEntityStatsEntry 11 } 1385 mplsLdpEntityStatsShutdownReceivedNotifications OBJECT-TYPE 1386 SYNTAX Counter32 1387 MAX-ACCESS read-only 1388 STATUS current 1389 DESCRIPTION 1390 "This object counts the number of Shutdown Notfications 1391 received related to session(s) (past and present) 1392 associated with this LDP Entity. 1394 Discontinuities in the value of this counter can occur 1395 at re-initialization of the management system, and at 1396 other times as indicated by the value of 1397 mplsLdpEntityDiscontinuityTime." 1398 ::= { mplsLdpEntityStatsEntry 12 } 1400 mplsLdpEntityStatsShutdownSentNotifications OBJECT-TYPE 1401 SYNTAX Counter32 1402 MAX-ACCESS read-only 1403 STATUS current 1404 DESCRIPTION 1405 "This object counts the number of Shutdown Notfications 1406 sent related to session(s) (past and present) associated 1407 with this LDP Entity. 1409 Discontinuities in the value of this counter can occur 1410 at re-initialization of the management system, and at 1411 other times as indicated by the value of 1412 mplsLdpEntityDiscontinuityTime." 1413 ::= { mplsLdpEntityStatsEntry 13 } 1415 -- 1416 -- The MPLS LDP Peer Table 1417 -- 1419 mplsLdpSessionObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 3 } 1421 mplsLdpPeerLastChange OBJECT-TYPE 1422 SYNTAX TimeStamp 1423 MAX-ACCESS read-only 1424 STATUS current 1425 DESCRIPTION 1426 "The value of sysUpTime at the time of the most 1427 recent addition or deletion to/from the 1428 mplsLdpPeerTable/mplsLdpSessionTable." 1429 ::= { mplsLdpSessionObjects 1 } 1431 mplsLdpPeerTable OBJECT-TYPE 1432 SYNTAX SEQUENCE OF MplsLdpPeerEntry 1433 MAX-ACCESS not-accessible 1434 STATUS current 1435 DESCRIPTION 1436 "Information about LDP peers known by Entities in 1437 the mplsLdpEntityTable. The information in this table 1438 is based on information from the Entity-Peer interaction 1439 during session initialization but is not appropriate 1440 for the mplsLdpSessionTable, because objects in this 1441 table may or may not be used in session establishment." 1442 ::= { mplsLdpSessionObjects 2 } 1444 mplsLdpPeerEntry OBJECT-TYPE 1445 SYNTAX MplsLdpPeerEntry 1446 MAX-ACCESS not-accessible 1447 STATUS current 1448 DESCRIPTION 1449 "Information about a single Peer which is related 1450 to a Session. This table is augmented by 1451 the mplsLdpSessionTable." 1452 INDEX { mplsLdpEntityLdpId, 1453 mplsLdpEntityIndex, 1454 mplsLdpPeerLdpId } 1455 ::= { mplsLdpPeerTable 1 } 1457 MplsLdpPeerEntry ::= SEQUENCE { 1458 mplsLdpPeerLdpId MplsLdpIdentifier, 1459 mplsLdpPeerLabelDistMethod MplsLabelDistributionMethod, 1460 mplsLdpPeerPathVectorLimit Integer32, 1461 mplsLdpPeerTransportAddrType InetAddressType, 1462 mplsLdpPeerTransportAddr InetAddress 1463 } 1465 mplsLdpPeerLdpId OBJECT-TYPE 1466 SYNTAX MplsLdpIdentifier 1467 MAX-ACCESS not-accessible 1468 STATUS current 1469 DESCRIPTION 1470 "The LDP identifier of this LDP Peer." 1471 ::= { mplsLdpPeerEntry 1 } 1473 mplsLdpPeerLabelDistMethod OBJECT-TYPE 1474 SYNTAX MplsLabelDistributionMethod 1475 MAX-ACCESS read-only 1476 STATUS current 1477 DESCRIPTION 1478 "For any given LDP session, the method of 1479 label distribution must be specified." 1480 ::= { mplsLdpPeerEntry 2 } 1482 mplsLdpPeerPathVectorLimit OBJECT-TYPE 1483 SYNTAX Integer32 (0..255) 1484 MAX-ACCESS read-only 1485 STATUS current 1486 DESCRIPTION 1487 "If the value of this object is 0 (zero) then 1488 Loop Dection for Path Vectors for this Peer 1489 is disabled. 1491 Otherwise, if this object has a value greater than 1492 zero, then Loop Dection for Path Vectors for this 1493 Peer is enabled and the Path Vector Limit is this value." 1494 REFERENCE 1495 "RFC3036, LDP Specification, Section 2.8 Loop Dection, 1496 Section 3.4.5 Path Vector TLV." 1497 ::= { mplsLdpPeerEntry 3 } 1499 mplsLdpPeerTransportAddrType OBJECT-TYPE 1500 SYNTAX InetAddressType 1501 MAX-ACCESS read-only 1502 STATUS current 1503 DESCRIPTION 1504 "The type of the Internet address for the 1505 mplsLdpPeerTransportAddr object. The LDP 1506 specification describes this as being either 1507 an IPv4 Transport Address or IPv6 Transport 1508 Address which is used in opening the LDP session's 1509 TCP connection, or if the optional TLV is not 1510 present, then this is the IPv4/IPv6 source 1511 address for the UPD packet carrying the Hellos. 1513 This object specifies how the value of the 1514 mplsLdpPeerTransportAddr object should be 1515 interpreted." 1516 REFERENCE 1517 "RFC3036, LDP Specification, Section 2.5.2 1518 Transport Connection Establishment and 1519 Section 3.5.2.1 Hello Message Procedures." 1520 ::= { mplsLdpPeerEntry 4 } 1522 mplsLdpPeerTransportAddr OBJECT-TYPE 1523 SYNTAX InetAddress 1524 MAX-ACCESS read-only 1525 STATUS current 1526 DESCRIPTION 1527 "The Internet address advertised by the peer 1528 in the Hello Message or the Hello source address. 1530 The type of this address is specified by the 1531 value of the mplsLdpPeerTransportAddrType 1532 object." 1533 REFERENCE 1534 "RFC3036, LDP Specification, Section 2.5.2 1535 Transport Connection Establishment and 1536 Section 3.5.2.1 Hello Message Procedures." 1537 ::= { mplsLdpPeerEntry 5 } 1539 -- 1540 -- The MPLS LDP Sessions Table 1541 -- 1543 mplsLdpSessionTable OBJECT-TYPE 1544 SYNTAX SEQUENCE OF MplsLdpSessionEntry 1545 MAX-ACCESS not-accessible 1546 STATUS current 1547 DESCRIPTION 1548 "A table of Sessions between the LDP Entities 1549 and LDP Peers. This table AUGMENTS the 1550 mplsLdpPeerTable. Each row in this table 1551 represents a single session." 1552 ::= { mplsLdpSessionObjects 3 } 1554 mplsLdpSessionEntry OBJECT-TYPE 1555 SYNTAX MplsLdpSessionEntry 1556 MAX-ACCESS not-accessible 1557 STATUS current 1558 DESCRIPTION 1559 "An entry in this table represents information on a 1560 single session between an LDP Entity and LDP Peer. 1561 The information contained in a row is read-only. 1563 Please note: the Path Vector Limit for the 1564 Session is the value which is configured in 1565 the corresponding mplsLdpEntityEntry. The 1566 Peer's Path Vector Limit is in the 1567 mplsLdpPeerPathVectorLimit object in the 1568 mplsLdpPeerTable. 1570 Values which may differ from those configured are 1571 noted in the objects of this table, the 1572 mplsLdpAtmSessionTable and the 1573 mplsLdpFrameRelaySessionTable. A value will 1574 differ if it was negotiated between the 1575 Entity and the Peer. Values may or may not 1576 be negotiated. For example, if the values 1577 are the same then no negotiation takes place. 1578 If they are negotiated, then they may differ." 1579 AUGMENTS { mplsLdpPeerEntry } 1580 ::= { mplsLdpSessionTable 1 } 1582 MplsLdpSessionEntry ::= SEQUENCE { 1583 mplsLdpSessionStateLastChange TimeStamp, 1584 mplsLdpSessionState INTEGER, 1585 mplsLdpSessionRole INTEGER, 1586 mplsLdpSessionProtocolVersion Unsigned32, 1587 mplsLdpSessionKeepAliveHoldTimeRem TimeInterval, 1588 mplsLdpSessionKeepAliveTime Unsigned32, 1589 mplsLdpSessionMaxPduLength Unsigned32, 1590 mplsLdpSessionDiscontinuityTime TimeStamp 1591 } 1593 mplsLdpSessionStateLastChange OBJECT-TYPE 1594 SYNTAX TimeStamp 1595 MAX-ACCESS read-only 1596 STATUS current 1597 DESCRIPTION 1598 "The value of sysUpTime at the time this 1599 Session entered its current state as 1600 denoted by the mplsLdpSessionState 1601 object." 1602 ::= { mplsLdpSessionEntry 1 } 1604 mplsLdpSessionState OBJECT-TYPE 1605 SYNTAX INTEGER { 1606 nonexistent(1), 1607 initialized(2), 1608 openrec(3), 1609 opensent(4), 1610 operational(5) 1611 } 1612 MAX-ACCESS read-only 1613 STATUS current 1614 DESCRIPTION 1615 "The current state of the session, all of the 1616 states 1 to 5 are based on the state machine 1617 for session negotiation behavior." 1618 REFERENCE 1619 "RFC3036, LDP Specification, Section 2.5.4, 1620 Initialization State Machine." 1621 ::= { mplsLdpSessionEntry 2 } 1623 mplsLdpSessionRole OBJECT-TYPE 1624 SYNTAX INTEGER { 1625 unknown(1), 1626 active(2), 1627 passive(3) 1628 } 1629 MAX-ACCESS read-only 1630 STATUS current 1631 DESCRIPTION 1632 "During session establishment the LSR/LER takes either 1633 the active role or the passive role based on address 1634 comparisons. This object indicates whether this LSR/LER 1635 was behaving in an active role or passive role during 1636 this session's establishment. 1638 The value of unknown(1), indicates that the role is not 1639 able to be determined at the present time." 1640 REFERENCE 1641 "RFC3036, LDP Specification, Section 2.5.3., 1642 Session Initialization" 1643 ::= { mplsLdpSessionEntry 3 } 1645 mplsLdpSessionProtocolVersion OBJECT-TYPE 1646 SYNTAX Unsigned32(1..65535) 1647 MAX-ACCESS read-only 1648 STATUS current 1649 DESCRIPTION 1650 "The version of the LDP Protocol which 1651 this session is using. This is the version of 1652 the LDP protocol which has been negotiated 1653 during session initialization." 1654 REFERENCE 1655 "RFC3036, LDP Specification, Section 3.5.3, 1656 Initialization Message." 1657 ::= { mplsLdpSessionEntry 4 } 1659 mplsLdpSessionKeepAliveHoldTimeRem OBJECT-TYPE 1660 SYNTAX TimeInterval 1661 MAX-ACCESS read-only 1662 STATUS current 1663 DESCRIPTION 1664 "The keep alive hold time remaining for 1665 this session." 1666 ::= { mplsLdpSessionEntry 5 } 1668 mplsLdpSessionKeepAliveTime OBJECT-TYPE 1669 SYNTAX Unsigned32 (1..65535) 1670 UNITS "seconds" 1671 MAX-ACCESS read-only 1672 STATUS current 1673 DESCRIPTION 1674 "The negotiated KeepAlive Time which 1675 represents the amount of seconds between 1676 keep alive messages. The 1677 mplsLdpEntityKeepAliveHoldTimer 1678 related to this Session is the 1679 value that was proposed as the 1680 KeepAlive Time for this session. 1682 This value is negotiated during 1683 session initialization between 1684 the entity's proposed value 1685 (i.e. the value configured in 1686 mplsLdpEntityKeepAliveHoldTimer) 1687 and the peer's proposed 1688 KeepAlive Hold Timer value. 1689 This value is the smaller 1690 of the two proposed values." 1691 REFERENCE 1692 "RFC3036, LDP Specification, Section 3.5.3, 1693 Initialization Message." 1694 ::= { mplsLdpSessionEntry 6 } 1696 mplsLdpSessionMaxPduLength OBJECT-TYPE 1697 SYNTAX Unsigned32 (1..65535) 1698 UNITS "octets" 1699 MAX-ACCESS read-only 1700 STATUS current 1701 DESCRIPTION 1702 "The value of maximum allowable length for LDP PDUs for 1703 this session. This value may have been negotiated during 1704 the Session Initialization. This object is related to 1705 the mplsLdpEntityMaxPduLength object. The 1706 mplsLdpEntityMaxPduLength object specifies the requested 1707 LDP PDU length, and this object reflects the negotiated 1708 LDP PDU length between the Entity and 1709 the Peer." 1710 REFERENCE 1711 "RFC3036, LDP Specification, Section 3.5.3, 1712 Initialization Message." 1713 ::= { mplsLdpSessionEntry 7 } 1715 mplsLdpSessionDiscontinuityTime OBJECT-TYPE 1716 SYNTAX TimeStamp 1717 MAX-ACCESS read-only 1718 STATUS current 1719 DESCRIPTION 1720 "The value of sysUpTime on the most recent occasion 1721 at which any one or more of this session's counters 1722 suffered a discontinuity. The relevant counters are 1723 the specific instances associated with this session 1724 of any Counter32 object contained in the 1725 mplsLdpSessionStatsTable. 1727 The initial value of this object is the value of 1728 sysUpTime when the entry was created in this table. 1730 Also, a command generator can distinguish when a session 1731 between a given Entity and Peer goes away and a new 1732 session is established. This value would change and 1733 thus indicate to the command generator that this is a 1734 different session." 1735 ::= { mplsLdpSessionEntry 8 } 1737 -- 1738 -- The MPLS LDP Session Statistics Table 1739 -- 1741 mplsLdpSessionStatsTable OBJECT-TYPE 1742 SYNTAX SEQUENCE OF MplsLdpSessionStatsEntry 1743 MAX-ACCESS not-accessible 1744 STATUS current 1745 DESCRIPTION 1746 "A table of statistics for Sessions between 1747 LDP Entities and LDP Peers. This table AUGMENTS 1748 the mplsLdpPeerTable." 1749 ::= { mplsLdpSessionObjects 4 } 1751 mplsLdpSessionStatsEntry OBJECT-TYPE 1752 SYNTAX MplsLdpSessionStatsEntry 1753 MAX-ACCESS not-accessible 1754 STATUS current 1755 DESCRIPTION 1756 "An entry in this table represents statistical 1757 information on a single session between an LDP 1758 Entity and LDP Peer." 1760 AUGMENTS { mplsLdpPeerEntry } 1761 ::= { mplsLdpSessionStatsTable 1 } 1763 MplsLdpSessionStatsEntry ::= SEQUENCE { 1764 mplsLdpSessionStatsUnknownMesTypeErrors Counter32, 1765 mplsLdpSessionStatsUnknownTlvErrors Counter32 1766 } 1768 mplsLdpSessionStatsUnknownMesTypeErrors OBJECT-TYPE 1769 SYNTAX Counter32 1770 MAX-ACCESS read-only 1771 STATUS current 1772 DESCRIPTION 1773 "This object counts the number of Unknown Message Type 1774 Errors detected by this LSR/LER during this session. 1776 Discontinuities in the value of this counter can occur 1777 at re-initialization of the management system, and at 1778 other times as indicated by the value of 1779 mplsLdpSessionDiscontinuityTime." 1780 ::= { mplsLdpSessionStatsEntry 1 } 1782 mplsLdpSessionStatsUnknownTlvErrors OBJECT-TYPE 1783 SYNTAX Counter32 1784 MAX-ACCESS read-only 1785 STATUS current 1786 DESCRIPTION 1787 "This object counts the number of Unknown TLV Errors 1788 detected by this LSR/LER during this session. 1790 Discontinuities in the value of this counter can occur 1791 at re-initialization of the management system, and at 1792 other times as indicated by the value of 1793 mplsLdpSessionDiscontinuityTime." 1794 ::= { mplsLdpSessionStatsEntry 2 } 1796 -- 1797 -- The MPLS LDP Hello Adjacency Table 1798 -- 1800 mplsLdpHelloAdjacencyObjects OBJECT IDENTIFIER ::= 1801 { mplsLdpSessionObjects 5 } 1803 mplsLdpHelloAdjacencyTable OBJECT-TYPE 1804 SYNTAX SEQUENCE OF MplsLdpHelloAdjacencyEntry 1805 MAX-ACCESS not-accessible 1806 STATUS current 1807 DESCRIPTION 1808 "A table of Hello Adjacencies for Sessions." 1809 ::= { mplsLdpHelloAdjacencyObjects 1 } 1811 mplsLdpHelloAdjacencyEntry OBJECT-TYPE 1812 SYNTAX MplsLdpHelloAdjacencyEntry 1813 MAX-ACCESS not-accessible 1814 STATUS current 1815 DESCRIPTION 1816 "Each row represents a single LDP Hello Adjacency. 1817 An LDP Session can have one or more Hello 1818 Adjacencies." 1819 INDEX { mplsLdpEntityLdpId, 1820 mplsLdpEntityIndex, 1821 mplsLdpPeerLdpId, 1822 mplsLdpHelloAdjacencyIndex } 1823 ::= { mplsLdpHelloAdjacencyTable 1 } 1825 MplsLdpHelloAdjacencyEntry ::= SEQUENCE { 1826 mplsLdpHelloAdjacencyIndex Unsigned32, 1827 mplsLdpHelloAdjacencyHoldTimeRem TimeInterval, 1828 mplsLdpHelloAdjacencyHoldTime Unsigned32, 1829 mplsLdpHelloAdjacencyType INTEGER 1830 } 1832 mplsLdpHelloAdjacencyIndex OBJECT-TYPE 1833 SYNTAX Unsigned32 (1..4294967295) 1834 MAX-ACCESS not-accessible 1835 STATUS current 1836 DESCRIPTION 1837 "An identifier for this specific adjacency." 1838 ::= { mplsLdpHelloAdjacencyEntry 1 } 1840 mplsLdpHelloAdjacencyHoldTimeRem OBJECT-TYPE 1841 SYNTAX TimeInterval 1842 UNITS "seconds" 1843 MAX-ACCESS read-only 1844 STATUS current 1845 DESCRIPTION 1846 "If the value of this object is 65535, 1847 this means that the hold time is infinite 1848 (i.e. wait forever). 1850 Otherwise, the time remaining for 1851 this Hello Adjacency to receive its 1852 next Hello Message. 1854 This interval will change when the 'next' 1855 Hello Message which corresponds to this 1856 Hello Adjacency is received unless it 1857 is infinite." 1858 ::= { mplsLdpHelloAdjacencyEntry 2 } 1860 mplsLdpHelloAdjacencyHoldTime OBJECT-TYPE 1861 SYNTAX Unsigned32 (0..65535) 1862 MAX-ACCESS read-only 1863 STATUS current 1864 DESCRIPTION 1865 "The Hello hold time which is negotiated between 1866 the Entity and the Peer. The entity associated 1867 with this Hello Adjacency issues a proposed 1868 Hello Hold Time value in the 1869 mplsLdpEntityHelloHoldTimer object. The peer 1870 also proposes a value and this object represents 1871 the negotiated value. 1873 A value of 0 means the default, 1874 which is 15 seconds for Link Hellos 1875 and 45 seconds for Targeted Hellos. 1876 A value of 65535 indicates an 1877 infinite hold time." 1878 REFERENCE 1879 "RFC3036, LDP Specification, Section 3.5.2 Hello Message" 1880 ::= { mplsLdpHelloAdjacencyEntry 3 } 1882 mplsLdpHelloAdjacencyType OBJECT-TYPE 1883 SYNTAX INTEGER { 1884 link(1), 1885 targeted(2) 1886 } 1887 MAX-ACCESS read-only 1888 STATUS current 1889 DESCRIPTION 1890 "This adjacency is the result of a 'link' 1891 hello if the value of this object is link(1). 1892 Otherwise, it is a result of a 'targeted' 1893 hello, targeted(2)." 1894 ::= { mplsLdpHelloAdjacencyEntry 4 } 1896 -- 1897 -- Session Label (LSP) Mapping to LSR MIB's 1898 -- In Segment LIB Information. 1899 -- 1901 -- 1902 -- NOTE: the next 2 tables map to the 1903 -- MPLS-LSR-STD-MIB's MplsInSegmentTable 1904 -- and MplsOutSegmentTable. The 1905 -- cross-connect (XC) information is not 1906 -- represented here as it can be gleaned 1907 -- from the MPLS-LSR-STD-MIB. 1908 -- 1910 mplsInSegmentLdpLspTable OBJECT-TYPE 1911 SYNTAX SEQUENCE OF MplsInSegmentLdpLspEntry 1912 MAX-ACCESS not-accessible 1913 STATUS current 1914 DESCRIPTION 1915 "A table of LDP LSP's which 1916 map to the mplsInSegmentTable in the 1917 the MPLS-LSR-STD-MIB module." 1918 ::= { mplsLdpSessionObjects 6 } 1920 mplsInSegmentLdpLspEntry OBJECT-TYPE 1921 SYNTAX MplsInSegmentLdpLspEntry 1922 MAX-ACCESS not-accessible 1923 STATUS current 1924 DESCRIPTION 1925 "An entry in this table represents information 1926 on a single LDP LSP which is represented by 1927 a session's index triple (mplsLdpEntityLdpId, 1928 mplsLdpEntityIndex, mplsLdpPeerLdpId) AND the 1929 index for the mplsInSegmentTable 1930 (mplsInSegmentLdpLspLabelIndex) from the 1931 MPLS-LSR-STD-MIB. 1933 The information contained in a row is read-only." 1934 INDEX { mplsLdpEntityLdpId, 1935 mplsLdpEntityIndex, 1936 mplsLdpPeerLdpId, 1937 mplsInSegmentLdpLspIndex 1938 } 1939 ::= { mplsInSegmentLdpLspTable 1 } 1941 MplsInSegmentLdpLspEntry ::= SEQUENCE { 1942 mplsInSegmentLdpLspIndex MplsIndexType, 1943 mplsInSegmentLdpLspLabelType MplsLdpLabelType, 1944 mplsInSegmentLdpLspType MplsLspType 1945 } 1947 mplsInSegmentLdpLspIndex OBJECT-TYPE 1948 SYNTAX MplsIndexType 1949 MAX-ACCESS not-accessible 1950 STATUS current 1951 DESCRIPTION 1952 "This contains the same value as the 1953 mplsInSegmentIndex in the 1954 MPLS-LSR-STD-MIB's mplsInSegmentTable." 1955 ::= { mplsInSegmentLdpLspEntry 1 } 1957 mplsInSegmentLdpLspLabelType OBJECT-TYPE 1958 SYNTAX MplsLdpLabelType 1959 MAX-ACCESS read-only 1960 STATUS current 1961 DESCRIPTION 1962 "The Layer 2 Label Type." 1963 ::= { mplsInSegmentLdpLspEntry 2 } 1965 mplsInSegmentLdpLspType OBJECT-TYPE 1966 SYNTAX MplsLspType 1967 MAX-ACCESS read-only 1968 STATUS current 1969 DESCRIPTION 1970 "The type of LSP connection." 1971 ::= { mplsInSegmentLdpLspEntry 3 } 1973 -- 1974 -- Session Label (LSP) Mapping to LSR MIB's 1975 -- Out Segment LIB Information. 1976 -- 1978 mplsOutSegmentLdpLspTable OBJECT-TYPE 1979 SYNTAX SEQUENCE OF MplsOutSegmentLdpLspEntry 1980 MAX-ACCESS not-accessible 1981 STATUS current 1982 DESCRIPTION 1983 "A table of LDP LSP's which 1984 map to the mplsOutSegmentTable in the 1985 the MPLS-LSR-STD-MIB." 1987 ::= { mplsLdpSessionObjects 7 } 1989 mplsOutSegmentLdpLspEntry OBJECT-TYPE 1990 SYNTAX MplsOutSegmentLdpLspEntry 1991 MAX-ACCESS not-accessible 1992 STATUS current 1993 DESCRIPTION 1994 "An entry in this table represents information 1995 on a single LDP LSP which is represented by 1996 a session's index triple (mplsLdpEntityLdpId, 1997 mplsLdpEntityIndex, mplsLdpPeerLdpId) AND the 1998 index (mplsOutSegmentLdpLspIndex) 1999 for the mplsOutSegmentTable. 2001 The information contained in a row is read-only." 2002 INDEX { mplsLdpEntityLdpId, 2003 mplsLdpEntityIndex, 2004 mplsLdpPeerLdpId, 2005 mplsOutSegmentLdpLspIndex 2006 } 2007 ::= { mplsOutSegmentLdpLspTable 1 } 2009 MplsOutSegmentLdpLspEntry ::= SEQUENCE { 2010 mplsOutSegmentLdpLspIndex MplsIndexType, 2011 mplsOutSegmentLdpLspLabelType MplsLdpLabelType, 2012 mplsOutSegmentLdpLspType MplsLspType 2013 } 2015 mplsOutSegmentLdpLspIndex OBJECT-TYPE 2016 SYNTAX MplsIndexType 2017 MAX-ACCESS not-accessible 2018 STATUS current 2019 DESCRIPTION 2020 "This contains the same value as the 2021 mplsOutSegmentIndex in the 2022 MPLS-LSR-STD-MIB's mplsOutSegmentTable." 2023 ::= { mplsOutSegmentLdpLspEntry 1 } 2025 mplsOutSegmentLdpLspLabelType OBJECT-TYPE 2026 SYNTAX MplsLdpLabelType 2027 MAX-ACCESS read-only 2028 STATUS current 2029 DESCRIPTION 2030 "The Layer 2 Label Type." 2031 ::= { mplsOutSegmentLdpLspEntry 2 } 2033 mplsOutSegmentLdpLspType OBJECT-TYPE 2034 SYNTAX MplsLspType 2035 MAX-ACCESS read-only 2036 STATUS current 2037 DESCRIPTION 2038 "The type of LSP connection." 2039 ::= { mplsOutSegmentLdpLspEntry 3 } 2041 -- 2042 -- Mpls FEC Table 2043 -- 2045 mplsFecObjects OBJECT IDENTIFIER ::= 2046 { mplsLdpSessionObjects 8 } 2048 mplsFecLastChange OBJECT-TYPE 2049 SYNTAX TimeStamp 2050 MAX-ACCESS read-only 2051 STATUS current 2052 DESCRIPTION 2053 "The value of sysUpTime at the time of the most 2054 recent addition/deletion of an entry 2055 to/from the mplsLdpFectTable or 2056 the most recent change in values to any objects 2057 in the mplsLdpFecTable. 2059 If no such changes have occurred since the last 2060 re-initialization of the local management subsystem, 2061 then this object contains a zero value." 2062 ::= { mplsFecObjects 1 } 2064 mplsFecIndexNext OBJECT-TYPE 2065 SYNTAX IndexIntegerNextFree 2066 MAX-ACCESS read-only 2067 STATUS current 2068 DESCRIPTION 2069 "This object contains an appropriate value to 2070 be used for mplsFecIndex when creating 2071 entries in the mplsFecTable. The value 2072 0 indicates that no unassigned entries are 2073 available." 2074 ::= { mplsFecObjects 2 } 2076 mplsFecTable OBJECT-TYPE 2077 SYNTAX SEQUENCE OF MplsFecEntry 2078 MAX-ACCESS not-accessible 2079 STATUS current 2080 DESCRIPTION 2081 "This table represents the FEC 2082 (Forwarding Equivalence Class) 2083 Information associated with an LSP." 2084 ::= { mplsFecObjects 3 } 2086 mplsFecEntry OBJECT-TYPE 2087 SYNTAX MplsFecEntry 2088 MAX-ACCESS not-accessible 2089 STATUS current 2090 DESCRIPTION 2091 "Each row represents a single FEC Element." 2092 INDEX { mplsFecIndex } 2093 ::= { mplsFecTable 1 } 2095 MplsFecEntry ::= SEQUENCE { 2096 mplsFecIndex IndexInteger, 2097 mplsFecType INTEGER, 2098 mplsFecAddrType InetAddressType, 2099 mplsFecAddr InetAddress, 2100 mplsFecAddrPrefixLength InetAddressPrefixLength, 2101 mplsFecStorageType StorageType, 2102 mplsFecRowStatus RowStatus 2103 } 2105 mplsFecIndex OBJECT-TYPE 2106 SYNTAX IndexInteger 2107 MAX-ACCESS not-accessible 2108 STATUS current 2109 DESCRIPTION 2110 "The index which uniquely identifies this entry." 2111 ::= { mplsFecEntry 1 } 2113 mplsFecType OBJECT-TYPE 2114 SYNTAX INTEGER { 2115 prefix(1), 2116 hostAddress(2) 2117 } 2118 MAX-ACCESS read-create 2119 STATUS current 2120 DESCRIPTION 2121 "The type of the FEC. If the value of this object 2122 is 'prefix(1)' then the FEC type described by this 2123 row is an address prefix. 2125 If the value of this object is 'hostAddress(2)' then 2126 the FEC type described by this row is a host address." 2127 REFERENCE 2128 "RFC3036, Section 3.4.1. FEC TLV." 2129 ::= { mplsFecEntry 2 } 2131 mplsFecAddrType OBJECT-TYPE 2132 SYNTAX InetAddressType 2133 MAX-ACCESS read-create 2134 STATUS current 2135 DESCRIPTION 2136 "The value of this object is the type of the 2137 Internet address. The value of this object, 2138 decides how the value of the mplsFecAddr object 2139 is interpreted." 2140 REFERENCE 2141 "RFC3036, Section 3.4.1. FEC TLV." 2142 ::= { mplsFecEntry 4 } 2144 mplsFecAddr OBJECT-TYPE 2145 SYNTAX InetAddress 2146 MAX-ACCESS read-create 2147 STATUS current 2148 DESCRIPTION 2149 "The value of this object is interpreted based 2150 on the value of the 'mplsFecAddrType' object. 2152 This address is then further interpretted as 2153 an being used with the address prefix, 2154 or as the host address. This further interpretation 2155 is indicated by the 'mplsFecType' object. 2156 In other words, the FEC element is populated 2157 according to the Prefix FEC Element value encoding, or 2158 the Host Address FEC Element encoding." 2159 REFERENCE 2160 "RFC3036, Section 3.4.1 FEC TLV." 2161 ::= { mplsFecEntry 5 } 2163 mplsFecAddrPrefixLength OBJECT-TYPE 2164 SYNTAX InetAddressPrefixLength 2165 MAX-ACCESS read-create 2166 STATUS current 2167 DESCRIPTION 2168 "If the value of the 'mplsFecType' is 'hostAddress(2)' 2169 then this object is undefined. 2171 If the value of 'mplsFecType' is 'prefix(1)' 2172 then the value of this object is the length in 2173 bits of the address prefix represented by 2174 'mplsFecAddr', or zero. If the value of this 2175 object is zero, this indicates that the 2176 prefix matches all addresses. In this case the 2177 address prefix MUST also be zero (i.e. 'mplsFecAddr' 2178 should have the value of zero.)" 2179 REFERENCE 2180 "RFC3036, Section 3.4.1. FEC TLV." 2181 DEFVAL { 0 } 2182 ::= { mplsFecEntry 3 } 2184 mplsFecStorageType OBJECT-TYPE 2185 SYNTAX StorageType 2186 MAX-ACCESS read-create 2187 STATUS current 2188 DESCRIPTION 2189 "The storage type for this conceptual row. 2190 Conceptual rows having the value 'permanent(4)' 2191 need not allow write-access to any columnar 2192 objects in the row." 2193 DEFVAL { nonVolatile } 2194 ::= { mplsFecEntry 6 } 2196 mplsFecRowStatus OBJECT-TYPE 2197 SYNTAX RowStatus 2198 MAX-ACCESS read-create 2199 STATUS current 2200 DESCRIPTION 2201 "The status of this conceptual row. If the value of this 2202 object is 'active(1)', then none of the writable objects of 2203 this entry can be modified, except to set this object 2204 to 'destroy(6)'. 2206 NOTE: if this row is being referenced by any entry in the 2207 mplsLdpLspFecTable, then a request to destroy this row, will 2208 result in an inconsistentValue error." 2209 ::= { mplsFecEntry 7 } 2211 -- 2212 -- LDP LSP FEC Table 2213 -- 2215 mplsLdpLspFecLastChange OBJECT-TYPE 2216 SYNTAX TimeStamp 2217 MAX-ACCESS read-only 2218 STATUS current 2219 DESCRIPTION 2220 "The value of sysUpTime at the time of the most 2221 recent addition/deletion of an entry 2222 to/from the mplsLdpLspFecTable or 2223 the most recent change in values to any objects in the 2224 mplsLdpLspFecTable. 2226 If no such changes have occurred since the last 2227 re-initialization of the local management subsystem, 2228 then this object contains a zero value." 2229 ::= { mplsLdpSessionObjects 9 } 2231 mplsLdpLspFecTable OBJECT-TYPE 2232 SYNTAX SEQUENCE OF MplsLdpLspFecEntry 2233 MAX-ACCESS not-accessible 2234 STATUS current 2235 DESCRIPTION 2236 "A table which shows the relationship between 2237 LDP LSPs and FECs. Each row represents 2238 a single LDP LSP to FEC association." 2239 ::= { mplsLdpSessionObjects 10 } 2241 mplsLdpLspFecEntry OBJECT-TYPE 2242 SYNTAX MplsLdpLspFecEntry 2243 MAX-ACCESS not-accessible 2244 STATUS current 2245 DESCRIPTION 2246 "An entry represents a LDP LSP 2247 to FEC association." 2248 INDEX { mplsLdpEntityLdpId, 2249 mplsLdpEntityIndex, 2250 mplsLdpPeerLdpId, 2251 mplsLdpLspFecSegment, 2252 mplsLdpLspFecSegmentIndex, 2253 mplsLdpLspFecIndex 2254 } 2255 ::= { mplsLdpLspFecTable 1 } 2257 MplsLdpLspFecEntry ::= SEQUENCE { 2258 mplsLdpLspFecSegment INTEGER, 2259 mplsLdpLspFecSegmentIndex MplsIndexType, 2260 mplsLdpLspFecIndex IndexInteger, 2261 mplsLdpLspFecStorageType StorageType, 2262 mplsLdpLspFecRowStatus RowStatus 2263 } 2265 mplsLdpLspFecSegment OBJECT-TYPE 2266 SYNTAX INTEGER { 2267 inSegment(1), 2268 outSegment(2) 2269 } 2270 MAX-ACCESS not-accessible 2271 STATUS current 2272 DESCRIPTION 2273 "If the value is inSegment(1), then this 2274 indicates that the following index, 2275 mplsLdpLspFecSegmentIndex, contains the same 2276 value as the mplsInSegmentLdpLspIndex. 2278 Otherwise, if the value of this object is 2279 outSegment(2), then this 2280 indicates that following index, 2281 mplsLdpLspFecSegmentIndex, contains the same 2282 value as the mplsOutSegmentLdpLspIndex." 2283 ::= { mplsLdpLspFecEntry 1 } 2285 mplsLdpLspFecSegmentIndex OBJECT-TYPE 2286 SYNTAX MplsIndexType 2287 MAX-ACCESS not-accessible 2288 STATUS current 2289 DESCRIPTION 2290 "This index is interpretted by using the value 2291 of the mplsLdpLspFecSegment. 2293 If the mplsLdpLspFecSegment is inSegment(1), 2294 then this index has the same value as 2295 mplsInSegmentLdpLspIndex. 2297 If the mplsLdpLspFecSegment is outSegment(2), 2298 then this index has the same value as 2299 mplsOutSegmentLdpLspIndex." 2300 ::= { mplsLdpLspFecEntry 2 } 2302 mplsLdpLspFecIndex OBJECT-TYPE 2303 SYNTAX IndexInteger 2304 MAX-ACCESS not-accessible 2305 STATUS current 2306 DESCRIPTION 2307 "This index identifies the FEC entry in the 2308 mplsFecTable associated with this session. 2309 In other words, the value of this index 2310 is the same as the value of the mplsFecIndex 2311 that denotes the FEC associated with this 2312 Session." 2313 ::= { mplsLdpLspFecEntry 3 } 2315 mplsLdpLspFecStorageType OBJECT-TYPE 2316 SYNTAX StorageType 2317 MAX-ACCESS read-create 2318 STATUS current 2319 DESCRIPTION 2320 "The storage type for this conceptual row. 2321 Conceptual rows having the value 'permanent(4)' 2322 need not allow write-access to any columnar 2323 objects in the row." 2324 DEFVAL { nonVolatile } 2325 ::= { mplsLdpLspFecEntry 4 } 2327 mplsLdpLspFecRowStatus OBJECT-TYPE 2328 SYNTAX RowStatus 2329 MAX-ACCESS read-create 2330 STATUS current 2331 DESCRIPTION 2332 "The status of this conceptual row. If the 2333 value of this object is 'active(1)', then 2334 none of the writable objects of this entry 2335 can be modified. 2337 The Agent should delete this row when 2338 the session ceases to exist. If an 2339 operator wants to associate the session with 2340 a different FEC, the recommended 2341 procedure is (as described in detail in the section 2342 entitled, 'Changing Values After Session 2343 Establishment', and again described in the 2344 DESCRIPTION clause of the 2345 mplsLdpEntityAdminStatus object) 2346 is to set the mplsLdpEntityAdminStatus to 2347 down, thereby explicitly causing a session 2348 to be torn down. This will also 2349 cause this entry to be deleted. 2351 Then, set the mplsLdpEntityAdminStatus 2352 to enable which enables a new session to be initiated. 2353 Once the session is initiated, an entry may be added to this 2354 table to associate the new session with a FEC." 2355 ::= { mplsLdpLspFecEntry 5 } 2357 -- 2358 -- Address Message/Address Withdraw Message Information 2359 -- 2360 -- This information is associated with a specific Session 2361 -- because Label Address Messages are sent after session 2362 -- initialization has taken place. 2363 -- 2365 mplsLdpSessionPeerAddrTable OBJECT-TYPE 2366 SYNTAX SEQUENCE OF MplsLdpSessionPeerAddrEntry 2367 MAX-ACCESS not-accessible 2368 STATUS current 2369 DESCRIPTION 2370 "This table 'extends' the mplsLdpSessionTable. 2371 This table is used to store Label Address Information 2372 from Label Address Messages received by this LSR from 2373 Peers. This table is read-only and should be updated 2374 when Label Withdraw Address Messages are received, i.e. 2375 Rows should be deleted as apropriate. 2377 NOTE: since more than one address may be contained 2378 in a Label Address Message, this table 'sparse augments', 2379 the mplsLdpSessionTable's information." 2380 ::= { mplsLdpSessionObjects 11 } 2382 mplsLdpSessionPeerAddrEntry OBJECT-TYPE 2383 SYNTAX MplsLdpSessionPeerAddrEntry 2384 MAX-ACCESS not-accessible 2385 STATUS current 2386 DESCRIPTION 2387 "An entry in this table represents information on 2388 a session's single next hop address which was 2389 advertised in an Address Message from the LDP peer. 2390 The information contained in a row is read-only." 2392 INDEX { mplsLdpEntityLdpId, 2393 mplsLdpEntityIndex, 2394 mplsLdpPeerLdpId, 2395 mplsLdpSessionPeerAddrIndex 2396 } 2397 ::= { mplsLdpSessionPeerAddrTable 1 } 2399 MplsLdpSessionPeerAddrEntry ::= SEQUENCE { 2400 mplsLdpSessionPeerAddrIndex Unsigned32, 2401 mplsLdpSessionPeerNextHopAddrType InetAddressType, 2402 mplsLdpSessionPeerNextHopAddr InetAddress 2403 } 2405 mplsLdpSessionPeerAddrIndex OBJECT-TYPE 2406 SYNTAX Unsigned32 (1..4294967295) 2407 MAX-ACCESS not-accessible 2408 STATUS current 2409 DESCRIPTION 2410 "An index which uniquely identifies this entry within 2411 a given session." 2412 ::= { mplsLdpSessionPeerAddrEntry 1 } 2414 mplsLdpSessionPeerNextHopAddrType OBJECT-TYPE 2415 SYNTAX InetAddressType 2416 MAX-ACCESS read-only 2417 STATUS current 2418 DESCRIPTION 2419 "The internetwork layer address type of this Next Hop 2420 Address as specified in the Label Address Message 2421 associated with this Session. The value of this 2422 object indicates how to interpret the value of 2423 mplsLdpSessionPeerNextHopAddr." 2424 ::= { mplsLdpSessionPeerAddrEntry 2 } 2426 mplsLdpSessionPeerNextHopAddr OBJECT-TYPE 2427 SYNTAX InetAddress 2428 MAX-ACCESS read-only 2429 STATUS current 2430 DESCRIPTION 2431 "The next hop address. The type of this address 2432 is specified by the value of the 2433 mplsLdpSessionPeerNextHopAddrType." 2434 REFERENCE 2435 "RFC3036, Section 2.7. LDP Identifiers 2436 and Next Hop Addresses" 2437 ::= { mplsLdpSessionPeerAddrEntry 3 } 2439 --- 2440 --- Notifications 2441 --- 2443 mplsLdpInitSessionThresholdExceeded NOTIFICATION-TYPE 2444 OBJECTS { 2445 mplsLdpEntityInitSessionThreshold 2446 } 2447 STATUS current 2448 DESCRIPTION 2449 "This notification is generated when the value of 2450 the 'mplsLdpEntityInitSessionThreshold' object 2451 is not zero, and the number of Session 2452 Initialization messages exceeds the value 2453 of the 'mplsLdpEntityInitSessionThreshold' object." 2454 ::= { mplsLdpNotifications 1 } 2456 mplsLdpPathVectorLimitMismatch NOTIFICATION-TYPE 2457 OBJECTS { 2458 mplsLdpEntityPathVectorLimit, 2459 mplsLdpPeerPathVectorLimit 2460 } 2461 STATUS current 2462 DESCRIPTION 2463 "This notification is sent when the 2464 'mplsLdpEntityPathVectorLimit' does NOT match 2465 the value of the 'mplsLdpPeerPathVectorLimit' for 2466 a specific Entity." 2467 REFERENCE 2468 "RFC3036, LDP Specification, Section 3.5.3." 2469 ::= { mplsLdpNotifications 2 } 2471 mplsLdpSessionUp NOTIFICATION-TYPE 2472 OBJECTS { 2473 mplsLdpSessionState, 2474 mplsLdpSessionDiscontinuityTime, 2475 mplsLdpSessionStatsUnknownMesTypeErrors, 2476 mplsLdpSessionStatsUnknownTlvErrors 2477 } 2478 STATUS current 2479 DESCRIPTION 2480 "If this notification is sent when the 2481 value of 'mplsLdpSessionState' enters 2482 the 'operational(5)' state." 2483 ::= { mplsLdpNotifications 3 } 2485 mplsLdpSessionDown NOTIFICATION-TYPE 2486 OBJECTS { 2487 mplsLdpSessionState, 2488 mplsLdpSessionDiscontinuityTime, 2489 mplsLdpSessionStatsUnknownMesTypeErrors, 2490 mplsLdpSessionStatsUnknownTlvErrors 2492 } 2493 STATUS current 2494 DESCRIPTION 2495 "This notification is sent when the 2496 the value of 'mplsLdpSessionState' leaves 2497 the 'operational(5)' state." 2498 ::= { mplsLdpNotifications 4 } 2500 --**************************************************************** 2501 -- Module Conformance Statement 2502 --**************************************************************** 2504 mplsLdpGroups 2505 OBJECT IDENTIFIER ::= { mplsLdpConformance 1 } 2507 mplsLdpCompliances 2508 OBJECT IDENTIFIER ::= { mplsLdpConformance 2 } 2510 -- 2511 -- Full Compliance 2512 -- 2514 mplsLdpModuleFullCompliance MODULE-COMPLIANCE 2515 STATUS current 2516 DESCRIPTION 2517 "The Module is implemented with support 2518 for read-create and read-write. In other 2519 words, both monitoring and configuration 2520 are available when using this MODULE-COMPLIANCE." 2522 MODULE -- this module 2523 MANDATORY-GROUPS { mplsLdpGeneralGroup, 2524 mplsLdpNotificationsGroup 2525 } 2527 GROUP mplsLdpLspGroup 2528 DESCRIPTION 2529 "This group must be supported if the LSR MIB is 2530 implemented, specifically the mplsInSegmentTable, 2531 the mplsOutSegmentTable or the mplsXCTable." 2533 OBJECT mplsLdpEntityTargetPeerAddrType 2534 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2535 DESCRIPTION 2536 "An implementation is only required to support 2537 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2539 OBJECT mplsLdpEntityTargetPeerAddr 2540 SYNTAX InetAddress (SIZE(0|4|16)) 2541 DESCRIPTION 2542 "An implementation is only required to support IPv4 and 2543 globally unique IPv6 addresses." 2545 OBJECT mplsLdpEntityRowStatus 2546 SYNTAX RowStatus { active(1) } 2547 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 2548 DESCRIPTION 2549 "Support for createAndWait and notInService is not 2550 required." 2552 OBJECT mplsFecAddrType 2553 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2554 DESCRIPTION 2555 "An implementation is only required to support 2556 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2558 OBJECT mplsFecAddr 2559 SYNTAX InetAddress (SIZE(0|4|16)) 2560 DESCRIPTION 2561 "An implementation is only required to support IPv4 and 2562 globally unique IPv6 addresses." 2564 OBJECT mplsFecRowStatus 2565 SYNTAX RowStatus { active(1) } 2566 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 2567 MIN-ACCESS read-only 2568 DESCRIPTION 2569 "Support for createAndWait and notInService is not 2570 required. Also, the entries in this table may be 2571 created by the agent, so strictly speaking 2572 read-create functionality is not necessary, but 2573 may be nice to have." 2575 OBJECT mplsLdpLspFecRowStatus 2576 SYNTAX RowStatus { active(1) } 2577 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 2578 MIN-ACCESS read-only 2579 DESCRIPTION 2580 "Support for createAndWait and notInService is not 2581 required. Also, the entries in this table may be 2582 created by the agent, so strictly speaking 2583 read-create functionality is not necessary, but 2584 may be nice to have." 2586 OBJECT mplsLdpSessionPeerNextHopAddrType 2587 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2588 DESCRIPTION 2589 "An implementation is only required to support 2590 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2592 OBJECT mplsLdpSessionPeerNextHopAddr 2593 SYNTAX InetAddress (SIZE(0|4|16)) 2594 DESCRIPTION 2595 "An implementation is only required to support IPv4 2596 and globally unique IPv6 addresses." 2598 ::= { mplsLdpCompliances 1 } 2600 -- 2601 -- Read-Only Compliance 2602 -- 2604 mplsLdpModuleReadOnlyCompliance MODULE-COMPLIANCE 2605 STATUS current 2606 DESCRIPTION 2607 "The Module is implemented with support 2608 for read-only. In other words, only monitoring 2609 is available by implementing this MODULE-COMPLIANCE." 2611 MODULE -- this module 2612 MANDATORY-GROUPS { mplsLdpGeneralGroup, 2613 mplsLdpNotificationsGroup 2614 } 2616 GROUP mplsLdpLspGroup 2617 DESCRIPTION 2618 "This group must be supported if the LSR MIB is 2619 implemented, specifically the mplsInSegmentTable, 2620 the mplsOutSegmentTable or the mplsXCTable." 2622 OBJECT mplsLdpEntityProtocolVersion 2623 MIN-ACCESS read-only 2624 DESCRIPTION 2625 "Write access is not required." 2627 OBJECT mplsLdpEntityAdminStatus 2628 MIN-ACCESS read-only 2629 DESCRIPTION 2630 "Write access is not required." 2632 OBJECT mplsLdpEntityTcpDscPort 2633 MIN-ACCESS read-only 2634 DESCRIPTION 2635 "Write access is not required." 2637 OBJECT mplsLdpEntityUdpDscPort 2638 MIN-ACCESS read-only 2639 DESCRIPTION 2640 "Write access is not required." 2642 OBJECT mplsLdpEntityMaxPduLength 2643 MIN-ACCESS read-only 2644 DESCRIPTION 2645 "Write access is not required." 2647 OBJECT mplsLdpEntityKeepAliveHoldTimer 2648 MIN-ACCESS read-only 2649 DESCRIPTION 2650 "Write access is not required." 2652 OBJECT mplsLdpEntityHelloHoldTimer 2653 MIN-ACCESS read-only 2654 DESCRIPTION 2655 "Write access is not required." 2657 OBJECT mplsLdpEntityInitSessionThreshold 2658 MIN-ACCESS read-only 2659 DESCRIPTION 2660 "Write access is not required." 2662 OBJECT mplsLdpEntityLabelDistMethod 2663 MIN-ACCESS read-only 2664 DESCRIPTION 2665 "Write access is not required." 2667 OBJECT mplsLdpEntityLabelRetentionMode 2668 MIN-ACCESS read-only 2669 DESCRIPTION 2670 "Write access is not required." 2672 OBJECT mplsLdpEntityPathVectorLimit 2673 MIN-ACCESS read-only 2674 DESCRIPTION 2675 "Write access is not required." 2677 OBJECT mplsLdpEntityHopCountLimit 2678 MIN-ACCESS read-only 2679 DESCRIPTION 2680 "Write access is not required." 2682 OBJECT mplsLdpEntityTransportAddrKind 2683 MIN-ACCESS read-only 2684 DESCRIPTION 2685 "Write access is not required." 2687 OBJECT mplsLdpEntityTargetPeer 2688 MIN-ACCESS read-only 2689 DESCRIPTION 2690 "Write access is not required." 2692 OBJECT mplsLdpEntityTargetPeerAddrType 2693 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2694 MIN-ACCESS read-only 2695 DESCRIPTION 2696 "Write access is not required. 2697 An implementation is only required to support 2698 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2700 OBJECT mplsLdpEntityTargetPeerAddr 2701 SYNTAX InetAddress (SIZE(0|4|16)) 2702 MIN-ACCESS read-only 2703 DESCRIPTION 2704 "Write access is not required. 2705 An implementation is only required to support IPv4 and 2706 globally unique IPv6 addresses." 2708 OBJECT mplsLdpEntityLabelType 2709 MIN-ACCESS read-only 2710 DESCRIPTION 2711 "Write access is not required." 2713 OBJECT mplsLdpEntityStorageType 2714 MIN-ACCESS read-only 2715 DESCRIPTION 2716 "Write access is not required." 2718 OBJECT mplsLdpEntityRowStatus 2719 SYNTAX RowStatus { active(1) } 2720 MIN-ACCESS read-only 2721 DESCRIPTION 2722 "Write access is not required, and active is the 2723 only status that needs to be supported." 2725 OBJECT mplsFecType 2726 MIN-ACCESS read-only 2727 DESCRIPTION 2728 "Write access is not required." 2730 OBJECT mplsFecAddrPrefixLength 2731 MIN-ACCESS read-only 2732 DESCRIPTION 2733 "Write access is not required." 2735 OBJECT mplsFecAddrType 2736 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2737 MIN-ACCESS read-only 2738 DESCRIPTION 2739 "Write access is not required. 2740 An implementation is only required to support 2741 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2743 OBJECT mplsFecAddr 2744 SYNTAX InetAddress (SIZE(0|4|16)) 2745 MIN-ACCESS read-only 2746 DESCRIPTION 2747 "Write access is not required. 2748 An implementation is only required to support IPv4 and 2749 globally unique IPv6 addresses." 2751 OBJECT mplsFecStorageType 2752 MIN-ACCESS read-only 2753 DESCRIPTION 2754 "Write access is not required." 2756 OBJECT mplsFecRowStatus 2757 SYNTAX RowStatus { active(1) } 2758 MIN-ACCESS read-only 2759 DESCRIPTION 2760 "Write access is not required, and active is the 2761 only status that needs to be supported." 2763 OBJECT mplsLdpLspFecStorageType 2764 MIN-ACCESS read-only 2765 DESCRIPTION 2766 "Write access is not required." 2768 OBJECT mplsLdpLspFecRowStatus 2769 SYNTAX RowStatus { active(1) } 2770 MIN-ACCESS read-only 2771 DESCRIPTION 2772 "Write access is not required, and active is the 2773 only status that needs to be supported." 2775 OBJECT mplsLdpSessionPeerNextHopAddrType 2776 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2777 DESCRIPTION 2778 "An implementation is only required to support 2779 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2781 OBJECT mplsLdpSessionPeerNextHopAddr 2782 SYNTAX InetAddress (SIZE(0|4|16)) 2783 DESCRIPTION 2784 "An implementation is only required to support IPv4 2785 and globally unique IPv6 addresses." 2787 ::= { mplsLdpCompliances 2 } 2789 -- units of conformance 2791 mplsLdpGeneralGroup OBJECT-GROUP 2792 OBJECTS { 2793 mplsLdpLsrId, 2794 mplsLdpLsrLoopDetectionCapable, 2795 mplsLdpEntityLastChange, 2796 mplsLdpEntityIndexNext, 2797 mplsLdpEntityProtocolVersion, 2798 mplsLdpEntityAdminStatus, 2799 mplsLdpEntityOperStatus, 2800 mplsLdpEntityTcpDscPort, 2801 mplsLdpEntityUdpDscPort, 2802 mplsLdpEntityMaxPduLength, 2803 mplsLdpEntityKeepAliveHoldTimer, 2804 mplsLdpEntityHelloHoldTimer, 2805 mplsLdpEntityInitSessionThreshold, 2806 mplsLdpEntityLabelDistMethod, 2807 mplsLdpEntityLabelRetentionMode, 2808 mplsLdpEntityPathVectorLimit, 2809 mplsLdpEntityHopCountLimit, 2810 mplsLdpEntityTransportAddrKind, 2811 mplsLdpEntityTargetPeer, 2812 mplsLdpEntityTargetPeerAddrType, 2813 mplsLdpEntityTargetPeerAddr, 2814 mplsLdpEntityLabelType, 2815 mplsLdpEntityDiscontinuityTime, 2816 mplsLdpEntityStorageType, 2817 mplsLdpEntityRowStatus, 2818 mplsLdpEntityStatsSessionAttempts, 2819 mplsLdpEntityStatsSessionRejectedNoHelloErrors, 2820 mplsLdpEntityStatsSessionRejectedAdErrors, 2821 mplsLdpEntityStatsSessionRejectedMaxPduErrors, 2822 mplsLdpEntityStatsSessionRejectedLRErrors, 2823 mplsLdpEntityStatsBadLdpIdentifierErrors, 2824 mplsLdpEntityStatsBadPduLengthErrors, 2825 mplsLdpEntityStatsBadMessageLengthErrors, 2826 mplsLdpEntityStatsBadTlvLengthErrors, 2827 mplsLdpEntityStatsMalformedTlvValueErrors, 2828 mplsLdpEntityStatsKeepAliveTimerExpErrors, 2829 mplsLdpEntityStatsShutdownReceivedNotifications, 2830 mplsLdpEntityStatsShutdownSentNotifications, 2831 mplsLdpPeerLastChange, 2832 mplsLdpPeerLabelDistMethod, 2833 mplsLdpPeerPathVectorLimit, 2834 mplsLdpPeerTransportAddrType, 2835 mplsLdpPeerTransportAddr, 2836 mplsLdpHelloAdjacencyHoldTimeRem, 2837 mplsLdpHelloAdjacencyHoldTime, 2838 mplsLdpHelloAdjacencyType, 2839 mplsLdpSessionStateLastChange, 2840 mplsLdpSessionState, 2841 mplsLdpSessionRole, 2842 mplsLdpSessionProtocolVersion, 2843 mplsLdpSessionKeepAliveHoldTimeRem, 2844 mplsLdpSessionKeepAliveTime, 2845 mplsLdpSessionMaxPduLength, 2846 mplsLdpSessionDiscontinuityTime, 2847 mplsLdpSessionStatsUnknownMesTypeErrors, 2848 mplsLdpSessionStatsUnknownTlvErrors, 2849 mplsLdpSessionPeerNextHopAddrType, 2850 mplsLdpSessionPeerNextHopAddr, 2851 mplsFecLastChange, 2852 mplsFecIndexNext, 2853 mplsFecType, 2854 mplsFecAddrType, 2855 mplsFecAddr, 2856 mplsFecAddrPrefixLength, 2857 mplsFecStorageType, 2858 mplsFecRowStatus 2859 } 2860 STATUS current 2861 DESCRIPTION 2862 "Objects that apply to all MPLS LDP implementations." 2863 ::= { mplsLdpGroups 1 } 2865 mplsLdpLspGroup OBJECT-GROUP 2866 OBJECTS { 2867 mplsInSegmentLdpLspLabelType, 2868 mplsInSegmentLdpLspType, 2869 mplsOutSegmentLdpLspLabelType, 2870 mplsOutSegmentLdpLspType, 2871 mplsLdpLspFecLastChange, 2872 mplsLdpLspFecStorageType, 2873 mplsLdpLspFecRowStatus 2874 } 2875 STATUS current 2876 DESCRIPTION 2877 "These objects are for LDP implementations 2878 which interface to the Label Information Base (LIB) 2879 in the MPLS-LSR-STD-MIB. The LIB is 2880 represented in the mplsInSegmentTable, 2881 mplsOutSegmentTable and mplsXCTable." 2882 ::= { mplsLdpGroups 2 } 2884 mplsLdpNotificationsGroup NOTIFICATION-GROUP 2885 NOTIFICATIONS { mplsLdpInitSessionThresholdExceeded, 2886 mplsLdpPathVectorLimitMismatch, 2887 mplsLdpSessionUp, 2888 mplsLdpSessionDown 2889 } 2890 STATUS current 2891 DESCRIPTION 2892 "The notification for an MPLS LDP implemention." 2893 ::= { mplsLdpGroups 3 } 2895 END 2897 4.1. The MPLS-LDP-ATM-STD-MIB Module 2899 This MIB Module MUST be supported if LDP uses ATM as the Layer 2 2900 medium. There are three tables in this MIB Module. Two tables are 2901 for configuring LDP to use ATM. These tables are the 2902 mplsLdpEntityAtmTable and the mplsLdpEntityAtmLRTable. The third 2903 table is the mplsLdpAtmSessionTable which is a read-only table. 2905 4.1.1. The LDP Entity ATM Table 2907 The mplsLdpEntityAtmTable provides a way to configure information 2908 which would be contained in the "Optional Parameter" portion of an 2909 LDP PDU Initialization Message. 2911 4.1.2. The LDP Entity ATM Label Range Table 2913 The mplsLdpEntityAtmLRTable provides a way to configure information 2914 which would be contained in the "ATM Label Range Components" portion 2915 of an LDP PDU Intialization Message, see [RFC3035] and [RFC3036]. 2917 4.1.3. The LDP ATM Session Table 2919 The MPLS LDP ATM Session Table is a read-only table which contains 2920 session information specific to ATM. 2922 MPLS-LDP-ATM-STD-MIB DEFINITIONS ::= BEGIN 2923 IMPORTS 2924 OBJECT-TYPE, MODULE-IDENTITY, 2925 Unsigned32 2926 FROM SNMPv2-SMI 2927 MODULE-COMPLIANCE, OBJECT-GROUP 2928 FROM SNMPv2-CONF 2930 RowStatus, 2931 StorageType 2932 FROM SNMPv2-TC 2934 InterfaceIndexOrZero 2935 FROM IF-MIB 2937 AtmVpIdentifier 2938 FROM ATM-TC-MIB 2940 mplsStdMIB, 2941 MplsAtmVcIdentifier 2942 FROM MPLS-TC-STD-MIB 2944 mplsLdpEntityLdpId, 2945 mplsLdpEntityIndex, 2946 mplsLdpPeerLdpId 2947 FROM MPLS-LDP-STD-MIB 2949 ; 2951 mplsLdpAtmStdMIB MODULE-IDENTITY 2952 LAST-UPDATED "200306281200Z" -- 28 June 2003 2953 ORGANIZATION "Multiprotocol Label Switching (mpls) 2954 Working Group" 2955 CONTACT-INFO 2956 "Joan Cucchiara (jcucchiara@artel.com) 2957 Artel 2959 Hans Sjostrand (hans@ipunplugged.com) 2960 ipUnplugged 2962 James V. Luciani (james_luciani@mindspring.com) 2963 Consultant 2965 Working Group Chairs: 2966 George Swallow, email: swallow@cisco.com 2967 Loa Andersson, email: loa@pi.se 2968 MPLS Working Group, email: mpls@uu.net 2969 " 2970 DESCRIPTION 2971 "Copyright (C) The Internet Society (2003). This 2972 version of this MIB module is part of RFCXXX; see 2973 the RFC itself for full legal notices. 2975 This MIB contains managed object definitions for 2976 configuring and monitoring the Multiprotocol Label 2977 Switching (MPLS), Label Distribution Protocol (LDP), 2978 utilizing Asynchronous Transfer Mode (ATM) as the Layer 2 2979 media." 2980 REVISION "200306281200Z" -- 28 June 2003 2981 DESCRIPTION 2982 "Initial version published as part of RFC XXXX." 2984 -- Please see the IANA Considerations Section 2985 -- the suggested mplsStdMIB subId is 5, e.g. 2986 -- ::= { mplsStdMIB 5 } 2988 ::= { mplsStdMIB XXX } -- to be assigned by IANA 2990 --**************************************************************** 2992 mplsLdpAtmObjects OBJECT IDENTIFIER 2993 ::= { mplsLdpAtmStdMIB 1 } 2994 mplsLdpAtmConformance OBJECT IDENTIFIER 2995 ::= { mplsLdpAtmStdMIB 2 } 2997 --**************************************************************** 2998 -- MPLS LDP ATM Objects 2999 --**************************************************************** 3001 -- 3002 -- Ldp Entity Objects for ATM 3003 -- 3005 mplsLdpEntityAtmObjects OBJECT IDENTIFIER ::= 3006 { mplsLdpAtmObjects 1 } 3008 mplsLdpEntityAtmTable OBJECT-TYPE 3009 SYNTAX SEQUENCE OF MplsLdpEntityAtmEntry 3010 MAX-ACCESS not-accessible 3011 STATUS current 3012 DESCRIPTION 3013 "This table contains ATM specific information 3014 which could be used in the 3015 'Optional Parameters' and other ATM specific 3016 information. 3018 This table 'sparse augments' the mplsLdpEntityTable 3019 when ATM is the Layer 2 medium." 3020 ::= { mplsLdpEntityAtmObjects 1 } 3022 mplsLdpEntityAtmEntry OBJECT-TYPE 3023 SYNTAX MplsLdpEntityAtmEntry 3024 MAX-ACCESS not-accessible 3025 STATUS current 3026 DESCRIPTION 3027 "An entry in this table represents the ATM parameters 3028 and ATM information for this LDP entity." 3029 INDEX { mplsLdpEntityLdpId, 3030 mplsLdpEntityIndex 3031 } 3032 ::= { mplsLdpEntityAtmTable 1 } 3034 MplsLdpEntityAtmEntry ::= SEQUENCE { 3035 mplsLdpEntityAtmIfIndexOrZero InterfaceIndexOrZero, 3036 mplsLdpEntityAtmMergeCap INTEGER, 3037 mplsLdpEntityAtmLRComponents Unsigned32, 3038 mplsLdpEntityAtmVcDirectionality INTEGER, 3039 mplsLdpEntityAtmLsrConnectivity INTEGER, 3040 mplsLdpEntityAtmDefaultControlVpi AtmVpIdentifier, 3041 mplsLdpEntityAtmDefaultControlVci MplsAtmVcIdentifier, 3042 mplsLdpEntityAtmUnlabTrafVpi AtmVpIdentifier, 3043 mplsLdpEntityAtmUnlabTrafVci MplsAtmVcIdentifier, 3044 mplsLdpEntityAtmStorageType StorageType, 3045 mplsLdpEntityAtmRowStatus RowStatus 3046 } 3048 mplsLdpEntityAtmIfIndexOrZero OBJECT-TYPE 3049 SYNTAX InterfaceIndexOrZero 3050 MAX-ACCESS read-create 3051 STATUS current 3052 DESCRIPTION 3053 "This value represents either the InterfaceIndex 3054 or 0 (zero). The value of zero means that the 3055 InterfaceIndex is not known. 3057 However, if the InterfaceIndex is known, then it must 3058 be represented by this value. 3060 If an InterfaceIndex becomes known, then the 3061 network management entity (e.g. SNMP agent) responsible 3062 for this object MUST change the value from 0 (zero) to the 3063 value of the InterfaceIndex. If an ATM Label is 3064 being used in forwarding data, then the value of this 3065 object MUST be the InterfaceIndex." 3066 ::= { mplsLdpEntityAtmEntry 1 } 3068 mplsLdpEntityAtmMergeCap OBJECT-TYPE 3069 SYNTAX INTEGER { 3070 notSupported(0), 3071 vpMerge(1), 3072 vcMerge(2), 3073 vpAndVcMerge(3) 3074 } 3075 MAX-ACCESS read-create 3076 STATUS current 3077 DESCRIPTION 3078 "Denotes the Merge Capability of this Entity. 3079 This is the EXACT value for the ATM Session Parameter, 3080 field M (for ATM Merge Capabilities). The ATM Session Parameter 3081 is an optional parameter in the Initialization Message. 3083 The description from rfc3036.txt is: 3085 'M, ATM Merge Capabilities 3086 Specifies the merge capabilities of an ATM switch. The 3087 following values are supported in this version of the 3088 specification: 3090 Value Meaning 3092 0 Merge not supported 3093 1 VP Merge supported 3094 2 VC Merge supported 3095 3 VP & VC Merge supported 3097 If the merge capabilities of the LSRs differ, then: 3098 - Non-merge and VC-merge LSRs may freely interoperate. 3100 - The interoperability of VP-merge-capable switches with non- 3101 VP-merge-capable switches is a subject for future study. 3103 When the LSRs differ on the use of VP-merge, the session is 3104 established, but VP merge is not used.' 3106 Please refer to the following reference for a complete 3107 description of this feature." 3108 REFERENCE 3109 "RFC3036, LDP Specification, Section 3.5.3 Initialization Message." 3110 ::= { mplsLdpEntityAtmEntry 2 } 3112 mplsLdpEntityAtmLRComponents OBJECT-TYPE 3113 SYNTAX Unsigned32 (1..65535) 3114 MAX-ACCESS read-only 3115 STATUS current 3116 DESCRIPTION 3117 "Number of Label Range Components in the Initialization 3118 message. This also represents the number of entries 3119 in the mplsLdpEntityAtmLRTable which correspond 3120 to this entry. 3122 This is the EXACT value for the ATM Session Parameter, 3123 field N (for Number of label range components). The ATM 3124 Session Parameter is an optional parameter in the Initialization 3125 Message. 3127 The description from rfc3036.txt is: 3129 'N, Number of label range components 3130 Specifies the number of ATM Label Range Components 3131 included in the TLV.' 3133 Please refer to the following reference for a complete 3134 description of this feature." 3135 REFERENCE 3136 "RFC3036, LDP Specification, Section 3.5.3 Initialization Message." 3137 ::= { mplsLdpEntityAtmEntry 3 } 3139 mplsLdpEntityAtmVcDirectionality OBJECT-TYPE 3140 SYNTAX INTEGER { 3141 bidirectional(0), 3142 unidirectional(1) 3143 } 3144 MAX-ACCESS read-create 3145 STATUS current 3146 DESCRIPTION 3147 "If the value of this object is 'bidirectional(0)', 3148 a given VCI, within a given VPI, is used as a 3149 label for both directions independently. 3151 If the value of this object is 'unidirectional(1)', 3152 a given VCI within a VPI designates one direction. 3154 This is the EXACT value for the ATM Session Parameter, 3155 field D (for VC Directionality). The ATM Session Parameter 3156 is an optional parameter in the Initialization Message. 3158 The description from rfc3036.txt is: 3160 'D, VC Directionality 3161 A value of 0 specifies bidirectional VC capability, meaning the 3162 LSR can (within a given VPI) support the use of a given VCI as 3163 a label for both link directions independently. A value of 1 3164 specifies unidirectional VC capability, meaning (within a given 3165 VPI) a given VCI may appear in a label mapping for one 3166 direction on the link only. When either or both of the peers 3167 specifies unidirectional VC capability, both LSRs use 3168 unidirectional VC label assignment for the link as follows. 3169 The LSRs compare their LDP Identifiers as unsigned integers. 3170 The LSR with the larger LDP Identifier may assign only odd- 3171 numbered VCIs in the VPI/VCI range as labels. The system with 3172 the smaller LDP Identifier may assign only even-numbered VCIs 3173 in the VPI/VCI range as labels.' 3175 Please refer to the following reference for a complete 3176 description of this feature." 3177 REFERENCE 3178 "RFC3036, LDP Specification, Section 3.5.3 Initialization Message." 3179 ::= { mplsLdpEntityAtmEntry 4 } 3181 mplsLdpEntityAtmLsrConnectivity OBJECT-TYPE 3182 SYNTAX INTEGER { 3183 direct(1), 3184 indirect(2) 3185 } 3186 MAX-ACCESS read-create 3187 STATUS current 3188 DESCRIPTION 3189 "The peer LSR may be connected indirectly by means of an 3190 ATM VP so that the VPI values may be different on either 3191 endpoint so the label MUST be encoded entirely within the 3192 VCI field." 3193 DEFVAL { direct } 3194 ::= { mplsLdpEntityAtmEntry 5 } 3196 mplsLdpEntityAtmDefaultControlVpi OBJECT-TYPE 3197 SYNTAX AtmVpIdentifier 3198 MAX-ACCESS read-create 3199 STATUS current 3200 DESCRIPTION 3201 "The default VPI value for the non-MPLS connection. The 3202 default value of this is 0 (zero) but other values may 3203 be configured. This object allows a different value 3204 to be configured." 3205 DEFVAL { 0 } 3206 ::= { mplsLdpEntityAtmEntry 6 } 3208 mplsLdpEntityAtmDefaultControlVci OBJECT-TYPE 3209 SYNTAX MplsAtmVcIdentifier 3210 MAX-ACCESS read-create 3211 STATUS current 3212 DESCRIPTION 3213 "The Default VCI value for a non-MPLS connection. The 3214 default value of this is 32 but other values may be 3215 configured. This object allows a different value to 3216 be configured." 3217 DEFVAL { 32 } 3218 ::= { mplsLdpEntityAtmEntry 7 } 3220 mplsLdpEntityAtmUnlabTrafVpi OBJECT-TYPE 3221 SYNTAX AtmVpIdentifier 3222 MAX-ACCESS read-create 3223 STATUS current 3224 DESCRIPTION 3225 "VPI value of the VCC supporting unlabeled traffic. This 3226 non-MPLS connection is used to carry unlabeled (IP) 3227 packets. The default value is the same as the default 3228 value of the 'mplsLdpEntityAtmDefaultControlVpi', however 3229 another value may be configured." 3230 DEFVAL { 0 } 3231 ::= { mplsLdpEntityAtmEntry 8 } 3233 mplsLdpEntityAtmUnlabTrafVci OBJECT-TYPE 3234 SYNTAX MplsAtmVcIdentifier 3235 MAX-ACCESS read-create 3236 STATUS current 3237 DESCRIPTION 3238 "VCI value of the VCC supporting unlabeled traffic. 3239 This non-MPLS connection is used to carry unlabeled (IP) 3240 packets. The default value is the same as the default 3241 value of the 'mplsLdpEntityAtmDefaultControlVci', however 3242 another value may be configured." 3243 DEFVAL { 32 } 3244 ::= { mplsLdpEntityAtmEntry 9 } 3246 mplsLdpEntityAtmStorageType OBJECT-TYPE 3247 SYNTAX StorageType 3248 MAX-ACCESS read-create 3249 STATUS current 3250 DESCRIPTION 3251 "The storage type for this conceptual row. 3252 Conceptual rows having the value 'permanent(4)' 3253 need not allow write-access to any columnar 3254 objects in the row." 3255 DEFVAL { nonVolatile } 3256 ::= { mplsLdpEntityAtmEntry 10 } 3258 mplsLdpEntityAtmRowStatus OBJECT-TYPE 3259 SYNTAX RowStatus 3260 MAX-ACCESS read-create 3261 STATUS current 3262 DESCRIPTION 3263 "The status of this conceptual row. All writable 3264 objects in this row may be modified at any time, 3265 however, as described in detail in the section 3266 entitled, 'Changing Values After Session 3267 Establishment', and again described in the 3268 DESCRIPTION clause of the mplsLdpEntityAdminStatus 3269 object, if a session has been initiated with a Peer, 3270 changing objects in this table will wreak havoc 3271 with the session and interrupt traffic. To repeat again: 3272 the recommended procedure is to set the 3273 mplsLdpEntityAdminStatus to down, thereby explicitly 3274 causing a session to be torn down. Then, 3275 change objects in this entry, then set the 3276 mplsLdpEntityAdminStatus to enable 3277 which enables a new session to be initiated." 3278 ::= { mplsLdpEntityAtmEntry 11 } 3280 -- 3281 -- The MPLS LDP Entity ATM Label Range Table 3282 -- 3284 mplsLdpEntityAtmLRTable OBJECT-TYPE 3285 SYNTAX SEQUENCE OF MplsLdpEntityAtmLREntry 3286 MAX-ACCESS not-accessible 3287 STATUS current 3288 DESCRIPTION 3289 "The MPLS LDP Entity ATM Label Range (LR) Table. 3290 The purpose of this table is to provide a mechanism 3291 for configuring a contiguous range of vpi's 3292 with a contiguous range of vci's, or a 'label range' 3293 for LDP Entities. 3295 LDP Entities which use ATM must have at least one 3296 entry in this table. 3298 There must exist at least one entry in this 3299 table for every LDP Entity that has 3300 'mplsLdpEntityOptionalParameters' object with 3301 a value of 'atmSessionParameters'." 3302 ::= { mplsLdpEntityAtmObjects 2 } 3304 mplsLdpEntityAtmLREntry OBJECT-TYPE 3305 SYNTAX MplsLdpEntityAtmLREntry 3306 MAX-ACCESS not-accessible 3307 STATUS current 3308 DESCRIPTION 3309 "A row in the LDP Entity ATM Label 3310 Range Table. One entry in this table contains 3311 information on a single range of labels 3312 represented by the configured Upper and Lower 3313 Bounds VPI/VCI pairs. These are the same 3314 data used in the Initialization Message. 3316 NOTE: The ranges for a specific LDP Entity 3317 are UNIQUE and non-overlapping. For example, 3318 for a specific LDP Entity index, there could 3319 be one entry having LowerBound vpi/vci == 0/32, and 3320 UpperBound vpi/vci == 0/100, and a second entry 3321 for this same interface with LowerBound 3322 vpi/vci == 0/101 and UpperBound vpi/vci == 0/200. 3323 However, there could not be a third entry with 3324 LowerBound vpi/vci == 0/200 and 3325 UpperBound vpi/vci == 0/300 because this label 3326 range overlaps with the second entry (i.e. both 3327 entries now have 0/200). 3329 A row will not become active unless a unique and 3330 non-overlapping range is specified. 3332 At least one label range entry for a 3333 specific LDP Entity MUST 3334 include the default VPI/VCI values denoted 3335 in the LDP Entity Table. 3337 A request to create a row with an overlapping 3338 range should result in an inconsistentValue 3339 error." 3340 INDEX { mplsLdpEntityLdpId, 3341 mplsLdpEntityIndex, 3342 mplsLdpEntityAtmLRMinVpi, 3343 mplsLdpEntityAtmLRMinVci 3344 } 3345 ::= { mplsLdpEntityAtmLRTable 1 } 3347 MplsLdpEntityAtmLREntry ::= SEQUENCE { 3348 mplsLdpEntityAtmLRMinVpi AtmVpIdentifier, 3349 mplsLdpEntityAtmLRMinVci MplsAtmVcIdentifier, 3350 mplsLdpEntityAtmLRMaxVpi AtmVpIdentifier, 3351 mplsLdpEntityAtmLRMaxVci MplsAtmVcIdentifier, 3352 mplsLdpEntityAtmLRStorageType StorageType, 3353 mplsLdpEntityAtmLRRowStatus RowStatus 3354 } 3356 mplsLdpEntityAtmLRMinVpi OBJECT-TYPE 3357 SYNTAX AtmVpIdentifier 3358 MAX-ACCESS not-accessible 3359 STATUS current 3360 DESCRIPTION 3361 "The minimum VPI number configured for this range. 3362 The value of zero is a valid value for the VPI portion 3363 of the label." 3364 ::= { mplsLdpEntityAtmLREntry 1 } 3366 mplsLdpEntityAtmLRMinVci OBJECT-TYPE 3367 SYNTAX MplsAtmVcIdentifier 3368 MAX-ACCESS not-accessible 3369 STATUS current 3370 DESCRIPTION 3371 "The minimum VCI number configured for this range." 3372 ::= { mplsLdpEntityAtmLREntry 2 } 3374 mplsLdpEntityAtmLRMaxVpi OBJECT-TYPE 3375 SYNTAX AtmVpIdentifier 3376 MAX-ACCESS read-create 3377 STATUS current 3378 DESCRIPTION 3379 "The maximum VPI number configured for this range." 3380 ::= { mplsLdpEntityAtmLREntry 3 } 3382 mplsLdpEntityAtmLRMaxVci OBJECT-TYPE 3383 SYNTAX MplsAtmVcIdentifier 3384 MAX-ACCESS read-create 3385 STATUS current 3386 DESCRIPTION 3387 "The maximum VCI number configured for this range." 3388 ::= { mplsLdpEntityAtmLREntry 4 } 3390 mplsLdpEntityAtmLRStorageType OBJECT-TYPE 3391 SYNTAX StorageType 3392 MAX-ACCESS read-create 3393 STATUS current 3394 DESCRIPTION 3395 "The storage type for this conceptual row. 3396 Conceptual rows having the value 'permanent(4)' 3397 need not allow write-access to any columnar 3398 objects in the row." 3399 DEFVAL { nonVolatile } 3400 ::= { mplsLdpEntityAtmLREntry 5 } 3402 mplsLdpEntityAtmLRRowStatus OBJECT-TYPE 3403 SYNTAX RowStatus 3404 MAX-ACCESS read-create 3405 STATUS current 3406 DESCRIPTION 3407 "The status of this conceptual row. All writable 3408 objects in this row may be modified at any time, 3409 however, as described in detail in the section 3410 entitled, 'Changing Values After Session 3411 Establishment', and again described in the 3412 DESCRIPTION clause of the 3413 mplsLdpEntityAdminStatus object, 3414 if a session has been initiated with a Peer, 3415 changing objects in this table will 3416 wreak havoc with the session and interrupt traffic. 3417 To repeat again: the recommended procedure 3418 is to set the mplsLdpEntityAdminStatus to 3419 down, thereby explicitly causing a session 3420 to be torn down. Then, change objects in this 3421 entry, then set the mplsLdpEntityAdminStatus 3422 to enable which enables a new session 3423 to be initiated." 3425 ::= { mplsLdpEntityAtmLREntry 6 } 3427 -- 3428 -- MPLS LDP ATM Session Information 3429 -- 3431 mplsLdpAtmSessionObjects OBJECT IDENTIFIER ::= 3432 { mplsLdpAtmObjects 2 } 3434 mplsLdpAtmSessionTable OBJECT-TYPE 3435 SYNTAX SEQUENCE OF MplsLdpAtmSessionEntry 3436 MAX-ACCESS not-accessible 3437 STATUS current 3438 DESCRIPTION 3439 "A table which relates sessions in the 3440 'mplsLdpSessionTable' and their label 3441 range intersections. There could be one 3442 or more label range intersections between an 3443 LDP Entity and LDP Peer using ATM as the 3444 underlying media. Each row represents 3445 a single label range intersection. 3447 This table cannot use the 'AUGMENTS' 3448 clause because there is not necessarily 3449 a one-to-one mapping between this table 3450 and the mplsLdpSessionTable." 3451 ::= { mplsLdpAtmSessionObjects 1 } 3453 mplsLdpAtmSessionEntry OBJECT-TYPE 3454 SYNTAX MplsLdpAtmSessionEntry 3455 MAX-ACCESS not-accessible 3456 STATUS current 3457 DESCRIPTION 3458 "An entry in this table represents information on a 3459 single label range intersection between an LDP Entity 3460 and LDP Peer. 3462 The information contained in a row is read-only." 3463 INDEX { mplsLdpEntityLdpId, 3464 mplsLdpEntityIndex, 3465 mplsLdpPeerLdpId, 3466 mplsLdpSessionAtmLRLowerBoundVpi, 3467 mplsLdpSessionAtmLRLowerBoundVci 3469 } 3470 ::= { mplsLdpAtmSessionTable 1 } 3472 MplsLdpAtmSessionEntry ::= SEQUENCE { 3473 mplsLdpSessionAtmLRLowerBoundVpi AtmVpIdentifier, 3474 mplsLdpSessionAtmLRLowerBoundVci MplsAtmVcIdentifier, 3475 mplsLdpSessionAtmLRUpperBoundVpi AtmVpIdentifier, 3476 mplsLdpSessionAtmLRUpperBoundVci MplsAtmVcIdentifier 3477 } 3479 mplsLdpSessionAtmLRLowerBoundVpi OBJECT-TYPE 3480 SYNTAX AtmVpIdentifier 3481 MAX-ACCESS not-accessible 3482 STATUS current 3483 DESCRIPTION 3484 "The minimum VPI number for this range." 3485 ::= { mplsLdpAtmSessionEntry 1 } 3487 mplsLdpSessionAtmLRLowerBoundVci OBJECT-TYPE 3488 SYNTAX MplsAtmVcIdentifier 3489 MAX-ACCESS not-accessible 3490 STATUS current 3491 DESCRIPTION 3492 "The minimum VCI number for this range." 3493 ::= { mplsLdpAtmSessionEntry 2 } 3495 mplsLdpSessionAtmLRUpperBoundVpi OBJECT-TYPE 3496 SYNTAX AtmVpIdentifier 3497 MAX-ACCESS read-only 3498 STATUS current 3499 DESCRIPTION 3500 "The maximum VPI number for this range." 3501 ::= { mplsLdpAtmSessionEntry 3 } 3503 mplsLdpSessionAtmLRUpperBoundVci OBJECT-TYPE 3504 SYNTAX MplsAtmVcIdentifier 3505 MAX-ACCESS read-only 3506 STATUS current 3507 DESCRIPTION 3508 "The maximum VCI number for this range." 3509 ::= { mplsLdpAtmSessionEntry 4 } 3511 --************************************************************** 3512 -- Module Conformance Statement 3513 --************************************************************** 3515 mplsLdpAtmGroups 3516 OBJECT IDENTIFIER ::= { mplsLdpAtmConformance 1 } 3518 mplsLdpAtmCompliances 3519 OBJECT IDENTIFIER ::= { mplsLdpAtmConformance 2 } 3521 -- 3522 -- Full Compliance 3523 -- 3525 mplsLdpAtmModuleFullCompliance MODULE-COMPLIANCE 3526 STATUS current 3527 DESCRIPTION 3528 "The Module is implemented with support for 3529 read-create and read-write. In other words, 3530 both monitoring and configuration 3531 are available when using this MODULE-COMPLIANCE." 3532 MODULE -- this module 3533 MANDATORY-GROUPS { 3534 mplsLdpAtmGroup 3535 } 3537 OBJECT mplsLdpEntityAtmRowStatus 3538 SYNTAX RowStatus { active(1) } 3539 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 3540 DESCRIPTION 3541 "Support for createAndWait and notInService is not required." 3543 OBJECT mplsLdpEntityAtmLRRowStatus 3544 SYNTAX RowStatus { active(1) } 3545 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 3546 DESCRIPTION 3547 "Support for createAndWait and notInService is not required." 3549 ::= { mplsLdpAtmCompliances 1 } 3551 -- 3552 -- Read-Only Compliance 3553 -- 3555 mplsLdpAtmModuleReadOnlyCompliance MODULE-COMPLIANCE 3556 STATUS current 3557 DESCRIPTION 3558 "The Module is implemented with support for 3559 read-only. In other words, only monitoring 3560 is available by implementing this MODULE-COMPLIANCE." 3562 MODULE -- this module 3563 MANDATORY-GROUPS { 3564 mplsLdpAtmGroup 3565 } 3567 OBJECT mplsLdpEntityAtmIfIndexOrZero 3568 MIN-ACCESS read-only 3569 DESCRIPTION 3570 "Write access is not required." 3572 OBJECT mplsLdpEntityAtmMergeCap 3573 MIN-ACCESS read-only 3574 DESCRIPTION 3575 "Write access is not required." 3577 OBJECT mplsLdpEntityAtmVcDirectionality 3578 MIN-ACCESS read-only 3579 DESCRIPTION 3580 "Write access is not required." 3582 OBJECT mplsLdpEntityAtmLsrConnectivity 3583 MIN-ACCESS read-only 3584 DESCRIPTION 3585 "Write access is not required." 3587 OBJECT mplsLdpEntityAtmDefaultControlVpi 3588 MIN-ACCESS read-only 3589 DESCRIPTION 3590 "Write access is not required." 3592 OBJECT mplsLdpEntityAtmDefaultControlVci 3593 MIN-ACCESS read-only 3594 DESCRIPTION 3595 "Write access is not required." 3597 OBJECT mplsLdpEntityAtmUnlabTrafVpi 3598 MIN-ACCESS read-only 3599 DESCRIPTION 3600 "Write access is not required." 3602 OBJECT mplsLdpEntityAtmUnlabTrafVci 3603 MIN-ACCESS read-only 3604 DESCRIPTION 3605 "Write access is not required." 3607 OBJECT mplsLdpEntityAtmStorageType 3608 MIN-ACCESS read-only 3609 DESCRIPTION 3610 "Write access is not required." 3612 OBJECT mplsLdpEntityAtmRowStatus 3613 SYNTAX RowStatus { active(1) } 3614 MIN-ACCESS read-only 3615 DESCRIPTION 3616 "Write access is not required, and active is the 3617 only status that needs to be supported." 3619 OBJECT mplsLdpEntityAtmLRMaxVpi 3620 MIN-ACCESS read-only 3621 DESCRIPTION 3622 "Write access is not required." 3624 OBJECT mplsLdpEntityAtmLRMaxVci 3625 MIN-ACCESS read-only 3626 DESCRIPTION 3627 "Write access is not required." 3629 OBJECT mplsLdpEntityAtmLRStorageType 3630 MIN-ACCESS read-only 3631 DESCRIPTION 3632 "Write access is not required." 3634 OBJECT mplsLdpEntityAtmLRRowStatus 3635 SYNTAX RowStatus { active(1) } 3636 MIN-ACCESS read-only 3637 DESCRIPTION 3638 "Write access is not required, and active is the 3639 only status that needs to be supported." 3641 ::= { mplsLdpAtmCompliances 2 } 3643 -- 3644 -- units of conformance 3645 -- 3647 mplsLdpAtmGroup OBJECT-GROUP 3648 OBJECTS { 3649 mplsLdpEntityAtmIfIndexOrZero, 3650 mplsLdpEntityAtmMergeCap, 3651 mplsLdpEntityAtmLRComponents, 3652 mplsLdpEntityAtmVcDirectionality, 3653 mplsLdpEntityAtmLsrConnectivity, 3654 mplsLdpEntityAtmDefaultControlVpi, 3655 mplsLdpEntityAtmDefaultControlVci, 3656 mplsLdpEntityAtmUnlabTrafVpi, 3657 mplsLdpEntityAtmUnlabTrafVci, 3658 mplsLdpEntityAtmStorageType, 3659 mplsLdpEntityAtmRowStatus, 3660 mplsLdpEntityAtmLRMaxVpi, 3661 mplsLdpEntityAtmLRMaxVci, 3662 mplsLdpEntityAtmLRStorageType, 3663 mplsLdpEntityAtmLRRowStatus, 3664 mplsLdpSessionAtmLRUpperBoundVpi, 3665 mplsLdpSessionAtmLRUpperBoundVci 3667 } 3668 STATUS current 3669 DESCRIPTION 3670 "Objects that apply to all MPLS LDP implementations 3671 using ATM as the Layer 2." 3672 ::= { mplsLdpAtmGroups 1 } 3674 END 3676 4.2. The MPLS-LDP-FRAME-RELAY-STD-MIB Module 3678 This MIB Module MUST be supported if LDP uses FRAME RELAY as the 3679 Layer 2 medium. There are three tables in this MIB Module. Two 3680 tables are to configure LDP for using Frame Relay. These tables are 3681 the mplsLdpEntityFrameRelayTable and the 3682 mplsLdpEntityFrameRelayLRTable. The third table, 3683 mplsLdpFrameRelaySessionTable, is a read-only table. 3685 4.2.1. The LDP Entity Frame Relay Table 3687 The mplsLdpEntityFrameRelayTable provides a way to configure 3688 information which would be contained in the "Optional Parameter" 3689 portion of an LDP PDU Initialization Message. 3691 4.2.2. The LDP Entity Frame Relay Label Range Table 3693 The mplsLdpEntityFrameRelayLRTable provides a way to configure 3694 information which would be contained in the "Frame Relay Label Range 3695 Components" portion of an LDP PDU Intialization Message, see 3696 [RFC3034] and [RFC3036]. 3698 4.2.3. The LDP Frame Relay Session Table 3700 The MPLS LDP Frame Relay Session Table is a read-only table which 3701 contains session information specific to Frame Relay. 3703 MPLS-LDP-FRAME-RELAY-STD-MIB DEFINITIONS ::= BEGIN 3705 IMPORTS 3706 OBJECT-TYPE, 3707 MODULE-IDENTITY, 3708 Unsigned32 3709 FROM SNMPv2-SMI 3710 MODULE-COMPLIANCE, 3711 OBJECT-GROUP 3712 FROM SNMPv2-CONF 3714 RowStatus, 3715 StorageType 3716 FROM SNMPv2-TC 3718 DLCI 3719 FROM FRAME-RELAY-DTE-MIB 3721 InterfaceIndexOrZero 3722 FROM IF-MIB 3724 mplsStdMIB 3725 FROM MPLS-TC-STD-MIB 3727 mplsLdpEntityLdpId, 3728 mplsLdpEntityIndex, 3729 mplsLdpPeerLdpId 3730 FROM MPLS-LDP-STD-MIB 3732 ; 3734 mplsLdpFrameRelayStdMIB MODULE-IDENTITY 3735 LAST-UPDATED "200306281200Z" -- 28 June 2003 3736 ORGANIZATION "Multiprotocol Label Switching (mpls) 3737 Working Group" 3738 CONTACT-INFO 3739 "Joan Cucchiara (jcucchiara@artel.com) 3740 Artel 3742 Hans Sjostrand (hans@ipunplugged.com) 3743 ipUnplugged 3745 James V. Luciani (james_luciani@mindspring.com) 3746 Consultant 3748 Working Group Chairs: 3749 George Swallow, email: swallow@cisco.com 3750 Loa Andersson, email: loa@pi.se 3752 MPLS Working Group, email: mpls@uu.net 3753 " 3754 DESCRIPTION 3755 "Copyright (C) The Internet Society (2003). This 3756 version of this MIB module is part of RFCXXX; see 3757 the RFC itself for full legal notices. 3759 This MIB contains managed object definitions for 3760 configuring and monitoring the Multiprotocol Label 3761 Switching (MPLS), Label Distribution Protocol (LDP), 3762 utilizing Frame Relay as the Layer 2 media." 3763 REVISION "200306281200Z" -- 28 June 2003 3764 DESCRIPTION 3765 "Initial version published as part of RFC XXXX." 3767 -- Please see the IANA Considerations Section. 3768 -- The requested mplsStdMIB subId is 6, e.g. 3769 -- ::= { mplsStdMIB 6 } 3771 ::= { mplsStdMIB XXX } -- to be assigned by IANA 3773 --**************************************************************** 3775 mplsLdpFrameRelayObjects OBJECT IDENTIFIER 3776 ::= { mplsLdpFrameRelayStdMIB 1 } 3778 mplsLdpFrameRelayConformance OBJECT IDENTIFIER 3779 ::= { mplsLdpFrameRelayStdMIB 2 } 3781 --**************************************************************** 3782 -- MPLS LDP Frame Relay Objects 3783 --**************************************************************** 3785 -- 3786 -- Ldp Entity Objects for Frame Relay 3787 -- 3789 mplsLdpEntityFrameRelayObjects OBJECT IDENTIFIER ::= 3790 { mplsLdpFrameRelayObjects 1 } 3792 mplsLdpEntityFrameRelayTable OBJECT-TYPE 3793 SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayEntry 3794 MAX-ACCESS not-accessible 3795 STATUS current 3796 DESCRIPTION 3797 "This table contains Frame Relay specific 3798 information which could be used in the 3799 'Optional Parameters' and other Frame Relay 3800 Relay specific information. 3802 This table 'sparse augments' the mplsLdpEntityTable 3803 when Frame Relay is the Layer 2 medium." 3804 ::= { mplsLdpEntityFrameRelayObjects 1 } 3806 mplsLdpEntityFrameRelayEntry OBJECT-TYPE 3807 SYNTAX MplsLdpEntityFrameRelayEntry 3808 MAX-ACCESS not-accessible 3809 STATUS current 3810 DESCRIPTION 3811 "An entry in this table represents the Frame Relay 3812 optional parameters associated with the LDP entity." 3813 INDEX { mplsLdpEntityLdpId, 3814 mplsLdpEntityIndex 3815 } 3816 ::= { mplsLdpEntityFrameRelayTable 1 } 3818 MplsLdpEntityFrameRelayEntry ::= SEQUENCE { 3819 mplsLdpEntityFrameRelayIfIndexOrZero InterfaceIndexOrZero, 3820 mplsLdpEntityFrameRelayMergeCap INTEGER, 3821 mplsLdpEntityFrameRelayLRComponents Unsigned32, 3822 mplsLdpEntityFrameRelayVcDirectionality INTEGER, 3823 mplsLdpEntityFrameRelayStorageType StorageType, 3824 mplsLdpEntityFrameRelayRowStatus RowStatus 3825 } 3827 mplsLdpEntityFrameRelayIfIndexOrZero OBJECT-TYPE 3828 SYNTAX InterfaceIndexOrZero 3829 MAX-ACCESS read-create 3830 STATUS current 3831 DESCRIPTION 3832 "This value represents either the InterfaceIndex of 3833 the 'ifLayer' where the Frame Relay Labels 'owned' by this 3834 entry were created, or 0 (zero). The value of zero 3835 means that the InterfaceIndex is not known. For example, 3836 if the InterfaceIndex is created subsequent to the 3837 Frame Relay Label's creation, then it would not be known. 3838 However, if the InterfaceIndex is known, then it must 3839 be represented by this value. 3841 If an InterfaceIndex becomes known, then the 3842 network management entity (e.g. SNMP agent) responsible 3843 for this object MUST change the value from 0 (zero) to the 3844 value of the InterfaceIndex. If an Frame Relay Label is 3845 being used in forwarding data, then the value of this 3846 object MUST be the InterfaceIndex." 3847 ::= { mplsLdpEntityFrameRelayEntry 1 } 3849 mplsLdpEntityFrameRelayMergeCap OBJECT-TYPE 3850 SYNTAX INTEGER { 3851 notSupported(0), 3852 supported(1) 3853 } 3854 MAX-ACCESS read-create 3855 STATUS current 3856 DESCRIPTION 3857 "This represents whether or not the Frame Relay merge 3858 capability is supported. This is the EXACT value for the 3859 Frame Relay Session Parameter, field M (for Frame Relay 3860 Merge Capabilities). The Frame Relay Session Parameter 3861 is an optional parameter in the Initialization Message. 3863 The description from rfc3036.txt is: 3864 'M, Frame Relay Merge Capabilities 3865 Specifies the merge capabilities of a Frame Relay switch. The 3866 following values are supported in this version of the 3867 specification: 3869 Value Meaning 3871 0 Merge not supported 3872 1 Merge supported 3874 Non-merge and merge Frame Relay LSRs may freely interoperate.' 3876 Please refer to the following reference for a complete 3877 description of this feature." 3878 REFERENCE 3879 "RFC3036, LDP Specification, Section 3.5.3 Initialization Message." 3880 ::= { mplsLdpEntityFrameRelayEntry 2 } 3882 mplsLdpEntityFrameRelayLRComponents OBJECT-TYPE 3883 SYNTAX Unsigned32 (1..65535) 3884 MAX-ACCESS read-only 3885 STATUS current 3886 DESCRIPTION 3887 "Number of Label Range Components in the Initialization 3888 message. This also represents the number of entries 3889 in the mplsLdpEntityFrameRelayLRTable which correspond 3890 to this entry. 3892 This is the EXACT value for the Frame Relay Session Parameter, 3893 field N (for Number of label range components). The Frame Relay 3894 Session Parameter is an optional parameter in 3895 the Initialization Message. 3897 The description from rfc3036.txt is: 3899 'N, Number of label range components 3900 Specifies the number of Frame Relay Label Range Components 3901 included in the TLV.' 3903 Please refer to the following reference for a complete 3904 description of this feature." 3905 REFERENCE 3906 "RFC3036, LDP Specification, Section 3.5.3 Initialization Message." 3907 ::= { mplsLdpEntityFrameRelayEntry 3 } 3909 mplsLdpEntityFrameRelayVcDirectionality OBJECT-TYPE 3910 SYNTAX INTEGER { 3911 bidirectional(0), 3912 unidirection(1) 3913 } 3914 MAX-ACCESS read-create 3915 STATUS current 3916 DESCRIPTION 3917 "If the value of this object is 'bidirectional(0)', then 3918 the LSR supports the use of a given DLCI as a label for 3919 both directions independently. If the value of 3920 this object is 'unidirectional(1)', then the LSR 3921 uses the given DLCI as a label in only one direction. 3923 This is the EXACT value for the Frame Relay Session Parameter, 3924 field D (for VC Directionality). The Frame Relay Session Parameter 3925 is an optional parameter in the Initialization Message. 3927 The description from rfc3036.txt is: 3929 'D, VC Directionality 3930 A value of 0 specifies bidirectional VC capability, meaning the 3931 LSR can support the use of a given DLCI as a label for both 3932 link directions independently. A value of 1 specifies 3933 unidirectional VC capability, meaning a given DLCI may appear 3934 in a label mapping for one direction on the link only. When 3935 either or both of the peers specifies unidirectional VC 3936 capability, both LSRs use unidirectional VC label assignment 3937 for the link as follows. The LSRs compare their LDP 3938 Identifiers as unsigned integers. The LSR with the larger LDP 3939 Identifier may assign only odd-numbered DLCIs in the range as 3940 labels. The system with the smaller LDP Identifier may assign 3941 only even-numbered DLCIs in the range as labels.' 3943 Please refer to the following reference for a complete 3944 description of this feature." 3945 REFERENCE 3946 "RFC3036, LDP Specification, Section 3.5.3 Initialization Message." 3947 ::= { mplsLdpEntityFrameRelayEntry 4 } 3949 mplsLdpEntityFrameRelayStorageType OBJECT-TYPE 3950 SYNTAX StorageType 3951 MAX-ACCESS read-create 3952 STATUS current 3953 DESCRIPTION 3954 "The storage type for this conceptual row. 3955 Conceptual rows having the value 'permanent(4)' 3956 need not allow write-access to any columnar 3957 objects in the row." 3958 DEFVAL { nonVolatile } 3959 ::= { mplsLdpEntityFrameRelayEntry 5 } 3961 mplsLdpEntityFrameRelayRowStatus OBJECT-TYPE 3962 SYNTAX RowStatus 3963 MAX-ACCESS read-create 3964 STATUS current 3965 DESCRIPTION 3966 "The status of this conceptual row. All writable 3967 objects in this row may be modified at any time, 3968 however, as described in detail in the section 3969 entitled, 'Changing Values After Session 3970 Establishment', and again described in the 3971 DESCRIPTION clause of the 3972 mplsLdpEntityAdminStatus object, 3973 if a session has been initiated with a Peer, 3974 changing objects in this table will 3975 wreak havoc with the session and interrupt 3976 traffic. To repeat again: 3977 the recommended procedure is to set the 3978 mplsLdpEntityAdminStatus to 3979 down, thereby explicitly causing a 3980 session to be torn down. Then, 3981 change objects in this entry, then set 3982 the mplsLdpEntityAdminStatus 3983 to enable which enables a new session 3984 to be initiated." 3985 ::= { mplsLdpEntityFrameRelayEntry 6 } 3987 -- 3988 -- Frame Relay Label Range Components 3989 -- 3991 mplsLdpEntityFrameRelayLRTable OBJECT-TYPE 3992 SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayLREntry 3993 MAX-ACCESS not-accessible 3994 STATUS current 3995 DESCRIPTION 3996 "This table contains information about the 3997 Optional Parameters for the Frame Relay Session 3998 in the LDP Initialization Message, specifically 3999 it contains information about the Frame Relay 4000 Label Range Components. 4002 If the value of the object 4003 'mplsLdpEntityOptionalParameters' contains the 4004 value of 'frameRelaySessionParameters(3)' then 4005 there must be at least one corresponding entry 4006 in this table." 4007 ::= { mplsLdpEntityFrameRelayObjects 2 } 4009 mplsLdpEntityFrameRelayLREntry OBJECT-TYPE 4010 SYNTAX MplsLdpEntityFrameRelayLREntry 4011 MAX-ACCESS not-accessible 4012 STATUS current 4013 DESCRIPTION 4014 "An entry in this table represents the Frame Relay 4015 Label Range Component associated with the LDP entity." 4016 INDEX { mplsLdpEntityLdpId, 4017 mplsLdpEntityIndex, 4018 mplsLdpEntityFrameRelayLRMinDlci 4019 } 4020 ::= { mplsLdpEntityFrameRelayLRTable 1 } 4022 MplsLdpEntityFrameRelayLREntry ::= SEQUENCE { 4023 mplsLdpEntityFrameRelayLRMinDlci DLCI, 4024 mplsLdpEntityFrameRelayLRMaxDlci DLCI, 4025 mplsLdpEntityFrameRelayLRLen INTEGER, 4026 mplsLdpEntityFrameRelayLRStorageType StorageType, 4027 mplsLdpEntityFrameRelayLRRowStatus RowStatus 4028 } 4030 mplsLdpEntityFrameRelayLRMinDlci OBJECT-TYPE 4031 SYNTAX DLCI 4032 MAX-ACCESS not-accessible 4033 STATUS current 4034 DESCRIPTION 4035 "The lower bound which is supported. This value should 4036 be the same as that in the Frame Relay Label Range 4037 Component's Minimum DLCI field. The value of zero 4038 is valid for the minimum DLCI field of the label." 4039 REFERENCE 4040 "RFC3034, Use of Label Switching on Frame Relay Networks 4041 Specification." 4042 ::= { mplsLdpEntityFrameRelayLREntry 1 } 4044 mplsLdpEntityFrameRelayLRMaxDlci OBJECT-TYPE 4045 SYNTAX DLCI 4046 MAX-ACCESS read-create 4047 STATUS current 4048 DESCRIPTION 4049 "The upper bound which is supported. This value should 4050 be the same as that in the Frame Relay Label Range 4051 Component's Maximum DLCI field." 4052 ::= { mplsLdpEntityFrameRelayLREntry 2 } 4054 mplsLdpEntityFrameRelayLRLen OBJECT-TYPE 4055 SYNTAX INTEGER { 4056 tenDlciBits(0), 4057 twentyThreeDlciBits(2) 4058 } 4059 MAX-ACCESS read-create 4060 STATUS current 4061 DESCRIPTION 4062 "This object specifies the length of the DLCI bits. 4064 This is the EXACT value for the Len field of the 4065 Frame Relay Label Range Component. 4067 The description from rfc3036.txt is: 4069 'Len 4070 This field specifies the number of bits of the DLCI. The 4071 following values are supported: 4073 Len DLCI bits 4075 0 10 4076 2 23 4078 Len values 1 and 3 are reserved.' 4080 Please refer to the following reference for a complete 4081 description of this feature." 4082 REFERENCE 4083 "RFC3036, LDP Specification, Section 3.5.3 Initialization Message." 4084 ::= { mplsLdpEntityFrameRelayLREntry 3 } 4086 mplsLdpEntityFrameRelayLRStorageType OBJECT-TYPE 4087 SYNTAX StorageType 4088 MAX-ACCESS read-create 4089 STATUS current 4090 DESCRIPTION 4091 "The storage type for this conceptual row. 4092 Conceptual rows having the value 'permanent(4)' 4093 need not allow write-access to any columnar 4094 objects in the row." 4095 DEFVAL { nonVolatile } 4096 ::= { mplsLdpEntityFrameRelayLREntry 4 } 4098 mplsLdpEntityFrameRelayLRRowStatus OBJECT-TYPE 4099 SYNTAX RowStatus 4100 MAX-ACCESS read-create 4101 STATUS current 4102 DESCRIPTION 4103 "The status of this conceptual row. All writable 4104 objects in this row may be modified at any time, 4105 however, as described in detail in the section 4106 entitled, 'Changing Values After Session 4107 Establishment', and again described in the 4108 DESCRIPTION clause of the 4109 mplsLdpEntityAdminStatus object, 4110 if a session has been initiated with a Peer, 4111 changing objects in this table will 4112 wreak havoc with the session and interrupt 4113 traffic. To repeat again: 4114 the recommended procedure is to set the 4115 mplsLdpEntityAdminStatus to down, thereby 4116 explicitly causing a session to be torn down. Then, 4117 change objects in this entry, then set the 4118 mplsLdpEntityAdminStatus to enable which enables 4119 a new session to be initiated." 4120 ::= { mplsLdpEntityFrameRelayLREntry 5 } 4122 -- 4123 -- MPLS LDP Frame Relay Session Information 4124 -- 4126 mplsLdpFrameRelaySessionObjects OBJECT IDENTIFIER ::= 4127 { mplsLdpFrameRelayObjects 2 } 4129 mplsLdpFrameRelaySessionTable OBJECT-TYPE 4130 SYNTAX SEQUENCE OF MplsLdpFrameRelaySessionEntry 4131 MAX-ACCESS not-accessible 4132 STATUS current 4133 DESCRIPTION 4134 "A table of Frame Relay label range intersections 4135 between the LDP Entities and LDP Peers. 4137 Each row represents a single label range intersection. 4139 NOTE: this table cannot use the 'AUGMENTS' 4140 clause because there is not necessarily a one-to-one 4141 mapping between this table and the mplsLdpSessionTable." 4142 ::= { mplsLdpFrameRelaySessionObjects 1 } 4144 mplsLdpFrameRelaySessionEntry OBJECT-TYPE 4145 SYNTAX MplsLdpFrameRelaySessionEntry 4146 MAX-ACCESS not-accessible 4147 STATUS current 4148 DESCRIPTION 4149 "An entry in this table represents information on a 4150 single label range intersection between an 4151 LDP Entity and LDP Peer. 4153 The information contained in a row is read-only." 4154 INDEX { mplsLdpEntityLdpId, 4155 mplsLdpEntityIndex, 4156 mplsLdpPeerLdpId, 4157 mplsLdpFrameRelaySessionMinDlci 4158 } 4159 ::= { mplsLdpFrameRelaySessionTable 1 } 4161 MplsLdpFrameRelaySessionEntry ::= SEQUENCE { 4162 mplsLdpFrameRelaySessionMinDlci DLCI, 4163 mplsLdpFrameRelaySessionMaxDlci DLCI, 4164 mplsLdpFrameRelaySessionLen INTEGER 4165 } 4167 mplsLdpFrameRelaySessionMinDlci OBJECT-TYPE 4168 SYNTAX DLCI 4169 MAX-ACCESS not-accessible 4170 STATUS current 4171 DESCRIPTION 4172 "The lower bound of DLCIs which are supported. 4173 The value of zero is a valid value for the 4174 minimum DLCI field of the label." 4175 REFERENCE 4176 "RFC3034, Use of Label Switching on Frame Relay Networks 4177 Specification." 4178 ::= { mplsLdpFrameRelaySessionEntry 1 } 4180 mplsLdpFrameRelaySessionMaxDlci OBJECT-TYPE 4181 SYNTAX DLCI 4182 MAX-ACCESS read-only 4183 STATUS current 4184 DESCRIPTION 4185 "The upper bound of DLCIs which are supported." 4186 ::= { mplsLdpFrameRelaySessionEntry 2 } 4188 mplsLdpFrameRelaySessionLen OBJECT-TYPE 4189 SYNTAX INTEGER { 4190 tenDlciBits(0), 4191 twentyThreeDlciBits(2) 4192 } 4193 MAX-ACCESS read-only 4194 STATUS current 4195 DESCRIPTION 4196 "This object specifies the DLCI bits." 4197 ::= { mplsLdpFrameRelaySessionEntry 3 } 4199 --**************************************************************** 4200 -- Module Conformance Statement 4201 --**************************************************************** 4203 mplsLdpFrameRelayGroups 4204 OBJECT IDENTIFIER ::= { mplsLdpFrameRelayConformance 1 } 4206 mplsLdpFrameRelayCompliances 4207 OBJECT IDENTIFIER ::= { mplsLdpFrameRelayConformance 2 } 4209 -- 4210 -- Full Compliance 4211 -- 4213 mplsLdpFrameRelayModuleFullCompliance MODULE-COMPLIANCE 4214 STATUS current 4215 DESCRIPTION 4216 "The Module is implemented with support for 4217 read-create and read-write. In other words, 4218 both monitoring and configuration 4219 are available when using this MODULE-COMPLIANCE." 4220 MODULE -- this module 4221 MANDATORY-GROUPS { 4222 mplsLdpFrameRelayGroup 4223 } 4225 OBJECT mplsLdpEntityFrameRelayRowStatus 4226 SYNTAX RowStatus { active(1) } 4227 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 4228 DESCRIPTION 4229 "Support for createAndWait and notInService is not required." 4231 OBJECT mplsLdpEntityFrameRelayLRRowStatus 4232 SYNTAX RowStatus { active(1) } 4233 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 4234 DESCRIPTION 4235 "Support for createAndWait and notInService is not required." 4237 ::= { mplsLdpFrameRelayCompliances 1 } 4239 -- 4240 -- Read-Only Compliance 4241 -- 4243 mplsLdpFrameRelayModuleReadOnlyCompliance MODULE-COMPLIANCE 4244 STATUS current 4245 DESCRIPTION 4246 "The Module is implemented with support for 4247 read-only. In other words, only monitoring 4248 is available by implementing this MODULE-COMPLIANCE." 4249 MODULE -- this module 4250 MANDATORY-GROUPS { 4251 mplsLdpFrameRelayGroup 4252 } 4254 OBJECT mplsLdpEntityFrameRelayIfIndexOrZero 4255 MIN-ACCESS read-only 4256 DESCRIPTION 4257 "Write access is not required." 4259 OBJECT mplsLdpEntityFrameRelayMergeCap 4260 MIN-ACCESS read-only 4261 DESCRIPTION 4262 "Write access is not required." 4264 OBJECT mplsLdpEntityFrameRelayVcDirectionality 4265 MIN-ACCESS read-only 4266 DESCRIPTION 4267 "Write access is not required." 4269 OBJECT mplsLdpEntityFrameRelayStorageType 4270 MIN-ACCESS read-only 4271 DESCRIPTION 4272 "Write access is not required." 4274 OBJECT mplsLdpEntityFrameRelayRowStatus 4275 SYNTAX RowStatus { active(1) } 4276 MIN-ACCESS read-only 4277 DESCRIPTION 4278 "Write access is not required, and active is the 4279 only status that needs to be supported." 4281 OBJECT mplsLdpEntityFrameRelayLRMaxDlci 4282 MIN-ACCESS read-only 4283 DESCRIPTION 4284 "Write access is not required." 4286 OBJECT mplsLdpEntityFrameRelayLRLen 4287 MIN-ACCESS read-only 4288 DESCRIPTION 4289 "Write access is not required." 4291 OBJECT mplsLdpEntityFrameRelayLRStorageType 4292 MIN-ACCESS read-only 4293 DESCRIPTION 4294 "Write access is not required." 4296 OBJECT mplsLdpEntityFrameRelayLRRowStatus 4297 SYNTAX RowStatus { active(1) } 4298 MIN-ACCESS read-only 4299 DESCRIPTION 4300 "Write access is not required, and active is the 4301 only status that needs to be supported." 4302 ::= { mplsLdpFrameRelayCompliances 2 } 4304 -- 4305 -- units of conformance 4306 -- 4308 mplsLdpFrameRelayGroup OBJECT-GROUP 4309 OBJECTS { 4310 mplsLdpEntityFrameRelayIfIndexOrZero, 4311 mplsLdpEntityFrameRelayMergeCap, 4312 mplsLdpEntityFrameRelayLRComponents, 4313 mplsLdpEntityFrameRelayVcDirectionality, 4314 mplsLdpEntityFrameRelayStorageType, 4315 mplsLdpEntityFrameRelayRowStatus, 4316 mplsLdpEntityFrameRelayLRMaxDlci, 4317 mplsLdpEntityFrameRelayLRLen, 4318 mplsLdpEntityFrameRelayLRStorageType, 4319 mplsLdpEntityFrameRelayLRRowStatus, 4320 mplsLdpFrameRelaySessionMaxDlci, 4321 mplsLdpFrameRelaySessionLen 4322 } 4323 STATUS current 4324 DESCRIPTION 4325 "Objects that apply to all MPLS LDP implementations 4326 using Frame Relay as the Layer 2." 4327 ::= { mplsLdpFrameRelayGroups 1 } 4329 END 4331 4.3. The MPLS-LDP-GENERIC-STD-MIB Module 4333 This MIB Module MUST be supported if LDP uses a Per Platform Label 4334 Space. This MIB Module contains a Label Range (LR) table for 4335 configuring MPLS Generic Label Ranges. This table is 4336 mplsLdpEntityGenericLRTable. Although the LDP Specification does not 4337 provide a way for configuring Label Ranges for Generic Labels, the 4338 MIB does provide a way to reserve a range of generic labels because 4339 this was thought to be useful by the working group. 4341 MPLS-LDP-GENERIC-STD-MIB DEFINITIONS ::= BEGIN 4343 IMPORTS 4345 OBJECT-TYPE, 4346 MODULE-IDENTITY, 4347 Unsigned32 4348 FROM SNMPv2-SMI 4350 MODULE-COMPLIANCE, 4351 OBJECT-GROUP 4352 FROM SNMPv2-CONF 4354 RowStatus, 4355 StorageType 4356 FROM SNMPv2-TC 4358 InterfaceIndexOrZero 4359 FROM IF-MIB 4361 mplsStdMIB 4362 FROM MPLS-TC-STD-MIB 4364 mplsLdpEntityLdpId, 4365 mplsLdpEntityIndex 4366 FROM MPLS-LDP-STD-MIB 4367 ; 4369 mplsLdpGenericStdMIB MODULE-IDENTITY 4370 LAST-UPDATED "200306281200Z" -- 28 June 2003 4371 ORGANIZATION "Multiprotocol Label Switching (mpls) 4372 Working Group" 4373 CONTACT-INFO 4374 "Joan Cucchiara (jcucchiara@artel.com) 4375 Artel 4377 Hans Sjostrand (hans@ipunplugged.com) 4378 ipUnplugged 4380 James V. Luciani (james_luciani@mindspring.com) 4381 Consultant 4383 Working Group Chairs: 4384 George Swallow, email: swallow@cisco.com 4385 Loa Andersson, email: loa@pi.se 4387 MPLS Working Group, email: mpls@uu.net 4388 " 4389 DESCRIPTION 4390 "Copyright (C) The Internet Society (2003). This 4391 version of this MIB module is part of RFCXXX; see 4392 the RFC itself for full legal notices. 4394 This MIB contains managed object definitions for 4395 configuring and monitoring the Multiprotocol Label 4396 Switching (MPLS), Label Distribution Protocol (LDP), 4397 utilizing ethernet as the Layer 2 media." 4398 REVISION "200306281200Z" -- 28 June 2003 4399 DESCRIPTION 4400 "Initial version published as part of RFC XXXX." 4402 -- Please see the IANA Considerations Section. 4404 -- The requested mplsStdMIB subId is 7, e.g. 4405 -- ::= { mplsStdMIB 7 } 4407 ::= { mplsStdMIB XXX } -- to be assigned by IANA 4409 --**************************************************************** 4411 mplsLdpGenericObjects 4412 OBJECT IDENTIFIER ::= { mplsLdpGenericStdMIB 1 } 4413 mplsLdpGenericConformance 4414 OBJECT IDENTIFIER ::= { mplsLdpGenericStdMIB 2 } 4416 --**************************************************************** 4417 -- MPLS LDP GENERIC Objects 4418 --**************************************************************** 4420 -- 4421 -- Ldp Entity Objects for Generic Labels 4422 -- 4424 mplsLdpEntityGenericObjects OBJECT IDENTIFIER ::= 4425 { mplsLdpGenericObjects 1 } 4427 -- 4428 -- The MPLS LDP Entity Generic Label Range Table 4429 -- 4431 mplsLdpEntityGenericLRTable OBJECT-TYPE 4432 SYNTAX SEQUENCE OF MplsLdpEntityGenericLREntry 4433 MAX-ACCESS not-accessible 4434 STATUS current 4435 DESCRIPTION 4436 "The MPLS LDP Entity Generic Label Range (LR) 4437 Table. 4439 The purpose of this table is to provide a mechanism 4440 for configurating a contiguous range of generic labels, 4441 or a 'label range' for LDP Entities. 4443 LDP Entities which use Generic Labels must have at least 4444 one entry in this table. In other words, this table 4445 'extends' the mpldLdpEntityTable for Generic Labels." 4447 ::= { mplsLdpEntityGenericObjects 1 } 4449 mplsLdpEntityGenericLREntry OBJECT-TYPE 4450 SYNTAX MplsLdpEntityGenericLREntry 4451 MAX-ACCESS not-accessible 4452 STATUS current 4453 DESCRIPTION 4454 "A row in the LDP Entity Generic Label 4455 Range (LR) Table. One entry in this table contains 4456 information on a single range of labels 4457 represented by the configured Upper and Lower 4458 Bounds pairs. NOTE: there is NO corresponding 4459 LDP message which relates to the information 4460 in this table, however, this table does provide 4461 a way for a user to 'reserve' a generic label 4462 range. 4464 NOTE: The ranges for a specific LDP Entity 4465 are UNIQUE and non-overlapping. 4467 A row will not be created unless a unique and 4468 non-overlapping range is specified." 4469 INDEX { mplsLdpEntityLdpId, 4470 mplsLdpEntityIndex, 4471 mplsLdpEntityGenericLRMin, 4472 mplsLdpEntityGenericLRMax 4473 } 4474 ::= { mplsLdpEntityGenericLRTable 1 } 4476 MplsLdpEntityGenericLREntry ::= SEQUENCE { 4477 mplsLdpEntityGenericLRMin Unsigned32, 4478 mplsLdpEntityGenericLRMax Unsigned32, 4479 mplsLdpEntityGenericLabelSpace INTEGER, 4480 mplsLdpEntityGenericIfIndexOrZero InterfaceIndexOrZero, 4481 mplsLdpEntityGenericLRStorageType StorageType, 4482 mplsLdpEntityGenericLRRowStatus RowStatus 4483 } 4485 mplsLdpEntityGenericLRMin OBJECT-TYPE 4486 SYNTAX Unsigned32(0..1048575) 4487 MAX-ACCESS not-accessible 4488 STATUS current 4489 DESCRIPTION 4490 "The minimum label configured for this range." 4491 ::= { mplsLdpEntityGenericLREntry 1 } 4493 mplsLdpEntityGenericLRMax OBJECT-TYPE 4494 SYNTAX Unsigned32(0..1048575) 4495 MAX-ACCESS not-accessible 4496 STATUS current 4497 DESCRIPTION 4498 "The maximum label configured for this range." 4499 ::= { mplsLdpEntityGenericLREntry 2 } 4501 mplsLdpEntityGenericLabelSpace OBJECT-TYPE 4502 SYNTAX INTEGER { 4503 perPlatform(1), 4504 perInterface(2) 4505 } 4506 MAX-ACCESS read-create 4507 STATUS current 4508 DESCRIPTION 4509 "This value of this object is perPlatform(1), then 4510 this means that the label space type is 4511 per platform. 4513 If this object is perInterface(2), then this 4514 means that the label space type is per Interface." 4515 REFERENCE 4516 "RFC3036, LDP Specification, Section 2.2.1, 4517 Label Spaces." 4518 DEFVAL { perPlatform } 4519 ::= { mplsLdpEntityGenericLREntry 3 } 4521 mplsLdpEntityGenericIfIndexOrZero OBJECT-TYPE 4522 SYNTAX InterfaceIndexOrZero 4523 MAX-ACCESS read-create 4524 STATUS current 4525 DESCRIPTION 4526 "This value represents either the InterfaceIndex of 4527 the 'ifLayer' where these Generic Label would be created, 4528 or 0 (zero). The value of zero means that the 4529 InterfaceIndex is not known. 4531 However, if the InterfaceIndex is known, 4532 then it must be represented by this value. 4534 If an InterfaceIndex becomes known, then the 4535 network management entity (e.g. SNMP agent) responsible 4536 for this object MUST change the value from 0 (zero) to the 4537 value of the InterfaceIndex." 4539 ::= { mplsLdpEntityGenericLREntry 4 } 4541 mplsLdpEntityGenericLRStorageType OBJECT-TYPE 4542 SYNTAX StorageType 4543 MAX-ACCESS read-create 4544 STATUS current 4545 DESCRIPTION 4546 "The storage type for this conceptual row. 4547 Conceptual rows having the value 'permanent(4)' 4548 need not allow write-access to any columnar 4549 objects in the row." 4550 DEFVAL { nonVolatile } 4551 ::= { mplsLdpEntityGenericLREntry 5 } 4553 mplsLdpEntityGenericLRRowStatus OBJECT-TYPE 4554 SYNTAX RowStatus 4555 MAX-ACCESS read-create 4556 STATUS current 4557 DESCRIPTION 4558 "The status of this conceptual row. All writable 4559 objects in this row may be modified at any time, 4560 however, as described in detail in the section 4561 entitled, 'Changing Values After Session 4562 Establishment', and again described in the 4563 DESCRIPTION clause of the mplsLdpEntityAdminStatus object, 4564 if a session has been initiated with a Peer, 4565 changing objects in this table will 4566 wreak havoc with the session and interrupt traffic. 4567 To repeat again: the recommended procedure is 4568 to set the mplsLdpEntityAdminStatus to 4569 down, thereby explicitly causing a 4570 session to be torn down. Then, change objects 4571 in this entry, then set the mplsLdpEntityAdminStatus 4572 to enable which enables a new session to be initiated. 4574 There must exist at least one entry in this 4575 table for every LDP Entity that has a 4576 generic label configured." 4577 ::= { mplsLdpEntityGenericLREntry 6 } 4579 --**************************************************************** 4580 -- Module Conformance Statement 4581 --**************************************************************** 4582 mplsLdpGenericGroups 4583 OBJECT IDENTIFIER ::= { mplsLdpGenericConformance 1 } 4585 mplsLdpGenericCompliances 4586 OBJECT IDENTIFIER ::= { mplsLdpGenericConformance 2 } 4588 -- 4589 -- Full Compliance 4590 -- 4592 mplsLdpGenericModuleFullCompliance MODULE-COMPLIANCE 4593 STATUS current 4594 DESCRIPTION 4595 "The Module is implemented with support for 4596 read-create and read-write. In other words, 4597 both monitoring and configuration 4598 are available when using this MODULE-COMPLIANCE." 4599 MODULE -- this module 4600 MANDATORY-GROUPS { 4601 mplsLdpGenericGroup 4602 } 4604 OBJECT mplsLdpEntityGenericLRRowStatus 4605 SYNTAX RowStatus { active(1) } 4606 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 4607 DESCRIPTION 4608 "Support for createAndWait and notInService is not required." 4610 ::= { mplsLdpGenericCompliances 1 } 4612 -- 4613 -- Read-Only Compliance 4614 -- 4616 mplsLdpGenericModuleReadOnlyCompliance MODULE-COMPLIANCE 4617 STATUS current 4618 DESCRIPTION 4619 "The Module is implemented with support for 4620 read-only. In other words, only monitoring 4621 is available by implementing this MODULE-COMPLIANCE." 4622 MODULE -- this module 4623 MANDATORY-GROUPS { 4624 mplsLdpGenericGroup 4625 } 4627 OBJECT mplsLdpEntityGenericLabelSpace 4628 MIN-ACCESS read-only 4629 DESCRIPTION 4630 "Write access is not required." 4632 OBJECT mplsLdpEntityGenericIfIndexOrZero 4633 MIN-ACCESS read-only 4634 DESCRIPTION 4635 "Write access is not required." 4637 OBJECT mplsLdpEntityGenericLRStorageType 4638 MIN-ACCESS read-only 4639 DESCRIPTION 4640 "Write access is not required." 4642 OBJECT mplsLdpEntityGenericLRRowStatus 4643 SYNTAX RowStatus { active(1) } 4644 MIN-ACCESS read-only 4645 DESCRIPTION 4646 "Write access is not required, and active is the 4647 only status that needs to be supported." 4649 ::= { mplsLdpGenericCompliances 2 } 4651 -- 4652 -- units of conformance 4653 -- 4655 mplsLdpGenericGroup OBJECT-GROUP 4656 OBJECTS { 4657 mplsLdpEntityGenericLabelSpace, 4658 mplsLdpEntityGenericIfIndexOrZero, 4659 mplsLdpEntityGenericLRStorageType, 4660 mplsLdpEntityGenericLRRowStatus 4661 } 4662 STATUS current 4663 DESCRIPTION 4664 "Objects that apply to all MPLS LDP implementations 4665 using Generic Labels as the Layer 2." 4666 ::= { mplsLdpGenericGroups 1 } 4668 END 4670 5. Revision History 4672 NOTE TO RFC-Editor: before publishing this document as an RFC, 4673 please remove this Revision History (change log) section. 4675 5.1. Changes from 4677 Updated with comments from the 3rd Last Call for this MIB which took 4678 place, Thursday, June 12 to June 24, 2003. 4680 Updated with last call comments from Adrian Farell posted to the MPLS 4681 Working Group email list on June 12, 2003. 4683 Updated the 2 outstanding issues from Bert's email May 9th which was 4684 posted to the MPLS Working Group. These issues were not updated for 4685 version 10, so were addressed in version 11: 1) updated #3 from that 4686 email and 2) reviewed all the InetAddressType and InetAddress objects 4687 to make sure that descriptions were per rfc3291. 4689 5.2. Changes from 4691 Renamed the MIB module to include Std and also updated the IANA 4692 Considerations Section to use mplsStdMIB. 4694 Updated per Bert's email May 9th, with 2 exceptions: 1) did not yet 4695 update #3 from that email and 2) did not yet review all the 4696 InetAddressType and InetAddress objects to make sure that 4697 descriptions were per rfc3291. 4699 Changed Ses to Session for clarity. 4701 5.3. Changes from 4703 Added the new MIB boiler plate and associated MIB reference changes. 4705 Reworked the OID tree structure so that the Modules only have the 4706 mplsMIB subid dependency. This was discussed in mpls wg email 4707 (discussion was mostly between Bert, Tom and Joan). 4709 Added IANA Considerations section. This contains 4 subsections, one 4710 per MIB module. 4712 Updated and added new references as needed. 4714 Changed mplsMIB subid values to agree with the latest "Multiprotocol 4715 Label Switching (MPLS) Management Overview" document, [MPLSMGMT]. 4717 Moved MIB modules around so that they would appear in subId order. 4718 The Generic MIB module is shown last, since the subid is 7 (which is 4719 the last (and largest) subid requested by IANA. 4721 5.3.1. Changes based on MIB Doctor Review Comments 4723 The following changes are based on comments from the MIB DR Review. 4724 The comments are from email to the mpls working group dated, Dec 6, 4725 2002. These comments are quoted and prefaced by "REQ: comment goes 4726 here", and then followed by our resolution. 4728 "REQ: - missing IPR section". RSP: it has been added. 4730 "REQ: - Security considerations probably needs more work 4731 Security ADs want you to explain what the vulnerabilities/risks 4732 are and what to do against them. 4733 Also for read only objects, pls list each (group of) object(s) 4734 and explain what sensitivity attributes they have". RSP: Done. We 4735 added subsections here since the Security template is MIB Module 4736 based and it seemed to us more clear to do a subsection per MIB 4737 Module. 4739 "REQ: - pls do the consistency checking for descriptors and all 4740 that". RSP: believe this to be done. Changed Gen to Generic 4741 everywhere, changed Fr to FrameRelay, changed RO to ReadOnly. 4742 Changed Sessions to Ses everywhere. Reviewed tables to make sure 4743 they were prefixed consistently. Added more references, used more 4744 TCs and other stuff. 4746 "REQ: - sect 3.5 1st sentence, s/would be/are/ ??". RSP: done. 4748 "REQ: - sect 3.5 2nd para first sentence s/initiation/initiate/ ". 4749 RSP: done. 4751 "REQ: - section 3.5.2 s/mpsl/mpls/". RSP: done. 4753 "REQ: - mplsXxxIndexNext 4754 See my comments on FTN MIB and LSR MIB on these type of objects 4755 Best to use something aka rfc3289 ". RSP: We have imported the 4756 IndexInteger and IndexIntegerNextFree TCs (from rfc3289.txt). NOTE: 4757 we do not like the names of these TCs because they use the term 4758 Integer when the values are Unsigned32. Would prefer new TCs with 4759 IndexUnsigned32 and IndexUnsigned32NextFree. 4761 "REQ:- RowStatus and StorageType objects 4762 see my comments about similar objects in LSR MIB 4763 for StorageType might also want to add a DEFVAL ". RSP: Added 4764 descriptive text to the RowStatus objects to specify which columns 4765 can be changed when row is active. Added descriptive text to the 4766 StorageType objects to specify what happens when the StorageType is 4767 permanent. Also added DEFVALs for the StorageType objects. 4769 "REQ: - mplsLdpNotifications ... { mplsLdpMib 2 } 4770 why not { mplsLdpMib 0} so that it is right away the prefix? 4771 I believe LSR MIB does it that way now. You may want to do 4772 it consistently for all notifications. 4773 I can live with either way, but prefer them to be shorter OIDs.". 4774 RSP: We changed this to follow what LSR MIB does (i.e. 4775 mplsLdpNotifications 0) for shorter OIDs..PP "REQ: - 4776 mplsXxxLastChange 4777 does that time stamp only get changed if an addition/deletion takes 4778 place? Not if something gets changed via a SNMP SET command? 4779 I think I'd prefer to also see changes (modifications) via SET. 4780 But in any event, be very explicit about if those are included or 4781 not.". RSP: All Last change object DESCRIPTIONs have been 4782 updated to be very specific. 4784 "REQ:- mplsLdpLspType 4785 All that stuff in the DESCRIPTION clause is just a repeat of the 4786 TC DESCRIPTION clause. Seems not needed to me. What if a value 4787 gets added later... how do you stay in sync?". RSP: This has 4788 been fixed. 4790 "REQ: - mplsFecAddrLength 4791 Should that be of SYNTAX InetAddressPrefixLength as per RFC3291?". 4792 RSP: yes, fixed. 4794 "REQ: - mplsFecAddrFamily and mplsFecAddr 4795 These are strange. The DESCRIPTIONS are certainly not meeting the 4796 requirements as specified in RFC3291. At other places you do it 4797 correct, so you do understand what is required I think.". RSP: 4798 changed to have a better descriptions. Should note that the TLVs in 4799 the LDP Specification use Address Family Numbers and are still 4800 referring to RFC1700. 4802 "REQ: - mplsLdpLspFecTable claims to be a read-only table. 4803 Yet you have a read-create RowStatus object in it.". RSP: fixed. 4805 "REQ: - mplsLdpSessionUp and mplsLdpSessionDown 4806 Is it not better to just have one notification, namely a 4807 mplsLdpSessionStateChange and then the mplsLdpSesState object will 4808 explain what the change is?". RSP: We prefer to leave it this 4809 way. There are some 3rd Party applications that try to resolve 4810 Notifications, so you see one for down, then resolve this by seeing 4811 another one for up. Granted, these 3rd party apps could be coded to 4812 parse the varbind within the trap, but then this requires coding 4813 whereas having 2 distinct notifications is easier on the developer. 4814 Granted, this maybe makes the MIB design more cumbersome. If this is 4815 a blocking issue, then we will change it. 4817 "REQ:- COMPLIANCE section. I hope that INT ADs are OK with making 4818 IPv6 4819 addresses optional. Is that cause current LDP only supports IPv4? 4820 If so you may want to add that as an explanation.". RSP: IPv6 4821 was made mandatory, also supported in MPLS LDP Spec (rfc3036.txt). 4823 Continue with MIB Dr Comments for the MPLS-LDP-GENERIC-MIB. 4825 "REQ:- same on mplsXXXIndexNext and RowStatus and STorageType 4826 objects". RSP: These hdescriptions have been updated. It should 4827 be noted, that these should be EXACTLY the same as the 4828 mplsLdpEntityTable since the Label Range Tables extend the Entity 4829 Table. "REQ:- this looks wierd: 4830 ::= { mplsMib 6 } -- to be assigned 4831 use cc instead of 6 if you want IANA to assign, and do tell 4832 -- to be assigned by IANA 4833 and write something about it in an IANA Considerations Section if 4834 this is what you want.". RSP: Added more comments, and added an 4835 IANA Considerations Section. "REQ:- mplsGenModuleROCompliance 4836 I would call it mplsGenModuleReadOnlyCompliance 4837 You have used ReadOnly and Full in other places/mib modules and 4838 it is good to be clear and consistent". RSP: done. 4840 MIB Doctor Review comments for ATM. 4842 "REQ:- s/Moduel/Module/". RSP: done. 4844 "REQ:- same on mplsXXXIndexNext and RowStatus and STorageType 4845 objects". RSP: done. 4847 "REQ:- this looks wierd: 4848 ::= { mplsMib 4 } -- to be assigned 4849 use cc instead of 4 if you want IANA to assign, and do tell 4850 -- to be assigned by IANA 4852 and write something about it in an IANA Considerations Section if 4853 this is what you want.". RSP: done. 4855 "REQ:- See earlier remark on Notifications (use zero instead of 2 4856 right away)". RSP:Removed this branch because there aren't any 4857 notifications in this MIB module. 4859 "REQ:- There are still some INTEGER enumerations that start with zero 4860 It is not a BLOCKING problem... but if acceptable, pls make it 4861 start 4862 at 1 (as you have done vor various others of these enumerations)". 4863 RSP: We would rather leave these enums starting with zero. (There are 4864 2 of them in the ATM Module). The reason for leaving them is because 4865 the value zero is what the protocol uses. We have added REFERENCES 4866 to these objects and more info in the descriptions themselves. We 4867 believe it is in the best interest of developers to start enums at 4868 zero. The INET-ADDRESS-MIB uses the value zero, and since we are 4869 already required to use that MIB, there is precedence for zero in an 4870 enum where it makes sense. We believe the value of zero makes sense 4871 for where it is being used in this MIB module. 4873 "REQ:- mplsXxxxROCompliance -> better mplsXxxxReadOnlyCompliance". 4874 RSP: done. 4876 "REQ:- some formatting problems with DEFVAL lines being split on 2 4877 lines?". RSP: fixed. 4879 MIB Doctor Review comments for FrameRelay 4881 "REQ:- consistency in descriptors (FrameRelay vs FR etc)". RSP: 4882 done. "REQ:- same on mplsXXXIndexNext and RowStatus and STorageType 4883 objects". RSP: done. "REQ:- this looks wierd: 4884 ::= { mplsMib 5 } -- to be assigned 4885 use cc instead of 5 if you want IANA to assign, and do tell 4886 -- to be assigned by IANA 4887 and write something about it in an IANA Considerations Section if 4888 this is what you want.". RSP: done. "REQ:- See earlier remark 4889 on Notifications (use zero instead of 2 right away)". RSP:Removed 4890 this branch because there aren't any notifications in this MIB 4891 module. 4893 "REQ:- There are still some INTEGER enumerations that start with zero 4894 It is not a BLOCKING problem... but if acceptable, pls make it 4895 start 4896 at 1 (as you have done vor various others of these enumerations)". 4897 RSP: We would rather leave these enums starting with zero. (There are 4898 4 of them in the Frame Relay Module). The reason for leaving them is 4899 because the value zero is what the protocol uses. We have added 4900 REFERENCES to these objects and more info in the descriptions 4901 themselves. We believe it is in the best interest of developers to 4902 start enums at zero. The INET-ADDRESS-MIB uses the value zero, and 4903 since we are already required to use that MIB, there is precedence 4904 for zero in an enum where it makes sense. We believe the value of 4905 zero makes sense for where it is being used in this MIB module. 4907 "REQ:- mplsLdpEntityFrLRComponents OBJECT-TYPE 4908 SYNTAX Unsigned32 (1..65535) 4909 MAX-ACCESS read-create 4910 STATUS current 4911 DESCRIPTION 4912 "Number of Label Range Components in the Initialization 4913 message. This also represents the number of entries 4914 in the mplsLdpEntityConfFrLRTable which correspond 4915 to this entry." 4916 Where is this mplsLdpEntityConfFrLRTable ??". RSP: fixed. 4917 "REQ:- I see the xxxDlci index objects start at zero. 4918 Pls add to DESCRIPTION clauses why zero must be an index.". RSP: 4919 Since we are using DLCI and the value of zero is valid for a DLCI. A 4920 statement was added about this. Also, used the DLCI TC from 4921 rfc2115.txt to make this more clear. NOTE: the MPLS-LDP-ATM-MIB 4922 module uses an index of the VP which can also take on the value of 4923 zero. A statement was added to this Index also. "REQ:- 4924 mplsXxxxROCompliance -> better mplsXxxxReadOnlyCompliance". RSP: 4925 done. 4927 5.4. Changes from 4929 The following changes are from the IESG MIB review. 4931 Changed "Label Switch Router" to "Label Switching Router". 4933 Spelling errors fixed (unlabelled, atttempt, subsytem). 4935 Changed some of the enums to start at 1, instead of zero: 4936 mplsLdpPeerLoopDetectionForPV and mplsLdpEntityOperStatus. 4938 Added REFERENCE clauses. 4940 Added a timestamp object for mplsLdpSesState changes. 4942 Changed NMS to command generator as defined in RFC2571. 4944 Added a lastChange objects: mplsLdpEntityLastChange and 4945 mplsLdpPeerLastChange. 4947 Added TEXTUAL-CONVENTIONS for MplsLabelDistributionMethod and 4948 MplsRetentionMode. These TCs have been incorporated into draft-ietf- 4949 mpls-tc-mib-04.txt. 4951 Divided up the one MIB MODULE into 3 additional modules for a total 4952 of 4 MIB MODULES: 1) mplsLdpMIB, 2) mplsLdpGenericMIB which includes 4953 objects pertaining to Ethernet as the L2, 3) mplsLdpAtmMIB which 4954 includes objects pertaining to ATM as the L2, and 4) 4955 mplsLdpFrameRelayMIB which includes objects pertaining to Frame Relay 4956 as the L2. 4958 Also, reduced the number of objects by creating the mplsLdpLspTable 4959 and removing the Mapping tables. 4961 In section 3.1 changed "where each row in the table initiates" to 4962 "where each row in the table represents". 4964 Updated Reference Section and divided them into Normative vs. 4965 Informative. 4967 Removed the MplsGenAddress TC and used the INET-ADDRESS-MIB's 4968 InetAddress TC. Objects using this TC are: 4969 mplsLdpEntityTargetPeerAddr, mplsFecAddr, and 4970 mplsLdpSesPeerNextHopAddr and are noted in the conformance statements 4971 supporting: unknown(0), ipv4(1), and ipv6(2). 4973 Removed AddressFamilyNumbers TC and used InetAddressType TC from the 4974 INET-ADDRESS-MIB. One of the MIB compilers as a warning because 4975 apparently one is expected to use InetAddressType and InetAddress 4976 together (although, think this restriction is too restrictive). Also, 4977 removed the reference for the Address Family Numbers MIB. 4979 Changed the name TargPeer to TargetPeer. 4981 Removed the Enable/Disable trap objects: 4982 mplsLdpEntityPVLMisTrapEnable, and mplsLdpSesUpDownTrapEnable. RFC 4983 2573 should be used to eable/disable traps. 4985 Removed the import for "transmission" and instead, imported "mplsMIB 4986 from the MPLS-TC-MIB". 4988 Changed mplsLdpEntityPVL to mplsLdpEntityPathVectorLimit and updated 4989 the DESCRIPTION clause. Also, the PVL abbreviation was expanded to 4990 PathVectorLimit for other objects. 4992 Combined the objects: mplsLdpPeerLoopDectionForPV and mplsLdpPeerPVL 4993 into one object: mplsLdpPeerPathVectorLimit and updated the 4994 DESCRIPTION clause. 4996 mplsLdpEntityTcpDscPort uses InetPortNumber TC from the INET-ADDRESS- 4997 MIB. Likewise, mplsLdpEntityUdpDscPort uses the InetPortNumber TC 4998 from the INET-ADDRESS-MIB. Also a REFERENCE clause was added. 5000 The mplsLdpEntityMaxPduLength object has the SYNTAX range changed to 5001 start at 256. Also the DESCRIPTION clause was updated. 5003 The mplsLdpSesMaxPduLen object's name was changed to 5004 mplsLdpSesMaxPduLength and a UNITS clause was added, and the 5005 DESCRIPTION clause was updated. This object is related to the 5006 mplsLdpEntityMaxPduLength object. 5008 The mplsLdpEntityKeepAliveHoldTimer and mplsLdpEntityHelloHoldTimer 5009 DESCRIPTION clause was changed from "The two octet value" to "The 5010 16-bit integer value". 5012 The mplsLdpEntityHelloHoldTimer object's DESCRIPTION clause was 5013 updated. 5015 A range of Integer32(0..100) was added to the SYNTAX clause of the 5016 mplsLdpEntityInitSesThreshold object. Also, the DESCRIPTION clause 5017 of this object was updated. 5019 The mplsLdpEntityOptionalParameters object was renamed to 5020 mplsLdpEntityLabelType. 5022 Updated the mplsLdpEntityAdminStatus and mplsLdpEntityRowStatus 5023 objects. RowStatus now reflects the status of the row, and Admin 5024 status controls enabling/disabling the entry. 5026 Updated the DESCRIPTION clauses for the objects in the 5027 mplsLdpEntityStatsTable to refer to the 5028 mplsLdpEntityDiscontinuityTime object. 5030 Changed StorType to StorageType. 5032 5.5. Changes from 5034 There were three types of changes: the first change was that all the 5035 MPLS Textual Conventions from this MIB, the LSR and MPLS-TE MIBs were 5036 moved into a new document [MPLSTCMIB], "draft-ietf-mpls-tc- 5037 mib-00.txt". The Textual Conventions are now IMPORTED from 5038 [MPLSTCMIB]. The second type of change was updates based on comments 5039 from the IESG. These changes will be discussed below. The third 5040 type of changes were based on minor editorial changes from the co- 5041 authors. 5043 The "Introduction" and "Structure of the MIB" sections were reworded 5044 since they were repetitive. 5046 The "Overview" was rearranged. 5048 References were added to "The LDP Entity ATM Objects" and "The LDP 5049 Entity Frame Relay Objects" Sections. 5051 The Working Group mailing list and Chairs were added to the CONTACT- 5052 INFO. 5054 Updated the DESCRIPTION clause for the "mplsLdpEntityLdpId" object. 5056 Updated the mplsLdpEntityProtocolVersion to include a range 5057 (1..65535). 5059 Updated the "References" Section. 5061 Running the MIB through the smilint MIB compiler showed that some 5062 object names were longer than 32 characters, these were shortened to 5063 32 characters or fewer. 5065 The following changes were from the co-authors. 5067 Other minor editorial changes such as fixing typographical errors, 5068 and removing MIB comments which are no longer meaningful. 5070 Page 17 (also page 46) the description was enhanced to describe the 5071 version field in the LDP header from RFC3036. 5073 Removed WellKnown from the tcp and upd port names. It's the ports 5074 that get set, and the default value is the well known (actually the 5075 registered) port number. 5077 mplsLdpEntityInitSesTrapEnable object is useless and was removed 5078 since setting mplsLdpEntityInitSesThreshold=0 acheives the same 5079 thing. Also removed it from the descriptive text in section 3. 5081 Page 47, mplsLdpSessionDiscontinuityTime The initial value of this 5082 was changed to be sysUpTime instead of zero. sysUpTime for when the 5083 session starts is more meaningful and was added to the Session 5084 Up/Down Traps also. Also, added the Session specific stats to the 5085 up/down traps. 5087 5.6. Changes from 5089 All changes were from the second last call which took place Thursday, 5090 July 20th, until Thursday, July 27th, 2000 and are described in the 5091 remainder of this section. 5093 Remove the reference to the MPLS framework document. 5095 Add an mplsFecIndexNext type of object. 5097 Change the conformance of the FEC table objects to be part of the 5098 mplsLdpGeneralGroup. 5100 The mplsLdpEntityConfGenericTable is no longer needed because the 5101 functionality has been absorbed by the 5102 mplsLdpEntityConfGenericLabelRangeTable. The 5103 mplsLdpEntityConfGenericTable has been removed and the front section 5104 was updated accordingly. 5106 Other editorial issues, updating references, typos and so forth. 5108 5.7. Changes from 5110 The majority of changes in this revision are based on Last Call 5111 comments which were received during the last call from Thursday, 5112 March 9, 2000 to Friday, March 17, 2000, or slightly thereafter. 5113 Also, changes were made to agree with the latest specifications. 5114 These changes are described in this section. 5116 Changes due to draft-ietf-mpls-ldp-07.txt and draft-ietf-mpls- 5117 ldp-08.txt. Specifically, removing references to IPv4/IP and using 5118 router id, as appropriate. 5120 Removed vpMerge and vpAndVcMerge choices from the object, 5121 mplsLdpEntityAtmMergeCap. VP Merge is not described in [RFC3036]. 5123 The LIB Table was removed and replaced by mapping tables to map LDP 5124 LSPs created by LDP sessions to the mplsInSegment, mplsOutSegment and 5125 mplsXC tables in the LSR MIB. The conformance section was updated 5126 to include a Mapping Group which is to be implemented iff these LSR 5127 MIB tables (mplsInSegmentTable, mplsOutSegmentTable and mplsXCTable) 5128 are implemented. 5130 The front section was updated to include information on the Generic 5131 label table. 5133 Added more in the front section on on Row 5134 Creation/adminStatus/OperStatus in the LDP Entity and related tables. 5136 Added a generic label range table. NOTE: there is NO corresponding 5137 LDP message which relates to the information in this table, however, 5138 this table does provide a way for a user to 'reserve' a generic label 5139 range. 5141 A new TEXTUAL-CONVENTION, MplsAtmVcIdentifier was added. This TC has 5142 the same upper bounds as AtmVcIdentifier (from rfc2514) except that 5143 the lower bound is 32 (and not 0). The lower bound is 32 since this 5144 value is specified by [RFC3035]. 5146 Removed the scalar object mplsLsrLabelRetentionMode and added 5147 mplsLdpEntityLabelRetentionMode. The change was made to allow 5148 configuring the retention mode on a per LDP Entity basis, as opposed 5149 for the entire LSR. 5151 Typo in section 3.5.2 was fixed. 5153 Typo in the mplsLdpSessionUp notification description was fixed. 5155 Section 'LDP Notifications' was expanded to cover both the 5156 'mplsLdpSessionUp' and 'mplsLdpSessionDown' traps. Also, the objects 5157 which enable and disable these traps have been described in this 5158 Section: 5160 The 'mplsLdpEntityHopCountLoopDetection' object and the 5161 'mplsLdpEntityHopCount' object have been combined into the new 5162 object, 'mplsLdpEntityHopCountLimit'. 5164 MplsLabel has been updated to reflect the VPI value of 12 bits and 5165 not 8. 5167 Added DEFVAL clause to the 'mplsLdpEntityWellKnownDiscoveryPort' 5168 object. The default value is 646. 5170 Added UNITS and DEFVAL clauses to the 'mplsLdpEntityMaxPduLength' 5171 object. The default value is 4096 and the units is octets. 5173 Added DEFVAL clause to 'mplsLdpEntityProtocolVersion' object. The 5174 default value is 1. 5176 Added DEFVAL clause to 'mplsLdpEntityKeepAliveHoldTimer' of 40 5177 seconds. 5179 Added DEFVAL clause to 'mplsLdpEntityInitSesThreshold' object. The 5180 default value is 8. 5182 The mplsLdpEntityWellKnownDiscoveryPort was changed into two objects, 5183 one for TCP and one for UDP. The names are 5185 Typo in the description for the 5187 The mplsLdpEntityPeerTable was (re-)named mplsLdpPeerTable. The 5188 mplsLdpSessionTable now AUGMENTs the mplsLdpPeerTable in order to 5189 show that these two tables are related. There has been wording added 5190 to the mplsLdpSessionEntry description and to the description for the 5191 mplsLdpPeerTable. 5193 5.8. Changes from 5195 Editorial changes, fixing typo's, fixing wrapping lines, etc. 5197 Updated references for latest drafts, and added [RFC3032] and 5198 [RFC3034] to Reference Section. 5200 Added to the Acknowledgements Section. 5202 Changed the SYNTAX and DESCRIPTION of the 5203 'mplsLdpLsrLoopDetectionCapable' object, so that it will also support 5204 the loop detection by hop count. 5206 Combined the 'mplsLdpEntityLoopDetectionForPV' and 'mplsLdpEntityPVL' 5207 objects. The functionality of the 'mplsLdpEntityLoopDectionForPV' is 5208 now denoted by the value of 0 (zero) in the 'mplsLdpEntityPVL' 5209 object. This results in one less object 5210 'mplsLdpEntityLoopDectionForPV' but does not sacrifice functionality. 5212 Changed 'mplsLdpLibLabelType' into two objects: 5213 'mplsLdpLibInLabelType' and differ from the egress label type. The 5214 MIB now reflects this. 5216 The following items were changed as a result of the Frame Relay Forum 5217 dropping support for 17-bit DLCIs: the MplsLabel TC description has 5218 been modified, and other Frame Relay Object descriptions were also 5219 modified (as specified in this section). 5221 The MplsLabel TC was also modified and reference 3. was added to the 5222 REFERENCE Clause. 5224 MplsLdpLabelTypes TC was modified to use an enum. 5226 InterfaceIndex support was added to the Entity information. This was 5227 specifically requested by several members of the working group. An 5228 additional table, mplsLdpEntityConfGenericTable as a way to configure 5229 Generic Labels, and an object, 'mplsLdpConfGenericIfIndexOrZero was 5230 added to map the InterfaceIndex used by Generic Labels. Objects were 5231 also added to the 'mplsLdpEntityAtmParmsTable' and the and 5232 'mplsLdpEntityFrIfIndex', respectively. 5234 Changed the name of the 'mplsLdpEntityMtu' object to be 5235 'mplsLdpEntityMaxPduLength' which is more consistent with the LDP 5236 Specification. Also, the description and SYNTAX were changed. 5238 Changed the SYNTAX of the 'mplsLdpSessionMaxPduLength' to unsigned32 5239 and changed the Range from (0..65535) to (1..65535). 5241 Added and improved the front section discussion on SNMP 5242 Notifications. 5244 Also, modified the DESCRIPTION clause of the 5246 Added objects to enable/disable the sending of traps: 5248 Added an object to enable/disable sending traps for Sessions changing 5249 from Up to Down, or Down to Up. 5251 Added notifications to generate traps from session changing from Up 5252 to Down, or Down to up. 5254 Added a StorageType object to the Entity and associated tables which 5255 are configurable. 5257 Added a Discontinuity Time object to the Entity Table, 5259 Added discussion on row creation in the Entity and other associated 5260 Entity tables. This is a new Section in the Front part of the 5261 document called: 5263 Removed the 'mplsLdpEntityControlMethod'. 5265 Made 'mplsLdpFecLspId' as part of the INDEX for the FEC table. This 5266 is to allow FECs to map to multiple LSPs. Also add a RowPointer to a 5267 row in the Session Table. 5269 Added an operation status object, 'mplsLdpLspOperStatus' and a last 5270 Change object, 'mplsLdpLspLastChangeto the LIB Table. This will be 5271 used to detect whether an LSP has changed its status. 5273 Changed the name of the mplsLdpPeerTable to the 5274 mplsLdpEntityPeerTable. This table contains information relevant to 5275 Peers which are known to specific Entities. The indexing of this 5276 table has also changed to include the Row in the Entity Table that 5277 this Peer is known by. The mplsLdpHelloAdjacencyTable and the 5278 mplsLdpSessionTable have been moved under this table. Since Hello 5279 Adjacencies are related to Entity-Peer information and Sessions are 5280 related to Entity-Peer information this was seen as a comprehensive 5281 and coherent modelling. Associated descriptions in the front section 5282 and in the tables have been changed to reflect this change. 5284 Moved the 'mplsLdpConfFrLen' object from the 5285 'mplsLdpEntityConfFrLabelRangeTable' to the 5286 'mplsLdpEntityFrameRelayParmsTable' since the Frame Relay 5287 interface/port can only use one header length at a time, i.e. a 5288 specific FR interface supports one address length for all VCs on that 5289 interface. Also, changed the object so that it only supports 10 and 5290 23 bit DLCI lengths. (The 17 bit length was dropped by the Frame 5291 Relay Forum and thus, is no longer required.) The name of this 5292 object was changed from 'mplsLdpConfFrLen' to 'mplsLdpEntityFrLen' to 5293 fit in with the 'mplsLdpEntityFrameRelayParmsTable'. 5295 Removed the seventeenDlciBits(1) value from the mplsLdpFrSessionLen 5296 object. (The 17 bit length was dropped by the Frame Relay Forum and 5297 thus, is no longer required.) 5299 Corrected the range of the 'mplsLdpEntityIndexNext' object to include 5300 0 (zero). 5302 5.9. Changes from 5304 Reworded the description of the mplsLdpAtmSessionTable to clarify 5305 that one or MORE label range intersection(s) is/are represented in 5306 this table. 5308 Reworded the description of the mplsLdpFrameRelaySessionTable to 5309 clarify that one or MORE label range intersection(s) is/are 5310 represented in this table. 5312 Added a new index, mplsLdpSessionPeerIndex, to the 5313 mplsLdpSessionPeerAddressTable. This new index uniquely identifies 5314 the entry within a given session. (Since adding 5315 mplsLdpSessionPeerNextHopAddressType, 5316 mplsLdpSessionPeerNextHopAddress to the INDEX clause of the 5317 mplsLdpSessionPeerAddressTable leaves a table with only indices and 5318 no objects, the work around was to add a new index which uniquely 5319 differentiates an entry within a given session.) 5321 Quite a few changes to the mplsLdpPeerTable. First, removed the 5322 mplsLdpPeerIndex from the mplsLdpPeerTable and other tables. This 5323 index served no purpose, so was removed. Second, removed the 5324 objects: mplsLdpPeerInternetworkAddrType, and 5325 mplsLdpPeerInternetworkAddr. Third, reworded the description of this 5326 table to include information which is known during Session 5327 Intialization attempts, the specific information has to do with Loop 5328 Dection based on Path Vectors. Since Section 3.5.3 of the LDP Spec 5329 when describing the PVLim says: "Although knowledge of a peer's path 5330 vector limit will not change an LSR's behavior, it does enable the 5331 LSR to alert an operator to a possible misconfiguration." and the 5332 object mplsLdpPeerPVL is sent as a varbind in the mplsLdpPVLMismatch 5333 notification. 5335 Removed the mplsLdpPeerIndex from the mplsLdpHelloAdjacencyTable. 5337 Removed the "IANA Address Family Numbers" MIB section. 5339 Updated the boiler.me from the ops web page dated Weds., Dec 22, 5340 1999. 5342 Updated the Security Section from the ops web page. 5344 Added the following objects to the mplsLdpEntityTable: 5345 mplsLdpEntityControlMethod, mplsLdpEntityLoopDectionForPV, and 5346 mplsLdpEntityPathVectorLimit. 5348 Removed mplsLdpSessionLabelAdvertisement, 5349 mplsLdpSessionLoopDetectionForPV, and mplsLdpSessionPathVectorLimit 5350 from the mplsLdpSessionTable. 5352 Changed the mplsLdpPathVectorLimitMismatch Notification to send 5353 mplsLdpEntityPathVectorLimit (instead of 5354 mplsLdpSessionPathVectorLimit). 5356 Copied the MplsLabel TC from draft-ietf-mpls-lsr-mib-00.txt and 5357 replaced the MplsLdpGenAddr for mplsLdpLibInLabel and 5358 mplsLdpLibOutLabel with MplsLabel. 5360 The mplsLdpSessionIndex was removed throughout the MIB. This was 5361 replaced by the object mplsLdpSessionDiscontinuityTime. The 5362 motivation was to reduce the number of indices. 5364 The descriptions for the objects in the mplsLdpSessionStatsTable, 5365 mplsLdpSessionStatsUnknownMessageTypeErrors and 5366 mplsLdpSessionStatsUnknownTlvErrors, have been updated to include a 5367 reference to the mplsLdpSessionDiscontinuityTime object. 5369 5.10. Changes from 5371 Added Scalar Objects: mplsLdpLsrLoopDetectionPresent, and 5372 mplsLdpEntityIndexNext. 5374 Added the following objects to the mplsLdpEntityTable: 5375 mplsLdpEntityProtocolVersion, mplsLdpEntityAdminStatus, 5376 mplsLdpEntityOperStatus, mplsLdpEntityTargetedPeer, 5377 mplsLdpEntityTargetedPeerAddrType, mplsLdpEntityTargetedPeerAddr, and 5378 mplsLdpEntityHelloHoldTimer. 5380 Changed the description of the mplsLdpEntityAtmParmsTable and added 5381 the following objects to this table: mplsLdpEntityAtmLsrConnectivity, 5382 mplsLdpEntityDefaultControlVpi, mplsLdpEntityDefaultControlVci, 5383 mplsLdpEntityUnlabTrafVpi, and mplsLdpEntityUnlabTrafVci. NOTE: the 5384 last four objects were in Version 01 of the MIB but were mistakenly 5385 omitted from Version 02. Now, they are back. 5387 Changed the indexing of the mplsLdpEntityConfAtmLabelRangeTable to 5388 include the minimum VPI/VCI. This is to ensure that indices in this 5389 table are unique. 5391 Changed the indexing of the mplsLdpEntityConfFrLabelRangeTable, to 5392 include the minimum DLCI value. This is to ensure that indices in 5393 this table are unique. 5395 Added [RFC3036] to Reference Section. 5397 5.11. Changes from 5399 The MIB was updated to correspond to draft-ietf-mpls-ldp-06.txt of 5400 the LDP Specification [RFC3036]. 5402 The front section was updated. 5404 The MIB was made to be less ATM-centric. Essentially, the ATM 5405 specific objects where removed from the tables and placed in ATM 5406 specific Tables. A type was added to the base tables and a row is to 5407 be created in the ATM/FR/etc. type table. Apropos compliance 5408 statements were added to reflect the separation of ATM and Frame 5409 Relay objects into their respective tables. 5411 Objects for Loop Detection were removed from describing the LDP 5412 implementation (i.e. the scalars were removed) and Loop Dection 5413 objects were added to the Session Table. (Although as the LDP 5414 Specification indicates loop detection should be for an LSR within a 5415 domain.) 5417 The following tables were added: mplsLdpEntityAtmParmsTable, 5418 mplsLdpEntityConfAtmLabelRangeTable, mplsLdpFrameRelayParmsTable, 5419 mplsLdpConfFrLabelRangeTable, mplsLdpAtmSessionTable, 5420 mplsLdpFrameRelaySessionTable, mplsLdpSessionPeerAddressTable, 5421 mplsLdpLibTable, and the mplsLdpFecTable. 5423 The following notifications were added: notification for Session 5424 removal. 5426 The following objects were removed from the Session Table: 5427 mplsLdpSessionRole was removed (this can be determined by comparing 5428 LSR Ids and does not need to be explicitly in the MIB.) ATM specific 5429 objects (mplsLdpSessionAtmLabelRangeLowerBoundVpi 5430 mplsLdpSessionAtmLabelRangeLowerBoundVci, 5431 mplsLdpSessionAtmLabelRangeUpperBoundVpi 5432 mplsLdpSessionAtmLabelRangeUpperBoundVci) were removed and put into a 5433 separate table. Frame Relay objects were added in a separate table. 5435 Hello Adjacency Table was updated. 5437 The objects, mplsLdpSessionRejectedParamErrors, 5438 mplsLdpSessionRejectedNoHelloErrors, mplsLdpBadLdpIdentifierErrors, 5439 mplsLdpBadPduLengthErrors, mplsLdpBadMessageLengthErrors, 5440 mplsLdpBadTlvLengthErrors, mplsLdpMalformedTlvValueErrors, 5441 mplsLdpKeepAliveTimerExpiredErrors, mplsLdpShutdownNotifReceived, and 5442 mplsLdpShutdownNotifSent were added to the mplsLdpEntityStatsTable. 5444 The mplsLdpSessionStatsTable was added to count statics based on a 5445 per Session basis. 5447 The mplLdpPeerConfAtmLabelRangeTable has been removed. There is no 5448 need to configure information for a Peer. All information for a peer 5449 is learned, thus peer information is read-only. 5451 (Editorial) References were updated to reflect the documents which 5452 this version was based on. 5454 5.12. Changes from 5456 Textual conventions were added for the LSR Identifier and the LDP 5457 Identifier. 5459 Top-level mib structure was added. The LDP MIB falls under a proposed 5460 hierarchy of mpls.mplsProtocols. 5462 The mib hierarchy within the LDP MIB was also changed. A new branch, 5463 under mpls.mplsProtocols.mplsLdpMIB.mplsLdpObjects was added. This 5464 branch is mplsLdpLsrObjects. Currently, this contains several new 5465 scalar objects: mplsLdpLsrID, mplsLdpLsrLoopDetectionPresent, 5466 mplsLdpLsrLoopDetectinAdminStatus, mplsLdpLsrPathVectorLimit, 5467 mplsLdpLsrHopCountLimit, mplsLdpLsrLoopPreventionPresent, 5468 mplsLdpLsrLoopPreventionAdminStatus, and 5469 mplsLdpLsrLabelRetentionMode. 5471 mplsLdpEntityTable is now indexed by mplsLdpEntityIdentifier, which 5472 is the LDP Identifier used in Session establishment. 5473 mplsLdpEntityLoopDetection and mplsLdpEntityLoopPrevention objects 5474 were removed from this table. 5476 The following objects were added to the mplsLdpEntityTable: 5477 mplsLdpEntityLabelSpaceType, mplsLdpEntityUnlabTrafVpi, 5478 mplsLdpEntityUnlabTrafVci, mplsLdpEntityMergeCapability, 5479 mplsLdpEntityVcDirectionality, and 5480 mplsLdpEntityLabelDistributionMethod. 5482 The following objects were added to the mplsLdpPeerEntityTable: 5483 mplsLdpPeerLabelDistributionMethod. 5485 The following object was removed from the mplsLdpEntityStatsTable: 5486 mplsLdpEntityEstablishedSessions. 5488 References were added and revised. 5490 6. Acknowledgments 5492 This document is a product of the MPLS Working Group. The authors 5493 would like to thank Mike MacFadden and Adrian Farrel for their 5494 helpful comments on several reviews. Also, the authors would like to 5495 give a special acknowledgement to Bert Wijnen for his many detailed 5496 reviews. Bert's assistance and guidance is greatly appreciated. 5498 We would also like to thank Cheenu Srinivasan, Arun Viswanathan and 5499 Thomas D. Nadeau, the authors of the MPLS-LSR-STD-MIB [LSRMIB], for 5500 their assistance. 5502 Additionally, there have been other members of the working group that 5503 have been very helpful: Alan Kullberg from NetPlane Systems gave 5504 input on earlier versions of this document, and more recently, Riza 5505 Cetin of Alcatel and Neil Jerram of Data Connection who both provided 5506 MIB objects. 5508 Early versions of this document were also reviewed by colleagues at 5509 Nortel Networks and Ericsson. The authors would like to thank the 5510 following people: Leigh McLellan, Geetha Brown, Geping Chen and 5511 Charlan Zhou from Nortel Networks, and Zoltan Takacs and Bo 5512 Augustsson from Ericsson. 5514 7. Normative References 5516 [RFC2115] Brown, C., and F. Baker, "Management Information Base for 5517 Frame Relay DTEs Using SMIv2", RFC 2115, September 1997. 5519 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 5520 Requirement Levels", BCP 14, RFC 2119, Harvard University, 5521 March 1997 5523 [RFC2514] Noto, M., E. Spiegel, K. Tesink, editors, "Definition of 5524 Textual Conventions and OBJECT-IDENTITIES for ATM 5525 Management", RFC 2514, February 1999. 5527 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 5528 Rose, M. and S. Waldbusser, "Structure of Management 5529 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 5530 1999. 5532 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 5533 Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", 5534 STD 58, RFC 2579, April 1999. 5536 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 5537 Rose, M. and S. Waldbusser, "Conformance Statements for 5538 SMIv2", STD 58, RFC 2580, April 1999. 5540 [RFC2863] McCloghrie, K., F. Kastenholz, "The Interfaces Group MIB 5541 using SMIv2", RFC 2863, June 2000. 5543 [RFC3031] Rosen, E., Viswananthan, A., and R. Callon, "Multiprotocol 5544 Label Switching Architecture", RFC 3031, January 2001. 5546 [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., Farinacci, 5547 D., Li, T. and A. Conta, "MPLS Label Stack Encoding", RFC 5548 3032, January 2001. 5550 [RFC3034] Conta, A., Doolan, P., and A. Malis, "Use of Label Switching 5551 on Frame Relay Networks Specification", RFC 3034, January 5552 2001. 5554 [RFC3035] Davie, B., Lawrence, J., McCloghrie, K., Rosen, E., Swallow, 5555 G., Rekhter, Y. and P. Doolan, "MPLS using LDP and ATM VC 5556 Switching", RFC 3035, January 2001. 5558 [RFC3036] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and B. 5559 Thomas, "LDP Specification", RFC 3036, January 2001. 5561 [RFC3037] Thomas, B. and E. Gray, "LDP Applicability", RFC 3037, 5562 January 2001. 5564 [RFC3215] Boscher, C., Cheval, P., Wu L. and E. Gray, "LDP State 5565 Machine", RFC 3215, January 2002. 5567 [RFC3289] Baker, F., Chan, K. and A. Smith, "Management Information 5568 Base for the Differentiated Services Architecture", RFC 5569 3289, May 2002. 5571 [RFC3291] Daniele, M., Haberman, B., Routhier, S. and J. 5572 Schoenwaelder, "Textual Coventions for Internet Network 5573 Addresses", RFC 3291, May 2002. 5575 [LSRMIB] Srinivansan, C., Viswanathan, A., and T. Nadeau "MPLS Label 5576 Switching Router Management Information Base Using SMIv2", 5577 draft-ietf-mpls-lsr-mib-11.txt, June 2003. 5579 [MPLSTCMIB] Nadeau, T., J. Cucchiara, (Eds.) "Definitions of Textual 5580 Conventions for Multiprotocol Label Switching Management", 5581 draft-ietf-mpls-tc-mib-08.txt, June 2003. 5583 8. Informative References 5585 [RFC2026] S. Bradner, "The Internet Standards Process -- Revision 3", 5586 RFC 2026, October 1996. 5588 [RFC2684] Grossman, D., and J. Heinanen, "Multiprotocol Encapsulation 5589 over ATM Adaptation Layer 5", RFC 2684, September 1999. 5591 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 5592 "Introduction and Applicability Statements for Internet- 5593 Standard Management Framework", RFC 3410, December 2002. 5595 [MPLSMGMT] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol 5596 Label Switching (MPLS) Management Overview", draft-ietf- 5597 mpls-mgmt-overview-06.txt, June 2003. 5599 9. Security Considerations 5601 This Security Considerations section consists of 4 subsections, one 5602 for each of the MIB Modules in this document. 5604 9.1. Security Considerations for MPLS-LDP-STD-MIB 5606 There are a number of management objects defined in this MIB module 5607 with a MAX-ACCESS clause of read-write and/or read-create. Such 5608 objects may be considered sensitive or vulnerable in some network 5609 environments. The support for SET operations in a non-secure 5610 environment without proper protection can have a negative effect on 5611 network operations. These are the tables and objects and their 5612 sensitivity/vulnerability: 5614 o the mplsLdpEntityTable contains objects to provision potential 5615 LDP sessions on the Label Switching Router (LSR) or Label Edge 5616 Router (LER). The mplsLdpLspFecTable contains objects which 5617 associate an LSP with a FEC. Unauthorized access to objects in 5618 these tables, could result in disruption of traffic on the 5619 network. This is especially true if an LDP session has been 5620 established. The use of stronger mechanisms such as SNMPv3 5621 security should be considered where possible. Specifically, 5622 SNMPv3 VACM and USM MUST be used with any v3 agent which 5623 implements this MIB. Administrators should consider whether 5624 read access to these objects should be allowed, since read 5625 access may be undesirable under certain circumstances. 5627 Some of the readable objects in this MIB module i.e., "objects with a 5628 MAX-ACCESS other than not-accessible", may be considered sensitive or 5629 vulnerable in some network environments. It is thus important to 5630 control even GET and/or NOTIFY access to these objects and possibly 5631 to even encrypt the values of these objects when sending them over 5632 the network via SNMP. These are the tables and objects and their 5633 sensitivity/vulnerability: 5635 o the mplsLdpEntityTable, mplsLdpPeerTable, mplsLdpSesTable and 5636 mplsLdpSesStatsTable collectively show the LDP LSP network 5637 topology. If an Administrator does not want to reveal the LDP 5638 LSP topology of the network, then these tables should be 5639 considered sensitive/vulnerable. 5641 9.2. Security Considerations for MPLS-LDP-ATM-STD-MIB 5643 There are a number of management objects defined in this MIB module 5644 with a MAX-ACCESS clause of read-write and/or read-create. Such 5645 objects may be considered sensitive or vulnerable in some network 5646 environments. The support for SET operations in a non-secure 5647 environment without proper protection can have a negative effect on 5648 network operations. These are the tables and objects and their 5649 sensitivity/vulnerability: 5651 o the mplsLdpEntityAtmTable and mplsLdpEntityAtmLRTable contain 5652 objects to provision potential LDP sessions on the Label 5653 Switching Router (LSR) or Label Edge Router (LER) over Layer 2 5654 of ATM. These tables extend the mplsLdpEntityTable in the MPLS- 5655 LDP-MIB. Unauthorized access to objects in these tables, could 5656 result in disruption of traffic on the network. This is 5657 especially true if an LDP session has been established. The use 5658 of stronger mechanisms such as SNMPv3 security should be 5659 considered where possible. Specifically, SNMPv3 VACM and USM 5660 MUST be used with any v3 agent which implements this MIB. 5661 Administrators should consider whether read access to these 5662 objects should be allowed, since read access may be undesirable 5663 under certain circumstances. 5665 Some of the readable objects in this MIB module i.e., "objects with a 5666 MAX-ACCESS other than not-accessible", may be considered sensitive or 5667 vulnerable in some network environments. It is thus important to 5668 control even GET and/or NOTIFY access to these objects and possibly 5669 to even encrypt the values of these objects when sending them over 5670 the network via SNMP. These are the tables and objects and their 5671 sensitivity/vulnerability: 5673 o the mplsLdpEntityAtmTable and mplsLdpEntityAtmLRTable show the 5674 Label Ranges for ATM. If an Administrator does not want to 5675 reveal this information then these tables should be considered 5676 sensitive/vulnerable and treated accordingly. 5678 9.3. Security Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB 5680 There are a number of management objects defined in this MIB module 5681 with a MAX-ACCESS clause of read-write and/or read-create. Such 5682 objects may be considered sensitive or vulnerable in some network 5683 environments. The support for SET operations in a non-secure 5684 environment without proper protection can have a negative effect on 5685 network operations. These are the tables and objects and their 5686 sensitivity/vulnerability: 5688 o the mplsLdpEntityFrameRelayTable and 5689 mplsLdpEntityFrameRelayLRTable contain objects to provision 5690 potential LDP sessions on the Label Switching Router (LSR) or 5691 Label Edge Router (LER) over Layer 2 of Frame Relay. These 5692 tables extend the mplsLdpEntityTable in the MPLS-LDP-MIB. 5693 Unauthorized access to objects in these tables, could result in 5694 disruption of traffic on the network. This is especially true 5695 if an LDP session has been established. The use of stronger 5696 mechanisms such as SNMPv3 security should be considered where 5697 possible. Specifically, SNMPv3 VACM and USM MUST be used with 5698 any v3 agent which implements this MIB. Administrators should 5699 consider whether read access to these objects should be allowed, 5700 since read access may be undesirable under certain 5701 circumstances. 5703 Some of the readable objects in this MIB module i.e., "objects with a 5704 MAX-ACCESS other than not-accessible", may be considered sensitive or 5705 vulnerable in some network environments. It is thus important to 5706 control even GET and/or NOTIFY access to these objects and possibly 5707 to even encrypt the values of these objects when sending them over 5708 the network via SNMP. These are the tables and objects and their 5709 sensitivity/vulnerability: 5711 o the mplsLdpEntityFrameRelayTable and 5712 mplsLdpEntityFrameRelayLRTable show the Label Ranges for Frame 5713 Relay. If an Administrator does not want to reveal this 5714 information then these tables should be considered 5715 sensitive/vulnerable and treated accordingly. 5717 9.4. Security Considerations for MPLS-LDP-GENERIC-STD-MIB 5719 There are a number of management objects defined in this MIB module 5720 with a MAX-ACCESS clause of read-write and/or read-create. Such 5721 objects may be considered sensitive or vulnerable in some network 5722 environments. The support for SET operations in a non-secure 5723 environment without proper protection can have a negative effect on 5724 network operations. These are the tables and objects and their 5725 sensitivity/vulnerability: 5727 o the mplsLdpEntityGenericLRTable contains objects to provision 5728 potential LDP sessions on the Label Switching Router (LSR) or 5729 Label Edge Router (LER) over Layer 2 of Ethernet. This table 5730 extends the mplsLdpEntityTable in the MPLS-LDP-MIB. 5731 Unauthorized access to objects in these tables, could result in 5732 disruption of traffic on the network. This is especially true 5733 if an LDP session has been established. The use of stronger 5734 mechanisms such as SNMPv3 security should be considered where 5735 possible. Specifically, SNMPv3 VACM and USM MUST be used with 5736 any v3 agent which implements this MIB. Administrators should 5737 consider whether read access to these objects should be allowed, 5738 since read access may be undesirable under certain 5739 circumstances. 5741 Some of the readable objects in this MIB module i.e., "objects with a 5742 MAX-ACCESS other than not-accessible", may be considered sensitive or 5743 vulnerable in some network environments. It is thus important to 5744 control even GET and/or NOTIFY access to these objects and possibly 5745 to even encrypt the values of these objects when sending them over 5746 the network via SNMP. These are the tables and objects and their 5747 sensitivity/vulnerability: 5749 o the mplsLdpEntityGenericLRTable shows the Label Ranges for 5750 ethernet. If an Administrator does not want to reveal this 5751 information then these tables should be considered 5752 sensitive/vulnerable and treated accordingly. 5754 9.5. Additional Security Considerations 5756 The following paragraphs describe additional security considerations 5757 which are applicable to all 4 of the MIB Modules in this document. 5759 SNMP versions prior to SNMPv3 did not include adequate security. 5760 Even if the network itself is secure "for example by using IPSec", 5761 even then, there is no control as to who on the secure network is 5762 allowed to access and GET/SET "read/change/create/delete" the objects 5763 in this MIB module. 5765 It is RECOMMENDED that implementers consider the security features as 5766 provided by the SNMPv3 framework "see [RFC3410], section 8", 5767 including full support for the SNMPv3 cryptographic mechanisms "for 5768 authentication and privacy". 5770 Further, deployment of SNMP versions prior to SNMPv3 is NOT 5771 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 5772 enable cryptographic security. It is then a customer/operator 5773 responsibility to ensure that the SNMP entity giving access to an 5774 instance of this MIB module, is properly configured to give access to 5775 the objects only to those principals "users" that have legitimate 5776 rights to indeed GET or SET "change/create/delete" them. 5778 10. IANA Considerations 5780 As described in [MPLSMGMT] and as requested in the MPLS-TC-STD-MIB 5781 [MPLSTCMIB], MPLS related standards track MIB modules should be 5782 rooted under the mplsStdMIB subtree. There are 4 MPLS MIB Modules 5783 contained in this document, each of the following "IANA 5784 Considerations" subsections requests IANA for a new assignment under 5785 the mplsStdMIB subtree. New assignments can only be made via a 5786 Standards Action as specified in [RFC2434]. 5788 10.1. IANA Considerations for MPLS-LDP-STD-MIB 5790 The IANA is requested to assign { mplsStdMIB 4 } to the MPLS-LDP-STD- 5791 MIB module specified in this document. 5793 10.2. IANA Considerations for MPLS-LDP-ATM-STD-MIB 5795 The IANA is requested to assign { mplsStdMIB 5 } to the MPLS-LDP-ATM- 5796 STD-MIB module specified in this document. 5798 10.3. IANA Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB 5800 The IANA is requested to assign { mplsStdMIB 6 } to the MPLS-LDP- 5801 FRAME-RELAY-STD-MIB module specified in this document. 5803 10.4. IANA Considerations for MPLS-LDP-GENERIC-STD-MIB 5805 The IANA is requested to assign { mplsStdMIB 7 } to the MPLS-LDP- 5806 GENERIC-STD-MIB module specified in this document. 5808 11. Intellectual Property Notice 5810 The IETF takes no position regarding the validity or scope of any 5811 intellectual property or other rights that might be claimed to 5812 pertain to the implementation or use of the technology described in 5813 this document or the extent to which any license under such rights 5814 might or might not be available; neither does it represent that it 5815 has made any effort to identify any such rights. Information on the 5816 IETF's procedures with respect to rights in standards-track and 5817 standards-related documentation can be found in BCP-11 [RFC2028]. 5818 Copies of claims of rights made available for publication and any 5819 assurances of licenses to be made available, or the result of an 5820 attempt made to obtain a general license or permission for the use of 5821 such proprietary rights by implementors or users of this 5822 specification can be obtained from the IETF Secretariat. 5824 The IETF invites any interested party to bring to its attention any 5825 copyrights, patents or patent applications, or other proprietary 5826 rights that may cover technology that may be required to practice 5827 this standard. Please address the information to the IETF Executive 5828 Director. 5830 12. Authors' Addresses 5832 James V. Luciani 5833 Consultant 5834 PO Box 1010 5835 Concord, MA 01742 5836 USA 5837 Email: james_luciani@mindspring.com 5839 Hans Sjostrand 5840 ipUnplugged 5841 P.O. Box 101 60 5842 S-121 28 Stockholm, Sweden 5843 Phone: +46 8 725 5930 5844 Email: hans@ipunplugged.com 5845 Joan Cucchiara 5846 Artel 5847 237 Cedar Hill Street 5848 Marlborough, MA 01752 5849 Phone: +1-508-303-8200 x302 5850 Email: jcucchiara@artel.com 5852 13. Full Copyright Statement 5854 Copyright (C) The Internet Society (2003). All Rights Reserved. 5856 This document and translations of it may be copied and furnished to 5857 others, and derivative works that comment on or otherwise explain it 5858 or assist in its implementation may be prepared, copied, published 5859 and distributed, in whole or in part, without restriction of any 5860 kind, provided that the above copyright notice and this paragraph are 5861 included on all such copies and derivative works. However, this 5862 document itself may not be modified in any way, such as by removing 5863 the copyright notice or references to the Internet Society or other 5864 Internet organizations, except as needed for the purpose of 5865 developing Internet standards in which case the procedures for 5866 copyrights defined in the Internet Standards process must be 5867 followed, or as required to translate it into languages other than 5868 English. 5870 The limited permissions granted above are perpetual and will not be 5871 revoked by the Internet Society or its successors or assigns. 5873 This document and the information contained herein is provided on an 5874 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 5875 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 5876 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 5877 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 5878 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.