Status in source: mandatory.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"saRingCplNetCoupling",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"ringCoupling",
"(",
"1",
")",
",",
"netCoupling",
"(",
"2",
")",
"}",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"Specifies the kind of the coupled net segment. If two rings are coupled ringCoupling(1) must be used. In netCoupling(2) the coupled segment is no ring topology and the switches in the coupled net segment may be connected with other ports than their ringports. Notice: if the ring coupling mechanism switches over, in ringCoupling(1) only the address tables of the switches in the two coupled rings will be erased, in netCoupling(2) the address tables of all switches in the coupled net will be erased.\"",
"::=",
"{",
"saRingCouplingEntry",
"18",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"ringCoupling",
1
],
[
"netCoupling",
2
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Specifies the kind of the coupled net segment. If two rings are coupled ringCoupling(1) must be used. In netCoupling(2) the coupled segment is no ring topology and the switches in the coupled net segment may be connected with other ports than their ringports. Notice: if the ring coupling mechanism switches over, in ringCoupling(1) only the address tables of the switches in the two coupled rings will be erased, in netCoupling(2) the address tables of all switches in the coupled net will be erased."
],
null,
null,
null,
null
]
}