OID reference

commandTransProtocol

1.3.6.1.4.1.1206.4.2.10.3.2.1.6

Description

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.1206.4.2.10.3.2.1 (commandEntry)
Node code: 6
Node name: commandTransProtocol
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.1206.4.2.10.3.2.1.6
URN notation: urn:oid:1.3.6.1.4.1.1206.4.2.10.3.2.1.6

ASN.1, OID-IRI and named path variants

ASN.1 notation

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

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) ssm(10) commandSetup(3) commandTable(2) commandEntry(1) commandTransProtocol(6)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) ssm(10) commandSetup(3) commandTable(2) commandEntry(1) commandTransProtocol(6)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) ssm(10) commandSetup(3) commandTable(2) commandEntry(1) commandTransProtocol(6)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) ssm(10) commandSetup(3) commandTable(2) commandEntry(1) commandTransProtocol(6)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) ssm(10) commandSetup(3) commandTable(2) commandEntry(1) commandTransProtocol(6)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) ssm(10) commandSetup(3) commandTable(2) commandEntry(1) commandTransProtocol(6)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) ssm(10) commandSetup(3) commandTable(2) commandEntry(1) commandTransProtocol(6)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) ssm(10) commandSetup(3) commandTable(2) commandEntry(1) commandTransProtocol(6)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) ssm(10) commandSetup(3) commandTable(2) commandEntry(1) commandTransProtocol(6)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) ssm(10) commandSetup(3) commandTable(2) commandEntry(1) commandTransProtocol(6)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) ssm(10) commandSetup(3) commandTable(2) commandEntry(1) commandTransProtocol(6)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) ssm(10) commandSetup(3) commandTable(2) commandEntry(1) commandTransProtocol(6)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) ssm(10) commandSetup(3) commandTable(2) commandEntry(1) commandTransProtocol(6)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) ssm(10) commandSetup(3) commandTable(2) commandEntry(1) commandTransProtocol(6)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) ssm(10) commandSetup(3) commandTable(2) commandEntry(1) commandTransProtocol(6)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) ssm(10) commandSetup(3) commandTable(2) commandEntry(1) commandTransProtocol(6)}

OID-IRI notation

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

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/ssm/commandSetup/commandTable/commandEntry/commandTransProtocol
/iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/ssm/commandSetup/commandTable/commandEntry/commandTransProtocol
/iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/ssm/commandSetup/commandTable/commandEntry/commandTransProtocol
/iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/ssm/commandSetup/commandTable/commandEntry/commandTransProtocol
/iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/ssm/commandSetup/commandTable/commandEntry/commandTransProtocol
/iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/ssm/commandSetup/commandTable/commandEntry/commandTransProtocol
/iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/ssm/commandSetup/commandTable/commandEntry/commandTransProtocol
/iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/ssm/commandSetup/commandTable/commandEntry/commandTransProtocol
/iso/org/dod/internet/private/enterprise/1206/transportation/devices/ssm/commandSetup/commandTable/commandEntry/commandTransProtocol
/iso/org/dod/internet/private/enterprise/nema/transportation/devices/ssm/commandSetup/commandTable/commandEntry/commandTransProtocol
/iso/org/dod/internet/private/enterprises/1206/transportation/devices/ssm/commandSetup/commandTable/commandEntry/commandTransProtocol
/iso/org/dod/internet/private/enterprises/nema/transportation/devices/ssm/commandSetup/commandTable/commandEntry/commandTransProtocol
/iso/org/dod/internet/private/ldap-enterprise/1206/transportation/devices/ssm/commandSetup/commandTable/commandEntry/commandTransProtocol
/iso/org/dod/internet/private/ldap-enterprise/nema/transportation/devices/ssm/commandSetup/commandTable/commandEntry/commandTransProtocol
/iso/org/dod/internet/private/vendor-objects/1206/transportation/devices/ssm/commandSetup/commandTable/commandEntry/commandTransProtocol
/iso/org/dod/internet/private/vendor-objects/nema/transportation/devices/ssm/commandSetup/commandTable/commandEntry/commandTransProtocol
Additional combinations skipped.

SNMP properties

Value type: INTEGER
Maximum access defined by MIB: read-write
Status in MIB: mandatory
Default value: t2-NPN

Enumerated values

Value	Name
1	t2-NPN
2	udpIp

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 NTCIP1210v01-51, the row index consists of these components in order:

sectionNumber (INTEGER): one numeric subidentifier for the non-negative value.
commandMsgNumber (INTEGER): one numeric subidentifier for the non-negative value.

An instance has the form .1.3.6.1.4.1.1206.4.2.10.3.2.1.6.<sectionNumber>.<commandMsgNumber>. 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.10.3.2.1.6

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 definition

The displayed source records contain one distinct definition. Compare its source records.

commandTransProtocol         OBJECT-TYPE
         SYNTAX        INTEGER { t2-NPN (1),
                       udpIp (2) }
         ACCESS        read-write
         STATUS        mandatory
         DESCRIPTION "
                <Definition> This object determines what transport profile
                is used to exchange the command.
                t2-NPN       NTCIP 2201 Encapsulation Method 1 is used. Port
                             Numbers are not used.
                udpIp        indicates the UDP/IP protocols as defined in
                             NTCIP 2202 –Internet (TCP/IP and UDP/IP) Transport
                             Profile is used.

                 This object does not mandate support of any specific transport
                 profile.

                 For the predefined messages (commandMsgNumber = 1 - 6), the
                 DEFVAL shall be as follows:
                  commandMsgNumber.1 = t2-NPN (global time control)
                  commandMsgNumber.2 = t2-NPN (sync control)
                  commandMsgNumber.3 = t2-NPN (pattern control)
                  commandMsgNumber.4 = t2-NPN (special function control)
                  commandMsgNumber.5 = t2-NPN (SSL Status)
                  commandMsgNumber.6 = t2-NPN (Det Vol & Occ)

            <Object Identifier> 1.3.6.1.4.1.1206.4.2.10.3.2.1.6"
      DEFVAL { t2-NPN }
::= { commandEntry 6 }

Meaning

Descriptions

1 unique

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

<Definition> This object determines what transport profile is used to exchange the command. t2-NPN NTCIP 2201 Encapsulation Method 1 is used. Port Numbers are not used. udpIp indicates the UDP/IP protocols as defined in NTCIP 2202 –Internet (TCP/IP and UDP/IP) Transport Profile is used. This object does not mandate support of any specific transport profile. For the predefined messages (commandMsgNumber = 1 - 6), the DEFVAL shall be as follows: commandMsgNumber.1 = t2-NPN (global time control) commandMsgNumber.2 = t2-NPN (sync control) commandMsgNumber.3 = t2-NPN (pattern control) commandMsgNumber.4 = t2-NPN (special function control) commandMsgNumber.5 = t2-NPN (SSL Status) commandMsgNumber.6 = t2-NPN (Det Vol & Occ) <Object Identifier> 1.3.6.1.4.1.1206.4.2.10.3.2.1.6

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Evidence

Source records

1 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

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

Status in source: mandatory.

Names: commandTransProtocol

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "commandTransProtocol",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "t2-NPN",
    "(",
    "1",
    ")",
    ",",
    "udpIp",
    "(",
    "2",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\" <Definition> This object determines what transport profile is used to exchange the command. t2-NPN NTCIP 2201 Encapsulation Method 1 is used. Port Numbers are not used. udpIp indicates the UDP/IP protocols as defined in NTCIP 2202 –Internet (TCP/IP and UDP/IP) Transport Profile is used. This object does not mandate support of any specific transport profile. For the predefined messages (commandMsgNumber = 1 - 6), the DEFVAL shall be as follows: commandMsgNumber.1 = t2-NPN (global time control) commandMsgNumber.2 = t2-NPN (sync control) commandMsgNumber.3 = t2-NPN (pattern control) commandMsgNumber.4 = t2-NPN (special function control) commandMsgNumber.5 = t2-NPN (SSL Status) commandMsgNumber.6 = t2-NPN (Det Vol & Occ) <Object Identifier> 1.3.6.1.4.1.1206.4.2.10.3.2.1.6\"",
    "DEFVAL",
    "{",
    "t2-NPN",
    "}",
    "::=",
    "{",
    "commandEntry",
    "6",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "t2-NPN",
            1
          ],
          [
            "udpIp",
            2
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> This object determines what transport profile is used to exchange the command. t2-NPN NTCIP 2201 Encapsulation Method 1 is used. Port Numbers are not used. udpIp indicates the UDP/IP protocols as defined in NTCIP 2202 –Internet (TCP/IP and UDP/IP) Transport Profile is used. This object does not mandate support of any specific transport profile. For the predefined messages (commandMsgNumber = 1 - 6), the DEFVAL shall be as follows: commandMsgNumber.1 = t2-NPN (global time control) commandMsgNumber.2 = t2-NPN (sync control) commandMsgNumber.3 = t2-NPN (pattern control) commandMsgNumber.4 = t2-NPN (special function control) commandMsgNumber.5 = t2-NPN (SSL Status) commandMsgNumber.6 = t2-NPN (Det Vol & Occ) <Object Identifier> 1.3.6.1.4.1.1206.4.2.10.3.2.1.6"
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "t2-NPN"
    ]
  ]
}

NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1210 v01, Field Master Stations (FMS)—Part 1: Object Definitions for Signal System Masters (SSM) Published September 2013 — original PDF · Official record
Module: NTCIP1210v01-51

See published definition above
Module imports
```
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'null', 'Counter'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004v0217-SMI': ['OwnerString', 'BITMAP8', 'BITMAP16', 'ssm'], 'NTCIP1103v0217-STMP': ['ConfigEntryStatus']}
```
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: A typographic opening DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP8004v0217-SMI. 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 NTCIP1210v0155r.pdf — NTCIP1210v01-51 (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

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.10.3.2.1.1	commandMsgNumber	0	0
1.3.6.1.4.1.1206.4.2.10.3.2.1.2	commandIntersection	0	0
1.3.6.1.4.1.1206.4.2.10.3.2.1.3	commandMsgDefNumber	0	0
1.3.6.1.4.1.1206.4.2.10.3.2.1.4	commandFrequency	0	0
1.3.6.1.4.1.1206.4.2.10.3.2.1.5	commandOpCode	0	0