AX-BFD-TC-MIB
ALAXALA Networks CorporationThis MIB module defines TEXTUAL-CONVENTIONs for concepts used in Bidirectional Forwarding Detection (BFD) protocols.
snmptranslate -m AX-BFD-TC-MIB -Tpsnmpwalk -v2c -c <community> -m AX-BFD-TC-MIB <host> 1.3.6.1.4.1.21839.2.4.1.204Imports
| AX-SMI-MIB | axMib |
|---|---|
| SNMPv2-CONF | MODULE-COMPLIANCE, NOTIFICATION-GROUP |
| SNMPv2-SMI | Bits, Integer32, IpAddress, MODULE-IDENTITY, MibIdentifier, OBJECT-IDENTITY, OBJECT-TYPE, TimeTicks, Unsigned32, iso |
| SNMPv2-TC | DisplayString, PhysAddress, TEXTUAL-CONVENTION |
OID tree
| Name | OID | Type | Access | Status |
|---|---|---|---|---|
| IaxBfdTCMib | 1.3.6.1.4.1.21839.2.4.1.204 | |||
identity This MIB module defines TEXTUAL-CONVENTIONs for concepts used in Bidirectional Forwarding Detection (BFD) protocols. | ||||
Textual conventions
BfdCtrlDestPortNumberTCUnsigned32 (0..65535)Display hint:
dUDP destination port number of BFD control packets. 3784 represents single hop BFD session. 4784 represents multi hop BFD 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 drafts.
BfdCtrlSourcePortNumberTCUnsigned32 (0..65535)Display hint:
dUDP 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 drafts.
BfdDiagTCINTEGERadministrativelyDown(7)concatenatedPathDown(6)controlDetectionTimeExpired(1)echoFunctionFailed(2)forwardingPlaneReset(4)neighborSignaledSessionDown(3)noDiagnostic(0)pathDown(5)reverseConcatenatedPathDown(8)A common BFD diagnostic code.
BfdIntervalTCUnsigned32 (0..4294967295)Display hint:
dThe BFD interval in microseconds.
BfdMultiplierTCUnsigned32 (1..255)Display hint:
dThe BFD failure detection multiplier.
BfdSessAuthenticationTypeTCINTEGERkeyedMD5(2)keyedSHA1(4)meticulousKeyedMD5(3)meticulousKeyedSHA1(5)noAuthentication(-1)reserved(0)simplePassword(1)BFD authentication type
BfdSessIndexTCUnsigned32 (1..4294967295)Display hint:
dAn index used to uniquely identify BFD sessions.
BfdSessOperModeTCINTEGERasyncModeWEchoFunction(1)asynchModeWOEchoFunction(2)demandModeWEchoFunction(3)demandModeWOEchoFunction(4)BFD session operating mode
BfdSessStateTCINTEGERadminDown(1)down(2)failing(5)init(3)up(4)BFD session state. State failing(5) is only applicable if corresponding session is running in BFD version 0.
BfdSessTypeTCINTEGERmultiHopOutOfBandSignaling(3)multiHopTotallyArbitraryPaths(2)multiHopUnidirectionalLinks(4)multiPointHead(5)multiPointTail(6)singleHop(1)BFD session type
BfdSessionAuthenticationKeyTCOCTET STRING (SIZE (0..252))Display hint:
1xBFD authentication key type. A BfdSessionAuthenticationKeyTC is always interpreted within the context of an BfdSessAuthenticationTypeTC value. Every usage of the BfdSessionAuthenticationTypeTC textual convention is required to specify the BfdSessionAuthenticationKeyTC object that provides the context. It is suggested that the BfdSessionAuthentcationTypeTC object be logically registered before the object(s) that use the BfdSessionAuthenticationKeyTC textual convention, if they appear in the same logical row. The value of a BfdSessionAuthenticationKeyTC must always be consistent with the value of the associated BfdSessionAuthencationTypeTC object. Attempts to set a BfdSessionAuthenticationKeyTC object to a value inconsistent with the associated BfdSessionAuthenticationTypeTC must fail with an inconsistentValue error. The following size constraints for a BfdSessionAuthenticationKeyTC object are defined for the associated BfdSessionAuthenticationTypeTC 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.