idnits 2.17.1 draft-ietf-rtgwg-ipfrr-ip-mib-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 58 instances of too long lines in the document, the longest one being 64 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 (June 15, 2015) is 3236 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: December 17, 2015 Cisco Systems 6 J. Flick 7 Hewlett-Packard 8 S. Litkowski 9 Orange 10 June 15, 2015 12 IP MIB for IP Fast-Reroute 13 draft-ietf-rtgwg-ipfrr-ip-mib-06 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 December 17, 2015. 45 Copyright Notice 47 Copyright (c) 2015 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 231 DESCRIPTION 232 "Add ipFrrTunnelType in ipFrrAltEntry 233 Modify ipFrrAltType" 234 REVISION "201405261200Z" -- May 26, 2014 235 DESCRIPTION 236 "Add ipFrrInstanceTable. 237 Add ipFrrIfTable. 238 ipFrrProtectStatsTable complements ipFrrProtectStats to have statistics per instance. 239 Add ipFrrAltMetric2, ipFrrAltMetric3, ipFrrAltBest, ipFrrAltNonBestReason to ipFrrAltEntry. 240 Add integer values to ipFrrAltType. 241 Add integer values to ipFrrAltProtectionAvailable. 242 Changed attachement of ipFrrAltStatus in ipFrrAltEntry. 243 Added IPv6 objects in ipFrrProtectStats." 244 REVISION "201203131200Z" -- Mar 13, 2012 245 DESCRIPTION 246 "Editorial changes. Added new type to ipFrrAltType." 247 REVISION "200502181200Z" -- February 18, 2005 248 DESCRIPTION 249 "Add Set operations on ipFrrAltTable" 250 REVISION "200502131200Z" -- February 13, 2005 251 DESCRIPTION 252 "Initial version." 253 ::= { ip ZZZ } -- To be assigned by IANA 255 -- Top level components of this MIB module. 257 ipFrrMIBObjects OBJECT IDENTIFIER ::= { ipFrrMIB 1 } 259 ipFrrProtectStats OBJECT IDENTIFIER ::= { ipFrrMIBObjects 1 } 261 -- the IP FRR MIB-Group 263 -- A collection of objects providing summarized information 264 -- about the protection availability and type of alternate paths 265 -- provided by IP Fast-Reroute mechanisms. 267 ipFrrTotalRoutes OBJECT-TYPE 268 SYNTAX Gauge32 269 MAX-ACCESS read-only 270 STATUS current 271 DESCRIPTION 272 "The number of IPv4 valid routes known by this entity." 273 ::= { ipFrrProtectStats 1 } 275 ipFrrUnprotectedRoutes OBJECT-TYPE 276 SYNTAX Gauge32 277 MAX-ACCESS read-only 278 STATUS current 279 DESCRIPTION 280 "The number of IPv4 valid routes known by this entity 281 which do not have an alternate next-hop associated 282 with any primary next-hop." 283 ::= { ipFrrProtectStats 2 } 285 ipFrrProtectedRoutes OBJECT-TYPE 286 SYNTAX Gauge32 287 MAX-ACCESS read-only 288 STATUS current 289 DESCRIPTION 290 "The number of IPv4 routes known by this entity 291 which have at least one alternate next-hop." 292 ::= { ipFrrProtectStats 3 } 294 ipFrrLinkProtectedRoutes OBJECT-TYPE 295 SYNTAX Gauge32 296 MAX-ACCESS read-only 297 STATUS current 298 DESCRIPTION 299 "The number of IPv4 routes known by this entity 300 for which all alternate next-hops provide link 301 protection for their associated primary next-hops." 302 ::= { ipFrrProtectStats 4 } 304 ipFrrNodeProtectedRoutes OBJECT-TYPE 305 SYNTAX Gauge32 306 MAX-ACCESS read-only 307 STATUS current 308 DESCRIPTION 309 "The number of IPv4 routes known by this entity 310 for which all alternate next-hops provide node 311 protection for their associated primary next-hops." 312 ::= { ipFrrProtectStats 5 } 314 ipv6FrrTotalRoutes OBJECT-TYPE 315 SYNTAX Gauge32 316 MAX-ACCESS read-only 317 STATUS current 318 DESCRIPTION 319 "The number of IPv6 valid routes known by this entity." 320 ::= { ipFrrProtectStats 6 } 322 ipv6FrrUnprotectedRoutes OBJECT-TYPE 323 SYNTAX Gauge32 324 MAX-ACCESS read-only 325 STATUS current 326 DESCRIPTION 327 "The number of IPv6 valid routes known by this entity 328 which do not have an alternate next-hop associated 329 with any primary next-hop." 330 ::= { ipFrrProtectStats 7 } 332 ipv6FrrProtectedRoutes OBJECT-TYPE 333 SYNTAX Gauge32 334 MAX-ACCESS read-only 335 STATUS current 336 DESCRIPTION 337 "The number of IPv6 routes known by this entity 338 which have at least one alternate next-hop." 339 ::= { ipFrrProtectStats 8 } 341 ipv6FrrLinkProtectedRoutes OBJECT-TYPE 342 SYNTAX Gauge32 343 MAX-ACCESS read-only 344 STATUS current 345 DESCRIPTION 346 "The number of IPv6 routes known by this entity 347 for which all alternate next-hops provide link 348 protection for their associated primary next-hops." 349 ::= { ipFrrProtectStats 9 } 351 ipv6FrrNodeProtectedRoutes OBJECT-TYPE 352 SYNTAX Gauge32 353 MAX-ACCESS read-only 354 STATUS current 355 DESCRIPTION 356 "The number of IPv6 routes known by this entity 357 for which all alternate next-hops provide node 358 protection for their associated primary next-hops." 359 ::= { ipFrrProtectStats 10 } 361 -- the IP FRR instance MIB-group 362 -- 363 -- The ipFrrInstanceTable provides detail on current IPFRR 364 -- instances activated on the node 366 ipFrrInstanceTable OBJECT-TYPE 367 SYNTAX SEQUENCE OF IpFrrInstanceEntry 368 MAX-ACCESS not-accessible 369 STATUS current 370 DESCRIPTION 371 "This entity's IP Fast Reroute Instance table." 372 ::= { 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 } 421 ipFrrInstancePerPrefixComputation OBJECT-TYPE 422 SYNTAX INTEGER { 423 false(0), 424 true(1) 425 } 426 MAX-ACCESS read-create 427 STATUS current 428 DESCRIPTION 429 "This object specifies if per prefix computation is used." 430 ::= { ipFrrInstanceEntry 4 } 432 ipFrrInstanceRowStatus OBJECT-TYPE 433 SYNTAX RowStatus 434 MAX-ACCESS read-create 435 STATUS current 436 DESCRIPTION 437 "." 438 ::= { ipFrrInstanceEntry 5 } 440 -- the IP FRR Interface MIB-Group 441 -- 442 -- ipFrrIfTable provides information on configuration 443 -- of interfaces for IPFRR 445 ipFrrIfTable OBJECT-TYPE 446 SYNTAX SEQUENCE OF IpFrrIfEntry 447 MAX-ACCESS not-accessible 448 STATUS current 449 DESCRIPTION 450 "This entity's IP Fast Reroute Alternates Interface configuration table." 451 ::= { ipFrrMIBObjects 5 } 453 ipFrrIfEntry OBJECT-TYPE 454 SYNTAX IpFrrIfEntry 455 MAX-ACCESS not-accessible 456 STATUS current 457 DESCRIPTION 458 "An entry containing information on a particular instance of an IPFRR interface." 460 INDEX { ipFrrInstanceId, 461 ifIndex 462 } 463 ::= { ipFrrIfTable 1 } 465 IpFrrIfEntry ::= SEQUENCE { 466 ipFrrIfProtectionType BITS, 467 ipFrrIfCandidate INTEGER, 468 ipFrrIfRowStatus RowStatus 469 } 471 ipFrrIfProtectionType OBJECT-TYPE 472 SYNTAX BITS { 473 nodeProtect(0), 474 linkProtect(1), 475 nodelinkProtect(2) 476 } 477 MAX-ACCESS read-create 478 STATUS current 479 DESCRIPTION 480 "This object specifies the scope of protection requested for the protection of the destinations. 481 nodeProtect means node protection only compared to nodelinkProtect which means node protection 482 if available and link protection if not available. " 483 ::= { ipFrrIfEntry 1 } 485 ipFrrIfCandidate OBJECT-TYPE 486 SYNTAX INTEGER { 487 false (0), 488 true (1) 490 } 491 MAX-ACCESS read-create 492 STATUS current 493 DESCRIPTION 494 "This object specifies the scope of protection requested for the protection of the destinations. 495 nodeProtect means node protection only compared to nodelinkProtect which means node protection 496 if available and link protection if not available. " 497 ::= { ipFrrIfEntry 2 } 499 ipFrrIfRowStatus OBJECT-TYPE 500 SYNTAX RowStatus 501 MAX-ACCESS read-create 502 STATUS current 503 DESCRIPTION 504 "." 505 ::= { ipFrrIfEntry 3 } 507 -- the IP FRR Stats MIB-Group 508 -- 509 -- ipFrrProtectStatsTable provides provides 510 -- protection availability and type of alternate paths 511 -- provided by IP Fast-Reroute mechanisms per IPFRR instance. 513 ipFrrProtectStatsTable OBJECT-TYPE 514 SYNTAX SEQUENCE OF IpFrrProtectStatsEntry 515 MAX-ACCESS not-accessible 516 STATUS current 517 DESCRIPTION 518 "This entity's IP Fast Reroute Alternates statistics table." 519 ::= { ipFrrMIBObjects 6 } 521 ipFrrProtectStatsEntry OBJECT-TYPE 522 SYNTAX IpFrrProtectStatsEntry 523 MAX-ACCESS not-accessible 524 STATUS current 525 DESCRIPTION 526 "An entry containing information on a particular instance of IPFRR. 528 ." 530 INDEX { ipFrrInstanceId 531 } 532 ::= { ipFrrProtectStatsTable 1 } 534 IpFrrProtectStatsEntry ::= SEQUENCE { 535 ipFrrStatsTotalRoutes Gauge32, 536 ipFrrStatsUnprotectedRoutes Gauge32, 537 ipFrrStatsProtectedRoutes Gauge32, 538 ipFrrStatsLinkProtectedRoutes Gauge32, 539 ipFrrStatsNodeProtectedRoutes Gauge32, 540 ipv6FrrStatsTotalRoutes Gauge32, 541 ipv6FrrStatsUnprotectedRoutes Gauge32, 542 ipv6FrrStatsProtectedRoutes Gauge32, 543 ipv6FrrStatsLinkProtectedRoutes Gauge32, 544 ipv6FrrStatsNodeProtectedRoutes Gauge32 545 } 547 ipFrrStatsTotalRoutes OBJECT-TYPE 548 SYNTAX Gauge32 549 MAX-ACCESS read-only 550 STATUS current 551 DESCRIPTION 552 "The number of valid routes known by this entity." 553 ::= { ipFrrProtectStatsEntry 1 } 555 ipFrrStatsUnprotectedRoutes OBJECT-TYPE 556 SYNTAX Gauge32 557 MAX-ACCESS read-only 558 STATUS current 559 DESCRIPTION 560 "The number of valid routes known by this entity 561 which do not have an alternate next-hop associated 562 with any primary next-hop." 563 ::= { ipFrrProtectStatsEntry 2 } 565 ipFrrStatsProtectedRoutes OBJECT-TYPE 566 SYNTAX Gauge32 567 MAX-ACCESS read-only 568 STATUS current 569 DESCRIPTION 570 "The number of routes known by this entity 571 which have at least one alternate next-hop." 572 ::= { ipFrrProtectStatsEntry 3 } 574 ipFrrStatsLinkProtectedRoutes OBJECT-TYPE 575 SYNTAX Gauge32 576 MAX-ACCESS read-only 577 STATUS current 578 DESCRIPTION 579 "The number of routes known by this entity 580 for which all alternate next-hops provide link 581 protection for their associated primary next-hops." 582 ::= { ipFrrProtectStatsEntry 4 } 584 ipFrrStatsNodeProtectedRoutes OBJECT-TYPE 585 SYNTAX Gauge32 586 MAX-ACCESS read-only 587 STATUS current 588 DESCRIPTION 589 "The number of routes known by this entity 590 for which all alternate next-hops provide node 591 protection for their associated primary next-hops." 592 ::= { ipFrrProtectStatsEntry 5 } 594 ipv6FrrStatsTotalRoutes OBJECT-TYPE 595 SYNTAX Gauge32 596 MAX-ACCESS read-only 597 STATUS current 598 DESCRIPTION 599 "The number of valid IPv6 routes known by this entity." 600 ::= { ipFrrProtectStatsEntry 6 } 602 ipv6FrrStatsUnprotectedRoutes OBJECT-TYPE 603 SYNTAX Gauge32 604 MAX-ACCESS read-only 605 STATUS current 606 DESCRIPTION 607 "The number of valid IPv6 routes known by this entity 608 which do not have an alternate next-hop associated 609 with any primary next-hop." 610 ::= { ipFrrProtectStatsEntry 7 } 612 ipv6FrrStatsProtectedRoutes OBJECT-TYPE 613 SYNTAX Gauge32 614 MAX-ACCESS read-only 615 STATUS current 616 DESCRIPTION 617 "The number of IPv6 routes known by this entity 618 which have at least one alternate next-hop." 619 ::= { ipFrrProtectStatsEntry 8 } 621 ipv6FrrStatsLinkProtectedRoutes OBJECT-TYPE 622 SYNTAX Gauge32 623 MAX-ACCESS read-only 624 STATUS current 625 DESCRIPTION 626 "The number of IPv6 routes known by this entity 627 for which all alternate next-hops provide link 628 protection for their associated primary next-hops." 629 ::= { ipFrrProtectStatsEntry 9 } 631 ipv6FrrStatsNodeProtectedRoutes OBJECT-TYPE 632 SYNTAX Gauge32 633 MAX-ACCESS read-only 634 STATUS current 635 DESCRIPTION 636 "The number of IPv6 routes known by this entity 637 for which all alternate next-hops provide node 638 protection for their associated primary next-hops." 639 ::= { ipFrrProtectStatsEntry 10 } 641 -- the IP FRR Alternate MIB-Group 642 -- 643 -- The ipFrrAltTable extends the inetCidrRouteTable to indicate 644 -- the alternate next-hop(s) associated with each primary 645 -- next-hop. The additional indices (ipFrrAltNextHopType and 646 -- ipFrrAltNextHop ) allow for multiple alternate paths for a 647 -- given primary next-hop. 649 ipFrrAltTable OBJECT-TYPE 650 SYNTAX SEQUENCE OF IpFrrAltEntry 651 MAX-ACCESS not-accessible 652 STATUS current 653 DESCRIPTION 654 "This entity's IP Fast Reroute Alternates table." 655 ::= { ipFrrMIBObjects 2 } 657 ipFrrAltEntry OBJECT-TYPE 658 SYNTAX IpFrrAltEntry 659 MAX-ACCESS not-accessible 660 STATUS current 661 DESCRIPTION 662 "An entry containing information on a particular route, 663 one of its particular (primary) next-hops and one of 664 the associated alternate next-hops. 666 Implementers need to be aware that if the total 667 number of elements (octets or sub-identifiers) in 668 inetCidrRouteDest, inetCidrRoutePolicy, 669 inetCidrRouteNextHop, and ipFrrAltNextHop exceeds 107 670 then OIDs of column instances in this table will have 671 more than 128 sub-identifiers and cannot be accessed 672 using SNMPv1, SNMPv2c, or SNMPv3." 674 INDEX { inetCidrRouteDestType, 675 inetCidrRouteDest, 676 inetCidrRoutePfxLen, 677 inetCidrRoutePolicy, 678 inetCidrRouteNextHopType, 679 inetCidrRouteNextHop, 680 ipFrrAltNextHopType, 681 ipFrrAltNextHop 682 } 683 ::= { ipFrrAltTable 1 } 685 IpFrrAltEntry ::= SEQUENCE { 686 ipFrrAltNextHopType InetAddressType, 687 ipFrrAltNextHop InetAddress, 688 ipFrrAltIfIndex InterfaceIndex, 689 ipFrrAltType INTEGER, 690 ipFrrTunnelType INTEGER, 691 ipFrrAltProtectionAvailable BITS, 692 ipFrrAltMetric1 Integer32, 693 ipFrrAltMetric2 Integer32, 694 ipFrrAltMetric3 Integer32, 695 ipFrrAltBest INTEGER, 696 ipFrrAltNonBestReason OCTET STRING, 697 ipFrrAltStatus RowStatus 698 } 700 ipFrrAltNextHopType OBJECT-TYPE 701 SYNTAX InetAddressType 702 MAX-ACCESS not-accessible 703 STATUS current 704 DESCRIPTION 705 "The type of the ipFrrNextHop address, as defined 706 in the InetAddress MIB. 708 Only those address types that may appear in an actual 709 routing table are allowed as values of this object." 710 REFERENCE "RFC 4001" 711 ::= { ipFrrAltEntry 1 } 713 ipFrrAltNextHop OBJECT-TYPE 714 SYNTAX InetAddress 715 MAX-ACCESS not-accessible 716 STATUS current 717 DESCRIPTION 718 "The address of the next system along the alternate 719 route. 721 The type of this address is determined by the value 722 of the ipFrrAltNextHopType." 723 ::= { ipFrrAltEntry 2 } 725 ipFrrAltIfIndex OBJECT-TYPE 726 SYNTAX InterfaceIndex 727 MAX-ACCESS read-create 728 STATUS current 729 DESCRIPTION 730 "The ifIndex value which identifies the local 731 interface through which the next hop of this 732 alternate route should be reached." 733 ::= { ipFrrAltEntry 3 } 735 ipFrrAltType OBJECT-TYPE 736 SYNTAX INTEGER { 737 other (1), -- type not defined 738 equalCost (2), -- primary path 739 loopFree (3), -- loop free alternate 740 loopFreeRemote (4), -- remote loop free alternate 741 loopFreeNH (5), -- loop free alternate using a configured tunnel toward the nexthop 742 loopFreeNNH (6), -- loop free alternate using a configured tunnel toward the nextnexthop 743 loopFreeTI (7), -- loop free alternate using topology independent algorithm 744 mrt (8) -- Maximally Redundant Trees 745 } 746 MAX-ACCESS read-create 747 STATUS current 748 DESCRIPTION 749 "The type of alternate which is provided by the 750 alternate next-hop. The supported types are as 751 follows: 753 equalCost : The alternate next-hop is another 754 primary next-hop. 756 loopFreeConnected : loop free alternate (LFA as described in RFC5286) 758 loopFreeRemote : remote LFA (as described in draft-ietf-rtgwg-remote-lfa) 760 loopFreeNH : loop free alternate using a configured tunnel toward the nexthop (link protection only) 762 loopFreeNNH : loop free alternate using a configured tunnel toward the nextnexthop (node protection) 764 loopFreeTI : loop free alternate using topology independent algorithm 766 other : The mechanism by which the alternate next-hop 767 can be used is not specified. 769 MRT : Maximally Redundant Trees, where each 770 destination has two MRTs associated with it. 771 These two trees are referred as blue and red 772 MRTs. 773 See draft-ietf-rtgwg-mrt-frr-architecture-00. 774 " 775 ::= { ipFrrAltEntry 4 } 777 ipFrrTunnelType OBJECT-TYPE 778 SYNTAX INTEGER { 779 none (1), -- No tunnel used 780 other (2), -- type not defined 781 LDP (3), -- LDP tunnel 782 IP (4), -- IP based tunnel (GRE, IPIP, L2TP ...) 783 SPRING MPLS (5), -- SPRING tunnel using MPLS dataplane 784 SPRING IPv6 (6), -- SPRING tunnel using IPv6 dataplane 785 RSVP-TE (7), -- RSVP-TE tunnel 786 MULTI-TOPOLOGY LDP(8) -- LDP tunnel on another topology 787 } 788 MAX-ACCESS read-create 789 STATUS current 790 DESCRIPTION 791 "The type of tunnel used to reach the alternate. 792 The supported types are as follows: 794 none : No tunnel used 796 LDP : use LDP tunnel to reach the alternate (typically the case of rLFA) 798 IP : use IP based tunnel to reach the alternate 800 SPRING MPLS or SPRING IPv6 : use SPRING based tunnel (typically the case of TI-LFA) 801 RSVP-TE : use a RSVP-TE LSP to reach the alternate 803 MULTI-TOPOLOGY LDP : use an LDP tunnel based on another topology (typically the case of MRT) 805 " 806 ::= { ipFrrAltEntry 5 } 808 ipFrrAltProtectionAvailable OBJECT-TYPE 809 SYNTAX BITS { 810 nodeProtect(0), 811 linkProtect(1), 812 srlgProtect(2), 813 downstreamProtect(3), 814 unknownProtection(4) 815 } 816 MAX-ACCESS read-create 817 STATUS current 818 DESCRIPTION 819 "This object specifies the scope of protection for 820 which this alternate next-hop can provide failure 821 protection. The alternate next-hop should provide 822 one or more of node-protection and link-protection. 823 If the protection provided by the alternate next-hop 824 is unknown, then only unknownProtection should be 825 specified. Specifying uknownProtection with any 826 other type of protection is not supported. " 827 ::= { ipFrrAltEntry 6 } 829 ipFrrAltMetric1 OBJECT-TYPE 830 SYNTAX Integer32 831 MAX-ACCESS read-create 832 STATUS current 833 DESCRIPTION 834 "This is the primary routing metric for this 835 alternate path to the destination IP address. 836 If the alternate path metric is unknown, the value 837 should be set to -1." 838 ::= { ipFrrAltEntry 7 } 840 ipFrrAltMetric2 OBJECT-TYPE 841 SYNTAX Integer32 842 MAX-ACCESS read-create 843 STATUS current 844 DESCRIPTION 845 "This is the primary routing metric for this 846 alternate path from the PLR to the alternate. 847 If the alternate path metric is unknown, the value 848 should be set to -1." 849 ::= { ipFrrAltEntry 8 } 851 ipFrrAltMetric3 OBJECT-TYPE 852 SYNTAX Integer32 853 MAX-ACCESS read-create 854 STATUS current 855 DESCRIPTION 856 "This is the primary routing metric for this 857 alternate path from the alternate to the destination. 858 If the alternate path metric is unknown, the value 859 should be set to -1." 860 ::= { ipFrrAltEntry 9 } 862 ipFrrAltBest OBJECT-TYPE 863 SYNTAX INTEGER { false(0), true(1) } 864 MAX-ACCESS read-create 865 STATUS current 866 DESCRIPTION 867 "This object provides information if the alternate is the best one." 868 ::= { ipFrrAltEntry 10 } 870 ipFrrAltNonBestReason OBJECT-TYPE 871 SYNTAX OCTET STRING (SIZE (0..255)) 872 MAX-ACCESS read-create 873 STATUS current 874 DESCRIPTION 875 "This object provides reason why an alternate is not the best one." 876 ::= { ipFrrAltEntry 11 } 878 ipFrrAltStatus OBJECT-TYPE 879 SYNTAX RowStatus 880 MAX-ACCESS read-create 881 STATUS current 882 DESCRIPTION 883 "The row status variable, used according to 884 row installation and removal conventions." 885 ::= { ipFrrAltEntry 12 } 887 -- the IP FRR No Alternate MIB-Group 888 -- 889 -- The ipFrrNoAltTable extends the inetCidrRouteTable 890 -- to indicate which routes are unprotected and the reason 891 -- why. The indices do not include the primary next-hop because 892 -- the lack of protection is for the route. This allows easy 893 -- access to the set of unprotected routes that would be 894 -- affected by a local failure of their primary next-hop. 896 ipFrrNoAltTable OBJECT-TYPE 897 SYNTAX SEQUENCE OF IpFrrNoAltEntry 898 MAX-ACCESS not-accessible 899 STATUS current 900 DESCRIPTION 901 "This entity's IP Fast Reroute Unprotected Routes 902 table." 903 ::= { ipFrrMIBObjects 3 } 905 ipFrrNoAltEntry OBJECT-TYPE 906 SYNTAX IpFrrNoAltEntry 907 MAX-ACCESS not-accessible 908 STATUS current 909 DESCRIPTION 910 "An entry containing the reason why a route does not 911 have an alternate next-hop. The existence of an 912 entry for a route indicates that there is no 913 alternate next-hop." 914 INDEX { inetCidrRouteDestType, 915 inetCidrRouteDest, 916 inetCidrRoutePfxLen 917 } 918 ::= { ipFrrNoAltTable 1 } 920 IpFrrNoAltEntry ::= SEQUENCE { 921 ipFrrNoAltCause INTEGER 922 } 924 ipFrrNoAltCause OBJECT-TYPE 925 SYNTAX INTEGER { 926 ipFrrUnavailable (1), -- No valid alternate(s) 927 localAddress (2), -- local/internal address 928 ipFrrDisabled (3), -- Protection not enabled 929 other (4) -- unknown or other cause 930 } 931 MAX-ACCESS read-only 932 STATUS current 933 DESCRIPTION 934 "For valid routes without an alternate next-hop, this 935 object enumerates the reason why no protection is 936 available. The possibilities are as follows. 938 ipFrrUnavailable : The supported IP Fast-Reroute 939 mechanisms could not find a safe 940 alternate next-hop. 942 localAddress : The route represents a local address. 943 This system is the destination so no 944 alternate path is possible or necessary. 946 ipFrrDisabled : Finding of alternate next-hops is 947 operationally disabled. 949 other : The reason is unknown or different from those 950 specifically enumerated possible causes." 951 ::= { ipFrrNoAltEntry 1 } 953 -- conformance information 955 ipFrrMIBConformance 956 OBJECT IDENTIFIER ::= { ipFrrMIB 2 } 958 ipFrrMIBCompliances 959 OBJECT IDENTIFIER ::= { ipFrrMIBConformance 1 } 961 ipFrrMIBGroups 962 OBJECT IDENTIFIER ::= { ipFrrMIBConformance 2 } 964 -- compliance statements 966 ipFrrMIBCompliance MODULE-COMPLIANCE 967 STATUS deprecated 968 DESCRIPTION 969 "Minimum requirements to state conformity 970 to this MIB. Supporting only IP v4 addresses 971 This is deprecated in favor of 972 ipFrrMIBInetCompliance 974 There are a number of INDEX objects that cannot be 975 represented in the form of OBJECT clauses in SMIv2, 976 but for which there are compliance requirements, 977 expressed in OBJECT clause form in this description: 979 OBJECT inetCidrRouteDestType 980 SYNTAX InetAddressType { ipv4(1), ipv4z(3) } 981 MIN-ACCESS read-only 982 DESCRIPTION 983 A (deprecated) complying implementation at this 984 level is required to support IPv4 addresses only. 985 This compliance level is defined so an 986 implementation only needs to support the addresses 987 it actually supports on the device. 989 OBJECT inetCidrRouteNextHopType 990 SYNTAX InetAddressType { ipv4(1), ipv4z(3) } 991 MIN-ACCESS read-only 993 DESCRIPTION 994 A (deprecated) complying implementation at this 995 level is required to support IPv4 addresses only. 996 This compliance level is defined so an 997 implementation only needs to support the addresses 998 it actually supports on the device. 1000 OBJECT ipFrrAltNextHopType 1001 SYNTAX InetAddressType { ipv4(1), ipv4z(3) } 1002 MIN-ACCESS read-only 1003 DESCRIPTION 1004 A (deprecated) complying implementation at this 1005 level is required to support IPv4 addresses only. 1006 This compliance level is defined so an 1007 implementation only needs to support the 1008 addresses it actually supports on the device. 1009 " 1010 MODULE -- this module 1011 MANDATORY-GROUPS { ipFrrBasicGroup } 1013 ::= { ipFrrMIBCompliances 1 } 1015 ipFrrMIBInetCompliance MODULE-COMPLIANCE 1016 STATUS current 1017 DESCRIPTION 1018 "Full conformity to this MIB." 1019 MODULE -- this module 1020 MANDATORY-GROUPS { ipFrrBasicGroup } 1022 OBJECT ipFrrAltStatus 1023 SYNTAX INTEGER { active(1) } 1024 WRITE-SYNTAX INTEGER { createAndGo(4), destroy(6) } 1025 DESCRIPTION 1026 "Support for createAndWait and notInService is not 1027 required." 1029 ::= { ipFrrMIBCompliances 2 } 1031 ipFrrReadOnlyCompliance MODULE-COMPLIANCE 1032 STATUS current 1033 DESCRIPTION 1035 "When this MIB is implemented without support for 1036 read-create (i.e. in read-only mode), then that 1037 implementation can claim read-only compliance. In that 1038 case, ipFrrAlt group can be monitored but cannot be 1039 configured with this MIB." 1041 MODULE 1042 MANDATORY-GROUPS { ipFrrBasicGroup } 1044 OBJECT ipFrrAltIfIndex 1045 MIN-ACCESS read-only 1046 DESCRIPTION 1047 "Write access is not required." 1049 OBJECT ipFrrAltType 1050 MIN-ACCESS read-only 1051 DESCRIPTION 1052 "Write access is not required." 1054 OBJECT ipFrrAltProtectionAvailable 1055 MIN-ACCESS read-only 1056 DESCRIPTION 1057 "Write access is not required." 1059 OBJECT ipFrrAltMetric1 1060 MIN-ACCESS read-only 1061 DESCRIPTION 1062 "Write access is not required." 1064 OBJECT ipFrrAltStatus 1065 MIN-ACCESS read-only 1066 DESCRIPTION 1067 "Write access is not required." 1069 ::= { ipFrrMIBCompliances 3 } 1071 -- units of conformance 1072 ipFrrBasicGroup OBJECT-GROUP 1073 OBJECTS {ipFrrTotalRoutes, 1074 ipFrrUnprotectedRoutes, 1075 ipFrrProtectedRoutes, 1076 ipFrrLinkProtectedRoutes, 1077 ipFrrNodeProtectedRoutes, 1078 ipv6FrrTotalRoutes, 1079 ipv6FrrUnprotectedRoutes, 1080 ipv6FrrProtectedRoutes, 1081 ipv6FrrLinkProtectedRoutes, 1082 ipv6FrrNodeProtectedRoutes, 1083 ipFrrAltIfIndex, 1084 ipFrrAltType, 1085 ipFrrAltProtectionAvailable, 1086 ipFrrAltMetric1, 1087 ipFrrAltMetric2, 1088 ipFrrAltMetric3, 1089 ipFrrAltNonBestReason, 1090 ipFrrAltBest, 1091 ipFrrAltStatus, 1092 ipFrrNoAltCause, 1093 ipFrrInstanceAlgorithm, 1094 ipFrrInstanceProtocol, 1095 ipFrrInstancePerPrefixComputation, 1096 ipFrrInstanceRowStatus, 1097 ipFrrIfCandidate, 1098 ipFrrIfProtectionType, 1099 ipFrrIfRowStatus, 1100 ipFrrStatsTotalRoutes, 1101 ipFrrStatsUnprotectedRoutes, 1102 ipFrrStatsProtectedRoutes, 1103 ipFrrStatsLinkProtectedRoutes, 1104 ipFrrStatsNodeProtectedRoutes, 1105 ipv6FrrStatsTotalRoutes, 1106 ipv6FrrStatsUnprotectedRoutes, 1107 ipv6FrrStatsProtectedRoutes, 1108 ipv6FrrStatsLinkProtectedRoutes, 1109 ipv6FrrStatsNodeProtectedRoutes 1111 } 1112 STATUS current 1113 DESCRIPTION 1114 "The entire collection of objects defined in 1115 this MIB for management of IP Fast Reroute ." 1116 ::= { ipFrrMIBGroups 1 } 1118 END 1120 4. Security Considerations 1122 There are a number of management objects defined in this MIB module 1123 with a MAX-ACCESS clause of read-write and/or read-create. Such 1124 objects may be considered sensitive or vulnerable in some network 1125 environments. The support for SET operations in a non-secure 1126 environment without proper protection can have a negative effect on 1127 network operations. The ipFrrAltTable contains routing and 1128 forwarding information that is critical to the operation of the 1129 network in the event of a local failure. Allowing unauthenticated 1130 write access to this table can compromise the validity of the 1131 alternate forwarding information. 1133 Some of the readable objects in this MIB module (i.e. objects with a 1134 MAX-ACCESS other than not-accessible) may be considered sensitive or 1135 vulnerable in some network environments. It is thus important to 1136 control even GET access to these objects and possibly to even encrypt 1137 the values of these objects when sending them over the network via 1138 SNMP. 1140 SNMP versions prior to SNMPv3 did not include adequate security. 1141 Even if the network itself is secure (for example by using IPSec), 1142 even then, there is no control as to who on the secure network is 1143 allowed to access and GET the objects in this MIB module. 1145 It is RECOMMENDED that implementers consider the security features as 1146 provided by the SNMPv3 framework (see [RFC3410], section 8), 1147 including full support for the SNMPv3 cryptographic mechanisms (for 1148 authentication and privacy). 1150 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1151 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1152 enable cryptographic security. It is then a customer/operator 1153 responsibility to ensure that the SNMP entity giving access to an 1154 instance of this MIB module is properly configured to give access to 1155 the objects only to those principals (users) that have legitimate 1156 rights to indeed GET them. 1158 5. Acknowledgements 1160 The authors would like to acknowledge contributions made by Bill 1161 Anderson, Don Fedyk and Bruno Decraene. 1163 6. IANA Considerations 1165 The MIB module in this document uses the following IANA-assigned 1166 OBJECT IDENTIFIER value recorded in the SMI Numbers registry. 1168 The IANA is requested to assign { ip ZZZ } to the IPFRR-MIB MIB 1169 module specified in this document. 1171 Editor's Note (to be removed prior to publication): the IANA is 1172 requested to assign a value for "ZZZ" under the ip subtree and to 1173 record the assignments in the SMI Numbers registry. When the 1174 assignments have been made, the RFC Editor is asked to replace "ZZZ" 1175 (here and in the MIB modules) with the assigned value and to remove 1176 this note. 1178 7. References 1179 7.1. Normative References 1181 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1182 Requirement Levels", BCP 14, RFC 2119, March 1997. 1184 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1185 MIB", RFC 2863, June 2000. 1187 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 1188 Schoenwaelder, "Textual Conventions for Internet Network 1189 Addresses", RFC 4001, February 2005. 1191 [RFC4292] Haberman, B., "IP Forwarding Table MIB", RFC 4292, April 1192 2006. 1194 [RFC4293] Routhier, S., "Management Information Base for the 1195 Internet Protocol (IP)", RFC 4293, April 2006. 1197 [RFC5286] Atlas, A. and A. Zinin, "Basic Specification for IP Fast 1198 Reroute: Loop-Free Alternates", RFC 5286, September 2008. 1200 7.2. Informative References 1202 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1203 Schoenwaelder, Ed., "Structure of Management Information 1204 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1206 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1207 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 1208 58, RFC 2579, April 1999. 1210 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1211 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1212 April 1999. 1214 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1215 "Introduction and Applicability Statements for Internet- 1216 Standard Management Framework", RFC 3410, December 2002. 1218 [RFC5036] Andersson, L., Minei, I., and B. Thomas, "LDP 1219 Specification", RFC 5036, October 2007. 1221 [RFC5714] Shand, M. and S. Bryant, "IP Fast Reroute Framework", RFC 1222 5714, January 2010. 1224 Authors' Addresses 1226 Alia Atlas 1227 Juniper Networks 1229 Email: akatlas@juniper.net 1231 A S Kiran Koushik 1232 Cisco Systems 1234 Email: kkoushik@cisco.com 1236 John Flick 1237 Hewlett-Packard 1239 Email: john.flick@hp.com 1241 Stephane Litkowski 1242 Orange 1244 Email: stephane.litkowski@orange.com