CISCO-ATM2-MIB :: ciscoatmSigDetectUnavailResrcs

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CISCO-ATM2-MIB › ciscoatmSigDetectUnavailResrcs

ciscoatmSigDetectUnavailResrcs

Module: CISCO-ATM2-MIB

OID (symbolic): CISCO-ATM2-MIB::ciscoatmSigDetectUnavailResrcs

OID (numeric): 1.3.6.1.4.1.9.10.23.1.1.1.11

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Number of Resource Unavailability detected on this interfrace. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is received (Note: These cause values apply to both UNI3.0 and UNI3.1 unless otherwise stated):

Cause Value Meaning

35 requested VPCI/VCI not available 37 user cell rate not available (UNI3.1 only) 38 network out of order 41 temporary failure 45 no VPCI/VCI available 47 resource unavailable, unspecified 49 Quality of Service unavailable 51 user cell rate not available (UNI3.0 only) 58 bearer capability not presently available 63 Service or option not available, unspecified 92 too many pending add party requests

NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted.

What is ciscoatmSigDetectUnavailResrcs?

This counter increments when a RELEASE, RELEASE COMPLETE, ADD PARTY REJECT, or STATUS message reporting resource unavailability is received on this interface. Unlike a routing failure, this cause reflects the network reporting that a path exists but lacks the bandwidth or connection resources to admit the call, so a rising count during otherwise normal routing conditions is a capacity signal, telling the admin the interface or network is running out of room for new calls rather than that destinations are unreachable. This counter climbing during a high-traffic period while ciscoatmSigDetectUnavailRoutes stays flat points to bandwidth exhaustion on the call path, not a routing problem.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.10.23.1.1.1.11
snmpwalk -v2c -c public <target> CISCO-ATM2-MIB::ciscoatmSigDetectUnavailResrcs

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.10.23.1.1.1.11.1
snmpget -v2c -c public <target> CISCO-ATM2-MIB::ciscoatmSigDetectUnavailResrcs.1

Start monitoring Cisco routers/switches with ATM interfaces with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-ATM2-MIB::ciscoatmSigDetectUnavailResrcs OID value, configure state conditions and alerts, and monitor any Cisco routers/switches with ATM interfaces from a single console.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.10ciscoExperimentCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.10.23ciscoAtm2MIBCISCO-ATM2-MIB
1.3.6.1.4.1.9.10.23.1ciscoatm2MIBObjectsCISCO-ATM2-MIB
1.3.6.1.4.1.9.10.23.1.1ciscoatmSigStatTableCISCO-ATM2-MIB
1.3.6.1.4.1.9.10.23.1.1.1ciscoatmSigStatEntryCISCO-ATM2-MIB
1.3.6.1.4.1.9.10.23.1.1.1.11ciscoatmSigDetectUnavailResrcsCISCO-ATM2-MIB