OID reference

rmcPassageStatEntry

1.3.6.1.4.1.1206.4.2.2.3.5.2.1

Description

Status parameters of the passage detector table. This table is directly correlated to the Passage Detector Configuration and Control Table, which means that the number of rows in this table is exactly the same as the number of rows in the Passage Detector Configuration and Control Table (AUGMENT TABLE in SNMPv2 termin…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.2.2.3.5.2 (rmcPassageStatTable)
Node code
1
Node name
rmcPassageStatEntry
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.2.3.5.2.1
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.2.3.5.2.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) ramp(2) rmcMeter(3) rmcPassage(5) rmcPassageStatTable(2) rmcPassageStatEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) ramp(2) rmcMeter(3) rmcPassage(5) rmcPassageStatTable(2) rmcPassageStatEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) ramp(2) rmcMeter(3) rmcPassage(5) rmcPassageStatTable(2) rmcPassageStatEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) ramp(2) rmcMeter(3) rmcPassage(5) rmcPassageStatTable(2) rmcPassageStatEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) ramp(2) rmcMeter(3) rmcPassage(5) rmcPassageStatTable(2) rmcPassageStatEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) ramp(2) rmcMeter(3) rmcPassage(5) rmcPassageStatTable(2) rmcPassageStatEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) ramp(2) rmcMeter(3) rmcPassage(5) rmcPassageStatTable(2) rmcPassageStatEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) ramp(2) rmcMeter(3) rmcPassage(5) rmcPassageStatTable(2) rmcPassageStatEntry(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) ramp(2) rmcMeter(3) rmcPassage(5) rmcPassageStatTable(2) rmcPassageStatEntry(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) ramp(2) rmcMeter(3) rmcPassage(5) rmcPassageStatTable(2) rmcPassageStatEntry(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) ramp(2) rmcMeter(3) rmcPassage(5) rmcPassageStatTable(2) rmcPassageStatEntry(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) ramp(2) rmcMeter(3) rmcPassage(5) rmcPassageStatTable(2) rmcPassageStatEntry(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) ramp(2) rmcMeter(3) rmcPassage(5) rmcPassageStatTable(2) rmcPassageStatEntry(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) ramp(2) rmcMeter(3) rmcPassage(5) rmcPassageStatTable(2) rmcPassageStatEntry(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) ramp(2) rmcMeter(3) rmcPassage(5) rmcPassageStatTable(2) rmcPassageStatEntry(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) ramp(2) rmcMeter(3) rmcPassage(5) rmcPassageStatTable(2) rmcPassageStatEntry(1)}
OID-IRI notation
  • /1/3/6/1/4/1/1206/4/2/2/3/5/2/1
  • /ISO/Identified-Organization/6/1/4/1/1206/4/2/2/3/5/2/1
  • /ISO/3/6/1/4/1/1206/4/2/2/3/5/2/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/ramp/rmcMeter/rmcPassage/rmcPassageStatTable/rmcPassageStatEntry
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/ramp/rmcMeter/rmcPassage/rmcPassageStatTable/rmcPassageStatEntry
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/ramp/rmcMeter/rmcPassage/rmcPassageStatTable/rmcPassageStatEntry
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/ramp/rmcMeter/rmcPassage/rmcPassageStatTable/rmcPassageStatEntry
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/ramp/rmcMeter/rmcPassage/rmcPassageStatTable/rmcPassageStatEntry
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/ramp/rmcMeter/rmcPassage/rmcPassageStatTable/rmcPassageStatEntry
  • /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/ramp/rmcMeter/rmcPassage/rmcPassageStatTable/rmcPassageStatEntry
  • /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/ramp/rmcMeter/rmcPassage/rmcPassageStatTable/rmcPassageStatEntry
  • /iso/org/dod/internet/private/enterprise/1206/transportation/devices/ramp/rmcMeter/rmcPassage/rmcPassageStatTable/rmcPassageStatEntry
  • /iso/org/dod/internet/private/enterprise/nema/transportation/devices/ramp/rmcMeter/rmcPassage/rmcPassageStatTable/rmcPassageStatEntry
  • /iso/org/dod/internet/private/enterprises/1206/transportation/devices/ramp/rmcMeter/rmcPassage/rmcPassageStatTable/rmcPassageStatEntry
  • /iso/org/dod/internet/private/enterprises/nema/transportation/devices/ramp/rmcMeter/rmcPassage/rmcPassageStatTable/rmcPassageStatEntry
  • /iso/org/dod/internet/private/ldap-enterprise/1206/transportation/devices/ramp/rmcMeter/rmcPassage/rmcPassageStatTable/rmcPassageStatEntry
  • /iso/org/dod/internet/private/ldap-enterprise/nema/transportation/devices/ramp/rmcMeter/rmcPassage/rmcPassageStatTable/rmcPassageStatEntry
  • /iso/org/dod/internet/private/vendor-objects/1206/transportation/devices/ramp/rmcMeter/rmcPassage/rmcPassageStatTable/rmcPassageStatEntry
  • /iso/org/dod/internet/private/vendor-objects/nema/transportation/devices/ramp/rmcMeter/rmcPassage/rmcPassageStatTable/rmcPassageStatEntry
  • Additional combinations skipped.

SNMP properties

Value type
RmcPassageStatEntry
Maximum access defined by MIB
not-accessible
Status in MIB
mandatory

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

rmcPassageStatEntry · mandatory

rmcPassageStatEntry OBJECT-TYPE
SYNTAX RmcPassageStatEntry
ACCESS not-accessible


                                                                                                            

                                                                                                          
                                                                                                          



STATUS mandatory
DESCRIPTION
"Status parameters of the passage detector table. This table is directly
 correlated to the Passage Detector Configuration and Control Table, which means
 that the number of rows in this table is exactly the same as the number of rows
 in the Passage Detector Configuration and Control Table (AUGMENT TABLE in
 SNMPv2 terminology). Table management can only take place through the Passage
 Detector Configuration and Control Table, while this table provides status
 information for the associated passage detector."
INDEX { rmcMeterNumber }
::={ rmcPassageStatTable 1 }

rmcPassageStatEntry · mandatory

rmcPassageStatEntry   OBJECT-TYPE
SYNTAX   RmcPassageStatEntry
ACCESS   not-accessible
STATUS   mandatory
DESCRIPTION
"Status parameters of the passage detector table. This table is directly
correlated to the Passage Detector Configuration and Control Table, which
means that the number of rows in this table is exactly the same as the number
of rows in the Passage Detector Configuration and Control Table (AUGMENT
TABLE in SNMPv2 terminology). Table management can only take place through
the PassagDetector Configuration and Control Table, while this table provides
status information for the associated passage detector.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.2.3.5.2.1"
INDEX { rmcMeterNumber }
::={ rmcPassageStatTable 1 }

Meaning

Descriptions

2 unique

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

Description 1

Status parameters of the passage detector table. This table is directly correlated to the Passage Detector Configuration and Control Table, which means that the number of rows in this table is exactly the same as the number of rows in the Passage Detector Configuration and Control Table (AUGMENT TABLE in SNMPv2 terminology). Table management can only take place through the Passage Detector Configuration and Control Table, while this table provides status information for the associated passage detector.

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 2

Status parameters of the passage detector table. This table is directly correlated to the Passage Detector Configuration and Control Table, which means that the number of rows in this table is exactly the same as the number of rows in the Passage Detector Configuration and Control Table (AUGMENT TABLE in SNMPv2 terminology). Table management can only take place through the PassagDetector Configuration and Control Table, while this table provides status information for the associated passage detector. <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.3.5.2.1

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

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

Status in source: mandatory.

Names: rmcPassageStatEntry

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "rmcPassageStatEntry",
    "OBJECT-TYPE",
    "SYNTAX",
    "RmcPassageStatEntry",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"Status parameters of the passage detector table. This table is directly correlated to the Passage Detector Configuration and Control Table, which means that the number of rows in this table is exactly the same as the number of rows in the Passage Detector Configuration and Control Table (AUGMENT TABLE in SNMPv2 terminology). Table management can only take place through the Passage Detector Configuration and Control Table, while this table provides status information for the associated passage detector.\"",
    "INDEX",
    "{",
    "rmcMeterNumber",
    "}",
    "::=",
    "{",
    "rmcPassageStatTable",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "RmcPassageStatEntry"
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "Status parameters of the passage detector table. This table is directly correlated to the Passage Detector Configuration and Control Table, which means that the number of rows in this table is exactly the same as the number of rows in the Passage Detector Configuration and Control Table (AUGMENT TABLE in SNMPv2 terminology). Table management can only take place through the Passage Detector Configuration and Control Table, while this table provides status information for the associated passage detector."
    ],
    null,
    null,
    [
      "INDEX",
      [
        [
          0,
          "rmcMeterNumber"
        ]
      ]
    ],
    null
  ]
}
Records for description 2NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 2

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

Status in source: mandatory.

Names: rmcPassageStatEntry

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "rmcPassageStatEntry",
    "OBJECT-TYPE",
    "SYNTAX",
    "RmcPassageStatEntry",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"Status parameters of the passage detector table. This table is directly correlated to the Passage Detector Configuration and Control Table, which means that the number of rows in this table is exactly the same as the number of rows in the Passage Detector Configuration and Control Table (AUGMENT TABLE in SNMPv2 terminology). Table management can only take place through the PassagDetector Configuration and Control Table, while this table provides status information for the associated passage detector. <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.3.5.2.1\"",
    "INDEX",
    "{",
    "rmcMeterNumber",
    "}",
    "::=",
    "{",
    "rmcPassageStatTable",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "RmcPassageStatEntry"
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "Status parameters of the passage detector table. This table is directly correlated to the Passage Detector Configuration and Control Table, which means that the number of rows in this table is exactly the same as the number of rows in the Passage Detector Configuration and Control Table (AUGMENT TABLE in SNMPv2 terminology). Table management can only take place through the PassagDetector Configuration and Control Table, while this table provides status information for the associated passage detector. <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.3.5.2.1"
    ],
    null,
    null,
    [
      "INDEX",
      [
        [
          0,
          "rmcMeterNumber"
        ]
      ]
    ],
    null
  ]
}
  • NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1207 v02, Object Definitions for Ramp Meter Control (RMC) Units Published September 2014 — original PDF · Official record

    Module: N207v0214-MIB

    See published definition above

    Module imports
    {'NTCIP': ['ramp'], 'RFC-1212': ['OBJECT-TYPE']}

    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: The PDF prints an invalid ASN.1 module label (1207v0214-MIB). The derived transcription uses an equal-length internal parsing label; this is not an OID registration or an alteration of any numeric assignment. The original label and full PDF are retained.

    Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP. 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 NTCIP1207v0214hj.pdf — N207v0214-MIB (MIB transcription)

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Direct children (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.2.3.5.2.1.1 rmcPassageStatus00
1.3.6.1.4.1.1206.4.2.2.3.5.2.1.2 rmcHistPassageStatus00
1.3.6.1.4.1.1206.4.2.2.3.5.2.1.3 rmcPassageVehicleCount00