TELDAT-TRAP-P3OE-MIB

Description: Defines Teldat router P3OE (802.3at PoE) 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-P3OE-MIB is a Teldat proprietary, notification-only SNMP MIB that defines the trap varbinds emitted by the router's P3OE event subsystem; although the module's short label suggests 802.3at Power-over-Ethernet, its actual varbinds - service-name, host-uniq, tag-type/tag-value, base interface, and MAC address - match the discovery-stage fields of PPPoE (Point-to-Point Protocol over Ethernet, RFC 2516), so this MIB most plausibly instruments PPPoE session-establishment events rather than PoE power delivery. It groups numbered event definitions (p3oe1 through p3oe7, under p3oeEventsGroup/p3oeNotifications) carrying the base/logical interface, PPPoE service name, host-uniq tag, VLAN-style tag type/value, and peer MAC address. Operationally it is a fault/event monitor for the PPPoE session-setup software path: it lets a management station learn asynchronously about discovery-stage events per interface, such as a service-name mismatch, a host-uniq tag exchange, or a specific peer MAC completing discovery, which helps diagnose PPPoE sessions that fail to establish. As with Teldat's other TRAP-* modules it depends on the standard SNMPv2-SMI/SNMPv2-TC notification conventions and Teldat's private enterprise OID tree, layered on top of the RFC 2516 PPPoE standard it appears to track. It is deployed on Teldat routers using PPPoE-based WAN access (common with DSL/fiber ISPs), where discovery-stage failures need visibility. Engineers can download the TELDAT-TRAP-P3OE-MIB file directly to load it into their MIB browser.

This module defines only notification objects and their varbinds rather than a polled session table, so there is no GET-based monitoring scenario; it is trap-only. An SNMP trap receiver would inspect p3oe3-service-name and p3oe3-interface to see which requested PPPoE service failed to be offered, or p3oe7-mac together with p3oe5-host-uniq/p3oe5-interface to identify the peer MAC and tag involved in a specific discovery event.

SNMP notifications for Teldat P3OE event subsystem monitoring packet processing and interface errors.