Reference record for OID 1.3.6.1.4.1.52642.2.72.1.3.1.12

Parent
1.3.6.1.4.1.52642.2.72.1.3.1 (fsBfdSessEntry)
Node code
12
Node name
fsBfdSessState
Numeric OID
1.3.6.1.4.1.52642.2.72.1.3.1.12
URN notation
urn:oid:1.3.6.1.4.1.52642.2.72.1.3.1.12
ASN.1 notation

{1 3 6 1 4 1 52642 2 72 1 3 1 12}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) fsnetworks(2) fsBfdMIB(72) fsBfdObjects(1) fsBfdSessTable(3) fsBfdSessEntry(1) fsBfdSessState(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) nmslocal(2) fsBfdMIB(72) fsBfdObjects(1) fsBfdSessTable(3) fsBfdSessEntry(1) fsBfdSessState(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) fsProtocol(2) fsBfdMIB(72) fsBfdObjects(1) fsBfdSessTable(3) fsBfdSessEntry(1) fsBfdSessState(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) fsCommon(2) fsBfdMIB(72) fsBfdObjects(1) fsBfdSessTable(3) fsBfdSessEntry(1) fsBfdSessState(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) transmission(2) fsBfdMIB(72) fsBfdObjects(1) fsBfdSessTable(3) fsBfdSessEntry(1) fsBfdSessState(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) fsnetworks(2) fsBfdMIB(72) fsBfdObjects(1) fsBfdSessTable(3) fsBfdSessEntry(1) fsBfdSessState(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) nmslocal(2) fsBfdMIB(72) fsBfdObjects(1) fsBfdSessTable(3) fsBfdSessEntry(1) fsBfdSessState(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) fsProtocol(2) fsBfdMIB(72) fsBfdObjects(1) fsBfdSessTable(3) fsBfdSessEntry(1) fsBfdSessState(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) fsCommon(2) fsBfdMIB(72) fsBfdObjects(1) fsBfdSessTable(3) fsBfdSessEntry(1) fsBfdSessState(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) transmission(2) fsBfdMIB(72) fsBfdObjects(1) fsBfdSessTable(3) fsBfdSessEntry(1) fsBfdSessState(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fiberstore(52642) fsnetworks(2) fsBfdMIB(72) fsBfdObjects(1) fsBfdSessTable(3) fsBfdSessEntry(1) fsBfdSessState(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fiberstore(52642) nmslocal(2) fsBfdMIB(72) fsBfdObjects(1) fsBfdSessTable(3) fsBfdSessEntry(1) fsBfdSessState(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fiberstore(52642) fsProtocol(2) fsBfdMIB(72) fsBfdObjects(1) fsBfdSessTable(3) fsBfdSessEntry(1) fsBfdSessState(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fiberstore(52642) fsCommon(2) fsBfdMIB(72) fsBfdObjects(1) fsBfdSessTable(3) fsBfdSessEntry(1) fsBfdSessState(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fiberstore(52642) transmission(2) fsBfdMIB(72) fsBfdObjects(1) fsBfdSessTable(3) fsBfdSessEntry(1) fsBfdSessState(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) vtss(52642) fsnetworks(2) fsBfdMIB(72) fsBfdObjects(1) fsBfdSessTable(3) fsBfdSessEntry(1) fsBfdSessState(12)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/52642/2/72/1/3/1/12
  • /ISO/Identified-Organization/6/1/4/1/52642/2/72/1/3/1/12
  • /ISO/3/6/1/4/1/52642/2/72/1/3/1/12
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/fs/fsnetworks/fsBfdMIB/fsBfdObjects/fsBfdSessTable/fsBfdSessEntry/fsBfdSessState
  • /iso/identified-organization/dod/internet/private/enterprise/fs/nmslocal/fsBfdMIB/fsBfdObjects/fsBfdSessTable/fsBfdSessEntry/fsBfdSessState
  • /iso/identified-organization/dod/internet/private/enterprise/fs/fsProtocol/fsBfdMIB/fsBfdObjects/fsBfdSessTable/fsBfdSessEntry/fsBfdSessState
  • /iso/identified-organization/dod/internet/private/enterprise/fs/fsCommon/fsBfdMIB/fsBfdObjects/fsBfdSessTable/fsBfdSessEntry/fsBfdSessState
  • /iso/identified-organization/dod/internet/private/enterprise/fs/transmission/fsBfdMIB/fsBfdObjects/fsBfdSessTable/fsBfdSessEntry/fsBfdSessState
  • /iso/identified-organization/dod/internet/private/enterprise/nms/fsnetworks/fsBfdMIB/fsBfdObjects/fsBfdSessTable/fsBfdSessEntry/fsBfdSessState
  • /iso/identified-organization/dod/internet/private/enterprise/nms/nmslocal/fsBfdMIB/fsBfdObjects/fsBfdSessTable/fsBfdSessEntry/fsBfdSessState
  • /iso/identified-organization/dod/internet/private/enterprise/nms/fsProtocol/fsBfdMIB/fsBfdObjects/fsBfdSessTable/fsBfdSessEntry/fsBfdSessState
  • /iso/identified-organization/dod/internet/private/enterprise/nms/fsCommon/fsBfdMIB/fsBfdObjects/fsBfdSessTable/fsBfdSessEntry/fsBfdSessState
  • /iso/identified-organization/dod/internet/private/enterprise/nms/transmission/fsBfdMIB/fsBfdObjects/fsBfdSessTable/fsBfdSessEntry/fsBfdSessState
  • /iso/identified-organization/dod/internet/private/enterprise/fiberstore/fsnetworks/fsBfdMIB/fsBfdObjects/fsBfdSessTable/fsBfdSessEntry/fsBfdSessState
  • /iso/identified-organization/dod/internet/private/enterprise/fiberstore/nmslocal/fsBfdMIB/fsBfdObjects/fsBfdSessTable/fsBfdSessEntry/fsBfdSessState
  • /iso/identified-organization/dod/internet/private/enterprise/fiberstore/fsProtocol/fsBfdMIB/fsBfdObjects/fsBfdSessTable/fsBfdSessEntry/fsBfdSessState
  • /iso/identified-organization/dod/internet/private/enterprise/fiberstore/fsCommon/fsBfdMIB/fsBfdObjects/fsBfdSessTable/fsBfdSessEntry/fsBfdSessState
  • /iso/identified-organization/dod/internet/private/enterprise/fiberstore/transmission/fsBfdMIB/fsBfdObjects/fsBfdSessTable/fsBfdSessEntry/fsBfdSessState
  • /iso/identified-organization/dod/internet/private/enterprise/FS/fsnetworks/fsBfdMIB/fsBfdObjects/fsBfdSessTable/fsBfdSessEntry/fsBfdSessState
  • Additional combinations skipped.

Descriptions

fsBfdSessState — FS.COM official Documentation Hub native MIB packages

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.

Source records

fsBfdSessState

Status in source: current.

Names: fsBfdSessState

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsBfdSessState",
    "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",
    "}",
    "::=",
    "{",
    "fsBfdSessEntry",
    "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"
    ]
  ]
}
  • FS.COM official Documentation Hub native MIB packages · Publisher's source file: Source package: ies3220-8t4f-switch-snmp-mib-files.zip

    Module: FS-BFD-STD-MIB

    Published definition
    fsBfdSessState 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 }
        ::= { fsBfdSessEntry 12 }
    Module imports
    {'IF-MIB': ['InterfaceIndex', 'InterfaceIndexOrZero'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'TimeStamp', 'DisplayString'], 'FS-OID-MIB': ['fsCommon'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32', 'Counter32', 'Counter64', 'NOTIFICATION-TYPE'], 'INET-ADDRESS-MIB': ['InetAddress', 'InetAddressType', 'InetPortNumber']}

    Related source files and packages:

    • IES5120-28TF Switch SNMP MIB FilesIES5120-28TF Switch SNMP MIB Files; Models: IES5120-28TF; Catalog updated: 2026-02-27 15:56:52; File: mall/resource/ies5120-28tf-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:14:36 GMT; 2.6 MiB
    • IES3220-8T4F Switch SNMP MIB FilesIES3220-8T4F Switch SNMP MIB Files; Models: IES3220-8T4F; Catalog updated: 2025-12-03 14:28:43; File: mall/resource/ies3220-8t4f-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:08:16 GMT; 2.6 MiB
    • IES5120-48T4S Switch SNMP MIB FilesIES5120-48T4S Switch SNMP MIB Files; Models: IES5120-48T4S; Catalog updated: 2026-02-27 16:10:26; File: mall/resource/ies5120-48t4s-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:16:11 GMT; 2.6 MiB
    Show all 10 related files and packages
    • TSN3220-10S Switch SNMP MIB FilesTSN3220-10S Switch SNMP MIB Files; Models: TSN3220-10S; Catalog updated: 2026-01-08 09:53:00; File: mall/resource/tsn3220-10s-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:10:41 GMT; 2.6 MiB
    • IES5120-28TS-P Switch SNMP MIB FilesIES5120-28TS-P Switch SNMP MIB Files; Models: IES5120-28TS-P; Catalog updated: 2026-02-27 16:09:52; File: mall/resource/ies5120-28ts-p-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:15:40 GMT; 2.6 MiB
    • IES5220-30TS-3ES Switch SNMP MIB FilesIES5220-30TS-3ES Switch SNMP MIB Files; Models: IES5220-30TS-3ES; Catalog updated: 2025-08-19 16:17:18; File: mall/resource/ies5220-30ts-3es-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:17:18 GMT; 2.6 MiB
    • IES5220-6S-3ES Switch SNMP MIB FilesIES5220-6S-3ES Switch SNMP MIB Files; Models: IES5220-6S-3ES; Catalog updated: 2026-02-27 16:11:15; File: mall/resource/ies5220-6s-3es-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:32:47 GMT; 2.6 MiB
    • IES3220-8T4F-U Switch SNMP MIB FilesIES3220-8T4F-U Switch SNMP MIB Files; Models: IES3220-8T4F-U; Catalog updated: 2025-12-03 14:47:49; File: mall/resource/ies3220-8t4f-u-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:09:07 GMT; 2.6 MiB
    • IES5120-28TS Switch SNMP MIB FilesIES5120-28TS Switch SNMP MIB Files; Models: IES5120-28TS; Catalog updated: 2026-02-27 15:57:39; File: mall/resource/ies5120-28ts-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:15:08 GMT; 2.6 MiB
    • TSN3220-10S-U Switch SNMP MIB FilesTSN3220-10S-U Switch SNMP MIB Files; Models: TSN3220-10S-U; Catalog updated: 2025-12-16 18:11:48; File: mall/resource/tsn3220-10s-u-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:13:57 GMT; 2.6 MiB

    Source location: FS-BFD-STD-MIB::fsBfdSessState.
    Source version and references

    Same file in tsn3220-10s-u-switch-snmp-mib-files.zip.

    Same file in tsn3220-10s-switch-snmp-mib-files.zip.

    Same file in ies5220-6s-3es-switch-snmp-mib-files.zip.

    Same file in ies5220-30ts-3es-switch-snmp-mib-files.zip.

    Downloaded: 2026-10-24T13:35:15.234927+00:00.

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.52642)

FS.COM INC

Siblings (14)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.52642.2.72.1.3.1.1 fsBfdSessIndex00
1.3.6.1.4.1.52642.2.72.1.3.1.2 fsBfdSessIfIndex00
1.3.6.1.4.1.52642.2.72.1.3.1.3 fsBfdSessAppSupportId00
1.3.6.1.4.1.52642.2.72.1.3.1.4 fsBfdSessLocalDiscr00
1.3.6.1.4.1.52642.2.72.1.3.1.5 fsBfdSessRemoteDiscr00
1.3.6.1.4.1.52642.2.72.1.3.1.6 fsBfdSessDstPort00
1.3.6.1.4.1.52642.2.72.1.3.1.7 fsBfdSessOperMode00
1.3.6.1.4.1.52642.2.72.1.3.1.8 fsBfdSessAddrType00
1.3.6.1.4.1.52642.2.72.1.3.1.9 fsBfdSessLocalAddr00
1.3.6.1.4.1.52642.2.72.1.3.1.10 fsBfdSessRemoteAddr00
1.3.6.1.4.1.52642.2.72.1.3.1.11 fsBfdSessLocalDiag00
1.3.6.1.4.1.52642.2.72.1.3.1.13 fsBfdSessControlPlanIndepFlag00
1.3.6.1.4.1.52642.2.72.1.3.1.14 fsBfdSessAuthFlag00
1.3.6.1.4.1.52642.2.72.1.3.1.15 fsBfdSessDemandModeFlag00