idnits 2.17.1 draft-ietf-mpls-tp-te-mib-07.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 (November 04, 2013) is 3824 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: May 08, 2014 Kannan KV Sampath 6 Redeem 7 Sam K. Aldrin 8 Huawei Technologies 9 Thomas D. Nadeau 10 Juniper Networks 12 November 04, 2013 14 MPLS-TP Traffic Engineering (TE) Management Information Base (MIB) 15 draft-ietf-mpls-tp-te-mib-07.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 Switching Router and Textual conventions for Multiprotocol 23 Label 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 May 08, 2014. 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 . . . . . . . . . . . . . . . . . 9 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 10. MPLS Textual Convention Extension MIB definitions . . . . . . 22 113 11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 25 114 12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 30 115 13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 35 116 14. Security Consideration . . . . . . . . . . . . . . . . . . . . 55 117 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 56 118 15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB . . . . . . . 56 119 15.2. IANA Considerations for MPLS-ID-STD-MIB . . . . . . . . . 57 120 15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB . . . . . . . 57 121 15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB . . . . . . . 57 122 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 57 123 16.1. Normative References . . . . . . . . . . . . . . . . . . . 57 124 16.2. Informative References . . . . . . . . . . . . . . . . . 57 125 17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 58 126 18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 58 128 1. Introduction 130 This memo defines a portion of the Management Information Base (MIB) for 131 use with network management protocols in the Internet community. In 132 particular, it describes managed objects of Tunnels, Identifiers, Label 133 Switching Router and Textual conventions for Multiprotocol Label 134 Switching (MPLS) based Transport Profile (TP). These MIB modules extend 135 the existing MPLS MIB objects for both MPLS-TP and Non-MPLS-TP 136 operations, so the MPLS-TP name is not included in the MIB module name. 138 The existing Multiprotocol Label Switching (MPLS) Traffic Engineering 139 (TE) Management Information Base (MIB) [RFC3812] and Generalized 140 Multiprotocol Label Switching (GMPLS) Traffic Engineering Management 141 Information Base [RFC4802] do not support the transport network 142 requirements of NON-IP based management and static bidirectional 143 tunnels. These MIB modules should be used in conjunction with [RFC3812] 144 and companion document [RFC3813] for MPLS-TP tunnel configuration and 145 management. 147 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 148 "SHOULD", "SHOULD NOT", "MAY", and "OPTIONAL" in this document are to be 149 interpreted as described in BCP 14, RFC2119. 151 2. The Internet-Standard Management Framework 153 For a detailed overview of the documents that describe the current 154 Internet-Standard Management Framework, please refer to section 7 of 155 RFC3410 [RFC3410]. 157 Managed objects are accessed via a virtual information store, termed the 158 Management Information Base or MIB. MIB objects are generally accessed 159 through the Simple Network Management Protocol (SNMP). Objects in the 160 MIB are defined using the mechanisms defined in the Structure of 161 Management Information (SMI). This memo specifies a MIB module that is 162 compliant to the SMIv2, which is described in STD 58, RFC2578, STD 58, 163 RFC2579 and STD58, RFC2580. 165 3. Overview 167 3.1. Conventions used in this document 169 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 170 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 171 document are to be interpreted as described in [RFC2119]. 173 3.2. Terminology 174 This document uses terminology from the Multiprotocol Label Switching 175 Architecture [RFC3031], Multiprotocol Label Switching (MPLS) Traffic 176 Engineering (TE) Management Information Base (MIB) [RFC3812], 177 Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) 178 Management Information Base (MIB) [RFC3813] and MPLS Transport Profile 179 (MPLS-TP) Identifiers [RFC6370]. 181 3.3. Acronyms 183 CC: Country Code 184 GMPLS: Generalized Multi-Protocol Label Switching 185 ICC: ITU Carrier Code 186 IP: Internet Protocol 187 ITU: International Telecommunication Union 188 ITU-T: ITU Telecommunication Standardization Sector 189 LSP: Label Switching Path 190 LSR: Label Switching Router 191 MIB: Management Information Base 192 MPLS: Multi-Protocol Label Switching 193 MPLS-TP: MPLS Transport Profile 194 OSPF: Open Shortest Path First 195 PW: Pseudowire 196 TE: Traffic Engineering 197 TP: Transport Profile 199 4. Motivations 201 Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management 202 Information Base (MIB) [RFC3812] provides support for Traffic 203 Engineering tunnels. However, with MPLS-TP, the characteristics of 204 Tunnels were enhanced. For example, MPLS-TP tunnels are bidirectional in 205 nature and could be used in non-IP environments. As the existing MPLS- 206 TE-STD-MIB is not sufficient to capture all the characteristics of the 207 tunnels, enhancing the MIB to support MPLS TP tunnels is required. As 208 most of the attributes of MPLS Traffic Engineering tunnels are also 209 applicable to MPLS-TP tunnels, it is optimal to re-use the existing MIB 210 definition instead of a new MIB. 212 This document defines four MIB modules, namely MPLS-TE-EXT-STD-MIB, 213 MPLS-TC-EXT-STD-MIB, MPLS-ID-STD-MIB and MPLS-LSR-EXT-STD-MIB. As these 214 new MIB modules are required for MPLS-TP functionality, these are 215 retained in the same document, instead of a separate document. 217 5. Feature List 219 The MPLS-TE-EXT-STD-MIB is designed to satisfy the following 220 requirements and constraints: 222 The MIB module supports static and signaling point-to-point, co-routed 223 bi-directional and associated bi-directional tunnels. 225 - The MPLS tunnels need not be interfaces, but it is possible 226 to configure a TP tunnel as an interface. 228 - The mplsTunnelTable [RFC3812] to be also used for MPLS-TP 229 tunnels 231 - The mplsTunnelTable is extended to support MPLS-TP specific 232 objects. 234 - A node configuration table (mplsTunnelExtNodeConfigTable) 235 is used to translate the Global_ID::Node_ID or 236 ICC_Operator_ID::Node_ID to the local identifier in order 237 to index mplsTunnelTable. 239 - The MIB module supports persistent, as well as non-persistent 240 tunnels. 242 6. Brief description of MPLS-TE-EXT-STD-MIB Objects 244 The objects described in this section support the functionality 245 described in documents [RFC5654] and [RFC6370]. The tables support 246 both IP compatible and ICC based tunnel configurations. 248 6.1. mplsTunnelExtNodeConfigTable 250 The mplsTunnelExtNodeConfigTable is used to assign a local identifier 251 for a given ICC_Operator_ID::Node_ID or Global_ID::Node_ID 252 combination as defined in [RFC6923] and [RFC6370] respectively. 253 The CC is a string of two alphabetic characters represented with 254 upper case letters (i.e., A-Z). The ICC is a string of one to six 255 characters, each character being either alphabetic (i.e. A-Z) 256 or numeric (i.e. 0-9) characters. Alphabetic characters in the ICC 257 should be represented with upper case letters. In the IP compatible 258 mode, Global_ID::Node_ID, is used to uniquely identify a node. 260 Each ICC_Operator_ID::Node_ID or Global_ID::Node_ID contains one 261 unique entry in the table representing a node. Every node is assigned 262 a local identifier within a range of 0 to 16777215. This local 263 identifier is used for indexing into mplsTunnelTable as 264 mplsTunnelIngressLSRId and mplsTunnelEgressLSRId. 266 For IP compatible environment, MPLS-TP tunnel is indexed by Tunnel 267 Index, Tunnel Instance, Source Global_ID, Source Node_ID, Destination 268 Global_ID and Destination Node_ID. 270 For ICC based environment, MPLS-TP tunnel is indexed by Tunnel Index, 271 Tunnel Instance, Source CC, Source ICC, Source Node_ID, Destination 272 CC, Destination ICC and Destination Node_ID. 274 As mplsTunnelTable is indexed by mplsTunnelIndex, 275 mplsTunnelInstance, mplsTunnelIngressLSRId, and 276 mplsTunnelEgressLSRId, the MPLS-TP tunnel identifiers cannot be 277 used directly. 279 The mplsTunnelExtNodeConfigTable will be used to store an entry for 280 ICC_Operator_ID::Node_ID or Global_ID::Node_ID with a local 281 identifier to be used as LSR ID in mplsTunnelTable. As the regular TE 282 tunnels use IP address as LSR ID, the local identifier should be 283 below the first valid IP address, which is 16777216[1.0.0.0]. 285 6.2. mplsTunnelExtNodeIpMapTable 287 The read-only mplsTunnelExtNodeIpMaptable is used to query the local 288 identifier assigned and stored in mplsTunnelExtNodeConfigTable for 289 a given Global_ID::Node_ID. In order to query the local identifier, 290 in the IP compatible mode, this table is indexed with 291 Global_ID::Node_ID. In the IP compatible mode for a TP tunnel, 292 Global_ID::Node_ID is used. 294 A separate query is made to get the local identifier of both 295 Ingress and Egress Global_ID::Node_ID identifiers. These local 296 identifiers are used as mplsTunnelIngressLSRId and 297 mplsTunnelEgressLSRId, while indexing mplsTunnelTable. 299 6.3. mplsTunnelExtNodeIccMapTable 301 The read-only mplsTunnelExtNodeIccMapTable is used to query the local 302 identifier assigned and stored in the mplsTunnelExtNodeConfigTable 303 for a given ICC_Operator_ID::Node_ID. 305 A separate query is made to get the local identifier of both 306 Ingress and Egress ICC_Operator_ID::Node_ID. These local identifiers 307 are used as mplsTunnelIngressLSRId and mplsTunnelEgressLSRId, 308 while indexing mplsTunnelTable. 310 6.4. mplsTunnelExtTable 312 mplsTunnelExtTable extends the mplsTunnelTable in order to support 313 MPLS-TP tunnels with additional objects. All the additional 314 attributes specific to supporting TP tunnel are contained in this 315 extended table and could be accessed with the mplsTunnelTable 316 indices. 318 6.5. mplsTunnelExtReversePerfTable 320 This table sparse augments the mplsTunnelTable to provide per-tunnel 321 packet performance information for the reverse direction of a 322 bidirectional tunnel. It can be seen as supplementing the 323 mplsTunnelPerfTable, which augments the mplsTunnelTable. 325 7. MIB Module Interdependencies 327 This section provides an overview of the relationship between the 328 MPLS-TP TE MIB module and other MPLS MIB modules. 330 The arrows in the following diagram show a 'depends on' 331 relationship. A relationship "MIB module A depends on MIB module B" 332 means that MIB module A uses an object, object identifier, or 333 textual convention defined in MIB module B, or that MIB module A 334 contains a pointer (index or RowPointer) to an object in 335 MIB module B. 337 MPLS-TC-EXT-STD-MIB 338 ^ 339 | 340 | 341 +<---- MPLS-ID-STD-MIB 342 ^ 343 | | 344 +<---- MPLS-TE-EXT-STD-MIB 345 | | 346 | V 347 | MPLS-TE-STD-MIB 348 | | 349 | | 350 | V 351 | MPLS-LSR-STD-MIB 352 | ^ 353 | | 354 | | 355 +------MPLS-LSR-EXT-STD-MIB 357 Thus: 359 - All the new MPLS extension MIB modules depend on 360 MPLS-TC-EXT-STD-MIB. 362 - MPLS-ID-STD-MIB contains references to objects in 363 MPLS-TE-STD-MIB [RFC3812]. 365 - MPLS-TE-EXT-STD-MIB contains references to objects in 366 MPLS-TE-STD-MIB [RFC3812]. 368 - MPLS-LSR-EXT-STD-MIB contains references to objects in 369 MPLS-LSR-STD-MIB [RFC3813]. 371 MPLS-TE-STD-MIB [RFC3812] is extended by MPLS-TE-EXT-STD-MIB 372 MIB module for associating the reverse direction tunnel 373 information. 375 Note that the nature of the 'extends' relationship 376 is a sparse augmentation so that the entry in the 377 mplsTunnelExtTable has the same index values as the in the 378 mplsTunnelTable. 380 MPLS-LSR-STD-MIB [RFC3813] is extended by MPLS-LSR-EXT-STD-MIB 381 MIB module for pointing back to the tunnel entry for easy tunnel 382 access from XC entry. 384 Note that the nature of the 'extends' relationship 385 is a sparse augmentation so that the entry in the 386 mplsXCExtTable has the same index values as the in the mplsXCTable. 388 8. Dependencies between MIB Module Tables 390 The tables in MPLS-TE-EXT-STD-MIB are related as shown on the diagram 391 below. The arrows indicate a reference from one table to another. 393 mplsTunnelExtNodeConfigTable 394 ^ mplsXCExtTable 395 | | ^ 396 | +---------+ | 397 | | | 398 | V V 399 mplsTunnelTable ---->mplsXCTable 400 ^ 401 | 402 | 403 mplsTunnelExtTable 405 An existing mplsTunnelTable uses the mplsTunnelExtNodeConfigTable 406 table to map the Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID 407 with the local number in order to accommodate in the existing tunnel 408 table's ingress/egress LSR-id. 410 New mplsTunnelExtTable table provides the reverse direction LSP 411 information for the existing tunnel table in order to achieve 412 bidirectional LSPs. 414 mplsXCExtTable is extended from mplsLsrXCTable to provide 415 backward reference to tunnel entry. 417 9. Example of MPLS-TP Tunnel Setup 418 In this section, we provide an example of the IP based MPLS-TP 419 bidirectional tunnel setup. This example provides the usage of 420 MPLS-TP Tunnel MIB along with the extended new MIB modules introduced 421 in this document. 423 Do note that a MPLS-TP tunnel could be setup statically as well as 424 signaled via control plane. This example considers accessing MIB 425 objects on a head-end for a static and signaling MPLS-TP tunnels. 426 Only relevant objects which are applicable for MPLS-TP tunnel are 427 illustrated here. 429 In mplsTunnelExtNodeConfigTable: 431 { 432 -- Non-IP Ingress LSR-Id (Index to the table) 433 mplsTunnelExtNodeConfigLocalId = 1, 435 mplsTunnelExtNodeConfigGlobalId = 1234, 436 mplsTunnelExtNodeConfigNodeId = 10, 437 -- Mandatory parameters needed to activate the row go here 438 mplsTunnelExtNodeConfigRowStatus = createAndGo (4) 440 -- Non-IP Egress LSR-Id (Index to the table) 441 mplsTunnelExtNodeConfigLocalId = 2, 442 mplsTunnelExtNodeConfigGlobalId = 1234, 443 mplsTunnelExtNodeConfigNodeId = 20, 444 -- Mandatory parameters needed to activate the row go here 445 mplsTunnelExtNodeConfigRowStatus = createAndGo (4) 446 } 448 This will create an entry in the mplsTunnelExtNodeConfigTable for a 449 Global_ID::Node_ID. A separate entry is made for both Ingress LSR 450 and Egress LSR. 452 The following read-only mplsTunnelExtNodeIpMapTable table is 453 populated automatically upon creating an entry in 454 mplsTunnelExtNodeConfigTable and this table is used to retrieve 455 the local identifier for the given Global_ID::Node_ID. 457 In mplsTunnelExtNodeIpMapTable: 459 { 460 -- Global_ID (Index to the table) 461 mplsTunnelExtNodeIpMapGlobalId = 1234, 462 -- Node Identifier (Index to the table) 463 mplsTunnelExtNodeIpMapNodeId = 10, 464 mplsTunnelExtNodeIpMapLocalId = 1 466 -- Global_ID (Index to the table) 467 mplsTunnelExtNodeIpMapGlobalId = 1234, 468 -- Node Identifier (Index to the table) 469 mplsTunnelExtNodeIpMapNodeId = 20, 470 mplsTunnelExtNodeIpMapLocalId = 2 471 } 473 9.1. Example of MPLS-TP static co-routed bidirectional tunnel setup 475 The following denotes the configured co-routed bidirectional 476 tunnel "head" entry: 478 9.1.1. mplsTunnelEntry 480 In mplsTunnelTable: 482 { 483 mplsTunnelIndex = 1, 484 mplsTunnelInstance = 1, 485 -- Local map number created in mplsTunnelExtNodeConfigTable for 486 -- Ingress LSR-Id 487 mplsTunnelIngressLSRId = 1, 489 -- Local map number created in mplsTunnelExtNodeConfigTable for 490 -- Egress LSR-Id 491 mplsTunnelEgressLSRId = 2, 492 mplsTunnelName = "TP co-routed bidirectional LSP", 493 mplsTunnelDescr = "East to West", 494 mplsTunnelIsIf = true (1), 495 -- RowPointer MUST point to the first accessible column 496 mplsTunnelXCPointer = 497 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1, 498 mplsTunnelSignallingProto = none (1), 499 mplsTunnelSetupPrio = 0, 500 mplsTunnelHoldingPrio = 0, 501 mplsTunnelSessionAttributes = 0, 502 mplsTunnelLocalProtectInUse = false (0), 503 -- RowPointer MUST point to the first accessible column 504 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 505 mplsTunnelInstancePriority = 1, 506 mplsTunnelHopTableIndex = 1, 507 mplsTunnelIncludeAnyAffinity = 0, 508 mplsTunnelIncludeAllAffinity = 0, 509 mplsTunnelExcludeAnyAffinity = 0, 510 mplsTunnelRole = head (1), 511 -- Mandatory parameters needed to activate the row go here 512 mplsTunnelRowStatus = createAndGo (4) 513 } 515 9.1.2. mplsTunnelExtEntry 517 -- An MPLS extension table 518 In mplsTunnelExtTable: 519 { 520 -- This opposite direction tunnel pointer MAY be point to 0.0 521 -- if co-routed bidirectional tunnel is managed by single tunnel 522 -- entry 523 mplsTunnelExtOppositeDirTnlPtr = 0.0 524 -- Set both the Ingress and Egress LocalId objects to TRUE as 525 -- this tunnel entry uses the local identifiers. 526 mplsTunnelExtIngressLSRLocalIdValid = true, 527 mplsTunnelExtEgressLSRLocalIdValid = true 529 } 530 We must next create the appropriate in-segment and out-segment 531 entries. These are done in [RFC3813] using the mplsInSegmentTable and 532 mplsOutSegmentTable. 534 9.1.3. Forward direction mplsOutSegmentEntry 536 For the forward direction. 538 In mplsOutSegmentTable: 539 { 540 mplsOutSegmentIndex = 0x0000001, 541 mplsOutSegmentInterface = 13, -- outgoing interface 542 mplsOutSegmentPushTopLabel = true(1), 543 mplsOutSegmentTopLabel = 22, -- outgoing label 545 -- RowPointer MUST point to the first accessible column. 546 mplsOutSegmentTrafficParamPtr = 0.0, 547 mplsOutSegmentRowStatus = createAndGo (4) 548 } 550 9.1.4. Reverse direction mplsInSegmentEntry 552 For the reverse direction. 554 In mplsInSegmentTable: 555 { 556 mplsInSegmentIndex = 0x0000001 557 mplsInSegmentLabel = 21, -- incoming label 558 mplsInSegmentNPop = 1, 559 mplsInSegmentInterface = 13, -- incoming interface 561 -- RowPointer MUST point to the first accessible column. 562 mplsInSegmentTrafficParamPtr = 0.0, 563 mplsInSegmentRowStatus = createAndGo (4) 564 } 566 Next, two cross-connect entries are created in the mplsXCTable of the 567 MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created 568 segments together. 570 9.1.5. Forward direction mplsXCEntry 572 In mplsXCTable: 573 { 574 mplsXCIndex = 0x01, 575 mplsXCInSegmentIndex = 0x00000000, 576 mplsXCOutSegmentIndex = 0x00000001, 577 mplsXCLspId = 0x0102 -- unique ID 578 -- only a single outgoing label 579 mplsXCLabelStackIndex = 0x00, 580 mplsXCRowStatus = createAndGo(4) 582 } 584 9.1.6. Reverse direction mplsXCEntry 586 In mplsXCTable: 587 { 588 mplsXCIndex = 0x01, 589 mplsXCInSegmentIndex = 0x00000001, 590 mplsXCOutSegmentIndex = 0x00000000, 591 mplsXCLspId = 0x0102 -- unique ID 592 -- only a single outgoing label 593 mplsXCLabelStackIndex = 0x00, 594 mplsXCRowStatus = createAndGo(4) 595 } 597 This table entry is extended by entry in the 598 mplsXCExtTable. Note that the nature of the 'extends' 599 relationship is a sparse augmentation so that the entry in the 600 mplsXCExtTable has the same index values as the entry in 601 the mplsXCTable. 603 9.1.7. Forward direction mplsXCExtEntry 605 In mplsXCExtTable (0x01, 0x00000000, 0x00000001) 606 { 607 -- Back pointer from XC table to Tunnel table 608 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 609 mplsXCExtOppositeDirXCPtr = 610 mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0 611 } 613 9.1.8. Reverse direction mplsXCExtEntry 615 Next for the reverse direction: 617 In mplsXCExtTable (0x01, 0x00000001, 0x00000000) 618 { 619 -- Back pointer from XC table to Tunnel table 620 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 621 mplsXCExtOppositeDirXCPtr = 622 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1 623 } 625 9.1.9. mplsTunnelExtReversePerfTable 626 The mplsTunnelExtReversePerfTable SHOULD be populated incase 627 the single tunnel entry is used for co-routed bidirectional tunnel 628 setup. The mplsTunnelPerfTable will have the forward direction 629 LSP performance counters and mplsTunnelExtReversePerfTable will have 630 the reverse direction LSP performance counters. 632 9.2. Example of MPLS-TP static associated bidirectional tunnel setup 634 The MPLS-TP associated bidirectional tunnel has two different 635 direction tunnels[Forward and Reverse LSPs] and these are 636 associated together using mplsTunnelExtTable. Two different 637 tunnel entries for both forward and reverse direction MAY be used 638 for co-routed bidirectional tunnel as well. 640 The following denotes the configured associated bidirectional forward 641 tunnel "head" entry: 643 9.2.1. Forward direction mplsTunnelEntry 645 In mplsTunnelTable: 647 { 648 mplsTunnelIndex = 1, 649 mplsTunnelInstance = 1, 650 -- Local map number created in mplsTunnelExtNodeConfigTable for 651 -- Ingress LSR-Id 652 mplsTunnelIngressLSRId = 1, 654 -- Local map number created in mplsTunnelExtNodeConfigTable for 655 -- Egress LSR-Id 656 mplsTunnelEgressLSRId = 2, 657 mplsTunnelName = "TP associated bi-directional 658 forward LSP", 659 mplsTunnelDescr = "East to West", 660 mplsTunnelIsIf = true (1), 661 -- RowPointer MUST point to the first accessible column 662 mplsTunnelXCPointer = 663 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1, 664 mplsTunnelSignallingProto = none (1), 665 mplsTunnelSetupPrio = 0, 666 mplsTunnelHoldingPrio = 0, 667 mplsTunnelSessionAttributes = 0, 668 mplsTunnelLocalProtectInUse = false (0), 669 -- RowPointer MUST point to the first accessible column 670 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 671 mplsTunnelInstancePriority = 1, 672 mplsTunnelHopTableIndex = 1, 673 mplsTunnelIncludeAnyAffinity = 0, 674 mplsTunnelIncludeAllAffinity = 0, 675 mplsTunnelExcludeAnyAffinity = 0, 676 mplsTunnelRole = head (1), 677 -- Mandatory parameters needed to activate the row go here 678 mplsTunnelRowStatus = createAndGo (4) 679 } 681 9.2.2. Forward direction mplsTunnelExtEntry 683 For Associated bidirectional forward LSP, 684 In mplsTunnelExtTable: 685 { 686 mplsTunnelExtOppositeDirPtr = mplsTunnelName.2.1.2.1 687 -- Set both the Ingress and Egress LocalId objects to TRUE as 688 -- this tunnel entry uses the local identifiers. 689 mplsTunnelExtIngressLSRLocalIdValid = true, 690 mplsTunnelExtEgressLSRLocalIdValid = true 691 } 693 9.2.3. Forward direction mplsOutSegmentTable 695 For the forward direction. 697 In mplsOutSegmentTable: 698 { 699 mplsOutSegmentIndex = 0x0000001, 700 mplsOutSegmentInterface = 13, -- outgoing interface 701 mplsOutSegmentPushTopLabel = true(1), 702 mplsOutSegmentTopLabel = 22, -- outgoing label 704 -- RowPointer MUST point to the first accessible column. 705 mplsOutSegmentTrafficParamPtr = 0.0, 706 mplsOutSegmentRowStatus = createAndGo (4) 707 } 709 9.2.4. Forward direction mplsXCEntry 711 In mplsXCTable: 712 { 713 mplsXCIndex = 0x01, 714 mplsXCInSegmentIndex = 0x00000000, 715 mplsXCOutSegmentIndex = 0x00000001, 716 mplsXCLspId = 0x0102 -- unique ID 717 -- only a single outgoing label 718 mplsXCLabelStackIndex = 0x00, 719 mplsXCRowStatus = createAndGo(4) 721 } 723 9.2.5. Forward direction mplsXCExtEntry 725 In mplsXCExtTable (0x01, 0x00000000, 0x00000001) 726 { 727 -- Back pointer from XC table to Tunnel table 728 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 729 mplsXCExtOppositeDirXCPtr = 730 mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0 731 } 733 9.2.6. Reverse direction mplsTunnelEntry 735 The following denotes the configured associated bidirectional reverse 736 tunnel "tail" entry: 738 In mplsTunnelTable: 740 { 741 mplsTunnelIndex = 2, 742 mplsTunnelInstance = 1, 743 -- Local map number created in mplsTunnelExtNodeConfigTable for 744 -- Ingress LSR-Id 745 mplsTunnelIngressLSRId = 2, 746 -- Local map number created in mplsTunnelExtNodeConfigTable for 747 -- Egress LSR-Id 748 mplsTunnelEgressLSRId = 1, 749 mplsTunnelName = "TP associated bi-directional 750 reverse LSP", 751 mplsTunnelDescr = "West to East", 752 mplsTunnelIsIf = true (1), 753 -- RowPointer MUST point to the first accessible column 754 mplsTunnelXCPointer = 755 mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0, 756 mplsTunnelSignallingProto = none (1), 757 mplsTunnelSetupPrio = 0, 758 mplsTunnelHoldingPrio = 0, 759 mplsTunnelSessionAttributes = 0, 760 mplsTunnelLocalProtectInUse = false (0), 762 -- RowPointer MUST point to the first accessible column 763 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 764 mplsTunnelInstancePriority = 1, 765 mplsTunnelHopTableIndex = 1, 766 mplsTunnelIncludeAnyAffinity = 0, 767 mplsTunnelIncludeAllAffinity = 0, 768 mplsTunnelExcludeAnyAffinity = 0, 769 mplsTunnelRole = head (1), 770 -- Mandatory parameters needed to activate the row go here 771 mplsTunnelRowStatus = createAndGo (4) 772 } 774 9.2.7. Reverse direction mplsTunnelExtEntry 776 For Associated bidirectional reverse LSP, 777 In mplsTunnelExtTable: 778 { 779 mplsTunnelExtOppositeDirPtr = mplsTunnelName.1.1.1.2 780 -- Set both the Ingress and Egress LocalId objects to TRUE as 781 -- this tunnel entry uses the local identifiers. 782 mplsTunnelExtIngressLSRLocalIdValid = true, 783 mplsTunnelExtEgressLSRLocalIdValid = true 784 } 786 9.2.8. Reverse direction mplsInSegmentEntry 788 We must next create the appropriate in-segment and out-segment 789 entries. These are done in [RFC3813] using the mplsInSegmentTable and 790 mplsOutSegmentTable. 792 In mplsInSegmentTable: 793 { 794 mplsInSegmentIndex = 0x0000001 795 mplsInSegmentLabel = 21, -- incoming label 796 mplsInSegmentNPop = 1, 797 mplsInSegmentInterface = 13, -- incoming interface 799 -- RowPointer MUST point to the first accessible column. 800 mplsInSegmentTrafficParamPtr = 0.0, 801 mplsInSegmentRowStatus = createAndGo (4) 802 } 804 Next, two cross-connect entries are created in the mplsXCTable of the 805 MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created 806 segments together. 808 9.2.9. Reverse direction mplsXCEntry 810 In mplsXCTable: 811 { 812 mplsXCIndex = 0x01, 813 mplsXCInSegmentIndex = 0x00000001, 814 mplsXCOutSegmentIndex = 0x00000000, 815 mplsXCLspId = 0x0102 -- unique ID 816 -- only a single outgoing label 817 mplsXCLabelStackIndex = 0x00, 818 mplsXCRowStatus = createAndGo(4) 819 } 821 This table entry is extended by entry in the 822 mplsXCExtTable. Note that the nature of the 'extends' 823 relationship is a sparse augmentation so that the entry in the 824 mplsXCExtTable has the same index values as the entry in 825 the mplsXCTable. 827 9.2.10. Reverse direction mplsXCExtEntry 829 Next for the reverse direction: 831 In mplsXCExtTable (0x01, 0x00000001, 0x00000000) 832 { 833 -- Back pointer from XC table to Tunnel table 834 mplsXCExtTunnelPointer = mplsTunnelName.2.1.2.1 835 mplsXCExtOppositeDirXCPtr = 836 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1 837 } 839 9.3. Example of MPLS-TP signaling co-routed bidirectional tunnel setup 841 The following denotes the configured co-routed bidirectional 842 tunnel "head" entry and in intermediate and tail-end nodes, 843 the tunnel table and its associated tables are created 844 by the local management subsystem (e.g. agent) when the MPLS TP 845 tunnel is signaled successfully. Refer [RFC3812] and [RFC4802] 846 for signaling tunnel table configuration examples. 848 9.3.1. mplsTunnelEntry 850 In mplsTunnelTable: 852 { 853 mplsTunnelIndex = 1, 854 mplsTunnelInstance = 0, 855 -- Local map number created in mplsTunnelExtNodeConfigTable for 856 -- Ingress LSR-Id, for the intermediate and tail-end nodes, 857 -- the local management entity is expected to pick a first available 858 -- local identifier which is not used in mplsTunnelTable. 859 mplsTunnelIngressLSRId = 1, 861 -- Local map number created in mplsTunnelExtNodeConfigTable for 862 -- Egress LSR-Id 863 mplsTunnelEgressLSRId = 2, 864 mplsTunnelName = "TP co-routed bidirectional LSP", 865 mplsTunnelDescr = "East to West", 866 mplsTunnelIsIf = true (1), 868 -- RowPointer MUST point to the first accessible column 869 mplsTunnelXCPointer = 870 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1, 871 mplsTunnelSignallingProto = none (1), 872 mplsTunnelSetupPrio = 0, 873 mplsTunnelHoldingPrio = 0, 874 mplsTunnelSessionAttributes = 0, 875 mplsTunnelLocalProtectInUse = false (0), 876 -- RowPointer MUST point to the first accessible column 877 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 878 mplsTunnelInstancePriority = 1, 879 mplsTunnelHopTableIndex = 1, 880 mplsTunnelIncludeAnyAffinity = 0, 881 mplsTunnelIncludeAllAffinity = 0, 882 mplsTunnelExcludeAnyAffinity = 0, 883 mplsTunnelRole = head (1), 884 -- Mandatory parameters needed to activate the row go here 885 mplsTunnelRowStatus = createAndGo (4) 886 } 888 9.3.2. mplsTunnelExtEntry 890 -- An MPLS extension table 891 In mplsTunnelExtTable: 892 { 893 -- This opposite direction tunnel pointer MAY be point to 0.0 894 -- if co-routed bidirectional tunnel is managed by single tunnel 895 -- entry 896 mplsTunnelExtOppositeDirTnlPtr = 0.0 897 -- Set both the Ingress and Egress LocalId objects to TRUE as 898 -- this tunnel entry uses the local identifiers. 899 mplsTunnelExtIngressLSRLocalIdValid = true, 900 mplsTunnelExtEgressLSRLocalIdValid = true 901 } 903 We must next create the appropriate in-segment and out-segment 904 entries. These are done in [RFC3813] using the mplsInSegmentTable and 905 mplsOutSegmentTable. 907 9.3.3. Forward direction mplsOutSegmentEntry 909 The forward direction mplsOutSegmentTable will be populated 910 automatically based on the information received from the signaling 911 protocol. 913 9.3.4. Reverse direction mplsInSegmentEntry 914 The reverse direction mplsOutSegmentTable will be populated 915 automatically based on the information received from the signaling 916 protocol. 918 Next, two cross-connect entries are created in the mplsXCTable of the 919 MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created 920 segments together. 922 9.3.5. Forward direction mplsXCEntry 924 The forward direction mplsXCEntry will be populated as soon as the 925 forward path label information is available. 927 9.3.6. Reverse direction mplsXCEntry 929 The reverse direction mplsXCEntry will be populated as soon as the 930 reverse path label information is available. 932 This table entry is extended by entry in the mplsXCExtTable. Note 933 that the nature of the 'extends' relationship is a sparse 934 augmentation so that the entry in the mplsXCExtTable has the same 935 index values as the entry in the mplsXCTable. 937 9.3.7. Forward direction mplsXCExtEntry 939 Once the forward path information is negotiated using signaling 940 protocol, the forward direction mplsXCExtEntry will be created for 941 associating the opposite direction XC entry and tunnel table entry. 943 9.3.8. Reverse direction mplsXCExtEntry 945 Once the reverse path information is negotiated using signaling 946 protocol, the reverse direction mplsXCExtEntry will be created for 947 associating the opposite direction XC entry and tunnel table entry. 949 9.3.9. mplsTunnelExtReversePerfTable 951 The mplsTunnelExtReversePerfTable SHOULD be populated incase the 952 single tunnel entry is used for co-routed bidirectional tunnel setup. 953 The mplsTunnelPerfTable will have the forward direction LSP 954 performance counters and mplsTunnelExtReversePerfTable will have the 955 reverse direction LSP performance counters. 957 10. MPLS Textual Convention Extension MIB definitions 958 MPLS-TC-EXT-STD-MIB DEFINITIONS ::= BEGIN 960 IMPORTS 961 MODULE-IDENTITY, Unsigned32 962 FROM SNMPv2-SMI -- [RFC2578] 964 TEXTUAL-CONVENTION 965 FROM SNMPv2-TC -- [RFC2579] 967 mplsStdMIB 968 FROM MPLS-TC-STD-MIB -- [RFC3811] 970 ; 972 mplsTcExtStdMIB MODULE-IDENTITY 974 LAST-UPDATED 975 "201311010000Z" -- November 01, 2013 976 ORGANIZATION 977 "Multiprotocol Label Switching (MPLS) Working Group" 978 CONTACT-INFO 979 " 980 Venkatesan Mahalingam 981 Dell Inc, 982 350 Holger way, San Jose, CA, USA 983 Email: venkat.mahalingams@gmail.com 985 Kannan KV Sampath 986 Redeem, 987 India 988 Email: kannankvs@gmail.com 990 Sam Aldrin 991 Huawei Technologies 992 2330 Central Express Way, 993 Santa Clara, CA 95051, USA 994 Email: aldrin.ietf@gmail.com 996 Thomas D. Nadeau 997 Juniper Networks 998 10 Technology Park Drive, 999 Westford, MA 01886 1000 Email: tnadeau@juniper.net 1001 " 1002 DESCRIPTION 1003 "Copyright (c) 2013 IETF Trust and the persons identified 1004 as the document authors. All rights reserved. 1006 This MIB module contains Textual Conventions for 1007 LSPs and PWs of MPLS based transport networks." 1009 -- Revision history. 1011 REVISION 1013 "201311010000Z" -- November 01, 2013 1014 DESCRIPTION 1015 "MPLS Textual Convention Extensions" 1017 ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value 1019 MplsGlobalId ::= TEXTUAL-CONVENTION 1021 STATUS current 1022 DESCRIPTION 1023 "This object contains the Textual Convention of IP based 1024 operator unique identifier (Global_ID), the Global_ID can 1025 contain the 2-octet or 4-octet value of the operator's 1026 Autonomous System Number (ASN). 1028 It is expected that the Global_ID will be derived from 1029 the globally unique ASN of the autonomous system hosting 1030 the PEs containing the actual AIIs. 1031 The presence of a Global_ID based on the operator's 1032 ASN ensures that the AII will be globally unique. 1034 When the Global_ID is derived from a 2-octet AS number, 1035 the two high-order octets of this 4-octet identifier 1036 MUST be set to zero. 1037 Further ASN 0 is reserved. A Global_ID of zero means 1038 that no Global_ID is present. Note that a Global_ID of 1039 zero is limited to entities contained within a single 1040 operator and MUST NOT be used across an NNI. 1041 A non-zero Global_ID MUST be derived from an ASN owned by 1042 the operator." 1043 REFERENCE 1044 "MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370] 1045 Section 3" 1046 SYNTAX OCTET STRING (SIZE (4)) 1048 MplsCcId ::= TEXTUAL-CONVENTION 1049 STATUS current 1050 DESCRIPTION 1051 "The CC (Country Code) is a string of two alphabetic 1052 characters represented with upper case 1053 letters (i.e., A-Z)." 1054 REFERENCE 1055 "MPLS-TP Identifiers Following ITU-T Conventions, 1056 [RFC6923] Section 3" 1057 SYNTAX OCTET STRING (SIZE (2)) 1058 MplsIccId ::= TEXTUAL-CONVENTION 1059 STATUS current 1060 DESCRIPTION 1061 "The ICC is a string of one to six characters, each 1062 character being either alphabetic (i.e. A-Z) or 1063 numeric (i.e. 0-9) characters. 1064 Alphabetic characters in the ICC SHOULD be represented 1065 with upper case letters. The size of the ICC string MUST be 1066 zero if the ICC identifier is invalid." 1067 REFERENCE 1068 "MPLS-TP Identifiers Following ITU-T Conventions, 1069 [RFC6923] Section 3" 1070 SYNTAX OCTET STRING (SIZE (0|1..6)) 1072 MplsNodeId ::= TEXTUAL-CONVENTION 1073 DISPLAY-HINT "d" 1074 STATUS current 1075 DESCRIPTION 1076 "The Node_ID is assigned within the scope of 1077 the Global_ID/ICC_Operator_ID. 1078 The value 0(or 0.0.0.0 in dotted decimal notation) is 1079 reserved and MUST NOT be used. 1081 When IPv4 addresses are in use, the value of this object 1082 can be derived from the LSR's IPv4 loop back address. 1083 When IPv6 addresses are in use, the value of this object 1084 can be a 32-bit value unique within the scope of 1085 a Global_ID. 1087 Note that, when IP reach ability is not needed, the 32-bit 1088 Node_ID is not required to have any association 1089 with the IPv4 address space." 1090 REFERENCE 1091 "MPLS Transport Profile (MPLS-TP) Identifiers, [RFC6370] 1092 Section 4" 1093 SYNTAX Unsigned32 (0|1..4294967295) 1095 -- MPLS-TC-EXT-STD-MIB module ends 1096 END 1098 11. MPLS Identifier MIB definitions 1100 MPLS-ID-STD-MIB DEFINITIONS ::= BEGIN 1102 IMPORTS 1103 MODULE-IDENTITY, OBJECT-TYPE 1104 FROM SNMPv2-SMI -- [RFC2578] 1105 MODULE-COMPLIANCE, OBJECT-GROUP 1106 FROM SNMPv2-CONF -- [RFC2580] 1107 mplsStdMIB 1108 FROM MPLS-TC-STD-MIB -- [RFC3811] 1109 MplsGlobalId, MplsCcId, MplsIccId, MplsNodeId 1110 FROM MPLS-TC-EXT-STD-MIB 1111 ; 1113 mplsIdStdMIB MODULE-IDENTITY 1114 LAST-UPDATED 1115 "201311010000Z" -- November 01, 2013 1116 ORGANIZATION 1117 "Multiprotocol Label Switching (MPLS) Working Group" 1119 CONTACT-INFO 1120 " 1121 Venkatesan Mahalingam 1122 Dell Inc, 1123 350 Holger way, San Jose, CA, USA 1124 Email: venkat.mahalingams@gmail.com 1126 Kannan KV Sampath 1128 Redeem, 1129 India 1130 Email: kannankvs@gmail.com 1132 Sam Aldrin 1133 Huawei Technologies 1134 2330 Central Express Way, 1135 Santa Clara, CA 95051, USA 1136 Email: aldrin.ietf@gmail.com 1138 Thomas D. Nadeau 1139 Juniper Networks 1140 10 Technology Park Drive, 1141 Westford, MA 01886 1142 Email: tnadeau@juniper.net 1143 " 1144 DESCRIPTION 1145 "Copyright (c) 2013 IETF Trust and the persons identified 1146 as the document authors. All rights reserved. 1148 This MIB module contains generic object definitions for 1149 MPLS Traffic Engineering in transport networks." 1151 -- Revision history. 1153 REVISION 1154 "201311010000Z" -- November 01, 2013 1155 DESCRIPTION 1156 "This MIB modules defines the MIB objects for MPLS-TP 1157 identifiers" 1159 ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value 1161 -- notifications 1162 mplsIdNotifications OBJECT IDENTIFIER ::= { mplsIdStdMIB 0 } 1163 -- tables, scalars 1164 mplsIdObjects OBJECT IDENTIFIER ::= { mplsIdStdMIB 1 } 1165 -- conformance 1166 mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 2 } 1168 -- MPLS common objects 1170 mplsIdGlobalId OBJECT-TYPE 1171 SYNTAX MplsGlobalId 1172 MAX-ACCESS read-write 1173 STATUS current 1174 DESCRIPTION 1175 "This object allows the operator to assign a unique 1176 operator identifier also called MPLS-TP Global_ID. 1177 If this value is used in mplsTunnelExtNodeConfigGlobalId 1178 for mapping Global_ID::Node_ID with the local identifier 1179 then this object value SHOULD NOT be changed." 1180 ::= { mplsIdObjects 1 } 1182 mplsIdNodeId OBJECT-TYPE 1183 SYNTAX MplsNodeId 1184 MAX-ACCESS read-write 1185 STATUS current 1186 DESCRIPTION 1187 "This object allows the operator or service provider to 1188 assign a unique MPLS-TP Node_ID. 1190 The Node_ID is assigned within the scope of 1191 the Global_ID/ICC_Operator_ID. 1193 If this value is used in mplsTunnelExtNodeConfigNodeId 1194 for mapping Global_ID::Node_ID with the local identifier 1195 then this object value SHOULD NOT be changed. 1196 If this value is used in mplsTunnelExtNodeConfigNodeId 1197 for mapping ICC_Operator_ID::Node_ID with the local 1198 identifier then this object value SHOULD NOT be changed." 1199 ::= { mplsIdObjects 2 } 1201 mplsIdCc OBJECT-TYPE 1202 SYNTAX MplsCcId 1203 MAX-ACCESS read-write 1204 STATUS current 1205 DESCRIPTION 1206 "This object allows the operator or service provider to 1207 assign a unique Country Code (CC). Global uniqueness is 1208 assured by concatenating the ICC with a 1209 Country Code (CC). 1210 If this value is used in mplsTunnelExtNodeConfigCcId 1211 for mapping ICC_Operator_ID::Node_ID with the local 1212 identifier then this object value SHOULD NOT be changed." 1213 REFERENCE 1214 "MPLS-TP Identifiers Following ITU-T Conventions, 1215 [RFC6923] Section 3" 1216 ::= { mplsIdObjects 3 } 1218 mplsIdIcc OBJECT-TYPE 1219 SYNTAX MplsIccId 1220 MAX-ACCESS read-write 1221 STATUS current 1222 DESCRIPTION 1223 "This object allows the operator or service provider to 1224 assign a unique MPLS-TP ITU-T Carrier Code (ICC) to a 1225 network. Together, the CC and the ICC form 1226 the ICC_Operator_ID as CC::ICC. 1227 If this value is used in mplsTunnelExtNodeConfigIccId 1228 for mapping ICC_Operator_ID::Node_ID with the local 1229 identifier then this object value SHOULD NOT be changed." 1230 REFERENCE 1231 "MPLS-TP Identifiers Following ITU-T Conventions, 1232 [RFC6923] Section 3" 1233 ::= { mplsIdObjects 4 } 1235 -- Module compliance. 1237 mplsIdCompliances 1238 OBJECT IDENTIFIER ::= { mplsIdConformance 1 } 1240 mplsIdGroups 1241 OBJECT IDENTIFIER ::= { mplsIdConformance 2 } 1243 -- Compliance requirement for fully compliant implementations. 1245 mplsIdModuleFullCompliance MODULE-COMPLIANCE 1246 STATUS current 1247 DESCRIPTION 1248 "Compliance statement for agents that provide full 1249 support the MPLS-ID-STD-MIB module." 1251 MODULE -- this module 1253 -- The mandatory group has to be implemented by all 1254 -- LSRs that originate/terminate MPLS-TP paths. 1256 MANDATORY-GROUPS { 1257 mplsIdScalarGroup 1258 } 1260 ::= { mplsIdCompliances 1 } 1262 -- Compliance requirement for read-only implementations. 1264 mplsIdModuleReadOnlyCompliance MODULE-COMPLIANCE 1265 STATUS current 1266 DESCRIPTION 1267 "Compliance statement for agents that only provide 1268 read-only support for the MPLS-ID-STD-MIB module." 1270 MODULE -- this module 1272 MANDATORY-GROUPS { 1273 mplsIdScalarGroup 1274 } 1276 OBJECT mplsIdGlobalId 1277 MIN-ACCESS read-only 1278 DESCRIPTION 1279 "Write access is not required." 1281 OBJECT mplsIdNodeId 1282 MIN-ACCESS read-only 1283 DESCRIPTION 1284 "Write access is not required." 1286 OBJECT mplsIdIcc 1287 MIN-ACCESS read-only 1288 DESCRIPTION 1289 "Write access is not required." 1291 OBJECT mplsIdCc 1292 MIN-ACCESS read-only 1293 DESCRIPTION 1294 "Write access is not required." 1296 ::= { mplsIdCompliances 2 } 1298 -- Units of conformance. 1300 mplsIdScalarGroup OBJECT-GROUP 1301 OBJECTS { mplsIdGlobalId, 1302 mplsIdNodeId, 1303 mplsIdIcc, 1304 mplsIdCc 1306 } 1307 STATUS current 1308 DESCRIPTION 1309 "Scalar object needed to implement MPLS TP path." 1310 ::= { mplsIdGroups 1 } 1312 -- MPLS-ID-STD-MIB module ends 1313 END 1315 12. MPLS LSR Extension MIB definitions 1317 MPLS-LSR-EXT-STD-MIB DEFINITIONS ::= BEGIN 1319 IMPORTS 1320 MODULE-IDENTITY, OBJECT-TYPE 1321 FROM SNMPv2-SMI -- [RFC2578] 1322 MODULE-COMPLIANCE, OBJECT-GROUP 1323 FROM SNMPv2-CONF -- [RFC2580] 1324 mplsStdMIB 1325 FROM MPLS-TC-STD-MIB -- [RFC3811] 1326 RowPointer 1327 FROM SNMPv2-TC -- [RFC2579] 1328 mplsXCIndex, mplsXCInSegmentIndex, mplsXCOutSegmentIndex, 1329 mplsInterfaceGroup, mplsInSegmentGroup, mplsOutSegmentGroup, 1330 mplsXCGroup, mplsPerfGroup, mplsLsrNotificationGroup 1331 FROM MPLS-LSR-STD-MIB; -- [RFC3813] 1333 mplsLsrExtStdMIB MODULE-IDENTITY 1334 LAST-UPDATED 1335 "201311010000Z" -- November 01, 2013 1336 ORGANIZATION 1337 "Multiprotocol Label Switching (MPLS) Working Group" 1338 CONTACT-INFO 1339 " 1340 Venkatesan Mahalingam 1341 Dell Inc, 1342 350 Holger way, San Jose, CA, USA 1343 Email: venkat.mahalingams@gmail.com 1345 Kannan KV Sampath 1346 Redeem, 1347 India 1348 Email: kannankvs@gmail.com 1350 Sam Aldrin 1351 Huawei Technologies 1352 2330 Central Express Way, 1353 Santa Clara, CA 95051, USA 1355 Email: aldrin.ietf@gmail.com 1357 Thomas D. Nadeau 1358 Juniper Networks 1359 10 Technology Park Drive, Westford, MA 01886 1360 Email: tnadeau@juniper.net 1361 " 1362 DESCRIPTION 1364 "Copyright (c) 2013 IETF Trust and the persons identified 1365 as the document authors. All rights reserved. 1367 This MIB module contains generic object definitions for 1369 MPLS LSR in transport networks." 1371 -- Revision history. 1373 REVISION 1374 "201311010000Z" -- November 01, 2013 1375 DESCRIPTION 1376 "MPLS LSR specific MIB objects extension" 1378 ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value 1380 -- notifications 1381 mplsLsrExtNotifications OBJECT IDENTIFIER ::= { mplsLsrExtStdMIB 0 } 1383 -- tables, scalars 1384 mplsLsrExtObjects OBJECT IDENTIFIER 1385 ::= { mplsLsrExtStdMIB 1 } 1386 -- conformance 1387 mplsLsrExtConformance OBJECT IDENTIFIER 1388 ::= { mplsLsrExtStdMIB 2 } 1390 -- MPLS LSR common objects 1391 mplsXCExtTable OBJECT-TYPE 1392 SYNTAX SEQUENCE OF MplsXCExtEntry 1393 MAX-ACCESS not-accessible 1394 STATUS current 1395 DESCRIPTION 1396 "This table sparse augments the mplsXCTable of 1397 MPLS-LSR-STD-MIB [RFC3813] to provide MPLS-TP specific 1398 information about associated tunnel information" 1399 REFERENCE 1400 "1. Multiprotocol Label Switching (MPLS) Label Switching 1401 Router (LSR) Management Information Base (MIB), RFC 3813." 1402 ::= { mplsLsrExtObjects 1 } 1404 mplsXCExtEntry OBJECT-TYPE 1405 SYNTAX MplsXCExtEntry 1406 MAX-ACCESS not-accessible 1408 STATUS current 1409 DESCRIPTION 1411 "An entry in this table extends the cross connect 1412 information represented by an entry in 1413 the mplsXCTable in MPLS-LSR-STD-MIB [RFC3813] through 1414 a sparse augmentation. An entry can be created by 1415 a network operator via SNMP SET commands, or in 1416 response to signaling protocol events." 1417 REFERENCE 1418 "1. Multiprotocol Label Switching (MPLS) Label Switching 1419 Router (LSR) Management Information Base (MIB), RFC 3813." 1421 INDEX { mplsXCIndex, mplsXCInSegmentIndex, 1422 mplsXCOutSegmentIndex } 1423 ::= { mplsXCExtTable 1 } 1425 MplsXCExtEntry ::= SEQUENCE { 1426 mplsXCExtTunnelPointer RowPointer, 1427 mplsXCExtOppositeDirXCPtr RowPointer 1428 } 1430 mplsXCExtTunnelPointer OBJECT-TYPE 1431 SYNTAX RowPointer 1432 MAX-ACCESS read-only 1433 STATUS current 1434 DESCRIPTION 1435 "This read-only object indicates the back pointer to 1436 the tunnel entry segment. 1437 The only valid value for Tunnel Pointer is 1438 mplsTunnelTable entry." 1439 REFERENCE 1440 "1. Multiprotocol Label Switching (MPLS) Label Switching 1441 Router (LSR) Management Information Base (MIB), RFC 3813." 1442 ::= { mplsXCExtEntry 1 } 1444 mplsXCExtOppositeDirXCPtr OBJECT-TYPE 1445 SYNTAX RowPointer 1446 MAX-ACCESS read-create 1447 STATUS current 1448 DESCRIPTION 1449 "This object indicates the pointer to the opposite 1450 direction XC entry. This object cannot be modified if 1451 mplsXCRowStatus for the corresponding entry in the 1452 mplsXCTable is active(1)." 1453 REFERENCE 1454 "1. Multiprotocol Label Switching (MPLS) Label Switching 1455 Router (LSR) Management Information Base (MIB), RFC 3813." 1456 ::= { mplsXCExtEntry 2 } 1458 mplsLsrExtCompliances 1459 OBJECT IDENTIFIER ::= { mplsLsrExtConformance 1 } 1461 mplsLsrExtGroups 1462 OBJECT IDENTIFIER ::= { mplsLsrExtConformance 2 } 1464 -- Compliance requirement for fully compliant implementations. 1466 mplsLsrExtModuleFullCompliance MODULE-COMPLIANCE 1467 STATUS current 1468 DESCRIPTION 1469 "Compliance statement for agents that provide full support 1470 for MPLS-LSR-EXT-STD-MIB. 1471 The mandatory group has to be implemented by all LSRs 1472 that originate, terminate, or act as transit for 1473 TE-LSPs/tunnels. 1474 In addition, depending on the type of tunnels supported, 1475 other groups become mandatory as explained below." 1477 MODULE MPLS-LSR-STD-MIB -- The MPLS-LSR-STD-MIB, RFC3813 1479 MANDATORY-GROUPS { 1480 mplsInSegmentGroup, 1481 mplsOutSegmentGroup, 1482 mplsXCGroup, 1483 mplsPerfGroup, 1484 mplsLsrNotificationGroup 1485 } 1487 MODULE -- this module 1489 MANDATORY-GROUPS { 1490 mplsXCExtGroup 1491 } 1493 ::= { mplsLsrExtCompliances 1 } 1495 -- Compliance requirement for implementations that provide 1496 -- read-only access. 1498 mplsLsrExtModuleReadOnlyCompliance MODULE-COMPLIANCE 1499 STATUS current 1500 DESCRIPTION 1501 "Compliance requirement for implementations that only 1502 provide read-only support for MPLS-LSR-EXT-STD-MIB. 1503 Such devices can then be monitored but cannot be 1504 configured using this MIB module." 1506 MODULE MPLS-LSR-STD-MIB 1508 MANDATORY-GROUPS { 1509 mplsInterfaceGroup, 1510 mplsInSegmentGroup, 1511 mplsOutSegmentGroup, 1512 mplsPerfGroup 1513 } 1515 MODULE -- this module 1517 GROUP mplsXCExtReadOnlyObjectsGroup 1518 DESCRIPTION 1519 "This group is mandatory for devices which support 1520 Opposite direction XC configuration of tunnels." 1522 -- mplsXCExtTable 1523 OBJECT mplsXCExtOppositeDirXCPtr 1524 MIN-ACCESS read-only 1525 DESCRIPTION 1526 "Write access is not required. 1527 This object indicates the pointer to the opposite 1528 direction XC entry. The only valid value for XC 1529 Pointer is mplsXCTable entry." 1530 ::= { mplsLsrExtCompliances 2 } 1532 -- Units of conformance. 1534 mplsXCExtGroup OBJECT-GROUP 1535 OBJECTS { 1536 mplsXCExtTunnelPointer, 1537 mplsXCExtOppositeDirXCPtr 1538 } 1539 STATUS current 1540 DESCRIPTION 1541 "This object should be supported in order to access 1542 the tunnel entry from XC entry." 1543 ::= { mplsLsrExtGroups 1 } 1545 mplsXCExtReadOnlyObjectsGroup OBJECT-GROUP 1546 OBJECTS { 1547 mplsXCExtTunnelPointer, 1548 mplsXCExtOppositeDirXCPtr 1549 } 1550 STATUS current 1551 DESCRIPTION 1552 "This Object is needed to associate the opposite direction 1553 (forward/reverse) XC entry." 1554 ::= { mplsLsrExtGroups 2 } 1556 -- MPLS-LSR-EXT-STD-MIB module ends 1557 END 1559 13. MPLS Tunnel Extension MIB definitions 1561 MPLS-TE-EXT-STD-MIB DEFINITIONS ::= BEGIN 1563 IMPORTS 1564 MODULE-IDENTITY, OBJECT-TYPE, Counter32, 1565 Counter64, zeroDotZero 1567 FROM SNMPv2-SMI -- [RFC2578] 1568 MODULE-COMPLIANCE, OBJECT-GROUP 1569 FROM SNMPv2-CONF -- [RFC2580] 1570 TruthValue, RowStatus, RowPointer, StorageType 1571 FROM SNMPv2-TC -- [RFC2579] 1573 MplsGlobalId, MplsNodeId, MplsCcId, MplsIccId 1574 FROM MPLS-TC-EXT-STD-MIB 1575 mplsStdMIB, MplsTunnelIndex, MplsTunnelInstanceIndex, 1576 MplsExtendedTunnelId 1577 FROM MPLS-TC-STD-MIB -- [RFC3811] 1578 mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, 1579 mplsTunnelEgressLSRId 1580 FROM MPLS-TE-STD-MIB -- [RFC3812] 1581 ; 1583 mplsTeExtStdMIB MODULE-IDENTITY 1584 LAST-UPDATED 1585 "201311010000Z" -- November 01, 2013 1586 ORGANIZATION 1587 "Multiprotocol Label Switching (MPLS) Working Group" 1588 CONTACT-INFO 1589 " 1590 Venkatesan Mahalingam 1591 Dell Inc, 1592 350 Holger way, San Jose, CA, USA 1593 Email: venkat.mahalingams@gmail.com 1595 Kannan KV Sampath 1596 Redeem, 1597 India 1598 Email: kannankvs@gmail.com 1600 Sam Aldrin 1601 Huawei Technologies 1602 2330 Central Express Way, 1603 Santa Clara, CA 95051, USA 1604 Email: aldrin.ietf@gmail.com 1606 Thomas D. Nadeau 1607 Juniper Networks 1608 10 Technology Park Drive, Westford, MA 01886 1609 Email: tnadeau@juniper.net 1610 " 1611 DESCRIPTION 1612 "Copyright (c) 2013 IETF Trust and the persons identified 1613 as the document authors. All rights reserved. 1615 This MIB module contains generic object definitions for 1616 MPLS Traffic Engineering in transport networks." 1618 -- Revision history. 1620 REVISION 1621 "201311010000Z" -- November 01, 2013 1623 DESCRIPTION 1624 "MPLS TE MIB objects extension" 1626 ::= { mplsStdMIB xxx } -- xxx to be replaced 1627 -- with correct value 1629 -- Top level components of this MIB module. 1631 -- notifications 1632 mplsTeExtNotifications OBJECT IDENTIFIER ::= { mplsTeExtStdMIB 0 } 1634 -- tables, scalars 1635 mplsTeExtObjects OBJECT IDENTIFIER 1636 ::= { mplsTeExtStdMIB 1 } 1637 -- conformance 1638 mplsTeExtConformance OBJECT IDENTIFIER 1639 ::= { mplsTeExtStdMIB 2 } 1641 -- Start of MPLS Transport Profile Node configuration table 1642 mplsTunnelExtNodeConfigTable OBJECT-TYPE 1643 SYNTAX SEQUENCE OF MplsTunnelExtNodeConfigEntry 1644 MAX-ACCESS not-accessible 1645 STATUS current 1646 DESCRIPTION 1647 "This table allows the operator to map a node or 1648 LSR Identifier (IP compatible [Global_ID::Node_ID] or 1649 ICC based [ICC_Operator_ID::Node_ID]) with a local 1650 identifier. 1652 This table is created to reuse the existing 1653 mplsTunnelTable for MPLS based transport network 1654 tunnels also. 1656 Since the MPLS tunnel's Ingress/Egress LSR identifiers' 1657 size (Unsigned32) value is not compatible for 1658 MPLS-TP tunnel i.e. Global_ID::Node_ID of size 8 bytes and 1659 ICC_Operator_ID::Node_ID of size 12 bytes, there exists a 1660 need to map the Global_ID::Node_ID or ICC_Operator_ID::Node_ID 1661 with the local identifier of size 4 bytes (Unsigned32) value 1662 in order to index (Ingress/Egress LSR identifier) 1663 the existing mplsTunnelTable." 1665 ::= { mplsTeExtObjects 1 } 1667 mplsTunnelExtNodeConfigEntry OBJECT-TYPE 1668 SYNTAX MplsTunnelExtNodeConfigEntry 1669 MAX-ACCESS not-accessible 1670 STATUS current 1671 DESCRIPTION 1672 "An entry in this table represents a mapping 1673 identification for the operator or service provider 1674 with node or LSR. 1676 As per [RFC6370], IP compatible mapping is represented 1677 as Global_ID::Node_ID. 1679 As per [RFC6923], the CC and the ICC form the ICC_Operator_ID 1680 as CC::ICC and ICC compatible mapping is represented 1681 as ICC_Operator_ID::Node_ID. 1683 Note: Each entry in this table should have a unique 1684 [Global_ID and Node_ID] or [CC::ICC and Node_ID] combination." 1685 INDEX { mplsTunnelExtNodeConfigLocalId } 1686 ::= { mplsTunnelExtNodeConfigTable 1 } 1688 MplsTunnelExtNodeConfigEntry ::= SEQUENCE { 1689 mplsTunnelExtNodeConfigLocalId MplsExtendedTunnelId, 1690 mplsTunnelExtNodeConfigGlobalId MplsGlobalId, 1691 mplsTunnelExtNodeConfigCcId MplsCcId, 1692 mplsTunnelExtNodeConfigIccId MplsIccId, 1693 mplsTunnelExtNodeConfigNodeId MplsNodeId, 1694 mplsTunnelExtNodeConfigIccValid TruthValue, 1695 mplsTunnelExtNodeConfigStorageType StorageType, 1696 mplsTunnelExtNodeConfigRowStatus RowStatus 1698 } 1700 mplsTunnelExtNodeConfigLocalId OBJECT-TYPE 1701 SYNTAX MplsExtendedTunnelId 1702 MAX-ACCESS not-accessible 1703 STATUS current 1704 DESCRIPTION 1705 "This object is used in accommodating the bigger 1706 size Global_ID::Node_ID and/or the ICC_Operator_ID::Node_ID 1707 with lower size LSR identifier in order to index 1708 the mplsTunnelTable. 1710 The Local Identifier is configured between 0 and 16777215, 1711 as valid IP address range starts from 16777216(01.00.00.00). 1712 This range is chosen to identify the mplsTunnelTable's 1713 Ingress/Egress LSR-id is IP address or Local identifier, 1714 if the configured range is not IP address, operator is 1715 expected to retrieve the complete information 1716 (Global_ID::Node_ID or ICC_Operator_ID::Node_ID) from 1717 mplsTunnelExtNodeConfigTable. 1718 This way, existing mplsTunnelTable is reused for 1719 bidirectional tunnel extensions for MPLS based transport 1720 networks. 1722 This Local Identifier allows the operator to assign 1723 a unique identifier to map Global_ID::Node_ID and/or 1724 ICC_Operator_ID::Node_ID. As this Local Identifier is unique 1725 within the node and the same syntax of this object can be 1726 used for MPLS TE tunnel also, it is up to the operator/local 1727 management entity to choose the non-conflicting value for 1728 indexing the MPLS and MPLS-TP tunnel entries." 1729 ::= { mplsTunnelExtNodeConfigEntry 1 } 1731 mplsTunnelExtNodeConfigGlobalId OBJECT-TYPE 1732 SYNTAX MplsGlobalId 1733 MAX-ACCESS read-create 1734 STATUS current 1735 DESCRIPTION 1736 "This object indicates the Global Operator Identifier. 1737 This object has no meaning when 1738 mplsTunnelExtNodeConfigIccValid is set true." 1739 REFERENCE 1740 "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370] 1741 Section 3." 1742 ::= { mplsTunnelExtNodeConfigEntry 2 } 1744 mplsTunnelExtNodeConfigCcId OBJECT-TYPE 1745 SYNTAX MplsCcId 1746 MAX-ACCESS read-create 1747 STATUS current 1748 DESCRIPTION 1749 "This object allows the operator or service provider to 1750 configure a unique MPLS-TP ITU-T Country Code (CC) 1751 either for Ingress ID or Egress ID. 1753 This object has no meaning when 1754 mplsTunnelExtNodeConfigIccValid is set false." 1755 REFERENCE 1756 "MPLS-TP Identifiers Following ITU-T Conventions, 1757 [RFC6923] Section 3" 1758 ::= { mplsTunnelExtNodeConfigEntry 3 } 1760 mplsTunnelExtNodeConfigIccId OBJECT-TYPE 1761 SYNTAX MplsIccId 1762 MAX-ACCESS read-create 1763 STATUS current 1764 DESCRIPTION 1765 "This object allows the operator or service provider to 1766 configure a unique MPLS-TP ITU-T Carrier Code (ICC) 1767 either for Ingress ID or Egress ID. 1769 This object has no meaning when 1770 mplsTunnelExtNodeConfigIccValid is set false." 1771 REFERENCE 1772 "MPLS-TP Identifiers Following ITU-T Conventions, 1773 [RFC6923] Section 3" 1774 ::= { mplsTunnelExtNodeConfigEntry 4 } 1776 mplsTunnelExtNodeConfigNodeId OBJECT-TYPE 1777 SYNTAX MplsNodeId 1778 MAX-ACCESS read-create 1779 STATUS current 1780 DESCRIPTION 1781 "This object indicates the Node_ID within the scope 1782 of a Global_ID or ICC_Operator_ID." 1783 REFERENCE 1784 "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370] 1785 Section 4." 1786 ::= { mplsTunnelExtNodeConfigEntry 5 } 1788 mplsTunnelExtNodeConfigIccValid OBJECT-TYPE 1789 SYNTAX TruthValue 1790 MAX-ACCESS read-create 1791 STATUS current 1792 DESCRIPTION 1793 "Denotes whether or not this entry uses 1794 mplsTunnelExtNodeConfigCcId, 1795 mplsTunnelExtNodeConfigIccId and 1796 mplsTunnelExtNodeConfigNodeId for mapping 1797 the ICC based identifiers with the local identifier. 1798 Note that if this variable is set to false then the 1799 mplsTunnelExtNodeConfigGlobalId and 1800 mplsTunnelExtNodeConfigNodeId objects should have 1801 the valid information." 1802 DEFVAL { false } 1803 ::= { mplsTunnelExtNodeConfigEntry 6 } 1805 mplsTunnelExtNodeConfigStorageType OBJECT-TYPE 1806 SYNTAX StorageType 1807 MAX-ACCESS read-create 1808 STATUS current 1809 DESCRIPTION 1810 "This variable indicates the storage type for this 1811 object. 1812 Conceptual rows having the value 'permanent' 1813 need not allow write-access to any columnar 1814 objects in the row." 1815 DEFVAL { volatile } 1816 ::= { mplsTunnelExtNodeConfigEntry 7 } 1818 mplsTunnelExtNodeConfigRowStatus OBJECT-TYPE 1819 SYNTAX RowStatus 1820 MAX-ACCESS read-create 1821 STATUS current 1822 DESCRIPTION 1823 "This object allows the operator to create, modify, 1824 and/or delete a row in this table." 1825 ::= { mplsTunnelExtNodeConfigEntry 8 } 1827 -- End of MPLS Transport Profile Node configuration table 1829 -- Start of MPLS Transport Profile Node IP compatible 1830 -- mapping table 1832 mplsTunnelExtNodeIpMapTable OBJECT-TYPE 1833 SYNTAX SEQUENCE OF MplsTunnelExtNodeIpMapEntry 1835 MAX-ACCESS not-accessible 1836 STATUS current 1837 DESCRIPTION 1838 "This read-only table allows the operator to retrieve 1839 the local identifier for a given Global_ID::Node_ID in an IP 1840 compatible operator environment. 1842 This table MAY be used in on-demand and/or proactive 1844 OAM operations to get the Ingress/Egress LSR identifier 1845 (Local Identifier) from Src-Global_Node_ID 1846 or Dst-Global_Node_ID and the Ingress and Egress LSR 1847 identifiers are used to retrieve the tunnel entry. 1849 This table returns nothing when the associated entry 1850 is not defined in mplsTunnelExtNodeConfigTable." 1851 ::= { mplsTeExtObjects 2 } 1853 mplsTunnelExtNodeIpMapEntry OBJECT-TYPE 1854 SYNTAX MplsTunnelExtNodeIpMapEntry 1855 MAX-ACCESS not-accessible 1856 STATUS current 1857 DESCRIPTION 1858 "An entry in this table represents a mapping of 1859 Global_ID::Node_ID with the local identifier. 1861 An entry in this table is created automatically when 1862 the Local identifier is associated with Global_ID and 1863 Node_Id in the mplsTunnelExtNodeConfigTable. 1865 Note: Each entry in this table should have a unique 1866 Global_ID and Node_ID combination." 1867 INDEX { mplsTunnelExtNodeIpMapGlobalId, 1868 mplsTunnelExtNodeIpMapNodeId 1869 } 1870 ::= { mplsTunnelExtNodeIpMapTable 1 } 1872 MplsTunnelExtNodeIpMapEntry ::= SEQUENCE { 1873 mplsTunnelExtNodeIpMapGlobalId MplsGlobalId, 1874 mplsTunnelExtNodeIpMapNodeId MplsNodeId, 1875 mplsTunnelExtNodeIpMapLocalId MplsExtendedTunnelId 1876 } 1878 mplsTunnelExtNodeIpMapGlobalId OBJECT-TYPE 1879 SYNTAX MplsGlobalId 1880 MAX-ACCESS not-accessible 1881 STATUS current 1882 DESCRIPTION 1883 "This object indicates the Global_ID." 1884 ::= { mplsTunnelExtNodeIpMapEntry 1 } 1886 mplsTunnelExtNodeIpMapNodeId OBJECT-TYPE 1887 SYNTAX MplsNodeId 1888 MAX-ACCESS not-accessible 1889 STATUS current 1890 DESCRIPTION 1891 "This object indicates the Node_ID within the 1893 operator." 1894 ::= { mplsTunnelExtNodeIpMapEntry 2 } 1896 mplsTunnelExtNodeIpMapLocalId OBJECT-TYPE 1897 SYNTAX MplsExtendedTunnelId 1898 MAX-ACCESS read-only 1899 STATUS current 1900 DESCRIPTION 1901 "This object contains an IP compatible local identifier 1902 which is defined in mplsTunnelExtNodeConfigTable." 1903 ::= { mplsTunnelExtNodeIpMapEntry 3 } 1905 -- End MPLS Transport Profile Node IP compatible table 1907 -- Start of MPLS Transport Profile Node ICC based table 1909 mplsTunnelExtNodeIccMapTable OBJECT-TYPE 1910 SYNTAX SEQUENCE OF MplsTunnelExtNodeIccMapEntry 1911 MAX-ACCESS not-accessible 1912 STATUS current 1913 DESCRIPTION 1914 "This read-only table allows the operator to retrieve 1915 the local identifier for a given ICC_Operator_ID::Node_ID 1916 in an ICC operator environment. 1918 This table MAY be used in on-demand and/or proactive 1919 OAM operations to get the Ingress/Egress LSR 1920 identifier (Local Identifier) from Src-ICC 1921 or Dst-ICC and the Ingress and Egress LSR 1922 identifiers are used to retrieve the tunnel entry. 1923 This table returns nothing when the associated entry 1924 is not defined in mplsTunnelExtNodeConfigTable." 1925 ::= { mplsTeExtObjects 3 } 1927 mplsTunnelExtNodeIccMapEntry OBJECT-TYPE 1928 SYNTAX MplsTunnelExtNodeIccMapEntry 1929 MAX-ACCESS not-accessible 1930 STATUS current 1931 DESCRIPTION 1932 "An entry in this table represents a mapping of 1933 ICC_Operator_ID::Node_ID with the local identifier. 1935 An entry in this table is created automatically when 1936 the Local identifier is associated with 1937 ICC_Operator_ID::Node_ID in 1938 the mplsTunnelExtNodeConfigTable." 1939 INDEX { mplsTunnelExtNodeIccMapCcId, 1940 mplsTunnelExtNodeIccMapIccId, 1941 mplsTunnelExtNodeIccMapNodeId } 1942 ::= { mplsTunnelExtNodeIccMapTable 1 } 1944 MplsTunnelExtNodeIccMapEntry ::= SEQUENCE { 1945 mplsTunnelExtNodeIccMapCcId MplsCcId, 1946 mplsTunnelExtNodeIccMapIccId MplsIccId, 1947 mplsTunnelExtNodeIccMapNodeId MplsNodeId, 1948 mplsTunnelExtNodeIccMapLocalId MplsExtendedTunnelId 1949 } 1951 mplsTunnelExtNodeIccMapCcId OBJECT-TYPE 1952 SYNTAX MplsCcId 1953 MAX-ACCESS not-accessible 1954 STATUS current 1955 DESCRIPTION 1956 "This object allows the operator or service provider to 1957 configure a unique MPLS-TP ITU-T Country Code (CC) 1958 either for Ingress or Egress LSR ID. 1960 The CC is a string of two alphabetic characters 1961 represented with upper case letters (i.e., A-Z)." 1962 ::= { mplsTunnelExtNodeIccMapEntry 1 } 1964 mplsTunnelExtNodeIccMapIccId OBJECT-TYPE 1965 SYNTAX MplsIccId 1966 MAX-ACCESS not-accessible 1967 STATUS current 1968 DESCRIPTION 1969 "This object allows the operator or service provider 1970 to configure a unique MPLS-TP ITU-T Carrier 1971 Code (ICC) either for Ingress or Egress LSR ID. 1973 The ICC is a string of one to six characters, each 1974 character being either alphabetic (i.e. A-Z) or 1975 numeric (i.e. 0-9) characters. Alphabetic characters 1976 in the ICC should be represented with upper case 1977 letters." 1978 ::= { mplsTunnelExtNodeIccMapEntry 2 } 1980 mplsTunnelExtNodeIccMapNodeId OBJECT-TYPE 1981 SYNTAX MplsNodeId 1982 MAX-ACCESS not-accessible 1983 STATUS current 1984 DESCRIPTION 1985 "This object indicates the Node_ID within the 1986 ICC based operator." 1987 ::= { mplsTunnelExtNodeIccMapEntry 3} 1989 mplsTunnelExtNodeIccMapLocalId OBJECT-TYPE 1990 SYNTAX MplsExtendedTunnelId 1991 MAX-ACCESS read-only 1992 STATUS current 1993 DESCRIPTION 1994 "This object contains an ICC based local identifier 1995 which is defined in mplsTunnelExtNodeConfigTable." 1996 ::= { mplsTunnelExtNodeIccMapEntry 4 } 1998 -- End MPLS Transport Profile Node ICC based table 1999 -- Start of MPLS Tunnel table extension 2001 mplsTunnelExtTable OBJECT-TYPE 2002 SYNTAX SEQUENCE OF MplsTunnelExtEntry 2003 MAX-ACCESS not-accessible 2004 STATUS current 2005 DESCRIPTION 2006 "This table represents extensions to mplsTunnelTable 2007 in order to support MPLS-TP tunnels. 2009 As per MPLS-TP Identifiers [RFC6370], LSP_ID for IP based 2010 co-routed bidirectional tunnel, 2012 A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: 2013 Node_ID::Tunnel_Num}::LSP_Num 2015 LSP_ID for IP based associated bidirectional tunnel, 2016 A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: 2017 Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num} 2019 mplsTunnelTable is reused for forming the LSP_ID 2020 as follows, 2022 Source Tunnel_Num is mapped with mplsTunnelIndex, 2023 Source Node_ID is mapped with 2024 mplsTunnelIngressLSRId, Destination Node_ID is 2025 mapped with mplsTunnelEgressLSRId LSP_Num is mapped with 2026 mplsTunnelInstance. 2028 Source Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID and 2029 Destination Global_ID::Node_ID and/or ICC_Operator_ID::Node-ID 2030 are maintained in the mplsTunnelExtNodeConfigTable and 2031 mplsTunnelExtNodeConfigLocalId is used to create an entry 2032 in mplsTunnelTable." 2033 REFERENCE 2034 "MPLS Transport Profile (MPLS-TP) Identifiers [RFC6370]." 2035 ::= { mplsTeExtObjects 4 } 2037 mplsTunnelExtEntry OBJECT-TYPE 2038 SYNTAX MplsTunnelExtEntry 2039 MAX-ACCESS not-accessible 2040 STATUS current 2041 DESCRIPTION 2042 "An entry in this table represents MPLS-TP 2043 specific additional tunnel configurations." 2044 INDEX { 2045 mplsTunnelIndex, 2046 mplsTunnelInstance, 2047 mplsTunnelIngressLSRId, 2048 mplsTunnelEgressLSRId 2049 } 2050 ::= { mplsTunnelExtTable 1 } 2052 MplsTunnelExtEntry ::= SEQUENCE { 2053 mplsTunnelExtOppositeDirPtr RowPointer, 2054 mplsTunnelExtOppositeDirTnlValid TruthValue, 2055 mplsTunnelExtDestTnlIndex MplsTunnelIndex, 2056 mplsTunnelExtDestTnlLspIndex MplsTunnelInstanceIndex, 2057 mplsTunnelExtDestTnlValid TruthValue, 2058 mplsTunnelExtIngressLSRLocalIdValid TruthValue, 2059 mplsTunnelExtEgressLSRLocalIdValid TruthValue 2061 } 2063 mplsTunnelExtOppositeDirPtr OBJECT-TYPE 2064 SYNTAX RowPointer 2065 MAX-ACCESS read-create 2066 STATUS current 2067 DESCRIPTION 2068 "This object is applicable only for the bidirectional 2069 tunnel that has the forward and reverse LSPs in the 2070 same tunnel or in the different tunnels. 2072 This object holds the opposite direction tunnel entry 2073 if the bidirectional tunnel is setup by configuring two 2074 tunnel entries in mplsTunnelTable. 2076 The value of zeroDotZero indicates single tunnel entry 2077 is used for bidirectional tunnel setup." 2078 DEFVAL { zeroDotZero } 2079 ::= { mplsTunnelExtEntry 1 } 2081 mplsTunnelExtOppositeDirTnlValid OBJECT-TYPE 2082 SYNTAX TruthValue 2083 MAX-ACCESS read-create 2084 STATUS current 2085 DESCRIPTION 2086 "Denotes whether or not this tunnel uses 2087 mplsTunnelExtOppositeDirPtr for identifying the opposite 2088 direction tunnel information. Note that if this variable 2089 is set to true then the mplsTunnelExtOppositeDirPtr should 2090 point to the first accessible row of the opposite 2091 direction tunnel." 2092 DEFVAL { false } 2093 ::= { mplsTunnelExtEntry 2 } 2095 mplsTunnelExtDestTnlIndex OBJECT-TYPE 2096 SYNTAX MplsTunnelIndex 2097 MAX-ACCESS read-create 2098 STATUS current 2099 DESCRIPTION 2100 "This object is applicable only for the bidirectional 2101 tunnel that has the forward and reverse LSPs in the 2102 same tunnel or in the different tunnels. 2104 This object holds the same value as that of the 2105 mplsTunnelIndex of mplsTunnelEntry if the forward and 2106 reverse LSPs are in the same tunnel. Otherwise, 2107 this object holds the value of the other direction 2108 associated LSP's mplsTunnelIndex from a different 2110 tunnel. 2112 The values of this object and the 2113 mplsTunnelExtDestTnlLspIndex object together can be used 2114 to identify an opposite direction LSP i.e. if the 2115 mplsTunnelIndex and mplsTunnelInstance hold the value 2116 for forward LSP, this object and 2117 mplsTunnelExtDestTnlLspIndex can be used to retrieve 2118 the reverse direction LSP and vice versa. 2120 This object and mplsTunnelExtDestTnlLspIndex values 2121 provide the first two indices of tunnel entry and 2122 the remaining indices can be derived as follows, 2123 if both the forward and reverse LSPs are present in 2124 the same tunnel, the opposite direction LSP's Ingress 2125 and Egress Identifier will be same for both the LSPs, 2126 else the Ingress and Egress Identifiers should be 2127 swapped in order to index the other direction tunnel." 2129 ::= { mplsTunnelExtEntry 3 } 2131 mplsTunnelExtDestTnlLspIndex OBJECT-TYPE 2132 SYNTAX MplsTunnelInstanceIndex 2133 MAX-ACCESS read-create 2134 STATUS current 2135 DESCRIPTION 2136 "This object is applicable only for the bidirectional 2137 tunnel that has the forward and reverse LSPs in the 2138 same tunnel or in the different tunnels. 2140 This object should contain different value if both the 2141 forward and reverse LSPs present in the same tunnel. 2143 This object can contain same value or different values 2144 if the forward and reverse LSPs present in the different 2145 tunnels." 2147 ::= { mplsTunnelExtEntry 4 } 2149 mplsTunnelExtDestTnlValid OBJECT-TYPE 2150 SYNTAX TruthValue 2151 MAX-ACCESS read-create 2152 STATUS current 2153 DESCRIPTION 2154 "Denotes whether or not this tunnel uses 2155 mplsTunnelExtDestTnlIndex and 2156 mplsTunnelExtDestTnlLspIndex for identifying 2157 the opposite direction tunnel information. Note that if 2158 this variable is set to true then the 2159 mplsTunnelExtDestTnlIndex and 2160 mplsTunnelExtDestTnlLspIndex objects should have 2161 the valid opposite direction tunnel indices." 2162 DEFVAL { false } 2163 ::= { mplsTunnelExtEntry 5 } 2165 mplsTunnelExtIngressLSRLocalIdValid OBJECT-TYPE 2166 SYNTAX TruthValue 2167 MAX-ACCESS read-create 2168 STATUS current 2169 DESCRIPTION 2170 "This object denotes whether the mplsTunnelIngressLSRId 2171 contains the local value, which is used to reference 2172 the complete Ingress Global_ID::Node_ID or ICC_Operator_ID 2173 from the mplsTunnelExtNodeConfigTable. 2175 If this object is set to FALSE, mplsTunnelExtNodeConfigTable 2176 will not contain an entry to reference local identifier with 2177 Global_ID::Node_ID or ICC_Operator_ID::Node_ID value. 2179 This object is set to FALSE for legacy implementations like 2180 MPLS TE tunnels where mplsTunnelIngressId itself provides 2181 complete Ingress LSRId." 2182 REFERENCE 2183 "MPLS-TE-STD-MIB [RFC3812], Section 11. 2184 mplsTunnelIngressLSRId object in mplsTunnelTable." 2185 DEFVAL { false } 2186 ::= { mplsTunnelExtEntry 6 } 2188 mplsTunnelExtEgressLSRLocalIdValid OBJECT-TYPE 2189 SYNTAX TruthValue 2190 MAX-ACCESS read-create 2191 STATUS current 2192 DESCRIPTION 2193 "This object denotes whether the mplsTunnelEgressLSRId 2194 contains the local value, which is used to reference 2195 the complete Egress Global_ID::Node_ID or 2196 ICC_Operator_ID::Node_ID from 2197 the mplsTunnelExtNodeConfigTable. 2199 If this object is set to FALSE, mplsTunnelExtNodeConfigTable 2200 will not contain an entry to reference local identifier with 2201 Global_ID::Node_ID or ICC_Operator_ID::Node_ID value. 2203 This object is set to FALSE for legacy implementations like 2204 MPLS TE tunnels where mplsTunnelEgressId itself provides 2205 complete Egress LSRId." 2206 REFERENCE 2207 "MPLS-TE-STD-MIB [RFC3812], Section 11. 2208 mplsTunnelEgressLSRId object in mplsTunnelTable." 2209 DEFVAL { false } 2210 ::= { mplsTunnelExtEntry 7 } 2212 -- End of MPLS Tunnel table extension 2213 mplsTunnelExtReversePerfTable OBJECT-TYPE 2214 SYNTAX SEQUENCE OF MplsTunnelExtReversePerfEntry 2215 MAX-ACCESS not-accessible 2216 STATUS current 2217 DESCRIPTION 2218 "This table extends the mplsTunnelTable to provide 2219 per-tunnel packet performance information for the reverse 2220 direction of a bidirectional tunnel. It can be seen as 2221 supplementing the mplsTunnelPerfTable, which augments the 2222 mplsTunnelTable." 2223 REFERENCE 2224 "1. Multiprotocol Label Switching (MPLS) Traffic 2225 Engineering (TE)Management Information Base (MIB), 2226 RFC 3812." 2227 ::= { mplsTeExtObjects 5 } 2229 mplsTunnelExtReversePerfEntry OBJECT-TYPE 2230 SYNTAX MplsTunnelExtReversePerfEntry 2231 MAX-ACCESS not-accessible 2232 STATUS current 2233 DESCRIPTION 2234 "An entry in this table is created by the LSR for every 2235 bidirectional MPLS tunnel where packets are visible to the 2236 LSR." 2237 INDEX { 2238 mplsTunnelIndex, 2239 mplsTunnelInstance, 2240 mplsTunnelIngressLSRId, 2241 mplsTunnelEgressLSRId 2242 } 2243 ::= { mplsTunnelExtReversePerfTable 1 } 2245 MplsTunnelExtReversePerfEntry ::= SEQUENCE { 2246 mplsTunnelExtReversePerfPackets Counter32, 2247 mplsTunnelExtReversePerfHCPackets Counter64, 2248 mplsTunnelExtReversePerfErrors Counter32, 2249 mplsTunnelExtReversePerfBytes Counter32, 2250 mplsTunnelExtReversePerfHCBytes Counter64 2251 } 2253 mplsTunnelExtReversePerfPackets OBJECT-TYPE 2254 SYNTAX Counter32 2255 MAX-ACCESS read-only 2257 STATUS current 2258 DESCRIPTION 2259 "Number of packets forwarded on the tunnel in the reverse 2260 direction if it is bidirectional. 2262 This object represents the 32-bit value of the least 2263 significant part of the 64-bit value if both 2264 mplsTunnelExtReversePerfHCPackets and this object 2265 are returned." 2266 ::= { mplsTunnelExtReversePerfEntry 1 } 2268 mplsTunnelExtReversePerfHCPackets OBJECT-TYPE 2269 SYNTAX Counter64 2270 MAX-ACCESS read-only 2271 STATUS current 2272 DESCRIPTION 2273 "High-capacity counter for number of packets forwarded on 2274 the tunnel in the reverse direction if it is 2275 bidirectional." 2277 ::= { mplsTunnelExtReversePerfEntry 2 } 2279 mplsTunnelExtReversePerfErrors OBJECT-TYPE 2280 SYNTAX Counter32 2281 MAX-ACCESS read-only 2282 STATUS current 2283 DESCRIPTION 2284 "Number of errored packets received on the tunnel in 2285 the reverse direction if it is bidirectional." 2286 ::= { mplsTunnelExtReversePerfEntry 3 } 2287 mplsTunnelExtReversePerfBytes OBJECT-TYPE 2288 SYNTAX Counter32 2289 MAX-ACCESS read-only 2290 STATUS current 2291 DESCRIPTION 2292 "Number of bytes forwarded on the tunnel in the reverse 2293 direction if it is bidirectional. 2295 This object represents the 32-bit value of the least 2296 significant part of the 64-bit value if both 2297 mplsTunnelExtReversePerfHCBytes and this object are 2298 returned." 2300 ::= { mplsTunnelExtReversePerfEntry 4 } 2302 mplsTunnelExtReversePerfHCBytes OBJECT-TYPE 2303 SYNTAX Counter64 2304 MAX-ACCESS read-only 2305 STATUS current 2306 DESCRIPTION 2307 "High-capacity counter for number of bytes forwarded on the 2308 tunnel in the reverse direction if it is bidirectional." 2309 ::= { mplsTunnelExtReversePerfEntry 5 } 2311 -- Module compliance. 2313 mplsTeExtCompliances 2314 OBJECT IDENTIFIER ::= { mplsTeExtConformance 1 } 2316 mplsTeExtGroups 2317 OBJECT IDENTIFIER ::= { mplsTeExtConformance 2 } 2319 -- Compliance requirement for fully compliant implementations. 2321 mplsTeExtModuleFullCompliance MODULE-COMPLIANCE 2322 STATUS current 2323 DESCRIPTION 2324 "Compliance statement for agents that provide full 2325 support the MPLS-TE-EXT-STD-MIB module." 2327 MODULE -- this module 2329 -- The mandatory group has to be implemented by all 2330 -- LSRs that originate/terminate MPLS-TP tunnels. 2331 -- In addition, depending on the type of tunnels 2332 -- supported, other groups become mandatory as 2334 -- explained below. 2336 MANDATORY-GROUPS { 2337 mplsTunnelExtGroup 2338 } 2340 ::= { mplsTeExtCompliances 1 } 2342 -- Compliance requirement for read-only implementations. 2344 mplsTeExtModuleReadOnlyCompliance MODULE-COMPLIANCE 2345 STATUS current 2346 DESCRIPTION 2347 "Compliance statement for agents that only provide 2348 read-only support for MPLS-TE-EXT-STD-MIB module." 2350 MODULE -- this module 2352 MANDATORY-GROUPS { 2353 mplsTunnelExtGroup 2354 } 2356 GROUP mplsTunnelExtIpOperatorGroup 2357 DESCRIPTION 2358 "This group is mandatory for devices which support 2359 configuration of IP based identifier tunnels." 2361 GROUP mplsTunnelExtIccOperatorGroup 2362 DESCRIPTION 2363 "This group is mandatory for devices which support 2364 configuration of ICC based tunnels." 2366 -- mplsTunnelExtTable 2368 OBJECT mplsTunnelExtOppositeDirPtr 2369 MIN-ACCESS read-only 2370 DESCRIPTION 2371 "Write access is not required." 2373 OBJECT mplsTunnelExtOppositeDirTnlValid 2374 MIN-ACCESS read-only 2375 DESCRIPTION 2376 "Write access is not required." 2378 OBJECT mplsTunnelExtDestTnlIndex 2379 MIN-ACCESS read-only 2380 DESCRIPTION 2381 "Write access is not required." 2383 OBJECT mplsTunnelExtDestTnlLspIndex 2384 MIN-ACCESS read-only 2385 DESCRIPTION 2386 "Write access is not required." 2388 OBJECT mplsTunnelExtDestTnlValid 2389 MIN-ACCESS read-only 2390 DESCRIPTION 2391 "Write access is not required." 2393 OBJECT mplsTunnelExtIngressLSRLocalIdValid 2394 MIN-ACCESS read-only 2395 DESCRIPTION 2396 "Write access is not required." 2398 OBJECT mplsTunnelExtEgressLSRLocalIdValid 2399 MIN-ACCESS read-only 2400 DESCRIPTION 2401 "Write access is not required." 2403 OBJECT mplsTunnelExtNodeConfigGlobalId 2404 MIN-ACCESS read-only 2405 DESCRIPTION 2406 "Write access is not required." 2408 OBJECT mplsTunnelExtNodeConfigNodeId 2409 MIN-ACCESS read-only 2410 DESCRIPTION 2411 "Write access is not required." 2413 OBJECT mplsTunnelExtNodeConfigStorageType 2414 MIN-ACCESS read-only 2415 DESCRIPTION 2416 "Write access is not required." 2418 OBJECT mplsTunnelExtNodeConfigRowStatus 2419 SYNTAX RowStatus { active(1) } 2420 MIN-ACCESS read-only 2421 DESCRIPTION 2422 "Write access is not required." 2424 OBJECT mplsTunnelExtNodeConfigCcId 2425 MIN-ACCESS read-only 2426 DESCRIPTION 2427 "Write access is not required." 2429 OBJECT mplsTunnelExtNodeConfigIccId 2430 MIN-ACCESS read-only 2431 DESCRIPTION 2432 "Write access is not required." 2434 OBJECT mplsTunnelExtNodeConfigIccValid 2435 MIN-ACCESS read-only 2436 DESCRIPTION 2437 "Write access is not required." 2439 ::= { mplsTeExtCompliances 2 } 2441 -- Units of conformance. 2443 mplsTunnelExtGroup OBJECT-GROUP 2444 OBJECTS { 2445 mplsTunnelExtOppositeDirPtr, 2446 mplsTunnelExtOppositeDirTnlValid, 2447 mplsTunnelExtDestTnlIndex, 2448 mplsTunnelExtDestTnlLspIndex, 2449 mplsTunnelExtDestTnlValid, 2450 mplsTunnelExtIngressLSRLocalIdValid, 2451 mplsTunnelExtEgressLSRLocalIdValid, 2452 mplsTunnelExtReversePerfPackets, 2453 mplsTunnelExtReversePerfHCPackets, 2454 mplsTunnelExtReversePerfErrors, 2455 mplsTunnelExtReversePerfBytes, 2456 mplsTunnelExtReversePerfHCBytes 2457 } 2459 STATUS current 2460 DESCRIPTION 2461 "Necessary, but not sufficient, set of objects to 2462 implement tunnels. In addition, depending on the 2463 operating environment, the following groups are 2464 mandatory." 2465 ::= { mplsTeExtGroups 1 } 2467 mplsTunnelExtIpOperatorGroup OBJECT-GROUP 2468 OBJECTS { mplsTunnelExtNodeConfigGlobalId, 2469 mplsTunnelExtNodeConfigNodeId, 2470 mplsTunnelExtNodeIpMapLocalId, 2471 mplsTunnelExtNodeConfigStorageType, 2472 mplsTunnelExtNodeConfigRowStatus 2473 } 2474 STATUS current 2475 DESCRIPTION 2476 "Object(s) needed to implement IP compatible tunnels." 2477 ::= { mplsTeExtGroups 2 } 2479 mplsTunnelExtIccOperatorGroup OBJECT-GROUP 2480 OBJECTS { mplsTunnelExtNodeConfigCcId, 2481 mplsTunnelExtNodeConfigIccId, 2482 mplsTunnelExtNodeConfigNodeId, 2483 mplsTunnelExtNodeConfigIccValid, 2484 mplsTunnelExtNodeIccMapLocalId, 2485 mplsTunnelExtNodeConfigStorageType, 2486 mplsTunnelExtNodeConfigRowStatus 2487 } 2488 STATUS current 2489 DESCRIPTION 2490 "Object(s) needed to implement ICC based tunnels." 2491 ::= { mplsTeExtGroups 3 } 2493 -- MPLS-TE-EXT-STD-MIB module ends 2494 END 2496 14. Security Consideration 2498 It is clear that this MIB module is potentially useful for the 2499 monitoring of MPLS TE tunnels. This MIB module can also be used for 2500 the configuration of certain objects, and anything that can be 2501 configured can be incorrectly configured, with potentially disastrous 2502 results. 2504 There are a number of management objects defined in this MIB module 2505 with a MAX-ACCESS clause of read-write. Such objects may be 2506 considered sensitive or vulnerable in some network environments. The 2507 support for SET operations in a non-secure environment without proper 2508 protection can have a negative effect on network operations. These 2509 are the tables and objects and their sensitivity/vulnerability: 2511 - the tables specified in [RFC3812], [RFC3813] and this document 2512 MIB tables mplsTunnelExtNodeConfigTable, mplsTunnelExtTable and 2513 mplsXCExtTable collectively contain objects to provision MPLS-TP 2514 tunnels, tunnel hops, and tunnel resources. 2515 Unauthorized access to objects in these tables, could result in 2516 disruption of traffic on the network. This is especially true if 2517 a tunnel has been established. The use of stronger mechanisms, 2518 such as SNMPv3 security, should be considered where possible. 2519 Specifically, SNMPv3 VACM and USM MUST be used with any v3 agent 2520 which implements this MIB. Administrators should consider whether 2521 read access to these objects should be allowed, since read access 2522 may be undesirable under certain circumstances. 2524 Some of the readable objects in this MIB module (i.e., objects 2525 with a MAX-ACCESS other than not-accessible) may be considered 2526 sensitive or vulnerable in some network environments. 2528 It is thus important to control even GET and/or NOTIFY access to 2529 these objects and possibly to even encrypt the values of these 2530 objects when sending them over the network via SNMP. These are 2531 the tables and objects and their sensitivity/vulnerability: 2533 - the tables specified in [RFC3812], [RFC3813] and this document 2534 MIB tables mplsTunnelExtNodeConfigTable, mplsTunnelExtTable, 2535 mplsXCExtTable and mplsTunnelExtReversePerfTable collectively 2536 show the MPLS-TP tunnel network topology and its performance 2537 characteristics. If an Administrator does not want to reveal 2538 this information, then these tables should be considered 2539 sensitive/vulnerable. 2541 SNMP versions prior to SNMPv3 did not include adequate security. 2542 Even if the network itself is secure (for example by using IPsec), 2543 even then, there is no control as to who on the secure network is 2544 allowed to access and GET/SET (read/change/create/delete) 2545 the objects in this MIB module. 2547 It is recommended that implementers consider the security features as 2548 provided by the SNMPv3 framework (see [RFC3410], section 8), 2549 including full supports for the SNMPv3 cryptographic mechanisms (for 2550 authentication and privacy). 2552 Further, deployment of SNMP versions prior to SNMPv3 is not 2553 recommended. Instead, it is recommended to deploy SNMPv3 and to 2554 enable cryptographic security. It is then a customer/operator 2555 responsibility to ensure that the SNMP entity giving access to an 2556 instance of this MIB module is properly configured to give 2557 access to the objects only to those principles (users) that 2558 have legitimate rights to indeed GET or SET (change/create/delete) 2559 them. 2561 15. IANA Considerations 2563 As described in [RFC4221], [RFC6639] and as requested in the MPLS-TC- 2564 STD-MIB [RFC3811], MPLS related standards track MIB modules should be 2565 rooted under the mplsStdMIB subtree. There are 4 MPLS MIB Modules 2566 contained in this document, each of the following "IANA 2567 Considerations" subsections requests IANA for a new assignment under 2568 the mplsStdMIB subtree. New assignments can only be made via a 2569 Standards Action as specified in [RFC5226]. 2571 15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB 2573 IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS-TC- 2574 EXT-STD-MIB module specified in this document. 2576 15.2. IANA Considerations for MPLS-ID-STD-MIB 2577 IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS-ID- 2578 STD-MIB module specified in this document. 2580 15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB 2582 IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS- 2583 LSR-EXT-STD-MIB module specified in this document. 2585 15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB 2587 IANA is requested to assign an OID { mplsStdMIB OID } to the MPLS-TE- 2588 EXT-STD-MIB module specified in this document. 2590 16. References 2592 16.1. Normative References 2594 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2595 Requirement Levels", BCP 14, RFC 2119, March 1997. 2597 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2598 "Structure of Management Information Version 2 (SMIv2)", 2599 STD 58, RFC 2578, April 1999. 2601 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2602 "Textual Conventions for SMIv2", STD 58, RFC 2579, April 2603 1999. 2605 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2606 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2607 April 1999. 2609 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 2610 Label Switching Architecture", RFC 3031, January 2001. 2612 16.2. Informative References 2614 [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction 2615 and Applicability Statement for Internet Standard 2616 Management Framework", RFC 3410, December 2002. 2618 [RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of 2619 Textual Conventions (TCs) for Multiprotocol Label 2620 Switching (MPLS) Management", RFC 3811, June 2004. 2622 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 2623 "Multiprotocol Label Switching (MPLS) Traffic Engineering 2624 (TE) Management Information Base (MIB)", RFC 3812, June 2625 2004. 2627 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 2628 "Multiprotocol Label Switching (MPLS) Label Switching 2629 (LSR) Router Management Information Base (MIB)", RFC 3813, 2630 June 2004. 2632 [RFC4221] Nadeau, T., Srinivasan, C., and A. Farrel, "MSMGMT Label 2633 Switching (MPLS) Management Overview", RFC 4221, November 2634 2005. 2636 [RFC4802] Nadeau, T., Ed., and A. Farrel, Ed., "Generalized 2637 Multiprotocol Label Switching (GMPLS) Traffic Engineering 2638 Management Information Base", RFC 4802, February 2007. 2640 [RFC5226] Narten, T. and H. Alvestrand., "Guidelines for Writing an 2641 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 2642 May 2008. 2644 [RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., 2645 Ed.,Sprecher, N., and S. Ueno, "Requirements of an MPLS 2646 Transport Profile", RFC 5654, September 2009. 2648 [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport 2649 Profile (MPLS-TP) Identifiers", RFC 6370, September 2011. 2651 [RFC6639] Venkatesan, M., King, D., "Multiprotocol Label Switching 2652 Transport Profile (MPLS-TP) MIB-Based Management 2653 Overview", RFC 6639, June 2012 2655 [RFC6923] Winter, R., Gray, E., Helvoort, H., and M. Betts, "MPLS-TP 2656 Identifiers Following ITU-T Conventions", RFC 6923, May 2657 2013 2659 17. Acknowledgments 2661 The authors would like to thank Francesco Fondelli, Josh Littlefield, 2662 Agrahara Kiran Koushik, Metrri Jain, Muly Ilan and Randy Presuhn for 2663 their valuable comments. A special thanks to Joan Cucchiara for 2664 really getting the MIB modules into shape. 2666 18. Authors' Addresses 2668 Venkatesan Mahalingam 2669 Dell Inc. 2670 350 Holger way, San Jose, CA, USA 2671 Email: venkat.mahalingams@gmail.com 2673 Sam Aldrin 2674 Huawei Technologies 2675 2330 Central Express Way, 2676 Santa Clara, CA 95051, USA 2677 Email: aldrin.ietf@gmail.com 2679 Thomas D. Nadeau 2680 Juniper Networks 2681 10 Technology Park Drive, Westford, MA 01886 2682 Email: tnadeau@juniper.net 2684 Kannan KV Sampath 2685 Redeem 2686 India 2687 Email: kannankvs@gmail.com