idnits 2.17.1 draft-ietf-rtgwg-ipfrr-ip-mib-05.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 : ---------------------------------------------------------------------------- ** There are 38 instances of too long lines in the document, the longest one being 46 characters in excess of 72. ** The abstract seems to contain references ([RFC5714]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. 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 lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (December 22, 2014) is 3411 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: 2 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Routing Area Working Group A. Atlas 3 Internet-Draft Juniper Networks 4 Intended status: Standards Track K. Koushik 5 Expires: June 25, 2015 Cisco Systems 6 J. Flick 7 Hewlett-Packard 8 S. Litkowski 9 Orange 10 December 22, 2014 12 IP MIB for IP Fast-Reroute 13 draft-ietf-rtgwg-ipfrr-ip-mib-05 15 Abstract 17 This draft defines a portion of the Management Information Base (MIB) 18 for use with network management protocols in the Internet community. 19 In particular, it describes managed objects relevant for IP routes 20 using IP Fast-Reroute [RFC5714] 22 Requirements Language 24 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 25 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 26 document are to be interpreted as described in [RFC2119]. 28 Status of This Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at http://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on June 25, 2015. 45 Copyright Notice 47 Copyright (c) 2014 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 63 1.1. The SNMP Management Framework . . . . . . . . . . . . . . 3 64 2. Brief description of MIB Objects . . . . . . . . . . . . . . 3 65 2.1. ipFrrProtectStats Group . . . . . . . . . . . . . . . . . 3 66 2.2. ipFrrInstanceTable . . . . . . . . . . . . . . . . . . . 4 67 2.3. ipFrrIfTable . . . . . . . . . . . . . . . . . . . . . . 4 68 2.4. ipFrrProtectStatsTable . . . . . . . . . . . . . . . . . 4 69 2.5. ipFrrAltTable . . . . . . . . . . . . . . . . . . . . . . 4 70 2.6. ipFrrNoAltTable . . . . . . . . . . . . . . . . . . . . . 4 71 3. IP Fast-Reroute MIB Module Definitions . . . . . . . . . . . 4 72 4. Security Considerations . . . . . . . . . . . . . . . . . . . 24 73 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25 74 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 75 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 76 7.1. Normative References . . . . . . . . . . . . . . . . . . 26 77 7.2. Informative References . . . . . . . . . . . . . . . . . 26 78 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27 80 1. Introduction 82 This document defines a portion of the Management Information Base 83 (MIB) for use with network management protocols in the Internet 84 community. In particular, it defines the managed objects used for IP 85 routes and interfaces in relation to IP Fast-Reroute. This document 86 uses terminology from [RFC5714] and [RFC5286]. 88 Current work is underway to define mechanisms for determining 89 alternate paths for traffic to use when the original path becomes 90 unavailable due to a local failure. The alternate next-hops can be 91 computed in the context of any IGP. 93 There are certain configuration attributes for IP Fast-Reroute that 94 should be configured to enable IP Fast Reroute in the context of the 95 IGP. These configuration attributes of IP Fast-Reroute are not 96 covered by this MIB module. Examples include whether IP Fast-Reroute 97 is enabled on a network region (i.e. an OSPF area or IS-IS level) and 98 the desired local hold-down timer [RFC5286], whose proper value is 99 dependent upon the size of the network region. 101 It is possible for traffic other than IP to depend upon and use the 102 alternate next-hops computed by IP Fast-Reroute. An example would be 103 MPLS traffic whose path is configured via LDP [RFC5036]. The 104 additional details (for example, outgoing MPLS label) pertaining to 105 alternate next-hops that are required by such traffic are not covered 106 by this MIB module. 108 An IP route may be reachable via multiple primary next-hops which 109 provide equal-cost paths. Where IP Fast-Reroute is enabled, each 110 primary next-hop will be protected by one or more alternate next- 111 hops. Such an alternate next-hop may itself be a primary next-hop. 113 1.1. The SNMP Management Framework 115 For a detailed overview of the documents that describe the current 116 Internet-Standard Management Framework, please refer to section 7 of 117 [RFC3410]. 119 Managed objects are accessed via a virtual information store, termed 120 the Management Information Base or MIB. MIB objects are generally 121 accessed through the Simple Network Management Protocol (SNMP). 122 Objects in the MIB are defined using the mechanisms defined in the 123 Structure of Management Information (SMI). This memo specifies a MIB 124 module that is compliant to the SMIv2, which is described in STD 58, 125 [RFC2578], STD 58, [RFC2579] and STD 58, [RFC2580]. 127 2. Brief description of MIB Objects 129 2.1. ipFrrProtectStats Group 131 The global objects in this group provide summary information related 132 to protection for all IP routes. The information available includes 133 counts of all routes, of all protected routes, of all unprotected 134 routes, of all routes which are protected against a link failure, and 135 of all routes which are protected against a node failure. 137 2.2. ipFrrInstanceTable 139 The ipFrrInstanceTable provides information about configuration of IP 140 FRR instantiations on a node. A single node may have multiple 141 instances of IP FRR using different algorithms or protocols. 143 2.3. ipFrrIfTable 145 The ipFrrIfTable provides information about configuration of 146 interfaces for IPFRR. 148 2.4. ipFrrProtectStatsTable 150 The ipFrrProtectStatsTable complements the ipFrrProtectStats group by 151 providing statistics per IP FRR instance. 153 2.5. ipFrrAltTable 155 The ipFrrAltTable extends the inetCidrRouteTable [RFC4292] to provide 156 information about each alternate next-hop associated with a primary 157 next-hop used by a route. Statically configured alternate next-hops 158 associated with primary next-hops can be created. 160 2.6. ipFrrNoAltTable 162 The ipFrrNoAltTable extends the inetCidrRouteTable [RFC4292] to 163 provide information about the routes which do not have an alternate 164 next-hop associated with any of the route's primary next-hop. The 165 entry provides an explanation for the lack of protection. 167 3. IP Fast-Reroute MIB Module Definitions 169 IPFRR-MIB DEFINITIONS ::= BEGIN 171 IMPORTS 172 MODULE-IDENTITY, 173 OBJECT-TYPE, 174 Gauge32, 175 Integer32 FROM SNMPv2-SMI -- [RFC2578] 177 RowStatus 178 FROM SNMPv2-TC -- [RFC2579] 180 MODULE-COMPLIANCE, 181 OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] 183 InetAddressType, 184 InetAddress FROM INET-ADDRESS-MIB -- [RFC4001] 185 ifIndex, InterfaceIndex FROM IF-MIB -- [RFC2863] 187 ip FROM IP-MIB -- [RFC4293] 189 inetCidrRouteDestType, 190 inetCidrRouteDest, 191 inetCidrRoutePfxLen, 192 inetCidrRoutePolicy, 193 inetCidrRouteNextHopType, 194 inetCidrRouteNextHop FROM IP-FORWARD-MIB 195 -- [RFC4292] 197 IANAipRouteProtocol FROM IANA-RTPROTO-MIB 199 ; 201 ipFrrMIB MODULE-IDENTITY 202 LAST-UPDATED "201405261200Z" -- May 26, 2014 203 ORGANIZATION "draft-ietf-ipfrr-ip-mib-03.txt" 204 CONTACT-INFO 205 " 206 A S Kiran Koushik 207 Cisco Systems Inc. 208 EMail: kkoushik@cisco.com 210 John W Flick 211 Hewlett Packard Company 212 EMail: john.flick@hp.com 214 Alia Atlas 215 Juniper Networks 216 Email: akatlas@juniper.net 218 Stephane Litkowski 219 Orange Business Service 220 Email: stephane.litkowski@orange.com 222 " 223 DESCRIPTION 224 "IP MIB module for management of IP Fast-Reroute. 226 Copyright (C) The Internet Society (date). 227 This version of this MIB module is part of 228 draft-ietf-rtgwg-ipfrr-ip-mib-03.txt" 229 REVISION "201406131200Z" -- Jun 13, 2014 230 DESCRIPTION 231 "Add ipFrrTunnelType in ipFrrAltEntry 232 Modify ipFrrAltType" 233 REVISION "201405261200Z" -- May 26, 2014 234 DESCRIPTION 235 "Add ipFrrInstanceTable. 236 Add ipFrrIfTable. 237 ipFrrProtectStatsTable complements ipFrrProtectStats to have statistics per instance. 238 Add ipFrrAltMetric2, ipFrrAltMetric3, ipFrrAltBest, ipFrrAltNonBestReason to ipFrrAltEntry. 239 Add integer values to ipFrrAltType. 240 Add integer values to ipFrrAltProtectionAvailable. 241 Changed attachement of ipFrrAltStatus in ipFrrAltEntry. 242 Added IPv6 objects in ipFrrProtectStats." 243 REVISION "201203131200Z" -- Mar 13, 2012 244 DESCRIPTION 245 "Editorial changes. Added new type to ipFrrAltType." 246 REVISION "200502181200Z" -- February 18, 2005 247 DESCRIPTION 248 "Add Set operations on ipFrrAltTable" 249 REVISION "200502131200Z" -- February 13, 2005 250 DESCRIPTION 251 "Initial version." 252 ::= { ip ZZZ } -- To be assigned by IANA 254 -- Top level components of this MIB module. 256 ipFrrMIBObjects OBJECT IDENTIFIER ::= { ipFrrMIB 1 } 258 ipFrrProtectStats OBJECT IDENTIFIER ::= { ipFrrMIBObjects 1 } 260 -- the IP FRR MIB-Group 262 -- A collection of objects providing summarized information 263 -- about the protection availability and type of alternate paths 264 -- provided by IP Fast-Reroute mechanisms. 266 ipFrrTotalRoutes OBJECT-TYPE 267 SYNTAX Gauge32 268 MAX-ACCESS read-only 269 STATUS current 270 DESCRIPTION 271 "The number of IPv4 valid routes known by this entity." 272 ::= { ipFrrProtectStats 1 } 274 ipFrrUnprotectedRoutes OBJECT-TYPE 275 SYNTAX Gauge32 276 MAX-ACCESS read-only 277 STATUS current 278 DESCRIPTION 279 "The number of IPv4 valid routes known by this entity 280 which do not have an alternate next-hop associated 281 with any primary next-hop." 282 ::= { ipFrrProtectStats 2 } 284 ipFrrProtectedRoutes OBJECT-TYPE 285 SYNTAX Gauge32 286 MAX-ACCESS read-only 287 STATUS current 288 DESCRIPTION 289 "The number of IPv4 routes known by this entity 290 which have at least one alternate next-hop." 291 ::= { ipFrrProtectStats 3 } 293 ipFrrLinkProtectedRoutes OBJECT-TYPE 294 SYNTAX Gauge32 295 MAX-ACCESS read-only 296 STATUS current 297 DESCRIPTION 298 "The number of IPv4 routes known by this entity 299 for which all alternate next-hops provide link 300 protection for their associated primary next-hops." 301 ::= { ipFrrProtectStats 4 } 303 ipFrrNodeProtectedRoutes OBJECT-TYPE 304 SYNTAX Gauge32 305 MAX-ACCESS read-only 306 STATUS current 307 DESCRIPTION 308 "The number of IPv4 routes known by this entity 309 for which all alternate next-hops provide node 310 protection for their associated primary next-hops." 311 ::= { ipFrrProtectStats 5 } 313 ipv6FrrTotalRoutes OBJECT-TYPE 314 SYNTAX Gauge32 315 MAX-ACCESS read-only 316 STATUS current 317 DESCRIPTION 318 "The number of IPv6 valid routes known by this entity." 319 ::= { ipFrrProtectStats 6 } 321 ipv6FrrUnprotectedRoutes OBJECT-TYPE 322 SYNTAX Gauge32 323 MAX-ACCESS read-only 324 STATUS current 325 DESCRIPTION 326 "The number of IPv6 valid routes known by this entity 327 which do not have an alternate next-hop associated 328 with any primary next-hop." 329 ::= { ipFrrProtectStats 7 } 331 ipv6FrrProtectedRoutes OBJECT-TYPE 332 SYNTAX Gauge32 333 MAX-ACCESS read-only 334 STATUS current 335 DESCRIPTION 336 "The number of IPv6 routes known by this entity 337 which have at least one alternate next-hop." 338 ::= { ipFrrProtectStats 8 } 340 ipv6FrrLinkProtectedRoutes OBJECT-TYPE 341 SYNTAX Gauge32 342 MAX-ACCESS read-only 343 STATUS current 344 DESCRIPTION 345 "The number of IPv6 routes known by this entity 346 for which all alternate next-hops provide link 347 protection for their associated primary next-hops." 348 ::= { ipFrrProtectStats 9 } 350 ipv6FrrNodeProtectedRoutes OBJECT-TYPE 351 SYNTAX Gauge32 352 MAX-ACCESS read-only 353 STATUS current 354 DESCRIPTION 355 "The number of IPv6 routes known by this entity 356 for which all alternate next-hops provide node 357 protection for their associated primary next-hops." 358 ::= { ipFrrProtectStats 10 } 360 -- the IP FRR instance MIB-group 361 -- 362 -- The ipFrrInstanceTable provides detail on current IPFRR 363 -- instances activated on the node 365 ipFrrInstanceTable OBJECT-TYPE 366 SYNTAX SEQUENCE OF IpFrrInstanceEntry 367 MAX-ACCESS not-accessible 368 STATUS current 369 DESCRIPTION 370 "This entity's IP Fast Reroute Instance table." 371 ::= { ipFrrMIBObjects 4 } 373 ipFrrInstanceEntry OBJECT-TYPE 374 SYNTAX IpFrrInstanceEntry 375 MAX-ACCESS not-accessible 376 STATUS current 377 DESCRIPTION 378 "An entry containing information on a particular 379 IP FRR instance on the node." 381 INDEX { ipFrrInstanceId 382 } 383 ::= { ipFrrInstanceTable 1 } 385 IpFrrInstanceEntry ::= SEQUENCE { 386 ipFrrInstanceId INTEGER, 387 ipFrrInstanceProtocol IANAipRouteProtocol, 388 ipFrrInstanceAlgorithm Integer32, 389 ipFrrInstancePerPrefixComputation INTEGER, 390 ipFrrInstanceRowStatus RowStatus 391 } 393 ipFrrInstanceId OBJECT-TYPE 394 SYNTAX Integer32 (1..255) 395 MAX-ACCESS not-accessible 396 STATUS current 397 DESCRIPTION 398 "This object specifies an identificator a of particular IPFRR instance. " 399 ::= { ipFrrInstanceEntry 1 } 401 ipFrrInstanceProtocol OBJECT-TYPE 402 SYNTAX IANAipRouteProtocol 403 MAX-ACCESS read-create 404 STATUS current 405 DESCRIPTION 406 "This object specifies the protocol used by the IPFRR instance." 407 ::= { ipFrrInstanceEntry 2 } 409 ipFrrInstanceAlgorithm OBJECT-TYPE 410 SYNTAX INTEGER { 411 loopFree(1), 412 loopFreeRemote(2), 413 loopFreeTI(3), 414 mrt(4) 415 } 416 MAX-ACCESS read-create 417 STATUS current 418 DESCRIPTION 419 "This object specifies the algorithm used by the IPFRR instance." 420 ::= { ipFrrInstanceEntry 3 } 422 ipFrrInstancePerPrefixComputation OBJECT-TYPE 423 SYNTAX INTEGER { 424 false(0), 425 true(1) 426 } 427 MAX-ACCESS read-create 428 STATUS current 429 DESCRIPTION 430 "This object specifies if per prefix computation is used." 431 ::= { ipFrrInstanceEntry 4 } 433 ipFrrInstanceRowStatus OBJECT-TYPE 434 SYNTAX RowStatus 435 MAX-ACCESS read-create 436 STATUS current 437 DESCRIPTION 438 "." 439 ::= { ipFrrInstanceEntry 5 } 441 -- the IP FRR Interface MIB-Group 442 -- 443 -- ipFrrIfTable provides information on configuration 444 -- of interfaces for IPFRR 446 ipFrrIfTable OBJECT-TYPE 447 SYNTAX SEQUENCE OF IpFrrIfEntry 448 MAX-ACCESS not-accessible 449 STATUS current 450 DESCRIPTION 451 "This entity's IP Fast Reroute Alternates Interface configuration table." 452 ::= { ipFrrMIBObjects 5 } 454 ipFrrIfEntry OBJECT-TYPE 455 SYNTAX IpFrrIfEntry 456 MAX-ACCESS not-accessible 457 STATUS current 458 DESCRIPTION 459 "An entry containing information on a particular instance of an IPFRR interface." 461 INDEX { ipFrrInstanceId, 462 ifIndex 463 } 464 ::= { ipFrrIfTable 1 } 466 IpFrrIfEntry ::= SEQUENCE { 467 ipFrrIfProtectionType BITS, 468 ipFrrIfCandidate INTEGER, 469 ipFrrIfRowStatus RowStatus 470 } 472 ipFrrIfProtectionType OBJECT-TYPE 473 SYNTAX BITS { 474 nodeProtect(0), 475 linkProtect(1), 476 nodelinkProtect(2) 477 } 478 MAX-ACCESS read-create 479 STATUS current 480 DESCRIPTION 481 "This object specifies the scope of protection requested for the protection of the destinations. 482 nodeProtect means node protection only compared to nodelinkProtect which means node protection 483 if available and link protection if not available. " 484 ::= { ipFrrIfEntry 1 } 486 ipFrrIfCandidate OBJECT-TYPE 487 SYNTAX INTEGER { 488 false (0), 489 true (1) 491 } 492 MAX-ACCESS read-create 493 STATUS current 494 DESCRIPTION 495 "This object specifies the scope of protection requested for the protection of the destinations. 496 nodeProtect means node protection only compared to nodelinkProtect which means node protection 497 if available and link protection if not available. " 498 ::= { ipFrrIfEntry 2 } 500 ipFrrIfRowStatus OBJECT-TYPE 501 SYNTAX RowStatus 502 MAX-ACCESS read-create 503 STATUS current 504 DESCRIPTION 505 "." 506 ::= { ipFrrIfEntry 3 } 508 -- the IP FRR Stats MIB-Group 509 -- 510 -- ipFrrProtectStatsTable provides provides 511 -- protection availability and type of alternate paths 512 -- provided by IP Fast-Reroute mechanisms per IPFRR instance. 514 ipFrrProtectStatsTable OBJECT-TYPE 515 SYNTAX SEQUENCE OF IpFrrProtectStatsEntry 516 MAX-ACCESS not-accessible 517 STATUS current 518 DESCRIPTION 519 "This entity's IP Fast Reroute Alternates statistics table." 520 ::= { ipFrrMIBObjects 6 } 522 ipFrrProtectStatsEntry OBJECT-TYPE 523 SYNTAX IpFrrProtectStatsEntry 524 MAX-ACCESS not-accessible 525 STATUS current 526 DESCRIPTION 527 "An entry containing information on a particular instance of IPFRR. 529 ." 531 INDEX { ipFrrInstanceId 532 } 533 ::= { ipFrrProtectStatsTable 1 } 535 IpFrrProtectStatsEntry ::= SEQUENCE { 536 ipFrrStatsTotalRoutes Gauge32, 537 ipFrrStatsUnprotectedRoutes Gauge32, 538 ipFrrStatsProtectedRoutes Gauge32, 539 ipFrrStatsLinkProtectedRoutes Gauge32, 540 ipFrrStatsNodeProtectedRoutes Gauge32, 541 ipv6FrrStatsTotalRoutes Gauge32, 542 ipv6FrrStatsUnprotectedRoutes Gauge32, 543 ipv6FrrStatsProtectedRoutes Gauge32, 544 ipv6FrrStatsLinkProtectedRoutes Gauge32, 545 ipv6FrrStatsNodeProtectedRoutes Gauge32 546 } 548 ipFrrStatsTotalRoutes OBJECT-TYPE 549 SYNTAX Gauge32 550 MAX-ACCESS read-only 551 STATUS current 552 DESCRIPTION 553 "The number of valid routes known by this entity." 554 ::= { ipFrrProtectStatsEntry 1 } 556 ipFrrStatsUnprotectedRoutes OBJECT-TYPE 557 SYNTAX Gauge32 558 MAX-ACCESS read-only 559 STATUS current 560 DESCRIPTION 561 "The number of valid routes known by this entity 562 which do not have an alternate next-hop associated 563 with any primary next-hop." 564 ::= { ipFrrProtectStatsEntry 2 } 566 ipFrrStatsProtectedRoutes OBJECT-TYPE 567 SYNTAX Gauge32 568 MAX-ACCESS read-only 569 STATUS current 570 DESCRIPTION 571 "The number of routes known by this entity 572 which have at least one alternate next-hop." 573 ::= { ipFrrProtectStatsEntry 3 } 575 ipFrrStatsLinkProtectedRoutes OBJECT-TYPE 576 SYNTAX Gauge32 577 MAX-ACCESS read-only 578 STATUS current 579 DESCRIPTION 580 "The number of routes known by this entity 581 for which all alternate next-hops provide link 582 protection for their associated primary next-hops." 583 ::= { ipFrrProtectStatsEntry 4 } 585 ipFrrStatsNodeProtectedRoutes OBJECT-TYPE 586 SYNTAX Gauge32 587 MAX-ACCESS read-only 588 STATUS current 589 DESCRIPTION 590 "The number of routes known by this entity 591 for which all alternate next-hops provide node 592 protection for their associated primary next-hops." 593 ::= { ipFrrProtectStatsEntry 5 } 595 ipv6FrrStatsTotalRoutes OBJECT-TYPE 596 SYNTAX Gauge32 597 MAX-ACCESS read-only 598 STATUS current 599 DESCRIPTION 600 "The number of valid IPv6 routes known by this entity." 601 ::= { ipFrrProtectStatsEntry 6 } 603 ipv6FrrStatsUnprotectedRoutes OBJECT-TYPE 604 SYNTAX Gauge32 605 MAX-ACCESS read-only 606 STATUS current 607 DESCRIPTION 608 "The number of valid IPv6 routes known by this entity 609 which do not have an alternate next-hop associated 610 with any primary next-hop." 611 ::= { ipFrrProtectStatsEntry 7 } 613 ipv6FrrStatsProtectedRoutes OBJECT-TYPE 614 SYNTAX Gauge32 615 MAX-ACCESS read-only 616 STATUS current 617 DESCRIPTION 618 "The number of IPv6 routes known by this entity 619 which have at least one alternate next-hop." 620 ::= { ipFrrProtectStatsEntry 8 } 622 ipv6FrrStatsLinkProtectedRoutes OBJECT-TYPE 623 SYNTAX Gauge32 624 MAX-ACCESS read-only 625 STATUS current 626 DESCRIPTION 627 "The number of IPv6 routes known by this entity 628 for which all alternate next-hops provide link 629 protection for their associated primary next-hops." 630 ::= { ipFrrProtectStatsEntry 9 } 632 ipv6FrrStatsNodeProtectedRoutes OBJECT-TYPE 633 SYNTAX Gauge32 634 MAX-ACCESS read-only 635 STATUS current 636 DESCRIPTION 637 "The number of IPv6 routes known by this entity 638 for which all alternate next-hops provide node 639 protection for their associated primary next-hops." 640 ::= { ipFrrProtectStatsEntry 10 } 642 -- the IP FRR Alternate MIB-Group 643 -- 644 -- The ipFrrAltTable extends the inetCidrRouteTable to indicate 645 -- the alternate next-hop(s) associated with each primary 646 -- next-hop. The additional indices (ipFrrAltNextHopType and 647 -- ipFrrAltNextHop ) allow for multiple alternate paths for a 648 -- given primary next-hop. 650 ipFrrAltTable OBJECT-TYPE 651 SYNTAX SEQUENCE OF IpFrrAltEntry 652 MAX-ACCESS not-accessible 653 STATUS current 654 DESCRIPTION 655 "This entity's IP Fast Reroute Alternates table." 656 ::= { ipFrrMIBObjects 2 } 658 ipFrrAltEntry OBJECT-TYPE 659 SYNTAX IpFrrAltEntry 660 MAX-ACCESS not-accessible 661 STATUS current 662 DESCRIPTION 663 "An entry containing information on a particular route, 664 one of its particular (primary) next-hops and one of 665 the associated alternate next-hops. 667 Implementers need to be aware that if the total 668 number of elements (octets or sub-identifiers) in 669 inetCidrRouteDest, inetCidrRoutePolicy, 670 inetCidrRouteNextHop, and ipFrrAltNextHop exceeds 107 671 then OIDs of column instances in this table will have 672 more than 128 sub-identifiers and cannot be accessed 673 using SNMPv1, SNMPv2c, or SNMPv3." 675 INDEX { inetCidrRouteDestType, 676 inetCidrRouteDest, 677 inetCidrRoutePfxLen, 678 inetCidrRoutePolicy, 679 inetCidrRouteNextHopType, 680 inetCidrRouteNextHop, 681 ipFrrAltNextHopType, 682 ipFrrAltNextHop 683 } 684 ::= { ipFrrAltTable 1 } 686 IpFrrAltEntry ::= SEQUENCE { 687 ipFrrAltNextHopType InetAddressType, 688 ipFrrAltNextHop InetAddress, 689 ipFrrAltIfIndex InterfaceIndex, 690 ipFrrAltType INTEGER, 691 ipFrrTunnelType INTEGER, 692 ipFrrAltProtectionAvailable BITS, 693 ipFrrAltMetric1 Integer32, 694 ipFrrAltMetric2 Integer32, 695 ipFrrAltMetric3 Integer32, 696 ipFrrAltBest INTEGER, 697 ipFrrAltNonBestReason OCTET STRING, 698 ipFrrAltStatus RowStatus 699 } 701 ipFrrAltNextHopType OBJECT-TYPE 702 SYNTAX InetAddressType 703 MAX-ACCESS not-accessible 704 STATUS current 705 DESCRIPTION 706 "The type of the ipFrrNextHop address, as defined 707 in the InetAddress MIB. 709 Only those address types that may appear in an actual 710 routing table are allowed as values of this object." 711 REFERENCE "RFC 4001" 712 ::= { ipFrrAltEntry 1 } 714 ipFrrAltNextHop OBJECT-TYPE 715 SYNTAX InetAddress 716 MAX-ACCESS not-accessible 717 STATUS current 718 DESCRIPTION 719 "The address of the next system along the alternate 720 route. 722 The type of this address is determined by the value 723 of the ipFrrAltNextHopType." 724 ::= { ipFrrAltEntry 2 } 726 ipFrrAltIfIndex OBJECT-TYPE 727 SYNTAX InterfaceIndex 728 MAX-ACCESS read-create 729 STATUS current 730 DESCRIPTION 731 "The ifIndex value which identifies the local 732 interface through which the next hop of this 733 alternate route should be reached." 734 ::= { ipFrrAltEntry 3 } 736 ipFrrAltType OBJECT-TYPE 737 SYNTAX INTEGER { 738 other (1), -- type not defined 739 equalCost (2), -- primary path 740 loopFree (3), -- loop free alternate 741 loopFreeRemote (4), -- remote loop free alternate 742 loopFreeNH (5), -- loop free alternate using a configured tunnel toward the nexthop 743 loopFreeNNH (6), -- loop free alternate using a configured tunnel toward the nextnexthop 744 loopFreeTI (7), -- loop free alternate using topology independent algorithm 745 mrt (8) -- Maximally Redundant Trees 746 } 747 MAX-ACCESS read-create 748 STATUS current 749 DESCRIPTION 750 "The type of alternate which is provided by the 751 alternate next-hop. The supported types are as 752 follows: 754 equalCost : The alternate next-hop is another 755 primary next-hop. 757 loopFreeConnected : loop free alternate (LFA as described in RFC5286) 759 loopFreeRemote : remote LFA (as described in draft-ietf-rtgwg-remote-lfa) 761 loopFreeNH : loop free alternate using a configured tunnel toward the nexthop (link protection only) 763 loopFreeNNH : loop free alternate using a configured tunnel toward the nextnexthop (node protection) 765 loopFreeTI : loop free alternate using topology independent algorithm 767 other : The mechanism by which the alternate next-hop 768 can be used is not specified. 770 MRT : Maximally Redundant Trees, where each 771 destination has two MRTs associated with it. 772 These two trees are referred as blue and red 773 MRTs. 774 See draft-ietf-rtgwg-mrt-frr-architecture-00. 775 " 776 ::= { ipFrrAltEntry 4 } 778 ipFrrTunnelType OBJECT-TYPE 779 SYNTAX INTEGER { 780 none (1), -- No tunnel used 781 other (2), -- type not defined 782 LDP (3), -- LDP tunnel 783 IP (4), -- IP based tunnel (GRE, IPIP, L2TP ...) 784 SPRING MPLS (5), -- SPRING tunnel using MPLS dataplane 785 SPRING IPv6 (6), -- SPRING tunnel using IPv6 dataplane 786 RSVP-TE (7), -- RSVP-TE tunnel 787 MULTI-TOPOLOGY LDP(8) -- LDP tunnel on another topology 788 } 789 MAX-ACCESS read-create 790 STATUS current 791 DESCRIPTION 792 "The type of tunnel used to reach the alternate. 793 The supported types are as follows: 795 none : No tunnel used 797 LDP : use LDP tunnel to reach the alternate (typically the case of rLFA) 799 IP : use IP based tunnel to reach the alternate 801 SPRING MPLS or SPRING IPv6 : use SPRING based tunnel (typically the case of TI-LFA) 802 RSVP-TE : use a RSVP-TE LSP to reach the alternate 804 MULTI-TOPOLOGY LDP : use an LDP tunnel based on another topology (typically the case of MRT) 806 " 807 ::= { ipFrrAltEntry 5 } 809 ipFrrAltProtectionAvailable OBJECT-TYPE 810 SYNTAX BITS { 811 nodeProtect(0), 812 linkProtect(1), 813 srlgProtect(2), 814 downstreamProtect(3), 815 unknownProtection(4) 816 } 817 MAX-ACCESS read-create 818 STATUS current 819 DESCRIPTION 820 "This object specifies the scope of protection for 821 which this alternate next-hop can provide failure 822 protection. The alternate next-hop should provide 823 one or more of node-protection and link-protection. 824 If the protection provided by the alternate next-hop 825 is unknown, then only unknownProtection should be 826 specified. Specifying uknownProtection with any 827 other type of protection is not supported. " 828 ::= { ipFrrAltEntry 6 } 830 ipFrrAltMetric1 OBJECT-TYPE 831 SYNTAX Integer32 832 MAX-ACCESS read-create 833 STATUS current 834 DESCRIPTION 835 "This is the primary routing metric for this 836 alternate path to the destination IP address. 837 If the alternate path metric is unknown, the value 838 should be set to -1." 839 ::= { ipFrrAltEntry 7 } 841 ipFrrAltMetric2 OBJECT-TYPE 842 SYNTAX Integer32 843 MAX-ACCESS read-create 844 STATUS current 845 DESCRIPTION 846 "This is the primary routing metric for this 847 alternate path from the PLR to the alternate. 848 If the alternate path metric is unknown, the value 849 should be set to -1." 850 ::= { ipFrrAltEntry 8 } 852 ipFrrAltMetric3 OBJECT-TYPE 853 SYNTAX Integer32 854 MAX-ACCESS read-create 855 STATUS current 856 DESCRIPTION 857 "This is the primary routing metric for this 858 alternate path from the alternate to the destination. 859 If the alternate path metric is unknown, the value 860 should be set to -1." 861 ::= { ipFrrAltEntry 9 } 863 ipFrrAltBest OBJECT-TYPE 864 SYNTAX INTEGER { false(0), true(1) } 865 MAX-ACCESS read-create 866 STATUS current 867 DESCRIPTION 868 "This object provides information if the alternate is the best one." 869 ::= { ipFrrAltEntry 10 } 871 ipFrrAltNonBestReason OBJECT-TYPE 872 SYNTAX OCTET STRING (SIZE (0..255)) 873 MAX-ACCESS read-create 874 STATUS current 875 DESCRIPTION 876 "This object provides reason why an alternate is not the best one." 877 ::= { ipFrrAltEntry 11 } 879 ipFrrAltStatus OBJECT-TYPE 880 SYNTAX RowStatus 881 MAX-ACCESS read-create 882 STATUS current 883 DESCRIPTION 884 "The row status variable, used according to 885 row installation and removal conventions." 886 ::= { ipFrrAltEntry 12 } 888 -- the IP FRR No Alternate MIB-Group 889 -- 890 -- The ipFrrNoAltTable extends the inetCidrRouteTable 891 -- to indicate which routes are unprotected and the reason 892 -- why. The indices do not include the primary next-hop because 893 -- the lack of protection is for the route. This allows easy 894 -- access to the set of unprotected routes that would be 895 -- affected by a local failure of their primary next-hop. 897 ipFrrNoAltTable OBJECT-TYPE 898 SYNTAX SEQUENCE OF IpFrrNoAltEntry 899 MAX-ACCESS not-accessible 900 STATUS current 901 DESCRIPTION 902 "This entity's IP Fast Reroute Unprotected Routes 903 table." 904 ::= { ipFrrMIBObjects 3 } 906 ipFrrNoAltEntry OBJECT-TYPE 907 SYNTAX IpFrrNoAltEntry 908 MAX-ACCESS not-accessible 909 STATUS current 910 DESCRIPTION 911 "An entry containing the reason why a route does not 912 have an alternate next-hop. The existence of an 913 entry for a route indicates that there is no 914 alternate next-hop." 915 INDEX { inetCidrRouteDestType, 916 inetCidrRouteDest, 917 inetCidrRoutePfxLen 918 } 919 ::= { ipFrrNoAltTable 1 } 921 IpFrrNoAltEntry ::= SEQUENCE { 922 ipFrrNoAltCause INTEGER 923 } 925 ipFrrNoAltCause OBJECT-TYPE 926 SYNTAX INTEGER { 927 ipFrrUnavailable (1), -- No valid alternate(s) 928 localAddress (2), -- local/internal address 929 ipFrrDisabled (3), -- Protection not enabled 930 other (4) -- unknown or other cause 931 } 932 MAX-ACCESS read-only 933 STATUS current 934 DESCRIPTION 935 "For valid routes without an alternate next-hop, this 936 object enumerates the reason why no protection is 937 available. The possibilities are as follows. 939 ipFrrUnavailable : The supported IP Fast-Reroute 940 mechanisms could not find a safe 941 alternate next-hop. 943 localAddress : The route represents a local address. 944 This system is the destination so no 945 alternate path is possible or necessary. 947 ipFrrDisabled : Finding of alternate next-hops is 948 operationally disabled. 950 other : The reason is unknown or different from those 951 specifically enumerated possible causes." 952 ::= { ipFrrNoAltEntry 1 } 954 -- conformance information 956 ipFrrMIBConformance 957 OBJECT IDENTIFIER ::= { ipFrrMIB 2 } 959 ipFrrMIBCompliances 960 OBJECT IDENTIFIER ::= { ipFrrMIBConformance 1 } 962 ipFrrMIBGroups 963 OBJECT IDENTIFIER ::= { ipFrrMIBConformance 2 } 965 -- compliance statements 967 ipFrrMIBCompliance MODULE-COMPLIANCE 968 STATUS deprecated 969 DESCRIPTION 970 "Minimum requirements to state conformity 971 to this MIB. Supporting only IP v4 addresses 972 This is deprecated in favor of 973 ipFrrMIBInetCompliance 975 There are a number of INDEX objects that cannot be 976 represented in the form of OBJECT clauses in SMIv2, 977 but for which there are compliance requirements, 978 expressed in OBJECT clause form in this description: 980 OBJECT inetCidrRouteDestType 981 SYNTAX InetAddressType { ipv4(1), ipv4z(3) } 982 MIN-ACCESS read-only 983 DESCRIPTION 984 A (deprecated) complying implementation at this 985 level is required to support IPv4 addresses only. 986 This compliance level is defined so an 987 implementation only needs to support the addresses 988 it actually supports on the device. 990 OBJECT inetCidrRouteNextHopType 991 SYNTAX InetAddressType { ipv4(1), ipv4z(3) } 992 MIN-ACCESS read-only 994 DESCRIPTION 995 A (deprecated) complying implementation at this 996 level is required to support IPv4 addresses only. 997 This compliance level is defined so an 998 implementation only needs to support the addresses 999 it actually supports on the device. 1001 OBJECT ipFrrAltNextHopType 1002 SYNTAX InetAddressType { ipv4(1), ipv4z(3) } 1003 MIN-ACCESS read-only 1004 DESCRIPTION 1005 A (deprecated) complying implementation at this 1006 level is required to support IPv4 addresses only. 1007 This compliance level is defined so an 1008 implementation only needs to support the 1009 addresses it actually supports on the device. 1010 " 1011 MODULE -- this module 1012 MANDATORY-GROUPS { ipFrrBasicGroup } 1014 ::= { ipFrrMIBCompliances 1 } 1016 ipFrrMIBInetCompliance MODULE-COMPLIANCE 1017 STATUS current 1018 DESCRIPTION 1019 "Full conformity to this MIB." 1020 MODULE -- this module 1021 MANDATORY-GROUPS { ipFrrBasicGroup } 1023 OBJECT ipFrrAltStatus 1024 SYNTAX INTEGER { active(1) } 1025 WRITE-SYNTAX INTEGER { createAndGo(4), destroy(6) } 1026 DESCRIPTION 1027 "Support for createAndWait and notInService is not 1028 required." 1030 ::= { ipFrrMIBCompliances 2 } 1032 ipFrrReadOnlyCompliance MODULE-COMPLIANCE 1033 STATUS current 1034 DESCRIPTION 1036 "When this MIB is implemented without support for 1037 read-create (i.e. in read-only mode), then that 1038 implementation can claim read-only compliance. In that 1039 case, ipFrrAlt group can be monitored but cannot be 1040 configured with this MIB." 1042 MODULE 1043 MANDATORY-GROUPS { ipFrrBasicGroup } 1045 OBJECT ipFrrAltIfIndex 1046 MIN-ACCESS read-only 1047 DESCRIPTION 1048 "Write access is not required." 1050 OBJECT ipFrrAltType 1051 MIN-ACCESS read-only 1052 DESCRIPTION 1053 "Write access is not required." 1055 OBJECT ipFrrAltProtectionAvailable 1056 MIN-ACCESS read-only 1057 DESCRIPTION 1058 "Write access is not required." 1060 OBJECT ipFrrAltMetric1 1061 MIN-ACCESS read-only 1062 DESCRIPTION 1063 "Write access is not required." 1065 OBJECT ipFrrAltStatus 1066 MIN-ACCESS read-only 1067 DESCRIPTION 1068 "Write access is not required." 1070 ::= { ipFrrMIBCompliances 3 } 1072 -- units of conformance 1073 ipFrrBasicGroup OBJECT-GROUP 1074 OBJECTS {ipFrrTotalRoutes, 1075 ipFrrUnprotectedRoutes, 1076 ipFrrProtectedRoutes, 1077 ipFrrLinkProtectedRoutes, 1078 ipFrrNodeProtectedRoutes, 1079 ipv6FrrTotalRoutes, 1080 ipv6FrrUnprotectedRoutes, 1081 ipv6FrrProtectedRoutes, 1082 ipv6FrrLinkProtectedRoutes, 1083 ipv6FrrNodeProtectedRoutes, 1084 ipFrrAltIfIndex, 1085 ipFrrAltType, 1086 ipFrrAltProtectionAvailable, 1087 ipFrrAltMetric1, 1088 ipFrrAltMetric2, 1089 ipFrrAltMetric3, 1090 ipFrrAltNonBestReason, 1091 ipFrrAltBest, 1092 ipFrrAltStatus, 1093 ipFrrNoAltCause, 1094 ipFrrInstanceAlgorithm, 1095 ipFrrInstanceProtocol, 1096 ipFrrInstancePerPrefixComputation, 1097 ipFrrInstanceRowStatus, 1098 ipFrrIfCandidate, 1099 ipFrrIfProtectionType, 1100 ipFrrIfRowStatus, 1101 ipFrrStatsTotalRoutes, 1102 ipFrrStatsUnprotectedRoutes, 1103 ipFrrStatsProtectedRoutes, 1104 ipFrrStatsLinkProtectedRoutes, 1105 ipFrrStatsNodeProtectedRoutes, 1106 ipv6FrrStatsTotalRoutes, 1107 ipv6FrrStatsUnprotectedRoutes, 1108 ipv6FrrStatsProtectedRoutes, 1109 ipv6FrrStatsLinkProtectedRoutes, 1110 ipv6FrrStatsNodeProtectedRoutes 1112 } 1113 STATUS current 1114 DESCRIPTION 1115 "The entire collection of objects defined in 1116 this MIB for management of IP Fast Reroute ." 1117 ::= { ipFrrMIBGroups 1 } 1119 END 1121 4. Security Considerations 1123 There are a number of management objects defined in this MIB module 1124 with a MAX-ACCESS clause of read-write and/or read-create. Such 1125 objects may be considered sensitive or vulnerable in some network 1126 environments. The support for SET operations in a non-secure 1127 environment without proper protection can have a negative effect on 1128 network operations. The ipFrrAltTable contains routing and 1129 forwarding information that is critical to the operation of the 1130 network in the event of a local failure. Allowing unauthenticated 1131 write access to this table can compromise the validity of the 1132 alternate forwarding information. 1134 Some of the readable objects in this MIB module (i.e. objects with a 1135 MAX-ACCESS other than not-accessible) may be considered sensitive or 1136 vulnerable in some network environments. It is thus important to 1137 control even GET access to these objects and possibly to even encrypt 1138 the values of these objects when sending them over the network via 1139 SNMP. 1141 SNMP versions prior to SNMPv3 did not include adequate security. 1142 Even if the network itself is secure (for example by using IPSec), 1143 even then, there is no control as to who on the secure network is 1144 allowed to access and GET the objects in this MIB module. 1146 It is RECOMMENDED that implementers consider the security features as 1147 provided by the SNMPv3 framework (see [RFC3410], section 8), 1148 including full support for the SNMPv3 cryptographic mechanisms (for 1149 authentication and privacy). 1151 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1152 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1153 enable cryptographic security. It is then a customer/operator 1154 responsibility to ensure that the SNMP entity giving access to an 1155 instance of this MIB module is properly configured to give access to 1156 the objects only to those principals (users) that have legitimate 1157 rights to indeed GET them. 1159 5. Acknowledgements 1161 The authors would like to acknowledge contributions made by Bill 1162 Anderson, Don Fedyk and Bruno Decraene. 1164 6. IANA Considerations 1166 The MIB module in this document uses the following IANA-assigned 1167 OBJECT IDENTIFIER value recorded in the SMI Numbers registry. 1169 The IANA is requested to assign { ip ZZZ } to the IPFRR-MIB MIB 1170 module specified in this document. 1172 Editor's Note (to be removed prior to publication): the IANA is 1173 requested to assign a value for "ZZZ" under the ip subtree and to 1174 record the assignments in the SMI Numbers registry. When the 1175 assignments have been made, the RFC Editor is asked to replace "ZZZ" 1176 (here and in the MIB modules) with the assigned value and to remove 1177 this note. 1179 7. References 1180 7.1. Normative References 1182 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1183 Requirement Levels", BCP 14, RFC 2119, March 1997. 1185 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1186 MIB", RFC 2863, June 2000. 1188 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 1189 Schoenwaelder, "Textual Conventions for Internet Network 1190 Addresses", RFC 4001, February 2005. 1192 [RFC4292] Haberman, B., "IP Forwarding Table MIB", RFC 4292, April 1193 2006. 1195 [RFC4293] Routhier, S., "Management Information Base for the 1196 Internet Protocol (IP)", RFC 4293, April 2006. 1198 [RFC5286] Atlas, A. and A. Zinin, "Basic Specification for IP Fast 1199 Reroute: Loop-Free Alternates", RFC 5286, September 2008. 1201 7.2. Informative References 1203 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1204 Schoenwaelder, Ed., "Structure of Management Information 1205 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1207 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1208 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 1209 58, RFC 2579, April 1999. 1211 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1212 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1213 April 1999. 1215 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1216 "Introduction and Applicability Statements for Internet- 1217 Standard Management Framework", RFC 3410, December 2002. 1219 [RFC5036] Andersson, L., Minei, I., and B. Thomas, "LDP 1220 Specification", RFC 5036, October 2007. 1222 [RFC5714] Shand, M. and S. Bryant, "IP Fast Reroute Framework", RFC 1223 5714, January 2010. 1225 Authors' Addresses 1227 Alia Atlas 1228 Juniper Networks 1230 Email: akatlas@juniper.net 1232 A S Kiran Koushik 1233 Cisco Systems 1235 Email: kkoushik@cisco.com 1237 John Flick 1238 Hewlett-Packard 1240 Email: john.flick@hp.com 1242 Stephane Litkowski 1243 Orange 1245 Email: stephane.litkowski@orange.com