idnits 2.17.1 draft-ietf-bfd-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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document 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 (May 30, 2014) is 3611 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group T. Nadeau 3 Internet-Draft Brocade 4 Intended status: Standards Track Z. Ali 5 Expires: November 10, 2014 N. Akiya 6 Cisco Systems 7 May 30, 2014 9 BFD Management Information Base 10 draft-ietf-bfd-mib-21 12 Abstract 14 This draft defines a portion of the Management Information Base (MIB) 15 for use with network management protocols in the Internet community. 16 In particular, it describes managed objects for modeling 17 Bidirectional Forwarding Detection (BFD) protocol. 19 Requirements Language 21 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 22 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 23 "OPTIONAL" in this document are to be interpreted as described in BCP 24 14, RFC 2119 [RFC2119]. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on November 10, 2014. 43 Copyright Notice 45 Copyright (c) 2014 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 BFD-STD-MIB May 30, 2014 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 2. The Internet-Standard Management Framework . . . . . . . . . 3 64 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 65 4. Brief Description of MIB Objects . . . . . . . . . . . . . . 3 66 4.1. General Variables . . . . . . . . . . . . . . . . . . . . 3 67 4.2. Session Table (bfdSessionTable) . . . . . . . . . . . . . 3 68 4.3. Session Performance Table (bfdSessionPerfTable) . . . . . 3 69 4.4. BFD Session Discriminator Mapping Table 70 (bfdSessDiscMapTable) . . . . . . . . . . . . . . . . . . 4 71 4.5. BFD Session IP Mapping Table (bfdSessIpMapTable) . . . . 4 72 5. BFD MIB Module Definitions . . . . . . . . . . . . . . . . . 4 73 6. Security Considerations . . . . . . . . . . . . . . . . . . . 34 74 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36 75 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 37 76 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 37 77 9.1. Normative References . . . . . . . . . . . . . . . . . . 37 78 9.2. Informative References . . . . . . . . . . . . . . . . . 38 80 1. Introduction 82 This memo defines a portion of the Management Information Base (MIB) 83 for use with network management protocols in the Internet community. 84 In particular, it describes managed objects to configure and/or 85 monitor Bidirectional Forwarding Detection for [RFC5880], [RFC5881], 86 [RFC5883] and [RFC7130], BFD versions 0 and/or 1, on devices 87 supporting this feature. 89 This memo does not define a compliance requirement for a system that 90 only implements BFD version 0. This is a reflection of a considered 91 and deliberate decision by the BFD WG, because the BFD version 0 92 protocol is primarily of historical interest by comparison to the 93 widespread deployment of the BFD version 1 protocol. 95 2. The Internet-Standard Management Framework 97 For a detailed overview of the documents that describe the current 98 BFD-STD-MIB May 30, 2014 100 Internet-Standard Management Framework, please refer to section 7 of 101 RFC 3410 [RFC3410]. 103 Managed objects are accessed via a virtual information store, termed 104 the Management Information Base or MIB. MIB objects are generally 105 accessed through the Simple Network Management Protocol (SNMP). 106 Objects in the MIB are defined using the mechanisms defined in the 107 Structure of Management Information (SMI). This memo specifies a MIB 108 module that is compliant to the SMIv2, which is described in STD 58, 109 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 110 [RFC2580]. 112 As with all MIB modules, an attempt to SET or CREATE an object to a 113 value that is not supported by the implementation will result in a 114 failure using a return code that indicates that the value is not 115 supported. 117 3. Terminology 119 This document adopts the definitions, acronyms and mechanisms 120 described in [RFC5880], [RFC5881], [RFC5883] and [RFC7130]. Unless 121 otherwise stated, the mechanisms described therein will not be re- 122 described here. 124 4. Brief Description of MIB Objects 126 This section describes objects pertaining to BFD. The MIB objects 127 are derived from [RFC5880], [RFC5881], [RFC5883] and [RFC7130], and 128 also include textual conventions defined in [I-D.ietf-bfd-tc-mib]. 130 4.1. General Variables 132 The General Variables are used to identify parameters that are global 133 to the BFD process. 135 4.2. Session Table (bfdSessionTable) 137 The session table is used to identify a BFD session between a pair of 138 nodes. 140 4.3. Session Performance Table (bfdSessionPerfTable) 142 The session performance table is used for collecting BFD performance 143 counters on a per session basis. This table is an AUGMENT to the 144 bfdSessionTable. 146 4.4. BFD Session Discriminator Mapping Table (bfdSessDiscMapTable) 147 BFD-STD-MIB May 30, 2014 149 The BFD Session Discriminator Mapping Table provides a mapping 150 between a local discriminator value to the associated BFD session 151 found in the bfdSessionTable. 153 4.5. BFD Session IP Mapping Table (bfdSessIpMapTable) 155 The BFD Session IP Mapping Table maps, given bfdSessInterface, 156 bfdSessSrcAddrType, bfdSessSrcAddr, bfdSessDstAddrType, and 157 bfdSessDstAddr, to an associated BFD session found in the 158 bfdSessionTable. This table SHOULD contain those BFD sessions that 159 are of type IP. 161 5. BFD MIB Module Definitions 163 This MIB module makes references to the following documents. 164 [RFC2578], [RFC2579], [RFC2580], [RFC2863], [RFC3289], [RFC3413], 165 [RFC5082] and [RFC5880]. 167 BFD-STD-MIB DEFINITIONS ::= BEGIN 169 IMPORTS 170 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 171 mib-2, Integer32, Unsigned32, Counter32, Counter64 172 FROM SNMPv2-SMI -- [RFC2578] 174 TruthValue, RowStatus, StorageType, TimeStamp 175 FROM SNMPv2-TC -- [RFC2579] 177 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 178 FROM SNMPv2-CONF -- [RFC2580] 180 InterfaceIndexOrZero 181 FROM IF-MIB -- [RFC2863] 183 InetAddress, InetAddressType, InetPortNumber 184 FROM INET-ADDRESS-MIB 186 IndexIntegerNextFree 187 FROM DIFFSERV-MIB -- [RFC3289] 189 BfdSessIndexTC, BfdIntervalTC, BfdMultiplierTC, 190 BfdCtrlDestPortNumberTC, BfdCtrlSourcePortNumberTC 191 FROM BFD-TC-STD-MIB 193 IANAbfdDiagTC, IANAbfdSessTypeTC, IANAbfdSessOperModeTC, 194 IANAbfdSessStateTC, IANAbfdSessAuthenticationTypeTC, 195 IANAbfdSessAuthenticationKeyTC 196 BFD-STD-MIB May 30, 2014 198 FROM IANA-BFD-TC-STD-MIB; 200 bfdMIB MODULE-IDENTITY 201 LAST-UPDATED "201405091200Z" -- 9 May 2014 12:00:00 EST 202 ORGANIZATION "IETF Bidirectional Forwarding Detection 203 Working Group" 204 CONTACT-INFO 205 "Thomas D. Nadeau 206 Brocade 207 Email: tnadeau@lucidvision.com 209 Zafar Ali 210 Cisco Systems, Inc. 211 Email: zali@cisco.com 213 Nobo Akiya 214 Cisco Systems, Inc. 215 Email: nobo@cisco.com 217 Comments about this document should be emailed directly 218 to the BFD working group mailing list at 219 rtg-bfd@ietf.org" 220 DESCRIPTION 221 "Bidirectional Forwarding Management Information Base." 222 REVISION "201405091200Z" -- 9 May 2014 12:00:00 EST 223 DESCRIPTION 224 "Initial version. Published as RFC xxxx." 225 -- RFC Ed.: RFC-editor pls fill in xxxx 226 ::= { mib-2 XXX } 227 -- RFC Ed.: assigned by IANA, see section 7.1 for details 229 -- Top level components of this MIB module. 231 bfdNotifications OBJECT IDENTIFIER ::= { bfdMIB 0 } 233 bfdObjects OBJECT IDENTIFIER ::= { bfdMIB 1 } 235 bfdConformance OBJECT IDENTIFIER ::= { bfdMIB 2 } 237 bfdScalarObjects OBJECT IDENTIFIER ::= { bfdObjects 1 } 239 -- BFD General Variables 241 -- These parameters apply globally to the Systems' 242 -- BFD Process. 244 bfdAdminStatus OBJECT-TYPE 245 SYNTAX INTEGER { 246 BFD-STD-MIB May 30, 2014 248 enabled(1), 249 disabled(2), 250 adminDown(3), 251 down(4) 252 } 253 MAX-ACCESS read-write 254 STATUS current 255 DESCRIPTION 256 "The desired global administrative status of the BFD 257 system in this device." 258 ::= { bfdScalarObjects 1 } 260 bfdOperStatus OBJECT-TYPE 261 SYNTAX INTEGER { 262 up(1), 263 down(2), 264 adminDown(3) 265 } 266 MAX-ACCESS read-only 267 STATUS current 268 DESCRIPTION 269 "Indicates the actual operational status of the 270 BFD system in this device. When this value is 271 down(2), all entries in the bfdSessTable MUST have 272 their bfdSessOperStatus as down(2) as well. When 273 this value is adminDown(3), all entries in the 274 bfdSessTable MUST have their bfdSessOperStatus 275 as adminDown(3) as well." 276 ::= { bfdScalarObjects 2 } 278 bfdNotificationsEnable OBJECT-TYPE 279 SYNTAX TruthValue 280 MAX-ACCESS read-write 281 STATUS current 282 DESCRIPTION 283 "If this object is set to true(1), then it enables 284 the emission of bfdSessUp and bfdSessDown 285 notifications; otherwise these notifications are not 286 emitted." 287 REFERENCE 288 "See also RFC3413 for explanation that 289 notifications are under the ultimate control of the 290 MIB modules in this document." 291 DEFVAL { false } 292 ::= { bfdScalarObjects 3 } 294 bfdSessIndexNext OBJECT-TYPE 295 SYNTAX IndexIntegerNextFree (0..4294967295) 296 BFD-STD-MIB May 30, 2014 298 MAX-ACCESS read-only 299 STATUS current 300 DESCRIPTION 301 "This object contains an unused value for 302 bfdSessIndex that can be used when creating 303 entries in the table. A zero indicates that 304 no entries are available, but MUST NOT be used 305 as a valid index. " 306 ::= { bfdScalarObjects 4 } 308 -- BFD Session Table 309 -- The BFD Session Table specifies BFD session specific 310 -- information. 312 bfdSessTable OBJECT-TYPE 313 SYNTAX SEQUENCE OF BfdSessEntry 314 MAX-ACCESS not-accessible 315 STATUS current 316 DESCRIPTION 317 "The BFD Session Table describes the BFD sessions." 318 REFERENCE 319 "Katz, D. and D. Ward, Bidirectional Forwarding 320 Detection (BFD), RFC 5880, June 2012." 321 ::= { bfdObjects 2 } 323 bfdSessEntry OBJECT-TYPE 324 SYNTAX BfdSessEntry 325 MAX-ACCESS not-accessible 326 STATUS current 327 DESCRIPTION 328 "The BFD Session Entry describes BFD session." 329 INDEX { bfdSessIndex } 330 ::= { bfdSessTable 1 } 332 BfdSessEntry ::= SEQUENCE { 333 bfdSessIndex BfdSessIndexTC, 334 bfdSessVersionNumber Unsigned32, 335 bfdSessType IANAbfdSessTypeTC, 336 bfdSessDiscriminator Unsigned32, 337 bfdSessRemoteDiscr Unsigned32, 338 bfdSessDestinationUdpPort BfdCtrlDestPortNumberTC, 339 bfdSessSourceUdpPort BfdCtrlSourcePortNumberTC, 340 bfdSessEchoSourceUdpPort InetPortNumber, 341 bfdSessAdminStatus INTEGER, 342 bfdSessOperStatus INTEGER, 343 bfdSessState IANAbfdSessStateTC, 344 bfdSessRemoteHeardFlag TruthValue, 345 bfdSessDiag IANAbfdDiagTC, 346 BFD-STD-MIB May 30, 2014 348 bfdSessOperMode IANAbfdSessOperModeTC, 349 bfdSessDemandModeDesiredFlag TruthValue, 350 bfdSessControlPlaneIndepFlag TruthValue, 351 bfdSessMultipointFlag TruthValue, 352 bfdSessInterface InterfaceIndexOrZero, 353 bfdSessSrcAddrType InetAddressType, 354 bfdSessSrcAddr InetAddress, 355 bfdSessDstAddrType InetAddressType, 356 bfdSessDstAddr InetAddress, 357 bfdSessGTSM TruthValue, 358 bfdSessGTSMTTL Unsigned32, 359 bfdSessDesiredMinTxInterval BfdIntervalTC, 360 bfdSessReqMinRxInterval BfdIntervalTC, 361 bfdSessReqMinEchoRxInterval BfdIntervalTC, 362 bfdSessDetectMult BfdMultiplierTC, 363 bfdSessNegotiatedInterval BfdIntervalTC, 364 bfdSessNegotiatedEchoInterval BfdIntervalTC, 365 bfdSessNegotiatedDetectMult BfdMultiplierTC, 366 bfdSessAuthPresFlag TruthValue, 367 bfdSessAuthenticationType IANAbfdSessAuthenticationTypeTC, 368 bfdSessAuthenticationKeyID Integer32, 369 bfdSessAuthenticationKey IANAbfdSessAuthenticationKeyTC, 370 bfdSessStorageType StorageType, 371 bfdSessRowStatus RowStatus 372 } 374 bfdSessIndex OBJECT-TYPE 375 SYNTAX BfdSessIndexTC 376 MAX-ACCESS not-accessible 377 STATUS current 378 DESCRIPTION 379 "This object contains an index used to represent a 380 unique BFD session on this device. Managers 381 should obtain new values for row creation in this 382 table by reading bfdSessIndexNext." 383 ::= { bfdSessEntry 1 } 385 bfdSessVersionNumber OBJECT-TYPE 386 SYNTAX Unsigned32 (0..7) 387 MAX-ACCESS read-create 388 STATUS current 389 DESCRIPTION 390 "The version number of the BFD protocol that this session 391 is running in. Write access is available for this object 392 to provide ability to set desired version for this 393 BFD session." 395 REFERENCE 396 BFD-STD-MIB May 30, 2014 398 "Katz, D. and D. Ward, Bidirectional Forwarding 399 Detection (BFD), RFC 5880, June 2012." 400 DEFVAL { 1 } 401 ::= { bfdSessEntry 2 } 403 bfdSessType OBJECT-TYPE 404 SYNTAX IANAbfdSessTypeTC 405 MAX-ACCESS read-create 406 STATUS current 407 DESCRIPTION 408 "This object specifies the type of this BFD session." 409 ::= { bfdSessEntry 3 } 411 bfdSessDiscriminator OBJECT-TYPE 412 SYNTAX Unsigned32 (1..4294967295) 413 MAX-ACCESS read-create 414 STATUS current 415 DESCRIPTION 416 "This object specifies the local discriminator for this BFD 417 session, used to uniquely identify it." 418 ::= { bfdSessEntry 4 } 420 bfdSessRemoteDiscr OBJECT-TYPE 421 SYNTAX Unsigned32 (0 | 1..4294967295) 422 MAX-ACCESS read-only 423 STATUS current 424 DESCRIPTION 425 "This object specifies the session discriminator chosen 426 by the remote system for this BFD session. The value may 427 be zero(0) if the remote discriminator is not yet known 428 or if the session is in the down or adminDown(1) state." 429 REFERENCE 430 "Section 6.8.6, from Katz, D. and D. Ward, Bidirectional 431 Forwarding Detection (BFD), RFC 5880, June 2012." 432 ::= { bfdSessEntry 5 } 434 bfdSessDestinationUdpPort OBJECT-TYPE 435 SYNTAX BfdCtrlDestPortNumberTC 436 MAX-ACCESS read-create 437 STATUS current 438 DESCRIPTION 439 "This object specifies the destination UDP port number 440 used for this BFD session's control packets. The value 441 may be zero(0) if the session is in adminDown(1) state." 442 DEFVAL { 0 } 443 ::= { bfdSessEntry 6 } 445 bfdSessSourceUdpPort OBJECT-TYPE 446 BFD-STD-MIB May 30, 2014 448 SYNTAX BfdCtrlSourcePortNumberTC 449 MAX-ACCESS read-create 450 STATUS current 451 DESCRIPTION 452 "This object specifies the source UDP port number used 453 for this BFD session's control packets. The value may be 454 zero(0) if the session is in adminDown(1) state. Upon 455 creation of a new BFD session via this MIB, the value of 456 zero(0) specified would permit the implementation to 457 choose its own source port number." 458 DEFVAL { 0 } 459 ::= { bfdSessEntry 7 } 461 bfdSessEchoSourceUdpPort OBJECT-TYPE 462 SYNTAX InetPortNumber 463 MAX-ACCESS read-create 464 STATUS current 465 DESCRIPTION 466 "This object specifies the source UDP port number used for 467 this BFD session's echo packets. The value may be zero(0) 468 if the session is not running in the echo mode, or the 469 session is in adminDown(1) state. Upon creation of a new 470 BFD session via this MIB, the value of zero(0) would 471 permit the implementation to choose its own source port 472 number." 473 DEFVAL { 0 } 474 ::= { bfdSessEntry 8 } 476 bfdSessAdminStatus OBJECT-TYPE 477 SYNTAX INTEGER { 478 enabled(1), 479 disabled(2), 480 adminDown(3), 481 down(4) 482 } 483 MAX-ACCESS read-create 484 STATUS current 485 DESCRIPTION 486 "Denotes the desired operational status of the BFD Session. 488 A transition to enabled(1) will start the BFD state machine 489 for the session. The state machine will have an initial 490 state of down(2). 492 A transition to disabled(2) will stop the BFD state machine 493 for the session. The state machine may first transition to 494 adminDown(1) prior to stopping. 496 BFD-STD-MIB May 30, 2014 498 A transition to adminDown(3) will cause the BFD state 499 machine to transition to adminDown(1), and will cause the 500 session to remain in this state. 502 A transition to down(4) will cause the BFD state machine 503 to transition to down(2), and will cause the session to 504 remain in this state. 506 Care should be used in providing write access to this 507 object without adequate authentication." 508 ::= { bfdSessEntry 9 } 510 bfdSessOperStatus OBJECT-TYPE 511 SYNTAX INTEGER { 512 up(1), 513 down(2), 514 adminDown(3) 515 } 516 MAX-ACCESS read-only 517 STATUS current 518 DESCRIPTION 519 "Denotes the actual operational status of the BFD Session. 520 If the value of bfdOperStatus is down(2), this value MUST 521 eventually be down(2) as well. If the value of 522 bfdOperStatus is adminDown(3), this value MUST eventually 523 be adminDown(3) as well." 524 ::= { bfdSessEntry 10 } 526 bfdSessState OBJECT-TYPE 527 SYNTAX IANAbfdSessStateTC 528 MAX-ACCESS read-only 529 STATUS current 530 DESCRIPTION 531 "Configured BFD session state." 532 ::= { bfdSessEntry 11 } 534 bfdSessRemoteHeardFlag OBJECT-TYPE 535 SYNTAX TruthValue 536 MAX-ACCESS read-only 537 STATUS current 538 DESCRIPTION 539 "This object specifies status of BFD packet reception from 540 the remote system. Specifically, it is set to true(1) if 541 the local system is actively receiving BFD packets from the 542 remote system, and is set to false(2) if the local system 543 has not received BFD packets recently (within the detection 544 time) or if the local system is attempting to tear down 545 the BFD session." 546 BFD-STD-MIB May 30, 2014 548 REFERENCE 549 "Katz, D. and D. Ward, Bidirectional 550 Forwarding Detection (BFD), RFC 5880, June 2012." 551 ::= { bfdSessEntry 12 } 553 bfdSessDiag OBJECT-TYPE 554 SYNTAX IANAbfdDiagTC 555 MAX-ACCESS read-only 556 STATUS current 557 DESCRIPTION 558 "A diagnostic code specifying the local system's reason 559 for the last transition of the session from up(4) 560 to some other state." 561 ::= { bfdSessEntry 13 } 563 bfdSessOperMode OBJECT-TYPE 564 SYNTAX IANAbfdSessOperModeTC 565 MAX-ACCESS read-create 566 STATUS current 567 DESCRIPTION 568 "This object specifies the operational mode of this 569 BFD session." 570 ::= { bfdSessEntry 14 } 572 bfdSessDemandModeDesiredFlag OBJECT-TYPE 573 SYNTAX TruthValue 574 MAX-ACCESS read-create 575 STATUS current 576 DESCRIPTION 577 "This object indicates that the local system's 578 desire to use Demand mode. Specifically, it is set 579 to true(1) if the local system wishes to use 580 Demand mode or false(2) if not" 581 DEFVAL { false } 582 ::= { bfdSessEntry 15 } 584 bfdSessControlPlaneIndepFlag OBJECT-TYPE 585 SYNTAX TruthValue 586 MAX-ACCESS read-create 587 STATUS current 588 DESCRIPTION 589 "This object indicates that the local system's 590 ability to continue to function through a disruption of 591 the control plane. Specifically, it is set 592 to true(1) if the local system BFD implementation is 593 independent of the control plane. Otherwise, the 594 value is set to false(2)" 595 BFD-STD-MIB May 30, 2014 597 DEFVAL { false } 598 ::= { bfdSessEntry 16 } 600 bfdSessMultipointFlag OBJECT-TYPE 601 SYNTAX TruthValue 602 MAX-ACCESS read-create 603 STATUS current 604 DESCRIPTION 605 "This object indicates the Multipoint (M) bit for this 606 session. It is set to true(1) if Multipoint (M) bit is 607 set to 1. Otherwise, the value is set to false(2)" 608 DEFVAL { false } 609 ::= { bfdSessEntry 17 } 611 bfdSessInterface OBJECT-TYPE 612 SYNTAX InterfaceIndexOrZero 613 MAX-ACCESS read-create 614 STATUS current 615 DESCRIPTION 616 "This object contains an interface index used to indicate 617 the interface which this BFD session is running on. This 618 value can be zero if there is no interface associated 619 with this BFD session." 620 ::= { bfdSessEntry 18 } 622 bfdSessSrcAddrType OBJECT-TYPE 623 SYNTAX InetAddressType 624 MAX-ACCESS read-create 625 STATUS current 626 DESCRIPTION 627 "This object specifies IP address type of the source IP 628 address of this BFD session. The value of unknown(0) is 629 allowed only when the session is singleHop(1) and the 630 source IP address of this BFD session is derived from 631 the outgoing interface, or when the BFD session is not 632 associated with a specific interface. If any other 633 unsupported values are attempted in a set operation, the 634 agent MUST return an inconsistentValue error." 635 ::= { bfdSessEntry 19 } 637 bfdSessSrcAddr OBJECT-TYPE 638 SYNTAX InetAddress 639 MAX-ACCESS read-create 640 STATUS current 641 DESCRIPTION 642 "This object specifies the source IP address of this BFD 643 session. The format of this object is controlled by the 644 bfdSessSrcAddrType object." 645 BFD-STD-MIB May 30, 2014 647 ::= { bfdSessEntry 20 } 649 bfdSessDstAddrType OBJECT-TYPE 650 SYNTAX InetAddressType 651 MAX-ACCESS read-create 652 STATUS current 653 DESCRIPTION 654 "This object specifies IP address type of the neighboring IP 655 address which is being monitored with this BFD session. 656 The value of unknown(0) is allowed only when the session is 657 singleHop(1) and the outgoing interface is of type 658 point-to-point, or when the BFD session is not associated 659 with a specific interface. If any other unsupported values 660 are attempted in a set operation, the agent MUST return an 661 inconsistentValue error." 662 ::= { bfdSessEntry 21 } 664 bfdSessDstAddr OBJECT-TYPE 665 SYNTAX InetAddress 666 MAX-ACCESS read-create 667 STATUS current 668 DESCRIPTION 669 "This object specifies the neighboring IP address which is 670 being monitored with this BFD session. The format of this 671 object is controlled by the bfdSessDstAddrType object." 672 ::= { bfdSessEntry 22 } 674 bfdSessGTSM OBJECT-TYPE 675 SYNTAX TruthValue 676 MAX-ACCESS read-create 677 STATUS current 678 DESCRIPTION 679 "Setting the value of this object to false(2) will disable 680 GTSM protection of the BFD session. GTSM MUST be enabled 681 on a singleHop(1) session if no authentication is in use." 682 REFERENCE 683 "RFC5082, The Generalized TTL Security Mechanism (GTSM). 684 RFC5881, Section 5" 685 DEFVAL { true } 686 ::= { bfdSessEntry 23 } 688 bfdSessGTSMTTL OBJECT-TYPE 689 SYNTAX Unsigned32 (0..255) 690 MAX-ACCESS read-create 691 STATUS current 692 DESCRIPTION 693 "This object is valid only when bfdSessGTSM protection is 694 enabled on the system. This object indicates the minimum 695 BFD-STD-MIB May 30, 2014 697 allowed TTL for received BFD control packets. For a 698 singleHop(1) session, if GTSM protection is enabled, 699 this object SHOULD be set to maximum TTL value allowed 700 for single hop. 702 By default, GTSM is enabled and TTL value is 255. For a 703 multihop session, updating of maximum TTL value allowed 704 is likely required." 705 REFERENCE 706 "RFC5082, The Generalized TTL Security Mechanism (GTSM). 707 RFC5881, Section 5" 708 DEFVAL { 255 } 709 ::= { bfdSessEntry 24 } 711 bfdSessDesiredMinTxInterval OBJECT-TYPE 712 SYNTAX BfdIntervalTC 713 MAX-ACCESS read-create 714 STATUS current 715 DESCRIPTION 716 "This object specifies the minimum interval, in 717 microseconds, that the local system would like to use 718 when transmitting BFD Control packets. The value of 719 zero(0) is reserved in this case, and should not be 720 used." 721 REFERENCE 722 "Section 4.1 from Katz, D. and D. Ward, Bidirectional 723 Forwarding Detection (BFD), RFC 5880, June 2012." 724 ::= { bfdSessEntry 25 } 726 bfdSessReqMinRxInterval OBJECT-TYPE 727 SYNTAX BfdIntervalTC 728 MAX-ACCESS read-create 729 STATUS current 730 DESCRIPTION 731 "This object specifies the minimum interval, in 732 microseconds, between received BFD Control packets the 733 local system is capable of supporting. The value of 734 zero(0) can be specified when the transmitting system 735 does not want the remote system to send any periodic BFD 736 control packets." 737 REFERENCE 738 "Section 4.1 from Katz, D. and D. Ward, Bidirectional 739 Forwarding Detection (BFD), RFC 5880, June 2012." 740 ::= { bfdSessEntry 26 } 742 bfdSessReqMinEchoRxInterval OBJECT-TYPE 743 SYNTAX BfdIntervalTC 744 MAX-ACCESS read-create 745 BFD-STD-MIB May 30, 2014 747 STATUS current 748 DESCRIPTION 749 "This object specifies the minimum interval, in 750 microseconds, between received BFD Echo packets that this 751 system is capable of supporting. Value must be zero(0) if 752 this is a multihop BFD session." 753 ::= { bfdSessEntry 27 } 755 bfdSessDetectMult OBJECT-TYPE 756 SYNTAX BfdMultiplierTC 757 MAX-ACCESS read-create 758 STATUS current 759 DESCRIPTION 760 "This object specifies the Detect time multiplier." 761 ::= { bfdSessEntry 28 } 763 bfdSessNegotiatedInterval OBJECT-TYPE 764 SYNTAX BfdIntervalTC 765 MAX-ACCESS read-only 766 STATUS current 767 DESCRIPTION 768 "This object specifies the negotiated interval, in 769 microseconds, that the local system is transmitting 770 BFD Control packets." 771 ::= { bfdSessEntry 29 } 773 bfdSessNegotiatedEchoInterval OBJECT-TYPE 774 SYNTAX BfdIntervalTC 775 MAX-ACCESS read-only 776 STATUS current 777 DESCRIPTION 778 "This object specifies the negotiated interval, in 779 microseconds, that the local system is transmitting 780 BFD echo packets. Value is expected to be zero if 781 the sessions is not running in echo mode." 782 ::= { bfdSessEntry 30 } 784 bfdSessNegotiatedDetectMult OBJECT-TYPE 785 SYNTAX BfdMultiplierTC 786 MAX-ACCESS read-only 787 STATUS current 788 DESCRIPTION 789 "This object specifies the Detect time multiplier." 790 ::= { bfdSessEntry 31 } 792 bfdSessAuthPresFlag OBJECT-TYPE 793 SYNTAX TruthValue 794 MAX-ACCESS read-create 795 BFD-STD-MIB May 30, 2014 797 STATUS current 798 DESCRIPTION 799 "This object indicates that the local system's 800 desire to use Authentication. Specifically, it is set 801 to true(1) if the local system wishes the session 802 to be authenticated or false(2) if not." 803 REFERENCE 804 "Sections 4.2 - 4.4 from Katz, D. and D. Ward, 805 Bidirectional Forwarding Detection (BFD), RFC 5880, 806 June 2012." 807 DEFVAL { false } 808 ::= { bfdSessEntry 32 } 810 bfdSessAuthenticationType OBJECT-TYPE 811 SYNTAX IANAbfdSessAuthenticationTypeTC 812 MAX-ACCESS read-create 813 STATUS current 814 DESCRIPTION 815 "The Authentication Type used for this BFD session. 816 This field is valid only when the Authentication 817 Present bit is set. Max-access to this object as well as 818 other authentication related objects are set to 819 read-create in order to support management of a single 820 key ID at a time, key rotation is not handled. Key update 821 in practice must be done by atomic update using a set 822 containing all affected objects in the same varBindList 823 or otherwise risk the session dropping." 824 REFERENCE 825 "Sections 4.2 - 4.4 from Katz, D. and D. Ward, 826 Bidirectional Forwarding Detection (BFD), RFC 5880, 827 June 2012." 828 DEFVAL { noAuthentication } 829 ::= { bfdSessEntry 33 } 831 bfdSessAuthenticationKeyID OBJECT-TYPE 832 SYNTAX Integer32 (-1 | 0..255) 833 MAX-ACCESS read-create 834 STATUS current 835 DESCRIPTION 836 "The authentication key ID in use for this session. This 837 object permits multiple keys to be active simultaneously. 838 The value -1 indicates that no Authentication Key ID will 839 be present in the optional BFD Authentication Section." 840 REFERENCE 841 "Sections 4.2 - 4.4 from Katz, D. and D. Ward, 842 Bidirectional Forwarding Detection (BFD), RFC 5880, 843 June 2012." 844 DEFVAL { -1 } 845 BFD-STD-MIB May 30, 2014 847 ::= { bfdSessEntry 34 } 849 bfdSessAuthenticationKey OBJECT-TYPE 850 SYNTAX IANAbfdSessAuthenticationKeyTC 851 MAX-ACCESS read-create 852 STATUS current 853 DESCRIPTION 854 "The authentication key. When the 855 bfdSessAuthenticationType is simplePassword(1), the value 856 of this object is the password present in the BFD packets. 858 When the bfdSessAuthenticationType is one of the keyed 859 authentication types, this value is used in the 860 computation of the key present in the BFD authentication 861 packet." 862 REFERENCE 863 "Sections 4.2 - 4.4 from Katz, D. and D. Ward, 864 Bidirectional Forwarding Detection (BFD), RFC 5880, 865 June 2012." 866 ::= { bfdSessEntry 35 } 868 bfdSessStorageType OBJECT-TYPE 869 SYNTAX StorageType 870 MAX-ACCESS read-create 871 STATUS current 872 DESCRIPTION 873 "This variable indicates the storage type for this 874 object. Conceptual rows having the value 875 'permanent' need not allow write-access to any 876 columnar objects in the row." 877 ::= { bfdSessEntry 36 } 879 bfdSessRowStatus OBJECT-TYPE 880 SYNTAX RowStatus 881 MAX-ACCESS read-create 882 STATUS current 883 DESCRIPTION 884 "This variable is used to create, modify, and/or 885 delete a row in this table. When a row in this 886 table has a row in the active(1) state, no 887 objects in this row can be modified except the 888 bfdSessRowStatus and bfdSessStorageType." 889 ::= { bfdSessEntry 37 } 891 -- BFD Session Performance Table 893 bfdSessPerfTable OBJECT-TYPE 894 SYNTAX SEQUENCE OF BfdSessPerfEntry 895 BFD-STD-MIB May 30, 2014 897 MAX-ACCESS not-accessible 898 STATUS current 899 DESCRIPTION 900 "This table specifies BFD Session performance counters." 901 ::= { bfdObjects 3 } 903 bfdSessPerfEntry OBJECT-TYPE 904 SYNTAX BfdSessPerfEntry 905 MAX-ACCESS not-accessible 906 STATUS current 907 DESCRIPTION 908 "An entry in this table is created by a BFD-enabled node 909 for every BFD Session. bfdSessPerfDiscTime is used to 910 indicate potential discontinuity for all counter objects 911 in this table." 912 AUGMENTS { bfdSessEntry } 913 ::= { bfdSessPerfTable 1 } 915 BfdSessPerfEntry ::= SEQUENCE { 916 bfdSessPerfCtrlPktIn Counter32, 917 bfdSessPerfCtrlPktOut Counter32, 918 bfdSessPerfCtrlPktDrop Counter32, 919 bfdSessPerfCtrlPktDropLastTime TimeStamp, 920 bfdSessPerfEchoPktIn Counter32, 921 bfdSessPerfEchoPktOut Counter32, 922 bfdSessPerfEchoPktDrop Counter32, 923 bfdSessPerfEchoPktDropLastTime TimeStamp, 924 bfdSessUpTime TimeStamp, 925 bfdSessPerfLastSessDownTime TimeStamp, 926 bfdSessPerfLastCommLostDiag IANAbfdDiagTC, 927 bfdSessPerfSessUpCount Counter32, 928 bfdSessPerfDiscTime TimeStamp, 930 -- High Capacity Counters 931 bfdSessPerfCtrlPktInHC Counter64, 932 bfdSessPerfCtrlPktOutHC Counter64, 933 bfdSessPerfCtrlPktDropHC Counter64, 934 bfdSessPerfEchoPktInHC Counter64, 935 bfdSessPerfEchoPktOutHC Counter64, 936 bfdSessPerfEchoPktDropHC Counter64 937 } 939 bfdSessPerfCtrlPktIn OBJECT-TYPE 940 SYNTAX Counter32 941 MAX-ACCESS read-only 942 STATUS current 943 DESCRIPTION 944 "The total number of BFD control messages received for this 945 BFD-STD-MIB May 30, 2014 947 BFD session. 949 It MUST be equal to the least significant 32 bits of 950 bfdSessPerfCtrlPktInHC if supported, and MUST do so 951 with the rules spelled out in RFC 2863." 952 ::= { bfdSessPerfEntry 1 } 954 bfdSessPerfCtrlPktOut OBJECT-TYPE 955 SYNTAX Counter32 956 MAX-ACCESS read-only 957 STATUS current 958 DESCRIPTION 959 "The total number of BFD control messages sent for this BFD 960 session. 962 It MUST be equal to the least significant 32 bits of 963 bfdSessPerfCtrlPktOutHC if supported, and MUST do so 964 with the rules spelled out in RFC 2863." 965 ::= { bfdSessPerfEntry 2 } 967 bfdSessPerfCtrlPktDrop OBJECT-TYPE 968 SYNTAX Counter32 969 MAX-ACCESS read-only 970 STATUS current 971 DESCRIPTION 972 "The total number of BFD control messages received for this 973 session yet dropped for being invalid. 975 It MUST be equal to the least significant 32 bits of 976 bfdSessPerfCtrlPktDropHC if supported, and MUST do so 977 with the rules spelled out in RFC 2863." 978 ::= { bfdSessPerfEntry 3 } 980 bfdSessPerfCtrlPktDropLastTime OBJECT-TYPE 981 SYNTAX TimeStamp 982 MAX-ACCESS read-only 983 STATUS current 984 DESCRIPTION 985 "The value of sysUpTime on the most recent occasion at 986 which received BFD control message for this session was 987 dropped. If no such up event exists, this object contains 988 a zero value." 989 ::= { bfdSessPerfEntry 4 } 991 bfdSessPerfEchoPktIn OBJECT-TYPE 992 SYNTAX Counter32 993 MAX-ACCESS read-only 994 STATUS current 995 BFD-STD-MIB May 30, 2014 997 DESCRIPTION 998 "The total number of BFD echo messages received for this 999 BFD session. 1001 It MUST be equal to the least significant 32 bits of 1002 bfdSessPerfEchoPktInHC if supported, and MUST do so 1003 with the rules spelled out in RFC 2863." 1004 ::= { bfdSessPerfEntry 5 } 1006 bfdSessPerfEchoPktOut OBJECT-TYPE 1007 SYNTAX Counter32 1008 MAX-ACCESS read-only 1009 STATUS current 1010 DESCRIPTION 1011 "The total number of BFD echo messages sent for this BFD 1012 session. 1014 It MUST be equal to the least significant 32 bits of 1015 bfdSessPerfEchoPktOutHC if supported, and MUST do so 1016 with the rules spelled out in RFC 2863." 1017 ::= { bfdSessPerfEntry 6 } 1019 bfdSessPerfEchoPktDrop OBJECT-TYPE 1020 SYNTAX Counter32 1021 MAX-ACCESS read-only 1022 STATUS current 1023 DESCRIPTION 1024 "The total number of BFD echo messages received for this 1025 session yet dropped for being invalid. 1027 It MUST be equal to the least significant 32 bits of 1028 bfdSessPerfEchoPktDropHC if supported, and MUST do so 1029 with the rules spelled out in RFC 2863." 1030 ::= { bfdSessPerfEntry 7 } 1032 bfdSessPerfEchoPktDropLastTime OBJECT-TYPE 1033 SYNTAX TimeStamp 1034 MAX-ACCESS read-only 1035 STATUS current 1036 DESCRIPTION 1037 "The value of sysUpTime on the most recent occasion at 1038 which received BFD echo message for this session was 1039 dropped. If no such up event has been issued, this 1040 object contains a zero value." 1041 ::= { bfdSessPerfEntry 8 } 1043 bfdSessUpTime OBJECT-TYPE 1044 SYNTAX TimeStamp 1045 BFD-STD-MIB May 30, 2014 1047 MAX-ACCESS read-only 1048 STATUS current 1049 DESCRIPTION 1050 "The value of sysUpTime on the most recent occasion at which 1051 the session came up. If no such event has been issued, 1052 this object contains a zero value." 1053 ::= { bfdSessPerfEntry 9 } 1055 bfdSessPerfLastSessDownTime OBJECT-TYPE 1056 SYNTAX TimeStamp 1057 MAX-ACCESS read-only 1058 STATUS current 1059 DESCRIPTION 1060 "The value of sysUpTime on the most recent occasion at 1061 which the last time communication was lost with the 1062 neighbor. If no down event has been issued this object 1063 contains a zero value." 1064 ::= { bfdSessPerfEntry 10 } 1066 bfdSessPerfLastCommLostDiag OBJECT-TYPE 1067 SYNTAX IANAbfdDiagTC 1068 MAX-ACCESS read-only 1069 STATUS current 1070 DESCRIPTION 1071 "The BFD diag code for the last time communication was lost 1072 with the neighbor. If such an event has not been issued 1073 this object contains a zero value." 1074 ::= { bfdSessPerfEntry 11 } 1076 bfdSessPerfSessUpCount OBJECT-TYPE 1077 SYNTAX Counter32 1078 MAX-ACCESS read-only 1079 STATUS current 1080 DESCRIPTION 1081 "The number of times this session has gone into the Up 1082 state since the system last rebooted." 1083 ::= { bfdSessPerfEntry 12 } 1085 bfdSessPerfDiscTime OBJECT-TYPE 1086 SYNTAX TimeStamp 1087 MAX-ACCESS read-only 1088 STATUS current 1089 DESCRIPTION 1090 "The value of sysUpTime on the most recent occasion at 1091 which any one or more of the session counters suffered 1092 a discontinuity. 1094 The relevant counters are the specific instances associated 1095 BFD-STD-MIB May 30, 2014 1097 with this BFD session of any Counter32 object contained in 1098 the BfdSessPerfTable. If no such discontinuities have 1099 occurred since the last re-initialization of the local 1100 management subsystem, then this object contains a zero 1101 value." 1102 ::= { bfdSessPerfEntry 13 } 1104 bfdSessPerfCtrlPktInHC OBJECT-TYPE 1105 SYNTAX Counter64 1106 MAX-ACCESS read-only 1107 STATUS current 1108 DESCRIPTION 1109 "This value represents the total number of BFD control 1110 messages received for this BFD session. 1112 The least significant 32 bits MUST equal to 1113 bfdSessPerfCtrlPktIn, and MUST do so with 1114 the rules spelled out in RFC 2863." 1115 ::= { bfdSessPerfEntry 14 } 1117 bfdSessPerfCtrlPktOutHC OBJECT-TYPE 1118 SYNTAX Counter64 1119 MAX-ACCESS read-only 1120 STATUS current 1121 DESCRIPTION 1122 "This value represents the total number of BFD control 1123 messages transmitted for this BFD session. 1125 The least significant 32 bits MUST equal to 1126 bfdSessPerfCtrlPktOut, and MUST do so with 1127 the rules spelled out in RFC 2863." 1128 ::= { bfdSessPerfEntry 15 } 1130 bfdSessPerfCtrlPktDropHC OBJECT-TYPE 1131 SYNTAX Counter64 1132 MAX-ACCESS read-only 1133 STATUS current 1134 DESCRIPTION 1135 "This value represents the total number of BFD control 1136 messages received for this BFD session yet dropped for 1137 being invalid. 1139 The least significant 32 bits MUST equal to 1140 bfdSessPerfCtrlPktDrop, and MUST do so with 1141 the rules spelled out in RFC 2863." 1142 ::= { bfdSessPerfEntry 16 } 1144 bfdSessPerfEchoPktInHC OBJECT-TYPE 1145 BFD-STD-MIB May 30, 2014 1147 SYNTAX Counter64 1148 MAX-ACCESS read-only 1149 STATUS current 1150 DESCRIPTION 1151 "This value represents the total number of BFD echo 1152 messages received for this BFD session. 1154 The least significant 32 bits MUST equal to 1155 bfdSessPerfEchoPktIn, and MUST do so with 1156 the rules spelled out in RFC 2863." 1157 ::= { bfdSessPerfEntry 17 } 1159 bfdSessPerfEchoPktOutHC OBJECT-TYPE 1160 SYNTAX Counter64 1161 MAX-ACCESS read-only 1162 STATUS current 1163 DESCRIPTION 1164 "This value represents the total number of BFD echo 1165 messages transmitted for this BFD session. 1167 The least significant 32 bits MUST equal to 1168 bfdSessPerfEchoPktOut, and MUST do so with 1169 the rules spelled out in RFC 2863." 1170 ::= { bfdSessPerfEntry 18 } 1172 bfdSessPerfEchoPktDropHC OBJECT-TYPE 1173 SYNTAX Counter64 1174 MAX-ACCESS read-only 1175 STATUS current 1176 DESCRIPTION 1177 "This value represents the total number of BFD echo 1178 messages received for this BFD session yet dropped 1179 for being invalid. 1181 The least significant 32 bits MUST equal to 1182 bfdSessPerfEchoPktDrop, and MUST do so with 1183 the rules spelled out in RFC 2863." 1184 ::= { bfdSessPerfEntry 19 } 1186 -- BFD Session Discriminator Mapping Table 1188 bfdSessDiscMapTable OBJECT-TYPE 1189 SYNTAX SEQUENCE OF BfdSessDiscMapEntry 1190 MAX-ACCESS not-accessible 1191 STATUS current 1192 DESCRIPTION 1193 "The BFD Session Discriminator Mapping Table maps a 1194 local discriminator value to associated BFD session's 1195 BFD-STD-MIB May 30, 2014 1197 bfdSessIndex found in the bfdSessionTable." 1198 ::= { bfdObjects 4 } 1200 bfdSessDiscMapEntry OBJECT-TYPE 1201 SYNTAX BfdSessDiscMapEntry 1202 MAX-ACCESS not-accessible 1203 STATUS current 1204 DESCRIPTION 1205 "The BFD Session Discriminator Mapping Entry 1206 specifies a mapping between a local discriminator 1207 and a BFD session." 1208 INDEX { bfdSessDiscriminator } 1209 ::= { bfdSessDiscMapTable 1 } 1211 BfdSessDiscMapEntry ::= SEQUENCE { 1212 bfdSessDiscMapIndex BfdSessIndexTC 1213 } 1215 bfdSessDiscMapIndex OBJECT-TYPE 1216 SYNTAX BfdSessIndexTC 1217 MAX-ACCESS read-only 1218 STATUS current 1219 DESCRIPTION 1220 "This object specifies a mapping between a 1221 local discriminator and a BFD Session in 1222 the BfdSessTable." 1223 ::= { bfdSessDiscMapEntry 1 } 1225 -- BFD Session IP Mapping Table 1227 bfdSessIpMapTable OBJECT-TYPE 1228 SYNTAX SEQUENCE OF BfdSessIpMapEntry 1229 MAX-ACCESS not-accessible 1230 STATUS current 1231 DESCRIPTION 1232 "The BFD Session IP Mapping Table maps given 1233 bfdSessInterface, bfdSessSrcAddrType, bfdSessSrcAddr, 1234 bfdSessDstAddrType and bfdSessDstAddr 1235 to an associated BFD session found in the 1236 bfdSessionTable." 1237 ::= { bfdObjects 5 } 1239 bfdSessIpMapEntry OBJECT-TYPE 1240 SYNTAX BfdSessIpMapEntry 1241 MAX-ACCESS not-accessible 1242 STATUS current 1243 DESCRIPTION 1244 BFD-STD-MIB May 30, 2014 1246 "The BFD Session IP Map Entry contains a mapping 1247 from the IP information for a session, to the session 1248 in the bfdSessionTable." 1249 INDEX { 1250 bfdSessInterface, 1251 bfdSessSrcAddrType, 1252 bfdSessSrcAddr, 1253 bfdSessDstAddrType, 1254 bfdSessDstAddr 1255 } 1256 ::= { bfdSessIpMapTable 1 } 1258 BfdSessIpMapEntry ::= SEQUENCE { 1259 bfdSessIpMapIndex BfdSessIndexTC 1260 } 1262 bfdSessIpMapIndex OBJECT-TYPE 1263 SYNTAX BfdSessIndexTC 1264 MAX-ACCESS read-only 1265 STATUS current 1266 DESCRIPTION 1267 "This object specifies the BfdSessIndexTC referred 1268 to by the indexes of this row. In essence, a mapping is 1269 provided between these indexes and the BfdSessTable." 1270 ::= { bfdSessIpMapEntry 1 } 1272 -- Notification Configuration 1274 bfdSessUp NOTIFICATION-TYPE 1275 OBJECTS { 1276 bfdSessDiag, -- low range value 1277 bfdSessDiag -- high range value 1278 } 1279 STATUS current 1280 DESCRIPTION 1281 "This notification is generated when the 1282 bfdSessState object for one or more contiguous 1283 entries in bfdSessTable are about to enter the up(4) 1284 state from some other state. The included values of 1285 bfdSessDiag MUST both be set equal to this 1286 new state (i.e: up(4)). The two instances of 1287 bfdSessDiag in this notification indicate the range 1288 of indexes that are affected. Note that all the indexes 1289 of the two ends of the range can be derived from the 1290 instance identifiers of these two objects. For the 1291 cases where a contiguous range of sessions 1292 have transitioned into the up(4) state at roughly 1293 the same time, the device SHOULD issue a single 1294 BFD-STD-MIB May 30, 2014 1296 notification for each range of contiguous indexes in 1297 an effort to minimize the emission of a large number 1298 of notifications. If a notification has to be 1299 issued for just a single bfdSessEntry, then 1300 the instance identifier (and values) of the two 1301 bfdSessDiag objects MUST be the identical." 1302 ::= { bfdNotifications 1 } 1304 bfdSessDown NOTIFICATION-TYPE 1305 OBJECTS { 1306 bfdSessDiag, -- low range value 1307 bfdSessDiag -- high range value 1308 } 1309 STATUS current 1310 DESCRIPTION 1311 "This notification is generated when the 1312 bfdSessState object for one or more contiguous 1313 entries in bfdSessTable are about to enter the down(2) 1314 or adminDown(1) states from some other state. The included 1315 values of bfdSessDiag MUST both be set equal to this new 1316 state (i.e: down(2) or adminDown(1)). The two instances 1317 of bfdSessDiag in this notification indicate the range 1318 of indexes that are affected. Note that all the indexes 1319 of the two ends of the range can be derived from the 1320 instance identifiers of these two objects. For 1321 cases where a contiguous range of sessions 1322 have transitioned into the down(2) or adminDown(1) states 1323 at roughly the same time, the device SHOULD issue a single 1324 notification for each range of contiguous indexes in 1325 an effort to minimize the emission of a large number 1326 of notifications. If a notification has to be 1327 issued for just a single bfdSessEntry, then 1328 the instance identifier (and values) of the two 1329 bfdSessDiag objects MUST be the identical." 1330 ::= { bfdNotifications 2 } 1332 -- Module compliance. 1334 bfdGroups 1335 OBJECT IDENTIFIER ::= { bfdConformance 1 } 1337 bfdCompliances 1338 OBJECT IDENTIFIER ::= { bfdConformance 2 } 1340 -- Compliance requirement for fully compliant implementations. 1342 bfdModuleFullCompliance MODULE-COMPLIANCE 1343 STATUS current 1344 BFD-STD-MIB May 30, 2014 1346 DESCRIPTION 1347 "Compliance statement for agents that provide full 1348 support for the BFD-MIB module. Such devices can 1349 then be monitored and also be configured using 1350 this MIB module." 1352 MODULE -- This module. 1354 MANDATORY-GROUPS { 1355 bfdSessionGroup, 1356 bfdSessionReadOnlyGroup, 1357 bfdSessionPerfGroup, 1358 bfdNotificationGroup 1359 } 1361 GROUP bfdSessionPerfHCGroup 1362 DESCRIPTION "This group is mandatory for all systems that 1363 are able to support the Counter64 date type." 1365 OBJECT bfdSessSrcAddrType 1366 SYNTAX InetAddressType { unknown(0), ipv4(1), 1367 ipv6(2), ipv6z(4) } 1368 DESCRIPTION "Only unknown(0), ipv4(1), ipv6(2) and ipv6z(4) 1369 support are required. ipv4z(3) is not required 1370 and dns(16) is not allowed." 1372 OBJECT bfdSessSrcAddr 1373 SYNTAX InetAddress (SIZE (0|4|16|20)) 1374 DESCRIPTION "An implementation is only required to support 1375 unknown(0), ipv4(1), ipv6(2) and ipv6z(4) sizes." 1377 OBJECT bfdSessDstAddrType 1378 SYNTAX InetAddressType { unknown(0), ipv4(1), 1379 ipv6(2), ipv6z(4) } 1380 DESCRIPTION "Only unknown(0), ipv4(1), ipv6(2) and ipv6z(4) 1381 support are required. ipv4z(3) is not required 1382 and dns(16) is not allowed." 1384 OBJECT bfdSessDstAddr 1385 SYNTAX InetAddress (SIZE (0|4|16|20)) 1386 DESCRIPTION "An implementation is only required to support 1387 unknown(0), ipv4(1), ipv6(2) and ipv6z(4) sizes." 1389 OBJECT bfdSessRowStatus 1390 SYNTAX RowStatus { active(1), notInService(2) } 1391 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1392 createAndGo(4), destroy(6) } 1393 DESCRIPTION "Support for createAndWait and notReady is not 1394 BFD-STD-MIB May 30, 2014 1396 required." 1398 ::= { bfdCompliances 1 } 1400 bfdModuleReadOnlyCompliance MODULE-COMPLIANCE 1401 STATUS current 1402 DESCRIPTION 1403 "Compliance requirement for implementations that only 1404 provide read-only support for BFD-MIB. Such devices 1405 can then be monitored but cannot be configured using 1406 this MIB module." 1408 MODULE -- This module. 1410 MANDATORY-GROUPS { 1411 bfdSessionGroup, 1412 bfdSessionReadOnlyGroup, 1413 bfdSessionPerfGroup, 1414 bfdNotificationGroup 1415 } 1417 GROUP bfdSessionPerfHCGroup 1418 DESCRIPTION "This group is mandatory for all systems that 1419 are able to support the Counter64 date type." 1421 OBJECT bfdSessVersionNumber 1422 MIN-ACCESS read-only 1423 DESCRIPTION "Write access is not required." 1425 OBJECT bfdSessType 1426 MIN-ACCESS read-only 1427 DESCRIPTION "Write access is not required." 1429 OBJECT bfdSessDiscriminator 1430 MIN-ACCESS read-only 1431 DESCRIPTION "Write access is not required." 1433 OBJECT bfdSessDestinationUdpPort 1434 MIN-ACCESS read-only 1435 DESCRIPTION "Write access is not required." 1437 OBJECT bfdSessSourceUdpPort 1438 MIN-ACCESS read-only 1439 DESCRIPTION "Write access is not required." 1441 OBJECT bfdSessEchoSourceUdpPort 1442 MIN-ACCESS read-only 1443 DESCRIPTION "Write access is not required." 1444 BFD-STD-MIB May 30, 2014 1446 OBJECT bfdSessAdminStatus 1447 MIN-ACCESS read-only 1448 DESCRIPTION "Write access is not required." 1450 OBJECT bfdSessOperMode 1451 MIN-ACCESS read-only 1452 DESCRIPTION "Write access is not required." 1454 OBJECT bfdSessDemandModeDesiredFlag 1455 MIN-ACCESS read-only 1456 DESCRIPTION "Write access is not required." 1458 OBJECT bfdSessControlPlaneIndepFlag 1459 MIN-ACCESS read-only 1460 DESCRIPTION "Write access is not required." 1462 OBJECT bfdSessMultipointFlag 1463 MIN-ACCESS read-only 1464 DESCRIPTION "Write access is not required." 1466 OBJECT bfdSessInterface 1467 MIN-ACCESS read-only 1468 DESCRIPTION "Write access is not required." 1470 OBJECT bfdSessSrcAddrType 1471 SYNTAX InetAddressType { unknown(0), ipv4(1), 1472 ipv6(2), ipv6z(4) } 1473 MIN-ACCESS read-only 1474 DESCRIPTION "Only unknown(0), ipv4(1), ipv6(2) and ipv6z(4) 1475 support are required. ipv4z(3) is not required 1476 and dns(16) is not allowed." 1478 OBJECT bfdSessSrcAddr 1479 SYNTAX InetAddress (SIZE (0|4|16|20)) 1480 MIN-ACCESS read-only 1481 DESCRIPTION "An implementation is only required to support 1482 unknown(0), ipv4(1), ipv6(2) and ipv6z(4) sizes." 1484 OBJECT bfdSessDstAddrType 1485 SYNTAX InetAddressType { unknown(0), ipv4(1), 1486 ipv6(2), ipv6z(4) } 1487 MIN-ACCESS read-only 1488 DESCRIPTION "Only unknown(0), ipv4(1), ipv6(2) and ipv6z(4) 1489 support are required. ipv4z(3) is not required 1490 and dns(16) is not allowed." 1492 OBJECT bfdSessDstAddr 1493 BFD-STD-MIB May 30, 2014 1495 SYNTAX InetAddress (SIZE (0|4|16|20)) 1496 MIN-ACCESS read-only 1497 DESCRIPTION "An implementation is only required to support 1498 unknown(0), ipv4(1), ipv6(2) and ipv6z(4) sizes." 1500 OBJECT bfdSessGTSM 1501 MIN-ACCESS read-only 1502 DESCRIPTION "Write access is not required." 1504 OBJECT bfdSessGTSMTTL 1505 MIN-ACCESS read-only 1506 DESCRIPTION "Write access is not required." 1508 OBJECT bfdSessDesiredMinTxInterval 1509 MIN-ACCESS read-only 1510 DESCRIPTION "Write access is not required." 1512 OBJECT bfdSessReqMinRxInterval 1513 MIN-ACCESS read-only 1514 DESCRIPTION "Write access is not required." 1516 OBJECT bfdSessReqMinEchoRxInterval 1517 MIN-ACCESS read-only 1518 DESCRIPTION "Write access is not required." 1520 OBJECT bfdSessDetectMult 1521 MIN-ACCESS read-only 1522 DESCRIPTION "Write access is not required." 1524 OBJECT bfdSessAuthPresFlag 1525 MIN-ACCESS read-only 1526 DESCRIPTION "Write access is not required." 1528 OBJECT bfdSessAuthenticationType 1529 MIN-ACCESS read-only 1530 DESCRIPTION "Write access is not required." 1532 OBJECT bfdSessAuthenticationKeyID 1533 MIN-ACCESS read-only 1534 DESCRIPTION "Write access is not required." 1536 OBJECT bfdSessAuthenticationKey 1537 MIN-ACCESS read-only 1538 DESCRIPTION "Write access is not required." 1540 OBJECT bfdSessStorageType 1541 MIN-ACCESS read-only 1542 DESCRIPTION "Write access is not required." 1543 BFD-STD-MIB May 30, 2014 1545 OBJECT bfdSessRowStatus 1546 SYNTAX RowStatus { active(1) } 1547 MIN-ACCESS read-only 1548 DESCRIPTION "Write access is not required." 1549 ::= { bfdCompliances 2 } 1551 -- Units of conformance. 1553 bfdSessionGroup OBJECT-GROUP 1554 OBJECTS { 1555 bfdAdminStatus, 1556 bfdOperStatus, 1557 bfdNotificationsEnable, 1558 bfdSessVersionNumber, 1559 bfdSessType, 1560 bfdSessIndexNext, 1561 bfdSessDiscriminator, 1562 bfdSessDestinationUdpPort, 1563 bfdSessSourceUdpPort, 1564 bfdSessEchoSourceUdpPort, 1565 bfdSessAdminStatus, 1566 bfdSessOperStatus, 1567 bfdSessOperMode, 1568 bfdSessDemandModeDesiredFlag, 1569 bfdSessControlPlaneIndepFlag, 1570 bfdSessMultipointFlag, 1571 bfdSessInterface, 1572 bfdSessSrcAddrType, 1573 bfdSessSrcAddr, 1574 bfdSessDstAddrType, 1575 bfdSessDstAddr, 1576 bfdSessGTSM, 1577 bfdSessGTSMTTL, 1578 bfdSessDesiredMinTxInterval, 1579 bfdSessReqMinRxInterval, 1580 bfdSessReqMinEchoRxInterval, 1581 bfdSessDetectMult, 1582 bfdSessAuthPresFlag, 1583 bfdSessAuthenticationType, 1584 bfdSessAuthenticationKeyID, 1585 bfdSessAuthenticationKey, 1586 bfdSessStorageType, 1587 bfdSessRowStatus 1588 } 1589 STATUS current 1590 DESCRIPTION 1591 "Collection of objects needed for BFD sessions." 1592 BFD-STD-MIB May 30, 2014 1594 ::= { bfdGroups 1 } 1596 bfdSessionReadOnlyGroup OBJECT-GROUP 1597 OBJECTS { 1598 bfdSessRemoteDiscr, 1599 bfdSessState, 1600 bfdSessRemoteHeardFlag, 1601 bfdSessDiag, 1602 bfdSessNegotiatedInterval, 1603 bfdSessNegotiatedEchoInterval, 1604 bfdSessNegotiatedDetectMult, 1605 bfdSessDiscMapIndex, 1606 bfdSessIpMapIndex 1607 } 1608 STATUS current 1609 DESCRIPTION 1610 "Collection of read-only objects needed for BFD sessions." 1611 ::= { bfdGroups 2 } 1613 bfdSessionPerfGroup OBJECT-GROUP 1614 OBJECTS { 1615 bfdSessPerfCtrlPktIn, 1616 bfdSessPerfCtrlPktOut, 1617 bfdSessPerfCtrlPktDrop, 1618 bfdSessPerfCtrlPktDropLastTime, 1619 bfdSessPerfEchoPktIn, 1620 bfdSessPerfEchoPktOut, 1621 bfdSessPerfEchoPktDrop, 1622 bfdSessPerfEchoPktDropLastTime, 1623 bfdSessUpTime, 1624 bfdSessPerfLastSessDownTime, 1625 bfdSessPerfLastCommLostDiag, 1626 bfdSessPerfSessUpCount, 1627 bfdSessPerfDiscTime 1628 } 1629 STATUS current 1630 DESCRIPTION 1631 "Collection of objects needed to monitor the 1632 performance of BFD sessions." 1633 ::= { bfdGroups 3 } 1635 bfdSessionPerfHCGroup OBJECT-GROUP 1636 OBJECTS { 1637 bfdSessPerfCtrlPktInHC, 1638 bfdSessPerfCtrlPktOutHC, 1639 bfdSessPerfCtrlPktDropHC, 1640 bfdSessPerfEchoPktInHC, 1641 bfdSessPerfEchoPktOutHC, 1642 BFD-STD-MIB May 30, 2014 1644 bfdSessPerfEchoPktDropHC 1645 } 1647 STATUS current 1648 DESCRIPTION 1649 "Collection of objects needed to monitor the 1650 performance of BFD sessions for which the 1651 values of bfdSessPerfPktIn, bfdSessPerfPktOut 1652 wrap around too quickly." 1653 ::= { bfdGroups 4 } 1655 bfdNotificationGroup NOTIFICATION-GROUP 1656 NOTIFICATIONS { 1657 bfdSessUp, 1658 bfdSessDown 1659 } 1660 STATUS current 1661 DESCRIPTION 1662 "Set of notifications implemented in this 1663 module." 1664 ::= { bfdGroups 5 } 1666 END 1668 6. Security Considerations 1670 As BFD may be tied into the stability of the network infrastructure 1671 (such as routing protocols), the effects of an attack on a BFD 1672 session may be very serious. This ultimately has denial-of-service 1673 effects, as links may be declared to be down (or falsely declared to 1674 be up.) As such, improper manipulation of the objects represented by 1675 this MIB may result in denial of service to a large number of end- 1676 users. 1678 There are a number of management objects defined in this MIB module 1679 with a MAX-ACCESS clause of read-write and/or read-create. Such 1680 objects may be considered sensitive or vulnerable in some network 1681 environments. The support for SET operations in a non-secure 1682 environment without proper protection can have a negative effect on 1683 network operations. These are the tables and objects and their 1684 sensitivity/vulnerability: 1686 o bfdAdminStatus - Improper change of bfdAdminStatus, to 1687 disabled(2), adminDown(3) or down(4), can cause significant 1688 disruption of the connectivity to those portions of the Internet 1689 reached via all the applicable remote BFD peers. 1691 o bfdSessAdminStatus - Improper change of bfdSessAdminStatus, to 1692 BFD-STD-MIB May 30, 2014 1694 disabled(2), adminDown(3) or down(4), can cause significant 1695 disruption of the connectivity to those portions of the Internet 1696 reached via all the applicable remote BFD peers. 1698 o bfdSessDesiredMinTxInterval, bfdSessReqMinRxInterval, 1699 bfdSessReqMinEchoRxInterval, bfdSessDetectMult - Improper change 1700 of this object can cause connections to be disrupted for extremely 1701 long time periods when otherwise they would be restored in a 1702 relatively short period of time. 1704 o Some management objects define the BFD session whilst other 1705 management objects define the parameter of the BFD session. It is 1706 particularly important to control the support for SET access to 1707 those management objects that define the BFD session, as changes 1708 to them can be disruptive. Implementation SHOULD NOT allow 1709 changes to following management objects when bfdSessState is 1710 up(4): 1712 * bfdSessVersionNumber 1714 * bfdSessType 1716 * bfdSessDestinationUdpPort 1718 * bfdSessMultipointFlag 1720 * bfdSessInterface 1722 * bfdSessSrcAddrType 1724 * bfdSessSrcAddr 1726 * bfdSessDstAddrType 1728 * bfdSessDstAddr 1730 There are a number of management objects defined in this MIB module 1731 with a MAX-ACCESS clause of read-write and/or read-create. Such 1732 objects may be considered sensitive or vulnerable in some network 1733 environments. It is thus important to control even GET and/or NOTIFY 1734 access to these objects and possibly to even encrypt the values of 1735 these objects when sending them over the network via SNMP. 1737 o The bfdSessTable may be used to directly configure BFD sessions. 1738 The bfdSessMapTable can be used indirectly in the same way. 1739 Unauthorized access to objects in this table could result in 1740 disruption of traffic on the network. This is especially true if 1741 an unauthorized user configures enough tables to invoke a denial 1742 BFD-STD-MIB May 30, 2014 1744 of service attack on the device where they are configured, or on a 1745 remote device where the sessions terminate. 1747 Some of the readable objects in this MIB module (i.e., objects with a 1748 MAX-ACCESS other than not-accessible) may be considered sensitive or 1749 vulnerable in some network environments. It is thus important to 1750 control even GET and/or NOTIFY access to these objects and possibly 1751 to even encrypt the values of these objects when sending them over 1752 the network via SNMP. These are the tables and objects and their 1753 sensitivity/vulnerability: 1755 o The bfdSessPerfTable both allows access to the performance 1756 characteristics of BFD sessions. Network administrators not 1757 wishing to show this information should consider this table 1758 sensitive. 1760 The bfdSessAuthenticationType, bfdSessAuthenticationKeyID, and 1761 bfdSessAuthenticationKey objects hold security methods and associated 1762 security keys of BFD sessions. These objects SHOULD be considered 1763 highly sensitive objects. In order to prevent this sensitive 1764 information from being improperly accessed, implementers MAY disallow 1765 access to these objects. 1767 SNMP versions prior to SNMPv3 did not include adequate security. 1768 Even if the network itself is secure "for example by using IPSec", 1769 even then, there is no control as to who on the secure network is 1770 allowed to access and GET/SET "read/change/create/delete" the objects 1771 in these MIB modules. 1773 It is RECOMMENDED that implementers consider the security features as 1774 provided by the SNMPv3 framework (see [RFC3410], section 8), 1775 including full support for the SNMPv3 cryptographic mechanisms "for 1776 authentication and privacy". 1778 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1779 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1780 enable cryptographic security. It is then a customer/operator 1781 responsibility to ensure that the SNMP entity giving access to an 1782 instance of this MIB module, is properly configured to give access to 1783 the objects only to those principals "users" that have legitimate 1784 rights to indeed GET or SET "change/create/delete" them. 1786 7. IANA Considerations 1788 The MIB module in this document uses the following IANA-assigned 1789 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 1791 Descriptor OBJECT IDENTIFIER value 1792 BFD-STD-MIB May 30, 2014 1794 ---------- ----------------------- 1796 bfdMib { mib-2 XXX } 1798 [RFC-Editor's Note (to be removed prior to publication): the IANA is 1799 requested to assign a value for "XXX" under the 'mib-2' subtree and 1800 to record the assignment in the SMI Numbers registry. When the 1801 assignment has been made, the RFC Editor is asked to replace "XXX" 1802 (here and in the MIB module) with the assigned value and to remove 1803 this note.] 1805 8. Acknowledgments 1807 Authors would like to thank Adrian Farrel and Jeffrey Haas for 1808 performing thorough reviews and providing number of suggestions. 1809 Authors would also like to thank David Ward, Reshad Rahman, David 1810 Toscano, Sylvain Masse, Mark Tooker, Kiran Koushik Agrahara 1811 Sreenivasa, David Black and Bert Wijnen for their comments and 1812 suggestions. 1814 9. References 1816 9.1. Normative References 1818 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1819 Requirement Levels", BCP 14, RFC 2119, March 1997. 1821 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1822 Schoenwaelder, Ed., "Structure of Management Information 1823 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1825 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1826 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 1827 58, RFC 2579, April 1999. 1829 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1830 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1831 April 1999. 1833 [RFC5082] Gill, V., Heasley, J., Meyer, D., Savola, P., and C. 1834 Pignataro, "The Generalized TTL Security Mechanism 1835 (GTSM)", RFC 5082, October 2007. 1837 [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection 1838 (BFD)", RFC 5880, June 2010. 1840 [RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection 1841 (BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881, June 1842 BFD-STD-MIB May 30, 2014 1844 2010. 1846 [RFC5883] Katz, D. and D. Ward, "Bidirectional Forwarding Detection 1847 (BFD) for Multihop Paths", RFC 5883, June 2010. 1849 [RFC7130] Bhatia, M., Chen, M., Boutros, S., Binderberger, M., and 1850 J. Haas, "Bidirectional Forwarding Detection (BFD) on Link 1851 Aggregation Group (LAG) Interfaces", RFC 7130, February 1852 2014. 1854 [I-D.ietf-bfd-tc-mib] 1855 Nadeau, T., Ali, Z., and N. Akiya, "Definitions of Textual 1856 Conventions (TCs) for Bidirectional Forwarding Detection 1857 (BFD) Management", draft-ietf-bfd-tc-mib-08 (work in 1858 progress), April 2014. 1860 9.2. Informative References 1862 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1863 "Introduction and Applicability Statements for Internet- 1864 Standard Management Framework", RFC 3410, December 2002. 1866 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1867 MIB", RFC 2863, June 2000. 1869 [RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network 1870 Management Protocol (SNMP) Applications", STD 62, RFC 1871 3413, December 2002. 1873 [RFC3289] Baker, F., Chan, K., and A. Smith, "Management Information 1874 Base for the Differentiated Services Architecture", RFC 1875 3289, May 2002. 1877 Authors' Addresses 1879 Thomas D. Nadeau 1880 Brocade 1882 EMail: tnadeau@lucidvision.com 1884 Zafar Ali 1885 Cisco Systems 1887 EMail: zali@cisco.com 1889 Nobo Akiya 1890 BFD-STD-MIB May 30, 2014 1892 Cisco Systems 1894 EMail: nobo@cisco.com