OID reference

h3cBfdSessState

1.3.6.1.4.1.2011.10.2.72.1.3.1.12

Description

The 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 …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.2011.10.2.72.1.3.1 (h3cBfdSessEntry)
Node code
12
Node name
h3cBfdSessState
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2011.10.2.72.1.3.1.12
URN notation
urn:oid:1.3.6.1.4.1.2011.10.2.72.1.3.1.12
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 2011 10 2 72 1 3 1 12}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessState(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessState(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) huawei(2011) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessState(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) iMAP(2011) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessState(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessState(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessState(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) huawei(2011) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessState(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) iMAP(2011) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessState(12)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessState(12)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessState(12)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) huawei(2011) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessState(12)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) iMAP(2011) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessState(12)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessState(12)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessState(12)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) huawei(2011) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessState(12)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) iMAP(2011) h3c(10) h3cCommon(2) h3cBfdMIB(72) h3cBfdObjects(1) h3cBfdSessTable(3) h3cBfdSessEntry(1) h3cBfdSessState(12)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/2011/10/2/72/1/3/1/12
  • /ISO/Identified-Organization/6/1/4/1/2011/10/2/72/1/3/1/12
  • /ISO/3/6/1/4/1/2011/10/2/72/1/3/1/12
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessState
  • /iso/identified-organization/dod/internet/private/enterprise/iMAP/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessState
  • /iso/identified-organization/dod/internet/private/enterprises/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessState
  • /iso/identified-organization/dod/internet/private/enterprises/iMAP/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessState
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessState
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/iMAP/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessState
  • /iso/identified-organization/dod/internet/private/vendor-objects/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessState
  • /iso/identified-organization/dod/internet/private/vendor-objects/iMAP/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessState
  • /iso/org/dod/internet/private/enterprise/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessState
  • /iso/org/dod/internet/private/enterprise/iMAP/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessState
  • /iso/org/dod/internet/private/enterprises/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessState
  • /iso/org/dod/internet/private/enterprises/iMAP/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessState
  • /iso/org/dod/internet/private/ldap-enterprise/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessState
  • /iso/org/dod/internet/private/ldap-enterprise/iMAP/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessState
  • /iso/org/dod/internet/private/vendor-objects/huawei/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessState
  • /iso/org/dod/internet/private/vendor-objects/iMAP/h3c/h3cCommon/h3cBfdMIB/h3cBfdObjects/h3cBfdSessTable/h3cBfdSessEntry/h3cBfdSessState
  • Additional combinations skipped.

SNMP properties

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

Enumerated values

ValueName
0adminDown
1down
2init
3up

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 variants: h3cBfdSessIfIndex, h3cBfdSessIndex; h3cBfdSessIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.2011.10.2.72.1.3.1.12

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

h3cBfdSessState · current

h3cBfdSessState OBJECT-TYPE
    SYNTAX        INTEGER {
                           adminDown(0),
                           down(1),
                           init(2),
                           up(3)
    }
    MAX-ACCESS    read-only
    STATUS        current
    DESCRIPTION
        "The 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."
    DEFVAL { down }
    ::= { h3cBfdSessEntry 12 }

h3cBfdSessState · current

h3cBfdSessState OBJECT-TYPE
       SYNTAX        INTEGER {
                              adminDown(0),
                              down(1),
                              init(2),
                              up(3)
       }
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
           "The 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.            
           "
       DEFVAL { down }
       ::= { h3cBfdSessEntry 12 }

Meaning

Descriptions

1 unique

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

The 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.

Sources for this description

H3C and HH3C MIB copies (Observium Community)Netdisco MIB archive copies

See 2 matching source records

Evidence

Source records

2 records

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

Records for description 1H3C and HH3C MIB copies (Observium Community), Netdisco MIB archive copies2 records · 2 sources

Description 1

h3cBfdSessState · currentH3C and HH3C MIB copies (Observium Community)1 source

Status in source: current.

Names: h3cBfdSessState

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cBfdSessState",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "adminDown",
    "(",
    "0",
    ")",
    ",",
    "down",
    "(",
    "1",
    ")",
    ",",
    "init",
    "(",
    "2",
    ")",
    ",",
    "up",
    "(",
    "3",
    ")",
    "}",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The 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.\"",
    "DEFVAL",
    "{",
    "down",
    "}",
    "::=",
    "{",
    "h3cBfdSessEntry",
    "12",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "adminDown",
            0
          ],
          [
            "down",
            1
          ],
          [
            "init",
            2
          ],
          [
            "up",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The 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."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "down"
    ]
  ]
}
h3cBfdSessState · currentNetdisco MIB archive copies1 source

Status in source: current.

Names: h3cBfdSessState

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cBfdSessState",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "adminDown",
    "(",
    "0",
    ")",
    ",",
    "down",
    "(",
    "1",
    ")",
    ",",
    "init",
    "(",
    "2",
    ")",
    ",",
    "up",
    "(",
    "3",
    ")",
    "}",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The 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. \"",
    "DEFVAL",
    "{",
    "down",
    "}",
    "::=",
    "{",
    "h3cBfdSessEntry",
    "12",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "adminDown",
            0
          ],
          [
            "down",
            1
          ],
          [
            "init",
            2
          ],
          [
            "up",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The 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."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "down"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2011)

Lwu Zhao

Siblings (14)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2011.10.2.72.1.3.1.1 h3cBfdSessIndex, h3cBfdSessIfIndex00
1.3.6.1.4.1.2011.10.2.72.1.3.1.2 h3cBfdSessIfIndex, h3cBfdSessIndex00
1.3.6.1.4.1.2011.10.2.72.1.3.1.3 h3cBfdSessAppSupportId00
1.3.6.1.4.1.2011.10.2.72.1.3.1.4 h3cBfdSessLocalDiscr00
1.3.6.1.4.1.2011.10.2.72.1.3.1.5 h3cBfdSessRemoteDiscr00
1.3.6.1.4.1.2011.10.2.72.1.3.1.6 h3cBfdSessDstPort00
1.3.6.1.4.1.2011.10.2.72.1.3.1.7 h3cBfdSessOperMode00
1.3.6.1.4.1.2011.10.2.72.1.3.1.8 h3cBfdSessAddrType00
1.3.6.1.4.1.2011.10.2.72.1.3.1.9 h3cBfdSessLocalAddr00
1.3.6.1.4.1.2011.10.2.72.1.3.1.10 h3cBfdSessRemoteAddr00
1.3.6.1.4.1.2011.10.2.72.1.3.1.11 h3cBfdSessLocalDiag00
1.3.6.1.4.1.2011.10.2.72.1.3.1.13 h3cBfdSessControlPlanIndepFlag00
1.3.6.1.4.1.2011.10.2.72.1.3.1.14 h3cBfdSessAuthFlag00
1.3.6.1.4.1.2011.10.2.72.1.3.1.15 h3cBfdSessDemandModeFlag00