Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"ospfPmEntDoRestartIgnoreLostIf",
"OBJECT-TYPE",
"SYNTAX",
"TruthValue",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"Indicates whether DC-OSPF should perform hitless restart ignoring local interfaces listed in its pre-restart Router LSAs that are no longer present or no longer active. This option is useful when the non-stop forwarding of data over those interfaces that still exist is more important than avoiding routing loops and black-holing of data for routes that use the interfaces that no longer exist. Note that using this option means that the hitless restart procedures do not strictly follow those defined in RFC 3623, Graceful OSPF Restart. Note also that ospfPmEntDoRestartIgnoreLostIf qualifies the graceful restart procedures followed by DC-OSPF. Whether or not to use Graceful Restart procedures is configured by setting DoGraceHitless or DoGraceUnplannedHitless.\"",
"DEFVAL",
"{",
"false",
"}",
"::=",
"{",
"ospfPmEntEntry",
"88",
"}"
],
"syntax_tree": [
[
"row",
"TruthValue"
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Indicates whether DC-OSPF should perform hitless restart ignoring local interfaces listed in its pre-restart Router LSAs that are no longer present or no longer active. This option is useful when the non-stop forwarding of data over those interfaces that still exist is more important than avoiding routing loops and black-holing of data for routes that use the interfaces that no longer exist. Note that using this option means that the hitless restart procedures do not strictly follow those defined in RFC 3623, Graceful OSPF Restart. Note also that ospfPmEntDoRestartIgnoreLostIf qualifies the graceful restart procedures followed by DC-OSPF. Whether or not to use Graceful Restart procedures is configured by setting DoGraceHitless or DoGraceUnplannedHitless."
],
null,
null,
null,
[
"DEFVAL",
"false"
]
]
}