ASCEND-MIBATMPNNI-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsASCEND-MIBATMPNNI-MIB

Category: ATM, Vendor: Ascend/Lucent

Description: Manages ATM Private Network-to-Network Interface routing on Ascend ATM switch equipment.

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 ASCEND-MIBATMPNNI-MIB?

ASCEND-MIBATMPNNI-MIB is a vendor-specific MIB from Ascend Communications (later part of Lucent) that models ATM Private Network-to-Network Interface (PNNI) routing configuration on Ascend TAOS-based ATM switches. It organizes its objects under the ASCEND-MIB configuration branch into mibpnniNodeConfig, mibpnniIfConfig, mibpnniDTLConfig (Designated Transit List path configuration), mibpnniRouteNodeConfig, mibpnniRouteAddrConfig, mibpnniSummaryAddrEntry, mibpnniRouteTnsConfig, and mibpnniMetricsConfig, each exposed as its own profile table (e.g., mibpnniSummaryAddrEntryTable, MibpnniSummaryAddrEntryEntry). This structure is useful for monitoring because it exposes the PNNI hierarchical routing configuration — node identity, per-interface PNNI parameters, summarized reachable addresses, and routing metrics — that determines how call setup paths are computed across an ATM PNNI network. It depends on the vendor's ASCEND-MIB for the base configuration OID tree and RFC-1212/RFC1155-SMI conventions, and is deployed on Ascend ATM switching platforms running TAOS software in service-provider or carrier ATM backbones; administrators can download the ASCEND-MIBATMPNNI-MIB file to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in ASCEND-MIBATMPNNI-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

  • Ascend Communications TAOS-based ATM switches

Monitoring Examples

An operator polls mibpnniIfConfig table entries for an ATM trunk interface to confirm PNNI is enabled and the interface's routing parameters match the peer switch, then checks mibpnniRouteAddrConfig for the expected summarized reachable address; a mismatch between advertised summary addresses and mibpnniRouteNodeConfig entries would indicate a PNNI topology database inconsistency likely to cause call routing failures.

What Can Be Monitored

  • PNNI node configuration
  • per-interface PNNI parameters
  • Designated Transit List (DTL) path configuration
  • summarized reachable address entries
  • route node and route address configuration
  • PNNI routing metrics
Imported Objects

From ASCEND-MIB

configurationOBJECT-IDENTITY

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

IpAddress
OIDs

RFC description

Monitors ATM PNNI (Private Network-to-Network Interface) configuration parameters on Ascend devices.

Start monitoring Ascend Communications (Lucent) ATM switching equipment (legacy) 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 ASCEND-MIBATMPNNI-MIB