OID reference

h3cBfdSessOperMode

1.3.6.1.4.1.43.45.1.10.2.72.1.3.1.7

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 …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.43.45.1.10.2.72.1.3.1 (h3cBfdSessEntry)
Node code
7
Node name
h3cBfdSessOperMode
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.43.45.1.10.2.72.1.3.1.7
URN notation
urn:oid:1.3.6.1.4.1.43.45.1.10.2.72.1.3.1.7
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 43 45 1 10 2 72 1 3 1 7}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessOperMode(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessOperMode(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessOperMode(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessOperMode(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessOperMode(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessOperMode(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessOperMode(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessOperMode(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessOperMode(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessOperMode(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessOperMode(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessOperMode(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessOperMode(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessOperMode(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessOperMode(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessOperMode(7)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/43/45/1/10/2/72/1/3/1/7
  • /ISO/Identified-Organization/6/1/4/1/43/45/1/10/2/72/1/3/1/7
  • /ISO/3/6/1/4/1/43/45/1/10/2/72/1/3/1/7
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessOperMode
  • /iso/identified-organization/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessOperMode
  • /iso/identified-organization/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessOperMode
  • /iso/identified-organization/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessOperMode
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessOperMode
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessOperMode
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessOperMode
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessOperMode
  • /iso/org/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessOperMode
  • /iso/org/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessOperMode
  • /iso/org/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessOperMode
  • /iso/org/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessOperMode
  • /iso/org/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessOperMode
  • /iso/org/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessOperMode
  • /iso/org/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessOperMode
  • /iso/org/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessOperMode
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-only
Status in MIB
current
Default value
asynchModeWOEchoFun

Enumerated values

ValueName
1asynchModeWOEchoFun
2demandModeWOEchoFunction
3asyncModeWEchoFun
4demandModeWEchoFunction

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.

Published row index: h3cBfdSessIfIndex, h3cBfdSessIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.43.45.1.10.2.72.1.3.1.7

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

h3cBfdSessOperMode · current

h3cBfdSessOperMode OBJECT-TYPE
       SYNTAX   INTEGER {
                            asynchModeWOEchoFun(1),
                            demandModeWOEchoFunction(2),
                            asyncModeWEchoFun(3),
                            demandModeWEchoFunction(4)

       }
       MAX-ACCESS   read-only
       STATUS   current
       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.                           
           "
       DEFVAL { asynchModeWOEchoFun }
       ::= { h3cBfdSessEntry 7 }

h3cBfdSessOperMode · current

h3cBfdSessOperMode OBJECT-TYPE
       SYNTAX   INTEGER {
                            asynchModeWOEchoFun(1),
                            demandModeWOEchoFunction(2),
                            asyncModeWEchoFun(3),
                            demandModeWEchoFunction(4)

       }
       MAX-ACCESS   read-only
       STATUS   current
       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.                           
           "
       DEFVAL { asynchModeWOEchoFun }
       ::= { h3cBfdSessEntry 7 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

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.

Sources for this description

3Com MIB copies (LibreNMS/Observium Community)Netdisco MIB archive copies

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 13Com MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies1 record · 2 sources

Description 1

h3cBfdSessOperMode · current3Com MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies2 sources

Status in source: current.

Names: h3cBfdSessOperMode

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cBfdSessOperMode",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "asynchModeWOEchoFun",
    "(",
    "1",
    ")",
    ",",
    "demandModeWOEchoFunction",
    "(",
    "2",
    ")",
    ",",
    "asyncModeWEchoFun",
    "(",
    "3",
    ")",
    ",",
    "demandModeWEchoFunction",
    "(",
    "4",
    ")",
    "}",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "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. \"",
    "DEFVAL",
    "{",
    "asynchModeWOEchoFun",
    "}",
    "::=",
    "{",
    "h3cBfdSessEntry",
    "7",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "asynchModeWOEchoFun",
            1
          ],
          [
            "demandModeWOEchoFunction",
            2
          ],
          [
            "asyncModeWEchoFun",
            3
          ],
          [
            "demandModeWEchoFunction",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "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."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "asynchModeWOEchoFun"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.43)

Jeremy Siegel

Siblings (14)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.43.45.1.10.2.72.1.3.1.1 h3cBfdSessIfIndex00
1.3.6.1.4.1.43.45.1.10.2.72.1.3.1.2 h3cBfdSessIndex00
1.3.6.1.4.1.43.45.1.10.2.72.1.3.1.3 h3cBfdSessAppSupportId00
1.3.6.1.4.1.43.45.1.10.2.72.1.3.1.4 h3cBfdSessLocalDiscr00
1.3.6.1.4.1.43.45.1.10.2.72.1.3.1.5 h3cBfdSessRemoteDiscr00
1.3.6.1.4.1.43.45.1.10.2.72.1.3.1.6 h3cBfdSessDstPort00
1.3.6.1.4.1.43.45.1.10.2.72.1.3.1.8 h3cBfdSessAddrType00
1.3.6.1.4.1.43.45.1.10.2.72.1.3.1.9 h3cBfdSessLocalAddr00
1.3.6.1.4.1.43.45.1.10.2.72.1.3.1.10 h3cBfdSessRemoteAddr00
1.3.6.1.4.1.43.45.1.10.2.72.1.3.1.11 h3cBfdSessLocalDiag00
1.3.6.1.4.1.43.45.1.10.2.72.1.3.1.12 h3cBfdSessState00
1.3.6.1.4.1.43.45.1.10.2.72.1.3.1.13 h3cBfdSessControlPlanIndepFlag00
1.3.6.1.4.1.43.45.1.10.2.72.1.3.1.14 h3cBfdSessAuthFlag00
1.3.6.1.4.1.43.45.1.10.2.72.1.3.1.15 h3cBfdSessDemandModeFlag00