draft-ietf-bfd-mib-03.txt   draft-ietf-bfd-mib-04.txt 
BFD Working Group Thomas D. Nadeau BFD Working Group Thomas D. Nadeau
Standard Track Zafar Ali INTERNET-DRAFT BT
Intended status: Standards Track Zafar Ali
Cisco Systems, Inc. Cisco Systems, Inc.
Nobo Akiya
Cisco Systems, G.K.
Expires: April 2007 October 2006 Expires: August 24, 2008 February 25, 2008
Bidirectional Forwarding Detection Management Information Base Bidirectional Forwarding Detection Management Information Base
draft-ietf-bfd-mib-03.txt draft-ietf-bfd-mib-04.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
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 other Task Force (IETF), its areas, and its working groups. Note that other
skipping to change at page 1, line 43 skipping to change at page 1, line 46
Abstract Abstract
This draft defines a portion of the Management Information Base This draft defines a portion of the Management Information Base
(MIB) for use with network management protocols in the Internet (MIB) for use with network management protocols in the Internet
community. In particular, it describes managed objects for modeling community. In particular, it describes managed objects for modeling
Bidirectional Forwarding Detection (BFD) protocol [BFD]. Bidirectional Forwarding Detection (BFD) protocol [BFD].
Contents Contents
1. Introduction..................................................2 1. Introduction..................................................2
2. Terminology...................................................3 2. Terminology...................................................2
3. The Internet-Standard Management Framework....................3 3. The Internet-Standard Management Framework....................2
3. Brief Description of MIB Objects..............................3 4. Brief Description of MIB Objects..............................3
3.1 General Variables.............................................3 4.1 General Variables.............................................3
3.2 Session Table (bfdSessionTable)...............................3 4.2 Session Table (bfdSessionTable)...............................3
3.3 Session Performance Table (bfdSessionPerfTable)...............3
3.4 Session Mapping Table (bfdSessMapTable).......................3 BFD MIB February 25, 2008
BFD MIB October 20, 2006
4.3 Session Performance Table (bfdSessionPerfTable)...............3
4.4 BFD Session Discriminator Mapping Table (bfdSessDiscMapTable).3
4.5 BFD Session IP Mapping Table (bfdSessIpMapTable)..............3
5. BFD MIB Module Definitions....................................4 5. BFD MIB Module Definitions....................................4
6. Security Considerations......................................21 6. Security Considerations......................................23
7. IANA Considerations..........................................41 7. IANA Considerations..........................................24
7.1 IANA Considerations for BFD-STD-MIB..........................41 7.1 IANA Considerations for BFD-STD-MIB..........................24
8. References...................................................23 8. References...................................................24
8.1 Normative References.........................................23 8.1 Normative References.........................................24
8.2 Informative References.......................................23 8.2 Informative References.......................................25
9. Acknowledgements.............................................22 9. Acknowledgements.............................................25
10. Authors' Addresses...........................................23 10. Authors' Addresses...........................................25
11. Intellectual Property Statement..............................41 11. Intellectual Property Statement..............................26
12. Full Copyright Statement.....................................24 12. Full Copyright Statement.....................................26
1. Introduction 1. Introduction
This memo defines an portion of the Management This memo defines an portion of the Management Information Base
Information Base (MIB) for use with network management protocols (MIB) for use with network management protocols in the Internet
in the Internet community. In particular, it describes managed community. In particular, it describes managed objects to configure
objects to configure and/or monitor Bi-Directional Forwarding and/or monitor Bi-Directional Forwarding Detection for [BFD] and
Detection on devices supporting this feature. [BFD-MH],BFD versions 0 and/or 1, on devices supporting this
feature.
-- Ed Note: TBA, support for [BFD-LSP].
This document adopts the definitions, acronyms and mechanisms This document adopts the definitions, acronyms and mechanisms
described in [BFD], [BFD-MH] and [BFD-LSP]. Unless otherwise described in [BFD], [BFD-MH] and [BFD-LSP]. Unless otherwise
stated, the mechanisms described therein will not be re-described stated, the mechanisms described therein will not be re-described
here. here.
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.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
skipping to change at page 2, line 46 skipping to change at page 3, line 5
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
[RFC2119]. [RFC2119].
2. Terminology 2. Terminology
This document adopts the definitions, acronyms and mechanisms This document adopts the definitions, acronyms and mechanisms
described in [BFD], [BFD-MH] and [BFD-LSP]. Unless otherwise described in [BFD], [BFD-MH] and [BFD-LSP]. Unless otherwise
stated, the mechanisms described therein will not be re-described stated, the mechanisms described therein will not be re-described
here. here.
BFD MIB February 25, 2008
3. The Internet-Standard Management Framework 3. 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
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [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
BFD MIB October 20, 2006
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,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
4. 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 the BFD document [BFD]. are derived from [BFD] and [BFD-MH].
4.1 General Variables 4.1 General Variables
The General Variables are used to identify parameters that are The General Variables are used to identify parameters that are
global to the BFD process. global to the BFD process.
4.2 Session Table (bfdSessionTable) 4.2 Session Table (bfdSessionTable)
The session table is used to identify a BFD session between a pair The session table is used to identify a BFD session between a pair
of nodes. of nodes.
4.3 Session Performance Table (bfdSessionPerfTable) 4.3 Session Performance Table (bfdSessionPerfTable)
The session performance table is used for collecting BFD The session performance table is used for collecting BFD
performance counts on a per session basis. This table is an AUGMENT performance counts on a per session basis. This table is an AUGMENT
to the bfdSessionTable. to the bfdSessionTable.
3.4 Session Mapping Table (bfdSessMapTable) 4.4 BFD Session Discriminator Mapping Table (bfdSessDiscMapTable)
The BFD Session Mapping Table maps the complex indexing of the BFD The BFD Session Discriminator Mapping Table maps a local
sessions to the flat BFDIndex used in the BfdSessionTable. discriminator value to associated BFD sessions' BfdSessIndexTC used
in the bfdSessionTable.
4.5 BFD Session IP Mapping Table (bfdSessIpMapTable)
The BFD Session IP Mapping Table maps, given bfdSessInterface,
bfdSessAddrType, and bfdSessAddr, to an associated BFD sessions'
BfdSessIndexTC used in the bfdSessionTable. This table SHOULD
contains those BFD sessions are of IP type.
BFD MIB February 25, 2008
5. 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.
[RFC2578], [RFC2579], [RFC2580], [RFC3291], and [RFC3413]. [RFC2578], [RFC2579], [RFC2580], [RFC2863], [RFC4001], and [RFC3413].
BFD-STD-MIB DEFINITIONS ::= BEGIN BFD-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Unsigned32, Counter32, Counter64, Unsigned32, Counter32, Counter64,
NOTIFICATION-TYPE, mib-2 NOTIFICATION-TYPE, mib-2
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION, TruthValue, TEXTUAL-CONVENTION, TruthValue,
RowStatus, StorageType, TimeStamp RowStatus, StorageType, TimeStamp
BFD MIB October 20, 2006
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP, MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
InterfaceIndex
FROM IF-MIB -- [RFC2863]
InetAddress, InetAddressType, InetPortNumber InetAddress, InetAddressType, InetPortNumber
FROM INET-ADDRESS-MIB -- [RFC3291] FROM INET-ADDRESS-MIB -- [RFC4001]
; ;
bfdMIB MODULE-IDENTITY bfdMIB MODULE-IDENTITY
LAST-UPDATED "200507221200Z" -- 04 July 2005 12:00:00 EST LAST-UPDATED "200802231200Z" -- 23 February 2008 12:00:00 EST
ORGANIZATION "IETF" ORGANIZATION "IETF"
CONTACT-INFO CONTACT-INFO
" Thomas D. Nadeau " Thomas D. Nadeau
Cisco Systems, Inc. BT
Email: tnadeau@cisco.com Email: tom.nadeau@bt.com
Zafar Ali Zafar Ali
Cisco Systems, Inc. Cisco Systems, Inc.
Email: zali@cisco.com Email: zali@cisco.com
Nobo Akiya
Cisco Systems, G.K.
Email: nobo@cisco.com
" "
DESCRIPTION DESCRIPTION
"Bidirectional Forwarding Management Information Base." "Bidirectional Forwarding Management Information Base."
BFD MIB February 25, 2008
-- Revision history. -- Revision history.
REVISION REVISION
"200508221200Z" -- 04 August 2005 12:00:00 EST "200802231200Z" -- 23 February 2008 12:00:00 EST
DESCRIPTION DESCRIPTION
"Initial version. Published as RFC xxxx." -- RFC-editor pls fill "Initial version. Published as RFC xxxx." -- RFC-editor pls fill
-- in xxxx -- in xxxx
::= { mib-2 XXX } -- assigned by IANA, see section 18.1 for details ::= { mib-2 XXX } -- 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 }
bfdObjects OBJECT IDENTIFIER ::= { bfdMIB 1 } bfdObjects OBJECT IDENTIFIER ::= { bfdMIB 1 }
bfdConformance OBJECT IDENTIFIER ::= { bfdMIB 3 } bfdConformance OBJECT IDENTIFIER ::= { bfdMIB 3 }
bfdScalarObjects OBJECT IDENTIFIER ::= { bfdObjects 1 } bfdScalarObjects OBJECT IDENTIFIER ::= { bfdObjects 1 }
-- Textual Conventions -- Textual Conventions
BfdSessIndexTC ::= TEXTUAL-CONVENTION BfdSessIndexTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
BFD MIB October 20, 2006
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index used to uniquely identify BFD sessions." "An index used to uniquely identify BFD sessions."
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
BfdInterval ::= TEXTUAL-CONVENTION BfdInterval ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BFD interval delay in microseconds." "The BFD interval delay in microseconds."
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
skipping to change at page 5, line 33 skipping to change at page 6, line 5
controlDetectionTimeExpired(2), controlDetectionTimeExpired(2),
echoFunctionFailed(3), echoFunctionFailed(3),
neighborSignaledSessionDown(4), neighborSignaledSessionDown(4),
forwardingPlaneReset(5), forwardingPlaneReset(5),
pathDown(6), pathDown(6),
concatenatedPathDown(7), concatenatedPathDown(7),
administrativelyDown(8), administrativelyDown(8),
reverseConcatenatedPathDown (9) reverseConcatenatedPathDown (9)
} }
BFD MIB February 25, 2008
-- BFD General Variables -- BFD General Variables
-- These parameters apply globally to the Router's -- These parameters apply globally to the Router's
-- BFD Process. -- BFD Process.
bfdAdminStatus OBJECT-TYPE bfdAdminStatus OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) } SYNTAX INTEGER { enabled(1), 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 router.
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 }
skipping to change at page 5, line 50 skipping to change at page 6, line 25
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 router.
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 }
bfdVersionNumber OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
BFD MIB October 20, 2006
DESCRIPTION
"The current version number of the BFD protocol."
REFERENCE
" BFD Version 0 (draft-katz-ward-bfd-02.txt)"
DEFVAL { 0 }
::= { bfdScalarObjects 3 }
-- BFD Session Table -- BFD Session Table
-- 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)" "BFD Version 0 (draft-katz-ward-bfd-02.txt) and
BFD Version 1 (draft-ietf-bfd-base-07.txt)"
::= { 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
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,
bfdSessApplicationId Unsigned32, bfdSessVersionNumber Unsigned32,
bfdSessType INTEGER,
bfdSessDiscriminator Unsigned32, bfdSessDiscriminator Unsigned32,
bfdSessRemoteDiscr Unsigned32, bfdSessRemoteDiscr Unsigned32,
BFD MIB February 25, 2008
bfdSessUdpPort InetPortNumber, bfdSessUdpPort InetPortNumber,
bfdSessState INTEGER, bfdSessState INTEGER,
bfdSessRemoteHeardFlag TruthValue, bfdSessRemoteHeardFlag TruthValue,
bfdSessDiag Unsigned32, bfdSessDiag BfdDiag,
bfdSessOperMode INTEGER, bfdSessOperMode INTEGER,
bfdSessDemandModeDesiredFlag TruthValue, bfdSessDemandModeDesiredFlag TruthValue,
bfdSessEchoFuncModeDesiredFlag TruthValue, bfdSessEchoFuncModeDesiredFlag TruthValue,
bfdSessControlPlanIndepFlag TruthValue, bfdSessControlPlanIndepFlag TruthValue,
bfdSessInterface InterfaceIndex,
bfdSessAddrType InetAddressType, bfdSessAddrType InetAddressType,
bfdSessAddr InetAddress, bfdSessAddr InetAddress,
bfdSessDesiredMinTxInterval BfdInterval, bfdSessDesiredMinTxInterval BfdInterval,
bfdSessReqMinRxInterval BfdInterval, bfdSessReqMinRxInterval BfdInterval,
BFD MIB October 20, 2006
bfdSessReqMinEchoRxInterval BfdInterval, bfdSessReqMinEchoRxInterval BfdInterval,
bfdSessDetectMult Unsigned32, bfdSessDetectMult Unsigned32,
bfdSessStorType StorageType, bfdSessStorType StorageType,
bfdSessRowStatus RowStatus, bfdSessRowStatus RowStatus,
bfdSessAuthPresFlag TruthValue, bfdSessAuthPresFlag TruthValue,
bfdSessAuthenticationType INTEGER bfdSessAuthenticationType INTEGER
} }
bfdSessIndex OBJECT-TYPE bfdSessIndex OBJECT-TYPE
SYNTAX BfdSessIndexTC SYNTAX BfdSessIndexTC
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
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 }
bfdSessApplicationId OBJECT-TYPE bfdVersionNumber OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains an index used to indicate "The version number of the BFD protocol that this session
a local application which owns or maintains this is running in."
BFD session. For instance, the MPLS VPN process may REFERENCE
maintain a subset of the total number of BFD "BFD Version 0 (draft-katz-ward-bfd-02.txt) and
sessions. This application ID provides a convenient BFD Version 1 (draft-ietf-bfd-base-07.txt)"
way to segregate sessions by the applications which DEFVAL { 0 }
maintain them."
::= { bfdSessEntry 2 } ::= { bfdSessEntry 2 }
bfdSessType OBJECT-TYPE
SYNTAX INTEGER {
singleHop(1),
multiHop(2)
}
BFD MIB February 25, 2008
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of this BFD session."
::= { bfdSessEntry 3 }
bfdSessDiscriminator OBJECT-TYPE bfdSessDiscriminator OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the local discriminator for this BFD "This object specifies the local discriminator for this BFD
session, used to uniquely identify it." session, used to uniquely identify it."
::= { bfdSessEntry 3 } ::= { bfdSessEntry 4 }
bfdSessRemoteDiscr OBJECT-TYPE bfdSessRemoteDiscr OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (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." by the remote system for this BFD session."
::= { bfdSessEntry 4 } ::= { bfdSessEntry 5 }
BFD MIB October 20, 2006
bfdSessUdpPort OBJECT-TYPE bfdSessUdpPort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The UDP Port for BFD. The default value is the "The destination UDP Port for BFD. The default value is
well-known value for this port." the well-known value for this port. BFD State failing(5)
is only applicable if this BFD session is running
version 0"
REFERENCE REFERENCE
"draft-katz-ward-bfd-02.txt and "draft-katz-ward-bfd-02.txt and
draft-raggarwa-mpls-bfd-00.txt" draft-raggarwa-mpls-bfd-00.txt"
DEFVAL { 0 } DEFVAL { 0 }
::= { bfdSessEntry 5 } ::= { bfdSessEntry 6 }
bfdSessState OBJECT-TYPE bfdSessState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
adminDown(1), adminDown(1),
down(2), down(2),
init(3), init(3),
up(4) up(4),
failing(5)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
BFD MIB February 25, 2008
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The perceived state of the BFD session." "The perceived state of the BFD session."
::= { bfdSessEntry 6 } ::= { bfdSessEntry 7 }
bfdSessRemoteHeardFlag OBJECT-TYPE bfdSessRemoteHeardFlag OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
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(0) if the local system remote system, and is set to false(0) 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. Value placed in this object is valid only
::= { bfdSessEntry 7 } if this session is running in BFD version 0."
REFERENCE
"BFD Version 0 (draft-katz-ward-bfd-02.txt) and
BFD Version 1 (draft-ietf-bfd-base-07.txt)"
DEFVAL { 0 }
::= { bfdSessEntry 8 }
bfdSessDiag OBJECT-TYPE bfdSessDiag OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX BfdDiag
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
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(1) for the last transition of the session from up(4)
BFD MIB October 20, 2006
to some other state." to some other state."
::= { bfdSessEntry 8 } ::= { bfdSessEntry 9 }
bfdSessOperMode OBJECT-TYPE bfdSessOperMode OBJECT-TYPE
SYNTAX INTEGER { asyncModeWEchoFun(1), SYNTAX INTEGER { asyncModeWEchoFun(1),
asynchModeWOEchoFun(2), asynchModeWOEchoFun(2),
demandModeWEchoFunction(3), demandModeWEchoFunction(3),
demandModeWOEchoFunction(4) demandModeWOEchoFunction(4)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
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.
BFD MIB February 25, 2008
A value of AsyncModeWEchoFun(1) ... A value of AsyncModeWEchoFun(1) ...
A value of AsynchModeWOEchoFun(2) ... A value of AsynchModeWOEchoFun(2) ...
A value of DemandModeWEchoFunction(3) ... A value of DemandModeWEchoFunction(3) ...
A value of DemandModeWOEchoFunction(4) ... A value of DemandModeWOEchoFunction(4) ...
" "
::= { bfdSessEntry 9 } ::= { bfdSessEntry 10 }
bfdSessDemandModeDesiredFlag OBJECT-TYPE bfdSessDemandModeDesiredFlag 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 Demand mode. Specifically, it is set desire to use Demand mode. Specifically, it is set
to true(1) if the local system wishes to use to true(1) if the local system wishes to use
Demand mode or false(0) if not" Demand mode or false(0) if not"
DEFVAL { false } DEFVAL { false }
::= { bfdSessEntry 10 } ::= { bfdSessEntry 11 }
bfdSessEchoFuncModeDesiredFlag OBJECT-TYPE bfdSessEchoFuncModeDesiredFlag 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 Echo mode. Specifically, it is set desire to use Echo mode. Specifically, it is set
to true(1) if the local system wishes to use to true(1) if the local system wishes to use
Echo mode or false(0) if not" Echo mode or false(0) if not"
DEFVAL { false } DEFVAL { false }
::= { bfdSessEntry 11 } ::= { bfdSessEntry 12 }
bfdSessControlPlanIndepFlag OBJECT-TYPE bfdSessControlPlanIndepFlag OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
BFD MIB October 20, 2006
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
ability to continue to function through a disruption of ability to continue to function through a disruption of
the control plane. Specifically, it is set the control plane. Specifically, it is set
to true(1) if the local system BFD implementation is to true(1) if the local system BFD implementation is
independent of the control plane. Otherwise, the independent of the control plane. Otherwise, the
value is set to false(0)" value is set to false(0)"
DEFVAL { false } DEFVAL { false }
::= { bfdSessEntry 12 } ::= { bfdSessEntry 13 }
BFD MIB February 25, 2008
bfdSessInterface OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an interface index used to indicate
the interface which this BFD session is running on. This
value can be zero if there are no interface associated
with this BFD session"
::= { bfdSessEntry 14 }
bfdSessAddrType OBJECT-TYPE bfdSessAddrType 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 of the interface "This object specifies IP address type of the neighboring IP
associated with this BFD session. address which is being monitored with this BFD session.
Only values unknown(0), ipv4(1) or ipv6(2) Only values unknown(0), ipv4(1) or ipv6(2)
have to be supported. have to be supported.
A value of unknown(0) is allowed only when A value of unknown(0) is allowed only when
the outgoing interface is of type point-to-point, or the outgoing interface is of type point-to-point, or
when the BFD session is not associated with a specific when the BFD session is not associated with a specific
interface. interface.
If any other unsupported values are attempted in a set If any other unsupported values are attempted in a set
operation, the agent MUST return an inconsistentValue operation, the agent MUST return an inconsistentValue
error. error.
" "
::= { bfdSessEntry 13 } ::= { bfdSessEntry 15 }
bfdSessAddr OBJECT-TYPE bfdSessAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies IP address of the interface "This object specifies the neighboring IP address which is
associated with this BFD session. being monitored with this BFD session.
It can also be used to enabled BFD on a specific It can also be used to enabled BFD on a specific
interface. The value is set to zero when BFD session is not interface. The value is set to zero when BFD session is not
associated with a specific interface. " associated with a specific interface. "
::= { bfdSessEntry 14 } ::= { bfdSessEntry 16 }
BFD MIB February 25, 2008
bfdSessDesiredMinTxInterval OBJECT-TYPE bfdSessDesiredMinTxInterval OBJECT-TYPE
SYNTAX BfdInterval SYNTAX BfdInterval
BFD MIB October 20, 2006
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 when microseconds, that the local system would like to use when
transmitting BFD Control packets." transmitting BFD Control packets."
::= { bfdSessEntry 15 } ::= { bfdSessEntry 17 }
bfdSessReqMinRxInterval OBJECT-TYPE bfdSessReqMinRxInterval OBJECT-TYPE
SYNTAX BfdInterval SYNTAX BfdInterval
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." local system is capable of supporting."
::= { bfdSessEntry 16 } ::= { bfdSessEntry 18 }
bfdSessReqMinEchoRxInterval OBJECT-TYPE bfdSessReqMinEchoRxInterval OBJECT-TYPE
SYNTAX BfdInterval SYNTAX BfdInterval
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." system is capable of supporting."
::= { bfdSessEntry 17 } ::= { bfdSessEntry 19 }
bfdSessDetectMult OBJECT-TYPE bfdSessDetectMult OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
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 18 } ::= { bfdSessEntry 20 }
bfdSessStorType OBJECT-TYPE bfdSessStorType 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 19 } ::= { bfdSessEntry 21 }
bfdSessRowStatus OBJECT-TYPE BFD MIB February 25, 2008
BFD MIB October 20, 2006
bfdSessRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table. When a row in this delete a row in this table. When a row in this
table has a row in the active(1) state, no table has a row in the active(1) state, no
objects in this row can be modified except the objects in this row can be modified except the
bfdSessRowStatus and bfdSessStorageType." bfdSessRowStatus and bfdSessStorageType."
::= { bfdSessEntry 20 } ::= { bfdSessEntry 22 }
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(0) if not" to be authenticated or false(0) if not"
DEFVAL { false } DEFVAL { false }
::= { bfdSessEntry 21 } ::= { bfdSessEntry 23 }
bfdSessAuthenticationType OBJECT-TYPE bfdSessAuthenticationType OBJECT-TYPE
SYNTAX INTEGER { simplePassword(1), SYNTAX INTEGER { simplePassword(1),
keyedMD5(2), keyedMD5(2),
meticulousKeyedMD5(3), meticulousKeyedMD5(3),
keyedSHA1(4), keyedSHA1(4),
meticulousKeyedSHA1(5) meticulousKeyedSHA1(5)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Authentication Type used for this BFD session. This "The Authentication Type used for this BFD session. This
field is valid only when the Authentication Present bit is set" field is valid only when the Authentication Present bit is set"
::= { bfdSessEntry 22 } ::= { bfdSessEntry 24 }
-- BFD Session Performance Table -- BFD Session Performance Table
bfdSessPerfTable OBJECT-TYPE bfdSessPerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF BfdSessPerfEntry SYNTAX SEQUENCE OF BfdSessPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies BFD Session performance counters." "This table specifies BFD Session performance counters."
::= { bfdObjects 3 } ::= { bfdObjects 3 }
bfdSessPerfEntry OBJECT-TYPE BFD MIB February 25, 2008
BFD MIB October 20, 2006
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 for "An entry in this table is created by a BFD-enabled node for
every BFD Session. bfdCounterDiscontinuityTime is used to every BFD Session. bfdCounterDiscontinuityTime 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 }
skipping to change at page 13, line 50 skipping to change at page 15, line 5
::= { bfdSessPerfEntry 1 } ::= { bfdSessPerfEntry 1 }
bfdSessPerfPktOut OBJECT-TYPE bfdSessPerfPktOut 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 messages sent for this BFD session." "The total number of BFD messages sent for this BFD session."
::= { bfdSessPerfEntry 2 } ::= { bfdSessPerfEntry 2 }
BFD MIB February 25, 2008
bfdSessUpTime OBJECT-TYPE bfdSessUpTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
BFD MIB October 20, 2006
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 3 } ::= { bfdSessPerfEntry 3 }
bfdSessPerfLastSessDownTime OBJECT-TYPE bfdSessPerfLastSessDownTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 14, line 50 skipping to change at page 16, line 5
bfdSessPerfDiscTime OBJECT-TYPE bfdSessPerfDiscTime 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 any one or more of the session counters suffered which any one or more of the session counters suffered
a discontinuity. a discontinuity.
BFD MIB February 25, 2008
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 occurred the BfdSessPerfTable. If no such discontinuities have occurred
since the last re-initialization of the local management since the last re-initialization of the local management
BFD MIB October 20, 2006
subsystem, then this object contains a zero value." subsystem, then this object contains a zero value."
::= { bfdSessPerfEntry 7 } ::= { bfdSessPerfEntry 7 }
bfdSessPerfPktInHC OBJECT-TYPE bfdSessPerfPktInHC 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 messages "This value represents the total number of BFD messages
received for this BFD session. It MUST be equal to the received for this BFD session. It MUST be equal to the
skipping to change at page 15, line 34 skipping to change at page 16, line 39
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the total number of "This value represents the total number of
total number of BFD messages transmitted for this total number of BFD messages transmitted for this
BFD session. It MUST be equal to the BFD session. It MUST be equal to the
least significant 32 bits of bfdSessPerfPktIn least significant 32 bits of bfdSessPerfPktIn
if bfdSessPerfPktOutHC is supported according to if bfdSessPerfPktOutHC is supported according to
the rules spelled out in RFC2863." the rules spelled out in RFC2863."
::= { bfdSessPerfEntry 9 } ::= { bfdSessPerfEntry 9 }
-- BFD Session Mapping Table -- BFD Session Discriminator Mapping Table
bfdSessMapTable OBJECT-TYPE bfdSessDiscMapTable OBJECT-TYPE
SYNTAX SEQUENCE OF BfdSessMapEntry SYNTAX SEQUENCE OF BfdSessDiscMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BFD Session Mapping Table maps the complex "The BFD Session Discriminator Mapping Table maps a
indexing of the BFD sessions to the flat local discriminator value to associated BFD sessions'
BFDIndex used in the BfdSessionTable. BfdSessIndexTC used in the bfdSessionTable."
::= { bfdObjects 4 }
Implementors need to be aware that if the value of BFD MIB February 25, 2008
the bfdSessAddr (an OID) has more
that 111 sub-identifiers, then OIDs of column
instances in this table will have more than 128
sub-identifiers and cannot be accessed using SNMPv1,
SNMPv2c, or SNMPv3.
"
BFD MIB October 20, 2006
REFERENCE bfdSessDiscMapEntry OBJECT-TYPE
"BFD Version 0 (draft-katz-ward-bfd-02.txt)" SYNTAX BfdSessDiscMapEntry
::= { bfdObjects 4 } MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The BFD Session Discriminator Map Entry describes
BFD session that is mapped to this BfdSessIndexTC."
INDEX { bfdSessDiscriminator }
::= { bfdSessDiscMapTable 1 }
bfdSessMapEntry OBJECT-TYPE BfdSessDiscrMapEntry ::= SEQUENCE {
SYNTAX BfdSessMapEntry bfdSessDiscMapIndex BfdSessIndexTC
}
bfdSessDiscMapIndex OBJECT-TYPE
SYNTAX BfdSessIndexTC
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the BfdIndex referred to by
the indexes of this row. In essence, a mapping is
provided between these indexes and the BfdSessTable."
::= { bfdSessDiscMapEntry 1 }
-- BFD Session IP Mapping Table
bfdSessIpMapTable OBJECT-TYPE
SYNTAX SEQUENCE OF BfdSessIpMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BFD Session Entry describes BFD session "The BFD Session IP Mapping Table maps given
that is mapped to this index. bfdSessInterface, bfdSessAddrType, and bfdSessAddr
to an associated BFD sessions' BfdSessIndexTC used in
the bfdSessionTable. This table SHOULD contains those
BFD sessions are of IP type: SingleHop(1) and
MultiHop(2)."
::= { bfdObjects 5 }
Implementors need to be aware that if the value of bfdSessIpMapEntry OBJECT-TYPE
the mplsInSegmentMapLabelPtrIndex (an OID) has more SYNTAX BfdSessIpMapEntry
that 111 sub-identifiers, then OIDs of column MAX-ACCESS not-accessible
instances in this table will have more than 128 STATUS current
sub-identifiers and cannot be accessed using SNMPv1, DESCRIPTION
SNMPv2c, or SNMPv3." "The BFD Session IP Map Entry describes
INDEX { bfdSessApplicationId, BFD session that is mapped to this BfdSessIndexTC."
bfdSessDiscriminator,
BFD MIB February 25, 2008
INDEX { bfdSessInterface,
bfdSessAddrType, bfdSessAddrType,
bfdSessAddr bfdSessAddr
} }
::= { bfdSessMapTable 1 } ::= { bfdSessIpMapTable 1 }
BfdSessMapEntry ::= SEQUENCE { BfdSessIpMapEntry ::= SEQUENCE {
bfdSessMapBfdIndex BfdSessIndexTC bfdSessIpMapIndex BfdSessIndexTC
} }
bfdSessMapBfdIndex 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 BfdIndex referred to by "This object specifies the BfdIndex 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."
::= { bfdSessMapEntry 1 } ::= { bfdSessIpMapEntry 1 }
-- Notification Configuration -- Notification Configuration
bfdSessNotificationsEnable OBJECT-TYPE bfdSessNotificationsEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this object is set to true(1), then it enables "If this object is set to true(1), then it enables
the emission of bfdSessUp and bfdSessDown the emission of bfdSessUp and bfdSessDown
BFD MIB October 20, 2006
notifications; otherwise these notifications are not notifications; otherwise these notifications are not
emitted." emitted."
REFERENCE REFERENCE
"See also RFC3413 for explanation that "See also RFC3413 for explanation that
notifications are under the ultimate control of the notifications are under the ultimate control of the
MIB modules in this document." MIB modules in this document."
DEFVAL { false } DEFVAL { false }
::= { bfdScalarObjects 4 } ::= { bfdScalarObjects 4 }
bfdSessUp NOTIFICATION-TYPE bfdSessUp NOTIFICATION-TYPE
OBJECTS { bfdSessDiag, -- low range value OBJECTS { 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 up(2) entries in bfdSessTable are about to enter the up(4)
state from some other state. The included values of state from some other state. The included values of
BFD MIB February 25, 2008
bfdSessDiag MUST both be set equal to this bfdSessDiag MUST both be set equal to this
new state (i.e: up(1)). The two instances of new state (i.e: up(4)). The two instances of
bfdSessDiag in this notification indicate the range bfdSessDiag in this notification indicate the range
of indexes that are affected. Note that all the indexes of indexes that are affected. Note that all the indexes
of the two ends of the range can be derived from the of the two ends of the range can be derived from the
instance identifiers of these two objects. For the instance identifiers of these two objects. For the
cases where a contiguous range of sessions cases where a contiguous range of sessions
have transitioned into the up(1) state at roughly have transitioned into the up(4) state at roughly
the same time, the device SHOULD issue a single the same time, the device SHOULD issue a single
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 { bfdSessDiag, -- low range value OBJECTS { 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(4) entries in bfdSessTable are about to enter the down(2)
or adminDown(5) 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 values of bfdSessDiag MUST both be set equal to this
new state (i.e: down(4) or adminDown(5)). The two instances new state (i.e: down(2) or adminDown(1)). The two instances
BFD MIB October 20, 2006
of bfdSessDiag in this notification indicate the range of bfdSessDiag in this notification indicate the range
of indexes that are affected. Note that all the indexes of indexes that are affected. Note that all the indexes
of the two ends of the range can be derived from the of the two ends of the range can be derived from the
instance identifiers of these two objects. For instance identifiers of these two objects. For
cases where a contiguous range of sessions cases where a contiguous range of sessions
have transitioned into the down(4) or adminDown(5) states have transitioned into the down(2) or adminDown(1) states
at roughly the same time, the device SHOULD issue a single at roughly the same time, the device SHOULD issue a single
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 2 } ::= { bfdNotifications 2 }
BFD MIB February 25, 2008
-- Ed Note: We need to add notification for changes -- Ed Note: We need to add notification for changes
-- when the two ends automatically negotiate to a new detection time -- when the two ends automatically negotiate to a new detection time
-- value or when detection multiplier changes. -- value or when detection multiplier changes.
-- Similarly, changes in the operating mode (bfdSessOperMode) -- Similarly, changes in the operating mode (bfdSessOperMode)
-- also need to be notified. -- also need to be notified.
-- Module compliance. -- Module compliance.
bfdGroups bfdGroups
OBJECT IDENTIFIER ::= { bfdConformance 1 } OBJECT IDENTIFIER ::= { bfdConformance 1 }
skipping to change at page 19, line 4 skipping to change at page 20, line 40
MODULE -- This module. MODULE -- This module.
MANDATORY-GROUPS { MANDATORY-GROUPS {
bfdSessionGroup, bfdSessionGroup,
bfdSessionPerfGroup, bfdSessionPerfGroup,
bfdSessionPerfHCGroup, bfdSessionPerfHCGroup,
bfdNotificationGroup bfdNotificationGroup
} }
GROUP bfdSessionPerfHCGroup GROUP bfdSessionPerfHCGroup
DESCRIPTION "This group is mandatory for those bfdPerfTable DESCRIPTION "This group is mandatory for those bfdPerfTable
BFD MIB October 20, 2006
entries for which any of the objects entries for which any of the objects
bfdSessPerfPktInHC or bfdSessPerfPktOutHC bfdSessPerfPktInHC or bfdSessPerfPktOutHC
wraps around too quickly wraps around too quickly
based on the criteria specified in RFC 2863 for based on the criteria specified in RFC 2863 for
high-capacity counters." high-capacity counters."
GROUP bfdNotificationGroup GROUP bfdNotificationGroup
DESCRIPTION "This group is only mandatory for those DESCRIPTION "This group is only mandatory for those
implementations which can efficiently implement implementations which can efficiently implement
the notifications contained in this group." the notifications contained in this group."
OBJECT bfdSessAddrType OBJECT bfdSessAddrType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support
is required." is required."
BFD MIB February 25, 2008
OBJECT bfdSessAddr OBJECT bfdSessAddr
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
DESCRIPTION "An implementation is only required to support DESCRIPTION "An implementation is only required to support
unknown(0), ipv4(1) and ipv6(2) sizes." unknown(0), ipv4(1) and ipv6(2) sizes."
::= { bfdCompliances 1 } ::= { bfdCompliances 1 }
-- Read-Only Conformance TBD... -- Read-Only Conformance TBD...
-- Units of conformance. -- Units of conformance.
bfdSessionGroup OBJECT-GROUP bfdSessionGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bfdSessNotificationsEnable, bfdSessNotificationsEnable,
bfdAdminStatus, bfdAdminStatus,
bfdVersionNumber, bfdSessVersionNumber,
bfdSessApplicationId, bfdSessType,
bfdSessDiscriminator, bfdSessDiscriminator,
bfdSessAddrType,
bfdSessAddr,
bfdSessRemoteDiscr, bfdSessRemoteDiscr,
bfdSessUdpPort, bfdSessUdpPort,
bfdSessState, bfdSessState,
bfdSessRemoteHeardFlag, bfdSessRemoteHeardFlag,
bfdSessDiag, bfdSessDiag,
bfdSessOperMode, bfdSessOperMode,
bfdSessDemandModeDesiredFlag, bfdSessDemandModeDesiredFlag,
bfdSessEchoFuncModeDesiredFlag, bfdSessEchoFuncModeDesiredFlag,
bfdSessControlPlanIndepFlag, bfdSessControlPlanIndepFlag,
bfdSessInterface,
bfdSessAddrType,
bfdSessAddr,
bfdSessDesiredMinTxInterval, bfdSessDesiredMinTxInterval,
bfdSessReqMinRxInterval, bfdSessReqMinRxInterval,
BFD MIB October 20, 2006
bfdSessReqMinEchoRxInterval, bfdSessReqMinEchoRxInterval,
bfdSessDetectMult, bfdSessDetectMult,
bfdSessStorType, bfdSessStorType,
bfdSessRowStatus, bfdSessRowStatus,
bfdSessMapBfdIndex,
bfdSessAuthPresFlag, bfdSessAuthPresFlag,
bfdSessAuthenticationType bfdSessAuthenticationType,
bfdSessDiscMapIndex,
bfdSessIpMapIndex
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for BFD sessions." "Collection of objects needed for BFD sessions."
::= { bfdGroups 1 } ::= { bfdGroups 1 }
BFD MIB February 25, 2008
bfdSessionPerfGroup OBJECT-GROUP bfdSessionPerfGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bfdSessPerfPktIn, bfdSessPerfPktIn,
bfdSessPerfPktOut, bfdSessPerfPktOut,
bfdSessUpTime, bfdSessUpTime,
bfdSessPerfLastSessDownTime, bfdSessPerfLastSessDownTime,
bfdSessPerfLastCommLostDiag, bfdSessPerfLastCommLostDiag,
bfdSessPerfSessUpCount, bfdSessPerfSessUpCount,
bfdSessPerfDiscTime bfdSessPerfDiscTime
} }
skipping to change at page 21, line 4 skipping to change at page 22, line 41
performance of BFD sessions for which the performance of BFD sessions for which the
values of bfdSessPerfPktIn, bfdSessPerfPktOut values of bfdSessPerfPktIn, bfdSessPerfPktOut
wrap around too quickly." wrap around too quickly."
::= { bfdGroups 3 } ::= { bfdGroups 3 }
bfdNotificationGroup NOTIFICATION-GROUP bfdNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
bfdSessUp, bfdSessUp,
bfdSessDown bfdSessDown
} }
BFD MIB October 20, 2006
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of notifications implemented in this "Set of notifications implemented in this
module." module."
::= { bfdGroups 4 } ::= { bfdGroups 4 }
END END
BFD MIB February 25, 2008
6. Security Considerations 6. Security Considerations
There are a number of management objects defined in this MIB There are a number of management objects defined in this MIB
module with a MAX-ACCESS clause of read-write and/or read-create. module with a MAX-ACCESS clause of read-write and/or read-create.
Such objects may be considered sensitive or vulnerable in some Such objects may be considered sensitive or vulnerable in some
network environments. It is thus important to control even GET and/or network environments. It is thus important to control even GET and/or
NOTIFY access to these objects and possibly to even encrypt the NOTIFY access to these objects and possibly to even encrypt the
values of these objects when sending them over the network via SNMP. values of these objects when sending them over the network via SNMP.
o The bfdSessTable may be used to directly configure BFD o The bfdSessTable may be used to directly configure BFD
skipping to change at page 22, line 4 skipping to change at page 23, line 46
table sensative. table sensative.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure "for example by using IPSec", Even if the network itself is secure "for example by using IPSec",
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET "read/change/create/delete" the objects allowed to access and GET/SET "read/change/create/delete" the objects
in these MIB modules. in these MIB modules.
It is RECOMMENDED that implementers consider the security features It is RECOMMENDED that implementers consider the security features
as provided by the SNMPv3 framework "see [RFC3410], section 8", as provided by the SNMPv3 framework "see [RFC3410], section 8",
BFD MIB October 20, 2006
including full support for the SNMPv3 cryptographic mechanisms "for including full support for the SNMPv3 cryptographic mechanisms "for
authentication and privacy". authentication and privacy".
BFD MIB February 25, 2008
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.
7. IANA Considerations 7. IANA Considerations
There is one MIB module contained in this document. The following There is one MIB module contained in this document. The following
"IANA Considerations" subsection requests IANA for a new "IANA Considerations" subsection requests IANA for a new
assignment under the mib-2 subtree. New assignments can only assignment under the mib-2 subtree. New assignments can only
be made via a Standards Action as specified in [RFC2434]. be made via a Standards Action as specified in [RFC2434].
7.1. IANA Considerations for BFD-STD-MIB 7.1. IANA Considerations for BFD-STD-MIB
The IANA is requested to assign { mib-2 XXX } to the The IANA is requested to assign { mib-2 XXX } to the BFD-STD-MIB
MPLS-L3VPN-STD-MIB module specified in this document. module specified in this document.
8. References 8. References
8.1 Normative References 8.1 Normative References
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Structure of Management Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Textual Conventions for Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Conformance Statements for Rose, M. and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[RFC3291] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet
Network Addresses", RFC 3291, May 2002.
[BFD] Katz, D., and Ward, D., "Bidirectional Forwarding [BFD] Katz, D., and Ward, D., "Bidirectional Forwarding
Detection", draft-ietf-bfd-base-05.txt. Detection", draft-ietf-bfd-base-07.txt.
BFD MIB October 20, 2006 BFD MIB February 25, 2008
[BFD-MH] Katz, D., and Ward, D., "BFD for Multihop Paths", [BFD-MH] Katz, D., and Ward, D., "BFD for Multihop Paths",
draft-ietf-bfd-multihop-04.txt. draft-ietf-bfd-multihop-06.txt.
[BFD-LSP] Aggarwal, R., Kompella, K., T. D. Nadeau, and G. Swallow [BFD-LSP] Aggarwal, R., Kompella, K., T. D. Nadeau, and G. Swallow
BFD For MPLS LSPs, draft-ietf-bfd-mpls-03.txt. BFD For MPLS LSPs, draft-ietf-bfd-mpls-05.txt.
8.2 Informative References 8.2 Informative References
[RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group MIB",
STD 58, RFC 2863, June 2000.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet
Network Addresses", RFC 4001, Feb. 2005.
[RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate
Requirement Levels", RFC 2119, BCP 14, April 1997. Requirement Levels", RFC 2119, BCP 14, April 1997.
[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 "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
[RFC3413] Levi, D., Meyer, P., Stewart, B., [RFC3413] Levi, D., Meyer, P., Stewart, B.,
"SNMP Applications", RFC 3413, December 2002. "SNMP Applications", RFC 3413, December 2002.
[RFC2434] Narten, T. and H. Alvestrand., "Guidelines for Writing [RFC2434] Narten, T. and H. Alvestrand., "Guidelines for Writing
an IANA Considerations Section in RFCs", BCP 26, RFC an IANA Considerations Section in RFCs", BCP 26, RFC
2434, October 1998. 2434, October 1998.
9. Acknowledgements 9. Acknowledgements
We would like to thank David Ward for his comments and suggestions. We would like to thank David Ward, Reshad Rahman, David Toscano,
Sylvain Masse, Mark Tooker, and Kiran Koushik Agrahara Sreenivasa
for their comments and suggestions.
10. Authors' Addresses 10. Authors' Addresses
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. BT
300 Beaver Brook Road BT Centre
Boxboro, MA 01719 81 Newgate Street
Phone: 978-936-1470 London, EC1A 7AJ
United Kingdom
Email: tnadeau@cisco.com Email: tom.nadeau@bt.com
Zafar Ali Zafar Ali
Cisco Systems Inc. 2000 Innovation Drive
100 South Main St. #200 Kanata, Ontario, K2K 3E8, Canada.
Ann Arbor, MI 48104, USA.
Phone: 734-276-2459 Phone: 734-276-2459
Email: zali@cisco.com Email: zali@cisco.com
BFD MIB February 25, 2008
Nobo Akiya
Cisco Systems G.K.
Shinjuku Mitsui Building, 2-1-1,
Nishi-Shinjuku, Shinjuku-Ku,
Tokyo 163-0409, Japan
Phone: +81 3 5324 4096
Email: nobo@cisco.com
11. Intellectual Property Statement 11. Intellectual Property Statement
BFD MIB October 20, 2006
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 24, line 30 skipping to change at page 26, line 41
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
12. Full Copyright Statement 12. Full Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject Copyright (C) The IETF Trust (2008). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement Acknowledgement
Funding for the RFC Editor function is provided by the IETF Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA). Administrative Support Activity (IASA).
 End of changes. 123 change blocks. 
199 lines changed or deleted 291 lines changed or added

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