Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"ospfRedistributeMetricType",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"e1",
"(",
"1",
")",
",",
"e2",
"(",
"2",
")",
"}",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"The type of metric, with which the external routes are advertised into the OSPF routing domain. OSPF supports two types of external metrics. Type 1 external metrics are expressed in the same units as the OSPF interface cost (i.e., in terms of the link state metric). Type 2 external metrics are an order of magnitude larger; any Type 2 metric is considered greater than the cost of any path internal to the AS. Use of Type 2 external metrics assumes that routing between AS'es is the major cost of routing a packet, and eliminates the need for conversion of external costs to internal link state metrics.\"",
"::=",
"{",
"ospfRedistributeEntry",
"3",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"e1",
1
],
[
"e2",
2
]
]
]
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The type of metric, with which the external routes are advertised into the OSPF routing domain. OSPF supports two types of external metrics. Type 1 external metrics are expressed in the same units as the OSPF interface cost (i.e., in terms of the link state metric). Type 2 external metrics are an order of magnitude larger; any Type 2 metric is considered greater than the cost of any path internal to the AS. Use of Type 2 external metrics assumes that routing between AS'es is the major cost of routing a packet, and eliminates the need for conversion of external costs to internal link state metrics."
],
null,
null,
null,
null
]
}