ATM-TRACE-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsATM-TRACE-MIB

Organization: The ATM Forum.

Last Updated: 2004-02-06

Category: ATM

Description: Provides ATM connection trace and diagnostic objects for fault isolation on ATM virtual circuits.

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 ATM-TRACE-MIB?

ATM-TRACE-MIB is a standards-track module published by the ATM Forum that models path and connection tracing for fault isolation on ATM networks, built on textual conventions such as CallReference and AtmEndPointReference and importing PNNI, ATM-TC, IF-MIB, and MPLS-TC identifiers to describe signalling-layer entities. It defines six tables under atmTraceMIBObjects — a Trace Connection table to trigger a connection trace, a Trace Path Test table to trigger a test connection or party, a Trace Path Filter table to trigger path trace by filtering calls, a Trace Filter Record table correlating records with filters, a Trace Record table with overall connection/party trace info, and a Trace Interface table designating PNNI interfaces as trace destinations — plus scalars like atmTraceFilterControl, atmTraceMaxConcurrentRequests, and atmTraceAvailableRequests. It gives operators visibility into how a specific ATM call or path was actually routed hop-by-hop through a PNNI network, which is essential for diagnosing misrouted virtual circuits, unexpected call rejections, or PNNI routing anomalies that plain interface counters cannot explain. It depends on the ATM Forum's PNNI-MIB and ATM-TC-MIB for the addressing and node-identification types it reuses, and it is deployed on ATM switches participating in a PNNI routing domain. For engineers standing up trace-based ATM diagnostics, the ATM-TRACE-MIB reference documents exactly which objects to poll to reconstruct a connection's path.

IPNetwork Monitor allows you to monitor SNMP objects defined in ATM-TRACE-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 (ATM Forum specification), not tied to a specific manufacturer — applies to PNNI-capable ATM switches

Monitoring Examples

An operator sets atmTraceFilterControl to enable and populates the Trace Path Filter table to capture the next call matching a given source/destination pair, then reads the resulting Trace Record and Trace Info table entries; an empty or truncated trace transit list where a live connection is expected would indicate a PNNI routing or signalling fault along the path.

What Can Be Monitored

  • active/available connection trace request counts
  • trace path filter match criteria
  • per-connection trace record entries
  • call/endpoint reference identifiers in trace records
  • PNNI trace destination interface list
Imported Objects

From ATM-POLICY-CONSTRAINT-MIB

NetworkEntityNetworkServiceCategory
PolicyConstraintIndex
ResourcePartitionNetworkServiceCategory

From ATM-TC-MIB

AtmAddr
AtmConnCastType
AtmConnKind
AtmServiceCategory
AtmTrafficDescrParamIndex
AtmVcIdentifier
AtmVpIdentifier

From IF-MIB

InterfaceIndex
InterfaceIndexOrZero

From MPLS-TC-STD-MIB

MplsLabel

From PNNI-MIB

PnniNodeId
PnniPortId
pnniIfEntryOBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
enterprises

From SNMPv2-TC

RowStatus
TEXTUAL-CONVENTION
TimeStamp
TruthValue

How to Use in IPNetwork Monitor

Example using atmTraceFilterNumMatches OID:

Select a PNNI-capable ATM switch (ATM Forum path/connection trace) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type atmTraceFilterNumMatches into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. It reports a monotonically increasing counter to keep track of the number of calls or parties that matched this entry for the entire lifetime of this entry. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Provides ATM path and connection tracing for policy routing and MPLS network interworking diagnostics.

Start monitoring PNNI-capable ATM switches (ATM Forum path/connection trace) 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 ATM-TRACE-MIB