OID reference
1.3.6.1.4.1.1206.4.2.17.2.18.1.2
<Definition> Each octet within the octet string contains the mapLaneIndex (binary value) that is to be broadcasted in a MAP data message. An octet of 00 indicates there are no additional lane indexes in the sequence. <Object Identifier> 1.3.6.1.4.1.1206.4.2.17.2.18.1.2
Identification
{1 3 6 1 4 1 1206 4 2 17 2 18 1 2}
Definitions may combine these properties differently.
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 NTCIP1217-v01, the row index mapPlanIndex 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.17.2.18.1.2.<mapPlanIndex>. 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.17.2.18.1.2
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.
mapPlanLanes OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-write
STATUS deprecated
DESCRIPTION "<Definition> Each octet within the octet string contains
the mapLaneIndex (binary value) that is to be broadcasted in a
MAP data message. An octet of 00 indicates there are no
additional lane indexes in the sequence.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.17.2.18.1.2"
DEFVAL { ''H }
::= { mapPlanEntry 2 }mapPlanLanes OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-write
STATUS mandatory
DESCRIPTION "<Definition> Each octet within the octet string contains
the mapLaneIndex (binary value) that is to be broadcasted in a
MAP data message. An octet of 00 indicates there are no
additional lane indexes in the sequence.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.17.2.18.1.2"
DEFVAL { ''H }
::= { mapPlanEntry 2 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
<Definition> Each octet within the octet string contains the mapLaneIndex (binary value) that is to be broadcasted in a MAP data message. An octet of 00 indicates there are no additional lane indexes in the sequence. <Object Identifier> 1.3.6.1.4.1.1206.4.2.17.2.18.1.2
NTCIP published standard MIB annexes (reviewed modules)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: unconfirmed.
Names: mapPlanLanes
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"mapPlanLanes",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"ACCESS",
"read-write",
"STATUS",
"deprecated",
"DESCRIPTION",
"\"<Definition> Each octet within the octet string contains the mapLaneIndex (binary value) that is to be broadcasted in a MAP data message. An octet of 00 indicates there are no additional lane indexes in the sequence. <Object Identifier> 1.3.6.1.4.1.1206.4.2.17.2.18.1.2\"",
"DEFVAL",
"{",
"'",
"'",
"H",
"}",
"::=",
"{",
"mapPlanEntry",
"2",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"deprecated"
],
[
"DESCRIPTION",
"<Definition> Each octet within the octet string contains the mapLaneIndex (binary value) that is to be broadcasted in a MAP data message. An octet of 00 indicates there are no additional lane indexes in the sequence. <Object Identifier> 1.3.6.1.4.1.1206.4.2.17.2.18.1.2"
],
null,
null,
null,
[
"DEFVAL",
"''H"
]
]
}Module: NTCIP1217-v01
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1213-MIB': ['DisplayString', 'ifIndex'], 'NTCIP8004v02': ['devices', 'OerString'], 'NTCIP1202-v03': ['channelNumber', 'signalGroupEntryNumber']}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: The mapSpeedLimitType DESCRIPTION starts with a duplicated malformed prefix. Mask only the extra DESCRIPTION prefix in an equal-length parsing copy, retaining the complete following native DESCRIPTION, original definition and unchanged OID assignment.
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.
Source data warning: Published source disagreement: this literal SMI assignment resolves to 1.3.6.1.4.1.1206.4.2.17.2.20.1.2, but its DESCRIPTION explicitly lists 1.3.6.1.4.1.1206.4.2.17.2.18.1.2. Both published numeric claims are retained as unconfirmed evidence. Neither value is presented as a verified correction or an independently confirmed registration; consult the original file and the applicable standard edition.
· Download NTCIP-1202v03.35e-aspublished.pdf — NTCIP1217-v01 (MIB transcription)Related source files and packages:
Status in source: unconfirmed.
Names: mapPlanLanes
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"mapPlanLanes",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> Each octet within the octet string contains the mapLaneIndex (binary value) that is to be broadcasted in a MAP data message. An octet of 00 indicates there are no additional lane indexes in the sequence. <Object Identifier> 1.3.6.1.4.1.1206.4.2.17.2.18.1.2\"",
"DEFVAL",
"{",
"'",
"'",
"H",
"}",
"::=",
"{",
"mapPlanEntry",
"2",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> Each octet within the octet string contains the mapLaneIndex (binary value) that is to be broadcasted in a MAP data message. An octet of 00 indicates there are no additional lane indexes in the sequence. <Object Identifier> 1.3.6.1.4.1.1206.4.2.17.2.18.1.2"
],
null,
null,
null,
[
"DEFVAL",
"''H"
]
]
}Module: NTCIP1217-v01
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1213-MIB': ['DisplayString', 'ifIndex'], 'NTCIP8004v02': ['Devices', 'OerString'], 'NTCIP1202-v03': ['channelNumber']}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: missing or unreadable imports of devices. 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.
Source data warning: Published source disagreement: this literal SMI assignment resolves to 1.3.6.1.4.1.1206.4.2.17.2.20.1.2, but its DESCRIPTION explicitly lists 1.3.6.1.4.1.1206.4.2.17.2.18.1.2. Both published numeric claims are retained as unconfirmed evidence. Neither value is presented as a verified correction or an independently confirmed registration; consult the original file and the applicable standard edition.
· Download NTCIP-1202v0328A.pdf — NTCIP1217-v01 (MIB transcription)Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1206.4.2.17.2.18.1.1 | mapPlanIndex | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.17.2.18.1.3 | mapPlanCRC | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.17.2.18.1.4 | mapPlanLayerType | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.17.2.18.1.5 | mapPlanLayerId | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.17.2.18.1.6 | mapPlanMetadataMethod | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.17.2.18.1.7 | mapPlanMetadataAgency | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.17.2.18.1.8 | mapPlanMetadataDate | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.17.2.18.1.9 | mapPlanMetadataGeoid | 0 | 0 |