Status in source: current.
Names: ospfPmVirtIfMtuIgnore
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"ospfPmVirtIfMtuIgnore",
"OBJECT-TYPE",
"SYNTAX",
"TruthValue",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"This object controls whether DC-OSPF checks the MTU size on incoming Database Description packets. By default, if the received MTU size in a DB Description packet is higher than the MTU size configured on the incoming interface, the OSPF adjacency will not be established. If the interface is tunneled over, say, an MPLS network, then the administrator may not know the maximum MTU size and so can tell DC-OSPF to ignore the MTU size on incoming DB description packets.\"",
"DEFVAL",
"{",
"false",
"}",
"::=",
"{",
"ospfPmVirtIfEntry",
"28",
"}"
],
"syntax_tree": [
[
"row",
"TruthValue"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This object controls whether DC-OSPF checks the MTU size on incoming Database Description packets. By default, if the received MTU size in a DB Description packet is higher than the MTU size configured on the incoming interface, the OSPF adjacency will not be established. If the interface is tunneled over, say, an MPLS network, then the administrator may not know the maximum MTU size and so can tell DC-OSPF to ignore the MTU size on incoming DB description packets."
],
null,
null,
null,
[
"DEFVAL",
"false"
]
]
}