CHECK-MIB :: checkResultRowStatus

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CHECK-MIB › checkResultRowStatus

checkResultRowStatus

Module: CHECK-MIB

OID (symbolic): CHECK-MIB::checkResultRowStatus

OID (numeric): 1.3.6.1.2.1.7777.1.3.1.8

Node type: OBJECT-TYPE

Type: RowStatus

Access: read-create

Description: This object allows to create and delete rows in the table. 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 checkResultRowStatus has the notInService(2) value and set operations on objects of a row in active(1) status result to inconsistentValue. A change of the value of the checkResultRowStatus object is propagated to the checkRuleRowStatus of all the related entries in the checkRuleTable (those indexed by the same checkResultName); if the change of the value of a checkRuleRowStatus object results in an inconsistentValue error, then this error is returned to the manager while setting the value of this checkResultRowStatus.

An attempt to set the value of this object to active(1), causes the following actions: - all the related entries in the checkRuleTable become active; if an attempt to activate an entry results in an inconsistentValue error, then this error is returned to the manager and further action is taken; - all the objects of this row become read-only, with the exception of checkResultRowStatus; - if the value of checkResultInterval is greater than 0, then the timer to schedule the performances of the check starts immediately, but the first check will be performed only but after the time specified by checkResultInterval; for rules defining delta operations the values of managed objects to be checked are read immediately, so that delta operations can be computed at the first scheduled check. - if the value of checkResultInterval is equal to 0, then retrieving the value of checkResultSeverity forces the performance of the check. When a row is put in the notInService status, then the following actions are taken: - all the objects of the row marked as read-create can be modified; - all the related entries in the checkRuleTable become notInService; - all scheduled future checks are canceled. - retrieving the value of checkResultSeverity returns always the value computed at the last check. When a row is deleted, then if an alarm was configured, it is removed, and all the related entries in checkRuleTable are deleted (eventually freeing the resources allocated for delta operations defined by those rules).

Creating a new row when the table reached the maximum number of entries defined in checkCapabMaxResults results in a resourceUnavailable error.

What is checkResultRowStatus?

This object creates and deletes rows in the check result table, with the specific restriction that createAndGo(4) is disallowed, returning wrongValue, so checks must be built up gradually through notInService before being activated, and rows can only be edited while notInService since editing an active(1) row's objects triggers an inconsistentValue error. An admin scripting automated check provisioning needs to respect this create-then-activate sequence rather than trying to one-shot a new check into service, since attempting createAndGo will simply fail outright on this particular implementation. To add a new check, an admin's script must create the row with createAndWait, configure all the check's parameters while it's notInService, and only then set this object to active(1) to bring it live.

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