idnits 2.17.1 draft-ietf-mpls-ldp-mib-14.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 3453 has weird spacing: '...erlying media...' == Line 4574 has weird spacing: '...ibed in detai...' == Line 4783 has weird spacing: '...entence s/ini...' == Line 5349 has weird spacing: '... (Since addin...' == Line 5903 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 (November 2003) is 7467 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 4705, but not defined ** Obsolete undefined reference: RFC 2573 (Obsoleted by RFC 3413) == Missing Reference: 'RFC2434' is mentioned on line 5825, but not defined ** Obsolete undefined reference: RFC 2434 (Obsoleted by RFC 5226) == Unused Reference: 'RFC2115' is defined on line 5552, but no explicit reference was found in the text == Unused Reference: 'RFC2514' is defined on line 5559, but no explicit reference was found in the text == Unused Reference: 'RFC3037' is defined on line 5597, but no explicit reference was found in the text == Unused Reference: 'RFC3215' is defined on line 5600, but no explicit reference was found in the text == Unused Reference: 'RFC3289' is defined on line 5603, but no explicit reference was found in the text == Unused Reference: 'RFC3291' is defined on line 5607, but no explicit reference was found in the text == Unused Reference: 'RFC2026' is defined on line 5624, 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-12 == Outdated reference: A later version (-10) exists of draft-ietf-mpls-tc-mib-09 == Outdated reference: A later version (-09) exists of draft-ietf-mpls-mgmt-overview-08 Summary: 8 errors (**), 0 flaws (~~), 20 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Cucchiara 3 Internet-Draft Artel 4 Expires February 2004 H. Sjostrand 5 IP Unplugged 6 J. Luciani 7 Marconi 8 November 2003 10 Definitions of Managed Objects for 11 the Multiprotocol Label Switching, Label Distribution Protocol (LDP) 13 15 Status of this Memo 17 This document is an Internet-Draft and is in full conformance with 18 all provisions of Section 10 of RFC 2026. Internet-Drafts are 19 working documents of the Internet Engineering Task Force (IETF), its 20 areas, and its working groups. Note that other groups may also 21 distribute working documents as Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress". 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html 34 Distribution of this document is unlimited. Please send comments to 35 the Multiprotocol Label Switching (mpls) Working Group, mpls@uu.net. 37 Copyright Notice 39 Copyright (C) The Internet Society (2003). All Rights Reserved. 41 Abstract 43 This memo defines a portion of the Management Information Base (MIB) 44 for use with network management protocols in the Internet community. 45 In particular, it describes managed objects for the Multiprotocol 46 Label Switching, Label Distribution Protocol (LDP). 48 Table of Contents 50 1 Introduction ................................................. 4 51 2 The Internet-Standard Management Framework ................... 4 52 3 Structure of the MIB Modules ................................. 5 53 3.1 Overview ................................................... 5 54 3.2 Future Considerations ...................................... 5 55 3.3 Interface Indexing ......................................... 6 56 3.4 Differences from the LDP Specification ..................... 6 57 3.5 The MPLS-LDP-STD-MIB Module ................................ 7 58 3.5.1 LDP Scalar Objects ....................................... 7 59 3.5.2 The LDP Entity Table ..................................... 7 60 3.5.2.1 Changing Values After Session Establishment ............ 8 61 3.5.3 The LDP Entity Statistics Table .......................... 9 62 3.5.4 The LDP Peer Table ....................................... 9 63 3.5.5 The LDP Session Table .................................... 10 64 3.5.6 The LDP Session Statistics Table ......................... 10 65 3.5.7 The LDP Hello Adjacency Table ............................ 10 66 3.5.8 The LDP LSP Table ........................................ 10 67 3.5.9 The FEC Table ............................................ 11 68 3.5.10 The LDP Session Peer Address Table ...................... 11 69 3.6 LDP Notifications .......................................... 11 70 3.7 LDP Notification Frequency ................................. 12 71 4 MPLS Label Distribution Protocol MIB Definitions ............. 12 72 4.1 The MPLS-LDP-ATM-STD-MIB Module ............................ 66 73 4.1.1 The LDP Entity ATM Table ................................. 66 74 4.1.2 The LDP Entity ATM Label Range Table ..................... 66 75 4.1.3 The LDP ATM Session Table ................................ 66 76 4.2 The MPLS-LDP-FRAME-RELAY-STD-MIB Module .................... 83 77 4.2.1 The LDP Entity Frame Relay Table ......................... 83 78 4.2.2 The LDP Entity Frame Relay Label Range Table ............. 84 79 4.2.3 The LDP Frame Relay Session Table ........................ 84 80 4.3 The MPLS-LDP-GENERIC-STD-MIB Module ........................ 98 81 5 Revision History ............................................. 107 82 5.1 Changes from .............. 107 83 5.2 Changes from .............. 107 84 5.3 Changes from .............. 107 85 5.4 Changes from .............. 108 86 5.5 Changes from .............. 108 87 5.5.1 Changes based on MIB Doctor Review Comments .............. 108 88 5.6 Changes from .............. 113 89 5.7 Changes from .............. 115 90 5.8 Changes from .............. 116 91 5.9 Changes from .............. 117 92 5.10 Changes from ............. 119 93 5.11 Changes from ............. 121 94 5.12 Changes from ............. 122 95 5.13 Changes from ............. 123 96 5.14 Changes from ............. 124 97 6 Acknowledgments .............................................. 125 98 7 Normative References ......................................... 127 99 8 Informative References ....................................... 129 100 9 Security Considerations ...................................... 129 101 9.1 Security Considerations for MPLS-LDP-STD-MIB ............... 129 102 9.2 Security Considerations for MPLS-LDP-ATM-STD-MIB ........... 130 103 9.3 Security Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB ... 131 104 9.4 Security Considerations for MPLS-LDP-GENERIC-STD-MIB ....... 132 105 9.5 Additional Security Considerations ......................... 132 106 10 IANA Considerations ......................................... 133 107 10.1 IANA Considerations for MPLS-LDP-STD-MIB .................. 133 108 10.2 IANA Considerations for MPLS-LDP-ATM-STD-MIB .............. 133 109 10.3 IANA Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB ...... 133 110 10.4 IANA Considerations for MPLS-LDP-GENERIC-STD-MIB .......... 134 111 11 Intellectual Property Notice ................................ 134 112 12 Authors' Addresses .......................................... 134 113 13 Full Copyright Statement .................................... 135 115 1. Introduction 117 This document defines 4 MIB Modules which together support the 118 configuration and monitoring of the Label Distribution Protocol 119 (LDP). The Label Distribution Protocol (LDP) [RFC3036] is one type 120 of Multiprotocol Label Switching (MPLS) protocols described in 121 [RFC3031] and [RFC3032]. Utilizing all 4 MIB Modules allows an 122 operator to configure LDP sessions using 3 different Layer 2 media. 123 The Layer 2 media supported by the MIB Modules are Ethernet, ATM and 124 Frame Relay as described in [RFC3036], [RFC3034] and [RFC3035]. 126 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 127 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 128 document are to be interpreted as described in RFC 2119 [RFC2119]. 130 2. The Internet-Standard Management Framework 132 For a detailed overview of the documents that describe the current 133 Internet-Standard Management Framework, please refer to section 7 of 134 RFC 3410 [RFC3410]. 136 Managed objects are accessed via a virtual information store, termed 137 the Management Information Base or MIB. MIB objects are generally 138 accessed through the Simple Network Management Protocol (SNMP). 139 Objects in the MIB are defined using the mechanisms defined in the 140 Structure of Management Information (SMI). This memo specifies a MIB 141 module that is compliant to the SMIv2, which is described in STD 58, 142 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 143 [RFC2580]. 145 3. Structure of the MIB Modules 147 This section describes the structure of the LDP MIB Modules. 149 3.1. Overview 151 There are 4 MIB Modules in this document. These MIB Modules are the 152 MPLS-LDP-STD-MIB, the MPLS-LDP-GENERIC-STD-MIB, the MPLS-LDP-ATM-STD- 153 MIB and the MPLS-LDP-FRAME-RELAY-STD-MIB. The MPLS-LDP-STD-MIB 154 defines objects which are common to all LDP implementations. The 155 MPLS-LDP-GENERIC-STD-MIB defines Layer 2 Per Platform Label Space 156 objects for use with the MPLS-LDP-STD-MIB. The MPLS-LDP-ATM-STD-MIB 157 defines Layer 2 Asynchronous Transfer Mode (ATM) objects for use with 158 the MPLS-LDP-STD-MIB. The MPLS-LDP-FRAME-RELAY-STD-MIB defines Layer 159 2 FRAME-RELAY objects for use with the MPLS-LDP-STD-MIB. 161 The MPLS-LDP-STD-MIB Module MUST be implemented and at least one of 162 the Layer 2 MIB Modules MUST be implemented by an Agent developer on 163 an Label Switching Router (LSR) or Label Edge Router (LER). As an 164 example, if an Label Switching Router (LSR) or Label Edge Router 165 (LER) implementation intends to support LDP utilizing a Layer 2 of 166 Ethernet, then the MPLS-LDP-STD-MIB and the MPLS-LDP-GENERIC-STD-MIB 167 Modules MUST implemented. If an LSR/LER implementation intends to 168 support LDP utilizing a Layer 2 of ATM, then the MPLS-LDP-STD-MIB 169 Module and the MPLS-LDP-ATM-MIB Module MUST be implemented. If an 170 LSR/LER implementation intends to support LDP utilizing a Layer 2 of 171 FRAME-RELAY, then the MPLS-LDP-STD-MIB Module and the MPLS-LDP-FRAME- 172 RELAY-STD-MIB Module MUST be implemented. An LDP implementation that 173 utilizes all three Layer 2 media (Ethernet, Frame-Relay, ATM) MUST 174 support all 4 MIB Modules. Each of the Modules will be discussed in 175 detail in the following sections. 177 There are 2 compliance statements for each MIB Module. One 178 compliance statement is for full compliance which allows both 179 configuration and monitoring via SNMP. The other compliance 180 statement is for read-only compliance which allows only monitoring 181 via SNMP. 183 3.2. Future Considerations 185 The LDP Specification [RFC3036] does not specify the use of VPNs or 186 multicast for LDP, and thus, objects related to these areas have not 187 been included. 189 [RFC2684] does not describe VP merge capability and so this feature 190 has not been included. 192 These areas need to be specified in the LDP Specification or other 193 specifications prior to being added in this or any other MIB 194 document. 196 3.3. Interface Indexing 198 Interface Indexes as specified in [RFC2863] are used in these MIB 199 Modules. The descriptions of the ifIndexes denote which ifIndex is 200 being used. The use of ifIndex is for actual existing connections. 202 3.4. Differences from the LDP Specification 204 Currently, there are 3 differences between this specification and the 205 LDP Specification. As described in the Introduction, this document 206 is almost entirely based on the LDP specification. The differences 207 are documented here. 209 The first difference is that the LDP Entity Table contains some 210 DEFVAL clauses which are not specified explicitly in the LDP 211 Specification. These values, although not documented in the LDP 212 Specification, are widely used by existing LDP MIB implementations 213 and thus, have been adopted within this MPLS-LDP-STD-MIB module. 214 Please note, they can certainly be changed during row creation or a 215 subsequent SET request. 217 A second difference is the mplsLdpEntityConfGenericLRTable in the 218 MPLS-LDP-GENERIC-STD-MIB Module. This table, although provided as a 219 way to reserve a range of generic labels, does not exist in the LDP 220 Specification. It was added to the MIB due to a request from the 221 working group and because this table was considered useful for 222 reserving a range of generic labels. 224 The third difference is documented by the TEXTUAL-CONVENTION, 225 MplsAtmVcIdentifier which is in the MPLS-TC-STD-MIB [MPLSTCMIB]. 226 This TC was added to restrict vci values to be greater than 31 as 227 described in RFC 3035 [RFC3035]. 229 3.5. The MPLS-LDP-STD-MIB Module 231 This MIB Module contains objects which are common to all LDP 232 implementations. This MIB Module MUST always be implemented along 233 with one or more of the Layer 2 MIB Modules. 235 This table allows the Label Edge Router (LER) or the Label Switching 236 Router (LSR) to initiate and/or receive requests to establish LDP 237 sessions. As the LDP protocol distributes labels and establishes 238 sessions with Peers most of the tables in this module are populated 239 by the agent as instructed by the LDP protocol. The exception is the 240 mplsFecTable and the mplsLdpLspFecTable which can be configured by 241 the operator to specify Forwarding Equivalence Class information for 242 an LSP. 244 Some scalars and each table in the MPLS-LDP-STD-MIB Module is 245 described in the following subsections. 247 3.5.1. LDP Scalar Objects 249 There are several scalar objects in the LDP MIB module. The 250 mplsLdpLsrId is a read-only scalar object which reports Lable 251 Switching Router's (LSR's) Identifier. This MUST be a globally 252 unique value, such as the 32-bit router ID assigned to the LSR. 254 The mplsLdpLsrLoopDetectionCapable scalar object denotes whether the 255 LSR is capable of supporting loop detection and if so, which form of 256 loop detection. 258 There are two LastChange scalar objects, mplsLdpEntityLastChange and 259 mplsLdpPeerLastChange. These objects give an indication of there was 260 a change in the number of entries in the table, or if any of the 261 values in the respective tables changed. Please see the object's 262 description for more details. 264 The mplsLdpEntityIndexNext scalar object is described in the next 265 section. 267 3.5.2. The LDP Entity Table 269 The MPLS-LDP-STD-MIB provides objects to configure/set-up potential 270 LDP sessions on a specific LSR/LER. The mplsLdpEntityTable is used 271 to configure information which is used by the LDP protocol to setup 272 potential LDP Sessions. 274 Each entry/row in this table represents a single LDP Entity. There 275 is no maximum number of LDP Entities specified. However, there is an 276 mplsLdpEntityIndexNext object which should be retrieved by the 277 command generator prior to creating an LDP Entity. If the 278 mplsLdpEntityIndexNext object is zero, this indicates that the 279 LSR/LER is not able to create another LDP Entity at that time. 281 3.5.2.1. Changing Values After Session Establishment 283 One way to manually modify a session's parameters is by using SNMP to 284 change the MIB objects related to that session. Please note, special 285 care should be taken if MIB objects which are used in the MPLS LDP 286 Session Initialization need to be modified. If the modification of 287 any of these MIB variables takes place anytime after the start of 288 session intialization, then the entire session must be halted. Any 289 information learned by that session must be discarded. The objects 290 should then be modified, and session initialization started. 291 Assuming that the configuration was done correctly, then a new 292 session will be created. 294 For example, assume that an operator wishes to change the 295 configuration of a Label Range which is used by a Session that has 296 already been established. The operator should change the 297 mplsLdpEntityAdminStatus to "disable(2)". Setting the 298 mplsLdpEntityAdminStatus to "disable(2)" will cause the session to be 299 torn down (i.e. this will signal to LDP that it should send out tear 300 down messages for that session). Also, all information related to 301 that session should be removed from this MIB by the Agent. This 302 includes Peer information (i.e. relevant row in the mplsPeerTable) 303 and Session statistics (i.e. relevant row in the 304 mplsLdpSessionTable). Also, if the MPLS-LSR-STD-MIB module [LSRMIB] 305 is implemented and the optional Mapping Table objects are 306 implemented, then all information related to the LSPs in this session 307 should be removed from these MIB modules. [For more information 308 please see the section on "The Mapping Tables".] At this point, the 309 operator could modify the Label Range. Lastly, the operator should 310 set the mplsLdpEntityAdminStatus to "enable(1)". At this point 311 session initialization should occur. The LDP Entity goes through the 312 Session Initialization in order to communicate the new Label Ranges 313 to the Peer and establish new LSPs. 315 3.5.3. The LDP Entity Statistics Table 317 The mplsLpdEntityStatsTable is a read-only table which contains 318 statistical information related to failed attempts to establish 319 sessions. Each row in this table AUGMENTS an mplsLdpEntityEntry. 320 This table could be used to give insight into how to reconfigure 321 values so that a session could be successfully established. For 322 example, if the mplsLdpEntityStatsSessionRejectedLRErrors Counter 323 object was increasing, then this would indicate that the Label Range 324 (LR) may need to be adjusted. 326 3.5.4. The LDP Peer Table 328 The mplsLdpPeerTable is a read-only table which contains information 329 about LDP Peers known to LDP Entities. In other words, the Peer 330 information is learned by LDP through initialization or discovery. 331 This table should be populated by the agent as directed by the LDP 332 protocol. 334 A row in this table is related to one or more rows in the Hello 335 Adjacency Table and related to a single row in the Session Table. 336 The values in the Peer table are specific to a Peer and may or may 337 not be the same values used in the session. The reason is that the 338 Peer and Entity negotiate certain values. The Entity's values are 339 configured in the mplsLdpEntityTable and the Peer's values are 340 learned (and placed into the mplsLdpPeerTable). The 341 mplsLdpSessionTable shows the values used in establishing the 342 session. 344 One example, of when the Peer's values and the Session's values may 345 differ is with the Peer's Path Limit information. The Peer's Path 346 Limit information is learned from the session initialization phase. 347 The actual value for the Path Vector Limit is the Peer's value and 348 may not be the same value that appears in the session. There could 349 be a mismatch in this value between the Entity and the Peer. In the 350 event of a mismatch, then the session will use the Path Limit set by 351 the Entity (and not the Peer). 353 The Peer Table information was placed in a separate table from the 354 Session information to allow for a more comprehensive and coherent 355 MIB model. 357 3.5.5. The LDP Session Table 359 The LDP Session Table is a read-only table. Each entry in this table 360 represents a single session between an LDP Entity and a Peer. The 361 mplsLdpSessionEntry AUGMENTS the mplsLdpPeerEntry. 363 The information in this table is learned during session 364 establishment. NOTE: rows in this table will appear during session 365 intialization. 367 3.5.6. The LDP Session Statistics Table 369 The mplsLdpSessionStatsTable is a read-only table which contains 370 statistical information on sessions. This table AUGMENTS the 371 mplsLdpPeerTable. 373 3.5.7. The LDP Hello Adjacency Table 375 This is a table of all adjacencies between all LDP Entities and all 376 LDP Peers. A Session may have one or more adjacencies. A session 377 should not have zero adjacencies, because this indicates that the 378 session has lost contact with the Peer. A session which has zero 379 Hello Adjacencies should be removed. 381 3.5.8. The LDP LSP Table 383 The Label Information Base (LIB) contains information about labels 384 learned by the LSR. The LIB for LDP, CR-LDP and MPLS-RSVP (i.e. all 385 currently defined MPLS protocols) is represented in the LSR MIB 386 [LSRMIB]. The LIB is represented by the LSR MIB's mplsXCTable (mpls 387 Cross Connect Table), mplsInSegmentTable (mpls In Segment Table) and 388 the mplsOutSegmentTable (mpls Out Segment Table). The mplsXCTable 389 models the cross-connection of the incoming label with a specific 390 outgoing label. The mplsInSegmentTable stores the incoming label's 391 information, and the mplsOutSegmentTable stores the outgoing label's 392 information. 394 The LDP Session that created the LSP and the LSP's (incoming label, 395 outgoing label) pair along with other information is contained in the 396 MPLS-LSR-STD-MIB module's mplsXCTable, the mplsInSegmentTable and the 397 mplsOutSegmentTable. 399 In order to utilize the MPLS-LSR-STD-MIB module's mplsXCTable, 400 mplsInSegmentTable and mplsOutSegmentTable for LDP LSPs, there needs 401 to be a mechanism to associate LDP sessions with LDP LSPs created as 402 a result of those LDP sessions. The mplsInSegmentLdpLspTable and 403 mplsOutSegmentLdpLspTable in this MIB contain information to find the 404 LDP LSP entries in the mplsInSegmentTable, mplsOutSegmentTable and 405 the mplsXCTable. 407 These two tables, the mplsInSegmentLdpLspTable and 408 mplsOutSegmentLdpLspTable, have been made optional in the conformance 409 section of the MIB. They only need to be supported if the LSR MIBs 410 mplsInSegmentTable, mplsOutSegmentTable and mplsXCTable are 411 implemented. 413 As discussed in the section, "Changing Values after Session 414 Establishment", if a session is torn down, then all the information 415 related to this session, must be removed from the both LDP MIB and, 416 if implemented, from the LSR MIB. 418 3.5.9. The FEC Table 420 The FEC Table is a table which contains FEC (Forwarding Equivalence 421 Class) information. Each entry/row represents a single FEC Element. 422 There is also an LDP LSP FEC Table, mplsLdpLspFecTable, which 423 associates FECs with the LSPs. 425 3.5.10. The LDP Session Peer Address Table 427 The MPLS LDP Session Peer Address Table is a table which extends the 428 mplsLdpSessionTable. This table is a read-only table which stores 429 Addresses learned after session initialization via Address Message 430 advertisement. 432 3.6. LDP Notifications 434 Currently, there are several notifications which are specific for 435 LDP. These are described in this section. There are no objects 436 which enable or disable notifications from being generated. RFC 3413 437 [RFC3413] contains MIB modules which can be implemented that will 438 enable or disable these notifications from being generated. 440 The mplsLdpInitSessionThresholdExceeded notification indicates to the 441 operator that there may be a misconfigured mplsLdpEntityEntry because 442 the session associated with this Entity is not being established, and 443 the Entity keeps trying to establish the session. A side effect of 444 this situation is that a row in the mplsLdpSessionTable may not be 445 reaching the operational state as indicated by the 446 mplsLdpSessionState object. If the value of 447 mplsLdpEntityInitSessionThreshold is 0 (zero) then this is equal to 448 specifying the value of infinity for the threshold, and the 449 mplsLdpInitSessionThresholdExceeded notification will never be sent. 451 The mplsLdpPathVectorLimitMismatch notification is generated when 452 there is a mismatch in the Path Vector Limits between the Entity and 453 Peer during session initialization. The session uses the value which 454 is configured as the Entity's Path Vector Limit. However, a 455 notification should be generated to indicate that a mismatch 456 occurred. For further details, please see Section 3.5.3 of the LDP 457 Specification [RFC3036]. 459 The mplsLdpSessionUp and mplsLdpSessionDown notifications are 460 generated when there is an appropriate change in the 461 mplsLdpSessionState object, e.g. when sessions change state (Up to 462 Down for the mplsLdpSessionDown notification, or Down to Up for the 463 mplsLdpSessionUp notification). There was discussion about combining 464 these two notifications into a single notification, however, some NMS 465 applications can utilize two different notifications, rather than 466 having to parse the varbind list of a single notification. For 467 example, the SessionDown is matched to a SessionUp notification more 468 easily by some NMS applications, than having to parse a Varbind list 469 in a SessionChange type of notification. 471 3.7. LDP Notification Frequency 473 LDP Notifications are expected to be few in number when LDP is 474 ubiquitously deployed in a relatively stable network. A notification 475 receiver, e.g. an NMS, that receives these notifications should not 476 be overwhelmed by the frequency of LDP notifications. If this 477 assertion proves to be inaccurate, then a throttling object to 478 throttle these notifications may be added to future versions of the 479 MPLS-LDP-STD-MIB. 481 4. MPLS Label Distribution Protocol MIB Definitions 483 MPLS-LDP-STD-MIB DEFINITIONS ::= BEGIN 485 IMPORTS 486 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, 487 Integer32, Counter32, Unsigned32 488 FROM SNMPv2-SMI 489 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 490 FROM SNMPv2-CONF 492 RowStatus, TimeInterval, TruthValue, 493 TimeStamp, StorageType 494 FROM SNMPv2-TC 496 InetAddressPrefixLength, 497 InetAddressType, 498 InetAddress, 499 InetPortNumber 500 FROM INET-ADDRESS-MIB 502 IndexInteger, 503 IndexIntegerNextFree 504 FROM DIFFSERV-MIB 506 mplsStdMIB, 507 MplsLabelDistributionMethod, 508 MplsLdpIdentifier, 509 MplsLdpLabelType, 510 MplsLspType, 511 MplsLsrIdentifier, 512 MplsRetentionMode 513 FROM MPLS-TC-STD-MIB 515 MplsIndexType 516 FROM MPLS-LSR-STD-MIB; 518 mplsLdpStdMIB MODULE-IDENTITY 519 LAST-UPDATED "200311181200Z" -- 18 November 2003 520 ORGANIZATION "Multiprotocol Label Switching (mpls) 521 Working Group" 522 CONTACT-INFO 524 "Joan Cucchiara (jcucchiara@artel.com) 525 Artel 527 Hans Sjostrand (hans@ipunplugged.com) 528 ipUnplugged 530 James V. Luciani (james_luciani@mindspring.com) 531 Marconi Communications, Inc. 533 Working Group Chairs: 534 George Swallow, email: swallow@cisco.com 535 Loa Andersson, email: loa@pi.se 537 MPLS Working Group, email: mpls@uu.net" 539 DESCRIPTION 540 "Copyright (C) The Internet Society (2003). This 541 version of this MIB module is part of RFCXXX; see 542 the RFC itself for full legal notices. 544 This MIB contains managed object definitions for the 545 'Multiprotocol Label Switching, Label Distribution 546 Protocol, LDP' document." 548 REVISION "200311181200Z" -- 18 November 2003 549 DESCRIPTION 550 "Initial version published as part of RFC XXXX." 552 -- Please see the IANA Considerations Section. 553 -- The requested mplsStdMIB subId is 4, e.g. 554 -- ::= { mplsStdMIB 4 } 556 ::= { mplsStdMIB XXX } -- to be assigned by IANA 558 --**************************************************************** 560 mplsLdpNotifications OBJECT IDENTIFIER ::= { mplsLdpStdMIB 0 } 561 mplsLdpObjects OBJECT IDENTIFIER ::= { mplsLdpStdMIB 1 } 562 mplsLdpConformance OBJECT IDENTIFIER ::= { mplsLdpStdMIB 2 } 564 --**************************************************************** 565 -- MPLS LDP Objects 566 --**************************************************************** 568 mplsLdpLsrObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 1 } 570 mplsLdpEntityObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 2 } 572 -- 573 -- The MPLS Label Distribution Protocol's 574 -- Label Switching Router Objects 575 -- 576 mplsLdpLsrId OBJECT-TYPE 577 SYNTAX MplsLsrIdentifier 578 MAX-ACCESS read-only 579 STATUS current 580 DESCRIPTION 581 "The Label Switching Router's Identifier." 582 ::= { mplsLdpLsrObjects 1 } 584 mplsLdpLsrLoopDetectionCapable OBJECT-TYPE 585 SYNTAX INTEGER { 586 none(1), 587 other(2), 588 hopCount(3), 589 pathVector(4), 590 hopCountAndPathVector(5) 591 } 592 MAX-ACCESS read-only 593 STATUS current 594 DESCRIPTION 595 "A indication of whether this 596 Label Switching Router supports 597 loop detection. 599 none(1) -- Loop Detection is not supported 600 on this LSR. 602 other(2) -- Loop Detection is supported but 603 by a method other than those 604 listed below. 606 hopCount(3) -- Loop Detection is supported by 607 Hop Count only. 609 pathVector(4) -- Loop Detection is supported by 610 Path Vector only. 612 hopCountAndPathVector(5) -- Loop Detection is 613 supported by both Hop Count 614 And Path Vector. 616 Since Loop Detection is determined during 617 Session Initialization, an individual session 618 may not be running with loop detection. This 619 object simply gives an indication of whether or not the 620 LSR has the ability to support Loop Detection and 621 which types." 623 ::= { mplsLdpLsrObjects 2 } 625 -- 626 -- The MPLS Label Distribution Protocol Entity Objects 627 -- 629 mplsLdpEntityLastChange OBJECT-TYPE 630 SYNTAX TimeStamp 631 MAX-ACCESS read-only 632 STATUS current 633 DESCRIPTION 634 "The value of sysUpTime at the time of the most 635 recent addition or deletion of an entry 636 to/from the mplsLdpEntityTable/mplsLdpEntityStatsTable, or 637 the most recent change in value of any objects in the 638 mplsLdpEntityTable. 640 If no such changes have occurred since the last 641 re-initialization of the local management subsystem, 642 then this object contains a zero value." 643 ::= { mplsLdpEntityObjects 1 } 645 mplsLdpEntityIndexNext OBJECT-TYPE 646 SYNTAX IndexIntegerNextFree 647 MAX-ACCESS read-only 648 STATUS current 649 DESCRIPTION 650 "This object contains an appropriate value to 651 be used for mplsLdpEntityIndex when creating 652 entries in the mplsLdpEntityTable. The value 653 0 indicates that no unassigned entries are 654 available." 655 ::= { mplsLdpEntityObjects 2 } 657 mplsLdpEntityTable OBJECT-TYPE 658 SYNTAX SEQUENCE OF MplsLdpEntityEntry 659 MAX-ACCESS not-accessible 660 STATUS current 661 DESCRIPTION 662 "This table contains information about the 663 MPLS Label Distribution Protocol Entities which 664 exist on this Label Switching Router (LSR) 665 or Label Edge Router (LER)." 667 ::= { mplsLdpEntityObjects 3 } 669 mplsLdpEntityEntry OBJECT-TYPE 670 SYNTAX MplsLdpEntityEntry 671 MAX-ACCESS not-accessible 672 STATUS current 673 DESCRIPTION 674 "An entry in this table represents an LDP entity. 675 An entry can be created by a network administrator 676 or by an SNMP agent as instructed by LDP." 677 INDEX { mplsLdpEntityLdpId, mplsLdpEntityIndex } 678 ::= { mplsLdpEntityTable 1 } 680 MplsLdpEntityEntry ::= SEQUENCE { 681 mplsLdpEntityLdpId MplsLdpIdentifier, 682 mplsLdpEntityIndex IndexInteger, 683 mplsLdpEntityProtocolVersion Unsigned32, 684 mplsLdpEntityAdminStatus INTEGER, 685 mplsLdpEntityOperStatus INTEGER, 686 mplsLdpEntityTcpDscPort InetPortNumber, 687 mplsLdpEntityUdpDscPort InetPortNumber, 688 mplsLdpEntityMaxPduLength Unsigned32, 689 mplsLdpEntityKeepAliveHoldTimer Unsigned32, 690 mplsLdpEntityHelloHoldTimer Unsigned32, 691 mplsLdpEntityInitSessionThreshold Integer32, 692 mplsLdpEntityLabelDistMethod MplsLabelDistributionMethod, 693 mplsLdpEntityLabelRetentionMode MplsRetentionMode, 694 mplsLdpEntityPathVectorLimit Integer32, 695 mplsLdpEntityHopCountLimit Integer32, 696 mplsLdpEntityTransportAddrKind INTEGER, 697 mplsLdpEntityTargetPeer TruthValue, 698 mplsLdpEntityTargetPeerAddrType InetAddressType, 699 mplsLdpEntityTargetPeerAddr InetAddress, 700 mplsLdpEntityLabelType MplsLdpLabelType, 701 mplsLdpEntityDiscontinuityTime TimeStamp, 702 mplsLdpEntityStorageType StorageType, 703 mplsLdpEntityRowStatus RowStatus 704 } 706 mplsLdpEntityLdpId OBJECT-TYPE 707 SYNTAX MplsLdpIdentifier 708 MAX-ACCESS not-accessible 709 STATUS current 710 DESCRIPTION 711 "The LDP identifier." 713 REFERENCE 714 "RFC3036, LDP Specification, Section on LDP Identifiers." 715 ::= { mplsLdpEntityEntry 1 } 717 mplsLdpEntityIndex OBJECT-TYPE 718 SYNTAX IndexInteger 719 MAX-ACCESS not-accessible 720 STATUS current 721 DESCRIPTION 722 "This index is used as a secondary index to uniquely 723 identify this row. Before creating a row in this table, 724 the 'mplsLdpEntityIndexNext' object should be retrieved. 725 That value should be used for the value of this index 726 when creating a row in this table. NOTE: if a value 727 of zero (0) is retrieved, that indicates that no rows 728 can be created in this table at this time. 730 A secondary index (this object) is meaningful to some 731 but not all, LDP implementations. For example 732 an LDP implementation which uses PPP would 733 use this index to differentiate PPP sub-links. 735 Another way to use this index is to give this the 736 value of ifIndex. However, this is dependant 737 on the implementation." 738 ::= { mplsLdpEntityEntry 2 } 740 mplsLdpEntityProtocolVersion OBJECT-TYPE 741 SYNTAX Unsigned32(1..65535) 742 MAX-ACCESS read-create 743 STATUS current 744 DESCRIPTION 745 "The version number of the LDP protocol which will be 746 used in the session initialization message. 748 Section 3.5.3 in the LDP Specification specifies 749 that the version of the LDP protocol is negotiated during 750 session establishment. The value of this object 751 represents the value that is sent in the initialization 752 message." 753 REFERENCE 754 "RFC3036, LDP Specification, Section 3.5.3 Initialization 755 Message." 756 DEFVAL { 1 } 757 ::= { mplsLdpEntityEntry 3 } 759 mplsLdpEntityAdminStatus OBJECT-TYPE 760 SYNTAX INTEGER { 761 enable(1), 762 disable(2) 763 } 764 MAX-ACCESS read-create 765 STATUS current 766 DESCRIPTION 767 "The administrative status of this LDP Entity. 768 If this object is changed from 'enable' to 'disable' 769 and this entity has already attempted to establish 770 contact with a Peer, then all contact with that 771 Peer is lost and all information from that Peer 772 needs to be removed from the MIB. (This implies 773 that the network management subsystem should clean 774 up any related entry in the mplsLdpPeerTable. This 775 further implies that a 'tear-down' for that session 776 is issued and the session and all information related 777 to that session cease to exist). 779 At this point the operator is able to change values 780 which are related to this entity. 782 When the admin status is set back to 'enable', then 783 this Entity will attempt to establish a new session 784 with the Peer." 785 DEFVAL { enable } 786 ::= { mplsLdpEntityEntry 4 } 788 mplsLdpEntityOperStatus OBJECT-TYPE 789 SYNTAX INTEGER { 790 unknown(1), 791 enabled(2), 792 disabled(3) 793 } 794 MAX-ACCESS read-only 795 STATUS current 796 DESCRIPTION 797 "The operational status of this LDP Entity. 799 The value of unknown(1) indicates that the 800 operational status cannot be determined at 801 this time. The value of unknown should be 802 a transient condition before changing 803 to enabled(2) or disabled(3)." 805 ::= { mplsLdpEntityEntry 5 } 807 mplsLdpEntityTcpDscPort OBJECT-TYPE 808 SYNTAX InetPortNumber 809 MAX-ACCESS read-create 810 STATUS current 811 DESCRIPTION 812 "The TCP Discovery Port for 813 LDP. The default value is the well-known 814 value of this port." 815 REFERENCE 816 "RFC3036, LDP Specification, Section 2.4.1, 817 Basic Discovery Mechanism, Section 2.4.2, 818 Extended Discovery Mechanism, Section 819 3.10, Well-known Numbers, and Section 3.10.1. 820 UDP and TCP Ports." 821 DEFVAL { 646 } 822 ::= { mplsLdpEntityEntry 6 } 824 mplsLdpEntityUdpDscPort OBJECT-TYPE 825 SYNTAX InetPortNumber 826 MAX-ACCESS read-create 827 STATUS current 828 DESCRIPTION 829 "The UDP Discovery Port for 830 LDP. The default value is the 831 well-known value for this port." 832 REFERENCE 833 "RFC3036, LDP Specification, Section 2.4.1, 834 Basic Discovery Mechanism, Section 2.4.2, 835 Extended Discovery Mechanism, Section 836 3.10, Well-known Numbers, and Section 3.10.1. 837 UDP and TCP Ports." 838 DEFVAL { 646 } 839 ::= { mplsLdpEntityEntry 7 } 841 mplsLdpEntityMaxPduLength OBJECT-TYPE 842 SYNTAX Unsigned32 (256..65535) 843 UNITS "octets" 844 MAX-ACCESS read-create 845 STATUS current 846 DESCRIPTION 847 "The maximum PDU Length that is sent in 848 the Common Session Parameters of an Initialization 849 Message. According to the LDP Specification [RFC3036] 850 a value of 255 or less specifies the 851 default maximum length of 4096 octets, this is why 852 the value of this object starts at 256. The operator 853 should explicitly choose the default value (i.e. 4096), 854 or some other value. 856 The receiving LSR MUST calculate the maximum PDU 857 length for the session by using the smaller of its and 858 its peer's proposals for Max PDU Length." 859 REFERENCE 860 "RFC3036, LDP Specification, Section 3.5.3. 861 Initialization Message." 862 DEFVAL { 4096 } 863 ::= { mplsLdpEntityEntry 8 } 865 mplsLdpEntityKeepAliveHoldTimer OBJECT-TYPE 866 SYNTAX Unsigned32 (1..65535) 867 UNITS "seconds" 868 MAX-ACCESS read-create 869 STATUS current 870 DESCRIPTION 871 "The 16-bit integer value which is the proposed keep 872 alive hold timer for this LDP Entity." 873 DEFVAL { 40 } 874 ::= { mplsLdpEntityEntry 9 } 876 mplsLdpEntityHelloHoldTimer OBJECT-TYPE 877 SYNTAX Unsigned32 (0..65535) 878 UNITS "seconds" 879 MAX-ACCESS read-create 880 STATUS current 881 DESCRIPTION 882 "The 16-bit integer value which is the proposed Hello 883 hold timer for this LDP Entity. The Hello Hold time 884 in seconds. 886 An LSR maintains a record of Hellos received 887 from potential peers. This object represents 888 the Hold Time in the Common Hello Parameters TLV of 889 the Hello Message. 891 A value of 0 is a default value and should be 892 interpretted in conjunction with the 893 mplsLdpEntityTargetPeer object. 895 If the value of this object is 0: if the value of the 896 mplsLdpEntityTargetPeer object is false(2), then this 897 specifies that the Hold Time's actual default value is 898 15 seconds (i.e. the default Hold time for Link Hellos 899 is 15 seconds). Otherwise if the value of the 900 mplsLdpEntityTargetPeer object is true(1), then this 901 specifies that the Hold Time's actual default value is 902 45 seconds (i.e. the default Hold time for Targeted 903 Hellos is 45 seconds). 905 A value of 65535 means infinite (i.e. wait forever). 907 All other values represent the amount of time in 908 seconds to wait for a Hello Message. Setting the 909 hold time to a value smaller than 15 is not 910 recommended, although not forbidden according 911 to RFC3036." 912 REFERENCE 913 "RFC3036, LDP Specification, Section 3.5.2., 914 Hello Message." 915 DEFVAL { 0 } 916 ::= { mplsLdpEntityEntry 10 } 918 mplsLdpEntityInitSessionThreshold OBJECT-TYPE 919 SYNTAX Integer32(0..100) 920 MAX-ACCESS read-create 921 STATUS current 922 DESCRIPTION 923 "When attempting to establish a session with 924 a given Peer, the given LDP Entity should 925 send out the SNMP notification, 926 'mplsLdpInitSessionThresholdExceeded', when 927 the number of Session Initialization messages 928 sent exceeds this threshold. 930 The notification is used to notify an 931 operator when this Entity and its Peer are 932 possibily engaged in an endless sequence 933 of messages as each NAKs the other's 934 Initialization messages with Error Notification 935 messages. Setting this threshold which triggers 936 the notification is one way to notify the 937 operator. The notification should be generated 938 each time this threshold is exceeded and 939 for every subsequent Initialization message 940 which is NAK'd with an Error Notification 941 message after this threshold is exceeded. 943 A value of 0 (zero) for this object 944 indicates that the threshold is infinity, thus 945 the SNMP notification will never be generated." 946 REFERENCE 947 "RFC3036, LDP Specification, 948 Section 2.5.3 Session Initialization." 949 DEFVAL { 8 } 950 ::= { mplsLdpEntityEntry 11 } 952 mplsLdpEntityLabelDistMethod OBJECT-TYPE 953 SYNTAX MplsLabelDistributionMethod 954 MAX-ACCESS read-create 955 STATUS current 956 DESCRIPTION 957 "For any given LDP session, the method of 958 label distribution must be specified." 959 ::= { mplsLdpEntityEntry 12 } 961 mplsLdpEntityLabelRetentionMode OBJECT-TYPE 962 SYNTAX MplsRetentionMode 963 MAX-ACCESS read-create 964 STATUS current 965 DESCRIPTION 966 "The LDP Entity can be configured to use either 967 conservative or liberal label retention mode. 969 If the value of this object is conservative(1) 970 then advertized label mappings are retained 971 only if they will be used to forward packets, 972 i.e. if label came from a valid next hop. 974 If the value of this object is liberal(2) 975 then all advertized label mappings are retained 976 whether they are from a valid next hop or not." 977 ::= { mplsLdpEntityEntry 13 } 979 mplsLdpEntityPathVectorLimit OBJECT-TYPE 980 SYNTAX Integer32 (0..255) 981 MAX-ACCESS read-create 982 STATUS current 983 DESCRIPTION 984 "If the value of this object is 0 (zero) then 985 Loop Dection for Path Vectors is disabled. 987 Otherwise, if this object has a value greater than 988 zero, then Loop Dection for Path Vectors is enabled, 989 and the Path Vector Limit is this value. 990 Also, the value of the object, 991 'mplsLdpLsrLoopDetectionCapable', must be set to 992 either 'pathVector(4)' or 'hopCountAndPathVector(5)', 993 if this object has a value greater than 0 (zero), 994 otherwise it is ignored." 995 REFERENCE 996 "RFC3036, LDP Specification, Section 2.8 Loop Dection, 997 Section 3.4.5 Path Vector TLV." 998 ::= { mplsLdpEntityEntry 14 } 1000 mplsLdpEntityHopCountLimit OBJECT-TYPE 1001 SYNTAX Integer32 (0..255) 1002 MAX-ACCESS read-create 1003 STATUS current 1004 DESCRIPTION 1005 "If the value of this object is 0 (zero), 1006 then Loop Detection using Hop Counters is 1007 disabled. 1009 If the value of this object is greater than 1010 0 (zero) then Loop Detection using Hop 1011 Counters is enabled, and this object 1012 specifies this Entity's maximum allowable 1013 value for the Hop Count. 1014 Also, the value of the object 1015 mplsLdpLsrLoopDetectionCapable must be set 1016 to either 'hopCount(3)' or 1017 'hopCountAndPathVector(5)' if this object 1018 has a value greater than 0 (zero), otherwise 1019 it is ignored." 1020 DEFVAL { 0 } 1021 ::= { mplsLdpEntityEntry 15 } 1023 mplsLdpEntityTransportAddrKind OBJECT-TYPE 1024 SYNTAX INTEGER { 1025 interface(1), 1026 loopback(2) 1027 } 1028 MAX-ACCESS read-create 1029 STATUS current 1030 DESCRIPTION 1031 "This specifies whether the loopback or interface 1032 address is to be used as the transport address 1033 in the transport address TLV of the 1034 hello message. 1036 If the value is interface(1), then the IP 1037 address of the interface from which hello 1038 messages are sent is used as the transport 1039 address in the hello message. 1041 Otherwise, if the value is loopback(2), then the IP 1042 address of the loopback interface is used as the 1043 transport address in the hello message." 1044 DEFVAL { loopback } 1045 ::= { mplsLdpEntityEntry 16 } 1047 mplsLdpEntityTargetPeer OBJECT-TYPE 1048 SYNTAX TruthValue 1049 MAX-ACCESS read-create 1050 STATUS current 1051 DESCRIPTION 1052 "If this LDP entity uses targeted peer then set 1053 this to true." 1054 DEFVAL { false } 1055 ::= { mplsLdpEntityEntry 17 } 1057 mplsLdpEntityTargetPeerAddrType OBJECT-TYPE 1058 SYNTAX InetAddressType 1059 MAX-ACCESS read-create 1060 STATUS current 1061 DESCRIPTION 1062 "The type of the internetwork layer address used for 1063 the Extended Discovery. This object indicates how 1064 the value of mplsLdpEntityTargetPeerAddr is to 1065 be interpreted." 1066 ::= { mplsLdpEntityEntry 18 } 1068 mplsLdpEntityTargetPeerAddr OBJECT-TYPE 1069 SYNTAX InetAddress 1070 MAX-ACCESS read-create 1071 STATUS current 1072 DESCRIPTION 1073 "The value of the internetwork layer address 1074 used for the Extended Discovery. The value of 1075 mplsLdpEntityTargetPeerAddrType specifies how 1076 this address is to be intepreted." 1077 ::= { mplsLdpEntityEntry 19 } 1079 mplsLdpEntityLabelType OBJECT-TYPE 1080 SYNTAX MplsLdpLabelType 1081 MAX-ACCESS read-create 1082 STATUS current 1083 DESCRIPTION 1084 "Specifies the optional parameters for the LDP 1085 Initialization Message. 1087 If the value is generic(1) then no 1088 optional parameters will be sent in 1089 the LDP Initialization message associated 1090 with this Entity. 1092 If the value is atmParameters(2) then 1093 a row must be created in the 1094 mplsLdpEntityAtmTable, which 1095 corresponds to this entry. 1097 If the value is frameRelayParameters(3) then 1098 a row must be created in the 1099 mplsLdpEntityFrameRelayTable, which 1100 corresponds to this entry." 1101 REFERENCE 1102 "RFC3036, LDP Specification, Section 3.5.3., 1103 Initialization Message." 1104 ::= { mplsLdpEntityEntry 20 } 1106 mplsLdpEntityDiscontinuityTime OBJECT-TYPE 1107 SYNTAX TimeStamp 1108 MAX-ACCESS read-only 1109 STATUS current 1110 DESCRIPTION 1111 "The value of sysUpTime on the most recent occasion 1112 at which any one or more of this entity's counters 1113 suffered a discontinuity. The relevant counters 1114 are the specific instances associated with this 1115 entity of any Counter32 object contained 1116 in the 'mplsLdpEntityStatsTable'. If no such 1117 discontinuities have occurred since the last 1118 re-initialization of the local management 1119 subsystem, then this object contains a zero 1120 value." 1121 ::= { mplsLdpEntityEntry 21 } 1123 mplsLdpEntityStorageType OBJECT-TYPE 1124 SYNTAX StorageType 1125 MAX-ACCESS read-create 1126 STATUS current 1127 DESCRIPTION 1128 "The storage type for this conceptual row. 1129 Conceptual rows having the value 'permanent(4)' 1130 need not allow write-access to any columnar 1131 objects in the row." 1132 DEFVAL{ nonVolatile } 1133 ::= { mplsLdpEntityEntry 22 } 1135 mplsLdpEntityRowStatus OBJECT-TYPE 1136 SYNTAX RowStatus 1137 MAX-ACCESS read-create 1138 STATUS current 1139 DESCRIPTION 1140 "The status of this conceptual row. All writable 1141 objects in this row may be modified at any 1142 time, however, as described in detail in 1143 the section entitled, 'Changing Values After 1144 Session Establishment', and again described 1145 in the DESCRIPTION clause of the 1146 mplsLdpEntityAdminStatus object, if a session 1147 has been initiated with a Peer, changing objects 1148 in this table will wreak havoc with the session 1149 and interrupt traffic. To repeat again: 1150 the recommended procedure is to 1151 set the mplsLdpEntityAdminStatus to down, thereby 1152 explicitly causing a session to be torn down. Then, 1153 change objects in this entry, then set 1154 the mplsLdpEntityAdminStatus to enable, 1155 which enables a new session to be initiated." 1156 ::= { mplsLdpEntityEntry 23 } 1158 -- 1159 -- The MPLS LDP Entity Statistics Table 1160 -- 1162 mplsLdpEntityStatsTable OBJECT-TYPE 1163 SYNTAX SEQUENCE OF MplsLdpEntityStatsEntry 1164 MAX-ACCESS not-accessible 1165 STATUS current 1166 DESCRIPTION 1167 "This table is a read-only table which augments 1168 the mplsLdpEntityTable. The purpose of this 1169 table is to keep statistical information about 1170 the LDP Entities on the LSR." 1171 ::= { mplsLdpEntityObjects 4 } 1173 mplsLdpEntityStatsEntry OBJECT-TYPE 1174 SYNTAX MplsLdpEntityStatsEntry 1175 MAX-ACCESS not-accessible 1176 STATUS current 1177 DESCRIPTION 1178 "A row in this table contains statistical information 1179 about an LDP Entity. Some counters contained in a 1180 row are for fatal errors received during a former 1181 LDP Session associated with this entry. For example, 1182 an LDP PDU received on a TCP connection during an 1183 LDP Session contains a fatal error. That 1184 error is counted here, because the 1185 session is terminated. 1187 If the error is NOT fatal (i.e. the Session 1188 remains), then the error is counted in the 1189 mplsLdpSessionStatsEntry." 1190 AUGMENTS { mplsLdpEntityEntry } 1191 ::= { mplsLdpEntityStatsTable 1 } 1193 MplsLdpEntityStatsEntry ::= SEQUENCE { 1194 mplsLdpEntityStatsSessionAttempts Counter32, 1195 mplsLdpEntityStatsSessionRejectedNoHelloErrors Counter32, 1196 mplsLdpEntityStatsSessionRejectedAdErrors Counter32, 1197 mplsLdpEntityStatsSessionRejectedMaxPduErrors Counter32, 1198 mplsLdpEntityStatsSessionRejectedLRErrors Counter32, 1199 mplsLdpEntityStatsBadLdpIdentifierErrors Counter32, 1200 mplsLdpEntityStatsBadPduLengthErrors Counter32, 1201 mplsLdpEntityStatsBadMessageLengthErrors Counter32, 1202 mplsLdpEntityStatsBadTlvLengthErrors Counter32, 1203 mplsLdpEntityStatsMalformedTlvValueErrors Counter32, 1204 mplsLdpEntityStatsKeepAliveTimerExpErrors Counter32, 1205 mplsLdpEntityStatsShutdownReceivedNotifications Counter32, 1206 mplsLdpEntityStatsShutdownSentNotifications Counter32 1207 } 1209 mplsLdpEntityStatsSessionAttempts OBJECT-TYPE 1210 SYNTAX Counter32 1211 MAX-ACCESS read-only 1212 STATUS current 1213 DESCRIPTION 1214 "A count of the Session Initialization messages 1215 which were sent or received by this LDP Entity and 1216 were NAK'd. In other words, this counter counts 1217 the number of session initializations that failed. 1219 Discontinuities in the value of this counter can occur 1220 at re-initialization of the management system, and at 1221 other times as indicated by the value of 1222 mplsLdpEntityDiscontinuityTime." 1223 ::= { mplsLdpEntityStatsEntry 1 } 1225 mplsLdpEntityStatsSessionRejectedNoHelloErrors OBJECT-TYPE 1226 SYNTAX Counter32 1227 MAX-ACCESS read-only 1228 STATUS current 1229 DESCRIPTION 1230 "A count of the Session Rejected/No Hello Error 1231 Notification Messages sent or received by 1232 this LDP Entity. 1234 Discontinuities in the value of this counter can occur 1235 at re-initialization of the management system, and at 1236 other times as indicated by the value of 1237 mplsLdpEntityDiscontinuityTime." 1238 ::= { mplsLdpEntityStatsEntry 2 } 1240 mplsLdpEntityStatsSessionRejectedAdErrors OBJECT-TYPE 1241 SYNTAX Counter32 1242 MAX-ACCESS read-only 1243 STATUS current 1244 DESCRIPTION 1245 "A count of the Session Rejected/Parameters 1246 Advertisement Mode Error Notification Messages sent 1247 or received by this LDP Entity. 1249 Discontinuities in the value of this counter can occur 1250 at re-initialization of the management system, and at 1251 other times as indicated by the value of 1252 mplsLdpEntityDiscontinuityTime." 1253 ::= { mplsLdpEntityStatsEntry 3 } 1255 mplsLdpEntityStatsSessionRejectedMaxPduErrors OBJECT-TYPE 1256 SYNTAX Counter32 1257 MAX-ACCESS read-only 1258 STATUS current 1259 DESCRIPTION 1260 "A count of the Session Rejected/Parameters 1261 Max Pdu Length Error Notification Messages sent 1262 or received by this LDP Entity. 1264 Discontinuities in the value of this counter can occur 1265 at re-initialization of the management system, and at 1266 other times as indicated by the value of 1267 mplsLdpEntityDiscontinuityTime." 1268 ::= { mplsLdpEntityStatsEntry 4 } 1270 mplsLdpEntityStatsSessionRejectedLRErrors OBJECT-TYPE 1271 SYNTAX Counter32 1272 MAX-ACCESS read-only 1273 STATUS current 1274 DESCRIPTION 1275 "A count of the Session Rejected/Parameters 1276 Label Range Notification Messages sent 1277 or received by this LDP Entity. 1279 Discontinuities in the value of this counter can occur 1280 at re-initialization of the management system, and at 1281 other times as indicated by the value of 1282 mplsLdpEntityDiscontinuityTime." 1283 ::= { mplsLdpEntityStatsEntry 5 } 1285 mplsLdpEntityStatsBadLdpIdentifierErrors OBJECT-TYPE 1286 SYNTAX Counter32 1287 MAX-ACCESS read-only 1288 STATUS current 1289 DESCRIPTION 1290 "This object counts the number of Bad LDP Identifier 1291 Fatal Errors detected by the session(s) 1292 (past and present) associated with this LDP Entity. 1294 Discontinuities in the value of this counter can occur 1295 at re-initialization of the management system, and at 1296 other times as indicated by the value of 1297 mplsLdpEntityDiscontinuityTime." 1298 REFERENCE 1299 "RFC3036, LDP Specification, Section 3.5.1.2." 1300 ::= { mplsLdpEntityStatsEntry 6 } 1302 mplsLdpEntityStatsBadPduLengthErrors OBJECT-TYPE 1303 SYNTAX Counter32 1304 MAX-ACCESS read-only 1305 STATUS current 1306 DESCRIPTION 1307 "This object counts the number of Bad PDU Length 1308 Fatal Errors detected by the session(s) 1309 (past and present) associated with this LDP Entity. 1311 Discontinuities in the value of this counter can occur 1312 at re-initialization of the management system, and at 1313 other times as indicated by the value of 1314 mplsLdpEntityDiscontinuityTime." 1315 REFERENCE 1316 "RFC3036, LDP Specification, Section 3.5.1.2." 1317 ::= { mplsLdpEntityStatsEntry 7 } 1319 mplsLdpEntityStatsBadMessageLengthErrors OBJECT-TYPE 1320 SYNTAX Counter32 1321 MAX-ACCESS read-only 1322 STATUS current 1323 DESCRIPTION 1324 "This object counts the number of Bad Message 1325 Length Fatal Errors detected by the session(s) 1326 (past and present) associated with this LDP Entity. 1328 Discontinuities in the value of this counter can occur 1329 at re-initialization of the management system, and at 1330 other times as indicated by the value of 1331 mplsLdpEntityDiscontinuityTime." 1332 REFERENCE 1333 "RFC3036, LDP Specification, Section 3.5.1.2." 1334 ::= { mplsLdpEntityStatsEntry 8 } 1336 mplsLdpEntityStatsBadTlvLengthErrors OBJECT-TYPE 1337 SYNTAX Counter32 1338 MAX-ACCESS read-only 1339 STATUS current 1340 DESCRIPTION 1341 "This object counts the number of Bad TLV 1342 Length Fatal Errors detected by the session(s) 1343 (past and present) associated with this LDP Entity. 1345 Discontinuities in the value of this counter can occur 1346 at re-initialization of the management system, and at 1347 other times as indicated by the value of 1348 mplsLdpEntityDiscontinuityTime." 1349 REFERENCE 1350 "RFC3036, LDP Specification, Section 3.5.1.2." 1351 ::= { mplsLdpEntityStatsEntry 9 } 1353 mplsLdpEntityStatsMalformedTlvValueErrors OBJECT-TYPE 1354 SYNTAX Counter32 1355 MAX-ACCESS read-only 1356 STATUS current 1357 DESCRIPTION 1358 "This object counts the number of Malformed TLV 1359 Value Fatal Errors detected by the session(s) 1360 (past and present) associated with this 1361 LDP Entity. 1363 Discontinuities in the value of this counter can occur 1364 at re-initialization of the management system, and at 1365 other times as indicated by the value of 1366 mplsLdpEntityDiscontinuityTime." 1367 REFERENCE 1368 "RFC3036, LDP Specification, Section 3.5.1.2." 1369 ::= { mplsLdpEntityStatsEntry 10 } 1371 mplsLdpEntityStatsKeepAliveTimerExpErrors OBJECT-TYPE 1372 SYNTAX Counter32 1373 MAX-ACCESS read-only 1374 STATUS current 1375 DESCRIPTION 1376 "This object counts the number of Session Keep Alive 1377 Timer Expired Errors detected by the session(s) 1378 (past and present) associated with this LDP Entity. 1380 Discontinuities in the value of this counter can occur 1381 at re-initialization of the management system, and at 1382 other times as indicated by the value of 1383 mplsLdpEntityDiscontinuityTime." 1384 REFERENCE 1385 "RFC3036, LDP Specification, Section 3.5.1.2." 1386 ::= { mplsLdpEntityStatsEntry 11 } 1388 mplsLdpEntityStatsShutdownReceivedNotifications OBJECT-TYPE 1389 SYNTAX Counter32 1390 MAX-ACCESS read-only 1391 STATUS current 1392 DESCRIPTION 1393 "This object counts the number of Shutdown Notfications 1394 received related to session(s) (past and present) 1395 associated with this LDP Entity. 1397 Discontinuities in the value of this counter can occur 1398 at re-initialization of the management system, and at 1399 other times as indicated by the value of 1400 mplsLdpEntityDiscontinuityTime." 1401 ::= { mplsLdpEntityStatsEntry 12 } 1403 mplsLdpEntityStatsShutdownSentNotifications OBJECT-TYPE 1404 SYNTAX Counter32 1405 MAX-ACCESS read-only 1406 STATUS current 1407 DESCRIPTION 1408 "This object counts the number of Shutdown Notfications 1409 sent related to session(s) (past and present) associated 1410 with this LDP Entity. 1412 Discontinuities in the value of this counter can occur 1413 at re-initialization of the management system, and at 1414 other times as indicated by the value of 1415 mplsLdpEntityDiscontinuityTime." 1416 ::= { mplsLdpEntityStatsEntry 13 } 1418 -- 1419 -- The MPLS LDP Peer Table 1420 -- 1422 mplsLdpSessionObjects OBJECT IDENTIFIER ::= { mplsLdpObjects 3 } 1424 mplsLdpPeerLastChange OBJECT-TYPE 1425 SYNTAX TimeStamp 1426 MAX-ACCESS read-only 1427 STATUS current 1428 DESCRIPTION 1429 "The value of sysUpTime at the time of the most 1430 recent addition or deletion to/from the 1431 mplsLdpPeerTable/mplsLdpSessionTable." 1432 ::= { mplsLdpSessionObjects 1 } 1434 mplsLdpPeerTable OBJECT-TYPE 1435 SYNTAX SEQUENCE OF MplsLdpPeerEntry 1436 MAX-ACCESS not-accessible 1437 STATUS current 1438 DESCRIPTION 1439 "Information about LDP peers known by Entities in 1440 the mplsLdpEntityTable. The information in this table 1441 is based on information from the Entity-Peer interaction 1442 during session initialization but is not appropriate 1443 for the mplsLdpSessionTable, because objects in this 1444 table may or may not be used in session establishment." 1445 ::= { mplsLdpSessionObjects 2 } 1447 mplsLdpPeerEntry OBJECT-TYPE 1448 SYNTAX MplsLdpPeerEntry 1449 MAX-ACCESS not-accessible 1450 STATUS current 1451 DESCRIPTION 1452 "Information about a single Peer which is related 1453 to a Session. This table is augmented by 1454 the mplsLdpSessionTable." 1455 INDEX { mplsLdpEntityLdpId, 1456 mplsLdpEntityIndex, 1457 mplsLdpPeerLdpId } 1458 ::= { mplsLdpPeerTable 1 } 1460 MplsLdpPeerEntry ::= SEQUENCE { 1461 mplsLdpPeerLdpId MplsLdpIdentifier, 1462 mplsLdpPeerLabelDistMethod MplsLabelDistributionMethod, 1463 mplsLdpPeerPathVectorLimit Integer32, 1464 mplsLdpPeerTransportAddrType InetAddressType, 1465 mplsLdpPeerTransportAddr InetAddress 1466 } 1468 mplsLdpPeerLdpId OBJECT-TYPE 1469 SYNTAX MplsLdpIdentifier 1470 MAX-ACCESS not-accessible 1471 STATUS current 1472 DESCRIPTION 1473 "The LDP identifier of this LDP Peer." 1474 ::= { mplsLdpPeerEntry 1 } 1476 mplsLdpPeerLabelDistMethod OBJECT-TYPE 1477 SYNTAX MplsLabelDistributionMethod 1478 MAX-ACCESS read-only 1479 STATUS current 1480 DESCRIPTION 1481 "For any given LDP session, the method of 1482 label distribution must be specified." 1483 ::= { mplsLdpPeerEntry 2 } 1485 mplsLdpPeerPathVectorLimit OBJECT-TYPE 1486 SYNTAX Integer32 (0..255) 1487 MAX-ACCESS read-only 1488 STATUS current 1489 DESCRIPTION 1490 "If the value of this object is 0 (zero) then 1491 Loop Dection for Path Vectors for this Peer 1492 is disabled. 1494 Otherwise, if this object has a value greater than 1495 zero, then Loop Dection for Path Vectors for this 1496 Peer is enabled and the Path Vector Limit is this value." 1497 REFERENCE 1498 "RFC3036, LDP Specification, Section 2.8 Loop Dection, 1499 Section 3.4.5 Path Vector TLV." 1500 ::= { mplsLdpPeerEntry 3 } 1502 mplsLdpPeerTransportAddrType OBJECT-TYPE 1503 SYNTAX InetAddressType 1504 MAX-ACCESS read-only 1505 STATUS current 1506 DESCRIPTION 1507 "The type of the Internet address for the 1508 mplsLdpPeerTransportAddr object. The LDP 1509 specification describes this as being either 1510 an IPv4 Transport Address or IPv6 Transport 1511 Address which is used in opening the LDP session's 1512 TCP connection, or if the optional TLV is not 1513 present, then this is the IPv4/IPv6 source 1514 address for the UPD packet carrying the Hellos. 1516 This object specifies how the value of the 1517 mplsLdpPeerTransportAddr object should be 1518 interpreted." 1519 REFERENCE 1520 "RFC3036, LDP Specification, Section 2.5.2 1521 Transport Connection Establishment and 1522 Section 3.5.2.1 Hello Message Procedures." 1523 ::= { mplsLdpPeerEntry 4 } 1525 mplsLdpPeerTransportAddr OBJECT-TYPE 1526 SYNTAX InetAddress 1527 MAX-ACCESS read-only 1528 STATUS current 1529 DESCRIPTION 1530 "The Internet address advertised by the peer 1531 in the Hello Message or the Hello source address. 1533 The type of this address is specified by the 1534 value of the mplsLdpPeerTransportAddrType 1535 object." 1536 REFERENCE 1537 "RFC3036, LDP Specification, Section 2.5.2 1538 Transport Connection Establishment and 1539 Section 3.5.2.1 Hello Message Procedures." 1540 ::= { mplsLdpPeerEntry 5 } 1542 -- 1543 -- The MPLS LDP Sessions Table 1544 -- 1546 mplsLdpSessionTable OBJECT-TYPE 1547 SYNTAX SEQUENCE OF MplsLdpSessionEntry 1548 MAX-ACCESS not-accessible 1549 STATUS current 1550 DESCRIPTION 1551 "A table of Sessions between the LDP Entities 1552 and LDP Peers. This table AUGMENTS the 1553 mplsLdpPeerTable. Each row in this table 1554 represents a single session." 1555 ::= { mplsLdpSessionObjects 3 } 1557 mplsLdpSessionEntry OBJECT-TYPE 1558 SYNTAX MplsLdpSessionEntry 1559 MAX-ACCESS not-accessible 1560 STATUS current 1561 DESCRIPTION 1562 "An entry in this table represents information on a 1563 single session between an LDP Entity and LDP Peer. 1564 The information contained in a row is read-only. 1566 Please note: the Path Vector Limit for the 1567 Session is the value which is configured in 1568 the corresponding mplsLdpEntityEntry. The 1569 Peer's Path Vector Limit is in the 1570 mplsLdpPeerPathVectorLimit object in the 1571 mplsLdpPeerTable. 1573 Values which may differ from those configured are 1574 noted in the objects of this table, the 1575 mplsLdpAtmSessionTable and the 1576 mplsLdpFrameRelaySessionTable. A value will 1577 differ if it was negotiated between the 1578 Entity and the Peer. Values may or may not 1579 be negotiated. For example, if the values 1580 are the same then no negotiation takes place. 1581 If they are negotiated, then they may differ." 1582 AUGMENTS { mplsLdpPeerEntry } 1583 ::= { mplsLdpSessionTable 1 } 1585 MplsLdpSessionEntry ::= SEQUENCE { 1586 mplsLdpSessionStateLastChange TimeStamp, 1587 mplsLdpSessionState INTEGER, 1588 mplsLdpSessionRole INTEGER, 1589 mplsLdpSessionProtocolVersion Unsigned32, 1590 mplsLdpSessionKeepAliveHoldTimeRem TimeInterval, 1591 mplsLdpSessionKeepAliveTime Unsigned32, 1592 mplsLdpSessionMaxPduLength Unsigned32, 1593 mplsLdpSessionDiscontinuityTime TimeStamp 1594 } 1596 mplsLdpSessionStateLastChange OBJECT-TYPE 1597 SYNTAX TimeStamp 1598 MAX-ACCESS read-only 1599 STATUS current 1600 DESCRIPTION 1601 "The value of sysUpTime at the time this 1602 Session entered its current state as 1603 denoted by the mplsLdpSessionState 1604 object." 1605 ::= { mplsLdpSessionEntry 1 } 1607 mplsLdpSessionState OBJECT-TYPE 1608 SYNTAX INTEGER { 1609 nonexistent(1), 1610 initialized(2), 1611 openrec(3), 1612 opensent(4), 1613 operational(5) 1614 } 1615 MAX-ACCESS read-only 1616 STATUS current 1617 DESCRIPTION 1618 "The current state of the session, all of the 1619 states 1 to 5 are based on the state machine 1620 for session negotiation behavior." 1621 REFERENCE 1622 "RFC3036, LDP Specification, Section 2.5.4, 1623 Initialization State Machine." 1624 ::= { mplsLdpSessionEntry 2 } 1626 mplsLdpSessionRole OBJECT-TYPE 1627 SYNTAX INTEGER { 1628 unknown(1), 1629 active(2), 1630 passive(3) 1631 } 1632 MAX-ACCESS read-only 1633 STATUS current 1634 DESCRIPTION 1635 "During session establishment the LSR/LER takes either 1636 the active role or the passive role based on address 1637 comparisons. This object indicates whether this LSR/LER 1638 was behaving in an active role or passive role during 1639 this session's establishment. 1641 The value of unknown(1), indicates that the role is not 1642 able to be determined at the present time." 1643 REFERENCE 1644 "RFC3036, LDP Specification, Section 2.5.3., 1645 Session Initialization" 1646 ::= { mplsLdpSessionEntry 3 } 1648 mplsLdpSessionProtocolVersion OBJECT-TYPE 1649 SYNTAX Unsigned32(1..65535) 1650 MAX-ACCESS read-only 1651 STATUS current 1652 DESCRIPTION 1653 "The version of the LDP Protocol which 1654 this session is using. This is the version of 1655 the LDP protocol which has been negotiated 1656 during session initialization." 1657 REFERENCE 1658 "RFC3036, LDP Specification, Section 3.5.3, 1659 Initialization Message." 1660 ::= { mplsLdpSessionEntry 4 } 1662 mplsLdpSessionKeepAliveHoldTimeRem OBJECT-TYPE 1663 SYNTAX TimeInterval 1664 MAX-ACCESS read-only 1665 STATUS current 1666 DESCRIPTION 1667 "The keep alive hold time remaining for 1668 this session." 1669 ::= { mplsLdpSessionEntry 5 } 1671 mplsLdpSessionKeepAliveTime OBJECT-TYPE 1672 SYNTAX Unsigned32 (1..65535) 1673 UNITS "seconds" 1674 MAX-ACCESS read-only 1675 STATUS current 1676 DESCRIPTION 1677 "The negotiated KeepAlive Time which 1678 represents the amount of seconds between 1679 keep alive messages. The 1680 mplsLdpEntityKeepAliveHoldTimer 1681 related to this Session is the 1682 value that was proposed as the 1683 KeepAlive Time for this session. 1685 This value is negotiated during 1686 session initialization between 1687 the entity's proposed value 1688 (i.e. the value configured in 1689 mplsLdpEntityKeepAliveHoldTimer) 1690 and the peer's proposed 1691 KeepAlive Hold Timer value. 1692 This value is the smaller 1693 of the two proposed values." 1694 REFERENCE 1695 "RFC3036, LDP Specification, Section 3.5.3, 1696 Initialization Message." 1697 ::= { mplsLdpSessionEntry 6 } 1699 mplsLdpSessionMaxPduLength OBJECT-TYPE 1700 SYNTAX Unsigned32 (1..65535) 1701 UNITS "octets" 1702 MAX-ACCESS read-only 1703 STATUS current 1704 DESCRIPTION 1705 "The value of maximum allowable length for LDP PDUs for 1706 this session. This value may have been negotiated during 1707 the Session Initialization. This object is related to 1708 the mplsLdpEntityMaxPduLength object. The 1709 mplsLdpEntityMaxPduLength object specifies the requested 1710 LDP PDU length, and this object reflects the negotiated 1711 LDP PDU length between the Entity and 1712 the Peer." 1713 REFERENCE 1714 "RFC3036, LDP Specification, Section 3.5.3, 1715 Initialization Message." 1716 ::= { mplsLdpSessionEntry 7 } 1718 mplsLdpSessionDiscontinuityTime OBJECT-TYPE 1719 SYNTAX TimeStamp 1720 MAX-ACCESS read-only 1721 STATUS current 1722 DESCRIPTION 1723 "The value of sysUpTime on the most recent occasion 1724 at which any one or more of this session's counters 1725 suffered a discontinuity. The relevant counters are 1726 the specific instances associated with this session 1727 of any Counter32 object contained in the 1728 mplsLdpSessionStatsTable. 1730 The initial value of this object is the value of 1731 sysUpTime when the entry was created in this table. 1733 Also, a command generator can distinguish when a session 1734 between a given Entity and Peer goes away and a new 1735 session is established. This value would change and 1736 thus indicate to the command generator that this is a 1737 different session." 1738 ::= { mplsLdpSessionEntry 8 } 1740 -- 1741 -- The MPLS LDP Session Statistics Table 1742 -- 1744 mplsLdpSessionStatsTable OBJECT-TYPE 1745 SYNTAX SEQUENCE OF MplsLdpSessionStatsEntry 1746 MAX-ACCESS not-accessible 1747 STATUS current 1748 DESCRIPTION 1749 "A table of statistics for Sessions between 1750 LDP Entities and LDP Peers. This table AUGMENTS 1751 the mplsLdpPeerTable." 1752 ::= { mplsLdpSessionObjects 4 } 1754 mplsLdpSessionStatsEntry OBJECT-TYPE 1755 SYNTAX MplsLdpSessionStatsEntry 1756 MAX-ACCESS not-accessible 1757 STATUS current 1758 DESCRIPTION 1759 "An entry in this table represents statistical 1760 information on a single session between an LDP 1761 Entity and LDP Peer." 1763 AUGMENTS { mplsLdpPeerEntry } 1764 ::= { mplsLdpSessionStatsTable 1 } 1766 MplsLdpSessionStatsEntry ::= SEQUENCE { 1767 mplsLdpSessionStatsUnknownMesTypeErrors Counter32, 1768 mplsLdpSessionStatsUnknownTlvErrors Counter32 1769 } 1771 mplsLdpSessionStatsUnknownMesTypeErrors OBJECT-TYPE 1772 SYNTAX Counter32 1773 MAX-ACCESS read-only 1774 STATUS current 1775 DESCRIPTION 1776 "This object counts the number of Unknown Message Type 1777 Errors detected by this LSR/LER during this session. 1779 Discontinuities in the value of this counter can occur 1780 at re-initialization of the management system, and at 1781 other times as indicated by the value of 1782 mplsLdpSessionDiscontinuityTime." 1783 ::= { mplsLdpSessionStatsEntry 1 } 1785 mplsLdpSessionStatsUnknownTlvErrors OBJECT-TYPE 1786 SYNTAX Counter32 1787 MAX-ACCESS read-only 1788 STATUS current 1789 DESCRIPTION 1790 "This object counts the number of Unknown TLV Errors 1791 detected by this LSR/LER during this session. 1793 Discontinuities in the value of this counter can occur 1794 at re-initialization of the management system, and at 1795 other times as indicated by the value of 1796 mplsLdpSessionDiscontinuityTime." 1797 ::= { mplsLdpSessionStatsEntry 2 } 1799 -- 1800 -- The MPLS LDP Hello Adjacency Table 1801 -- 1803 mplsLdpHelloAdjacencyObjects OBJECT IDENTIFIER ::= 1804 { mplsLdpSessionObjects 5 } 1806 mplsLdpHelloAdjacencyTable OBJECT-TYPE 1807 SYNTAX SEQUENCE OF MplsLdpHelloAdjacencyEntry 1808 MAX-ACCESS not-accessible 1809 STATUS current 1810 DESCRIPTION 1811 "A table of Hello Adjacencies for Sessions." 1812 ::= { mplsLdpHelloAdjacencyObjects 1 } 1814 mplsLdpHelloAdjacencyEntry OBJECT-TYPE 1815 SYNTAX MplsLdpHelloAdjacencyEntry 1816 MAX-ACCESS not-accessible 1817 STATUS current 1818 DESCRIPTION 1819 "Each row represents a single LDP Hello Adjacency. 1820 An LDP Session can have one or more Hello 1821 Adjacencies." 1822 INDEX { mplsLdpEntityLdpId, 1823 mplsLdpEntityIndex, 1824 mplsLdpPeerLdpId, 1825 mplsLdpHelloAdjacencyIndex } 1826 ::= { mplsLdpHelloAdjacencyTable 1 } 1828 MplsLdpHelloAdjacencyEntry ::= SEQUENCE { 1829 mplsLdpHelloAdjacencyIndex Unsigned32, 1830 mplsLdpHelloAdjacencyHoldTimeRem TimeInterval, 1831 mplsLdpHelloAdjacencyHoldTime Unsigned32, 1832 mplsLdpHelloAdjacencyType INTEGER 1833 } 1835 mplsLdpHelloAdjacencyIndex OBJECT-TYPE 1836 SYNTAX Unsigned32 (1..4294967295) 1837 MAX-ACCESS not-accessible 1838 STATUS current 1839 DESCRIPTION 1840 "An identifier for this specific adjacency." 1841 ::= { mplsLdpHelloAdjacencyEntry 1 } 1843 mplsLdpHelloAdjacencyHoldTimeRem OBJECT-TYPE 1844 SYNTAX TimeInterval 1845 UNITS "seconds" 1846 MAX-ACCESS read-only 1847 STATUS current 1848 DESCRIPTION 1849 "If the value of this object is 65535, 1850 this means that the hold time is infinite 1851 (i.e. wait forever). 1853 Otherwise, the time remaining for 1854 this Hello Adjacency to receive its 1855 next Hello Message. 1857 This interval will change when the 'next' 1858 Hello Message which corresponds to this 1859 Hello Adjacency is received unless it 1860 is infinite." 1861 ::= { mplsLdpHelloAdjacencyEntry 2 } 1863 mplsLdpHelloAdjacencyHoldTime OBJECT-TYPE 1864 SYNTAX Unsigned32 (0..65535) 1865 MAX-ACCESS read-only 1866 STATUS current 1867 DESCRIPTION 1868 "The Hello hold time which is negotiated between 1869 the Entity and the Peer. The entity associated 1870 with this Hello Adjacency issues a proposed 1871 Hello Hold Time value in the 1872 mplsLdpEntityHelloHoldTimer object. The peer 1873 also proposes a value and this object represents 1874 the negotiated value. 1876 A value of 0 means the default, 1877 which is 15 seconds for Link Hellos 1878 and 45 seconds for Targeted Hellos. 1879 A value of 65535 indicates an 1880 infinite hold time." 1881 REFERENCE 1882 "RFC3036, LDP Specification, Section 3.5.2 Hello Message" 1883 ::= { mplsLdpHelloAdjacencyEntry 3 } 1885 mplsLdpHelloAdjacencyType OBJECT-TYPE 1886 SYNTAX INTEGER { 1887 link(1), 1888 targeted(2) 1889 } 1890 MAX-ACCESS read-only 1891 STATUS current 1892 DESCRIPTION 1893 "This adjacency is the result of a 'link' 1894 hello if the value of this object is link(1). 1895 Otherwise, it is a result of a 'targeted' 1896 hello, targeted(2)." 1897 ::= { mplsLdpHelloAdjacencyEntry 4 } 1899 -- 1900 -- Session Label (LSP) Mapping to LSR MIB's 1901 -- In Segment LIB Information. 1902 -- 1904 -- 1905 -- NOTE: the next 2 tables map to the 1906 -- MPLS-LSR-STD-MIB's MplsInSegmentTable 1907 -- and MplsOutSegmentTable. The 1908 -- cross-connect (XC) information is not 1909 -- represented here as it can be gleaned 1910 -- from the MPLS-LSR-STD-MIB. 1911 -- 1913 mplsInSegmentLdpLspTable OBJECT-TYPE 1914 SYNTAX SEQUENCE OF MplsInSegmentLdpLspEntry 1915 MAX-ACCESS not-accessible 1916 STATUS current 1917 DESCRIPTION 1918 "A table of LDP LSP's which 1919 map to the mplsInSegmentTable in the 1920 the MPLS-LSR-STD-MIB module." 1921 ::= { mplsLdpSessionObjects 6 } 1923 mplsInSegmentLdpLspEntry OBJECT-TYPE 1924 SYNTAX MplsInSegmentLdpLspEntry 1925 MAX-ACCESS not-accessible 1926 STATUS current 1927 DESCRIPTION 1928 "An entry in this table represents information 1929 on a single LDP LSP which is represented by 1930 a session's index triple (mplsLdpEntityLdpId, 1931 mplsLdpEntityIndex, mplsLdpPeerLdpId) AND the 1932 index for the mplsInSegmentTable 1933 (mplsInSegmentLdpLspLabelIndex) from the 1934 MPLS-LSR-STD-MIB. 1936 The information contained in a row is read-only." 1937 INDEX { mplsLdpEntityLdpId, 1938 mplsLdpEntityIndex, 1939 mplsLdpPeerLdpId, 1940 mplsInSegmentLdpLspIndex 1941 } 1942 ::= { mplsInSegmentLdpLspTable 1 } 1944 MplsInSegmentLdpLspEntry ::= SEQUENCE { 1945 mplsInSegmentLdpLspIndex MplsIndexType, 1946 mplsInSegmentLdpLspLabelType MplsLdpLabelType, 1947 mplsInSegmentLdpLspType MplsLspType 1948 } 1950 mplsInSegmentLdpLspIndex OBJECT-TYPE 1951 SYNTAX MplsIndexType 1952 MAX-ACCESS not-accessible 1953 STATUS current 1954 DESCRIPTION 1955 "This contains the same value as the 1956 mplsInSegmentIndex in the 1957 MPLS-LSR-STD-MIB's mplsInSegmentTable." 1958 ::= { mplsInSegmentLdpLspEntry 1 } 1960 mplsInSegmentLdpLspLabelType OBJECT-TYPE 1961 SYNTAX MplsLdpLabelType 1962 MAX-ACCESS read-only 1963 STATUS current 1964 DESCRIPTION 1965 "The Layer 2 Label Type." 1966 ::= { mplsInSegmentLdpLspEntry 2 } 1968 mplsInSegmentLdpLspType OBJECT-TYPE 1969 SYNTAX MplsLspType 1970 MAX-ACCESS read-only 1971 STATUS current 1972 DESCRIPTION 1973 "The type of LSP connection." 1974 ::= { mplsInSegmentLdpLspEntry 3 } 1976 -- 1977 -- Session Label (LSP) Mapping to LSR MIB's 1978 -- Out Segment LIB Information. 1979 -- 1981 mplsOutSegmentLdpLspTable OBJECT-TYPE 1982 SYNTAX SEQUENCE OF MplsOutSegmentLdpLspEntry 1983 MAX-ACCESS not-accessible 1984 STATUS current 1985 DESCRIPTION 1986 "A table of LDP LSP's which 1987 map to the mplsOutSegmentTable in the 1988 the MPLS-LSR-STD-MIB." 1990 ::= { mplsLdpSessionObjects 7 } 1992 mplsOutSegmentLdpLspEntry OBJECT-TYPE 1993 SYNTAX MplsOutSegmentLdpLspEntry 1994 MAX-ACCESS not-accessible 1995 STATUS current 1996 DESCRIPTION 1997 "An entry in this table represents information 1998 on a single LDP LSP which is represented by 1999 a session's index triple (mplsLdpEntityLdpId, 2000 mplsLdpEntityIndex, mplsLdpPeerLdpId) AND the 2001 index (mplsOutSegmentLdpLspIndex) 2002 for the mplsOutSegmentTable. 2004 The information contained in a row is read-only." 2005 INDEX { mplsLdpEntityLdpId, 2006 mplsLdpEntityIndex, 2007 mplsLdpPeerLdpId, 2008 mplsOutSegmentLdpLspIndex 2009 } 2010 ::= { mplsOutSegmentLdpLspTable 1 } 2012 MplsOutSegmentLdpLspEntry ::= SEQUENCE { 2013 mplsOutSegmentLdpLspIndex MplsIndexType, 2014 mplsOutSegmentLdpLspLabelType MplsLdpLabelType, 2015 mplsOutSegmentLdpLspType MplsLspType 2016 } 2018 mplsOutSegmentLdpLspIndex OBJECT-TYPE 2019 SYNTAX MplsIndexType 2020 MAX-ACCESS not-accessible 2021 STATUS current 2022 DESCRIPTION 2023 "This contains the same value as the 2024 mplsOutSegmentIndex in the 2025 MPLS-LSR-STD-MIB's mplsOutSegmentTable." 2026 ::= { mplsOutSegmentLdpLspEntry 1 } 2028 mplsOutSegmentLdpLspLabelType OBJECT-TYPE 2029 SYNTAX MplsLdpLabelType 2030 MAX-ACCESS read-only 2031 STATUS current 2032 DESCRIPTION 2033 "The Layer 2 Label Type." 2034 ::= { mplsOutSegmentLdpLspEntry 2 } 2036 mplsOutSegmentLdpLspType OBJECT-TYPE 2037 SYNTAX MplsLspType 2038 MAX-ACCESS read-only 2039 STATUS current 2040 DESCRIPTION 2041 "The type of LSP connection." 2042 ::= { mplsOutSegmentLdpLspEntry 3 } 2044 -- 2045 -- Mpls FEC Table 2046 -- 2048 mplsFecObjects OBJECT IDENTIFIER ::= 2049 { mplsLdpSessionObjects 8 } 2051 mplsFecLastChange OBJECT-TYPE 2052 SYNTAX TimeStamp 2053 MAX-ACCESS read-only 2054 STATUS current 2055 DESCRIPTION 2056 "The value of sysUpTime at the time of the most 2057 recent addition/deletion of an entry 2058 to/from the mplsLdpFectTable or 2059 the most recent change in values to any objects 2060 in the mplsLdpFecTable. 2062 If no such changes have occurred since the last 2063 re-initialization of the local management subsystem, 2064 then this object contains a zero value." 2065 ::= { mplsFecObjects 1 } 2067 mplsFecIndexNext OBJECT-TYPE 2068 SYNTAX IndexIntegerNextFree 2069 MAX-ACCESS read-only 2070 STATUS current 2071 DESCRIPTION 2072 "This object contains an appropriate value to 2073 be used for mplsFecIndex when creating 2074 entries in the mplsFecTable. The value 2075 0 indicates that no unassigned entries are 2076 available." 2077 ::= { mplsFecObjects 2 } 2079 mplsFecTable OBJECT-TYPE 2080 SYNTAX SEQUENCE OF MplsFecEntry 2081 MAX-ACCESS not-accessible 2082 STATUS current 2083 DESCRIPTION 2084 "This table represents the FEC 2085 (Forwarding Equivalence Class) 2086 Information associated with an LSP." 2087 ::= { mplsFecObjects 3 } 2089 mplsFecEntry OBJECT-TYPE 2090 SYNTAX MplsFecEntry 2091 MAX-ACCESS not-accessible 2092 STATUS current 2093 DESCRIPTION 2094 "Each row represents a single FEC Element." 2095 INDEX { mplsFecIndex } 2096 ::= { mplsFecTable 1 } 2098 MplsFecEntry ::= SEQUENCE { 2099 mplsFecIndex IndexInteger, 2100 mplsFecType INTEGER, 2101 mplsFecAddrType InetAddressType, 2102 mplsFecAddr InetAddress, 2103 mplsFecAddrPrefixLength InetAddressPrefixLength, 2104 mplsFecStorageType StorageType, 2105 mplsFecRowStatus RowStatus 2106 } 2108 mplsFecIndex OBJECT-TYPE 2109 SYNTAX IndexInteger 2110 MAX-ACCESS not-accessible 2111 STATUS current 2112 DESCRIPTION 2113 "The index which uniquely identifies this entry." 2114 ::= { mplsFecEntry 1 } 2116 mplsFecType OBJECT-TYPE 2117 SYNTAX INTEGER { 2118 prefix(1), 2119 hostAddress(2) 2120 } 2121 MAX-ACCESS read-create 2122 STATUS current 2123 DESCRIPTION 2124 "The type of the FEC. If the value of this object 2125 is 'prefix(1)' then the FEC type described by this 2126 row is an address prefix. 2128 If the value of this object is 'hostAddress(2)' then 2129 the FEC type described by this row is a host address." 2130 REFERENCE 2131 "RFC3036, Section 3.4.1. FEC TLV." 2132 ::= { mplsFecEntry 2 } 2134 mplsFecAddrType OBJECT-TYPE 2135 SYNTAX InetAddressType 2136 MAX-ACCESS read-create 2137 STATUS current 2138 DESCRIPTION 2139 "The value of this object is the type of the 2140 Internet address. The value of this object, 2141 decides how the value of the mplsFecAddr object 2142 is interpreted." 2143 REFERENCE 2144 "RFC3036, Section 3.4.1. FEC TLV." 2145 ::= { mplsFecEntry 4 } 2147 mplsFecAddr OBJECT-TYPE 2148 SYNTAX InetAddress 2149 MAX-ACCESS read-create 2150 STATUS current 2151 DESCRIPTION 2152 "The value of this object is interpreted based 2153 on the value of the 'mplsFecAddrType' object. 2155 This address is then further interpretted as 2156 an being used with the address prefix, 2157 or as the host address. This further interpretation 2158 is indicated by the 'mplsFecType' object. 2159 In other words, the FEC element is populated 2160 according to the Prefix FEC Element value encoding, or 2161 the Host Address FEC Element encoding." 2162 REFERENCE 2163 "RFC3036, Section 3.4.1 FEC TLV." 2164 ::= { mplsFecEntry 5 } 2166 mplsFecAddrPrefixLength OBJECT-TYPE 2167 SYNTAX InetAddressPrefixLength 2168 MAX-ACCESS read-create 2169 STATUS current 2170 DESCRIPTION 2171 "If the value of the 'mplsFecType' is 'hostAddress(2)' 2172 then this object is undefined. 2174 If the value of 'mplsFecType' is 'prefix(1)' 2175 then the value of this object is the length in 2176 bits of the address prefix represented by 2177 'mplsFecAddr', or zero. If the value of this 2178 object is zero, this indicates that the 2179 prefix matches all addresses. In this case the 2180 address prefix MUST also be zero (i.e. 'mplsFecAddr' 2181 should have the value of zero.)" 2182 REFERENCE 2183 "RFC3036, Section 3.4.1. FEC TLV." 2184 DEFVAL { 0 } 2185 ::= { mplsFecEntry 3 } 2187 mplsFecStorageType OBJECT-TYPE 2188 SYNTAX StorageType 2189 MAX-ACCESS read-create 2190 STATUS current 2191 DESCRIPTION 2192 "The storage type for this conceptual row. 2193 Conceptual rows having the value 'permanent(4)' 2194 need not allow write-access to any columnar 2195 objects in the row." 2196 DEFVAL { nonVolatile } 2197 ::= { mplsFecEntry 6 } 2199 mplsFecRowStatus OBJECT-TYPE 2200 SYNTAX RowStatus 2201 MAX-ACCESS read-create 2202 STATUS current 2203 DESCRIPTION 2204 "The status of this conceptual row. If the value of this 2205 object is 'active(1)', then none of the writable objects 2206 of this entry can be modified, except to set this object 2207 to 'destroy(6)'. 2209 NOTE: if this row is being referenced by any entry in 2210 the mplsLdpLspFecTable, then a request to destroy 2211 this row, will result in an inconsistentValue error." 2212 ::= { mplsFecEntry 7 } 2214 -- 2215 -- LDP LSP FEC Table 2216 -- 2218 mplsLdpLspFecLastChange OBJECT-TYPE 2219 SYNTAX TimeStamp 2220 MAX-ACCESS read-only 2221 STATUS current 2222 DESCRIPTION 2223 "The value of sysUpTime at the time of the most 2224 recent addition/deletion of an entry 2225 to/from the mplsLdpLspFecTable or 2226 the most recent change in values to any objects in the 2227 mplsLdpLspFecTable. 2229 If no such changes have occurred since the last 2230 re-initialization of the local management subsystem, 2231 then this object contains a zero value." 2232 ::= { mplsLdpSessionObjects 9 } 2234 mplsLdpLspFecTable OBJECT-TYPE 2235 SYNTAX SEQUENCE OF MplsLdpLspFecEntry 2236 MAX-ACCESS not-accessible 2237 STATUS current 2238 DESCRIPTION 2239 "A table which shows the relationship between 2240 LDP LSPs and FECs. Each row represents 2241 a single LDP LSP to FEC association." 2242 ::= { mplsLdpSessionObjects 10 } 2244 mplsLdpLspFecEntry OBJECT-TYPE 2245 SYNTAX MplsLdpLspFecEntry 2246 MAX-ACCESS not-accessible 2247 STATUS current 2248 DESCRIPTION 2249 "An entry represents a LDP LSP 2250 to FEC association." 2251 INDEX { mplsLdpEntityLdpId, 2252 mplsLdpEntityIndex, 2253 mplsLdpPeerLdpId, 2254 mplsLdpLspFecSegment, 2255 mplsLdpLspFecSegmentIndex, 2256 mplsLdpLspFecIndex 2257 } 2258 ::= { mplsLdpLspFecTable 1 } 2260 MplsLdpLspFecEntry ::= SEQUENCE { 2261 mplsLdpLspFecSegment INTEGER, 2262 mplsLdpLspFecSegmentIndex MplsIndexType, 2263 mplsLdpLspFecIndex IndexInteger, 2264 mplsLdpLspFecStorageType StorageType, 2265 mplsLdpLspFecRowStatus RowStatus 2266 } 2268 mplsLdpLspFecSegment OBJECT-TYPE 2269 SYNTAX INTEGER { 2270 inSegment(1), 2271 outSegment(2) 2272 } 2273 MAX-ACCESS not-accessible 2274 STATUS current 2275 DESCRIPTION 2276 "If the value is inSegment(1), then this 2277 indicates that the following index, 2278 mplsLdpLspFecSegmentIndex, contains the same 2279 value as the mplsInSegmentLdpLspIndex. 2281 Otherwise, if the value of this object is 2282 outSegment(2), then this 2283 indicates that following index, 2284 mplsLdpLspFecSegmentIndex, contains the same 2285 value as the mplsOutSegmentLdpLspIndex." 2286 ::= { mplsLdpLspFecEntry 1 } 2288 mplsLdpLspFecSegmentIndex OBJECT-TYPE 2289 SYNTAX MplsIndexType 2290 MAX-ACCESS not-accessible 2291 STATUS current 2292 DESCRIPTION 2293 "This index is interpretted by using the value 2294 of the mplsLdpLspFecSegment. 2296 If the mplsLdpLspFecSegment is inSegment(1), 2297 then this index has the same value as 2298 mplsInSegmentLdpLspIndex. 2300 If the mplsLdpLspFecSegment is outSegment(2), 2301 then this index has the same value as 2302 mplsOutSegmentLdpLspIndex." 2303 ::= { mplsLdpLspFecEntry 2 } 2305 mplsLdpLspFecIndex OBJECT-TYPE 2306 SYNTAX IndexInteger 2307 MAX-ACCESS not-accessible 2308 STATUS current 2309 DESCRIPTION 2310 "This index identifies the FEC entry in the 2311 mplsFecTable associated with this session. 2312 In other words, the value of this index 2313 is the same as the value of the mplsFecIndex 2314 that denotes the FEC associated with this 2315 Session." 2316 ::= { mplsLdpLspFecEntry 3 } 2318 mplsLdpLspFecStorageType OBJECT-TYPE 2319 SYNTAX StorageType 2320 MAX-ACCESS read-create 2321 STATUS current 2322 DESCRIPTION 2323 "The storage type for this conceptual row. 2324 Conceptual rows having the value 'permanent(4)' 2325 need not allow write-access to any columnar 2326 objects in the row." 2327 DEFVAL { nonVolatile } 2328 ::= { mplsLdpLspFecEntry 4 } 2330 mplsLdpLspFecRowStatus OBJECT-TYPE 2331 SYNTAX RowStatus 2332 MAX-ACCESS read-create 2333 STATUS current 2334 DESCRIPTION 2335 "The status of this conceptual row. If the 2336 value of this object is 'active(1)', then 2337 none of the writable objects of this entry 2338 can be modified. 2340 The Agent should delete this row when 2341 the session ceases to exist. If an 2342 operator wants to associate the session with 2343 a different FEC, the recommended 2344 procedure is (as described in detail in the section 2345 entitled, 'Changing Values After Session 2346 Establishment', and again described in the 2347 DESCRIPTION clause of the 2348 mplsLdpEntityAdminStatus object) 2349 is to set the mplsLdpEntityAdminStatus to 2350 down, thereby explicitly causing a session 2351 to be torn down. This will also 2352 cause this entry to be deleted. 2354 Then, set the mplsLdpEntityAdminStatus 2355 to enable which enables a new session to be initiated. 2356 Once the session is initiated, an entry may be 2357 added to this table to associate the new session 2358 with a FEC." 2359 ::= { mplsLdpLspFecEntry 5 } 2361 -- 2362 -- Address Message/Address Withdraw Message Information 2363 -- 2364 -- This information is associated with a specific Session 2365 -- because Label Address Messages are sent after session 2366 -- initialization has taken place. 2367 -- 2369 mplsLdpSessionPeerAddrTable OBJECT-TYPE 2370 SYNTAX SEQUENCE OF MplsLdpSessionPeerAddrEntry 2371 MAX-ACCESS not-accessible 2372 STATUS current 2373 DESCRIPTION 2374 "This table 'extends' the mplsLdpSessionTable. 2375 This table is used to store Label Address Information 2376 from Label Address Messages received by this LSR from 2377 Peers. This table is read-only and should be updated 2378 when Label Withdraw Address Messages are received, i.e. 2379 Rows should be deleted as apropriate. 2381 NOTE: since more than one address may be contained 2382 in a Label Address Message, this table 'sparse augments', 2383 the mplsLdpSessionTable's information." 2384 ::= { mplsLdpSessionObjects 11 } 2386 mplsLdpSessionPeerAddrEntry OBJECT-TYPE 2387 SYNTAX MplsLdpSessionPeerAddrEntry 2388 MAX-ACCESS not-accessible 2389 STATUS current 2390 DESCRIPTION 2391 "An entry in this table represents information on 2392 a session's single next hop address which was 2393 advertised in an Address Message from the LDP peer. 2395 The information contained in a row is read-only." 2396 INDEX { mplsLdpEntityLdpId, 2397 mplsLdpEntityIndex, 2398 mplsLdpPeerLdpId, 2399 mplsLdpSessionPeerAddrIndex 2400 } 2401 ::= { mplsLdpSessionPeerAddrTable 1 } 2403 MplsLdpSessionPeerAddrEntry ::= SEQUENCE { 2404 mplsLdpSessionPeerAddrIndex Unsigned32, 2405 mplsLdpSessionPeerNextHopAddrType InetAddressType, 2406 mplsLdpSessionPeerNextHopAddr InetAddress 2407 } 2409 mplsLdpSessionPeerAddrIndex OBJECT-TYPE 2410 SYNTAX Unsigned32 (1..4294967295) 2411 MAX-ACCESS not-accessible 2412 STATUS current 2413 DESCRIPTION 2414 "An index which uniquely identifies this entry within 2415 a given session." 2416 ::= { mplsLdpSessionPeerAddrEntry 1 } 2418 mplsLdpSessionPeerNextHopAddrType OBJECT-TYPE 2419 SYNTAX InetAddressType 2420 MAX-ACCESS read-only 2421 STATUS current 2422 DESCRIPTION 2423 "The internetwork layer address type of this Next Hop 2424 Address as specified in the Label Address Message 2425 associated with this Session. The value of this 2426 object indicates how to interpret the value of 2427 mplsLdpSessionPeerNextHopAddr." 2428 ::= { mplsLdpSessionPeerAddrEntry 2 } 2430 mplsLdpSessionPeerNextHopAddr OBJECT-TYPE 2431 SYNTAX InetAddress 2432 MAX-ACCESS read-only 2433 STATUS current 2434 DESCRIPTION 2435 "The next hop address. The type of this address 2436 is specified by the value of the 2437 mplsLdpSessionPeerNextHopAddrType." 2438 REFERENCE 2439 "RFC3036, Section 2.7. LDP Identifiers 2440 and Next Hop Addresses" 2442 ::= { mplsLdpSessionPeerAddrEntry 3 } 2444 --- 2445 --- Notifications 2446 --- 2448 mplsLdpInitSessionThresholdExceeded NOTIFICATION-TYPE 2449 OBJECTS { 2450 mplsLdpEntityInitSessionThreshold 2451 } 2452 STATUS current 2453 DESCRIPTION 2454 "This notification is generated when the value of 2455 the 'mplsLdpEntityInitSessionThreshold' object 2456 is not zero, and the number of Session 2457 Initialization messages exceeds the value 2458 of the 'mplsLdpEntityInitSessionThreshold' object." 2459 ::= { mplsLdpNotifications 1 } 2461 mplsLdpPathVectorLimitMismatch NOTIFICATION-TYPE 2462 OBJECTS { 2463 mplsLdpEntityPathVectorLimit, 2464 mplsLdpPeerPathVectorLimit 2465 } 2466 STATUS current 2467 DESCRIPTION 2468 "This notification is sent when the 2469 'mplsLdpEntityPathVectorLimit' does NOT match 2470 the value of the 'mplsLdpPeerPathVectorLimit' for 2471 a specific Entity." 2472 REFERENCE 2473 "RFC3036, LDP Specification, Section 3.5.3." 2474 ::= { mplsLdpNotifications 2 } 2476 mplsLdpSessionUp NOTIFICATION-TYPE 2477 OBJECTS { 2478 mplsLdpSessionState, 2479 mplsLdpSessionDiscontinuityTime, 2480 mplsLdpSessionStatsUnknownMesTypeErrors, 2481 mplsLdpSessionStatsUnknownTlvErrors 2482 } 2483 STATUS current 2484 DESCRIPTION 2485 "If this notification is sent when the 2486 value of 'mplsLdpSessionState' enters 2487 the 'operational(5)' state." 2488 ::= { mplsLdpNotifications 3 } 2490 mplsLdpSessionDown NOTIFICATION-TYPE 2491 OBJECTS { 2492 mplsLdpSessionState, 2493 mplsLdpSessionDiscontinuityTime, 2494 mplsLdpSessionStatsUnknownMesTypeErrors, 2495 mplsLdpSessionStatsUnknownTlvErrors 2497 } 2498 STATUS current 2499 DESCRIPTION 2500 "This notification is sent when the 2501 the value of 'mplsLdpSessionState' leaves 2502 the 'operational(5)' state." 2503 ::= { mplsLdpNotifications 4 } 2505 --**************************************************************** 2506 -- Module Conformance Statement 2507 --**************************************************************** 2509 mplsLdpGroups 2510 OBJECT IDENTIFIER ::= { mplsLdpConformance 1 } 2512 mplsLdpCompliances 2513 OBJECT IDENTIFIER ::= { mplsLdpConformance 2 } 2515 -- 2516 -- Full Compliance 2517 -- 2519 mplsLdpModuleFullCompliance MODULE-COMPLIANCE 2520 STATUS current 2521 DESCRIPTION 2522 "The Module is implemented with support 2523 for read-create and read-write. In other 2524 words, both monitoring and configuration 2525 are available when using this MODULE-COMPLIANCE." 2527 MODULE -- this module 2528 MANDATORY-GROUPS { mplsLdpGeneralGroup, 2529 mplsLdpNotificationsGroup 2530 } 2532 GROUP mplsLdpLspGroup 2533 DESCRIPTION 2534 "This group must be supported if the LSR MIB is 2535 implemented, specifically the mplsInSegmentTable, 2536 the mplsOutSegmentTable or the mplsXCTable." 2538 OBJECT mplsLdpEntityTargetPeerAddrType 2539 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2540 DESCRIPTION 2541 "An implementation is only required to support 2542 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2544 OBJECT mplsLdpEntityTargetPeerAddr 2545 SYNTAX InetAddress (SIZE(0|4|16)) 2546 DESCRIPTION 2547 "An implementation is only required to support IPv4 and 2548 globally unique IPv6 addresses." 2550 OBJECT mplsLdpEntityRowStatus 2551 SYNTAX RowStatus { active(1) } 2552 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 2553 DESCRIPTION 2554 "Support for createAndWait and notInService is not 2555 required." 2557 OBJECT mplsFecAddrType 2558 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2559 DESCRIPTION 2560 "An implementation is only required to support 2561 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2563 OBJECT mplsFecAddr 2564 SYNTAX InetAddress (SIZE(0|4|16)) 2565 DESCRIPTION 2566 "An implementation is only required to support IPv4 and 2567 globally unique IPv6 addresses." 2569 OBJECT mplsFecRowStatus 2570 SYNTAX RowStatus { active(1) } 2571 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 2572 DESCRIPTION 2573 "Support for createAndWait and notInService is not 2574 required." 2576 OBJECT mplsLdpLspFecRowStatus 2577 SYNTAX RowStatus { active(1) } 2578 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 2579 DESCRIPTION 2580 "Support for createAndWait and notInService is not 2581 required." 2583 OBJECT mplsLdpSessionPeerNextHopAddrType 2584 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2585 DESCRIPTION 2586 "An implementation is only required to support 2587 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2589 OBJECT mplsLdpSessionPeerNextHopAddr 2590 SYNTAX InetAddress (SIZE(0|4|16)) 2591 DESCRIPTION 2592 "An implementation is only required to support IPv4 2593 and globally unique IPv6 addresses." 2595 ::= { mplsLdpCompliances 1 } 2597 -- 2598 -- Read-Only Compliance 2599 -- 2601 mplsLdpModuleReadOnlyCompliance MODULE-COMPLIANCE 2602 STATUS current 2603 DESCRIPTION 2604 "The Module is implemented with support 2605 for read-only. In other words, only monitoring 2606 is available by implementing this MODULE-COMPLIANCE." 2608 MODULE -- this module 2609 MANDATORY-GROUPS { mplsLdpGeneralGroup, 2610 mplsLdpNotificationsGroup 2611 } 2613 GROUP mplsLdpLspGroup 2614 DESCRIPTION 2615 "This group must be supported if the LSR MIB is 2616 implemented, specifically the mplsInSegmentTable, 2617 the mplsOutSegmentTable or the mplsXCTable." 2619 OBJECT mplsLdpEntityProtocolVersion 2620 MIN-ACCESS read-only 2621 DESCRIPTION 2622 "Write access is not required." 2624 OBJECT mplsLdpEntityAdminStatus 2625 MIN-ACCESS read-only 2626 DESCRIPTION 2627 "Write access is not required." 2629 OBJECT mplsLdpEntityTcpDscPort 2630 MIN-ACCESS read-only 2631 DESCRIPTION 2632 "Write access is not required." 2634 OBJECT mplsLdpEntityUdpDscPort 2635 MIN-ACCESS read-only 2636 DESCRIPTION 2637 "Write access is not required." 2639 OBJECT mplsLdpEntityMaxPduLength 2640 MIN-ACCESS read-only 2641 DESCRIPTION 2642 "Write access is not required." 2644 OBJECT mplsLdpEntityKeepAliveHoldTimer 2645 MIN-ACCESS read-only 2646 DESCRIPTION 2647 "Write access is not required." 2649 OBJECT mplsLdpEntityHelloHoldTimer 2650 MIN-ACCESS read-only 2651 DESCRIPTION 2652 "Write access is not required." 2654 OBJECT mplsLdpEntityInitSessionThreshold 2655 MIN-ACCESS read-only 2656 DESCRIPTION 2657 "Write access is not required." 2659 OBJECT mplsLdpEntityLabelDistMethod 2660 MIN-ACCESS read-only 2661 DESCRIPTION 2662 "Write access is not required." 2664 OBJECT mplsLdpEntityLabelRetentionMode 2665 MIN-ACCESS read-only 2666 DESCRIPTION 2667 "Write access is not required." 2669 OBJECT mplsLdpEntityPathVectorLimit 2670 MIN-ACCESS read-only 2671 DESCRIPTION 2672 "Write access is not required." 2674 OBJECT mplsLdpEntityHopCountLimit 2675 MIN-ACCESS read-only 2676 DESCRIPTION 2677 "Write access is not required." 2679 OBJECT mplsLdpEntityTransportAddrKind 2680 MIN-ACCESS read-only 2681 DESCRIPTION 2682 "Write access is not required." 2684 OBJECT mplsLdpEntityTargetPeer 2685 MIN-ACCESS read-only 2686 DESCRIPTION 2687 "Write access is not required." 2689 OBJECT mplsLdpEntityTargetPeerAddrType 2690 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2691 MIN-ACCESS read-only 2692 DESCRIPTION 2693 "Write access is not required. 2694 An implementation is only required to support 2695 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2697 OBJECT mplsLdpEntityTargetPeerAddr 2698 SYNTAX InetAddress (SIZE(0|4|16)) 2699 MIN-ACCESS read-only 2700 DESCRIPTION 2701 "Write access is not required. 2702 An implementation is only required to support IPv4 and 2703 globally unique IPv6 addresses." 2705 OBJECT mplsLdpEntityLabelType 2706 MIN-ACCESS read-only 2707 DESCRIPTION 2708 "Write access is not required." 2710 OBJECT mplsLdpEntityStorageType 2711 MIN-ACCESS read-only 2712 DESCRIPTION 2713 "Write access is not required." 2715 OBJECT mplsLdpEntityRowStatus 2716 SYNTAX RowStatus { active(1) } 2717 MIN-ACCESS read-only 2718 DESCRIPTION 2719 "Write access is not required, and active is the 2720 only status that needs to be supported." 2722 OBJECT mplsFecType 2723 MIN-ACCESS read-only 2724 DESCRIPTION 2725 "Write access is not required." 2727 OBJECT mplsFecAddrPrefixLength 2728 MIN-ACCESS read-only 2729 DESCRIPTION 2730 "Write access is not required." 2732 OBJECT mplsFecAddrType 2733 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2734 MIN-ACCESS read-only 2735 DESCRIPTION 2736 "Write access is not required. 2737 An implementation is only required to support 2738 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2740 OBJECT mplsFecAddr 2741 SYNTAX InetAddress (SIZE(0|4|16)) 2742 MIN-ACCESS read-only 2743 DESCRIPTION 2744 "Write access is not required. 2745 An implementation is only required to support IPv4 and 2746 globally unique IPv6 addresses." 2748 OBJECT mplsFecStorageType 2749 MIN-ACCESS read-only 2750 DESCRIPTION 2751 "Write access is not required." 2753 OBJECT mplsFecRowStatus 2754 SYNTAX RowStatus { active(1) } 2755 MIN-ACCESS read-only 2756 DESCRIPTION 2757 "Write access is not required, and active is the 2758 only status that needs to be supported." 2760 OBJECT mplsLdpLspFecStorageType 2761 MIN-ACCESS read-only 2762 DESCRIPTION 2763 "Write access is not required." 2765 OBJECT mplsLdpLspFecRowStatus 2766 SYNTAX RowStatus { active(1) } 2767 MIN-ACCESS read-only 2768 DESCRIPTION 2769 "Write access is not required, and active is the 2770 only status that needs to be supported." 2772 OBJECT mplsLdpSessionPeerNextHopAddrType 2773 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2774 DESCRIPTION 2775 "An implementation is only required to support 2776 'unknown(0)', IPv4 and globally unique IPv6 addresses." 2778 OBJECT mplsLdpSessionPeerNextHopAddr 2779 SYNTAX InetAddress (SIZE(0|4|16)) 2780 DESCRIPTION 2781 "An implementation is only required to support IPv4 2782 and globally unique IPv6 addresses." 2784 ::= { mplsLdpCompliances 2 } 2786 -- units of conformance 2788 mplsLdpGeneralGroup OBJECT-GROUP 2789 OBJECTS { 2790 mplsLdpLsrId, 2791 mplsLdpLsrLoopDetectionCapable, 2792 mplsLdpEntityLastChange, 2793 mplsLdpEntityIndexNext, 2794 mplsLdpEntityProtocolVersion, 2795 mplsLdpEntityAdminStatus, 2796 mplsLdpEntityOperStatus, 2797 mplsLdpEntityTcpDscPort, 2798 mplsLdpEntityUdpDscPort, 2799 mplsLdpEntityMaxPduLength, 2800 mplsLdpEntityKeepAliveHoldTimer, 2801 mplsLdpEntityHelloHoldTimer, 2802 mplsLdpEntityInitSessionThreshold, 2803 mplsLdpEntityLabelDistMethod, 2804 mplsLdpEntityLabelRetentionMode, 2805 mplsLdpEntityPathVectorLimit, 2806 mplsLdpEntityHopCountLimit, 2807 mplsLdpEntityTransportAddrKind, 2808 mplsLdpEntityTargetPeer, 2809 mplsLdpEntityTargetPeerAddrType, 2810 mplsLdpEntityTargetPeerAddr, 2811 mplsLdpEntityLabelType, 2812 mplsLdpEntityDiscontinuityTime, 2813 mplsLdpEntityStorageType, 2814 mplsLdpEntityRowStatus, 2815 mplsLdpEntityStatsSessionAttempts, 2816 mplsLdpEntityStatsSessionRejectedNoHelloErrors, 2817 mplsLdpEntityStatsSessionRejectedAdErrors, 2818 mplsLdpEntityStatsSessionRejectedMaxPduErrors, 2819 mplsLdpEntityStatsSessionRejectedLRErrors, 2820 mplsLdpEntityStatsBadLdpIdentifierErrors, 2821 mplsLdpEntityStatsBadPduLengthErrors, 2822 mplsLdpEntityStatsBadMessageLengthErrors, 2823 mplsLdpEntityStatsBadTlvLengthErrors, 2824 mplsLdpEntityStatsMalformedTlvValueErrors, 2825 mplsLdpEntityStatsKeepAliveTimerExpErrors, 2826 mplsLdpEntityStatsShutdownReceivedNotifications, 2827 mplsLdpEntityStatsShutdownSentNotifications, 2828 mplsLdpPeerLastChange, 2829 mplsLdpPeerLabelDistMethod, 2830 mplsLdpPeerPathVectorLimit, 2831 mplsLdpPeerTransportAddrType, 2832 mplsLdpPeerTransportAddr, 2833 mplsLdpHelloAdjacencyHoldTimeRem, 2834 mplsLdpHelloAdjacencyHoldTime, 2835 mplsLdpHelloAdjacencyType, 2836 mplsLdpSessionStateLastChange, 2837 mplsLdpSessionState, 2838 mplsLdpSessionRole, 2839 mplsLdpSessionProtocolVersion, 2840 mplsLdpSessionKeepAliveHoldTimeRem, 2841 mplsLdpSessionKeepAliveTime, 2842 mplsLdpSessionMaxPduLength, 2843 mplsLdpSessionDiscontinuityTime, 2844 mplsLdpSessionStatsUnknownMesTypeErrors, 2845 mplsLdpSessionStatsUnknownTlvErrors, 2846 mplsLdpSessionPeerNextHopAddrType, 2847 mplsLdpSessionPeerNextHopAddr, 2848 mplsFecLastChange, 2849 mplsFecIndexNext, 2850 mplsFecType, 2851 mplsFecAddrType, 2852 mplsFecAddr, 2853 mplsFecAddrPrefixLength, 2854 mplsFecStorageType, 2855 mplsFecRowStatus 2856 } 2857 STATUS current 2858 DESCRIPTION 2859 "Objects that apply to all MPLS LDP implementations." 2860 ::= { mplsLdpGroups 1 } 2862 mplsLdpLspGroup OBJECT-GROUP 2863 OBJECTS { 2864 mplsInSegmentLdpLspLabelType, 2865 mplsInSegmentLdpLspType, 2866 mplsOutSegmentLdpLspLabelType, 2867 mplsOutSegmentLdpLspType, 2868 mplsLdpLspFecLastChange, 2869 mplsLdpLspFecStorageType, 2870 mplsLdpLspFecRowStatus 2871 } 2872 STATUS current 2873 DESCRIPTION 2874 "These objects are for LDP implementations 2875 which interface to the Label Information Base (LIB) 2876 in the MPLS-LSR-STD-MIB. The LIB is 2877 represented in the mplsInSegmentTable, 2878 mplsOutSegmentTable and mplsXCTable." 2879 ::= { mplsLdpGroups 2 } 2881 mplsLdpNotificationsGroup NOTIFICATION-GROUP 2882 NOTIFICATIONS { mplsLdpInitSessionThresholdExceeded, 2883 mplsLdpPathVectorLimitMismatch, 2884 mplsLdpSessionUp, 2885 mplsLdpSessionDown 2886 } 2887 STATUS current 2888 DESCRIPTION 2889 "The notification for an MPLS LDP implemention." 2891 ::= { mplsLdpGroups 3 } 2893 END 2895 4.1. The MPLS-LDP-ATM-STD-MIB Module 2897 This MIB Module MUST be supported if LDP uses ATM as the Layer 2 2898 medium. There are three tables in this MIB Module. Two tables are 2899 for configuring LDP to use ATM. These tables are the 2900 mplsLdpEntityAtmTable and the mplsLdpEntityAtmLRTable. The third 2901 table is the mplsLdpAtmSessionTable which is a read-only table. 2903 4.1.1. The LDP Entity ATM Table 2905 The mplsLdpEntityAtmTable provides a way to configure information 2906 which would be contained in the "Optional Parameter" portion of an 2907 LDP PDU Initialization Message. 2909 4.1.2. The LDP Entity ATM Label Range Table 2911 The mplsLdpEntityAtmLRTable provides a way to configure information 2912 which would be contained in the "ATM Label Range Components" portion 2913 of an LDP PDU Intialization Message, see [RFC3035] and [RFC3036]. 2915 4.1.3. The LDP ATM Session Table 2917 The MPLS LDP ATM Session Table is a read-only table which contains 2918 session information specific to ATM. 2920 MPLS-LDP-ATM-STD-MIB DEFINITIONS ::= BEGIN 2922 IMPORTS 2923 OBJECT-TYPE, MODULE-IDENTITY, 2924 Unsigned32 2925 FROM SNMPv2-SMI 2926 MODULE-COMPLIANCE, OBJECT-GROUP 2927 FROM SNMPv2-CONF 2929 RowStatus, 2930 StorageType 2931 FROM SNMPv2-TC 2933 InterfaceIndexOrZero 2934 FROM IF-MIB 2936 AtmVpIdentifier 2937 FROM ATM-TC-MIB 2939 mplsStdMIB, 2940 MplsAtmVcIdentifier 2941 FROM MPLS-TC-STD-MIB 2943 mplsLdpEntityLdpId, 2944 mplsLdpEntityIndex, 2945 mplsLdpPeerLdpId 2946 FROM MPLS-LDP-STD-MIB 2948 ; 2950 mplsLdpAtmStdMIB MODULE-IDENTITY 2951 LAST-UPDATED "200311181200Z" -- 18 November 2003 2952 ORGANIZATION "Multiprotocol Label Switching (mpls) 2953 Working Group" 2954 CONTACT-INFO 2955 "Joan Cucchiara (jcucchiara@artel.com) 2956 Artel 2958 Hans Sjostrand (hans@ipunplugged.com) 2959 ipUnplugged 2961 James V. Luciani (james_luciani@mindspring.com) 2962 Marconi Communications, Inc. 2964 Working Group Chairs: 2965 George Swallow, email: swallow@cisco.com 2966 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 "200311181200Z" -- 18 November 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." 3021 ::= { mplsLdpEntityAtmObjects 1 } 3023 mplsLdpEntityAtmEntry OBJECT-TYPE 3024 SYNTAX MplsLdpEntityAtmEntry 3025 MAX-ACCESS not-accessible 3026 STATUS current 3027 DESCRIPTION 3028 "An entry in this table represents the ATM parameters 3029 and ATM information for this LDP entity." 3030 INDEX { mplsLdpEntityLdpId, 3031 mplsLdpEntityIndex 3032 } 3033 ::= { mplsLdpEntityAtmTable 1 } 3035 MplsLdpEntityAtmEntry ::= SEQUENCE { 3036 mplsLdpEntityAtmIfIndexOrZero InterfaceIndexOrZero, 3037 mplsLdpEntityAtmMergeCap INTEGER, 3038 mplsLdpEntityAtmLRComponents Unsigned32, 3039 mplsLdpEntityAtmVcDirectionality INTEGER, 3040 mplsLdpEntityAtmLsrConnectivity INTEGER, 3041 mplsLdpEntityAtmDefaultControlVpi AtmVpIdentifier, 3042 mplsLdpEntityAtmDefaultControlVci MplsAtmVcIdentifier, 3043 mplsLdpEntityAtmUnlabTrafVpi AtmVpIdentifier, 3044 mplsLdpEntityAtmUnlabTrafVci MplsAtmVcIdentifier, 3045 mplsLdpEntityAtmStorageType StorageType, 3046 mplsLdpEntityAtmRowStatus RowStatus 3047 } 3049 mplsLdpEntityAtmIfIndexOrZero OBJECT-TYPE 3050 SYNTAX InterfaceIndexOrZero 3051 MAX-ACCESS read-create 3052 STATUS current 3053 DESCRIPTION 3054 "This value represents either the InterfaceIndex 3055 or 0 (zero). The value of zero means that the 3056 InterfaceIndex is not known. 3058 However, if the InterfaceIndex is known, then it must 3059 be represented by this value. 3061 If an InterfaceIndex becomes known, then the 3062 network management entity (e.g. SNMP agent) responsible 3063 for this object MUST change the value from 0 (zero) to the 3064 value of the InterfaceIndex. If an ATM Label is 3065 being used in forwarding data, then the value of this 3066 object MUST be the InterfaceIndex." 3067 ::= { mplsLdpEntityAtmEntry 1 } 3069 mplsLdpEntityAtmMergeCap OBJECT-TYPE 3070 SYNTAX INTEGER { 3071 notSupported(0), 3072 vpMerge(1), 3073 vcMerge(2), 3074 vpAndVcMerge(3) 3075 } 3076 MAX-ACCESS read-create 3077 STATUS current 3078 DESCRIPTION 3079 "Denotes the Merge Capability of this Entity. 3080 This is the EXACT value for the ATM Session 3081 Parameter, field M (for ATM Merge Capabilities). 3082 The ATM Session Parameter is an optional 3083 parameter in the Initialization Message. 3085 The description from rfc3036.txt is: 3087 'M, ATM Merge Capabilities 3088 Specifies the merge capabilities of an ATM switch. The 3089 following values are supported in this version of the 3090 specification: 3092 Value Meaning 3094 0 Merge not supported 3095 1 VP Merge supported 3096 2 VC Merge supported 3097 3 VP & VC Merge supported 3099 If the merge capabilities of the LSRs differ, then: 3100 - Non-merge and VC-merge LSRs may freely interoperate. 3102 - The interoperability of VP-merge-capable switches 3103 with non-VP-merge-capable switches is a subject 3104 for future study. When the LSRs differ on the 3105 use of VP-merge, the session is established, 3106 but VP merge is not used.' 3108 Please refer to the following reference for a 3109 complete description of this feature." 3111 REFERENCE 3112 "RFC3036, LDP Specification, Section 3.5.3 3113 Initialization Message." 3114 ::= { mplsLdpEntityAtmEntry 2 } 3116 mplsLdpEntityAtmLRComponents OBJECT-TYPE 3117 SYNTAX Unsigned32 (1..65535) 3118 MAX-ACCESS read-only 3119 STATUS current 3120 DESCRIPTION 3121 "Number of Label Range Components in the Initialization 3122 message. This also represents the number of entries 3123 in the mplsLdpEntityAtmLRTable which correspond 3124 to this entry. 3126 This is the EXACT value for the ATM Session Parameter, 3127 field N (for Number of label range components). 3128 The ATM Session Parameter is an optional parameter 3129 in the Initialization Message. 3131 The description from rfc3036.txt is: 3133 'N, Number of label range components 3134 Specifies the number of ATM Label Range 3135 Components included in the TLV.' 3137 Please refer to the following reference for 3138 a complete description of this feature." 3139 REFERENCE 3140 "RFC3036, LDP Specification, Section 3.5.3 3141 Initialization Message." 3142 ::= { mplsLdpEntityAtmEntry 3 } 3144 mplsLdpEntityAtmVcDirectionality OBJECT-TYPE 3145 SYNTAX INTEGER { 3146 bidirectional(0), 3147 unidirectional(1) 3148 } 3149 MAX-ACCESS read-create 3150 STATUS current 3151 DESCRIPTION 3152 "If the value of this object is 'bidirectional(0)', 3153 a given VCI, within a given VPI, is used as a 3154 label for both directions independently. 3156 If the value of this object is 'unidirectional(1)', 3157 a given VCI within a VPI designates one direction. 3159 This is the EXACT value for the ATM Session Parameter, 3160 field D (for VC Directionality). The ATM Session 3161 Parameter is an optional parameter in the 3162 Initialization Message. 3164 The description from rfc3036.txt is: 3166 'D, VC Directionality 3167 A value of 0 specifies bidirectional VC capability, 3168 meaning the LSR can (within a given VPI) support 3169 the use of a given VCI as a label for both link 3170 directions independently. A value of 1 3171 specifies unidirectional VC capability, meaning 3172 (within a given VPI) a given VCI may appear in 3173 a label mapping for one direction on the link 3174 only. When either or both of the peers 3175 specifies unidirectional VC capability, both 3176 LSRs use unidirectional VC label assignment for 3177 the link as follows. The LSRs compare their 3178 LDP Identifiers as unsigned integers. The LSR 3179 with the larger LDP Identifier may assign 3180 only odd-numbered VCIs in the VPI/VCI 3181 range as labels. The system with the smaller 3182 LDP Identifier may assign only even-numbered 3183 VCIs in the VPI/VCI range as labels.' 3185 Please refer to the following reference 3186 for a complete description of this feature." 3187 REFERENCE 3188 "RFC3036, LDP Specification, Section 3.5.3 3189 Initialization Message." 3190 ::= { mplsLdpEntityAtmEntry 4 } 3192 mplsLdpEntityAtmLsrConnectivity OBJECT-TYPE 3193 SYNTAX INTEGER { 3194 direct(1), 3195 indirect(2) 3196 } 3197 MAX-ACCESS read-create 3198 STATUS current 3199 DESCRIPTION 3200 "The peer LSR may be connected indirectly by means 3201 of an ATM VP so that the VPI values may be different 3202 on either endpoint so the label MUST be encoded 3203 entirely within the VCI field." 3204 DEFVAL { direct } 3205 ::= { mplsLdpEntityAtmEntry 5 } 3207 mplsLdpEntityAtmDefaultControlVpi OBJECT-TYPE 3208 SYNTAX AtmVpIdentifier 3209 MAX-ACCESS read-create 3210 STATUS current 3211 DESCRIPTION 3212 "The default VPI value for the non-MPLS connection. The 3213 default value of this is 0 (zero) but other values may 3214 be configured. This object allows a different value 3215 to be configured." 3216 DEFVAL { 0 } 3217 ::= { mplsLdpEntityAtmEntry 6 } 3219 mplsLdpEntityAtmDefaultControlVci OBJECT-TYPE 3220 SYNTAX MplsAtmVcIdentifier 3221 MAX-ACCESS read-create 3222 STATUS current 3223 DESCRIPTION 3224 "The Default VCI value for a non-MPLS connection. The 3225 default value of this is 32 but other values may be 3226 configured. This object allows a different value to 3227 be configured." 3228 DEFVAL { 32 } 3229 ::= { mplsLdpEntityAtmEntry 7 } 3231 mplsLdpEntityAtmUnlabTrafVpi OBJECT-TYPE 3232 SYNTAX AtmVpIdentifier 3233 MAX-ACCESS read-create 3234 STATUS current 3235 DESCRIPTION 3236 "VPI value of the VCC supporting unlabeled traffic. This 3237 non-MPLS connection is used to carry unlabeled (IP) 3238 packets. The default value is the same as the default 3239 value of the 'mplsLdpEntityAtmDefaultControlVpi', however 3240 another value may be configured." 3241 DEFVAL { 0 } 3242 ::= { mplsLdpEntityAtmEntry 8 } 3244 mplsLdpEntityAtmUnlabTrafVci OBJECT-TYPE 3245 SYNTAX MplsAtmVcIdentifier 3246 MAX-ACCESS read-create 3247 STATUS current 3248 DESCRIPTION 3249 "VCI value of the VCC supporting unlabeled traffic. 3250 This non-MPLS connection is used to carry unlabeled (IP) 3251 packets. The default value is the same as the default 3252 value of the 'mplsLdpEntityAtmDefaultControlVci', however 3253 another value may be configured." 3254 DEFVAL { 32 } 3255 ::= { mplsLdpEntityAtmEntry 9 } 3257 mplsLdpEntityAtmStorageType OBJECT-TYPE 3258 SYNTAX StorageType 3259 MAX-ACCESS read-create 3260 STATUS current 3261 DESCRIPTION 3262 "The storage type for this conceptual row. 3263 Conceptual rows having the value 'permanent(4)' 3264 need not allow write-access to any columnar 3265 objects in the row." 3266 DEFVAL { nonVolatile } 3267 ::= { mplsLdpEntityAtmEntry 10 } 3269 mplsLdpEntityAtmRowStatus OBJECT-TYPE 3270 SYNTAX RowStatus 3271 MAX-ACCESS read-create 3272 STATUS current 3273 DESCRIPTION 3274 "The status of this conceptual row. All writable 3275 objects in this row may be modified at any time, 3276 however, as described in detail in the section 3277 entitled, 'Changing Values After Session 3278 Establishment', and again described in the 3279 DESCRIPTION clause of the mplsLdpEntityAdminStatus 3280 object, if a session has been initiated with a Peer, 3281 changing objects in this table will wreak havoc 3282 with the session and interrupt traffic. To repeat again: 3283 the recommended procedure is to set the 3284 mplsLdpEntityAdminStatus to down, thereby explicitly 3285 causing a session to be torn down. Then, 3286 change objects in this entry, then set the 3287 mplsLdpEntityAdminStatus to enable 3288 which enables a new session to be initiated." 3289 ::= { mplsLdpEntityAtmEntry 11 } 3291 -- 3292 -- The MPLS LDP Entity ATM Label Range Table 3293 -- 3294 mplsLdpEntityAtmLRTable OBJECT-TYPE 3295 SYNTAX SEQUENCE OF MplsLdpEntityAtmLREntry 3296 MAX-ACCESS not-accessible 3297 STATUS current 3298 DESCRIPTION 3299 "The MPLS LDP Entity ATM Label Range (LR) Table. 3300 The purpose of this table is to provide a mechanism 3301 for configuring a contiguous range of vpi's 3302 with a contiguous range of vci's, or a 'label range' 3303 for LDP Entities. 3305 LDP Entities which use ATM must have at least one 3306 entry in this table. 3308 There must exist at least one entry in this 3309 table for every LDP Entity that has 3310 'mplsLdpEntityOptionalParameters' object with 3311 a value of 'atmSessionParameters'." 3312 ::= { mplsLdpEntityAtmObjects 2 } 3314 mplsLdpEntityAtmLREntry OBJECT-TYPE 3315 SYNTAX MplsLdpEntityAtmLREntry 3316 MAX-ACCESS not-accessible 3317 STATUS current 3318 DESCRIPTION 3319 "A row in the LDP Entity ATM Label 3320 Range Table. One entry in this table contains 3321 information on a single range of labels 3322 represented by the configured Upper and Lower 3323 Bounds VPI/VCI pairs. These are the same 3324 data used in the Initialization Message. 3326 NOTE: The ranges for a specific LDP Entity 3327 are UNIQUE and non-overlapping. For example, 3328 for a specific LDP Entity index, there could 3329 be one entry having LowerBound vpi/vci == 0/32, and 3330 UpperBound vpi/vci == 0/100, and a second entry 3331 for this same interface with LowerBound 3332 vpi/vci == 0/101 and UpperBound vpi/vci == 0/200. 3333 However, there could not be a third entry with 3334 LowerBound vpi/vci == 0/200 and 3335 UpperBound vpi/vci == 0/300 because this label 3336 range overlaps with the second entry (i.e. both 3337 entries now have 0/200). 3339 A row will not become active unless a unique and 3340 non-overlapping range is specified. 3342 At least one label range entry for a 3343 specific LDP Entity MUST 3344 include the default VPI/VCI values denoted 3345 in the LDP Entity Table. 3347 A request to create a row with an overlapping 3348 range should result in an inconsistentValue 3349 error." 3350 INDEX { mplsLdpEntityLdpId, 3351 mplsLdpEntityIndex, 3352 mplsLdpEntityAtmLRMinVpi, 3353 mplsLdpEntityAtmLRMinVci 3354 } 3355 ::= { mplsLdpEntityAtmLRTable 1 } 3357 MplsLdpEntityAtmLREntry ::= SEQUENCE { 3358 mplsLdpEntityAtmLRMinVpi AtmVpIdentifier, 3359 mplsLdpEntityAtmLRMinVci MplsAtmVcIdentifier, 3360 mplsLdpEntityAtmLRMaxVpi AtmVpIdentifier, 3361 mplsLdpEntityAtmLRMaxVci MplsAtmVcIdentifier, 3362 mplsLdpEntityAtmLRStorageType StorageType, 3363 mplsLdpEntityAtmLRRowStatus RowStatus 3364 } 3366 mplsLdpEntityAtmLRMinVpi OBJECT-TYPE 3367 SYNTAX AtmVpIdentifier 3368 MAX-ACCESS not-accessible 3369 STATUS current 3370 DESCRIPTION 3371 "The minimum VPI number configured for this range. 3372 The value of zero is a valid value for the VPI portion 3373 of the label." 3374 ::= { mplsLdpEntityAtmLREntry 1 } 3376 mplsLdpEntityAtmLRMinVci OBJECT-TYPE 3377 SYNTAX MplsAtmVcIdentifier 3378 MAX-ACCESS not-accessible 3379 STATUS current 3380 DESCRIPTION 3381 "The minimum VCI number configured for this range." 3382 ::= { mplsLdpEntityAtmLREntry 2 } 3384 mplsLdpEntityAtmLRMaxVpi OBJECT-TYPE 3385 SYNTAX AtmVpIdentifier 3386 MAX-ACCESS read-create 3387 STATUS current 3388 DESCRIPTION 3389 "The maximum VPI number configured for this range." 3390 ::= { mplsLdpEntityAtmLREntry 3 } 3392 mplsLdpEntityAtmLRMaxVci OBJECT-TYPE 3393 SYNTAX MplsAtmVcIdentifier 3394 MAX-ACCESS read-create 3395 STATUS current 3396 DESCRIPTION 3397 "The maximum VCI number configured for this range." 3398 ::= { mplsLdpEntityAtmLREntry 4 } 3400 mplsLdpEntityAtmLRStorageType OBJECT-TYPE 3401 SYNTAX StorageType 3402 MAX-ACCESS read-create 3403 STATUS current 3404 DESCRIPTION 3405 "The storage type for this conceptual row. 3406 Conceptual rows having the value 'permanent(4)' 3407 need not allow write-access to any columnar 3408 objects in the row." 3409 DEFVAL { nonVolatile } 3410 ::= { mplsLdpEntityAtmLREntry 5 } 3412 mplsLdpEntityAtmLRRowStatus OBJECT-TYPE 3413 SYNTAX RowStatus 3414 MAX-ACCESS read-create 3415 STATUS current 3416 DESCRIPTION 3417 "The status of this conceptual row. All writable 3418 objects in this row may be modified at any time, 3419 however, as described in detail in the section 3420 entitled, 'Changing Values After Session 3421 Establishment', and again described in the 3422 DESCRIPTION clause of the 3423 mplsLdpEntityAdminStatus object, 3424 if a session has been initiated with a Peer, 3425 changing objects in this table will 3426 wreak havoc with the session and interrupt traffic. 3427 To repeat again: the recommended procedure 3428 is to set the mplsLdpEntityAdminStatus to 3429 down, thereby explicitly causing a session 3430 to be torn down. Then, change objects in this 3431 entry, then set the mplsLdpEntityAdminStatus 3432 to enable which enables a new session 3433 to be initiated." 3434 ::= { mplsLdpEntityAtmLREntry 6 } 3436 -- 3437 -- MPLS LDP ATM Session Information 3438 -- 3440 mplsLdpAtmSessionObjects OBJECT IDENTIFIER ::= 3441 { mplsLdpAtmObjects 2 } 3443 mplsLdpAtmSessionTable OBJECT-TYPE 3444 SYNTAX SEQUENCE OF MplsLdpAtmSessionEntry 3445 MAX-ACCESS not-accessible 3446 STATUS current 3447 DESCRIPTION 3448 "A table which relates sessions in the 3449 'mplsLdpSessionTable' and their label 3450 range intersections. There could be one 3451 or more label range intersections between an 3452 LDP Entity and LDP Peer using ATM as the 3453 underlying media. Each row represents 3454 a single label range intersection. 3456 This table cannot use the 'AUGMENTS' 3457 clause because there is not necessarily 3458 a one-to-one mapping between this table 3459 and the mplsLdpSessionTable." 3460 ::= { mplsLdpAtmSessionObjects 1 } 3462 mplsLdpAtmSessionEntry OBJECT-TYPE 3463 SYNTAX MplsLdpAtmSessionEntry 3464 MAX-ACCESS not-accessible 3465 STATUS current 3466 DESCRIPTION 3467 "An entry in this table represents information on a 3468 single label range intersection between an LDP Entity 3469 and LDP Peer. 3471 The information contained in a row is read-only." 3472 INDEX { mplsLdpEntityLdpId, 3473 mplsLdpEntityIndex, 3474 mplsLdpPeerLdpId, 3475 mplsLdpSessionAtmLRLowerBoundVpi, 3476 mplsLdpSessionAtmLRLowerBoundVci 3478 } 3479 ::= { mplsLdpAtmSessionTable 1 } 3481 MplsLdpAtmSessionEntry ::= SEQUENCE { 3482 mplsLdpSessionAtmLRLowerBoundVpi AtmVpIdentifier, 3483 mplsLdpSessionAtmLRLowerBoundVci MplsAtmVcIdentifier, 3484 mplsLdpSessionAtmLRUpperBoundVpi AtmVpIdentifier, 3485 mplsLdpSessionAtmLRUpperBoundVci MplsAtmVcIdentifier 3486 } 3488 mplsLdpSessionAtmLRLowerBoundVpi OBJECT-TYPE 3489 SYNTAX AtmVpIdentifier 3490 MAX-ACCESS not-accessible 3491 STATUS current 3492 DESCRIPTION 3493 "The minimum VPI number for this range." 3494 ::= { mplsLdpAtmSessionEntry 1 } 3496 mplsLdpSessionAtmLRLowerBoundVci OBJECT-TYPE 3497 SYNTAX MplsAtmVcIdentifier 3498 MAX-ACCESS not-accessible 3499 STATUS current 3500 DESCRIPTION 3501 "The minimum VCI number for this range." 3502 ::= { mplsLdpAtmSessionEntry 2 } 3504 mplsLdpSessionAtmLRUpperBoundVpi OBJECT-TYPE 3505 SYNTAX AtmVpIdentifier 3506 MAX-ACCESS read-only 3507 STATUS current 3508 DESCRIPTION 3509 "The maximum VPI number for this range." 3510 ::= { mplsLdpAtmSessionEntry 3 } 3512 mplsLdpSessionAtmLRUpperBoundVci OBJECT-TYPE 3513 SYNTAX MplsAtmVcIdentifier 3514 MAX-ACCESS read-only 3515 STATUS current 3516 DESCRIPTION 3517 "The maximum VCI number for this range." 3518 ::= { mplsLdpAtmSessionEntry 4 } 3520 --************************************************************** 3521 -- Module Conformance Statement 3522 --************************************************************** 3523 mplsLdpAtmGroups 3524 OBJECT IDENTIFIER ::= { mplsLdpAtmConformance 1 } 3526 mplsLdpAtmCompliances 3527 OBJECT IDENTIFIER ::= { mplsLdpAtmConformance 2 } 3529 -- 3530 -- Full Compliance 3531 -- 3533 mplsLdpAtmModuleFullCompliance MODULE-COMPLIANCE 3534 STATUS current 3535 DESCRIPTION 3536 "The Module is implemented with support for 3537 read-create and read-write. In other words, 3538 both monitoring and configuration 3539 are available when using this MODULE-COMPLIANCE." 3540 MODULE -- this module 3541 MANDATORY-GROUPS { 3542 mplsLdpAtmGroup 3543 } 3545 OBJECT mplsLdpEntityAtmRowStatus 3546 SYNTAX RowStatus { active(1) } 3547 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 3548 DESCRIPTION 3549 "Support for createAndWait and notInService is not required." 3551 OBJECT mplsLdpEntityAtmLRRowStatus 3552 SYNTAX RowStatus { active(1) } 3553 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 3554 DESCRIPTION 3555 "Support for createAndWait and notInService is not required." 3557 ::= { mplsLdpAtmCompliances 1 } 3559 -- 3560 -- Read-Only Compliance 3561 -- 3563 mplsLdpAtmModuleReadOnlyCompliance MODULE-COMPLIANCE 3564 STATUS current 3565 DESCRIPTION 3566 "The Module is implemented with support for 3567 read-only. In other words, only monitoring 3568 is available by implementing this MODULE-COMPLIANCE." 3569 MODULE -- this module 3570 MANDATORY-GROUPS { 3571 mplsLdpAtmGroup 3572 } 3574 OBJECT mplsLdpEntityAtmIfIndexOrZero 3575 MIN-ACCESS read-only 3576 DESCRIPTION 3577 "Write access is not required." 3579 OBJECT mplsLdpEntityAtmMergeCap 3580 MIN-ACCESS read-only 3581 DESCRIPTION 3582 "Write access is not required." 3584 OBJECT mplsLdpEntityAtmVcDirectionality 3585 MIN-ACCESS read-only 3586 DESCRIPTION 3587 "Write access is not required." 3589 OBJECT mplsLdpEntityAtmLsrConnectivity 3590 MIN-ACCESS read-only 3591 DESCRIPTION 3592 "Write access is not required." 3594 OBJECT mplsLdpEntityAtmDefaultControlVpi 3595 MIN-ACCESS read-only 3596 DESCRIPTION 3597 "Write access is not required." 3599 OBJECT mplsLdpEntityAtmDefaultControlVci 3600 MIN-ACCESS read-only 3601 DESCRIPTION 3602 "Write access is not required." 3604 OBJECT mplsLdpEntityAtmUnlabTrafVpi 3605 MIN-ACCESS read-only 3606 DESCRIPTION 3607 "Write access is not required." 3609 OBJECT mplsLdpEntityAtmUnlabTrafVci 3610 MIN-ACCESS read-only 3611 DESCRIPTION 3612 "Write access is not required." 3614 OBJECT mplsLdpEntityAtmStorageType 3615 MIN-ACCESS read-only 3616 DESCRIPTION 3617 "Write access is not required." 3619 OBJECT mplsLdpEntityAtmRowStatus 3620 SYNTAX RowStatus { active(1) } 3621 MIN-ACCESS read-only 3622 DESCRIPTION 3623 "Write access is not required, and active is the 3624 only status that needs to be supported." 3626 OBJECT mplsLdpEntityAtmLRMaxVpi 3627 MIN-ACCESS read-only 3628 DESCRIPTION 3629 "Write access is not required." 3631 OBJECT mplsLdpEntityAtmLRMaxVci 3632 MIN-ACCESS read-only 3633 DESCRIPTION 3634 "Write access is not required." 3636 OBJECT mplsLdpEntityAtmLRStorageType 3637 MIN-ACCESS read-only 3638 DESCRIPTION 3639 "Write access is not required." 3641 OBJECT mplsLdpEntityAtmLRRowStatus 3642 SYNTAX RowStatus { active(1) } 3643 MIN-ACCESS read-only 3644 DESCRIPTION 3645 "Write access is not required, and active is the 3646 only status that needs to be supported." 3648 ::= { mplsLdpAtmCompliances 2 } 3650 -- 3651 -- units of conformance 3652 -- 3654 mplsLdpAtmGroup OBJECT-GROUP 3655 OBJECTS { 3656 mplsLdpEntityAtmIfIndexOrZero, 3657 mplsLdpEntityAtmMergeCap, 3658 mplsLdpEntityAtmLRComponents, 3659 mplsLdpEntityAtmVcDirectionality, 3660 mplsLdpEntityAtmLsrConnectivity, 3661 mplsLdpEntityAtmDefaultControlVpi, 3662 mplsLdpEntityAtmDefaultControlVci, 3663 mplsLdpEntityAtmUnlabTrafVpi, 3664 mplsLdpEntityAtmUnlabTrafVci, 3665 mplsLdpEntityAtmStorageType, 3666 mplsLdpEntityAtmRowStatus, 3667 mplsLdpEntityAtmLRMaxVpi, 3668 mplsLdpEntityAtmLRMaxVci, 3669 mplsLdpEntityAtmLRStorageType, 3670 mplsLdpEntityAtmLRRowStatus, 3671 mplsLdpSessionAtmLRUpperBoundVpi, 3672 mplsLdpSessionAtmLRUpperBoundVci 3674 } 3675 STATUS current 3676 DESCRIPTION 3677 "Objects that apply to all MPLS LDP implementations 3678 using ATM as the Layer 2." 3679 ::= { mplsLdpAtmGroups 1 } 3681 END 3683 4.2. The MPLS-LDP-FRAME-RELAY-STD-MIB Module 3685 This MIB Module MUST be supported if LDP uses FRAME RELAY as the 3686 Layer 2 medium. There are three tables in this MIB Module. Two 3687 tables are to configure LDP for using Frame Relay. These tables are 3688 the mplsLdpEntityFrameRelayTable and the 3689 mplsLdpEntityFrameRelayLRTable. The third table, 3690 mplsLdpFrameRelaySessionTable, is a read-only table. 3692 4.2.1. The LDP Entity Frame Relay Table 3694 The mplsLdpEntityFrameRelayTable provides a way to configure 3695 information which would be contained in the "Optional Parameter" 3696 portion of an LDP PDU Initialization Message. 3698 4.2.2. The LDP Entity Frame Relay Label Range Table 3700 The mplsLdpEntityFrameRelayLRTable provides a way to configure 3701 information which would be contained in the "Frame Relay Label Range 3702 Components" portion of an LDP PDU Intialization Message, see 3703 [RFC3034] and [RFC3036]. 3705 4.2.3. The LDP Frame Relay Session Table 3707 The MPLS LDP Frame Relay Session Table is a read-only table which 3708 contains session information specific to Frame Relay. 3710 MPLS-LDP-FRAME-RELAY-STD-MIB DEFINITIONS ::= BEGIN 3712 IMPORTS 3713 OBJECT-TYPE, 3714 MODULE-IDENTITY, 3715 Unsigned32 3716 FROM SNMPv2-SMI 3717 MODULE-COMPLIANCE, 3718 OBJECT-GROUP 3719 FROM SNMPv2-CONF 3721 RowStatus, 3722 StorageType 3723 FROM SNMPv2-TC 3725 DLCI 3726 FROM FRAME-RELAY-DTE-MIB 3728 InterfaceIndexOrZero 3729 FROM IF-MIB 3731 mplsStdMIB 3732 FROM MPLS-TC-STD-MIB 3734 mplsLdpEntityLdpId, 3735 mplsLdpEntityIndex, 3736 mplsLdpPeerLdpId 3737 FROM MPLS-LDP-STD-MIB 3738 ; 3740 mplsLdpFrameRelayStdMIB MODULE-IDENTITY 3741 LAST-UPDATED "200311181200Z" -- 18 November 2003 3742 ORGANIZATION "Multiprotocol Label Switching (mpls) 3743 Working Group" 3744 CONTACT-INFO 3745 "Joan Cucchiara (jcucchiara@artel.com) 3746 Artel 3748 Hans Sjostrand (hans@ipunplugged.com) 3749 ipUnplugged 3751 James V. Luciani (james_luciani@mindspring.com) 3752 Marconi Communications, Inc. 3754 Working Group Chairs: 3755 George Swallow, email: swallow@cisco.com 3756 Loa Andersson, email: loa@pi.se 3758 MPLS Working Group, email: mpls@uu.net 3759 " 3760 DESCRIPTION 3761 "Copyright (C) The Internet Society (2003). This 3762 version of this MIB module is part of RFCXXX; see 3763 the RFC itself for full legal notices. 3765 This MIB contains managed object definitions for 3766 configuring and monitoring the Multiprotocol Label 3767 Switching (MPLS), Label Distribution Protocol (LDP), 3768 utilizing Frame Relay as the Layer 2 media." 3769 REVISION "200311181200Z" -- 18 November 2003 3770 DESCRIPTION 3771 "Initial version published as part of RFC XXXX." 3773 -- Please see the IANA Considerations Section. 3774 -- The requested mplsStdMIB subId is 6, e.g. 3775 -- ::= { mplsStdMIB 6 } 3777 ::= { mplsStdMIB XXX } -- to be assigned by IANA 3779 --**************************************************************** 3781 mplsLdpFrameRelayObjects OBJECT IDENTIFIER 3782 ::= { mplsLdpFrameRelayStdMIB 1 } 3784 mplsLdpFrameRelayConformance OBJECT IDENTIFIER 3785 ::= { mplsLdpFrameRelayStdMIB 2 } 3787 --**************************************************************** 3788 -- MPLS LDP Frame Relay Objects 3789 --**************************************************************** 3791 -- 3792 -- Ldp Entity Objects for Frame Relay 3793 -- 3795 mplsLdpEntityFrameRelayObjects OBJECT IDENTIFIER ::= 3796 { mplsLdpFrameRelayObjects 1 } 3798 mplsLdpEntityFrameRelayTable OBJECT-TYPE 3799 SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayEntry 3800 MAX-ACCESS not-accessible 3801 STATUS current 3802 DESCRIPTION 3803 "This table contains Frame Relay specific 3804 information which could be used in the 3805 'Optional Parameters' and other Frame Relay 3806 Relay specific information. 3808 This table 'sparse augments' the mplsLdpEntityTable 3809 when Frame Relay is the Layer 2 medium." 3810 ::= { mplsLdpEntityFrameRelayObjects 1 } 3812 mplsLdpEntityFrameRelayEntry OBJECT-TYPE 3813 SYNTAX MplsLdpEntityFrameRelayEntry 3814 MAX-ACCESS not-accessible 3815 STATUS current 3816 DESCRIPTION 3817 "An entry in this table represents the Frame Relay 3818 optional parameters associated with the LDP entity." 3819 INDEX { mplsLdpEntityLdpId, 3820 mplsLdpEntityIndex 3821 } 3822 ::= { mplsLdpEntityFrameRelayTable 1 } 3824 MplsLdpEntityFrameRelayEntry ::= SEQUENCE { 3825 mplsLdpEntityFrameRelayIfIndexOrZero InterfaceIndexOrZero, 3826 mplsLdpEntityFrameRelayMergeCap INTEGER, 3827 mplsLdpEntityFrameRelayLRComponents Unsigned32, 3828 mplsLdpEntityFrameRelayVcDirectionality INTEGER, 3829 mplsLdpEntityFrameRelayStorageType StorageType, 3830 mplsLdpEntityFrameRelayRowStatus RowStatus 3831 } 3833 mplsLdpEntityFrameRelayIfIndexOrZero OBJECT-TYPE 3834 SYNTAX InterfaceIndexOrZero 3835 MAX-ACCESS read-create 3836 STATUS current 3837 DESCRIPTION 3838 "This value represents either the InterfaceIndex of 3839 the 'ifLayer' where the Frame Relay Labels 'owned' by this 3840 entry were created, or 0 (zero). The value of zero 3841 means that the InterfaceIndex is not known. For example, 3842 if the InterfaceIndex is created subsequent to the 3843 Frame Relay Label's creation, then it would not be known. 3844 However, if the InterfaceIndex is known, then it must 3845 be represented by this value. 3847 If an InterfaceIndex becomes known, then the 3848 network management entity (e.g. SNMP agent) responsible 3849 for this object MUST change the value from 0 (zero) to the 3850 value of the InterfaceIndex. If an Frame Relay Label is 3851 being used in forwarding data, then the value of this 3852 object MUST be the InterfaceIndex." 3853 ::= { mplsLdpEntityFrameRelayEntry 1 } 3855 mplsLdpEntityFrameRelayMergeCap OBJECT-TYPE 3856 SYNTAX INTEGER { 3857 notSupported(0), 3858 supported(1) 3859 } 3860 MAX-ACCESS read-create 3861 STATUS current 3862 DESCRIPTION 3863 "This represents whether or not the Frame Relay merge 3864 capability is supported. This is the EXACT value for the 3865 Frame Relay Session Parameter, field M (for Frame Relay 3866 Merge Capabilities). The Frame Relay Session Parameter 3867 is an optional parameter in the Initialization Message. 3869 The description from rfc3036.txt is: 3870 'M, Frame Relay Merge Capabilities 3871 Specifies the merge capabilities of a Frame 3872 Relay switch. The following values are 3873 supported in this version of the 3874 specification: 3876 Value Meaning 3878 0 Merge not supported 3879 1 Merge supported 3881 Non-merge and merge Frame Relay LSRs may 3882 freely interoperate.' 3884 Please refer to the following reference for a 3885 complete description of this feature." 3886 REFERENCE 3887 "RFC3036, LDP Specification, Section 3.5.3 3888 Initialization Message." 3889 ::= { mplsLdpEntityFrameRelayEntry 2 } 3891 mplsLdpEntityFrameRelayLRComponents OBJECT-TYPE 3892 SYNTAX Unsigned32 (1..65535) 3893 MAX-ACCESS read-only 3894 STATUS current 3895 DESCRIPTION 3896 "Number of Label Range Components in the Initialization 3897 message. This also represents the number of entries 3898 in the mplsLdpEntityFrameRelayLRTable which correspond 3899 to this entry. 3901 This is the EXACT value for the Frame Relay Session 3902 Parameter, field N (for Number of label range 3903 components). The Frame Relay Session Parameter 3904 is an optional parameter in the Initialization 3905 Message. 3907 The description from rfc3036.txt is: 3909 'N, Number of label range components 3910 Specifies the number of Frame Relay Label 3911 Range Components included in the TLV.' 3913 Please refer to the following reference for a 3914 complete description of this feature." 3915 REFERENCE 3916 "RFC3036, LDP Specification, Section 3.5.3 3917 Initialization Message." 3918 ::= { mplsLdpEntityFrameRelayEntry 3 } 3920 mplsLdpEntityFrameRelayVcDirectionality OBJECT-TYPE 3921 SYNTAX INTEGER { 3922 bidirectional(0), 3923 unidirection(1) 3924 } 3925 MAX-ACCESS read-create 3926 STATUS current 3927 DESCRIPTION 3928 "If the value of this object is 'bidirectional(0)', then 3929 the LSR supports the use of a given DLCI as a label for 3930 both directions independently. If the value of 3931 this object is 'unidirectional(1)', then the LSR 3932 uses the given DLCI as a label in only one direction. 3934 This is the EXACT value for the Frame Relay Session 3935 Parameter, field D (for VC Directionality). The 3936 Frame Relay Session Parameter is an optional 3937 parameter in the Initialization Message. 3939 The description from rfc3036.txt is: 3941 'D, VC Directionality 3942 A value of 0 specifies bidirectional VC capability, 3943 meaning the LSR can support the use of a given 3944 DLCI as a label for both link directions 3945 independently. A value of 1 specifies 3946 unidirectional VC capability, meaning a given 3947 DLCI may appear in a label mapping for one 3948 direction on the link only. When either or both 3949 of the peers specifies unidirectional VC 3950 capability, both LSRs use unidirectional VC 3951 label assignment for the link as follows. The 3952 LSRs compare their LDP Identifiers as unsigned 3953 integers. The LSR with the larger LDP 3954 Identifier may assign only odd-numbered DLCIs 3955 in the range as labels. The system with the 3956 smaller LDP Identifier may assign only 3957 even-numbered DLCIs in the range as labels.' 3959 Please refer to the following reference for a 3960 complete description of this feature." 3961 REFERENCE 3962 "RFC3036, LDP Specification, Section 3.5.3 3963 Initialization Message." 3964 ::= { mplsLdpEntityFrameRelayEntry 4 } 3966 mplsLdpEntityFrameRelayStorageType OBJECT-TYPE 3967 SYNTAX StorageType 3968 MAX-ACCESS read-create 3969 STATUS current 3970 DESCRIPTION 3971 "The storage type for this conceptual row. 3972 Conceptual rows having the value 'permanent(4)' 3973 need not allow write-access to any columnar 3974 objects in the row." 3975 DEFVAL { nonVolatile } 3976 ::= { mplsLdpEntityFrameRelayEntry 5 } 3978 mplsLdpEntityFrameRelayRowStatus OBJECT-TYPE 3979 SYNTAX RowStatus 3980 MAX-ACCESS read-create 3981 STATUS current 3982 DESCRIPTION 3983 "The status of this conceptual row. All writable 3984 objects in this row may be modified at any time, 3985 however, as described in detail in the section 3986 entitled, 'Changing Values After Session 3987 Establishment', and again described in the 3988 DESCRIPTION clause of the 3989 mplsLdpEntityAdminStatus object, 3990 if a session has been initiated with a Peer, 3991 changing objects in this table will 3992 wreak havoc with the session and interrupt 3993 traffic. To repeat again: 3994 the recommended procedure is to set the 3995 mplsLdpEntityAdminStatus to 3996 down, thereby explicitly causing a 3997 session to be torn down. Then, 3998 change objects in this entry, then set 3999 the mplsLdpEntityAdminStatus 4000 to enable which enables a new session 4001 to be initiated." 4002 ::= { mplsLdpEntityFrameRelayEntry 6 } 4004 -- 4005 -- Frame Relay Label Range Components 4006 -- 4008 mplsLdpEntityFrameRelayLRTable OBJECT-TYPE 4009 SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayLREntry 4010 MAX-ACCESS not-accessible 4011 STATUS current 4012 DESCRIPTION 4013 "This table contains information about the 4014 Optional Parameters for the Frame Relay Session 4015 in the LDP Initialization Message, specifically 4016 it contains information about the Frame Relay 4017 Label Range Components. 4019 If the value of the object 4020 'mplsLdpEntityOptionalParameters' contains the 4021 value of 'frameRelaySessionParameters(3)' then 4022 there must be at least one corresponding entry 4023 in this table." 4024 ::= { mplsLdpEntityFrameRelayObjects 2 } 4026 mplsLdpEntityFrameRelayLREntry OBJECT-TYPE 4027 SYNTAX MplsLdpEntityFrameRelayLREntry 4028 MAX-ACCESS not-accessible 4029 STATUS current 4030 DESCRIPTION 4031 "An entry in this table represents the Frame Relay 4032 Label Range Component associated with the LDP entity." 4033 INDEX { mplsLdpEntityLdpId, 4034 mplsLdpEntityIndex, 4035 mplsLdpEntityFrameRelayLRMinDlci 4036 } 4037 ::= { mplsLdpEntityFrameRelayLRTable 1 } 4039 MplsLdpEntityFrameRelayLREntry ::= SEQUENCE { 4040 mplsLdpEntityFrameRelayLRMinDlci DLCI, 4041 mplsLdpEntityFrameRelayLRMaxDlci DLCI, 4042 mplsLdpEntityFrameRelayLRLen INTEGER, 4043 mplsLdpEntityFrameRelayLRStorageType StorageType, 4044 mplsLdpEntityFrameRelayLRRowStatus RowStatus 4045 } 4047 mplsLdpEntityFrameRelayLRMinDlci OBJECT-TYPE 4048 SYNTAX DLCI 4049 MAX-ACCESS not-accessible 4050 STATUS current 4051 DESCRIPTION 4052 "The lower bound which is supported. This value 4053 should be the same as that in the Frame Relay Label 4054 Range Component's Minimum DLCI field. The value 4055 of zero is valid for the minimum DLCI field of 4056 the label." 4057 REFERENCE 4058 "RFC3034, Use of Label Switching on Frame Relay 4059 Networks Specification." 4060 ::= { mplsLdpEntityFrameRelayLREntry 1 } 4062 mplsLdpEntityFrameRelayLRMaxDlci OBJECT-TYPE 4063 SYNTAX DLCI 4064 MAX-ACCESS read-create 4065 STATUS current 4066 DESCRIPTION 4067 "The upper bound which is supported. This value 4068 should be the same as that in the Frame Relay Label 4069 Range Component's Maximum DLCI field." 4070 ::= { mplsLdpEntityFrameRelayLREntry 2 } 4072 mplsLdpEntityFrameRelayLRLen OBJECT-TYPE 4073 SYNTAX INTEGER { 4074 tenDlciBits(0), 4075 twentyThreeDlciBits(2) 4076 } 4077 MAX-ACCESS read-create 4078 STATUS current 4079 DESCRIPTION 4080 "This object specifies the length of the DLCI bits. 4082 This is the EXACT value for the Len field of the 4083 Frame Relay Label Range Component. 4085 The description from rfc3036.txt is: 4087 'Len 4088 This field specifies the number of bits of the DLCI. 4089 The following values are supported: 4091 Len DLCI bits 4093 0 10 4094 2 23 4096 Len values 1 and 3 are reserved.' 4098 Please refer to the following reference for a complete 4099 description of this feature." 4100 REFERENCE 4101 "RFC3036, LDP Specification, Section 3.5.3 4102 Initialization Message." 4103 ::= { mplsLdpEntityFrameRelayLREntry 3 } 4105 mplsLdpEntityFrameRelayLRStorageType OBJECT-TYPE 4106 SYNTAX StorageType 4107 MAX-ACCESS read-create 4108 STATUS current 4109 DESCRIPTION 4110 "The storage type for this conceptual row. 4111 Conceptual rows having the value 'permanent(4)' 4112 need not allow write-access to any columnar 4113 objects in the row." 4114 DEFVAL { nonVolatile } 4115 ::= { mplsLdpEntityFrameRelayLREntry 4 } 4117 mplsLdpEntityFrameRelayLRRowStatus OBJECT-TYPE 4118 SYNTAX RowStatus 4119 MAX-ACCESS read-create 4120 STATUS current 4121 DESCRIPTION 4122 "The status of this conceptual row. All writable 4123 objects in this row may be modified at any time, 4124 however, as described in detail in the section 4125 entitled, 'Changing Values After Session 4126 Establishment', and again described in the 4127 DESCRIPTION clause of the 4128 mplsLdpEntityAdminStatus object, 4129 if a session has been initiated with a Peer, 4130 changing objects in this table will 4131 wreak havoc with the session and interrupt 4132 traffic. To repeat again: 4133 the recommended procedure is to set the 4134 mplsLdpEntityAdminStatus to down, thereby 4135 explicitly causing a session to be torn down. Then, 4136 change objects in this entry, then set the 4137 mplsLdpEntityAdminStatus to enable which enables 4138 a new session to be initiated." 4139 ::= { mplsLdpEntityFrameRelayLREntry 5 } 4141 -- 4142 -- MPLS LDP Frame Relay Session Information 4143 -- 4144 mplsLdpFrameRelaySessionObjects OBJECT IDENTIFIER ::= 4145 { mplsLdpFrameRelayObjects 2 } 4147 mplsLdpFrameRelaySessionTable OBJECT-TYPE 4148 SYNTAX SEQUENCE OF MplsLdpFrameRelaySessionEntry 4149 MAX-ACCESS not-accessible 4150 STATUS current 4151 DESCRIPTION 4152 "A table of Frame Relay label range intersections 4153 between the LDP Entities and LDP Peers. 4154 Each row represents a single label range intersection. 4156 NOTE: this table cannot use the 'AUGMENTS' 4157 clause because there is not necessarily a one-to-one 4158 mapping between this table and the 4159 mplsLdpSessionTable." 4160 ::= { mplsLdpFrameRelaySessionObjects 1 } 4162 mplsLdpFrameRelaySessionEntry OBJECT-TYPE 4163 SYNTAX MplsLdpFrameRelaySessionEntry 4164 MAX-ACCESS not-accessible 4165 STATUS current 4166 DESCRIPTION 4167 "An entry in this table represents information on a 4168 single label range intersection between an 4169 LDP Entity and LDP Peer. 4171 The information contained in a row is read-only." 4172 INDEX { mplsLdpEntityLdpId, 4173 mplsLdpEntityIndex, 4174 mplsLdpPeerLdpId, 4175 mplsLdpFrameRelaySessionMinDlci 4176 } 4177 ::= { mplsLdpFrameRelaySessionTable 1 } 4179 MplsLdpFrameRelaySessionEntry ::= SEQUENCE { 4180 mplsLdpFrameRelaySessionMinDlci DLCI, 4181 mplsLdpFrameRelaySessionMaxDlci DLCI, 4182 mplsLdpFrameRelaySessionLen INTEGER 4183 } 4185 mplsLdpFrameRelaySessionMinDlci OBJECT-TYPE 4186 SYNTAX DLCI 4187 MAX-ACCESS not-accessible 4188 STATUS current 4189 DESCRIPTION 4190 "The lower bound of DLCIs which are supported. 4191 The value of zero is a valid value for the 4192 minimum DLCI field of the label." 4193 REFERENCE 4194 "RFC3034, Use of Label Switching on Frame Relay 4195 Networks Specification." 4196 ::= { mplsLdpFrameRelaySessionEntry 1 } 4198 mplsLdpFrameRelaySessionMaxDlci OBJECT-TYPE 4199 SYNTAX DLCI 4200 MAX-ACCESS read-only 4201 STATUS current 4202 DESCRIPTION 4203 "The upper bound of DLCIs which are supported." 4204 ::= { mplsLdpFrameRelaySessionEntry 2 } 4206 mplsLdpFrameRelaySessionLen OBJECT-TYPE 4207 SYNTAX INTEGER { 4208 tenDlciBits(0), 4209 twentyThreeDlciBits(2) 4210 } 4211 MAX-ACCESS read-only 4212 STATUS current 4213 DESCRIPTION 4214 "This object specifies the DLCI bits." 4215 ::= { mplsLdpFrameRelaySessionEntry 3 } 4217 --**************************************************************** 4218 -- Module Conformance Statement 4219 --**************************************************************** 4221 mplsLdpFrameRelayGroups 4222 OBJECT IDENTIFIER ::= { mplsLdpFrameRelayConformance 1 } 4224 mplsLdpFrameRelayCompliances 4225 OBJECT IDENTIFIER ::= { mplsLdpFrameRelayConformance 2 } 4227 -- 4228 -- Full Compliance 4229 -- 4231 mplsLdpFrameRelayModuleFullCompliance MODULE-COMPLIANCE 4232 STATUS current 4233 DESCRIPTION 4234 "The Module is implemented with support for 4235 read-create and read-write. In other words, 4236 both monitoring and configuration 4237 are available when using this MODULE-COMPLIANCE." 4238 MODULE -- this module 4239 MANDATORY-GROUPS { 4240 mplsLdpFrameRelayGroup 4241 } 4243 OBJECT mplsLdpEntityFrameRelayRowStatus 4244 SYNTAX RowStatus { active(1) } 4245 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 4246 DESCRIPTION 4247 "Support for createAndWait and notInService is not required." 4249 OBJECT mplsLdpEntityFrameRelayLRRowStatus 4250 SYNTAX RowStatus { active(1) } 4251 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 4252 DESCRIPTION 4253 "Support for createAndWait and notInService is not required." 4255 ::= { mplsLdpFrameRelayCompliances 1 } 4257 -- 4258 -- Read-Only Compliance 4259 -- 4261 mplsLdpFrameRelayModuleReadOnlyCompliance MODULE-COMPLIANCE 4262 STATUS current 4263 DESCRIPTION 4264 "The Module is implemented with support for 4265 read-only. In other words, only monitoring 4266 is available by implementing this MODULE-COMPLIANCE." 4267 MODULE -- this module 4268 MANDATORY-GROUPS { 4269 mplsLdpFrameRelayGroup 4270 } 4272 OBJECT mplsLdpEntityFrameRelayIfIndexOrZero 4273 MIN-ACCESS read-only 4274 DESCRIPTION 4275 "Write access is not required." 4277 OBJECT mplsLdpEntityFrameRelayMergeCap 4278 MIN-ACCESS read-only 4279 DESCRIPTION 4280 "Write access is not required." 4282 OBJECT mplsLdpEntityFrameRelayVcDirectionality 4283 MIN-ACCESS read-only 4284 DESCRIPTION 4285 "Write access is not required." 4287 OBJECT mplsLdpEntityFrameRelayStorageType 4288 MIN-ACCESS read-only 4289 DESCRIPTION 4290 "Write access is not required." 4292 OBJECT mplsLdpEntityFrameRelayRowStatus 4293 SYNTAX RowStatus { active(1) } 4294 MIN-ACCESS read-only 4295 DESCRIPTION 4296 "Write access is not required, and active is the 4297 only status that needs to be supported." 4299 OBJECT mplsLdpEntityFrameRelayLRMaxDlci 4300 MIN-ACCESS read-only 4301 DESCRIPTION 4302 "Write access is not required." 4304 OBJECT mplsLdpEntityFrameRelayLRLen 4305 MIN-ACCESS read-only 4306 DESCRIPTION 4307 "Write access is not required." 4309 OBJECT mplsLdpEntityFrameRelayLRStorageType 4310 MIN-ACCESS read-only 4311 DESCRIPTION 4312 "Write access is not required." 4314 OBJECT mplsLdpEntityFrameRelayLRRowStatus 4315 SYNTAX RowStatus { active(1) } 4316 MIN-ACCESS read-only 4317 DESCRIPTION 4318 "Write access is not required, and active is the 4319 only status that needs to be supported." 4320 ::= { mplsLdpFrameRelayCompliances 2 } 4322 -- 4323 -- units of conformance 4324 -- 4326 mplsLdpFrameRelayGroup OBJECT-GROUP 4327 OBJECTS { 4328 mplsLdpEntityFrameRelayIfIndexOrZero, 4329 mplsLdpEntityFrameRelayMergeCap, 4330 mplsLdpEntityFrameRelayLRComponents, 4331 mplsLdpEntityFrameRelayVcDirectionality, 4332 mplsLdpEntityFrameRelayStorageType, 4333 mplsLdpEntityFrameRelayRowStatus, 4334 mplsLdpEntityFrameRelayLRMaxDlci, 4335 mplsLdpEntityFrameRelayLRLen, 4336 mplsLdpEntityFrameRelayLRStorageType, 4337 mplsLdpEntityFrameRelayLRRowStatus, 4338 mplsLdpFrameRelaySessionMaxDlci, 4339 mplsLdpFrameRelaySessionLen 4340 } 4341 STATUS current 4342 DESCRIPTION 4343 "Objects that apply to all MPLS LDP implementations 4344 using Frame Relay as the Layer 2." 4345 ::= { mplsLdpFrameRelayGroups 1 } 4347 END 4349 4.3. The MPLS-LDP-GENERIC-STD-MIB Module 4351 This MIB Module MUST be supported if LDP uses a Per Platform Label 4352 Space. This MIB Module contains a Label Range (LR) table for 4353 configuring MPLS Generic Label Ranges. This table is 4354 mplsLdpEntityGenericLRTable. Although the LDP Specification does not 4355 provide a way for configuring Label Ranges for Generic Labels, the 4356 MIB does provide a way to reserve a range of generic labels because 4357 this was thought to be useful by the working group. 4359 MPLS-LDP-GENERIC-STD-MIB DEFINITIONS ::= BEGIN 4361 IMPORTS 4362 OBJECT-TYPE, 4363 MODULE-IDENTITY, 4364 Unsigned32 4365 FROM SNMPv2-SMI 4367 MODULE-COMPLIANCE, 4368 OBJECT-GROUP 4369 FROM SNMPv2-CONF 4371 RowStatus, 4372 StorageType 4373 FROM SNMPv2-TC 4375 InterfaceIndexOrZero 4376 FROM IF-MIB 4378 mplsStdMIB 4379 FROM MPLS-TC-STD-MIB 4381 mplsLdpEntityLdpId, 4382 mplsLdpEntityIndex 4383 FROM MPLS-LDP-STD-MIB 4384 ; 4386 mplsLdpGenericStdMIB MODULE-IDENTITY 4387 LAST-UPDATED "200311181200Z" -- 18 November 2003 4388 ORGANIZATION "Multiprotocol Label Switching (mpls) 4389 Working Group" 4390 CONTACT-INFO 4391 "Joan Cucchiara (jcucchiara@artel.com) 4392 Artel 4394 Hans Sjostrand (hans@ipunplugged.com) 4395 ipUnplugged 4397 James V. Luciani (james_luciani@mindspring.com) 4398 Marconi Communications, Inc. 4400 Working Group Chairs: 4401 George Swallow, email: swallow@cisco.com 4402 Loa Andersson, email: loa@pi.se 4404 MPLS Working Group, email: mpls@uu.net 4405 " 4406 DESCRIPTION 4407 "Copyright (C) The Internet Society (2003). This 4408 version of this MIB module is part of RFCXXX; see 4409 the RFC itself for full legal notices. 4411 This MIB contains managed object definitions for 4412 configuring and monitoring the Multiprotocol Label 4413 Switching (MPLS), Label Distribution Protocol (LDP), 4414 utilizing ethernet as the Layer 2 media." 4415 REVISION "200311181200Z" -- 18 November 2003 4416 DESCRIPTION 4417 "Initial version published as part of RFC XXXX." 4419 -- Please see the IANA Considerations Section. 4420 -- The requested mplsStdMIB subId is 7, e.g. 4421 -- ::= { mplsStdMIB 7 } 4423 ::= { mplsStdMIB XXX } -- to be assigned by IANA 4425 --**************************************************************** 4427 mplsLdpGenericObjects 4428 OBJECT IDENTIFIER ::= { mplsLdpGenericStdMIB 1 } 4429 mplsLdpGenericConformance 4430 OBJECT IDENTIFIER ::= { mplsLdpGenericStdMIB 2 } 4432 --**************************************************************** 4433 -- MPLS LDP GENERIC Objects 4434 --**************************************************************** 4436 -- 4437 -- Ldp Entity Objects for Generic Labels 4438 -- 4440 mplsLdpEntityGenericObjects OBJECT IDENTIFIER ::= 4441 { mplsLdpGenericObjects 1 } 4443 -- 4444 -- The MPLS LDP Entity Generic Label Range Table 4445 -- 4447 mplsLdpEntityGenericLRTable OBJECT-TYPE 4448 SYNTAX SEQUENCE OF MplsLdpEntityGenericLREntry 4449 MAX-ACCESS not-accessible 4450 STATUS current 4451 DESCRIPTION 4452 "The MPLS LDP Entity Generic Label Range (LR) 4453 Table. 4455 The purpose of this table is to provide a mechanism 4456 for configurating a contiguous range of generic labels, 4457 or a 'label range' for LDP Entities. 4459 LDP Entities which use Generic Labels must have at least 4460 one entry in this table. In other words, this table 4461 'extends' the mpldLdpEntityTable for Generic Labels." 4462 ::= { mplsLdpEntityGenericObjects 1 } 4464 mplsLdpEntityGenericLREntry OBJECT-TYPE 4465 SYNTAX MplsLdpEntityGenericLREntry 4466 MAX-ACCESS not-accessible 4467 STATUS current 4468 DESCRIPTION 4469 "A row in the LDP Entity Generic Label 4470 Range (LR) Table. One entry in this table contains 4471 information on a single range of labels 4472 represented by the configured Upper and Lower 4473 Bounds pairs. NOTE: there is NO corresponding 4474 LDP message which relates to the information 4475 in this table, however, this table does provide 4476 a way for a user to 'reserve' a generic label 4477 range. 4479 NOTE: The ranges for a specific LDP Entity 4480 are UNIQUE and non-overlapping. 4482 A row will not be created unless a unique and 4483 non-overlapping range is specified." 4484 INDEX { mplsLdpEntityLdpId, 4485 mplsLdpEntityIndex, 4486 mplsLdpEntityGenericLRMin, 4487 mplsLdpEntityGenericLRMax 4488 } 4489 ::= { mplsLdpEntityGenericLRTable 1 } 4491 MplsLdpEntityGenericLREntry ::= SEQUENCE { 4492 mplsLdpEntityGenericLRMin Unsigned32, 4493 mplsLdpEntityGenericLRMax Unsigned32, 4494 mplsLdpEntityGenericLabelSpace INTEGER, 4495 mplsLdpEntityGenericIfIndexOrZero InterfaceIndexOrZero, 4496 mplsLdpEntityGenericLRStorageType StorageType, 4497 mplsLdpEntityGenericLRRowStatus RowStatus 4498 } 4500 mplsLdpEntityGenericLRMin OBJECT-TYPE 4501 SYNTAX Unsigned32(0..1048575) 4502 MAX-ACCESS not-accessible 4503 STATUS current 4504 DESCRIPTION 4505 "The minimum label configured for this range." 4506 ::= { mplsLdpEntityGenericLREntry 1 } 4508 mplsLdpEntityGenericLRMax OBJECT-TYPE 4509 SYNTAX Unsigned32(0..1048575) 4510 MAX-ACCESS not-accessible 4511 STATUS current 4512 DESCRIPTION 4513 "The maximum label configured for this range." 4514 ::= { mplsLdpEntityGenericLREntry 2 } 4516 mplsLdpEntityGenericLabelSpace OBJECT-TYPE 4517 SYNTAX INTEGER { 4518 perPlatform(1), 4519 perInterface(2) 4520 } 4521 MAX-ACCESS read-create 4522 STATUS current 4523 DESCRIPTION 4524 "This value of this object is perPlatform(1), then 4525 this means that the label space type is 4526 per platform. 4528 If this object is perInterface(2), then this 4529 means that the label space type is per Interface." 4530 REFERENCE 4531 "RFC3036, LDP Specification, Section 2.2.1, 4532 Label Spaces." 4533 DEFVAL { perPlatform } 4534 ::= { mplsLdpEntityGenericLREntry 3 } 4536 mplsLdpEntityGenericIfIndexOrZero OBJECT-TYPE 4537 SYNTAX InterfaceIndexOrZero 4538 MAX-ACCESS read-create 4539 STATUS current 4540 DESCRIPTION 4541 "This value represents either the InterfaceIndex of 4542 the 'ifLayer' where these Generic Label would be created, 4543 or 0 (zero). The value of zero means that the 4544 InterfaceIndex is not known. 4546 However, if the InterfaceIndex is known, 4547 then it must be represented by this value. 4549 If an InterfaceIndex becomes known, then the 4550 network management entity (e.g. SNMP agent) responsible 4551 for this object MUST change the value from 0 (zero) to the 4552 value of the InterfaceIndex." 4553 ::= { mplsLdpEntityGenericLREntry 4 } 4555 mplsLdpEntityGenericLRStorageType OBJECT-TYPE 4556 SYNTAX StorageType 4557 MAX-ACCESS read-create 4558 STATUS current 4559 DESCRIPTION 4560 "The storage type for this conceptual row. 4561 Conceptual rows having the value 'permanent(4)' 4562 need not allow write-access to any columnar 4563 objects in the row." 4564 DEFVAL { nonVolatile } 4565 ::= { mplsLdpEntityGenericLREntry 5 } 4567 mplsLdpEntityGenericLRRowStatus OBJECT-TYPE 4568 SYNTAX RowStatus 4569 MAX-ACCESS read-create 4570 STATUS current 4571 DESCRIPTION 4572 "The status of this conceptual row. All writable 4573 objects in this row may be modified at any time, 4574 however, as described in detail in the section 4575 entitled, 'Changing Values After Session 4576 Establishment', and again described in the 4577 DESCRIPTION clause of the mplsLdpEntityAdminStatus object, 4578 if a session has been initiated with a Peer, 4579 changing objects in this table will 4580 wreak havoc with the session and interrupt traffic. 4581 To repeat again: the recommended procedure is 4582 to set the mplsLdpEntityAdminStatus to 4583 down, thereby explicitly causing a 4584 session to be torn down. Then, change objects 4585 in this entry, then set the mplsLdpEntityAdminStatus 4586 to enable which enables a new session to be initiated. 4588 There must exist at least one entry in this 4589 table for every LDP Entity that has a 4590 generic label configured." 4591 ::= { mplsLdpEntityGenericLREntry 6 } 4593 --**************************************************************** 4594 -- Module Conformance Statement 4595 --**************************************************************** 4597 mplsLdpGenericGroups 4598 OBJECT IDENTIFIER ::= { mplsLdpGenericConformance 1 } 4600 mplsLdpGenericCompliances 4601 OBJECT IDENTIFIER ::= { mplsLdpGenericConformance 2 } 4603 -- 4604 -- Full Compliance 4605 -- 4607 mplsLdpGenericModuleFullCompliance MODULE-COMPLIANCE 4608 STATUS current 4609 DESCRIPTION 4610 "The Module is implemented with support for 4611 read-create and read-write. In other words, 4612 both monitoring and configuration 4613 are available when using this MODULE-COMPLIANCE." 4614 MODULE -- this module 4615 MANDATORY-GROUPS { 4616 mplsLdpGenericGroup 4617 } 4619 OBJECT mplsLdpEntityGenericLRRowStatus 4620 SYNTAX RowStatus { active(1) } 4621 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 4622 DESCRIPTION 4623 "Support for createAndWait and notInService is not required." 4625 ::= { mplsLdpGenericCompliances 1 } 4627 -- 4628 -- Read-Only Compliance 4629 -- 4630 mplsLdpGenericModuleReadOnlyCompliance MODULE-COMPLIANCE 4631 STATUS current 4632 DESCRIPTION 4633 "The Module is implemented with support for 4634 read-only. In other words, only monitoring 4635 is available by implementing this MODULE-COMPLIANCE." 4636 MODULE -- this module 4637 MANDATORY-GROUPS { 4638 mplsLdpGenericGroup 4639 } 4641 OBJECT mplsLdpEntityGenericLabelSpace 4642 MIN-ACCESS read-only 4643 DESCRIPTION 4644 "Write access is not required." 4646 OBJECT mplsLdpEntityGenericIfIndexOrZero 4647 MIN-ACCESS read-only 4648 DESCRIPTION 4649 "Write access is not required." 4651 OBJECT mplsLdpEntityGenericLRStorageType 4652 MIN-ACCESS read-only 4653 DESCRIPTION 4654 "Write access is not required." 4656 OBJECT mplsLdpEntityGenericLRRowStatus 4657 SYNTAX RowStatus { active(1) } 4658 MIN-ACCESS read-only 4659 DESCRIPTION 4660 "Write access is not required, and active is the 4661 only status that needs to be supported." 4663 ::= { mplsLdpGenericCompliances 2 } 4665 -- 4666 -- units of conformance 4667 -- 4669 mplsLdpGenericGroup OBJECT-GROUP 4670 OBJECTS { 4671 mplsLdpEntityGenericLabelSpace, 4672 mplsLdpEntityGenericIfIndexOrZero, 4673 mplsLdpEntityGenericLRStorageType, 4674 mplsLdpEntityGenericLRRowStatus 4675 } 4676 STATUS current 4677 DESCRIPTION 4678 "Objects that apply to all MPLS LDP implementations 4679 using Generic Labels as the Layer 2." 4680 ::= { mplsLdpGenericGroups 1 } 4682 END 4684 5. Revision History 4686 NOTE TO RFC-Editor: before publishing this document as an RFC, 4687 please remove this Revision History (change log) section. 4689 5.1. Changes from 4691 Fix in the Full Compliance of the MPLS-LDP-STD-MIB module to remove 4692 MIN-ACCESS read-only from the mplsFecRowStatus and 4693 mplsLdpLspFecRowStatus objects. The DESCRIPTION clauses were also 4694 updated accordingly. 4696 5.2. Changes from 4698 These fixes were from the MIB Doctor Review. 4700 - bottom of page6 4701 s/MPLS-TC-MIB/MPLS-TC-STD-MIB/ 4703 - sect 3.6 first para 4704 change RFC2573 into RFC3413 4705 The citation [RFC2573] does not occur in the ref section either 4706 Neither doe RFC3413 4708 Fixed line lengths. 4710 5.3. Changes from 4712 Updated with comments from the 3rd Last Call for this MIB which took 4713 place, Thursday, June 12 to June 24, 2003. 4715 Updated with last call comments from Adrian Farrel posted to the MPLS 4716 Working Group email list on June 12, 2003. 4718 Updated the 2 outstanding issues from Bert's email May 9th which was 4719 posted to the MPLS Working Group. These issues were not updated for 4720 version 10, so were addressed in version 11: 1) updated #3 from that 4721 email and 2) reviewed all the InetAddressType and InetAddress objects 4722 to make sure that descriptions were per rfc3291. 4724 5.4. Changes from 4726 Renamed the MIB module to include Std and also updated the IANA 4727 Considerations Section to use mplsStdMIB. 4729 Updated per Bert's email May 9th, with 2 exceptions: 1) did not yet 4730 update #3 from that email and 2) did not yet review all the 4731 InetAddressType and InetAddress objects to make sure that 4732 descriptions were per rfc3291. 4734 Changed Ses to Session for clarity. 4736 5.5. Changes from 4738 Added the new MIB boiler plate and associated MIB reference changes. 4740 Reworked the OID tree structure so that the Modules only have the 4741 mplsMIB subid dependency. This was discussed in mpls wg email 4742 (discussion was mostly between Bert, Tom and Joan). 4744 Added IANA Considerations section. This contains 4 subsections, one 4745 per MIB module. 4747 Updated and added new references as needed. 4749 Changed mplsMIB subid values to agree with the latest "Multiprotocol 4750 Label Switching (MPLS) Management Overview" document, [MPLSMGMT]. 4752 Moved MIB modules around so that they would appear in subId order. 4753 The Generic MIB module is shown last, since the subid is 7 (which is 4754 the last (and largest) subid requested by IANA. 4756 5.5.1. Changes based on MIB Doctor Review Comments 4758 The following changes are based on comments from the MIB DR Review. 4759 The comments are from email to the mpls working group dated, Dec 6, 4760 2002. These comments are quoted and prefaced by "REQ: comment goes 4761 here", and then followed by our resolution. 4763 "REQ: - missing IPR section". RSP: it has been added. 4765 "REQ: - Security considerations probably needs more work 4766 Security ADs want you to explain what the vulnerabilities/risks 4767 are and what to do against them. 4768 Also for read only objects, pls list each (group of) object(s) 4769 and explain what sensitivity attributes they have". RSP: Done. We 4770 added subsections here since the Security template is MIB Module 4771 based and it seemed to us more clear to do a subsection per MIB 4772 Module. 4774 "REQ: - pls do the consistency checking for descriptors and all 4775 that". RSP: believe this to be done. Changed Gen to Generic 4776 everywhere, changed Fr to FrameRelay, changed RO to ReadOnly. 4777 Changed Sessions to Ses everywhere. Reviewed tables to make sure 4778 they were prefixed consistently. Added more references, used more 4779 TCs and other stuff. 4781 "REQ: - sect 3.5 1st sentence, s/would be/are/ ??". RSP: done. 4783 "REQ: - sect 3.5 2nd para first sentence s/initiation/initiate/ ". 4784 RSP: done. 4786 "REQ: - section 3.5.2 s/mpsl/mpls/". RSP: done. 4788 "REQ: - mplsXxxIndexNext 4789 See my comments on FTN MIB and LSR MIB on these type of objects 4790 Best to use something aka rfc3289 ". RSP: We have imported the 4791 IndexInteger and IndexIntegerNextFree TCs (from rfc3289.txt). NOTE: 4792 we do not like the names of these TCs because they use the term 4793 Integer when the values are Unsigned32. Would prefer new TCs with 4794 IndexUnsigned32 and IndexUnsigned32NextFree. 4796 "REQ:- RowStatus and StorageType objects 4797 see my comments about similar objects in LSR MIB 4798 for StorageType might also want to add a DEFVAL ". RSP: Added 4799 descriptive text to the RowStatus objects to specify which columns 4800 can be changed when row is active. Added descriptive text to the 4801 StorageType objects to specify what happens when the StorageType is 4802 permanent. Also added DEFVALs for the StorageType objects. 4804 "REQ: - mplsLdpNotifications ... { mplsLdpMib 2 } 4805 why not { mplsLdpMib 0} so that it is right away the prefix? 4806 I believe LSR MIB does it that way now. You may want to do 4807 it consistently for all notifications. 4808 I can live with either way, but prefer them to be shorter OIDs.". 4809 RSP: We changed this to follow what LSR MIB does (i.e. 4810 mplsLdpNotifications 0) for shorter OIDs..PP "REQ: - 4811 mplsXxxLastChange 4812 does that time stamp only get changed if an addition/deletion takes 4813 place? Not if something gets changed via a SNMP SET command? 4814 I think I'd prefer to also see changes (modifications) via SET. 4815 But in any event, be very explicit about if those are included or 4816 not.". RSP: All Last change object DESCRIPTIONs have been 4817 updated to be very specific. 4819 "REQ:- mplsLdpLspType 4820 All that stuff in the DESCRIPTION clause is just a repeat of the 4821 TC DESCRIPTION clause. Seems not needed to me. What if a value 4822 gets added later... how do you stay in sync?". RSP: This has 4823 been fixed. 4825 "REQ: - mplsFecAddrLength 4826 Should that be of SYNTAX InetAddressPrefixLength as per RFC3291?". 4827 RSP: yes, fixed. 4829 "REQ: - mplsFecAddrFamily and mplsFecAddr 4830 These are strange. The DESCRIPTIONS are certainly not meeting the 4831 requirements as specified in RFC3291. At other places you do it 4832 correct, so you do understand what is required I think.". RSP: 4833 changed to have a better descriptions. Should note that the TLVs in 4834 the LDP Specification use Address Family Numbers and are still 4835 referring to RFC1700. 4837 "REQ: - mplsLdpLspFecTable claims to be a read-only table. 4838 Yet you have a read-create RowStatus object in it.". RSP: fixed. 4840 "REQ: - mplsLdpSessionUp and mplsLdpSessionDown 4841 Is it not better to just have one notification, namely a 4842 mplsLdpSessionStateChange and then the mplsLdpSesState object will 4843 explain what the change is?". RSP: We prefer to leave it this 4844 way. There are some 3rd Party applications that try to resolve 4845 Notifications, so you see one for down, then resolve this by seeing 4846 another one for up. Granted, these 3rd party apps could be coded to 4847 parse the varbind within the trap, but then this requires coding 4848 whereas having 2 distinct notifications is easier on the developer. 4849 Granted, this maybe makes the MIB design more cumbersome. If this is 4850 a blocking issue, then we will change it. 4852 "REQ:- COMPLIANCE section. I hope that INT ADs are OK with making 4853 IPv6 4854 addresses optional. Is that cause current LDP only supports IPv4? 4855 If so you may want to add that as an explanation.". RSP: IPv6 4856 was made mandatory, also supported in MPLS LDP Spec (rfc3036.txt). 4858 Continue with MIB Dr Comments for the MPLS-LDP-GENERIC-MIB. 4860 "REQ:- same on mplsXXXIndexNext and RowStatus and STorageType 4861 objects". RSP: These hdescriptions have been updated. It should 4862 be noted, that these should be EXACTLY the same as the 4863 mplsLdpEntityTable since the Label Range Tables extend the Entity 4864 Table. "REQ:- this looks wierd: 4865 ::= { mplsMib 6 } -- to be assigned 4866 use cc instead of 6 if you want IANA to assign, and do tell 4867 -- to be assigned by IANA 4868 and write something about it in an IANA Considerations Section if 4869 this is what you want.". RSP: Added more comments, and added an 4870 IANA Considerations Section. "REQ:- mplsGenModuleROCompliance 4871 I would call it mplsGenModuleReadOnlyCompliance 4872 You have used ReadOnly and Full in other places/mib modules and 4873 it is good to be clear and consistent". RSP: done. 4875 MIB Doctor Review comments for ATM. 4877 "REQ:- s/Moduel/Module/". RSP: done. 4879 "REQ:- same on mplsXXXIndexNext and RowStatus and STorageType 4880 objects". RSP: done. 4882 "REQ:- this looks wierd: 4883 ::= { mplsMib 4 } -- to be assigned 4884 use cc instead of 4 if you want IANA to assign, and do tell 4885 -- to be assigned by IANA 4886 and write something about it in an IANA Considerations Section if 4887 this is what you want.". RSP: done. 4889 "REQ:- See earlier remark on Notifications (use zero instead of 2 4890 right away)". RSP:Removed this branch because there aren't any 4891 notifications in this MIB 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 2 of them in the ATM Module). The reason for leaving them is because 4899 the value zero is what the protocol uses. We have added REFERENCES 4900 to these objects and more info in the descriptions themselves. We 4901 believe it is in the best interest of developers to start enums at 4902 zero. The INET-ADDRESS-MIB uses the value zero, and since we are 4903 already required to use that MIB, there is precedence for zero in an 4904 enum where it makes sense. We believe the value of zero makes sense 4905 for where it is being used in this MIB module. 4907 "REQ:- mplsXxxxROCompliance -> better mplsXxxxReadOnlyCompliance". 4908 RSP: done. 4910 "REQ:- some formatting problems with DEFVAL lines being split on 2 4911 lines?". RSP: fixed. 4913 MIB Doctor Review comments for FrameRelay 4915 "REQ:- consistency in descriptors (FrameRelay vs FR etc)". RSP: 4916 done. "REQ:- same on mplsXXXIndexNext and RowStatus and STorageType 4917 objects". RSP: done. "REQ:- this looks wierd: 4918 ::= { mplsMib 5 } -- to be assigned 4919 use cc instead of 5 if you want IANA to assign, and do tell 4920 -- to be assigned by IANA 4921 and write something about it in an IANA Considerations Section if 4922 this is what you want.". RSP: done. "REQ:- See earlier remark 4923 on Notifications (use zero instead of 2 right away)". RSP:Removed 4924 this branch because there aren't any notifications in this MIB 4925 module. 4927 "REQ:- There are still some INTEGER enumerations that start with zero 4928 It is not a BLOCKING problem... but if acceptable, pls make it 4929 start 4930 at 1 (as you have done vor various others of these enumerations)". 4931 RSP: We would rather leave these enums starting with zero. (There are 4932 4 of them in the Frame Relay Module). The reason for leaving them is 4933 because the value zero is what the protocol uses. We have added 4934 REFERENCES to these objects and more info in the descriptions 4935 themselves. We believe it is in the best interest of developers to 4936 start enums at zero. The INET-ADDRESS-MIB uses the value zero, and 4937 since we are already required to use that MIB, there is precedence 4938 for zero in an enum where it makes sense. We believe the value of 4939 zero makes sense for where it is being used in this MIB module. 4941 "REQ:- mplsLdpEntityFrLRComponents OBJECT-TYPE 4942 SYNTAX Unsigned32 (1..65535) 4943 MAX-ACCESS read-create 4944 STATUS current 4945 DESCRIPTION 4946 "Number of Label Range Components in the Initialization 4947 message. This also represents the number of entries 4948 in the mplsLdpEntityConfFrLRTable which correspond 4949 to this entry." 4950 Where is this mplsLdpEntityConfFrLRTable ??". RSP: fixed. 4951 "REQ:- I see the xxxDlci index objects start at zero. 4952 Pls add to DESCRIPTION clauses why zero must be an index.". RSP: 4954 Since we are using DLCI and the value of zero is valid for a DLCI. A 4955 statement was added about this. Also, used the DLCI TC from 4956 rfc2115.txt to make this more clear. NOTE: the MPLS-LDP-ATM-MIB 4957 module uses an index of the VP which can also take on the value of 4958 zero. A statement was added to this Index also. "REQ:- 4959 mplsXxxxROCompliance -> better mplsXxxxReadOnlyCompliance". RSP: 4960 done. 4962 5.6. Changes from 4964 The following changes are from the IESG MIB review. 4966 Changed "Label Switch Router" to "Label Switching Router". 4968 Spelling errors fixed (unlabelled, atttempt, subsytem). 4970 Changed some of the enums to start at 1, instead of zero: 4971 mplsLdpPeerLoopDetectionForPV and mplsLdpEntityOperStatus. 4973 Added REFERENCE clauses. 4975 Added a timestamp object for mplsLdpSesState changes. 4977 Changed NMS to command generator as defined in RFC2571. 4979 Added a lastChange objects: mplsLdpEntityLastChange and 4980 mplsLdpPeerLastChange. 4982 Added TEXTUAL-CONVENTIONS for MplsLabelDistributionMethod and 4983 MplsRetentionMode. These TCs have been incorporated into draft-ietf- 4984 mpls-tc-mib-04.txt. 4986 Divided up the one MIB MODULE into 3 additional modules for a total 4987 of 4 MIB MODULES: 1) mplsLdpMIB, 2) mplsLdpGenericMIB which includes 4988 objects pertaining to Ethernet as the L2, 3) mplsLdpAtmMIB which 4989 includes objects pertaining to ATM as the L2, and 4) 4990 mplsLdpFrameRelayMIB which includes objects pertaining to Frame Relay 4991 as the L2. 4993 Also, reduced the number of objects by creating the mplsLdpLspTable 4994 and removing the Mapping tables. 4996 In section 3.1 changed "where each row in the table initiates" to 4997 "where each row in the table represents". 4999 Updated Reference Section and divided them into Normative vs. 5000 Informative. 5002 Removed the MplsGenAddress TC and used the INET-ADDRESS-MIB's 5003 InetAddress TC. Objects using this TC are: 5004 mplsLdpEntityTargetPeerAddr, mplsFecAddr, and 5005 mplsLdpSesPeerNextHopAddr and are noted in the conformance statements 5006 supporting: unknown(0), ipv4(1), and ipv6(2). 5008 Removed AddressFamilyNumbers TC and used InetAddressType TC from the 5009 INET-ADDRESS-MIB. One of the MIB compilers as a warning because 5010 apparently one is expected to use InetAddressType and InetAddress 5011 together (although, think this restriction is too restrictive). Also, 5012 removed the reference for the Address Family Numbers MIB. 5014 Changed the name TargPeer to TargetPeer. 5016 Removed the Enable/Disable trap objects: 5017 mplsLdpEntityPVLMisTrapEnable, and mplsLdpSesUpDownTrapEnable. RFC 5018 3413 should be used to enable/disable traps. 5020 Removed the import for "transmission" and instead, imported "mplsMIB 5021 from the MPLS-TC-STD-MIB". 5023 Changed mplsLdpEntityPVL to mplsLdpEntityPathVectorLimit and updated 5024 the DESCRIPTION clause. Also, the PVL abbreviation was expanded to 5025 PathVectorLimit for other objects. 5027 Combined the objects: mplsLdpPeerLoopDectionForPV and mplsLdpPeerPVL 5028 into one object: mplsLdpPeerPathVectorLimit and updated the 5029 DESCRIPTION clause. 5031 mplsLdpEntityTcpDscPort uses InetPortNumber TC from the INET-ADDRESS- 5032 MIB. Likewise, mplsLdpEntityUdpDscPort uses the InetPortNumber TC 5033 from the INET-ADDRESS-MIB. Also a REFERENCE clause was added. 5035 The mplsLdpEntityMaxPduLength object has the SYNTAX range changed to 5036 start at 256. Also the DESCRIPTION clause was updated. 5038 The mplsLdpSesMaxPduLen object's name was changed to 5039 mplsLdpSesMaxPduLength and a UNITS clause was added, and the 5040 DESCRIPTION clause was updated. This object is related to the 5041 mplsLdpEntityMaxPduLength object. 5043 The mplsLdpEntityKeepAliveHoldTimer and mplsLdpEntityHelloHoldTimer 5044 DESCRIPTION clause was changed from "The two octet value" to "The 5045 16-bit integer value". 5047 The mplsLdpEntityHelloHoldTimer object's DESCRIPTION clause was 5048 updated. 5050 A range of Integer32(0..100) was added to the SYNTAX clause of the 5051 mplsLdpEntityInitSesThreshold object. Also, the DESCRIPTION clause 5052 of this object was updated. 5054 The mplsLdpEntityOptionalParameters object was renamed to 5055 mplsLdpEntityLabelType. 5057 Updated the mplsLdpEntityAdminStatus and mplsLdpEntityRowStatus 5058 objects. RowStatus now reflects the status of the row, and Admin 5059 status controls enabling/disabling the entry. 5061 Updated the DESCRIPTION clauses for the objects in the 5062 mplsLdpEntityStatsTable to refer to the 5063 mplsLdpEntityDiscontinuityTime object. 5065 Changed StorType to StorageType. 5067 5.7. Changes from 5069 There were three types of changes: the first change was that all the 5070 MPLS Textual Conventions from this MIB, the LSR and MPLS-TE MIBs were 5071 moved into a new document [MPLSTCMIB], "draft-ietf-mpls-tc- 5072 mib-00.txt". The Textual Conventions are now IMPORTED from 5073 [MPLSTCMIB]. The second type of change was updates based on comments 5074 from the IESG. These changes will be discussed below. The third 5075 type of changes were based on minor editorial changes from the co- 5076 authors. 5078 The "Introduction" and "Structure of the MIB" sections were reworded 5079 since they were repetitive. 5081 The "Overview" was rearranged. 5083 References were added to "The LDP Entity ATM Objects" and "The LDP 5084 Entity Frame Relay Objects" Sections. 5086 The Working Group mailing list and Chairs were added to the CONTACT- 5087 INFO. 5089 Updated the DESCRIPTION clause for the "mplsLdpEntityLdpId" object. 5091 Updated the mplsLdpEntityProtocolVersion to include a range 5092 (1..65535). 5094 Updated the "References" Section. 5096 Running the MIB through the smilint MIB compiler showed that some 5097 object names were longer than 32 characters, these were shortened to 5098 32 characters or fewer. 5100 The following changes were from the co-authors. 5102 Other minor editorial changes such as fixing typographical errors, 5103 and removing MIB comments which are no longer meaningful. 5105 Page 17 (also page 46) the description was enhanced to describe the 5106 version field in the LDP header from RFC3036. 5108 Removed WellKnown from the tcp and upd port names. It's the ports 5109 that get set, and the default value is the well known (actually the 5110 registered) port number. 5112 mplsLdpEntityInitSesTrapEnable object is useless and was removed 5113 since setting mplsLdpEntityInitSesThreshold=0 acheives the same 5114 thing. Also removed it from the descriptive text in section 3. 5116 Page 47, mplsLdpSessionDiscontinuityTime The initial value of this 5117 was changed to be sysUpTime instead of zero. sysUpTime for when the 5118 session starts is more meaningful and was added to the Session 5119 Up/Down Traps also. Also, added the Session specific stats to the 5120 up/down traps. 5122 5.8. Changes from 5124 All changes were from the second last call which took place Thursday, 5125 July 20th, until Thursday, July 27th, 2000 and are described in the 5126 remainder of this section. 5128 Remove the reference to the MPLS framework document. 5130 Add an mplsFecIndexNext type of object. 5132 Change the conformance of the FEC table objects to be part of the 5133 mplsLdpGeneralGroup. 5135 The mplsLdpEntityConfGenericTable is no longer needed because the 5136 functionality has been absorbed by the 5137 mplsLdpEntityConfGenericLabelRangeTable. The 5138 mplsLdpEntityConfGenericTable has been removed and the front section 5139 was updated accordingly. 5141 Other editorial issues, updating references, typos and so forth. 5143 5.9. Changes from 5145 The majority of changes in this revision are based on Last Call 5146 comments which were received during the last call from Thursday, 5147 March 9, 2000 to Friday, March 17, 2000, or slightly thereafter. 5148 Also, changes were made to agree with the latest specifications. 5149 These changes are described in this section. 5151 Changes due to draft-ietf-mpls-ldp-07.txt and draft-ietf-mpls- 5152 ldp-08.txt. Specifically, removing references to IPv4/IP and using 5153 router id, as appropriate. 5155 Removed vpMerge and vpAndVcMerge choices from the object, 5156 mplsLdpEntityAtmMergeCap. VP Merge is not described in [RFC3036]. 5158 The LIB Table was removed and replaced by mapping tables to map LDP 5159 LSPs created by LDP sessions to the mplsInSegment, mplsOutSegment and 5160 mplsXC tables in the LSR MIB. The conformance section was updated 5161 to include a Mapping Group which is to be implemented iff these LSR 5162 MIB tables (mplsInSegmentTable, mplsOutSegmentTable and mplsXCTable) 5163 are implemented. 5165 The front section was updated to include information on the Generic 5166 label table. 5168 Added more in the front section on on Row 5169 Creation/adminStatus/OperStatus in the LDP Entity and related tables. 5171 Added a generic label range table. NOTE: there is NO corresponding 5172 LDP message which relates to the information in this table, however, 5173 this table does provide a way for a user to 'reserve' a generic label 5174 range. 5176 A new TEXTUAL-CONVENTION, MplsAtmVcIdentifier was added. This TC has 5177 the same upper bounds as AtmVcIdentifier (from rfc2514) except that 5178 the lower bound is 32 (and not 0). The lower bound is 32 since this 5179 value is specified by [RFC3035]. 5181 Removed the scalar object mplsLsrLabelRetentionMode and added 5182 mplsLdpEntityLabelRetentionMode. The change was made to allow 5183 configuring the retention mode on a per LDP Entity basis, as opposed 5184 for the entire LSR. 5186 Typo in section 3.5.2 was fixed. 5188 Typo in the mplsLdpSessionUp notification description was fixed. 5190 Section 'LDP Notifications' was expanded to cover both the 5191 'mplsLdpSessionUp' and 'mplsLdpSessionDown' traps. Also, the objects 5192 which enable and disable these traps have been described in this 5193 Section: 5195 The 'mplsLdpEntityHopCountLoopDetection' object and the 5196 'mplsLdpEntityHopCount' object have been combined into the new 5197 object, 'mplsLdpEntityHopCountLimit'. 5199 MplsLabel has been updated to reflect the VPI value of 12 bits and 5200 not 8. 5202 Added DEFVAL clause to the 'mplsLdpEntityWellKnownDiscoveryPort' 5203 object. The default value is 646. 5205 Added UNITS and DEFVAL clauses to the 'mplsLdpEntityMaxPduLength' 5206 object. The default value is 4096 and the units is octets. 5208 Added DEFVAL clause to 'mplsLdpEntityProtocolVersion' object. The 5209 default value is 1. 5211 Added DEFVAL clause to 'mplsLdpEntityKeepAliveHoldTimer' of 40 5212 seconds. 5214 Added DEFVAL clause to 'mplsLdpEntityInitSesThreshold' object. The 5215 default value is 8. 5217 The mplsLdpEntityWellKnownDiscoveryPort was changed into two objects, 5218 one for TCP and one for UDP. The names are 5220 Typo in the description for the 5222 The mplsLdpEntityPeerTable was (re-)named mplsLdpPeerTable. The 5223 mplsLdpSessionTable now AUGMENTs the mplsLdpPeerTable in order to 5224 show that these two tables are related. There has been wording added 5225 to the mplsLdpSessionEntry description and to the description for the 5226 mplsLdpPeerTable. 5228 5.10. Changes from 5230 Editorial changes, fixing typo's, fixing wrapping lines, etc. 5232 Updated references for latest drafts, and added [RFC3032] and 5233 [RFC3034] to Reference Section. 5235 Added to the Acknowledgements Section. 5237 Changed the SYNTAX and DESCRIPTION of the 5238 'mplsLdpLsrLoopDetectionCapable' object, so that it will also support 5239 the loop detection by hop count. 5241 Combined the 'mplsLdpEntityLoopDetectionForPV' and 'mplsLdpEntityPVL' 5242 objects. The functionality of the 'mplsLdpEntityLoopDectionForPV' is 5243 now denoted by the value of 0 (zero) in the 'mplsLdpEntityPVL' 5244 object. This results in one less object 5245 'mplsLdpEntityLoopDectionForPV' but does not sacrifice functionality. 5247 Changed 'mplsLdpLibLabelType' into two objects: 5248 'mplsLdpLibInLabelType' and differ from the egress label type. The 5249 MIB now reflects this. 5251 The following items were changed as a result of the Frame Relay Forum 5252 dropping support for 17-bit DLCIs: the MplsLabel TC description has 5253 been modified, and other Frame Relay Object descriptions were also 5254 modified (as specified in this section). 5256 The MplsLabel TC was also modified and reference 3. was added to the 5257 REFERENCE Clause. 5259 MplsLdpLabelTypes TC was modified to use an enum. 5261 InterfaceIndex support was added to the Entity information. This was 5262 specifically requested by several members of the working group. An 5263 additional table, mplsLdpEntityConfGenericTable as a way to configure 5264 Generic Labels, and an object, 'mplsLdpConfGenericIfIndexOrZero was 5265 added to map the InterfaceIndex used by Generic Labels. Objects were 5266 also added to the 'mplsLdpEntityAtmParmsTable' and the and 5267 'mplsLdpEntityFrIfIndex', respectively. 5269 Changed the name of the 'mplsLdpEntityMtu' object to be 5270 'mplsLdpEntityMaxPduLength' which is more consistent with the LDP 5271 Specification. Also, the description and SYNTAX were changed. 5273 Changed the SYNTAX of the 'mplsLdpSessionMaxPduLength' to unsigned32 5274 and changed the Range from (0..65535) to (1..65535). 5276 Added and improved the front section discussion on SNMP 5277 Notifications. 5279 Also, modified the DESCRIPTION clause of the 5281 Added objects to enable/disable the sending of traps: 5283 Added an object to enable/disable sending traps for Sessions changing 5284 from Up to Down, or Down to Up. 5286 Added notifications to generate traps from session changing from Up 5287 to Down, or Down to up. 5289 Added a StorageType object to the Entity and associated tables which 5290 are configurable. 5292 Added a Discontinuity Time object to the Entity Table, 5294 Added discussion on row creation in the Entity and other associated 5295 Entity tables. This is a new Section in the Front part of the 5296 document called: 5298 Removed the 'mplsLdpEntityControlMethod'. 5300 Made 'mplsLdpFecLspId' as part of the INDEX for the FEC table. This 5301 is to allow FECs to map to multiple LSPs. Also add a RowPointer to a 5302 row in the Session Table. 5304 Added an operation status object, 'mplsLdpLspOperStatus' and a last 5305 Change object, 'mplsLdpLspLastChangeto the LIB Table. This will be 5306 used to detect whether an LSP has changed its status. 5308 Changed the name of the mplsLdpPeerTable to the 5309 mplsLdpEntityPeerTable. This table contains information relevant to 5310 Peers which are known to specific Entities. The indexing of this 5311 table has also changed to include the Row in the Entity Table that 5312 this Peer is known by. The mplsLdpHelloAdjacencyTable and the 5313 mplsLdpSessionTable have been moved under this table. Since Hello 5314 Adjacencies are related to Entity-Peer information and Sessions are 5315 related to Entity-Peer information this was seen as a comprehensive 5316 and coherent modelling. Associated descriptions in the front section 5317 and in the tables have been changed to reflect this change. 5319 Moved the 'mplsLdpConfFrLen' object from the 5320 'mplsLdpEntityConfFrLabelRangeTable' to the 5321 'mplsLdpEntityFrameRelayParmsTable' since the Frame Relay 5322 interface/port can only use one header length at a time, i.e. a 5323 specific FR interface supports one address length for all VCs on that 5324 interface. Also, changed the object so that it only supports 10 and 5325 23 bit DLCI lengths. (The 17 bit length was dropped by the Frame 5326 Relay Forum and thus, is no longer required.) The name of this 5327 object was changed from 'mplsLdpConfFrLen' to 'mplsLdpEntityFrLen' to 5328 fit in with the 'mplsLdpEntityFrameRelayParmsTable'. 5330 Removed the seventeenDlciBits(1) value from the mplsLdpFrSessionLen 5331 object. (The 17 bit length was dropped by the Frame Relay Forum and 5332 thus, is no longer required.) 5334 Corrected the range of the 'mplsLdpEntityIndexNext' object to include 5335 0 (zero). 5337 5.11. Changes from 5339 Reworded the description of the mplsLdpAtmSessionTable to clarify 5340 that one or MORE label range intersection(s) is/are represented in 5341 this table. 5343 Reworded the description of the mplsLdpFrameRelaySessionTable to 5344 clarify that one or MORE label range intersection(s) is/are 5345 represented in this table. 5347 Added a new index, mplsLdpSessionPeerIndex, to the 5348 mplsLdpSessionPeerAddressTable. This new index uniquely identifies 5349 the entry within a given session. (Since adding 5350 mplsLdpSessionPeerNextHopAddressType, 5351 mplsLdpSessionPeerNextHopAddress to the INDEX clause of the 5352 mplsLdpSessionPeerAddressTable leaves a table with only indices and 5353 no objects, the work around was to add a new index which uniquely 5354 differentiates an entry within a given session.) 5356 Quite a few changes to the mplsLdpPeerTable. First, removed the 5357 mplsLdpPeerIndex from the mplsLdpPeerTable and other tables. This 5358 index served no purpose, so was removed. Second, removed the 5359 objects: mplsLdpPeerInternetworkAddrType, and 5360 mplsLdpPeerInternetworkAddr. Third, reworded the description of this 5361 table to include information which is known during Session 5362 Intialization attempts, the specific information has to do with Loop 5363 Dection based on Path Vectors. Since Section 3.5.3 of the LDP Spec 5364 when describing the PVLim says: "Although knowledge of a peer's path 5365 vector limit will not change an LSR's behavior, it does enable the 5366 LSR to alert an operator to a possible misconfiguration." and the 5367 object mplsLdpPeerPVL is sent as a varbind in the mplsLdpPVLMismatch 5368 notification. 5370 Removed the mplsLdpPeerIndex from the mplsLdpHelloAdjacencyTable. 5372 Removed the "IANA Address Family Numbers" MIB section. 5374 Updated the boiler.me from the ops web page dated Weds., Dec 22, 5375 1999. 5377 Updated the Security Section from the ops web page. 5379 Added the following objects to the mplsLdpEntityTable: 5380 mplsLdpEntityControlMethod, mplsLdpEntityLoopDectionForPV, and 5381 mplsLdpEntityPathVectorLimit. 5383 Removed mplsLdpSessionLabelAdvertisement, 5384 mplsLdpSessionLoopDetectionForPV, and mplsLdpSessionPathVectorLimit 5385 from the mplsLdpSessionTable. 5387 Changed the mplsLdpPathVectorLimitMismatch Notification to send 5388 mplsLdpEntityPathVectorLimit (instead of 5389 mplsLdpSessionPathVectorLimit). 5391 Copied the MplsLabel TC from draft-ietf-mpls-lsr-mib-00.txt and 5392 replaced the MplsLdpGenAddr for mplsLdpLibInLabel and 5393 mplsLdpLibOutLabel with MplsLabel. 5395 The mplsLdpSessionIndex was removed throughout the MIB. This was 5396 replaced by the object mplsLdpSessionDiscontinuityTime. The 5397 motivation was to reduce the number of indices. 5399 The descriptions for the objects in the mplsLdpSessionStatsTable, 5400 mplsLdpSessionStatsUnknownMessageTypeErrors and 5401 mplsLdpSessionStatsUnknownTlvErrors, have been updated to include a 5402 reference to the mplsLdpSessionDiscontinuityTime object. 5404 5.12. Changes from 5406 Added Scalar Objects: mplsLdpLsrLoopDetectionPresent, and 5407 mplsLdpEntityIndexNext. 5409 Added the following objects to the mplsLdpEntityTable: 5411 mplsLdpEntityProtocolVersion, mplsLdpEntityAdminStatus, 5412 mplsLdpEntityOperStatus, mplsLdpEntityTargetedPeer, 5413 mplsLdpEntityTargetedPeerAddrType, mplsLdpEntityTargetedPeerAddr, and 5414 mplsLdpEntityHelloHoldTimer. 5416 Changed the description of the mplsLdpEntityAtmParmsTable and added 5417 the following objects to this table: mplsLdpEntityAtmLsrConnectivity, 5418 mplsLdpEntityDefaultControlVpi, mplsLdpEntityDefaultControlVci, 5419 mplsLdpEntityUnlabTrafVpi, and mplsLdpEntityUnlabTrafVci. NOTE: the 5420 last four objects were in Version 01 of the MIB but were mistakenly 5421 omitted from Version 02. Now, they are back. 5423 Changed the indexing of the mplsLdpEntityConfAtmLabelRangeTable to 5424 include the minimum VPI/VCI. This is to ensure that indices in this 5425 table are unique. 5427 Changed the indexing of the mplsLdpEntityConfFrLabelRangeTable, to 5428 include the minimum DLCI value. This is to ensure that indices in 5429 this table are unique. 5431 Added [RFC3036] to Reference Section. 5433 5.13. Changes from 5435 The MIB was updated to correspond to draft-ietf-mpls-ldp-06.txt of 5436 the LDP Specification [RFC3036]. 5438 The front section was updated. 5440 The MIB was made to be less ATM-centric. Essentially, the ATM 5441 specific objects where removed from the tables and placed in ATM 5442 specific Tables. A type was added to the base tables and a row is to 5443 be created in the ATM/FR/etc. type table. Apropos compliance 5444 statements were added to reflect the separation of ATM and Frame 5445 Relay objects into their respective tables. 5447 Objects for Loop Detection were removed from describing the LDP 5448 implementation (i.e. the scalars were removed) and Loop Dection 5449 objects were added to the Session Table. (Although as the LDP 5450 Specification indicates loop detection should be for an LSR within a 5451 domain.) 5453 The following tables were added: mplsLdpEntityAtmParmsTable, 5454 mplsLdpEntityConfAtmLabelRangeTable, mplsLdpFrameRelayParmsTable, 5455 mplsLdpConfFrLabelRangeTable, mplsLdpAtmSessionTable, 5456 mplsLdpFrameRelaySessionTable, mplsLdpSessionPeerAddressTable, 5457 mplsLdpLibTable, and the mplsLdpFecTable. 5459 The following notifications were added: notification for Session 5460 removal. 5462 The following objects were removed from the Session Table: 5463 mplsLdpSessionRole was removed (this can be determined by comparing 5464 LSR Ids and does not need to be explicitly in the MIB.) ATM specific 5465 objects (mplsLdpSessionAtmLabelRangeLowerBoundVpi 5466 mplsLdpSessionAtmLabelRangeLowerBoundVci, 5467 mplsLdpSessionAtmLabelRangeUpperBoundVpi 5468 mplsLdpSessionAtmLabelRangeUpperBoundVci) were removed and put into a 5469 separate table. Frame Relay objects were added in a separate table. 5471 Hello Adjacency Table was updated. 5473 The objects, mplsLdpSessionRejectedParamErrors, 5474 mplsLdpSessionRejectedNoHelloErrors, mplsLdpBadLdpIdentifierErrors, 5475 mplsLdpBadPduLengthErrors, mplsLdpBadMessageLengthErrors, 5476 mplsLdpBadTlvLengthErrors, mplsLdpMalformedTlvValueErrors, 5477 mplsLdpKeepAliveTimerExpiredErrors, mplsLdpShutdownNotifReceived, and 5478 mplsLdpShutdownNotifSent were added to the mplsLdpEntityStatsTable. 5480 The mplsLdpSessionStatsTable was added to count statics based on a 5481 per Session basis. 5483 The mplLdpPeerConfAtmLabelRangeTable has been removed. There is no 5484 need to configure information for a Peer. All information for a peer 5485 is learned, thus peer information is read-only. 5487 (Editorial) References were updated to reflect the documents which 5488 this version was based on. 5490 5.14. Changes from 5492 Textual conventions were added for the LSR Identifier and the LDP 5493 Identifier. 5495 Top-level mib structure was added. The LDP MIB falls under a proposed 5496 hierarchy of mpls.mplsProtocols. 5498 The mib hierarchy within the LDP MIB was also changed. A new branch, 5499 under mpls.mplsProtocols.mplsLdpMIB.mplsLdpObjects was added. This 5500 branch is mplsLdpLsrObjects. Currently, this contains several new 5501 scalar objects: mplsLdpLsrID, mplsLdpLsrLoopDetectionPresent, 5502 mplsLdpLsrLoopDetectinAdminStatus, mplsLdpLsrPathVectorLimit, 5503 mplsLdpLsrHopCountLimit, mplsLdpLsrLoopPreventionPresent, 5504 mplsLdpLsrLoopPreventionAdminStatus, and 5505 mplsLdpLsrLabelRetentionMode. 5507 mplsLdpEntityTable is now indexed by mplsLdpEntityIdentifier, which 5508 is the LDP Identifier used in Session establishment. 5509 mplsLdpEntityLoopDetection and mplsLdpEntityLoopPrevention objects 5510 were removed from this table. 5512 The following objects were added to the mplsLdpEntityTable: 5513 mplsLdpEntityLabelSpaceType, mplsLdpEntityUnlabTrafVpi, 5514 mplsLdpEntityUnlabTrafVci, mplsLdpEntityMergeCapability, 5515 mplsLdpEntityVcDirectionality, and 5516 mplsLdpEntityLabelDistributionMethod. 5518 The following objects were added to the mplsLdpPeerEntityTable: 5519 mplsLdpPeerLabelDistributionMethod. 5521 The following object was removed from the mplsLdpEntityStatsTable: 5522 mplsLdpEntityEstablishedSessions. 5524 References were added and revised. 5526 6. Acknowledgments 5528 This document is a product of the MPLS Working Group. The authors 5529 would like to thank Mike MacFadden and Adrian Farrel for their 5530 helpful comments on several reviews. Also, the authors would like to 5531 give a special acknowledgement to Bert Wijnen for his many detailed 5532 reviews. Bert's assistance and guidance is greatly appreciated. 5534 We would also like to thank Cheenu Srinivasan, Arun Viswanathan and 5535 Thomas D. Nadeau, the authors of the MPLS-LSR-STD-MIB [LSRMIB], for 5536 their assistance. 5538 Additionally, there have been other members of the working group that 5539 have been very helpful: Alan Kullberg from NetPlane Systems gave 5540 input on earlier versions of this document, and more recently, Riza 5541 Cetin of Alcatel and Neil Jerram of Data Connection who both provided 5542 MIB objects. 5544 Early versions of this document were also reviewed by colleagues at 5545 Nortel Networks and Ericsson. The authors would like to thank the 5546 following people: Leigh McLellan, Geetha Brown, Geping Chen and 5547 Charlan Zhou from Nortel Networks, and Zoltan Takacs and Bo 5548 Augustsson from Ericsson. 5550 7. Normative References 5552 [RFC2115] Brown, C., and F. Baker, "Management Information Base for 5553 Frame Relay DTEs Using SMIv2", RFC 2115, September 1997. 5555 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 5556 Requirement Levels", BCP 14, RFC 2119, Harvard University, 5557 March 1997 5559 [RFC2514] Noto, M., E. Spiegel, K. Tesink, editors, "Definition of 5560 Textual Conventions and OBJECT-IDENTITIES for ATM 5561 Management", RFC 2514, February 1999. 5563 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 5564 Rose, M. and S. Waldbusser, "Structure of Management 5565 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 5566 1999. 5568 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 5569 Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", 5570 STD 58, RFC 2579, April 1999. 5572 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 5573 Rose, M. and S. Waldbusser, "Conformance Statements for 5574 SMIv2", STD 58, RFC 2580, April 1999. 5576 [RFC2863] McCloghrie, K., F. Kastenholz, "The Interfaces Group MIB 5577 using SMIv2", RFC 2863, June 2000. 5579 [RFC3031] Rosen, E., Viswananthan, A., and R. Callon, "Multiprotocol 5580 Label Switching Architecture", RFC 3031, January 2001. 5582 [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., Farinacci, 5583 D., Li, T. and A. Conta, "MPLS Label Stack Encoding", RFC 5584 3032, January 2001. 5586 [RFC3034] Conta, A., Doolan, P., and A. Malis, "Use of Label Switching 5587 on Frame Relay Networks Specification", RFC 3034, January 5588 2001. 5590 [RFC3035] Davie, B., Lawrence, J., McCloghrie, K., Rosen, E., Swallow, 5591 G., Rekhter, Y. and P. Doolan, "MPLS using LDP and ATM VC 5592 Switching", RFC 3035, January 2001. 5594 [RFC3036] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and B. 5595 Thomas, "LDP Specification", RFC 3036, January 2001. 5597 [RFC3037] Thomas, B. and E. Gray, "LDP Applicability", RFC 3037, 5598 January 2001. 5600 [RFC3215] Boscher, C., Cheval, P., Wu L. and E. Gray, "LDP State 5601 Machine", RFC 3215, January 2002. 5603 [RFC3289] Baker, F., Chan, K. and A. Smith, "Management Information 5604 Base for the Differentiated Services Architecture", RFC 5605 3289, May 2002. 5607 [RFC3291] Daniele, M., Haberman, B., Routhier, S. and J. 5608 Schoenwaelder, "Textual Coventions for Internet Network 5609 Addresses", RFC 3291, May 2002. 5611 [RFC3413] Levi, D., Meyers, P., and B. Stewart, "Simple Network 5612 Management Protocol (SNMP) Applications", December 2002. 5614 [LSRMIB] Srinivansan, C., Viswanathan, A., and T. Nadeau, "MPLS 5615 Label Switching Router Management Information Base Using 5616 SMIv2", draft-ietf-mpls-lsr-mib-12.txt, August 2003. 5618 [MPLSTCMIB] Nadeau, T., J. Cucchiara, (Eds.) "Definitions of Textual 5619 Conventions for Multiprotocol Label Switching Management", 5620 draft-ietf-mpls-tc-mib-09.txt, August 2003. 5622 8. Informative References 5624 [RFC2026] S. Bradner, "The Internet Standards Process -- Revision 3", 5625 RFC 2026, October 1996. 5627 [RFC2684] Grossman, D., and J. Heinanen, "Multiprotocol Encapsulation 5628 over ATM Adaptation Layer 5", RFC 2684, September 1999. 5630 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 5631 "Introduction and Applicability Statements for Internet- 5632 Standard Management Framework", RFC 3410, December 2002. 5634 [MPLSMGMT] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol 5635 Label Switching (MPLS) Management Overview", draft-ietf- 5636 mpls-mgmt-overview-08.txt, August 2003. 5638 9. Security Considerations 5640 This Security Considerations section consists of 4 subsections, one 5641 for each of the MIB Modules in this document. 5643 9.1. Security Considerations for MPLS-LDP-STD-MIB 5645 There are a number of management objects defined in this MIB module 5646 with a MAX-ACCESS clause of read-write and/or read-create. Such 5647 objects may be considered sensitive or vulnerable in some network 5648 environments. The support for SET operations in a non-secure 5649 environment without proper protection can have a negative effect on 5650 network operations. These are the tables and objects and their 5651 sensitivity/vulnerability: 5653 o the mplsLdpEntityTable contains objects to provision potential 5654 LDP sessions on the Label Switching Router (LSR) or Label Edge 5655 Router (LER). The mplsLdpLspFecTable contains objects which 5656 associate an LSP with a FEC. Unauthorized access to objects in 5657 these tables, could result in disruption of traffic on the 5658 network. This is especially true if an LDP session has been 5659 established. The use of stronger mechanisms such as SNMPv3 5660 security should be considered where possible. Specifically, 5661 SNMPv3 VACM and USM MUST be used with any v3 agent which 5662 implements this MIB. Administrators should consider whether 5663 read access to these objects should be allowed, since read 5664 access may be undesirable under certain circumstances. 5666 Some of the readable objects in this MIB module i.e., "objects with a 5667 MAX-ACCESS other than not-accessible", may be considered sensitive or 5668 vulnerable in some network environments. It is thus important to 5669 control even GET and/or NOTIFY access to these objects and possibly 5670 to even encrypt the values of these objects when sending them over 5671 the network via SNMP. These are the tables and objects and their 5672 sensitivity/vulnerability: 5674 o the mplsLdpEntityTable, mplsLdpPeerTable, mplsLdpSesTable and 5675 mplsLdpSesStatsTable collectively show the LDP LSP network 5676 topology. If an Administrator does not want to reveal the LDP 5677 LSP topology of the network, then these tables should be 5678 considered sensitive/vulnerable. 5680 9.2. Security Considerations for MPLS-LDP-ATM-STD-MIB 5682 There are a number of management objects defined in this MIB module 5683 with a MAX-ACCESS clause of read-write and/or read-create. Such 5684 objects may be considered sensitive or vulnerable in some network 5685 environments. The support for SET operations in a non-secure 5686 environment without proper protection can have a negative effect on 5687 network operations. These are the tables and objects and their 5688 sensitivity/vulnerability: 5690 o the mplsLdpEntityAtmTable and mplsLdpEntityAtmLRTable contain 5691 objects to provision potential LDP sessions on the Label 5692 Switching Router (LSR) or Label Edge Router (LER) over Layer 2 5693 of ATM. These tables extend the mplsLdpEntityTable in the MPLS- 5694 LDP-MIB. Unauthorized access to objects in these tables, could 5695 result in disruption of traffic on the network. This is 5696 especially true if an LDP session has been established. The use 5697 of stronger mechanisms such as SNMPv3 security should be 5698 considered where possible. Specifically, SNMPv3 VACM and USM 5699 MUST be used with any v3 agent which implements this MIB. 5700 Administrators should consider whether read access to these 5701 objects should be allowed, since read access may be undesirable 5702 under certain circumstances. 5704 Some of the readable objects in this MIB module i.e., "objects with a 5705 MAX-ACCESS other than not-accessible", may be considered sensitive or 5706 vulnerable in some network environments. It is thus important to 5707 control even GET and/or NOTIFY access to these objects and possibly 5708 to even encrypt the values of these objects when sending them over 5709 the network via SNMP. These are the tables and objects and their 5710 sensitivity/vulnerability: 5712 o the mplsLdpEntityAtmTable and mplsLdpEntityAtmLRTable show the 5713 Label Ranges for ATM. If an Administrator does not want to 5714 reveal this information then these tables should be considered 5715 sensitive/vulnerable and treated accordingly. 5717 9.3. Security Considerations for MPLS-LDP-FRAME-RELAY-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 mplsLdpEntityFrameRelayTable and 5728 mplsLdpEntityFrameRelayLRTable contain objects to provision 5729 potential LDP sessions on the Label Switching Router (LSR) or 5730 Label Edge Router (LER) over Layer 2 of Frame Relay. These 5731 tables extend the mplsLdpEntityTable in the MPLS-LDP-MIB. 5732 Unauthorized access to objects in these tables, could result in 5733 disruption of traffic on the network. This is especially true 5734 if an LDP session has been established. The use of stronger 5735 mechanisms such as SNMPv3 security should be considered where 5736 possible. Specifically, SNMPv3 VACM and USM MUST be used with 5737 any v3 agent which implements this MIB. Administrators should 5738 consider whether read access to these objects should be allowed, 5739 since read access may be undesirable under certain 5740 circumstances. 5742 Some of the readable objects in this MIB module i.e., "objects with a 5743 MAX-ACCESS other than not-accessible", may be considered sensitive or 5744 vulnerable in some network environments. It is thus important to 5745 control even GET and/or NOTIFY access to these objects and possibly 5746 to even encrypt the values of these objects when sending them over 5747 the network via SNMP. These are the tables and objects and their 5748 sensitivity/vulnerability: 5750 o the mplsLdpEntityFrameRelayTable and 5751 mplsLdpEntityFrameRelayLRTable show the Label Ranges for Frame 5752 Relay. If an Administrator does not want to reveal this 5753 information then these tables should be considered 5754 sensitive/vulnerable and treated accordingly. 5756 9.4. Security Considerations for MPLS-LDP-GENERIC-STD-MIB 5758 There are a number of management objects defined in this MIB module 5759 with a MAX-ACCESS clause of read-write and/or read-create. Such 5760 objects may be considered sensitive or vulnerable in some network 5761 environments. The support for SET operations in a non-secure 5762 environment without proper protection can have a negative effect on 5763 network operations. These are the tables and objects and their 5764 sensitivity/vulnerability: 5766 o the mplsLdpEntityGenericLRTable contains objects to provision 5767 potential LDP sessions on the Label Switching Router (LSR) or 5768 Label Edge Router (LER) over Layer 2 of Ethernet. This table 5769 extends the mplsLdpEntityTable in the MPLS-LDP-MIB. 5770 Unauthorized access to objects in these tables, could result in 5771 disruption of traffic on the network. This is especially true 5772 if an LDP session has been established. The use of stronger 5773 mechanisms such as SNMPv3 security should be considered where 5774 possible. Specifically, SNMPv3 VACM and USM MUST be used with 5775 any v3 agent which implements this MIB. Administrators should 5776 consider whether read access to these objects should be allowed, 5777 since read access may be undesirable under certain 5778 circumstances. 5780 Some of the readable objects in this MIB module i.e., "objects with a 5781 MAX-ACCESS other than not-accessible", may be considered sensitive or 5782 vulnerable in some network environments. It is thus important to 5783 control even GET and/or NOTIFY access to these objects and possibly 5784 to even encrypt the values of these objects when sending them over 5785 the network via SNMP. These are the tables and objects and their 5786 sensitivity/vulnerability: 5788 o the mplsLdpEntityGenericLRTable shows the Label Ranges for 5789 ethernet. If an Administrator does not want to reveal this 5790 information then these tables should be considered 5791 sensitive/vulnerable and treated accordingly. 5793 9.5. Additional Security Considerations 5795 The following paragraphs describe additional security considerations 5796 which are applicable to all 4 of the MIB Modules in this document. 5798 SNMP versions prior to SNMPv3 did not include adequate security. 5799 Even if the network itself is secure "for example by using IPSec", 5800 even then, there is no control as to who on the secure network is 5801 allowed to access and GET/SET "read/change/create/delete" the objects 5802 in this MIB module. 5804 It is RECOMMENDED that implementers consider the security features as 5805 provided by the SNMPv3 framework "see [RFC3410], section 8", 5806 including full support for the SNMPv3 cryptographic mechanisms "for 5807 authentication and privacy". 5809 Further, deployment of SNMP versions prior to SNMPv3 is NOT 5810 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 5811 enable cryptographic security. It is then a customer/operator 5812 responsibility to ensure that the SNMP entity giving access to an 5813 instance of this MIB module, is properly configured to give access to 5814 the objects only to those principals "users" that have legitimate 5815 rights to indeed GET or SET "change/create/delete" them. 5817 10. IANA Considerations 5819 As described in [MPLSMGMT] and as requested in the MPLS-TC-STD-MIB 5820 [MPLSTCMIB], MPLS related standards track MIB modules should be 5821 rooted under the mplsStdMIB subtree. There are 4 MPLS MIB Modules 5822 contained in this document, each of the following "IANA 5823 Considerations" subsections requests IANA for a new assignment under 5824 the mplsStdMIB subtree. New assignments can only be made via a 5825 Standards Action as specified in [RFC2434]. 5827 10.1. IANA Considerations for MPLS-LDP-STD-MIB 5829 The IANA is requested to assign { mplsStdMIB 4 } to the MPLS-LDP-STD- 5830 MIB module specified in this document. 5832 10.2. IANA Considerations for MPLS-LDP-ATM-STD-MIB 5834 The IANA is requested to assign { mplsStdMIB 5 } to the MPLS-LDP-ATM- 5835 STD-MIB module specified in this document. 5837 10.3. IANA Considerations for MPLS-LDP-FRAME-RELAY-STD-MIB 5839 The IANA is requested to assign { mplsStdMIB 6 } to the MPLS-LDP- 5840 FRAME-RELAY-STD-MIB module specified in this document. 5842 10.4. IANA Considerations for MPLS-LDP-GENERIC-STD-MIB 5844 The IANA is requested to assign { mplsStdMIB 7 } to the MPLS-LDP- 5845 GENERIC-STD-MIB module specified in this document. 5847 11. Intellectual Property Notice 5849 The IETF takes no position regarding the validity or scope of any 5850 intellectual property or other rights that might be claimed to 5851 pertain to the implementation or use of the technology described in 5852 this document or the extent to which any license under such rights 5853 might or might not be available; neither does it represent that it 5854 has made any effort to identify any such rights. Information on the 5855 IETF's procedures with respect to rights in standards-track and 5856 standards-related documentation can be found in BCP-11 [RFC2028]. 5857 Copies of claims of rights made available for publication and any 5858 assurances of licenses to be made available, or the result of an 5859 attempt made to obtain a general license or permission for the use of 5860 such proprietary rights by implementors or users of this 5861 specification can be obtained from the IETF Secretariat. 5863 The IETF invites any interested party to bring to its attention any 5864 copyrights, patents or patent applications, or other proprietary 5865 rights that may cover technology that may be required to practice 5866 this standard. Please address the information to the IETF Executive 5867 Director. 5869 12. Authors' Addresses 5871 James V. Luciani 5872 Marconi Communications, Inc. 5873 2000 Marconi Drive 5874 Warrendale, PA 15086 5875 USA 5876 Email: james_luciani@mindspring.com 5878 Hans Sjostrand 5879 ipUnplugged 5880 P.O. Box 101 60 5881 S-121 28 Stockholm, Sweden 5882 Phone: +46 8 725 5930 5883 Email: hans@ipunplugged.com 5884 Joan Cucchiara 5885 Artel 5886 237 Cedar Hill Street 5887 Marlborough, MA 01752 5888 Phone: +1-508-303-8200 x302 5889 Email: jcucchiara@artel.com 5891 13. Full Copyright Statement 5893 Copyright (C) The Internet Society (2003). All Rights Reserved. 5895 This document and translations of it may be copied and furnished to 5896 others, and derivative works that comment on or otherwise explain it 5897 or assist in its implementation may be prepared, copied, published 5898 and distributed, in whole or in part, without restriction of any 5899 kind, provided that the above copyright notice and this paragraph are 5900 included on all such copies and derivative works. However, this 5901 document itself may not be modified in any way, such as by removing 5902 the copyright notice or references to the Internet Society or other 5903 Internet organizations, except as needed for the purpose of 5904 developing Internet standards in which case the procedures for 5905 copyrights defined in the Internet Standards process must be 5906 followed, or as required to translate it into languages other than 5907 English. 5909 The limited permissions granted above are perpetual and will not be 5910 revoked by the Internet Society or its successors or assigns. 5912 This document and the information contained herein is provided on an 5913 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 5914 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 5915 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 5916 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 5917 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.