idnits 2.17.1 draft-ietf-mpls-tp-te-mib-09.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 22, 2014) is 3501 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) -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group 3 INTERNET-DRAFT M.Venkatesan 4 Intended Status: Standards Track Dell Inc. 5 Expires: March 26, 2015 Kannan KV Sampath 6 Redeem 7 Sam K. Aldrin 8 Huawei Technologies 9 Thomas D. Nadeau 10 Brocade 12 September 22, 2014 14 MPLS-TP Traffic Engineering (TE) Management Information Base (MIB) 15 draft-ietf-mpls-tp-te-mib-09.txt 17 Abstract 19 This memo defines a portion of the Management Information Base (MIB) 20 for use with network management protocols in the Internet community. 21 In particular, it describes additional managed objects of Tunnels, 22 Identifiers, Label Switching Router and Textual conventions to 23 support Multiprotocol Label Switching (MPLS) MIB modules for 24 transport networks. 26 Status of this Memo 28 This Internet-Draft is submitted to IETF in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF), its areas, and its working groups. Note that 33 other groups may also distribute working documents as Internet- 34 Drafts. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 The list of current Internet-Drafts can be accessed at 42 http://www.ietf.org/ietf/1id-abstracts.txt. 44 The list of Internet-Draft Shadow Directories can be accessed at 45 http://www.ietf.org/shadow.html. 47 This Internet-Draft will expire on March 26, 2015. 49 Copyright and License Notice 51 Copyright (c) 2014 IETF Trust and the persons identified as the 52 document authors. All rights reserved. 54 This document is subject to BCP 78 and the IETF Trust's Legal 55 Provisions Relating to IETF Documents 56 (http://trustee.ietf.org/license-info) in effect on the date of 57 publication of this document. Please review these documents 58 carefully, as they describe your rights and restrictions with respect 59 to this document. Code Components extracted from this document must 60 include Simplified BSD License text as described in Section 4.e of 61 the Trust Legal Provisions and are provided without warranty as 62 described in the Simplified BSD License. 63 Table of Contents 65 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 66 2. The Internet-Standard Management Framework . . . . . . . . . . 4 67 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 68 3.1. Conventions used in this document . . . . . . . . . . . . . 4 69 3.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4 70 3.3. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . 6 71 4. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . . 6 72 5. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 6 73 6. Brief description of MIB modules . . . . . . . . . . . . . . . 7 74 6.1. mplsTunnelExtNodeConfigTable . . . . . . . . . . . . . . . 7 75 6.2. mplsTunnelExtNodeIpMapTable . . . . . . . . . . . . . . . . 8 76 6.3. mplsTunnelExtNodeIccMapTable . . . . . . . . . . . . . . . 8 77 6.4. mplsTunnelExtTable . . . . . . . . . . . . . . . . . . . . 9 78 6.5 MPLS-TC-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 9 79 6.6 MPLS-ID-STD-MIB . . . . . . . . . . . . . . . . . . . . . . 9 80 6.7 MPLS-LSR-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 9 81 7. MIB Module Interdependencies . . . . . . . . . . . . . . . . . 9 82 8. Dependencies between MIB Module Tables . . . . . . . . . . . . 11 83 9. Example of MPLS-TP Tunnel Setup . . . . . . . . . . . . . . . . 12 84 9.1. Example of MPLS-TP static co-routed bidirectional tunnel 85 setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 86 9.1.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 14 87 9.1.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 14 88 9.1.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 15 89 9.1.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 15 90 9.1.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 16 91 9.1.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 16 92 9.1.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 16 93 9.1.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 16 94 9.2. Example of MPLS-TP static associated bidirectional tunnel 95 setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 96 9.2.1. Forward direction mplsTunnelEntry . . . . . . . . . . . 17 97 9.2.2. Forward direction mplsTunnelExtEntry . . . . . . . . . 18 98 9.2.3. Forward direction mplsOutSegmentTable . . . . . . . . . 18 99 9.2.4. Forward direction mplsXCEntry . . . . . . . . . . . . . 18 100 9.2.5. Forward direction mplsXCExtEntry . . . . . . . . . . . 19 101 9.2.6. Reverse direction mplsTunnelEntry . . . . . . . . . . . 19 102 9.2.7. Reverse direction mplsTunnelExtEntry . . . . . . . . . 20 103 9.2.8. Reverse direction mplsInSegmentEntry . . . . . . . . . 20 104 9.2.9. Reverse direction mplsXCEntry . . . . . . . . . . . . . 20 105 9.2.10. Reverse direction mplsXCExtEntry . . . . . . . . . . . 21 106 9.3. Example of MPLS-TP signaled co-routed bidirectional 107 tunnel setup . . . . . . . . . . . . . . . . . . . . . . . 21 108 9.3.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 21 109 9.3.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 22 110 9.3.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 23 111 9.3.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 23 112 9.3.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 23 113 9.3.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 23 114 9.3.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 23 115 9.3.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 23 116 10. MPLS Textual Convention Extension MIB definitions . . . . . . 23 117 11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 26 118 12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 31 119 13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 36 120 14. Security Consideration . . . . . . . . . . . . . . . . . . . . 54 121 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55 122 15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB . . . . . . . 55 123 15.2. IANA Considerations for MPLS-ID-STD-MIB . . . . . . . . . 55 124 15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB . . . . . . . 55 125 15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB . . . . . . . 56 126 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 56 127 16.1. Normative References . . . . . . . . . . . . . . . . . . . 56 128 16.2. Informative References . . . . . . . . . . . . . . . . . 56 129 17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 57 130 18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 57 132 1. Introduction 134 This memo defines a portion of the Management Information Base (MIB) for 135 use with network management protocols in the Internet community. In 136 particular, it describes additional managed objects of Tunnels, 137 Identifiers, Label Switching Router and Textual conventions to support 138 Multiprotocol Label Switching (MPLS) MIB modules for transport networks. 139 MIB modules defined in this document extends the existing MPLS MIB 140 objects in such a way that they support MPLS-TP and Non-MPLS-TP networks 141 as well. Hence, the MPLS-TP name is not included in the MIB module name. 143 The existing MPLS Traffic Engineering (TE) Management Information Base 144 (MIB) [RFC3812] and Generalized Multiprotocol Label Switching (GMPLS) 145 Traffic Engineering Management Information Base [RFC4802] do not support 146 the management of transport network requirements of Tunnel end points 147 with non-IP based identifiers and static bidirectional tunnels. This 148 document focuses on static bidirectional MIB modules that should be used 149 in conjunction with [RFC3812] and companion document [RFC3813] for MPLS 150 Transport Profile (MPLS-TP) path configuration and management. 152 It is understood that SNMP SET is not used for MPLS configuration these 153 days, however the read-write and read-create option is still specified 154 for some objects as a way to provide the information model. 156 2. The Internet-Standard Management Framework 158 For a detailed overview of the documents that describe the current 159 Internet-Standard Management Framework, please refer to section 7 of RFC 160 3410 [RFC3410]. 162 Managed objects are accessed via a virtual information store, termed the 163 Management Information Base or MIB. MIB objects are generally accessed 164 through the Simple Network Management Protocol (SNMP). Objects in the 165 MIB are defined using the mechanisms defined in the Structure of 166 Management Information (SMI). This memo specifies a MIB module that is 167 compliant to the SMIv2, which is described in STD 58 [RFC2578], STD 58 168 [RFC2579] and STD 58 [RFC2580]. 170 3. Overview 172 3.1. Conventions used in this document 174 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 175 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 176 document are to be interpreted as described in [RFC2119]. 178 3.2. Terminology 179 This document uses terminology from the Multiprotocol Label Switching 180 Architecture [RFC3031], Multiprotocol Label Switching (MPLS) Traffic 181 Engineering (TE) Management Information Base (MIB) [RFC3812], 182 Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) 183 Management Information Base (MIB) [RFC3813] and MPLS Transport Profile 184 (MPLS-TP) Identifiers [RFC6370]. 186 3.3. Acronyms 188 CC: Country Code 189 ICC: ITU Carrier Code 190 LSP: Label Switching Path 191 LSR: Label Switching Router 192 MPLS-TP: MPLS Transport Profile 193 TE: Traffic Engineering 194 TP: Transport Profile 196 4. Motivations 198 Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management 199 Information Base (MIB) [RFC3812] provides support for Traffic 200 Engineering tunnels. However, with MPLS-TP, the characteristics of 201 Tunnels were enhanced. In MPLS, the actual transport of packets is 202 provided by Label Switched Paths (LSPs). A transport service may be 203 composed of multiple LSPs. In order to clearly identify the service, as 204 defined in [RFC6370], we use the term "MPLS-TP Tunnel" or simply 205 "tunnel" For example, MPLS-TP tunnels, are bidirectional in nature and 206 could be used with non-IP identifiers for the tunnel end points. As the 207 existing MPLS-TE-STD-MIB and GMPLS-TE-STD-MIB were defined mainly to 208 support unidirectional tunnel and signaled co-routed bidirectional 209 tunnel definitions respectively, these existing MIBs are not sufficient 210 to capture all the characteristics of the tunnels. Hence, enhancing the 211 MIB modules to support MPLS TP tunnels is required. As most of the 212 attributes of MPLS Traffic Engineering tunnels are also applicable to 213 MPLS-TP tunnels, it is optimal to re-use the existing MIB definition 214 instead of a defining a new MIB. 216 This document defines four MIB modules, namely MPLS-TE-EXT-STD-MIB, 217 MPLS-TC-EXT-STD-MIB, MPLS-ID-STD-MIB and MPLS-LSR-EXT-STD-MIB. As these 218 new MIB modules are required for MPLS-TP functionality, these are 219 retained in the same document, instead of a separate document. 221 5. Feature List 223 This document identifies the following requirements and constraints: 225 The MIB module supports static and signaled point-to-point, co-routed 226 bi-directional and associated bi-directional tunnels. 228 - The MPLS tunnels need not be interfaces, but it is possible 229 to configure an MPLS TP tunnel as an interface. 231 - The mplsTunnelTable [RFC3812] to be also used for MPLS-TP 232 tunnels 234 - New MPLS-TP specific textual conventions and identifiers 236 - The mplsTunnelTable is sparsely extended to support MPLS-TP 237 tunnel specific objects. 239 - A node configuration table (mplsTunnelExtNodeConfigTable) 240 is used to translate the Global_ID::Node_ID or 241 ICC_Operator_ID::Node_ID to the local identifier in order 242 to index mplsTunnelTable. 244 - The mplsXCTable is sparsely extended to support MPLS-TP 245 XC(Cross Connect) specific objects. 247 - The MIB module supports persistent, as well as non-persistent 248 tunnels. 250 6. Brief description of MIB modules 252 This section describes the MIB modules present in this document. The 253 tables and MIB modules that are mentioned in the below subsections 254 support the functionality described in documents [RFC5654] and 255 [RFC6370]. The tables support both IP compatible and ICC based 256 tunnel configurations. 258 The below diagram depicts how the table references are followed in 259 this MIB. 261 Tunnel1-->XC1<-------------- 262 ^ ^ | | | 263 | | | |-->InSeg1 | 264 | | | |-->OutSeg1 | 265 | | v | 266 | ------XCext1 | 267 | | | 268 V v | 269 Tunnel2-->XC1 | 270 ^ | | | 271 | | |-->InSeg2 | 272 | | |-->OutSeg2 | 273 | v | 274 ------XCext2------------ 276 6.1. mplsTunnelExtNodeConfigTable 278 The mplsTunnelExtNodeConfigTable is used to assign a local identifier 279 for a given ICC_Operator_ID::Node_ID or Global_ID::Node_ID 280 combination as defined in [RFC6923] and [RFC6370] respectively. The 281 CC is a string of two alphabetic characters represented with upper 282 case letters (i.e., A-Z). The ICC is a string of one to six 283 characters, each character being either alphabetic (i.e. A-Z) or 284 numeric (i.e. 0-9) characters. Alphabetic characters in the ICC 285 should be represented with upper case letters. In the IP compatible 286 mode, Global_ID::Node_ID, is used to uniquely identify a node. For 287 each ICC_Operator_ID::Node_ID or Global_ID::Node_ID, there is a 288 unique entry in the table representing a node. As the regular TE 289 tunnels use IP address as LSR ID, the local identifier should be 290 below the first valid IP address, which is 16777216[1.0.0.0]. Every 291 node is assigned a local identifier within a range of 0 to 16777215. 292 This local identifier is used for indexing into mplsTunnelTable as 293 mplsTunnelIngressLSRId and mplsTunnelEgressLSRId. 295 For IP compatible environment, MPLS-TP tunnel is indexed by Tunnel 296 Index, Tunnel Instance, Source Global_ID, Source Node_ID, Destination 297 Global_ID and Destination Node_ID. 299 For ICC based environment, MPLS-TP tunnel is indexed by Tunnel Index, 300 Tunnel Instance, Source CC, Source ICC, Source Node_ID, Destination 301 CC, Destination ICC and Destination Node_ID. 303 As mplsTunnelTable is indexed by mplsTunnelIndex, 304 mplsTunnelInstance, mplsTunnelIngressLSRId, and 305 mplsTunnelEgressLSRId, the MPLS-TP tunnel identifiers cannot be 306 used directly. 308 The mplsTunnelExtNodeConfigTable will be used to store an entry for 309 ICC_Operator_ID::Node_ID or Global_ID::Node_ID with a local 310 identifier to be used as LSR ID in mplsTunnelTable. 312 6.2. mplsTunnelExtNodeIpMapTable 314 The read-only mplsTunnelExtNodeIpMapTable is used to query the local 315 identifier assigned and stored in mplsTunnelExtNodeConfigTable for 316 a given Global_ID::Node_ID. In order to query the local identifier, 317 in the IP compatible mode, this table is indexed with 318 Global_ID::Node_ID. In the IP compatible mode for a TP tunnel, 319 Global_ID::Node_ID is used. 321 A separate query is made to get the local identifier of both 322 Ingress and Egress Global_ID::Node_ID identifiers. These local 323 identifiers are used as mplsTunnelIngressLSRId and 324 mplsTunnelEgressLSRId, while indexing mplsTunnelTable. 326 6.3. mplsTunnelExtNodeIccMapTable 327 The read-only mplsTunnelExtNodeIccMapTable is used to query the local 328 identifier assigned and stored in the mplsTunnelExtNodeConfigTable 329 for a given ICC_Operator_ID::Node_ID. 331 A separate query is made to get the local identifier of both 332 Ingress and Egress ICC_Operator_ID::Node_ID. These local identifiers 333 are used as mplsTunnelIngressLSRId and mplsTunnelEgressLSRId, 334 while indexing mplsTunnelTable. 336 6.4. mplsTunnelExtTable 338 This table sparsely extends the mplsTunnelTable in order to support 339 MPLS-TP tunnels with additional objects. All the additional 340 attributes specific to supporting TP tunnel are contained in this 341 extended table and could be accessed with the mplsTunnelTable 342 indices. 344 The gmplsTunnelReversePerfTable [RFC4802] should be used to provide 345 per-tunnel packet performance information for the reverse direction 346 of a bidirectional tunnel. It can be seen as supplementing the 347 mplsTunnelPerfTable, which augments the mplsTunnelTable. 349 6.5 MPLS-TC-EXT-STD-MIB 351 This MIB module contains Textual Conventions for LSPs of MPLS based 352 transport networks. 354 6.6 MPLS-ID-STD-MIB 356 This MIB module contains generic object definitions for MPLS Traffic 357 Engineering in transport networks. 359 6.7 MPLS-LSR-EXT-STD-MIB 361 This MIB module contains generic object definitions for MPLS LSR in 362 transport networks. 364 7. MIB Module Interdependencies 366 This section provides an overview of the relationship between the 367 MPLS-TP TE MIB module and other MPLS MIB modules. 369 The arrows in the following diagram show a 'depends on' 370 relationship. A relationship "MIB module A depends on MIB module B" 371 means that MIB module A uses an object, object identifier, or 372 textual convention defined in MIB module B, or that MIB module A 373 contains a pointer (index or RowPointer) to an object in 374 MIB module B. 376 MPLS-TC-EXT-STD-MIB 377 ^ 378 | 379 | 380 +<---- MPLS-ID-STD-MIB 381 ^ 382 | | 383 +<---- MPLS-TE-EXT-STD-MIB 384 | | 385 | V 386 | MPLS-TE-STD-MIB 387 | | 388 | | 389 | V 390 | MPLS-LSR-STD-MIB 391 | ^ 392 | | 393 | | 394 +------MPLS-LSR-EXT-STD-MIB 396 Thus: 398 - All the new MPLS extension MIB modules depend on 399 MPLS-TC-EXT-STD-MIB. 401 - MPLS-ID-STD-MIB contains references to objects in 402 MPLS-TE-STD-MIB [RFC3812]. 404 - MPLS-TE-EXT-STD-MIB contains references to objects in 405 MPLS-TE-STD-MIB [RFC3812]. 407 - MPLS-LSR-EXT-STD-MIB contains references to objects in 408 MPLS-LSR-STD-MIB [RFC3813]. 410 The mplsTunnelExtTable sparsely extends the mplsTunnelTable of 411 MPLS-TE-STD-MIB [RFC3812]. This helps in associating the reverse 412 direction tunnel information. 414 The mplsXCExtTable sparsely extends the mplsXCTable of 415 MPLS-LSR-STD-MIB [RFC3813]. This helps in pointing back to the tunnel 416 entry for easy tunnel access from XC entry. 418 Note that all of the MIB modules shown above in the figure also 419 have a dependency on MPLS-TC-STD-MIB. 421 8. Dependencies between MIB Module Tables 423 The tables in MPLS-TE-EXT-STD-MIB are related as shown on the diagram 424 below. The arrows indicate a reference from one table to another. 426 mplsTunnelExtNodeConfigTable 427 ^ ^ ^ 428 | | | 429 | | | 430 | | | 431 | | +----------------------+ 432 | | | 433 | mplsTunnelExtNodeIpMapTable mplsTunnelExtNodeIccMapTable 434 | 435 | mplsXCExtTable 436 | | ^ 437 | +---------+ | 438 | | | 439 | | | 440 | V V 441 mplsTunnelTable ---->mplsXCTable 442 ^ 443 | 444 | 445 | 446 mplsTunnelExtTable 448 An existing mplsTunnelTable uses the mplsTunnelExtNodeConfigTable 449 table to map the Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID 450 with the local number in order to accommodate in the existing tunnel 451 table's ingress/egress LSR-id. 453 New mplsTunnelExtTable table provides the reverse direction LSP 454 information for the existing tunnel table in order to achieve 455 bidirectional LSPs. 457 mplsXCExtTable sparsely extends the mplsLsrXCTable to provide 458 backward reference to tunnel entry. 460 9. Example of MPLS-TP Tunnel Setup 462 In this section, we provide an example to configure MPLS-TP 463 bidirectional tunnels with IP tunnel identifiers. This example 464 provides the usage of MPLS-TP Tunnel MIB along with the extended new 465 MIB modules introduced in this document. 467 Do note that a MPLS-TP tunnel could be setup statically as well as 468 signaled via control plane. This example considers accessing MIB 469 objects on a head-end for a static and signaled MPLS-TP tunnels. This 470 section shows the configuration of the forward and reverse direction 471 MPLS-TP LSPs that runs between East and West and vice-versa. Only 472 relevant objects which are applicable for MPLS-TP tunnel are 473 illustrated here. 475 In mplsTunnelExtNodeConfigTable: 477 { 478 -- Non-IP Ingress LSR-Id (Index to the table) 480 mplsTunnelExtNodeConfigLocalId = 1, 482 mplsTunnelExtNodeConfigGlobalId = 1234, 483 mplsTunnelExtNodeConfigNodeId = 10, 484 -- Mandatory parameters needed to activate the row go here 485 mplsTunnelExtNodeConfigRowStatus = createAndGo (4) 487 -- Non-IP Egress LSR-Id (Index to the table) 488 mplsTunnelExtNodeConfigLocalId = 2, 489 mplsTunnelExtNodeConfigGlobalId = 1234, 490 mplsTunnelExtNodeConfigNodeId = 20, 491 -- Mandatory parameters needed to activate the row go here 492 mplsTunnelExtNodeConfigRowStatus = createAndGo (4) 493 } 495 This will create an entry in the mplsTunnelExtNodeConfigTable for a 496 Global_ID::Node_ID. A separate entry is made for both Ingress LSR 497 and Egress LSR. 499 The following read-only mplsTunnelExtNodeIpMapTable table is 500 populated automatically upon creating an entry in 501 mplsTunnelExtNodeConfigTable and this table is used to retrieve 502 the local identifier for the given Global_ID::Node_ID. 504 In mplsTunnelExtNodeIpMapTable: 506 { 507 -- Global_ID (Index to the table) 508 mplsTunnelExtNodeIpMapGlobalId = 1234, 509 -- Node Identifier (Index to the table) 510 mplsTunnelExtNodeIpMapNodeId = 10, 511 mplsTunnelExtNodeIpMapLocalId = 1 513 -- Global_ID (Index to the table) 514 mplsTunnelExtNodeIpMapGlobalId = 1234, 515 -- Node Identifier (Index to the table) 516 mplsTunnelExtNodeIpMapNodeId = 20, 517 mplsTunnelExtNodeIpMapLocalId = 2 518 } 520 9.1. Example of MPLS-TP static co-routed bidirectional tunnel setup 522 The following denotes the co-routed bidirectional tunnel "head" 523 entry. 525 9.1.1. mplsTunnelEntry 527 In mplsTunnelTable: 529 { 530 mplsTunnelIndex = 1, 531 mplsTunnelInstance = 1, 532 -- Local map number created in mplsTunnelExtNodeConfigTable for 533 -- Ingress LSR-Id 534 mplsTunnelIngressLSRId = 1, 536 -- Local map number created in mplsTunnelExtNodeConfigTable for 537 -- Egress LSR-Id 538 mplsTunnelEgressLSRId = 2, 539 mplsTunnelName = "TP co-routed bidirectional LSP", 540 mplsTunnelDescr = "East to West", 541 mplsTunnelIsIf = true (1), 542 -- RowPointer MUST point to the first accessible column 543 mplsTunnelXCPointer = 544 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1, 545 mplsTunnelSignallingProto = none (1), 546 mplsTunnelSetupPrio = 0, 547 mplsTunnelHoldingPrio = 0, 548 mplsTunnelSessionAttributes = 0, 549 mplsTunnelLocalProtectInUse = false (0), 550 -- RowPointer MUST point to the first accessible column 551 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 552 mplsTunnelInstancePriority = 1, 553 mplsTunnelHopTableIndex = 1, 554 mplsTunnelIncludeAnyAffinity = 0, 555 mplsTunnelIncludeAllAffinity = 0, 556 mplsTunnelExcludeAnyAffinity = 0, 557 mplsTunnelRole = head (1), 558 -- Mandatory parameters needed to activate the row go here 559 mplsTunnelRowStatus = createAndGo (4) 560 } 562 9.1.2. mplsTunnelExtEntry 564 -- An MPLS extension table 565 In mplsTunnelExtTable: 566 { 567 -- This opposite direction tunnel pointer may point to 0.0 568 -- if co-routed bidirectional tunnel is managed by single tunnel 569 -- entry 570 mplsTunnelExtOppositeDirTnlPtr = 0.0 571 -- Set both the Ingress and Egress LocalId objects to TRUE as 572 -- this tunnel entry uses the local identifiers. 573 mplsTunnelExtIngressLSRLocalIdValid = true, 574 mplsTunnelExtEgressLSRLocalIdValid = true 576 } 578 We must next create the appropriate in-segment and out-segment 579 entries. These are done in [RFC3813] using the mplsInSegmentTable and 580 mplsOutSegmentTable. 582 9.1.3. Forward direction mplsOutSegmentEntry 584 For the forward direction, 586 In mplsOutSegmentTable: 587 { 588 mplsOutSegmentIndex = 0x0000001, 589 mplsOutSegmentInterface = 13, -- outgoing interface 590 mplsOutSegmentPushTopLabel = true(1), 591 mplsOutSegmentTopLabel = 22, -- outgoing label 593 -- RowPointer MUST point to the first accessible column. 594 mplsOutSegmentTrafficParamPtr = 0.0, 595 mplsOutSegmentRowStatus = createAndGo (4) 596 } 598 9.1.4. Reverse direction mplsInSegmentEntry 600 For the reverse direction, 602 In mplsInSegmentTable: 603 { 604 mplsInSegmentIndex = 0x0000001 605 mplsInSegmentLabel = 21, -- incoming label 606 mplsInSegmentNPop = 1, 607 mplsInSegmentInterface = 13, -- incoming interface 609 -- RowPointer MUST point to the first accessible column. 610 mplsInSegmentTrafficParamPtr = 0.0, 611 mplsInSegmentRowStatus = createAndGo (4) 612 } 614 Next, two cross-connect entries are created in the mplsXCTable of the 615 MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created 616 segments together. 618 9.1.5. Forward direction mplsXCEntry 620 In mplsXCTable: 621 { 622 mplsXCIndex = 0x01, 623 mplsXCInSegmentIndex = 0x00000000, 624 mplsXCOutSegmentIndex = 0x00000001, 625 mplsXCLspId = 0x0102 -- unique ID 627 -- only a single outgoing label 628 mplsXCLabelStackIndex = 0x00, 629 mplsXCRowStatus = createAndGo(4) 631 } 633 9.1.6. Reverse direction mplsXCEntry 635 In mplsXCTable: 636 { 637 mplsXCIndex = 0x01, 638 mplsXCInSegmentIndex = 0x00000001, 639 mplsXCOutSegmentIndex = 0x00000000, 640 mplsXCLspId = 0x0102 -- unique ID 641 -- only a single outgoing label 642 mplsXCLabelStackIndex = 0x00, 643 mplsXCRowStatus = createAndGo(4) 644 } 646 This table entry is extended by entry in the 647 mplsXCExtTable. Note that the nature of the 'extends' 648 relationship is a sparse augmentation so that the entry in the 649 mplsXCExtTable has the same index values as the entry in 650 the mplsXCTable. 652 9.1.7. Forward direction mplsXCExtEntry 654 In mplsXCExtTable (0x01, 0x00000000, 0x00000001) 655 { 656 -- Back pointer from XC table to Tunnel table 657 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 658 mplsXCExtOppositeDirXCPtr = 659 mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0 660 } 662 9.1.8. Reverse direction mplsXCExtEntry 663 Next for the reverse direction: 665 In mplsXCExtTable (0x01, 0x00000001, 0x00000000) 666 { 667 -- Back pointer from XC table to Tunnel table 668 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 669 mplsXCExtOppositeDirXCPtr = 670 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1 671 } 673 9.2. Example of MPLS-TP static associated bidirectional tunnel setup 675 The MPLS-TP associated bidirectional tunnel has two different 676 direction tunnels[Forward and Reverse LSPs] and these are 677 associated together using mplsTunnelExtTable. Two different 678 tunnel entries for both forward and reverse direction MAY be used 679 for co-routed bidirectional tunnel as well. 681 The following denotes the associated bidirectional forward tunnel 682 "head" entry: 684 9.2.1. Forward direction mplsTunnelEntry 686 In mplsTunnelTable: 688 { 689 mplsTunnelIndex = 1, 690 mplsTunnelInstance = 1, 691 -- Local map number created in mplsTunnelExtNodeConfigTable for 692 -- Ingress LSR-Id 693 mplsTunnelIngressLSRId = 1, 695 -- Local map number created in mplsTunnelExtNodeConfigTable for 696 -- Egress LSR-Id 697 mplsTunnelEgressLSRId = 2, 698 mplsTunnelName = "TP associated bi-directional 699 forward LSP", 700 mplsTunnelDescr = "East to West", 701 mplsTunnelIsIf = true (1), 702 -- RowPointer MUST point to the first accessible column 703 mplsTunnelXCPointer = 704 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1, 705 mplsTunnelSignallingProto = none (1), 706 mplsTunnelSetupPrio = 0, 707 mplsTunnelHoldingPrio = 0, 708 mplsTunnelSessionAttributes = 0, 709 mplsTunnelLocalProtectInUse = false (0), 710 -- RowPointer MUST point to the first accessible column 711 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 712 mplsTunnelInstancePriority = 1, 713 mplsTunnelHopTableIndex = 1, 714 mplsTunnelIncludeAnyAffinity = 0, 716 mplsTunnelIncludeAllAffinity = 0, 717 mplsTunnelExcludeAnyAffinity = 0, 718 mplsTunnelRole = head (1), 719 -- Mandatory parameters needed to activate the row go here 720 mplsTunnelRowStatus = createAndGo (4) 721 } 723 9.2.2. Forward direction mplsTunnelExtEntry 725 For Associated bidirectional forward LSP, 726 In mplsTunnelExtTable: 727 { 728 mplsTunnelExtOppositeDirPtr = mplsTunnelName.2.1.2.1 729 -- Set both the Ingress and Egress LocalId objects to TRUE as 730 -- this tunnel entry uses the local identifiers. 731 mplsTunnelExtIngressLSRLocalIdValid = true, 732 mplsTunnelExtEgressLSRLocalIdValid = true 733 } 735 9.2.3. Forward direction mplsOutSegmentTable 737 For the forward direction. 739 In mplsOutSegmentTable: 740 { 741 mplsOutSegmentIndex = 0x0000001, 742 mplsOutSegmentInterface = 13, -- outgoing interface 743 mplsOutSegmentPushTopLabel = true(1), 744 mplsOutSegmentTopLabel = 22, -- outgoing label 746 -- RowPointer MUST point to the first accessible column. 747 mplsOutSegmentTrafficParamPtr = 0.0, 748 mplsOutSegmentRowStatus = createAndGo (4) 749 } 751 9.2.4. Forward direction mplsXCEntry 753 In mplsXCTable: 754 { 755 mplsXCIndex = 0x01, 756 mplsXCInSegmentIndex = 0x00000000, 757 mplsXCOutSegmentIndex = 0x00000001, 758 mplsXCLspId = 0x0102 -- unique ID 759 -- only a single outgoing label 760 mplsXCLabelStackIndex = 0x00, 761 mplsXCRowStatus = createAndGo(4) 763 } 765 9.2.5. Forward direction mplsXCExtEntry 767 In mplsXCExtTable (0x01, 0x00000000, 0x00000001) 768 { 769 -- Back pointer from XC table to Tunnel table 770 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 771 mplsXCExtOppositeDirXCPtr = 772 mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0 773 } 775 9.2.6. Reverse direction mplsTunnelEntry 777 The following denotes the configured associated bidirectional reverse 778 tunnel "tail" entry: 780 In mplsTunnelTable: 782 { 783 mplsTunnelIndex = 2, 784 mplsTunnelInstance = 1, 785 -- Local map number created in mplsTunnelExtNodeConfigTable for 786 -- Ingress LSR-Id 787 mplsTunnelIngressLSRId = 2, 788 -- Local map number created in mplsTunnelExtNodeConfigTable for 789 -- Egress LSR-Id 790 mplsTunnelEgressLSRId = 1, 791 mplsTunnelName = "TP associated bi-directional 792 reverse LSP", 793 mplsTunnelDescr = "West to East", 794 mplsTunnelIsIf = true (1), 795 -- RowPointer MUST point to the first accessible column 796 mplsTunnelXCPointer = 797 mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0, 798 mplsTunnelSignallingProto = none (1), 799 mplsTunnelSetupPrio = 0, 800 mplsTunnelHoldingPrio = 0, 801 mplsTunnelSessionAttributes = 0, 802 mplsTunnelLocalProtectInUse = false (0), 804 -- RowPointer MUST point to the first accessible column 805 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 806 mplsTunnelInstancePriority = 1, 807 mplsTunnelHopTableIndex = 1, 808 mplsTunnelIncludeAnyAffinity = 0, 809 mplsTunnelIncludeAllAffinity = 0, 810 mplsTunnelExcludeAnyAffinity = 0, 811 mplsTunnelRole = head (1), 812 -- Mandatory parameters needed to activate the row go here 814 mplsTunnelRowStatus = createAndGo (4) 815 } 817 9.2.7. Reverse direction mplsTunnelExtEntry 819 For Associated bidirectional reverse LSP, 820 In mplsTunnelExtTable: 821 { 822 mplsTunnelExtOppositeDirPtr = mplsTunnelName.1.1.1.2 823 -- Set both the Ingress and Egress LocalId objects to TRUE as 824 -- this tunnel entry uses the local identifiers. 825 mplsTunnelExtIngressLSRLocalIdValid = true, 826 mplsTunnelExtEgressLSRLocalIdValid = true 827 } 829 9.2.8. Reverse direction mplsInSegmentEntry 831 We must next create the appropriate in-segment and out-segment 832 entries. These are done in [RFC3813] using the mplsInSegmentTable and 833 mplsOutSegmentTable. 835 In mplsInSegmentTable: 836 { 837 mplsInSegmentIndex = 0x0000001 838 mplsInSegmentLabel = 21, -- incoming label 839 mplsInSegmentNPop = 1, 840 mplsInSegmentInterface = 13, -- incoming interface 842 -- RowPointer MUST point to the first accessible column. 843 mplsInSegmentTrafficParamPtr = 0.0, 844 mplsInSegmentRowStatus = createAndGo (4) 845 } 847 Next, two cross-connect entries are created in the mplsXCTable of the 848 MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created 849 segments together. 851 9.2.9. Reverse direction mplsXCEntry 853 In mplsXCTable: 855 { 856 mplsXCIndex = 0x01, 857 mplsXCInSegmentIndex = 0x00000001, 858 mplsXCOutSegmentIndex = 0x00000000, 859 mplsXCLspId = 0x0102 -- unique ID 860 -- only a single outgoing label 861 mplsXCLabelStackIndex = 0x00, 863 mplsXCRowStatus = createAndGo(4) 864 } 866 This table entry is extended by entry in the 867 mplsXCExtTable. Note that the nature of the 'extends' 868 relationship is a sparse augmentation so that the entry in the 869 mplsXCExtTable has the same index values as the entry in 870 the mplsXCTable. 872 9.2.10. Reverse direction mplsXCExtEntry 874 Next for the reverse direction: 876 In mplsXCExtTable (0x01, 0x00000001, 0x00000000) 877 { 878 -- Back pointer from XC table to Tunnel table 879 mplsXCExtTunnelPointer = mplsTunnelName.2.1.2.1 880 mplsXCExtOppositeDirXCPtr = 881 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1 882 } 884 9.3. Example of MPLS-TP signaled co-routed bidirectional tunnel setup 886 The following denotes the co-routed bidirectional tunnel "head" entry 887 and in intermediate and tail-end nodes, the tunnel table and its 888 associated tables are created by the local management subsystem 889 (e.g. agent) when the MPLS TP tunnel is signaled successfully. 890 Refer [RFC3812] and [RFC4802] for signaled tunnel table 891 configuration examples. 893 9.3.1. mplsTunnelEntry 895 In mplsTunnelTable: 897 { 898 mplsTunnelIndex = 1, 899 mplsTunnelInstance = 0, 900 -- Local map number created in mplsTunnelExtNodeConfigTable for 901 -- Ingress LSR-Id, for the intermediate and tail-end nodes, 902 -- the local management entity is expected to pick a first available 903 -- local identifier which is not used in mplsTunnelTable. 904 mplsTunnelIngressLSRId = 1, 906 -- Local map number created in mplsTunnelExtNodeConfigTable for 907 -- Egress LSR-Id 908 mplsTunnelEgressLSRId = 2, 909 mplsTunnelName = "TP co-routed bidirectional LSP", 910 mplsTunnelDescr = "East to West", 911 mplsTunnelIsIf = true (1), 913 -- RowPointer MUST point to the first accessible column 914 mplsTunnelXCPointer = 915 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1, 916 mplsTunnelSignallingProto = none (1), 917 mplsTunnelSetupPrio = 0, 918 mplsTunnelHoldingPrio = 0, 919 mplsTunnelSessionAttributes = 0, 920 mplsTunnelLocalProtectInUse = false (0), 921 -- RowPointer MUST point to the first accessible column 922 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 923 mplsTunnelInstancePriority = 1, 924 mplsTunnelHopTableIndex = 1, 925 mplsTunnelIncludeAnyAffinity = 0, 926 mplsTunnelIncludeAllAffinity = 0, 927 mplsTunnelExcludeAnyAffinity = 0, 928 mplsTunnelRole = head (1), 929 -- Mandatory parameters needed to activate the row go here 930 mplsTunnelRowStatus = createAndGo (4) 931 } 933 9.3.2. mplsTunnelExtEntry 935 -- An MPLS extension table 936 In mplsTunnelExtTable: 937 { 938 -- This opposite direction tunnel pointer may point to 0.0 939 -- if co-routed bidirectional tunnel is managed by single tunnel 940 -- entry 941 mplsTunnelExtOppositeDirTnlPtr = 0.0 942 -- Set both the Ingress and Egress LocalId objects to TRUE as 943 -- this tunnel entry uses the local identifiers. 944 mplsTunnelExtIngressLSRLocalIdValid = true, 945 mplsTunnelExtEgressLSRLocalIdValid = true 946 } 948 We must next create the appropriate in-segment and out-segment 949 entries. These are done in [RFC3813] using the mplsInSegmentTable and 950 mplsOutSegmentTable. 952 9.3.3. Forward direction mplsOutSegmentEntry 954 The forward direction mplsOutSegmentTable will be populated 955 automatically based on the information received from the signaling 956 protocol. 958 9.3.4. Reverse direction mplsInSegmentEntry 960 The reverse direction mplsOutSegmentTable will be populated 961 automatically based on the information received from the signaling 962 protocol. 964 Next, two cross-connect entries are created in the mplsXCTable of the 965 MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created 966 segments together. 968 9.3.5. Forward direction mplsXCEntry 970 The forward direction mplsXCEntry will be populated as soon as the 971 forward path label information is available. 973 9.3.6. Reverse direction mplsXCEntry 975 The reverse direction mplsXCEntry will be populated as soon as the 976 reverse path label information is available. 978 This table entry is extended by entry in the mplsXCExtTable. Note 979 that the nature of the 'extends' relationship is a sparse 980 augmentation so that the entry in the mplsXCExtTable has the same 981 index values as the entry in the mplsXCTable. 983 9.3.7. Forward direction mplsXCExtEntry 985 Once the forward path information is negotiated using signaling 986 protocol, the forward direction mplsXCExtEntry will be created for 987 associating the opposite direction XC entry and tunnel table entry. 989 9.3.8. Reverse direction mplsXCExtEntry 991 Once the reverse path information is negotiated using signaling 992 protocol, the reverse direction mplsXCExtEntry will be created for 993 associating the opposite direction XC entry and tunnel table entry. 995 10. MPLS Textual Convention Extension MIB definitions 997 MPLS-TC-EXT-STD-MIB DEFINITIONS ::= BEGIN 999 IMPORTS 1000 MODULE-IDENTITY, Unsigned32 1001 FROM SNMPv2-SMI -- [RFC2578] 1003 TEXTUAL-CONVENTION 1004 FROM SNMPv2-TC -- [RFC2579] 1006 mplsStdMIB 1007 FROM MPLS-TC-STD-MIB -- [RFC3811] 1009 ; 1011 mplsTcExtStdMIB MODULE-IDENTITY 1013 LAST-UPDATED 1014 "201405050000Z" -- May 05, 2014 1015 ORGANIZATION 1016 "Multiprotocol Label Switching (MPLS) Working Group" 1017 CONTACT-INFO 1018 " 1019 Venkatesan Mahalingam 1020 Dell Inc, 1021 5450 Great America Parkway, 1022 Santa Clara, CA 95054, USA 1023 Email: venkat.mahalingams@gmail.com 1025 Kannan KV Sampath 1026 Redeem, 1027 India 1028 Email: kannankvs@gmail.com 1030 Sam Aldrin 1031 Huawei Technologies 1032 2330 Central Express Way, 1033 Santa Clara, CA 95051, USA 1034 Email: aldrin.ietf@gmail.com 1036 Thomas D. Nadeau 1037 Email: tnadeau@lucidvision.com 1038 " 1039 DESCRIPTION 1040 "Copyright (c) 2014 IETF Trust and the persons identified 1041 as the document authors. All rights reserved. 1043 This MIB module contains Textual Conventions for LSPs of MPLS 1044 based transport networks." 1046 -- Revision history. 1048 REVISION 1050 "201405050000Z" -- May 05, 2014 1051 DESCRIPTION 1052 "MPLS Textual Convention Extensions" 1054 ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value 1056 MplsGlobalId ::= TEXTUAL-CONVENTION 1057 STATUS current 1058 DESCRIPTION 1059 "This object contains the Textual Convention of IP based 1060 operator unique identifier (Global_ID), the Global_ID can 1061 contain the 2-octet or 4-octet value of the operator's 1062 Autonomous System Number (ASN). 1064 When the Global_ID is derived from a 2-octet AS number, 1065 the two high-order octets of this 4-octet identifier 1066 MUST be set to zero(0x00). Further ASN 0 is reserved. 1067 The size of the Global_ID string MUST be zero if 1068 the Global_ID is invalid. 1070 Note that a Global_ID of zero is limited to entities 1071 contained within a single operator and MUST NOT be used 1072 across an Network-to-Network Interface (NNI). A non-zero 1073 Global_ID MUST be derived from an ASN owned by 1074 the operator." 1075 REFERENCE 1076 "MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370] 1077 Section 3" 1078 SYNTAX OCTET STRING (SIZE (4)) 1080 MplsCcId ::= TEXTUAL-CONVENTION 1081 STATUS current 1082 DESCRIPTION 1083 "The CC (Country Code) is a string of two alphabetic 1084 characters represented with upper case 1085 letters (i.e., A-Z). The size of the CC string MUST be 1086 zero if the CC identifier is invalid." 1087 REFERENCE 1088 "MPLS-TP Identifiers Following ITU-T Conventions, 1089 [RFC6923] Section 3" 1090 SYNTAX OCTET STRING (SIZE (2)) 1092 MplsIccId ::= TEXTUAL-CONVENTION 1093 STATUS current 1094 DESCRIPTION 1095 "The ICC is a string of one to six characters, each 1096 character being either alphabetic (i.e. A-Z) or 1097 numeric (i.e. 0-9) characters. 1098 Alphabetic characters in the ICC SHOULD be represented 1099 with upper case letters. The size of the ICC string MUST 1100 be zero if the ICC identifier is invalid." 1101 REFERENCE 1102 "MPLS-TP Identifiers Following ITU-T Conventions, 1103 [RFC6923] Section 3" 1104 SYNTAX OCTET STRING (SIZE (0|1..6)) 1106 MplsNodeId ::= TEXTUAL-CONVENTION 1107 DISPLAY-HINT "d" 1108 STATUS current 1109 DESCRIPTION 1110 "The Node_ID is assigned within the scope of 1111 the Global_ID/ICC_Operator_ID. 1113 When IPv4 addresses are in use, the value of this object 1114 can be derived from the LSR's IPv4 loop back address. 1115 When IPv6 addresses are in use, the value of this object 1116 can be a 32-bit value unique within the scope of 1117 a Global_ID. 1119 Note that, when IP reach ability is not needed, the 32-bit 1120 Node_ID is not required to have any association 1121 with the IPv4 address space. The value of 0 indicates 1122 the invalid Node identifier." 1123 REFERENCE 1124 "MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370] 1125 Section 4" 1126 SYNTAX Unsigned32 (0|1..4294967295) 1128 -- MPLS-TC-EXT-STD-MIB module ends 1129 END 1131 11. MPLS Identifier MIB definitions 1133 MPLS-ID-STD-MIB DEFINITIONS ::= BEGIN 1135 IMPORTS 1136 MODULE-IDENTITY, OBJECT-TYPE 1137 FROM SNMPv2-SMI -- [RFC2578] 1138 MODULE-COMPLIANCE, OBJECT-GROUP 1139 FROM SNMPv2-CONF -- [RFC2580] 1140 mplsStdMIB 1141 FROM MPLS-TC-STD-MIB -- [RFC3811] 1142 MplsGlobalId, MplsCcId, MplsIccId, MplsNodeId 1143 FROM MPLS-TC-EXT-STD-MIB 1145 ; 1147 mplsIdStdMIB MODULE-IDENTITY 1148 LAST-UPDATED 1149 "201405050000Z" -- May 05, 2014 1150 ORGANIZATION 1151 "Multiprotocol Label Switching (MPLS) Working Group" 1153 CONTACT-INFO 1154 " 1155 Venkatesan Mahalingam 1156 Dell Inc, 1157 5450 Great America Parkway, 1158 Santa Clara, CA 95054, USA 1159 Email: venkat.mahalingams@gmail.com 1161 Kannan KV Sampath 1163 Redeem, 1164 India 1165 Email: kannankvs@gmail.com 1167 Sam Aldrin 1168 Huawei Technologies 1169 2330 Central Express Way, 1170 Santa Clara, CA 95051, USA 1171 Email: aldrin.ietf@gmail.com 1173 Thomas D. Nadeau 1174 Email: tnadeau@lucidvision.com 1175 " 1176 DESCRIPTION 1177 "Copyright (c) 2014 IETF Trust and the persons identified 1178 as the document authors. All rights reserved. 1180 This MIB module contains generic object definitions for 1181 MPLS Traffic Engineering in transport networks." 1183 -- Revision history. 1185 REVISION 1186 "201405050000Z" -- May 05, 2014 1187 DESCRIPTION 1188 "This MIB modules defines the MIB objects for MPLS-TP 1189 identifiers" 1191 ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value 1192 -- notifications 1193 mplsIdNotifications OBJECT IDENTIFIER ::= { mplsIdStdMIB 0 } 1194 -- tables, scalars 1195 mplsIdObjects OBJECT IDENTIFIER ::= { mplsIdStdMIB 1 } 1196 -- conformance 1197 mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 2 } 1199 -- MPLS common objects 1201 mplsIdGlobalId OBJECT-TYPE 1202 SYNTAX MplsGlobalId 1203 MAX-ACCESS read-write 1204 STATUS current 1205 DESCRIPTION 1206 "This object allows the operator or service provider to 1207 assign a unique operator identifier also called MPLS-TP 1208 Global_ID. 1209 If this value is used in mplsTunnelExtNodeConfigGlobalId 1210 for mapping Global_ID::Node_ID with the local identifier 1211 then this object value MUST NOT be changed." 1212 ::= { mplsIdObjects 1 } 1214 mplsIdNodeId OBJECT-TYPE 1215 SYNTAX MplsNodeId 1216 MAX-ACCESS read-write 1217 STATUS current 1218 DESCRIPTION 1219 "This object allows the operator or service provider to 1220 assign a unique MPLS-TP Node_ID. The Node_ID is assigned 1221 within the scope of the Global_ID/ICC_Operator_ID. 1222 If this value is used in mplsTunnelExtNodeConfigNodeId 1223 for mapping Global_ID::Node_ID with the local identifier 1224 then this object value SHOULD NOT be changed. 1225 If this value is used in mplsTunnelExtNodeConfigNodeId 1226 for mapping ICC_Operator_ID::Node_ID with the local 1227 identifier then this object value MUST NOT be changed." 1228 ::= { mplsIdObjects 2 } 1230 mplsIdCc OBJECT-TYPE 1231 SYNTAX MplsCcId 1232 MAX-ACCESS read-write 1233 STATUS current 1234 DESCRIPTION 1235 "This object allows the operator or service provider to 1236 assign a Country Code (CC) to the node. Global 1237 uniqueness of ICC is assured by concatenating the ICC 1238 with a Country Code (CC). 1240 If this value is used in mplsTunnelExtNodeConfigCcId 1241 for mapping ICC_Operator_ID::Node_ID with the local 1242 identifier then this object value MUST NOT be changed." 1243 REFERENCE 1244 "MPLS-TP Identifiers Following ITU-T Conventions, 1245 [RFC6923] Section 3" 1246 ::= { mplsIdObjects 3 } 1248 mplsIdIcc OBJECT-TYPE 1249 SYNTAX MplsIccId 1250 MAX-ACCESS read-write 1251 STATUS current 1252 DESCRIPTION 1253 "This object allows the operator or service provider to 1254 assign a unique MPLS-TP ITU-T Carrier Code (ICC) to 1255 the node. Together, the CC and the ICC form 1256 the ICC_Operator_ID as CC::ICC. 1257 If this value is used in mplsTunnelExtNodeConfigIccId 1258 for mapping ICC_Operator_ID::Node_ID with the local 1259 identifier then this object value MUST NOT be changed." 1260 REFERENCE 1261 "MPLS-TP Identifiers Following ITU-T Conventions, 1262 [RFC6923] Section 3" 1263 ::= { mplsIdObjects 4 } 1265 -- Module compliance. 1267 mplsIdCompliances 1268 OBJECT IDENTIFIER ::= { mplsIdConformance 1 } 1270 mplsIdGroups 1271 OBJECT IDENTIFIER ::= { mplsIdConformance 2 } 1273 -- Compliance requirement for fully compliant implementations. 1275 mplsIdModuleFullCompliance MODULE-COMPLIANCE 1276 STATUS current 1277 DESCRIPTION 1278 "Compliance statement for agents that provide full 1279 support of the MPLS-ID-STD-MIB module." 1281 MODULE -- this module 1283 -- The mandatory group has to be implemented by all LSRs that 1284 -- originate, terminate, or act as transit for MPLS-TP tunnels. 1286 GROUP mplsIdIpOperatorGroup 1287 DESCRIPTION 1288 "This group is mandatory for devices which support 1289 IP based identifier configuration." 1291 GROUP mplsIdIccOperatorGroup 1292 DESCRIPTION 1293 "This group is mandatory for devices which support 1294 ICC based identifier configuration." 1296 ::= { mplsIdCompliances 1 } 1298 -- Compliance requirement for read-only implementations. 1300 mplsIdModuleReadOnlyCompliance MODULE-COMPLIANCE 1301 STATUS current 1302 DESCRIPTION 1303 "Compliance statement for agents that only provide 1304 read-only support for the MPLS-ID-STD-MIB module." 1306 MODULE -- this module 1308 GROUP mplsIdIpOperatorGroup 1309 DESCRIPTION 1310 "This group is mandatory for devices which support 1311 IP based identifier configuration." 1313 GROUP mplsIdIccOperatorGroup 1314 DESCRIPTION 1315 "This group is mandatory for devices which support 1316 ICC based identifier configuration." 1318 OBJECT mplsIdGlobalId 1319 MIN-ACCESS read-only 1320 DESCRIPTION 1321 "Write access is not required." 1323 OBJECT mplsIdNodeId 1324 MIN-ACCESS read-only 1325 DESCRIPTION 1326 "Write access is not required." 1328 OBJECT mplsIdCc 1329 MIN-ACCESS read-only 1330 DESCRIPTION 1331 "Write access is not required." 1333 OBJECT mplsIdIcc 1334 MIN-ACCESS read-only 1335 DESCRIPTION 1336 "Write access is not required." 1338 ::= { mplsIdCompliances 2 } 1340 -- Units of conformance. 1342 mplsIdIpOperatorGroup OBJECT-GROUP 1343 OBJECTS { mplsIdGlobalId, 1344 mplsIdNodeId 1345 } 1346 STATUS current 1347 DESCRIPTION 1348 "The objects in this group are optional for ICC based 1349 node." 1350 ::= { mplsIdGroups 1 } 1352 mplsIdIccOperatorGroup OBJECT-GROUP 1353 OBJECTS { mplsIdNodeId, 1354 mplsIdCc, 1355 mplsIdIcc 1357 } 1358 STATUS current 1359 DESCRIPTION 1360 "The objects in this group are optional for IP based 1361 node." 1362 ::= { mplsIdGroups 2 } 1364 -- MPLS-ID-STD-MIB module ends 1365 END 1367 12. MPLS LSR Extension MIB definitions 1369 MPLS-LSR-EXT-STD-MIB DEFINITIONS ::= BEGIN 1371 IMPORTS 1372 MODULE-IDENTITY, OBJECT-TYPE 1373 FROM SNMPv2-SMI -- [RFC2578] 1374 MODULE-COMPLIANCE, OBJECT-GROUP 1375 FROM SNMPv2-CONF -- [RFC2580] 1376 mplsStdMIB 1377 FROM MPLS-TC-STD-MIB -- [RFC3811] 1378 RowPointer 1379 FROM SNMPv2-TC -- [RFC2579] 1380 mplsXCIndex, mplsXCInSegmentIndex, mplsXCOutSegmentIndex, 1381 mplsInterfaceGroup, mplsInSegmentGroup, mplsOutSegmentGroup, 1382 mplsXCGroup, mplsLsrNotificationGroup 1383 FROM MPLS-LSR-STD-MIB; -- [RFC3813] 1385 mplsLsrExtStdMIB MODULE-IDENTITY 1386 LAST-UPDATED 1387 "201405050000Z" -- May 05, 2014 1388 ORGANIZATION 1389 "Multiprotocol Label Switching (MPLS) Working Group" 1390 CONTACT-INFO 1391 " 1392 Venkatesan Mahalingam 1393 Dell Inc, 1394 5450 Great America Parkway, 1395 Santa Clara, CA 95054, USA 1396 Email: venkat.mahalingams@gmail.com 1398 Kannan KV Sampath 1399 Redeem, 1400 India 1401 Email: kannankvs@gmail.com 1403 Sam Aldrin 1404 Huawei Technologies 1405 2330 Central Express Way, 1406 Santa Clara, CA 95051, USA 1408 Email: aldrin.ietf@gmail.com 1410 Thomas D. Nadeau 1411 Email: tnadeau@lucidvision.com 1412 " 1413 DESCRIPTION 1414 "Copyright (c) 2014 IETF Trust and the persons identified 1415 as the document authors. All rights reserved. 1417 This MIB module contains generic object definitions for 1418 MPLS LSR in transport networks." 1420 -- Revision history. 1422 REVISION 1423 "201405050000Z" -- May 05, 2014 1424 DESCRIPTION 1425 "MPLS LSR specific MIB objects extension" 1427 ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value 1429 -- notifications 1430 mplsLsrExtNotifications OBJECT IDENTIFIER ::= { mplsLsrExtStdMIB 0 } 1432 -- tables, scalars 1433 mplsLsrExtObjects OBJECT IDENTIFIER 1434 ::= { mplsLsrExtStdMIB 1 } 1435 -- conformance 1436 mplsLsrExtConformance OBJECT IDENTIFIER 1437 ::= { mplsLsrExtStdMIB 2 } 1439 -- MPLS LSR common objects 1440 mplsXCExtTable OBJECT-TYPE 1441 SYNTAX SEQUENCE OF MplsXCExtEntry 1442 MAX-ACCESS not-accessible 1443 STATUS current 1444 DESCRIPTION 1445 "This table sparse augments the mplsXCTable of 1446 MPLS-LSR-STD-MIB [RFC3813] to provide MPLS-TP specific 1447 information about associated tunnel information" 1448 REFERENCE 1449 "1. Multiprotocol Label Switching (MPLS) Label Switching 1450 Router (LSR) Management Information Base (MIB), RFC 3813." 1451 ::= { mplsLsrExtObjects 1 } 1453 mplsXCExtEntry OBJECT-TYPE 1454 SYNTAX MplsXCExtEntry 1455 MAX-ACCESS not-accessible 1457 STATUS current 1458 DESCRIPTION 1460 "An entry in this table sparsely extends the cross connect 1461 information represented by an entry in 1462 the mplsXCTable in MPLS-LSR-STD-MIB [RFC3813] through 1463 a sparse augmentation. An entry can be created by 1464 a network operator via SNMP SET commands, or in 1465 response to signaling protocol events." 1466 REFERENCE 1467 "1. Multiprotocol Label Switching (MPLS) Label Switching 1468 Router (LSR) Management Information Base (MIB), RFC 3813." 1470 INDEX { mplsXCIndex, mplsXCInSegmentIndex, 1471 mplsXCOutSegmentIndex } 1472 ::= { mplsXCExtTable 1 } 1474 MplsXCExtEntry ::= SEQUENCE { 1475 mplsXCExtTunnelPointer RowPointer, 1476 mplsXCExtOppositeDirXCPtr RowPointer 1477 } 1479 mplsXCExtTunnelPointer OBJECT-TYPE 1480 SYNTAX RowPointer 1481 MAX-ACCESS read-only 1482 STATUS current 1483 DESCRIPTION 1484 "This read-only object indicates the back pointer to 1485 the tunnel entry segment. 1486 The only valid value for Tunnel Pointer is 1487 mplsTunnelTable entry." 1488 REFERENCE 1489 "1. Multiprotocol Label Switching (MPLS) Label Switching 1490 Router (LSR) Management Information Base (MIB), RFC 3813." 1491 ::= { mplsXCExtEntry 1 } 1493 mplsXCExtOppositeDirXCPtr OBJECT-TYPE 1494 SYNTAX RowPointer 1495 MAX-ACCESS read-create 1496 STATUS current 1497 DESCRIPTION 1498 "This object indicates the pointer to the opposite 1499 direction XC entry. This object cannot be modified if 1500 mplsXCRowStatus for the corresponding entry in the 1501 mplsXCTable is active(1). If this pointer is not set or 1502 removed, mplsXCOperStatus should be set to down(2)." 1503 REFERENCE 1504 "1. Multiprotocol Label Switching (MPLS) Label Switching 1505 Router (LSR) Management Information Base (MIB), RFC 3813." 1506 ::= { mplsXCExtEntry 2 } 1508 mplsLsrExtCompliances 1509 OBJECT IDENTIFIER ::= { mplsLsrExtConformance 1 } 1511 mplsLsrExtGroups 1512 OBJECT IDENTIFIER ::= { mplsLsrExtConformance 2 } 1514 -- Compliance requirement for fully compliant implementations. 1516 mplsLsrExtModuleFullCompliance MODULE-COMPLIANCE 1517 STATUS current 1518 DESCRIPTION 1519 "Compliance statement for agents that provide full support 1520 for MPLS-LSR-EXT-STD-MIB. 1521 The mandatory group has to be implemented by all LSRs 1522 that originate, terminate, or act as transit for 1523 TE-LSPs/tunnels. 1525 In addition, depending on the type of tunnels supported, 1526 other groups become mandatory as explained below." 1528 MODULE MPLS-LSR-STD-MIB -- The MPLS-LSR-STD-MIB, RFC3813 1530 MANDATORY-GROUPS { 1531 mplsInSegmentGroup, 1532 mplsOutSegmentGroup, 1533 mplsXCGroup, 1534 mplsLsrNotificationGroup 1535 } 1537 MODULE -- this module 1539 MANDATORY-GROUPS { 1540 mplsXCExtGroup 1541 } 1543 ::= { mplsLsrExtCompliances 1 } 1545 -- Compliance requirement for implementations that provide 1546 -- read-only access. 1548 mplsLsrExtModuleReadOnlyCompliance MODULE-COMPLIANCE 1549 STATUS current 1550 DESCRIPTION 1551 "Compliance requirement for implementations that only 1552 provide read-only support for MPLS-LSR-EXT-STD-MIB. 1553 Such devices can then be monitored but cannot be 1554 configured using this MIB module." 1556 MODULE MPLS-LSR-STD-MIB 1558 MANDATORY-GROUPS { 1559 mplsInterfaceGroup, 1560 mplsInSegmentGroup, 1561 mplsOutSegmentGroup 1562 } 1564 MODULE -- this module 1566 GROUP mplsXCExtReadOnlyObjectsGroup 1567 DESCRIPTION 1568 "This group is mandatory for devices which support 1569 Opposite direction XC configuration of tunnels." 1571 -- mplsXCExtTable 1572 OBJECT mplsXCExtOppositeDirXCPtr 1573 MIN-ACCESS read-only 1574 DESCRIPTION 1575 "Write access is not required. 1576 This object indicates the pointer to the opposite 1577 direction XC entry. The only valid value for XC 1578 Pointer is mplsXCTable entry." 1579 ::= { mplsLsrExtCompliances 2 } 1581 -- Units of conformance. 1583 mplsXCExtGroup OBJECT-GROUP 1584 OBJECTS { 1585 mplsXCExtTunnelPointer, 1586 mplsXCExtOppositeDirXCPtr 1587 } 1588 STATUS current 1589 DESCRIPTION 1590 "This object should be supported in order to access 1591 the tunnel entry from XC entry." 1592 ::= { mplsLsrExtGroups 1 } 1594 mplsXCExtReadOnlyObjectsGroup OBJECT-GROUP 1595 OBJECTS { 1596 mplsXCExtTunnelPointer, 1597 mplsXCExtOppositeDirXCPtr 1598 } 1599 STATUS current 1600 DESCRIPTION 1601 "This Object is needed to associate the opposite direction 1602 (forward/reverse) XC entry." 1603 ::= { mplsLsrExtGroups 2 } 1605 -- MPLS-LSR-EXT-STD-MIB module ends 1606 END 1608 13. MPLS Tunnel Extension MIB definitions 1610 MPLS-TE-EXT-STD-MIB DEFINITIONS ::= BEGIN 1612 IMPORTS 1613 MODULE-IDENTITY, OBJECT-TYPE, Counter32, 1614 Counter64, zeroDotZero 1615 FROM SNMPv2-SMI -- [RFC2578] 1616 MODULE-COMPLIANCE, OBJECT-GROUP 1617 FROM SNMPv2-CONF -- [RFC2580] 1618 TruthValue, RowStatus, RowPointer, StorageType 1619 FROM SNMPv2-TC -- [RFC2579] 1620 IndexIntegerNextFree 1621 FROM DIFFSERV-MIB -- [RFC3289] 1622 MplsGlobalId, MplsNodeId, MplsCcId, MplsIccId 1623 FROM MPLS-TC-EXT-STD-MIB 1624 mplsStdMIB, MplsTunnelIndex, MplsTunnelInstanceIndex, 1625 MplsExtendedTunnelId 1626 FROM MPLS-TC-STD-MIB -- [RFC3811] 1627 mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, 1628 mplsTunnelEgressLSRId 1629 FROM MPLS-TE-STD-MIB -- [RFC3812] 1630 ; 1632 mplsTeExtStdMIB MODULE-IDENTITY 1633 LAST-UPDATED 1634 "201405050000Z" -- May 05, 2014 1635 ORGANIZATION 1636 "Multiprotocol Label Switching (MPLS) Working Group" 1637 CONTACT-INFO 1638 " 1639 Venkatesan Mahalingam 1640 Dell Inc, 1641 5450 Great America Parkway, 1642 Santa Clara, CA 95054, USA 1643 Email: venkat.mahalingams@gmail.com 1645 Kannan KV Sampath 1646 Redeem, 1647 India 1648 Email: kannankvs@gmail.com 1650 Sam Aldrin 1651 Huawei Technologies 1652 2330 Central Express Way, 1653 Santa Clara, CA 95051, USA 1654 Email: aldrin.ietf@gmail.com 1656 Thomas D. Nadeau 1657 Email: tnadeau@lucidvision.com 1658 " 1659 DESCRIPTION 1660 "Copyright (c) 2014 IETF Trust and the persons identified 1661 as the document authors. All rights reserved. 1663 This MIB module contains generic object definitions for 1664 MPLS Traffic Engineering in transport networks." 1666 -- Revision history. 1668 REVISION 1669 "201405050000Z" -- May 05, 2014 1671 DESCRIPTION 1672 "MPLS TE MIB objects extension" 1674 ::= { mplsStdMIB xxx } -- xxx to be replaced 1675 -- with correct value 1677 -- Top level components of this MIB module. 1679 -- tables, scalars 1680 mplsTeExtObjects OBJECT IDENTIFIER 1681 ::= { mplsTeExtStdMIB 0 } 1682 -- conformance 1683 mplsTeExtConformance OBJECT IDENTIFIER 1684 ::= { mplsTeExtStdMIB 1 } 1686 -- Start of MPLS Transport Profile Node configuration table 1688 mplsTunnelExtNodeConfigLocalIdNext OBJECT-TYPE 1689 SYNTAX IndexIntegerNextFree (0..16777215) 1690 MAX-ACCESS read-only 1691 STATUS current 1692 DESCRIPTION 1693 "This object contains an unused value for 1694 mplsTunnelExtNodeConfigLocalId, or a zero to indicate 1695 that none exist. Negative values are not allowed, 1696 as they do not correspond to valid values of 1697 mplsTunnelExtNodeConfigLocalId." 1698 ::= { mplsTeExtObjects 1 } 1700 mplsTunnelExtNodeConfigTable OBJECT-TYPE 1701 SYNTAX SEQUENCE OF MplsTunnelExtNodeConfigEntry 1702 MAX-ACCESS not-accessible 1703 STATUS current 1704 DESCRIPTION 1705 "This table allows the operator to map a node or 1706 LSR Identifier (IP compatible [Global_ID::Node_ID] or 1707 ICC based [ICC_Operator_ID::Node_ID]) with a local 1708 identifier. 1710 This table is created to reuse the existing 1711 mplsTunnelTable for MPLS based transport network 1712 tunnels also. 1714 Since the MPLS tunnel's Ingress/Egress LSR identifiers' 1715 size (Unsigned32) value is not compatible for 1716 MPLS-TP tunnel i.e. Global_ID::Node_ID of size 8 bytes and 1717 ICC_Operator_ID::Node_ID of size 12 bytes, there exists a 1718 need to map the Global_ID::Node_ID or ICC_Operator_ID::Node_ID 1719 with the local identifier of size 4 bytes (Unsigned32) value 1720 in order to index (Ingress/Egress LSR identifier) 1721 the existing mplsTunnelTable." 1723 ::= { mplsTeExtObjects 2 } 1725 mplsTunnelExtNodeConfigEntry OBJECT-TYPE 1726 SYNTAX MplsTunnelExtNodeConfigEntry 1727 MAX-ACCESS not-accessible 1728 STATUS current 1729 DESCRIPTION 1730 "An entry in this table represents a mapping 1731 identification for the operator or service provider 1732 with node or LSR. 1734 As per [RFC6370], IP compatible mapping is represented 1735 as Global_ID::Node_ID. 1737 As per [RFC6923], the CC and the ICC form the ICC_Operator_ID 1738 as CC::ICC and ICC compatible mapping is represented 1739 as ICC_Operator_ID::Node_ID. 1741 Note: Each entry in this table should have a unique 1742 [Global_ID and Node_ID] or [CC::ICC and Node_ID] combination." 1743 INDEX { mplsTunnelExtNodeConfigLocalId } 1744 ::= { mplsTunnelExtNodeConfigTable 1 } 1746 MplsTunnelExtNodeConfigEntry ::= SEQUENCE { 1747 mplsTunnelExtNodeConfigLocalId MplsExtendedTunnelId, 1748 mplsTunnelExtNodeConfigGlobalId MplsGlobalId, 1749 mplsTunnelExtNodeConfigCcId MplsCcId, 1750 mplsTunnelExtNodeConfigIccId MplsIccId, 1751 mplsTunnelExtNodeConfigNodeId MplsNodeId, 1752 mplsTunnelExtNodeConfigIccValid TruthValue, 1753 mplsTunnelExtNodeConfigStorageType StorageType, 1754 mplsTunnelExtNodeConfigRowStatus RowStatus 1756 } 1757 mplsTunnelExtNodeConfigLocalId OBJECT-TYPE 1758 SYNTAX MplsExtendedTunnelId 1759 MAX-ACCESS not-accessible 1760 STATUS current 1761 DESCRIPTION 1762 "This object is used in accommodating the bigger 1763 size Global_ID::Node_ID and/or the ICC_Operator_ID::Node_ID 1764 with lower size LSR identifier in order to index 1765 the mplsTunnelTable. 1767 The Local Identifier is configured between 0 and 16777215, 1768 as valid IP address range starts from 16777216(01.00.00.00). 1769 This range is chosen to identify the mplsTunnelTable's 1770 Ingress/Egress LSR-id is IP address or Local identifier, 1771 if the configured range is not IP address, operator is 1772 expected to retrieve the complete information 1773 (Global_ID::Node_ID or ICC_Operator_ID::Node_ID) from 1774 mplsTunnelExtNodeConfigTable. 1775 This way, existing mplsTunnelTable is reused for 1776 bidirectional tunnel extensions for MPLS based transport 1777 networks. 1779 This Local Identifier allows the operator to assign 1780 a unique identifier to map Global_ID::Node_ID and/or 1781 ICC_Operator_ID::Node_ID. As this Local Identifier is unique 1782 within the node and the same syntax of this object can be 1783 used for MPLS TE tunnel also, it is up to the operator/local 1784 management entity to choose the non-conflicting value for 1785 indexing the MPLS and MPLS-TP tunnel entries." 1786 ::= { mplsTunnelExtNodeConfigEntry 1 } 1788 mplsTunnelExtNodeConfigGlobalId OBJECT-TYPE 1789 SYNTAX MplsGlobalId 1790 MAX-ACCESS read-create 1791 STATUS current 1792 DESCRIPTION 1793 "This object indicates the Global Operator Identifier. 1794 This object has no meaning when 1795 mplsTunnelExtNodeConfigIccValid is set true." 1796 REFERENCE 1797 "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370] 1798 Section 3." 1799 ::= { mplsTunnelExtNodeConfigEntry 2 } 1801 mplsTunnelExtNodeConfigCcId OBJECT-TYPE 1802 SYNTAX MplsCcId 1803 MAX-ACCESS read-create 1804 STATUS current 1805 DESCRIPTION 1806 "This object allows the operator or service provider to 1807 configure a unique MPLS-TP ITU-T Country Code (CC) 1808 either for Ingress ID or Egress ID. 1810 This object has no meaning when 1811 mplsTunnelExtNodeConfigIccValid is set false." 1812 REFERENCE 1813 "MPLS-TP Identifiers Following ITU-T Conventions, 1814 [RFC6923] Section 3" 1815 ::= { mplsTunnelExtNodeConfigEntry 3 } 1817 mplsTunnelExtNodeConfigIccId OBJECT-TYPE 1818 SYNTAX MplsIccId 1819 MAX-ACCESS read-create 1820 STATUS current 1821 DESCRIPTION 1822 "This object allows the operator or service provider to 1823 configure a unique MPLS-TP ITU-T Carrier Code (ICC) 1824 either for Ingress ID or Egress ID. 1826 This object has no meaning when 1827 mplsTunnelExtNodeConfigIccValid is set false." 1828 REFERENCE 1829 "MPLS-TP Identifiers Following ITU-T Conventions, 1830 [RFC6923] Section 3" 1831 ::= { mplsTunnelExtNodeConfigEntry 4 } 1833 mplsTunnelExtNodeConfigNodeId OBJECT-TYPE 1834 SYNTAX MplsNodeId 1835 MAX-ACCESS read-create 1836 STATUS current 1837 DESCRIPTION 1838 "This object indicates the Node_ID within the scope 1839 of a Global_ID or ICC_Operator_ID." 1840 REFERENCE 1841 "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370] 1842 Section 4." 1843 ::= { mplsTunnelExtNodeConfigEntry 5 } 1845 mplsTunnelExtNodeConfigIccValid OBJECT-TYPE 1846 SYNTAX TruthValue 1847 MAX-ACCESS read-create 1848 STATUS current 1849 DESCRIPTION 1850 "Denotes whether or not this entry uses 1851 mplsTunnelExtNodeConfigCcId, 1852 mplsTunnelExtNodeConfigIccId and 1853 mplsTunnelExtNodeConfigNodeId for mapping 1854 the ICC based identifiers with the local identifier. 1855 Note that if this variable is set to false then the 1856 mplsTunnelExtNodeConfigGlobalId and 1857 mplsTunnelExtNodeConfigNodeId objects should have 1858 the valid information." 1859 DEFVAL { false } 1860 ::= { mplsTunnelExtNodeConfigEntry 6 } 1862 mplsTunnelExtNodeConfigStorageType OBJECT-TYPE 1863 SYNTAX StorageType 1864 MAX-ACCESS read-create 1865 STATUS current 1866 DESCRIPTION 1867 "This variable indicates the storage type for this 1868 object. 1869 Conceptual rows having the value 'permanent' 1870 need not allow write-access to any columnar 1871 objects in the row." 1872 DEFVAL { volatile } 1873 ::= { mplsTunnelExtNodeConfigEntry 7 } 1875 mplsTunnelExtNodeConfigRowStatus OBJECT-TYPE 1876 SYNTAX RowStatus 1877 MAX-ACCESS read-create 1878 STATUS current 1879 DESCRIPTION 1880 "This object allows the operator to create, modify, 1881 and/or delete a row in this table." 1882 ::= { mplsTunnelExtNodeConfigEntry 8 } 1884 -- End of MPLS Transport Profile Node configuration table 1886 -- Start of MPLS Transport Profile Node IP compatible 1887 -- mapping table 1889 mplsTunnelExtNodeIpMapTable OBJECT-TYPE 1890 SYNTAX SEQUENCE OF MplsTunnelExtNodeIpMapEntry 1892 MAX-ACCESS not-accessible 1893 STATUS current 1894 DESCRIPTION 1895 "This read-only table allows the operator to retrieve 1896 the local identifier for a given Global_ID::Node_ID in an IP 1897 compatible operator environment. 1899 This table MAY be used in on-demand and/or proactive 1901 OAM operations to get the Ingress/Egress LSR identifier 1902 (Local Identifier) from Src-Global_Node_ID 1903 or Dst-Global_Node_ID and the Ingress and Egress LSR 1904 identifiers are used to retrieve the tunnel entry. 1906 This table returns nothing when the associated entry 1907 is not defined in mplsTunnelExtNodeConfigTable." 1908 ::= { mplsTeExtObjects 3 } 1910 mplsTunnelExtNodeIpMapEntry OBJECT-TYPE 1911 SYNTAX MplsTunnelExtNodeIpMapEntry 1912 MAX-ACCESS not-accessible 1913 STATUS current 1914 DESCRIPTION 1915 "An entry in this table represents a mapping of 1916 Global_ID::Node_ID with the local identifier. 1918 An entry in this table is created automatically when 1919 the Local identifier is associated with Global_ID and 1920 Node_Id in the mplsTunnelExtNodeConfigTable. 1922 Note: Each entry in this table should have a unique 1923 Global_ID and Node_ID combination." 1924 INDEX { mplsTunnelExtNodeIpMapGlobalId, 1925 mplsTunnelExtNodeIpMapNodeId 1926 } 1927 ::= { mplsTunnelExtNodeIpMapTable 1 } 1929 MplsTunnelExtNodeIpMapEntry ::= SEQUENCE { 1930 mplsTunnelExtNodeIpMapGlobalId MplsGlobalId, 1931 mplsTunnelExtNodeIpMapNodeId MplsNodeId, 1932 mplsTunnelExtNodeIpMapLocalId MplsExtendedTunnelId 1933 } 1935 mplsTunnelExtNodeIpMapGlobalId OBJECT-TYPE 1936 SYNTAX MplsGlobalId 1937 MAX-ACCESS not-accessible 1938 STATUS current 1939 DESCRIPTION 1940 "This object indicates the Global_ID." 1941 ::= { mplsTunnelExtNodeIpMapEntry 1 } 1943 mplsTunnelExtNodeIpMapNodeId OBJECT-TYPE 1944 SYNTAX MplsNodeId 1945 MAX-ACCESS not-accessible 1946 STATUS current 1947 DESCRIPTION 1948 "This object indicates the Node_ID within the 1950 operator." 1951 ::= { mplsTunnelExtNodeIpMapEntry 2 } 1953 mplsTunnelExtNodeIpMapLocalId OBJECT-TYPE 1954 SYNTAX MplsExtendedTunnelId 1955 MAX-ACCESS read-only 1956 STATUS current 1957 DESCRIPTION 1958 "This object contains an IP compatible local identifier 1959 which is defined in mplsTunnelExtNodeConfigTable." 1960 ::= { mplsTunnelExtNodeIpMapEntry 3 } 1962 -- End MPLS Transport Profile Node IP compatible table 1964 -- Start of MPLS Transport Profile Node ICC based table 1966 mplsTunnelExtNodeIccMapTable OBJECT-TYPE 1967 SYNTAX SEQUENCE OF MplsTunnelExtNodeIccMapEntry 1968 MAX-ACCESS not-accessible 1969 STATUS current 1970 DESCRIPTION 1971 "This read-only table allows the operator to retrieve 1972 the local identifier for a given ICC_Operator_ID::Node_ID 1973 in an ICC operator environment. 1975 This table MAY be used in on-demand and/or proactive 1976 OAM operations to get the Ingress/Egress LSR 1977 identifier (Local Identifier) from Src-ICC 1978 or Dst-ICC and the Ingress and Egress LSR 1979 identifiers are used to retrieve the tunnel entry. 1980 This table returns nothing when the associated entry 1981 is not defined in mplsTunnelExtNodeConfigTable." 1982 ::= { mplsTeExtObjects 4 } 1984 mplsTunnelExtNodeIccMapEntry OBJECT-TYPE 1985 SYNTAX MplsTunnelExtNodeIccMapEntry 1986 MAX-ACCESS not-accessible 1987 STATUS current 1988 DESCRIPTION 1989 "An entry in this table represents a mapping of 1990 ICC_Operator_ID::Node_ID with the local identifier. 1992 An entry in this table is created automatically when 1993 the Local identifier is associated with 1994 ICC_Operator_ID::Node_ID in 1995 the mplsTunnelExtNodeConfigTable." 1996 INDEX { mplsTunnelExtNodeIccMapCcId, 1997 mplsTunnelExtNodeIccMapIccId, 1998 mplsTunnelExtNodeIccMapNodeId } 1999 ::= { mplsTunnelExtNodeIccMapTable 1 } 2001 MplsTunnelExtNodeIccMapEntry ::= SEQUENCE { 2002 mplsTunnelExtNodeIccMapCcId MplsCcId, 2003 mplsTunnelExtNodeIccMapIccId MplsIccId, 2004 mplsTunnelExtNodeIccMapNodeId MplsNodeId, 2005 mplsTunnelExtNodeIccMapLocalId MplsExtendedTunnelId 2006 } 2008 mplsTunnelExtNodeIccMapCcId OBJECT-TYPE 2009 SYNTAX MplsCcId 2010 MAX-ACCESS not-accessible 2011 STATUS current 2012 DESCRIPTION 2013 "This object allows the operator or service provider to 2014 configure a unique MPLS-TP ITU-T Country Code (CC) 2015 either for Ingress or Egress LSR ID. 2017 The CC is a string of two alphabetic characters 2018 represented with upper case letters (i.e., A-Z)." 2019 ::= { mplsTunnelExtNodeIccMapEntry 1 } 2021 mplsTunnelExtNodeIccMapIccId OBJECT-TYPE 2022 SYNTAX MplsIccId 2023 MAX-ACCESS not-accessible 2024 STATUS current 2025 DESCRIPTION 2026 "This object allows the operator or service provider 2027 to configure a unique MPLS-TP ITU-T Carrier 2028 Code (ICC) either for Ingress or Egress LSR ID. 2030 The ICC is a string of one to six characters, each 2031 character being either alphabetic (i.e. A-Z) or 2032 numeric (i.e. 0-9) characters. Alphabetic characters 2033 in the ICC should be represented with upper case 2034 letters." 2035 ::= { mplsTunnelExtNodeIccMapEntry 2 } 2037 mplsTunnelExtNodeIccMapNodeId OBJECT-TYPE 2038 SYNTAX MplsNodeId 2039 MAX-ACCESS not-accessible 2040 STATUS current 2041 DESCRIPTION 2042 "This object indicates the Node_ID within the 2043 ICC based operator." 2044 ::= { mplsTunnelExtNodeIccMapEntry 3} 2046 mplsTunnelExtNodeIccMapLocalId OBJECT-TYPE 2047 SYNTAX MplsExtendedTunnelId 2048 MAX-ACCESS read-only 2049 STATUS current 2050 DESCRIPTION 2051 "This object contains an ICC based local identifier 2052 which is defined in mplsTunnelExtNodeConfigTable." 2053 ::= { mplsTunnelExtNodeIccMapEntry 4 } 2055 -- End MPLS Transport Profile Node ICC based table 2057 -- Start of MPLS Tunnel table extension 2059 mplsTunnelExtTable OBJECT-TYPE 2060 SYNTAX SEQUENCE OF MplsTunnelExtEntry 2061 MAX-ACCESS not-accessible 2062 STATUS current 2063 DESCRIPTION 2064 "This table represents extensions to mplsTunnelTable 2065 in order to support MPLS-TP tunnels. 2067 As per MPLS-TP Identifiers [RFC6370], LSP_ID for IP based 2068 co-routed bidirectional tunnel, 2070 A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: 2071 Node_ID::Tunnel_Num}::LSP_Num 2073 LSP_ID for IP based associated bidirectional tunnel, 2074 A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: 2075 Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num} 2077 mplsTunnelTable is reused for forming the LSP_ID 2078 as follows, 2080 Source Tunnel_Num is mapped with mplsTunnelIndex, 2081 Source Node_ID is mapped with 2082 mplsTunnelIngressLSRId, Destination Node_ID is 2083 mapped with mplsTunnelEgressLSRId LSP_Num is mapped with 2084 mplsTunnelInstance. 2086 Source Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID and 2087 Destination Global_ID::Node_ID and/or ICC_Operator_ID::Node-ID 2088 are maintained in the mplsTunnelExtNodeConfigTable and 2089 mplsTunnelExtNodeConfigLocalId is used to create an entry 2090 in mplsTunnelTable." 2091 REFERENCE 2092 "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370]." 2093 ::= { mplsTeExtObjects 5 } 2095 mplsTunnelExtEntry OBJECT-TYPE 2096 SYNTAX MplsTunnelExtEntry 2097 MAX-ACCESS not-accessible 2098 STATUS current 2099 DESCRIPTION 2100 "An entry in this table represents MPLS-TP 2101 specific additional tunnel configurations." 2102 INDEX { 2103 mplsTunnelIndex, 2104 mplsTunnelInstance, 2105 mplsTunnelIngressLSRId, 2106 mplsTunnelEgressLSRId 2107 } 2108 ::= { mplsTunnelExtTable 1 } 2110 MplsTunnelExtEntry ::= SEQUENCE { 2111 mplsTunnelExtOppositeDirPtr RowPointer, 2112 mplsTunnelExtOppositeDirTnlValid TruthValue, 2113 mplsTunnelExtDestTnlIndex MplsTunnelIndex, 2114 mplsTunnelExtDestTnlLspIndex MplsTunnelInstanceIndex, 2115 mplsTunnelExtDestTnlValid TruthValue, 2116 mplsTunnelExtIngressLSRLocalIdValid TruthValue, 2117 mplsTunnelExtEgressLSRLocalIdValid TruthValue 2119 } 2121 mplsTunnelExtOppositeDirPtr OBJECT-TYPE 2122 SYNTAX RowPointer 2123 MAX-ACCESS read-create 2124 STATUS current 2125 DESCRIPTION 2126 "This object points to the opposite direction tunnel entry." 2127 ::= { mplsTunnelExtEntry 1 } 2129 mplsTunnelExtOppositeDirTnlValid OBJECT-TYPE 2130 SYNTAX TruthValue 2131 MAX-ACCESS read-create 2132 STATUS current 2133 DESCRIPTION 2134 "Denotes whether or not this tunnel uses 2135 mplsTunnelExtOppositeDirPtr for identifying the opposite 2136 direction tunnel information. Note that if this variable 2137 is set to true then the mplsTunnelExtOppositeDirPtr should 2138 point to the first accessible row of the valid opposite 2139 direction tunnel." 2140 DEFVAL { false } 2141 ::= { mplsTunnelExtEntry 2 } 2143 mplsTunnelExtDestTnlIndex OBJECT-TYPE 2144 SYNTAX MplsTunnelIndex 2145 MAX-ACCESS read-create 2146 STATUS current 2147 DESCRIPTION 2148 "This object is applicable only for the bidirectional 2149 tunnel that has the forward and reverse LSPs in the 2150 different tunnel entries. 2152 The values of this object and the 2153 mplsTunnelExtDestTnlLspIndex object together can be used 2154 to identify an opposite direction LSP i.e. if the 2155 mplsTunnelIndex and mplsTunnelInstance hold the value 2156 for forward LSP, this object and 2157 mplsTunnelExtDestTnlLspIndex can be used to retrieve 2158 the reverse direction LSP and vice versa. 2160 This object and mplsTunnelExtDestTnlLspIndex values 2161 provide the first two indices of tunnel entry and 2162 the remaining indices can be derived as follows, 2163 the Ingress and Egress Identifiers should be 2164 swapped in order to index the other direction tunnel." 2165 ::= { mplsTunnelExtEntry 3 } 2167 mplsTunnelExtDestTnlLspIndex OBJECT-TYPE 2168 SYNTAX MplsTunnelInstanceIndex 2169 MAX-ACCESS read-create 2170 STATUS current 2171 DESCRIPTION 2172 "This object is applicable only for the bidirectional 2173 tunnel that has the forward and reverse LSPs in the 2174 different tunnel entries. This object holds 2175 the instance index of the opposite direction tunnel." 2176 ::= { mplsTunnelExtEntry 4 } 2178 mplsTunnelExtDestTnlValid OBJECT-TYPE 2179 SYNTAX TruthValue 2180 MAX-ACCESS read-create 2181 STATUS current 2182 DESCRIPTION 2183 "Denotes whether or not this tunnel uses 2184 mplsTunnelExtDestTnlIndex and 2185 mplsTunnelExtDestTnlLspIndex for identifying 2186 the opposite direction tunnel information. Note that if 2187 this variable is set to true then the 2188 mplsTunnelExtDestTnlIndex and 2189 mplsTunnelExtDestTnlLspIndex objects should have 2190 the valid opposite direction tunnel indices." 2191 DEFVAL { false } 2192 ::= { mplsTunnelExtEntry 5 } 2194 mplsTunnelExtIngressLSRLocalIdValid OBJECT-TYPE 2195 SYNTAX TruthValue 2196 MAX-ACCESS read-create 2197 STATUS current 2198 DESCRIPTION 2199 "This object denotes whether the mplsTunnelIngressLSRId 2200 contains the local value, which is used to reference 2201 the complete Ingress Global_ID::Node_ID or ICC_Operator_ID 2202 from the mplsTunnelExtNodeConfigTable. 2204 If this object is set to FALSE, mplsTunnelExtNodeConfigTable 2205 will not contain an entry to reference local identifier with 2206 Global_ID::Node_ID or ICC_Operator_ID::Node_ID value. 2208 This object is set to FALSE for legacy implementations like 2209 MPLS TE tunnels where mplsTunnelIngressId itself provides 2210 complete Ingress LSRId." 2211 REFERENCE 2212 "MPLS-TE-STD-MIB [RFC3812], Section 11. 2213 mplsTunnelIngressLSRId object in mplsTunnelTable." 2214 DEFVAL { false } 2215 ::= { mplsTunnelExtEntry 6 } 2217 mplsTunnelExtEgressLSRLocalIdValid OBJECT-TYPE 2218 SYNTAX TruthValue 2219 MAX-ACCESS read-create 2220 STATUS current 2221 DESCRIPTION 2222 "This object denotes whether the mplsTunnelEgressLSRId 2223 contains the local value, which is used to reference 2224 the complete Egress Global_ID::Node_ID or 2225 ICC_Operator_ID::Node_ID from 2226 the mplsTunnelExtNodeConfigTable. 2228 If this object is set to FALSE, mplsTunnelExtNodeConfigTable 2229 will not contain an entry to reference local identifier with 2230 Global_ID::Node_ID or ICC_Operator_ID::Node_ID value. 2232 This object is set to FALSE for legacy implementations like 2233 MPLS TE tunnels where mplsTunnelEgressId itself provides 2234 complete Egress LSRId." 2235 REFERENCE 2236 "MPLS-TE-STD-MIB [RFC3812], Section 11. 2237 mplsTunnelEgressLSRId object in mplsTunnelTable." 2238 DEFVAL { false } 2239 ::= { mplsTunnelExtEntry 7 } 2241 -- End of MPLS Tunnel table extension 2243 -- Module compliance. 2245 mplsTeExtCompliances 2246 OBJECT IDENTIFIER ::= { mplsTeExtConformance 1 } 2248 mplsTeExtGroups 2249 OBJECT IDENTIFIER ::= { mplsTeExtConformance 2 } 2251 -- Compliance requirement for fully compliant implementations. 2253 mplsTeExtModuleFullCompliance MODULE-COMPLIANCE 2254 STATUS current 2255 DESCRIPTION 2256 "Compliance statement for agents that provide full 2257 support the MPLS-TE-EXT-STD-MIB module." 2259 MODULE -- this module 2261 -- The mandatory group has to be implemented by all 2262 -- LSRs that originate/terminate MPLS-TP tunnels. 2263 -- In addition, depending on the type of tunnels 2264 -- supported, other groups become mandatory as 2266 -- explained below. 2268 MANDATORY-GROUPS { 2269 mplsTunnelExtGroup 2270 } 2272 GROUP mplsTunnelExtIpOperatorGroup 2273 DESCRIPTION 2274 "This group is mandatory for devices which support 2275 configuration of IP based identifier tunnels." 2277 GROUP mplsTunnelExtIccOperatorGroup 2278 DESCRIPTION 2279 "This group is mandatory for devices which support 2280 configuration of ICC based tunnels." 2282 ::= { mplsTeExtCompliances 1 } 2284 -- Compliance requirement for read-only implementations. 2286 mplsTeExtModuleReadOnlyCompliance MODULE-COMPLIANCE 2287 STATUS current 2288 DESCRIPTION 2289 "Compliance statement for agents that only provide 2290 read-only support for MPLS-TE-EXT-STD-MIB module." 2292 MODULE -- this module 2294 MANDATORY-GROUPS { 2295 mplsTunnelExtGroup 2296 } 2298 GROUP mplsTunnelExtIpOperatorGroup 2299 DESCRIPTION 2300 "This group is mandatory for devices which support 2301 configuration of IP based identifier tunnels." 2303 GROUP mplsTunnelExtIccOperatorGroup 2304 DESCRIPTION 2305 "This group is mandatory for devices which support 2306 configuration of ICC based tunnels." 2308 -- mplsTunnelExtTable 2310 OBJECT mplsTunnelExtOppositeDirPtr 2311 MIN-ACCESS read-only 2312 DESCRIPTION 2313 "Write access is not required." 2315 OBJECT mplsTunnelExtOppositeDirTnlValid 2316 MIN-ACCESS read-only 2317 DESCRIPTION 2318 "Write access is not required." 2320 OBJECT mplsTunnelExtDestTnlIndex 2321 MIN-ACCESS read-only 2322 DESCRIPTION 2323 "Write access is not required." 2325 OBJECT mplsTunnelExtDestTnlLspIndex 2326 MIN-ACCESS read-only 2327 DESCRIPTION 2328 "Write access is not required." 2330 OBJECT mplsTunnelExtDestTnlValid 2331 MIN-ACCESS read-only 2332 DESCRIPTION 2333 "Write access is not required." 2335 OBJECT mplsTunnelExtIngressLSRLocalIdValid 2336 MIN-ACCESS read-only 2337 DESCRIPTION 2338 "Write access is not required." 2340 OBJECT mplsTunnelExtEgressLSRLocalIdValid 2341 MIN-ACCESS read-only 2342 DESCRIPTION 2343 "Write access is not required." 2345 OBJECT mplsTunnelExtNodeConfigGlobalId 2346 MIN-ACCESS read-only 2347 DESCRIPTION 2348 "Write access is not required." 2350 OBJECT mplsTunnelExtNodeConfigNodeId 2351 MIN-ACCESS read-only 2352 DESCRIPTION 2353 "Write access is not required." 2355 OBJECT mplsTunnelExtNodeConfigStorageType 2356 MIN-ACCESS read-only 2357 DESCRIPTION 2358 "Write access is not required." 2360 OBJECT mplsTunnelExtNodeConfigRowStatus 2361 SYNTAX RowStatus { active(1) } 2362 MIN-ACCESS read-only 2363 DESCRIPTION 2364 "Write access is not required." 2366 OBJECT mplsTunnelExtNodeConfigCcId 2367 MIN-ACCESS read-only 2368 DESCRIPTION 2369 "Write access is not required." 2371 OBJECT mplsTunnelExtNodeConfigIccId 2372 MIN-ACCESS read-only 2373 DESCRIPTION 2374 "Write access is not required." 2376 OBJECT mplsTunnelExtNodeConfigIccValid 2377 MIN-ACCESS read-only 2378 DESCRIPTION 2379 "Write access is not required." 2381 ::= { mplsTeExtCompliances 2 } 2383 -- Units of conformance. 2385 mplsTunnelExtGroup OBJECT-GROUP 2386 OBJECTS { 2387 mplsTunnelExtOppositeDirPtr, 2388 mplsTunnelExtOppositeDirTnlValid, 2389 mplsTunnelExtDestTnlIndex, 2390 mplsTunnelExtDestTnlLspIndex, 2391 mplsTunnelExtDestTnlValid, 2392 mplsTunnelExtIngressLSRLocalIdValid, 2393 mplsTunnelExtEgressLSRLocalIdValid 2394 } 2396 STATUS current 2397 DESCRIPTION 2398 "Necessary, but not sufficient, set of objects to 2399 implement tunnels. In addition, depending on the 2400 operating environment, the following groups are 2401 mandatory." 2402 ::= { mplsTeExtGroups 1 } 2404 mplsTunnelExtIpOperatorGroup OBJECT-GROUP 2405 OBJECTS { mplsTunnelExtNodeConfigLocalIdNext, 2406 mplsTunnelExtNodeConfigGlobalId, 2407 mplsTunnelExtNodeConfigNodeId, 2408 mplsTunnelExtNodeIpMapLocalId, 2409 mplsTunnelExtNodeConfigStorageType, 2410 mplsTunnelExtNodeConfigRowStatus 2411 } 2412 STATUS current 2413 DESCRIPTION 2414 "Object(s) needed to implement IP compatible tunnels." 2415 ::= { mplsTeExtGroups 2 } 2417 mplsTunnelExtIccOperatorGroup OBJECT-GROUP 2418 OBJECTS { mplsTunnelExtNodeConfigLocalIdNext, 2419 mplsTunnelExtNodeConfigCcId, 2420 mplsTunnelExtNodeConfigIccId, 2421 mplsTunnelExtNodeConfigNodeId, 2422 mplsTunnelExtNodeConfigIccValid, 2423 mplsTunnelExtNodeIccMapLocalId, 2424 mplsTunnelExtNodeConfigStorageType, 2425 mplsTunnelExtNodeConfigRowStatus 2426 } 2427 STATUS current 2428 DESCRIPTION 2429 "Object(s) needed to implement ICC based tunnels." 2430 ::= { mplsTeExtGroups 3 } 2432 -- MPLS-TE-EXT-STD-MIB module ends 2433 END 2435 14. Security Consideration 2437 It is clear that this MIB module is potentially useful for the 2438 monitoring of MPLS TE tunnels. This MIB module can also be used for 2439 the configuration of certain objects, and anything that can be 2440 configured can be incorrectly configured, with potentially disastrous 2441 results. 2443 There are a number of management objects defined in this MIB module 2444 with a MAX-ACCESS clause of read-write and/or read-create. Such 2445 objects may be considered sensitive or vulnerable in some network 2446 environments. The support for SET operations in a non-secure 2447 environment without proper protection can have a negative effect on 2448 network operations. These are the tables and objects and their 2449 sensitivity/vulnerability: 2451 - the tables specified in [RFC3812], [RFC3813] and this document 2452 MIB tables mplsTunnelExtNodeConfigTable, mplsTunnelExtTable and 2453 mplsXCExtTable collectively contain objects to provision MPLS-TP 2454 tunnels, tunnel hops, and tunnel resources. 2455 Unauthorized access to objects in these tables, could result in 2456 disruption of traffic on the network. This is especially true if 2457 a tunnel has been established. The use of stronger mechanisms, 2458 such as SNMPv3 security, should be considered where possible. 2459 Specifically, SNMPv3 VACM and USM MUST be used with any v3 agent 2460 which implements this MIB. Administrators should consider whether 2461 read access to these objects should be allowed, since read access 2462 may be undesirable under certain circumstances. 2464 Some of the readable objects in this MIB module (i.e., objects 2465 with a MAX-ACCESS other than not-accessible) may be considered 2466 sensitive or vulnerable in some network environments. 2467 It is thus important to control even GET and/or NOTIFY access to 2468 these objects and possibly to even encrypt the values of these 2469 objects when sending them over the network via SNMP. These are 2470 the tables and objects and their sensitivity/vulnerability: 2472 - the tables specified in [RFC3812], [RFC3813] and this document 2473 MIB tables mplsTunnelExtNodeConfigTable, mplsTunnelExtTable, 2474 and mplsXCExtTable collectively show the MPLS-TP tunnel network 2475 topology characteristics. If an Administrator does not want to 2476 reveal this information, then these tables should be considered 2477 sensitive/vulnerable. 2479 SNMP versions prior to SNMPv3 did not include adequate security. 2480 Even if the network itself is secure (for example by using IPsec), 2481 even then, there is no control as to who on the secure network is 2482 allowed to access and GET/SET (read/change/create/delete) 2483 the objects in this MIB module. 2485 It is recommended that implementers consider the security features as 2486 provided by the SNMPv3 framework (see [RFC3410], section 8), 2487 including full supports for the SNMPv3 cryptographic mechanisms (for 2488 authentication and privacy). 2490 Further, deployment of SNMP versions prior to SNMPv3 is not 2491 recommended. Instead, it is recommended to deploy SNMPv3 and to 2492 enable cryptographic security. It is then a customer/operator 2493 responsibility to ensure that the SNMP entity giving access to an 2494 instance of this MIB module is properly configured to give 2495 access to the objects only to those principles (users) that 2496 have legitimate rights to indeed GET or SET (change/create/delete) 2497 them. 2499 15. IANA Considerations 2501 As described in [RFC4221], [RFC6639] and as requested in the MPLS-TC- 2502 STD-MIB [RFC3811], MPLS related standards track MIB modules should be 2503 rooted under the mplsStdMIB subtree. There are 4 MPLS MIB Modules 2504 contained in this document, each of the following "IANA 2505 Considerations" subsections requests IANA for a new assignment under 2506 the mplsStdMIB subtree. New assignments can only be made via a 2507 Standards Action as specified in [RFC5226]. 2509 15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB 2511 IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS-TC- 2512 EXT-STD-MIB module specified in this document. 2514 15.2. IANA Considerations for MPLS-ID-STD-MIB 2515 IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS-ID- 2516 STD-MIB module specified in this document. 2518 15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB 2519 IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS- 2520 LSR-EXT-STD-MIB module specified in this document. 2522 15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB 2524 IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS-TE- 2525 EXT-STD-MIB module specified in this document. 2527 16. References 2529 16.1. Normative References 2531 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2532 Requirement Levels", BCP 14, RFC 2119, March 1997. 2534 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2535 "Structure of Management Information Version 2 (SMIv2)", 2536 STD 58, RFC 2578, April 1999. 2538 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2539 "Textual Conventions for SMIv2", STD 58, RFC 2579, April 2540 1999. 2542 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2543 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2544 April 1999. 2546 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 2547 Label Switching Architecture", RFC 3031, January 2001. 2549 [RFC3289] Baker, F., Chan, K., and A. Smith, "Management 2550 Information Base for the Differentiated Services 2551 Architecture", RFC 3289, May 2002. 2553 16.2. Informative References 2555 [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction 2556 and Applicability Statement for Internet Standard 2557 Management Framework", RFC 3410, December 2002. 2559 [RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of 2560 Textual Conventions (TCs) for Multiprotocol Label 2561 Switching (MPLS) Management", RFC 3811, June 2004. 2563 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 2564 "Multiprotocol Label Switching (MPLS) Traffic Engineering 2565 (TE) Management Information Base (MIB)", RFC 3812, June 2566 2004. 2568 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 2569 "Multiprotocol Label Switching (MPLS) Label Switching 2570 (LSR) Router Management Information Base (MIB)", RFC 3813, 2571 June 2004. 2573 [RFC4221] Nadeau, T., Srinivasan, C., and A. Farrel, "MSMGMT Label 2574 Switching (MPLS) Management Overview", RFC 4221, November 2575 2005. 2577 [RFC4802] Nadeau, T., Ed., and A. Farrel, Ed., "Generalized 2578 Multiprotocol Label Switching (GMPLS) Traffic Engineering 2579 Management Information Base", RFC 4802, February 2007. 2581 [RFC5226] Narten, T. and H. Alvestrand., "Guidelines for Writing an 2582 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 2583 May 2008. 2585 [RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., 2586 Ed.,Sprecher, N., and S. Ueno, "Requirements of an MPLS 2587 Transport Profile", RFC 5654, September 2009. 2589 [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport 2590 Profile (MPLS-TP) Identifiers", RFC 6370, September 2011. 2592 [RFC6639] Venkatesan, M., King, D., "Multiprotocol Label Switching 2593 Transport Profile (MPLS-TP) MIB-Based Management 2594 Overview", RFC 6639, June 2012 2596 [RFC6923] Winter, R., Gray, E., Helvoort, H., and M. Betts, "MPLS-TP 2597 Identifiers Following ITU-T Conventions", RFC 6923, May 2598 2013 2600 17. Acknowledgments 2602 The authors would like to thank Francesco Fondelli, Josh Littlefield, 2603 Agrahara Kiran Koushik, Metrri Jain, Muly Ilan, Randy Presuhn and 2604 Adrian Farrel for their valuable comments. A special thanks to Joan 2605 Cucchiara for really getting the MIB modules into shape. 2607 18. Authors' Addresses 2609 Venkatesan Mahalingam 2610 Dell Inc. 2611 5450 Great America Parkway, 2612 Santa Clara, CA 95054, USA 2613 Email: venkat.mahalingams@gmail.com 2614 Sam Aldrin 2615 Huawei Technologies 2616 2330 Central Express Way, 2617 Santa Clara, CA 95051, USA 2618 Email: aldrin.ietf@gmail.com 2620 Thomas D. Nadeau 2621 Brocade 2622 Email: tnadeau@lucidvision.com 2624 Kannan KV Sampath 2625 Redeem 2626 India 2627 Email: kannankvs@gmail.com