draft-ietf-bfd-mib-10.txt   draft-ietf-bfd-mib-11.txt 
Network Working Group T. Nadeau Network Working Group T. Nadeau
Internet Draft BT Internet Draft Juniper Networks
Intended status: Standards Track Z. Ali Intended status: Standards Track Z. Ali
Expires: January 8, 2011 Cisco Systems, Inc. Expires: December 14, 2012 N. Akiya
N. Akiya Cisco Systems
Cisco Systems G.K. June 14, 2012
July 8, 2010
BFD Management Information Base BFD Management Information Base
draft-ietf-bfd-mib-10 draft-ietf-bfd-mib-11
Abstract
This draft defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects for modeling
Bidirectional Forwarding Detection (BFD) protocol.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79.
from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on December 14, 2012.
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
Copyright and License Notice Copyright Notice
BFD-STD-MIB June 14, 2012
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with respect
respect to this document. Code Components extracted from this to this document. Code Components extracted from this document must
document must include Simplified BSD License text as described include Simplified BSD License text as described in Section 4.e of
in Section 4.e of the Trust Legal Provisions and are provided the Trust Legal Provisions and are provided without warranty as
without warranty as described in the Simplified BSD License. described in the Simplified BSD License.
Abstract Requirements Language
This draft defines a portion of the Management Information Base (MIB) The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
for use with network management protocols in the Internet community. "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
In particular, it describes managed objects for modeling OPTIONAL" in this document are to be interpreted as described in
Bidirectional Forwarding Detection (BFD) protocol. [RFC2119].
Table of Contents Table of Contents
1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3 1. The Internet-Standard Management Framework . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Brief Description of MIB Objects . . . . . . . . . . . . . . . 3
5. Brief Description of MIB Objects . . . . . . . . . . . . . . . 3 4.1. General Variables . . . . . . . . . . . . . . . . . . . . 4
5.1. General Variables . . . . . . . . . . . . . . . . . . . . 4 4.2. Session Table (bfdSessionTable) . . . . . . . . . . . . . 4
5.2. Session Table (bfdSessionTable) . . . . . . . . . . . . . 4 4.3. Session Performance Table (bfdSessionPerfTable) . . . . . 4
5.3. Session Performance Table (bfdSessionPerfTable) . . . . . 4 4.4. BFD Session Discriminator Mapping Table
5.4. BFD Session Discriminator Mapping Table
(bfdSessDiscMapTable) . . . . . . . . . . . . . . . . . . 4 (bfdSessDiscMapTable) . . . . . . . . . . . . . . . . . . 4
5.5. BFD Session IP Mapping Table (bfdSessIpMapTable) . . . . . 4 4.5. BFD Session IP Mapping Table (bfdSessIpMapTable) . . . . . 4
6. BFD MIB Module Definitions . . . . . . . . . . . . . . . . . . 4 5. BFD MIB Module Definitions . . . . . . . . . . . . . . . . . . 4
7. Security Considerations . . . . . . . . . . . . . . . . . . . 31 6. Security Considerations . . . . . . . . . . . . . . . . . . . 31
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 33 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 33
9.1. Normative References . . . . . . . . . . . . . . . . . . . 33 8.1. Normative References . . . . . . . . . . . . . . . . . . . 33
9.2. Informative References . . . . . . . . . . . . . . . . . . 34 8.2. Informative References . . . . . . . . . . . . . . . . . . 34
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 34 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 34
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 34 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 34
1. Requirements notation 1. The Internet-Standard Management Framework
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
BFD-STD-MIB June 14, 2012
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
[RFC3410]. [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
[RFC2578], STD 58, [RFC2579] and STD 58, [RFC2580]. [RFC2578], STD 58, [RFC2579] and STD 58, [RFC2580].
3. Introduction 2. Introduction
This memo defines an portion of the Management Information Base (MIB) This memo defines an portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects to configure and/or In particular, it describes managed objects to configure and/or
monitor Bi-Directional Forwarding Detection for [BFD], [BFD-1HOP] and monitor Bi-Directional Forwarding Detection for [BFD], [BFD-1HOP] and
[BFD-MH], BFD versions 0 and/or 1, on devices supporting this [BFD-MH], BFD versions 0 and/or 1, on devices supporting this
feature. feature.
Comments should be made directly to the BFD mailing list at Comments should be made directly to the BFD mailing list at
rtg-bfd@ietf.org. rtg-bfd@ietf.org.
4. Terminology 3. Terminology
This document adopts the definitions, acronyms and mechanisms This document adopts the definitions, acronyms and mechanisms
described in [BFD], [BFD-1HOP] and [BFD-MH]. Unless otherwise described in [BFD], [BFD-1HOP] and [BFD-MH]. Unless otherwise
stated, the mechanisms described therein will not be re-described stated, the mechanisms described therein will not be re-described
here. here.
5. Brief Description of MIB Objects 4. Brief Description of MIB Objects
This section describes objects pertaining to BFD. The MIB objects This section describes objects pertaining to BFD. The MIB objects
are derived from [BFD] and [BFD-MH]. are derived from [BFD] and [BFD-MH], and also include textual
conventions defined in [BFD-TC].
5.1. General Variables 4.1. General Variables
The General Variables are used to identify parameters that are global The General Variables are used to identify parameters that are global
to the BFD process. to the BFD process.
5.2. Session Table (bfdSessionTable) 4.2. Session Table (bfdSessionTable)
The session table is used to identify a BFD session between a pair of The session table is used to identify a BFD session between a pair of
nodes. nodes.
5.3. Session Performance Table (bfdSessionPerfTable) BFD-STD-MIB June 14, 2012
4.3. Session Performance Table (bfdSessionPerfTable)
The session performance table is used for collecting BFD performance The session performance table is used for collecting BFD performance
counters on a per session basis. This table is an AUGMENT to the counters on a per session basis. This table is an AUGMENT to the
bfdSessionTable. bfdSessionTable.
5.4. BFD Session Discriminator Mapping Table (bfdSessDiscMapTable) 4.4. BFD Session Discriminator Mapping Table (bfdSessDiscMapTable)
The BFD Session Discriminator Mapping Table maps a local The BFD Session Discriminator Mapping Table maps a local
discriminator value to associated BFD session's BfdSessIndexTC used discriminator value to associated BFD session's BfdSessIndexTC used
in the bfdSessionTable. in the bfdSessionTable.
5.5. BFD Session IP Mapping Table (bfdSessIpMapTable) 4.5. BFD Session IP Mapping Table (bfdSessIpMapTable)
The BFD Session IP Mapping Table maps, given bfdSessInterface, The BFD Session IP Mapping Table maps, given bfdSessInterface,
bfdSessSrcAddrType, bfdSessSrcAddr, bfdSessDstAddrType, and bfdSessSrcAddrType, bfdSessSrcAddr, bfdSessDstAddrType, and
bfdSessDstAddr, to an associated BFD session's BfdSessIndexTC bfdSessDstAddr, to an associated BFD session's BfdSessIndexTC
used in the bfdSessionTable. This table SHOULD contains those used in the bfdSessionTable. This table SHOULD contains those
BFD sessions that are of IP type. BFD sessions that are of IP type.
6. BFD MIB Module Definitions 5. BFD MIB Module Definitions
This MIB module makes references to the following documents. This MIB module makes references to the following documents.
[RFC2579], [RFC2580], [RFC2863], [RFC4001], and [RFC3413]. [RFC2579], [RFC2580], [RFC2863], [RFC4001], and [RFC3413].
BFD-STD-MIB DEFINITIONS ::= BEGIN BFD-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
mib-2, Integer32, Unsigned32, Counter32, Counter64 mib-2, Integer32, Unsigned32, Counter32, Counter64
FROM SNMPv2-SMI FROM SNMPv2-SMI
skipping to change at page 4, line 48 skipping to change at page 5, line 4
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
InterfaceIndexOrZero InterfaceIndexOrZero
FROM IF-MIB FROM IF-MIB
InetAddress, InetAddressType, InetPortNumber InetAddress, InetAddressType, InetPortNumber
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
BFD-STD-MIB June 14, 2012
BfdSessIndexTC, BfdIntervalTC, BfdMultiplierTC, BfdDiagTC, BfdSessIndexTC, BfdIntervalTC, BfdMultiplierTC, BfdDiagTC,
BfdSessTypeTC, BfdSessOperModeTC, BfdCtrlDestPortNumberTC, BfdSessTypeTC, BfdSessOperModeTC, BfdCtrlDestPortNumberTC,
BfdCtrlSourcePortNumberTC, BfdSessStateTC, BfdCtrlSourcePortNumberTC, BfdSessStateTC,
BfdSessAuthenticationTypeTC, BfdSessionAuthenticationKeyTC BfdSessAuthenticationTypeTC, BfdSessionAuthenticationKeyTC
FROM BFD-TC-STD-MIB; FROM BFD-TC-STD-MIB;
bfdMib MODULE-IDENTITY bfdMIB MODULE-IDENTITY
LAST-UPDATED "201007081200Z" -- 8 July 2010 12:00:00 EST LAST-UPDATED "201204141200Z" -- 14 June 2012 12:00:00 EST
ORGANIZATION "IETF Bidirectional Forwarding Detection ORGANIZATION "IETF Bidirectional Forwarding Detection
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"Thomas D. Nadeau "Thomas D. Nadeau
BT Juniper Networks
Email: tnadeau@lucidvision.com Email: tnadeau@lucidvision.com
Zafar Ali Zafar Ali
Cisco Systems, Inc. Cisco Systems, Inc.
Email: zali@cisco.com Email: zali@cisco.com
Nobo Akiya Nobo Akiya
Cisco Systems, G.K. Cisco Systems, G.K.
Email: nobo@cisco.com" Email: nobo@cisco.com"
DESCRIPTION DESCRIPTION
"Bidirectional Forwarding Management Information Base." "Bidirectional Forwarding Management Information Base."
REVISION "201007081200Z" -- 8 July 2010 12:00:00 EST REVISION "201204141200Z" -- 14 June 2012 12:00:00 EST
DESCRIPTION DESCRIPTION
"Initial version. Published as RFC xxxx." "Initial version. Published as RFC xxxx."
-- RFC Ed.: RFC-editor pls fill in xxxx -- RFC Ed.: RFC-editor pls fill in xxxx
::= { mib-2 XXX } ::= { mib-2 XXX }
-- RFC Ed.: assigned by IANA, see section 7.1 for details -- RFC Ed.: assigned by IANA, see section 7.1 for details
-- Top level components of this MIB module. -- Top level components of this MIB module.
bfdNotifications OBJECT IDENTIFIER ::= { bfdMIB 0 } bfdNotifications OBJECT IDENTIFIER ::= { bfdMIB 0 }
skipping to change at page 5, line 49 skipping to change at page 6, line 4
bfdScalarObjects OBJECT IDENTIFIER ::= { bfdObjects 1 } bfdScalarObjects OBJECT IDENTIFIER ::= { bfdObjects 1 }
-- BFD General Variables -- BFD General Variables
-- These parameters apply globally to the Systems' -- These parameters apply globally to the Systems'
-- BFD Process. -- BFD Process.
bfdAdminStatus OBJECT-TYPE bfdAdminStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
BFD-STD-MIB June 14, 2012
enabled(1), enabled(1),
disabled(2) disabled(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The global administrative status of BFD in this router. "The global administrative status of BFD in this device.
The value 'enabled' denotes that the BFD Process is The value 'enabled' denotes that the BFD Process is
active on at least one interface; 'disabled' disables active on at least one interface; 'disabled' disables
it on all interfaces." it on all interfaces."
DEFVAL { enabled } DEFVAL { enabled }
::= { bfdScalarObjects 1 } ::= { bfdScalarObjects 1 }
bfdSessNotificationsEnable OBJECT-TYPE bfdSessNotificationsEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
skipping to change at page 6, line 40 skipping to change at page 6, line 46
-- The BFD Session Table specifies BFD session specific -- The BFD Session Table specifies BFD session specific
-- information. -- information.
bfdSessTable OBJECT-TYPE bfdSessTable OBJECT-TYPE
SYNTAX SEQUENCE OF BfdSessEntry SYNTAX SEQUENCE OF BfdSessEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BFD Session Table describes the BFD sessions." "The BFD Session Table describes the BFD sessions."
REFERENCE REFERENCE
"BFD Version 0 (draft-katz-ward-bfd-02.txt) and "Katz, D. and D. Ward, Bidirectional Forwarding
BFD Version 1 (RFC5880)" Detection (BFD), RFC 5880, June 2012."
::= { bfdObjects 2 } ::= { bfdObjects 2 }
bfdSessEntry OBJECT-TYPE bfdSessEntry OBJECT-TYPE
SYNTAX BfdSessEntry SYNTAX BfdSessEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
BFD-STD-MIB June 14, 2012
DESCRIPTION DESCRIPTION
"The BFD Session Entry describes BFD session." "The BFD Session Entry describes BFD session."
INDEX { bfdSessIndex } INDEX { bfdSessIndex }
::= { bfdSessTable 1 } ::= { bfdSessTable 1 }
BfdSessEntry ::= SEQUENCE { BfdSessEntry ::= SEQUENCE {
bfdSessIndex BfdSessIndexTC, bfdSessIndex BfdSessIndexTC,
bfdSessVersionNumber Unsigned32, bfdSessVersionNumber Unsigned32,
bfdSessType BfdSessTypeTC, bfdSessType BfdSessTypeTC,
bfdSessDiscriminator Unsigned32, bfdSessDiscriminator Unsigned32,
skipping to change at page 7, line 40 skipping to change at page 7, line 46
bfdSessReqMinRxInterval BfdIntervalTC, bfdSessReqMinRxInterval BfdIntervalTC,
bfdSessReqMinEchoRxInterval BfdIntervalTC, bfdSessReqMinEchoRxInterval BfdIntervalTC,
bfdSessDetectMult BfdMultiplierTC, bfdSessDetectMult BfdMultiplierTC,
bfdSessNegotiatedInterval BfdIntervalTC, bfdSessNegotiatedInterval BfdIntervalTC,
bfdSessNegotiatedEchoInterval BfdIntervalTC, bfdSessNegotiatedEchoInterval BfdIntervalTC,
bfdSessNegotiatedDetectMult BfdMultiplierTC, bfdSessNegotiatedDetectMult BfdMultiplierTC,
bfdSessAuthPresFlag TruthValue, bfdSessAuthPresFlag TruthValue,
bfdSessAuthenticationType BfdSessAuthenticationTypeTC, bfdSessAuthenticationType BfdSessAuthenticationTypeTC,
bfdSessAuthenticationKeyID Integer32, bfdSessAuthenticationKeyID Integer32,
bfdSessAuthenticationKey BfdSessionAuthenticationKeyTC, bfdSessAuthenticationKey BfdSessionAuthenticationKeyTC,
bfdSessStorType StorageType, bfdSessStorageType StorageType,
bfdSessRowStatus RowStatus bfdSessRowStatus RowStatus
} }
bfdSessIndex OBJECT-TYPE bfdSessIndex OBJECT-TYPE
SYNTAX BfdSessIndexTC SYNTAX BfdSessIndexTC
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
BFD-STD-MIB June 14, 2012
DESCRIPTION DESCRIPTION
"This object contains an index used to represent a "This object contains an index used to represent a
unique BFD session on this device." unique BFD session on this device."
::= { bfdSessEntry 1 } ::= { bfdSessEntry 1 }
bfdSessVersionNumber OBJECT-TYPE bfdSessVersionNumber OBJECT-TYPE
SYNTAX Unsigned32 (0..7) SYNTAX Unsigned32 (0..7)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The version number of the BFD protocol that this session "The version number of the BFD protocol that this session
is running in. Write access is available for this object is running in. Write access is available for this object
to provide ability to set desired version for this to provide ability to set desired version for this
BFD session." BFD session."
REFERENCE REFERENCE
"BFD Version 0 (draft-katz-ward-bfd-02.txt) and "Katz, D. and D. Ward, Bidirectional Forwarding
BFD Version 1 (RFC5880)" Detection (BFD), RFC 5880, June 2012."
DEFVAL { 1 } DEFVAL { 1 }
::= { bfdSessEntry 2 } ::= { bfdSessEntry 2 }
bfdSessType OBJECT-TYPE bfdSessType OBJECT-TYPE
SYNTAX BfdSessTypeTC SYNTAX BfdSessTypeTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the type of this BFD session." "This object specifies the type of this BFD session."
::= { bfdSessEntry 3 } ::= { bfdSessEntry 3 }
skipping to change at page 8, line 45 skipping to change at page 8, line 53
bfdSessRemoteDiscr OBJECT-TYPE bfdSessRemoteDiscr OBJECT-TYPE
SYNTAX Unsigned32 (0 | 1..4294967295) SYNTAX Unsigned32 (0 | 1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the session discriminator chosen "This object specifies the session discriminator chosen
by the remote system for this BFD session. The value may by the remote system for this BFD session. The value may
be zero(0) if the remote discriminator is not yet known be zero(0) if the remote discriminator is not yet known
or if the session is in the down or adminDown(1) state." or if the session is in the down or adminDown(1) state."
REFERENCE REFERENCE
"RFC5880, Section 6.8.6" "Section 6.8.6, from Katz, D. and D. Ward, Bidirectional
BFD-STD-MIB June 14, 2012
Forwarding Detection (BFD), RFC 5880, June 2012."
::= { bfdSessEntry 5 } ::= { bfdSessEntry 5 }
bfdSessDestinationUdpPort OBJECT-TYPE bfdSessDestinationUdpPort OBJECT-TYPE
SYNTAX BfdCtrlDestPortNumberTC SYNTAX BfdCtrlDestPortNumberTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the destination UDP port number "This object specifies the destination UDP port number
used for this BFD session's control packets. The value used for this BFD session's control packets. The value
may be zero(0) if the session is in adminDown(1) state." may be zero(0) if the session is in adminDown(1) state."
skipping to change at page 9, line 44 skipping to change at page 10, line 4
permit the implementation to chose its own source port permit the implementation to chose its own source port
number." number."
DEFVAL { 0 } DEFVAL { 0 }
::= { bfdSessEntry 8 } ::= { bfdSessEntry 8 }
bfdSessAdminStatus OBJECT-TYPE bfdSessAdminStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
stop(1), stop(1),
start(2) start(2)
} }
BFD-STD-MIB June 14, 2012
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A transition from 'stop' to 'start' will start "A transition from 'stop' to 'start' will start
the BFD state machine for the session. The state the BFD state machine for the session. The state
machine will have an initial state of down. machine will have an initial state of down.
A transition from 'start' to 'stop' will cause A transition from 'start' to 'stop' will cause
the BFD sesssion to be brought down to the BFD sesssion to be brought down to
adminDown(1). Care should be used in providing adminDown(1). Care should be used in providing
write access to this object without adequate write access to this object without adequate
skipping to change at page 10, line 31 skipping to change at page 10, line 42
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies status of BFD packet reception from "This object specifies status of BFD packet reception from
the remote system. Specifically, it is set to true(1) if the remote system. Specifically, it is set to true(1) if
the local system is actively receiving BFD packets from the the local system is actively receiving BFD packets from the
remote system, and is set to false(2) if the local system remote system, and is set to false(2) if the local system
has not received BFD packets recently (within the detection has not received BFD packets recently (within the detection
time) or if the local system is attempting to tear down time) or if the local system is attempting to tear down
the BFD session." the BFD session."
REFERENCE REFERENCE
"BFD Version 0 (draft-katz-ward-bfd-02.txt) and "Katz, D. and D. Ward, Bidirectional
BFD Version 1 (RFC5880)" Forwarding Detection (BFD), RFC 5880, June 2012."
DEFVAL { false } DEFVAL { false }
::= { bfdSessEntry 11 } ::= { bfdSessEntry 11 }
bfdSessDiag OBJECT-TYPE bfdSessDiag OBJECT-TYPE
SYNTAX BfdDiagTC SYNTAX BfdDiagTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A diagnostic code specifying the local system's reason "A diagnostic code specifying the local system's reason
for the last transition of the session from up(4) for the last transition of the session from up(4)
BFD-STD-MIB June 14, 2012
to some other state." to some other state."
::= { bfdSessEntry 12 } ::= { bfdSessEntry 12 }
bfdSessOperMode OBJECT-TYPE bfdSessOperMode OBJECT-TYPE
SYNTAX BfdSessOperModeTC SYNTAX BfdSessOperModeTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies current operating mode that BFD "This object specifies current operating mode that BFD
session is operating in." session is operating in."
skipping to change at page 11, line 43 skipping to change at page 12, line 4
bfdSessMultipointFlag OBJECT-TYPE bfdSessMultipointFlag OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the Multipoint (M) bit for this "This object indicates the Multipoint (M) bit for this
session. It is set to true(1) if Multipoint (M) bit is session. It is set to true(1) if Multipoint (M) bit is
set to 1. Otherwise, the value is set to false(2)" set to 1. Otherwise, the value is set to false(2)"
DEFVAL { false } DEFVAL { false }
::= { bfdSessEntry 16 } ::= { bfdSessEntry 16 }
BFD-STD-MIB June 14, 2012
bfdSessInterface OBJECT-TYPE bfdSessInterface OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains an interface index used to indicate "This object contains an interface index used to indicate
the interface which this BFD session is running on. This the interface which this BFD session is running on. This
value can be zero if there is no interface associated value can be zero if there is no interface associated
with this BFD session." with this BFD session."
skipping to change at page 12, line 41 skipping to change at page 13, line 4
bfdSessDstAddrType OBJECT-TYPE bfdSessDstAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies IP address type of the neighboring IP "This object specifies IP address type of the neighboring IP
address which is being monitored with this BFD session. address which is being monitored with this BFD session.
Only values unknown(0), ipv4(1), ipv6(2), or ipv6z(4) Only values unknown(0), ipv4(1), ipv6(2), or ipv6z(4)
have to be supported. The value of unknown(0) is allowed have to be supported. The value of unknown(0) is allowed
only when the session is singleHop(1) and the outgoing only when the session is singleHop(1) and the outgoing
BFD-STD-MIB June 14, 2012
interface is of type point-to-point, or when the BFD interface is of type point-to-point, or when the BFD
session is not associated with a specific interface. If any session is not associated with a specific interface. If any
other unsupported values are attempted in a set operation, other unsupported values are attempted in a set operation,
the agent MUST return an inconsistentValue error." the agent MUST return an inconsistentValue error."
::= { bfdSessEntry 20 } ::= { bfdSessEntry 20 }
bfdSessDstAddr OBJECT-TYPE bfdSessDstAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 13, line 40 skipping to change at page 14, line 4
this object SHOULD be set to maximum TTL allowed for this object SHOULD be set to maximum TTL allowed for
single hop. The value of zero(0) indicates that single hop. The value of zero(0) indicates that
bfdSessGTSM is disabled." bfdSessGTSM is disabled."
REFERENCE REFERENCE
"RFC5082, The Generalized TTL Security Mechanism (GTSM). "RFC5082, The Generalized TTL Security Mechanism (GTSM).
RFC5881, Section 5" RFC5881, Section 5"
DEFVAL { 0 } DEFVAL { 0 }
::= { bfdSessEntry 23 } ::= { bfdSessEntry 23 }
bfdSessDesiredMinTxInterval OBJECT-TYPE bfdSessDesiredMinTxInterval OBJECT-TYPE
BFD-STD-MIB June 14, 2012
SYNTAX BfdIntervalTC SYNTAX BfdIntervalTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the minimum interval, in "This object specifies the minimum interval, in
microseconds, that the local system would like to use microseconds, that the local system would like to use
when transmitting BFD Control packets. The value of when transmitting BFD Control packets. The value of
zero(0) is reserved, and should not be used." zero(0) is reserved, and should not be used."
REFERENCE REFERENCE
"RFC5880, Section 4.1" "Section 4.1 from Katz, D. and D. Ward, Bidirectional
Forwarding Detection (BFD), RFC 5880, June 2012."
::= { bfdSessEntry 24 } ::= { bfdSessEntry 24 }
bfdSessReqMinRxInterval OBJECT-TYPE bfdSessReqMinRxInterval OBJECT-TYPE
SYNTAX BfdIntervalTC SYNTAX BfdIntervalTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the minimum interval, in "This object specifies the minimum interval, in
microseconds, between received BFD Control packets the microseconds, between received BFD Control packets the
local system is capable of supporting. The value of local system is capable of supporting. The value of
zero(0) can be specified when the transmitting system zero(0) can be specified when the transmitting system
does not want the remote system to send any periodic BFD does not want the remote system to send any periodic BFD
control packets." control packets."
REFERENCE REFERENCE
"RFC5880, Section 4.1" "Section 4.1 from Katz, D. and D. Ward, Bidirectional
Forwarding Detection (BFD), RFC 5880, June 2012."
::= { bfdSessEntry 25 } ::= { bfdSessEntry 25 }
bfdSessReqMinEchoRxInterval OBJECT-TYPE bfdSessReqMinEchoRxInterval OBJECT-TYPE
SYNTAX BfdIntervalTC SYNTAX BfdIntervalTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the minimum interval, in "This object specifies the minimum interval, in
microseconds, between received BFD Echo packets that this microseconds, between received BFD Echo packets that this
system is capable of supporting. Value must be zero(0) if system is capable of supporting. Value must be zero(0) if
this is a multihop BFD session." this is a multihop BFD session."
::= { bfdSessEntry 26 } ::= { bfdSessEntry 26 }
bfdSessDetectMult OBJECT-TYPE bfdSessDetectMult OBJECT-TYPE
SYNTAX BfdMultiplierTC SYNTAX BfdMultiplierTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the Detect time multiplier." "This object specifies the Detect time multiplier."
::= { bfdSessEntry 27 } ::= { bfdSessEntry 27 }
BFD-STD-MIB June 14, 2012
bfdSessNegotiatedInterval OBJECT-TYPE bfdSessNegotiatedInterval OBJECT-TYPE
SYNTAX BfdIntervalTC SYNTAX BfdIntervalTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the negotiated interval, in "This object specifies the negotiated interval, in
microseconds, that the local system is transmitting microseconds, that the local system is transmitting
BFD Control packets." BFD Control packets."
::= { bfdSessEntry 28 } ::= { bfdSessEntry 28 }
skipping to change at page 15, line 27 skipping to change at page 15, line 45
bfdSessAuthPresFlag OBJECT-TYPE bfdSessAuthPresFlag OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates that the local system's "This object indicates that the local system's
desire to use Authentication. Specifically, it is set desire to use Authentication. Specifically, it is set
to true(1) if the local system wishes the session to true(1) if the local system wishes the session
to be authenticated or false(2) if not." to be authenticated or false(2) if not."
REFERENCE REFERENCE
"RFC5880, Sections 4.2 - 4.4" "Sections 4.2 - 4.4 from Katz, D. and D. Ward,
Bidirectional Forwarding Detection (BFD), RFC 5880,
June 2012."
DEFVAL { false } DEFVAL { false }
::= { bfdSessEntry 31 } ::= { bfdSessEntry 31 }
bfdSessAuthenticationType OBJECT-TYPE bfdSessAuthenticationType OBJECT-TYPE
SYNTAX BfdSessAuthenticationTypeTC SYNTAX BfdSessAuthenticationTypeTC
MAX-ACCESS read-create MAX-ACCESS read-create
BFD-STD-MIB June 14, 2012
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Authentication Type used for this BFD session. "The Authentication Type used for this BFD session.
This field is valid only when the Authentication This field is valid only when the Authentication
Present bit is set. Max-access to this object as well as Present bit is set. Max-access to this object as well as
other authentication related objects are set to other authentication related objects are set to
read-create in order to support management of a single read-create in order to support management of a single
key ID at a time, key rotation is not handled. Key update key ID at a time, key rotation is not handled. Key update
in practice must be done by atomic update using a set in practice must be done by atomic update using a set
containing all affected objects in the same varBindList containing all affected objects in the same varBindList
or otherwise risk the session dropping. Value -1 or otherwise risk the session dropping. Value -1
indicates that no authentication is in use for this indicates that no authentication is in use for this
session." session."
REFERENCE REFERENCE
"RFC5880, Sections 4.2 - 4.4" "Sections 4.2 - 4.4 from Katz, D. and D. Ward,
Bidirectional Forwarding Detection (BFD), RFC 5880,
June 2012."
DEFVAL { -1 } DEFVAL { -1 }
::= { bfdSessEntry 32 } ::= { bfdSessEntry 32 }
bfdSessAuthenticationKeyID OBJECT-TYPE bfdSessAuthenticationKeyID OBJECT-TYPE
SYNTAX Integer32 (-1 | 0..255) SYNTAX Integer32 (-1 | 0..255)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The authentication key ID in use for this session. This "The authentication key ID in use for this session. This
object permits multiple keys to be active simultaneously. object permits multiple keys to be active simultaneously.
When bfdSessAuthPresFlag is false(2), then the value When bfdSessAuthPresFlag is false(2), then the value
of this object MUST be -1. The value -1 indicates that of this object MUST be -1. The value -1 indicates that
no Authentication Key ID will be present in the optional no Authentication Key ID will be present in the optional
BFD Authentication Section." BFD Authentication Section."
REFERENCE REFERENCE
"RFC5880, Sections 4.2 - 4.4" "Sections 4.2 - 4.4 from Katz, D. and D. Ward,
Bidirectional Forwarding Detection (BFD), RFC 5880,
June 2012."
DEFVAL { -1 } DEFVAL { -1 }
::= { bfdSessEntry 33 } ::= { bfdSessEntry 33 }
bfdSessAuthenticationKey OBJECT-TYPE bfdSessAuthenticationKey OBJECT-TYPE
SYNTAX BfdSessionAuthenticationKeyTC SYNTAX BfdSessionAuthenticationKeyTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The authentication key. When the "The authentication key. When the
bfdSessAuthenticationType is simplePassword(1), the value bfdSessAuthenticationType is simplePassword(1), the value
of this object is the password present in the BFD packets. of this object is the password present in the BFD packets.
When the bfdSessAuthentication type is one of the keyed When the bfdSessAuthentication type is one of the keyed
BFD-STD-MIB June 14, 2012
authentication types, this value is used in the authentication types, this value is used in the
computation of the key present in the BFD authentication computation of the key present in the BFD authentication
packet." packet."
REFERENCE REFERENCE
"RFC5880, Sections 4.2 - 4.4" "Sections 4.2 - 4.4 from from Katz, D. and D. Ward,
Bidirectional Forwarding Detection (BFD), RFC 5880,
June 2012."
::= { bfdSessEntry 34 } ::= { bfdSessEntry 34 }
bfdSessStorType OBJECT-TYPE bfdSessStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this "This variable indicates the storage type for this
object. Conceptual rows having the value object. Conceptual rows having the value
'permanent' need not allow write-access to any 'permanent' need not allow write-access to any
columnar objects in the row." columnar objects in the row."
::= { bfdSessEntry 35 } ::= { bfdSessEntry 35 }
skipping to change at page 17, line 26 skipping to change at page 18, line 4
DESCRIPTION DESCRIPTION
"This table specifies BFD Session performance counters." "This table specifies BFD Session performance counters."
::= { bfdObjects 3 } ::= { bfdObjects 3 }
bfdSessPerfEntry OBJECT-TYPE bfdSessPerfEntry OBJECT-TYPE
SYNTAX BfdSessPerfEntry SYNTAX BfdSessPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by a BFD-enabled node "An entry in this table is created by a BFD-enabled node
BFD-STD-MIB June 14, 2012
for every BFD Session. bfdSessPerfDiscTime is used to for every BFD Session. bfdSessPerfDiscTime is used to
indicate potential discontinuity for all counter objects indicate potential discontinuity for all counter objects
in this table." in this table."
AUGMENTS { bfdSessEntry } AUGMENTS { bfdSessEntry }
::= { bfdSessPerfTable 1 } ::= { bfdSessPerfTable 1 }
BfdSessPerfEntry ::= SEQUENCE { BfdSessPerfEntry ::= SEQUENCE {
bfdSessPerfCtrlPktIn Counter32, bfdSessPerfCtrlPktIn Counter32,
bfdSessPerfCtrlPktOut Counter32, bfdSessPerfCtrlPktOut Counter32,
bfdSessPerfCtrlPktDrop Counter32, bfdSessPerfCtrlPktDrop Counter32,
skipping to change at page 18, line 25 skipping to change at page 19, line 4
BFD session. This value MUST be equal to the least BFD session. This value MUST be equal to the least
significant 32 bits of bfdSessPerfCtrlPktInHC." significant 32 bits of bfdSessPerfCtrlPktInHC."
::= { bfdSessPerfEntry 1 } ::= { bfdSessPerfEntry 1 }
bfdSessPerfCtrlPktOut OBJECT-TYPE bfdSessPerfCtrlPktOut OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of BFD control messages sent for this BFD "The total number of BFD control messages sent for this BFD
session. This value MUST be equal to the least significant BFD-STD-MIB June 14, 2012
32 bits of bfdSessPerfCtrlPktOutHC."
session.
It MUST be equal to the least significant 32 bits of
significant 32 bits of bfdSessPerfCtrlPktOutHC
if supported, and MUST do so the rules spelled out in
RFC 2863."
::= { bfdSessPerfEntry 2 } ::= { bfdSessPerfEntry 2 }
bfdSessPerfCtrlPktDrop OBJECT-TYPE bfdSessPerfCtrlPktDrop OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of BFD control messages received for this "The total number of BFD control messages received for this
session yet dropped for being invalid. This value MUST be session yet dropped for being invalid.
equal to the least significant 32 bits of
bfdSessPerfCtrlPktDropHC." It MUST be equal to the least significant 32 bits of
significant 32 bits of bfdSessPerfCtrlPktDropHC
if supported, and MUST do so the rules spelled out in
RFC 2863."
::= { bfdSessPerfEntry 3 } ::= { bfdSessPerfEntry 3 }
bfdSessPerfCtrlPktDropLastTime OBJECT-TYPE bfdSessPerfCtrlPktDropLastTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion at "The value of sysUpTime on the most recent occasion at
which received BFD control message for this session was which received BFD control message for this session was
dropped. If no such up event exists, this object contains dropped. If no such up event exists, this object contains
a zero value." a zero value."
::= { bfdSessPerfEntry 4 } ::= { bfdSessPerfEntry 4 }
bfdSessPerfEchoPktIn OBJECT-TYPE bfdSessPerfEchoPktIn OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of BFD echo messages received for this "The total number of BFD echo messages received for this
BFD session. This value MUST be equal to the least BFD session.
significant 32 bits of bfdSessPerfEchoPktInHC."
It MUST be equal to the least significant 32 bits of
significant 32 bits of bfdSessPerfEchoPktInHC if
supported, and MUST do so the rules spelled out in
RFC 2863."
::= { bfdSessPerfEntry 5 } ::= { bfdSessPerfEntry 5 }
BFD-STD-MIB June 14, 2012
bfdSessPerfEchoPktOut OBJECT-TYPE bfdSessPerfEchoPktOut OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of BFD echo messages sent for this BFD "The total number of BFD echo messages sent for this BFD
session. This value MUST be equal to the least significant session.
32 bits of bfdSessPerfEchoPktOutHC."
It MUST be equal to the least significant 32 bits of
bfdSessPerfEchoPktOutHC if supported, and MUST do so
the rules spelled out in RFC 2863."
::= { bfdSessPerfEntry 6 } ::= { bfdSessPerfEntry 6 }
bfdSessPerfEchoPktDrop OBJECT-TYPE bfdSessPerfEchoPktDrop OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of BFD echo messages received for this "The total number of BFD echo messages received for this
session yet dropped for being invalid. This value MUST be session yet dropped for being invalid.
equal to the least significant 32 bits of
bfdSessPerfEchoPktDropHC." It MUST be equal to the least significant 32 bits of
bfdSessPerfEchoPktDropHC if supported, and MUST do so
the rules spelled out in RFC 2863."
::= { bfdSessPerfEntry 7 } ::= { bfdSessPerfEntry 7 }
bfdSessPerfEchoPktDropLastTime OBJECT-TYPE bfdSessPerfEchoPktDropLastTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion at "The value of sysUpTime on the most recent occasion at
which received BFD echo message for this session was which received BFD echo message for this session was
dropped. If no such up event exists, this object contains dropped. If no such up event exists, this object contains
skipping to change at page 20, line 6 skipping to change at page 21, line 4
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion at which "The value of sysUpTime on the most recent occasion at which
the session came up. If no such up event exists this object the session came up. If no such up event exists this object
contains a zero value." contains a zero value."
::= { bfdSessPerfEntry 9 } ::= { bfdSessPerfEntry 9 }
bfdSessPerfLastSessDownTime OBJECT-TYPE bfdSessPerfLastSessDownTime OBJECT-TYPE
BFD-STD-MIB June 14, 2012
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion at "The value of sysUpTime on the most recent occasion at
which the last time communication was lost with the which the last time communication was lost with the
neighbor. If no such down event exist this object neighbor. If no such down event exist this object
contains a zero value." contains a zero value."
::= { bfdSessPerfEntry 10 } ::= { bfdSessPerfEntry 10 }
skipping to change at page 21, line 4 skipping to change at page 22, line 4
The relevant counters are the specific instances associated The relevant counters are the specific instances associated
with this BFD session of any Counter32 object contained in with this BFD session of any Counter32 object contained in
the BfdSessPerfTable. If no such discontinuities have the BfdSessPerfTable. If no such discontinuities have
occurred since the last re-initialization of the local occurred since the last re-initialization of the local
management subsystem, then this object contains a zero management subsystem, then this object contains a zero
value." value."
::= { bfdSessPerfEntry 13 } ::= { bfdSessPerfEntry 13 }
bfdSessPerfCtrlPktInHC OBJECT-TYPE bfdSessPerfCtrlPktInHC OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
BFD-STD-MIB June 14, 2012
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the total number of BFD control "This value represents the total number of BFD control
messages received for this BFD session." messages received for this BFD session.
It MUST be equal to the least significant 32 bits of
bfdSessPerfCtrlPktInHC if supported, and MUST do so
the rules spelled out in RFC 2863."
::= { bfdSessPerfEntry 14 } ::= { bfdSessPerfEntry 14 }
bfdSessPerfCtrlPktOutHC OBJECT-TYPE bfdSessPerfCtrlPktOutHC OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the total number of BFD control "This value represents the total number of BFD control
messages transmitted for this BFD session." messages transmitted for this BFD session.
It MUST be equal to the least significant 32 bits of
bfdSessPerfCtrlPktOut if supported, and MUST do so
the rules spelled out in RFC 2863."
::= { bfdSessPerfEntry 15 } ::= { bfdSessPerfEntry 15 }
bfdSessPerfCtrlPktDropHC OBJECT-TYPE bfdSessPerfCtrlPktDropHC OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the total number of BFD control "This value represents the total number of BFD control
messages received for this BFD session yet dropped for messages received for this BFD session yet dropped for
being invalid." being invalid.
It MUST be equal to the least significant 32 bits of
bfdSessPerfCtrlPktDrop if supported, and MUST do so
the rules spelled out in RFC 2863."
::= { bfdSessPerfEntry 16 } ::= { bfdSessPerfEntry 16 }
bfdSessPerfEchoPktInHC OBJECT-TYPE bfdSessPerfEchoPktInHC OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the total number of BFD echo "This value represents the total number of BFD echo
messages received for this BFD session." messages received for this BFD session.
It MUST be equal to the least significant 32 bits of
bfdSessPerfEchoPktIn if supported, and MUST do so
BFD-STD-MIB June 14, 2012
the rules spelled out in RFC 2863."
::= { bfdSessPerfEntry 17 } ::= { bfdSessPerfEntry 17 }
bfdSessPerfEchoPktOutHC OBJECT-TYPE bfdSessPerfEchoPktOutHC OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the total number of BFD echo "This value represents the total number of BFD echo
messages transmitted for this BFD session." messages transmitted for this BFD session.
It MUST be equal to the least significant 32 bits of
bfdSessPerfEchoPktOut if supported, and MUST do so
the rules spelled out in RFC 2863."
::= { bfdSessPerfEntry 18 } ::= { bfdSessPerfEntry 18 }
bfdSessPerfEchoPktDropHC OBJECT-TYPE bfdSessPerfEchoPktDropHC OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the total number of BFD echo "This value represents the total number of BFD echo
messages received for this BFD session yet dropped messages received for this BFD session yet dropped
for being invalid." for being invalid.
It MUST be equal to the least significant 32 bits of
bfdSessPerfEchoPktDrop if supported, and MUST do so
the rules spelled out in RFC 2863."
::= { bfdSessPerfEntry 19 } ::= { bfdSessPerfEntry 19 }
-- BFD Session Discriminator Mapping Table -- BFD Session Discriminator Mapping Table
bfdSessDiscMapTable OBJECT-TYPE bfdSessDiscMapTable OBJECT-TYPE
SYNTAX SEQUENCE OF BfdSessDiscMapEntry SYNTAX SEQUENCE OF BfdSessDiscMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BFD Session Discriminator Mapping Table maps a "The BFD Session Discriminator Mapping Table maps a
local discriminator value to associated BFD session's local discriminator value to associated BFD session's
BfdSessIndexTC used in the bfdSessionTable." BfdSessIndexTC used in the bfdSessionTable."
::= { bfdObjects 4 } ::= { bfdObjects 4 }
bfdSessDiscMapEntry OBJECT-TYPE bfdSessDiscMapEntry OBJECT-TYPE
SYNTAX BfdSessDiscMapEntry SYNTAX BfdSessDiscMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BFD Session Discriminator Map Entry describes "The BFD Session Discriminator Map Entry describes
BFD-STD-MIB June 14, 2012
BFD session that is mapped to this BfdSessIndexTC." BFD session that is mapped to this BfdSessIndexTC."
INDEX { bfdSessDiscriminator } INDEX { bfdSessDiscriminator }
::= { bfdSessDiscMapTable 1 } ::= { bfdSessDiscMapTable 1 }
BfdSessDiscMapEntry ::= SEQUENCE { BfdSessDiscMapEntry ::= SEQUENCE {
bfdSessDiscMapIndex BfdSessIndexTC bfdSessDiscMapIndex BfdSessIndexTC,
bfdSessDiscMapStorageType StorageType,
bfdSessDiscMapRowStatus RowStatus
} }
bfdSessDiscMapIndex OBJECT-TYPE bfdSessDiscMapIndex OBJECT-TYPE
SYNTAX BfdSessIndexTC SYNTAX BfdSessIndexTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the BfdSessIndexTC referred to by "This object specifies the BfdSessIndexTC referred to by
the indices of this row. In essence, a mapping is the indices of this row. In essence, a mapping is
provided between these indexes and the BfdSessTable." provided between these indexes and the BfdSessTable."
::= { bfdSessDiscMapEntry 1 } ::= { bfdSessDiscMapEntry 1 }
bfdSessDiscMapStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this
object. Conceptual rows having the value
'permanent' need not allow write-access to any
columnar objects in the row."
::= { bfdSessDiscMapEntry 2 }
bfdSessDiscMapRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or
delete a row in this table. When a row in this
table has a row in the active(1) state, no
objects in this row can be modified except the
bfdSessDiscMapRowStatus and bfdSessDiscMapStorageType."
::= { bfdSessDiscMapEntry 3 }
-- BFD Session IP Mapping Table -- BFD Session IP Mapping Table
bfdSessIpMapTable OBJECT-TYPE bfdSessIpMapTable OBJECT-TYPE
SYNTAX SEQUENCE OF BfdSessIpMapEntry SYNTAX SEQUENCE OF BfdSessIpMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
BFD-STD-MIB June 14, 2012
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BFD Session IP Mapping Table maps given "The BFD Session IP Mapping Table maps given
bfdSessInterface, bfdSessSrcAddrType, bfdSessSrcAddr, bfdSessInterface, bfdSessSrcAddrType, bfdSessSrcAddr,
bfdSessDstAddrType and bfdSessDstAddr bfdSessDstAddrType and bfdSessDstAddr
to an associated BFD session's BfdSessIndexTC used in to an associated BFD session's BfdSessIndexTC used in
the bfdSessionTable." the bfdSessionTable."
::= { bfdObjects 5 } ::= { bfdObjects 5 }
bfdSessIpMapEntry OBJECT-TYPE bfdSessIpMapEntry OBJECT-TYPE
skipping to change at page 23, line 27 skipping to change at page 25, line 32
INDEX { INDEX {
bfdSessInterface, bfdSessInterface,
bfdSessSrcAddrType, bfdSessSrcAddrType,
bfdSessSrcAddr, bfdSessSrcAddr,
bfdSessDstAddrType, bfdSessDstAddrType,
bfdSessDstAddr bfdSessDstAddr
} }
::= { bfdSessIpMapTable 1 } ::= { bfdSessIpMapTable 1 }
BfdSessIpMapEntry ::= SEQUENCE { BfdSessIpMapEntry ::= SEQUENCE {
bfdSessIpMapIndex BfdSessIndexTC bfdSessIpMapIndex BfdSessIndexTC,
bfdSessIpMapStorageType StorageType,
bfdSessIpMapRowStatus RowStatus
} }
bfdSessIpMapIndex OBJECT-TYPE bfdSessIpMapIndex OBJECT-TYPE
SYNTAX BfdSessIndexTC SYNTAX BfdSessIndexTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the BfdSessIndexTC referred to by "This object specifies the BfdSessIndexTC referred to by
the indexes of this row. In essence, a mapping is the indexes of this row. In essence, a mapping is
provided between these indexes and the BfdSessTable." provided between these indexes and the BfdSessTable."
::= { bfdSessIpMapEntry 1 } ::= { bfdSessIpMapEntry 1 }
bfdSessIpMapStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this
object. Conceptual rows having the value
BFD-STD-MIB June 14, 2012
'permanent' need not allow write-access to any
columnar objects in the row."
::= { bfdSessIpMapEntry 2 }
bfdSessIpMapRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or
delete a row in this table. When a row in this
table has a row in the active(1) state, no
objects in this row can be modified except the
bfdSessIpMapRowStatus and bfdSessIpMapStorageType."
::= { bfdSessIpMapEntry 3 }
-- Notification Configuration -- Notification Configuration
bfdSessUp NOTIFICATION-TYPE bfdSessUp NOTIFICATION-TYPE
OBJECTS { OBJECTS {
bfdSessDiag, -- low range value bfdSessDiag, -- low range value
bfdSessDiag -- high range value bfdSessDiag -- high range value
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when the "This notification is generated when the
skipping to change at page 24, line 23 skipping to change at page 27, line 4
notification for each range of contiguous indexes in notification for each range of contiguous indexes in
an effort to minimize the emission of a large number an effort to minimize the emission of a large number
of notifications. If a notification has to be of notifications. If a notification has to be
issued for just a single bfdSessEntry, then issued for just a single bfdSessEntry, then
the instance identifier (and values) of the two the instance identifier (and values) of the two
bfdSessDiag objects MUST be the identical." bfdSessDiag objects MUST be the identical."
::= { bfdNotifications 1 } ::= { bfdNotifications 1 }
bfdSessDown NOTIFICATION-TYPE bfdSessDown NOTIFICATION-TYPE
OBJECTS { OBJECTS {
BFD-STD-MIB June 14, 2012
bfdSessDiag, -- low range value bfdSessDiag, -- low range value
bfdSessDiag -- high range value bfdSessDiag -- high range value
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when the "This notification is generated when the
bfdSessState object for one or more contiguous bfdSessState object for one or more contiguous
entries in bfdSessTable are about to enter the down(2) entries in bfdSessTable are about to enter the down(2)
or adminDown(1) states from some other state. The included or adminDown(1) states from some other state. The included
values of bfdSessDiag MUST both be set equal to this new values of bfdSessDiag MUST both be set equal to this new
skipping to change at page 25, line 22 skipping to change at page 28, line 4
-- Compliance requirement for fully compliant implementations. -- Compliance requirement for fully compliant implementations.
bfdModuleFullCompliance MODULE-COMPLIANCE bfdModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that provide full "Compliance statement for agents that provide full
support for the BFD-MIB module. Such devices can support for the BFD-MIB module. Such devices can
then be monitored and also be configured using then be monitored and also be configured using
this MIB module." this MIB module."
BFD-STD-MIB June 14, 2012
MODULE -- This module. MODULE -- This module.
MANDATORY-GROUPS { MANDATORY-GROUPS {
bfdSessionGroup, bfdSessionGroup,
bfdSessionReadOnlyGroup, bfdSessionReadOnlyGroup,
bfdSessionPerfGroup, bfdSessionPerfGroup,
bfdNotificationGroup bfdNotificationGroup
} }
skipping to change at page 26, line 15 skipping to change at page 28, line 48
DESCRIPTION "An implementation is only required to support DESCRIPTION "An implementation is only required to support
unknown(0), ipv4(1), ipv6(2) and ipv6z(4) sizes." unknown(0), ipv4(1), ipv6(2) and ipv6z(4) sizes."
OBJECT bfdSessRowStatus OBJECT bfdSessRowStatus
SYNTAX RowStatus { active(1), notInService(2) } SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2), WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
DESCRIPTION "Support for createAndWait and notReady is not DESCRIPTION "Support for createAndWait and notReady is not
required." required."
OBJECT bfdSessDiscMapRowStatus
SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) }
DESCRIPTION "Support for createAndWait and notReady is not
BFD-STD-MIB June 14, 2012
required."
OBJECT bfdSessIpMapRowStatus
SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) }
DESCRIPTION "Support for createAndWait and notReady is not
required."
::= { bfdCompliances 1 } ::= { bfdCompliances 1 }
bfdModuleReadOnlyCompliance MODULE-COMPLIANCE bfdModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance requirement for implementations that only "Compliance requirement for implementations that only
provide read-only support for BFD-MIB. Such devices provide read-only support for BFD-MIB. Such devices
can then be monitored but cannot be configured using can then be monitored but cannot be configured using
this MIB module." this MIB module."
skipping to change at page 27, line 4 skipping to change at page 30, line 4
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessDestinationUdpPort OBJECT bfdSessDestinationUdpPort
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessSourceUdpPort OBJECT bfdSessSourceUdpPort
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
BFD-STD-MIB June 14, 2012
OBJECT bfdSessEchoSourceUdpPort OBJECT bfdSessEchoSourceUdpPort
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessAdminStatus OBJECT bfdSessAdminStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessOperMode OBJECT bfdSessOperMode
MIN-ACCESS read-only MIN-ACCESS read-only
skipping to change at page 28, line 4 skipping to change at page 31, line 4
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "An implementation is only required to support DESCRIPTION "An implementation is only required to support
unknown(0), ipv4(1), ipv6(2) and ipv6z(4) sizes." unknown(0), ipv4(1), ipv6(2) and ipv6z(4) sizes."
OBJECT bfdSessDstAddrType OBJECT bfdSessDstAddrType
SYNTAX InetAddressType { unknown(0), ipv4(1), SYNTAX InetAddressType { unknown(0), ipv4(1),
ipv6(2), ipv6z(4) } ipv6(2), ipv6z(4) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Only unknown(0), ipv4(1), ipv6(2) and ipv6z(4) DESCRIPTION "Only unknown(0), ipv4(1), ipv6(2) and ipv6z(4)
support are required." support are required."
BFD-STD-MIB June 14, 2012
OBJECT bfdSessDstAddr OBJECT bfdSessDstAddr
SYNTAX InetAddress (SIZE (0|4|16|20)) SYNTAX InetAddress (SIZE (0|4|16|20))
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "An implementation is only required to support DESCRIPTION "An implementation is only required to support
unknown(0), ipv4(1), ipv6(2) and ipv6z(4) sizes." unknown(0), ipv4(1), ipv6(2) and ipv6z(4) sizes."
OBJECT bfdSessGTSM OBJECT bfdSessGTSM
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
skipping to change at page 28, line 51 skipping to change at page 31, line 52
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessAuthenticationKeyID OBJECT bfdSessAuthenticationKeyID
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessAuthenticationKey OBJECT bfdSessAuthenticationKey
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessStorType OBJECT bfdSessStorageType
BFD-STD-MIB June 14, 2012
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessRowStatus OBJECT bfdSessRowStatus
SYNTAX RowStatus { active(1) } SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT bfdSessDiscMapStorageType
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT bfdSessDiscMapRowStatus
SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT bfdSessIpMapStorageType
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
OBJECT bfdSessIpMapRowStatus
SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
::= { bfdCompliances 2 } ::= { bfdCompliances 2 }
-- Units of conformance. -- Units of conformance.
bfdSessionGroup OBJECT-GROUP bfdSessionGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bfdAdminStatus, bfdAdminStatus,
bfdSessNotificationsEnable, bfdSessNotificationsEnable,
bfdSessVersionNumber, bfdSessVersionNumber,
bfdSessType, bfdSessType,
skipping to change at page 29, line 31 skipping to change at page 33, line 4
bfdSessEchoSourceUdpPort, bfdSessEchoSourceUdpPort,
bfdSessAdminStatus, bfdSessAdminStatus,
bfdSessOperMode, bfdSessOperMode,
bfdSessDemandModeDesiredFlag, bfdSessDemandModeDesiredFlag,
bfdSessControlPlaneIndepFlag, bfdSessControlPlaneIndepFlag,
bfdSessMultipointFlag, bfdSessMultipointFlag,
bfdSessInterface, bfdSessInterface,
bfdSessSrcAddrType, bfdSessSrcAddrType,
bfdSessSrcAddr, bfdSessSrcAddr,
bfdSessDstAddrType, bfdSessDstAddrType,
BFD-STD-MIB June 14, 2012
bfdSessDstAddr, bfdSessDstAddr,
bfdSessGTSM, bfdSessGTSM,
bfdSessGTSMTTL, bfdSessGTSMTTL,
bfdSessDesiredMinTxInterval, bfdSessDesiredMinTxInterval,
bfdSessReqMinRxInterval, bfdSessReqMinRxInterval,
bfdSessReqMinEchoRxInterval, bfdSessReqMinEchoRxInterval,
bfdSessDetectMult, bfdSessDetectMult,
bfdSessAuthPresFlag, bfdSessAuthPresFlag,
bfdSessAuthenticationType, bfdSessAuthenticationType,
bfdSessAuthenticationKeyID, bfdSessAuthenticationKeyID,
bfdSessAuthenticationKey, bfdSessAuthenticationKey,
bfdSessStorType, bfdSessStorageType,
bfdSessRowStatus bfdSessRowStatus,
bfdSessDiscMapStorageType,
bfdSessDiscMapRowStatus,
bfdSessIpMapStorageType,
bfdSessIpMapRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for BFD sessions." "Collection of objects needed for BFD sessions."
::= { bfdGroups 1 } ::= { bfdGroups 1 }
bfdSessionReadOnlyGroup OBJECT-GROUP bfdSessionReadOnlyGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bfdSessDiscriminator, bfdSessDiscriminator,
bfdSessRemoteDiscr, bfdSessRemoteDiscr,
skipping to change at page 30, line 27 skipping to change at page 34, line 4
"Collection of read-only objects needed for BFD sessions." "Collection of read-only objects needed for BFD sessions."
::= { bfdGroups 2 } ::= { bfdGroups 2 }
bfdSessionPerfGroup OBJECT-GROUP bfdSessionPerfGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bfdSessPerfCtrlPktIn, bfdSessPerfCtrlPktIn,
bfdSessPerfCtrlPktOut, bfdSessPerfCtrlPktOut,
bfdSessPerfCtrlPktDrop, bfdSessPerfCtrlPktDrop,
bfdSessPerfCtrlPktDropLastTime, bfdSessPerfCtrlPktDropLastTime,
bfdSessPerfEchoPktIn, bfdSessPerfEchoPktIn,
BFD-STD-MIB June 14, 2012
bfdSessPerfEchoPktOut, bfdSessPerfEchoPktOut,
bfdSessPerfEchoPktDrop, bfdSessPerfEchoPktDrop,
bfdSessPerfEchoPktDropLastTime, bfdSessPerfEchoPktDropLastTime,
bfdSessUpTime, bfdSessUpTime,
bfdSessPerfLastSessDownTime, bfdSessPerfLastSessDownTime,
bfdSessPerfLastCommLostDiag, bfdSessPerfLastCommLostDiag,
bfdSessPerfSessUpCount, bfdSessPerfSessUpCount,
bfdSessPerfDiscTime bfdSessPerfDiscTime
} }
STATUS current STATUS current
skipping to change at page 31, line 23 skipping to change at page 34, line 51
bfdSessDown bfdSessDown
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of notifications implemented in this "Set of notifications implemented in this
module." module."
::= { bfdGroups 5 } ::= { bfdGroups 5 }
END END
7. Security Considerations 6. Security Considerations
BFD-STD-MIB June 14, 2012
As BFD may be tied into the stability of the network infrastructure As BFD may be tied into the stability of the network infrastructure
(such as routing protocols), the effects of an attack on a BFD (such as routing protocols), the effects of an attack on a BFD
session may be very serious. This ultimately has denial-of-service session may be very serious. This ultimately has denial-of-service
effects, as links may be declared to be down (or falsely declared to effects, as links may be declared to be down (or falsely declared to
be up.) As such, improper manipulation of the objects represented by be up.) As such, improper manipulation of the objects represented by
this MIB may result in denial of service to a large number of end- this MIB may result in denial of service to a large number of end-
users. users.
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
skipping to change at page 32, line 25 skipping to change at page 36, line 4
disruption of traffic on the network. This is especially true if disruption of traffic on the network. This is especially true if
an unauthorized user configures enough tables to invoke a denial an unauthorized user configures enough tables to invoke a denial
of service attack on the device where they are configured, or on a of service attack on the device where they are configured, or on a
remote device where the sessions terminate. remote device where the sessions terminate.
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
BFD-STD-MIB June 14, 2012
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o The bfdSessPerfTable both allows access to the performance o The bfdSessPerfTable both allows access to the performance
characteristics of BFD sessions. Network administrators not characteristics of BFD sessions. Network administrators not
wishing to show this information should consider this table wishing to show this information should consider this table
sensitive. sensitive.
The bfdSessAuthenticationType, bfdSessAuthenticationKeyID, and The bfdSessAuthenticationType, bfdSessAuthenticationKeyID, and
bfdSessAuthenticationKey objects hold security methods and associated bfdSessAuthenticationKey objects hold security methods and associated
skipping to change at page 33, line 9 skipping to change at page 36, line 40
authentication and privacy". authentication and privacy".
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module, is properly configured to give access to instance of this MIB module, is properly configured to give access to
the objects only to those principals "users" that have legitimate the objects only to those principals "users" that have legitimate
rights to indeed GET or SET "change/create/delete" them. rights to indeed GET or SET "change/create/delete" them.
8. IANA Considerations 7. IANA Considerations
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
bfdMib { mib-2 XXX } bfdMib { mib-2 XXX }
[Editor's Note (to be removed prior to publication): the IANA is [Editor's Note (to be removed prior to publication): the IANA is
requested to assign a value for "XXX" under the 'mib-2' subtree and requested to assign a value for "XXX" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the to record the assignment in the SMI Numbers registry. When the
BFD-STD-MIB June 14, 2012
assignment has been made, the RFC Editor is asked to replace "XXX" assignment has been made, the RFC Editor is asked to replace "XXX"
(here and in the MIB module) with the assigned value and to remove (here and in the MIB module) with the assigned value and to remove
this note.] this note.]
This document also requests IANA to manage the registry for the This document also requests IANA to manage the registry for the
BfdDiagTC object. BfdDiagTC object.
9. References 8. References
9.1. Normative References 8.1. Normative References
[BFD] Katz, D. and D. Ward, "Bidirectional Forwarding [BFD] Katz, D. and D. Ward, "Bidirectional Forwarding
Detection (BFD)", RFC 5880, June 2010. Detection (BFD)", RFC 5880, June 2012.
[BFD-1HOP] Katz, D. and D. Ward, "Bidirectional Forwarding [BFD-1HOP] Katz, D. and D. Ward, "Bidirectional Forwarding
Detection (BFD) for IPv4 and IPv6 (Single Hop)", Detection (BFD) for IPv4 and IPv6 (Single Hop)",
RFC 5881, June 2010. RFC 5881, June 2012.
[BFD-MH] Katz, D. and D. Ward, "Bidirectional Forwarding [BFD-MH] Katz, D. and D. Ward, "Bidirectional Forwarding
Detection (BFD) for Multihop Paths", RFC 5883, Detection (BFD) for Multihop Paths", RFC 5883,
June 2010. June 2012.
[BFD-TC] Nadeau, T., Ali, Z. and N. Akiya, "Definitions of Textual [BFD-TC] Nadeau, T., Ali, Z. and N. Akiya, "Definitions of Textual
Conventions (TCs) for Bidirectional Forwarding Detection Conventions (TCs) for Bidirectional Forwarding Detection
(BFD) Management", (BFD) Management",
ID Document: draft-ietf-bfd-tc-mib-01.txt, June 2010. ID Document: draft-ietf-bfd-tc-mib-01.txt, June 2012.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
9.2. Informative References 8.2. Informative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
BFD-STD-MIB June 14, 2012
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network [RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network
Management Protocol (SNMP) Applications", STD 62, Management Protocol (SNMP) Applications", STD 62,
RFC 3413, December 2002. RFC 3413, December 2002.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network Schoenwaelder, "Textual Conventions for Internet Network
skipping to change at page 34, line 43 skipping to change at page 38, line 28
Appendix A. Acknowledgments Appendix A. Acknowledgments
We would like to thank David Ward, Jeffrey Haas, Reshad Rahman, David We would like to thank David Ward, Jeffrey Haas, Reshad Rahman, David
Toscano, Sylvain Masse, Mark Tooker, and Kiran Koushik Agrahara Toscano, Sylvain Masse, Mark Tooker, and Kiran Koushik Agrahara
Sreenivasa for their comments and suggestions. Sreenivasa for their comments and suggestions.
Authors' Addresses Authors' Addresses
Thomas D. Nadeau Thomas D. Nadeau
BT Juniper Networks
BT Centre
81 Newgate Street Email: tnadeau@juniper.net
London EC1A 7AJ
United Kingdom
Email: tnadeau@lucidvision.com
Zafar Ali Zafar Ali
Cisco Systems, Inc. Cisco Systems, Inc.
2000 Innovation Drive 2000 Innovation Drive
Kanata, Ontario K2K 3E8 Kanata, Ontario K2K 3E8
Canada Canada
Email: zali@cisco.com Email: zali@cisco.com
Nobo Akiya Nobo Akiya
Cisco Systems G.K. Cisco Systems G.K.
 End of changes. 101 change blocks. 
131 lines changed or deleted 319 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/