All MIBs › TUBS-TNM-MIB
Organization: TU Braunschweig
Last Updated: 1994-11-15
Category: TU Braunschweig Research MIBs
Description: Manages TU Braunschweig Tcl Network Management toolkit objects for scriptable SNMP operations.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is TUBS-TNM-MIB?
TUBS-TNM-MIB is an experimental MIB module from the Tcl Network Management (TNM) toolkit developed at Technical University of Braunschweig, used by Tcl/Tk-based SNMP agents and management scripts (scotty/TNM) for scriptable network management. It exposes agent/toolkit self-describing information — version identifiers for the TNM toolkit and embedded Tcl interpreter, a command counter, agent date/time, trap-destination and trap-message configuration, HTTP proxy/source/error status, and a peer table describing other TNM-based peers the agent knows about. Its monitoring value is primarily around software/agent status rather than hardware: it lets a manager confirm which TNM/Tcl version an agent is running, track how many Tcl commands it has executed (a rough software-activity/load indicator), verify its trap-forwarding and HTTP-proxy configuration, and enumerate known peer agents and their reachability/status. It is a self-contained, standards-adjacent (SNMPv2-SMI based) experimental MIB not formally dependent on other vendor MIBs, though it is specific to the TNM/scotty toolkit ecosystem. It is typically found in academic/research or legacy Unix network-management environments running Tcl-scripted SNMP agents rather than in commercial production hardware. Engineers can download the TUBS-TNM-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in TUBS-TNM-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Unix host running a Tcl/Tk (scotty/TNM) based SNMP agent
Monitoring Examples
An administrator would poll tnmVersion and tnmTclVersion to confirm which TNM toolkit/Tcl interpreter build an agent is running, check tnmTclCmdCount as a rough measure of scripting activity/load, and query the tnmPeerTable (tnmPeerEntry, tnmPeerTAddress) to see which other TNM agents this one is aware of and their transport addresses; tnmTrapDst/tnmTrapMsg reveal where and what the agent sends as trap notifications, while tnmHttpProxy/tnmHttpSource/tnmHttpError expose its HTTP-proxy configuration and any proxy fetch errors.
What Can Be Monitored
- TNM toolkit and Tcl interpreter version
- Tcl command execution count
- agent date/time
- trap destination and message configuration
- HTTP proxy configuration and errors
- known peer agents and their addresses
Imported Objects
From SNMPv2-SMI
| Counter32 | |
| Integer32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE | |
| TimeTicks | |
| Unsigned32 | |
| enterprises |
From SNMPv2-TC
| DateAndTime | |
| DisplayString | |
| RowStatus | |
| TAddress | |
| TEXTUAL-CONVENTION | |
| TimeStamp | |
| TruthValue |
How to Use in IPNetwork Monitor
Example using tnmTclCmdCount OID:
OIDs
RFC description
TU Braunschweig experimental MIB for tnm (Tcl-based network management) agent status and configuration.
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. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.