Status in source: mandatory.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"lanIpRipVersion",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"ohter",
"(",
"1",
")",
",",
"rip1",
"(",
"2",
")",
",",
"rip2B",
"(",
"3",
")",
",",
"rip2M",
"(",
"4",
")",
"}",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"This object controls the format and the broadcasting method of the RIP packets that the Prestige sends (it recognizes both formats when receiving). RIP-1 is universally supported; but RIP-2 carries more information. RIP-1 is probably adequate for most networks, unless you have a unusual network topology. Both RIP-2B and RIP-2M sends the routing data in RIP-2 format; the difference being that RIP-2B uses subnet broadcasting while RIP-2M uses multicasting.\"",
"::=",
"{",
"lanTcpIp",
"4",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"ohter",
1
],
[
"rip1",
2
],
[
"rip2B",
3
],
[
"rip2M",
4
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"This object controls the format and the broadcasting method of the RIP packets that the Prestige sends (it recognizes both formats when receiving). RIP-1 is universally supported; but RIP-2 carries more information. RIP-1 is probably adequate for most networks, unless you have a unusual network topology. Both RIP-2B and RIP-2M sends the routing data in RIP-2 format; the difference being that RIP-2B uses subnet broadcasting while RIP-2M uses multicasting."
],
null,
null,
null,
null
]
}