OID reference

sensorZoneLoopLayout

1.3.6.1.4.1.1206.4.2.4.4.1.1.4

Description

<Definition> The zone configuration provides for standardized sensor loop layouts typically used in roadway applications. other(1) - Used for special loop configurations and layouts. oneSixBySixLoopOneLane(2) - Used when there in one six-foot by six- foot loop in one travel lane. twoSixBySixLoopsOneLane(3) - Used when…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.2.4.4.1.1 (loopSensorSetupEntry)
Node code
4
Node name
sensorZoneLoopLayout
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.4.4.1.1.4
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.4.4.1.1.4
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) tss(4) tssInductiveLoop(4) loopSensorSetupTable(1) loopSensorSetupEntry(1) sensorZoneLoopLayout(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) tss(4) tssInductiveLoop(4) loopSensorSetupTable(1) loopSensorSetupEntry(1) sensorZoneLoopLayout(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) tss(4) tssInductiveLoop(4) loopSensorSetupTable(1) loopSensorSetupEntry(1) sensorZoneLoopLayout(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) tss(4) tssInductiveLoop(4) loopSensorSetupTable(1) loopSensorSetupEntry(1) sensorZoneLoopLayout(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) tss(4) tssInductiveLoop(4) loopSensorSetupTable(1) loopSensorSetupEntry(1) sensorZoneLoopLayout(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) tss(4) tssInductiveLoop(4) loopSensorSetupTable(1) loopSensorSetupEntry(1) sensorZoneLoopLayout(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) tss(4) tssInductiveLoop(4) loopSensorSetupTable(1) loopSensorSetupEntry(1) sensorZoneLoopLayout(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) tss(4) tssInductiveLoop(4) loopSensorSetupTable(1) loopSensorSetupEntry(1) sensorZoneLoopLayout(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) tss(4) tssInductiveLoop(4) loopSensorSetupTable(1) loopSensorSetupEntry(1) sensorZoneLoopLayout(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) tss(4) tssInductiveLoop(4) loopSensorSetupTable(1) loopSensorSetupEntry(1) sensorZoneLoopLayout(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) tss(4) tssInductiveLoop(4) loopSensorSetupTable(1) loopSensorSetupEntry(1) sensorZoneLoopLayout(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) tss(4) tssInductiveLoop(4) loopSensorSetupTable(1) loopSensorSetupEntry(1) sensorZoneLoopLayout(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) tss(4) tssInductiveLoop(4) loopSensorSetupTable(1) loopSensorSetupEntry(1) sensorZoneLoopLayout(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) tss(4) tssInductiveLoop(4) loopSensorSetupTable(1) loopSensorSetupEntry(1) sensorZoneLoopLayout(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) tss(4) tssInductiveLoop(4) loopSensorSetupTable(1) loopSensorSetupEntry(1) sensorZoneLoopLayout(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) tss(4) tssInductiveLoop(4) loopSensorSetupTable(1) loopSensorSetupEntry(1) sensorZoneLoopLayout(4)}
OID-IRI notation
  • /1/3/6/1/4/1/1206/4/2/4/4/1/1/4
  • /ISO/Identified-Organization/6/1/4/1/1206/4/2/4/4/1/1/4
  • /ISO/3/6/1/4/1/1206/4/2/4/4/1/1/4
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/tss/tssInductiveLoop/loopSensorSetupTable/loopSensorSetupEntry/sensorZoneLoopLayout
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/tss/tssInductiveLoop/loopSensorSetupTable/loopSensorSetupEntry/sensorZoneLoopLayout
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/tss/tssInductiveLoop/loopSensorSetupTable/loopSensorSetupEntry/sensorZoneLoopLayout
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/tss/tssInductiveLoop/loopSensorSetupTable/loopSensorSetupEntry/sensorZoneLoopLayout
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/tss/tssInductiveLoop/loopSensorSetupTable/loopSensorSetupEntry/sensorZoneLoopLayout
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/tss/tssInductiveLoop/loopSensorSetupTable/loopSensorSetupEntry/sensorZoneLoopLayout
  • /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/tss/tssInductiveLoop/loopSensorSetupTable/loopSensorSetupEntry/sensorZoneLoopLayout
  • /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/tss/tssInductiveLoop/loopSensorSetupTable/loopSensorSetupEntry/sensorZoneLoopLayout
  • /iso/org/dod/internet/private/enterprise/1206/transportation/devices/tss/tssInductiveLoop/loopSensorSetupTable/loopSensorSetupEntry/sensorZoneLoopLayout
  • /iso/org/dod/internet/private/enterprise/nema/transportation/devices/tss/tssInductiveLoop/loopSensorSetupTable/loopSensorSetupEntry/sensorZoneLoopLayout
  • /iso/org/dod/internet/private/enterprises/1206/transportation/devices/tss/tssInductiveLoop/loopSensorSetupTable/loopSensorSetupEntry/sensorZoneLoopLayout
  • /iso/org/dod/internet/private/enterprises/nema/transportation/devices/tss/tssInductiveLoop/loopSensorSetupTable/loopSensorSetupEntry/sensorZoneLoopLayout
  • /iso/org/dod/internet/private/ldap-enterprise/1206/transportation/devices/tss/tssInductiveLoop/loopSensorSetupTable/loopSensorSetupEntry/sensorZoneLoopLayout
  • /iso/org/dod/internet/private/ldap-enterprise/nema/transportation/devices/tss/tssInductiveLoop/loopSensorSetupTable/loopSensorSetupEntry/sensorZoneLoopLayout
  • /iso/org/dod/internet/private/vendor-objects/1206/transportation/devices/tss/tssInductiveLoop/loopSensorSetupTable/loopSensorSetupEntry/sensorZoneLoopLayout
  • /iso/org/dod/internet/private/vendor-objects/nema/transportation/devices/tss/tssInductiveLoop/loopSensorSetupTable/loopSensorSetupEntry/sensorZoneLoopLayout
  • Additional combinations skipped.

SNMP properties

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

Enumerated values

ValueName
1other
2oneSixBySixLoopOneLane
3twoSixBySixLoopsOneLane
4threeSixBySixLoopsOneLane
5fourSixBySixLoopsOneLane
6oneLongLoopOneLane
7oneSixBySixLoopMultipleLanes

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 NTCIP1209v02-MIB1, the row index sensorZoneNumber 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.4.4.1.1.4.<sensorZoneNumber>. 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.4.4.1.1.4

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

sensorZoneLoopLayout · optional

sensorZoneLoopLayout  OBJECT-TYPE
SYNTAX  INTEGER {
                 other (1),
                 oneSixBySixLoopOneLane (2),
                 twoSixBySixLoopsOneLane (3),
                 threeSixBySixLoopsOneLane (4),
                 fourSixBySixLoopsOneLane (5),
                 oneLongLoopOneLane (6),
                 oneSixBySixLoopMultipleLanes (7) }
ACCESS  read-write
STATUS  optional
DESCRIPTION
"<Definition> The zone configuration provides for standardized sensor loop layouts typically used in roadway applications.
      other(1) - Used for special loop configurations and layouts.
      oneSixBySixLoopOneLane(2) - Used when there in one six-foot by six-
      foot loop in one travel lane.
      twoSixBySixLoopsOneLane(3) - Used when there are two six-foot by six-
      foot loops in one travel lane. 
      threeSixBySixLoopsOneLane(4) - Used when there are three six-foot by
      six-foot loops in one travel lane.
      fourSixBySixLoopsOneLane(5) - Used when there are four six-foot by six-
      foot loops in one travel lane.
      oneLongLoopOneLane(6) - Used when there is one loop in one travel
      lane that exceeds six-feet in length.
      oneSixBySixLoopMultipleLanes(7) - Used when there is one six-foot by
      six-foot loop in each of more than one travel lane.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.4.4.1.1.4"
::= { loopSensorSetupEntry 4 }

sensorZoneLoopLayout · optional

sensorZoneLoopLayout OBJECT-TYPE
SYNTAX INTEGER {
                   other (1),
                   oneSixBySixLoopOneLane (2),
                   twoSixBySixLoopsOneLane (3),
                   threeSixBySixLoopsOneLane (4),
                   fourSixBySixLoopsOneLane (5),
                   oneLongLoopOneLane (6),
                   oneSixBySixLoopMultipleLanes (7) }
ACCESS read-write
STATUS optional
DESCRIPTION
"<Definition> The zone configuration provides for standardized sensor loop
layouts typically used in roadway applications.
       other(1) - Used for special loop configurations and layouts.
       oneSixBySixLoopOneLane(2) - Used when there in one six-foot by six-


                                                                                         

                 
        

      foot loop in one travel lane.
      twoSixBySixLoopsOneLane(3) - Used when there are two six-foot by six-
      foot loops in one travel lane.
      threeSixBySixLoopsOneLane(4) - Used when there are three six-foot by
      six-foot loops in one travel lane.
      fourSixBySixLoopsOneLane(5) - Used when there are four six-foot by six-
      foot loops in one travel lane.
      oneLongLoopOneLane(6) - Used when there is one loop in one travel
      lane that exceeds six-feet in length.
      oneSixBySixLoopMultipleLanes(7) - Used when there is one six-foot by
      six-foot loop in each of more than one travel lane.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.4.4.1.1.4"
::= { loopSensorSetupEntry 4 }

Meaning

Descriptions

1 unique

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

<Definition> The zone configuration provides for standardized sensor loop layouts typically used in roadway applications. other(1) - Used for special loop configurations and layouts. oneSixBySixLoopOneLane(2) - Used when there in one six-foot by six- foot loop in one travel lane. twoSixBySixLoopsOneLane(3) - Used when there are two six-foot by six- foot loops in one travel lane. threeSixBySixLoopsOneLane(4) - Used when there are three six-foot by six-foot loops in one travel lane. fourSixBySixLoopsOneLane(5) - Used when there are four six-foot by six- foot loops in one travel lane. oneLongLoopOneLane(6) - Used when there is one loop in one travel lane that exceeds six-feet in length. oneSixBySixLoopMultipleLanes(7) - Used when there is one six-foot by six-foot loop in each of more than one travel lane. <Object Identifier> 1.3.6.1.4.1.1206.4.2.4.4.1.1.4

Sources for this description

ITE public NTCIP working repository MIBsNTCIP 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 1ITE public NTCIP working repository MIBs, NTCIP published standard MIB annexes (reviewed modules)1 record · 2 sources

Description 1

sensorZoneLoopLayout · optionalITE public NTCIP working repository MIBs, NTCIP published standard MIB annexes (reviewed modules)2 sources

Status in source: optional.

Names: sensorZoneLoopLayout

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "sensorZoneLoopLayout",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "other",
    "(",
    "1",
    ")",
    ",",
    "oneSixBySixLoopOneLane",
    "(",
    "2",
    ")",
    ",",
    "twoSixBySixLoopsOneLane",
    "(",
    "3",
    ")",
    ",",
    "threeSixBySixLoopsOneLane",
    "(",
    "4",
    ")",
    ",",
    "fourSixBySixLoopsOneLane",
    "(",
    "5",
    ")",
    ",",
    "oneLongLoopOneLane",
    "(",
    "6",
    ")",
    ",",
    "oneSixBySixLoopMultipleLanes",
    "(",
    "7",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "optional",
    "DESCRIPTION",
    "\"<Definition> The zone configuration provides for standardized sensor loop layouts typically used in roadway applications. other(1) - Used for special loop configurations and layouts. oneSixBySixLoopOneLane(2) - Used when there in one six-foot by six- foot loop in one travel lane. twoSixBySixLoopsOneLane(3) - Used when there are two six-foot by six- foot loops in one travel lane. threeSixBySixLoopsOneLane(4) - Used when there are three six-foot by six-foot loops in one travel lane. fourSixBySixLoopsOneLane(5) - Used when there are four six-foot by six- foot loops in one travel lane. oneLongLoopOneLane(6) - Used when there is one loop in one travel lane that exceeds six-feet in length. oneSixBySixLoopMultipleLanes(7) - Used when there is one six-foot by six-foot loop in each of more than one travel lane. <Object Identifier> 1.3.6.1.4.1.1206.4.2.4.4.1.1.4\"",
    "::=",
    "{",
    "loopSensorSetupEntry",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "other",
            1
          ],
          [
            "oneSixBySixLoopOneLane",
            2
          ],
          [
            "twoSixBySixLoopsOneLane",
            3
          ],
          [
            "threeSixBySixLoopsOneLane",
            4
          ],
          [
            "fourSixBySixLoopsOneLane",
            5
          ],
          [
            "oneLongLoopOneLane",
            6
          ],
          [
            "oneSixBySixLoopMultipleLanes",
            7
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "optional"
    ],
    [
      "DESCRIPTION",
      "<Definition> The zone configuration provides for standardized sensor loop layouts typically used in roadway applications. other(1) - Used for special loop configurations and layouts. oneSixBySixLoopOneLane(2) - Used when there in one six-foot by six- foot loop in one travel lane. twoSixBySixLoopsOneLane(3) - Used when there are two six-foot by six- foot loops in one travel lane. threeSixBySixLoopsOneLane(4) - Used when there are three six-foot by six-foot loops in one travel lane. fourSixBySixLoopsOneLane(5) - Used when there are four six-foot by six- foot loops in one travel lane. oneLongLoopOneLane(6) - Used when there is one loop in one travel lane that exceeds six-feet in length. oneSixBySixLoopMultipleLanes(7) - Used when there is one six-foot by six-foot loop in each of more than one travel lane. <Object Identifier> 1.3.6.1.4.1.1206.4.2.4.4.1.1.4"
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.4.4.1.1.1 zoneSensitivityMode00
1.3.6.1.4.1.1206.4.2.4.4.1.1.2 zoneSensitivity00
1.3.6.1.4.1.1206.4.2.4.4.1.1.3 zoneFrequencyRange00