OID reference
1.3.6.1.4.1.1206.4.2.18.7.2.1.5
<Definition> Sets which direction of communications traffic to capture in the interface data log. biSeparate (3) indicates both directions are to be captured but in separate interface data log files, while biCombined (4) indicates both directions are to be captured in the same interface data log file. <Object Identifi…
Identification
{1 3 6 1 4 1 1206 4 2 18 7 2 1 5}
| Value | Name |
|---|---|
| 1 | inboundOnly |
| 2 | outboundOnly |
| 3 | biSeparate |
| 4 | biCombined |
At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.
Published row index: rsuIfaceLogIndex.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.1206.4.2.18.7.2.1.5
Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
The displayed source records contain one distinct definition. Compare its source records.
rsuIfaceLogByDir OBJECT-TYPE
SYNTAX INTEGER { inboundOnly (1),
outboundOnly (2),
biSeparate (3),
biCombined (4) }
MAX-ACCESS read-create
STATUS current
DESCRIPTION "<Definition> Sets which direction of communications traffic
to capture in the interface data log. biSeparate (3) indicates both
directions are to be captured but in separate interface data log
files, while biCombined (4) indicates both directions are to be
captured in the same interface data log file.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.18.7.2.1.5"
::= { rsuInterfaceLogEntry 5 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
<Definition> Sets which direction of communications traffic to capture in the interface data log. biSeparate (3) indicates both directions are to be captured but in separate interface data log files, while biCombined (4) indicates both directions are to be captured in the same interface data log file. <Object Identifier> 1.3.6.1.4.1.1206.4.2.18.7.2.1.5
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: rsuIfaceLogByDir
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rsuIfaceLogByDir",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"inboundOnly",
"(",
"1",
")",
",",
"outboundOnly",
"(",
"2",
")",
",",
"biSeparate",
"(",
"3",
")",
",",
"biCombined",
"(",
"4",
")",
"}",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"<Definition> Sets which direction of communications traffic to capture in the interface data log. biSeparate (3) indicates both directions are to be captured but in separate interface data log files, while biCombined (4) indicates both directions are to be captured in the same interface data log file. <Object Identifier> 1.3.6.1.4.1.1206.4.2.18.7.2.1.5\"",
"::=",
"{",
"rsuInterfaceLogEntry",
"5",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"inboundOnly",
1
],
[
"outboundOnly",
2
],
[
"biSeparate",
3
],
[
"biCombined",
4
]
]
]
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"<Definition> Sets which direction of communications traffic to capture in the interface data log. biSeparate (3) indicates both directions are to be captured but in separate interface data log files, while biCombined (4) indicates both directions are to be captured in the same interface data log file. <Object Identifier> 1.3.6.1.4.1.1206.4.2.18.7.2.1.5"
],
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
Same published definition (formatting differs; exact original is in the source file)
{'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
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1206.4.2.18.7.2.1.1 | rsuIfaceLogIndex | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.18.7.2.1.2 | rsuIfaceGenerate | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.18.7.2.1.3 | rsuIfaceMaxFileSize | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.18.7.2.1.4 | rsuIfaceMaxFileTime | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.18.7.2.1.6 | rsuIfaceName | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.18.7.2.1.7 | rsuIfaceStoragePath | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.18.7.2.1.8 | rsuIfaceLogName | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.18.7.2.1.9 | rsuIfaceLogStart | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.18.7.2.1.10 | rsuIfaceLogStop | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.18.7.2.1.11 | rsuIfaceLogOptions | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.18.7.2.1.12 | rsuIfaceLogStatus | 0 | 0 |