ATM2-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsATM2-MIB

Organization: IETF AToMMIB Working Group

Last Updated: 2003-09-23

Category: ATM, Network Interfaces

Description: Defines supplemental managed objects for ATM interface management beyond the base ATM-MIB, adding support for ATM Switched and Permanent Virtual Connections.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring ATM2-MIB with a free 30-day trial of IPNetwork Monitor.

What Is ATM2-MIB?

ATM2-MIB defines supplemental managed objects for ATM interface management, adding signaling statistics and support for switched and permanent virtual connections beyond the base ATM-MIB. It exposes counters for signaling message errors, calling-party events, timer expirations, restarts, and inbound/outbound call establishments, plus a signaling support table. Its monitoring emphasis is on software/protocol status: rising signaling error or restart counts reveal an unstable signaling interface, which typically precedes SVC setup failures, while establishment counters gauge call setup volume and load. It is explicitly published as RFC 3606 and is a formal supplement to the standard ATM-MIB defined in RFC 2515. It is used on ATM switches and interfaces that support SVC signaling in legacy carrier or enterprise ATM networks. Engineers implementing or auditing this functionality typically reference the ATM2-MIB RFC/standard documentation for the authoritative specification.

IPNetwork Monitor allows you to monitor SNMP objects defined in ATM2-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 (RFC 3606), applies to ATM switches and interfaces using SVC signaling

Monitoring Examples

The module exposes atmSigDetectMsgErrors/atmSigEmitMsgErrors, atmSigDetectRestarts/atmSigEmitRestarts, atmSigInEstabls/atmSigOutEstabls, and atmSigSupportTable/atmSigSupportEntry. An administrator would poll atmSigDetectMsgErrors and atmSigDetectRestarts to spot a signaling interface experiencing repeated protocol errors or restarts, typically a precursor to SVC setup failures, and track atmSigInEstabls/atmSigOutEstabls to gauge call setup volume on that interface.

What Can Be Monitored

  • signaling message error counts (detected/emitted)
  • signaling restart counts
  • inbound/outbound call establishment counts
  • calling-party event counts
  • timer expiry counts
  • signaling support table entries
Imported Objects

From ATM-MIB

atmInterfaceConfEntryOBJECT-TYPE
atmMIBObjectsOBJECT-IDENTITY
atmVcCrossConnectEntryOBJECT-TYPE
atmVclEntryOBJECT-TYPE
atmVclVciOBJECT-TYPE
atmVclVpiOBJECT-TYPE
atmVpCrossConnectEntryOBJECT-TYPE
atmVplEntryOBJECT-TYPE
atmVplVpiOBJECT-TYPE

From ATM-TC-MIB

AtmAddr
AtmIlmiNetworkPrefix
AtmInterfaceType
AtmSigDescrParamIndex
AtmTrafficDescrParamIndex
AtmVcIdentifier
AtmVpIdentifier

From IF-MIB

InterfaceIndex
InterfaceIndexOrZero
ifIndexOBJECT-TYPE

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

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

From SNMPv2-TC

RowStatus
TimeStamp
TruthValue

How to Use in IPNetwork Monitor

Example using atmSigSSCOPConEvents OID:

Select an ATM switches/interfaces using SVC signaling 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 atmSigSSCOPConEvents 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 sSCOP Connection Events Counter. This counter counts the sum of the following errors: 1) SSCOP Connection Disconnect Counter The abnormal occurrence of this event is characterized by the expiry of Timer_NO_RESPONSE. (This event is communicated to the layer management with MAA-ERROR code. 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 between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

IETF ATM2 MIB providing enhanced ATM interface management including VPL/VCL cross-connect and traffic descriptor parameter management.

Start monitoring ATM switches/interfaces using SVC signaling 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 ATM2-MIB