OID reference
1.3.6.1.4.1.1206.4.2.1.16.5.1.1
<Definition> Optional SPAT functions for this SPAT port(0 = False/Disabled, 1 = True/Enabled) Bit 1 - 7: Reserved Bit 0: Enabled SPAT. Provides a means to enable the CU to exchange SPAT data on this RSU port. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.16.5.1.1
Identification
{1 3 6 1 4 1 1206 4 2 1 16 5 1 1}
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.
In NTCIP1202-v03, the row index rsuPortIndex is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.1206.4.2.1.16.5.1.1.<rsuPortIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.1206.4.2.1.16.5.1.1
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.
Available source records contain 2 distinct definitions; some records may not include a definition.
spatPortOptions OBJECT-TYPE
SYNTAX INTEGER(0..255)
ACCESS read-write
STATUS mandatory
DESCRIPTION "<Definition> Optional SPAT functions for this SPAT port(0
= False/Disabled, 1 = True/Enabled)
Bit 1 - 7: Reserved
Bit 0: Enabled SPAT. Provides a means to enable the CU to
exchange SPAT data on this RSU port.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.1.16.5.1.1"
::= { spatPortEntry 1 }spatPortOptions OBJECT-TYPE
SYNTAX INTEGER(0..255)
ACCESS read-write
STATUS mandatory
DESCRIPTION "<Definition> Optional SPaT functions for this SPaT port(0
= False/Disabled, 1 = True/Enabled)
Bit 3 - 7: Reserved
Bit 2: MAP Validity. Indicates if the MAP data message
broadcasted by the RSU on this RSU port is valid (1) or invalid
(0). When this bit is one, the MAP Message broadcasted by the CV
Roadside Process is considered valid. When this bit is 0, then
the MAP message broadcasted by the RSU is considered invalid and
should not be used except for test purposes.
Bit 1: SPaT Validity. Indicates if the SPaT data on this RSU port
is valid (1) or invalid (0). When this bit is one, the SPaT data
provided by the controller is considered valid. When this bit is
0, then the SPaT data provided by the controller is considered
invalid and should not be used except for test purposes.
Bit 0: Enabled SPaT. Provides a means to enable the CU to
exchange SPaT data on this RSU port.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.1.16.5.1.1
<Object Type> P"
::= { spatPortEntry 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
<Definition> Optional SPAT functions for this SPAT port(0 = False/Disabled, 1 = True/Enabled) Bit 1 - 7: Reserved Bit 0: Enabled SPAT. Provides a means to enable the CU to exchange SPAT data on this RSU port. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.16.5.1.1
NTCIP published standard MIB annexes (reviewed modules)
Description 2
<Definition> Optional SPaT functions for this SPaT port(0 = False/Disabled, 1 = True/Enabled) Bit 3 - 7: Reserved Bit 2: MAP Validity. Indicates if the MAP data message broadcasted by the RSU on this RSU port is valid (1) or invalid (0). When this bit is one, the MAP Message broadcasted by the CV Roadside Process is considered valid. When this bit is 0, then the MAP message broadcasted by the RSU is considered invalid and should not be used except for test purposes. Bit 1: SPaT Validity. Indicates if the SPaT data on this RSU port is valid (1) or invalid (0). When this bit is one, the SPaT data provided by the controller is considered valid. When this bit is 0, then the SPaT data provided by the controller is considered invalid and should not be used except for test purposes. Bit 0: Enabled SPaT. Provides a means to enable the CU to exchange SPaT data on this RSU port. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.16.5.1.1 <Object Type> P
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: spatPortOptions
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"spatPortOptions",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"255",
")",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> Optional SPAT functions for this SPAT port(0 = False/Disabled, 1 = True/Enabled) Bit 1 - 7: Reserved Bit 0: Enabled SPAT. Provides a means to enable the CU to exchange SPAT data on this RSU port. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.16.5.1.1\"",
"::=",
"{",
"spatPortEntry",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> Optional SPAT functions for this SPAT port(0 = False/Disabled, 1 = True/Enabled) Bit 1 - 7: Reserved Bit 0: Enabled SPAT. Provides a means to enable the CU to exchange SPAT data on this RSU port. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.16.5.1.1"
],
null,
null,
null,
null
]
}Module: NTCIP1202-v03
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter', 'null'], 'RFC1213-MIB': ['DisplayString', 'ifIndex'], 'NTCIP8004v02': ['OwnerString', 'OerString', 'devices']}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-1202v0328A.pdf — NTCIP1202-v03 (MIB transcription)Related source files and packages:
Status in source: mandatory.
Names: spatPortOptions
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"spatPortOptions",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"255",
")",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> Optional SPaT functions for this SPaT port(0 = False/Disabled, 1 = True/Enabled) Bit 3 - 7: Reserved Bit 2: MAP Validity. Indicates if the MAP data message broadcasted by the RSU on this RSU port is valid (1) or invalid (0). When this bit is one, the MAP Message broadcasted by the CV Roadside Process is considered valid. When this bit is 0, then the MAP message broadcasted by the RSU is considered invalid and should not be used except for test purposes. Bit 1: SPaT Validity. Indicates if the SPaT data on this RSU port is valid (1) or invalid (0). When this bit is one, the SPaT data provided by the controller is considered valid. When this bit is 0, then the SPaT data provided by the controller is considered invalid and should not be used except for test purposes. Bit 0: Enabled SPaT. Provides a means to enable the CU to exchange SPaT data on this RSU port. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.16.5.1.1 <Object Type> P\"",
"::=",
"{",
"spatPortEntry",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> Optional SPaT functions for this SPaT port(0 = False/Disabled, 1 = True/Enabled) Bit 3 - 7: Reserved Bit 2: MAP Validity. Indicates if the MAP data message broadcasted by the RSU on this RSU port is valid (1) or invalid (0). When this bit is one, the MAP Message broadcasted by the CV Roadside Process is considered valid. When this bit is 0, then the MAP message broadcasted by the RSU is considered invalid and should not be used except for test purposes. Bit 1: SPaT Validity. Indicates if the SPaT data on this RSU port is valid (1) or invalid (0). When this bit is one, the SPaT data provided by the controller is considered valid. When this bit is 0, then the SPaT data provided by the controller is considered invalid and should not be used except for test purposes. Bit 0: Enabled SPaT. Provides a means to enable the CU to exchange SPaT data on this RSU port. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.16.5.1.1 <Object Type> P"
],
null,
null,
null,
null
]
}Module: NTCIP1202-v03
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter', 'null'], 'RFC1213-MIB': ['DisplayString', 'ifIndex'], 'NTCIP8004v02': ['OwnerString', 'OerString', 'devices']}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-1202v03.35e-aspublished.pdf — NTCIP1202-v03 (MIB transcription)Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1206.4.2.1.16.5.1.2 | spatPortStatus | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.1.16.5.1.3 | spatPortMapActivationCode | 0 | 0 |