SEE-MIB :: seeTaskControlNumExecOks

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › SEE-MIB › seeTaskControlNumExecOks

seeTaskControlNumExecOks

Module: SEE-MIB

OID (symbolic): SEE-MIB::seeTaskControlNumExecOks

OID (numeric): 1.3.6.1.4.1.99999.61.1.3.1.1.21

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: This counter is incremented by one, each time the script associated with this control entry is executed, and completed with a return status of 'noError'.

What is seeTaskControlNumExecOks?

This counts how many times this task's script has run to completion with a noError result. Admins use it as the primary health metric for a scheduled or event-driven script, watching for it to keep climbing as expected.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.99999.61.1.3.1.1.21
snmpwalk -v2c -c public <target> SEE-MIB::seeTaskControlNumExecOks

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.99999.61.1.3.1.1.21.1
snmpget -v2c -c public <target> SEE-MIB::seeTaskControlNumExecOks.1

Start monitoring Cisco routers and switches with embedded scripting, Script Execution Environment/Tcl (script task status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the SEE-MIB::seeTaskControlNumExecOks OID value, configure state conditions and alerts, and monitor any Cisco routers and switches with embedded scripting, Script Execution Environment/Tcl (script task status) from a single console.

How to Use in IPNetwork Monitor

Select a Cisco routers and switches with embedded scripting, Script Execution Environment/Tcl (script task status) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type seeTaskControlNumExecOks into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. This counter is incremented by one, each time the script associated with this control entry is executed, and completed with a return status of 'noError'. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (7 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.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.99999iec624392IEC-62439-2-MIB
Numeric OIDNameModule
1.3.6.1.4.1.99999.61seeMIBSEE-MIB
1.3.6.1.4.1.99999.61.1seeMibObjectsSEE-MIB
1.3.6.1.4.1.99999.61.1.3seeExecObjectsSEE-MIB
1.3.6.1.4.1.99999.61.1.3.1seeTaskControlTableSEE-MIB
1.3.6.1.4.1.99999.61.1.3.1.1seeTaskControlEntrySEE-MIB
1.3.6.1.4.1.99999.61.1.3.1.1.21seeTaskControlNumExecOksSEE-MIB