OID reference

rtmStaticRtBfdSupport

1.3.6.1.4.1.629.10.7.1.3.1.20

Description

This object indicates whether DC-RTM should use BFD to check IP reachability to the static route's next hop. DC-RTM will only attempt to use BFD if rtmEntityBfdIndex is non-zero and the static route has rtmStaticRtAction set to 'forward' and rtmStaticRtNextHop set to a non-null IP address. This object should be set as…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.629.10.7.1.3.1 (rtmStaticRtEntry)
Node code
20
Node name
rtmStaticRtBfdSupport
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.629.10.7.1.3.1.20
URN notation
urn:oid:1.3.6.1.4.1.629.10.7.1.3.1.20
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 629 10 7 1 3 1 20}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nbase(629) opx(10) rtmMib(7) rtmObjects(1) rtmStaticRtTable(3) rtmStaticRtEntry(1) rtmStaticRtBfdSupport(20)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nbs(629) opx(10) rtmMib(7) rtmObjects(1) rtmStaticRtTable(3) rtmStaticRtEntry(1) rtmStaticRtBfdSupport(20)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nbase(629) opx(10) rtmMib(7) rtmObjects(1) rtmStaticRtTable(3) rtmStaticRtEntry(1) rtmStaticRtBfdSupport(20)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nbs(629) opx(10) rtmMib(7) rtmObjects(1) rtmStaticRtTable(3) rtmStaticRtEntry(1) rtmStaticRtBfdSupport(20)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nbase(629) opx(10) rtmMib(7) rtmObjects(1) rtmStaticRtTable(3) rtmStaticRtEntry(1) rtmStaticRtBfdSupport(20)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nbs(629) opx(10) rtmMib(7) rtmObjects(1) rtmStaticRtTable(3) rtmStaticRtEntry(1) rtmStaticRtBfdSupport(20)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nbase(629) opx(10) rtmMib(7) rtmObjects(1) rtmStaticRtTable(3) rtmStaticRtEntry(1) rtmStaticRtBfdSupport(20)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nbs(629) opx(10) rtmMib(7) rtmObjects(1) rtmStaticRtTable(3) rtmStaticRtEntry(1) rtmStaticRtBfdSupport(20)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nbase(629) opx(10) rtmMib(7) rtmObjects(1) rtmStaticRtTable(3) rtmStaticRtEntry(1) rtmStaticRtBfdSupport(20)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nbs(629) opx(10) rtmMib(7) rtmObjects(1) rtmStaticRtTable(3) rtmStaticRtEntry(1) rtmStaticRtBfdSupport(20)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nbase(629) opx(10) rtmMib(7) rtmObjects(1) rtmStaticRtTable(3) rtmStaticRtEntry(1) rtmStaticRtBfdSupport(20)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nbs(629) opx(10) rtmMib(7) rtmObjects(1) rtmStaticRtTable(3) rtmStaticRtEntry(1) rtmStaticRtBfdSupport(20)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nbase(629) opx(10) rtmMib(7) rtmObjects(1) rtmStaticRtTable(3) rtmStaticRtEntry(1) rtmStaticRtBfdSupport(20)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nbs(629) opx(10) rtmMib(7) rtmObjects(1) rtmStaticRtTable(3) rtmStaticRtEntry(1) rtmStaticRtBfdSupport(20)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nbase(629) opx(10) rtmMib(7) rtmObjects(1) rtmStaticRtTable(3) rtmStaticRtEntry(1) rtmStaticRtBfdSupport(20)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nbs(629) opx(10) rtmMib(7) rtmObjects(1) rtmStaticRtTable(3) rtmStaticRtEntry(1) rtmStaticRtBfdSupport(20)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/629/10/7/1/3/1/20
  • /ISO/Identified-Organization/6/1/4/1/629/10/7/1/3/1/20
  • /ISO/3/6/1/4/1/629/10/7/1/3/1/20
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/nbase/opx/rtmMib/rtmObjects/rtmStaticRtTable/rtmStaticRtEntry/rtmStaticRtBfdSupport
  • /iso/identified-organization/dod/internet/private/enterprise/nbs/opx/rtmMib/rtmObjects/rtmStaticRtTable/rtmStaticRtEntry/rtmStaticRtBfdSupport
  • /iso/identified-organization/dod/internet/private/enterprises/nbase/opx/rtmMib/rtmObjects/rtmStaticRtTable/rtmStaticRtEntry/rtmStaticRtBfdSupport
  • /iso/identified-organization/dod/internet/private/enterprises/nbs/opx/rtmMib/rtmObjects/rtmStaticRtTable/rtmStaticRtEntry/rtmStaticRtBfdSupport
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nbase/opx/rtmMib/rtmObjects/rtmStaticRtTable/rtmStaticRtEntry/rtmStaticRtBfdSupport
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nbs/opx/rtmMib/rtmObjects/rtmStaticRtTable/rtmStaticRtEntry/rtmStaticRtBfdSupport
  • /iso/identified-organization/dod/internet/private/vendor-objects/nbase/opx/rtmMib/rtmObjects/rtmStaticRtTable/rtmStaticRtEntry/rtmStaticRtBfdSupport
  • /iso/identified-organization/dod/internet/private/vendor-objects/nbs/opx/rtmMib/rtmObjects/rtmStaticRtTable/rtmStaticRtEntry/rtmStaticRtBfdSupport
  • /iso/org/dod/internet/private/enterprise/nbase/opx/rtmMib/rtmObjects/rtmStaticRtTable/rtmStaticRtEntry/rtmStaticRtBfdSupport
  • /iso/org/dod/internet/private/enterprise/nbs/opx/rtmMib/rtmObjects/rtmStaticRtTable/rtmStaticRtEntry/rtmStaticRtBfdSupport
  • /iso/org/dod/internet/private/enterprises/nbase/opx/rtmMib/rtmObjects/rtmStaticRtTable/rtmStaticRtEntry/rtmStaticRtBfdSupport
  • /iso/org/dod/internet/private/enterprises/nbs/opx/rtmMib/rtmObjects/rtmStaticRtTable/rtmStaticRtEntry/rtmStaticRtBfdSupport
  • /iso/org/dod/internet/private/ldap-enterprise/nbase/opx/rtmMib/rtmObjects/rtmStaticRtTable/rtmStaticRtEntry/rtmStaticRtBfdSupport
  • /iso/org/dod/internet/private/ldap-enterprise/nbs/opx/rtmMib/rtmObjects/rtmStaticRtTable/rtmStaticRtEntry/rtmStaticRtBfdSupport
  • /iso/org/dod/internet/private/vendor-objects/nbase/opx/rtmMib/rtmObjects/rtmStaticRtTable/rtmStaticRtEntry/rtmStaticRtBfdSupport
  • /iso/org/dod/internet/private/vendor-objects/nbs/opx/rtmMib/rtmObjects/rtmStaticRtTable/rtmStaticRtEntry/rtmStaticRtBfdSupport
  • Additional combinations skipped.

SNMP properties

Value type
RtmBfdSupport
Maximum access defined by MIB
read-create
Status in MIB
current
Default value
desired

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

The displayed source records contain one distinct definition. Compare its source records.

rtmStaticRtBfdSupport OBJECT-TYPE
       SYNTAX       RtmBfdSupport
       MAX-ACCESS   read-create
       STATUS       current
       DESCRIPTION
          "This object indicates whether DC-RTM should use BFD to check IP
           reachability to the static route's next hop.

           DC-RTM will only attempt to use BFD if rtmEntityBfdIndex is non-zero
           and the static route has rtmStaticRtAction set to 'forward'
           and rtmStaticRtNextHop set to a non-null IP address.

           This object should be set as follows.

           -  Set to 'none' if BFD is not required for this static route.

           -  Set to 'desired' if it is not known whether the next hop
              router supports BFD.  DC-RTM will use BFD for reachability
              checking if BFD is able to contact the next hop router.  If the
              BFD session fails, the static route will be removed from the
              forwarding table and will not be used for redistribution.

           -  Set to 'required' if it is known that the next hop router
              supports BFD.  DC-RTM will use BFD to check reachability of the
              next hop.  If BFD is unable to contact the next hop router or if
              the BFD session fails, the static route will be removed from the
              forwarding table and will not be used for redistribution.

           The current state of the BFD session is indicated by
           rtmStaticRtBfdStatus."
       DEFVAL       { desired }
       ::= { rtmStaticRtEntry 20 }

Meaning

Descriptions

1 unique

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

This object indicates whether DC-RTM should use BFD to check IP reachability to the static route's next hop. DC-RTM will only attempt to use BFD if rtmEntityBfdIndex is non-zero and the static route has rtmStaticRtAction set to 'forward' and rtmStaticRtNextHop set to a non-null IP address. This object should be set as follows. - Set to 'none' if BFD is not required for this static route. - Set to 'desired' if it is not known whether the next hop router supports BFD. DC-RTM will use BFD for reachability checking if BFD is able to contact the next hop router. If the BFD session fails, the static route will be removed from the forwarding table and will not be used for redistribution. - Set to 'required' if it is known that the next hop router supports BFD. DC-RTM will use BFD to check reachability of the next hop. If BFD is unable to contact the next hop router or if the BFD session fails, the static route will be removed from the forwarding table and will not be used for redistribution. The current state of the BFD session is indicated by rtmStaticRtBfdStatus.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

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 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

rtmStaticRtBfdSupport · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: rtmStaticRtBfdSupport

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "rtmStaticRtBfdSupport",
    "OBJECT-TYPE",
    "SYNTAX",
    "RtmBfdSupport",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object indicates whether DC-RTM should use BFD to check IP reachability to the static route's next hop. DC-RTM will only attempt to use BFD if rtmEntityBfdIndex is non-zero and the static route has rtmStaticRtAction set to 'forward' and rtmStaticRtNextHop set to a non-null IP address. This object should be set as follows. - Set to 'none' if BFD is not required for this static route. - Set to 'desired' if it is not known whether the next hop router supports BFD. DC-RTM will use BFD for reachability checking if BFD is able to contact the next hop router. If the BFD session fails, the static route will be removed from the forwarding table and will not be used for redistribution. - Set to 'required' if it is known that the next hop router supports BFD. DC-RTM will use BFD to check reachability of the next hop. If BFD is unable to contact the next hop router or if the BFD session fails, the static route will be removed from the forwarding table and will not be used for redistribution. The current state of the BFD session is indicated by rtmStaticRtBfdStatus.\"",
    "DEFVAL",
    "{",
    "desired",
    "}",
    "::=",
    "{",
    "rtmStaticRtEntry",
    "20",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "RtmBfdSupport"
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object indicates whether DC-RTM should use BFD to check IP reachability to the static route's next hop. DC-RTM will only attempt to use BFD if rtmEntityBfdIndex is non-zero and the static route has rtmStaticRtAction set to 'forward' and rtmStaticRtNextHop set to a non-null IP address. This object should be set as follows. - Set to 'none' if BFD is not required for this static route. - Set to 'desired' if it is not known whether the next hop router supports BFD. DC-RTM will use BFD for reachability checking if BFD is able to contact the next hop router. If the BFD session fails, the static route will be removed from the forwarding table and will not be used for redistribution. - Set to 'required' if it is known that the next hop router supports BFD. DC-RTM will use BFD to check reachability of the next hop. If BFD is unable to contact the next hop router or if the BFD session fails, the static route will be removed from the forwarding table and will not be used for redistribution. The current state of the BFD session is indicated by rtmStaticRtBfdStatus."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "desired"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.629)

Rotenstein Sergiu

Siblings (21)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.629.10.7.1.3.1.1 rtmStaticRtFteIndex00
1.3.6.1.4.1.629.10.7.1.3.1.2 rtmStaticRtDestAddrType00
1.3.6.1.4.1.629.10.7.1.3.1.3 rtmStaticRtDestAddr00
1.3.6.1.4.1.629.10.7.1.3.1.4 rtmStaticRtDestLen00
1.3.6.1.4.1.629.10.7.1.3.1.5 rtmStaticRtNextHopType00
1.3.6.1.4.1.629.10.7.1.3.1.6 rtmStaticRtNextHop00
1.3.6.1.4.1.629.10.7.1.3.1.7 rtmStaticRtIfIndex00
1.3.6.1.4.1.629.10.7.1.3.1.8 rtmStaticRtRowStatus00
1.3.6.1.4.1.629.10.7.1.3.1.9 rtmStaticRtAdminStat00
1.3.6.1.4.1.629.10.7.1.3.1.10 rtmStaticRtOverride00
1.3.6.1.4.1.629.10.7.1.3.1.11 rtmStaticRtAdminDist00
1.3.6.1.4.1.629.10.7.1.3.1.12 rtmStaticRtAction00
1.3.6.1.4.1.629.10.7.1.3.1.13 rtmStaticRtFwdAddrType00
1.3.6.1.4.1.629.10.7.1.3.1.14 rtmStaticRtForwardingAddr00
1.3.6.1.4.1.629.10.7.1.3.1.15 rtmStaticRtPathType00
1.3.6.1.4.1.629.10.7.1.3.1.16 rtmStaticRtUsePathCost00
1.3.6.1.4.1.629.10.7.1.3.1.17 rtmStaticRtPathCost00
1.3.6.1.4.1.629.10.7.1.3.1.18 rtmStaticRtUserData00
1.3.6.1.4.1.629.10.7.1.3.1.19 rtmStaticRtLooseNextHop00
1.3.6.1.4.1.629.10.7.1.3.1.21 rtmStaticRtBfdStatus00
1.3.6.1.4.1.629.10.7.1.3.1.22 rtmStaticRtInterfaceName00