Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"aluRS232DeviceGender",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"dte",
"(",
"1",
")",
",",
"dce",
"(",
"2",
")",
"}",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"aluRS232DeviceGender configures the gender offered by the local interface. dte is not valid while the sub-channel is aluRS232SocketEntry. dte is not supported on the SAR-H and SAR-Hc systems. Regarding sdiv3 (tmnxMDAAssignedType 71): Due to hardware limitations, each Serial channel in a port duo must be of the same aluRS232DeviceGender. For example, if the channel on port 1 is configured as dte, then the channel on port 2 must be configured as dte, too. \"",
"DEFVAL",
"{",
"dce",
"}",
"::=",
"{",
"aluRS232Entry",
"5",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"dte",
1
],
[
"dce",
2
]
]
]
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"aluRS232DeviceGender configures the gender offered by the local interface. dte is not valid while the sub-channel is aluRS232SocketEntry. dte is not supported on the SAR-H and SAR-Hc systems. Regarding sdiv3 (tmnxMDAAssignedType 71): Due to hardware limitations, each Serial channel in a port duo must be of the same aluRS232DeviceGender. For example, if the channel on port 1 is configured as dte, then the channel on port 2 must be configured as dte, too."
],
null,
null,
null,
[
"DEFVAL",
"dce"
]
]
}