OID reference

ipDhcpClientRtTemplTable

1.3.6.1.4.1.272.4.5.52.9

Description

This table defines some 'gateway-route-templates' that extend the actions taken by the DHCP-client when receiving a 'Router' Option (see section 3.5 of RFC-2132). By default, it builds a default-route for the specified gateway. (See field <MakeDefRoute> of table <ipDhcpClient> for more details.) Additionally (and even…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.272.4.5.52 (dynipMIB)
Node code
9
Node name
ipDhcpClientRtTemplTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.272.4.5.52.9
URN notation
urn:oid:1.3.6.1.4.1.272.4.5.52.9
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 272 4 5 52 9}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) biboip(5) dynipMIB(52) ipDhcpClientRtTemplTable(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) biboipold(5) dynipMIB(52) ipDhcpClientRtTemplTable(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) biboip(5) dynipMIB(52) ipDhcpClientRtTemplTable(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) biboipold(5) dynipMIB(52) ipDhcpClientRtTemplTable(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) biboip(5) dynipMIB(52) ipDhcpClientRtTemplTable(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) biboipold(5) dynipMIB(52) ipDhcpClientRtTemplTable(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) biboip(5) dynipMIB(52) ipDhcpClientRtTemplTable(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) biboipold(5) dynipMIB(52) ipDhcpClientRtTemplTable(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) biboip(5) dynipMIB(52) ipDhcpClientRtTemplTable(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) biboipold(5) dynipMIB(52) ipDhcpClientRtTemplTable(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) biboip(5) dynipMIB(52) ipDhcpClientRtTemplTable(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) biboipold(5) dynipMIB(52) ipDhcpClientRtTemplTable(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) biboip(5) dynipMIB(52) ipDhcpClientRtTemplTable(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) biboipold(5) dynipMIB(52) ipDhcpClientRtTemplTable(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) biboip(5) dynipMIB(52) ipDhcpClientRtTemplTable(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) biboipold(5) dynipMIB(52) ipDhcpClientRtTemplTable(9)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/272/4/5/52/9
  • /ISO/Identified-Organization/6/1/4/1/272/4/5/52/9
  • /ISO/3/6/1/4/1/272/4/5/52/9
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/bintec/bibo/biboip/dynipMIB/ipDhcpClientRtTemplTable
  • /iso/identified-organization/dod/internet/private/enterprise/bintec/bibo/biboipold/dynipMIB/ipDhcpClientRtTemplTable
  • /iso/identified-organization/dod/internet/private/enterprises/bintec/bibo/biboip/dynipMIB/ipDhcpClientRtTemplTable
  • /iso/identified-organization/dod/internet/private/enterprises/bintec/bibo/biboipold/dynipMIB/ipDhcpClientRtTemplTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/bintec/bibo/biboip/dynipMIB/ipDhcpClientRtTemplTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/bintec/bibo/biboipold/dynipMIB/ipDhcpClientRtTemplTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/bintec/bibo/biboip/dynipMIB/ipDhcpClientRtTemplTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/bintec/bibo/biboipold/dynipMIB/ipDhcpClientRtTemplTable
  • /iso/org/dod/internet/private/enterprise/bintec/bibo/biboip/dynipMIB/ipDhcpClientRtTemplTable
  • /iso/org/dod/internet/private/enterprise/bintec/bibo/biboipold/dynipMIB/ipDhcpClientRtTemplTable
  • /iso/org/dod/internet/private/enterprises/bintec/bibo/biboip/dynipMIB/ipDhcpClientRtTemplTable
  • /iso/org/dod/internet/private/enterprises/bintec/bibo/biboipold/dynipMIB/ipDhcpClientRtTemplTable
  • /iso/org/dod/internet/private/ldap-enterprise/bintec/bibo/biboip/dynipMIB/ipDhcpClientRtTemplTable
  • /iso/org/dod/internet/private/ldap-enterprise/bintec/bibo/biboipold/dynipMIB/ipDhcpClientRtTemplTable
  • /iso/org/dod/internet/private/vendor-objects/bintec/bibo/biboip/dynipMIB/ipDhcpClientRtTemplTable
  • /iso/org/dod/internet/private/vendor-objects/bintec/bibo/biboipold/dynipMIB/ipDhcpClientRtTemplTable
  • Additional combinations skipped.

SNMP properties

Value type
SEQUENCE OF IpDhcpClientRtTemplEntry
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.

ipDhcpClientRtTemplTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF IpDhcpClientRtTemplEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "This table defines some 'gateway-route-templates' that extend the
         actions taken by the DHCP-client when receiving a 'Router' Option
         (see section 3.5 of RFC-2132).
         By default, it builds a default-route for the specified gateway. (See
         field <MakeDefRoute> of table <ipDhcpClient> for more details.)
         Additionally (and even if this default-route is suppressed by setting
         <MakeDefRoute> to <false>), DHCP-client adds a routing-entry for each
         template-entry with matching DstIfIndex.
         The <RtType> value tells whether an ipExtRt-entry or ipRoute-entry
         shall be built. In both cases, most fields are copied from template
         to routing-entry.
         In addition, the <Type> is always set to <indirect>, the <Proto> is
         set to <other>, the <Age> is initialised, and the <NextHop> is set to
         the gateway-address received via Router Option.
         Remark: For ipRoute-entries, some fields have slightly different names
           than the related template-fields, and some template-fields are
           meaningful only for ipExtRt-entries. Additionally, the <Info> field
           is set to a reserved OID-value (default-behaviour of DHCP-client to
           mark its entries).
         Remark: The template-table is tightly coupled to the generated routing
           entries. This means that any changes in the template-table cause the
           related routing-entries to be updated, added, or removed."
    ::= { dynipMIB 9 }

Meaning

Descriptions

1 unique

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

This table defines some 'gateway-route-templates' that extend the actions taken by the DHCP-client when receiving a 'Router' Option (see section 3.5 of RFC-2132). By default, it builds a default-route for the specified gateway. (See field <MakeDefRoute> of table <ipDhcpClient> for more details.) Additionally (and even if this default-route is suppressed by setting <MakeDefRoute> to <false>), DHCP-client adds a routing-entry for each template-entry with matching DstIfIndex. The <RtType> value tells whether an ipExtRt-entry or ipRoute-entry shall be built. In both cases, most fields are copied from template to routing-entry. In addition, the <Type> is always set to <indirect>, the <Proto> is set to <other>, the <Age> is initialised, and the <NextHop> is set to the gateway-address received via Router Option. Remark: For ipRoute-entries, some fields have slightly different names than the related template-fields, and some template-fields are meaningful only for ipExtRt-entries. Additionally, the <Info> field is set to a reserved OID-value (default-behaviour of DHCP-client to mark its entries). Remark: The template-table is tightly coupled to the generated routing entries. This means that any changes in the template-table cause the related routing-entries to be updated, added, or removed.

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

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

Status in source: current.

Names: ipDhcpClientRtTemplTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "ipDhcpClientRtTemplTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "IpDhcpClientRtTemplEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This table defines some 'gateway-route-templates' that extend the actions taken by the DHCP-client when receiving a 'Router' Option (see section 3.5 of RFC-2132). By default, it builds a default-route for the specified gateway. (See field <MakeDefRoute> of table <ipDhcpClient> for more details.) Additionally (and even if this default-route is suppressed by setting <MakeDefRoute> to <false>), DHCP-client adds a routing-entry for each template-entry with matching DstIfIndex. The <RtType> value tells whether an ipExtRt-entry or ipRoute-entry shall be built. In both cases, most fields are copied from template to routing-entry. In addition, the <Type> is always set to <indirect>, the <Proto> is set to <other>, the <Age> is initialised, and the <NextHop> is set to the gateway-address received via Router Option. Remark: For ipRoute-entries, some fields have slightly different names than the related template-fields, and some template-fields are meaningful only for ipExtRt-entries. Additionally, the <Info> field is set to a reserved OID-value (default-behaviour of DHCP-client to mark its entries). Remark: The template-table is tightly coupled to the generated routing entries. This means that any changes in the template-table cause the related routing-entries to be updated, added, or removed.\"",
    "::=",
    "{",
    "dynipMIB",
    "9",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "IpDhcpClientRtTemplEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This table defines some 'gateway-route-templates' that extend the actions taken by the DHCP-client when receiving a 'Router' Option (see section 3.5 of RFC-2132). By default, it builds a default-route for the specified gateway. (See field <MakeDefRoute> of table <ipDhcpClient> for more details.) Additionally (and even if this default-route is suppressed by setting <MakeDefRoute> to <false>), DHCP-client adds a routing-entry for each template-entry with matching DstIfIndex. The <RtType> value tells whether an ipExtRt-entry or ipRoute-entry shall be built. In both cases, most fields are copied from template to routing-entry. In addition, the <Type> is always set to <indirect>, the <Proto> is set to <other>, the <Age> is initialised, and the <NextHop> is set to the gateway-address received via Router Option. Remark: For ipRoute-entries, some fields have slightly different names than the related template-fields, and some template-fields are meaningful only for ipExtRt-entries. Additionally, the <Info> field is set to a reserved OID-value (default-behaviour of DHCP-client to mark its entries). Remark: The template-table is tightly coupled to the generated routing entries. This means that any changes in the template-table cause the related routing-entries to be updated, added, or removed."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.272)

Hertlein Elisabeth

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.272.4.5.52.9.1 ipDhcpClientRtTemplEntry1717

Siblings (7)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.272.4.5.52.2 ipDhcpClientTable112
1.3.6.1.4.1.272.4.5.52.3 ipDhcpPoolTable117
1.3.6.1.4.1.272.4.5.52.4 ipDynAddrPoolTable18
1.3.6.1.4.1.272.4.5.52.5 ipDynAddrTable118
1.3.6.1.4.1.272.4.5.52.6 ipDhcpOptionTable110
1.3.6.1.4.1.272.4.5.52.7 ipStatAddrTable118
1.3.6.1.4.1.272.4.5.52.8 ipDynaAddrTable123