OID reference

rmcDependInOutEntry

1.3.6.1.4.1.1206.4.2.2.6.5.1

Description

Configuration parameters of the dependency group physical input/output table. This table is directly correlated to the Dependency Group 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 Dependency Group 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.5 (rmcDependInOutTable)
Node code
1
Node name
rmcDependInOutEntry
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.2.6.5.1
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.2.6.5.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) ramp(2) rmcInOutput(6) rmcDependInOutTable(5) rmcDependInOutEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) ramp(2) rmcInOutput(6) rmcDependInOutTable(5) rmcDependInOutEntry(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) rmcDependInOutTable(5) rmcDependInOutEntry(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) rmcDependInOutTable(5) rmcDependInOutEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) ramp(2) rmcInOutput(6) rmcDependInOutTable(5) rmcDependInOutEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) ramp(2) rmcInOutput(6) rmcDependInOutTable(5) rmcDependInOutEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) ramp(2) rmcInOutput(6) rmcDependInOutTable(5) rmcDependInOutEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) ramp(2) rmcInOutput(6) rmcDependInOutTable(5) rmcDependInOutEntry(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) rmcDependInOutTable(5) rmcDependInOutEntry(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) rmcDependInOutTable(5) rmcDependInOutEntry(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) rmcDependInOutTable(5) rmcDependInOutEntry(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) rmcDependInOutTable(5) rmcDependInOutEntry(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) ramp(2) rmcInOutput(6) rmcDependInOutTable(5) rmcDependInOutEntry(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) ramp(2) rmcInOutput(6) rmcDependInOutTable(5) rmcDependInOutEntry(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) rmcDependInOutTable(5) rmcDependInOutEntry(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) rmcDependInOutTable(5) rmcDependInOutEntry(1)}
OID-IRI notation
  • /1/3/6/1/4/1/1206/4/2/2/6/5/1
  • /ISO/Identified-Organization/6/1/4/1/1206/4/2/2/6/5/1
  • /ISO/3/6/1/4/1/1206/4/2/2/6/5/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/ramp/rmcInOutput/rmcDependInOutTable/rmcDependInOutEntry
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/ramp/rmcInOutput/rmcDependInOutTable/rmcDependInOutEntry
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/ramp/rmcInOutput/rmcDependInOutTable/rmcDependInOutEntry
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/ramp/rmcInOutput/rmcDependInOutTable/rmcDependInOutEntry
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/ramp/rmcInOutput/rmcDependInOutTable/rmcDependInOutEntry
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/ramp/rmcInOutput/rmcDependInOutTable/rmcDependInOutEntry
  • /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/ramp/rmcInOutput/rmcDependInOutTable/rmcDependInOutEntry
  • /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/ramp/rmcInOutput/rmcDependInOutTable/rmcDependInOutEntry
  • /iso/org/dod/internet/private/enterprise/1206/transportation/devices/ramp/rmcInOutput/rmcDependInOutTable/rmcDependInOutEntry
  • /iso/org/dod/internet/private/enterprise/nema/transportation/devices/ramp/rmcInOutput/rmcDependInOutTable/rmcDependInOutEntry
  • /iso/org/dod/internet/private/enterprises/1206/transportation/devices/ramp/rmcInOutput/rmcDependInOutTable/rmcDependInOutEntry
  • /iso/org/dod/internet/private/enterprises/nema/transportation/devices/ramp/rmcInOutput/rmcDependInOutTable/rmcDependInOutEntry
  • /iso/org/dod/internet/private/ldap-enterprise/1206/transportation/devices/ramp/rmcInOutput/rmcDependInOutTable/rmcDependInOutEntry
  • /iso/org/dod/internet/private/ldap-enterprise/nema/transportation/devices/ramp/rmcInOutput/rmcDependInOutTable/rmcDependInOutEntry
  • /iso/org/dod/internet/private/vendor-objects/1206/transportation/devices/ramp/rmcInOutput/rmcDependInOutTable/rmcDependInOutEntry
  • /iso/org/dod/internet/private/vendor-objects/nema/transportation/devices/ramp/rmcInOutput/rmcDependInOutTable/rmcDependInOutEntry
  • Additional combinations skipped.

SNMP properties

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

rmcDependInOutEntry · mandatory

rmcDependInOutEntry OBJECT-TYPE
SYNTAX RmcDependInOutEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Configuration parameters of the dependency group physical input/output table.
 This table is directly correlated to the Dependency Group 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 Dependency Group Configuration and Control
 Table (AUGMENT TABLE in SNMPv2 terminology). Table management can only take
 place through the Dependency Group Configuration and Control Table
 (rmcDependGroupCtrlTable), while this table defines the associated physical
 input and outputs."
INDEX { rmcDependGroupNumber }
::={ rmcDependInOutTable 1 }

rmcDependInOutEntry · mandatory

rmcDependInOutEntry   OBJECT-TYPE
SYNTAX   RmcDependInOutEntry
ACCESS   not-accessible
STATUS   mandatory
DESCRIPTION
"Configuration parameters of the dependency group physical input/output table.
This table is directly correlated to the Dependency Group 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 Dependency Group Configuration and
Control Table (AUGMENT TABLE in SNMPv2 terminology). Table management can
only take place through the Dependency Group Configuration and Control Table



                                                                                        

                 
        

(rmcDependGroupCtrlTable), while this table defines the associated physical
input and outputs.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.2.6.5.1"
INDEX { rmcDependGroupNumber }
::={ rmcDependInOutTable 1 }

Meaning

Descriptions

2 unique

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

Description 1

Configuration parameters of the dependency group physical input/output table. This table is directly correlated to the Dependency Group 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 Dependency Group Configuration and Control Table (AUGMENT TABLE in SNMPv2 terminology). Table management can only take place through the Dependency Group Configuration and Control Table (rmcDependGroupCtrlTable), while this table defines the associated physical input and outputs.

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 2

Configuration parameters of the dependency group physical input/output table. This table is directly correlated to the Dependency Group 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 Dependency Group Configuration and Control Table (AUGMENT TABLE in SNMPv2 terminology). Table management can only take place through the Dependency Group Configuration and Control Table (rmcDependGroupCtrlTable), while this table defines the associated physical input and outputs. <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.6.5.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

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

Status in source: mandatory.

Names: rmcDependInOutEntry

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "rmcDependInOutEntry",
    "OBJECT-TYPE",
    "SYNTAX",
    "RmcDependInOutEntry",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"Configuration parameters of the dependency group physical input/output table. This table is directly correlated to the Dependency Group 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 Dependency Group Configuration and Control Table (AUGMENT TABLE in SNMPv2 terminology). Table management can only take place through the Dependency Group Configuration and Control Table (rmcDependGroupCtrlTable), while this table defines the associated physical input and outputs.\"",
    "INDEX",
    "{",
    "rmcDependGroupNumber",
    "}",
    "::=",
    "{",
    "rmcDependInOutTable",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "RmcDependInOutEntry"
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "Configuration parameters of the dependency group physical input/output table. This table is directly correlated to the Dependency Group 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 Dependency Group Configuration and Control Table (AUGMENT TABLE in SNMPv2 terminology). Table management can only take place through the Dependency Group Configuration and Control Table (rmcDependGroupCtrlTable), while this table defines the associated physical input and outputs."
    ],
    null,
    null,
    [
      "INDEX",
      [
        [
          0,
          "rmcDependGroupNumber"
        ]
      ]
    ],
    null
  ]
}
Records for description 2NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 2

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

Status in source: mandatory.

Names: rmcDependInOutEntry

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "rmcDependInOutEntry",
    "OBJECT-TYPE",
    "SYNTAX",
    "RmcDependInOutEntry",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"Configuration parameters of the dependency group physical input/output table. This table is directly correlated to the Dependency Group 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 Dependency Group Configuration and Control Table (AUGMENT TABLE in SNMPv2 terminology). Table management can only take place through the Dependency Group Configuration and Control Table (rmcDependGroupCtrlTable), while this table defines the associated physical input and outputs. <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.6.5.1\"",
    "INDEX",
    "{",
    "rmcDependGroupNumber",
    "}",
    "::=",
    "{",
    "rmcDependInOutTable",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "RmcDependInOutEntry"
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "Configuration parameters of the dependency group physical input/output table. This table is directly correlated to the Dependency Group 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 Dependency Group Configuration and Control Table (AUGMENT TABLE in SNMPv2 terminology). Table management can only take place through the Dependency Group Configuration and Control Table (rmcDependGroupCtrlTable), while this table defines the associated physical input and outputs. <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.6.5.1"
    ],
    null,
    null,
    [
      "INDEX",
      [
        [
          0,
          "rmcDependGroupNumber"
        ]
      ]
    ],
    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 (2)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.2.6.5.1.1 rmcDependMergeInNumber00
1.3.6.1.4.1.1206.4.2.2.6.5.1.2 rmcDependAdvSignOutNumber00