OID reference
1.3.6.1.4.1.1206.4.2.18.14.3
<Definition> Start time, in UTC, for filtering events. This time is supplied in the format of the first 8 octets in the DateAndTime field as defined in RFC2579. Example: October 7, 2017 at 11:34:01.4 PM UTC would be encoded as 07e10a0717220104. <Object Identifier> 1.3.6.1.4.1.1206.4.2.18.14.3
Identification
{1 3 6 1 4 1 1206 4 2 18 14 3}
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 2 distinct definitions; some records may not include a definition.
rsuSysLogQueryStart OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-write
STATUS current
DESCRIPTION "<Definition> Start time, in UTC, for filtering events. This
time is supplied in the format of the first 8 octets in the
DateAndTime field as defined in RFC2579. Example: October 7, 2017 at
11:34:01.4 PM UTC would be encoded as 07e10a0717220104.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.18.14.3"
::= { rsuSysSettings 3 }rsuSysLogQueryStart OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-write
STATUS current
DESCRIPTION "<Definition> Start time, in UTC, for filtering events. This
time is supplied in the format of the first 8 octets in the
DateAndTime field as defined in RFC2579. Example: October 7, 2017 at
11:34:01.4 PM UTC would be encoded as 07e10a0717220104.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.18.14.3"
::= { rsuSysSettings 3 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
<Definition> Start time, in UTC, for filtering events. This time is supplied in the format of the first 8 octets in the DateAndTime field as defined in RFC2579. Example: October 7, 2017 at 11:34:01.4 PM UTC would be encoded as 07e10a0717220104. <Object Identifier> 1.3.6.1.4.1.1206.4.2.18.14.3
NTCIP published standard MIB annexes (reviewed modules)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: rsuSysLogQueryStart
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rsuSysLogQueryStart",
"OBJECT-TYPE",
"SYNTAX",
"DateAndTime",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"<Definition> Start time, in UTC, for filtering events. This time is supplied in the format of the first 8 octets in the DateAndTime field as defined in RFC2579. Example: October 7, 2017 at 11:34:01.4 PM UTC would be encoded as 07e10a0717220104. <Object Identifier> 1.3.6.1.4.1.1206.4.2.18.14.3\"",
"::=",
"{",
"rsuSysSettings",
"3",
"}"
],
"syntax_tree": [
[
"row",
"DateAndTime"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"<Definition> Start time, in UTC, for filtering events. This time is supplied in the format of the first 8 octets in the DateAndTime field as defined in RFC2579. Example: October 7, 2017 at 11:34:01.4 PM UTC would be encoded as 07e10a0717220104. <Object Identifier> 1.3.6.1.4.1.1206.4.2.18.14.3"
],
null,
null,
null,
null
]
}Module: NTCIP1218-v01
See published definition above
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DateAndTime', 'RowStatus', 'DisplayString', 'MacAddress'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Counter32', 'NOTIFICATION-TYPE', 'enterprises'], 'URI-TC-MIB': ['Uri255', 'Uri1024'], 'NTCIP8004v02': ['devices', 'OerString'], 'SYSLOG-TC-MIB': ['SyslogSeverity'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}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: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP8004v02. 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 NTCIP-1218-v01A-2024-AsPublished.pdf — NTCIP1218-v01 (MIB transcription)Related source files and packages:
Module: NTCIP1218-v01
See published definition above
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DateAndTime', 'RowStatus', 'DisplayString', 'MacAddress'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Counter32', 'NOTIFICATION-TYPE', 'enterprises'], 'URI-TC-MIB': ['Uri255', 'Uri1024'], 'SYSLOG-TC-MIB': ['SyslogSeverity']}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.
· Download NTCIP-1218v0138-RSU-toUSDOT-20200905.pdf — NTCIP1218-v01 (MIB transcription)Related source files and packages:
Registration