TUBS-TNM-MIB :: tnmTclCmdCount

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsTUBS-TNM-MIBtnmTclCmdCount

tnmTclCmdCount

Module: TUBS-TNM-MIB

OID (symbolic): TUBS-TNM-MIB::tnmTclCmdCount

OID (numeric): 1.3.6.1.4.1.1575.1.1.1.3

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The nummber of Tcl statements evaluated so far.

What is tnmTclCmdCount?

This read-only Counter32 tallies how many Tcl statements the embedded interpreter has evaluated so far, a rough activity gauge for how much scripted management logic has run on the agent.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1575.1.1.1.3
snmpwalk -v2c -c public <target> TUBS-TNM-MIB::tnmTclCmdCount

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1575.1.1.1.3.1
snmpget -v2c -c public <target> TUBS-TNM-MIB::tnmTclCmdCount.1

Start monitoring Unix host running a Tcl/Tk (scotty/TNM) based SNMP agent (toolkit version/trap-forwarding/peer status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TUBS-TNM-MIB::tnmTclCmdCount OID value, configure state conditions and alerts, and monitor any Unix host running a Tcl/Tk (scotty/TNM) based SNMP agent (toolkit version/trap-forwarding/peer status) from a single console.

How to Use in IPNetwork Monitor

Select an Unix host running a Tcl/Tk (scotty/TNM) based SNMP agent (toolkit version/trap-forwarding/peer 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 tnmTclCmdCount into the Find box to locate it in the OID tree, then select it and click OK. The nummber of Tcl statements evaluated so far. 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 sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (8 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.1575tubsTUBS-SMI
1.3.6.1.4.1.1575.1ibrTUBS-SMI
Numeric OIDNameModule
1.3.6.1.4.1.1575.1.1tnmMIBTUBS-TNM-MIB
1.3.6.1.4.1.1575.1.1.1tnmStatusTUBS-TNM-MIB
1.3.6.1.4.1.1575.1.1.1.3tnmTclCmdCountTUBS-TNM-MIB