idnits 2.17.1 draft-ietf-mpls-fastreroute-mib-21.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 : ---------------------------------------------------------------------------- -- The document has examples using IPv4 documentation addresses according to RFC6890, but does not use any IPv6 documentation addresses. Maybe there should be IPv6 examples, too? Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to contain a disclaimer for pre-RFC5378 work, and may have content which was first submitted before 10 November 2008. The disclaimer is necessary when there are original authors that you have been unable to contact, or if some do not wish to grant the BCP78 rights to the IETF Trust. If you are able to get all authors (current and original) to grant those rights, you can and should remove the disclaimer; otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (Sep 2011) is 4604 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 (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Thomas D. Nadeau, Ed. 3 Internet Draft CA Technologies 4 Intended Status: Standards Track 5 Expires: Mar 2012 Agrahara S Kiran Koushik, Ed. 6 Cisco Systems, Inc. 8 Riza Cetin, Ed. 9 Alcatel 11 Sep 2011 13 Multiprotocol Label Switching (MPLS) Traffic Engineering Management 14 Information Base for Fast Reroute 16 draft-ietf-mpls-fastreroute-mib-21.txt 18 Status of this Memo 20 This Internet-Draft is submitted to IETF in full conformance with 21 the provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF), its areas, and its working groups. Note that 25 other groups may also distribute working documents as 26 Internet-Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/ietf/1id-abstracts.txt. 36 The list of Internet-Draft Shadow Directories can be accessed at 37 http://www.ietf.org/shadow.html. 39 Copyright Notice 41 Copyright (c) 2011 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and 49 restrictions with respect to this document. Code Components 50 extracted from this document must include Simplified BSD License 51 text as described in Section 4.e of the Trust Legal Provisions and 52 are provided without warranty as described in the Simplified BSD 53 License. 55 MPLS Fast-reroute MIB Sep 1, 2011 57 This document may contain material from IETF Documents or IETF 58 Contributions published or made publicly available before November 59 10, 2008. The person(s) controlling the copyright in some of this 60 material may not have granted the IETF Trust the right to allow 61 modifications of such material outside the IETF Standards Process. 62 Without obtaining an adequate license from the person(s) controlling 63 the copyright in such materials, this document may not be modified 64 outside the IETF Standards Process, and derivative works of it may 65 not be created outside the IETF Standards Process, except to format 66 it for publication as an RFC or to translate it into languages other 67 than English. 69 Abstract 71 This memo defines a portion of the Management Information Base 72 for use with network management protocols in the Internet community. 73 In particular, it describes managed objects used to support two 74 fast reroute (FRR) methods for Multiprotocol Label Switching 75 (MPLS) based traffic engineering (TE). The two methods are 76 one-to-one backup method and facility backup method. 78 Table of Contents 80 1. Introduction...............................................2 81 1.1. Conventions Used in This Document..........................2 82 2. Terminology................................................2 83 3. The Internet-Standard Management Framework.................3 84 4. Overview of the MIB Modules................................3 85 4.1. MPLS-FRR-GENERAL-STD-MIB...................................3 86 4.1.1 mplsFrrConstraintsTable....................................4 87 4.1.2 mplsFrrTunnelARHopTable....................................5 88 4.1.3 Example of relationship between various tables of 89 MPLS-FRR-GENERAL-STD-MIB...................................5 90 4.2. MPLS-FRR-ONE2ONE-STD-MIB...................................6 91 4.2.1 mplsFrrOne2OnePlrTable.....................................6 92 4.2.2 mplsFrrOne2OneDetourTable..................................6 93 4.2.3 Example of relationship between mplsFrrOne2OnePlrTable, 94 mplsFrrOne2OneDetourTable and mplsTunnelTable..............7 95 4.3 MPLS-FRR-FACILITY-STD-MIB..................................9 96 4.3.1 mplsFrrFacilityDBTable....................................10 97 4.3.2 Example of relationship between various tables of 98 MPLS-FRR-FACILITY-STD-MIB.................................10 99 5. Handling IPv6 Tunnels.....................................11 100 6. MIB Module Definitions....................................12 101 6.1 MPLS-FRR-GENERAL-STD-MIB Module Definitions...............12 102 MPLS Fast-reroute MIB Sep 1, 2011 104 6.2 MPLS-FRR-ONE2ONE-STD-MIB Module Definitions...............24 105 6.3 MPLS-FRR-FACILITY-STD-MIB Module Definitions..............34 106 7. Security Considerations...................................45 107 8. IANA Considerations.......................................46 108 8.1 IANA Considerations for MPLS-FRR-GENERAL-STD-MIB..........46 109 8.2 IANA Considerations for MPLS-FRR-ONE2ONE-STD-MIB..........46 110 8.3 IANA Considerations for MPLS-FRR-FACILITY-STD-MIB.........46 111 9. Acknowledgments...........................................47 112 10. References................................................47 113 10.1 Normative References......................................47 114 10.2 Informative References....................................48 115 11. Editors' Addresses........................................48 116 12. Contributors' Addresses...................................48 118 1. Introduction 120 This memo defines a portion of the Management Information Base (MIB) 121 containing objects used to manage Multiprotocol Label 122 Switching (MPLS)-based fast rerouting features on MPLS Label 123 Switching Routers as defined in [RFC4090]. This MIB module should 124 be used in conjunction with [RFC3811], [RFC3812] and [RFC3813]. 126 Comments should be made directly to the MPLS mailing list at 127 mpls@ietf.org. 129 1.1. Conventions Used in This Document 131 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 132 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 133 document are to be interpreted as described in RFC-2119 [RFC2119]. 135 2. Terminology 137 This document uses terminology from the document describing the 138 Multiprotocol Label Switching Architecture [RFC3031] and from 139 the document describing Fast Reroute Extensions to RSVP-TE for 140 LSP Tunnels [RFC4090]. 142 3. The Internet-Standard Management Framework 144 For a detailed overview of the documents that describe the current 145 Internet-Standard Management Framework, please refer to section 7 of 146 [RFC3410]. 148 Managed objects are accessed via a virtual information store, termed 149 the Management Information Base or MIB. MIB module objects are 150 generally accessed through the Simple Network Management Protocol 151 MPLS Fast-reroute MIB Sep 1, 2011 153 (SNMP). Objects in the MIB are defined using the mechanisms defined 154 in the Structure of Management Information (SMI). This memo 155 specifies a MIB module that is compliant to the SMIv2, which is 156 described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] 157 and STD 58, RFC 2580 [RFC2580]. 159 4. Overview of the MIB Modules 161 The specification [RFC4090] stipulates two different approaches 162 to implementing MPLS TE fast reroute: one-to-one and facility 163 backup. 165 We define three MIB modules to represent the respective 166 components: general, one-to-one and facility backup. 168 They are: 170 - MPLS-FRR-GENERAL-STD-MIB: Contains objects that apply to any 171 MPLS LSR(Label Switching Router) implementing MPLS TE fast 172 reroute functionality. 173 - MPLS-FRR-ONE2ONE-STD-MIB: Contains objects that apply to 174 one-to-one backup method. 175 - MPLS-FRR-FACILITY-STD-MIB: Contains objects that apply to 176 facility backup method. 178 Although [RFC4090] specifies that a node is able to support both 179 fast reroute methods simultaneously, common practice has shown 180 that operators choose to configure either one-to-one backup method 181 or facility backup at any given time. So by dividing the MIB 182 modules into three, we allow the developers to choose the MIB 183 modules they want to implement depending on the method supported 184 on that node. 186 4.1. MPLS-FRR-GENERAL-STD-MIB 188 This MIB module MUST be implemented if either of the fast reroute 189 methods is implemented. 191 4.1.1 mplsFrrConstraintsTable 193 This table contains objects that apply to all LSRs 194 implementing MPLS TE fast reroute functions. In particular, 195 this table defines fast reroute constraints such as 196 bandwidth for a tunnel instance to be protected by using 197 backup LSPs (detour LSPs or bypass tunnels). 199 This table MUST be implemented at the ingress node of the 200 protected TE tunnel instance to configure backup LSP setup 201 MPLS Fast-reroute MIB Sep 1, 2011 203 constraints. 205 4.1.2 mplsFrrTunnelARHopTable 207 This table extends mplsTunnelARHopTable (defined in the 208 MPLS-TE-STD-MIB [RFC3812]) with fast-reroute objects which 209 specify the local protection type or types of availability, 210 as well as what type or types are actally in-use for each 211 tunnel hop traversed by a protected TE tunnel. 213 4.1.3 Example of relationship between various tables of 214 MPLS-FRR-GENERAL-STD-MIB 216 (R1)----(R2)----(R3)----(R4)---(R5) 217 \ \ \ / 218 (R6)---(R7)------(R8) 220 Protected LSP: [R1->R2->R3->R4->R5] 222 R1's Backup: [R1->R6->R7->R8->R3] 224 In the above topology the various tables will be populated 225 as below on R1. 227 mplsFrrGeneralConstraintsTable 228 { 229 mplsFrrGeneralConstraintsIfIndexOrZero = 10,-- Interface to protect 230 mplsFrrGeneralConstraintsTunnelIndex = 1, -- Protecting tunnel 231 mplsFrrGeneralConstraintsTunnelInstance = 0, -- Use any instance 232 mplsFrrGeneralConstraintsProtectionType = 1, -- linkProtection 233 mplsFrrGeneralConstraintsSetupPrio = 0, 234 mplsFrrGeneralConstraintsHoldingPrio = 0, 235 mplsFrrGeneralConstraintsInclAnyAffinity = 0, 236 mplsFrrGeneralConstraintsInclAllAffinity = 0, 237 mplsFrrGeneralConstraintsExclAnyAffinity = 0, 238 mplsFrrGeneralConstraintsHopLimit = 0, 239 mplsFrrGeneralConstraintsBandwidth = 0, -- best effort 240 mplsFrrGeneralConstraintsStorageType = 2, -- volatile 241 mplsFrrGeneralConstraintsRowStatus = 1, -- active 242 }; 244 mplsFrrGeneralTunnelARHopEntry 245 { 246 mplsFrrGeneralTunnelARHopSessionAttributeFlags = 5, 247 -- SEStyleDesired | LocalProtectionDesired 249 MPLS Fast-reroute MIB Sep 1, 2011 251 mplsFrrGeneralTunnelARHopRROSubObjectFlags = 2 252 -- LocalProtectionInUse 253 }; 255 4.2. MPLS-FRR-ONE2ONE-STD-MIB 257 This MIB module MUST be implemented if one-to-one backup 258 fastreroute method is implemented. 260 4.2.1 mplsFrrOne2OnePlrTable 262 The mplsFrrOne2OnePlrTable contains information about 263 Points of Local Repair (PLR) that initiated detour LSPs to 264 protect tunnel instances. This table MUST be supported for LSRs 265 implementing the one-to-one backup method. 266 In these cases, the detour LSPs are reflected in the 267 mplsFrrOne2OneDetourTable. 269 4.2.2 mplsFrrOne2OneDetourTable 271 The mplsFrrOne2OneDetourTable shows the detour LSPs in each node 272 (ingress, transit and egress nodes). An entry of this table 273 represents a detour LSP. 275 Each detour is identified by the following indexes: 277 - mplsTunnelIndex [RFC3812]: 278 set to the tunnel-id of an LSP protected by a detour. 280 - mplsTunnelInstance [RFC3812]: consists of two parts 282 1) the higher 16 bits: - protected TE tunnel instance 283 - uniquely identifies a protected 284 LSP within a tunnel. 285 2) the lower 16 bits: - detour instance 286 - uniquely identifies a detour LSP 287 of a protected TE tunnel instance. 288 Multiple detours of the same 289 protected LSP may go through the 290 same node. In this case, the 291 higher 16 bits of the tunnel 292 instance object is used as a 293 detour instance. 295 - ingress node's LSR ID (mplsFrrOne2OnePlrTunnelIngressLSRId): 296 set to the ingress node of an LSP protected by a detour. 298 - egress node's LSR ID (mplsFrrOne2OnePlrTunnelEgressLSRId): 300 MPLS Fast-reroute MIB Sep 1, 2011 302 set to the egress node of an LSP protected by a detour. 304 A detour LSP is also considered as an instance of a protected 305 TE tunnel. Therefore, each detour LSP SHOULD have an entry in 306 the mplsTunnelTable (defined in the MPLS-TE-STD-MIB[RFC3812]). 308 The mplsTunnelTable entries are indexed using mplsTunnelIndex, 309 mplsTunnelInstance, mplsTunnelIngressLSRId, and 310 mplsTunnelEgressLSRId. 311 Entries where the higher 16 bits of mplsTunnelInstance are 312 set to zero represent detour TE tunnel instances. All other 313 values of the higher 16 bits represent protected tunnel 314 instances. 316 This table MUST be supported if one-to-one backup method is 317 used. 319 4.2.3 Example of relationship between mplsFrrOne2OnePlrTable, 320 mplsFrrOne2OneDetourTable and mplsTunnelTable 322 This section contains an example depicting the inter 323 relationship between the mplsFrrOne2OnePlrTable, 324 mplsFrrOne2OneDetourTable and mplsTunnelTable tables. 326 (R1)----(R2)----(R3)----(R4)---(R5) 327 \ \ \ / 328 (R6)---(R7)------(R8) 330 Protected LSP: [R1->R2->R3->R4->R5] 332 R1's Backup: [R1->R6->R7->R8->R3] 334 In the above topology the various tables will be populated 335 as below. 337 In mplsFrrOne2OnePlrTable: 339 { 340 mplsFrrOne2OnePlrTunnelIndex = 1, 341 mplsFrrOne2OnePlrTunnelDetourInstance = 6553601, 342 -- 343 -- (100 << 16 | 1) = 6553601 344 -- 100 is the tunnel instance of the protected tunnel. 345 -- 346 mplsFrrOne2OnePlrTunnelIngressLSRId = 192.0.2.1, --R1 347 mplsFrrOne2OnePlrTunnelEgressLSRId = 192.0.2.5, --R5 348 mplsFrrOne2OnePlrId = 192.0.2.1, -- 349 -- R1 is PLR 350 mplsFrrOne2OnePlrSenderAddrType = ipv4(1), 351 MPLS Fast-reroute MIB Sep 1, 2011 353 mplsFrrOne2OnePlrSenderAddr = "192.0.2.1", -- R1 354 mplsFrrOne2OnePlrAvoidNodeAddrType = ipv4(1), 355 mplsFrrOne2OnePlrAvoidNodeAddr = "192.0.2.2", 356 -- R1-R2(Avoid) 357 } 359 In mplsFrrOne2OneDetourTable: 360 { 361 mplsFrrOne2OnePlrTunnelIndex = 1, 362 mplsFrrOne2OnePlrTunnelDetourInstance = 6553601, 363 -- 364 -- (100 << 16 | 1) == 6553601 365 -- 366 -- 1 is mplsTunnelInstance for the detour lsp 367 -- from mplsTunnelTable. Marked by AAA below. 368 -- Shift 16 to put this into the high order bits 369 -- 370 -- 100 is mplsTunnelInstance for the protected tunnel 371 -- from the mplsTunnelTable. Marked by BBB below. 372 -- Need to OR the index value into low order bits) 374 -- To get all detour lsps of a protected tunnel(of instance 100) 375 -- we could do a snmpwalk of the mplsFrrOne2OneDetourEntry 376 -- where mplsFrrOne2OnePlrTunnelIndex == 1 377 -- mplsFrrOne2OnePlrTunnelDetourInstance == 6553600 379 -- The first value would be: 380 -- mplsFrrOne2OneDetourActive.1.6553601 382 mplsFrrOne2OnePlrTunnelIngressLSRId = 192.0.2.1, --R1 383 mplsFrrOne2OnePlrTunnelEgressLSRId = 192.0.2.3, --R3 384 mplsFrrOne2OneDetourActive = false(2), 385 mplsFrrOne2OneDetourMergedStatus = notMerged(1), 386 mplsFrrOne2OneDetourMergedDetourInst = 0, 387 } 389 In mplsTunnelTable(protected tunnel entry): 391 { 392 mplsTunnelIndex = 1, 393 mplsTunnelInstance = 100,-- Indicating protected tunnel 394 -- AAA 396 mplsTunnelIngressLSRId = 192.0.2.1, 397 mplsTunnelEgressLSRId = 192.0.2.5, 398 mplsTunnelName = "R1-R5", 399 mplsTunnelDescr = "R1-R5", 400 mplsTunnelIsIf = true (1), 401 mplsTunnelXCPointer = 0.0, 402 MPLS Fast-reroute MIB Sep 1, 2011 404 mplsTunnelSignallingProto = none (1), 405 mplsTunnelSetupPrio = 0, 406 mplsTunnelHoldingPrio = 0, 407 mplsTunnelSessionAttributes = 0, 408 mplsTunnelLocalProtectInUse = true(1), 409 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 410 mplsTunnelInstancePriority = 1, 411 mplsTunnelHopTableIndex = 1, 412 mplsTunnelIncludeAnyAffinity = 0, 413 mplsTunnelIncludeAllAffinity = 0, 414 mplsTunnelExcludeAnyAffinity = 0, 415 mplsTunnelPathInUse = 1, 416 mplsTunnelRole = head (1), 417 } 419 In mplsTunnelTable(detour lsp entry): 421 { 422 mplsTunnelIndex = 1, 423 mplsTunnelInstance = 1, 424 -- Indicating detour lsp(higher 16 bits) 425 -- BBB 427 mplsTunnelIngressLSRId = 192.0.2.1, 428 mplsTunnelEgressLSRId = 192.0.2.3, 429 mplsTunnelName = "R1-R3", 430 mplsTunnelDescr = "R1-R3", 431 mplsTunnelIsIf = true (1), 432 mplsTunnelXCPointer = 0.0, 433 mplsTunnelSignallingProto = none (1), 434 mplsTunnelSetupPrio = 0, 435 mplsTunnelHoldingPrio = 0, 436 mplsTunnelSessionAttributes = 0, 437 mplsTunnelLocalProtectInUse = false (0), 438 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.6, 439 mplsTunnelInstancePriority = 1, 440 mplsTunnelHopTableIndex = 1, 441 mplsTunnelIncludeAnyAffinity = 0, 442 mplsTunnelIncludeAllAffinity = 0, 443 mplsTunnelExcludeAnyAffinity = 0, 444 mplsTunnelPathInUse = 1, 445 mplsTunnelRole = head (1), 446 } 448 4.3 MPLS-FRR-FACILITY-STD-MIB 450 This MIB module MUST be implemented if facility backup 451 fastreroute method is implemented. 453 MPLS Fast-reroute MIB Sep 1, 2011 455 4.3.1 mplsFrrFacilityDBTable 457 The mplsFrrFacilityDBTable provides information about the fast 458 reroute database for facility-based fast reroute. 459 An entry is created in this table for each tunnel being 460 protected by a backup tunnel. Backup tunnels are defined 461 to protect the tunnels traversing an interface. 462 The protecting tunnel will exist on the PLR as per [RFC4090]. 463 Protected tunnels are the LSPs that traverse the protected link. 465 4.3.2 Example of relationship between various tables of 466 MPLS-FRR-FACILITY-STD-MIB 468 [R1]---[R2]----[R3]-----[R4]---[R5] 469 \ / 470 [R6]===[R7] 472 Protected LSP 1 : [R1->R2->R3->R4->R5] 473 Protecting Tunnel 999 : [R2->R6->R7->R4] 475 Facility Backup Technique 476 ------------------------- 477 In the above topology, the following tables are populated at R2: 479 mplsFrrFacilityDBEntry 480 { 481 mplsFrrFacilityProtectedIfIndex = 10, 482 mplsFrrFacilityProtectingTunnelIndex = 999, 483 mplsFrrFacilityBackupTunnelIndex = 1, 484 mplsFrrFacilityBackupTunnelInstance = 0, 485 mplsFrrFacilityBackupTunnelIngressLSRId = 486 mplsFrrFacilityBackupTunnelEgressLSRId = 487 mplsFrrFacilityDBNumProtectingTunnelOnIf = 1, 488 mplsFrrFacilityDBNumProtectedLspOnIf = 1, 489 mplsFrrFacilityDBNumProtectedTunnels = 1, 490 mplsFrrFacilityDBProtectingTunnelStatus = 1, -- active 491 mplsFrrFacilityDBProtectingTunnelResvBw = 0, 492 }; 494 In mplsTunnelTable(protecting tunnel entry): 496 { 497 mplsTunnelIndex = 999, -- protecting tunnel index 498 mplsTunnelInstance = 0, -- head 499 MPLS Fast-reroute MIB Sep 1, 2011 501 mplsTunnelIngressLSRId = 192.0.2.2, 502 mplsTunnelEgressLSRId = 192.0.2.4, 503 mplsTunnelName = "R2-R4", 504 mplsTunnelDescr = "R2-R4", 505 mplsTunnelIsIf = true (1), 506 mplsTunnelXCPointer = 0.0, 507 mplsTunnelSignallingProto = none (1), 508 mplsTunnelSetupPrio = 0, 509 mplsTunnelHoldingPrio = 0, 510 mplsTunnelSessionAttributes = 0, 511 mplsTunnelLocalProtectInUse = false(1), 512 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 513 mplsTunnelInstancePriority = 1, 514 mplsTunnelHopTableIndex = 1, 515 mplsTunnelIncludeAnyAffinity = 0, 516 mplsTunnelIncludeAllAffinity = 0, 517 mplsTunnelExcludeAnyAffinity = 0, 518 mplsTunnelPathInUse = 1, 519 mplsTunnelRole = head (1), 520 } 522 In mplsTunnelTable( Protected LSP ): 524 { 525 mplsTunnelIndex = 1, -- protected lsp tunnel index 526 mplsTunnelInstance = 100,-- Specific instance protected 527 mplsTunnelIngressLSRId = 192.0.2.1, 528 mplsTunnelEgressLSRId = 192.0.2.5, 529 mplsTunnelName = "R1-R5", 530 mplsTunnelDescr = "R1-R5", 531 mplsTunnelIsIf = false (2), 532 mplsTunnelXCPointer = 0.0, 533 mplsTunnelSignallingProto = none (1), 534 mplsTunnelSetupPrio = 0, 535 mplsTunnelHoldingPrio = 0, 536 mplsTunnelSessionAttributes = 0, 537 mplsTunnelLocalProtectInUse = true (1), 538 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.6, 539 mplsTunnelInstancePriority = 1, 540 mplsTunnelHopTableIndex = 1, 541 mplsTunnelIncludeAnyAffinity = 0, 542 mplsTunnelIncludeAllAffinity = 0, 543 mplsTunnelExcludeAnyAffinity = 0, 544 mplsTunnelPathInUse = 1, 545 mplsTunnelRole = transit (2), 546 } 548 5. Handling IPv6 Tunnels 549 MPLS Fast-reroute MIB Sep 1, 2011 551 As described in [RFC4990], in order to support IPv6 MPLS 552 tunnels in the mplsTunnelTable [RFC3812] all LSRs in the network 553 MUST have a 32-bit LSR ID that can be used to identify the LSR 554 with the existing mplsTunnelIngressLSRId and mplsTunnelEgressLSRId 555 objects which are 32-bit long. 557 In this MIB, the following objects which refer to ingress/egress 558 LSRs will have then the 32-bit LSR ID to support IPv6 tunnels: 559 - mplsFrrOne2OnePlrTunnelIngressLSRId and 560 - mplsFrrOne2OnePlrTunnelEgressLSRId 561 objects of the mplsFrrOne2OnePlrTable, 562 - mplsFrrOne2OnePlrTunnelIngressLSRId and 563 - mplsFrrOne2OnePlrTunnelEgressLSRId 564 objects of the mplsFrrOne2OneDetourTable 565 - mplsFrrFacilityBackupTunnelIngressLSRId and 566 - mplsFrrFacilityBackupTunnelEgressLSRId 567 objects of the mplsFrrFacilityDBTable 569 6. MIB Module Definitions 571 6.1. MPLS-FRR-GENERAL-STD-MIB Module: 573 -- Start of MPLS-FRR-GENERAL-STD-MIB 575 MPLS-FRR-GENERAL-STD-MIB DEFINITIONS ::= BEGIN 577 IMPORTS 578 MODULE-IDENTITY, OBJECT-TYPE, mib-2, 579 Unsigned32, 580 Counter32 581 FROM SNMPv2-SMI -- [RFC2578] 582 MODULE-COMPLIANCE, OBJECT-GROUP 583 FROM SNMPv2-CONF -- [RFC2580] 584 RowStatus, StorageType 585 FROM SNMPv2-TC -- [RFC2579] 586 InterfaceIndexOrZero, 587 ifGeneralInformationGroup, 588 ifCounterDiscontinuityGroup 590 FROM IF-MIB -- [RFC2863] 591 MplsTunnelIndex, MplsTunnelInstanceIndex, 592 MplsBitRate, 593 MplsTunnelAffinity 594 FROM MPLS-TC-STD-MIB -- [RFC3811] 595 mplsTunnelGroup, mplsTunnelScalarGroup, 596 mplsTunnelARHopListIndex, mplsTunnelARHopIndex 597 FROM MPLS-TE-STD-MIB -- [RFC3812] 598 ; 599 MPLS Fast-reroute MIB Sep 1, 2011 601 mplsFrrGeneralMIB MODULE-IDENTITY 602 LAST-UPDATED 603 "201106141200Z" -- 14 Jun 2011 12:00:00 GMT 604 ORGANIZATION 605 "Multiprotocol Label Switching (MPLS) Working Group" 606 CONTACT-INFO 607 " 608 Riza Cetin 609 Email: riza.cetin@alcatel.be 611 Thomas D. Nadeau 612 Email: tnadeau@lucidvision.com 614 A S Kiran Koushik 615 Email: kkoushik@cisco.com 617 Stefaan De Cnodder 618 Email: Stefaan.de_cnodder@alcatel.be 620 Der-Hwa Gan 621 Email: dhg@juniper.net 622 " 623 DESCRIPTION 624 "Copyright (c) 2011 IETF Trust and the persons identified 625 as the document authors. All rights reserved. This version 626 of this MIB module is part of RFC xxxx; See the RFC itself 627 for full legal notices. 629 -- RFC EDITOR: please replace xxxx with actual number 630 -- and remove this note. 632 This MIB module contains generic object definitions for 633 MPLS Traffic Engineering Fast Reroute as defined in 634 RFC4090." 635 -- Revision history. 636 REVISION 637 "201106141200Z" -- 14 Jun 2011 12:00:00 GMT 638 DESCRIPTION 639 "Initial version. Published as RFC xxxx." 640 -- RFC-editor pls fill in xxxx 641 ::= { mib-2 XXX } -- RFC-editor please fill in 642 -- yyy with value assigned by IANA, 643 -- see section 8.1 for details 645 -- Top level components of this MIB module. 647 mplsFrrGeneralObjects 648 OBJECT IDENTIFIER ::= { mplsFrrGeneralMIB 1 } 649 MPLS Fast-reroute MIB Sep 1, 2011 651 mplsFrrGeneralConformance 652 OBJECT IDENTIFIER ::= { mplsFrrGeneralMIB 2 } 654 -- MPLS Fast Reroute generic scalars. 655 mplsFrrGeneralProtectionMethod OBJECT-TYPE 656 SYNTAX INTEGER { 657 unknown(1), 658 oneToOneBackup(2), 659 facilityBackup(3) 660 } 661 MAX-ACCESS read-write 662 STATUS current 663 DESCRIPTION 664 "Indicates which protection method is to be used for fast 665 reroute on this device. Some devices may require a reboot 666 if this variable is to take affect after being modified." 667 ::= { mplsFrrGeneralObjects 1 } 669 mplsFrrGeneralIngressTunnelInstances OBJECT-TYPE 670 SYNTAX Counter32 671 MAX-ACCESS read-only 672 STATUS current 673 DESCRIPTION 674 "The number of tunnel instances for either detour LSPs or 675 bypass tunnels for which this LSR is the ingress." 676 ::= { mplsFrrGeneralObjects 2 } 678 -- 679 -- General FRR Table Section 680 -- 681 -- These tables apply to both types of FRR 682 -- and should be implemented by all LSRs supporting 683 -- FRR. 684 -- 685 -- MPLS Fast Reroute Constraints table 687 mplsFrrGeneralConstraintsTable OBJECT-TYPE 688 SYNTAX SEQUENCE OF MplsFrrGeneralConstraintsEntry 689 MAX-ACCESS not-accessible 690 STATUS current 691 DESCRIPTION 692 "This table shows detour LSP or bypass tunnel setup 693 constraints." 694 ::= { mplsFrrGeneralObjects 3 } 696 mplsFrrGeneralConstraintsEntry OBJECT-TYPE 697 SYNTAX MplsFrrGeneralConstraintsEntry 698 MAX-ACCESS not-accessible 699 STATUS current 700 MPLS Fast-reroute MIB Sep 1, 2011 702 DESCRIPTION 703 "An entry in this table represents detour LSP or bypass 704 tunnel setup constraints for an interface or link to be 705 protected by detour LSPs or a bypass tunnel. 707 Once the LSP or tunnel instance to be protected is identified 708 in the mplsTunnelTable, the corresponding mplsTunnelIfIndex 709 value of that tunnel can be used to get the ifIndex of 710 the underlying physical interface using the ifStackTable. 711 That ifIndex of the underlying physical interface will 712 be used as mplsFrrGeneralConstraintsIfIndexOrZero in this 713 table to protect the LSPs or tunnel instances determined 714 earlier. 716 It is recommended that ifIndex persistence be 717 enabled across re-initializations. 718 If persistence is not implemented then the value of 719 mplsFrrGeneralConstraintsIfIndexOrZero in this 720 table cannot be guaranteed across restarts and all entries 721 in this table MUST NOT be persistent, or the values of 722 mplsFrrGeneralConstraintsIfIndexOrZero MUST be reconstructed 723 on restart. 725 SNMP Engines must only allow entries in this table 726 to be created for tunnel instances that require fast-reroute 727 as indicated by the presense of the FAST_REROUTE Object 728 in the signaling for the LSP in question. 730 An entry in this table can be created only if a 731 corresponding entry in mplsTunnelTable exists with the 732 same mplsTunnelIndex as mplsFrrGeneralConstraintsTunnelIndex. 734 Entries in this table are deleted when the corresponding 735 entries in mplsTunnelTable are deleted. 737 It is recommended that entries in this table be persisted 738 across reboots. 740 Entries indexed with mplsFrrGeneralConstraintsIfIndexOrZero 741 set to 0 apply to all interfaces on this device for which 742 the FRR feature can operate. 744 If the mplsTunnelInstance object is 745 set to a value of 0, it indicates that the mplsTunnelEntry 746 contains a tunnel ingress. This is typically how 747 configuration of this feature is performed on devices 748 where the actual protection LSP used is left up to the 749 protecting tunnel. However, in cases where static 750 configuration is possible, any valid tunnel 751 instance is possible; however, it is STRONGLY RECOMMENDED 752 that the instance index SHOULD use the following convention 753 to identify backup LSPs: 754 - lower 16 bits : protected tunnel instance 755 MPLS Fast-reroute MIB Sep 1, 2011 757 - higher 16 bits: must be all zeros 758 " 759 REFERENCE "Section 4.1 of RFC4090 and Section 6.1 from RFC 3812." 760 INDEX { mplsFrrGeneralConstraintsIfIndexOrZero, 761 mplsFrrGeneralConstraintsTunnelIndex, 762 mplsFrrGeneralConstraintsTunnelInstance 763 } 764 ::= { mplsFrrGeneralConstraintsTable 1 } 766 MplsFrrGeneralConstraintsEntry ::= SEQUENCE { 767 mplsFrrGeneralConstraintsIfIndexOrZero InterfaceIndexOrZero, 768 mplsFrrGeneralConstraintsTunnelIndex MplsTunnelIndex, 769 mplsFrrGeneralConstraintsTunnelInstance MplsTunnelInstanceIndex, 770 mplsFrrGeneralConstraintsProtectionType INTEGER, 771 mplsFrrGeneralConstraintsSetupPrio Unsigned32, 772 mplsFrrGeneralConstraintsHoldingPrio Unsigned32, 773 mplsFrrGeneralConstraintsInclAnyAffinity MplsTunnelAffinity, 774 mplsFrrGeneralConstraintsInclAllAffinity MplsTunnelAffinity, 775 mplsFrrGeneralConstraintsExclAnyAffinity MplsTunnelAffinity, 776 mplsFrrGeneralConstraintsHopLimit Unsigned32, 777 mplsFrrGeneralConstraintsBandwidth MplsBitRate, 778 mplsFrrGeneralConstraintsStorageType StorageType, 779 mplsFrrGeneralConstraintsRowStatus RowStatus 780 } 782 mplsFrrGeneralConstraintsIfIndexOrZero OBJECT-TYPE 783 SYNTAX InterfaceIndexOrZero 784 MAX-ACCESS not-accessible 785 STATUS current 786 DESCRIPTION 787 "Uniquely identifies an interface which a fast reroute 788 protection tunnel is configured to potentially protect 789 in the event of a fault. Entries with this index set to 790 0 indicates that the protection tunnel configured protects 791 all interfaces on this device (i.e.: node protection)." 792 ::= { mplsFrrGeneralConstraintsEntry 1 } 794 mplsFrrGeneralConstraintsTunnelIndex OBJECT-TYPE 795 SYNTAX MplsTunnelIndex 796 MAX-ACCESS not-accessible 797 STATUS current 798 DESCRIPTION 799 "Uniquely identifies a tunnel in the mplsTunnelTable which 800 is configured to possibly protect the interface(s) specified 801 by mplsFrrGeneralConstraintsIfIndexOrZero in the event of a 802 fault." 803 REFERENCE "mplsTunnelTable from RFC3812." 804 ::= { mplsFrrGeneralConstraintsEntry 2 } 806 mplsFrrGeneralConstraintsTunnelInstance OBJECT-TYPE 807 SYNTAX MplsTunnelInstanceIndex 808 MAX-ACCESS not-accessible 809 STATUS current 810 DESCRIPTION 811 MPLS Fast-reroute MIB Sep 1, 2011 813 "Uniquely identifies an existing instance of this tunnel 814 for which fast reroute is requested. Note that a value of 815 0 indicates that the configuration points at a tunnel 816 head (as specified in RFC3812). This is typically how 817 configuration of this feature is performed on devices 818 where the actual protection LSP used is left up to the 819 protecting tunnel. However, in cases where static 820 configuration is possible, any valid tunnel 821 instance is permissible. In these cases, it is recommended 822 that the instance index follow the following convention 823 as to make identification of backup LSPs easier: 825 - lower 16 bits : protected tunnel instance 826 - higher 16 bits: must be all zeros" 827 ::= { mplsFrrGeneralConstraintsEntry 3 } 829 mplsFrrGeneralConstraintsProtectionType OBJECT-TYPE 830 SYNTAX INTEGER { linkProtection(1), 831 nodeProtection(2) 832 } 833 MAX-ACCESS read-create 834 STATUS current 835 DESCRIPTION 836 "Indicates type of the resource protection: 838 linkProtection(1) indicates that this tunnel is 839 setup to protect a particular link's resources. 840 nodeProtection(2) indicates that this tunnel is 841 setup to protect an entire node from failure. 842 " 843 REFERENCE "Section 3 in RFC4090." 844 DEFVAL { nodeProtection } 845 ::= { mplsFrrGeneralConstraintsEntry 4 } 847 mplsFrrGeneralConstraintsSetupPrio OBJECT-TYPE 848 SYNTAX Unsigned32 (0..7) 849 MAX-ACCESS read-create 850 STATUS current 851 DESCRIPTION 852 "Indicates the setup priority of the detour LSP 853 or bypass tunnel." 854 REFERENCE 855 "Section 4.7 in RFC 3209" 856 DEFVAL { 7 } 857 ::= { mplsFrrGeneralConstraintsEntry 5 } 858 MPLS Fast-reroute MIB Sep 1, 2011 860 mplsFrrGeneralConstraintsHoldingPrio OBJECT-TYPE 861 SYNTAX Unsigned32 (0..7) 862 MAX-ACCESS read-create 863 STATUS current 864 DESCRIPTION 865 "Indicates the holding priority for detour LSP 866 or bypass tunnel." 867 REFERENCE 868 "Section 4.7 RFC 3209" 869 DEFVAL { 0 } 870 ::= { mplsFrrGeneralConstraintsEntry 6 } 872 mplsFrrGeneralConstraintsInclAnyAffinity OBJECT-TYPE 873 SYNTAX MplsTunnelAffinity 874 MAX-ACCESS read-create 875 STATUS current 876 DESCRIPTION 877 "Indicates the include-any link constraint for the 878 detour LSP or bypass tunnel. A link satisfies the 879 include-any constraint if and only if the constraint 880 is zero, or the link and the constraint have a 881 resource class in common." 882 REFERENCE 883 "Section 4.7 in RFC 3209" 884 DEFVAL { 0 } 885 ::= { mplsFrrGeneralConstraintsEntry 7 } 887 mplsFrrGeneralConstraintsInclAllAffinity OBJECT-TYPE 888 SYNTAX MplsTunnelAffinity 889 MAX-ACCESS read-create 890 STATUS current 891 DESCRIPTION 892 "Indicates the include-all link constraint for the 893 detour LSP or bypass tunnel. A link satisfies the 894 include-all constraint if and only if the link contains 895 all of the administrative groups specified in the 896 constraint." 897 REFERENCE 898 "Section 4.7 in RFC 3209" 899 DEFVAL { 0 } 900 ::= { mplsFrrGeneralConstraintsEntry 8 } 902 mplsFrrGeneralConstraintsExclAnyAffinity OBJECT-TYPE 903 SYNTAX MplsTunnelAffinity 904 MAX-ACCESS read-create 905 STATUS current 906 DESCRIPTION 907 "Indicates the exclude-any link constraint for the 908 detour LSP or bypass tunnel. A link satisfies the 909 exclude-any constraint if and only if the link contains 910 none of the administrative groups specified in the 911 MPLS Fast-reroute MIB Sep 1, 2011 913 constraint." 914 REFERENCE 915 "Section 4.7 in RFC 3209" 916 DEFVAL { 0 } 917 ::= { mplsFrrGeneralConstraintsEntry 9 } 919 mplsFrrGeneralConstraintsHopLimit OBJECT-TYPE 920 SYNTAX Unsigned32(0..255) 921 MAX-ACCESS read-create 922 STATUS current 923 DESCRIPTION 924 "The maximum number of hops that the detour LSP or 925 bypass tunnel may traverse." 926 REFERENCE 927 "Section 4.1 in RFC4090." 928 DEFVAL { 32 } 929 ::= { mplsFrrGeneralConstraintsEntry 10 } 931 mplsFrrGeneralConstraintsBandwidth OBJECT-TYPE 932 SYNTAX MplsBitRate 933 UNITS "kilobits per second" 934 MAX-ACCESS read-create 935 STATUS current 936 DESCRIPTION 937 "The maximum bandwidth specifically reserved for a detour 938 LSP or bypass tunnel, in units of thousands of bits 939 per second (Kbps). Note that setting this value to 0 940 indicates best-effort treatment." 941 DEFVAL { 0 } 942 ::= { mplsFrrGeneralConstraintsEntry 11 } 944 mplsFrrGeneralConstraintsStorageType OBJECT-TYPE 945 SYNTAX StorageType 946 MAX-ACCESS read-create 947 STATUS current 948 DESCRIPTION 949 "The storage type for this configuration entry. 950 Conceptual rows having the value 'permanent' 951 need not allow write-access to any columnar 952 objects in the row." 953 DEFVAL { volatile } 954 ::= { mplsFrrGeneralConstraintsEntry 12 } 956 mplsFrrGeneralConstraintsRowStatus OBJECT-TYPE 957 SYNTAX RowStatus 958 MAX-ACCESS read-create 959 STATUS current 960 DESCRIPTION 961 "This object is used to create, modify, and/or delete a row in 962 this table. When a row in this table is in active(1) 963 state, no objects in that row can be modified 964 except mplsFrrGeneralConstraintsRowStatus and 965 mplsFrrGeneralConstraintsStorageType." 966 ::= { mplsFrrGeneralConstraintsEntry 13 } 967 MPLS Fast-reroute MIB Sep 1, 2011 969 -- MPLS Fast Reroute Tunnel Actual Route Hop table 971 mplsFrrGeneralTunnelARHopTable OBJECT-TYPE 972 SYNTAX SEQUENCE OF MplsFrrGeneralTunnelARHopEntry 973 MAX-ACCESS not-accessible 974 STATUS current 975 DESCRIPTION 976 "This table sparsely extends mplsTunnelARHopTable defined 977 in the MPLS-TE-STD-MIB MIB module with fast-reroute objects. 978 These objects specify the status of local protection including 979 availability and active use, on a per-hop basis, of hops 980 traversed by a protected tunnel." 981 ::= { mplsFrrGeneralObjects 4 } 983 mplsFrrGeneralTunnelARHopEntry OBJECT-TYPE 984 SYNTAX MplsFrrGeneralTunnelARHopEntry 985 MAX-ACCESS not-accessible 986 STATUS current 987 DESCRIPTION 988 "This entry contains fast-reroute protection status of a single 989 protected tunnel hop." 990 INDEX { 991 mplsTunnelARHopListIndex, 992 mplsTunnelARHopIndex 993 } 994 ::= { mplsFrrGeneralTunnelARHopTable 1 } 996 MplsFrrGeneralTunnelARHopEntry ::= SEQUENCE { 997 mplsFrrGeneralTunnelARHopSessionAttributeFlags BITS, 998 mplsFrrGeneralTunnelARHopRROSubObjectFlags BITS 999 } 1001 mplsFrrGeneralTunnelARHopSessionAttributeFlags OBJECT-TYPE 1002 SYNTAX BITS { ARHopSessionAttrFlagsUnsupported(0), 1003 LocalProtectionDesired(1), 1004 LabelRecordingDesired(2), 1005 SEStyleDesired(3), 1006 BandwidthProtectionDesired(4), 1007 NodeProtectionDesired(5) 1008 } 1009 MAX-ACCESS read-only 1010 STATUS current 1011 DESCRIPTION 1012 "This object indicates the desired values for 1013 the associated SESSION_ATTRIBUTE flags. Note that since 1014 this object is a BITS type, the bits 1015 may be set to indicate various desired combinations of the 1016 SESSION ATTRIBUTE flags. 1018 If SESSION_ATTRIBUTE flags are not supported, then this 1019 object contains the value of 1020 ARHopSessionAttrFlagsUnsupported(0)." 1021 REFERENCE 1022 MPLS Fast-reroute MIB Sep 1, 2011 1024 "See section 4.3 of RFC4090 for SESSION_ATTRIBUTE 1025 flags." 1026 ::= { mplsFrrGeneralTunnelARHopEntry 1 } 1028 mplsFrrGeneralTunnelARHopRROSubObjectFlags OBJECT-TYPE 1029 SYNTAX BITS { ARHopRROSubObjectFlagsUnsupported(0), 1030 LocalProtectionAvailable(1), 1031 LocalProtectionInUse(2), 1032 BandwidthProtection(3), 1033 NodeProtection(4) 1034 } 1035 MAX-ACCESS read-only 1036 STATUS current 1037 DESCRIPTION 1038 "This object indicates the flags that are 1039 currently in use by the associated RRO sub-object. 1040 Note that since this object is a BITS type, 1041 the bits may be set to indicate various combinations of 1042 the flags. 1044 If RRO sub-object is not supported, then this object 1045 contains the value of 1046 ARHopRROSubObjectFlagsUnsupported(0)." 1047 REFERENCE 1048 "See section 4.4 of RFC4090." 1049 ::= { mplsFrrGeneralTunnelARHopEntry 2 } 1051 -- Notifications 1053 -- Module Conformance Statement 1055 mplsFrrGeneralCompliances 1056 OBJECT IDENTIFIER ::= {mplsFrrGeneralConformance 1 } 1058 mplsFrrGeneralGroups 1059 OBJECT IDENTIFIER ::= {mplsFrrGeneralConformance 2 } 1061 mplsFrrGeneralModuleFullCompliance MODULE-COMPLIANCE 1062 STATUS current 1063 DESCRIPTION 1064 "Compliance statements for SNMP Engines that support 1065 the MPLS-FRR-GENERAL-STD-MIB MIB module." 1067 MODULE IF-MIB -- The Interfaces Group MIB module, RFC 2863. 1068 MANDATORY-GROUPS { 1069 ifGeneralInformationGroup, 1070 ifCounterDiscontinuityGroup 1071 } 1073 MODULE MPLS-TE-STD-MIB -- The MPLS Traffic Engineering 1074 -- MIB module, RFC 3812 1075 MANDATORY-GROUPS { 1076 mplsTunnelGroup, 1077 mplsTunnelScalarGroup 1078 MPLS Fast-reroute MIB Sep 1, 2011 1080 } 1082 MODULE -- this module 1083 MANDATORY-GROUPS { 1084 mplsFrrGeneralScalarGroup, 1085 mplsFrrGeneralTunnelARHopGroup, 1086 mplsFrrGeneralConstraintsGroup 1087 } 1089 OBJECT mplsFrrGeneralConstraintsRowStatus 1090 SYNTAX RowStatus { active(1), notInService(2) } 1091 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1092 createAndGo(4), destroy(6) 1093 } 1094 DESCRIPTION "Support for createAndWait and notReady is 1095 not required." 1097 ::= { mplsFrrGeneralCompliances 1 } 1099 mplsFrrGeneralModuleReadOnlyCompliance MODULE-COMPLIANCE 1100 STATUS current 1101 DESCRIPTION 1102 "Compliance statements for SNMP Engines that support 1103 the MPLS-FRR-GENERAL-STD-MIB MIB module." 1104 MODULE 1106 MANDATORY-GROUPS { 1107 mplsFrrGeneralScalarGroup, 1108 mplsFrrGeneralTunnelARHopGroup, 1109 mplsFrrGeneralConstraintsGroup 1110 } 1112 -- Scalars 1114 OBJECT mplsFrrGeneralProtectionMethod 1115 MIN-ACCESS read-only 1116 DESCRIPTION 1117 "Write access is not required." 1119 -- mplsFrrGeneralConstraintsTable 1121 OBJECT mplsFrrGeneralConstraintsSetupPrio 1122 MIN-ACCESS read-only 1123 DESCRIPTION 1124 "Write access is not required." 1126 OBJECT mplsFrrGeneralConstraintsHoldingPrio 1127 MIN-ACCESS read-only 1128 DESCRIPTION 1129 MPLS Fast-reroute MIB Sep 1, 2011 1131 "Write access is not required." 1133 OBJECT mplsFrrGeneralConstraintsInclAnyAffinity 1134 MIN-ACCESS read-only 1135 DESCRIPTION 1136 "Write access is not required." 1138 OBJECT mplsFrrGeneralConstraintsInclAllAffinity 1139 MIN-ACCESS read-only 1140 DESCRIPTION 1141 "Write access is not required." 1143 OBJECT mplsFrrGeneralConstraintsExclAnyAffinity 1144 MIN-ACCESS read-only 1145 DESCRIPTION 1146 "Write access is not required." 1148 OBJECT mplsFrrGeneralConstraintsBandwidth 1149 MIN-ACCESS read-only 1150 DESCRIPTION 1151 "Write access is not required." 1152 OBJECT mplsFrrGeneralConstraintsProtectionType 1153 MIN-ACCESS read-only 1154 DESCRIPTION 1155 "Write access is not required." 1157 OBJECT mplsFrrGeneralConstraintsHopLimit 1158 MIN-ACCESS read-only 1159 DESCRIPTION 1160 "Write access is not required." 1162 OBJECT mplsFrrGeneralConstraintsStorageType 1163 MIN-ACCESS read-only 1164 DESCRIPTION 1165 "Write access is not required." 1167 OBJECT mplsFrrGeneralConstraintsRowStatus 1168 SYNTAX RowStatus { active(1) } 1169 MIN-ACCESS read-only 1170 DESCRIPTION 1171 "Write access is not required." 1173 ::= { mplsFrrGeneralCompliances 2 } 1175 -- Units of conformance 1177 mplsFrrGeneralScalarGroup OBJECT-GROUP 1178 OBJECTS { 1179 MPLS Fast-reroute MIB Sep 1, 2011 1181 mplsFrrGeneralIngressTunnelInstances, 1182 mplsFrrGeneralProtectionMethod 1183 } 1184 STATUS current 1185 DESCRIPTION 1186 "Objects that are required to display general fast reroute 1187 information." 1188 ::= { mplsFrrGeneralGroups 1 } 1190 mplsFrrGeneralConstraintsGroup OBJECT-GROUP 1191 OBJECTS { 1192 mplsFrrGeneralConstraintsProtectionType, 1193 mplsFrrGeneralConstraintsSetupPrio, 1194 mplsFrrGeneralConstraintsHoldingPrio, 1195 mplsFrrGeneralConstraintsInclAnyAffinity, 1196 mplsFrrGeneralConstraintsInclAllAffinity, 1197 mplsFrrGeneralConstraintsExclAnyAffinity, 1198 mplsFrrGeneralConstraintsHopLimit, 1199 mplsFrrGeneralConstraintsBandwidth, 1200 mplsFrrGeneralConstraintsStorageType, 1201 mplsFrrGeneralConstraintsRowStatus 1202 } 1204 STATUS current 1205 DESCRIPTION 1206 "Objects that are required to configure fast reroute 1207 constraints at the ingress LSR of the tunnel that requires 1208 fast reroute service." 1209 ::= { mplsFrrGeneralGroups 2 } 1211 mplsFrrGeneralTunnelARHopGroup OBJECT-GROUP 1212 OBJECTS { 1213 mplsFrrGeneralTunnelARHopSessionAttributeFlags, 1214 mplsFrrGeneralTunnelARHopRROSubObjectFlags 1215 } 1216 STATUS current 1217 DESCRIPTION 1218 "Objects that are required to present per hop fast-reroute 1219 protection status." 1220 ::= { mplsFrrGeneralGroups 3} 1222 END 1224 -- End of MPLS-FRR-GENERAL-STD-MIB 1226 6.2. MPLS-FRR-ONE2ONE-STD-MIB 1228 -- Start of MPLS-FRR-ONE2ONE-STD-MIB 1229 MPLS Fast-reroute MIB Sep 1, 2011 1231 MPLS-FRR-ONE2ONE-STD-MIB DEFINITIONS ::= BEGIN 1233 IMPORTS 1234 MODULE-IDENTITY, OBJECT-TYPE, mib-2, 1235 Integer32, Gauge32 1236 FROM SNMPv2-SMI -- [RFC2578] 1237 MODULE-COMPLIANCE, OBJECT-GROUP 1238 FROM SNMPv2-CONF -- [RFC2580] 1239 TruthValue 1240 FROM SNMPv2-TC -- [RFC2579] 1241 MplsTunnelIndex, MplsTunnelInstanceIndex, 1242 MplsLsrIdentifier 1243 FROM MPLS-TC-STD-MIB -- [RFC3811] 1244 InetAddressType, InetAddress 1245 FROM INET-ADDRESS-MIB -- [RFC4001] 1246 mplsFrrGeneralScalarGroup, mplsFrrGeneralTunnelARHopGroup, 1247 mplsFrrGeneralConstraintsGroup 1248 FROM MPLS-FRR-GENERAL-STD-MIB 1249 ; 1251 mplsFrrOne2OneMIB MODULE-IDENTITY 1252 LAST-UPDATED 1253 "201106141200Z" -- 14 Jun 2011 12:00:00 GMT 1254 ORGANIZATION 1255 "Multiprotocol Label Switching (MPLS) Working Group" 1256 CONTACT-INFO 1257 " 1258 Riza Cetin 1259 Email: riza.cetin@alcatel.be 1261 Thomas D. Nadeau 1262 Email: tom.nadeau@bt.com 1264 A S Kiran Koushik 1265 Email: kkoushik@cisco.com 1267 Stefaan De Cnodder 1268 Email: Stefaan.de_cnodder@alcatel.be 1270 Der-Hwa Gan 1271 Email: dhg@juniper.net 1272 " 1273 DESCRIPTION 1274 "Copyright (c) 2011 IETF Trust and the persons identified 1275 as the document authors. All rights reserved. This version 1276 of this MIB module is part of RFC xxxx; See the RFC itself 1277 for full legal notices. 1279 -- RFC EDITOR: please replace xxxx with actual number 1280 MPLS Fast-reroute MIB Sep 1, 2011 1282 -- and remove this note. 1284 This MIB module contains object definitions for 1285 MPLS Traffic Engineering one-to-one backup method for 1286 Fast Reroute as defined in RFC4090." 1288 -- Revision history. 1289 REVISION 1290 "201106141200Z" -- 14 Jun 2011 12:00:00 GMT 1291 DESCRIPTION 1292 "Initial version. Published as RFC xxxx." 1293 -- RFC-editor pls fill in xxxx 1294 ::= { mib-2 YYY } -- RFC-editor please fill in 1295 -- yyy with value assigned by IANA, 1296 -- see section 8.2 for details 1298 -- Top level components of this MIB module. 1300 mplsFrrOne2OneObjects OBJECT IDENTIFIER 1301 ::= { mplsFrrOne2OneMIB 1 } 1302 mplsFrrOne2OneConformance OBJECT IDENTIFIER 1303 ::= { mplsFrrOne2OneMIB 2 } 1305 -- Scalar objects defined for 1-to-1 style FRR 1307 mplsFrrIncomingDetourLSPs OBJECT-TYPE 1308 SYNTAX Integer32 (0..2147483647) 1309 MAX-ACCESS read-only 1310 STATUS current 1311 DESCRIPTION 1312 "The number of detour LSPs entering the device." 1313 ::= { mplsFrrOne2OneObjects 1 } 1315 mplsFrrOutgoingDetourLSPs OBJECT-TYPE 1316 SYNTAX Integer32 (0..2147483647) 1317 MAX-ACCESS read-only 1318 STATUS current 1319 DESCRIPTION 1320 "The number of detour LSPs leaving the device." 1321 ::= { mplsFrrOne2OneObjects 2 } 1323 mplsFrrOne2OneDetourOriginating OBJECT-TYPE 1324 SYNTAX Integer32(0..2147483647) 1325 MAX-ACCESS read-only 1326 STATUS current 1327 DESCRIPTION 1328 "The number of detour LSPs originating at this PLR." 1329 ::= { mplsFrrOne2OneObjects 3 } 1330 MPLS Fast-reroute MIB Sep 1, 2011 1332 mplsFrrActiveProtectedLSPs OBJECT-TYPE 1333 SYNTAX Gauge32 1334 MAX-ACCESS read-only 1335 STATUS current 1336 DESCRIPTION 1337 "Indicates the number of LSPs currently protected by 1338 the FRR feature where this device acts as the PLR 1339 for those LSPs." 1340 ::= { mplsFrrOne2OneObjects 4 } 1342 -- 1343 -- One-to-One Specific Tables 1344 -- 1345 -- Tables in this section pertain only to the 1-1 1346 -- style of FRR. 1347 -- 1349 -- MPLS Fast Reroute Point of Local Repair table 1351 mplsFrrOne2OnePlrTable OBJECT-TYPE 1352 SYNTAX SEQUENCE OF MplsFrrOne2OnePlrEntry 1353 MAX-ACCESS not-accessible 1354 STATUS current 1355 DESCRIPTION 1356 "This table shows a list of protected TE tunnels with 1357 the corresponding protecting tunnel, as well as the PLR 1358 where the protecting tunnel that initiated the detour 1359 LSPs traverse this node." 1360 ::= { mplsFrrOne2OneObjects 5 } 1362 mplsFrrOne2OnePlrEntry OBJECT-TYPE 1363 SYNTAX MplsFrrOne2OnePlrEntry 1364 MAX-ACCESS not-accessible 1365 STATUS current 1366 DESCRIPTION 1367 "An entry in this table represents a protected tunnel LSP 1368 together with its detour tunnel instance. An entry in 1369 this table is only created by an SNMP engine as instructed 1370 by an MPLS signaling protocol. 1372 The entries of this table are present in all LSRs on the path 1373 of the detour LSP. 1375 The objects mplsFrrOne2OnePlrSenderAddrType and 1376 mplsFrrOne2OnePlrSenderAddr can be modified after the row 1377 is created. 1379 The objects mplsFrrOne2OnePlrTunnelIndex, 1380 MPLS Fast-reroute MIB Sep 1, 2011 1382 mplsFrrOne2OnePlrTunnelDetourInstance, 1383 mplsFrrOne2OnePlrTunnelIngressLSRId 1384 and mplsFrrOne2OnePlrTunnelEgressLSRId have the same values as 1385 the objects mplsTunnelIndex, mplsTunnelInstance, 1386 mplsTunnelIngressLSRId and mplsTunnelEgressLSRId of the detour 1387 tunnel instance created in the mplsTunnelTable 1388 (MPLS-TE-STD-MIB). 1390 The entries in this table will be deleted when the 1391 corresponding entries in the mplsTunnelTable are deleted." 1392 INDEX { mplsFrrOne2OnePlrTunnelIndex, -- from MPLS-TE-STD-MIB 1393 mplsFrrOne2OnePlrTunnelDetourInstance,-- mplsTunnelTable 1394 mplsFrrOne2OnePlrTunnelIngressLSRId,-- Tunnels must exist 1395 mplsFrrOne2OnePlrTunnelEgressLSRId, -- a priori 1396 mplsFrrOne2OnePlrId } 1397 ::= { mplsFrrOne2OnePlrTable 1 } 1399 MplsFrrOne2OnePlrEntry ::= SEQUENCE { 1400 mplsFrrOne2OnePlrTunnelIndex MplsTunnelIndex, 1401 mplsFrrOne2OnePlrTunnelDetourInstance MplsTunnelInstanceIndex, 1402 mplsFrrOne2OnePlrTunnelIngressLSRId MplsLsrIdentifier, 1403 mplsFrrOne2OnePlrTunnelEgressLSRId MplsLsrIdentifier, 1404 mplsFrrOne2OnePlrId MplsLsrIdentifier, 1405 mplsFrrOne2OnePlrSenderAddrType InetAddressType, 1406 mplsFrrOne2OnePlrSenderAddr InetAddress, 1407 mplsFrrOne2OnePlrAvoidNodeAddrType InetAddressType, 1408 mplsFrrOne2OnePlrAvoidNodeAddr InetAddress 1409 } 1411 mplsFrrOne2OnePlrTunnelIndex OBJECT-TYPE 1412 SYNTAX MplsTunnelIndex 1413 MAX-ACCESS not-accessible 1414 STATUS current 1415 DESCRIPTION 1416 "Uniquely identifies a tunnel between a pair of LSRs 1417 from the mplsTunnelEntry." 1418 ::= { mplsFrrOne2OnePlrEntry 1 } 1420 mplsFrrOne2OnePlrTunnelDetourInstance OBJECT-TYPE 1421 SYNTAX MplsTunnelInstanceIndex 1422 MAX-ACCESS not-accessible 1423 STATUS current 1424 DESCRIPTION 1425 "Uniquely identifies a detour instance of a tunnel from 1426 the mplsTunnelEntry. 1428 - lower 16 bits : protected tunnel instance 1429 - higher 16 bits: detour instance" 1430 ::= { mplsFrrOne2OnePlrEntry 2 } 1431 MPLS Fast-reroute MIB Sep 1, 2011 1433 mplsFrrOne2OnePlrTunnelIngressLSRId OBJECT-TYPE 1434 SYNTAX MplsLsrIdentifier 1435 MAX-ACCESS not-accessible 1436 STATUS current 1437 DESCRIPTION 1438 "The purpose of this object is to uniquely identify a 1439 tunnel within a network. When the MPLS signalling 1440 protocol is rsvp(2) this object SHOULD contain the 1441 same value as the Extended Tunnel Id field in the 1442 SESSION object. When the MPLS signalling protocol 1443 is crldp(3) this object SHOULD contain the same 1444 value as the Ingress LSR Router ID field in the 1445 LSPID TLV object. 1447 This value represents the head-end of the protected 1448 tunnel instance." 1449 REFERENCE 1450 "Sectopn 4.7 in RFC3209" 1451 ::= { mplsFrrOne2OnePlrEntry 3 } 1453 mplsFrrOne2OnePlrTunnelEgressLSRId OBJECT-TYPE 1454 SYNTAX MplsLsrIdentifier 1455 MAX-ACCESS not-accessible 1456 STATUS current 1457 DESCRIPTION 1458 "Specifies the egress LSR ID of the protected tunnel instance." 1459 ::= { mplsFrrOne2OnePlrEntry 4 } 1461 mplsFrrOne2OnePlrId OBJECT-TYPE 1462 SYNTAX MplsLsrIdentifier 1463 MAX-ACCESS not-accessible 1464 STATUS current 1465 DESCRIPTION 1466 "This value represents the PLR that has initiated a detour LSP 1467 to protect a tunnel instance. 1468 This value is signalled via the DETOUR object defined in MPLS 1469 RSVP protocol." 1470 REFERENCE 1471 "Section 4.2 of RFC4090" 1472 ::= { mplsFrrOne2OnePlrEntry 5 } 1474 mplsFrrOne2OnePlrSenderAddrType OBJECT-TYPE 1475 SYNTAX InetAddressType 1476 MAX-ACCESS read-write 1477 STATUS current 1478 DESCRIPTION 1479 "Denotes the address type of this detour instance's sender 1480 address." 1481 MPLS Fast-reroute MIB Sep 1, 2011 1483 DEFVAL { ipv4 } 1484 ::= { mplsFrrOne2OnePlrEntry 6 } 1486 mplsFrrOne2OnePlrSenderAddr OBJECT-TYPE 1487 SYNTAX InetAddress 1488 MAX-ACCESS read-write 1489 STATUS current 1490 DESCRIPTION 1491 "The IP address of the PLR which has initiated the detour LSP. 1492 The type of this address is determined by the value of the 1493 mplsFrrOne2OnePlrSenderAddrType object." 1494 ::= { mplsFrrOne2OnePlrEntry 7 } 1496 mplsFrrOne2OnePlrAvoidNodeAddrType OBJECT-TYPE 1497 SYNTAX InetAddressType 1498 MAX-ACCESS read-only 1499 STATUS current 1500 DESCRIPTION 1501 "Denotes the address type of the node that this PLR tries to 1502 avoid." 1503 DEFVAL { ipv4 } 1504 ::= { mplsFrrOne2OnePlrEntry 8 } 1506 mplsFrrOne2OnePlrAvoidNodeAddr OBJECT-TYPE 1507 SYNTAX InetAddress 1508 MAX-ACCESS read-only 1509 STATUS current 1510 DESCRIPTION 1511 "The IP address of the node that this PLR tries to avoid. 1512 The type of this address is determined by the value of the 1513 mplsFrrOne2OnePlrAvoidNodeAddrType object. 1514 This value is signalled via the DETOUR object defined in MPLS 1515 RSVP protocol." 1516 REFERENCE 1517 "Section 4.2 of RFC4090" 1518 ::= { mplsFrrOne2OnePlrEntry 9 } 1520 -- MPLS One-To-One Fast Reroute Detour table. 1522 mplsFrrOne2OneDetourTable OBJECT-TYPE 1523 SYNTAX SEQUENCE OF MplsFrrOne2OneDetourEntry 1524 MAX-ACCESS not-accessible 1525 STATUS current 1526 DESCRIPTION 1527 "This table shows detour LSPs." 1528 ::= { mplsFrrOne2OneObjects 6 } 1530 mplsFrrOne2OneDetourEntry OBJECT-TYPE 1531 SYNTAX MplsFrrOne2OneDetourEntry 1532 MPLS Fast-reroute MIB Sep 1, 2011 1534 MAX-ACCESS not-accessible 1535 STATUS current 1536 DESCRIPTION 1537 "An entry in this table represents a detour. An entry in this 1538 table is only created by an SNMP engine as instructed by an 1539 MPLS signaling protocol. " 1540 INDEX { 1541 mplsFrrOne2OnePlrTunnelIndex, -- from MPLS-TE-STD-MIB 1542 mplsFrrOne2OnePlrTunnelDetourInstance, -- mplsTunnelTable 1543 mplsFrrOne2OnePlrTunnelIngressLSRId,-- Tunnels must exist 1544 mplsFrrOne2OnePlrTunnelEgressLSRId -- a priori 1545 } 1546 ::= { mplsFrrOne2OneDetourTable 1 } 1548 MplsFrrOne2OneDetourEntry ::= SEQUENCE { 1549 mplsFrrOne2OneDetourActive TruthValue, 1550 mplsFrrOne2OneDetourMergedStatus INTEGER, 1551 mplsFrrOne2OneDetourMergedDetourInst MplsTunnelInstanceIndex 1552 } 1554 mplsFrrOne2OneDetourActive OBJECT-TYPE 1555 SYNTAX TruthValue 1556 MAX-ACCESS read-only 1557 STATUS current 1558 DESCRIPTION 1559 "Indicates whether or not the main LSP has switched over to 1560 this detour LSP. 1561 If the value of this object is 'true', then it means that 1562 the main LSP has switched over to this detour LSP. Otherwise 1563 it contains a value of 'false'. 1564 This is only relevant for detours originated by this node." 1565 ::= { mplsFrrOne2OneDetourEntry 1 } 1567 mplsFrrOne2OneDetourMergedStatus OBJECT-TYPE 1568 SYNTAX INTEGER { notMerged(1), 1569 mergedWithProtectedTunnel(2), 1570 mergedWithDetour(3) 1571 } 1572 MAX-ACCESS read-only 1573 STATUS current 1574 DESCRIPTION 1575 "This value represents whether or not this detour is merged. 1576 This value is set to notMerged(1) if this detour is not 1577 merged. 1579 This value is set to mergedWithProtectedTunnel(2) if 1580 this detour is merged with the protected tunnel. This value 1581 is mergedWithDetour(3) if this detour is merged 1582 with another detour protecting the same tunnel." 1583 MPLS Fast-reroute MIB Sep 1, 2011 1585 ::= { mplsFrrOne2OneDetourEntry 2 } 1587 mplsFrrOne2OneDetourMergedDetourInst OBJECT-TYPE 1588 SYNTAX MplsTunnelInstanceIndex 1589 MAX-ACCESS read-only 1590 STATUS current 1591 DESCRIPTION 1592 "This value represents the mplsTunnelInstance of the detour 1593 with which this detour is merged. This object is only valid 1594 when mplsFrrOne2OneDetourMergedStatus is set to 1595 mergedWithDetour(3). 1597 - lower 16 bits : protected tunnel instance 1598 - higher 16 bits: detour instance" 1599 ::= { mplsFrrOne2OneDetourEntry 3 } 1601 -- Module Conformance Statement 1603 mplsFrrOne2OneCompliances 1604 OBJECT IDENTIFIER ::= {mplsFrrOne2OneConformance 1 } 1606 mplsFrrOne2OneGroups 1607 OBJECT IDENTIFIER ::= {mplsFrrOne2OneConformance 2 } 1609 mplsFrrOne2OneModuleFullCompliance MODULE-COMPLIANCE 1610 STATUS current 1611 DESCRIPTION 1612 "Compliance statements for SNMP Engines that support the 1613 MPLS-FRR-ONE2ONE-STD-MIB MIB module." 1615 MODULE MPLS-FRR-GENERAL-STD-MIB -- MPLS FRR Generic MIB 1616 MANDATORY-GROUPS { 1617 mplsFrrGeneralScalarGroup, 1618 mplsFrrGeneralTunnelARHopGroup, 1619 mplsFrrGeneralConstraintsGroup 1620 } 1622 MODULE -- this module 1623 MANDATORY-GROUPS { 1624 mplsFrrOne2OneScalarsGroup, 1625 mplsFrrOne2OnePLRDetourGroup, 1626 mplsFrrOne2OnePlrGroup 1627 } 1629 ::= { mplsFrrOne2OneCompliances 1 } 1631 mplsFrrOne2OneModuleReadOnlyCompliance MODULE-COMPLIANCE 1632 STATUS current 1633 DESCRIPTION 1634 MPLS Fast-reroute MIB Sep 1, 2011 1636 "Compliance statements for SNMP Engines that support the 1637 MPLS-FRR-ONE2ONE-STD-MIB MIB module." 1638 MODULE 1639 MANDATORY-GROUPS { 1640 mplsFrrOne2OneScalarsGroup, 1641 mplsFrrOne2OnePLRDetourGroup, 1642 mplsFrrOne2OnePlrGroup 1643 } 1644 -- mplsFrrOne2OnePlrTable 1646 OBJECT mplsFrrOne2OnePlrSenderAddrType 1647 MIN-ACCESS read-only 1648 DESCRIPTION 1649 "Write access is not required." 1651 OBJECT mplsFrrOne2OnePlrSenderAddr 1652 MIN-ACCESS read-only 1653 DESCRIPTION 1654 "Write access is not required." 1656 ::= { mplsFrrOne2OneCompliances 2 } 1658 -- Units of conformance 1660 mplsFrrOne2OneScalarsGroup OBJECT-GROUP 1661 OBJECTS { 1662 mplsFrrIncomingDetourLSPs, 1663 mplsFrrOutgoingDetourLSPs, 1664 mplsFrrOne2OneDetourOriginating, 1665 mplsFrrActiveProtectedLSPs 1666 } 1667 STATUS current 1668 DESCRIPTION 1669 "Objects that are required for general One-2-One PLR 1670 information." 1671 ::= { mplsFrrOne2OneGroups 1 } 1673 mplsFrrOne2OnePLRDetourGroup OBJECT-GROUP 1674 OBJECTS { 1675 mplsFrrOne2OneDetourActive, 1676 mplsFrrOne2OneDetourMergedStatus, 1677 mplsFrrOne2OneDetourMergedDetourInst 1678 } 1679 STATUS current 1680 DESCRIPTION 1681 "Objects that are required to present the detour LSP 1682 information at the detour ingress, transit and egress LSRs." 1683 ::= { mplsFrrOne2OneGroups 2 } 1684 MPLS Fast-reroute MIB Sep 1, 2011 1686 mplsFrrOne2OnePlrGroup OBJECT-GROUP 1687 OBJECTS { 1688 mplsFrrOne2OnePlrSenderAddrType, 1689 mplsFrrOne2OnePlrSenderAddr, 1690 mplsFrrOne2OnePlrAvoidNodeAddrType, 1691 mplsFrrOne2OnePlrAvoidNodeAddr 1692 } 1693 STATUS current 1694 DESCRIPTION 1695 "Objects that are required to represent the FRR 1696 One-2-One PLR information." 1697 ::= { mplsFrrOne2OneGroups 3 } 1699 END 1701 -- End of MPLS-FRR-ONE2ONE-STD-MIB 1703 6.3. MPLS-FRR-FACILITY-STD-MIB 1705 -- Start of MPLS-FRR-FACILITY-STD-MIB 1707 MPLS-FRR-FACILITY-STD-MIB DEFINITIONS ::= BEGIN 1709 IMPORTS 1710 MODULE-IDENTITY, OBJECT-TYPE, mib-2, 1711 Integer32, 1712 NOTIFICATION-TYPE, Gauge32 1713 FROM SNMPv2-SMI -- [RFC2578] 1714 MODULE-COMPLIANCE, OBJECT-GROUP, 1715 NOTIFICATION-GROUP 1716 FROM SNMPv2-CONF -- [RFC2580] 1717 TruthValue 1718 FROM SNMPv2-TC -- [RFC2579] 1719 InterfaceIndex 1720 FROM IF-MIB -- [RFC2863] 1721 MplsTunnelIndex, MplsTunnelInstanceIndex, 1722 MplsLsrIdentifier, MplsBitRate 1723 FROM MPLS-TC-STD-MIB -- [RFC3811] 1724 mplsFrrGeneralScalarGroup, mplsFrrGeneralTunnelARHopGroup, 1725 mplsFrrGeneralConstraintsGroup 1726 FROM MPLS-FRR-GENERAL-STD-MIB 1727 ; 1729 mplsFrrFacilityMIB MODULE-IDENTITY 1730 LAST-UPDATED 1731 "201106141200Z" -- 14 Jun 2011 12:00:00 GMT 1732 ORGANIZATION 1733 MPLS Fast-reroute MIB Sep 1, 2011 1735 "Multiprotocol Label Switching (MPLS) Working Group" 1736 CONTACT-INFO 1737 " 1738 Riza Cetin 1739 Email: riza.cetin@alcatel.be 1741 Thomas D. Nadeau 1742 Email: tom.nadeau@bt.com 1744 A S Kiran Koushik 1745 Email: kkoushik@cisco.com 1747 Stefaan De Cnodder 1748 Email: Stefaan.de_cnodder@alcatel.be 1750 Der-Hwa Gan 1751 Email: dhg@juniper.net 1752 " 1753 DESCRIPTION 1754 "Copyright (C) 2011 The IETF Trust. This version of this MIB 1755 module is part of RFC xxxx; See the RFC itself for full 1756 legal notices. 1758 -- RFC EDITOR: please replace xxxx with actual number 1759 -- and remove this note. 1761 This MIB module contains object definitions for 1762 MPLS Traffic Engineering facility backup method for 1763 Fast Reroute as defined in RFC4090." 1765 -- Revision history. 1766 REVISION 1767 "201106141200Z" -- 14 Jun 2011 12:00:00 GMT 1768 DESCRIPTION 1769 "Initial version. Published as RFC xxxx." 1770 -- RFC-editor pls fill in xxxx 1771 ::= { mib-2 ZZZ } -- RFC-editor please fill in 1772 -- yyy with value assigned by IANA, 1773 -- see section 8.3 for details 1775 -- Top level components of this MIB module. 1776 mplsFrrFacilityNotifications OBJECT IDENTIFIER 1777 ::= { mplsFrrFacilityMIB 0 } 1779 mplsFrrFacilityObjects OBJECT IDENTIFIER 1780 ::= { mplsFrrFacilityMIB 1 } 1782 mplsFrrFacilityConformance OBJECT IDENTIFIER 1783 ::= { mplsFrrFacilityMIB 2 } 1785 MPLS Fast-reroute MIB Sep 1, 2011 1787 -- Scalar objects defined for Facility Backup style FRR 1789 mplsFrrConfiguredInterfaces OBJECT-TYPE 1790 SYNTAX Integer32(0..2147483647) 1791 MAX-ACCESS read-only 1792 STATUS current 1793 DESCRIPTION 1794 "Indicates the number of MPLS interfaces configured for 1795 protection." 1796 DEFVAL { 0 } 1797 ::= { mplsFrrFacilityObjects 1 } 1799 mplsFrrActiveInterfaces OBJECT-TYPE 1800 SYNTAX Gauge32 1801 MAX-ACCESS read-only 1802 STATUS current 1803 DESCRIPTION 1804 "Indicates the number of interfaces currently being 1805 protected. This value MUST be less than or equal 1806 to mplsFrrConfiguredInterfaces." 1807 DEFVAL { 0 } 1808 ::= { mplsFrrFacilityObjects 2 } 1810 mplsFrrConfiguredBypassTunnels OBJECT-TYPE 1811 SYNTAX Gauge32 1812 MAX-ACCESS read-only 1813 STATUS current 1814 DESCRIPTION 1815 "Indicates the number of bypass tunnels configured to 1816 protect TE tunnels on this LSR." 1817 DEFVAL { 0 } 1818 ::= { mplsFrrFacilityObjects 3 } 1820 mplsFrrActiveBypassTunnels OBJECT-TYPE 1821 SYNTAX Gauge32 1823 MAX-ACCESS read-only 1824 STATUS current 1825 DESCRIPTION 1826 "Indicates the number of bypass tunnels indicated in 1827 mplsFrrConfiguredBypassTunnels whose operStatus 1828 is up(1) indicating that they are currently protecting 1829 TE tunnels on this LSR." 1830 DEFVAL { 0 } 1831 ::= { mplsFrrFacilityObjects 4 } 1833 mplsFrrFacilityNotificationsEnabled OBJECT-TYPE 1834 MPLS Fast-reroute MIB Sep 1, 2011 1836 SYNTAX TruthValue 1837 MAX-ACCESS read-write 1838 STATUS current 1839 DESCRIPTION 1840 "Enables or disables FRR notifications defined in this 1841 MIB module. Notifications are disabled by default. 1843 This object is needed to control the notifications 1844 emitted by this implementation." 1845 DEFVAL { false } 1846 ::= { mplsFrrFacilityObjects 5 } 1848 mplsFrrFacilityNotificationsMaxRate OBJECT-TYPE 1849 SYNTAX Gauge32 1850 UNITS "Notifications per Second" 1851 MAX-ACCESS read-write 1852 STATUS current 1853 DESCRIPTION 1854 "This variable indicates the maximum number of 1855 notifications issued per second. If events occur 1856 more rapidly, the implementation may simply fail to 1857 emit these notifications during that period, or may 1858 queue them until an appropriate time. In case the 1859 implementation chooses to drop the events during 1860 throttling instead of queuing them to be sent at a later 1861 time, it is assumed that there will be no indication 1862 that events are being thrown away. 1864 A value of 0 means no throttling is applied and 1865 events may be generated at the rate at which they occur." 1866 DEFVAL { 0 } 1867 ::= { mplsFrrFacilityObjects 6 } 1869 -- 1870 -- Facility-based FRR-specific Tables 1871 -- 1872 -- Tables in this section pertain only to the facility- 1873 -- based style of FRR. 1874 -- 1876 mplsFrrFacilityDBTable OBJECT-TYPE 1877 SYNTAX SEQUENCE OF MplsFrrFacilityDBEntry 1878 MAX-ACCESS not-accessible 1879 STATUS current 1880 DESCRIPTION 1881 "The mplsFrrFacilityDBTable provides information about the 1882 fast reroute database. Each entry belongs to a protected 1883 interface, protecting backup tunnel and protected tunnel. 1884 MPLS interfaces defined on this node are protected by 1885 backup tunnels and are indicated by the index 1886 mplsFrrFacilityProtectedIfIndex. If the interface index is 1887 MPLS Fast-reroute MIB Sep 1, 2011 1889 set to 0, this indicates that the remaining indexes apply 1890 to all configured protected interfaces. 1892 Note that all objects in this table are read-only and 1893 if new objects are added to this table, they should also 1894 be read-only. 1896 It is recommended that ifIndex persistence be enabled 1897 across re-initializations. 1898 If persistence is not implemented then the value of 1899 mplsFrrFacilityProtectedIfIndex in this 1900 table cannot be guaranteed across restarts and all entries 1901 in this table MUST NOT be persistent, or the values of 1902 mplsFrrFacilityProtectedIfIndex MUST be reconstructed 1903 on restart. 1905 It is recommended that entries in this table be persisted 1906 across reboots. 1908 The protecting tunnel is indicated by the 1909 index mplsFrrFacilityProtectingTunnelIndex and 1910 represents a valid mplsTunnelEntry. Note that the tunnel 1911 instance index of the protecting tunnel may be set to 0 1912 which indicates the tunnel head interface for the 1913 protecting tunnel, as per RFC3812, but it may also be 1914 defined using the following semantics: 1916 - lower 16 bits : protected tunnel instance 1917 - higher 16 bits: must be all zeros 1918 " 1919 ::= { mplsFrrFacilityObjects 7 } 1921 mplsFrrFacilityDBEntry OBJECT-TYPE 1922 SYNTAX MplsFrrFacilityDBEntry 1923 MAX-ACCESS not-accessible 1924 STATUS current 1925 DESCRIPTION 1926 "An entry in the mplsFrrFacilityDBTable represents a single 1927 protected LSP, protected by a backup tunnel on a 1928 specific protected interface, or if the interface 1929 index is set to 0, on all interfaces. Note that for 1930 brevity, managers should consult the mplsTunnelTable 1931 present in the MPLS-TE-STD-MIB MIB module for 1932 additional information about the protecting and protected 1933 tunnels, and the ifEntry in the IF-MIB MIB module 1934 for the protected interface." 1935 INDEX { 1936 mplsFrrFacilityProtectedIfIndex, -- protected ifIndex 1937 mplsFrrFacilityProtectingTunnelIndex,-- protecting TE tun 1938 mplsFrrFacilityBackupTunnelIndex, -- protected TE tun 1939 mplsFrrFacilityBackupTunnelInstance, -- LSP 1940 mplsFrrFacilityBackupTunnelIngressLSRId, 1941 mplsFrrFacilityBackupTunnelEgressLSRId } 1942 ::= { mplsFrrFacilityDBTable 1 } 1943 MPLS Fast-reroute MIB Sep 1, 2011 1945 MplsFrrFacilityDBEntry ::= SEQUENCE { 1946 mplsFrrFacilityProtectedIfIndex InterfaceIndex, 1947 mplsFrrFacilityProtectingTunnelIndex MplsTunnelIndex, 1948 mplsFrrFacilityBackupTunnelIndex MplsTunnelIndex, 1949 mplsFrrFacilityBackupTunnelInstance MplsTunnelInstanceIndex, 1950 mplsFrrFacilityBackupTunnelIngressLSRId MplsLsrIdentifier, 1951 mplsFrrFacilityBackupTunnelEgressLSRId MplsLsrIdentifier, 1952 mplsFrrFacilityDBNumProtectingTunnelOnIf Gauge32, 1953 mplsFrrFacilityDBNumProtectedLspOnIf Gauge32, 1954 mplsFrrFacilityDBNumProtectedTunnels Gauge32, 1955 mplsFrrFacilityDBProtectingTunnelStatus INTEGER, 1956 mplsFrrFacilityDBProtectingTunnelResvBw MplsBitRate 1957 } 1959 mplsFrrFacilityProtectedIfIndex OBJECT-TYPE 1960 SYNTAX InterfaceIndex 1961 MAX-ACCESS not-accessible 1962 STATUS current 1963 DESCRIPTION 1964 "Uniquely identifies the interface configured for FRR 1965 protection. If this object is set to 0, this indicates 1966 that the remaining indexing combinations for this row 1967 apply to all interfaces on this device for which 1968 the FRR feature can operate." 1969 ::= { mplsFrrFacilityDBEntry 1 } 1971 mplsFrrFacilityProtectingTunnelIndex OBJECT-TYPE 1972 SYNTAX MplsTunnelIndex 1973 MAX-ACCESS not-accessible 1974 STATUS current 1975 DESCRIPTION 1976 "Uniquely identifies the mplsTunnelEntry primary index for 1977 the tunnel head interface designated to protect the 1978 interface as specified in the mplsFrrFacilityProtectedIfIndex 1979 (and all of the tunnels using this interface). Note 1980 that the corresponding mplsTunnelInstance MUST BE 1981 0 as per the indexing convention stipulated." 1982 REFERENCE 1983 "Section 6.1 of RFC3812" 1984 ::= { mplsFrrFacilityDBEntry 2 } 1986 mplsFrrFacilityBackupTunnelIndex OBJECT-TYPE 1987 SYNTAX MplsTunnelIndex 1988 MAX-ACCESS not-accessible 1989 STATUS current 1990 DESCRIPTION 1991 "Uniquely identifies the mplsTunnelEntry primary index for 1992 the TE tunnel LSP being protected on the 1993 interface as specified by mplsFrrFacilityProtectedIfIndex." 1994 ::= { mplsFrrFacilityDBEntry 3 } 1995 MPLS Fast-reroute MIB Sep 1, 2011 1997 mplsFrrFacilityBackupTunnelInstance OBJECT-TYPE 1998 SYNTAX MplsTunnelInstanceIndex 1999 MAX-ACCESS not-accessible 2000 STATUS current 2001 DESCRIPTION 2002 "Uniquely identifies the mplsTunnelEntry secondary index 2003 for the TE tunnel LSP being protected on the 2004 interface as specified by mplsFrrFacilityProtectedIfIndex." 2005 ::= { mplsFrrFacilityDBEntry 4 } 2007 mplsFrrFacilityBackupTunnelIngressLSRId OBJECT-TYPE 2008 SYNTAX MplsLsrIdentifier 2009 MAX-ACCESS not-accessible 2010 STATUS current 2011 DESCRIPTION 2012 "Uniquely identifies the mplsTunnelEntry third index 2013 for the TE tunnel LSP being protected on the 2014 interface as specified by mplsFrrFacilityProtectedIfIndex." 2015 REFERENCE 2016 "Section 6.1 of RFC3812" 2017 ::= { mplsFrrFacilityDBEntry 5 } 2019 mplsFrrFacilityBackupTunnelEgressLSRId OBJECT-TYPE 2020 SYNTAX MplsLsrIdentifier 2021 MAX-ACCESS not-accessible 2022 STATUS current 2023 DESCRIPTION 2024 "Uniquely identifies the mplsTunnelEntry fourth index 2025 for the TE tunnel LSP being protected on the 2026 interface as specified by mplsFrrFacilityProtectedIfIndex." 2027 ::= { mplsFrrFacilityDBEntry 6 } 2029 mplsFrrFacilityDBNumProtectingTunnelOnIf OBJECT-TYPE 2030 SYNTAX Gauge32 2031 MAX-ACCESS read-only 2032 STATUS current 2033 DESCRIPTION 2034 "The number of backup tunnels protecting the 2035 interface specified by mplsFrrFacilityProtectedIfIndex." 2036 ::= { mplsFrrFacilityDBEntry 7 } 2038 mplsFrrFacilityDBNumProtectedLspOnIf OBJECT-TYPE 2039 SYNTAX Gauge32 2040 MAX-ACCESS read-only 2041 STATUS current 2042 DESCRIPTION 2043 "The number of LSPs currently being protected on 2044 the interface specified by 2045 mplsFrrFacilityProtectedIfIndex." 2046 ::= { mplsFrrFacilityDBEntry 8 } 2047 MPLS Fast-reroute MIB Sep 1, 2011 2049 mplsFrrFacilityDBNumProtectedTunnels OBJECT-TYPE 2050 SYNTAX Gauge32 2051 MAX-ACCESS read-only 2052 STATUS current 2053 DESCRIPTION 2054 "The number of tunnels protected on the interface 2055 specified by mplsFrrFacilityProtectedIfIndex." 2056 ::= { mplsFrrFacilityDBEntry 9 } 2058 mplsFrrFacilityDBProtectingTunnelStatus OBJECT-TYPE 2059 SYNTAX INTEGER { 2060 active(1), 2061 ready(2), 2062 partial(3) 2063 } 2064 MAX-ACCESS read-only 2065 STATUS current 2066 DESCRIPTION 2067 "Specifies the state of the protecting tunnel as 2068 specified by mplsFrrFacilityProtectingTunnelIndex. 2070 active This tunnel's label has been placed in the 2071 LFIB and is ready to be applied to incoming 2072 packets. 2074 ready - This tunnel's label entry has been created but is 2075 not yet in the LFIB. 2076 partial - This tunnel's label entry has not been fully 2077 created." 2078 ::= { mplsFrrFacilityDBEntry 10 } 2080 mplsFrrFacilityDBProtectingTunnelResvBw OBJECT-TYPE 2081 SYNTAX MplsBitRate 2082 UNITS "kilobits per second" 2083 MAX-ACCESS read-only 2084 STATUS current 2085 DESCRIPTION 2086 "Specifies the amount of bandwidth in units 2087 of '1,000 bits per second', actually reserved by 2088 the protecting tunnel for facility backup purposes. 2089 This value is repeated here from the 2090 MPLS-TE-STD-MIB MIB module because the tunnel entry will 2091 reveal the bandwidth reserved by the signaling protocol, 2092 which is typically 0 for backup tunnels so as to not 2093 over-book bandwidth. However, internal reservations are 2094 typically made on the PLR, thus this value should be 2095 revealed here as it is often different from 2096 mplsTunnelResourceMeanRate found in the MPLS-TE-STD-MIB 2097 MIB module." 2098 MPLS Fast-reroute MIB Sep 1, 2011 2100 ::= { mplsFrrFacilityDBEntry 11 } 2102 -- Notifications 2103 mplsFrrFacilityInitialBackupTunnelInvoked NOTIFICATION-TYPE 2104 OBJECTS { mplsFrrFacilityDBNumProtectingTunnelOnIf, 2105 mplsFrrFacilityDBNumProtectedLspOnIf, 2106 mplsFrrFacilityDBNumProtectedTunnels, 2107 mplsFrrFacilityDBProtectingTunnelStatus, 2108 mplsFrrFacilityDBProtectingTunnelResvBw 2109 } 2110 STATUS current 2111 DESCRIPTION 2112 "This notification is generated when a tunnel running over an 2113 interface as specified in the mplsFrrConstraintsTable is 2114 initially protected by the backup tunnel also specified in the 2115 mplsFrrConstraintsTable. In some implementations there may be 2116 a difference between when the control plane triggers 2117 this notification and when the hardware is programmed to 2118 utilize the protection path. Due to the urgency of this 2119 operation, it is acceptable for the control plane to 2120 either issue this notification before or after it programs 2121 the hardware. In cases where it is the latter approach, 2122 the notification MUST be sent immediately after the 2123 data plane has been altered. 2125 This notification should not be generated 2126 for each subsequent tunnel that is backed up by the FRR feature 2127 on this LSR, as this may result in potential scaling issues 2128 with regard to LSR performance and network load. Note also 2129 that notifications MUST be generated in accordance with the 2130 mplsFrrNotificationsMaxRate." 2132 ::= { mplsFrrFacilityNotifications 1 } 2134 mplsFrrFacilityFinalTunnelRestored NOTIFICATION-TYPE 2135 OBJECTS { mplsFrrFacilityDBNumProtectingTunnelOnIf, 2136 mplsFrrFacilityDBNumProtectedLspOnIf, 2137 mplsFrrFacilityDBNumProtectedTunnels, 2138 mplsFrrFacilityDBProtectingTunnelStatus, 2139 mplsFrrFacilityDBProtectingTunnelResvBw 2140 } 2141 STATUS current 2142 DESCRIPTION 2143 "This notification is generated when the final tunnel that is 2144 being protected by a backup tunnel as specified in the 2145 mplsFrrConstraintsTable is restored to normal operation. This 2146 notification should not be generated for each restored tunnel, 2147 as this may result in potential scaling issues with regard to 2148 LSR performance and network load. Note also that 2149 MPLS Fast-reroute MIB Sep 1, 2011 2151 notifications MUST be generated in accordance with the 2152 mplsFrrNotificationsMaxRate." 2153 ::= { mplsFrrFacilityNotifications 2 } 2155 -- Module Conformance Statement 2157 mplsFrrFacilityCompliances 2158 OBJECT IDENTIFIER ::= {mplsFrrFacilityConformance 1 } 2160 mplsFrrFacilityGroups 2161 OBJECT IDENTIFIER ::= {mplsFrrFacilityConformance 2 } 2163 mplsFrrFacilityModuleFullCompliance MODULE-COMPLIANCE 2164 STATUS current 2165 DESCRIPTION 2166 "Compliance statements for SNMP Engines that support the 2167 MPLS-FRR-FACILITY-STD-MIB MIB module." 2169 MODULE MPLS-FRR-GENERAL-STD-MIB -- MPLS FRR Generic MIB 2170 MANDATORY-GROUPS { 2171 mplsFrrGeneralScalarGroup, 2172 mplsFrrGeneralTunnelARHopGroup, 2173 mplsFrrGeneralConstraintsGroup 2174 } 2176 MODULE -- this module 2177 MANDATORY-GROUPS { 2178 mplsFrrFacilityScalarGroup, 2179 mplsFrrFacilityDBGroup, 2180 mplsFrrFacilityNotificationsGroup 2181 } 2183 ::= { mplsFrrFacilityCompliances 1 } 2185 mplsFrrFacilityModuleReadOnlyCompliance MODULE-COMPLIANCE 2186 STATUS current 2187 DESCRIPTION 2188 "Compliance statements for SNMP Engines that support 2189 MPLS-FRR-FACILITY-STD-MIB MIB module." 2191 MODULE MPLS-FRR-GENERAL-STD-MIB -- MPLS FRR Generic MIB 2192 MANDATORY-GROUPS { 2193 mplsFrrGeneralScalarGroup, 2194 mplsFrrGeneralTunnelARHopGroup, 2195 mplsFrrGeneralConstraintsGroup 2196 } 2198 MODULE -- this module 2199 MPLS Fast-reroute MIB Sep 1, 2011 2201 MANDATORY-GROUPS { 2202 mplsFrrFacilityScalarGroup, 2203 mplsFrrFacilityDBGroup, 2204 mplsFrrFacilityNotificationsGroup 2205 } 2207 ::= { mplsFrrFacilityCompliances 2 } 2209 -- Units of conformance 2211 mplsFrrFacilityScalarGroup OBJECT-GROUP 2212 OBJECTS { mplsFrrConfiguredInterfaces, 2213 mplsFrrActiveInterfaces, 2214 mplsFrrConfiguredBypassTunnels, 2215 mplsFrrActiveBypassTunnels, 2216 mplsFrrFacilityNotificationsEnabled, 2217 mplsFrrFacilityNotificationsMaxRate 2218 } 2219 STATUS current 2220 DESCRIPTION 2221 "Objects that are required to represent the FRR 2222 Facility Route Database information." 2223 ::= { mplsFrrFacilityGroups 1 } 2225 mplsFrrFacilityDBGroup OBJECT-GROUP 2226 OBJECTS { mplsFrrFacilityDBNumProtectingTunnelOnIf, 2227 mplsFrrFacilityDBNumProtectedLspOnIf, 2228 mplsFrrFacilityDBNumProtectedTunnels, 2229 mplsFrrFacilityDBProtectingTunnelStatus, 2230 mplsFrrFacilityDBProtectingTunnelResvBw 2231 } 2232 STATUS current 2233 DESCRIPTION 2234 "Objects that are required to represent the FRR 2235 Facility Route Database information." 2236 ::= { mplsFrrFacilityGroups 2 } 2238 mplsFrrFacilityNotificationsGroup NOTIFICATION-GROUP 2239 NOTIFICATIONS { mplsFrrFacilityInitialBackupTunnelInvoked, 2240 mplsFrrFacilityFinalTunnelRestored 2241 } 2242 STATUS current 2243 DESCRIPTION 2244 "Objects that are required to represent FRR notifications." 2245 ::= { mplsFrrFacilityGroups 3 } 2247 END 2248 MPLS Fast-reroute MIB Sep 1, 2011 2250 -- End of MPLS-FRR-FACILITY-STD-MIB 2252 7. Security Considerations 2254 It is clear that these MIB modules are potentially useful for 2255 monitoring of MPLS LSRs supporting fast reroute. This 2256 MIB module can also be used for configuration of certain objects, 2257 and anything that can be configured can be incorrectly configured, 2258 with potentially disastrous results. 2260 There are a number of management objects defined in these MIB 2261 modules with a MAX-ACCESS clause of read-write and/or read-create. 2262 Such objects may be considered sensitive or vulnerable in some 2263 network environments. The support for SET operations in a 2264 non-secure environment without proper protection can have a 2265 negative effect on network operations. These are the tables and 2266 objects and their sensitivity/vulnerability: 2268 o the mplsFrrGeneralConstraintsTable( 2269 mplsFrrGeneralConstraintsProtectionType, 2270 mplsFrrGeneralConstraintsSetupPrio, etc.) and some objects in 2271 the mplsFrrScalarGroup( mplsFrrGeneralProtectionMethod, 2272 mplsFrrFacilityNotificationsEnabled, etc.) contain objects 2273 which may be used to provision MPLS fast reroute features. 2274 Unauthorized access to these objects could result in disruption 2275 of traffic on the network. 2277 Some of the readable objects in these MIB modules (i.e. objects with 2278 MAX-ACCESS other than not-accessible) may be considered sensitive or 2279 vulnerable in some network environments. It is thus important to 2280 control even GET and/or NOTIFY access to these objects and possibly 2281 to even encrypt the values of these objects when sending them over 2282 the network via SNMP. These are the tables and objects and their 2283 sensitivity/vulnerability: 2285 o the mplsFrrOne2OnePlrTable (mplsFrrOne2OnePlrSenderAddr, 2286 mplsFrrOne2OnePlrAvoidNodeAddr, etc.), 2287 mplsFrrOne2OneDetourTable (mplsFrrOne2OneDetourActive, 2288 mplsFrrOne2OneDetourMergedDetourInst, etc.), and 2289 mplsFrrGeneralTunnelARHopTable( 2290 mplsFrrGeneralTunnelARHopSessionAttributeFlags, 2291 mplsFrrGeneralTunnelARHopRROSubObjectFlags, etc.) 2292 tables and some objects contained in the mplsFrrScalarGroup( 2293 mplsFrrGeneralProtectionMethod, mplsFrrActiveInterfaces, etc.) 2294 collectively show the MPLS fast reroute interfaces, tunnels, 2295 and other associated fast reroute feature configurations 2296 as well as their linkages to other MPLS-related 2297 configuration and/or performance statistics. 2298 Administrators not wishing to reveal this information should 2299 MPLS Fast-reroute MIB Sep 1, 2011 2301 consider these objects sensitive/vulnerable and take 2302 precautions so they are not revealed. 2304 SNMP versions prior to SNMPv3 did not include adequate security. 2305 Even if the network itself is secure (for example by using IPSec), 2306 even then, there is no control as to who on the secure network is 2307 allowed to access and GET/SET (read/change/create/delete) the objects 2308 in these MIB modules. 2310 It is RECOMMENDED that implementers consider the security features as 2311 provided by the SNMPv3 framework (see [RFC3410], section 8), 2312 including full support for the SNMPv3 cryptographic mechanisms (for 2313 authentication and privacy). 2315 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2316 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2317 enable cryptographic security. It is then a customer/operator 2318 responsibility to ensure that the SNMP entity giving access to an 2319 instance of these MIB modules, is properly configured to give access 2320 to the objects only to those principals (users) that have legitimate 2321 rights to indeed GET or SET (change/create/delete) them. 2323 8. IANA Considerations 2325 The MIB modules in this document uses the following IANA-assigned 2326 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 2328 8.1. IANA Considerations for MPLS-FRR-GENERAL-STD-MIB 2330 The IANA is requested to assign { mib-2 XXX } to the 2331 MPLS-FRR-GENERAL-STD-MIB MIB module specified in this document. 2333 8.2. IANA Considerations for MPLS-FRR-ONE2ONE-STD-MIB 2335 The IANA is requested to assign { mib-2 YYY } to the 2336 MPLS-FRR-ONE2ONE-STD-MIB MIB module specified in this document. 2338 8.3. IANA Considerations for MPLS-FRR-FACILITY-STD-MIB 2340 The IANA is requested to assign { mib-2 ZZZ } to the 2341 MPLS-FRR-FACILITY-STD-MIB MIB module specified in this document. 2343 Editor's Note (to be removed prior to publication): the IANA is 2344 requested to assign a value for "XXX", "YYY" and "ZZZ" under 2345 the mib-2 subtree and to record the assignments in the SMI Numbers 2346 registry. When the assignments have been made, the RFC Editor is 2347 asked to replace "XXX", "YYY" and "ZZZ" (here and in the MIB 2348 modules) with the assigned values and to remove this note. 2350 MPLS Fast-reroute MIB Sep 1, 2011 2352 9. Acknowledgments 2354 This document is a product of the MPLS Working Group. 2355 We would like to thank Alia Atlas, Yeong Tai, Walter Vanhimbeeck, 2356 Mike Piecuch, Adrien Grise, Kiran Koushik, Joan Cucchiara and 2357 Adrian Farrel for the helpful and colorful discussions about, 2358 editorial comments on and contributions to this document. 2360 10. References 2362 10.1 Normative References 2364 [RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate 2365 Requirement Levels", RFC 2119, BCP 14, March 1997. 2367 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2368 J., Rose, M., and S. Waldbusser, "Structure of 2369 Management Information Version 2 (SMIv2)", STD 58, RFC 2370 2578, April 1999. 2372 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2373 J., Rose, M., and S. Waldbusser, "Textual Conventions 2374 for SMIv2", STD 58, RFC 2579, April 1999. 2376 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2377 J., Rose, M., and S. Waldbusser, "Conformance 2378 Statements for SMIv2", STD 58, RFC 2580, April 1999. 2380 [RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces Group 2381 MIB", RFC 2863, June 2000. 2383 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 2384 Label Switching Architecture", RFC 3031, January 2001. 2386 [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual 2387 Conventions and for Multiprotocol Label Switching (MPLS) 2388 Management", RFC 3811, June 2004. 2390 [RFC3812] Srinivasan, C., Viswanathan, A. and T. Nadeau, 2391 "Multiprotocol Label Switching (MPLS) Traffic 2392 Engineering Management Information 2393 Base", RFC 3812, June 2004 2395 [RFC3813] Srinivasan, C., Viswanathan, A. and Nadeau, T., 2396 "Multiprotocol Label Switching (MPLS) Label Switching 2397 Router (LSR) Management Information Base", 2398 RFC 3813, June 2004 2400 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2402 MPLS Fast-reroute MIB Sep 1, 2011 2404 Schoenwaelder, "Textual Conventions for Internet Network 2405 Addresses", RFC 4001, Feb 2005. 2407 [RFC4090] Pan, P., Swallow, G., and A. Atlas, "Fast Reroute 2408 Extensions to RSVP-TE for LSP Tunnels", RFC 4090, 2409 May 2005. 2411 10.2 Informative References 2413 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 2414 "Introduction and Applicability Statements for 2415 Internet-Standard Management Framework", RFC 3410, 2416 December 2002. 2418 [RFC4990] Shiomoto K., Papneja R., Rabbat R.," Use of Addresses 2419 in Generalized Multi-Protocol Label Switching (GMPLS) 2420 Networks", RFC 4990, Sep 2007. 2422 11. Editors' Addresses 2424 Riza Cetin 2425 Alcatel 2426 Francis Wellesplein 1 2427 B-2018 Antwerp, Belgium 2428 Email: riza.cetin@alcatel.be 2430 Thomas D. Nadeau 2431 CA Technologies 2432 Email: thomas.nadeau@ca.com 2434 A S Kiran Koushik 2435 Cisco Systems, Inc. 2436 12515 Research Blvd, Bldg 4 2437 Austin, TX 78664 2438 Phone: +1-512-378-1482 2439 Email: kkoushik@cisco.com 2441 12. Contributors' Addresses 2443 Stefaan De Cnodder 2444 Alcatel 2445 Francis Wellesplein 1 2446 B-2018 Antwerp, Belgium 2447 Email: stefaan.de_cnodder@alcatel.be 2449 Der-Hwa Gan 2450 Juniper Networks, Inc. 2451 1194 N. Mathilda Avenue 2452 Sunnyvale, CA 94089 2453 Email: derhwagan@yahoo.com 2454 MPLS Fast-reroute MIB Sep 1, 2011 2456 Intellectual Property Statement 2458 The IETF Trust takes no position regarding the validity or scope of 2459 any Intellectual Property Rights or other rights that might be 2460 claimed to pertain to the implementation or use of the technology 2461 described in any IETF Document or the extent to which any license 2462 under such rights might or might not be available; nor does it 2463 represent that it has made any independent effort to identify any 2464 such rights. 2466 Copies of Intellectual Property disclosures made to the IETF 2467 Secretariat and any assurances of licenses to be made available, or 2468 the result of an attempt made to obtain a general license or 2469 permission for the use of such proprietary rights by implementers or 2470 users of this specification can be obtained from the IETF on-line IPR 2471 repository at http://www.ietf.org/ipr 2473 The IETF invites any interested party to bring to its attention any 2474 copyrights, patents or patent applications, or other proprietary 2475 rights that may cover technology that may be required to implement 2476 any standard or specification contained in an IETF Document. Please 2477 address the information to the IETF at ietf-ipr@ietf.org. 2479 The definitive version of an IETF Document is that published by, or 2480 under the auspices of, the IETF. Versions of IETF Documents that are 2481 published by third parties, including those that are translated into 2482 other languages, should not be considered to be definitive versions 2483 of IETF Documents. The definitive version of these Legal Provisions 2484 is that published by, or under the auspices of, the IETF. Versions of 2485 these Legal Provisions that are published by third parties, including 2486 those that are translated into other languages, should not be 2487 considered to be definitive versions of these Legal Provisions. 2489 For the avoidance of doubt, each Contributor to the IETF Standards 2490 Process licenses each Contribution that he or she makes as part of 2491 the IETF Standards Process to the IETF Trust pursuant to the 2492 provisions of RFC 5378. No language to the contrary, or terms, 2493 conditions or rights that differ from or are inconsistent with the 2494 rights and licenses granted under RFC 5378, shall have any effect and 2495 shall be null and void, whether published or posted by such 2496 Contributor, or included with or in such Contribution. 2498 Acknowledgement 2500 This document is a product of the MPLS Working Group. 2501 Funding for the RFC Editor function is provided by the IETF 2502 Administrative Support Activity (IASA). 2504 MPLS Fast-reroute MIB Sep 1, 2011