OID reference

ascIOoutputMapDeviceType

1.3.6.1.4.1.1206.4.2.1.13.6.1.2

Description

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.1206.4.2.1.13.6.1 (ascIOoutputMapTableEntry)
Node code: 2
Node name: ascIOoutputMapDeviceType
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.1206.4.2.1.13.6.1.2
URN notation: urn:oid:1.3.6.1.4.1.1206.4.2.1.13.6.1.2

ASN.1, OID-IRI and named path variants

ASN.1 notation

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

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ascIOmapping(13) ascIOoutputMapTable(6) ascIOoutputMapTableEntry(1) ascIOoutputMapDeviceType(2)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) ascIOmapping(13) ascIOoutputMapTable(6) ascIOoutputMapTableEntry(1) ascIOoutputMapDeviceType(2)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ascIOmapping(13) ascIOoutputMapTable(6) ascIOoutputMapTableEntry(1) ascIOoutputMapDeviceType(2)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) ascIOmapping(13) ascIOoutputMapTable(6) ascIOoutputMapTableEntry(1) ascIOoutputMapDeviceType(2)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ascIOmapping(13) ascIOoutputMapTable(6) ascIOoutputMapTableEntry(1) ascIOoutputMapDeviceType(2)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) ascIOmapping(13) ascIOoutputMapTable(6) ascIOoutputMapTableEntry(1) ascIOoutputMapDeviceType(2)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ascIOmapping(13) ascIOoutputMapTable(6) ascIOoutputMapTableEntry(1) ascIOoutputMapDeviceType(2)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) ascIOmapping(13) ascIOoutputMapTable(6) ascIOoutputMapTableEntry(1) ascIOoutputMapDeviceType(2)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ascIOmapping(13) ascIOoutputMapTable(6) ascIOoutputMapTableEntry(1) ascIOoutputMapDeviceType(2)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) ascIOmapping(13) ascIOoutputMapTable(6) ascIOoutputMapTableEntry(1) ascIOoutputMapDeviceType(2)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ascIOmapping(13) ascIOoutputMapTable(6) ascIOoutputMapTableEntry(1) ascIOoutputMapDeviceType(2)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) ascIOmapping(13) ascIOoutputMapTable(6) ascIOoutputMapTableEntry(1) ascIOoutputMapDeviceType(2)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ascIOmapping(13) ascIOoutputMapTable(6) ascIOoutputMapTableEntry(1) ascIOoutputMapDeviceType(2)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) ascIOmapping(13) ascIOoutputMapTable(6) ascIOoutputMapTableEntry(1) ascIOoutputMapDeviceType(2)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ascIOmapping(13) ascIOoutputMapTable(6) ascIOoutputMapTableEntry(1) ascIOoutputMapDeviceType(2)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) ascIOmapping(13) ascIOoutputMapTable(6) ascIOoutputMapTableEntry(1) ascIOoutputMapDeviceType(2)}

OID-IRI notation

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

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/asc/ascIOmapping/ascIOoutputMapTable/ascIOoutputMapTableEntry/ascIOoutputMapDeviceType
/iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/asc/ascIOmapping/ascIOoutputMapTable/ascIOoutputMapTableEntry/ascIOoutputMapDeviceType
/iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/asc/ascIOmapping/ascIOoutputMapTable/ascIOoutputMapTableEntry/ascIOoutputMapDeviceType
/iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/asc/ascIOmapping/ascIOoutputMapTable/ascIOoutputMapTableEntry/ascIOoutputMapDeviceType
/iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/asc/ascIOmapping/ascIOoutputMapTable/ascIOoutputMapTableEntry/ascIOoutputMapDeviceType
/iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/asc/ascIOmapping/ascIOoutputMapTable/ascIOoutputMapTableEntry/ascIOoutputMapDeviceType
/iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/asc/ascIOmapping/ascIOoutputMapTable/ascIOoutputMapTableEntry/ascIOoutputMapDeviceType
/iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/asc/ascIOmapping/ascIOoutputMapTable/ascIOoutputMapTableEntry/ascIOoutputMapDeviceType
/iso/org/dod/internet/private/enterprise/1206/transportation/devices/asc/ascIOmapping/ascIOoutputMapTable/ascIOoutputMapTableEntry/ascIOoutputMapDeviceType
/iso/org/dod/internet/private/enterprise/nema/transportation/devices/asc/ascIOmapping/ascIOoutputMapTable/ascIOoutputMapTableEntry/ascIOoutputMapDeviceType
/iso/org/dod/internet/private/enterprises/1206/transportation/devices/asc/ascIOmapping/ascIOoutputMapTable/ascIOoutputMapTableEntry/ascIOoutputMapDeviceType
/iso/org/dod/internet/private/enterprises/nema/transportation/devices/asc/ascIOmapping/ascIOoutputMapTable/ascIOoutputMapTableEntry/ascIOoutputMapDeviceType
/iso/org/dod/internet/private/ldap-enterprise/1206/transportation/devices/asc/ascIOmapping/ascIOoutputMapTable/ascIOoutputMapTableEntry/ascIOoutputMapDeviceType
/iso/org/dod/internet/private/ldap-enterprise/nema/transportation/devices/asc/ascIOmapping/ascIOoutputMapTable/ascIOoutputMapTableEntry/ascIOoutputMapDeviceType
/iso/org/dod/internet/private/vendor-objects/1206/transportation/devices/asc/ascIOmapping/ascIOoutputMapTable/ascIOoutputMapTableEntry/ascIOoutputMapDeviceType
/iso/org/dod/internet/private/vendor-objects/nema/transportation/devices/asc/ascIOmapping/ascIOoutputMapTable/ascIOoutputMapTableEntry/ascIOoutputMapDeviceType
Additional combinations skipped.

SNMP properties

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

Enumerated values

Value	Name
1	unused
2	custom
3	fio
4	ts1
5	biu
6	siu
7	aux

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.

In NTCIP1202-v03, the row index consists of these components in order:

ascIOmapNumber (INTEGER): one numeric subidentifier for the non-negative value.
ascIOoutputMapIOindex (INTEGER): one numeric subidentifier for the non-negative value.

An instance has the form .1.3.6.1.4.1.1206.4.2.1.13.6.1.2.<ascIOmapNumber>.<ascIOoutputMapIOindex>. Use values 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.13.6.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.

Published definitions

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

Show 2 published definitions

ascIOoutputMapDeviceType · mandatory

ascIOoutputMapDeviceType OBJECT-TYPE
    SYNTAX INTEGER { unused (1),
                      custom (2),
                      fio (3),
                      ts1 (4),
                      biu (5),
                      siu (6),
                      aux (7) }


                                                                                                 

                                                                                      
                                                                                     

    ACCESS read-write
    STATUS mandatory
    DESCRIPTION
        "<Definition> This object is an selects the device type for
        this row of the table.
        A value of unused (1) means that this row of the table is
        unused (all values of ascIOoutputMapIOindex up to
        or ascIOmapMaxOutputs may not be needed by every mapping).
        A custom type is a manufacturer defined device which also
        requires a ascIOoutputMapDevicePNN and a
        ascIOoutputMapDevicePtype to fully specify the device.
        Values > 7 are reserved for future device types.
        <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.13.6.1.2"
::= { ascIOoutputMapTableEntry 2 }

ascIOoutputMapDeviceType · mandatory

ascIOoutputMapDeviceType OBJECT-TYPE
      SYNTAX INTEGER { unused (1),
                        custom (2),
                        fio (3),
                        ts1 (4),
                        biu (5),
                        siu (6),
                        aux (7) }
      ACCESS read-write
      STATUS mandatory
      DESCRIPTION "<Definition> This object is an selects the device type for
            this row of the table.
            A value of unused (1) means that this row of the table is unused
            (all values of ascIOoutputMapIOindex up to or ascIOmapMaxOutputs
            may not be needed by every mapping).
            A custom type is a manufacturer defined device which also
            requires a ascIOoutputMapDevicePNN and a
            ascIOoutputMapDevicePtype to fully specify the device.
            Values > 7 are reserved for future device types.
      <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.13.6.1.2
      <Object Type> P"


                                                                                    

                                                                                      
                                                                                     

::= { ascIOoutputMapTableEntry 2 }

Meaning

Descriptions

2 unique

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

Description 1

<Definition> This object is an selects the device type for this row of the table. A value of unused (1) means that this row of the table is unused (all values of ascIOoutputMapIOindex up to or ascIOmapMaxOutputs may not be needed by every mapping). A custom type is a manufacturer defined device which also requires a ascIOoutputMapDevicePNN and a ascIOoutputMapDevicePtype to fully specify the device. Values > 7 are reserved for future device types. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.13.6.1.2

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

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

Status in source: mandatory.

Names: ascIOoutputMapDeviceType

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "ascIOoutputMapDeviceType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "unused",
    "(",
    "1",
    ")",
    ",",
    "custom",
    "(",
    "2",
    ")",
    ",",
    "fio",
    "(",
    "3",
    ")",
    ",",
    "ts1",
    "(",
    "4",
    ")",
    ",",
    "biu",
    "(",
    "5",
    ")",
    ",",
    "siu",
    "(",
    "6",
    ")",
    ",",
    "aux",
    "(",
    "7",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> This object is an selects the device type for this row of the table. A value of unused (1) means that this row of the table is unused (all values of ascIOoutputMapIOindex up to or ascIOmapMaxOutputs may not be needed by every mapping). A custom type is a manufacturer defined device which also requires a ascIOoutputMapDevicePNN and a ascIOoutputMapDevicePtype to fully specify the device. Values > 7 are reserved for future device types. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.13.6.1.2\"",
    "::=",
    "{",
    "ascIOoutputMapTableEntry",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "unused",
            1
          ],
          [
            "custom",
            2
          ],
          [
            "fio",
            3
          ],
          [
            "ts1",
            4
          ],
          [
            "biu",
            5
          ],
          [
            "siu",
            6
          ],
          [
            "aux",
            7
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> This object is an selects the device type for this row of the table. A value of unused (1) means that this row of the table is unused (all values of ascIOoutputMapIOindex up to or ascIOmapMaxOutputs may not be needed by every mapping). A custom type is a manufacturer defined device which also requires a ascIOoutputMapDevicePNN and a ascIOoutputMapDevicePtype to fully specify the device. Values > 7 are reserved for future device types. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.13.6.1.2"
    ],
    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:
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

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

Status in source: mandatory.

Names: ascIOoutputMapDeviceType

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "ascIOoutputMapDeviceType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "unused",
    "(",
    "1",
    ")",
    ",",
    "custom",
    "(",
    "2",
    ")",
    ",",
    "fio",
    "(",
    "3",
    ")",
    ",",
    "ts1",
    "(",
    "4",
    ")",
    ",",
    "biu",
    "(",
    "5",
    ")",
    ",",
    "siu",
    "(",
    "6",
    ")",
    ",",
    "aux",
    "(",
    "7",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> This object is an selects the device type for this row of the table. A value of unused (1) means that this row of the table is unused (all values of ascIOoutputMapIOindex up to or ascIOmapMaxOutputs may not be needed by every mapping). A custom type is a manufacturer defined device which also requires a ascIOoutputMapDevicePNN and a ascIOoutputMapDevicePtype to fully specify the device. Values > 7 are reserved for future device types. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.13.6.1.2 <Object Type> P\"",
    "::=",
    "{",
    "ascIOoutputMapTableEntry",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "unused",
            1
          ],
          [
            "custom",
            2
          ],
          [
            "fio",
            3
          ],
          [
            "ts1",
            4
          ],
          [
            "biu",
            5
          ],
          [
            "siu",
            6
          ],
          [
            "aux",
            7
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> This object is an selects the device type for this row of the table. A value of unused (1) means that this row of the table is unused (all values of ascIOoutputMapIOindex up to or ascIOmapMaxOutputs may not be needed by every mapping). A custom type is a manufacturer defined device which also requires a ascIOoutputMapDevicePNN and a ascIOoutputMapDevicePtype to fully specify the device. Values > 7 are reserved for future device types. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.13.6.1.2 <Object Type> P"
    ],
    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:
- NTCIP 1202 v03b NTCIP 1202 v02, Object Definitions for Actuated Traffic Signal Controller (ASC) Units – version 03b Published October 2023 — original PDF

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (9)

OID	Name	Direct children	Descendants	Description
1.3.6.1.4.1.1206.4.2.1.13.6.1.1	ascIOoutputMapIOindex	0	0
1.3.6.1.4.1.1206.4.2.1.13.6.1.3	ascIOoutputMapDevicePNN	0	0
1.3.6.1.4.1.1206.4.2.1.13.6.1.4	ascIOoutputMapDevicePtype	0	0
1.3.6.1.4.1.1206.4.2.1.13.6.1.5	ascIOoutputMapDeviceAddr	0	0
1.3.6.1.4.1.1206.4.2.1.13.6.1.6	ascIOoutputMapDevicePin	0	0
1.3.6.1.4.1.1206.4.2.1.13.6.1.7	ascIOoutputMapFuncType	0	0
1.3.6.1.4.1.1206.4.2.1.13.6.1.8	ascIOoutputMapFuncPtype	0	0
1.3.6.1.4.1.1206.4.2.1.13.6.1.9	ascIOoutputMapFunction	0	0
1.3.6.1.4.1.1206.4.2.1.13.6.1.11	ascIOoutputMapFuncIndex	0	0