H3C-BFD-STD-MIB
AI MIB Summary
The H3C-BFD-STD-MIB module enables monitoring and management of Bidirectional Forwarding Detection (BFD) session states, detection timers, and failure events on H3C network devices to ensure rapid fault detection in IP forwarding paths.
Bidirectional Forwarding Management Information Base.
Main OID:
h3cBfdMIB.1.3.6.1.4.1.2011.10.2.72
46
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
46 total| Object Name |
|---|
h3cBfdMIBBidirectional Forwarding Management Information Base. MODULE-IDENTITY .1.3.6.1.4.1.2011.10.2.72 |
h3cBfdNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.72.0 |
h3cBfdSessStateChangeA notification sent when an session changes state, entering state up or entering state down. The session will enter state up finishing three times handshakes , and will enter state down when the communication path is out of work. When the h3cBfdSessState's value is state up, the session enters state up, and the session enters state down when the h3cBfdSessState's value is state down. The h3cBfdSessIfIndex contains an interface's index under which the BFD session runs. The h3cBfdSessIndex contains an index which represents a unique BFD session on this device. The h3cBfdSessState is the state of the running BFD session. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.10.2.72.0.1 |
h3cBfdSessAuthFailA notification sent when receiving a session with an authentication fail. The h3cBfdIfIndex is an index which represents a unique BFD interface on this device. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.10.2.72.0.2 |
h3cBfdObjects OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.72.1 |
h3cBfdGlobalObjects OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.72.1.1 |
h3cBfdVersionNumberIt indicates the BFD session's current version number.ro Unsigned32 .1.3.6.1.4.1.2011.10.2.72.1.1.1 |
h3cBfdSysInitModeA system may take either an active role or a passive role in session initialization. A system taking the active role must send BFD control packets for a particular session, regardless of whether it has received any BFD packets for that session. A system taking the passive role must not begin sending BFD packets for a particular session until it has received a BFD packet for that session, and thus has learned the remote system's discriminator value.rw Enumeration .1.3.6.1.4.1.2011.10.2.72.1.1.2 |
h3cBfdSessNotificationsEnableThis variable enables the emission of h3cBfdSessStateChange and h3cBfdSessAuthFail notifications if this variable is set to true(1); otherwise these notifications are not emitted.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.72.1.1.3 |
h3cBfdIfTableThis Table describes the BFD interface specific information. SEQUENCE OF H3cBfdIfEntry .1.3.6.1.4.1.2011.10.2.72.1.2 |
h3cBfdIfEntryThis Entry describes the BFD interface specific information. H3cBfdIfEntry .1.3.6.1.4.1.2011.10.2.72.1.2.1 |
h3cBfdIfIndexThis variable contains an index that represents a unique BFD interface on this device.ro InterfaceIndex (IF-MIB) .1.3.6.1.4.1.2011.10.2.72.1.2.1.1 |
h3cBfdIfDesiredMinTxIntervalThis variable defines the minimum interval, in microseconds, that the interface would like to use when transmitting BFD Control packets.rw BfdInterval .1.3.6.1.4.1.2011.10.2.72.1.2.1.2 |
h3cBfdIfDesiredMinRxIntervalThis variable defines the minimum interval, in, microseconds, between received BFD Control packets the local system is capable of supporting.rw BfdInterval .1.3.6.1.4.1.2011.10.2.72.1.2.1.3 |
h3cBfdIfDetectMultThe desired detect time multiplier for BFD control packets. The negotiated control packet transmission interval, multiplied by this variable, will be the detection time for this session (as seen by the remote system.) The variable must be a nonzero integer.rw Unsigned32 .1.3.6.1.4.1.2011.10.2.72.1.2.1.4 |
h3cBfdIfAuthTypeThe Authentication Type used for this interface. This field is valid only when the Authentication Present bit is set. The 'none' indicates the session doesn't support authentication. The 'simple' indicates the session supports simple password authentication. The 'md5' indicates the session supports Keyed MD5 authentication. The 'mmd5' indicates the session supports Meticulous Keyed MD5 authentication. The 'sha1' indicates the session supports Keyed SHA1 authentication. The 'msha1' indicates the session supports Meticulous Keyed SHA1 authentication.ro Enumeration .1.3.6.1.4.1.2011.10.2.72.1.2.1.5 |
h3cBfdSessTableThis table describes the BFD sessions. SEQUENCE OF H3cBfdSessEntry .1.3.6.1.4.1.2011.10.2.72.1.3 |
h3cBfdSessEntryThis Entry describes the BFD sessions. H3cBfdSessEntry .1.3.6.1.4.1.2011.10.2.72.1.3.1 |
h3cBfdSessIfIndexThis variable contains an interface's index under which the BFD session runs.ro InterfaceIndex (IF-MIB) .1.3.6.1.4.1.2011.10.2.72.1.3.1.1 |
h3cBfdSessIndexThis variable contains an index which represents a unique BFD session on this device.ro BfdSessIndexTC .1.3.6.1.4.1.2011.10.2.72.1.3.1.2 |
h3cBfdSessAppSupportIdThis variable contains an ID used to indicate a local application which owns or maintains this BFD session. Note, a BFD session can support several route protocols. This is a bit-map of possible conditions. The corresponding bit positions are: |0 |none | |1 |ospf | |2 |isis | |3 |bgp | |4 |mpls |ro Bits .1.3.6.1.4.1.2011.10.2.72.1.3.1.3 |
h3cBfdSessLocalDiscrThis variable defines the local discriminator for this BFD session, used to uniquely identify it.ro Unsigned32 .1.3.6.1.4.1.2011.10.2.72.1.3.1.4 |
h3cBfdSessRemoteDiscrThis variable defines the session discriminator chosen by the remote system for this BFD session.ro Unsigned32 .1.3.6.1.4.1.2011.10.2.72.1.3.1.5 |
h3cBfdSessDstPortThe UDP Port for BFD. The default value is the well-known value for this port.ro InetPortNumber (INET-ADDRESS-MIB) .1.3.6.1.4.1.2011.10.2.72.1.3.1.6 |
h3cBfdSessOperModeThis variable defines current operating mode that BFD session is running in. The primary mode which the BFD session runs in is known as Asynchronous mode. In this mode, the systems periodically send BFD Control packets to one another, and if a number of those packets in a row are not received by the other system, the session is declared to be down. The second mode is known as Demand mode. In this mode, it is assumed that each system has an independent way of verifying that it has connectivity to the other system. Once a BFD session is established, the systems stop sending BFD Control packets, except when either system feels the need to verify connectivity explicitly, in which case a short sequence of BFD Control packets is sent, and then the protocol quiesces. An adjunct to both modes is the Echo function. When the Echo function is active, a stream of BFD Echo packets is transmitted in such a way as to have the other system loop them back through its forwarding path. If a number of packets of the echoed data stream are not received, the session is declared to be down. The Echo function may be used with either Asynchronous or Demand modes. The 'asynchModeWOEchoFun' indicates this BFD session operates in the Asynchronous mode, and doesn't support the Echo Function. The 'demandModeWOEchoFunction' indicates this BFD session operates in the Demand mode, and doesn't support the Echo Function. The 'asyncModeWEchoFun' indicates this BFD session operates in the Asynchronous mode, and also supports the Echo Function. The 'demandModeWEchoFunction' indicates this BFD session operates in the Demand mode, and also supports the Echo Function.ro Enumeration .1.3.6.1.4.1.2011.10.2.72.1.3.1.7 |
h3cBfdSessAddrTypeThis object defines IP address type of the interface associated with this BFD session. Only values unknown(0), ipv4(1) or ipv6(2) have to be supported. A value of unknown(0) is allowed only when 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.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.2011.10.2.72.1.3.1.8 |
h3cBfdSessLocalAddrThis variable defines IP address of the local interface from which the BFD packets is transmitted. It can also be used to enabled BFD on a specific interface. The value is set to zero when BFD session is not associated with a specific interface.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.2011.10.2.72.1.3.1.9 |
h3cBfdSessRemoteAddrThis variable defines IP address of the remote interface from which the BFD packets is transmitted. It can also be used to enabled BFD on a specific interface. The value is set to zero when BFD session is not associated with a specific interface.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.2011.10.2.72.1.3.1.10 |
h3cBfdSessLocalDiagThe BFD diagnostic code for the BFD session was down with the neighbor. If no such event happens this object contains a zero value.ro BfdDiag .1.3.6.1.4.1.2011.10.2.72.1.3.1.11 |
h3cBfdSessStateThe state of the running BFD session. There are three states through which a session normally proceeds, two for establishing a session (Init and Up) and one for tearing down a session (Down.) This allows a three-way handshake for both session establishment and session teardown (assuring that both systems are aware of all session state changes.) A fourth state (AdminDown) exists so that a session can be administratively put down indefinitely. The Down state means that the session is down (or has just been created.) A session remains in Down state until the remote system indicates that it agrees that the session is down by sending a BFD Control packet with the State field set to anything other than Up. If that packet signals Down state, the session advances to Init state; if that packet signals Init state, the session advances to Up state. Init state means that the remote system is 0communicating, and the local system desires to bring the session up, but the remote system does not yet realize it. A session will remain in Init state until either a BFD Control Packet is received that is signaling Init or Up state (in which case the session advances to Up state) or until the detection time expires, meaning that communication with the remote system has been lost (in which case the session advances to Down state.) Up state means that the BFD session has successfully been established, and implies that connectivity between the systems is working. The session will remain in the Up state until either connectivity fails, or the session is taken down administratively. If either the remote system signals Down state, or the detection time expires, the session advances to Down state. AdminDown state means that the session is being held administratively down. This causes the remote system to enter Down state, and remain there until the local system exits AdminDown state.ro Enumeration .1.3.6.1.4.1.2011.10.2.72.1.3.1.12 |
h3cBfdSessControlPlanIndepFlagThis variable indicates whether the local system can continue to work while the control plane is out of work. Specifically, it is set to true(1) if the local system is independent of the control plane. Otherwise, the value is set to false(0)ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.72.1.3.1.13 |
h3cBfdSessAuthFlagThis variable indicates that the local system wants 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.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.72.1.3.1.14 |
h3cBfdSessDemandModeFlagThis variable indicates that the local system wants to use Demand mode. Specifically, it is set to true(1) if the local system wishes to use Demand mode or false(0) if notro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.72.1.3.1.15 |
h3cBfdSessStatTableThe table defines BFD session state. SEQUENCE OF H3cBfdSessStatEntry .1.3.6.1.4.1.2011.10.2.72.1.4 |
h3cBfdSessStatEntryAn entry in this table is created by a BFD-enabled node for every BFD Session. It defines BFD session statistics. H3cBfdSessStatEntry .1.3.6.1.4.1.2011.10.2.72.1.4.1 |
h3cBfdSessStatPktInHCThe total number of BFD messages received by this BFD session.ro Counter64 .1.3.6.1.4.1.2011.10.2.72.1.4.1.1 |
h3cBfdSessStatPktOutHCThe total number of BFD messages sent by this BFD session.ro Counter64 .1.3.6.1.4.1.2011.10.2.72.1.4.1.2 |
h3cBfdSessStatDownCountThe number of times this session has gone into the Down state since the router last rebooted.ro Counter32 .1.3.6.1.4.1.2011.10.2.72.1.4.1.3 |
h3cBfdSessStatPktDiscardThe number of packets the local system has discarded since the router last rebooted.ro Counter64 .1.3.6.1.4.1.2011.10.2.72.1.4.1.4 |
h3cBfdSessStatPktLostThe number of packets the local system has failed to transmit since the router last rebooted.ro Counter64 .1.3.6.1.4.1.2011.10.2.72.1.4.1.5 |
h3cBfdSessPerfTableThe table defines BFD session performance. SEQUENCE OF H3cBfdSessPerfEntry .1.3.6.1.4.1.2011.10.2.72.1.5 |
h3cBfdSessPerfEntryAn entry in this table is created by a BFD-enabled node for every BFD session. It defines BFD Session performance. H3cBfdSessPerfEntry .1.3.6.1.4.1.2011.10.2.72.1.5.1 |
h3cBfdSessPerfCreatTimeThe value of sysUpTime when the session was created. If no such create event exists this object contains a zero value.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.72.1.5.1.1 |
h3cBfdSessPerfLastUpTimeThe value of sysUpTime when the last time communication was lost. If no such up event exists this variable contains a zero value.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.72.1.5.1.2 |
h3cBfdSessPerfLastDownTimeThe value of sysUpTime when the last time communication was lost with the neighbor. If no such event exist this variable contains a zero value.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.72.1.5.1.3 |
h3cBfdConformance OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.72.2 |