OID reference

perfControlEffectiveUpdatePeriod

1.3.6.1.4.1.6368.2.7.2.1.5

Description

If several clients monitor the same V5 link or DSL interface, each sets its own update period. The server then computes the greatest common divisor of all values. For example, if a PEM client wants to have an update every 15 seconds, and the SNMP agent wants an update every 21 seconds, the server will produce updates …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.6368.2.7.2.1 (perfControlEntry)
Node code
5
Node name
perfControlEffectiveUpdatePeriod
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.6368.2.7.2.1.5
URN notation
urn:oid:1.3.6.1.4.1.6368.2.7.2.1.5
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 6368 2 7 2 1 5}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) schmidtelecom(6368) pegasusMibModule(2) perf(7) perfControlTable(2) perfControlEntry(1) perfControlEffectiveUpdatePeriod(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) schmidtelecom(6368) pegasusMibModule(2) perf(7) perfControlTable(2) perfControlEntry(1) perfControlEffectiveUpdatePeriod(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) schmidtelecom(6368) pegasusMibModule(2) perf(7) perfControlTable(2) perfControlEntry(1) perfControlEffectiveUpdatePeriod(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) schmidtelecom(6368) pegasusMibModule(2) perf(7) perfControlTable(2) perfControlEntry(1) perfControlEffectiveUpdatePeriod(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) schmidtelecom(6368) pegasusMibModule(2) perf(7) perfControlTable(2) perfControlEntry(1) perfControlEffectiveUpdatePeriod(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) schmidtelecom(6368) pegasusMibModule(2) perf(7) perfControlTable(2) perfControlEntry(1) perfControlEffectiveUpdatePeriod(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) schmidtelecom(6368) pegasusMibModule(2) perf(7) perfControlTable(2) perfControlEntry(1) perfControlEffectiveUpdatePeriod(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) schmidtelecom(6368) pegasusMibModule(2) perf(7) perfControlTable(2) perfControlEntry(1) perfControlEffectiveUpdatePeriod(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) schmidtelecom(6368) pegasusMibModule(2) perf(7) perfControlTable(2) perfControlEntry(1) perfControlEffectiveUpdatePeriod(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) schmidtelecom(6368) pegasusMibModule(2) perf(7) perfControlTable(2) perfControlEntry(1) perfControlEffectiveUpdatePeriod(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) schmidtelecom(6368) pegasusMibModule(2) perf(7) perfControlTable(2) perfControlEntry(1) perfControlEffectiveUpdatePeriod(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) schmidtelecom(6368) pegasusMibModule(2) perf(7) perfControlTable(2) perfControlEntry(1) perfControlEffectiveUpdatePeriod(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) schmidtelecom(6368) pegasusMibModule(2) perf(7) perfControlTable(2) perfControlEntry(1) perfControlEffectiveUpdatePeriod(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) schmidtelecom(6368) pegasusMibModule(2) perf(7) perfControlTable(2) perfControlEntry(1) perfControlEffectiveUpdatePeriod(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) schmidtelecom(6368) pegasusMibModule(2) perf(7) perfControlTable(2) perfControlEntry(1) perfControlEffectiveUpdatePeriod(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) schmidtelecom(6368) pegasusMibModule(2) perf(7) perfControlTable(2) perfControlEntry(1) perfControlEffectiveUpdatePeriod(5)}
OID-IRI notation
  • /1/3/6/1/4/1/6368/2/7/2/1/5
  • /ISO/Identified-Organization/6/1/4/1/6368/2/7/2/1/5
  • /ISO/3/6/1/4/1/6368/2/7/2/1/5
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/6368/pegasusMibModule/perf/perfControlTable/perfControlEntry/perfControlEffectiveUpdatePeriod
  • /iso/identified-organization/dod/internet/private/enterprise/schmidtelecom/pegasusMibModule/perf/perfControlTable/perfControlEntry/perfControlEffectiveUpdatePeriod
  • /iso/identified-organization/dod/internet/private/enterprises/6368/pegasusMibModule/perf/perfControlTable/perfControlEntry/perfControlEffectiveUpdatePeriod
  • /iso/identified-organization/dod/internet/private/enterprises/schmidtelecom/pegasusMibModule/perf/perfControlTable/perfControlEntry/perfControlEffectiveUpdatePeriod
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/6368/pegasusMibModule/perf/perfControlTable/perfControlEntry/perfControlEffectiveUpdatePeriod
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/schmidtelecom/pegasusMibModule/perf/perfControlTable/perfControlEntry/perfControlEffectiveUpdatePeriod
  • /iso/identified-organization/dod/internet/private/vendor-objects/6368/pegasusMibModule/perf/perfControlTable/perfControlEntry/perfControlEffectiveUpdatePeriod
  • /iso/identified-organization/dod/internet/private/vendor-objects/schmidtelecom/pegasusMibModule/perf/perfControlTable/perfControlEntry/perfControlEffectiveUpdatePeriod
  • /iso/org/dod/internet/private/enterprise/6368/pegasusMibModule/perf/perfControlTable/perfControlEntry/perfControlEffectiveUpdatePeriod
  • /iso/org/dod/internet/private/enterprise/schmidtelecom/pegasusMibModule/perf/perfControlTable/perfControlEntry/perfControlEffectiveUpdatePeriod
  • /iso/org/dod/internet/private/enterprises/6368/pegasusMibModule/perf/perfControlTable/perfControlEntry/perfControlEffectiveUpdatePeriod
  • /iso/org/dod/internet/private/enterprises/schmidtelecom/pegasusMibModule/perf/perfControlTable/perfControlEntry/perfControlEffectiveUpdatePeriod
  • /iso/org/dod/internet/private/ldap-enterprise/6368/pegasusMibModule/perf/perfControlTable/perfControlEntry/perfControlEffectiveUpdatePeriod
  • /iso/org/dod/internet/private/ldap-enterprise/schmidtelecom/pegasusMibModule/perf/perfControlTable/perfControlEntry/perfControlEffectiveUpdatePeriod
  • /iso/org/dod/internet/private/vendor-objects/6368/pegasusMibModule/perf/perfControlTable/perfControlEntry/perfControlEffectiveUpdatePeriod
  • /iso/org/dod/internet/private/vendor-objects/schmidtelecom/pegasusMibModule/perf/perfControlTable/perfControlEntry/perfControlEffectiveUpdatePeriod
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-only
Status in MIB
obsolete
Allowed ranges
0–180

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 PEGASUS-MIB, the row index perfControlIndex 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.6368.2.7.2.1.5.<perfControlIndex>. 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.6368.2.7.2.1.5

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.

perfControlEffectiveUpdatePeriod OBJECT-TYPE
  SYNTAX      INTEGER(0..180)
  MAX-ACCESS  read-only
  STATUS      obsolete
  DESCRIPTION
      "If several clients monitor the same V5 link or DSL interface, each sets
      its own update period. The server then computes the greatest common
      divisor of all values. For example, if a PEM client wants to have an
      update every 15 seconds, and the SNMP agent wants an update every 21
      seconds, the server will produce updates every 3 seconds (15=3*5,
      21=3*7). The subsequence of every fifth update than has a period of 15
      seconds, and the subsequence of every seventh has a period of 21 seconds."
  ::= { perfControlEntry 5 }

Meaning

Descriptions

1 unique

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

If several clients monitor the same V5 link or DSL interface, each sets its own update period. The server then computes the greatest common divisor of all values. For example, if a PEM client wants to have an update every 15 seconds, and the SNMP agent wants an update every 21 seconds, the server will produce updates every 3 seconds (15=3*5, 21=3*7). The subsequence of every fifth update than has a period of 15 seconds, and the subsequence of every seventh has a period of 21 seconds.

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

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

Status in source: obsolete.

Names: perfControlEffectiveUpdatePeriod

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "perfControlEffectiveUpdatePeriod",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "0",
    ".",
    ".",
    "180",
    ")",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "obsolete",
    "DESCRIPTION",
    "\"If several clients monitor the same V5 link or DSL interface, each sets its own update period. The server then computes the greatest common divisor of all values. For example, if a PEM client wants to have an update every 15 seconds, and the SNMP agent wants an update every 21 seconds, the server will produce updates every 3 seconds (15=3*5, 21=3*7). The subsequence of every fifth update than has a period of 15 seconds, and the subsequence of every seventh has a period of 21 seconds.\"",
    "::=",
    "{",
    "perfControlEntry",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            0,
            180
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "obsolete"
    ],
    [
      "DESCRIPTION",
      "If several clients monitor the same V5 link or DSL interface, each sets its own update period. The server then computes the greatest common divisor of all values. For example, if a PEM client wants to have an update every 15 seconds, and the SNMP agent wants an update every 21 seconds, the server will produce updates every 3 seconds (15=3*5, 21=3*7). The subsequence of every fifth update than has a period of 15 seconds, and the subsequence of every seventh has a period of 21 seconds."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.6368)

Poltera Gian Lucas

Siblings (5)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.6368.2.7.2.1.1 perfControlIndex00
1.3.6.1.4.1.6368.2.7.2.1.2 perfControlStatus00
1.3.6.1.4.1.6368.2.7.2.1.3 perfControlLinkDescr00
1.3.6.1.4.1.6368.2.7.2.1.4 perfControlUpdatePeriod00
1.3.6.1.4.1.6368.2.7.2.1.6 perfControlRowStatus00