OID reference

sensorProfileSampleInterval

1.3.6.1.4.1.42229.1.2.19.14.1.1.2

Description

Time in milliseconds between the device's sample of a telemetry data source. For example, setting this to 2000 would require the local device to collect the telemetry data every 2000 milliseconds. There can be latency or jitter in transmitting the data, but the sample must occur at the specified interval. The timestam…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.42229.1.2.19.14.1.1 (sensorProfileEntry)
Node code
2
Node name
sensorProfileSampleInterval
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.42229.1.2.19.14.1.1.2
URN notation
urn:oid:1.3.6.1.4.1.42229.1.2.19.14.1.1.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 42229 1 2 19 14 1 1 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) coriant(42229) products(1) groove(2) telemetry(19) sensorProfile(14) sensorProfileTable(1) sensorProfileEntry(1) sensorProfileSampleInterval(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) coriant(42229) products(1) groove(2) telemetry(19) sensorProfile(14) sensorProfileTable(1) sensorProfileEntry(1) sensorProfileSampleInterval(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) coriant(42229) products(1) groove(2) telemetry(19) sensorProfile(14) sensorProfileTable(1) sensorProfileEntry(1) sensorProfileSampleInterval(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) coriant(42229) products(1) groove(2) telemetry(19) sensorProfile(14) sensorProfileTable(1) sensorProfileEntry(1) sensorProfileSampleInterval(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) coriant(42229) products(1) groove(2) telemetry(19) sensorProfile(14) sensorProfileTable(1) sensorProfileEntry(1) sensorProfileSampleInterval(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) coriant(42229) products(1) groove(2) telemetry(19) sensorProfile(14) sensorProfileTable(1) sensorProfileEntry(1) sensorProfileSampleInterval(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) coriant(42229) products(1) groove(2) telemetry(19) sensorProfile(14) sensorProfileTable(1) sensorProfileEntry(1) sensorProfileSampleInterval(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) coriant(42229) products(1) groove(2) telemetry(19) sensorProfile(14) sensorProfileTable(1) sensorProfileEntry(1) sensorProfileSampleInterval(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) coriant(42229) products(1) groove(2) telemetry(19) sensorProfile(14) sensorProfileTable(1) sensorProfileEntry(1) sensorProfileSampleInterval(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) coriant(42229) products(1) groove(2) telemetry(19) sensorProfile(14) sensorProfileTable(1) sensorProfileEntry(1) sensorProfileSampleInterval(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) coriant(42229) products(1) groove(2) telemetry(19) sensorProfile(14) sensorProfileTable(1) sensorProfileEntry(1) sensorProfileSampleInterval(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) coriant(42229) products(1) groove(2) telemetry(19) sensorProfile(14) sensorProfileTable(1) sensorProfileEntry(1) sensorProfileSampleInterval(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) coriant(42229) products(1) groove(2) telemetry(19) sensorProfile(14) sensorProfileTable(1) sensorProfileEntry(1) sensorProfileSampleInterval(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) coriant(42229) products(1) groove(2) telemetry(19) sensorProfile(14) sensorProfileTable(1) sensorProfileEntry(1) sensorProfileSampleInterval(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) coriant(42229) products(1) groove(2) telemetry(19) sensorProfile(14) sensorProfileTable(1) sensorProfileEntry(1) sensorProfileSampleInterval(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) coriant(42229) products(1) groove(2) telemetry(19) sensorProfile(14) sensorProfileTable(1) sensorProfileEntry(1) sensorProfileSampleInterval(2)}
OID-IRI notation
  • /1/3/6/1/4/1/42229/1/2/19/14/1/1/2
  • /ISO/Identified-Organization/6/1/4/1/42229/1/2/19/14/1/1/2
  • /ISO/3/6/1/4/1/42229/1/2/19/14/1/1/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/42229/products/groove/telemetry/sensorProfile/sensorProfileTable/sensorProfileEntry/sensorProfileSampleInterval
  • /iso/identified-organization/dod/internet/private/enterprise/coriant/products/groove/telemetry/sensorProfile/sensorProfileTable/sensorProfileEntry/sensorProfileSampleInterval
  • /iso/identified-organization/dod/internet/private/enterprises/42229/products/groove/telemetry/sensorProfile/sensorProfileTable/sensorProfileEntry/sensorProfileSampleInterval
  • /iso/identified-organization/dod/internet/private/enterprises/coriant/products/groove/telemetry/sensorProfile/sensorProfileTable/sensorProfileEntry/sensorProfileSampleInterval
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/42229/products/groove/telemetry/sensorProfile/sensorProfileTable/sensorProfileEntry/sensorProfileSampleInterval
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/coriant/products/groove/telemetry/sensorProfile/sensorProfileTable/sensorProfileEntry/sensorProfileSampleInterval
  • /iso/identified-organization/dod/internet/private/vendor-objects/42229/products/groove/telemetry/sensorProfile/sensorProfileTable/sensorProfileEntry/sensorProfileSampleInterval
  • /iso/identified-organization/dod/internet/private/vendor-objects/coriant/products/groove/telemetry/sensorProfile/sensorProfileTable/sensorProfileEntry/sensorProfileSampleInterval
  • /iso/org/dod/internet/private/enterprise/42229/products/groove/telemetry/sensorProfile/sensorProfileTable/sensorProfileEntry/sensorProfileSampleInterval
  • /iso/org/dod/internet/private/enterprise/coriant/products/groove/telemetry/sensorProfile/sensorProfileTable/sensorProfileEntry/sensorProfileSampleInterval
  • /iso/org/dod/internet/private/enterprises/42229/products/groove/telemetry/sensorProfile/sensorProfileTable/sensorProfileEntry/sensorProfileSampleInterval
  • /iso/org/dod/internet/private/enterprises/coriant/products/groove/telemetry/sensorProfile/sensorProfileTable/sensorProfileEntry/sensorProfileSampleInterval
  • /iso/org/dod/internet/private/ldap-enterprise/42229/products/groove/telemetry/sensorProfile/sensorProfileTable/sensorProfileEntry/sensorProfileSampleInterval
  • /iso/org/dod/internet/private/ldap-enterprise/coriant/products/groove/telemetry/sensorProfile/sensorProfileTable/sensorProfileEntry/sensorProfileSampleInterval
  • /iso/org/dod/internet/private/vendor-objects/42229/products/groove/telemetry/sensorProfile/sensorProfileTable/sensorProfileEntry/sensorProfileSampleInterval
  • /iso/org/dod/internet/private/vendor-objects/coriant/products/groove/telemetry/sensorProfile/sensorProfileTable/sensorProfileEntry/sensorProfileSampleInterval
  • Additional combinations skipped.

SNMP properties

Value type
OCTET STRING
Maximum access defined by MIB
read-only
Status in MIB
current

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 CORIANT-GROOVE-MIB, the row index dialOutSubscriptionSubscriptionName is declared as OCTET STRING. The variable-length string is encoded as its number of octets, followed by one numeric subidentifier per octet. 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.42229.1.2.19.14.1.1.2

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.

sensorProfileSampleInterval OBJECT-TYPE
    SYNTAX OCTET STRING 
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION "Time in milliseconds between the device's sample of a
	telemetry data source. For example, setting this to 2000
	would require the local device to collect the telemetry
	data every 2000 milliseconds. There can be latency or jitter
	in transmitting the data, but the sample must occur at
	the specified interval.
	The timestamp must reflect the actual time when the data
	was sampled, not simply the previous sample timestamp +
	sample-interval.
	If sample-interval is set to 0, the telemetry sensor
	becomes event based. The sensor must then emit data upon
	every change of the underlying data source.
		
		UNITS:millisecond
		default value :10000"
::= { sensorProfileEntry 2 }

Meaning

Descriptions

1 unique

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

Time in milliseconds between the device's sample of a telemetry data source. For example, setting this to 2000 would require the local device to collect the telemetry data every 2000 milliseconds. There can be latency or jitter in transmitting the data, but the sample must occur at the specified interval. The timestamp must reflect the actual time when the data was sampled, not simply the previous sample timestamp + sample-interval. If sample-interval is set to 0, the telemetry sensor becomes event based. The sensor must then emit data upon every change of the underlying data source. UNITS:millisecond default value :10000

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

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 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

sensorProfileSampleInterval · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: sensorProfileSampleInterval

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "sensorProfileSampleInterval",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Time in milliseconds between the device's sample of a telemetry data source. For example, setting this to 2000 would require the local device to collect the telemetry data every 2000 milliseconds. There can be latency or jitter in transmitting the data, but the sample must occur at the specified interval. The timestamp must reflect the actual time when the data was sampled, not simply the previous sample timestamp + sample-interval. If sample-interval is set to 0, the telemetry sensor becomes event based. The sensor must then emit data upon every change of the underlying data source. UNITS:millisecond default value :10000\"",
    "::=",
    "{",
    "sensorProfileEntry",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Time in milliseconds between the device's sample of a telemetry data source. For example, setting this to 2000 would require the local device to collect the telemetry data every 2000 milliseconds. There can be latency or jitter in transmitting the data, but the sample must occur at the specified interval. The timestamp must reflect the actual time when the data was sampled, not simply the previous sample timestamp + sample-interval. If sample-interval is set to 0, the telemetry sensor becomes event based. The sensor must then emit data upon every change of the underlying data source. UNITS:millisecond default value :10000"
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.42229)

Peter Litz

Siblings (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.42229.1.2.19.14.1.1.1 sensorProfileSensorGroup00
1.3.6.1.4.1.42229.1.2.19.14.1.1.3 sensorProfileHeartbeatInterval00
1.3.6.1.4.1.42229.1.2.19.14.1.1.4 sensorProfileSuppressRedundant00