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