OID reference

commPortType

1.3.6.1.4.1.1206.4.2.1.3.23.2.1.1

Description

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.1206.4.2.1.3.23.2.1 (commPortsEntry)
Node code: 1
Node name: commPortType
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.1206.4.2.1.3.23.2.1.1
URN notation: urn:oid:1.3.6.1.4.1.1206.4.2.1.3.23.2.1.1

ASN.1, OID-IRI and named path variants

ASN.1 notation

{1 3 6 1 4 1 1206 4 2 1 3 23 2 1 1}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) commPorts(23) commPortTable(2) commPortsEntry(1) commPortType(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) commPorts(23) commPortTable(2) commPortsEntry(1) commPortType(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) commPorts(23) commPortTable(2) commPortsEntry(1) commPortType(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) commPorts(23) commPortTable(2) commPortsEntry(1) commPortType(1)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) commPorts(23) commPortTable(2) commPortsEntry(1) commPortType(1)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) commPorts(23) commPortTable(2) commPortsEntry(1) commPortType(1)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) commPorts(23) commPortTable(2) commPortsEntry(1) commPortType(1)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) commPorts(23) commPortTable(2) commPortsEntry(1) commPortType(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) commPorts(23) commPortTable(2) commPortsEntry(1) commPortType(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) commPorts(23) commPortTable(2) commPortsEntry(1) commPortType(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) commPorts(23) commPortTable(2) commPortsEntry(1) commPortType(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) commPorts(23) commPortTable(2) commPortsEntry(1) commPortType(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) commPorts(23) commPortTable(2) commPortsEntry(1) commPortType(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) commPorts(23) commPortTable(2) commPortsEntry(1) commPortType(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) commPorts(23) commPortTable(2) commPortsEntry(1) commPortType(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) commPorts(23) commPortTable(2) commPortsEntry(1) commPortType(1)}

OID-IRI notation

/1/3/6/1/4/1/1206/4/2/1/3/23/2/1/1
/ISO/Identified-Organization/6/1/4/1/1206/4/2/1/3/23/2/1/1
/ISO/3/6/1/4/1/1206/4/2/1/3/23/2/1/1

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/asc/unit/commPorts/commPortTable/commPortsEntry/commPortType
/iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/asc/unit/commPorts/commPortTable/commPortsEntry/commPortType
/iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/asc/unit/commPorts/commPortTable/commPortsEntry/commPortType
/iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/asc/unit/commPorts/commPortTable/commPortsEntry/commPortType
/iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/asc/unit/commPorts/commPortTable/commPortsEntry/commPortType
/iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/asc/unit/commPorts/commPortTable/commPortsEntry/commPortType
/iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/asc/unit/commPorts/commPortTable/commPortsEntry/commPortType
/iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/asc/unit/commPorts/commPortTable/commPortsEntry/commPortType
/iso/org/dod/internet/private/enterprise/1206/transportation/devices/asc/unit/commPorts/commPortTable/commPortsEntry/commPortType
/iso/org/dod/internet/private/enterprise/nema/transportation/devices/asc/unit/commPorts/commPortTable/commPortsEntry/commPortType
/iso/org/dod/internet/private/enterprises/1206/transportation/devices/asc/unit/commPorts/commPortTable/commPortsEntry/commPortType
/iso/org/dod/internet/private/enterprises/nema/transportation/devices/asc/unit/commPorts/commPortTable/commPortsEntry/commPortType
/iso/org/dod/internet/private/ldap-enterprise/1206/transportation/devices/asc/unit/commPorts/commPortTable/commPortsEntry/commPortType
/iso/org/dod/internet/private/ldap-enterprise/nema/transportation/devices/asc/unit/commPorts/commPortTable/commPortsEntry/commPortType
/iso/org/dod/internet/private/vendor-objects/1206/transportation/devices/asc/unit/commPorts/commPortTable/commPortsEntry/commPortType
/iso/org/dod/internet/private/vendor-objects/nema/transportation/devices/asc/unit/commPorts/commPortTable/commPortsEntry/commPortType
Additional combinations skipped.

SNMP properties

Value type: INTEGER
Maximum access defined by MIB: read-only
Status in MIB: mandatory

Enumerated values

Value	Name
1	other
2	ethernet
3	rs232like

Using this OID with SNMP

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: ifIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.1206.4.2.1.3.23.2.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.

Published definitions

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

commPortType · mandatory

commPortType    OBJECT-TYPE
      SYNTAX    INTEGER { other (1),
             ethernet (2),
             rs232like (3) }
      ACCESS    read-only
      STATUS    mandatory
      DESCRIPTION "<Definition> This object identifies the port type.
             Although RFC 1213 contains ifType, this object provides the
             user/device further guidance to additional objects that define
             the port and its configuration. The valid port types are defined
             as follows:
             other: the port type is not defined by this standard.
             Ethernet: the port type is Ethernet based (i.e. IP) and
             configured per NTCIP 2104 and 2202
             rs232like: the port type is rs-232-like (per RFC 1317) and may be
             either an asynchronous or synchronous serial. Port configuration
             is contained in RFC 1317 rs232PortTable
      <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.3.23.2.1.1
      <Object Type> S"
::= { commPortsEntry 1 }

commPortType · mandatory

commPortType    OBJECT-TYPE
      SYNTAX    INTEGER { other (1),
             ethernet (2),
             rs232like (3) }
      ACCESS    read-only
      STATUS    mandatory
      DESCRIPTION "<Definition> This object identifies the port type.
             Although RFC 1213 contains ifType, this object provides the
             user/device further guidance to additional objects that define
             the port and its configuration. The valid port types are defined
             as follows:
             other: the port type is not defined by this standard.
             Ethernet: the port type is Ethernet based (i.e. IP) and
             configured per NTCIP 2104 and 2202
             rs232like: the port type is rs-232-like (per RFC 1317) and may be
             either an asynchronous or synchronous serial. Port configuration
             is contained in RFC 1317 rs232PortTable
      <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.3.23.2.1.1"
::= { commPortsEntry 1 }

Meaning

Descriptions

2 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Description 1

<Definition> This object identifies the port type. Although RFC 1213 contains ifType, this object provides the user/device further guidance to additional objects that define the port and its configuration. The valid port types are defined as follows: other: the port type is not defined by this standard. Ethernet: the port type is Ethernet based (i.e. IP) and configured per NTCIP 2104 and 2202 rs232like: the port type is rs-232-like (per RFC 1317) and may be either an asynchronous or synchronous serial. Port configuration is contained in RFC 1317 rs232PortTable <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.3.23.2.1.1 <Object Type> S

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 2

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Evidence

Source records

2 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 1

commPortType · mandatoryNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: mandatory.

Names: commPortType

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "commPortType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "other",
    "(",
    "1",
    ")",
    ",",
    "ethernet",
    "(",
    "2",
    ")",
    ",",
    "rs232like",
    "(",
    "3",
    ")",
    "}",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> This object identifies the port type. Although RFC 1213 contains ifType, this object provides the user/device further guidance to additional objects that define the port and its configuration. The valid port types are defined as follows: other: the port type is not defined by this standard. Ethernet: the port type is Ethernet based (i.e. IP) and configured per NTCIP 2104 and 2202 rs232like: the port type is rs-232-like (per RFC 1317) and may be either an asynchronous or synchronous serial. Port configuration is contained in RFC 1317 rs232PortTable <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.3.23.2.1.1 <Object Type> S\"",
    "::=",
    "{",
    "commPortsEntry",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "other",
            1
          ],
          [
            "ethernet",
            2
          ],
          [
            "rs232like",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> This object identifies the port type. Although RFC 1213 contains ifType, this object provides the user/device further guidance to additional objects that define the port and its configuration. The valid port types are defined as follows: other: the port type is not defined by this standard. Ethernet: the port type is Ethernet based (i.e. IP) and configured per NTCIP 2104 and 2202 rs232like: the port type is rs-232-like (per RFC 1317) and may be either an asynchronous or synchronous serial. Port configuration is contained in RFC 1317 rs232PortTable <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.3.23.2.1.1 <Object Type> S"
    ],
    null,
    null,
    null,
    null
  ]
}

NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1202 v03b NTCIP 1202 v02, Object Definitions for Actuated Traffic Signal Controller (ASC) Units – version 03b Published October 2023 — original PDF · Official record
Module: NTCIP1202-v03

See published definition above
Module imports
```
{'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)
Related source files and packages:
Show more related files and packages
- NTCIP8004-NEMA.mib — ITE namespace dependency
- NTCIP8004-Transportation.mib — ITE namespace dependency

Records for description 2NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 2

commPortType · mandatoryNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: mandatory.

Names: commPortType

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "commPortType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "other",
    "(",
    "1",
    ")",
    ",",
    "ethernet",
    "(",
    "2",
    ")",
    ",",
    "rs232like",
    "(",
    "3",
    ")",
    "}",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> This object identifies the port type. Although RFC 1213 contains ifType, this object provides the user/device further guidance to additional objects that define the port and its configuration. The valid port types are defined as follows: other: the port type is not defined by this standard. Ethernet: the port type is Ethernet based (i.e. IP) and configured per NTCIP 2104 and 2202 rs232like: the port type is rs-232-like (per RFC 1317) and may be either an asynchronous or synchronous serial. Port configuration is contained in RFC 1317 rs232PortTable <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.3.23.2.1.1\"",
    "::=",
    "{",
    "commPortsEntry",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "other",
            1
          ],
          [
            "ethernet",
            2
          ],
          [
            "rs232like",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> This object identifies the port type. Although RFC 1213 contains ifType, this object provides the user/device further guidance to additional objects that define the port and its configuration. The valid port types are defined as follows: other: the port type is not defined by this standard. Ethernet: the port type is Ethernet based (i.e. IP) and configured per NTCIP 2104 and 2202 rs232like: the port type is rs-232-like (per RFC 1317) and may be either an asynchronous or synchronous serial. Port configuration is contained in RFC 1317 rs232PortTable <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.3.23.2.1.1"
    ],
    null,
    null,
    null,
    null
  ]
}

NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1202 v03A, Object Definitions for Actuated Signal Controllers (ASC) Interface Published May 2019 — original PDF · Official record
Module: NTCIP1202-v03

See published definition above
Module imports
```
{'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:
- NTCIP 1202 v03A, Object Definitions for Actuated Signal Controllers (ASC) Interface Published May 2019 — original PDF

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (5)

OID	Name	Direct children	Descendants	Description
1.3.6.1.4.1.1206.4.2.1.3.23.2.1.2	commPortTypeIndex	0	0
1.3.6.1.4.1.1206.4.2.1.3.23.2.1.3	commPortEnable	0	0
1.3.6.1.4.1.1206.4.2.1.3.23.2.1.4	commPortProtocolsSupported	0	0
1.3.6.1.4.1.1206.4.2.1.3.23.2.1.5	commPortProtocol	0	0
1.3.6.1.4.1.1206.4.2.1.3.23.2.1.6	commPortDiagnostics	0	0