All MIBs › SNMPv2-TM
Category: SNA and Legacy Protocols, SNMP Framework
Description: Defines transport domain mappings for SNMP messages over various protocols including UDP/IPv4, CLNS, AppleTalk, and IPX.
IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring SNMPv2-TM with a free 30-day trial of IPNetwork Monitor.
What Is SNMPv2-TM?
SNMPv2-TM (RFC 3417) is an IETF standards MIB module that defines transport domain mappings specifying how SNMP messages are carried over different underlying network transports, including UDP/IPv4, OSI CLNS, Novell IPX, and AppleTalk DDP, along with the historical RFC 1157 proxy transport object. It exposes no device operational data; it defines addressing conventions (transport domain and address OID formats) used by SNMP engines to know how to format and route management traffic across transports. As such it plays no direct role in monitoring hardware or software health, but it is a structural dependency enabling SNMP itself to function over non-UDP/IP transports in legacy or specialized networks. It depends on and complements SNMPv2-SMI for its base syntax and is referenced by SNMP engine/transport configuration in agent implementations. In modern deployments UDP/IPv4 is essentially the only transport used, so this MIB's non-IP mappings are largely legacy/historical in relevance, though the SNMPv2-TM RFC remains the authoritative reference for how SNMP transport addressing is defined.
IPNetwork Monitor allows you to monitor SNMP objects defined in SNMPv2-TM. 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; applies to any SNMP engine/agent needing multi-transport support
Monitoring Examples
An SNMP engine supporting multiple transports would reference the snmpUDPDomain or analogous CLNS/IPX domain object identifiers defined here to correctly interpret the transport-address encoding embedded in a trap's source address. The rfc1157Proxy object specifically supports interoperability with legacy SNMPv1 proxy agents translating between transport domains. There are no live 'sample objects' to monitor for anomalies since this MIB is purely definitional, used at protocol-engine configuration time rather than polled at runtime.
What Can Be Monitored
- transport domain OID mappings
- UDP/IPv4 address encoding
- CLNS/IPX/AppleTalk transport addressing
- RFC 1157 proxy transport support
RFC description
SNMP transport mappings for SNMP over UDP over IPv4 and other protocol transports.
Start monitoring vendor-neutral SNMP devices 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.