All MIBs › CISCO-ATM2-MIB › ciscoatmSigDetectCldPtyEvents
ciscoatmSigDetectCldPtyEvents
Module: CISCO-ATM2-MIB
OID (symbolic): CISCO-ATM2-MIB::ciscoatmSigDetectCldPtyEvents
OID (numeric): 1.3.6.1.4.1.9.10.23.1.1.1.13
Node type: OBJECT-TYPE
Type: Counter32
Access: read-only
Description: Number of Called Party Responsible For Unsuccessful Call detected on this interface. 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):
Cause Value Meaning
17 user busy 18 no user responding 21 call rejected 22 number changed 23 user rejects all calls with calling line id restriction (CLIR) 27 destination out of order 31 normal, unspecified 88 incompatible destination
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.
Note: Cause Value #30 'response to STATUS ENQUIRY' was not included in this memo since it did not apply to a hard failure.
What is ciscoatmSigDetectCldPtyEvents?
This counter increments when a RELEASE, RELEASE COMPLETE, ADD PARTY REJECT, or STATUS message attributing failure to the called party is received on this interface. It counts call failures whose cause codes specifically attribute the failure to something about the called party, such as being busy or refusing the call, rather than to the network, so a rising count points admins away from network troubleshooting entirely and toward the destination device or subscriber as the source of failed calls. A spike in this counter for calls to one particular destination, with no corresponding rise in unavailable-route or unavailable-resource counts, suggests that endpoint is busy or refusing calls, not a network fault.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.10.23.1.1.1.13 snmpwalk -v2c -c public <target> CISCO-ATM2-MIB::ciscoatmSigDetectCldPtyEvents
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.9.10.23.1.1.1.13.1 snmpget -v2c -c public <target> CISCO-ATM2-MIB::ciscoatmSigDetectCldPtyEvents.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::ciscoatmSigDetectCldPtyEvents 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 OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.9 | cisco | CAT2600-MIB |
| 1.3.6.1.4.1.9.10 | ciscoExperiment | CISCO-SMI |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.9.10.23 | ciscoAtm2MIB | CISCO-ATM2-MIB |
| 1.3.6.1.4.1.9.10.23.1 | ciscoatm2MIBObjects | CISCO-ATM2-MIB |
| 1.3.6.1.4.1.9.10.23.1.1 | ciscoatmSigStatTable | CISCO-ATM2-MIB |
| 1.3.6.1.4.1.9.10.23.1.1.1 | ciscoatmSigStatEntry | CISCO-ATM2-MIB |
| 1.3.6.1.4.1.9.10.23.1.1.1.13 | ciscoatmSigDetectCldPtyEvents | CISCO-ATM2-MIB |