PNNI-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsPNNI-MIB

Organization: The ATM Forum

Last Updated: 2002-04-24

Category: ATM

Description: Provides the ATM Forum's Private Network-to-Network Interface (PNNI) MIB, covering routing topology and signaling control for ATM switches.

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 PNNI-MIB?

PNNI-MIB implements the ATM Forum's Private Network-to-Network Interface specification, providing SNMP management objects for ATM switch routing topology discovery and signaling/call-admission control. It exposes data on PNNI protocol version support, designated transit list (DTL) usage, crankback and alternate-route event counts, and route failure statistics at both the originating switch and border-node level. Rather than classic hardware health metrics, its status focus is on ATM routing protocol behavior and software-level signaling faults — spikes in pnniCrankbackCountOriginator/Border or pnniRouteFailCountOriginator/Border reveal PNNI topology or call-setup problems inside the ATM switch's control-plane software. It builds on and complements other ATM Forum management specifications for interface-level ATM statistics. It is deployed on carrier-grade or enterprise ATM switches running PNNI hierarchical routing, a technology now largely legacy but still present in some telecom infrastructure, and anyone tracing the PNNI-MIB RFC lineage will find it actually derives from ATM Forum specifications adapted to SNMP SMI conventions rather than a single IETF RFC number.

IPNetwork Monitor allows you to monitor SNMP objects defined in PNNI-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
  • ATM switches supporting PNNI hierarchical routing

Monitoring Examples

An operator polls pnniRouteFailCountOriginator and pnniRouteFailCountBorder to see how many PNNI call setups failed to find a route from this switch versus as a transit border node, and correlates spikes with pnniCrankbackCountOriginator/Border to identify unstable topology paths needing crankback. pnniDtlCountOriginator and pnniDtlCountBorder track how many designated transit lists were generated, indicating routing complexity or churn. pnniHighestVersion and pnniLowestVersion confirm which PNNI protocol versions the switch negotiates with peers, useful when diagnosing interoperability issues between ATM switches from different vendors.

What Can Be Monitored

  • PNNI protocol version support
  • DTL (designated transit list) generation counts
  • crankback event counts
  • alternate route counts
  • route failure counts
  • unreachable route failure counts
Imported Objects

From ATM-TC-MIB

AtmTrafficDescrParamIndex

From IF-MIB

InterfaceIndex
ifIndexOBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Gauge32
Integer32
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32
enterprises
zeroDotZero

From SNMPv2-TC

DisplayString
RowStatus
TEXTUAL-CONVENTION
TimeStamp
TruthValue
OIDs

RFC description

Implements the ATM Forum Private Network-to-Network Interface (PNNI) MIB for ATM switch routing topology and signaling control.

Start monitoring vendor-neutral, standards-based MIB, ATM switches supporting PNNI hierarchical routing 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 PNNI-MIB