OID reference
1.3.6.1.4.1.1206.4.1.1.7.9.7
<Definition>A table containing Recording Mechanism Configuration information. The number of rows in this table is equal to the maxRecConfigs object. This table defines the parameters that the device monitors to create a recording. <TableType> static <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7
Identification
{1 3 6 1 4 1 1206 4 1 1 7 9 7}
Definitions may combine these properties differently.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
Available source records contain 3 distinct definitions; some records may not include a definition.
recConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF RecConfigEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"<Definition>A table containing Recording Mechanism Configuration
information. The number of rows in this table is equal to
the maxRecConfigs object. This table defines the
parameters that the device monitors to create a recording.
<TableType> static
<Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7
"
::= { recMech 7 }recConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF RecConfigEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"<Definition>A table containing Recording Mechanism Configuration
information. The number of rows in this table is equal to
the maxRecConfigs object. This table defines the
parameters that the device monitors to create a recording.
<TableType> static
<Superseded by> NTCIP1201-RecMechV2.recMechV2FactoryTable &
COND-TRIGGER-MIB.fdCondTriggerTable (ISO 20684-3)
<Informative> The replacement design divides the recConfigTable into
two tables: one that defines triggers that can be used to start
recordings or other actions and a second table that defines what to
record when the recording action is triggered.
<Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7"
::= { recMech 7 }recConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF RecConfigEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"<Definition>A table containing Recording Mechanism Configuration
information. The number of rows in this table is equal to the maxRecConfigs
object. This table defines the parameters that the device monitors to
create a recording.
<Table Type> static
<Supplanted by> ISO26048-1-Recording.fdRecordingFactoryTable & ISO26048-1-
CondTrigger.fdCondTriggerTable (ISO 26048-1)
<Informative> The replacement design divides the recConfigTable into two
tables: one that defines triggers that can be used to start recordings or
other actions and a second table that defines what to record when the
recording action is triggered.
<Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7"
::= { recMech 7 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
<Definition>A table containing Recording Mechanism Configuration information. The number of rows in this table is equal to the maxRecConfigs object. This table defines the parameters that the device monitors to create a recording. <TableType> static <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7
NTCIP published standard MIB annexes (reviewed modules)
Description 2
<Definition>A table containing Recording Mechanism Configuration information. The number of rows in this table is equal to the maxRecConfigs object. This table defines the parameters that the device monitors to create a recording. <TableType> static <Superseded by> NTCIP1201-RecMechV2.recMechV2FactoryTable & COND-TRIGGER-MIB.fdCondTriggerTable (ISO 20684-3) <Informative> The replacement design divides the recConfigTable into two tables: one that defines triggers that can be used to start recordings or other actions and a second table that defines what to record when the recording action is triggered. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7
Description 3
<Definition>A table containing Recording Mechanism Configuration information. The number of rows in this table is equal to the maxRecConfigs object. This table defines the parameters that the device monitors to create a recording. <Table Type> static <Supplanted by> ISO26048-1-Recording.fdRecordingFactoryTable & ISO26048-1- CondTrigger.fdCondTriggerTable (ISO 26048-1) <Informative> The replacement design divides the recConfigTable into two tables: one that defines triggers that can be used to start recordings or other actions and a second table that defines what to record when the recording action is triggered. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7
NTCIP published standard MIB annexes (reviewed modules)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: mandatory.
Names: recConfigTable
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"recConfigTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"RecConfigEntry",
"ACCESS",
"not-accessible",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition>A table containing Recording Mechanism Configuration information. The number of rows in this table is equal to the maxRecConfigs object. This table defines the parameters that the device monitors to create a recording. <TableType> static <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7 \"",
"::=",
"{",
"recMech",
"7",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"RecConfigEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition>A table containing Recording Mechanism Configuration information. The number of rows in this table is equal to the maxRecConfigs object. This table defines the parameters that the device monitors to create a recording. <TableType> static <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7"
],
null,
null,
null,
null
]
}Module: NTCIP1103v0352-RechMech
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter', 'Opaque', 'NetworkAddress', 'null'], 'NTCIP8004-2008': ['Application', 'OerString']}Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: missing or unreadable imports of application. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.
· Download NTCIP1103v0352b.pdf — NTCIP1103v0352-RechMech (MIB transcription)Related source files and packages:
Status in source: deprecated.
Names: recConfigTable
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"recConfigTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"RecConfigEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"deprecated",
"DESCRIPTION",
"\"<Definition>A table containing Recording Mechanism Configuration information. The number of rows in this table is equal to the maxRecConfigs object. This table defines the parameters that the device monitors to create a recording. <TableType> static <Superseded by> NTCIP1201-RecMechV2.recMechV2FactoryTable & COND-TRIGGER-MIB.fdCondTriggerTable (ISO 20684-3) <Informative> The replacement design divides the recConfigTable into two tables: one that defines triggers that can be used to start recordings or other actions and a second table that defines what to record when the recording action is triggered. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7\"",
"::=",
"{",
"recMech",
"7",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"RecConfigEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"deprecated"
],
[
"DESCRIPTION",
"<Definition>A table containing Recording Mechanism Configuration information. The number of rows in this table is equal to the maxRecConfigs object. This table defines the parameters that the device monitors to create a recording. <TableType> static <Superseded by> NTCIP1201-RecMechV2.recMechV2FactoryTable & COND-TRIGGER-MIB.fdCondTriggerTable (ISO 20684-3) <Informative> The replacement design divides the recConfigTable into two tables: one that defines triggers that can be used to start recordings or other actions and a second table that defines what to record when the recording action is triggered. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7"
],
null,
null,
null,
null
]
}Module: NTCIP1201-RecMech
See published definition above
{'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32', 'Counter32', 'IpAddress', 'Opaque', 'zeroDotZero'], 'SNMPv2-CONF': ['OBJECT-GROUP'], 'FIELD-DEVICE-TC-MIB': ['ITSOerString'], 'NTCIP8004-Transportation': ['application']}Source data warning: This original is published in an ITE NTCIP working repository. Repository publication does not establish that this particular revision is an adopted standard. Consult its native revision history and the NTCIP published standards catalog before implementation. Copyright and distribution notices are retained in the downloadable original.
· Download NTCIP-1201 — ntcip1201-AuxIO.mibSame file in ntcip1201-SNMPConfig.mib.
Same file in ntcip1201-Security.mib.
Same file in ntcip1201-ProfilesSTMP.mib.
Same file in ntcip1201-NtcipTraps.mib.
Module: NTCIP1201-RecMech
{'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32', 'Counter32', 'IpAddress', 'Opaque', 'zeroDotZero'], 'SNMPv2-CONF': ['OBJECT-GROUP'], 'FIELD-DEVICE-TC-MIB': ['ITSOerString'], 'NTCIP8004-Transportation': ['application']}Source data warning: This original is published in an ITE NTCIP working repository. Repository publication does not establish that this particular revision is an adopted standard. Consult its native revision history and the NTCIP published standards catalog before implementation. Copyright and distribution notices are retained in the downloadable original.
· Download NTCIP-1201 — ntcip1201-RecMech.mibStatus in source: deprecated.
Names: recConfigTable
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"recConfigTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"RecConfigEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"deprecated",
"DESCRIPTION",
"\"<Definition>A table containing Recording Mechanism Configuration information. The number of rows in this table is equal to the maxRecConfigs object. This table defines the parameters that the device monitors to create a recording. <Table Type> static <Supplanted by> ISO26048-1-Recording.fdRecordingFactoryTable & ISO26048-1- CondTrigger.fdCondTriggerTable (ISO 26048-1) <Informative> The replacement design divides the recConfigTable into two tables: one that defines triggers that can be used to start recordings or other actions and a second table that defines what to record when the recording action is triggered. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7\"",
"::=",
"{",
"recMech",
"7",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"RecConfigEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"deprecated"
],
[
"DESCRIPTION",
"<Definition>A table containing Recording Mechanism Configuration information. The number of rows in this table is equal to the maxRecConfigs object. This table defines the parameters that the device monitors to create a recording. <Table Type> static <Supplanted by> ISO26048-1-Recording.fdRecordingFactoryTable & ISO26048-1- CondTrigger.fdCondTriggerTable (ISO 26048-1) <Informative> The replacement design divides the recConfigTable into two tables: one that defines triggers that can be used to start recordings or other actions and a second table that defines what to record when the recording action is triggered. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7"
],
null,
null,
null,
null
]
}Module: NTCIP1201-RecMech
See published definition above
{'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32', 'Opaque', 'zeroDotZero'], 'NTCIP8004-Transportation': ['application']}Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.
· Download 1201v4-0-0.pdf — NTCIP1201-RecMech (MIB transcription)Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1206.4.1.1.7.9.7.1 | recConfigEntry | 13 | 13 |
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1206.4.1.1.7.9.1 | maxRecClasses | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.1.1.7.9.2 | recClassTable | 1 | 7 | |
| 1.3.6.1.4.1.1206.4.1.1.7.9.3 | maxRecConfigs | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.1.1.7.9.4 | recMinSamplePeriod | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.1.1.7.9.5 | recMaxSamplePeriod | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.1.1.7.9.6 | recSamplePeriodResolution | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.1.1.7.9.8 | maxRecordings | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.1.1.7.9.9 | recRecordingTable | 1 | 9 | |
| 1.3.6.1.4.1.1206.4.1.1.7.9.10 | maxRecEntries | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.1.1.7.9.11 | recEntriesTable | 1 | 4 | |
| 1.3.6.1.4.1.1206.4.1.1.7.9.12 | numRecordings | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.1.1.7.9.13 | recClearClasses | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.1.1.7.9.14 | recClearConfigurations | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.1.1.7.9.15 | recClearRecordingData | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.1.1.7.9.127 | recMechConformance | 2 | 3 |