OID reference

dcmFPRelativeAddrFlag

1.3.6.1.4.1.1206.4.2.9.7.7.1.6

Description

This column is used to enable/disable the use of relative OID addressing in the specified data file. Setting this to a 1 shall inhibit the use of relative OID addressing for this data file. Setting this to a 2 shall enable relative OID addressing for this data file. An application can only enable this feature. It has …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.2.9.7.7.1 (dcmFPEntry)
Node code
6
Node name
dcmFPRelativeAddrFlag
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.9.7.7.1.6
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.9.7.7.1.6
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFPTable(7) dcmFPEntry(1) dcmFPRelativeAddrFlag(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFPTable(7) dcmFPEntry(1) dcmFPRelativeAddrFlag(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFPTable(7) dcmFPEntry(1) dcmFPRelativeAddrFlag(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFPTable(7) dcmFPEntry(1) dcmFPRelativeAddrFlag(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFPTable(7) dcmFPEntry(1) dcmFPRelativeAddrFlag(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFPTable(7) dcmFPEntry(1) dcmFPRelativeAddrFlag(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFPTable(7) dcmFPEntry(1) dcmFPRelativeAddrFlag(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFPTable(7) dcmFPEntry(1) dcmFPRelativeAddrFlag(6)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFPTable(7) dcmFPEntry(1) dcmFPRelativeAddrFlag(6)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFPTable(7) dcmFPEntry(1) dcmFPRelativeAddrFlag(6)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFPTable(7) dcmFPEntry(1) dcmFPRelativeAddrFlag(6)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFPTable(7) dcmFPEntry(1) dcmFPRelativeAddrFlag(6)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFPTable(7) dcmFPEntry(1) dcmFPRelativeAddrFlag(6)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFPTable(7) dcmFPEntry(1) dcmFPRelativeAddrFlag(6)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFPTable(7) dcmFPEntry(1) dcmFPRelativeAddrFlag(6)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dcm(9) dcmFileConfig(7) dcmFPTable(7) dcmFPEntry(1) dcmFPRelativeAddrFlag(6)}
OID-IRI notation
  • /1/3/6/1/4/1/1206/4/2/9/7/7/1/6
  • /ISO/Identified-Organization/6/1/4/1/1206/4/2/9/7/7/1/6
  • /ISO/3/6/1/4/1/1206/4/2/9/7/7/1/6
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dcm/dcmFileConfig/dcmFPTable/dcmFPEntry/dcmFPRelativeAddrFlag
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dcm/dcmFileConfig/dcmFPTable/dcmFPEntry/dcmFPRelativeAddrFlag
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/dcm/dcmFileConfig/dcmFPTable/dcmFPEntry/dcmFPRelativeAddrFlag
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/dcm/dcmFileConfig/dcmFPTable/dcmFPEntry/dcmFPRelativeAddrFlag
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/dcm/dcmFileConfig/dcmFPTable/dcmFPEntry/dcmFPRelativeAddrFlag
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/dcm/dcmFileConfig/dcmFPTable/dcmFPEntry/dcmFPRelativeAddrFlag
  • /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/dcm/dcmFileConfig/dcmFPTable/dcmFPEntry/dcmFPRelativeAddrFlag
  • /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/dcm/dcmFileConfig/dcmFPTable/dcmFPEntry/dcmFPRelativeAddrFlag
  • /iso/org/dod/internet/private/enterprise/1206/transportation/devices/dcm/dcmFileConfig/dcmFPTable/dcmFPEntry/dcmFPRelativeAddrFlag
  • /iso/org/dod/internet/private/enterprise/nema/transportation/devices/dcm/dcmFileConfig/dcmFPTable/dcmFPEntry/dcmFPRelativeAddrFlag
  • /iso/org/dod/internet/private/enterprises/1206/transportation/devices/dcm/dcmFileConfig/dcmFPTable/dcmFPEntry/dcmFPRelativeAddrFlag
  • /iso/org/dod/internet/private/enterprises/nema/transportation/devices/dcm/dcmFileConfig/dcmFPTable/dcmFPEntry/dcmFPRelativeAddrFlag
  • /iso/org/dod/internet/private/ldap-enterprise/1206/transportation/devices/dcm/dcmFileConfig/dcmFPTable/dcmFPEntry/dcmFPRelativeAddrFlag
  • /iso/org/dod/internet/private/ldap-enterprise/nema/transportation/devices/dcm/dcmFileConfig/dcmFPTable/dcmFPEntry/dcmFPRelativeAddrFlag
  • /iso/org/dod/internet/private/vendor-objects/1206/transportation/devices/dcm/dcmFileConfig/dcmFPTable/dcmFPEntry/dcmFPRelativeAddrFlag
  • /iso/org/dod/internet/private/vendor-objects/nema/transportation/devices/dcm/dcmFileConfig/dcmFPTable/dcmFPEntry/dcmFPRelativeAddrFlag
  • Additional combinations skipped.

SNMP properties

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

Enumerated values

ValueName
1disabled
2enabled

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. The index encoding is not inferred here.

Published row index: dcmFPFileStudyIndex, dcmFPFileStrucNum.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.1206.4.2.9.7.7.1.6

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.

The displayed source records contain one distinct definition. Compare its source records.

dcmFPRelativeAddrFlag OBJECT-TYPE
 SYNTAX    INTEGER
 {
   disabled (1),
   enabled (2)
 }
 ACCESS    read-write
 STATUS    mandatory
 DESCRIPTION
 “This column is used to enable/disable the use of relative OID addressing in
the specified data file.          Setting this to a 1 shall inhibit the use of
relative OID addressing for this data file. Setting this to a 2 shall enable
relative OID addressing for this data file. An application can only enable
this feature. It has no control as to where and how often (within this data
file) that the device shall use this option (see dcmRelativeAddress object).”
::= {dcmFPEntry 6}

Meaning

Descriptions

1 unique

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

This column is used to enable/disable the use of relative OID addressing in the specified data file. Setting this to a 1 shall inhibit the use of relative OID addressing for this data file. Setting this to a 2 shall enable relative OID addressing for this data file. An application can only enable this feature. It has no control as to where and how often (within this data file) that the device shall use this option (see dcmRelativeAddress object).

Sources for this description

NTCIP 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 1NTCIP published standard MIB annexes (reviewed modules)1 record · 2 sources

Description 1

dcmFPRelativeAddrFlag · mandatoryNTCIP published standard MIB annexes (reviewed modules)2 sources

Status in source: mandatory.

Names: dcmFPRelativeAddrFlag

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dcmFPRelativeAddrFlag",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "disabled",
    "(",
    "1",
    ")",
    ",",
    "enabled",
    "(",
    "2",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "“",
    "This",
    "column",
    "is",
    "used",
    "to",
    "enable",
    "/",
    "disable",
    "the",
    "use",
    "of",
    "relative",
    "OID",
    "addressing",
    "in",
    "the",
    "specified",
    "data",
    "file",
    ".",
    "Setting",
    "this",
    "to",
    "a",
    "1",
    "shall",
    "inhibit",
    "the",
    "use",
    "of",
    "relative",
    "OID",
    "addressing",
    "for",
    "this",
    "data",
    "file",
    ".",
    "Setting",
    "this",
    "to",
    "a",
    "2",
    "shall",
    "enable",
    "relative",
    "OID",
    "addressing",
    "for",
    "this",
    "data",
    "file",
    ".",
    "An",
    "application",
    "can",
    "only",
    "enable",
    "this",
    "feature",
    ".",
    "It",
    "has",
    "no",
    "control",
    "as",
    "to",
    "where",
    "and",
    "how",
    "often",
    "(",
    "within",
    "this",
    "data",
    "file",
    ")",
    "that",
    "the",
    "device",
    "shall",
    "use",
    "this",
    "option",
    "(",
    "see",
    "dcmRelativeAddress",
    "object",
    ")",
    ".",
    "”",
    "::=",
    "{",
    "dcmFPEntry",
    "6",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "disabled",
            1
          ],
          [
            "enabled",
            2
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "This column is used to enable/disable the use of relative OID addressing in the specified data file. Setting this to a 1 shall inhibit the use of relative OID addressing for this data file. Setting this to a 2 shall enable relative OID addressing for this data file. An application can only enable this feature. It has no control as to where and how often (within this data file) that the device shall use this option (see dcmRelativeAddress object)."
    ],
    null,
    null,
    null,
    null
  ]
}
  • NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1206:2005, Object Definitions for Data Collection and Monitoring (DCM) Devices Published November 2005 — original PDF · Official record

    Module: DCM-MIB1

    See published definition above

    Module imports
    {'TMIB-II': ['devices'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter']}

    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: A typographic closing quotation mark terminates a DESCRIPTION in this PDF. Normalize that delimiter only in the derived MIB transcription; preserve the literal published definition and unmodified PDF. No numeric assignment changes.

    Source data warning: A typographic opening 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: Potentially inaccurate interpretation of historical NTCIP namespace references: TMIB-II. 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 NTCIP1206v0123f.pdf — DCM-MIB1 (MIB transcription)

    Related source files and packages:

    Show more related files and packages
  • NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1206:2005, Object Definitions for Daqta Collection and Monitoring (DCM) Devices Published November 2005 (superceded by NTCIP 1206 v02) — original PDF · Official record

    Module: DCM-MIB1

    Same published definition

    Module imports
    {'TMIB-II': ['devices'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter']}

    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: A typographic closing quotation mark terminates a DESCRIPTION in this PDF. Normalize that delimiter only in the derived MIB transcription; preserve the literal published definition and unmodified PDF. No numeric assignment changes.

    Source data warning: A typographic opening 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: Potentially inaccurate interpretation of historical NTCIP namespace references: TMIB-II. 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 NTCIP1206v0123f-1.pdf — DCM-MIB1 (MIB transcription)

    Related source files and packages:

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (7)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.9.7.7.1.1 dcmFPFileStudyIndex00
1.3.6.1.4.1.1206.4.2.9.7.7.1.2 dcmFPFileStrucNum00
1.3.6.1.4.1.1206.4.2.9.7.7.1.3 dcmFPRecInt00
1.3.6.1.4.1.1206.4.2.9.7.7.1.4 dcmFPFileFreq00
1.3.6.1.4.1.1206.4.2.9.7.7.1.5 dcmFPLogicalIONumber00
1.3.6.1.4.1.1206.4.2.9.7.7.1.7 dcmFPEncodingCode00
1.3.6.1.4.1.1206.4.2.9.7.7.1.8 dcmFPRowAdmin00