OID reference

recValue

1.3.6.1.4.1.1206.4.1.1.7.9.11.1.3

Description

<Definition>The value of this object is set to the BER encoding of the value referenced by the recConfigRecordOID of the associated recordingConfigID when the entry was collected. Its length is variable. The value shall not contain any padding characters either before or after the values. NOTE – Opaque objects are dou…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.1.1.7.9.11.1 (recEntry)
Node code
3
Node name
recValue
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.1.1.7.9.11.1.3
URN notation
urn:oid:1.3.6.1.4.1.1206.4.1.1.7.9.11.1.3
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 1206 4 1 1 7 9 11 1 3}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recEntriesTable(11) recEntry(1) recValue(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recEntriesTable(11) recEntry(1) recValue(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recEntriesTable(11) recEntry(1) recValue(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recEntriesTable(11) recEntry(1) recValue(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recEntriesTable(11) recEntry(1) recValue(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recEntriesTable(11) recEntry(1) recValue(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recEntriesTable(11) recEntry(1) recValue(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recEntriesTable(11) recEntry(1) recValue(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recEntriesTable(11) recEntry(1) recValue(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recEntriesTable(11) recEntry(1) recValue(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recEntriesTable(11) recEntry(1) recValue(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recEntriesTable(11) recEntry(1) recValue(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recEntriesTable(11) recEntry(1) recValue(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recEntriesTable(11) recEntry(1) recValue(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recEntriesTable(11) recEntry(1) recValue(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recEntriesTable(11) recEntry(1) recValue(3)}
OID-IRI notation
  • /1/3/6/1/4/1/1206/4/1/1/7/9/11/1/3
  • /ISO/Identified-Organization/6/1/4/1/1206/4/1/1/7/9/11/1/3
  • /ISO/3/6/1/4/1/1206/4/1/1/7/9/11/1/3
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/protocols/layers/application/recMech/recEntriesTable/recEntry/recValue
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/Protocols/layers/application/recMech/recEntriesTable/recEntry/recValue
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/protocols/layers/application/recMech/recEntriesTable/recEntry/recValue
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/Protocols/layers/application/recMech/recEntriesTable/recEntry/recValue
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/protocols/layers/application/recMech/recEntriesTable/recEntry/recValue
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/Protocols/layers/application/recMech/recEntriesTable/recEntry/recValue
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/protocols/layers/application/recMech/recEntriesTable/recEntry/recValue
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/Protocols/layers/application/recMech/recEntriesTable/recEntry/recValue
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/protocols/layers/application/recMech/recEntriesTable/recEntry/recValue
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/Protocols/layers/application/recMech/recEntriesTable/recEntry/recValue
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/protocols/layers/application/recMech/recEntriesTable/recEntry/recValue
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/Protocols/layers/application/recMech/recEntriesTable/recEntry/recValue
  • /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/protocols/layers/application/recMech/recEntriesTable/recEntry/recValue
  • /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/Protocols/layers/application/recMech/recEntriesTable/recEntry/recValue
  • /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/protocols/layers/application/recMech/recEntriesTable/recEntry/recValue
  • /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/Protocols/layers/application/recMech/recEntriesTable/recEntry/recValue
  • Additional combinations skipped.

SNMP properties

Value type
Opaque
Maximum access defined by MIB
read-only
Status in MIB
mandatory, deprecated

Definitions may combine these properties differently.

Compare 2 source variants

Variant 1 — NTCIP published standard MIB annexes (reviewed modules)

Value type
Opaque
Maximum access defined by MIB
read-only
Status in MIB
mandatory

Variant 2 — NTCIP published standard MIB annexes (reviewed modules), ITE public NTCIP working repository MIBs

Value type
Opaque
Maximum access defined by MIB
read-only
Status in MIB
deprecated

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 NTCIP1201-RecMech, the row index consists of these components in order:

  1. recordingID (Integer32): one numeric subidentifier for the non-negative value.
  2. recEntryNumber (Integer32): one numeric subidentifier for the non-negative value.

An instance has the form .1.3.6.1.4.1.1206.4.1.1.7.9.11.1.3.<recordingID>.<recEntryNumber>. Use values 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.1.1.7.9.11.1.3

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 3 distinct definitions; some records may not include a definition.

Show 3 published definitions

recValue · mandatory

recValue OBJECT-TYPE
   SYNTAX Opaque
   ACCESS read-only
   STATUS mandatory
   DESCRIPTION
        "<Definition>The value of this object is set to the BER
           encoding of the value referenced by the recConfigRecordOID
           of the associated recordingConfigID when the entry was collected.
           Its length is variable. The value shall not contain any padding
           characters either before or after the values.
           NOTE – Opaque objects are doubly wrapped. For SNMP
           operations, which use BER, this would be {type, length,
           {type, length, value}}. For example, a zero-length octet
           string, would be encoded in BER as 0x44 02 04 00. For STMP
           or SFMP operations, which use OER, this would be { length,
           {type, length, value}}. For example, the same example would
           be encoded in OER as 0x02 04 00.
          <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.11.1.3
        "
::= { recEntry 3 }

recValue · deprecated

recValue OBJECT-TYPE
SYNTAX        Opaque
MAX-ACCESS read-only
STATUS        deprecated
DESCRIPTION
   "<Definition>The value of this object is set to the BER encoding of the
   value referenced by the recConfigRecordOID of the associated
   recordingConfigID when the entry was collected. Its length is variable. The
   value shall not contain any padding characters either before or after the
   values.
  <Supplanted by> ISO26048-1-Recording.fdRecordingSampleValue
  <Informative> Opaque objects are doubly wrapped. For SNMP operations, which
  use BER, this would be {type, length, {type, length, value}}. For example,
  a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For
  STMP or SFMP operations, which use OER, this would be { length, {type,
  length, value}}. For example, the same example would be encoded in OER as
  0x02 04 00.
  The syntax of the replacement object is ITSOerString.
  <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.11.1.3"
::= { recEntry 3 }

recValue · deprecated

recValue  OBJECT-TYPE
  SYNTAX      Opaque
  MAX-ACCESS  read-only
  STATUS      deprecated
  DESCRIPTION
    "<Definition>The value of this object is set to the BER 
      encoding of the value referenced by the recConfigRecordOID 
      of the associated recordingConfigID when the entry was collected.
      Its length is variable. The value shall not contain any padding 
      characters either before or after the values.
      NOTE: Opaque objects are doubly wrapped. For SNMP 
      operations, which use BER, this would be {type, length, 
      {type, length, value}}. For example, a zero-length octet 
      string, would be encoded in BER as 0x44 02 04 00. For STMP 
      or SFMP operations, which use OER, this would be { length, 
      {type, length, value}}. For example, the same example would 
      be encoded in OER as 0x02 04 00. 
    <Superseded by> NTCIP1201-RecMechV2.recMechV2SampleValue
    <Informative> The syntax of the replacement object is ITSOerString. 
    <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.11.1.3"
::= { recEntry 3 }

Meaning

Descriptions

3 unique

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

Description 1

<Definition>The value of this object is set to the BER encoding of the value referenced by the recConfigRecordOID of the associated recordingConfigID when the entry was collected. Its length is variable. The value shall not contain any padding characters either before or after the values. NOTE – Opaque objects are doubly wrapped. For SNMP operations, which use BER, this would be {type, length, {type, length, value}}. For example, a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For STMP or SFMP operations, which use OER, this would be { length, {type, length, value}}. For example, the same example would be encoded in OER as 0x02 04 00. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.11.1.3

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 2

<Definition>The value of this object is set to the BER encoding of the value referenced by the recConfigRecordOID of the associated recordingConfigID when the entry was collected. Its length is variable. The value shall not contain any padding characters either before or after the values. <Supplanted by> ISO26048-1-Recording.fdRecordingSampleValue <Informative> Opaque objects are doubly wrapped. For SNMP operations, which use BER, this would be {type, length, {type, length, value}}. For example, a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For STMP or SFMP operations, which use OER, this would be { length, {type, length, value}}. For example, the same example would be encoded in OER as 0x02 04 00. The syntax of the replacement object is ITSOerString. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.11.1.3

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 3

<Definition>The value of this object is set to the BER encoding of the value referenced by the recConfigRecordOID of the associated recordingConfigID when the entry was collected. Its length is variable. The value shall not contain any padding characters either before or after the values. NOTE: Opaque objects are doubly wrapped. For SNMP operations, which use BER, this would be {type, length, {type, length, value}}. For example, a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For STMP or SFMP operations, which use OER, this would be { length, {type, length, value}}. For example, the same example would be encoded in OER as 0x02 04 00. <Superseded by> NTCIP1201-RecMechV2.recMechV2SampleValue <Informative> The syntax of the replacement object is ITSOerString. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.11.1.3

Sources for this description

ITE public NTCIP working repository MIBs

See 1 matching source record

Evidence

Source records

3 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

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

Status in source: mandatory.

Names: recValue

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "recValue",
    "OBJECT-TYPE",
    "SYNTAX",
    "Opaque",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition>The value of this object is set to the BER encoding of the value referenced by the recConfigRecordOID of the associated recordingConfigID when the entry was collected. Its length is variable. The value shall not contain any padding characters either before or after the values. NOTE – Opaque objects are doubly wrapped. For SNMP operations, which use BER, this would be {type, length, {type, length, value}}. For example, a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For STMP or SFMP operations, which use OER, this would be { length, {type, length, value}}. For example, the same example would be encoded in OER as 0x02 04 00. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.11.1.3 \"",
    "::=",
    "{",
    "recEntry",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "ApplicationSyntax",
      "Opaque"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition>The value of this object is set to the BER encoding of the value referenced by the recConfigRecordOID of the associated recordingConfigID when the entry was collected. Its length is variable. The value shall not contain any padding characters either before or after the values. NOTE – Opaque objects are doubly wrapped. For SNMP operations, which use BER, this would be {type, length, {type, length, value}}. For example, a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For STMP or SFMP operations, which use OER, this would be { length, {type, length, value}}. For example, the same example would be encoded in OER as 0x02 04 00. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.11.1.3"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 2

recValue · deprecatedNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: deprecated.

Names: recValue

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "recValue",
    "OBJECT-TYPE",
    "SYNTAX",
    "Opaque",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition>The value of this object is set to the BER encoding of the value referenced by the recConfigRecordOID of the associated recordingConfigID when the entry was collected. Its length is variable. The value shall not contain any padding characters either before or after the values. <Supplanted by> ISO26048-1-Recording.fdRecordingSampleValue <Informative> Opaque objects are doubly wrapped. For SNMP operations, which use BER, this would be {type, length, {type, length, value}}. For example, a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For STMP or SFMP operations, which use OER, this would be { length, {type, length, value}}. For example, the same example would be encoded in OER as 0x02 04 00. The syntax of the replacement object is ITSOerString. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.11.1.3\"",
    "::=",
    "{",
    "recEntry",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "ApplicationSyntax",
      "Opaque"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition>The value of this object is set to the BER encoding of the value referenced by the recConfigRecordOID of the associated recordingConfigID when the entry was collected. Its length is variable. The value shall not contain any padding characters either before or after the values. <Supplanted by> ISO26048-1-Recording.fdRecordingSampleValue <Informative> Opaque objects are doubly wrapped. For SNMP operations, which use BER, this would be {type, length, {type, length, value}}. For example, a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For STMP or SFMP operations, which use OER, this would be { length, {type, length, value}}. For example, the same example would be encoded in OER as 0x02 04 00. The syntax of the replacement object is ITSOerString. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.11.1.3"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 3ITE public NTCIP working repository MIBs1 record · 2 sources

Description 3

recValue · deprecatedITE public NTCIP working repository MIBs2 sources

Status in source: deprecated.

Names: recValue

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "recValue",
    "OBJECT-TYPE",
    "SYNTAX",
    "Opaque",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition>The value of this object is set to the BER encoding of the value referenced by the recConfigRecordOID of the associated recordingConfigID when the entry was collected. Its length is variable. The value shall not contain any padding characters either before or after the values. NOTE: Opaque objects are doubly wrapped. For SNMP operations, which use BER, this would be {type, length, {type, length, value}}. For example, a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For STMP or SFMP operations, which use OER, this would be { length, {type, length, value}}. For example, the same example would be encoded in OER as 0x02 04 00. <Superseded by> NTCIP1201-RecMechV2.recMechV2SampleValue <Informative> The syntax of the replacement object is ITSOerString. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.11.1.3\"",
    "::=",
    "{",
    "recEntry",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "ApplicationSyntax",
      "Opaque"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition>The value of this object is set to the BER encoding of the value referenced by the recConfigRecordOID of the associated recordingConfigID when the entry was collected. Its length is variable. The value shall not contain any padding characters either before or after the values. NOTE: Opaque objects are doubly wrapped. For SNMP operations, which use BER, this would be {type, length, {type, length, value}}. For example, a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For STMP or SFMP operations, which use OER, this would be { length, {type, length, value}}. For example, the same example would be encoded in OER as 0x02 04 00. <Superseded by> NTCIP1201-RecMechV2.recMechV2SampleValue <Informative> The syntax of the replacement object is ITSOerString. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.11.1.3"
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (2)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.1.1.7.9.11.1.1 recEntryNumber00
1.3.6.1.4.1.1206.4.1.1.7.9.11.1.2 recSampleTime00