TELDAT-TRAP-TIDP-MIB

Description: Defines Teldat router TIDP 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.

TELDAT-TRAP-TIDP-MIB is a Teldat enterprise SNMP module that defines trap notifications generated by the TIDP protocol subsystem, an internal Teldat inter-device discovery/keepalive protocol used for coordination between routers. The module packages protocol-level identifiers such as destination IP, remote hostname, serial number, protocol code, and sequence/acknowledgment numbers into notification bindings rather than exposing pollable counters. Its monitoring role is squarely in fault/event visibility: it tells an operator when a TIDP peer relationship changes or an acknowledgment is received or missed, which is useful for detecting connectivity or identity problems between paired Teldat devices, though it does not report classic hardware vitals like temperature or CPU. It builds on the common Teldat enterprise MIB tree and standard SNMP NOTIFICATION-TYPE mechanics for trap transport. It is used in Teldat router deployments where TIDP is enabled for device-to-device signaling, with an NMS trap collector watching for anomalies in the exchange. Engineers can download the TELDAT-TRAP-TIDP-MIB file directly to load it into their MIB browser.

An operator monitoring tidp1-ipdestination and tidp1-hostname in incoming traps can confirm which remote peer a TIDP session traps refer to, while tidp1-sequencenumber and tidp1-ack-rvd reveal whether an expected acknowledgment for that sequence was actually received. A gap between tidp2-sequencenumber values across traps, or a missing tidp2-ack-rvd, would flag a TIDP handshake failure between two Teldat units worth investigating. As with other Teldat trap MIBs, there is no runtime polling table — visibility comes solely from tidpNotifications events.

SNMP notification events for TIDP IP discovery protocol including device notification messaging.