idnits 2.17.1 draft-ietf-mpls-tp-te-mib-06.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 (May 08, 2013) is 4005 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: November 09, 2013 Kannan KV Sampath 6 Redeem 7 Sam K. Aldrin 8 Huawei Technologies 9 Thomas D. Nadeau 10 Juniper Networks 12 May 08, 2013 14 MPLS-TP Traffic Engineering (TE) Management Information Base (MIB) 15 draft-ietf-mpls-tp-te-mib-06.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 managed objects of Tunnels, Identifiers, 22 Label Switch Router and Textual conventions for Multiprotocol Label 23 Switching (MPLS) based Transport Profile (TP). 25 Status of this Memo 27 This Internet-Draft is submitted to IETF in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF), its areas, and its working groups. Note that 32 other groups may also distribute working documents as Internet- 33 Drafts. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 The list of current Internet-Drafts can be accessed at 41 http://www.ietf.org/ietf/1id-abstracts.txt. 43 The list of Internet-Draft Shadow Directories can be accessed at 44 http://www.ietf.org/shadow.html. 46 This Internet-Draft will expire on November 09, 2013. 48 Copyright and License Notice 50 Copyright (c) 2013 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents 55 (http://trustee.ietf.org/license-info) in effect on the date of 56 publication of this document. Please review these documents 57 carefully, as they describe your rights and restrictions with respect 58 to this document. Code Components extracted from this document must 59 include Simplified BSD License text as described in Section 4.e of 60 the Trust Legal Provisions and are provided without warranty as 61 described in the Simplified BSD License. 62 Table of Contents 64 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 65 2. The Internet-Standard Management Framework . . . . . . . . . . 4 66 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 67 3.1. Conventions used in this document . . . . . . . . . . . . . 4 68 3.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4 69 3.3. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . 6 70 4. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . . 6 71 5. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 6 72 6. Brief description of MPLS-TE-EXT-STD-MIB Objects . . . . . . . 7 73 6.1. mplsTunnelExtNodeConfigTable . . . . . . . . . . . . . . . 7 74 6.2. mplsTunnelExtNodeIpMapTable . . . . . . . . . . . . . . . . 8 75 6.3. mplsTunnelExtNodeIccMapTable . . . . . . . . . . . . . . . 8 76 6.4. mplsTunnelExtTable . . . . . . . . . . . . . . . . . . . . 8 77 6.5. mplsTunnelExtReversePerfTable . . . . . . . . . . . . . . . 8 78 7. MIB Module Interdependencies . . . . . . . . . . . . . . . . . 8 79 8. Dependencies between MIB Module Tables . . . . . . . . . . . . 11 80 9.1. Example of MPLS-TP static co-routed bidirectional tunnel 81 setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 82 9.1.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 12 83 9.1.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 13 84 9.1.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 14 85 9.1.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 14 86 9.1.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 14 87 9.1.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 15 88 9.1.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 15 89 9.1.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 15 90 9.1.9. mplsTunnelExtReversePerfTable . . . . . . . . . . . . . 15 91 9.2. Example of MPLS-TP static associated bidirectional tunnel 92 setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 93 9.2.1. Forward direction mplsTunnelEntry . . . . . . . . . . . 16 94 9.2.2. Forward direction mplsTunnelExtEntry . . . . . . . . . 17 95 9.2.3. Forward direction mplsOutSegmentTable . . . . . . . . . 17 96 9.2.4. Forward direction mplsXCEntry . . . . . . . . . . . . . 17 97 9.2.5. Forward direction mplsXCExtEntry . . . . . . . . . . . 18 98 9.2.6. Reverse direction mplsTunnelEntry . . . . . . . . . . . 18 99 9.2.7. Reverse direction mplsTunnelExtEntry . . . . . . . . . 19 100 9.2.8. Reverse direction mplsInSegmentEntry . . . . . . . . . 19 101 9.2.9. Reverse direction mplsXCEntry . . . . . . . . . . . . . 19 102 9.2.10. Reverse direction mplsXCExtEntry . . . . . . . . . . . 20 103 9.3.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 20 104 9.3.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 21 105 9.3.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 21 106 9.3.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 21 107 9.3.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 22 108 9.3.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 22 109 9.3.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 22 110 9.3.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 22 111 9.3.9. mplsTunnelExtReversePerfTable . . . . . . . . . . . . . 22 112 11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 25 113 12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 30 114 13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 35 115 14. Security Consideration . . . . . . . . . . . . . . . . . . . . 53 116 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55 117 15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB . . . . . . . 55 118 15.2. IANA Considerations for MPLS-ID-STD-MIB . . . . . . . . . 55 119 15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB . . . . . . . 55 120 15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB . . . . . . . 55 121 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 55 122 16.1. Normative References . . . . . . . . . . . . . . . . . . . 55 123 16.2. Informative References . . . . . . . . . . . . . . . . . 56 124 17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 57 125 18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 57 127 1. Introduction 129 This memo defines a portion of the Management Information Base (MIB) for 130 use with network management protocols in the Internet community. In 131 particular, it describes managed objects of Tunnels, Identifiers, Label 132 Switch Router and Textual conventions for Multiprotocol Label Switching 133 (MPLS) based Transport Profile (TP). These MIB modules extend the 134 existing MPLS MIB objects for both MPLS-TP and Non-MPLS-TP operations, 135 so the MPLS-TP name is not included in the MIB module name. 137 The existing Multiprotocol Label Switching (MPLS) Traffic Engineering 138 (TE) Management Information Base (MIB) [RFC3812] and Generalized 139 Multiprotocol Label Switching (GMPLS) Traffic Engineering Management 140 Information Base [RFC4802] do not support the transport network 141 requirements of NON-IP based management and static bidirectional 142 tunnels. These MIB modules should be used in conjunction with [RFC3812] 143 and companion document [RFC3813] for MPLS-TP tunnel configuration and 144 management. 146 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 147 "SHOULD", "SHOULD NOT", "MAY", and "OPTIONAL" in this document are to be 148 interpreted as described in BCP 14, RFC2119. 150 2. The Internet-Standard Management Framework 152 For a detailed overview of the documents that describe the current 153 Internet-Standard Management Framework, please refer to section 7 of 154 RFC3410 [RFC3410]. 156 Managed objects are accessed via a virtual information store, termed the 157 Management Information Base or MIB. MIB objects are generally accessed 158 through the Simple Network Management Protocol (SNMP). Objects in the 159 MIB are defined using the mechanisms defined in the Structure of 160 Management Information (SMI). This memo specifies a MIB module that is 161 compliant to the SMIv2, which is described in STD 58, RFC2578, STD 58, 162 RFC2579 and STD58, RFC2580. 164 3. Overview 166 3.1. Conventions used in this document 168 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 169 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 170 document are to be interpreted as described in [RFC2119]. 172 3.2. Terminology 173 This document uses terminology from the Multiprotocol Label Switching 174 Architecture [RFC3031], Multiprotocol Label Switching (MPLS) Traffic 175 Engineering (TE) Management Information Base (MIB) [RFC3812], 176 Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) 177 Management Information Base (MIB) [RFC3813] and MPLS Transport Profile 178 (MPLS-TP) Identifiers [RFC6370]. 180 3.3. Acronyms 182 GMPLS: Generalized Multi-Protocol Label Switching 183 ICC: ITU Carrier Code 184 IP: Internet Protocol 185 LSP: Label Switching Path 186 LSR: Label Switching Router 187 MIB: Management Information Base 188 MPLS: Multi-Protocol Label Switching 189 MPLS-TP: MPLS Transport Profile 190 OSPF: Open Shortest Path First 191 PW: Pseudowire 192 TE: Traffic Engineering 193 TP: Transport Profile 195 4. Motivations 197 Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management 198 Information Base (MIB) [RFC3812] provides support for Traffic 199 Engineering tunnels. However, with MPLS-TP, the characteristics of 200 Tunnels were enhanced. For example, MPLS-TP tunnels are bidirectional in 201 nature and could be used in non-IP environments. As the existing MPLS- 202 TE-STD-MIB is not sufficient to capture all the characteristics of the 203 tunnels, enhancing the MIB to support MPLS TP tunnels is required. As 204 most of the attributes of MPLS Traffic Engineering tunnels are also 205 applicable to MPLS-TP tunnels, it is optimal to re-use the existing MIB 206 definition instead of a new MIB. 208 This document defines four MIB modules, namely MPLS-TE-EXT-STD-MIB, 209 MPLS-TC-EXT-STD-MIB, MPLS-ID-STD-MIB and MPLS-LSR-EXT-STD-MIB. As these 210 new MIB modules are small in size, these new MIB modules are retained in 211 the same document, instead of a separate document. 213 5. Feature List 215 The MPLS-TE-EXT-STD-MIB is designed to satisfy the following 216 requirements and constraints: 218 The MIB module supports static and signaling point-to-point, co-routed 219 bi-directional and associated bi-directional tunnels. 221 - The MPLS tunnels need not be interfaces, but it is possible 222 to configure a TP tunnel as an interface. 224 - The mplsTunnelTable [RFC3812] to be also used for MPLS-TP 225 tunnels 227 - The mplsTunnelTable is extended to support MPLS-TP specific 228 objects. 230 - A node configuration table (mplsTunnelExtNodeConfigTable) 231 is used to translate the Global_ID::Node_ID or CC::ICC to 232 the local identifier in order to index mplsTunnelTable. 234 - The MIB module supports persistent, as well as non-persistent 235 tunnels. 237 6. Brief description of MPLS-TE-EXT-STD-MIB Objects 239 The objects described in this section support the functionality 240 described in documents [RFC5654] and [RFC6370]. The tables support 241 both IP compatible and ICC based tunnel configurations. 243 6.1. mplsTunnelExtNodeConfigTable 245 The mplsTunnelExtNodeConfigTable is used to assign a local identifier 246 for a given CC::ICC or Global_ID::Node_ID combination as defined in 247 [I-D.ietf-mpls-tp-itu-t-identifiers] and [RFC6370] respectively. 248 The CC is a string of two alphabetic characters represented with 249 upper case letters (i.e., A-Z). The ICC is a string of one to six 250 characters, each character being either alphabetic (i.e. A-Z) 251 or numeric (i.e. 0-9) characters. Alphabetic characters in the ICC 252 should be represented with upper case letters. In the IP compatible 253 mode, Global_ID::Node_ID, is used to uniquely identify a node. 255 Each CC::ICC or Global_ID::Node_ID contains one unique entry in the 256 table representing a node. Every node is assigned a local identifier 257 within a range of 0 to 16777215. This local identifier is used for 258 indexing into mplsTunnelTable as mplsTunnelIngressLSRId and 259 mplsTunnelEgressLSRId. 261 For IP compatible environment, MPLS-TP tunnel is indexed by Tunnel 262 Index, Tunnel Instance, Source Global_ID, Source Node_ID, Destination 263 Global_ID and Destination Node_ID. 265 For ICC based environment, MPLS-TP tunnel is indexed by Tunnel Index, 266 Tunnel Instance, Source CC, Source ICC, Destination CC and 267 Destination ICC. 269 As mplsTunnelTable is indexed by mplsTunnelIndex, 270 mplsTunnelInstance, mplsTunnelIngressLSRId, and 271 mplsTunnelEgressLSRId, the MPLS-TP tunnel identifiers cannot be 272 used directly. 274 The mplsTunnelExtNodeConfigTable will be used to store an entry for 275 CC::ICC or Global_ID::Node_ID with a local identifier to be used as 276 LSR ID in mplsTunnelTable. As the regular TE tunnels use IP address 277 as LSR ID, the local identifier should be below the first valid IP 278 address, which is 16777216[1.0.0.0]. 280 6.2. mplsTunnelExtNodeIpMapTable 282 The read-only mplsTunnelExtNodeIpMaptable is used to query the local 283 identifier assigned and stored in mplsTunnelExtNodeConfigTable for 284 a given Global_ID::Node_ID. In order to query the local identifier, 285 in the IP compatible mode, this table is indexed with 286 Global_ID::Node_ID. In the IP compatible mode for a TP tunnel, 287 Global_ID::Node_ID is used. 289 A separate query is made to get the local identifier of both 290 Ingress and Egress Global_ID::Node_ID identifiers. These local 291 identifiers are used as mplsTunnelIngressLSRId and 292 mplsTunnelEgressLSRId, while indexing mplsTunnelTable. 294 6.3. mplsTunnelExtNodeIccMapTable 296 The read-only mplsTunnelExtNodeIccMapTable is used to query the local 297 identifier assigned and stored in the mplsTunnelExtNodeConfigTable 298 for a given CC::ICC. 300 A separate query is made to get the local identifier of both 301 Ingress and Egress CC::ICC. These local identifiers are used as 302 mplsTunnelIngressLSRId and mplsTunnelEgressLSRId, 303 while indexing mplsTunnelTable. 305 6.4. mplsTunnelExtTable 307 mplsTunnelExtTable extends the mplsTunnelTable in order to support 308 MPLS-TP tunnels with additional objects. All the additional 309 attributes specific to supporting TP tunnel are contained in this 310 extended table and could be accessed with the mplsTunnelTable 311 indices. 313 6.5. mplsTunnelExtReversePerfTable 315 This table sparse augments the mplsTunnelTable to provide per-tunnel 316 packet performance information for the reverse direction of a 317 bidirectional tunnel. It can be seen as supplementing the 318 mplsTunnelPerfTable, which augments the mplsTunnelTable. 320 7. MIB Module Interdependencies 321 This section provides an overview of the relationship between the 322 MPLS-TP TE MIB module and other MPLS MIB modules. 324 The arrows in the following diagram show a 'depends on' 325 relationship. A relationship "MIB module A depends on MIB module B" 326 means that MIB module A uses an object, object identifier, or 327 textual convention defined in MIB module B, or that MIB module A 328 contains a pointer (index or RowPointer) to an object in 329 MIB module B. 331 MPLS-TC-EXT-STD-MIB 332 ^ 333 | 334 | 335 +<---- MPLS-ID-STD-MIB 336 ^ 337 | | 338 +<---- MPLS-TE-EXT-STD-MIB 339 | | 340 | V 341 | MPLS-TE-STD-MIB 342 | | 343 | | 344 | V 345 | MPLS-LSR-STD-MIB 346 | ^ 347 | | 348 | | 349 +------MPLS-LSR-EXT-STD-MIB 351 Thus: 353 - All the new MPLS extension MIB modules depend on 354 MPLS-TC-EXT-STD-MIB. 356 - MPLS-ID-STD-MIB contains references to objects in 357 MPLS-TE-STD-MIB [RFC3812]. 359 - MPLS-TE-EXT-STD-MIB contains references to objects in 360 MPLS-TE-STD-MIB [RFC3812]. 362 - MPLS-LSR-EXT-STD-MIB contains references to objects in 363 MPLS-LSR-STD-MIB [RFC3813]. 365 MPLS-TE-STD-MIB [RFC3812] is extended by MPLS-TE-EXT-STD-MIB 366 MIB module for associating the reverse direction tunnel 367 information. 369 Note that the nature of the 'extends' relationship 370 is a sparse augmentation so that the entry in the 371 mplsTunnelExtTable has the same index values as the in the 372 mplsTunnelTable. 374 MPLS-LSR-STD-MIB [RFC3813] is extended by MPLS-LSR-EXT-STD-MIB 375 MIB module for pointing back to the tunnel entry for easy tunnel 376 access from XC entry. 378 Note that the nature of the 'extends' relationship 379 is a sparse augmentation so that the entry in the 380 mplsXCExtTable has the same index values as the in the mplsXCTable. 382 8. Dependencies between MIB Module Tables 384 The tables in MPLS-TE-EXT-STD-MIB are related as shown on the diagram 385 below. The arrows indicate a reference from one table to another. 387 mplsTunnelExtNodeConfigTable 388 ^ mplsXCExtTable 389 | | ^ 390 | +---------+ | 391 | | | 392 | V V 393 mplsTunnelTable ---->mplsXCTable 394 ^ 395 | 396 | 397 mplsTunnelExtTable 399 An existing mplsTunnelTable uses the mplsTunnelExtNodeConfigTable 400 table to map the Global_ID::Node_ID and/or CC::ICC with the local 401 number in order to accommodate in the existing tunnel table's 402 ingress/egress LSR-id. 404 New mplsTunnelExtTable table provides the reverse direction LSP 405 information for the existing tunnel table in order to achieve 406 bidirectional LSPs. 408 mplsXCExtTable is extended from mplsLsrXCTable to provide 409 backward reference to tunnel entry. 411 9. Example of MPLS-TP Tunnel Setup 412 In this section, we provide an example of the IP based MPLS-TP 413 bidirectional tunnel setup. This example provides the usage of 414 MPLS-TP Tunnel MIB along with the extended new MIB modules introduced 415 in this document. 417 Do note that a MPLS-TP tunnel could be setup statically as well as 418 signaled via control plane. This example considers accessing MIB 419 objects on a head-end for a static and signaling MPLS-TP tunnels. 420 Only relevant objects which are applicable for MPLS-TP tunnel are 421 illustrated here. 423 In mplsTunnelExtNodeConfigTable: 425 { 426 -- Non-IP Ingress LSR-Id (Index to the table) 427 mplsTunnelExtNodeConfigLocalId = 1, 429 mplsTunnelExtNodeConfigGlobalId = 1234, 430 mplsTunnelExtNodeConfigNodeId = 10, 431 -- Mandatory parameters needed to activate the row go here 432 mplsTunnelExtNodeConfigRowStatus = createAndGo (4) 434 -- Non-IP Egress LSR-Id (Index to the table) 435 mplsTunnelExtNodeConfigLocalId = 2, 436 mplsTunnelExtNodeConfigGlobalId = 1234, 437 mplsTunnelExtNodeConfigNodeId = 20, 438 -- Mandatory parameters needed to activate the row go here 439 mplsTunnelExtNodeConfigRowStatus = createAndGo (4) 440 } 442 This will create an entry in the mplsTunnelExtNodeConfigTable for a 443 Global_ID::Node_ID. A separate entry is made for both Ingress LSR 444 and Egress LSR. 446 The following read-only mplsTunnelExtNodeIpMapTable table is 447 populated automatically upon creating an entry in 448 mplsTunnelExtNodeConfigTable and this table is used to retrieve 449 the local identifier for the given Global_ID::Node_ID. 451 In mplsTunnelExtNodeIpMapTable: 453 { 454 -- Global_ID (Index to the table) 455 mplsTunnelExtNodeIpMapGlobalId = 1234, 456 -- Node Identifier (Index to the table) 457 mplsTunnelExtNodeIpMapNodeId = 10, 458 mplsTunnelExtNodeIpMapLocalId = 1 460 -- Global_ID (Index to the table) 461 mplsTunnelExtNodeIpMapGlobalId = 1234, 462 -- Node Identifier (Index to the table) 463 mplsTunnelExtNodeIpMapNodeId = 20, 464 mplsTunnelExtNodeIpMapLocalId = 2 465 } 467 9.1. Example of MPLS-TP static co-routed bidirectional tunnel setup 469 The following denotes the configured co-routed bidirectional 470 tunnel "head" entry: 472 9.1.1. mplsTunnelEntry 474 In mplsTunnelTable: 476 { 477 mplsTunnelIndex = 1, 478 mplsTunnelInstance = 1, 479 -- Local map number created in mplsTunnelExtNodeConfigTable for 480 -- Ingress LSR-Id 481 mplsTunnelIngressLSRId = 1, 483 -- Local map number created in mplsTunnelExtNodeConfigTable for 484 -- Egress LSR-Id 485 mplsTunnelEgressLSRId = 2, 486 mplsTunnelName = "TP co-routed bidirectional LSP", 487 mplsTunnelDescr = "East to West", 488 mplsTunnelIsIf = true (1), 489 -- RowPointer MUST point to the first accessible column 490 mplsTunnelXCPointer = 491 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1, 492 mplsTunnelSignallingProto = none (1), 493 mplsTunnelSetupPrio = 0, 494 mplsTunnelHoldingPrio = 0, 495 mplsTunnelSessionAttributes = 0, 496 mplsTunnelLocalProtectInUse = false (0), 497 -- RowPointer MUST point to the first accessible column 498 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 499 mplsTunnelInstancePriority = 1, 500 mplsTunnelHopTableIndex = 1, 501 mplsTunnelIncludeAnyAffinity = 0, 502 mplsTunnelIncludeAllAffinity = 0, 503 mplsTunnelExcludeAnyAffinity = 0, 504 mplsTunnelRole = head (1), 505 -- Mandatory parameters needed to activate the row go here 506 mplsTunnelRowStatus = createAndGo (4) 507 } 509 9.1.2. mplsTunnelExtEntry 511 -- An MPLS extension table 512 In mplsTunnelExtTable: 513 { 514 -- This opposite direction tunnel pointer MAY be point to 0.0 515 -- if co-routed bidirectional tunnel is managed by single tunnel 516 -- entry 517 mplsTunnelExtOppositeDirTnlPtr = 0.0 518 -- Set both the Ingress and Egress LocalId objects to TRUE as 519 -- this tunnel entry uses the local identifiers. 520 mplsTunnelExtIngressLSRLocalIdValid = true, 521 mplsTunnelExtEgressLSRLocalIdValid = true 523 } 524 We must next create the appropriate in-segment and out-segment 525 entries. These are done in [RFC3813] using the mplsInSegmentTable and 526 mplsOutSegmentTable. 528 9.1.3. Forward direction mplsOutSegmentEntry 530 For the forward direction. 532 In mplsOutSegmentTable: 533 { 534 mplsOutSegmentIndex = 0x0000001, 535 mplsOutSegmentInterface = 13, -- outgoing interface 536 mplsOutSegmentPushTopLabel = true(1), 537 mplsOutSegmentTopLabel = 22, -- outgoing label 539 -- RowPointer MUST point to the first accessible column. 540 mplsOutSegmentTrafficParamPtr = 0.0, 541 mplsOutSegmentRowStatus = createAndGo (4) 542 } 544 9.1.4. Reverse direction mplsInSegmentEntry 546 For the reverse direction. 548 In mplsInSegmentTable: 549 { 550 mplsInSegmentIndex = 0x0000001 551 mplsInSegmentLabel = 21, -- incoming label 552 mplsInSegmentNPop = 1, 553 mplsInSegmentInterface = 13, -- incoming interface 555 -- RowPointer MUST point to the first accessible column. 556 mplsInSegmentTrafficParamPtr = 0.0, 557 mplsInSegmentRowStatus = createAndGo (4) 558 } 560 Next, two cross-connect entries are created in the mplsXCTable of the 561 MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created 562 segments together. 564 9.1.5. Forward direction mplsXCEntry 566 In mplsXCTable: 567 { 568 mplsXCIndex = 0x01, 569 mplsXCInSegmentIndex = 0x00000000, 570 mplsXCOutSegmentIndex = 0x00000001, 571 mplsXCLspId = 0x0102 -- unique ID 572 -- only a single outgoing label 573 mplsXCLabelStackIndex = 0x00, 574 mplsXCRowStatus = createAndGo(4) 576 } 578 9.1.6. Reverse direction mplsXCEntry 580 In mplsXCTable: 581 { 582 mplsXCIndex = 0x01, 583 mplsXCInSegmentIndex = 0x00000001, 584 mplsXCOutSegmentIndex = 0x00000000, 585 mplsXCLspId = 0x0102 -- unique ID 586 -- only a single outgoing label 587 mplsXCLabelStackIndex = 0x00, 588 mplsXCRowStatus = createAndGo(4) 589 } 591 This table entry is extended by entry in the 592 mplsXCExtTable. Note that the nature of the 'extends' 593 relationship is a sparse augmentation so that the entry in the 594 mplsXCExtTable has the same index values as the entry in 595 the mplsXCTable. 597 9.1.7. Forward direction mplsXCExtEntry 599 In mplsXCExtTable (0x01, 0x00000000, 0x00000001) 600 { 601 -- Back pointer from XC table to Tunnel table 602 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 603 mplsXCExtOppositeDirXCPtr = 604 mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0 605 } 607 9.1.8. Reverse direction mplsXCExtEntry 609 Next for the reverse direction: 611 In mplsXCExtTable (0x01, 0x00000001, 0x00000000) 612 { 613 -- Back pointer from XC table to Tunnel table 614 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 615 mplsXCExtOppositeDirXCPtr = 616 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1 617 } 619 9.1.9. mplsTunnelExtReversePerfTable 620 The mplsTunnelExtReversePerfTable SHOULD be populated incase 621 the single tunnel entry is used for co-routed bidirectional tunnel 622 setup. The mplsTunnelPerfTable will have the forward direction 623 LSP performance counters and mplsTunnelExtReversePerfTable will have 624 the reverse direction LSP performance counters. 626 9.2. Example of MPLS-TP static associated bidirectional tunnel setup 628 The MPLS-TP associated bidirectional tunnel has two different 629 direction tunnels[Forward and Reverse LSPs] and these are 630 associated together using mplsTunnelExtTable. Two different 631 tunnel entries for both forward and reverse direction MAY be used 632 for co-routed bidirectional tunnel as well. 634 The following denotes the configured associated bidirectional forward 635 tunnel "head" entry: 637 9.2.1. Forward direction mplsTunnelEntry 639 In mplsTunnelTable: 641 { 642 mplsTunnelIndex = 1, 643 mplsTunnelInstance = 1, 644 -- Local map number created in mplsTunnelExtNodeConfigTable for 645 -- Ingress LSR-Id 646 mplsTunnelIngressLSRId = 1, 648 -- Local map number created in mplsTunnelExtNodeConfigTable for 649 -- Egress LSR-Id 650 mplsTunnelEgressLSRId = 2, 651 mplsTunnelName = "TP associated bi-directional 652 forward LSP", 653 mplsTunnelDescr = "East to West", 654 mplsTunnelIsIf = true (1), 655 -- RowPointer MUST point to the first accessible column 656 mplsTunnelXCPointer = 657 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1, 658 mplsTunnelSignallingProto = none (1), 659 mplsTunnelSetupPrio = 0, 660 mplsTunnelHoldingPrio = 0, 661 mplsTunnelSessionAttributes = 0, 662 mplsTunnelLocalProtectInUse = false (0), 663 -- RowPointer MUST point to the first accessible column 664 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 665 mplsTunnelInstancePriority = 1, 666 mplsTunnelHopTableIndex = 1, 667 mplsTunnelIncludeAnyAffinity = 0, 668 mplsTunnelIncludeAllAffinity = 0, 669 mplsTunnelExcludeAnyAffinity = 0, 670 mplsTunnelRole = head (1), 671 -- Mandatory parameters needed to activate the row go here 672 mplsTunnelRowStatus = createAndGo (4) 673 } 675 9.2.2. Forward direction mplsTunnelExtEntry 677 For Associated bidirectional forward LSP, 678 In mplsTunnelExtTable: 679 { 680 mplsTunnelExtOppositeDirPtr = mplsTunnelName.2.1.2.1 681 -- Set both the Ingress and Egress LocalId objects to TRUE as 682 -- this tunnel entry uses the local identifiers. 683 mplsTunnelExtIngressLSRLocalIdValid = true, 684 mplsTunnelExtEgressLSRLocalIdValid = true 685 } 687 9.2.3. Forward direction mplsOutSegmentTable 689 For the forward direction. 691 In mplsOutSegmentTable: 692 { 693 mplsOutSegmentIndex = 0x0000001, 694 mplsOutSegmentInterface = 13, -- outgoing interface 695 mplsOutSegmentPushTopLabel = true(1), 696 mplsOutSegmentTopLabel = 22, -- outgoing label 698 -- RowPointer MUST point to the first accessible column. 699 mplsOutSegmentTrafficParamPtr = 0.0, 700 mplsOutSegmentRowStatus = createAndGo (4) 701 } 703 9.2.4. Forward direction mplsXCEntry 705 In mplsXCTable: 706 { 707 mplsXCIndex = 0x01, 708 mplsXCInSegmentIndex = 0x00000000, 709 mplsXCOutSegmentIndex = 0x00000001, 710 mplsXCLspId = 0x0102 -- unique ID 711 -- only a single outgoing label 712 mplsXCLabelStackIndex = 0x00, 713 mplsXCRowStatus = createAndGo(4) 715 } 717 9.2.5. Forward direction mplsXCExtEntry 719 In mplsXCExtTable (0x01, 0x00000000, 0x00000001) 720 { 721 -- Back pointer from XC table to Tunnel table 722 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 723 mplsXCExtOppositeDirXCPtr = 724 mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0 725 } 727 9.2.6. Reverse direction mplsTunnelEntry 729 The following denotes the configured associated bidirectional reverse 730 tunnel "tail" entry: 732 In mplsTunnelTable: 734 { 735 mplsTunnelIndex = 2, 736 mplsTunnelInstance = 1, 737 -- Local map number created in mplsTunnelExtNodeConfigTable for 738 -- Ingress LSR-Id 739 mplsTunnelIngressLSRId = 2, 740 -- Local map number created in mplsTunnelExtNodeConfigTable for 741 -- Egress LSR-Id 742 mplsTunnelEgressLSRId = 1, 743 mplsTunnelName = "TP associated bi-directional 744 reverse LSP", 745 mplsTunnelDescr = "West to East", 746 mplsTunnelIsIf = true (1), 747 -- RowPointer MUST point to the first accessible column 748 mplsTunnelXCPointer = 749 mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0, 750 mplsTunnelSignallingProto = none (1), 751 mplsTunnelSetupPrio = 0, 752 mplsTunnelHoldingPrio = 0, 753 mplsTunnelSessionAttributes = 0, 754 mplsTunnelLocalProtectInUse = false (0), 756 -- RowPointer MUST point to the first accessible column 757 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 758 mplsTunnelInstancePriority = 1, 759 mplsTunnelHopTableIndex = 1, 760 mplsTunnelIncludeAnyAffinity = 0, 761 mplsTunnelIncludeAllAffinity = 0, 762 mplsTunnelExcludeAnyAffinity = 0, 763 mplsTunnelRole = head (1), 764 -- Mandatory parameters needed to activate the row go here 765 mplsTunnelRowStatus = createAndGo (4) 766 } 768 9.2.7. Reverse direction mplsTunnelExtEntry 770 For Associated bidirectional reverse LSP, 771 In mplsTunnelExtTable: 772 { 773 mplsTunnelExtOppositeDirPtr = mplsTunnelName.1.1.1.2 774 -- Set both the Ingress and Egress LocalId objects to TRUE as 775 -- this tunnel entry uses the local identifiers. 776 mplsTunnelExtIngressLSRLocalIdValid = true, 777 mplsTunnelExtEgressLSRLocalIdValid = true 778 } 780 9.2.8. Reverse direction mplsInSegmentEntry 782 We must next create the appropriate in-segment and out-segment 783 entries. These are done in [RFC3813] using the mplsInSegmentTable and 784 mplsOutSegmentTable. 786 In mplsInSegmentTable: 787 { 788 mplsInSegmentIndex = 0x0000001 789 mplsInSegmentLabel = 21, -- incoming label 790 mplsInSegmentNPop = 1, 791 mplsInSegmentInterface = 13, -- incoming interface 793 -- RowPointer MUST point to the first accessible column. 794 mplsInSegmentTrafficParamPtr = 0.0, 795 mplsInSegmentRowStatus = createAndGo (4) 796 } 798 Next, two cross-connect entries are created in the mplsXCTable of the 799 MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created 800 segments together. 802 9.2.9. Reverse direction mplsXCEntry 804 In mplsXCTable: 805 { 806 mplsXCIndex = 0x01, 807 mplsXCInSegmentIndex = 0x00000001, 808 mplsXCOutSegmentIndex = 0x00000000, 809 mplsXCLspId = 0x0102 -- unique ID 810 -- only a single outgoing label 811 mplsXCLabelStackIndex = 0x00, 812 mplsXCRowStatus = createAndGo(4) 813 } 815 This table entry is extended by entry in the 816 mplsXCExtTable. Note that the nature of the 'extends' 817 relationship is a sparse augmentation so that the entry in the 818 mplsXCExtTable has the same index values as the entry in 819 the mplsXCTable. 821 9.2.10. Reverse direction mplsXCExtEntry 823 Next for the reverse direction: 825 In mplsXCExtTable (0x01, 0x00000001, 0x00000000) 826 { 827 -- Back pointer from XC table to Tunnel table 828 mplsXCExtTunnelPointer = mplsTunnelName.2.1.2.1 829 mplsXCExtOppositeDirXCPtr = 830 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1 831 } 833 9.3. Example of MPLS-TP signaling co-routed bidirectional tunnel setup 835 The following denotes the configured co-routed bidirectional 836 tunnel "head" entry and in intermediate and tail-end nodes, 837 the tunnel table and its associated tables are created 838 by the local management subsystem (e.g. agent) when the MPLS TP 839 tunnel is signaled successfully. Refer [RFC3812] and [RFC4802] 840 for signaling tunnel table configuration examples. 842 9.3.1. mplsTunnelEntry 844 In mplsTunnelTable: 846 { 847 mplsTunnelIndex = 1, 848 mplsTunnelInstance = 0, 849 -- Local map number created in mplsTunnelExtNodeConfigTable for 850 -- Ingress LSR-Id, for the intermediate and tail-end nodes, 851 -- the local management entity is expected to pick a first available 852 -- local identifier which is not used in mplsTunnelTable. 853 mplsTunnelIngressLSRId = 1, 855 -- Local map number created in mplsTunnelExtNodeConfigTable for 856 -- Egress LSR-Id 857 mplsTunnelEgressLSRId = 2, 858 mplsTunnelName = "TP co-routed bidirectional LSP", 859 mplsTunnelDescr = "East to West", 860 mplsTunnelIsIf = true (1), 862 -- RowPointer MUST point to the first accessible column 863 mplsTunnelXCPointer = 864 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1, 865 mplsTunnelSignallingProto = none (1), 866 mplsTunnelSetupPrio = 0, 867 mplsTunnelHoldingPrio = 0, 868 mplsTunnelSessionAttributes = 0, 869 mplsTunnelLocalProtectInUse = false (0), 870 -- RowPointer MUST point to the first accessible column 871 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 872 mplsTunnelInstancePriority = 1, 873 mplsTunnelHopTableIndex = 1, 874 mplsTunnelIncludeAnyAffinity = 0, 875 mplsTunnelIncludeAllAffinity = 0, 876 mplsTunnelExcludeAnyAffinity = 0, 877 mplsTunnelRole = head (1), 878 -- Mandatory parameters needed to activate the row go here 879 mplsTunnelRowStatus = createAndGo (4) 880 } 882 9.3.2. mplsTunnelExtEntry 884 -- An MPLS extension table 885 In mplsTunnelExtTable: 886 { 887 -- This opposite direction tunnel pointer MAY be point to 0.0 888 -- if co-routed bidirectional tunnel is managed by single tunnel 889 -- entry 890 mplsTunnelExtOppositeDirTnlPtr = 0.0 891 -- Set both the Ingress and Egress LocalId objects to TRUE as 892 -- this tunnel entry uses the local identifiers. 893 mplsTunnelExtIngressLSRLocalIdValid = true, 894 mplsTunnelExtEgressLSRLocalIdValid = true 895 } 897 We must next create the appropriate in-segment and out-segment 898 entries. These are done in [RFC3813] using the mplsInSegmentTable and 899 mplsOutSegmentTable. 901 9.3.3. Forward direction mplsOutSegmentEntry 903 The forward direction mplsOutSegmentTable will be populated 904 automatically based on the information received from the signaling 905 protocol. 907 9.3.4. Reverse direction mplsInSegmentEntry 908 The reverse direction mplsOutSegmentTable will be populated 909 automatically based on the information received from the signaling 910 protocol. 912 Next, two cross-connect entries are created in the mplsXCTable of the 913 MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created 914 segments together. 916 9.3.5. Forward direction mplsXCEntry 918 The forward direction mplsXCEntry will be populated as soon as the 919 forward path label information is available. 921 9.3.6. Reverse direction mplsXCEntry 923 The reverse direction mplsXCEntry will be populated as soon as the 924 reverse path label information is available. 926 This table entry is extended by entry in the mplsXCExtTable. Note 927 that the nature of the 'extends' relationship is a sparse 928 augmentation so that the entry in the mplsXCExtTable has the same 929 index values as the entry in the mplsXCTable. 931 9.3.7. Forward direction mplsXCExtEntry 933 Once the forward path information is negotiated using signaling 934 protocol, the forward direction mplsXCExtEntry will be created for 935 associating the opposite direction XC entry and tunnel table entry. 937 9.3.8. Reverse direction mplsXCExtEntry 939 Once the reverse path information is negotiated using signaling 940 protocol, the reverse direction mplsXCExtEntry will be created for 941 associating the opposite direction XC entry and tunnel table entry. 943 9.3.9. mplsTunnelExtReversePerfTable 945 The mplsTunnelExtReversePerfTable SHOULD be populated incase the 946 single tunnel entry is used for co-routed bidirectional tunnel setup. 947 The mplsTunnelPerfTable will have the forward direction LSP 948 performance counters and mplsTunnelExtReversePerfTable will have the 949 reverse direction LSP performance counters. 951 10. MPLS Textual Convention Extension MIB definitions 952 MPLS-TC-EXT-STD-MIB DEFINITIONS ::= BEGIN 954 IMPORTS 955 MODULE-IDENTITY, Unsigned32 956 FROM SNMPv2-SMI -- [RFC2578] 958 TEXTUAL-CONVENTION 959 FROM SNMPv2-TC -- [RFC2579] 961 mplsStdMIB 962 FROM MPLS-TC-STD-MIB -- [RFC3811] 964 ; 966 mplsTcExtStdMIB MODULE-IDENTITY 968 LAST-UPDATED 969 "201304130000Z" -- April 13, 2013 970 ORGANIZATION 971 "Multiprotocol Label Switching (MPLS) Working Group" 972 CONTACT-INFO 973 " 974 Venkatesan Mahalingam 975 Dell Inc, 976 350 Holger way, San Jose, CA, USA 977 Email: venkat.mahalingams@gmail.com 979 Kannan KV Sampath 980 Redeem, 981 India 982 Email: kannankvs@gmail.com 984 Sam Aldrin 985 Huawei Technologies 986 2330 Central Express Way, 987 Santa Clara, CA 95051, USA 988 Email: aldrin.ietf@gmail.com 990 Thomas D. Nadeau 991 Juniper Networks 992 10 Technology Park Drive, 993 Westford, MA 01886 994 Email: tnadeau@juniper.net 995 " 996 DESCRIPTION 997 "Copyright (c) 2013 IETF Trust and the persons identified 998 as the document authors. All rights reserved. 1000 This MIB module contains Textual Conventions for 1001 LSPs and PWs of MPLS based transport networks." 1003 -- Revision history. 1005 REVISION 1007 "201304130000Z" -- April 13, 2013 1008 DESCRIPTION 1009 "MPLS Textual Convention Extensions" 1011 ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value 1013 MplsGlobalId ::= TEXTUAL-CONVENTION 1015 STATUS current 1016 DESCRIPTION 1017 "This object contains the Textual Convention of IP based 1018 operator unique identifier (Global_ID), the Global_ID can 1019 contain the 2-octet or 4-octet value of the operator's 1020 Autonomous System Number (ASN). 1022 It is expected that the Global_ID will be derived from 1023 the globally unique ASN of the autonomous system hosting 1024 the PEs containing the actual AIIs. 1025 The presence of a Global_ID based on the operator's 1026 ASN ensures that the AII will be globally unique. 1028 When the Global_ID is derived from a 2-octet AS number, 1030 the two high-order octets of this 4-octet identifier 1031 MUST be set to zero. 1032 Further ASN 0 is reserved. A Global_ID of zero means 1033 that no Global_ID is present. Note that a Global_ID of 1034 zero is limited to entities contained within a single 1035 operator and MUST NOT be used across an NNI. 1036 A non-zero Global_ID MUST be derived from an ASN owned by 1037 the operator." 1038 REFERENCE 1039 "MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370] 1040 Section 3" 1041 SYNTAX OCTET STRING (SIZE (4)) 1043 MplsNodeId ::= TEXTUAL-CONVENTION 1044 DISPLAY-HINT "d" 1045 STATUS current 1046 DESCRIPTION 1047 "The Node_ID is assigned within the scope of the Global_ID. 1048 The value 0(or 0.0.0.0 in dotted decimal notation) is 1049 reserved and MUST NOT be used. 1051 When IPv4 addresses are in use, the value of this object 1052 can be derived from the LSR's IPv4 loop back address. 1053 When IPv6 addresses are in use, the value of this object 1054 can be a 32-bit value unique within the scope of 1055 a Global_ID. 1057 Note that, when IP reach ability is not needed, the 32-bit 1058 Node_ID is not required to have any association 1059 with the IPv4 address space." 1060 REFERENCE 1061 "MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370] 1062 Section 4" 1063 SYNTAX Unsigned32 (0|1..4294967295) 1065 MplsCcId ::= TEXTUAL-CONVENTION 1066 STATUS current 1067 DESCRIPTION 1068 "The CC (Country Code) is a string of two alphabetic 1069 characters represented with upper case 1070 letters (i.e., A-Z)." 1071 REFERENCE 1072 "MPLS-TP Identifiers Following ITU-T Conventions, 1073 draft-ietf-mpls-tp-itu-t-identifiers-08 (work in 1074 progress), February 2013. Section 3" 1075 SYNTAX OCTET STRING (SIZE (2)) 1077 MplsIccId ::= TEXTUAL-CONVENTION 1078 STATUS current 1079 DESCRIPTION 1080 "The ICC is a string of one to six characters, each 1081 character being either alphabetic (i.e. A-Z) or 1082 numeric (i.e. 0-9) characters. 1083 Alphabetic characters in the ICC SHOULD be represented 1084 with upper case letters. The ICC string should be assigned 1085 to zero if the ICC identifier is invalid." 1086 REFERENCE 1087 "MPLS-TP Identifiers Following ITU-T Conventions, 1088 draft-ietf-mpls-tp-itu-t-identifiers-08 (work in 1089 progress), February 2013. Section 3" 1090 SYNTAX OCTET STRING (SIZE (0..6)) 1092 -- MPLS-TC-EXT-STD-MIB module ends 1093 END 1095 11. MPLS Identifier MIB definitions 1097 MPLS-ID-STD-MIB DEFINITIONS ::= BEGIN 1098 IMPORTS 1099 MODULE-IDENTITY, OBJECT-TYPE 1100 FROM SNMPv2-SMI -- [RFC2578] 1101 MODULE-COMPLIANCE, OBJECT-GROUP 1102 FROM SNMPv2-CONF -- [RFC2580] 1103 mplsStdMIB 1104 FROM MPLS-TC-STD-MIB -- [RFC3811] 1105 MplsGlobalId, MplsCcId, MplsIccId, MplsNodeId 1106 FROM MPLS-TC-EXT-STD-MIB 1107 ; 1109 mplsIdStdMIB MODULE-IDENTITY 1110 LAST-UPDATED 1111 "201304130000Z" -- April 13, 2013 1112 ORGANIZATION 1113 "Multiprotocol Label Switching (MPLS) Working Group" 1115 CONTACT-INFO 1116 " 1117 Venkatesan Mahalingam 1118 Dell Inc, 1119 350 Holger way, San Jose, CA, USA 1120 Email: venkat.mahalingams@gmail.com 1122 Kannan KV Sampath 1124 Redeem, 1125 India 1126 Email: kannankvs@gmail.com 1128 Sam Aldrin 1129 Huawei Technologies 1130 2330 Central Express Way, 1131 Santa Clara, CA 95051, USA 1132 Email: aldrin.ietf@gmail.com 1134 Thomas D. Nadeau 1135 Juniper Networks 1136 10 Technology Park Drive, 1137 Westford, MA 01886 1138 Email: tnadeau@juniper.net 1139 " 1140 DESCRIPTION 1141 "Copyright (c) 2013 IETF Trust and the persons identified 1142 as the document authors. All rights reserved. 1144 This MIB module contains generic object definitions for 1145 MPLS Traffic Engineering in transport networks." 1147 -- Revision history. 1149 REVISION 1150 "201304130000Z" -- April 13, 2013 1151 DESCRIPTION 1152 "This MIB modules defines the MIB objects for MPLS-TP 1153 identifiers" 1155 ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value 1157 -- tables, scalars 1158 mplsIdObjects OBJECT IDENTIFIER ::= { mplsIdStdMIB 0 } 1159 -- conformance 1160 mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 1 } 1162 -- MPLS common objects 1164 mplsIdGlobalId OBJECT-TYPE 1165 SYNTAX MplsGlobalId 1166 MAX-ACCESS read-write 1167 STATUS current 1168 DESCRIPTION 1169 "This object allows the operator to assign a unique 1170 operator identifier also called MPLS-TP Global_ID. 1171 If this value is used in mplsTunnelExtNodeConfigGlobalId 1172 for mapping Global_ID::Node_ID with the local identifier 1173 then this object value SHOULD NOT be changed." 1174 ::= { mplsIdObjects 1 } 1176 mplsIdNodeId OBJECT-TYPE 1177 SYNTAX MplsNodeId 1178 MAX-ACCESS read-write 1179 STATUS current 1180 DESCRIPTION 1181 "This object allows the operator or service provider to 1182 assign a unique MPLS-TP Node_ID. 1184 The Node_ID is assigned within the scope of 1185 the Global_ID. 1186 If this value is used in mplsTunnelExtNodeConfigNodeId 1187 for mapping Global_ID::Node_ID with the local identifier 1188 then this object value SHOULD NOT be changed." 1189 ::= { mplsIdObjects 2 } 1191 mplsIdCc OBJECT-TYPE 1192 SYNTAX MplsCcId 1193 MAX-ACCESS read-write 1194 STATUS current 1195 DESCRIPTION 1196 "This object allows the operator or service provider to 1197 assign a unique Country Code (CC). Global uniqueness is 1198 assured by concatenating the ICC with a 1199 Country Code (CC). 1200 If this value is used in mplsTunnelExtNodeConfigCcId 1201 for mapping CC:ICC with the local identifier then this 1202 object value SHOULD NOT be changed." 1203 REFERENCE 1204 "MPLS-TP Identifiers Following ITU-T Conventions, 1205 draft-ietf-mpls-tp-itu-t-identifiers-08 (work in 1206 progress), February 2013. Section 3" 1207 ::= { mplsIdObjects 3 } 1209 mplsIdIcc OBJECT-TYPE 1210 SYNTAX MplsIccId 1211 MAX-ACCESS read-write 1212 STATUS current 1213 DESCRIPTION 1214 "This object allows the operator or service provider to 1215 assign a unique MPLS-TP ITU-T Carrier Code (ICC) to a 1216 network. Together, the CC and the ICC form 1217 the ICC_Operator_ID as: CC::ICC. 1218 If this value is used in mplsTunnelExtNodeConfigIccId 1219 for mapping CC::ICC with the local identifier then 1220 this object value SHOULD NOT be changed." 1221 REFERENCE 1222 "MPLS-TP Identifiers Following ITU-T Conventions, 1223 draft-ietf-mpls-tp-itu-t-identifiers-08 (work in 1224 progress), February 2013. Section 3" 1225 ::= { mplsIdObjects 4 } 1227 -- Module compliance. 1229 mplsIdCompliances 1230 OBJECT IDENTIFIER ::= { mplsIdConformance 1 } 1232 mplsIdGroups 1233 OBJECT IDENTIFIER ::= { mplsIdConformance 2 } 1235 -- Compliance requirement for fully compliant implementations. 1237 mplsIdModuleFullCompliance MODULE-COMPLIANCE 1238 STATUS current 1239 DESCRIPTION 1240 "Compliance statement for agents that provide full 1241 support the MPLS-ID-STD-MIB module." 1243 MODULE -- this module 1245 -- The mandatory group has to be implemented by all 1246 -- LSRs that originate/terminate MPLS-TP paths. 1248 MANDATORY-GROUPS { 1249 mplsIdScalarGroup 1250 } 1252 ::= { mplsIdCompliances 1 } 1254 -- Units of conformance. 1256 mplsIdScalarGroup OBJECT-GROUP 1257 OBJECTS { mplsIdGlobalId, 1258 mplsIdNodeId, 1259 mplsIdIcc, 1260 mplsIdCc 1262 } 1263 STATUS current 1264 DESCRIPTION 1265 "Scalar object needed to implement MPLS TP path." 1266 ::= { mplsIdGroups 1 } 1268 -- MPLS-ID-STD-MIB module ends 1269 END 1271 12. MPLS LSR Extension MIB definitions 1273 MPLS-LSR-EXT-STD-MIB DEFINITIONS ::= BEGIN 1275 IMPORTS 1276 MODULE-IDENTITY, OBJECT-TYPE 1277 FROM SNMPv2-SMI -- [RFC2578] 1278 MODULE-COMPLIANCE, OBJECT-GROUP 1279 FROM SNMPv2-CONF -- [RFC2580] 1280 mplsStdMIB 1281 FROM MPLS-TC-STD-MIB -- [RFC3811] 1282 RowPointer 1283 FROM SNMPv2-TC -- [RFC2579] 1284 mplsXCIndex, mplsXCInSegmentIndex, mplsXCOutSegmentIndex, 1285 mplsInterfaceGroup, mplsInSegmentGroup, mplsOutSegmentGroup, 1286 mplsXCGroup, mplsPerfGroup, mplsLsrNotificationGroup 1287 FROM MPLS-LSR-STD-MIB; -- [RFC3813] 1289 mplsLsrExtStdMIB MODULE-IDENTITY 1290 LAST-UPDATED 1291 "201304130000Z" -- April 13, 2013 1292 ORGANIZATION 1293 "Multiprotocol Label Switching (MPLS) Working Group" 1294 CONTACT-INFO 1295 " 1296 Venkatesan Mahalingam 1297 Dell Inc, 1298 350 Holger way, San Jose, CA, USA 1299 Email: venkat.mahalingams@gmail.com 1301 Kannan KV Sampath 1302 Redeem, 1303 India 1304 Email: kannankvs@gmail.com 1306 Sam Aldrin 1307 Huawei Technologies 1308 2330 Central Express Way, 1309 Santa Clara, CA 95051, USA 1311 Email: aldrin.ietf@gmail.com 1313 Thomas D. Nadeau 1314 Juniper Networks 1315 10 Technology Park Drive, Westford, MA 01886 1316 Email: tnadeau@juniper.net 1317 " 1318 DESCRIPTION 1319 "Copyright (c) 2013 IETF Trust and the persons identified 1320 as the document authors. All rights reserved. 1322 This MIB module contains generic object definitions for 1324 MPLS LSR in transport networks." 1326 -- Revision history. 1328 REVISION 1329 "201304130000Z" -- April 13, 2013 1330 DESCRIPTION 1331 "MPLS LSR specific MIB objects extension" 1333 ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value 1335 -- tables, scalars 1336 mplsLsrExtObjects OBJECT IDENTIFIER 1337 ::= { mplsLsrExtStdMIB 0 } 1338 -- conformance 1339 mplsLsrExtConformance OBJECT IDENTIFIER 1340 ::= { mplsLsrExtStdMIB 1 } 1342 -- MPLS LSR common objects 1343 mplsXCExtTable OBJECT-TYPE 1344 SYNTAX SEQUENCE OF MplsXCExtEntry 1345 MAX-ACCESS not-accessible 1346 STATUS current 1347 DESCRIPTION 1348 "This table sparse augments the mplsXCTable of 1349 MPLS-LSR-STD-MIB [RFC3813] to provide MPLS-TP specific 1350 information about associated tunnel information" 1351 REFERENCE 1352 "1. Multiprotocol Label Switching (MPLS) Label Switching 1353 Router (LSR) Management Information Base (MIB), RFC 3813." 1354 ::= { mplsLsrExtObjects 1 } 1356 mplsXCExtEntry OBJECT-TYPE 1357 SYNTAX MplsXCExtEntry 1358 MAX-ACCESS not-accessible 1360 STATUS current 1361 DESCRIPTION 1363 "An entry in this table extends the cross connect 1364 information represented by an entry in 1365 the mplsXCTable in MPLS-LSR-STD-MIB [RFC3813] through 1366 a sparse augmentation. An entry can be created by 1367 a network operator via SNMP SET commands, or in 1368 response to signaling protocol events." 1369 REFERENCE 1370 "1. Multiprotocol Label Switching (MPLS) Label Switching 1371 Router (LSR) Management Information Base (MIB), RFC 3813." 1373 INDEX { mplsXCIndex, mplsXCInSegmentIndex, 1374 mplsXCOutSegmentIndex } 1375 ::= { mplsXCExtTable 1 } 1377 MplsXCExtEntry ::= SEQUENCE { 1378 mplsXCExtTunnelPointer RowPointer, 1379 mplsXCExtOppositeDirXCPtr RowPointer 1380 } 1382 mplsXCExtTunnelPointer OBJECT-TYPE 1383 SYNTAX RowPointer 1384 MAX-ACCESS read-only 1385 STATUS current 1386 DESCRIPTION 1387 "This read-only object indicates the back pointer to 1388 the tunnel entry segment. 1389 The only valid value for Tunnel Pointer is 1390 mplsTunnelTable entry." 1391 REFERENCE 1392 "1. Multiprotocol Label Switching (MPLS) Label Switching 1393 Router (LSR) Management Information Base (MIB), RFC 3813." 1394 ::= { mplsXCExtEntry 1 } 1396 mplsXCExtOppositeDirXCPtr OBJECT-TYPE 1397 SYNTAX RowPointer 1398 MAX-ACCESS read-create 1399 STATUS current 1400 DESCRIPTION 1401 "This object indicates the pointer to the opposite 1402 direction XC entry. This object cannot be modified if 1403 mplsXCRowStatus for the corresponding entry in the 1404 mplsXCTable is active(1)." 1405 REFERENCE 1406 "1. Multiprotocol Label Switching (MPLS) Label Switching 1407 Router (LSR) Management Information Base (MIB), RFC 3813." 1408 ::= { mplsXCExtEntry 2 } 1410 mplsLsrExtCompliances 1411 OBJECT IDENTIFIER ::= { mplsLsrExtConformance 1 } 1413 mplsLsrExtGroups 1414 OBJECT IDENTIFIER ::= { mplsLsrExtConformance 2 } 1416 -- Compliance requirement for fully compliant implementations. 1418 mplsLsrExtModuleFullCompliance MODULE-COMPLIANCE 1419 STATUS current 1420 DESCRIPTION 1421 "Compliance statement for agents that provide full support 1422 for MPLS-LSR-EXT-STD-MIB. 1423 The mandatory group has to be implemented by all LSRs 1424 that originate, terminate, or act as transit for 1425 TE-LSPs/tunnels. 1426 In addition, depending on the type of tunnels supported, 1427 other groups become mandatory as explained below." 1429 MODULE MPLS-LSR-STD-MIB -- The MPLS-LSR-STD-MIB, RFC3813 1431 MANDATORY-GROUPS { 1432 mplsInSegmentGroup, 1433 mplsOutSegmentGroup, 1434 mplsXCGroup, 1435 mplsPerfGroup, 1436 mplsLsrNotificationGroup 1437 } 1439 MODULE -- this module 1441 MANDATORY-GROUPS { 1442 mplsXCExtGroup 1443 } 1445 ::= { mplsLsrExtCompliances 1 } 1447 -- Compliance requirement for implementations that provide 1448 -- read-only access. 1450 mplsLsrExtModuleReadOnlyCompliance MODULE-COMPLIANCE 1451 STATUS current 1452 DESCRIPTION 1453 "Compliance requirement for implementations that only 1454 provide read-only support for MPLS-LSR-EXT-STD-MIB. 1455 Such devices can then be monitored but cannot be 1456 configured using this MIB module." 1458 MODULE MPLS-LSR-STD-MIB 1460 MANDATORY-GROUPS { 1461 mplsInterfaceGroup, 1462 mplsInSegmentGroup, 1463 mplsOutSegmentGroup, 1464 mplsPerfGroup 1465 } 1467 MODULE -- this module 1469 GROUP mplsXCExtReadOnlyObjectsGroup 1470 DESCRIPTION 1471 "This group is mandatory for devices which support 1472 Opposite direction XC configuration of tunnels." 1474 -- mplsXCExtTable 1475 OBJECT mplsXCExtOppositeDirXCPtr 1476 MIN-ACCESS read-only 1477 DESCRIPTION 1478 "Write access is not required. 1479 This object indicates the pointer to the opposite 1480 direction XC entry. The only valid value for XC 1481 Pointer is mplsXCTable entry." 1482 ::= { mplsLsrExtCompliances 2 } 1484 -- Units of conformance. 1486 mplsXCExtGroup OBJECT-GROUP 1487 OBJECTS { 1488 mplsXCExtTunnelPointer, 1489 mplsXCExtOppositeDirXCPtr 1490 } 1491 STATUS current 1492 DESCRIPTION 1493 "This object should be supported in order to access 1494 the tunnel entry from XC entry." 1495 ::= { mplsLsrExtGroups 1 } 1497 mplsXCExtReadOnlyObjectsGroup OBJECT-GROUP 1498 OBJECTS { mplsXCExtOppositeDirXCPtr } 1499 STATUS current 1500 DESCRIPTION 1501 "This Object is needed to associate the opposite direction 1502 (forward/reverse) XC entry." 1503 ::= { mplsLsrExtGroups 2 } 1505 -- MPLS-LSR-EXT-STD-MIB module ends 1506 END 1508 13. MPLS Tunnel Extension MIB definitions 1510 MPLS-TE-EXT-STD-MIB DEFINITIONS ::= BEGIN 1512 IMPORTS 1513 MODULE-IDENTITY, OBJECT-TYPE, Counter32, 1514 Counter64, zeroDotZero 1516 FROM SNMPv2-SMI -- [RFC2578] 1517 MODULE-COMPLIANCE, OBJECT-GROUP 1518 FROM SNMPv2-CONF -- [RFC2580] 1519 TruthValue, RowStatus, RowPointer, StorageType 1520 FROM SNMPv2-TC -- [RFC2579] 1521 MplsGlobalId, MplsNodeId, MplsCcId, MplsIccId 1522 FROM MPLS-TC-EXT-STD-MIB 1523 mplsStdMIB, MplsTunnelIndex, MplsTunnelInstanceIndex, 1524 MplsExtendedTunnelId 1525 FROM MPLS-TC-STD-MIB -- [RFC3811] 1526 mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, 1527 mplsTunnelEgressLSRId 1528 FROM MPLS-TE-STD-MIB -- [RFC3812] 1529 ; 1531 mplsTeExtStdMIB MODULE-IDENTITY 1532 LAST-UPDATED 1533 "201304130000Z" -- April 13, 2013 1534 ORGANIZATION 1535 "Multiprotocol Label Switching (MPLS) Working Group" 1536 CONTACT-INFO 1537 " 1538 Venkatesan Mahalingam 1539 Dell Inc, 1540 350 Holger way, San Jose, CA, USA 1541 Email: venkat.mahalingams@gmail.com 1543 Kannan KV Sampath 1544 Redeem, 1545 India 1546 Email: kannankvs@gmail.com 1548 Sam Aldrin 1549 Huawei Technologies 1550 2330 Central Express Way, 1551 Santa Clara, CA 95051, USA 1553 Email: aldrin.ietf@gmail.com 1555 Thomas D. Nadeau 1556 Juniper Networks 1557 10 Technology Park Drive, Westford, MA 01886 1558 Email: tnadeau@juniper.net 1559 " 1560 DESCRIPTION 1561 "Copyright (c) 2013 IETF Trust and the persons identified 1562 as the document authors. All rights reserved. 1564 This MIB module contains generic object definitions for 1565 MPLS Traffic Engineering in transport networks." 1567 -- Revision history. 1569 REVISION 1570 "201304130000Z" -- April 13, 2013 1572 DESCRIPTION 1573 "MPLS TE MIB objects extension" 1575 ::= { mplsStdMIB xxx } -- xxx to be replaced 1576 -- with correct value 1578 -- Top level components of this MIB module. 1580 -- tables, scalars 1581 mplsTeExtObjects OBJECT IDENTIFIER 1582 ::= { mplsTeExtStdMIB 0 } 1583 -- conformance 1584 mplsTeExtConformance OBJECT IDENTIFIER 1585 ::= { mplsTeExtStdMIB 1 } 1587 -- Start of MPLS Transport Profile Node configuration table 1588 mplsTunnelExtNodeConfigTable OBJECT-TYPE 1589 SYNTAX SEQUENCE OF MplsTunnelExtNodeConfigEntry 1590 MAX-ACCESS not-accessible 1591 STATUS current 1592 DESCRIPTION 1593 "This table allows the operator to map a node or 1594 LSR Identifier (IP compatible [Global_ID::Node_ID] or 1595 ICC based [CC::ICC]) with a local identifier. 1597 This table is created to reuse the existing 1598 mplsTunnelTable for MPLS based transport network 1599 tunnels also. 1601 Since the MPLS tunnel's Ingress/Egress LSR identifiers' 1602 size (Unsigned32) value is not compatible for 1603 MPLS-TP tunnel i.e. Global_ID::Node_ID of size 8 bytes and 1604 CC::ICC of size 8 bytes, there exists a need to map the 1605 Global_ID::Node_ID or CC::ICC with the local identifier of 1606 size 4 bytes (Unsigned32) value in order to index 1607 (Ingress/Egress LSR identifier) the existing 1608 mplsTunnelTable." 1610 ::= { mplsTeExtObjects 1 } 1612 mplsTunnelExtNodeConfigEntry OBJECT-TYPE 1613 SYNTAX MplsTunnelExtNodeConfigEntry 1614 MAX-ACCESS not-accessible 1615 STATUS current 1616 DESCRIPTION 1618 "An entry in this table represents a mapping 1619 identification for the operator or service provider 1620 with node or LSR. 1622 As per [RFC6370], IP compatible mapping is 1623 represented as Global_ID::Node_ID. 1625 As per [I-D.ietf-mpls-tp-itu-t-identifiers], ICC 1626 compatible mapping is represented as CC::ICC. 1628 Note: Each entry in this table should have a unique 1629 [Global_ID and Node_ID] or [CC and ICC] combination." 1630 INDEX { mplsTunnelExtNodeConfigLocalId } 1631 ::= { mplsTunnelExtNodeConfigTable 1 } 1633 MplsTunnelExtNodeConfigEntry ::= SEQUENCE { 1634 mplsTunnelExtNodeConfigLocalId MplsExtendedTunnelId, 1635 mplsTunnelExtNodeConfigGlobalId MplsGlobalId, 1636 mplsTunnelExtNodeConfigNodeId MplsNodeId, 1637 mplsTunnelExtNodeConfigCcId MplsCcId, 1638 mplsTunnelExtNodeConfigIccId MplsIccId, 1639 mplsTunnelExtNodeConfigIccValid TruthValue, 1640 mplsTunnelExtNodeConfigRowStatus RowStatus, 1641 mplsTunnelExtNodeConfigStorageType StorageType 1643 } 1645 mplsTunnelExtNodeConfigLocalId OBJECT-TYPE 1646 SYNTAX MplsExtendedTunnelId 1647 MAX-ACCESS not-accessible 1648 STATUS current 1649 DESCRIPTION 1650 "This object is used in accommodating the bigger 1651 size Global_ID::Node_ID and/or CC::ICC with lower size LSR 1652 identifier in order to index the mplsTunnelTable. 1654 The Local Identifier is configured between 0 and 16777215, 1655 as valid IP address range starts from 16777216(01.00.00.00). 1656 This range is chosen to identify the mplsTunnelTable's 1657 Ingress/Egress LSR-id is IP address or Local identifier, 1658 if the configured range is not IP address, operator is 1659 expected to retrieve the complete information 1660 (Global_ID::Node_ID or CC::ICC) from 1661 mplsTunnelExtNodeConfigTable. 1662 This way, existing mplsTunnelTable is reused for 1663 bidirectional tunnel extensions for MPLS based transport 1664 networks. 1666 This Local Identifier allows the operator to assign 1667 a unique identifier to map Global_ID::Node_ID and/or 1668 CC::ICC. As this Local Identifier is unique within the node 1669 and the same syntax of this object can be used for MPLS TE 1670 tunnel also, it is up to the operator/local management 1671 entity to choose the non-conflicting value for indexing 1672 the MPLS and MPLS-TP tunnel entries." 1673 ::= { mplsTunnelExtNodeConfigEntry 1 } 1675 mplsTunnelExtNodeConfigGlobalId OBJECT-TYPE 1676 SYNTAX MplsGlobalId 1677 MAX-ACCESS read-create 1678 STATUS current 1679 DESCRIPTION 1680 "This object indicates the Global Operator Identifier. 1681 This object has no meaning when 1682 mplsTunnelExtNodeConfigIccValid is set true." 1683 REFERENCE 1684 "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370] 1685 Section 3." 1686 ::= { mplsTunnelExtNodeConfigEntry 2 } 1688 mplsTunnelExtNodeConfigNodeId OBJECT-TYPE 1689 SYNTAX MplsNodeId 1690 MAX-ACCESS read-create 1691 STATUS current 1692 DESCRIPTION 1693 "This object indicates the Node_ID within the scope 1694 of a Global_ID. This object has no meaning when 1695 mplsTunnelExtNodeConfigIccValid is set true." 1696 REFERENCE 1697 "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370] 1698 Section 4." 1699 ::= { mplsTunnelExtNodeConfigEntry 3 } 1701 mplsTunnelExtNodeConfigCcId OBJECT-TYPE 1702 SYNTAX MplsCcId 1703 MAX-ACCESS read-create 1704 STATUS current 1705 DESCRIPTION 1706 "This object allows the operator or service provider to 1707 configure a unique MPLS-TP ITU-T Country Code (CC) 1708 either for Ingress ID or Egress ID. 1710 This object has no meaning when 1711 mplsTunnelExtNodeConfigIccValid is set false." 1712 REFERENCE 1713 "MPLS-TP Identifiers Following ITU-T Conventions, 1714 draft-ietf-mpls-tp-itu-t-identifiers-08 (work in 1715 progress), February 2013. Section 3" 1716 ::= { mplsTunnelExtNodeConfigEntry 4 } 1718 mplsTunnelExtNodeConfigIccId OBJECT-TYPE 1719 SYNTAX MplsIccId 1720 MAX-ACCESS read-create 1721 STATUS current 1722 DESCRIPTION 1723 "This object allows the operator or service provider to 1724 configure a unique MPLS-TP ITU-T Carrier Code (ICC) 1725 either for Ingress ID or Egress ID. 1727 This object has no meaning when 1728 mplsTunnelExtNodeConfigIccValid is set false." 1729 REFERENCE 1730 "MPLS-TP Identifiers Following ITU-T Conventions, 1731 draft-ietf-mpls-tp-itu-t-identifiers-08 (work in 1732 progress), February 2013. Section 3" 1733 ::= { mplsTunnelExtNodeConfigEntry 5 } 1735 mplsTunnelExtNodeConfigIccValid OBJECT-TYPE 1736 SYNTAX TruthValue 1737 MAX-ACCESS read-create 1738 STATUS current 1739 DESCRIPTION 1740 "Denotes whether or not this entry uses 1741 mplsTunnelExtNodeConfigCcId and 1742 mplsTunnelExtNodeConfigIccId for mapping 1743 the ICC based identifiers with the local identifier. 1744 Note that if this variable is set to false then the 1745 mplsTunnelExtNodeConfigGlobalId and 1746 mplsTunnelExtNodeConfigNodeId objects should have 1747 the valid information." 1748 DEFVAL { false } 1749 ::= { mplsTunnelExtNodeConfigEntry 6 } 1751 mplsTunnelExtNodeConfigRowStatus OBJECT-TYPE 1752 SYNTAX RowStatus 1753 MAX-ACCESS read-create 1754 STATUS current 1755 DESCRIPTION 1756 "This object allows the operator to create, modify, 1757 and/or delete a row in this table." 1758 ::= { mplsTunnelExtNodeConfigEntry 7 } 1760 mplsTunnelExtNodeConfigStorageType OBJECT-TYPE 1761 SYNTAX StorageType 1762 MAX-ACCESS read-create 1763 STATUS current 1764 DESCRIPTION 1765 "This variable indicates the storage type for this 1766 object. 1767 Conceptual rows having the value 'permanent' 1768 need not allow write-access to any columnar 1769 objects in the row." 1770 DEFVAL { volatile } 1771 ::= { mplsTunnelExtNodeConfigEntry 8 } 1773 -- End of MPLS Transport Profile Node configuration table 1775 -- Start of MPLS Transport Profile Node IP compatible 1776 -- mapping table 1778 mplsTunnelExtNodeIpMapTable OBJECT-TYPE 1779 SYNTAX SEQUENCE OF MplsTunnelExtNodeIpMapEntry 1781 MAX-ACCESS not-accessible 1782 STATUS current 1783 DESCRIPTION 1784 "This read-only table allows the operator to retrieve 1785 the local identifier for a given Global_ID::Node_ID in an IP 1786 compatible operator environment. 1788 This table MAY be used in on-demand and/or proactive 1789 OAM operations to get the Ingress/Egress LSR identifier 1790 (Local Identifier) from Src-Global_Node_ID 1791 or Dst-Global_Node_ID and the Ingress and Egress LSR 1792 identifiers are used to retrieve the tunnel entry. 1794 This table returns nothing when the associated entry 1795 is not defined in mplsTunnelExtNodeConfigTable." 1796 ::= { mplsTeExtObjects 2 } 1798 mplsTunnelExtNodeIpMapEntry OBJECT-TYPE 1799 SYNTAX MplsTunnelExtNodeIpMapEntry 1800 MAX-ACCESS not-accessible 1801 STATUS current 1802 DESCRIPTION 1803 "An entry in this table represents a mapping of 1804 Global_ID::Node_ID with the local identifier. 1806 An entry in this table is created automatically when 1807 the Local identifier is associated with Global_ID and 1808 Node_Id in the mplsTunnelExtNodeConfigTable. 1810 Note: Each entry in this table should have a unique 1811 Global_ID and Node_ID combination." 1812 INDEX { mplsTunnelExtNodeIpMapGlobalId, 1813 mplsTunnelExtNodeIpMapNodeId 1814 } 1815 ::= { mplsTunnelExtNodeIpMapTable 1 } 1817 MplsTunnelExtNodeIpMapEntry ::= SEQUENCE { 1818 mplsTunnelExtNodeIpMapGlobalId MplsGlobalId, 1819 mplsTunnelExtNodeIpMapNodeId MplsNodeId, 1820 mplsTunnelExtNodeIpMapLocalId MplsExtendedTunnelId 1821 } 1823 mplsTunnelExtNodeIpMapGlobalId OBJECT-TYPE 1824 SYNTAX MplsGlobalId 1825 MAX-ACCESS not-accessible 1826 STATUS current 1827 DESCRIPTION 1828 "This object indicates the Global_ID." 1829 ::= { mplsTunnelExtNodeIpMapEntry 1 } 1831 mplsTunnelExtNodeIpMapNodeId OBJECT-TYPE 1832 SYNTAX MplsNodeId 1833 MAX-ACCESS not-accessible 1834 STATUS current 1835 DESCRIPTION 1836 "This object indicates the Node_ID within the 1837 operator." 1838 ::= { mplsTunnelExtNodeIpMapEntry 2 } 1840 mplsTunnelExtNodeIpMapLocalId OBJECT-TYPE 1841 SYNTAX MplsExtendedTunnelId 1842 MAX-ACCESS read-only 1843 STATUS current 1844 DESCRIPTION 1845 "This object contains an IP compatible local identifier 1846 which is defined in mplsTunnelExtNodeConfigTable." 1847 ::= { mplsTunnelExtNodeIpMapEntry 3 } 1849 -- End MPLS Transport Profile Node IP compatible table 1851 -- Start of MPLS Transport Profile Node ICC based table 1853 mplsTunnelExtNodeIccMapTable OBJECT-TYPE 1854 SYNTAX SEQUENCE OF MplsTunnelExtNodeIccMapEntry 1855 MAX-ACCESS not-accessible 1856 STATUS current 1857 DESCRIPTION 1858 "This read-only table allows the operator to retrieve 1859 the local identifier for a given CC::ICC in an ICC 1860 operator environment. 1862 This table MAY be used in on-demand and/or proactive 1863 OAM operations to get the Ingress/Egress LSR 1864 identifier (Local Identifier) from Src-ICC 1865 or Dst-ICC and the Ingress and Egress LSR 1866 identifiers are used to retrieve the tunnel entry. 1867 This table returns nothing when the associated entry 1868 is not defined in mplsTunnelExtNodeConfigTable." 1869 ::= { mplsTeExtObjects 3 } 1871 mplsTunnelExtNodeIccMapEntry OBJECT-TYPE 1872 SYNTAX MplsTunnelExtNodeIccMapEntry 1873 MAX-ACCESS not-accessible 1874 STATUS current 1875 DESCRIPTION 1876 "An entry in this table represents a mapping of CC::ICC 1877 with the local identifier. 1879 An entry in this table is created automatically when 1880 the Local identifier is associated with CC::ICC in 1881 the mplsTunnelExtNodeConfigTable." 1882 INDEX { mplsTunnelExtNodeIccMapCcId, 1883 mplsTunnelExtNodeIccMapIccId } 1884 ::= { mplsTunnelExtNodeIccMapTable 1 } 1886 MplsTunnelExtNodeIccMapEntry ::= SEQUENCE { 1887 mplsTunnelExtNodeIccMapCcId MplsCcId, 1888 mplsTunnelExtNodeIccMapIccId MplsIccId, 1889 mplsTunnelExtNodeIccMapLocalId MplsExtendedTunnelId 1890 } 1892 mplsTunnelExtNodeIccMapCcId OBJECT-TYPE 1893 SYNTAX MplsCcId 1894 MAX-ACCESS not-accessible 1895 STATUS current 1896 DESCRIPTION 1897 "This object allows the operator or service provider to 1898 configure a unique MPLS-TP ITU-T Country Code (CC) 1899 either for Ingress or Egress LSR ID. 1901 The CC is a string of two alphabetic characters 1902 represented with upper case letters (i.e., A-Z)." 1903 ::= { mplsTunnelExtNodeIccMapEntry 1 } 1905 mplsTunnelExtNodeIccMapIccId OBJECT-TYPE 1906 SYNTAX MplsIccId 1907 MAX-ACCESS not-accessible 1908 STATUS current 1909 DESCRIPTION 1910 "This object allows the operator or service provider 1911 to configure a unique MPLS-TP ITU-T Carrier 1912 Code (ICC) either for Ingress or Egress LSR ID. 1914 The ICC is a string of one to six characters, each 1915 character being either alphabetic (i.e. A-Z) or 1916 numeric (i.e. 0-9) characters. Alphabetic characters 1917 in the ICC should be represented with upper case 1918 letters." 1919 ::= { mplsTunnelExtNodeIccMapEntry 2 } 1921 mplsTunnelExtNodeIccMapLocalId OBJECT-TYPE 1922 SYNTAX MplsExtendedTunnelId 1923 MAX-ACCESS read-only 1924 STATUS current 1925 DESCRIPTION 1926 "This object contains an ICC based local identifier 1927 which is defined in mplsTunnelExtNodeConfigTable." 1929 ::= { mplsTunnelExtNodeIccMapEntry 3 } 1931 -- End MPLS Transport Profile Node ICC based table 1932 -- Start of MPLS Tunnel table extension 1934 mplsTunnelExtTable OBJECT-TYPE 1935 SYNTAX SEQUENCE OF MplsTunnelExtEntry 1936 MAX-ACCESS not-accessible 1937 STATUS current 1938 DESCRIPTION 1939 "This table represents extensions to mplsTunnelTable 1940 in order to support MPLS-TP tunnels. 1942 As per MPLS-TP Identifiers [RFC6370], LSP_ID for IP based 1943 co-routed bidirectional tunnel, 1945 A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: 1946 Node_ID::Tunnel_Num}::LSP_Num 1948 LSP_ID for IP based associated bidirectional tunnel, 1949 A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: 1950 Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num} 1952 mplsTunnelTable is reused for forming the LSP_ID 1953 as follows, 1955 Source Tunnel_Num is mapped with mplsTunnelIndex, 1956 Source Node_ID is mapped with 1957 mplsTunnelIngressLSRId, Destination Node_ID is 1958 mapped with mplsTunnelEgressLSRId LSP_Num is mapped with 1959 mplsTunnelInstance. 1961 Source Global_ID::Node_ID and/or CC::ICC and Destination 1962 Global_ID::Node_ID and/or CC::ICC are maintained in the 1963 mplsTunnelExtNodeConfigTable and 1964 mplsTunnelExtNodeConfigLocalId is used to create an entry 1965 in mplsTunnelTable." 1966 REFERENCE 1967 "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370]." 1968 ::= { mplsTeExtObjects 4 } 1970 mplsTunnelExtEntry OBJECT-TYPE 1971 SYNTAX MplsTunnelExtEntry 1972 MAX-ACCESS not-accessible 1973 STATUS current 1974 DESCRIPTION 1975 "An entry in this table represents MPLS-TP 1976 specific additional tunnel configurations." 1977 INDEX { 1978 mplsTunnelIndex, 1979 mplsTunnelInstance, 1980 mplsTunnelIngressLSRId, 1981 mplsTunnelEgressLSRId 1982 } 1983 ::= { mplsTunnelExtTable 1 } 1985 MplsTunnelExtEntry ::= SEQUENCE { 1986 mplsTunnelExtOppositeDirPtr RowPointer, 1987 mplsTunnelExtOppositeDirTnlValid TruthValue, 1988 mplsTunnelExtDestTnlIndex MplsTunnelIndex, 1989 mplsTunnelExtDestTnlLspIndex MplsTunnelInstanceIndex, 1990 mplsTunnelExtDestTnlValid TruthValue, 1991 mplsTunnelExtIngressLSRLocalIdValid TruthValue, 1992 mplsTunnelExtEgressLSRLocalIdValid TruthValue 1994 } 1996 mplsTunnelExtOppositeDirPtr OBJECT-TYPE 1997 SYNTAX RowPointer 1998 MAX-ACCESS read-create 1999 STATUS current 2000 DESCRIPTION 2001 "This object is applicable only for the bidirectional 2002 tunnel that has the forward and reverse LSPs in the 2003 same tunnel or in the different tunnels. 2005 This object holds the opposite direction tunnel entry 2006 if the bidirectional tunnel is setup by configuring two 2007 tunnel entries in mplsTunnelTable. 2009 The value of zeroDotZero indicates single tunnel entry 2010 is used for bidirectional tunnel setup." 2011 DEFVAL { zeroDotZero } 2012 ::= { mplsTunnelExtEntry 1 } 2014 mplsTunnelExtOppositeDirTnlValid OBJECT-TYPE 2015 SYNTAX TruthValue 2016 MAX-ACCESS read-create 2017 STATUS current 2018 DESCRIPTION 2019 "Denotes whether or not this tunnel uses 2020 mplsTunnelExtOppositeDirPtr for identifying the opposite 2021 direction tunnel information. Note that if this variable 2022 is set to true then the mplsTunnelExtOppositeDirPtr should 2023 point to the first accessible row of the opposite 2024 direction tunnel." 2025 DEFVAL { false } 2026 ::= { mplsTunnelExtEntry 2 } 2028 mplsTunnelExtDestTnlIndex OBJECT-TYPE 2029 SYNTAX MplsTunnelIndex 2030 MAX-ACCESS read-create 2031 STATUS current 2032 DESCRIPTION 2033 "This object is applicable only for the bidirectional 2034 tunnel that has the forward and reverse LSPs in the 2035 same tunnel or in the different tunnels. 2037 This object holds the same value as that of the 2038 mplsTunnelIndex of mplsTunnelEntry if the forward and 2039 reverse LSPs are in the same tunnel. Otherwise, 2040 this object holds the value of the other direction 2041 associated LSP's mplsTunnelIndex from a different 2043 tunnel. 2045 The values of this object and the 2046 mplsTunnelExtDestTnlLspIndex object together can be used 2047 to identify an opposite direction LSP i.e. if the 2048 mplsTunnelIndex and mplsTunnelInstance hold the value 2049 for forward LSP, this object and 2050 mplsTunnelExtDestTnlLspIndex can be used to retrieve 2051 the reverse direction LSP and vice versa. 2053 This object and mplsTunnelExtDestTnlLspIndex values 2054 provide the first two indices of tunnel entry and 2055 the remaining indices can be derived as follows, 2056 if both the forward and reverse LSPs are present in 2057 the same tunnel, the opposite direction LSP's Ingress 2058 and Egress Identifier will be same for both the LSPs, 2059 else the Ingress and Egress Identifiers should be 2060 swapped in order to index the other direction tunnel." 2062 ::= { mplsTunnelExtEntry 3 } 2064 mplsTunnelExtDestTnlLspIndex OBJECT-TYPE 2065 SYNTAX MplsTunnelInstanceIndex 2066 MAX-ACCESS read-create 2067 STATUS current 2068 DESCRIPTION 2069 "This object is applicable only for the bidirectional 2070 tunnel that has the forward and reverse LSPs in the 2071 same tunnel or in the different tunnels. 2073 This object should contain different value if both the 2074 forward and reverse LSPs present in the same tunnel. 2076 This object can contain same value or different values 2077 if the forward and reverse LSPs present in the different 2078 tunnels." 2080 ::= { mplsTunnelExtEntry 4 } 2082 mplsTunnelExtDestTnlValid OBJECT-TYPE 2083 SYNTAX TruthValue 2084 MAX-ACCESS read-create 2085 STATUS current 2086 DESCRIPTION 2087 "Denotes whether or not this tunnel uses 2088 mplsTunnelExtDestTnlIndex and 2089 mplsTunnelExtDestTnlLspIndex for identifying 2090 the opposite direction tunnel information. Note that if 2091 this variable is set to true then the 2092 mplsTunnelExtDestTnlIndex and 2093 mplsTunnelExtDestTnlLspIndex objects should have 2094 the valid opposite direction tunnel indices." 2095 DEFVAL { false } 2096 ::= { mplsTunnelExtEntry 5 } 2098 mplsTunnelExtIngressLSRLocalIdValid OBJECT-TYPE 2099 SYNTAX TruthValue 2100 MAX-ACCESS read-create 2101 STATUS current 2102 DESCRIPTION 2103 "This object denotes whether the mplsTunnelIngressLSRId 2104 contains the local value, which is used to reference 2105 the complete Ingress Global_ID::Node_ID or ICC from 2106 the mplsTunnelExtNodeConfigTable. 2108 If this object is set to FALSE, mplsTunnelExtNodeConfigTable 2109 will not contain an entry to reference local identifier with 2110 Global_ID::Node_ID or ICC value. 2112 This object is set to FALSE for legacy implementations like 2113 MPLS TE tunnels where mplsTunnelIngressId itself provides 2114 complete Ingress LSRId." 2115 REFERENCE 2116 "MPLS-TE-STD-MIB [RFC3812], Section 11. 2117 mplsTunnelIngressLSRId object in mplsTunnelTable." 2118 DEFVAL { false } 2119 ::= { mplsTunnelExtEntry 6 } 2121 mplsTunnelExtEgressLSRLocalIdValid OBJECT-TYPE 2122 SYNTAX TruthValue 2123 MAX-ACCESS read-create 2124 STATUS current 2125 DESCRIPTION 2126 "This object denotes whether the mplsTunnelEgressLSRId 2127 contains the local value, which is used to reference 2128 the complete Egress Global_ID::Node_ID or ICC from 2129 the mplsTunnelExtNodeConfigTable. 2131 If this object is set to FALSE, mplsTunnelExtNodeConfigTable 2132 will not contain an entry to reference local identifier with 2133 Global_ID::Node_ID or ICC value. 2135 This object is set to FALSE for legacy implementations like 2136 MPLS TE tunnels where mplsTunnelEgressId itself provides 2137 complete Egress LSRId." 2138 REFERENCE 2139 "MPLS-TE-STD-MIB [RFC3812], Section 11. 2140 mplsTunnelEgressLSRId object in mplsTunnelTable." 2141 DEFVAL { false } 2142 ::= { mplsTunnelExtEntry 7 } 2144 -- End of MPLS Tunnel table extension 2145 mplsTunnelExtReversePerfTable OBJECT-TYPE 2146 SYNTAX SEQUENCE OF MplsTunnelExtReversePerfEntry 2147 MAX-ACCESS not-accessible 2148 STATUS current 2149 DESCRIPTION 2150 "This table extends the mplsTunnelTable to provide 2151 per-tunnel packet performance information for the reverse 2152 direction of a bidirectional tunnel. It can be seen as 2153 supplementing the mplsTunnelPerfTable, which augments the 2154 mplsTunnelTable." 2155 REFERENCE 2156 "1. Multiprotocol Label Switching (MPLS) Traffic 2157 Engineering (TE)Management Information Base (MIB), 2158 RFC 3812." 2159 ::= { mplsTeExtObjects 5 } 2161 mplsTunnelExtReversePerfEntry OBJECT-TYPE 2162 SYNTAX MplsTunnelExtReversePerfEntry 2163 MAX-ACCESS not-accessible 2164 STATUS current 2165 DESCRIPTION 2166 "An entry in this table is created by the LSR for every 2167 bidirectional MPLS tunnel where packets are visible to the 2168 LSR." 2169 INDEX { 2170 mplsTunnelIndex, 2171 mplsTunnelInstance, 2172 mplsTunnelIngressLSRId, 2173 mplsTunnelEgressLSRId 2174 } 2175 ::= { mplsTunnelExtReversePerfTable 1 } 2177 MplsTunnelExtReversePerfEntry ::= SEQUENCE { 2178 mplsTunnelExtReversePerfPackets Counter32, 2179 mplsTunnelExtReversePerfHCPackets Counter64, 2180 mplsTunnelExtReversePerfErrors Counter32, 2181 mplsTunnelExtReversePerfBytes Counter32, 2182 mplsTunnelExtReversePerfHCBytes Counter64 2183 } 2185 mplsTunnelExtReversePerfPackets OBJECT-TYPE 2186 SYNTAX Counter32 2187 MAX-ACCESS read-only 2189 STATUS current 2190 DESCRIPTION 2191 "Number of packets forwarded on the tunnel in the reverse 2192 direction if it is bidirectional. 2194 This object represents the 32-bit value of the least 2195 significant part of the 64-bit value if both 2196 mplsTunnelExtReversePerfHCPackets and this object 2197 are returned." 2198 ::= { mplsTunnelExtReversePerfEntry 1 } 2200 mplsTunnelExtReversePerfHCPackets OBJECT-TYPE 2201 SYNTAX Counter64 2202 MAX-ACCESS read-only 2203 STATUS current 2204 DESCRIPTION 2205 "High-capacity counter for number of packets forwarded on 2206 the tunnel in the reverse direction if it is 2207 bidirectional." 2209 ::= { mplsTunnelExtReversePerfEntry 2 } 2211 mplsTunnelExtReversePerfErrors OBJECT-TYPE 2212 SYNTAX Counter32 2213 MAX-ACCESS read-only 2214 STATUS current 2215 DESCRIPTION 2216 "Number of errored packets received on the tunnel in 2217 the reverse direction if it is bidirectional." 2218 ::= { mplsTunnelExtReversePerfEntry 3 } 2219 mplsTunnelExtReversePerfBytes OBJECT-TYPE 2220 SYNTAX Counter32 2221 MAX-ACCESS read-only 2222 STATUS current 2223 DESCRIPTION 2224 "Number of bytes forwarded on the tunnel in the reverse 2225 direction if it is bidirectional. 2227 This object represents the 32-bit value of the least 2228 significant part of the 64-bit value if both 2229 mplsTunnelExtReversePerfHCBytes and this object are 2230 returned." 2232 ::= { mplsTunnelExtReversePerfEntry 4 } 2234 mplsTunnelExtReversePerfHCBytes OBJECT-TYPE 2235 SYNTAX Counter64 2236 MAX-ACCESS read-only 2237 STATUS current 2238 DESCRIPTION 2239 "High-capacity counter for number of bytes forwarded on the 2240 tunnel in the reverse direction if it is bidirectional." 2241 ::= { mplsTunnelExtReversePerfEntry 5 } 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 2274 DESCRIPTION 2275 "This group is mandatory for devices which support 2276 configuration of IP based identifier tunnels." 2278 GROUP mplsTunnelExtIccOperatorGroup 2280 DESCRIPTION 2281 "This group is mandatory for devices which support 2282 configuration of ICC based tunnels." 2284 ::= { mplsTeExtCompliances 1 } 2286 -- Compliance requirement for read-only implementations. 2288 mplsTeExtModuleReadOnlyCompliance MODULE-COMPLIANCE 2289 STATUS current 2290 DESCRIPTION 2291 "Compliance statement for agents that provide full 2292 support the MPLS-TE-EXT-STD-MIB module." 2294 MODULE -- this module 2296 -- The mandatory group has to be implemented by all 2297 -- LSRs that originate/terminate MPLS-TP tunnels. 2298 -- In addition, depending on the type of tunnels 2299 -- supported, other groups become mandatory as 2300 -- explained below. 2302 MANDATORY-GROUPS { 2303 mplsTunnelExtGroup 2304 } 2306 GROUP mplsTunnelExtIpOperatorGroup 2307 DESCRIPTION 2308 "This group is mandatory for devices which support 2309 configuration of IP based identifier tunnels." 2311 GROUP mplsTunnelExtIccOperatorGroup 2313 DESCRIPTION 2314 "This group is mandatory for devices which support 2315 configuration of ICC based tunnels." 2317 ::= { mplsTeExtCompliances 2 } 2319 -- Units of conformance. 2321 mplsTunnelExtGroup OBJECT-GROUP 2322 OBJECTS { 2323 mplsTunnelExtOppositeDirPtr, 2324 mplsTunnelExtOppositeDirTnlValid, 2325 mplsTunnelExtDestTnlIndex, 2326 mplsTunnelExtDestTnlLspIndex, 2327 mplsTunnelExtDestTnlValid, 2328 mplsTunnelExtIngressLSRLocalIdValid, 2329 mplsTunnelExtEgressLSRLocalIdValid, 2330 mplsTunnelExtReversePerfPackets, 2331 mplsTunnelExtReversePerfHCPackets, 2332 mplsTunnelExtReversePerfErrors, 2333 mplsTunnelExtReversePerfBytes, 2334 mplsTunnelExtReversePerfHCBytes 2335 } 2337 STATUS current 2338 DESCRIPTION 2339 "Necessary, but not sufficient, set of objects to 2340 implement tunnels. In addition, depending on the 2341 operating environment, the following groups are 2342 mandatory." 2343 ::= { mplsTeExtGroups 1 } 2345 mplsTunnelExtIpOperatorGroup OBJECT-GROUP 2346 OBJECTS { mplsTunnelExtNodeConfigGlobalId, 2347 mplsTunnelExtNodeConfigNodeId, 2348 mplsTunnelExtNodeConfigRowStatus, 2349 mplsTunnelExtNodeConfigStorageType, 2350 mplsTunnelExtNodeIpMapLocalId 2351 } 2352 STATUS current 2353 DESCRIPTION 2354 "Object(s) needed to implement IP compatible tunnels." 2355 ::= { mplsTeExtGroups 2 } 2357 mplsTunnelExtIccOperatorGroup OBJECT-GROUP 2358 OBJECTS { mplsTunnelExtNodeConfigCcId, 2359 mplsTunnelExtNodeConfigIccId, 2360 mplsTunnelExtNodeConfigIccValid, 2361 mplsTunnelExtNodeConfigRowStatus, 2362 mplsTunnelExtNodeConfigStorageType, 2363 mplsTunnelExtNodeIccMapLocalId 2364 } 2365 STATUS current 2366 DESCRIPTION 2367 "Object(s) needed to implement ICC based tunnels." 2368 ::= { mplsTeExtGroups 3 } 2370 -- MPLS-TE-EXT-STD-MIB module ends 2371 END 2373 14. Security Consideration 2375 It is clear that this MIB module is potentially useful for the 2376 monitoring of MPLS TE tunnels. This MIB module can also be used for 2377 the configuration of certain objects, and anything that can be 2378 configured can be incorrectly configured, with potentially disastrous 2379 results. 2381 There are a number of management objects defined in this MIB module 2382 with a MAX-ACCESS clause of read-write. Such objects may be 2383 considered sensitive or vulnerable in some network environments. The 2384 support for SET operations in a non-secure environment without proper 2385 protection can have a negative effect on network operations. These 2386 are the tables and objects and their sensitivity/vulnerability: 2388 - the tables specified in [RFC3812], [RFC3813] and this document 2389 MIB tables mplsTunnelExtNodeConfigTable, mplsTunnelExtTable and 2390 mplsXCExtTable collectively contain objects to provision MPLS-TP 2391 tunnels, tunnel hops, and tunnel resources. 2392 Unauthorized access to objects in these tables, could result in 2393 disruption of traffic on the network. This is especially true if 2394 a tunnel has been established. The use of stronger mechanisms, 2395 such as SNMPv3 security, should be considered where possible. 2396 Specifically, SNMPv3 VACM and USM MUST be used with any v3 agent 2397 which implements this MIB. Administrators should consider whether 2398 read access to these objects should be allowed, since read access 2399 may be undesirable under certain circumstances. 2401 Some of the readable objects in this MIB module (i.e., objects 2402 with a MAX-ACCESS other than not-accessible) may be considered 2403 sensitive or vulnerable in some network environments. 2404 It is thus important to control even GET and/or NOTIFY access to 2405 these objects and possibly to even encrypt the values of these 2406 objects when sending them over the network via SNMP. These are 2407 the tables and objects and their sensitivity/vulnerability: 2409 - the tables specified in [RFC3812], [RFC3813] and this document 2410 MIB tables mplsTunnelExtNodeConfigTable, mplsTunnelExtTable, 2411 mplsXCExtTable and mplsTunnelExtReversePerfTable collectively 2412 show the MPLS-TP tunnel network topology and its performance 2413 characteristics. If an Administrator does not want to reveal 2414 this information, then these tables should be considered 2415 sensitive/vulnerable. 2417 SNMP versions prior to SNMPv3 did not include adequate security. 2418 Even if the network itself is secure (for example by using IPsec), 2419 even then, there is no control as to who on the secure network is 2420 allowed to access and GET/SET (read/change/create/delete) 2421 the objects in this MIB module. 2423 It is recommended that implementers consider the security features as 2424 provided by the SNMPv3 framework (see [RFC3410], section 8), 2425 including full supports for the SNMPv3 cryptographic mechanisms (for 2426 authentication and privacy). 2428 Further, deployment of SNMP versions prior to SNMPv3 is not 2429 recommended. Instead, it is recommended to deploy SNMPv3 and to 2430 enable cryptographic security. It is then a customer/operator 2431 responsibility to ensure that the SNMP entity giving access to an 2432 instance of this MIB module is properly configured to give 2433 access to the objects only to those principles (users) that 2434 have legitimate rights to indeed GET or SET (change/create/delete) 2435 them. 2437 15. IANA Considerations 2439 As described in [MPLSMGMT] and as requested in the MPLS-TC-STD-MIB 2440 [RFC3811], MPLS related standards track MIB modules should be rooted 2441 under the mplsStdMIB subtree. There are 4 MPLS MIB Modules contained 2442 in this document, each of the following "IANA Considerations" 2443 subsections requests IANA for a new assignment under the mplsStdMIB 2444 subtree. New assignments can only be made via a Standards Action as 2445 specified in [RFC5226]. 2447 15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB 2449 IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS-TC- 2450 EXT-STD-MIB module specified in this document. 2452 15.2. IANA Considerations for MPLS-ID-STD-MIB 2453 IANA is requested to assign an OID { mplsStdMIB IOD } to the MPLS-ID- 2454 STD-MIB module specified in this document. 2456 15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB 2458 IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS- 2459 LSR-EXT-STD-MIB module specified in this document. 2461 15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB 2463 IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS-TE- 2464 EXT-STD-MIB module specified in this document. 2466 16. References 2468 16.1. Normative References 2470 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2471 Requirement Levels", BCP 14, RFC 2119, March 1997. 2473 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2474 "Structure of Management Information Version 2 (SMIv2)", 2475 STD 58, RFC 2578, April 1999. 2477 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2478 "Textual Conventions for SMIv2", STD 58, RFC 2579, April 2479 1999. 2481 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2483 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2484 April 1999. 2486 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 2487 Label Switching Architecture", RFC 3031, January 2001. 2489 16.2. Informative References 2491 [MPLSMGMT] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol 2492 Label Switching (MPLS) Management Overview", Work in 2493 Progress, September 2003. 2495 [RFC5226] Narten, T. and H. Alvestrand., "Guidelines for Writing 2496 an IANA Considerations Section in RFCs", BCP 26, 2497 RFC 5226, May 2008. 2499 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 2500 "Multiprotocol Label Switching (MPLS) Traffic Engineering 2501 (TE) Management Information Base (MIB)", RFC 3812, June 2502 2004. 2504 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 2505 "Multiprotocol Label Switching (MPLS) Label Switching 2506 (LSR) Router Management Information Base (MIB)", RFC 3813, 2507 June 2004. 2509 [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction 2510 and Applicability Statement for Internet Standard 2511 Management Framework", RFC 3410, December 2002. 2513 [RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of 2514 Textual Conventions (TCs) for Multiprotocol Label 2515 Switching (MPLS) Management", RFC 3811, June 2004. 2517 [RFC4802] Nadeau, T., Ed., and A. Farrel, Ed., "Generalized 2519 Multiprotocol Label Switching (GMPLS) Traffic 2520 Engineering Management Information Base", RFC 2521 4802, February 2007. 2522 [RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., Ed., 2523 Sprecher, N., and S. Ueno, "Requirements of an MPLS 2524 Transport Profile", RFC 5654, September 2009. 2526 [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport 2527 Profile (MPLS-TP) Identifiers", RFC 6370, September 2528 2011. 2530 [I-D.ietf-mpls-tp-itu-t-identifiers] Winter, R., Gray, E., Helvoort, 2531 H., and M. Betts, "MPLS-TP Identifiers Following ITU-T 2532 Conventions", draft-ietf-mpls-tp-itu-t-identifiers-08 2533 (work in progress), February 2013 2535 17. Acknowledgments 2537 The authors would like to thank Francesco Fondelli, Josh Littlefield, 2538 Agrahara Kiran Koushik, Metrri Jain, Muly Ilan and Randy Presuhn for 2539 their valuable comments. A special thanks to Joan Cucchiara for 2540 really getting the MIB modules into shape. 2542 18. Authors' Addresses 2544 Venkatesan Mahalingam 2545 Dell Inc. 2546 350 Holger way, San Jose, CA, USA 2547 Email: venkat.mahalingams@gmail.com 2549 Sam Aldrin 2550 Huawei Technologies 2551 2330 Central Express Way, 2552 Santa Clara, CA 95051, USA 2553 Email: aldrin.ietf@gmail.com 2555 Thomas D. Nadeau 2556 Juniper Networks 2557 10 Technology Park Drive, Westford, MA 01886 2558 Email: tnadeau@juniper.net 2560 Kannan KV Sampath 2561 Redeem 2562 India 2563 Email: kannankvs@gmail.com