OID reference

rtmRedistTable

1.3.6.1.4.1.629.10.7.1.2

Description

The table of DC-RTM redistribution information entries. This table is used to determine how routing information is redistributed to routing protocol managers (RPMs) using DC-RTM's Routing Protocol Input interface. The RPM to which the information may be redistributed is called the destination RPM. Routing information …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.629.10.7.1 (rtmObjects)
Node code
2
Node name
rtmRedistTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.629.10.7.1.2
URN notation
urn:oid:1.3.6.1.4.1.629.10.7.1.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

SNMP properties

Value type
SEQUENCE OF RtmRedistEntry
Maximum access defined by MIB
not-accessible
Status in MIB
current

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.

rtmRedistTable OBJECT-TYPE
  -- FAMILY-SHORT-NAME qcr_rds
       SYNTAX      SEQUENCE OF RtmRedistEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
          "The table of DC-RTM redistribution information entries.
          This table is used to determine how routing information is
          redistributed to routing protocol managers (RPMs) using DC-RTM's
          Routing Protocol Input interface.  The RPM to which the information
          may be redistributed is called the destination RPM.  Routing
          information is received from RPMs and from the MIB (for static
          routes); these are referred to as the routing information source.

          In general, DC-RTM will not redistribute a route from an RPM
          back to the same RPM.  The one exception to this is if it is
          explicitly configured to do so - in other words, if it is
          configured with a redistribution rule where the source and
          destination filters both indicate the same RPM instance.

          One example use for this is to inform an instance of BGP
          which of its routes are active - see the definition of
          bgpRmAfiSafiAdvertiseInactive in the BGP MIB for more
          details."
       ::= { rtmObjects 2 }

Meaning

Descriptions

1 unique

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

The table of DC-RTM redistribution information entries. This table is used to determine how routing information is redistributed to routing protocol managers (RPMs) using DC-RTM's Routing Protocol Input interface. The RPM to which the information may be redistributed is called the destination RPM. Routing information is received from RPMs and from the MIB (for static routes); these are referred to as the routing information source. In general, DC-RTM will not redistribute a route from an RPM back to the same RPM. The one exception to this is if it is explicitly configured to do so - in other words, if it is configured with a redistribution rule where the source and destination filters both indicate the same RPM instance. One example use for this is to inform an instance of BGP which of its routes are active - see the definition of bgpRmAfiSafiAdvertiseInactive in the BGP MIB for more details.

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

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

Status in source: current.

Names: rtmRedistTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "rtmRedistTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "RtmRedistEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The table of DC-RTM redistribution information entries. This table is used to determine how routing information is redistributed to routing protocol managers (RPMs) using DC-RTM's Routing Protocol Input interface. The RPM to which the information may be redistributed is called the destination RPM. Routing information is received from RPMs and from the MIB (for static routes); these are referred to as the routing information source. In general, DC-RTM will not redistribute a route from an RPM back to the same RPM. The one exception to this is if it is explicitly configured to do so - in other words, if it is configured with a redistribution rule where the source and destination filters both indicate the same RPM instance. One example use for this is to inform an instance of BGP which of its routes are active - see the definition of bgpRmAfiSafiAdvertiseInactive in the BGP MIB for more details.\"",
    "::=",
    "{",
    "rtmObjects",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "RtmRedistEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The table of DC-RTM redistribution information entries. This table is used to determine how routing information is redistributed to routing protocol managers (RPMs) using DC-RTM's Routing Protocol Input interface. The RPM to which the information may be redistributed is called the destination RPM. Routing information is received from RPMs and from the MIB (for static routes); these are referred to as the routing information source. In general, DC-RTM will not redistribute a route from an RPM back to the same RPM. The one exception to this is if it is explicitly configured to do so - in other words, if it is configured with a redistribution rule where the source and destination filters both indicate the same RPM instance. One example use for this is to inform an instance of BGP which of its routes are active - see the definition of bgpRmAfiSafiAdvertiseInactive in the BGP MIB for more details."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.629)

Rotenstein Sergiu

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.629.10.7.1.2.1 rtmRedistEntry4848

Siblings (8)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.629.10.7.1.1 rtmEntityTable147
1.3.6.1.4.1.629.10.7.1.3 rtmStaticRtTable123
1.3.6.1.4.1.629.10.7.1.4 rtmMjTable110
1.3.6.1.4.1.629.10.7.1.5 rtmSjTable17
1.3.6.1.4.1.629.10.7.1.6 rtmRouteTable125
1.3.6.1.4.1.629.10.7.1.7 rtmRibTable127
1.3.6.1.4.1.629.10.7.1.8 rtmRdstSetFieldTable17
1.3.6.1.4.1.629.10.7.1.9 rtmRouterDefinitionTable14