OID reference

recConfigTriggerPoint

1.3.6.1.4.1.1206.4.1.1.7.9.7.1.8

Description

<Definition> This object contains the value of the recording trigger point in percent relative to the recConfigNumEntries. The device needs to collect pre-event records prior to the trigger occurring and ends the recording after recConfigNumEntries have been recorded. A value of zero (0) means to start the recording o…

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
8
Node name
recConfigTriggerPoint
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.1.1.7.9.7.1.8
URN notation
urn:oid:1.3.6.1.4.1.1206.4.1.1.7.9.7.1.8
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 8}

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

SNMP properties

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

Definitions may combine these properties differently.

Compare 2 source variants

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

Value type
Integer32
Units
percent
Maximum access defined by MIB
read-write
Status in MIB
deprecated
Default value
80
Allowed ranges
0–100

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

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

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.8.<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.8

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

recConfigTriggerPoint · deprecated

recConfigTriggerPoint  OBJECT-TYPE
  SYNTAX      Integer32 (0..100)
  UNITS       "percent"
  MAX-ACCESS  read-write
  STATUS      deprecated
  DESCRIPTION
    "<Definition> This object contains the value of the recording
      trigger point in percent relative to the recConfigNumEntries.
      The device needs to collect pre-event records prior to the trigger
      occurring and ends the recording after recConfigNumEntries have
      been recorded. A value of zero (0) means to start the recording once
      the trigger condition occurs whereas a value of 100 means to stop
      the recording with the last record being the one collected
      immediately following the trigger condition occurring. If the trigger
      point is less than 100 then at least one record entry needs to occur 
      after the trigger point.
    <Superseded by> NTCIP1201-RecMechV2.recMechV2FactoryPreSamples 
    <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.8"
   DEFVAL  {80}
::= { recConfigEntry 8 }

recConfigTriggerPoint · deprecated

recConfigTriggerPoint OBJECT-TYPE
SYNTAX       Integer32 (0..100)
UNITS        "percent"
MAX-ACCESS read-write
STATUS       deprecated
DESCRIPTION
   "<Definition> This object contains the value of the recording trigger point
   in percent relative to the recConfigNumEntries. The device needs to collect
   pre-event records prior to the trigger occurring and ends the recording
   after recConfigNumEntries have been recorded. A value of zero (0) means to
   start the recording once the trigger condition occurs whereas a value of
   100 means to stop the recording with the last record being the one
   collected immediately following the trigger condition occurring. If the
   trigger point is less than 100 then at least one record entry needs to
   occur after the trigger point.
  <Supplanted by> ISO26048-1-Recording.fdRecordingFactoryPreSamples
  <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.8"
DEFVAL     { 80 }
::= { recConfigEntry 8 }

recConfigTriggerPoint · mandatory

recConfigTriggerPoint OBJECT-TYPE
   SYNTAX INTEGER (0..100)
   ACCESS read-write
   STATUS mandatory
   DESCRIPTION
        "<Definition> This object contains the value of the recording
           trigger point in percent relative to the recConfigNumEntries.
           The device needs to collect pre-event records prior to the trigger
           occurring and ends the recording after recConfigNumEntries have
           been recorded. A value of zero (0) means to start the recording once
           the trigger condition occurs whereas a value of 100 means to stop
           the recording with the last record being the one collected
           immediately following the trigger condition occurring. If the trigger



                                                                                             

                 
        

         point is less than 100 then at least one record entry needs to occur
after the
         trigger point.
        <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.8
      "
   DEFVAL {80}
::= { recConfigEntry 8 }

Meaning

Descriptions

3 unique

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

Description 1

<Definition> This object contains the value of the recording trigger point in percent relative to the recConfigNumEntries. The device needs to collect pre-event records prior to the trigger occurring and ends the recording after recConfigNumEntries have been recorded. A value of zero (0) means to start the recording once the trigger condition occurs whereas a value of 100 means to stop the recording with the last record being the one collected immediately following the trigger condition occurring. If the trigger point is less than 100 then at least one record entry needs to occur after the trigger point. <Superseded by> NTCIP1201-RecMechV2.recMechV2FactoryPreSamples <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.8

Sources for this description

ITE public NTCIP working repository MIBs

See 1 matching source record

Description 2

<Definition> This object contains the value of the recording trigger point in percent relative to the recConfigNumEntries. The device needs to collect pre-event records prior to the trigger occurring and ends the recording after recConfigNumEntries have been recorded. A value of zero (0) means to start the recording once the trigger condition occurs whereas a value of 100 means to stop the recording with the last record being the one collected immediately following the trigger condition occurring. If the trigger point is less than 100 then at least one record entry needs to occur after the trigger point. <Supplanted by> ISO26048-1-Recording.fdRecordingFactoryPreSamples <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.8

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 3

<Definition> This object contains the value of the recording trigger point in percent relative to the recConfigNumEntries. The device needs to collect pre-event records prior to the trigger occurring and ends the recording after recConfigNumEntries have been recorded. A value of zero (0) means to start the recording once the trigger condition occurs whereas a value of 100 means to stop the recording with the last record being the one collected immediately following the trigger condition occurring. If the trigger point is less than 100 then at least one record entry needs to occur after the trigger point. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.8

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

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 1ITE public NTCIP working repository MIBs1 record · 2 sources

Description 1

recConfigTriggerPoint · deprecatedITE public NTCIP working repository MIBs2 sources

Status in source: deprecated.

Names: recConfigTriggerPoint

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "recConfigTriggerPoint",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "0",
    ".",
    ".",
    "100",
    ")",
    "UNITS",
    [
      "literal",
      "2270657263656e7422"
    ],
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition> This object contains the value of the recording trigger point in percent relative to the recConfigNumEntries. The device needs to collect pre-event records prior to the trigger occurring and ends the recording after recConfigNumEntries have been recorded. A value of zero (0) means to start the recording once the trigger condition occurs whereas a value of 100 means to stop the recording with the last record being the one collected immediately following the trigger condition occurring. If the trigger point is less than 100 then at least one record entry needs to occur after the trigger point. <Superseded by> NTCIP1201-RecMechV2.recMechV2FactoryPreSamples <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.8\"",
    "DEFVAL",
    "{",
    "80",
    "}",
    "::=",
    "{",
    "recConfigEntry",
    "8",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            0,
            100
          ]
        ]
      ]
    ],
    [
      "UNITS",
      "percent"
    ],
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition> This object contains the value of the recording trigger point in percent relative to the recConfigNumEntries. The device needs to collect pre-event records prior to the trigger occurring and ends the recording after recConfigNumEntries have been recorded. A value of zero (0) means to start the recording once the trigger condition occurs whereas a value of 100 means to stop the recording with the last record being the one collected immediately following the trigger condition occurring. If the trigger point is less than 100 then at least one record entry needs to occur after the trigger point. <Superseded by> NTCIP1201-RecMechV2.recMechV2FactoryPreSamples <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.8"
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      80
    ]
  ]
}
Records for description 2NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 2

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

Status in source: deprecated.

Names: recConfigTriggerPoint

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "recConfigTriggerPoint",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "0",
    ".",
    ".",
    "100",
    ")",
    "UNITS",
    [
      "literal",
      "2270657263656e7422"
    ],
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition> This object contains the value of the recording trigger point in percent relative to the recConfigNumEntries. The device needs to collect pre-event records prior to the trigger occurring and ends the recording after recConfigNumEntries have been recorded. A value of zero (0) means to start the recording once the trigger condition occurs whereas a value of 100 means to stop the recording with the last record being the one collected immediately following the trigger condition occurring. If the trigger point is less than 100 then at least one record entry needs to occur after the trigger point. <Supplanted by> ISO26048-1-Recording.fdRecordingFactoryPreSamples <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.8\"",
    "DEFVAL",
    "{",
    "80",
    "}",
    "::=",
    "{",
    "recConfigEntry",
    "8",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            0,
            100
          ]
        ]
      ]
    ],
    [
      "UNITS",
      "percent"
    ],
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition> This object contains the value of the recording trigger point in percent relative to the recConfigNumEntries. The device needs to collect pre-event records prior to the trigger occurring and ends the recording after recConfigNumEntries have been recorded. A value of zero (0) means to start the recording once the trigger condition occurs whereas a value of 100 means to stop the recording with the last record being the one collected immediately following the trigger condition occurring. If the trigger point is less than 100 then at least one record entry needs to occur after the trigger point. <Supplanted by> ISO26048-1-Recording.fdRecordingFactoryPreSamples <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.8"
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      80
    ]
  ]
}
Records for description 3NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 3

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

Status in source: mandatory.

Names: recConfigTriggerPoint

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "recConfigTriggerPoint",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "0",
    ".",
    ".",
    "100",
    ")",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> This object contains the value of the recording trigger point in percent relative to the recConfigNumEntries. The device needs to collect pre-event records prior to the trigger occurring and ends the recording after recConfigNumEntries have been recorded. A value of zero (0) means to start the recording once the trigger condition occurs whereas a value of 100 means to stop the recording with the last record being the one collected immediately following the trigger condition occurring. If the trigger point is less than 100 then at least one record entry needs to occur after the trigger point. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.8 \"",
    "DEFVAL",
    "{",
    "80",
    "}",
    "::=",
    "{",
    "recConfigEntry",
    "8",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            0,
            100
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> This object contains the value of the recording trigger point in percent relative to the recConfigNumEntries. The device needs to collect pre-event records prior to the trigger occurring and ends the recording after recConfigNumEntries have been recorded. A value of zero (0) means to start the recording once the trigger condition occurs whereas a value of 100 means to stop the recording with the last record being the one collected immediately following the trigger condition occurring. If the trigger point is less than 100 then at least one record entry needs to occur after the trigger point. <Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.8"
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      80
    ]
  ]
}

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.9 recConfigSamplePeriod00
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