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
]
}