idnits 2.17.1 draft-ietf-mpls-tp-te-mib-03.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 (April 13, 2012) is 4396 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). 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: October 15, 2012 Kannan KV Sampath 6 Aricent 7 Sam K. Aldrin 8 Huawei Technologies 9 Thomas D. Nadeau 10 Juniper Networks 12 April 13, 2012 14 MPLS-TP Traffic Engineering (TE) Management Information Base (MIB) 15 draft-ietf-mpls-tp-te-mib-03.txt 17 Abstract 19 This memo defines a portion of the Management Information Base (MIB) 20 for use with network management protocols in the Internet community. 21 In particular, it describes managed objects of Tunnels, Identifiers, 22 Label Switch Router and Textual conventions for Multiprotocol Label 23 Switching (MPLS) based Transport Profile (TP). 25 Status of this Memo 27 This Internet-Draft is submitted to IETF in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF), its areas, and its working groups. Note that 32 other groups may also distribute working documents as Internet- 33 Drafts. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 The list of current Internet-Drafts can be accessed at 41 http://www.ietf.org/ietf/1id-abstracts.txt. 43 The list of Internet-Draft Shadow Directories can be accessed at 44 http://www.ietf.org/shadow.html. 46 This Internet-Draft will expire on October 15, 2012. 48 Copyright and License Notice 50 Copyright (c) 2012 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. 63 Table of Contents 65 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 66 2. The Internet-Standard Management Framework . . . . . . . . . . 3 67 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 68 3.1 Conventions used in this document . . . . . . . . . . . . . 3 69 3.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 70 3.3 Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . 3 71 4. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . . 4 72 5. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 4 73 6. Brief description of MIB Objects . . . . . . . . . . . . . . . 4 74 6.1. mplsNodeConfigTable . . . . . . . . . . . . . . . . . . . 5 75 6.2. mplsNodeIpMapTable . . . . . . . . . . . . . . . . . . . . 5 76 6.3. mplsNodeIccMapTable . . . . . . . . . . . . . . . . . . . 6 77 6.4.mplsTunnelExtTable . . . . . . . . . . . . . . . . . . . . . 6 78 7. MIB Module Interdependencies . . . . . . . . . . . . . . . . . 6 79 8. Dependencies between MIB Module Tables . . . . . . . . . . . . 8 80 9. Example of MPLS-TP tunnel setup . . . . . . . . . . . . . . . . 8 81 10. MPLS Textual Convention Extension MIB definitions . . . . . . 13 82 11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 16 83 12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 20 84 13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 24 85 14. Security Consideration . . . . . . . . . . . . . . . . . . . . 36 86 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 87 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 37 88 16.1 Normative References . . . . . . . . . . . . . . . . . . . 37 89 16.2 Informative References . . . . . . . . . . . . . . . . . . 38 90 17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 38 91 18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 38 93 1 Introduction 95 This memo defines a portion of the Management Information Base (MIB) 96 for use with network management protocols in the Internet community. 97 In particular, it describes managed objects of Tunnels, Identifiers, 98 Label Switch Router and Textual conventions for Multiprotocol Label 99 Switching (MPLS) based Transport Profile (TP). 101 This MIB module should be used in conjunction with the MPLS traffic 102 Engineering MIB [RFC3812] and companion document MPLS Label Switch 103 Router MIB [RFC3813] for MPLS based traffic engineering configuration 104 and management. 106 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 107 "SHOULD", "SHOULD NOT", "MAY", and "OPTIONAL" in this document are to 108 be interpreted as described in BCP 14, RFC2119. 110 2. The Internet-Standard Management Framework 112 For a detailed overview of the documents that describe the current 113 Internet-Standard Management Framework, please refer to section 7 of 114 RFC3410 [RFC3410]. 116 Managed objects are accessed via a virtual information store, termed 117 the Management Information Base or MIB. MIB objects are generally 118 accessed through the Simple Network Management Protocol (SNMP). 119 Objects in the MIB are defined using the mechanisms defined in the 120 Structure of Management Information (SMI). This memo specifies a MIB 121 module that is compliant to the SMIv2, which is described in STD 58, 122 RFC2578, STD 58, RFC2579 and STD58, RFC2580. 124 3. Overview 126 3.1 Conventions used in this document 128 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 129 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 130 document are to be interpreted as described in [RFC2119]. 132 3.2 Terminology 134 This document uses terminology from the MPLS architecture document 135 [RFC3031], MPLS Traffic Engineering Management information [RFC3812], 136 MPLS Label Switch Router MIB [RFC3813] and MPLS-TP Identifiers 137 document [RFC6370]. 139 3.3 Acronyms 140 GMPLS: Generalized Multi-Protocol Label Switching 141 ICC: ITU Carrier Code 142 IP: Internet Protocol 143 LSP: Label Switching Path 144 LSR: Label Switching Router 145 MIB: Management Information Base 146 MPLS: Multi-Protocol Label Switching 147 MPLS-TP: MPLS Transport Profile 148 OSPF: Open Shortest Path First 149 PW: Pseudowire 150 TE: Traffic Engineering 151 TP: Transport Profile 153 4. Motivations 155 The existing MPLS TE [RFC3812] and GMPLS MIBs [RFC4802] do not 156 support the transport network requirements of NON-IP based management 157 and static bidirectional tunnels. 159 5. Feature List 161 The MPLS transport profile MIB module is designed to satisfy the 162 following requirements and constraints: 164 The MIB module supports point-to-point, co-routed bi-directional 165 associated bi-directional tunnels. 167 - The MPLS tunnels need not be interfaces, but it is possible 168 to configure a TP tunnel as an interface. 170 - The mplsTunnelTable [RFC3812] to be also used for MPLS-TP 171 tunnels 173 - The mplsTunnelTable is extended to support MPLS-TP specific 174 objects. 176 - A node configuration table (mplsNodeConfigTable) is used to 177 translate the Global_Node_ID or ICC to the local identifier 178 in order to index mplsTunnelTable. 180 - The MIB module supports persistent, as well as non-persistent 181 tunnels. 183 6. Brief description of MIB Objects 185 The objects described in this section support the functionality 186 described in documents [RFC5654] and [RFC6370]. The tables support 187 both IP compatible and ICC based tunnel configurations. 189 6.1. mplsNodeConfigTable 191 The mplsNodeConfigTable is used to assign a local identifier for a 192 given ICC or Global_Node_ID combination as defined in [RFC6370]. 193 An ICC is a string of one to six characters, each character being 194 either alphabetic (i.e. A-Z) or numeric (i.e. 0-9) characters. 195 Alphabetic characters in the ICC should be represented 196 with upper case letters. In the IP compatible mode, 197 Global_Node_ID, is used to uniquely identify a node. 199 Each ICC or Global_Node_ID contains one unique entry in the 200 table representing a node. Every node is assigned a local identifier 201 within a range of 0 to 16777215. This local identifier is used for 202 indexing into mplsTunnelTable as mplsTunnelIngressLSRId and 203 mplsTunnelEgressLSRId. 205 For IP compatible environment, MPLS-TP tunnel is indexed by Tunnel 206 Index, Tunnel Instance, Source Global_ID, Source Node_ID, Destination 207 Global_ID and Destination Node_ID. 209 For ICC based environment, MPLS-TP tunnel is indexed by Tunnel Index, 210 Tunnel Instance, Source ICC and Destination ICC. 212 As mplsTunnelTable is indexed by mplsTunnelIndex, 213 mplsTunnelInstance, mplsTunnelIngressLSRId, and 214 mplsTunnelEgressLSRId, the MPLS-TP tunnel identifiers cannot be 215 used directly. 217 The mplsNodeConfigTable will be used to store an entry for ICC or 218 Global_Node_ID with a local identifier to be used as LSR ID 219 in mplsTunnelTable. As the regular TE tunnels use IP address as LSR 220 ID, the local identifier should be below the first valid IP address, 221 which is 16777216[1.0.0.0]. 223 6.2. mplsNodeIpMapTable 225 The read-only mplsNodeIpMaptable is used to query the local 226 identifier assigned and stored in mplsNodeConfigTable for a given 227 Global_Node_ID. In order to query the local identifier, 228 in the IP compatible mode, this table is indexed with Global_Node_ID. 229 In the IP compatible mode for a TP tunnel, Global_Node_ID 230 is used. 232 A separate query is made to get the local identifier of both 233 Ingress and Egress Global_Node_ID identifiers. These local 234 identifiers are used as mplsTunnelIngressLSRId and 235 mplsTunnelEgressLSRId, while indexing mplsTunnelTable. 237 6.3. mplsNodeIccMapTable 239 The read-only mplsNodeIccMapTable is used to query the local 240 identifier assigned and stored in the mplsNodeConfigTable 241 for a given ICC. 243 A separate query is made to get the local identifier of both 244 Ingress and Egress ICC. These local identifiers are used as 245 mplsTunnelIngressLSRId and mplsTunnelEgressLSRId, 246 while indexing mplsTunnelTable. 248 6.4.mplsTunnelExtTable 250 mplsTunnelExtTable extends the mplsTunnelTable to add MPLS-TP tunnel 251 specific additional objects. All the additional attributes specific 252 to TP tunnel are contained in this extended table and could be 253 accessed with the mplsTunnelTable indices. 255 6.5 mplsTunnelReversePerfTable 257 This table augments the mplsTunnelTable to provide per-tunnel packet 258 performance information for the reverse direction of a bidirectional 259 tunnel. It can be seen as supplementing the mplsTunnelPerfTable, 260 which augments the mplsTunnelTable. 262 7. MIB Module Interdependencies 264 This section provides an overview of the relationship between the 265 MPLS-TP TE MIB module and other MPLS MIB modules. 267 The arrows in the following diagram show a 'depends on' 268 relationship. A relationship "MIB module A depends on MIB module B" 269 means that MIB module A uses an object, object identifier, or 270 textual convention defined in MIB module B, or that MIB module A 271 contains a pointer (index or RowPointer) to an object in 272 MIB module B. 274 MPLS-TC-EXT-STD-MIB 275 ^ 276 | 277 | 278 +<---- MPLS-ID-STD-MIB 279 ^ 280 | | 281 +<---- MPLS-TE-EXT-STD-MIB 282 | | 283 | V 284 | MPLS-TE-STD-MIB 285 | | 286 | | 287 | V 288 | MPLS-LSR-STD-MIB 289 | ^ 290 | | 291 | | 292 +------MPLS-LSR-EXT-STD-MIB 294 Thus: 296 - All the new MPLS extension MIB modules depend on 297 MPLS-TC-EXT-STD-MIB. 299 - MPLS-TE-STD-MIB [RFC3812] contains references to objects in 300 MPLS-ID-STD-MIB. 302 - MPLS-TE-EXT-STD-MIB contains references to objects in 303 MPLS-TE-STD-MIB [RFC3812]. 305 - MPLS-LSR-EXT-STD-MIB contains references to objects in 306 MPLS-LSR-STD-MIB [RFC3813]. 308 MPLS-TE-STD-MIB [RFC3812] is extended by MPLS-TE-EXT-STD-MIB 309 mib module for associating the reverse direction tunnel 310 information. 312 Note that the nature of the 'extends' relationship 313 is a sparse augmentation so that the entry in the 314 mplsTunnelExtTable has the same index values as the in the 315 mplsTunnelTable. 317 MPLS-LSR-STD-MIB [RFC3813] is extended by MPLS-LSR-EXT-STD-MIB 318 mib module for pointing back to the tunnel entry for easy tunnel 319 access from XC entry. 321 Note that the nature of the 'extends' relationship 322 is a sparse augmentation so that the entry in the 323 mplsXCExtTable has the same index values as the in the mplsXCTable. 325 8. Dependencies between MIB Module Tables 327 The tables in MPLS-TE-EXT-STD-MIB are related as shown on the diagram 328 below. The arrows indicate a reference from one table to another. 330 mplsNodeConfigTable 331 ^ mplsXCExtTable 332 | | ^ 333 | +---------+ | 334 | | | 335 | V V 336 mplsTunnelTable ---->mplsXCTable 337 ^ 338 | 339 | 340 mplsTunnelExtTable 342 An existing mplsTunnelTable uses the mplsNodeConfigTable table to map 343 the Global_Node_ID and/or ICC with the local number in order to 344 accommodate in the existing tunnel table's ingress/egress LSR-id. 346 New mplsTunnelExtTable table provides the reverse direction LSP 347 information for the existing tunnel table in order to achieve 348 bidirectional LSPs. 350 mplsXCExtTable is extended from mplsLsrXCTable to provide 351 backward reference to tunnel entry. 353 9. Example of MPLS-TP Tunnel Setup 354 In this section, we provide an example of the IP based MPLS-TP 355 bidirectional tunnel setup. This example provides the usage of 356 MPLS-TP Tunnel MIB along with the extended new MIB modules introduced 357 in this document. 359 Do note that a MPLS-TP tunnel could be setup statically as well as 360 signaled via control plane. This example considers accessing mib 361 objects on a head-end for a static MPLS-TP tunnel. 362 Only relevant objects which are applicable for MPLS-TP tunnel are 363 illustrated here. 365 In mplsNodeConfigTable: 367 { 368 -- Non-IP Ingress LSR-Id (Index to the table) 369 mplsNodeConfigLocalId = 1, 370 mplsNodeConfigGlobalId = 1234, 371 mplsNodeConfigNodeId = 10, 372 -- Mandatory parameters needed to activate the row go here 373 mplsNodeConfigRowStatus = createAndGo (4) 375 -- Non-IP Egress LSR-Id (Index to the table) 376 mplsNodeConfigLocalId = 2, 377 mplsNodeConfigGlobalId = 1234, 378 mplsNodeConfigNodeId = 20, 379 -- Mandatory parameters needed to activate the row go here 380 mplsNodeConfigRowStatus = createAndGo (4) 381 } 383 This will create an entry in the mplsNodeConfigTable for a 384 Global_Node_ID. A separate entry is made for both Ingress LSR 385 and Egress LSR. 387 The following read-only mplsNodeIpMapTable table is populated 388 automatically upon creating an entry in mplsNodeConfigTable and 389 this table is used to retrieve the local identifier for the given 390 Global_Node_ID. 392 In mplsNodeIpMapTable: 394 { 395 -- Global_ID (Index to the table) 396 mplsNodeIpMapGlobalId = 1234, 397 -- Node Identifier (Index to the table) 398 mplsNodeIpMapNodeId = 10, 399 mplsNodeIpMapLocalId = 1 401 -- Global_ID (Index to the table) 402 mplsNodeIpMapGlobalId = 1234, 403 -- Node Identifier (Index to the table) 404 mplsNodeIpMapNodeId = 20, 405 mplsNodeIpMapLocalId = 2 406 } 408 9.1 Example of MPLS-TP co-routed bidirectional tunnel setup 410 The following denotes the configured co-routed bidirectional 411 tunnel "head" entry: 413 9.1.1 mplsTunnelEntry 415 In mplsTunnelTable: 417 { 418 mplsTunnelIndex = 1, 419 mplsTunnelInstance = 1, 420 -- Local map number created in mplsNodeConfigTable for Ingress 421 LSR-Id 422 mplsTunnelIngressLSRId = 1, 424 -- Local map number created in mplsNodeConfigTable for Egress 425 LSR-Id 426 mplsTunnelEgressLSRId = 2, 427 mplsTunnelName = "TP co-routed bidirectional LSP", 428 mplsTunnelDescr = "East to West", 429 mplsTunnelIsIf = true (1), 430 -- RowPointer MUST point to the first accessible column 431 mplsTunnelXCPointer = 432 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1, 433 mplsTunnelSignallingProto = none (1), 434 mplsTunnelSetupPrio = 0, 435 mplsTunnelHoldingPrio = 0, 436 mplsTunnelSessionAttributes = 0, 437 mplsTunnelLocalProtectInUse = false (0), 438 -- RowPointer MUST point to the first accessible column 439 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 440 mplsTunnelInstancePriority = 1, 441 mplsTunnelHopTableIndex = 1, 442 mplsTunnelIncludeAnyAffinity = 0, 443 mplsTunnelIncludeAllAffinity = 0, 444 mplsTunnelExcludeAnyAffinity = 0, 445 mplsTunnelRole = head (1), 446 -- Mandatory parameters needed to activate the row go here 447 mplsTunnelRowStatus = createAndGo (4) 448 } 450 9.1.2 mplsTunnelExtEntry 452 -- An MPLS extension table 453 In mplsTunnelExtTable: 454 { 455 -- This opposite direction tunnel pointer MAY be point to 0.0 456 -- if co-routed bidirectional tunnel is managed by single tunnel 457 -- entry 458 mplsTunnelOppositeDirTnlPtr = 0.0 459 } 461 We must next create the appropriate in-segment and out-segment 462 entries. These are done in [RFC3813] using the mplsInSegmentTable 463 and mplsOutSegmentTable. 465 9.1.3 Forward direction mplsOutSegmentEntry 466 For the forward direction. 468 In mplsOutSegmentTable: 469 { 470 mplsOutSegmentIndex = 0x0000001, 471 mplsOutSegmentInterface = 13, -- outgoing interface 472 mplsOutSegmentPushTopLabel = true(1), 473 mplsOutSegmentTopLabel = 22, -- outgoing label 475 -- RowPointer MUST point to the first accessible column. 476 mplsOutSegmentTrafficParamPtr = 0.0, 477 mplsOutSegmentRowStatus = createAndGo (4) 478 } 480 9.1.4 Reverse direction mplsInSegmentEntry 482 For the reverse direction. 484 In mplsInSegmentTable: 485 { 486 mplsInSegmentIndex = 0x0000001 487 mplsInSegmentLabel = 21, -- incoming label 488 mplsInSegmentNPop = 1, 489 mplsInSegmentInterface = 13, -- incoming interface 491 -- RowPointer MUST point to the first accessible column. 492 mplsInSegmentTrafficParamPtr = 0.0, 493 mplsInSegmentRowStatus = createAndGo (4) 494 } 496 Next, two cross-connect entries are created in the mplsXCTable of the 497 MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created 498 segments together. 500 9.1.5 Forward direction mplsXCEntry 502 In mplsXCTable: 503 { 504 mplsXCIndex = 0x01, 505 mplsXCInSegmentIndex = 0x00000000, 506 mplsXCOutSegmentIndex = 0x00000001, 507 mplsXCLspId = 0x0102 -- unique ID 508 -- only a single outgoing label 509 mplsXCLabelStackIndex = 0x00, 510 mplsXCRowStatus = createAndGo(4) 512 } 514 9.1.6 Reverse direction mplsXCEntry 516 In mplsXCTable: 517 { 518 mplsXCIndex = 0x01, 519 mplsXCInSegmentIndex = 0x00000001, 520 mplsXCOutSegmentIndex = 0x00000000, 521 mplsXCLspId = 0x0102 -- unique ID 522 -- only a single outgoing label 523 mplsXCLabelStackIndex = 0x00, 524 mplsXCRowStatus = createAndGo(4) 525 } 527 This table entry is extended by entry in the 528 mplsXCExtTable. Note that the nature of the 'extends' 529 relationship is a sparse augmentation so that the entry in the 530 mplsXCExtTable has the same index values as the entry in 531 the mplsXCTable. 533 9.1.5 Forward direction mplsXCExtEntry 535 In mplsXCExtTable (0x01, 0x00000000, 0x00000001) 536 { 537 -- Back pointer from XC table to Tunnel table 538 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 539 mplsXCOppositeDirXCPtr = 540 mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0 541 } 543 9.1.6 Reverse direction mplsXCExtEntry 545 Next for the reverse direction: 547 In mplsXCExtTable (0x01, 0x00000001, 0x00000000) 548 { 549 -- Back pointer from XC table to Tunnel table 550 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 551 mplsXCOppositeDirXCPtr = 552 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1 553 } 555 9.1.7 mplsTunnelReversePerfTable 557 The mplsTunnelReversePerfTable SHOULD be populated incase 558 the single tunnel entry is used for co-routed bidirectional tunnel 559 setup. The mplsTunnelPerfTable will have the forward direction 560 LSP performance counters and mplsTunnelReversePerfTable will have 561 the reverse direction LSP performance counters. 563 9.2 Example of MPLS-TP associated bidirectional tunnel setup 565 The MPLS-TP associated bidirectional tunnel has two different 566 direction tunnels[Forward and Reverse LSPs] and these are 567 associated together using mplsTunnelExtTable. Two different 568 tunnel entries for both forward and reverse direction MAY be used 569 for co-routed bidirectional tunnel as well. 571 The following denotes the configured associated bidirectional 572 forward tunnel "head" entry: 574 9.2.1 Forward direction mplsTunnelEntry 576 In mplsTunnelTable: 578 { 579 mplsTunnelIndex = 1, 580 mplsTunnelInstance = 1, 581 -- Local map number created in mplsNodeConfigTable for Ingress 582 LSR-Id 583 mplsTunnelIngressLSRId = 1, 585 -- Local map number created in mplsNodeConfigTable for Egress 586 LSR-Id 587 mplsTunnelEgressLSRId = 2, 588 mplsTunnelName = "TP associated bi-directional 589 forward LSP", 590 mplsTunnelDescr = "East to West", 591 mplsTunnelIsIf = true (1), 592 -- RowPointer MUST point to the first accessible column 593 mplsTunnelXCPointer = 594 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1, 595 mplsTunnelSignallingProto = none (1), 596 mplsTunnelSetupPrio = 0, 597 mplsTunnelHoldingPrio = 0, 598 mplsTunnelSessionAttributes = 0, 599 mplsTunnelLocalProtectInUse = false (0), 600 -- RowPointer MUST point to the first accessible column 601 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 602 mplsTunnelInstancePriority = 1, 603 mplsTunnelHopTableIndex = 1, 604 mplsTunnelIncludeAnyAffinity = 0, 605 mplsTunnelIncludeAllAffinity = 0, 606 mplsTunnelExcludeAnyAffinity = 0, 607 mplsTunnelRole = head (1), 608 -- Mandatory parameters needed to activate the row go here 609 mplsTunnelRowStatus = createAndGo (4) 610 } 612 9.2.2 Forward direction mplsTunnelExtEntry 614 For Associated bidirectional forward LSP, 615 In mplsTunnelExtTable: 616 { 617 mplsTunnelOppositeDirPtr.1.1.1.2 = mplsTunnelName.2.1.2.1 618 } 620 9.2.3 Forward direction mplsOutSegmentTable 622 For the forward direction. 624 In mplsOutSegmentTable: 625 { 626 mplsOutSegmentIndex = 0x0000001, 627 mplsOutSegmentInterface = 13, -- outgoing interface 628 mplsOutSegmentPushTopLabel = true(1), 629 mplsOutSegmentTopLabel = 22, -- outgoing label 631 -- RowPointer MUST point to the first accessible column. 632 mplsOutSegmentTrafficParamPtr = 0.0, 633 mplsOutSegmentRowStatus = createAndGo (4) 634 } 636 9.2.4 Forward direction mplsXCEntry 638 In mplsXCTable: 639 { 640 mplsXCIndex = 0x01, 641 mplsXCInSegmentIndex = 0x00000000, 642 mplsXCOutSegmentIndex = 0x00000001, 643 mplsXCLspId = 0x0102 -- unique ID 644 -- only a single outgoing label 645 mplsXCLabelStackIndex = 0x00, 646 mplsXCRowStatus = createAndGo(4) 648 } 650 9.2.5 Forward direction mplsXCExtEntry 652 In mplsXCExtTable (0x01, 0x00000000, 0x00000001) 653 { 654 -- Back pointer from XC table to Tunnel table 655 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 656 mplsXCOppositeDirXCPtr = 657 mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0 658 } 660 9.2.6 Forward direction mplsTunnelEntry 662 The following denotes the configured associated bidirectional 663 reverse tunnel "tail" entry: 665 In mplsTunnelTable: 667 { 668 mplsTunnelIndex = 2, 669 mplsTunnelInstance = 1, 670 -- Local map number created in mplsNodeConfigTable for Ingress 671 LSR-Id 672 mplsTunnelIngressLSRId = 2, 673 -- Local map number created in mplsNodeConfigTable for Egress 674 LSR-Id 675 mplsTunnelEgressLSRId = 1, 676 mplsTunnelName = "TP associated bi-directional 677 reverse LSP", 678 mplsTunnelDescr = "West to East", 679 mplsTunnelIsIf = true (1), 680 -- RowPointer MUST point to the first accessible column 681 mplsTunnelXCPointer = 682 mplsXCLspId.4.0.0.0.1.4.0.0.0.1.1.0, 683 mplsTunnelSignallingProto = none (1), 684 mplsTunnelSetupPrio = 0, 685 mplsTunnelHoldingPrio = 0, 686 mplsTunnelSessionAttributes = 0, 687 mplsTunnelLocalProtectInUse = false (0), 689 -- RowPointer MUST point to the first accessible column 690 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 691 mplsTunnelInstancePriority = 1, 692 mplsTunnelHopTableIndex = 1, 693 mplsTunnelIncludeAnyAffinity = 0, 694 mplsTunnelIncludeAllAffinity = 0, 695 mplsTunnelExcludeAnyAffinity = 0, 696 mplsTunnelRole = head (1), 697 -- Mandatory parameters needed to activate the row go here 698 mplsTunnelRowStatus = createAndGo (4) 699 } 701 9.2.7 Reverse direction mplsTunnelExtEntry 703 For Associated bidirectional reverse LSP, 704 In mplsTunnelExtTable: 705 { 706 mplsTunnelOppositeDirPtr.2.1.2.1 = mplsTunnelName.1.1.1.2 707 } 709 9.2.8 Reverse direction mplsInSegmentEntry 711 We must next create the appropriate in-segment and out-segment 712 entries. These are done in [RFC3813] using the mplsInSegmentTable 713 and mplsOutSegmentTable. 715 In mplsInSegmentTable: { mplsInSegmentIndex = 716 0x0000001 mplsInSegmentLabel = 21, -- incoming label 717 mplsInSegmentNPop = 1, mplsInSegmentInterface = 718 13, -- incoming interface 720 -- RowPointer MUST point to the first accessible column. 721 mplsInSegmentTrafficParamPtr = 0.0, mplsInSegmentRowStatus 722 = createAndGo (4) } 724 Next, two cross-connect entries are created in the mplsXCTable of 725 the MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly 726 created segments together. 728 9.2.9 Reverse direction mplsXCEntry 730 In mplsXCTable: 731 { 732 mplsXCIndex = 0x01, 733 mplsXCInSegmentIndex = 0x00000001, 734 mplsXCOutSegmentIndex = 0x00000000, 735 mplsXCLspId = 0x0102 -- unique ID 736 -- only a single outgoing label 737 mplsXCLabelStackIndex = 0x00, 738 mplsXCRowStatus = createAndGo(4) 739 } 741 This table entry is extended by entry in the 742 mplsXCExtTable. Note that the nature of the 'extends' 743 relationship is a sparse augmentation so that the entry in the 744 mplsXCExtTable has the same index values as the entry in 745 the mplsXCTable. 747 9.2.10 Reverse direction mplsXCExtEntry 749 Next for the reverse direction: 751 In mplsXCExtTable (0x01, 0x00000001, 0x00000000) 752 { 753 -- Back pointer from XC table to Tunnel table 754 mplsXCExtTunnelPointer = mplsTunnelName.1.1.1.2 755 mplsXCOppositeDirXCPtr = 756 mplsXCLspId.4.0.0.0.1.1.0.4.0.0.0.1 757 } 759 10. MPLS Textual Convention Extension MIB definitions 760 MPLS-TC-EXT-STD-MIB DEFINITIONS ::= BEGIN 762 IMPORTS 763 MODULE-IDENTITY, Unsigned32 764 FROM SNMPv2-SMI -- [RFC2578] 766 TEXTUAL-CONVENTION 767 FROM SNMPv2-TC -- [RFC2579] 769 mplsStdMIB 770 FROM MPLS-TC-STD-MIB -- [RFC3811] 772 ; 774 mplsTcExtStdMIB MODULE-IDENTITY 776 LAST-UPDATED 777 "201204080000Z" -- April 08, 2012 778 ORGANIZATION 779 "Multiprotocol Label Switching (MPLS) Working Group" 780 CONTACT-INFO 781 " 782 Venkatesan Mahalingam 783 Dell Inc, 784 350 Holger way, San Jose, CA, USA 785 Email: venkat.mahalingams@gmail.com 787 Kannan KV Sampath 788 Aricent, 789 India 790 Email: Kannan.Sampath@aricent.com 792 Sam Aldrin 793 Huawei Technologies 794 2330 Central Express Way, 795 Santa Clara, CA 95051, USA 796 Email: aldrin.ietf@gmail.com 798 Thomas D. Nadeau 799 Juniper Networks 800 10 Technology Park Drive, Westford, MA 01886 801 Email: tnadeau@juniper.net 802 " 803 DESCRIPTION 804 "Copyright (c) 2012 IETF Trust and the persons identified 805 as the document authors. All rights reserved. 807 This MIB module contains Textual Conventions for 808 MPLS based transport networks." 810 -- Revision history. 812 REVISION 813 "201204080000Z" -- April 08, 2012 814 DESCRIPTION 815 "MPLS Textual Convention Extensions" 817 ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value 819 MplsGlobalId ::= TEXTUAL-CONVENTION 821 STATUS current 822 DESCRIPTION 823 "This object contains the Textual Convention of IP based 824 operator unique identifier (Global_ID), the Global_ID can 825 contain the 2-octet or 4-octet value of the operator's 826 Autonomous System Number (ASN). 828 It is expected that the Global_ID will be derived from 829 the globally unique ASN of the autonomous system hosting 830 the PEs containing the actual AIIs. 831 The presence of a Global_ID based on the operator's 832 ASN ensures that the AII will be globally unique. 834 When the Global_ID is derived from a 2-octet AS number, 836 the two high-order octets of this 4-octet identifier 837 MUST be set to zero. 838 Further ASN 0 is reserved. A Global_ID of zero means 839 that no Global_ID is present. Note that a Global_ID of 840 zero is limited to entities contained within a single 841 operator and MUST NOT be used across an NNI. 842 A non-zero Global_ID MUST be derived from an ASN owned by 843 the operator." 844 SYNTAX OCTET STRING (SIZE (4)) 846 MplsNodeId ::= TEXTUAL-CONVENTION 847 DISPLAY-HINT "d" 848 STATUS current 849 DESCRIPTION 850 "The Node_ID is assigned within the scope of the Global_ID. 851 The value 0(or 0.0.0.0 in dotted decimal notation) is 852 reserved and MUST NOT be used. 854 When IPv4 addresses are in use, the value of this object 855 can be derived from the LSR's /32 IPv4 loop back address. 856 When IPv6 addresses are in use, the value of this object 857 can be a 32-bit value unique within the scope of 858 a Global_ID. 860 Note that, when IP reach ability is not needed, the 32-bit 861 Node_ID is not required to have any association 862 with the IPv4 address space." 863 SYNTAX Unsigned32 865 MplsIccId ::= TEXTUAL-CONVENTION 866 STATUS current 867 DESCRIPTION 868 "The ICC is a string of one to six characters, each 869 character being either alphabetic (i.e. A-Z) or 870 numeric (i.e. 0-9) characters. 871 Alphabetic characters in the ICC SHOULD be represented 873 with upper case letters." 874 SYNTAX OCTET STRING (SIZE (1..6)) 876 MplsLocalId ::= TEXTUAL-CONVENTION 877 DISPLAY-HINT "d" 878 STATUS current 879 DESCRIPTION 880 "This textual convention is used in accommodating the bigger 881 size Global_Node_ID and/or ICC with lower size LSR 882 identifier in order to index the mplsTunnelTable. 884 The Local Identifier is configured between 1 and 16777215, 885 as valid IP address range starts from 16777216(01.00.00.00). 886 This range is chosen to identify the mplsTunnelTable's 887 Ingress/Egress LSR-id is IP address or Local identifier, 888 if the configured range is not IP address, administrator is 889 expected to retrieve the complete information 890 (Global_Node_ID or ICC) from mplsNodeConfigTable. This way, 891 existing mplsTunnelTable is reused for bidirectional tunnel 892 extensions for MPLS based transport networks. 894 This Local Identifier allows the administrator to assign 895 a unique identifier to map Global_Node_ID and/or ICC." 896 SYNTAX Unsigned32(1..16777215) 898 -- MPLS-TC-EXT-STD-MIB module ends 899 END 901 11. MPLS Identifier MIB definitions 903 MPLS-ID-STD-MIB DEFINITIONS ::= BEGIN 905 IMPORTS 906 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE 907 FROM SNMPv2-SMI -- [RFC2578] 908 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 909 FROM SNMPv2-CONF -- [RFC2580] 910 mplsStdMIB 911 FROM MPLS-TC-STD-MIB -- [RFC3811] 912 MplsGlobalId, MplsIccId, MplsNodeId 913 FROM MPLS-TC-EXT-STD-MIB 914 ; 916 mplsIdStdMIB MODULE-IDENTITY 917 LAST-UPDATED 918 "201204080000Z" -- April 08, 2012 919 ORGANIZATION 920 "Multiprotocol Label Switching (MPLS) Working Group" 922 CONTACT-INFO 923 " 924 Venkatesan Mahalingam 925 Dell Inc, 926 350 Holger way, San Jose, CA, USA 927 Email: venkat.mahalingams@gmail.com 929 Kannan KV Sampath 930 Aricent, 931 India 932 Email: Kannan.Sampath@aricent.com 934 Sam Aldrin 935 Huawei Technologies 936 2330 Central Express Way, 937 Santa Clara, CA 95051, USA 938 Email: aldrin.ietf@gmail.com 940 Thomas D. Nadeau 941 Juniper Networks 942 10 Technology Park Drive, Westford, MA 01886 943 Email: tnadeau@juniper.net 944 " 946 DESCRIPTION 947 "Copyright (c) 2012 IETF Trust and the persons identified 948 as the document authors. All rights reserved. 950 This MIB module contains generic object definitions for 951 MPLS Traffic Engineering in transport networks." 953 -- Revision history. 955 REVISION 956 "201204080000Z" -- April 08, 2012 957 DESCRIPTION 958 "MPLS identifiers mib object extension" 960 ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value 962 -- traps 963 mplsIdNotifications OBJECT IDENTIFIER ::= { mplsIdStdMIB 0 } 964 -- tables, scalars 965 mplsIdObjects OBJECT IDENTIFIER ::= { mplsIdStdMIB 1 } 966 -- conformance 967 mplsIdConformance OBJECT IDENTIFIER ::= { mplsIdStdMIB 2 } 969 -- MPLS common objects 971 mplsGlobalId OBJECT-TYPE 972 SYNTAX MplsGlobalId 973 MAX-ACCESS read-write 974 STATUS current 975 DESCRIPTION 976 "This object allows the administrator to assign a unique 977 operator identifier also called MPLS-TP Global_ID." 978 REFERENCE 979 "MPLS-TP Identifiers [RFC6370]." 980 ::= { mplsIdObjects 1 } 982 mplsIcc OBJECT-TYPE 983 SYNTAX MplsIccId 984 MAX-ACCESS read-write 985 STATUS current 986 DESCRIPTION 987 "This object allows the operator or service provider to 988 assign a unique MPLS-TP ITU-T Carrier Code (ICC) to a 989 network." 990 REFERENCE 991 "MPLS-TP Identifiers [RFC6370]." 992 ::= { mplsIdObjects 2 } 994 mplsNodeId OBJECT-TYPE 995 SYNTAX MplsNodeId 996 MAX-ACCESS read-write 997 STATUS current 998 DESCRIPTION 999 "This object allows the operator or service provider to 1000 assign a unique MPLS-TP Node_ID. 1002 The Node_ID is assigned within the scope of 1003 the Global_ID." 1004 REFERENCE 1005 "MPLS-TP Identifiers [RFC6370]." 1006 ::= { mplsIdObjects 3 } 1008 -- Module compliance. 1010 mplsIdGroups 1011 OBJECT IDENTIFIER ::= { mplsIdConformance 1 } 1013 mplsIdCompliances 1014 OBJECT IDENTIFIER ::= { mplsIdConformance 2 } 1016 -- Compliance requirement for fully compliant implementations. 1018 mplsIdModuleFullCompliance MODULE-COMPLIANCE 1019 STATUS current 1020 DESCRIPTION 1021 "Compliance statement for agents that provide full 1022 support the MPLS-ID-STD-MIB module." 1024 MODULE -- this module 1026 -- The mandatory group has to be implemented by all 1027 -- LSRs that originate/terminate MPLS-TP paths. 1029 MANDATORY-GROUPS { 1030 mplsIdScalarGroup 1031 } 1033 ::= { mplsIdCompliances 1 } 1035 -- Compliance requirement for read-only implementations. 1037 mplsIdModuleReadOnlyCompliance MODULE-COMPLIANCE 1038 STATUS current 1039 DESCRIPTION 1040 "Compliance statement for agents that provide full 1041 support the MPLS-ID-STD-MIB module." 1043 MODULE -- this module 1045 -- The mandatory group has to be implemented by all 1046 -- LSRs that originate/terminate MPLS-TP paths. 1048 MANDATORY-GROUPS { 1049 mplsIdScalarGroup 1050 } 1052 ::= { mplsIdCompliances 2 } 1054 -- Units of conformance. 1056 mplsIdScalarGroup OBJECT-GROUP 1057 OBJECTS { mplsGlobalId, 1058 mplsNodeId, 1059 mplsIcc 1061 } 1062 STATUS current 1063 DESCRIPTION 1064 "Scalar object needed to implement MPLS TP path." 1065 ::= { mplsIdGroups 1 } 1067 -- MPLS-ID-STD-MIB module ends 1068 END 1070 12. MPLS LSR Extension MIB definitions 1072 MPLS-LSR-EXT-STD-MIB DEFINITIONS ::= BEGIN 1074 IMPORTS 1075 MODULE-IDENTITY, OBJECT-TYPE 1076 FROM SNMPv2-SMI -- [RFC2578] 1077 MODULE-COMPLIANCE, OBJECT-GROUP 1078 FROM SNMPv2-CONF -- [RFC2580] 1079 mplsStdMIB 1080 FROM MPLS-TC-STD-MIB -- [RFC3811] 1081 RowPointer 1082 FROM SNMPv2-TC -- [RFC2579] 1083 mplsXCIndex, mplsXCInSegmentIndex, mplsXCOutSegmentIndex, 1084 mplsInSegmentGroup, mplsOutSegmentGroup, mplsXCGroup, 1085 mplsPerfGroup, mplsLsrNotificationGroup 1086 FROM MPLS-LSR-STD-MIB; -- [RFC3813] 1088 mplsLsrExtStdMIB MODULE-IDENTITY 1089 LAST-UPDATED 1090 "201204080000Z" -- April 08, 2012 1091 ORGANIZATION 1092 "Multiprotocol Label Switching (MPLS) Working Group" 1093 CONTACT-INFO 1094 " 1095 Venkatesan Mahalingam 1096 Dell Inc, 1097 350 Holger way, San Jose, CA, USA 1098 Email: venkat.mahalingams@gmail.com 1100 Kannan KV Sampath 1101 Aricent, 1102 India 1103 Email: Kannan.Sampath@aricent.com 1105 Sam Aldrin 1106 Huawei Technologies 1107 2330 Central Express Way, 1108 Santa Clara, CA 95051, USA 1110 Email: aldrin.ietf@gmail.com 1112 Thomas D. Nadeau 1113 Juniper Networks 1114 10 Technology Park Drive, Westford, MA 01886 1115 Email: tnadeau@juniper.net 1116 " 1117 DESCRIPTION 1118 "Copyright (c) 2012 IETF Trust and the persons identified 1119 as the document authors. All rights reserved. 1121 This MIB module contains generic object definitions for 1123 MPLS LSR in transport networks." 1125 -- Revision history. 1127 REVISION 1128 "201204080000Z" -- April 08, 2012 1129 DESCRIPTION 1130 "MPLS LSR specific mib objects extension" 1132 ::= { mplsStdMIB xxx } -- xxx to be replaced with correct value 1134 -- traps 1135 mplsLsrExtNotifications OBJECT IDENTIFIER 1136 ::= { mplsLsrExtStdMIB 0 } 1137 -- tables, scalars 1138 mplsLsrExtObjects OBJECT IDENTIFIER 1139 ::= { mplsLsrExtStdMIB 1 } 1140 -- conformance 1141 mplsLsrExtConformance OBJECT IDENTIFIER 1142 ::= { mplsLsrExtStdMIB 2 } 1144 -- MPLS LSR common objects 1145 mplsXCExtTable OBJECT-TYPE 1146 SYNTAX SEQUENCE OF MplsXCExtEntry 1147 MAX-ACCESS not-accessible 1148 STATUS current 1149 DESCRIPTION 1150 "This table sparse augments the mplsXCTable of 1151 MPLS-LSR-STD-MIB [RFC3813] to provide MPLS-TP specific 1152 information about associated tunnel information" 1153 REFERENCE 1154 "1. Multiprotocol Label Switching (MPLS) Label Switching 1155 Router (LSR) Management Information Base (MIB), RFC 3813." 1156 ::= { mplsLsrExtObjects 1 } 1158 mplsXCExtEntry OBJECT-TYPE 1159 SYNTAX MplsXCExtEntry 1160 MAX-ACCESS not-accessible 1162 STATUS current 1163 DESCRIPTION 1164 "An entry in this table extends the cross connect 1165 information represented by an entry in 1166 the mplsXCTable in MPLS-LSR-STD-MIB [RFC3813] through 1167 a sparse augmentation. An entry can be created by 1168 a network administrator via SNMP SET commands, or in 1169 response to signaling protocol events." 1170 REFERENCE 1171 "1. Multiprotocol Label Switching (MPLS) Label Switching 1172 Router (LSR) Management Information Base (MIB), RFC 3813." 1174 INDEX { mplsXCIndex, mplsXCInSegmentIndex, 1175 mplsXCOutSegmentIndex } 1176 ::= { mplsXCExtTable 1 } 1178 MplsXCExtEntry ::= SEQUENCE { 1179 mplsXCExtTunnelPointer RowPointer, 1180 mplsXCOppositeDirXCPtr RowPointer 1181 } 1183 mplsXCExtTunnelPointer OBJECT-TYPE 1184 SYNTAX RowPointer 1185 MAX-ACCESS read-only 1186 STATUS current 1187 DESCRIPTION 1188 "This read-only object indicates the back pointer to 1189 the tunnel entry segment. This object cannot be modified 1190 if mplsXCRowStatus for the corresponding entry in the 1191 mplsXCTable is active(1)." 1192 REFERENCE 1193 "1. Multiprotocol Label Switching (MPLS) Label Switching 1194 Router (LSR) Management Information Base (MIB), RFC 3813." 1195 ::= { mplsXCExtEntry 1 } 1197 mplsXCOppositeDirXCPtr OBJECT-TYPE 1198 SYNTAX RowPointer 1199 MAX-ACCESS read-create 1200 STATUS current 1201 DESCRIPTION 1202 "This object indicates the pointer to the opposite 1203 direction XC entry. This object cannot be modified if 1204 mplsXCRowStatus for the corresponding entry in the 1205 mplsXCTable is active(1)." 1206 REFERENCE 1207 "1. Multiprotocol Label Switching (MPLS) Label Switching 1208 Router (LSR) Management Information Base (MIB), RFC 3813." 1209 ::= { mplsXCExtEntry 2 } 1211 mplsLsrExtGroups 1212 OBJECT IDENTIFIER ::= { mplsLsrExtConformance 1 } 1213 mplsLsrExtCompliances 1214 OBJECT IDENTIFIER ::= { mplsLsrExtConformance 2 } 1216 -- Compliance requirement for fully compliant implementations. 1218 mplsLsrExtModuleFullCompliance MODULE-COMPLIANCE 1219 STATUS current 1220 DESCRIPTION 1221 "Compliance statement for agents that provide full support 1222 for MPLS-LSR-EXT-STD-MIB. 1223 The mandatory group has to be implemented by all LSRs 1224 that originate, terminate, or act as transit for 1225 TE-LSPs/tunnels. 1226 In addition, depending on the type of tunnels supported, 1227 other groups become mandatory as explained below." 1229 MODULE MPLS-LSR-STD-MIB -- The MPLS-LSR-STD-MIB, RFC3813 1231 MANDATORY-GROUPS { 1232 mplsInSegmentGroup, 1233 mplsOutSegmentGroup, 1234 mplsXCGroup, 1235 mplsPerfGroup, 1236 mplsLsrNotificationGroup 1237 } 1239 MODULE -- this module 1241 MANDATORY-GROUPS { 1242 mplsXCExtGroup 1243 } 1245 OBJECT mplsXCExtTunnelPointer 1246 SYNTAX RowPointer 1247 MIN-ACCESS read-only 1248 DESCRIPTION 1249 "The only valid value for Tunnel Pointer is mplsTunnelTable 1250 entry." 1252 ::= { mplsLsrExtCompliances 1 } 1254 -- Compliance requirement for implementations that provide 1255 -- read-only access. 1257 mplsLsrExtModuleReadOnlyCompliance MODULE-COMPLIANCE 1258 STATUS current 1259 DESCRIPTION 1260 "Compliance requirement for implementations that only 1261 provide read-only support for MPLS-LSR-EXT-STD-MIB. 1262 Such devices can then be monitored but cannot be 1263 configured using this MIB module." 1265 MODULE MPLS-LSR-STD-MIB 1267 MANDATORY-GROUPS { 1268 mplsInterfaceGroup, 1269 mplsInSegmentGroup, 1270 mplsOutSegmentGroup, 1271 mplsXCGroup, 1272 mplsPerfGroup 1273 } 1275 MODULE -- this module 1277 MANDATORY-GROUPS { 1278 mplsXCExtGroup 1279 } 1281 OBJECT mplsXCExtTunnelPointer 1282 SYNTAX RowPointer 1283 MIN-ACCESS read-only 1284 DESCRIPTION 1285 "The only valid value for Tunnel Pointer is mplsTunnelTable 1286 entry." 1288 OBJECT mplsXCOppositeDirXCPtr 1289 SYNTAX RowPointer 1290 MIN-ACCESS read-only 1291 DESCRIPTION 1292 "The only valid value for Tunnel Pointer is mplsXCTable 1293 entry." 1295 ::= { mplsLsrExtCompliances 2 } 1297 mplsXCExtGroup OBJECT-GROUP 1298 OBJECTS { 1299 mplsXCExtTunnelPointer, 1300 mplsXCOppositeDirXCPtr 1301 } 1302 STATUS current 1303 DESCRIPTION 1304 "This object should be supported in order to access 1305 the tunnel entry from XC entry." 1306 ::= { mplsLsrExtGroups 1 } 1308 -- MPLS-LSR-EXT-STD-MIB module ends 1309 END 1311 13. MPLS Tunnel Extension MIB definitions 1313 MPLS-TE-EXT-STD-MIB DEFINITIONS ::= BEGIN 1315 IMPORTS 1316 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Counter32, 1317 Counter64, Gauge32, zeroDotZero, NOTIFICATION-TYPE 1318 FROM SNMPv2-SMI -- [RFC2578] 1319 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 1320 FROM SNMPv2-CONF -- [RFC2580] 1321 TruthValue, RowStatus, RowPointer, StorageType 1322 FROM SNMPv2-TC -- [RFC2579] 1323 MplsLocalId, MplsGlobalId, MplsNodeId, MplsIccId 1324 FROM MPLS-TC-EXT-STD-MIB 1325 mplsStdMIB, MplsTunnelIndex, MplsTunnelInstanceIndex 1326 FROM MPLS-TC-STD-MIB -- [RFC3811] 1327 mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, 1328 mplsTunnelEgressLSRId 1329 FROM MPLS-TE-STD-MIB -- [RFC3812] 1330 ; 1332 mplsTeExtStdMIB MODULE-IDENTITY 1333 LAST-UPDATED 1334 "201204080000Z" -- April 08, 2012 1335 ORGANIZATION 1336 "Multiprotocol Label Switching (MPLS) Working Group" 1337 CONTACT-INFO 1338 " 1339 Venkatesan Mahalingam 1340 Dell Inc, 1341 350 Holger way, San Jose, CA, USA 1342 Email: venkat.mahalingams@gmail.com 1344 Kannan KV Sampath 1345 Aricent, 1347 India 1348 Email: Kannan.Sampath@aricent.com 1350 Sam Aldrin 1351 Huawei Technologies 1352 2330 Central Express Way, 1353 Santa Clara, CA 95051, USA 1354 Email: aldrin.ietf@gmail.com 1356 Thomas D. Nadeau 1357 Juniper Networks 1358 10 Technology Park Drive, Westford, MA 01886 1359 Email: tnadeau@juniper.net 1360 " 1361 DESCRIPTION 1362 "Copyright (c) 2012 IETF Trust and the persons identified 1363 as the document authors. All rights reserved. 1365 This MIB module contains generic object definitions for 1366 MPLS Traffic Engineering in transport networks." 1368 -- Revision history. 1370 REVISION 1371 "201204080000Z" -- April 08, 2012 1373 DESCRIPTION 1374 "MPLS TE mib objects extension" 1376 ::= { mplsStdMIB xxx } -- xxx to be replaced 1377 -- with correct value 1379 -- Top level components of this MIB module. 1381 -- traps 1382 mplsTeExtNotifications OBJECT IDENTIFIER 1383 ::= { mplsTeExtStdMIB 0 } 1384 -- tables, scalars 1385 mplsTeExtObjects OBJECT IDENTIFIER 1386 ::= { mplsTeExtStdMIB 1 } 1387 -- conformance 1388 mplsTeExtConformance OBJECT IDENTIFIER 1389 ::= { mplsTeExtStdMIB 2 } 1391 -- Start of MPLS Transport Profile Node configuration table 1392 mplsNodeConfigTable OBJECT-TYPE 1393 SYNTAX SEQUENCE OF MplsNodeConfigEntry 1394 MAX-ACCESS not-accessible 1395 STATUS current 1396 DESCRIPTION 1397 "This table allows the administrator to map a node or 1398 LSR Identifier (IP compatible [Global_Node_ID] or ICC) 1399 with a local identifier. 1401 This table is created to reuse the existing 1402 mplsTunnelTable for MPLS based transport network 1403 tunnels also. 1404 Since the MPLS tunnel's Ingress/Egress LSR identifiers' 1405 size (Unsigned32) value is not compatible for 1406 MPLS-TP tunnel i.e. Global_Node_Id of size 8 bytes and 1407 ICC of size 6 bytes, there exists a need to map the 1408 Global_Node_ID or ICC with the local identifier of size 1409 4 bytes (Unsigned32) value in order 1410 to index (Ingress/Egress LSR identifier) 1411 the existing mplsTunnelTable." 1412 ::= { mplsTeExtObjects 1 } 1414 mplsNodeConfigEntry OBJECT-TYPE 1415 SYNTAX MplsNodeConfigEntry 1416 MAX-ACCESS not-accessible 1417 STATUS current 1418 DESCRIPTION 1420 "An entry in this table represents a mapping 1421 identification for the operator or service provider 1422 with node or LSR. 1424 As per [RFC6370], this mapping is 1426 represented as Global_Node_ID or ICC. 1428 Note: Each entry in this table should have a unique 1429 Global_ID and Node_ID combination." 1430 INDEX { mplsNodeConfigLocalId } 1431 ::= { mplsNodeConfigTable 1 } 1433 MplsNodeConfigEntry ::= SEQUENCE { 1434 mplsNodeConfigLocalId MplsLocalId, 1435 mplsNodeConfigGlobalId MplsGlobalId, 1436 mplsNodeConfigNodeId MplsNodeId, 1437 mplsNodeConfigIccId MplsIccId, 1438 mplsNodeConfigRowStatus RowStatus, 1439 mplsNodeConfigStorageType StorageType 1441 } 1443 mplsNodeConfigLocalId OBJECT-TYPE 1444 SYNTAX MplsLocalId 1445 MAX-ACCESS not-accessible 1446 STATUS current 1447 DESCRIPTION 1448 "This object allows the administrator to assign a unique 1449 local identifier to map Global_Node_ID or ICC." 1450 ::= { mplsNodeConfigEntry 1 } 1452 mplsNodeConfigGlobalId OBJECT-TYPE 1453 SYNTAX MplsGlobalId 1454 MAX-ACCESS read-write 1455 STATUS current 1456 DESCRIPTION 1457 "This object indicates the Global Operator Identifier. 1458 This object value should be zero when 1459 mplsNodeConfigIccId is configured with non-null value." 1460 REFERENCE 1461 "MPLS-TP Identifiers [RFC6370]." 1462 ::= { mplsNodeConfigEntry 2 } 1464 mplsNodeConfigNodeId OBJECT-TYPE 1465 SYNTAX MplsNodeId 1466 MAX-ACCESS read-write 1467 STATUS current 1468 DESCRIPTION 1469 "This object indicates the Node_ID within the operator. 1470 This object value should be zero when mplsNodeConfigIccId 1471 is configured with non-null value." 1472 REFERENCE 1473 "MPLS-TP Identifiers [RFC6370]." 1474 ::= { mplsNodeConfigEntry 3 } 1476 mplsNodeConfigIccId OBJECT-TYPE 1477 SYNTAX MplsIccId 1478 MAX-ACCESS read-write 1479 STATUS current 1480 DESCRIPTION 1481 "This object allows the operator or service provider to 1482 configure a unique MPLS-TP ITU-T Carrier Code (ICC) 1483 either for Ingress ID or Egress ID. 1485 This object value should be zero when 1486 mplsNodeConfigGlobalId and mplsNodeConfigNodeId are 1487 assigned with non-zero value." 1488 REFERENCE 1489 "MPLS-TP Identifiers [RFC6370]." 1490 ::= { mplsNodeConfigEntry 4 } 1492 mplsNodeConfigRowStatus OBJECT-TYPE 1493 SYNTAX RowStatus 1494 MAX-ACCESS read-create 1495 STATUS current 1496 DESCRIPTION 1497 "This object allows the administrator to create, modify, 1498 and/or delete a row in this table." 1499 ::= { mplsNodeConfigEntry 5 } 1501 mplsNodeConfigStorageType OBJECT-TYPE 1502 SYNTAX StorageType 1503 MAX-ACCESS read-create 1504 STATUS current 1505 DESCRIPTION 1506 "This variable indicates the storage type for this 1507 object. 1508 Conceptual rows having the value 'permanent' 1509 need not allow write-access to any columnar 1510 objects in the row." 1511 DEFVAL { volatile } 1512 ::= { mplsNodeConfigEntry 6 } 1514 -- End of MPLS Transport Profile Node configuration table 1516 -- Start of MPLS Transport Profile Node IP compatible 1517 -- mapping table 1519 mplsNodeIpMapTable OBJECT-TYPE 1520 SYNTAX SEQUENCE OF MplsNodeIpMapEntry 1522 MAX-ACCESS not-accessible 1523 STATUS current 1524 DESCRIPTION 1525 "This read-only table allows the administrator to retrieve 1526 the local identifier for a given Global_Node_ID in an IP 1527 compatible operator environment. 1529 This table MAY be used in on-demand and/or proactive 1530 OAM operations to get the Ingress/Egress LSR identifier 1531 (Local Identifier) from Src-Global_Node_ID 1532 or Dst-Global_Node_ID and the Ingress and Egress LSR 1533 identifiers are used to retrieve the tunnel entry. 1535 This table returns nothing when the associated entry 1536 is not defined in mplsNodeConfigTable." 1537 ::= { mplsTeExtObjects 2 } 1539 mplsNodeIpMapEntry OBJECT-TYPE 1540 SYNTAX MplsNodeIpMapEntry 1541 MAX-ACCESS not-accessible 1542 STATUS current 1543 DESCRIPTION 1544 "An entry in this table represents a mapping of 1545 Global_Node_ID with the local identifier. 1547 An entry in this table is created automatically when 1548 the Local identifier is associated with Global_ID and 1549 Node_Id in the mplsNodeConfigTable. 1551 Note: Each entry in this table should have a unique 1552 Global_ID and Node_ID combination." 1553 INDEX { mplsNodeIpMapGlobalId, 1554 mplsNodeIpMapNodeId 1555 } 1556 ::= { mplsNodeIpMapTable 1 } 1558 MplsNodeIpMapEntry ::= SEQUENCE { 1559 mplsNodeIpMapGlobalId MplsGlobalId, 1560 mplsNodeIpMapNodeId MplsNodeId, 1561 mplsNodeIpMapLocalId MplsLocalId 1562 } 1564 mplsNodeIpMapGlobalId OBJECT-TYPE 1565 SYNTAX MplsGlobalId 1566 MAX-ACCESS not-accessible 1567 STATUS current 1568 DESCRIPTION 1569 "This object indicates the Global_ID." 1570 ::= { mplsNodeIpMapEntry 1 } 1572 mplsNodeIpMapNodeId OBJECT-TYPE 1573 SYNTAX MplsNodeId 1574 MAX-ACCESS not-accessible 1575 STATUS current 1576 DESCRIPTION 1577 "This object indicates the Node_ID within the 1578 operator." 1579 ::= { mplsNodeIpMapEntry 2 } 1581 mplsNodeIpMapLocalId OBJECT-TYPE 1582 SYNTAX MplsLocalId 1583 MAX-ACCESS read-only 1584 STATUS current 1585 DESCRIPTION 1586 "This object contains an IP compatible local identifier 1587 which is defined in mplsNodeConfigTable." 1588 ::= { mplsNodeIpMapEntry 3 } 1590 -- End MPLS Transport Profile Node IP compatible table 1592 -- Start of MPLS Transport Profile Node ICC based table 1594 mplsNodeIccMapTable OBJECT-TYPE 1595 SYNTAX SEQUENCE OF MplsNodeIccMapEntry 1596 MAX-ACCESS not-accessible 1597 STATUS current 1598 DESCRIPTION 1599 "This read-only table allows the administrator to retrieve 1600 the local identifier for a given ICC operator in an ICC 1601 operator environment. 1603 This table MAY be used in on-demand and/or proactive 1604 OAM operations to get the Ingress/Egress LSR 1605 identifier (Local Identifier) from Src-ICC 1606 or Dst-ICC and the Ingress and Egress LSR 1607 identifiers are used to retrieve the tunnel entry. 1608 This table returns nothing when the associated entry 1609 is not defined in mplsNodeConfigTable." 1610 ::= { mplsTeExtObjects 3 } 1612 mplsNodeIccMapEntry OBJECT-TYPE 1613 SYNTAX MplsNodeIccMapEntry 1614 MAX-ACCESS not-accessible 1615 STATUS current 1616 DESCRIPTION 1617 "An entry in this table represents a mapping of ICC with 1618 the local identifier. 1620 An entry in this table is created automatically when 1621 the Local identifier is associated with ICC in 1622 the mplsNodeConfigTable." 1623 INDEX { mplsNodeIccMapIccId } 1624 ::= { mplsNodeIccMapTable 1 } 1626 MplsNodeIccMapEntry ::= SEQUENCE { 1627 mplsNodeIccMapIccId MplsIccId, 1628 mplsNodeIccMapLocalId MplsLocalId 1629 } 1631 mplsNodeIccMapIccId OBJECT-TYPE 1632 SYNTAX MplsIccId 1633 MAX-ACCESS not-accessible 1634 STATUS current 1635 DESCRIPTION 1636 "This object allows the operator or service provider to 1637 configure a unique MPLS-TP ITU-T Carrier Code (ICC) 1638 either for Ingress or Egress LSR ID. 1640 The ICC is a string of one to six characters, each 1641 character being either alphabetic (i.e. A-Z) or 1642 numeric (i.e. 0-9) characters. Alphabetic characters 1643 in the ICC should be represented with upper case 1644 letters." 1645 ::= { mplsNodeIccMapEntry 1 } 1647 mplsNodeIccMapLocalId OBJECT-TYPE 1648 SYNTAX MplsLocalId 1649 MAX-ACCESS read-only 1650 STATUS current 1651 DESCRIPTION 1652 "This object contains an ICC based local identifier 1653 which is defined in mplsNodeConfigTable." 1655 ::= { mplsNodeIccMapEntry 2 } 1657 -- End MPLS Transport Profile Node ICC based table 1659 -- Start of MPLS Tunnel table extension 1661 mplsTunnelExtTable OBJECT-TYPE 1662 SYNTAX SEQUENCE OF MplsTunnelExtEntry 1663 MAX-ACCESS not-accessible 1664 STATUS current 1665 DESCRIPTION 1666 "This table represents MPLS-TP specific extensions to 1667 mplsTunnelTable. 1669 As per MPLS-TP Identifiers [RFC6370], LSP_ID for IP based 1670 co-routed bidirectional tunnel, 1672 A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: 1673 Node_ID::Tunnel_Num}::LSP_Num 1675 LSP_ID for IP based associated bidirectional tunnel, 1676 A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: 1677 Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num} 1679 mplsTunnelTable is reused for forming the LSP_ID 1680 as follows, 1682 Source Tunnel_Num is mapped with mplsTunnelIndex, 1683 Source Node_ID is mapped with 1684 mplsTunnelIngressLSRId, Destination Node_ID is 1685 mapped with mplsTunnelEgressLSRId LSP_Num is mapped with 1686 mplsTunnelInstance. 1688 Source Global_Node_ID and/or ICC and Destination 1689 Global_Node_ID and/or ICC are maintained in the 1690 mplsNodeConfigTable and mplsNodeConfigLocalId is 1691 used to create an entry in mplsTunnelTable." 1692 REFERENCE 1693 "MPLS-TP Identifiers [RFC6370]." 1694 ::= { mplsTeExtObjects 4 } 1696 mplsTunnelExtEntry OBJECT-TYPE 1697 SYNTAX MplsTunnelExtEntry 1698 MAX-ACCESS not-accessible 1699 STATUS current 1700 DESCRIPTION 1701 "An entry in this table represents MPLS-TP 1702 specific additional tunnel configurations." 1703 INDEX { 1704 mplsTunnelIndex, 1705 mplsTunnelInstance, 1706 mplsTunnelIngressLSRId, 1707 mplsTunnelEgressLSRId 1708 } 1709 ::= { mplsTunnelExtTable 1 } 1711 MplsTunnelExtEntry ::= SEQUENCE { 1712 mplsTunnelOppositeDirPtr RowPointer, 1713 mplsTunnelExtOppositeDirTnlValid TruthValue, 1714 mplsTunnelExtDestTnlIndex MplsTunnelIndex, 1715 mplsTunnelExtDestTnlLspIndex MplsTunnelInstanceIndex, 1716 mplsTunnelExtDestTnlValid TruthValue 1717 } 1719 mplsTunnelOppositeDirPtr OBJECT-TYPE 1720 SYNTAX RowPointer 1721 MAX-ACCESS read-create 1722 STATUS current 1723 DESCRIPTION 1724 "This object is applicable only for the bidirectional 1725 tunnel that has the forward and reverse LSPs in the 1726 same tunnel or in the different tunnels. 1728 This object holds the opposite direction tunnel entry 1729 if the bidirectional tunnel is setup by configuring two 1730 tunnel entries in mplsTunnelTable. 1732 The value of zeroDotZero indicates single tunnel entry 1733 is used for bidirectional tunnel setup." 1734 DEFVAL { zeroDotZero } 1735 ::= { mplsTunnelExtEntry 1 } 1737 mplsTunnelExtOppositeDirTnlValid OBJECT-TYPE 1738 SYNTAX TruthValue 1739 MAX-ACCESS read-create 1740 STATUS current 1741 DESCRIPTION 1742 "Denotes whether or not this tunnel uses 1743 mplsTunnelOppositeDirPtr for identifying the opposite 1744 direction tunnel information. Note that if this variable 1745 is set to true then the mplsTunnelOppositeDirPtr should 1746 point to the first accessible row of the opposite 1747 direction tunnel." 1748 DEFVAL { false } 1749 ::= { mplsTunnelExtEntry 2 } 1751 mplsTunnelExtDestTnlIndex OBJECT-TYPE 1752 SYNTAX MplsTunnelIndex 1753 MAX-ACCESS read-create 1754 STATUS current 1755 DESCRIPTION 1756 "This object is applicable only for the bidirectional 1757 tunnel that has the forward and reverse LSPs in the 1758 same tunnel or in the different tunnels. 1760 This object holds the same value as that of the 1761 mplsTunnelIndex of mplsTunnelEntry if the forward and 1762 reverse LSPs are in the same tunnel. Otherwise, 1763 this object holds the value of the other direction 1764 associated LSP's mplsTunnelIndex from a different 1765 tunnel. 1767 The values of this object and the 1768 mplsTunnelExtDestTnlLspIndex object together can be used 1769 to identify an opposite direction LSP i.e. if the 1770 mplsTunnelIndex and mplsTunnelInstance hold the value 1771 for forward LSP, this object and 1772 mplsTunnelExtDestTnlLspIndex can be used to retrieve 1773 the reverse direction LSP and vice versa. 1775 This object and mplsTunnelExtDestTnlLspIndex values 1776 provide the first two indices of tunnel entry and 1777 the remaining indices can be derived as follows, 1778 if both the forward and reverse LSPs are present in 1779 the same tunnel, the opposite direction LSP's Ingress 1780 and Egress Identifier will be same for both the LSPs, 1781 else the Ingress and Egress Identifiers should be 1782 swapped in order to index the other direction tunnel." 1784 ::= { mplsTunnelExtEntry 3 } 1786 mplsTunnelExtDestTnlLspIndex OBJECT-TYPE 1787 SYNTAX MplsTunnelInstanceIndex 1788 MAX-ACCESS read-create 1789 STATUS current 1790 DESCRIPTION 1791 "This object is applicable only for the bidirectional 1792 tunnel that has the forward and reverse LSPs in the 1793 same tunnel or in the different tunnels. 1795 This object should contain different value if both the 1796 forward and reverse LSPs present in the same tunnel. 1798 This object can contain same value or different values 1799 if the forward and reverse LSPs present in the different 1800 tunnels." 1802 ::= { mplsTunnelExtEntry 4 } 1804 mplsTunnelExtDestTnlValid OBJECT-TYPE 1805 SYNTAX TruthValue 1806 MAX-ACCESS read-create 1807 STATUS current 1808 DESCRIPTION 1809 "Denotes whether or not this tunnel uses 1810 mplsTunnelExtDestTnlIndex and 1811 mplsTunnelExtDestTnlLspIndex for identifying 1812 the opposite direction tunnel information. Note that if 1813 this variable is set to true then the 1814 mplsTunnelExtDestTnlIndex and 1815 mplsTunnelExtDestTnlLspIndex objects should have 1816 the valid opposite direction tunnel indices." 1817 DEFVAL { false } 1818 ::= { mplsTunnelExtEntry 5 } 1820 -- End of MPLS Tunnel table extension 1822 mplsTunnelReversePerfTable OBJECT-TYPE 1823 SYNTAX SEQUENCE OF MplsTunnelReversePerfEntry 1824 MAX-ACCESS not-accessible 1825 STATUS current 1826 DESCRIPTION 1827 "This table extends the mplsTunnelTable to provide 1828 per-tunnel packet performance information for the reverse 1829 direction of a bidirectional tunnel. It can be seen as 1830 supplementing the mplsTunnelPerfTable, which augments the 1831 mplsTunnelTable. 1833 For links that do not transport packets, these packet 1834 counters cannot be maintained. For such links, attempts 1835 to read the objects in this table will return 1836 noSuchInstance." 1838 REFERENCE 1839 "1. Multiprotocol Label Switching (MPLS) Traffic 1840 Engineering (TE)Management Information Base (MIB), 1841 RFC 3812." 1842 ::= { mplsTeExtObjects 5 } 1844 mplsTunnelReversePerfEntry OBJECT-TYPE 1845 SYNTAX MplsTunnelReversePerfEntry 1846 MAX-ACCESS not-accessible 1847 STATUS current 1848 DESCRIPTION 1849 "An entry in this table is created by the LSR for every 1850 bidirectional MPLS tunnel where packets are visible to the 1851 LSR." 1852 INDEX { 1853 mplsTunnelIndex, 1854 mplsTunnelInstance, 1855 mplsTunnelIngressLSRId, 1856 mplsTunnelEgressLSRId 1857 } 1858 ::= { mplsTunnelReversePerfTable 1 } 1860 MplsTunnelReversePerfEntry ::= SEQUENCE { 1861 mplsTunnelReversePerfPackets Counter32, 1862 mplsTunnelReversePerfHCPackets Counter64, 1863 mplsTunnelReversePerfErrors Counter32, 1864 mplsTunnelReversePerfBytes Counter32, 1865 mplsTunnelReversePerfHCBytes Counter64 1866 } 1868 mplsTunnelReversePerfPackets OBJECT-TYPE 1869 SYNTAX Counter32 1870 MAX-ACCESS read-only 1871 STATUS current 1872 DESCRIPTION 1873 "Number of packets forwarded on the tunnel in the reverse 1874 direction if it is bidirectional. 1876 This object represents the 32-bit value of the least 1877 significant part of the 64-bit value if both 1878 mplsTunnelReversePerfHCPackets and this object 1879 are returned. 1881 For links that do not transport packets, this packet 1882 counter cannot be maintained. For such links, this value 1883 will return noSuchInstance." 1884 ::= { mplsTunnelReversePerfEntry 1 } 1885 mplsTunnelReversePerfHCPackets OBJECT-TYPE 1886 SYNTAX Counter64 1887 MAX-ACCESS read-only 1888 STATUS current 1889 DESCRIPTION 1890 "High-capacity counter for number of packets forwarded on 1891 the tunnel in the reverse direction if it is 1892 bidirectional. 1894 For links that do not transport packets, this packet 1895 counter cannot be maintained. For such links, this value 1896 will return noSuchInstance." 1897 ::= { mplsTunnelReversePerfEntry 2 } 1899 mplsTunnelReversePerfErrors OBJECT-TYPE 1900 SYNTAX Counter32 1901 MAX-ACCESS read-only 1902 STATUS current 1903 DESCRIPTION 1904 "Number of errored packets received on the tunnel in 1905 the reverse direction if it is bidirectional. For links 1906 that do not transport packets, this packet counter cannot 1907 be maintained. For such links, this value will return 1908 noSuchInstance." 1909 ::= { mplsTunnelReversePerfEntry 3 } 1911 mplsTunnelReversePerfBytes OBJECT-TYPE 1912 SYNTAX Counter32 1913 MAX-ACCESS read-only 1914 STATUS current 1915 DESCRIPTION 1916 "Number of bytes forwarded on the tunnel in the reverse 1917 direction if it is bidirectional. 1919 This object represents the 32-bit value of the least 1920 significant part of the 64-bit value if both 1921 mplsTunnelReversePerfHCBytes and this object are returned. 1923 For links that do not transport packets, this packet 1924 counter cannot be maintained. For such links, this value 1925 will return noSuchInstance." 1926 ::= { mplsTunnelReversePerfEntry 4 } 1928 mplsTunnelReversePerfHCBytes OBJECT-TYPE 1929 SYNTAX Counter64 1930 MAX-ACCESS read-only 1931 STATUS current 1932 DESCRIPTION 1933 "High-capacity counter for number of bytes forwarded on the 1934 tunnel in the reverse direction if it is bidirectional. 1936 For links that do not transport packets, this packet 1937 counter cannot be maintained. For such links, this value 1938 will return noSuchInstance." 1939 ::= { mplsTunnelReversePerfEntry 5 } 1941 -- Notifications. 1942 -- Notifications objects need to be added here. 1943 -- End of notifications. 1945 -- Module compliance. 1947 mplsTeExtGroups 1948 OBJECT IDENTIFIER ::= { mplsTeExtConformance 1 } 1950 mplsTeExtCompliances 1951 OBJECT IDENTIFIER ::= { mplsTeExtConformance 2 } 1953 -- Compliance requirement for fully compliant implementations. 1955 mplsTeExtModuleFullCompliance MODULE-COMPLIANCE 1956 STATUS current 1957 DESCRIPTION 1958 "Compliance statement for agents that provide full 1959 support the MPLS-TE-EXT-STD-MIB module." 1961 MODULE -- this module 1963 -- The mandatory group has to be implemented by all 1964 -- LSRs that originate/terminate MPLS-TP tunnels. 1965 -- In addition, depending on the type of tunnels 1966 -- supported, other groups become mandatory as 1967 -- explained below. 1969 MANDATORY-GROUPS { 1970 mplsTunnelExtGroup 1971 } 1973 GROUP mplsTunnelExtIpOperatorGroup 1975 DESCRIPTION 1976 "This group is mandatory for devices which support 1977 configuration of IP based identifier tunnels." 1979 GROUP mplsTunnelExtIccOperatorGroup 1980 DESCRIPTION 1981 "This group is mandatory for devices which support 1982 configuration of ICC based tunnels." 1984 ::= { mplsTeExtCompliances 1 } 1986 -- Compliance requirement for read-only implementations. 1988 mplsTeExtModuleReadOnlyCompliance MODULE-COMPLIANCE 1989 STATUS current 1990 DESCRIPTION 1991 "Compliance statement for agents that provide full 1992 support the MPLS-TE-EXT-STD-MIB module." 1994 MODULE -- this module 1996 -- The mandatory group has to be implemented by all 1997 -- LSRs that originate/terminate MPLS-TP tunnels. 1998 -- In addition, depending on the type of tunnels 1999 -- supported, other groups become mandatory as 2000 -- explained below. 2002 MANDATORY-GROUPS { 2003 mplsTunnelExtGroup 2004 } 2006 GROUP mplsTunnelExtIpOperatorGroup 2007 DESCRIPTION 2008 "This group is mandatory for devices which support 2009 configuration of IP based identifier tunnels." 2011 GROUP mplsTunnelExtIccOperatorGroup 2013 DESCRIPTION 2014 "This group is mandatory for devices which support 2015 configuration of ICC based tunnels." 2017 ::= { mplsTeExtCompliances 2 } 2019 -- Units of conformance. 2021 mplsTunnelExtGroup OBJECT-GROUP 2022 OBJECTS { 2023 mplsTunnelOppositeDirPtr, 2024 mplsTunnelExtOppositeDirTnlValid, 2025 mplsTunnelExtDestTnlIndex, 2026 mplsTunnelExtDestTnlLspIndex, 2027 mplsTunnelExtDestTnlValid, 2028 mplsTunnelReversePerfPackets, 2029 mplsTunnelReversePerfHCPackets, 2030 mplsTunnelReversePerfErrors, 2031 mplsTunnelReversePerfBytes, 2032 mplsTunnelReversePerfHCBytes 2033 } 2035 STATUS current 2036 DESCRIPTION 2037 "Necessary, but not sufficient, set of objects to 2038 implement tunnels. In addition, depending on the 2039 operating environment, the following groups are 2040 mandatory." 2041 ::= { mplsTeExtGroups 1 } 2043 mplsTunnelExtIpOperatorGroup OBJECT-GROUP 2044 OBJECTS { mplsNodeConfigGlobalId, 2045 mplsNodeConfigNodeId, 2046 mplsNodeConfigRowStatus, 2047 mplsNodeConfigStorageType, 2048 mplsNodeIpMapLocalId 2049 } 2050 STATUS current 2051 DESCRIPTION 2052 "Object(s) needed to implement IP compatible tunnels." 2053 ::= { mplsTeExtGroups 2 } 2055 mplsTunnelExtIccOperatorGroup OBJECT-GROUP 2056 OBJECTS { mplsNodeConfigIccId, 2057 mplsNodeConfigRowStatus, 2058 mplsNodeConfigStorageType, 2059 mplsNodeIccMapLocalId 2060 } 2061 STATUS current 2062 DESCRIPTION 2063 "Object(s) needed to implement ICC based tunnels." 2064 ::= { mplsTeExtGroups 3 } 2066 -- MPLS-TE-EXT-STD-MIB module ends 2067 END 2069 14. Security Consideration 2071 There is a number of management objects defined in this MIB module 2072 that has a MAX-ACCESS clause of read-write.. Such objects may be 2073 considered sensitive or vulnerable in some network environments. 2074 The support for SET operations in a non-secure environment without 2075 proper protection can have a negative effect on network 2076 operations. 2078 Some of the readable objects in this MIB module (i.e., objects 2079 with a MAX-ACCESS other than not-accessible) may be considered 2080 sensitive or vulnerable in some network environments. 2081 It is thus important to control even GET and/or NOTIFY access to 2082 these objects and possibly to even encrypt the values of these 2083 objects when sending them over the network via SNMP. These are 2084 the tables and objects and their sensitivity/vulnerability: 2086 SNMP versions prior to SNMPv3 did not include adequate security. 2087 Even if the network itself is secure (for example by using IPsec), 2088 even then, there is no control as to who on the secure network is 2089 allowed to access and GET/SET (read/change/create/delete) 2090 the objects in this MIB module. 2092 It is recommended that implementers consider the security features 2093 as provided by the SNMPv3 framework (see [RFC3410], section 8), 2094 including full supports for the SNMPv3 cryptographic mechanisms 2095 (for authentication and privacy). 2097 Further, deployment of SNMP versions prior to SNMPv3 is not 2098 recommended. Instead, it is recommended to deploy SNMPv3 and to 2099 enable cryptographic security. It is then a customer/operator 2100 responsibility to ensure that the SNMP entity giving access to an 2101 instance of this MIB module is properly configured to give 2102 access to the objects only to those principles (users) that 2103 have legitimate rights to indeed GET or SET (change/create/delete) 2104 them. 2106 15. IANA Considerations 2108 To be added in a later version of this document. 2110 16. References 2112 16.1 Normative References 2114 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2115 Requirement Levels", BCP 14, RFC 2119, March 1997. 2117 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2118 "Structure of Management Information Version 2 (SMIv2)", 2119 STD 58, RFC 2578, April 1999. 2121 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2122 "Textual Conventions for SMIv2", STD 58, RFC 2579, April 2123 1999. 2125 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2127 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2128 April 1999. 2130 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 2131 Label Switching Architecture", RFC 3031, January 2001. 2133 16.2 Informative References 2135 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 2136 "Multiprotocol Label Switching (MPLS) Traffic Engineering 2137 (TE) Management Information Base (MIB)", RFC 3812, June 2138 2004. 2140 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 2141 "Multiprotocol Label Switching (MPLS) Label Switching 2142 (LSR) Router Management Information Base (MIB)", RFC 3813, 2143 June 2004. 2145 [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction 2146 and Applicability Statement for Internet Standard 2147 Management Framework", RFC 3410, December 2002. 2149 [RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of 2150 Textual Conventions (TCs) for Multiprotocol Label 2151 Switching (MPLS) Management", RFC 3811, June 2004. 2153 [RFC4802] Nadeau, T., Ed., and A. Farrel, Ed., "Generalized 2154 Multiprotocol Label Switching (GMPLS) Traffic 2155 Engineering Management Information Base", RFC 2156 4802, February 2007. 2157 [RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., Ed., 2158 Sprecher, N., and S. Ueno, "Requirements of an MPLS 2159 Transport Profile", RFC 5654, September 2009. 2161 [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport 2162 Profile (MPLS-TP) Identifiers", RFC 6370, September 2163 2011. 2165 17. Acknowledgments 2167 The authors would like to thank Francesco Fondelli, Josh Littlefield, 2168 Agrahara Kiran Koushik, Metrri Jain and Muly Ilan for their valuable 2169 comments. 2171 18. Authors' Addresses 2173 Sam Aldrin 2174 Huawei Technologies 2175 2330 Central Express Way, 2176 Santa Clara, CA 95051, USA 2177 Email: aldrin.ietf@gmail.com 2179 Thomas D. Nadeau 2180 Juniper Networks 2181 10 Technology Park Drive, Westford, MA 01886 2182 Email: tnadeau@juniper.net 2184 Venkatesan Mahalingam 2185 Dell Inc. 2186 350 Holger way, San Jose, CA, USA 2187 Email: venkat.mahalingams@gmail.com 2189 Kannan KV Sampath 2190 Aricent 2191 India 2192 Email: Kannan.Sampath@aricent.com