CISCO-ATM-SIG-DIAG-MIB

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CISCO-ATM-SIG-DIAG-MIB

Organization: Cisco Systems, Inc.

Last Updated: 1997-07-28

Category: ATM

Description: Monitors ATM signaling diagnostics and call setup failure statistics on Cisco ATM interfaces.

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 CISCO-ATM-SIG-DIAG-MIB?

CISCO-ATM-SIG-DIAG-MIB is a Cisco module in the ATM networking technology area that facilitates diagnosis of ATM signaling failures, i.e. failed connection setup attempts on ATM interfaces. It exposes configuration objects for defining filter criteria (such as calling/called ATM addresses, service category, and interface) and retains records describing connection setup failures that match those filters. This is squarely a fault/diagnostics MIB used for monitoring the operational health of ATM signaling on a device: it lets an operator track call/connection setup failure rates and causes, which is critical for spotting signaling instability, addressing errors, or interoperability problems between ATM switches. It relies on the standard ATM signaling protocol concepts and likely complements the base ATM-MIB and Cisco's ATM interface MIBs for interface and address representation. It is deployed on Cisco ATM switches and ATM-capable routers used in carrier or enterprise ATM networks where call setup reliability needs active troubleshooting. Engineers can download the CISCO-ATM-SIG-DIAG-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-ATM-SIG-DIAG-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

  • Cisco ATM switches
  • Cisco routers with ATM interfaces

Monitoring Examples

An operator configures csfFilterTable entries (via csfFilterEntry) specifying criteria like csfFilterCallingParty, csfFilterInInterface/csfFilterOutInterface, and csfFilterServiceCategory to capture failures of interest, then enables collection with csfFilterControl. When a matching setup failure occurs, the record's csfFilterCause reveals the ATM signaling failure reason (e.g. no route, resource unavailable), letting the admin correlate repeated failures on a specific csfFilterInInterface with a downstream provisioning or capacity problem. A rising count of records filtered by csfFilterConnKind or csfFilterConnCastType would indicate a systemic issue with a particular connection type rather than an isolated fault.

What Can Be Monitored

  • ATM connection setup failure records
  • signaling failure cause codes
  • calling/called party ATM addresses
  • failures by interface
  • failures by service category
  • connection kind/cast type filters
Imported Objects

From CISCO-SMI

ciscoMgmtOBJECT-IDENTITY

From CISCO-TC

InterfaceIndexOrZero

From PNNI-MIB

PnniNodeId
PnniPortId
ServiceCategory

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

RowStatus
TEXTUAL-CONVENTION
TimeStamp

How to Use in IPNetwork Monitor

Example using csfFilterNumMatches OID:

Select a Cisco ATM switches/router 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 csfFilterNumMatches 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 a monotonically increasing counter to keep track of the number of call failures that matched this entry for the entire lifetime of this entry. 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

Diagnoses ATM signaling failures by recording connection setup errors matching specific selection criteria.

Start monitoring Cisco ATM switches/routers 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 CISCO-ATM-SIG-DIAG-MIB