OID reference
1.3.6.1.4.1.629.10.3.1.1.1.38
If DC-OSPF is attempting to undergo a planned hitless restart, this field specifies the reason for the restart. This reason is passed to adjacent neighbors in grace LSAs. Note that if the router is undergoing an unplanned hitless restart, this field is ignored and the reason for restart will always be reasonUnknown(0).
Identification
{1 3 6 1 4 1 629 10 3 1 1 1 38}
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.
ospfPmEntHitlessRestartReason OBJECT-TYPE
SYNTAX OspfHitlessRestartReasons
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"If DC-OSPF is attempting to undergo a planned hitless restart, this
field specifies the reason for the restart. This reason is passed to
adjacent neighbors in grace LSAs. Note that if the router is
undergoing an unplanned hitless restart, this field is ignored and
the reason for restart will always be reasonUnknown(0)."
DEFVAL { reasonUnknown }
::= { ospfPmEntEntry 38 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
If DC-OSPF is attempting to undergo a planned hitless restart, this field specifies the reason for the restart. This reason is passed to adjacent neighbors in grace LSAs. Note that if the router is undergoing an unplanned hitless restart, this field is ignored and the reason for restart will always be reasonUnknown(0).
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: ospfPmEntHitlessRestartReason
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"ospfPmEntHitlessRestartReason",
"OBJECT-TYPE",
"SYNTAX",
"OspfHitlessRestartReasons",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"If DC-OSPF is attempting to undergo a planned hitless restart, this field specifies the reason for the restart. This reason is passed to adjacent neighbors in grace LSAs. Note that if the router is undergoing an unplanned hitless restart, this field is ignored and the reason for restart will always be reasonUnknown(0).\"",
"DEFVAL",
"{",
"reasonUnknown",
"}",
"::=",
"{",
"ospfPmEntEntry",
"38",
"}"
],
"syntax_tree": [
[
"row",
"OspfHitlessRestartReasons"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"If DC-OSPF is attempting to undergo a planned hitless restart, this field specifies the reason for the restart. This reason is passed to adjacent neighbors in grace LSAs. Note that if the router is undergoing an unplanned hitless restart, this field is ignored and the reason for restart will always be reasonUnknown(0)."
],
null,
null,
null,
[
"DEFVAL",
"reasonUnknown"
]
]
}Vendor MIB copy from the Observium Community archive.
Module: DC-OSPF-MIB
See published definition above
{'IF-MIB': ['InterfaceIndex', 'InterfaceIndexOrZero'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'RowStatus', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Counter32', 'Gauge32', 'enterprises', 'Integer32', 'Unsigned32', 'IpAddress'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'DC-MASTER-TC': ['AuthUserDataString', 'NpgOperStatus', 'NumericIndex', 'IgpShortcutMetricType', 'IfOperStatus']}Related source files and packages:
Registration