TELDAT-TRAP-TKR-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsTELDAT-TRAP-TKR-MIB

Organization: Teldat, S.A.

Last Updated: 2014-01-20

Category: Remote Access and Serial WAN, Teldat Router Management, Teldat Trap Notifications

Description: Defines Teldat router TKR (token ring) interface event trap notifications.

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 TELDAT-TRAP-TKR-MIB?

TELDAT-TRAP-TKR-MIB is a Teldat router MIB dedicated to defining SNMP trap notifications generated by the TKR (Token Ring) interface event subsystem. It exposes only notification/trap-related objects rather than pollable status tables, carrying event details such as source MAC address, interface identifier, and event-specific codes. Administrators use it to monitor fault conditions on Token Ring interfaces, including self-test phase failures and error conditions, functioning as a software/hardware fault-reporting mechanism rather than a general performance MIB. It is a Teldat vendor-specific companion to standard trap conventions and depends on the underlying Token Ring interface subsystem it reports on. It is deployed on legacy Teldat routers still carrying Token Ring interfaces in enterprise or telco environments. Engineers can download the TELDAT-TRAP-TKR-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in TELDAT-TRAP-TKR-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

  • Teldat router (Token Ring interface models)

Monitoring Examples

A monitoring system trapping on tkr14-selftest-phase and tkr14-error-condition would receive notifications when a Token Ring interface fails a self-test, indicating a hardware or firmware fault requiring attention, with tkr14-interface identifying the affected port. Traps carrying tkr3-source-MAC or tkr5-type-code/tkr6-type-code let an admin identify which station triggered a ring event (such as beaconing or insertion faults) and correlate it to a specific interface via the accompanying -interface object.

What Can Be Monitored

  • Token Ring self-test phase/result
  • interface error condition
  • event source MAC address
  • affected interface index
  • trap type/event codes
Imported Objects

From SNMPv2-SMI

Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DisplayString

From TELDAT-MIB

telEventTrapsOBJECT-IDENTITY
OIDs

RFC description

Teldat TKR event subsystem MIB managing SNMP notifications for router network events.

Start monitoring Teldat router, Token Ring interface models, legacy (self-test/error event traps) 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 TELDAT-TRAP-TKR-MIB