CHECK-MIB :: checkRuleRowStatus

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CHECK-MIB › checkRuleRowStatus

checkRuleRowStatus

Module: CHECK-MIB

OID (symbolic): CHECK-MIB::checkRuleRowStatus

OID (numeric): 1.3.6.1.2.1.7777.1.4.1.7

Node type: OBJECT-TYPE

Type: RowStatus

Access: read-create

Description: The control to create and delete rows. It is possible to create new rules only for a check which is already defined in the CHECK-MIB. Creating a new row indexed by a value of checkResultName which doesn't exist already in any row of the checkResultTable results in a inconsistentName error. The value createAndGo(4) is not allowed and an wrongValue error is returned when attempting to set it.

Objects of the same row can be modified only when checkRuleRowStatus has the notInService(2) value and set operations on objects of a row in active(1) status result to inconsistentValue. A row in the notInService status is not considered in the performance of the check defined by the related entry in the checkResultTable (the one indexed by the same checkResultName).

An attempt to set the value of this object to active(1), causes the following actions: - the validity of the value of checkRuleOid is verified; if it fails, then an inconsistentValue error is returned; - the consistency between the type of the object referenced by checkRuleOid and the value of checkRuleOperation is verified; if it fails, then an inconsistentValue error is returned; - the consistency between the type of the object referenced by checkRuleOid and the value of checkRuleValue is verified; if it fails, then an inconsistentValue error is returned; - if all the tests pass, the row is activated.

An attempt to create a new row when the table has reached the maximum number of entries defined in checkCapabMaxRules results in a resourceUnavailable error. An attempt to create a new row in the table with the corresponding entry in the checkResultTable having the storage type permanent(4) results in an inconsistentValue error.

What is checkRuleRowStatus?

This object creates and deletes rows in the rule table, but only for a check that already exists in checkResultTable; attempting to create a rule indexed by a nonexistent checkResultName produces an inconsistentName error, and createAndGo(4) is likewise disallowed here as in checkResultRowStatus. An admin scripting bulk rule creation must therefore always create the parent check row first before attempting any of its rules, since the ordering dependency is enforced with a specific, identifiable error rather than a generic failure. Attempting to create a rule row referencing a checkResultName of cpuCheck before that check itself exists in checkResultTable would fail with an inconsistentName error rather than silently creating both.

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.4ahcfSysInfoAHCF-MIB
1.3.6.1.2.1.7777.1.4.1ahcfSysTimeAHCF-MIB
Numeric OIDNameModule
1.3.6.1.2.1.7777.1.4.1.7checkRuleRowStatusCHECK-MIB