draft-ietf-bfd-mib-00.txt   draft-ietf-bfd-mib-01.txt 
BFD Working Group Thomas D. Nadeau
Standard Track Zafar Ali
Cisco Systems, Inc.
Network Working Group Thomas D. Nadeau Document: draft-ietf-bfd-mib-01.txt
Internet Draft Zafar Ali Expires: January 2006 July 2005
Expires: December 2004 Cisco Systems, Inc.
June 2004
Bidirectional Forwarding Detection Management
Information Base
draft-ietf-bfd-mib-00.txt Bidirectional Forwarding Detection Management Information Base
draft-ietf-bfd-mib-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with By submitting this Internet-Draft, each author represents that any
all provisions of Section 10 of RFC 2026. 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
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the In ternet Engineering Internet-Drafts are working documents of the In ternet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that other
other groups may also distribute working documents as Internet- groups may also distribute working documents as Internet-Drafts.
Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six months
months and may be updated, replaced, or obsoleted by other and may be updated, replaced, or obsoleted by other documents at any
documents at any time. It is inappropriate to use Internet- time. It is inappropriate to use Internet-Drafts as reference
Drafts as reference material or to cite them other than as "work material or to cite them other than as "work in progress."
in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
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].
Conventions used in this document
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 RFC 2119
[RFC2119].
SUMMARY
This draft defines Management Information Base (MIB) for
Bidirectional Forwarding Detection (BFD) protocol [BFD].
RELATED REFERENCES
Please refer to the reference section.
Table of Contents Table of Contents
1. Introduction .........................................................2 1. Introduction...................................................2
2. Terminology ..........................................................2 2. Terminology....................................................3
3. The SNMP Management Framework ........................................3 3. The Internet-Standard Management Framework.....................3
4. Use of 32-bit and 64-bit Counters ....................................3 3. Brief Description of MIB Objects...............................3
5. Brief Description of MIB Objects .....................................3 3.1 General Variables..........................................3
5.1 General Variables ...................................................3 3.2 Session Table (bfdSessionTable)............................3
5.2 Session Table (bfdSessionTable) .....................................4 3.3 Session Performance Table (bfdSessionPerfTable)............3
5.3 Session Performance Table (bfdSessionPerfTable) .....................4 3.4 Session Mapping Table (bfdSessMapTable)....................3
5.4 Session Mapping Table (bfdSessMapTable) .............................4 4. BFD MIB Module Definitions.....................................4
6. BFD MIB Module Definitions ...........................................4 5. Security Considerations.......................................21
7. Security Considerations .............................................20 6. Acknowledgements..............................................22
8. Acknowledgements ....................................................21 7. Reference.....................................................23
9. References ..........................................................21 7.1 Normative References.........................................23
9.1. Normative References .............................................21 7.2 Informative References.......................................23
9.2. Informative References ...........................................22 8. Author's Addresses............................................23
10. Author's Addresses..................................................22 9. Full Copyright Statement......................................24
11. Full Copyright Statement ...........................................22 10. IANA Considerations.........................................41
12. Intellectual Property Notice .......................................22 10.1. IANA Considerations for BFD-STD-MIB.......................41
13. IANA Considerations ................................................23 11. Intellectual Property Statement.............................41
1. Introduction 1. Introduction
For a detailed overview of the documents that describe the This memo defines an portion of the Management
current Internet-Standard Management Framework, please refer to Information Base (MIB) for use with network management protocols
section of RFC 3410 [RFC3410]. in the Internet community. In particular, it describes managed
objects to configure and/or monitor Bi-Directional Forwarding
Managed objects are accessed via a virtual information store, Detection on devices supporting this feature.
termed the Management Information Base or MIB. MIB objects are
generally accessed through the Simple Network Management Protocol
(SNMP). Objects in the MIB are defined using the mechanisms defined
in the Structure of Management Information (SMI). This memo
specifies a MIB 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 [RFC2580].
Current work is underway in the IETF to specify a suite of This document adopts the definitions, acronyms and mechanisms
protocols known as Bidirectional Forwarding Detection to detect described in [BFD], [BFD-SHARED] and [BFD-LSP]. Unless otherwise
faults in the bidirectional path between two forwarding engines, stated, the mechanisms described therein will not be re-described
including interfaces, data link(s), and to the extent possible the here.
forwarding engines themselves, with potentially very low latency
[BFD].
In this document we describe a MIB module that can be used to Comments should be made directly to the BFD mailing list at
manage BFD implementations. This MIB module covers both rtg-bfd@ietf.org.
configuration and performance monitoring aspects of BFD.
This document is based on draft-katz-ward-bfd-02.txt [BFD] and The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
only addresses MIB for MFD running over point-to-point interfaces. NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
Specifically, this version of the ID does not address BFD over "OPTIONAL" in this document are to be interpreted as described in
shared interfaces [BFDSHARED]. Furthermore, at present we do not [RFC2119].
directly address manageability requirement when LSP-Ping is used for
boot-strapping the BFD session [BFD-LSP]. Nonetheless, some
considerations are in place for these applications of the BFD. These
aspects of BFD will be directly addressed in the future version of
the ID.
2. Terminology 2. Terminology
This document uses terminology from the document describing the
BFD protocol [BFD].
3. The SNMP Management Framework This document adopts the definitions, acronyms and mechanisms
described in [BFD], [BFD-SHARED] and [BFD-LSP]. Unless otherwise
stated, the mechanisms described therein will not be re-described
here.
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
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. Use of 32-bit and 64-bit Counters 4. Brief Description of MIB Objects
64-bit counters are provided in this MIB module for high speed
interfaces where the use of 32-bit counters might be impractical.
The requirements on the use of 32-bit and 64-bit counters (copied
verbatim from [RFC2863]) are as follows.
For interfaces that operate at 20,000,000 (20 million) bits per
second or less, 32-bit byte and packet counters MUST be supported.
For interfaces that operate faster than 20,000,000 bits/second,
and slower than 650,000,000 bits/second, 32-bit packet counters
MUST be supported and 64-bit octet counters MUST be supported.
For interfaces that operate at 650,000,000 bits/second or faster,
64-bit packet counters AND 64-bit octet counters MUST be
supported.
5. 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 the BFD document [BFD].
5.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.
5.2 Session Table (bfdSessionTable) 4.2 Session Table (bfdSessionTable)
The session table is used to identify a BFD session between a The session table is used to identify a BFD session between a pair
pair of nodes. of nodes.
5.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.
5.4 Session Mapping Table (bfdSessMapTable) 3.4 Session Mapping Table (bfdSessMapTable)
The BFD Session Mapping Table maps the complex indexing of the BFD The BFD Session Mapping Table maps the complex indexing of the BFD
sessions to the flat BFDIndex used in the BfdSessionTable. sessions to the flat BFDIndex used in the BfdSessionTable.
6. BFD MIB Module Definitions 5. BFD MIB Module Definitions
BFD-DRAFT-00-MIB DEFINITIONS ::= BEGIN BFD-DRAFT-01-MIB DEFINITIONS ::= BEGIN
-- RFC-editor pls change BFD-DRAFT-*-MIB to
-- BFD-STD-MIB
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 FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType,
TimeStamp TimeStamp
FROM SNMPv2-TC FROM SNMPv2-TC
InetAddress, InetAddressType InetAddress, InetAddressType, InetPortNumber
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
; ;
bfdMIB MODULE-IDENTITY bfdMIB MODULE-IDENTITY
LAST-UPDATED "200401221200Z" -- 22 January 2004 12:00:00 EST LAST-UPDATED "200507221200Z" -- 04 July 2005 12:00:00 EST
ORGANIZATION "IETF" ORGANIZATION "IETF"
CONTACT-INFO CONTACT-INFO
" Zafar Ali " Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
Email: zali@cisco.com Email: tnadeau@cisco.com
Thomas D. Nadeau Zafar Ali
Cisco Systems, Inc. Cisco Systems, Inc.
Email: tnadeau@cisco.com Email: zali@cisco.com
" "
DESCRIPTION DESCRIPTION
"Bidirectional Forwarding Management Information Base." "Bidirectional Forwarding Management Information Base."
-- Revision history. -- Revision history.
REVISION REVISION
"200401221200Z" -- 22 January 2004 12:00:00 EST "200507221200Z" -- 04 July 2005 12:00:00 EST
DESCRIPTION DESCRIPTION
"Initial version." "Initial version. Published as RFC xxxx." -- RFC-editor pls fill
::= { mib-2 999 } -- To be assigned by IANA. -- in xxx
::= { mib-2 XXX } -- assigned by IANA, see section 18.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 }
skipping to change at page 5, line 31 skipping to change at page 5, line 23
-- Textual Conventions -- Textual Conventions
BfdSessIndexTC ::= TEXTUAL-CONVENTION BfdSessIndexTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
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
DISPLAY-HINT "d"
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)
BfdDiag ::= TEXTUAL-CONVENTION BfdDiag ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A common BFD diagnostic code." "A common BFD diagnostic code."
SYNTAX INTEGER { noDiagnostic(1), SYNTAX INTEGER { noDiagnostic(1),
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)
} }
-- 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
skipping to change at page 6, line 15 skipping to change at page 6, line 9
-- 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 active The value 'enabled' denotes that the BFD Process is
on at least one interface; 'disabled' disables it on active on at least one interface; 'disabled' disables
all interfaces." it on all interfaces."
DEFVAL { enabled } DEFVAL { enabled }
::= { bfdScalarObjects 1 } ::= { bfdScalarObjects 1 }
bfdOperStatus OBJECT-TYPE
SYNTAX INTEGER { up(1), down(2) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The operational status of BFD on this router."
::= { bfdScalarObjects 2 }
bfdVersionNumber OBJECT-TYPE bfdVersionNumber OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current version number of the BFD protocol." "The current version number of the BFD protocol."
REFERENCE REFERENCE
" BFD Version 0 (draft-katz-ward-bfd-04.txt)" " BFD Version 0 (draft-katz-ward-bfd-02.txt)"
DEFVAL { 0 } DEFVAL { 0 }
::= { bfdScalarObjects 3 } ::= { 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-04.txt)" "BFD Version 0 (draft-katz-ward-bfd-02.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, bfdSessApplicationId Unsigned32,
bfdSessDiscriminator Unsigned32, bfdSessDiscriminator Unsigned32,
bfdSessLocalDiscr Unsigned32,
bfdSessRemoteDiscr Unsigned32, bfdSessRemoteDiscr Unsigned32,
bfdSessUdpPort InetPortNumber,
bfdSessState INTEGER, bfdSessState INTEGER,
bfdSessRemoteHeardFlag TruthValue, bfdSessRemoteHeardFlag TruthValue,
bfdSessDiag Unsigned32, bfdSessDiag Unsigned32,
bfdSessOperMode INTEGER, bfdSessOperMode INTEGER,
bfdSessDemandModeDesiredFlag TruthValue, bfdSessDemandModeDesiredFlag TruthValue,
bfdSessEchoFuncModeDesiredFlag TruthValue, bfdSessEchoFuncModeDesiredFlag TruthValue,
bfdSessEchoFuncFlag INTEGER, bfdSessControlPlanIndepFlag TruthValue,
bfdSessAddrType InetAddressType, bfdSessAddrType InetAddressType,
bfdSessAddr InetAddress, bfdSessAddr InetAddress,
bfdSessDesiredMinTxInterval BfdInterval, bfdSessDesiredMinTxInterval BfdInterval,
bfdSessDesiredMinRxInterval BfdInterval, bfdSessDesiredMinRxInterval BfdInterval,
bfdSessDesiredMinEchoRxInterval BfdInterval, bfdSessDesiredMinEchoRxInterval BfdInterval,
bfdSessDetectMult BfdInterval, bfdSessDetectMult Unsigned32,
bfdSessStorType StorageType, bfdSessStorType StorageType,
bfdSessRowStatus RowStatus bfdSessRowStatus RowStatus,
bfdSessAuthPresFlag TruthValue,
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 bfdSessApplicationId 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 "This object contains an index used to indicate
an local application which owns or maintains this a local application which owns or maintains this
BFD session. For instance, the VPN process may BFD session. For instance, the MPLS VPN process may
maintain a subset of the total number of BFD maintain a subset of the total number of BFD
sessions. This application ID provides a convienent sessions. This application ID provides a convenient
way to segretate sessions by the applications which way to segregate sessions by the applications which
maintain them." maintain them."
::= { bfdSessEntry 2 } ::= { bfdSessEntry 2 }
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 3 }
bfdSessLocalDiscr 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 local discriminator for this BFD "This object specifies the session discriminator chosen
session, used to uniquely identify it." by the remote system for this BFD session."
::= { bfdSessEntry 4 } ::= { bfdSessEntry 4 }
bfdSessRemoteDiscr OBJECT-TYPE bfdSessUdpPort OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX InetPortNumber
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the discriminator chosen by the "The UDP Port for BFD. The default value is the
remote system local discriminator for this BFD well-known value for this port."
session." REFERENCE
"draft-katz-ward-bfd-02.txt and
draft-raggarwa-mpls-bfd-00.txt"
DEFVAL { 0 }
::= { bfdSessEntry 5 } ::= { bfdSessEntry 5 }
bfdSessState OBJECT-TYPE bfdSessState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
init(1), adminDown(1),
up(2), down(2),
failing(3), init(3),
down(4), up(4)
adminDown(5)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The perceived state of the BFD session." "The perceived state of the BFD session."
::= { bfdSessEntry 6 } ::= { bfdSessEntry 6 }
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 the remote system. Specifically, it is set to true(1) if
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 the time) or if the local system is attempting to tear down
BFD session." the BFD session."
::= { bfdSessEntry 7 } ::= { bfdSessEntry 7 }
bfdSessDiag OBJECT-TYPE bfdSessDiag OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
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) to some for the last transition of the session from up(1)
other state." to some other state."
::= { bfdSessEntry 8 } ::= { bfdSessEntry 8 }
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
skipping to change at page 10, line 20 skipping to change at page 10, line 16
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 11 }
bfdSessEchoFuncFlag OBJECT-TYPE bfdSessControlPlanIndepFlag OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) } SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The administrative status of Echo function for this BFD "This object indicates that the local system's
session. The value 'enabled' denotes that the Echo ability to continue to function through a disruption of
function is enabled for this session; 'disabled' disables the control plane. Specifically, it is set
Echo function for this session." to true(1) if the local system BFD implementation is
independent of the control plane. Otherwise, the
value is set to false(0)"
DEFVAL { false }
::= { bfdSessEntry 12 } ::= { bfdSessEntry 12 }
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 associated with "This object specifies IP address of the interface
this BFD session. associated 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
skipping to change at page 10, line 52 skipping to change at page 11, line 4
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 13 }
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 associated with "This object specifies IP address of the interface
this BFD session. It can also be used to enabled BFD on a specific associated with this BFD session.
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 14 }
bfdSessDesiredMinTxInterval OBJECT-TYPE bfdSessDesiredMinTxInterval 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
skipping to change at page 11, line 45 skipping to change at page 11, line 47
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 17 }
bfdSessDetectMult OBJECT-TYPE bfdSessDetectMult OBJECT-TYPE
SYNTAX BfdInterval 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 18 }
bfdSessStorType OBJECT-TYPE bfdSessStorType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 12, line 25 skipping to change at page 12, line 30
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 20 }
bfdSessAuthPresFlag OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicates that the local system's
desire to use Authentication. Specifically, it is set
to true(1) if the local system wishes the session
to be authenticated or false(0) if not"
DEFVAL { false }
::= { bfdSessEntry 21 }
bfdSessAuthenticationType OBJECT-TYPE
SYNTAX INTEGER { simplePassword(1),
keyedMD5(2),
meticulousKeyedMD5(3),
keyedSHA1(4),
meticulousKeyedSHA1(5)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Authentication Type used for this BFD session. This
field is valid only when the Authentication Present bit is set"
::= { bfdSessEntry 22 }
-- 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 }
skipping to change at page 12, line 50 skipping to change at page 13, line 33
"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 }
BfdSessPerfEntry ::= SEQUENCE { BfdSessPerfEntry ::= SEQUENCE {
bfdSessPerfPktIn Counter32, bfdSessPerfPktIn Counter32,
bfdSessPerfPktOut Counter32, bfdSessPerfPktOut Counter32,
bfdSessPerfBadDiscrim Counter32, bfdSessUpTime TimeStamp,
bfdSessPerfLastSessDownTime TimeStamp, bfdSessPerfLastSessDownTime TimeStamp,
bfdSessPerfLastCommLostDiag BfdDiag, bfdSessPerfLastCommLostDiag BfdDiag,
bfdSessPerfSessDownCount Counter32, bfdSessPerfSessUpCount Counter32,
bfdSessPerfDiscTime TimeStamp, bfdSessPerfDiscTime TimeStamp,
-- High Capacity Counters -- High Capacity Counters
bfdSessPerfPktInHC Counter64, bfdSessPerfPktInHC Counter64,
bfdSessPerfPktOutHC Counter64, bfdSessPerfPktOutHC Counter64
bfdSessPerfBadDiscrimHC Counter64
} }
-- Ed Note: should we add per-diag code counts here, -- Ed Note: should we add per-diag code counts here,
bfdSessPerfPktIn OBJECT-TYPE bfdSessPerfPktIn 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 received for this BFD session." "The total number of BFD messages received for this BFD
session."
::= { 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 }
bfdSessPerfBadDiscrim OBJECT-TYPE bfdSessUpTime OBJECT-TYPE
SYNTAX Counter32 SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of BFD messages received with a "The value of sysUpTime on the most recent occasion at which
bad local Discriminator value for this BFD session." the session came up. If no such up event exists this object
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
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 last time communication was lost with the neighbor. If the last time communication was lost with the neighbor. If
no such down event exist this object contains a zero value." no such down event exist this object contains a zero value."
::= { bfdSessPerfEntry 4 } ::= { bfdSessPerfEntry 4 }
bfdSessPerfLastCommLostDiag OBJECT-TYPE bfdSessPerfLastCommLostDiag OBJECT-TYPE
SYNTAX BfdDiag SYNTAX BfdDiag
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BFD diag code for the last time communication was lost "The BFD diag code for the last time communication was lost
with the neighbor. If no such down event exist this object with the neighbor. If no such down event exists this object
contains a zero value." contains a zero value."
::= { bfdSessPerfEntry 5 } ::= { bfdSessPerfEntry 5 }
bfdSessPerfSessDownCount OBJECT-TYPE bfdSessPerfSessUpCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of times this session has gone into the down "The number of times this session has gone into the Up
state since the router last rebooted." state since the router last rebooted."
::= { bfdSessPerfEntry 6 } ::= { bfdSessPerfEntry 6 }
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 which any "The value of sysUpTime on the most recent occasion at which
one or more of the session counters suffered a discontinuity. any
one or more of the session counters suffered a
discontinuity.
The relevant counters are the specific instances associated The relevant counters are the specific instances associated
with this BFD sesion of any Counter32 object contained in the with this BFD session of any Counter32 object contained in
the
BfdSessPerfTable. If no such discontinuities have occurred BfdSessPerfTable. If no such discontinuities have occurred
since the last re-initialization of the local management subsystem, since the last re-initialization of the local management
subsystem,
then this object contains a zero value." 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 "This value represents the total number of BFD messages
total number of BFD messages received for this received 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 bfdSessPerfPktInHC is supported according to if bfdSessPerfPktInHC is supported according to
the rules spelled out in RFC2863." the rules spelled out in RFC2863."
::= { bfdSessPerfEntry 8 } ::= { bfdSessPerfEntry 8 }
bfdSessPerfPktOutHC OBJECT-TYPE bfdSessPerfPktOutHC 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 "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 }
bfdSessPerfBadDiscrimHC OBJECT-TYPE -- BFD Session Mapping Table
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This value represents the total number of
total number of BFD messages received with a
bad local Discriminator value for this BFD session.
It MUST be equal to the least significant 32 bits of
bfdSessPerfBadDiscrimHC if bfdSessPerfBadDiscrimHC
is supported according to the rules spelled out
in RFC2863."
::= { bfdSessPerfEntry 10 }
bfdSessMapTable OBJECT-TYPE bfdSessMapTable OBJECT-TYPE
SYNTAX SEQUENCE OF BfdSessMapEntry SYNTAX SEQUENCE OF BfdSessMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BFD Session Map Table maps the complex "The BFD Session Mapping Table maps the complex
indexing of the BFD sessions to the flat indexing of the BFD sessions to the flat
BFDIndex used in the BfdSessionTable. BFDIndex used in the BfdSessionTable.
Implementors need to be aware that if the value of Implementors need to be aware that if the value of
the bfdSessAddr (an OID) has more the bfdSessAddr (an OID) has more
that 111 sub-identifiers, then OIDs of column that 111 sub-identifiers, then OIDs of column
instances in this table will have more than 128 instances in this table will have more than 128
sub-identifiers and cannot be accessed using SNMPv1, sub-identifiers and cannot be accessed using SNMPv1,
SNMPv2c, or SNMPv3. SNMPv2c, or SNMPv3.
" "
REFERENCE REFERENCE
"BFD Version 0 (draft-katz-ward-bfd-04.txt)" "BFD Version 0 (draft-katz-ward-bfd-02.txt)"
::= { bfdObjects 4 } ::= { bfdObjects 4 }
bfdSessMapEntry OBJECT-TYPE bfdSessMapEntry OBJECT-TYPE
SYNTAX BfdSessMapEntry SYNTAX BfdSessMapEntry
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
that is mapped to this index. that is mapped to this index.
Implementors need to be aware that if the value of Implementors need to be aware that if the value of
the bfdSessAddr has more that 111 octets, then OIDs of the mplsInSegmentMapLabelPtrIndex (an OID) has more
column instances in this table will have more than 128 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, sub-identifiers and cannot be accessed using SNMPv1,
SNMPv2c, or SNMPv3" SNMPv2c, or SNMPv3."
INDEX { bfdSessApplicationId, INDEX { bfdSessApplicationId,
bfdSessDiscriminator, bfdSessDiscriminator,
bfdSessAddrType, bfdSessAddrType,
bfdSessAddr bfdSessAddr
} }
::= { bfdSessMapTable 1 } ::= { bfdSessMapTable 1 }
BfdSessMapEntry ::= SEQUENCE { BfdSessMapEntry ::= SEQUENCE {
bfdSessMapBfdIndex BfdSessIndexTC bfdSessMapBfdIndex BfdSessIndexTC
} }
bfdSessMapBfdIndex OBJECT-TYPE bfdSessMapBfdIndex 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 refered 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 } ::= { bfdSessMapEntry 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
skipping to change at page 17, line 15 skipping to change at page 17, line 44
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(2)
state from some other state. The included values of state from some other state. The included values of
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(1)). 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 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(1) 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 }
skipping to change at page 18, line 5 skipping to change at page 18, line 35
have transitioned into the down(4) or adminDown(5) states have transitioned into the down(4) or adminDown(5) 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 }
-- Ed Note: We need to add notification for changes
-- when the two ends automatically negotiate to a new detection time
-- value or when detection multiplier changes.
-- Similarly, changes in the operating mode (bfdSessOperMode)
-- also need to be notified.
-- Module compliance. -- Module compliance.
bfdGroups bfdGroups
OBJECT IDENTIFIER ::= { bfdConformance 1 } OBJECT IDENTIFIER ::= { bfdConformance 1 }
bfdCompliances bfdCompliances
OBJECT IDENTIFIER ::= { bfdConformance 2 } OBJECT IDENTIFIER ::= { bfdConformance 2 }
-- Compliance requirement for fully compliant implementations. -- Compliance requirement for fully compliant implementations.
skipping to change at page 18, line 31 skipping to change at page 19, line 19
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 entries DESCRIPTION "This group is mandatory for those bfdPerfTable
for which any of the objects bfdSessPerfPktInHC, entries for which any of the objects
bfdSessPerfPktOutHC, or bfdSessPerfBadDiscrimHC bfdSessPerfPktInHC or bfdSessPerfPktOutHC
wraps around too quickly based on the criteria specified in wraps around too quickly
RFC 2863 for high-capacity counters." based on the criteria specified in RFC 2863 for
high-capacity counters."
GROUP bfdNotificationGroup GROUP bfdNotificationGroup
DESCRIPTION "This group is only mandatory for those implementations DESCRIPTION "This group is only mandatory for those
which can efficiently implement the notifications implementations which can efficiently implement
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."
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...
-- Units of conformance. -- Units of conformance.
bfdSessionGroup OBJECT-GROUP bfdSessionGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bfdSessNotificationsEnable, bfdSessNotificationsEnable,
bfdAdminStatus, bfdAdminStatus,
bfdOperStatus,
bfdVersionNumber, bfdVersionNumber,
bfdSessApplicationId, bfdSessApplicationId,
bfdSessDiscriminator, bfdSessDiscriminator,
bfdSessAddrType, bfdSessAddrType,
bfdSessAddr, bfdSessAddr,
bfdSessLocalDiscr,
bfdSessRemoteDiscr, bfdSessRemoteDiscr,
bfdSessUdpPort,
bfdSessState, bfdSessState,
bfdSessRemoteHeardFlag, bfdSessRemoteHeardFlag,
bfdSessDiag, bfdSessDiag,
bfdSessOperMode, bfdSessOperMode,
bfdSessDemandModeDesiredFlag, bfdSessDemandModeDesiredFlag,
bfdSessEchoFuncFlag,
bfdSessEchoFuncModeDesiredFlag, bfdSessEchoFuncModeDesiredFlag,
bfdSessControlPlanIndepFlag,
bfdSessDesiredMinTxInterval, bfdSessDesiredMinTxInterval,
bfdSessDesiredMinRxInterval, bfdSessDesiredMinRxInterval,
bfdSessDesiredMinEchoRxInterval, bfdSessDesiredMinEchoRxInterval,
bfdSessDetectMult, bfdSessDetectMult,
bfdSessStorType, bfdSessStorType,
bfdSessRowStatus, bfdSessRowStatus,
bfdSessMapBfdIndex bfdSessMapBfdIndex,
bfdSessAuthPresFlag,
bfdSessAuthenticationType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for BFD sessions." "Collection of objects needed for BFD sessions."
::= { bfdGroups 1 } ::= { bfdGroups 1 }
bfdSessionPerfGroup OBJECT-GROUP bfdSessionPerfGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bfdSessPerfPktIn, bfdSessPerfPktIn,
bfdSessPerfPktOut, bfdSessPerfPktOut,
bfdSessPerfBadDiscrim, bfdSessUpTime,
bfdSessPerfLastSessDownTime, bfdSessPerfLastSessDownTime,
bfdSessPerfLastCommLostDiag, bfdSessPerfLastCommLostDiag,
bfdSessPerfSessDownCount, bfdSessPerfSessUpCount,
bfdSessPerfDiscTime bfdSessPerfDiscTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed to monitor the "Collection of objects needed to monitor the
performance of BFD sessions." performance of BFD sessions."
::= { bfdGroups 2 } ::= { bfdGroups 2 }
bfdSessionPerfHCGroup OBJECT-GROUP bfdSessionPerfHCGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bfdSessPerfPktInHC, bfdSessPerfPktInHC,
bfdSessPerfPktOutHC, bfdSessPerfPktOutHC
bfdSessPerfBadDiscrimHC
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed to monitor the "Collection of objects needed to monitor the
performance of BFD sessions for which the performance of BFD sessions for which the
values of bfdSessPerfPktIn, values of bfdSessPerfPktIn, bfdSessPerfPktOut
bfdSessPerfPktOut, or bfdSessPerfBadDiscrim
wrap around too quickly." wrap around too quickly."
::= { bfdGroups 3 } ::= { bfdGroups 3 }
bfdNotificationGroup NOTIFICATION-GROUP bfdNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
bfdSessUp, bfdSessUp,
bfdSessDown bfdSessDown
} }
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
7. 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 network environments. It is thus important to control even GET and/or
and/or NOTIFY access to these objects and possibly to even encrypt NOTIFY access to these objects and possibly to even encrypt the
the values of these objects when sending them over the network via values of these objects when sending them over the network via SNMP.
SNMP.
Some of the readable objects in this MIB module (i.e., objects Some of the readable objects in this MIB module (i.e., objects
with a MAX-ACCESS other than not-accessible) may be considered with a MAX-ACCESS other than not-accessible) may be considered
sensitive or vulnerable in some network environments. It is thus sensitive or vulnerable in some network environments. It is thus
important to control even GET and/or NOTIFY access to these objects important to control even GET and/or NOTIFY access to these objects
and possibly to even encrypt the values of these objects when and possibly to even encrypt the values of these objects when sending
sending them over the network via SNMP. them over the network via SNMP.
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 allowed to access and GET/SET "read/change/create/delete" the objects
objects in these MIB modules. in these MIB modules.
It is RECOMMENDED that implementers consider the security It is RECOMMENDED that implementers consider the security features
features as provided by the SNMPv3 framework "see [RFC3410], section as provided by the SNMPv3 framework "see [RFC3410], section 8",
8", including full support for the SNMPv3 cryptographic mechanisms including full support for the SNMPv3 cryptographic mechanisms "for
"for 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 instance of this MIB module, is properly configured to give access to
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. Acknowledgements 7. Acknowledgements
We would like to thank David Ward for his comments and suggestions. We would like to thank David Ward for his comments and suggestions.
9. References 8. Reference
9.1 Normative References
[BFD] Katz, D., and Ward, D., "Bidirectional Forwarding Detection", 8.1 Normative References
draft-katz-ward-bfd-02.txt (work in progress).
[BFDSHARED] "Bidirectional Forwarding Detection over Shared [BFD] Katz, D., and Ward, D., "Bidirectional Forwarding
Interfaces", work in progress. Detection", draft-ietf-bfd-base-02.txt.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [BFD-SHARED] Bidirectional Forwarding Detection over Shared
J., Rose, M., and S. Waldbusser, "Structure of Management Interfaces, work in progress.
Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [BFD-LSP] Aggarwal, R., Kompella, K., T. D. Nadeau, and G. Swallow
J., Rose, M., and S. Waldbusser, "Textual Conventions BFD For MPLS LSPs, draft-ietf-bfd-mpls-01.txt.
for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 8.2 Informative References
J., Rose, M., and S. Waldbusser, "Conformance Statements for SMIv2",
STD 58, RFC 2580, April 1999.
[RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
MIB", RFC 2863, June 2000. "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410,
December 2002.
9.2 Informative References [RFC3413] Levi, D., Meyer, P., Stewart, B.,
"SNMP Applications", RFC 3413, December 2002.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC2434] Narten, T. and H. Alvestrand., "Guidelines for Writing
"Introduction and Applicability Statements for Internet-Standard an IANA Considerations Section in RFCs", BCP 26, RFC
Management Framework", RFC 3410,December 2002. 2434, October 1998.
[RFC3413] Levi, D., Meyer, P., Stewart, B., "Simple Network 9. Authors' Addresses
Management Protocol (SNMP) Applications", RFC 3413, December 2002.
10. Author's Addresses Thomas D. Nadeau
Cisco Systems, Inc.
300 Beaver Brook Road
Boxboro, MA 01719
Phone: +1-978-936-1470
Thomas D. Nadeau Zafar Ali Email: tnadeau@cisco.com
Cisco Systems, Inc. Cisco Systems Inc.
300 Beaver Brook Road 100 South Main St. #200
Boxborough, MA 01719 Ann Arbor, MI 48104, USA.
Phone: +1-978-936-1470 Phone: +1-734-276-2459
Email: tnadeau@cisco.com Email: zali@cisco.com
16. Full Copyright Statement Zafar Ali
Cisco Systems Inc.
100 South Main St. #200
Ann Arbor, MI 48104, USA.
Phone: +1-734-276-2459
Email: zali@cisco.com
Copyright (C) The Internet Society (2003). All Rights Reserved. 10. Full Copyright Statement
This document and translations of it may be copied and furnished Copyright (C) The Internet Society (2005). This document is subject
to others, and derivative works that comment on or otherwise to the rights, licenses and restrictions contained in BCP 78, and
explain it or assist in its implementation may be prepared, except as set forth therein, the authors retain all their rights.
copied, published and distributed, in whole or in part, without
restriction of any kind, provided that the above copyright notice
and this paragraph are included on all such copies and derivative
works. However, this document itself may not be modified in any
way, such as by removing the copyright notice or references to the
Internet Society or other Internet organizations, except as needed
for the purpose of developing Internet standards in which case
the procedures for copyrights defined in the Internet Standards
process must be followed, or as required to translate it into
languages other than English.
The limited permissions granted above are perpetual and will not This document and the information contained herein are provided on an
be revoked by the Internet Society or its successors or assigns. "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
This document and the information contained herein is provided on OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
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.
17. Intellectual Property Notice 11. IANA Considerations
There is one MIB module contained in this document. The following
"IANA Considerations" subsection requests IANA for a new
assignment under the mib-2 subtree. New assignments can only
be made via a Standards Action as specified in [RFC2434].
11.1. IANA Considerations for BFD-STD-MIB
The IANA is requested to assign { mib-2 XXX } to the
MPLS-L3VPN-STD-MIB module specified in this document.
12. Intellectual Property Statement
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 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; neither does it represent that it might or might not be available; nor does it represent that it has
has made any effort to identify any such rights. Information on the made any independent effort to identify any such rights. Information
IETF's procedures with respect to rights in standards-track and on the procedures with respect to rights in RFC documents can be
standards-related documentation can be found in BCP-11 [RFC2028]. found in BCP 78 and BCP 79.
Copies of claims of rights made available for publication and any
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementors or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF Secretariat. specification can be obtained from the IETF on-line IPR repository at
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 practice rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF at ietf-
Director. ipr@ietf.org.
 End of changes. 

This html diff was produced by rfcdiff 1.24, available from http://www.levkowetz.com/ietf/tools/rfcdiff/