CHECK-MIB :: checkResultInterval

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CHECK-MIB › checkResultInterval

checkResultInterval

Module: CHECK-MIB

OID (symbolic): CHECK-MIB::checkResultInterval

OID (numeric): 1.3.6.1.2.1.7777.1.3.1.5

Node type: OBJECT-TYPE

Type: TimeInterval

Access: read-create

Description: The interval between two performances of the check defined in this row.

When this object is set to a value greater than 0, then the check is performed regularly with the number of centi-seconds indicated by this object between two performances. When this object is successfully set to a value greater than 0, then the check is not performed immediately. The first check is performed after the number of centi-seconds specified by the new value of the object. If a performance is scheduled to start before the previous one has been completed, then the previous check will be completed and the scheduled check will be skipped.

If the number of this object is 0, then the check is performed only on request when the value of the object checkResultSeverity is retrieved by a manager.

A set operation on this object may lead to an inconsistentValue error in two cases: - if the vale passed is greater than 0 but less than the value of checkCapabMinCheckInterval; - if the value passed is greater than 0 and the check defined in this row includes rules with delta operations.

What is checkResultInterval?

This object sets how often, in centi-seconds, this specific check is re-run; setting it above 0 schedules recurring checks spaced by that interval, and per the description the very first run after setting this doesn't happen immediately but only after that interval elapses. An admin should account for that initial-delay behavior when configuring a new check, since expecting an immediate first result right after activating a check would be a mistake given the object's description explicitly says the first run is deferred by the full interval. Setting this object to 3000 (30 seconds) on a newly created check means the admin should expect the first actual check result only 30 seconds after activation, not instantly.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
1.3.6.1.2.1.7777ahcfMIBAHCF-MIB
1.3.6.1.2.1.7777.1ahcfObjectsAHCF-MIB
1.3.6.1.2.1.7777.1.3ahcfSampleTableAHCF-MIB
1.3.6.1.2.1.7777.1.3.1ahcfSampleEntryAHCF-MIB
Numeric OIDNameModule
1.3.6.1.2.1.7777.1.3.1.5checkResultIntervalCHECK-MIB