TUBS-TNM-MIB

MIB Reference — IPNetwork Monitor

All MIBsTUBS-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.

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

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.

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

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.

OIDs
OID symbolicOID numericTypeAccessDescription
tnmMIB1.3.6.1.4.1.1575.1.1Experimental MIB modules for tnm based agents.
tnmStatus1.3.6.1.4.1.1575.1.1.1
STR tnmVersion1.3.6.1.4.1.1575.1.1.1.1DisplayStringread-onlyThe version number of the tnm agent.
STR tnmTclVersion1.3.6.1.4.1.1575.1.1.1.2DisplayStringread-onlyThe version number of the running Tcl interpreter.
C32 tnmTclCmdCount1.3.6.1.4.1.1575.1.1.1.3Counter32read-onlyThe nummber of Tcl statements evaluated so far.
DAT tnmDate1.3.6.1.4.1.1575.1.1.1.4DateAndTimeread-onlyThe current date.
STR tnmTrapDst1.3.6.1.4.1.1575.1.1.1.5DisplayStringread-writeThe host name of the trap sink host.
STR tnmTrapMsg1.3.6.1.4.1.1575.1.1.1.6DisplayStringread-onlyThe description of the last trap create by this entity.
tnmDownload1.3.6.1.4.1.1575.1.1.2
STR tnmHttpProxy1.3.6.1.4.1.1575.1.1.2.1DisplayStringread-writeThis variable specifies the proxy server. It must be of the form [:] where is either a domain name or an IP address and is the port number used to access the proxy server. The default port number is 80.
URL tnmHttpSource1.3.6.1.4.1.1575.1.1.2.2URLread-writeSetting this variable will make tnm to download and source the document with the given URL. The agent will try to retrieve the document and sets the variable to the URL if this operations was successfull. Otherwise, the value will become an empty string.
STR tnmHttpError1.3.6.1.4.1.1575.1.1.2.3DisplayStringread-onlyThis variable contains an error string is an http operation fails. An empty string signals that the last operation completed successfully.
tnmPeers1.3.6.1.4.1.1575.1.1.3
tnmPeerTable1.3.6.1.4.1.1575.1.1.3.1not-accessibleA (conceptual) table storing known tnm peers.
tnmPeerEntry1.3.6.1.4.1.1575.1.1.3.1.1not-accessibleAn entry (conceptual row) in the peer table.
ADR tnmPeerTAddress1.3.6.1.4.1.1575.1.1.3.1.1.1TAddressread-createThe address and port number of the peer agent.
OCT tnmPeerAuth1.3.6.1.4.1.1575.1.1.3.1.1.2OCTET STRINGread-createThe authentication information for this peer. This will usually be a community string until we get the final SNMPv2 decisions about the security model.
INT tnmPeerState1.3.6.1.4.1.1575.1.1.3.1.1.3INTEGERread-createThe current status of the peer as returned by the last status probe message.
TIM tnmPeerLastChecked1.3.6.1.4.1.1575.1.1.3.1.1.4TimeStampread-createThe value of sysUpTime when the status of the peer was retrieved and written to tnmPeerState.
ROW tnmPeerStatus1.3.6.1.4.1.1575.1.1.3.1.1.5RowStatusread-createThe status column used for creating, modifying, and deleting instances of the columnar objects in the tnm peer table.
tnmElection1.3.6.1.4.1.1575.1.1.4
U32 tnmElectionIndex1.3.6.1.4.1.1575.1.1.4.1Unsigned32read-onlyThe (hopefully) unique Index of this peer used by the Gully election algorithm.
T/F tnmElectionPanic1.3.6.1.4.1.1575.1.1.4.2TruthValueread-onlyReading this variable will start the panic algorithm on this peer. (We should use an inform request here.)
ADR tnmElectionMaster1.3.6.1.4.1.1575.1.1.4.3TAddressread-writeThis variable will be set by a new master appearing on the scene. (We should use an inform request here.)
tnmEval1.3.6.1.4.1.1575.1.1.5
I32 tnmEvalSlot1.3.6.1.4.1.1575.1.1.5.1Integer32read-onlyThe index number of the first unassigned entry in the evaluation table. A management station should create new entries in the evaluation table using this algorithm: first, issue a management protocol retrieval operation to determine the value of evalSlot; and, second, issue a management protocol set operation to create an instance of the evalStatus object setting its value to underCreation(1). If this latter operation succeeds, then the management station may continue modifying the instances corresponding to the newly created conceptual row, without fear of collision with other management stations.
tnmEvalTable1.3.6.1.4.1.1575.1.1.5.2not-accessibleThe (conceptual) evaluation table.
tnmEvalEntry1.3.6.1.4.1.1575.1.1.5.2.1not-accessibleAn entry (conceptual row) in the evaluation table.
I32 tnmEvalIndex1.3.6.1.4.1.1575.1.1.5.2.1.1Integer32read-onlyThe auxiliary variable used for identifying instances of the columnar objects in the evaluation table.
STR tnmEvalString1.3.6.1.4.1.1575.1.1.5.2.1.2DisplayStringread-createThe string to evaluate.
STR tnmEvalValue1.3.6.1.4.1.1575.1.1.5.2.1.3DisplayStringread-onlyThe value resturned by executing evalString.
ROW tnmEvalStatus1.3.6.1.4.1.1575.1.1.5.2.1.4RowStatusread-createThe status column used for creating, modifying, and deleting instances of the columnar objects in the evaluation table.

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.

Download TUBS-TNM-MIB