Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"zxGponDownFrameInfoOnuSendDBRuMode",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"notsend",
"(",
"1",
")",
",",
"mode0",
"(",
"2",
")",
",",
"mode1",
"(",
"3",
")",
",",
"mode2",
"(",
"4",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"Depending on the contents of these value, the ONU will send the DBRu corresponding to the allocation ID or not. The code points defined are: 1: Do not send DBRu at all. 2: Send the 'mode 0' DBRu (two bytes). 3: Send the 'mode 1' DBRu (three bytes). 4: Send the 'mode 2' DBRu (five bytes). The description of the syntax of the different DBRu's is given in section 8.4. Note that the ONU must respond with the required number of bytes, regardless of what mode it actually supports.\"",
"::=",
"{",
"zxGponDownFrameInfoEntry",
"6",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"notsend",
1
],
[
"mode0",
2
],
[
"mode1",
3
],
[
"mode2",
4
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Depending on the contents of these value, the ONU will send the DBRu corresponding to the allocation ID or not. The code points defined are: 1: Do not send DBRu at all. 2: Send the 'mode 0' DBRu (two bytes). 3: Send the 'mode 1' DBRu (three bytes). 4: Send the 'mode 2' DBRu (five bytes). The description of the syntax of the different DBRu's is given in section 8.4. Note that the ONU must respond with the required number of bytes, regardless of what mode it actually supports."
],
null,
null,
null,
null
]
}