Status in source: deprecated.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"recConfigEntry",
"OBJECT-TYPE",
"SYNTAX",
"RecConfigEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"deprecated",
"DESCRIPTION",
"\"<Definition>This object defines an entry in the recording configuration table. <Superseded by> NTCIP1201-RecMechV2.recMechV2FactoryEntry & COND-TRIGGER-MIB.fdCondTriggerEntry (ISO 20684-3) <Informative> The replacement trigger table has two indicies: an owner and a name. The replacement recording factory table has three indicies, an owner, the class name, and the factory name. In addition to the other changes described, the trigger table adds the following columns: - a textual description of the trigger - an indication whether the comparison is based on the current object value or a delta from its previous reading - an octet-based comparison value since SNMPv3 discourages the use of Opaque - a wildcard that allows defining the same condition on multiple comparison OIDs (e.g., all rows of a table) - indications of the target and context of the comparison object; in other words, the comparison can be performed by a proxy agent or can reference another device to get the object value to compare against - the frequency at which the comparison is made - a truthDuration that allows the configuration to require the evaluation to be true for some length of time prior to firing the trigger. - startup states that define whether the triggers startup in a fired or unfired state (for hysteresis, there are two startups) - a pointer to the action table that identifies the action(s) to be performed. - an error message object that allows a device to report configuration errors. - counters for the number of times the trigger has fired, had evaluation errors, and activation errors. - an indication of the type of storage to use - a RowStatus object. The recMech factory table adds the following columns: - the security data used to activate the row and that will be used to retrieve values for the recording - object contexts, which allows a proxy/hrbrid agent to capture information from another context - A StorageType object <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7.1\"",
"INDEX",
"{",
"recConfigID",
"}",
"::=",
"{",
"recConfigTable",
"1",
"}"
],
"syntax_tree": [
[
"row",
"RecConfigEntry"
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"deprecated"
],
[
"DESCRIPTION",
"<Definition>This object defines an entry in the recording configuration table. <Superseded by> NTCIP1201-RecMechV2.recMechV2FactoryEntry & COND-TRIGGER-MIB.fdCondTriggerEntry (ISO 20684-3) <Informative> The replacement trigger table has two indicies: an owner and a name. The replacement recording factory table has three indicies, an owner, the class name, and the factory name. In addition to the other changes described, the trigger table adds the following columns: - a textual description of the trigger - an indication whether the comparison is based on the current object value or a delta from its previous reading - an octet-based comparison value since SNMPv3 discourages the use of Opaque - a wildcard that allows defining the same condition on multiple comparison OIDs (e.g., all rows of a table) - indications of the target and context of the comparison object; in other words, the comparison can be performed by a proxy agent or can reference another device to get the object value to compare against - the frequency at which the comparison is made - a truthDuration that allows the configuration to require the evaluation to be true for some length of time prior to firing the trigger. - startup states that define whether the triggers startup in a fired or unfired state (for hysteresis, there are two startups) - a pointer to the action table that identifies the action(s) to be performed. - an error message object that allows a device to report configuration errors. - counters for the number of times the trigger has fired, had evaluation errors, and activation errors. - an indication of the type of storage to use - a RowStatus object. The recMech factory table adds the following columns: - the security data used to activate the row and that will be used to retrieve values for the recording - object contexts, which allows a proxy/hrbrid agent to capture information from another context - A StorageType object <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7.1"
],
null,
null,
[
"INDEX",
[
[
0,
"recConfigID"
]
]
],
null
]
}