OID reference

recConfigSamplePeriod

1.3.6.1.4.1.1206.4.1.1.7.9.7.1.9

Description

<Definition> This object contains the sample period for recordings collected at specified by this configuration. The sample period is expressed in units of 0.1 milliseconds. Allowable sample periods are restricted to a value of zero (0) or (recMinSamplePeriod + recSamplePeriodResolution * n) where n is integer, 0 <= n…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.1.1.7.9.7.1 (recConfigEntry)
Node code
9
Node name
recConfigSamplePeriod
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.1.1.7.9.7.1.9
URN notation
urn:oid:1.3.6.1.4.1.1206.4.1.1.7.9.7.1.9
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {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) recConfigTable(7) recConfigEntry(1) recConfigSamplePeriod(9)}
  • {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) recConfigTable(7) recConfigEntry(1) recConfigSamplePeriod(9)}
  • {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) recConfigTable(7) recConfigEntry(1) recConfigSamplePeriod(9)}
  • {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) recConfigTable(7) recConfigEntry(1) recConfigSamplePeriod(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recConfigTable(7) recConfigEntry(1) recConfigSamplePeriod(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) protocols(1) layers(1) application(7) recMech(9) recConfigTable(7) recConfigEntry(1) recConfigSamplePeriod(9)}
  • {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) recConfigTable(7) recConfigEntry(1) recConfigSamplePeriod(9)}
  • {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) recConfigTable(7) recConfigEntry(1) recConfigSamplePeriod(9)}
  • {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) recConfigTable(7) recConfigEntry(1) recConfigSamplePeriod(9)}
  • {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) recConfigTable(7) recConfigEntry(1) recConfigSamplePeriod(9)}
  • {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) recConfigTable(7) recConfigEntry(1) recConfigSamplePeriod(9)}
  • {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) recConfigTable(7) recConfigEntry(1) recConfigSamplePeriod(9)}
  • {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) recConfigTable(7) recConfigEntry(1) recConfigSamplePeriod(9)}
  • {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) recConfigTable(7) recConfigEntry(1) recConfigSamplePeriod(9)}
  • {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) recConfigTable(7) recConfigEntry(1) recConfigSamplePeriod(9)}
  • {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) recConfigTable(7) recConfigEntry(1) recConfigSamplePeriod(9)}
OID-IRI notation
  • /1/3/6/1/4/1/1206/4/1/1/7/9/7/1/9
  • /ISO/Identified-Organization/6/1/4/1/1206/4/1/1/7/9/7/1/9
  • /ISO/3/6/1/4/1/1206/4/1/1/7/9/7/1/9
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/protocols/layers/application/recMech/recConfigTable/recConfigEntry/recConfigSamplePeriod
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/Protocols/layers/application/recMech/recConfigTable/recConfigEntry/recConfigSamplePeriod
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/protocols/layers/application/recMech/recConfigTable/recConfigEntry/recConfigSamplePeriod
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/Protocols/layers/application/recMech/recConfigTable/recConfigEntry/recConfigSamplePeriod
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/protocols/layers/application/recMech/recConfigTable/recConfigEntry/recConfigSamplePeriod
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/Protocols/layers/application/recMech/recConfigTable/recConfigEntry/recConfigSamplePeriod
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/protocols/layers/application/recMech/recConfigTable/recConfigEntry/recConfigSamplePeriod
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/Protocols/layers/application/recMech/recConfigTable/recConfigEntry/recConfigSamplePeriod
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/protocols/layers/application/recMech/recConfigTable/recConfigEntry/recConfigSamplePeriod
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/Protocols/layers/application/recMech/recConfigTable/recConfigEntry/recConfigSamplePeriod
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/protocols/layers/application/recMech/recConfigTable/recConfigEntry/recConfigSamplePeriod
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/Protocols/layers/application/recMech/recConfigTable/recConfigEntry/recConfigSamplePeriod
  • /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/protocols/layers/application/recMech/recConfigTable/recConfigEntry/recConfigSamplePeriod
  • /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/Protocols/layers/application/recMech/recConfigTable/recConfigEntry/recConfigSamplePeriod
  • /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/protocols/layers/application/recMech/recConfigTable/recConfigEntry/recConfigSamplePeriod
  • /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/Protocols/layers/application/recMech/recConfigTable/recConfigEntry/recConfigSamplePeriod
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER, Integer32
Units
0.1 milliseconds
Maximum access defined by MIB
read-write
Status in MIB
mandatory, deprecated
Default value
1000

Definitions may combine these properties differently.

Compare 2 source variants

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

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
mandatory
Default value
1000
Allowed ranges
0–65535

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

Value type
Integer32
Units
0.1 milliseconds
Maximum access defined by MIB
read-write
Status in MIB
deprecated
Default value
1000
Allowed ranges
0–65535

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 recConfigID is declared as Integer32. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.1206.4.1.1.7.9.7.1.9.<recConfigID>. Use an index value actually 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.7.1.9

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

recConfigSamplePeriod · mandatory

recConfigSamplePeriod OBJECT-TYPE
   SYNTAX INTEGER (0..65535)
   ACCESS read-write
   STATUS mandatory
   DESCRIPTION
        "<Definition> This object contains the sample period for recordings
           collected at specified by this configuration. The sample period is
           expressed in units of 0.1 milliseconds. Allowable sample periods
           are restricted to a value of zero (0) or
               (recMinSamplePeriod + recSamplePeriodResolution * n)
           where n is integer, 0 <= n, and
           n <= (recMaxSamplePeriod-recMinSamplePeriod)/recSamplePeriodResolution
            If the value is zero (0), then the samples are not collected on a
            periodic basis, but rather a new sample is collected whenever the
            value of the object specified by recConfigSampleOID changes (i.e.
            similar to event log ‘on-change’ mode). A set to any other value
            results in a badValue response.
          <Object Identifier> 1.3.6.1.4.1. 1206.4.1.1.7.9.7.1.9
        "
   DEFVAL {1000}
::= { recConfigEntry 9 }

recConfigSamplePeriod · deprecated

recConfigSamplePeriod OBJECT-TYPE
SYNTAX       Integer32 (0..65535)
UNITS        "0.1 milliseconds"
MAX-ACCESS read-write
STATUS       deprecated
DESCRIPTION
   "<Definition> This object contains the sample period for recordings
   collected at specified by this configuration. The sample period is
   expressed in units of 0.1 milliseconds. Allowable sample periods are
   restricted to a value of zero (0) or
   (recMinSamplePeriod + recSamplePeriodResolution * n)
   where n is integer, 0 <= n, and n <= (recMaxSamplePeriod-
   recMinSamplePeriod)/recSamplePeriodResolution If the value is zero (0),
   then the samples are not collected on a periodic basis, but rather a new
   sample is collected whenever the value of the object specified by
   recConfigSampleOID changes (i.e. similar to event log 'on-change' mode). A
   set to any other value results in a badValue response.
  <Supplanted by> ISO26048-1-Recording.fdRecordingFactorySamplePeriod
  <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.9"
DEFVAL     { 1000 }
::= { recConfigEntry 9 }

recConfigSamplePeriod · deprecated

recConfigSamplePeriod  OBJECT-TYPE
  SYNTAX      Integer32 (0..65535)
  UNITS       "0.1 milliseconds"
  MAX-ACCESS  read-write
  STATUS      deprecated
  DESCRIPTION
    "<Definition> This object contains the sample period for recordings
      collected at specified by this configuration. The sample period is
      expressed in units of 0.1 milliseconds. Allowable sample periods
      are restricted to a value of zero (0) or 
            (recMinSamplePeriod + recSamplePeriodResolution * n)
      where  n is integer, 0 <= n, and 
      n <= (recMaxSamplePeriod-recMinSamplePeriod)/recSamplePeriodResolution
      If the value is zero (0), then the samples are not collected on a
      periodic basis, but rather a new sample is collected whenever the
      value of the object specified by recConfigSampleOID changes (i.e.
      similar to event log 'on-change' mode). A set to any other value
      results in a badValue response.
    <Superseded by> NTCIP1201-RecMechV2.recMechV2FactorySamplePeriod 
    <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.9"
   DEFVAL  {1000}
::= { recConfigEntry 9 }

Meaning

Descriptions

3 unique

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

Description 1

<Definition> This object contains the sample period for recordings collected at specified by this configuration. The sample period is expressed in units of 0.1 milliseconds. Allowable sample periods are restricted to a value of zero (0) or (recMinSamplePeriod + recSamplePeriodResolution * n) where n is integer, 0 <= n, and n <= (recMaxSamplePeriod-recMinSamplePeriod)/recSamplePeriodResolution If the value is zero (0), then the samples are not collected on a periodic basis, but rather a new sample is collected whenever the value of the object specified by recConfigSampleOID changes (i.e. similar to event log ‘on-change’ mode). A set to any other value results in a badValue response. <Object Identifier> 1.3.6.1.4.1. 1206.4.1.1.7.9.7.1.9

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 2

<Definition> This object contains the sample period for recordings collected at specified by this configuration. The sample period is expressed in units of 0.1 milliseconds. Allowable sample periods are restricted to a value of zero (0) or (recMinSamplePeriod + recSamplePeriodResolution * n) where n is integer, 0 <= n, and n <= (recMaxSamplePeriod- recMinSamplePeriod)/recSamplePeriodResolution If the value is zero (0), then the samples are not collected on a periodic basis, but rather a new sample is collected whenever the value of the object specified by recConfigSampleOID changes (i.e. similar to event log 'on-change' mode). A set to any other value results in a badValue response. <Supplanted by> ISO26048-1-Recording.fdRecordingFactorySamplePeriod <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.9

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 3

<Definition> This object contains the sample period for recordings collected at specified by this configuration. The sample period is expressed in units of 0.1 milliseconds. Allowable sample periods are restricted to a value of zero (0) or (recMinSamplePeriod + recSamplePeriodResolution * n) where n is integer, 0 <= n, and n <= (recMaxSamplePeriod-recMinSamplePeriod)/recSamplePeriodResolution If the value is zero (0), then the samples are not collected on a periodic basis, but rather a new sample is collected whenever the value of the object specified by recConfigSampleOID changes (i.e. similar to event log 'on-change' mode). A set to any other value results in a badValue response. <Superseded by> NTCIP1201-RecMechV2.recMechV2FactorySamplePeriod <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.9

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

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

Status in source: mandatory.

Names: recConfigSamplePeriod

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "recConfigSamplePeriod",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "0",
    ".",
    ".",
    "65535",
    ")",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> This object contains the sample period for recordings collected at specified by this configuration. The sample period is expressed in units of 0.1 milliseconds. Allowable sample periods are restricted to a value of zero (0) or (recMinSamplePeriod + recSamplePeriodResolution * n) where n is integer, 0 <= n, and n <= (recMaxSamplePeriod-recMinSamplePeriod)/recSamplePeriodResolution If the value is zero (0), then the samples are not collected on a periodic basis, but rather a new sample is collected whenever the value of the object specified by recConfigSampleOID changes (i.e. similar to event log ‘on-change’ mode). A set to any other value results in a badValue response. <Object Identifier> 1.3.6.1.4.1. 1206.4.1.1.7.9.7.1.9 \"",
    "DEFVAL",
    "{",
    "1000",
    "}",
    "::=",
    "{",
    "recConfigEntry",
    "9",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            0,
            65535
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> This object contains the sample period for recordings collected at specified by this configuration. The sample period is expressed in units of 0.1 milliseconds. Allowable sample periods are restricted to a value of zero (0) or (recMinSamplePeriod + recSamplePeriodResolution * n) where n is integer, 0 <= n, and n <= (recMaxSamplePeriod-recMinSamplePeriod)/recSamplePeriodResolution If the value is zero (0), then the samples are not collected on a periodic basis, but rather a new sample is collected whenever the value of the object specified by recConfigSampleOID changes (i.e. similar to event log ‘on-change’ mode). A set to any other value results in a badValue response. <Object Identifier> 1.3.6.1.4.1. 1206.4.1.1.7.9.7.1.9"
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      1000
    ]
  ]
}
Records for description 2NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 2

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

Status in source: deprecated.

Names: recConfigSamplePeriod

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "recConfigSamplePeriod",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "0",
    ".",
    ".",
    "65535",
    ")",
    "UNITS",
    [
      "literal",
      "22302e31206d696c6c697365636f6e647322"
    ],
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition> This object contains the sample period for recordings collected at specified by this configuration. The sample period is expressed in units of 0.1 milliseconds. Allowable sample periods are restricted to a value of zero (0) or (recMinSamplePeriod + recSamplePeriodResolution * n) where n is integer, 0 <= n, and n <= (recMaxSamplePeriod- recMinSamplePeriod)/recSamplePeriodResolution If the value is zero (0), then the samples are not collected on a periodic basis, but rather a new sample is collected whenever the value of the object specified by recConfigSampleOID changes (i.e. similar to event log 'on-change' mode). A set to any other value results in a badValue response. <Supplanted by> ISO26048-1-Recording.fdRecordingFactorySamplePeriod <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.9\"",
    "DEFVAL",
    "{",
    "1000",
    "}",
    "::=",
    "{",
    "recConfigEntry",
    "9",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            0,
            65535
          ]
        ]
      ]
    ],
    [
      "UNITS",
      "0.1 milliseconds"
    ],
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition> This object contains the sample period for recordings collected at specified by this configuration. The sample period is expressed in units of 0.1 milliseconds. Allowable sample periods are restricted to a value of zero (0) or (recMinSamplePeriod + recSamplePeriodResolution * n) where n is integer, 0 <= n, and n <= (recMaxSamplePeriod- recMinSamplePeriod)/recSamplePeriodResolution If the value is zero (0), then the samples are not collected on a periodic basis, but rather a new sample is collected whenever the value of the object specified by recConfigSampleOID changes (i.e. similar to event log 'on-change' mode). A set to any other value results in a badValue response. <Supplanted by> ISO26048-1-Recording.fdRecordingFactorySamplePeriod <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.9"
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      1000
    ]
  ]
}
Records for description 3ITE public NTCIP working repository MIBs1 record · 2 sources

Description 3

recConfigSamplePeriod · deprecatedITE public NTCIP working repository MIBs2 sources

Status in source: deprecated.

Names: recConfigSamplePeriod

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "recConfigSamplePeriod",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "0",
    ".",
    ".",
    "65535",
    ")",
    "UNITS",
    [
      "literal",
      "22302e31206d696c6c697365636f6e647322"
    ],
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition> This object contains the sample period for recordings collected at specified by this configuration. The sample period is expressed in units of 0.1 milliseconds. Allowable sample periods are restricted to a value of zero (0) or (recMinSamplePeriod + recSamplePeriodResolution * n) where n is integer, 0 <= n, and n <= (recMaxSamplePeriod-recMinSamplePeriod)/recSamplePeriodResolution If the value is zero (0), then the samples are not collected on a periodic basis, but rather a new sample is collected whenever the value of the object specified by recConfigSampleOID changes (i.e. similar to event log 'on-change' mode). A set to any other value results in a badValue response. <Superseded by> NTCIP1201-RecMechV2.recMechV2FactorySamplePeriod <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.9\"",
    "DEFVAL",
    "{",
    "1000",
    "}",
    "::=",
    "{",
    "recConfigEntry",
    "9",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            0,
            65535
          ]
        ]
      ]
    ],
    [
      "UNITS",
      "0.1 milliseconds"
    ],
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition> This object contains the sample period for recordings collected at specified by this configuration. The sample period is expressed in units of 0.1 milliseconds. Allowable sample periods are restricted to a value of zero (0) or (recMinSamplePeriod + recSamplePeriodResolution * n) where n is integer, 0 <= n, and n <= (recMaxSamplePeriod-recMinSamplePeriod)/recSamplePeriodResolution If the value is zero (0), then the samples are not collected on a periodic basis, but rather a new sample is collected whenever the value of the object specified by recConfigSampleOID changes (i.e. similar to event log 'on-change' mode). A set to any other value results in a badValue response. <Superseded by> NTCIP1201-RecMechV2.recMechV2FactorySamplePeriod <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.9"
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      1000
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (12)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.1.1.7.9.7.1.1 recConfigID00
1.3.6.1.4.1.1206.4.1.1.7.9.7.1.2 recConfigClass00
1.3.6.1.4.1.1206.4.1.1.7.9.7.1.3 recConfigMode00
1.3.6.1.4.1.1206.4.1.1.7.9.7.1.4 recConfigCompareValue00
1.3.6.1.4.1.1206.4.1.1.7.9.7.1.5 recConfigCompareValue200
1.3.6.1.4.1.1206.4.1.1.7.9.7.1.6 recConfigCompareOID00
1.3.6.1.4.1.1206.4.1.1.7.9.7.1.7 recConfigRecordOID00
1.3.6.1.4.1.1206.4.1.1.7.9.7.1.8 recConfigTriggerPoint00
1.3.6.1.4.1.1206.4.1.1.7.9.7.1.10 recConfigSampleOID00
1.3.6.1.4.1.1206.4.1.1.7.9.7.1.11 recConfigNumEntries00
1.3.6.1.4.1.1206.4.1.1.7.9.7.1.12 recConfigAction00
1.3.6.1.4.1.1206.4.1.1.7.9.7.1.13 recConfigStatus00