All MIBs › A3COM-HUAWEI-BFD-STD-MIB › h3cBfdSessOperMode
h3cBfdSessOperMode
Module: A3COM-HUAWEI-BFD-STD-MIB
OID (symbolic): A3COM-HUAWEI-BFD-STD-MIB::h3cBfdSessOperMode
OID (numeric): 1.3.6.1.4.1.43.45.1.10.2.72.1.3.1.7
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: This 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.
What is h3cBfdSessOperMode?
Shows the current operating mode: Asynchronous (periodic packet exchange) or Demand (on-demand polling). Network engineers monitor this to confirm the session runs in the intended mode for their topology. Asynchronous mode provides continuous monitoring; Demand reduces traffic.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.43.45.1.10.2.72.1.3.1.7 snmpwalk -v2c -c public <target> A3COM-HUAWEI-BFD-STD-MIB::h3cBfdSessOperMode
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.43.45.1.10.2.72.1.3.1.7.1 snmpget -v2c -c public <target> A3COM-HUAWEI-BFD-STD-MIB::h3cBfdSessOperMode.1
Start monitoring H3C routers and switches with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the A3COM-HUAWEI-BFD-STD-MIB::h3cBfdSessOperMode OID value, configure state conditions and alerts, and monitor any H3C routers and switches from a single console.
OID Breakdown
Upper-level ancestors (11 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.43 | a3Com | A3COM-AUDL-R1-MIB |
| 1.3.6.1.4.1.43.45 | jv_mib | A3COM-HUAWEI-OID-MIB |
| 1.3.6.1.4.1.43.45.1 | huawei | A3COM-HUAWEI-OID-MIB |
| 1.3.6.1.4.1.43.45.1.10 | h3c | A3COM-HUAWEI-OID-MIB |
| 1.3.6.1.4.1.43.45.1.10.2 | h3cCommon | A3COM-HUAWEI-OID-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.43.45.1.10.2.72 | h3cBfdMIB | A3COM-HUAWEI-BFD-STD-MIB |
| 1.3.6.1.4.1.43.45.1.10.2.72.1 | h3cBfdObjects | A3COM-HUAWEI-BFD-STD-MIB |
| 1.3.6.1.4.1.43.45.1.10.2.72.1.3 | h3cBfdSessTable | A3COM-HUAWEI-BFD-STD-MIB |
| 1.3.6.1.4.1.43.45.1.10.2.72.1.3.1 | h3cBfdSessEntry | A3COM-HUAWEI-BFD-STD-MIB |
| 1.3.6.1.4.1.43.45.1.10.2.72.1.3.1.7 | h3cBfdSessOperMode | A3COM-HUAWEI-BFD-STD-MIB |