TELDAT-TRAP-STP-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TELDAT-TRAP-STP-MIB

Organization: Teldat, S.A.

Last Updated: 2014-01-20

Category: Teldat Router Management, Teldat Trap Notifications

Description: Defines Teldat router STP (Spanning Tree Protocol) 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-STP-MIB?

TELDAT-TRAP-STP-MIB is a Teldat enterprise MIB defining SNMP notifications for Spanning Tree Protocol (STP) events on Teldat routers and switches. Rather than exposing polled counters, it models trap payload variables describing an STP event's source, such as source address, bridge type, bridge instance, bridge port, interface, and circuit name, in two parallel variable sets (stp1-* and stp2-*) likely representing the two endpoints or two protocol variants involved in an event. Its monitoring purpose is fault/topology-change alerting: it lets a management station be notified in near-real-time when an STP event (e.g., a topology change, root bridge change, or port state transition) occurs on a given bridge instance and port, which is critical for diagnosing loops or unexpected failovers in switched networks. It is built on and depends on the IEEE 802.1D/802.1w Spanning Tree Protocol concepts for its bridge/port semantics. It is typically deployed on Teldat routers and switches participating in Layer 2 networks where STP topology stability needs to be tracked, and a TELDAT-TRAP-STP-MIB download is the starting point for wiring up that topology-change alerting.

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

Monitoring Examples

A management station receiving a notification from stpNotifications (under stpNotificationsPrefix) would read the stp1-bridge-instance and stp1-bridge-port varbinds to identify exactly which spanning tree instance and port triggered the event, along with stp1-interface and stp1-circuit-name to map it to a physical link, and stp1-source-address to identify the originating bridge; the parallel stp2-* set would carry corresponding data for a second bridge/port, useful for correlating a topology change across two ends of a link.

What Can Be Monitored

  • STP topology change events
  • bridge instance and port involved in event
  • originating bridge source address
  • interface/circuit associated with event
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

SNMP notification events for Spanning Tree Protocol (STP) BPDU reception and bridge configuration.

Start monitoring Teldat routers and switches (Spanning Tree Protocol topology-change 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-STP-MIB