OID reference

overlapConflictingPedPhases

1.3.6.1.4.1.1206.4.2.1.9.2.1.10

Description

<Definition> Each octet is a Phase (number) that shall be a pedestrian modifier phase for the overlap. The phase number value shall not exceed the maxPhases object value. If the overlap type is 'normal', a non-null value would suppress the overlap when the pedestrian phase is active (in the walk or clearance interval)…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.2.1.9.2.1 (overlapEntry)
Node code
10
Node name
overlapConflictingPedPhases
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.1.9.2.1.10
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.1.9.2.1.10
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) overlap(9) overlapTable(2) overlapEntry(1) overlapConflictingPedPhases(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) overlap(9) overlapTable(2) overlapEntry(1) overlapConflictingPedPhases(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) overlap(9) overlapTable(2) overlapEntry(1) overlapConflictingPedPhases(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) overlap(9) overlapTable(2) overlapEntry(1) overlapConflictingPedPhases(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) overlap(9) overlapTable(2) overlapEntry(1) overlapConflictingPedPhases(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) overlap(9) overlapTable(2) overlapEntry(1) overlapConflictingPedPhases(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) overlap(9) overlapTable(2) overlapEntry(1) overlapConflictingPedPhases(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) overlap(9) overlapTable(2) overlapEntry(1) overlapConflictingPedPhases(10)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) overlap(9) overlapTable(2) overlapEntry(1) overlapConflictingPedPhases(10)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) overlap(9) overlapTable(2) overlapEntry(1) overlapConflictingPedPhases(10)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) overlap(9) overlapTable(2) overlapEntry(1) overlapConflictingPedPhases(10)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) overlap(9) overlapTable(2) overlapEntry(1) overlapConflictingPedPhases(10)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) overlap(9) overlapTable(2) overlapEntry(1) overlapConflictingPedPhases(10)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) overlap(9) overlapTable(2) overlapEntry(1) overlapConflictingPedPhases(10)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) overlap(9) overlapTable(2) overlapEntry(1) overlapConflictingPedPhases(10)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) overlap(9) overlapTable(2) overlapEntry(1) overlapConflictingPedPhases(10)}
OID-IRI notation
  • /1/3/6/1/4/1/1206/4/2/1/9/2/1/10
  • /ISO/Identified-Organization/6/1/4/1/1206/4/2/1/9/2/1/10
  • /ISO/3/6/1/4/1/1206/4/2/1/9/2/1/10
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/asc/overlap/overlapTable/overlapEntry/overlapConflictingPedPhases
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/asc/overlap/overlapTable/overlapEntry/overlapConflictingPedPhases
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/asc/overlap/overlapTable/overlapEntry/overlapConflictingPedPhases
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/asc/overlap/overlapTable/overlapEntry/overlapConflictingPedPhases
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/asc/overlap/overlapTable/overlapEntry/overlapConflictingPedPhases
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/asc/overlap/overlapTable/overlapEntry/overlapConflictingPedPhases
  • /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/asc/overlap/overlapTable/overlapEntry/overlapConflictingPedPhases
  • /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/asc/overlap/overlapTable/overlapEntry/overlapConflictingPedPhases
  • /iso/org/dod/internet/private/enterprise/1206/transportation/devices/asc/overlap/overlapTable/overlapEntry/overlapConflictingPedPhases
  • /iso/org/dod/internet/private/enterprise/nema/transportation/devices/asc/overlap/overlapTable/overlapEntry/overlapConflictingPedPhases
  • /iso/org/dod/internet/private/enterprises/1206/transportation/devices/asc/overlap/overlapTable/overlapEntry/overlapConflictingPedPhases
  • /iso/org/dod/internet/private/enterprises/nema/transportation/devices/asc/overlap/overlapTable/overlapEntry/overlapConflictingPedPhases
  • /iso/org/dod/internet/private/ldap-enterprise/1206/transportation/devices/asc/overlap/overlapTable/overlapEntry/overlapConflictingPedPhases
  • /iso/org/dod/internet/private/ldap-enterprise/nema/transportation/devices/asc/overlap/overlapTable/overlapEntry/overlapConflictingPedPhases
  • /iso/org/dod/internet/private/vendor-objects/1206/transportation/devices/asc/overlap/overlapTable/overlapEntry/overlapConflictingPedPhases
  • /iso/org/dod/internet/private/vendor-objects/nema/transportation/devices/asc/overlap/overlapTable/overlapEntry/overlapConflictingPedPhases
  • Additional combinations skipped.

SNMP properties

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

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 overlapNumber 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.1.9.2.1.10.<overlapNumber>. 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.1.9.2.1.10

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.

Show 2 published definitions

overlapConflictingPedPhases · mandatory

overlapConflictingPedPhases   OBJECT-TYPE
      SYNTAX OCTET STRING
      ACCESS read-write
      STATUS mandatory
      DESCRIPTION "<Definition> Each octet is a Phase (number) that shall be
            a pedestrian modifier phase for the overlap. The phase number
            value shall not exceed the maxPhases object value.
            If the overlap type is 'normal', a non-null value would suppress
            the overlap when the pedestrian phase is active (in the walk or
            clearance interval). Upon completion of the active pedestrian
            phase and upon completion of a clearance interval (MUTCD requires
            3 seconds), the overlap is allowed to proceed to the green state.

            If the overlap type is fYAThreeSection or fYAFourSection, a non-
            null value would maintain the overlap red state when the
            pedestrian phase is active (in the walk or clearance interval).
            Upon completion of the active pedestrian phase and upon
            completion of a clearance interval (MUTCD requires 3 seconds),
            the overlap is allowed to proceed to the flashing yellow state.
      <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.9.2.1.10
      <Object Type> P2"
::= { overlapEntry 10 }

overlapConflictingPedPhases · mandatory

overlapConflictingPedPhases   OBJECT-TYPE
      SYNTAX OCTET STRING
      ACCESS read-write
      STATUS mandatory
      DESCRIPTION "<Definition> Each octet is a Phase (number) that shall be
            a pedestrian modifier phase for the overlap. The phase number
            value shall not exceed the maxPhases object value.
            If the overlap type is 'normal', a non-null value would suppress
            the overlap when the pedestrian phase is active (in the walk or
            clearance interval). Upon completion of the active pedestrian
            phase and upon completion of a clearance interval (MUTCD requires
            3 seconds), the overlap is allowed to proceed to the green state.

            If the overlap type is fYAThreeSection or fYAFourSection, a non-
            null value would maintain the overlap red state when the
            pedestrian phase is active (in the walk or clearance interval).
            Upon completion of the active pedestrian phase and upon
            completion of a clearance interval (MUTCD requires 3 seconds),
            the overlap is allowed to proceed to the flashing yellow state.
      <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.9.2.1.10"
::= { overlapEntry 10 }

Meaning

Descriptions

2 unique

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

Description 1

<Definition> Each octet is a Phase (number) that shall be a pedestrian modifier phase for the overlap. The phase number value shall not exceed the maxPhases object value. If the overlap type is 'normal', a non-null value would suppress the overlap when the pedestrian phase is active (in the walk or clearance interval). Upon completion of the active pedestrian phase and upon completion of a clearance interval (MUTCD requires 3 seconds), the overlap is allowed to proceed to the green state. If the overlap type is fYAThreeSection or fYAFourSection, a non- null value would maintain the overlap red state when the pedestrian phase is active (in the walk or clearance interval). Upon completion of the active pedestrian phase and upon completion of a clearance interval (MUTCD requires 3 seconds), the overlap is allowed to proceed to the flashing yellow state. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.9.2.1.10 <Object Type> P2

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 2

<Definition> Each octet is a Phase (number) that shall be a pedestrian modifier phase for the overlap. The phase number value shall not exceed the maxPhases object value. If the overlap type is 'normal', a non-null value would suppress the overlap when the pedestrian phase is active (in the walk or clearance interval). Upon completion of the active pedestrian phase and upon completion of a clearance interval (MUTCD requires 3 seconds), the overlap is allowed to proceed to the green state. If the overlap type is fYAThreeSection or fYAFourSection, a non- null value would maintain the overlap red state when the pedestrian phase is active (in the walk or clearance interval). Upon completion of the active pedestrian phase and upon completion of a clearance interval (MUTCD requires 3 seconds), the overlap is allowed to proceed to the flashing yellow state. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.9.2.1.10

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

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

Status in source: mandatory.

Names: overlapConflictingPedPhases

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "overlapConflictingPedPhases",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> Each octet is a Phase (number) that shall be a pedestrian modifier phase for the overlap. The phase number value shall not exceed the maxPhases object value. If the overlap type is 'normal', a non-null value would suppress the overlap when the pedestrian phase is active (in the walk or clearance interval). Upon completion of the active pedestrian phase and upon completion of a clearance interval (MUTCD requires 3 seconds), the overlap is allowed to proceed to the green state. If the overlap type is fYAThreeSection or fYAFourSection, a non- null value would maintain the overlap red state when the pedestrian phase is active (in the walk or clearance interval). Upon completion of the active pedestrian phase and upon completion of a clearance interval (MUTCD requires 3 seconds), the overlap is allowed to proceed to the flashing yellow state. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.9.2.1.10 <Object Type> P2\"",
    "::=",
    "{",
    "overlapEntry",
    "10",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> Each octet is a Phase (number) that shall be a pedestrian modifier phase for the overlap. The phase number value shall not exceed the maxPhases object value. If the overlap type is 'normal', a non-null value would suppress the overlap when the pedestrian phase is active (in the walk or clearance interval). Upon completion of the active pedestrian phase and upon completion of a clearance interval (MUTCD requires 3 seconds), the overlap is allowed to proceed to the green state. If the overlap type is fYAThreeSection or fYAFourSection, a non- null value would maintain the overlap red state when the pedestrian phase is active (in the walk or clearance interval). Upon completion of the active pedestrian phase and upon completion of a clearance interval (MUTCD requires 3 seconds), the overlap is allowed to proceed to the flashing yellow state. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.9.2.1.10 <Object Type> P2"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 2

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

Status in source: mandatory.

Names: overlapConflictingPedPhases

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "overlapConflictingPedPhases",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> Each octet is a Phase (number) that shall be a pedestrian modifier phase for the overlap. The phase number value shall not exceed the maxPhases object value. If the overlap type is 'normal', a non-null value would suppress the overlap when the pedestrian phase is active (in the walk or clearance interval). Upon completion of the active pedestrian phase and upon completion of a clearance interval (MUTCD requires 3 seconds), the overlap is allowed to proceed to the green state. If the overlap type is fYAThreeSection or fYAFourSection, a non- null value would maintain the overlap red state when the pedestrian phase is active (in the walk or clearance interval). Upon completion of the active pedestrian phase and upon completion of a clearance interval (MUTCD requires 3 seconds), the overlap is allowed to proceed to the flashing yellow state. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.9.2.1.10\"",
    "::=",
    "{",
    "overlapEntry",
    "10",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> Each octet is a Phase (number) that shall be a pedestrian modifier phase for the overlap. The phase number value shall not exceed the maxPhases object value. If the overlap type is 'normal', a non-null value would suppress the overlap when the pedestrian phase is active (in the walk or clearance interval). Upon completion of the active pedestrian phase and upon completion of a clearance interval (MUTCD requires 3 seconds), the overlap is allowed to proceed to the green state. If the overlap type is fYAThreeSection or fYAFourSection, a non- null value would maintain the overlap red state when the pedestrian phase is active (in the walk or clearance interval). Upon completion of the active pedestrian phase and upon completion of a clearance interval (MUTCD requires 3 seconds), the overlap is allowed to proceed to the flashing yellow state. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.9.2.1.10"
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (9)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.1.9.2.1.1 overlapNumber00
1.3.6.1.4.1.1206.4.2.1.9.2.1.2 overlapType00
1.3.6.1.4.1.1206.4.2.1.9.2.1.3 overlapIncludedPhases00
1.3.6.1.4.1.1206.4.2.1.9.2.1.4 overlapModifierPhases00
1.3.6.1.4.1.1206.4.2.1.9.2.1.5 overlapTrailGreen00
1.3.6.1.4.1.1206.4.2.1.9.2.1.6 overlapTrailYellow00
1.3.6.1.4.1.1206.4.2.1.9.2.1.7 overlapTrailRed00
1.3.6.1.4.1.1206.4.2.1.9.2.1.8 overlapWalk00
1.3.6.1.4.1.1206.4.2.1.9.2.1.9 overlapPedClearance00