EZ5 MIB Catalog

BFD-STD-MIB

2014-08-12

Download BFD-STD-MIB.json.gz BFD-STD-MIB.txt Open BFD-STD-MIB.txt

Bidirectional Forwarding Management Information Base. Copyright (c) 2014 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).

SCALARS (4) · TABLES (4) · TRAPS (2)

Scalars (4)

NameOID
bfdAdminStatus1.3.6.1.2.1.222.1.1.1
bfdOperStatus1.3.6.1.2.1.222.1.1.2
bfdNotificationsEnable1.3.6.1.2.1.222.1.1.3
bfdSessIndexNext1.3.6.1.2.1.222.1.1.4

Tables (4)

NameOID
bfdSessTable1.3.6.1.2.1.222.1.2
bfdSessPerfTableaugments bfdSessTable1.3.6.1.2.1.222.1.3
bfdSessDiscMapTable1.3.6.1.2.1.222.1.4
bfdSessIpMapTable1.3.6.1.2.1.222.1.5

Traps (2)

NameOID
bfdSessUp1.3.6.1.2.1.222.0.1
bfdSessDown1.3.6.1.2.1.222.0.2

END OF TOC

Scalar details

bfdAdminStatus

1.3.6.1.2.1.222.1.1.1

INTEGER1 = enabled2 = disabled3 = adminDown4 = down · Integer32

The desired global administrative status of the BFD system in this device.

bfdOperStatus

1.3.6.1.2.1.222.1.1.2

INTEGER1 = up2 = down3 = adminDown · Integer32

Indicates the actual operational status of the BFD system in this device. When this value is down(2), all entries in the bfdSessTable MUST have their bfdSessOperStatus as down(2) as well. When this value is adminDown(3), all entries in the bfdSessTable MUST have their bfdSessOperStatus as adminDown(3) as well.

bfdNotificationsEnable

1.3.6.1.2.1.222.1.1.3

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32 · default false (2)

If this object is set to true(1), then it enables the emission of bfdSessUp and bfdSessDown notifications; otherwise, these notifications are not emitted.

bfdSessIndexNext

1.3.6.1.2.1.222.1.1.4

IndexIntegerNextFreeAn integer which may be used as a new Index in a table. The special value of 0 indicates that no more new entries can be created in the relevant table. When a MIB is used for configuration, an object with this SYNTAX always contains a legal value (if non-zero) for an index that is not currently used in the relevant table. The Command Generator (Network Management Application) reads this variable and uses the (non-zero) value read when creating a new row with an SNMP SET. When the SET is performed, the Command Responder (agent) must determine whether the value is indeed still unused; Two Network Management Applications may attempt to create a row (configuration entry) simultaneously and use the same value. If it is currently unused, the SET succeeds and the Command Responder (agent) changes the value of this object, according to an implementation-specific algorithm. If the value is in use, however, the SET fails. The Network Management Application must then re-read this variable to obtain a new usable value. An OBJECT-TYPE definition using this SYNTAX MUST specify the relevant table for which the object is providing this functionality. · Unsigned32 · hint d

This object contains an unused value for bfdSessIndex that can be used when creating entries in the table. A zero indicates that no entries are available, but it MUST NOT be used as a valid index.

Table details

bfdSessTable

1.3.6.1.2.1.222.1.2

Index: bfdSessIndex

The BFD Session Table describes the BFD sessions.

bfdSessIndex

1.3.6.1.2.1.222.1.2.1.1

BfdSessIndexTCAn index used to uniquely identify BFD sessions. (1..4294967295) · Unsigned32 · hint d

This object contains an index used to represent a unique BFD session on this device. Managers should obtain new values for row creation in this table by reading bfdSessIndexNext.

bfdSessVersionNumber

1.3.6.1.2.1.222.1.2.1.2

Unsigned32 (0..7) · default 1

The version number of the BFD protocol that this session is running in. Write access is available for this object to provide the ability to set the desired version for this BFD session.

bfdSessType

1.3.6.1.2.1.222.1.2.1.3

IANAbfdSessTypeTC1 = singleHop2 = multiHopTotallyArbitraryPaths3 = multiHopOutOfBandSignaling4 = multiHopUnidirectionalLinksBFD session typeReference: Katz, D. and D. Ward, Bidirectional Forwarding Detection (BFD), RFC 5880, June 2010. Katz, D. and D. Ward, Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop), RFC 5881, June 2010. Katz, D. and D. Ward, Bidirectional Forwarding Detection (BFD) for Multihop Paths, RFC 5883, June 2010. · Integer32

This object specifies the type of this BFD session.

bfdSessDiscriminator

1.3.6.1.2.1.222.1.2.1.4

Unsigned32 (1..4294967295)

This object specifies the local discriminator for this BFD session, which is used to uniquely identify it.

bfdSessRemoteDiscr

1.3.6.1.2.1.222.1.2.1.5

Unsigned32 (0 | 1..4294967295)

This object specifies the session discriminator chosen by the remote system for this BFD session. The value may be zero(0) if the remote discriminator is not yet known or if the session is in the down or adminDown(1) state.

bfdSessDestinationUdpPort

1.3.6.1.2.1.222.1.2.1.6

BfdCtrlDestPortNumberTCUDP destination port number of BFD control packets. 3784 represents single-hop BFD session. 4784 represents multi-hop BFD session. 6784 represents BFD on Link Aggregation Group (LAG) session. However, syntax is left open to wider range of values purposely for two reasons: 1. Implementation uses non-compliant port number for valid proprietary reason. 2. Potential future extension documents. The value of 0 is a special, reserved value used to indicate special conditions and should not be considered a valid port number.Reference: Use of port 3784 from Katz, D. and D. Ward, Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop), RFC 5881, June 2010. Use of port 4784 from Katz, D. and D. Ward, Bidirectional Forwarding Detection (BFD) for Multihop Paths, RFC 5883, June 2010. Use of port 6784 from Bhatia, M., Chen, M., Boutros, S., Binderberger, M., and J. Haas, Bidirectional Forwarding Detection (BFD) on Link Aggregation Group (LAG) Interfaces, RFC 7130, February 2014. (0..65535) · Unsigned32 · hint d · default 0

This object specifies the destination UDP port number used for this BFD session's Control packets. The value may be zero(0) if the session is in adminDown(1) state.

bfdSessSourceUdpPort

1.3.6.1.2.1.222.1.2.1.7

BfdCtrlSourcePortNumberTCUDP source port number of BFD control packets. However, syntax is left open to wider range of values purposely for two reasons: 1. Implementation uses non-compliant port number for valid proprietary reason. 2. Potential future extension documents. The value of 0 is a special, reserved value used to indicate special conditions and should not be considered a valid port number.Reference: Port 49152..65535 from RFC5881 (0..65535) · Unsigned32 · hint d · default 0

This object specifies the source UDP port number used for this BFD session's Control packets. The value may be zero(0) if the session is in adminDown(1) state. Upon creation of a new BFD session via this MIB, the value of zero(0) specified would permit the implementation to choose its own source port number.

bfdSessEchoSourceUdpPort

1.3.6.1.2.1.222.1.2.1.8

InetPortNumberRepresents a 16 bit port number of an Internet transport layer protocol. Port numbers are assigned by IANA. A current list of all assignments is available from <http://www.iana.org/>. The value zero is object-specific and must be defined as part of the description of any object that uses this syntax. Examples of the usage of zero might include situations where a port number is unknown, or when the value zero is used as a wildcard in a filter.Reference: STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960 (0..65535) · Unsigned32 · hint d · default 0

This object specifies the source UDP port number used for this BFD session's Echo packets. The value may be zero(0) if the session is not running in the Echo mode, or the session is in adminDown(1) state. Upon creation of a new BFD session via this MIB, the value of zero(0) would permit the implementation to choose its own source port number.

bfdSessAdminStatus

1.3.6.1.2.1.222.1.2.1.9

INTEGER1 = enabled2 = disabled3 = adminDown4 = down · Integer32

Denotes the desired operational status of the BFD session. A transition to enabled(1) will start the BFD state machine for the session. The state machine will have an initial state of down(2). A transition to disabled(2) will stop the BFD state machine for the session. The state machine may first transition to adminDown(1) prior to stopping. A transition to adminDown(3) will cause the BFD state machine to transition to adminDown(1) and will cause the session to remain in this state. A transition to down(4) will cause the BFD state machine to transition to down(2) and will cause the session to remain in this state. Care should be used in providing write access to this object without adequate authentication.

bfdSessOperStatus

1.3.6.1.2.1.222.1.2.1.10

INTEGER1 = up2 = down3 = adminDown · Integer32

Denotes the actual operational status of the BFD session. If the value of bfdOperStatus is down(2), this value MUST eventually be down(2) as well. If the value of bfdOperStatus is adminDown(3), this value MUST eventually be adminDown(3) as well.

bfdSessState

1.3.6.1.2.1.222.1.2.1.11

IANAbfdSessStateTC1 = adminDown2 = down3 = init4 = up5 = failingBFD session state. State failing(5) is only applicable if corresponding session is running in BFD version 0.Reference: Katz, D. and D. Ward, Bidirectional Forwarding Detection (BFD), RFC 5880, June 2010. · Integer32

Configured BFD session state.

bfdSessRemoteHeardFlag

1.3.6.1.2.1.222.1.2.1.12

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object specifies the status of BFD packet reception from the remote system. Specifically, it is set to true(1) if the local system is actively receiving BFD packets from the remote system and is set to false(2) if the local system has not received BFD packets recently (within the detection time) or if the local system is attempting to tear down the BFD session.

bfdSessDiag

1.3.6.1.2.1.222.1.2.1.13

IANAbfdDiagTC0 = noDiagnostic1 = controlDetectionTimeExpired2 = echoFunctionFailed3 = neighborSignaledSessionDown4 = forwardingPlaneReset5 = pathDown6 = concatenatedPathDown7 = administrativelyDown8 = reverseConcatenatedPathDown9 = misConnectivityDefectA common BFD diagnostic code.Reference: Katz, D. and D. Ward, Bidirectional Forwarding Detection (BFD), RFC 5880, June 2010. Allan, D., Swallow, G., and Drake, J., Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport Profile, RFC 6428, November 2011. · Integer32

A diagnostic code specifying the local system's reason for the last transition of the session from up(4) to some other state.

bfdSessOperMode

1.3.6.1.2.1.222.1.2.1.14

IANAbfdSessOperModeTC1 = asyncModeWEchoFunction2 = asynchModeWOEchoFunction3 = demandModeWEchoFunction4 = demandModeWOEchoFunctionBFD session operating modeReference: Katz, D. and D. Ward, Bidirectional Forwarding Detection (BFD), RFC 5880, June 2010. · Integer32

This object specifies the operational mode of this BFD session.

bfdSessDemandModeDesiredFlag

1.3.6.1.2.1.222.1.2.1.15

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32 · default false (2)

This object indicates the local system's desire to use Demand mode. Specifically, it is set to true(1) if the local system wishes to use Demand mode or false(2) if not.

bfdSessControlPlaneIndepFlag

1.3.6.1.2.1.222.1.2.1.16

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32 · default false (2)

This object indicates the local system's ability to continue to function through a disruption of the control plane. Specifically, it is set to true(1) if the local system BFD implementation is independent of the control plane. Otherwise, the value is set to false(2).

bfdSessMultipointFlag

1.3.6.1.2.1.222.1.2.1.17

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32 · default false (2)

This object indicates the Multipoint (M) bit for this session. It is set to true(1) if the Multipoint (M) bit is set to 1. Otherwise, the value is set to false(2).

bfdSessInterface

1.3.6.1.2.1.222.1.2.1.18

InterfaceIndexOrZeroThis textual convention is an extension of the InterfaceIndex convention. The latter defines a greater than zero value used to identify an interface or interface sub-layer in the managed system. This extension permits the additional value of zero. the value zero is object-specific and must therefore be defined as part of the description of any object which uses this syntax. Examples of the usage of zero might include situations where interface was unknown, or when none or all interfaces need to be referenced. (0..2147483647) · Integer32 · hint d

This object contains an interface index used to indicate the interface that this BFD session is running on. This value can be zero if there is no interface associated with this BFD session.

bfdSessSrcAddrType

1.3.6.1.2.1.222.1.2.1.19

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

This object specifies the IP address type of the source IP address of this BFD session. The value of unknown(0) is allowed only when the session is singleHop(1) and the source IP address of this BFD session is derived from the outgoing interface, or when the BFD session is not associated with a specific interface. If any other unsupported values are attempted in a set operation, the agent MUST return an inconsistentValue error.

bfdSessSrcAddr

1.3.6.1.2.1.222.1.2.1.20

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

This object specifies the source IP address of this BFD session. The format of this object is controlled by the bfdSessSrcAddrType object.

bfdSessDstAddrType

1.3.6.1.2.1.222.1.2.1.21

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

This object specifies the IP address type of the neighboring IP address that is being monitored with this BFD session. The value of unknown(0) is allowed only when the session is singleHop(1) and the outgoing interface is of type point to point, or when the BFD session is not associated with a specific interface. If any other unsupported values are attempted in a set operation, the agent MUST return an inconsistentValue error.

bfdSessDstAddr

1.3.6.1.2.1.222.1.2.1.22

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

This object specifies the neighboring IP address that is being monitored with this BFD session. The format of this object is controlled by the bfdSessDstAddrType object.

bfdSessGTSM

1.3.6.1.2.1.222.1.2.1.23

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32 · default true (1)

Setting the value of this object to false(2) will disable GTSM protection of the BFD session. GTSM MUST be enabled on a singleHop(1) session if no authentication is in use.

bfdSessGTSMTTL

1.3.6.1.2.1.222.1.2.1.24

Unsigned32 (0..255) · default 255

This object is valid only when bfdSessGTSM protection is enabled on the system. This object indicates the minimum allowed Time to Live (TTL) for received BFD Control packets. For a singleHop(1) session, if GTSM protection is enabled, this object SHOULD be set to the maximum TTL value allowed for a single hop. By default, GTSM is enabled and the TTL value is 255. For a multihop session, updating of the maximum TTL value allowed is likely required.

bfdSessDesiredMinTxInterval

1.3.6.1.2.1.222.1.2.1.25

BfdIntervalTCThe BFD interval in microseconds. · Unsigned32 · hint d

This object specifies the minimum interval, in microseconds, that the local system would like to use when transmitting BFD Control packets. The value of zero(0) is reserved in this case and should not be used.

bfdSessReqMinRxInterval

1.3.6.1.2.1.222.1.2.1.26

BfdIntervalTCThe BFD interval in microseconds. · Unsigned32 · hint d

This object specifies the minimum interval, in microseconds, between received BFD Control packets the local system is capable of supporting. The value of zero(0) can be specified when the transmitting system does not want the remote system to send any periodic BFD Control packets.

bfdSessReqMinEchoRxInterval

1.3.6.1.2.1.222.1.2.1.27

BfdIntervalTCThe BFD interval in microseconds. · Unsigned32 · hint d

This object specifies the minimum interval, in microseconds, between received BFD Echo packets that this system is capable of supporting. The value must be zero(0) if this is a multihop BFD session.

bfdSessDetectMult

1.3.6.1.2.1.222.1.2.1.28

BfdMultiplierTCThe BFD failure detection multiplier. (1..255) · Unsigned32 · hint d

This object specifies the Detect time multiplier.

bfdSessNegotiatedInterval

1.3.6.1.2.1.222.1.2.1.29

BfdIntervalTCThe BFD interval in microseconds. · Unsigned32 · hint d

This object specifies the negotiated interval, in microseconds, that the local system is transmitting BFD Control packets.

bfdSessNegotiatedEchoInterval

1.3.6.1.2.1.222.1.2.1.30

BfdIntervalTCThe BFD interval in microseconds. · Unsigned32 · hint d

This object specifies the negotiated interval, in microseconds, that the local system is transmitting BFD Echo packets. The value is expected to be zero if the sessions are not running in Echo mode.

bfdSessNegotiatedDetectMult

1.3.6.1.2.1.222.1.2.1.31

BfdMultiplierTCThe BFD failure detection multiplier. (1..255) · Unsigned32 · hint d

This object specifies the Detect time multiplier.

bfdSessAuthPresFlag

1.3.6.1.2.1.222.1.2.1.32

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32 · default false (2)

This object indicates 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(2) if not.

bfdSessAuthenticationType

1.3.6.1.2.1.222.1.2.1.33

IANAbfdSessAuthenticationTypeTC-1 = noAuthentication0 = reserved1 = simplePassword2 = keyedMD53 = meticulousKeyedMD54 = keyedSHA15 = meticulousKeyedSHA1BFD authentication typeReference: Sections 4.2 - 4.4 from Katz, D. and D. Ward, Bidirectional Forwarding Detection (BFD), RFC 5880, June 2010. · Integer32 · default noAuthentication (-1)

The authentication type used for this BFD session. This field is valid only when the Authentication Present bit is set. MAX-ACCESS to this object as well as other authentication-related objects are set to read-create in order to support management of a single key ID at a time; key rotation is not handled. Key update in practice must be done by atomic update using a set containing all affected objects in the same varBindList or otherwise risk the session dropping.

bfdSessAuthenticationKeyID

1.3.6.1.2.1.222.1.2.1.34

Integer32 (-1 | 0..255) · default -1

The authentication key ID in use for this session. This object permits multiple keys to be active simultaneously. The value -1 indicates that no authentication key ID will be present in the optional BFD Authentication Section.

bfdSessAuthenticationKey

1.3.6.1.2.1.222.1.2.1.35

IANAbfdSessAuthenticationKeyTCBFD authentication key type. An IANAbfdSessAuthenticationKeyTC is always interpreted within the context of an IANAbfdSessAuthenticationTypeTC value. Every usage of the IANAbfdSessAuthenticationTypeTC textual convention is required to specify the IANAbfdSessAuthenticationKeyTC object that provides the context. It is suggested that the IANAbfdSessAuthenticationKeyTC object be logically registered before the object(s) that use the IANAbfdSessAuthenticationKeyTC textual convention, if they appear in the same logical row. The value of an IANAbfdSessAuthenticationKeyTC must always be consistent with the value of the associated IANAbfdSessAuthenticationTypeTC object. Attempts to set an IANAbfdSessAuthenticationKeyTC object to a value inconsistent with the associated IANAbfdSessAuthenticationTypeTC must fail with an inconsistentValue error. The following size constraints for an IANAbfdSessAuthenticationKeyTC object are defined for the associated IANAbfdSessAuthenticationTypeTC values show below: noAuthentication(-1): SIZE(0) reserved(0): SIZE(0) simplePassword(1): SIZE(1..16) keyedMD5(2): SIZE(16) meticulousKeyedMD5(3): SIZE(16) keyedSHA1(4): SIZE(20) meticulousKeyedSHA1(5): SIZE(20) When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise, the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate.Reference: Sections 4.2 - 4.4 from Katz, D. and D. Ward, Bidirectional Forwarding Detection (BFD), RFC 5880, June 2010. SIZE (0..252) · OCTET STRING · hint 1x

The authentication key. When the bfdSessAuthenticationType is simplePassword(1), the value of this object is the password present in the BFD packets. When the bfdSessAuthenticationType is one of the keyed authentication types, this value is used in the computation of the key present in the BFD authentication packet.

bfdSessStorageType

1.3.6.1.2.1.222.1.2.1.36

StorageType1 = other2 = volatile3 = nonVolatile4 = permanent5 = readOnlyDescribes the memory realization of a conceptual row. A row which is volatile(2) is lost upon reboot. A row which is either nonVolatile(3), permanent(4) or readOnly(5), is backed up by stable storage. A row which is permanent(4) can be changed but not deleted. A row which is readOnly(5) cannot be changed nor deleted. If the value of an object with this syntax is either permanent(4) or readOnly(5), it cannot be written. Conversely, if the value is either other(1), volatile(2) or nonVolatile(3), it cannot be modified to be permanent(4) or readOnly(5). (All illegal modifications result in a 'wrongValue' error.) Every usage of this textual convention is required to specify the columnar objects which a permanent(4) row must at a minimum allow to be writable. · Integer32

This variable indicates the storage type for this object. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.

bfdSessRowStatus

1.3.6.1.2.1.222.1.2.1.37

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

This variable is used to create, modify, and/or delete a row in this table. When a row in this table has a row in the active(1) state, no objects in this row can be modified except the bfdSessRowStatus and bfdSessStorageType.

bfdSessPerfTable

1.3.6.1.2.1.222.1.3

augments bfdSessTable

Index: bfdSessIndex

This table specifies BFD session performance counters.

bfdSessPerfCtrlPktIn

1.3.6.1.2.1.222.1.3.1.1

Counter32

The total number of BFD control messages received for this BFD session. It MUST be equal to the least significant 32 bits of bfdSessPerfCtrlPktInHC if supported, and MUST do so with the rules spelled out in RFC 2863.

bfdSessPerfCtrlPktOut

1.3.6.1.2.1.222.1.3.1.2

Counter32

The total number of BFD control messages sent for this BFD session. It MUST be equal to the least significant 32 bits of bfdSessPerfCtrlPktOutHC if supported, and MUST do so with the rules spelled out in RFC 2863.

bfdSessPerfCtrlPktDrop

1.3.6.1.2.1.222.1.3.1.3

Counter32

The total number of BFD control messages received for this session yet dropped for being invalid. It MUST be equal to the least significant 32 bits of bfdSessPerfCtrlPktDropHC if supported, and MUST do so with the rules spelled out in RFC 2863.

bfdSessPerfCtrlPktDropLastTime

1.3.6.1.2.1.222.1.3.1.4

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

The value of sysUpTime on the most recent occasion at which received the BFD control message for this session was dropped. If no such up event exists, this object contains a zero value.

bfdSessPerfEchoPktIn

1.3.6.1.2.1.222.1.3.1.5

Counter32

The total number of BFD Echo messages received for this BFD session. It MUST be equal to the least significant 32 bits of bfdSessPerfEchoPktInHC if supported, and MUST do so with the rules spelled out in RFC 2863.

bfdSessPerfEchoPktOut

1.3.6.1.2.1.222.1.3.1.6

Counter32

The total number of BFD Echo messages sent for this BFD session. It MUST be equal to the least significant 32 bits of bfdSessPerfEchoPktOutHC if supported, and MUST do so with the rules spelled out in RFC 2863.

bfdSessPerfEchoPktDrop

1.3.6.1.2.1.222.1.3.1.7

Counter32

The total number of BFD Echo messages received for this session yet dropped for being invalid. It MUST be equal to the least significant 32 bits of bfdSessPerfEchoPktDropHC if supported, and MUST do so with the rules spelled out in RFC 2863.

bfdSessPerfEchoPktDropLastTime

1.3.6.1.2.1.222.1.3.1.8

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

The value of sysUpTime on the most recent occasion at which received the BFD Echo message for this session was dropped. If no such up event has been issued, this object contains a zero value.

bfdSessUpTime

1.3.6.1.2.1.222.1.3.1.9

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

The value of sysUpTime on the most recent occasion at which the session came up. If no such event has been issued, this object contains a zero value.

bfdSessPerfLastSessDownTime

1.3.6.1.2.1.222.1.3.1.10

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

The value of sysUpTime on the most recent occasion at which the last time communication was lost with the neighbor. If no down event has been issued, this object contains a zero value.

bfdSessPerfLastCommLostDiag

1.3.6.1.2.1.222.1.3.1.11

IANAbfdDiagTC0 = noDiagnostic1 = controlDetectionTimeExpired2 = echoFunctionFailed3 = neighborSignaledSessionDown4 = forwardingPlaneReset5 = pathDown6 = concatenatedPathDown7 = administrativelyDown8 = reverseConcatenatedPathDown9 = misConnectivityDefectA common BFD diagnostic code.Reference: Katz, D. and D. Ward, Bidirectional Forwarding Detection (BFD), RFC 5880, June 2010. Allan, D., Swallow, G., and Drake, J., Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport Profile, RFC 6428, November 2011. · Integer32

The BFD diag code for the last time communication was lost with the neighbor. If such an event has not been issued, this object contains a zero value.

bfdSessPerfSessUpCount

1.3.6.1.2.1.222.1.3.1.12

Counter32

The number of times this session has gone into the Up state since the system last rebooted.

bfdSessPerfDiscTime

1.3.6.1.2.1.222.1.3.1.13

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

The value of sysUpTime on the most recent occasion at which any one or more of the session counters suffered a discontinuity. The relevant counters are the specific instances associated with this BFD session of any Counter32 object contained in the BfdSessPerfTable. If no such discontinuities have occurred since the last reinitialization of the local management subsystem, then this object contains a zero value.

bfdSessPerfCtrlPktInHC

1.3.6.1.2.1.222.1.3.1.14

Counter64 (0..18446744073709551615)

This value represents the total number of BFD control messages received for this BFD session. The least significant 32 bits MUST be equal to bfdSessPerfCtrlPktIn, and MUST do so with the rules spelled out in RFC 2863.

bfdSessPerfCtrlPktOutHC

1.3.6.1.2.1.222.1.3.1.15

Counter64 (0..18446744073709551615)

This value represents the total number of BFD control messages transmitted for this BFD session. The least significant 32 bits MUST be equal to bfdSessPerfCtrlPktOut, and MUST do so with the rules spelled out in RFC 2863.

bfdSessPerfCtrlPktDropHC

1.3.6.1.2.1.222.1.3.1.16

Counter64 (0..18446744073709551615)

This value represents the total number of BFD control messages received for this BFD session yet dropped for being invalid. The least significant 32 bits MUST be equal to bfdSessPerfCtrlPktDrop, and MUST do so with the rules spelled out in RFC 2863.

bfdSessPerfEchoPktInHC

1.3.6.1.2.1.222.1.3.1.17

Counter64 (0..18446744073709551615)

This value represents the total number of BFD Echo messages received for this BFD session. The least significant 32 bits MUST be equal to bfdSessPerfEchoPktIn, and MUST do so with the rules spelled out in RFC 2863.

bfdSessPerfEchoPktOutHC

1.3.6.1.2.1.222.1.3.1.18

Counter64 (0..18446744073709551615)

This value represents the total number of BFD Echo messages transmitted for this BFD session. The least significant 32 bits MUST be equal to bfdSessPerfEchoPktOut, and MUST do so with the rules spelled out in RFC 2863.

bfdSessPerfEchoPktDropHC

1.3.6.1.2.1.222.1.3.1.19

Counter64 (0..18446744073709551615)

This value represents the total number of BFD Echo messages received for this BFD session yet dropped for being invalid. The least significant 32 bits MUST be equal to bfdSessPerfEchoPktDrop, and MUST do so with the rules spelled out in RFC 2863.

bfdSessDiscMapTable

1.3.6.1.2.1.222.1.4

Index: bfdSessDiscriminator

The BFD Session Discriminator Mapping Table maps a local discriminator value to the associated BFD session's bfdSessIndex found in the bfdSessionTable.

bfdSessDiscMapIndex

1.3.6.1.2.1.222.1.4.1.1

BfdSessIndexTCAn index used to uniquely identify BFD sessions. (1..4294967295) · Unsigned32 · hint d

This object specifies a mapping between a local discriminator and a BFD session in the BfdSessTable.

bfdSessIpMapTable

1.3.6.1.2.1.222.1.5

Index: bfdSessInterface · bfdSessSrcAddrType · bfdSessSrcAddr · bfdSessDstAddrType · bfdSessDstAddr

The BFD Session IP Mapping Table maps given bfdSessInterface, bfdSessSrcAddrType, bfdSessSrcAddr, bfdSessDstAddrType, and bfdSessDstAddr to an associated BFD session found in the bfdSessionTable.

bfdSessIpMapIndex

1.3.6.1.2.1.222.1.5.1.1

BfdSessIndexTCAn index used to uniquely identify BFD sessions. (1..4294967295) · Unsigned32 · hint d

This object specifies the BfdSessIndexTC referred to by the indexes of this row. In essence, a mapping is provided between these indexes and the BfdSessTable.

Trap details

bfdSessUp

1.3.6.1.2.1.222.0.1

This notification is generated when the bfdSessState object for one or more contiguous entries in bfdSessTable are about to enter the up(4) state from some other state. The included values of bfdSessDiag MUST both be set equal to this new state (i.e., up(4)). The two instances of bfdSessDiag in this notification indicate the range of indexes that are affected. Note that all the indexes of the two ends of the range can be derived from the instance identifiers of these two objects. For the cases where a contiguous range of sessions have transitioned into the up(4) state at roughly the same time, the device SHOULD issue a single notification for each range of contiguous indexes in an effort to minimize the emission of a large number of notifications. If a notification has to be issued for just a single bfdSessEntry, then the instance identifier (and values) of the two bfdSessDiag objects MUST be identical.

bfdSessDiag

1.3.6.1.2.1.222.1.2.1.13

IANAbfdDiagTC0 = noDiagnostic1 = controlDetectionTimeExpired2 = echoFunctionFailed3 = neighborSignaledSessionDown4 = forwardingPlaneReset5 = pathDown6 = concatenatedPathDown7 = administrativelyDown8 = reverseConcatenatedPathDown9 = misConnectivityDefectA common BFD diagnostic code.Reference: Katz, D. and D. Ward, Bidirectional Forwarding Detection (BFD), RFC 5880, June 2010. Allan, D., Swallow, G., and Drake, J., Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport Profile, RFC 6428, November 2011. · Integer32

A diagnostic code specifying the local system's reason for the last transition of the session from up(4) to some other state.

bfdSessDiag

1.3.6.1.2.1.222.1.2.1.13

IANAbfdDiagTC0 = noDiagnostic1 = controlDetectionTimeExpired2 = echoFunctionFailed3 = neighborSignaledSessionDown4 = forwardingPlaneReset5 = pathDown6 = concatenatedPathDown7 = administrativelyDown8 = reverseConcatenatedPathDown9 = misConnectivityDefectA common BFD diagnostic code.Reference: Katz, D. and D. Ward, Bidirectional Forwarding Detection (BFD), RFC 5880, June 2010. Allan, D., Swallow, G., and Drake, J., Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport Profile, RFC 6428, November 2011. · Integer32

A diagnostic code specifying the local system's reason for the last transition of the session from up(4) to some other state.

bfdSessDown

1.3.6.1.2.1.222.0.2

This notification is generated when the bfdSessState object for one or more contiguous entries in bfdSessTable are about to enter the down(2) or adminDown(1) states from some other state. The included values of bfdSessDiag MUST both be set equal to this new state (i.e., down(2) or adminDown(1)). The two instances of bfdSessDiag in this notification indicate the range of indexes that are affected. Note that all the indexes of the two ends of the range can be derived from the instance identifiers of these two objects. For cases where a contiguous range of sessions have transitioned into the down(2) or adminDown(1) states at roughly the same time, the device SHOULD issue a single notification for each range of contiguous indexes in an effort to minimize the emission of a large number of notifications. If a notification has to be issued for just a single bfdSessEntry, then the instance identifier (and values) of the two bfdSessDiag objects MUST be identical.

bfdSessDiag

1.3.6.1.2.1.222.1.2.1.13

IANAbfdDiagTC0 = noDiagnostic1 = controlDetectionTimeExpired2 = echoFunctionFailed3 = neighborSignaledSessionDown4 = forwardingPlaneReset5 = pathDown6 = concatenatedPathDown7 = administrativelyDown8 = reverseConcatenatedPathDown9 = misConnectivityDefectA common BFD diagnostic code.Reference: Katz, D. and D. Ward, Bidirectional Forwarding Detection (BFD), RFC 5880, June 2010. Allan, D., Swallow, G., and Drake, J., Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport Profile, RFC 6428, November 2011. · Integer32

A diagnostic code specifying the local system's reason for the last transition of the session from up(4) to some other state.

bfdSessDiag

1.3.6.1.2.1.222.1.2.1.13

IANAbfdDiagTC0 = noDiagnostic1 = controlDetectionTimeExpired2 = echoFunctionFailed3 = neighborSignaledSessionDown4 = forwardingPlaneReset5 = pathDown6 = concatenatedPathDown7 = administrativelyDown8 = reverseConcatenatedPathDown9 = misConnectivityDefectA common BFD diagnostic code.Reference: Katz, D. and D. Ward, Bidirectional Forwarding Detection (BFD), RFC 5880, June 2010. Allan, D., Swallow, G., and Drake, J., Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport Profile, RFC 6428, November 2011. · Integer32

A diagnostic code specifying the local system's reason for the last transition of the session from up(4) to some other state.

↑ To TOC