OID reference

rmcQueueInEntry

1.3.6.1.4.1.1206.4.2.2.6.3.1

Description

Configuration parameters of the metered lane queue detector physical input table. This table is directly correlated to the Queue 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 Queue Detector Configuration and Control Table (A…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.2.2.6.3 (rmcQueueInTable)
Node code
1
Node name
rmcQueueInEntry
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.2.6.3.1
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.2.6.3.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

SNMP properties

Value type
RmcQueueInEntry
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

rmcQueueInEntry · mandatory

rmcQueueInEntry    OBJECT-TYPE
SYNTAX   RmcQueueInEntry
ACCESS   not-accessible
STATUS   mandatory
DESCRIPTION
"Configuration parameters of the metered lane queue detector physical input
table. This table is directly correlated to the Queue 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 Queue Detector Configuration
and Control Table (AUGMENT TABLE in SNMPv2 terminology). Table management
can only take place through the rmcQueueDetectMode-object within Queue
Detector Configuration and Control Table (rmcQueueCtrlTable), while this
table defines the associated physical input.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.2.6.3.1"
INDEX { rmcMeterNumber, rmcQueueNum }
::={ rmcQueueInTable 1 }

rmcQueueInEntry · mandatory

rmcQueueInEntry OBJECT-TYPE
SYNTAX RmcQueueInEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Configuration parameters of the metered lane queue detector physical input
 table. This table is directly correlated to the Queue 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 Queue Detector Configuration and Control



                                                                                                           

                                                                                                            
                                                                                                            



 Table (AUGMENT TABLE in SNMPv2 terminology). Table management can only take
 place through the rmcQueueDetectMode-object within Queue Detector Configuration
 and Control Table (rmcQueueCtrlTable), while this table defines the associated
 physical input."
INDEX { rmcMeterNumber, rmcQueueNum }
::={ rmcQueueInTable 1 }

Meaning

Descriptions

2 unique

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

Description 1

Configuration parameters of the metered lane queue detector physical input table. This table is directly correlated to the Queue 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 Queue Detector Configuration and Control Table (AUGMENT TABLE in SNMPv2 terminology). Table management can only take place through the rmcQueueDetectMode-object within Queue Detector Configuration and Control Table (rmcQueueCtrlTable), while this table defines the associated physical input. <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.6.3.1

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 2

Configuration parameters of the metered lane queue detector physical input table. This table is directly correlated to the Queue 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 Queue Detector Configuration and Control Table (AUGMENT TABLE in SNMPv2 terminology). Table management can only take place through the rmcQueueDetectMode-object within Queue Detector Configuration and Control Table (rmcQueueCtrlTable), while this table defines the associated physical input.

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

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

Status in source: mandatory.

Names: rmcQueueInEntry

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "rmcQueueInEntry",
    "OBJECT-TYPE",
    "SYNTAX",
    "RmcQueueInEntry",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"Configuration parameters of the metered lane queue detector physical input table. This table is directly correlated to the Queue 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 Queue Detector Configuration and Control Table (AUGMENT TABLE in SNMPv2 terminology). Table management can only take place through the rmcQueueDetectMode-object within Queue Detector Configuration and Control Table (rmcQueueCtrlTable), while this table defines the associated physical input. <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.6.3.1\"",
    "INDEX",
    "{",
    "rmcMeterNumber",
    ",",
    "rmcQueueNum",
    "}",
    "::=",
    "{",
    "rmcQueueInTable",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "RmcQueueInEntry"
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "Configuration parameters of the metered lane queue detector physical input table. This table is directly correlated to the Queue 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 Queue Detector Configuration and Control Table (AUGMENT TABLE in SNMPv2 terminology). Table management can only take place through the rmcQueueDetectMode-object within Queue Detector Configuration and Control Table (rmcQueueCtrlTable), while this table defines the associated physical input. <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.6.3.1"
    ],
    null,
    null,
    [
      "INDEX",
      [
        [
          0,
          "rmcMeterNumber"
        ],
        [
          0,
          "rmcQueueNum"
        ]
      ]
    ],
    null
  ]
}
Records for description 2NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 2

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

Status in source: mandatory.

Names: rmcQueueInEntry

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "rmcQueueInEntry",
    "OBJECT-TYPE",
    "SYNTAX",
    "RmcQueueInEntry",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"Configuration parameters of the metered lane queue detector physical input table. This table is directly correlated to the Queue 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 Queue Detector Configuration and Control Table (AUGMENT TABLE in SNMPv2 terminology). Table management can only take place through the rmcQueueDetectMode-object within Queue Detector Configuration and Control Table (rmcQueueCtrlTable), while this table defines the associated physical input.\"",
    "INDEX",
    "{",
    "rmcMeterNumber",
    ",",
    "rmcQueueNum",
    "}",
    "::=",
    "{",
    "rmcQueueInTable",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "RmcQueueInEntry"
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "Configuration parameters of the metered lane queue detector physical input table. This table is directly correlated to the Queue 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 Queue Detector Configuration and Control Table (AUGMENT TABLE in SNMPv2 terminology). Table management can only take place through the rmcQueueDetectMode-object within Queue Detector Configuration and Control Table (rmcQueueCtrlTable), while this table defines the associated physical input."
    ],
    null,
    null,
    [
      "INDEX",
      [
        [
          0,
          "rmcMeterNumber"
        ],
        [
          0,
          "rmcQueueNum"
        ]
      ]
    ],
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.2.6.3.1.1 rmcMetQueueInNumber00