OID reference

dynObj2

1.3.6.1.4.1.1206.4.1.3.2.2

Description

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.1206.4.1.3.2 (dynObjData)
Node code: 2
Node name: dynObj2
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.1206.4.1.3.2.2
URN notation: urn:oid:1.3.6.1.4.1.1206.4.1.3.2.2

ASN.1, OID-IRI and named path variants

ASN.1 notation

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

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) protocols(1) dynObjMgmt(3) dynObjData(2) dynObj2(2)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) protocols(1) dynObjMgmt(3) dynObjData(2) dynObj2(2)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) protocols(1) dynObjMgmt(3) dynObjData(2) dynObj2(2)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) protocols(1) dynObjMgmt(3) dynObjData(2) dynObj2(2)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) protocols(1) dynObjMgmt(3) dynObjData(2) dynObj2(2)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) protocols(1) dynObjMgmt(3) dynObjData(2) dynObj2(2)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) protocols(1) dynObjMgmt(3) dynObjData(2) dynObj2(2)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) protocols(1) dynObjMgmt(3) dynObjData(2) dynObj2(2)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) protocols(1) dynObjMgmt(3) dynObjData(2) dynObj2(2)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) protocols(1) dynObjMgmt(3) dynObjData(2) dynObj2(2)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) protocols(1) dynObjMgmt(3) dynObjData(2) dynObj2(2)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) protocols(1) dynObjMgmt(3) dynObjData(2) dynObj2(2)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) protocols(1) dynObjMgmt(3) dynObjData(2) dynObj2(2)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) protocols(1) dynObjMgmt(3) dynObjData(2) dynObj2(2)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) protocols(1) dynObjMgmt(3) dynObjData(2) dynObj2(2)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) protocols(1) dynObjMgmt(3) dynObjData(2) dynObj2(2)}

OID-IRI notation

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

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/1206/transportation/protocols/dynObjMgmt/dynObjData/dynObj2
/iso/identified-organization/dod/internet/private/enterprise/1206/transportation/Protocols/dynObjMgmt/dynObjData/dynObj2
/iso/identified-organization/dod/internet/private/enterprise/nema/transportation/protocols/dynObjMgmt/dynObjData/dynObj2
/iso/identified-organization/dod/internet/private/enterprise/nema/transportation/Protocols/dynObjMgmt/dynObjData/dynObj2
/iso/identified-organization/dod/internet/private/enterprises/1206/transportation/protocols/dynObjMgmt/dynObjData/dynObj2
/iso/identified-organization/dod/internet/private/enterprises/1206/transportation/Protocols/dynObjMgmt/dynObjData/dynObj2
/iso/identified-organization/dod/internet/private/enterprises/nema/transportation/protocols/dynObjMgmt/dynObjData/dynObj2
/iso/identified-organization/dod/internet/private/enterprises/nema/transportation/Protocols/dynObjMgmt/dynObjData/dynObj2
/iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/protocols/dynObjMgmt/dynObjData/dynObj2
/iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/Protocols/dynObjMgmt/dynObjData/dynObj2
/iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/protocols/dynObjMgmt/dynObjData/dynObj2
/iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/Protocols/dynObjMgmt/dynObjData/dynObj2
/iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/protocols/dynObjMgmt/dynObjData/dynObj2
/iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/Protocols/dynObjMgmt/dynObjData/dynObj2
/iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/protocols/dynObjMgmt/dynObjData/dynObj2
/iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/Protocols/dynObjMgmt/dynObjData/dynObj2
Additional combinations skipped.

SNMP properties

Value type: OCTET STRING
Maximum access defined by MIB: read-write
Status in MIB: deprecated

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.1206.4.1.3.2.2.0

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 3 distinct definitions; some records may not include a definition.

Show 3 published definitions

dynObj2 · deprecated

dynObj2  OBJECT-TYPE
  SYNTAX      OCTET STRING
  MAX-ACCESS  read-write
  STATUS      deprecated
  DESCRIPTION
    "<Definition> The value of this object is determined by the dynObjDef 
     entries with dynObjNumber equal to 2. Packed Encoding Rules are utilized 
     to encode the objects for transmission. This object is intended for use 
     with the Simple Transportation Management Protocol, and provides little 
     advantage if used with SNMP. If no objects are defined for this dynamic 
     object number, then an error of noSuchName shall be returned by the 
     agent
    <Informative> This object has been deprecated along with STMP.
    <Object Identifier> 1.3.6.1.4.1.1206.4.1.3.2.2"
  ::= { dynObjData 2 }

dynObj2 · deprecated

dynObj2 OBJECT-TYPE
     SYNTAX OCTET STRING
     ACCESS read-write
     STATUS deprecated
     DESCRIPTION
         “The value of this object is determined by the dynObjDef entries with
         dynObjNumber equal to 2. Packed Encoding Rules are utilized to encode
         the objects for transmission. This object is intended for use with the Simple
         Transportation Management Protocol, and provides little advantage if used
         with SNMP.
         If no objects are defined for this dynamic object number, then an error of
         noSuchName shall be returned by the agent.”
::= { dynObjData 2 }

dynObj2 · deprecated

dynObj2 OBJECT-TYPE
SYNTAX      OCTET STRING
MAX-ACCESS read-write
STATUS      deprecated
DESCRIPTION
   "<Definition> The value of this object is determined by the dynObjDef
   entries with dynObjNumber equal to 2. Packed Encoding Rules are utilized to
   encode the objects for transmission. This object is intended for use with
   the Simple Transportation Management Protocol, and provides little
   advantage if used with SNMP. If no objects are defined for this dynamic
   object number, then an error of noSuchName shall be returned by the agent
  <Supplanted by> ISO26048-1-DynObj.fdDynObjCurrentValue and fdDynObjNewValue
  <Informative> This object has been deprecated along with STMP.
  <Object Identifier> 1.3.6.1.4.1.1206.4.1.3.2.2"
::= { dynObjData 2 }

Meaning

Descriptions

3 unique

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

Description 1

<Definition> The value of this object is determined by the dynObjDef entries with dynObjNumber equal to 2. Packed Encoding Rules are utilized to encode the objects for transmission. This object is intended for use with the Simple Transportation Management Protocol, and provides little advantage if used with SNMP. If no objects are defined for this dynamic object number, then an error of noSuchName shall be returned by the agent <Informative> This object has been deprecated along with STMP. <Object Identifier> 1.3.6.1.4.1.1206.4.1.3.2.2

Sources for this description

ITE public NTCIP working repository MIBs

See 1 matching source record

Description 2

The value of this object is determined by the dynObjDef entries with dynObjNumber equal to 2. Packed Encoding Rules are utilized to encode the objects for transmission. This object is intended for use with the Simple Transportation Management Protocol, and provides little advantage if used with SNMP. If no objects are defined for this dynamic object number, then an error of noSuchName shall be returned by the agent.

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 3

<Definition> The value of this object is determined by the dynObjDef entries with dynObjNumber equal to 2. Packed Encoding Rules are utilized to encode the objects for transmission. This object is intended for use with the Simple Transportation Management Protocol, and provides little advantage if used with SNMP. If no objects are defined for this dynamic object number, then an error of noSuchName shall be returned by the agent <Supplanted by> ISO26048-1-DynObj.fdDynObjCurrentValue and fdDynObjNewValue <Informative> This object has been deprecated along with STMP. <Object Identifier> 1.3.6.1.4.1.1206.4.1.3.2.2

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Evidence

Source records

3 records

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

Records for description 1ITE public NTCIP working repository MIBs1 record · 1 source

Description 1

dynObj2 · deprecatedITE public NTCIP working repository MIBs1 source

Status in source: deprecated.

Names: dynObj2

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dynObj2",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition> The value of this object is determined by the dynObjDef entries with dynObjNumber equal to 2. Packed Encoding Rules are utilized to encode the objects for transmission. This object is intended for use with the Simple Transportation Management Protocol, and provides little advantage if used with SNMP. If no objects are defined for this dynamic object number, then an error of noSuchName shall be returned by the agent <Informative> This object has been deprecated along with STMP. <Object Identifier> 1.3.6.1.4.1.1206.4.1.3.2.2\"",
    "::=",
    "{",
    "dynObjData",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition> The value of this object is determined by the dynObjDef entries with dynObjNumber equal to 2. Packed Encoding Rules are utilized to encode the objects for transmission. This object is intended for use with the Simple Transportation Management Protocol, and provides little advantage if used with SNMP. If no objects are defined for this dynamic object number, then an error of noSuchName shall be returned by the agent <Informative> This object has been deprecated along with STMP. <Object Identifier> 1.3.6.1.4.1.1206.4.1.3.2.2"
    ],
    null,
    null,
    null,
    null
  ]
}

ITE public NTCIP working repository MIBs · Publisher's source file: NTCIP-1201 — ntcip1201-AuxIO.mib
Module: NTCIP1201-DynObjMgmt

See published definition above
Module imports
```
{'SNMPv2-TC': ['TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'zeroDotZero'], 'SNMPv2-CONF': ['OBJECT-GROUP'], 'NTCIP8004-Transportation': ['protocols', 'NtcipOwnerString']}
```
Source data warning: This original is published in an ITE NTCIP working repository. Repository publication does not establish that this particular revision is an adopted standard. Consult its native revision history and the NTCIP published standards catalog before implementation. Copyright and distribution notices are retained in the downloadable original.
· Download NTCIP-1201 — ntcip1201-AuxIO.mib
Same file in ntcip1201-SNMPConfig.mib.
Same file in ntcip1201-Security.mib.
Same file in ntcip1201-ProfilesSTMP.mib.
Same file in ntcip1201-NtcipTraps.mib.

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

Description 2

dynObj2 · deprecatedNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: deprecated.

Names: dynObj2

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dynObj2",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "ACCESS",
    "read-write",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "“",
    "The",
    "value",
    "of",
    "this",
    "object",
    "is",
    "determined",
    "by",
    "the",
    "dynObjDef",
    "entries",
    "with",
    "dynObjNumber",
    "equal",
    "to",
    "2",
    ".",
    "Packed",
    "Encoding",
    "Rules",
    "are",
    "utilized",
    "to",
    "encode",
    "the",
    "objects",
    "for",
    "transmission",
    ".",
    "This",
    "object",
    "is",
    "intended",
    "for",
    "use",
    "with",
    "the",
    "Simple",
    "Transportation",
    "Management",
    "Protocol",
    ",",
    "and",
    "provides",
    "little",
    "advantage",
    "if",
    "used",
    "with",
    "SNMP",
    ".",
    "If",
    "no",
    "objects",
    "are",
    "defined",
    "for",
    "this",
    "dynamic",
    "object",
    "number",
    ",",
    "then",
    "an",
    "error",
    "of",
    "noSuchName",
    "shall",
    "be",
    "returned",
    "by",
    "the",
    "agent",
    ".",
    "”",
    "::=",
    "{",
    "dynObjData",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "The value of this object is determined by the dynObjDef entries with dynObjNumber equal to 2. Packed Encoding Rules are utilized to encode the objects for transmission. This object is intended for use with the Simple Transportation Management Protocol, and provides little advantage if used with SNMP. If no objects are defined for this dynamic object number, then an error of noSuchName shall be returned by the agent."
    ],
    null,
    null,
    null,
    null
  ]
}

NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1101:1996, Simple Transportation Management Framework Published December 2001 (Rescinded) — original PDF · Official record
Module: TMIB-II

See published definition above

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 closing 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: 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: missing or unreadable imports of transportation. 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 NTCIP1101Rescinded-2006.pdf — TMIB-II (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 3NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 3

dynObj2 · deprecatedNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: deprecated.

Names: dynObj2

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dynObj2",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition> The value of this object is determined by the dynObjDef entries with dynObjNumber equal to 2. Packed Encoding Rules are utilized to encode the objects for transmission. This object is intended for use with the Simple Transportation Management Protocol, and provides little advantage if used with SNMP. If no objects are defined for this dynamic object number, then an error of noSuchName shall be returned by the agent <Supplanted by> ISO26048-1-DynObj.fdDynObjCurrentValue and fdDynObjNewValue <Informative> This object has been deprecated along with STMP. <Object Identifier> 1.3.6.1.4.1.1206.4.1.3.2.2\"",
    "::=",
    "{",
    "dynObjData",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition> The value of this object is determined by the dynObjDef entries with dynObjNumber equal to 2. Packed Encoding Rules are utilized to encode the objects for transmission. This object is intended for use with the Simple Transportation Management Protocol, and provides little advantage if used with SNMP. If no objects are defined for this dynamic object number, then an error of noSuchName shall be returned by the agent <Supplanted by> ISO26048-1-DynObj.fdDynObjCurrentValue and fdDynObjNewValue <Informative> This object has been deprecated along with STMP. <Object Identifier> 1.3.6.1.4.1.1206.4.1.3.2.2"
    ],
    null,
    null,
    null,
    null
  ]
}

NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1201 v4.0.0 — ITE published 2025 edition — original PDF · Official record
Module: NTCIP1201-DynObjMgmt

See published definition above
Module imports
```
{'SNMPv2-TC': ['TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'zeroDotZero'], 'NTCIP8004-Transportation': ['protocols', 'NtcipOwnerString']}
```
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.
· Download 1201v4-0-0.pdf — NTCIP1201-DynObjMgmt (MIB transcription)
Related source files and packages:
- NTCIP 1201 v4.0.0 — ITE published 2025 edition — original PDF

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (12)

OID	Name	Direct children	Descendants	Description
1.3.6.1.4.1.1206.4.1.3.2.1	dynObj1	0	0
1.3.6.1.4.1.1206.4.1.3.2.3	dynObj3	0	0
1.3.6.1.4.1.1206.4.1.3.2.4	dynObj4	0	0
1.3.6.1.4.1.1206.4.1.3.2.5	dynObj5	0	0
1.3.6.1.4.1.1206.4.1.3.2.6	dynObj6	0	0
1.3.6.1.4.1.1206.4.1.3.2.7	dynObj7	0	0
1.3.6.1.4.1.1206.4.1.3.2.8	dynObj8	0	0
1.3.6.1.4.1.1206.4.1.3.2.9	dynObj9	0	0
1.3.6.1.4.1.1206.4.1.3.2.10	dynObj10	0	0
1.3.6.1.4.1.1206.4.1.3.2.11	dynObj11	0	0
1.3.6.1.4.1.1206.4.1.3.2.12	dynObj12	0	0
1.3.6.1.4.1.1206.4.1.3.2.13	dynObj13	0	0