All MIBs › ATM-Ext-MIB
Category: ATM
Description: Extends standard ATM MIB objects with additional connection and cell-layer performance counters.
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-Ext-MIB?
ATM-Ext-MIB is a Bellcore/Telcordia-originated extension to the standard ATM MIB, adding richer connection-level and cell-layer performance objects for ATM network equipment. It exposes contact/location information for interfaces, plus virtual channel link (VCL) and virtual path link (VPL) tables carrying VPI/VCI identifiers, usage parameter control (UPC) violation counts, and row status for connection provisioning. Its monitoring value centers on software/configuration and traffic-quality counters - specifically UPC violations that indicate a circuit is exceeding its negotiated traffic contract, which is a key ATM QoS fault indicator. It explicitly extends the base ATM-MIB (RFC 1695/2515) rather than standing alone. It is deployed in carrier and enterprise ATM network infrastructure, often alongside standard ATM-MIB implementations, to add finer per-circuit fault detection. Engineers can download the ATM-Ext-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in ATM-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
- ATM switch/network element (Bellcore/Telcordia-compliant)
- vendor-neutral, standards-based extension MIB, not tied to a specific manufacturer
Monitoring Examples
An operator would poll atmExtVclTable/atmExtVclEntry for a given atmExtVclVpi/atmExtVclVci pair and monitor atmExtVclUpcViolations to detect when a virtual circuit is sending traffic in excess of its policed contract. A rising UPC violation count combined with checking atmExtContactTable/atmExtContactEntry for atmExtContactIfLocation would help pinpoint which physical interface and circuit is generating contract violations, a common precursor to cell discard and service degradation.
What Can Be Monitored
- UPC (usage parameter control) violations per VCL
- VCL/VPL identifiers (VPI/VCI)
- interface contact and location info
- connection row status
Imported Objects
From RFC-1212
| OBJECT-TYPE |
From RFC1155-SMI
| Counter | |
| enterprises |
From RFC1213-MIB
| DisplayString | |
| ifIndex |
From SNMPv2-TC
| RowStatus |
OIDs
RFC description
Extends standard ATM MIB (RFC 1695) with vendor-specific ATM interface, circuit, and traffic management objects.
Start monitoring ATM switches/network elements (Bellcore/Telcordia extension) 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.