All MIBs › TUBS-IBR-PING-MIB
Organization: TU Braunschweig
Last Updated: 2000-07-07
Category: TU Braunschweig Research MIBs
Description: Manages ICMP ping test configuration and results for network reachability monitoring.
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-IBR-PING-MIB?
TUBS-IBR-PING-MIB is an experimental MIB from TU Braunschweig's IBR institute (originally built for JAX code-generator testing) that lets an SNMP manager configure ICMP ping tests toward remote addresses and retrieve the resulting reachability and round-trip-time statistics. It exposes a ping test table plus scalar statistics/notification objects, making it a network-reachability and latency-performance monitoring MIB rather than a hardware/environmental one. Its monitoring value lies in software-level network health checking: administrators can track round-trip time, average RTT, and timeout behavior to detect degraded connectivity or an unreachable peer, effectively surfacing network-path software status rather than device hardware faults. It is conceptually related to the standard IETF DISMAN-PING-MIB but is an independent, experimental TU Braunschweig implementation rather than a direct extension of it. It was typically used in academic/research SNMP agent testbeds and Tcl-based network management (TNM) environments rather than production networks. Engineers can download the TUBS-IBR-PING-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in TUBS-IBR-PING-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
- vendor-neutral, standards-based MIB, not tied to a specific manufacturer
- host running the TU Braunschweig TNM ping agent
Monitoring Examples
A manager would create an entry in pingTable/pingEntry keyed by pingIndex, setting pingAddress and pingTimeout, then poll pingRtt and pingAvgRtt to see current and historical round-trip times to that target. A pingRtt value pegged at or above pingTimeout, or a sudden jump versus pingAvgRtt, would indicate a reachability problem or network congestion toward that address, and would typically also fire one of the module's pingNotifications.
What Can Be Monitored
- ping round-trip time
- average round-trip time
- ping timeout events
- target reachability
Imported Objects
From SNMPv2-SMI
| IpAddress | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE | |
| Unsigned32 |
From TUBS-SMI
| ibr | OBJECT-IDENTITY |
OIDs
RFC description
TU Braunschweig experimental MIB for testing ping operations and network reachability monitoring.
Start monitoring vendor-neutral, standards-based MIB, host running the TU Braunschweig TNM ping agent (RTT/reachability 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.