PNNI-MOB-EXT-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › PNNI-MOB-EXT-MIB

Organization: The ATM Forum

Last Updated: 1999-02-12

Category: ATM

Description: Extends ATM Forum PNNI with mobility extensions for mobile ATM node location and handover management.

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-MOB-EXT-MIB?

PNNI-MOB-EXT-MIB is an ATM Forum standards-based MIB (not vendor-specific) that extends the PNNI (Private Network-to-Network Interface) routing protocol with mobility extensions, supporting mobile ATM nodes that need to update their network location and handle handovers. It exposes configuration and state objects describing mobility-enabled interfaces, mobile logical group node (LGN) hierarchy levels, and overlay/onhl (overlay next-hop-list style) peer group relationships used to track a mobile node's position in the PNNI hierarchy. Its monitoring value is largely about software/protocol state rather than physical hardware: confirming that mobility is enabled on the correct interfaces and that a mobile node's PNNI peer group and hierarchy-level associations remain correct as it roams, since incorrect state here would cause routing/handover failures. It explicitly extends the ATM Forum's base PNNI routing MIB and mobility framework, so it depends on the standard PNNI MIB definitions for full context. It would be deployed in specialized mobile-ATM network infrastructure, a niche and largely legacy technology used in some military/carrier mobile ATM deployments where the PNNI-MOB-EXT-MIB reference documents mobility-hierarchy state.

IPNetwork Monitor allows you to monitor SNMP objects defined in PNNI-MOB-EXT-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 ATM Forum MIB, not tied to a specific manufacturer
  • mobile ATM switches/nodes

Monitoring Examples

An operator would check pnniMSMobileIfTable/pnniMSMobileIfEntry for pnniIfMobilityEnabled to confirm mobility is turned on for the interfaces expected to serve mobile nodes, and pnniMobileLgnMinLevel/pnniMobileLgnMaxLevel to verify the logical group node hierarchy bounds are set correctly. Polling pnniMSOnhlTable/pnniMSOnhlEntry for pnniOnhlPeerGroupId and pnniOnhlLevel reveals whether a mobile node's recorded peer group and hierarchy level still match its actual location, and a stale or mismatched value would explain failed handover or misrouted calls as the node moves. pnniMobExtVersion confirms which revision of the mobility extension the device implements.

What Can Be Monitored

  • mobility-enabled interface flags
  • mobile logical group node hierarchy levels
  • peer group ID association
  • onhl overlay hierarchy level
  • mobility extension version
Imported Objects

From IF-MIB

InterfaceIndex

From PNNI-MIB

PnniAtmAddr
PnniLevel
PnniNodeId
PnniNodeIndex
PnniPeerGroupId
pnniIfEntryOBJECT-TYPE
pnniNodeEntryOBJECT-TYPE
pnniNodeIndexOBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
OBJECT-TYPE
enterprises

From SNMPv2-TC

TEXTUAL-CONVENTION
TimeStamp
TruthValue

How to Use in IPNetwork Monitor

Example using pnniDecisionProcessCount OID:

Select a device implementing PNNI-MOB-EXT-MIB 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 pnniDecisionProcessCount 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. The number of times that the decision process has been executed by this node. 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

Manages ATM Forum PNNI routing extensions for mobile networks and dynamic network topology.

Start monitoring vendor-neutral, standards-based ATM Forum MIB, mobile ATM switches/nodes (PNNI mobility extensions) 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-MOB-EXT-MIB