Status in source: mandatory.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"recValue",
"OBJECT-TYPE",
"SYNTAX",
"Opaque",
"ACCESS",
"read-only",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition>The value of this object is set to the BER encoding of the value referenced by the recConfigRecordOID of the associated recordingConfigID when the entry was collected. Its length is variable. The value shall not contain any padding characters either before or after the values. NOTE – Opaque objects are doubly wrapped. For SNMP operations, which use BER, this would be {type, length, {type, length, value}}. For example, a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For STMP or SFMP operations, which use OER, this would be { length, {type, length, value}}. For example, the same example would be encoded in OER as 0x02 04 00. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.11.1.3 \"",
"::=",
"{",
"recEntry",
"3",
"}"
],
"syntax_tree": [
[
"ApplicationSyntax",
"Opaque"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition>The value of this object is set to the BER encoding of the value referenced by the recConfigRecordOID of the associated recordingConfigID when the entry was collected. Its length is variable. The value shall not contain any padding characters either before or after the values. NOTE – Opaque objects are doubly wrapped. For SNMP operations, which use BER, this would be {type, length, {type, length, value}}. For example, a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For STMP or SFMP operations, which use OER, this would be { length, {type, length, value}}. For example, the same example would be encoded in OER as 0x02 04 00. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.11.1.3"
],
null,
null,
null,
null
]
}