Status in source: mandatory.
Names: rmcMeterInOutEntry
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rmcMeterInOutEntry",
"OBJECT-TYPE",
"SYNTAX",
"RmcMeterInOutEntry",
"ACCESS",
"not-accessible",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"Configuration parameters of the metered lane physical input/output table. This table is directly correlated to the Metered Lane Control Table, which means that the number of rows in this table is exactly the same as the number of rows in the Metered Lane Control Table (AUGMENT TABLE in SNMPv2 terminology). Table management can only take place through the Metered Lane Control Table (rmcMeterCtrlTable), while this table defines the associated physical input and outputs. <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.6.4.1\"",
"INDEX",
"{",
"rmcMeterNumber",
"}",
"::=",
"{",
"rmcMeterInOutTable",
"1",
"}"
],
"syntax_tree": [
[
"row",
"RmcMeterInOutEntry"
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Configuration parameters of the metered lane physical input/output table. This table is directly correlated to the Metered Lane Control Table, which means that the number of rows in this table is exactly the same as the number of rows in the Metered Lane Control Table (AUGMENT TABLE in SNMPv2 terminology). Table management can only take place through the Metered Lane Control Table (rmcMeterCtrlTable), while this table defines the associated physical input and outputs. <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.6.4.1"
],
null,
null,
[
"INDEX",
[
[
0,
"rmcMeterNumber"
]
]
],
null
]
}
- NTCIP published standard MIB annexes (reviewed modules)
· Publisher's source file: NTCIP 1207 v02, Object Definitions for Ramp Meter Control (RMC) Units Published September 2014 — original PDF
· Official record
Module: N207v0214-MIB
See published definition above
Module imports
{'NTCIP': ['ramp'], 'RFC-1212': ['OBJECT-TYPE']}Source data warning: Recovered from a file whose complete MIB does not parse. The original assignment and definition are preserved. Registration and implementation details may be inaccurate; consult the original file. Other damaged or unresolved declarations are not established registrations.
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: A typographic closing DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.
Source data warning: The PDF prints an invalid ASN.1 module label (1207v0214-MIB). The derived transcription uses an equal-length internal parsing label; this is not an OID registration or an alteration of any numeric assignment. The original label and full PDF are retained.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP. 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 NTCIP1207v0214hj.pdf — N207v0214-MIB (MIB transcription)
Related source files and packages:
Show more related files and packages