OID reference

rtmEntityUseUnidirectionalLinks

1.3.6.1.4.1.629.10.7.1.1.1.39

Description

Are unidirectional links usable for the FIB maintained by this instance of DC-RTM? If set to 'false' then unidirectional interfaces reported over the I3 and IGP shortcuts reported over the RPI are discarded. If set to 'true' then unidirectional interfaces can be used for next hops reported over the Active Routes Inter…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.629.10.7.1.1.1 (rtmEntityEntry)
Node code
39
Node name
rtmEntityUseUnidirectionalLinks
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.629.10.7.1.1.1.39
URN notation
urn:oid:1.3.6.1.4.1.629.10.7.1.1.1.39
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

SNMP properties

Value type
TruthValue
Maximum access defined by MIB
read-create
Status in MIB
current
Default value
true

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.

rtmEntityUseUnidirectionalLinks OBJECT-TYPE
       SYNTAX       TruthValue
       MAX-ACCESS   read-create
       STATUS       current
       DESCRIPTION
          "Are unidirectional links usable for the FIB maintained by
           this instance of DC-RTM?

           If set to 'false' then unidirectional interfaces reported
           over the I3 and IGP shortcuts reported over the RPI are
           discarded.

           If set to 'true' then unidirectional interfaces can be
           used for next hops reported over the Active Routes
           Interface.  Note in particular that IGP shortcuts through
           TE-tunnel next hops are reported over the Active Routes
           Interface in addition to native adjacency next hops.

           If the active route consumers of this FIB cannot use
           unidirectional links then this field should be set to
           'false'.  An example of such an active route consumer is
           DC-PIM.  Because DC-PIM uses paths for Reverse Path
           Forwarding, it cannot use unidirectional links.

           If this field is changed while DC-RTM is active, DC-RTM
           deactivates and then reactivates in order to refresh all
           routing information."
       DEFVAL { true }
       ::= { rtmEntityEntry 39 }

Meaning

Descriptions

1 unique

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

Are unidirectional links usable for the FIB maintained by this instance of DC-RTM? If set to 'false' then unidirectional interfaces reported over the I3 and IGP shortcuts reported over the RPI are discarded. If set to 'true' then unidirectional interfaces can be used for next hops reported over the Active Routes Interface. Note in particular that IGP shortcuts through TE-tunnel next hops are reported over the Active Routes Interface in addition to native adjacency next hops. If the active route consumers of this FIB cannot use unidirectional links then this field should be set to 'false'. An example of such an active route consumer is DC-PIM. Because DC-PIM uses paths for Reverse Path Forwarding, it cannot use unidirectional links. If this field is changed while DC-RTM is active, DC-RTM deactivates and then reactivates in order to refresh all routing information.

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

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

Status in source: current.

Names: rtmEntityUseUnidirectionalLinks

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "rtmEntityUseUnidirectionalLinks",
    "OBJECT-TYPE",
    "SYNTAX",
    "TruthValue",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Are unidirectional links usable for the FIB maintained by this instance of DC-RTM? If set to 'false' then unidirectional interfaces reported over the I3 and IGP shortcuts reported over the RPI are discarded. If set to 'true' then unidirectional interfaces can be used for next hops reported over the Active Routes Interface. Note in particular that IGP shortcuts through TE-tunnel next hops are reported over the Active Routes Interface in addition to native adjacency next hops. If the active route consumers of this FIB cannot use unidirectional links then this field should be set to 'false'. An example of such an active route consumer is DC-PIM. Because DC-PIM uses paths for Reverse Path Forwarding, it cannot use unidirectional links. If this field is changed while DC-RTM is active, DC-RTM deactivates and then reactivates in order to refresh all routing information.\"",
    "DEFVAL",
    "{",
    "true",
    "}",
    "::=",
    "{",
    "rtmEntityEntry",
    "39",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "TruthValue"
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Are unidirectional links usable for the FIB maintained by this instance of DC-RTM? If set to 'false' then unidirectional interfaces reported over the I3 and IGP shortcuts reported over the RPI are discarded. If set to 'true' then unidirectional interfaces can be used for next hops reported over the Active Routes Interface. Note in particular that IGP shortcuts through TE-tunnel next hops are reported over the Active Routes Interface in addition to native adjacency next hops. If the active route consumers of this FIB cannot use unidirectional links then this field should be set to 'false'. An example of such an active route consumer is DC-PIM. Because DC-PIM uses paths for Reverse Path Forwarding, it cannot use unidirectional links. If this field is changed while DC-RTM is active, DC-RTM deactivates and then reactivates in order to refresh all routing information."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "true"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.629)

Rotenstein Sergiu

Siblings (45)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.629.10.7.1.1.1.1 rtmEntityFteIndex00
1.3.6.1.4.1.629.10.7.1.1.1.2 rtmEntityRowStatus00
1.3.6.1.4.1.629.10.7.1.1.1.3 rtmEntityAdminStat00
1.3.6.1.4.1.629.10.7.1.1.1.4 rtmEntityOperStatus00
1.3.6.1.4.1.629.10.7.1.1.1.5 rtmEntityDsConnctd00
1.3.6.1.4.1.629.10.7.1.1.1.6 rtmEntityDsStatDf00
1.3.6.1.4.1.629.10.7.1.1.1.7 rtmEntityDsOspfInt00
1.3.6.1.4.1.629.10.7.1.1.1.8 rtmEntityDsOspfExt00
1.3.6.1.4.1.629.10.7.1.1.1.9 rtmEntityDsIntBgp00
1.3.6.1.4.1.629.10.7.1.1.1.10 rtmEntityDsExtBgp00
1.3.6.1.4.1.629.10.7.1.1.1.11 rtmEntityDsIsisInt100
1.3.6.1.4.1.629.10.7.1.1.1.12 rtmEntityDsIsisInt200
1.3.6.1.4.1.629.10.7.1.1.1.13 rtmEntityDsIsisExt100
1.3.6.1.4.1.629.10.7.1.1.1.14 rtmEntityDsIsisExt200
1.3.6.1.4.1.629.10.7.1.1.1.15 rtmEntityDsRip00
1.3.6.1.4.1.629.10.7.1.1.1.16 rtmEntityDsEgp00
1.3.6.1.4.1.629.10.7.1.1.1.17 rtmEntityDsGgp00
1.3.6.1.4.1.629.10.7.1.1.1.18 rtmEntityDsHello00
1.3.6.1.4.1.629.10.7.1.1.1.19 rtmEntityDsEsis00
1.3.6.1.4.1.629.10.7.1.1.1.20 rtmEntityDsBbnspfigp00
1.3.6.1.4.1.629.10.7.1.1.1.21 rtmEntityDsIdpr00
1.3.6.1.4.1.629.10.7.1.1.1.22 rtmEntityDsIgrp00
1.3.6.1.4.1.629.10.7.1.1.1.23 rtmEntityDsEigrpSmm00
1.3.6.1.4.1.629.10.7.1.1.1.24 rtmEntityDsIntEigrp00
1.3.6.1.4.1.629.10.7.1.1.1.25 rtmEntityDsEigrpExt00
1.3.6.1.4.1.629.10.7.1.1.1.26 rtmEntityDsUnknown00
1.3.6.1.4.1.629.10.7.1.1.1.27 rtmEntityEqlCostOpt00
1.3.6.1.4.1.629.10.7.1.1.1.28 rtmEntityDelDeadRte00
1.3.6.1.4.1.629.10.7.1.1.1.29 rtmEntityDeadRpmTmr00
1.3.6.1.4.1.629.10.7.1.1.1.30 rtmEntityRouteNumber00
1.3.6.1.4.1.629.10.7.1.1.1.31 rtmEntityAddressFamily00
1.3.6.1.4.1.629.10.7.1.1.1.32 rtmEntityDsDvmrp00
1.3.6.1.4.1.629.10.7.1.1.1.33 rtmEntityI3Index00
1.3.6.1.4.1.629.10.7.1.1.1.34 rtmEntityI3JoinStatus00
1.3.6.1.4.1.629.10.7.1.1.1.35 rtmEntityPartnerWaitTime00
1.3.6.1.4.1.629.10.7.1.1.1.36 rtmEntityStartupTime00
1.3.6.1.4.1.629.10.7.1.1.1.37 rtmEntityRestartTime00
1.3.6.1.4.1.629.10.7.1.1.1.38 rtmEntityFtStateRetained00
1.3.6.1.4.1.629.10.7.1.1.1.40 rtmEntityBfdIndex00
1.3.6.1.4.1.629.10.7.1.1.1.41 rtmEntityBfdJoinStatus00
1.3.6.1.4.1.629.10.7.1.1.1.42 rtmEntityEnableTrapSupport00
1.3.6.1.4.1.629.10.7.1.1.1.43 rtmEntityDisplayLocalAddrs00
1.3.6.1.4.1.629.10.7.1.1.1.44 rtmEntityRestarting00
1.3.6.1.4.1.629.10.7.1.1.1.45 rtmEntityRestartTimeLeft00
1.3.6.1.4.1.629.10.7.1.1.1.46 rtmEntityRestartExitReason00