All MIBs › CISCO-ATM2-MIB › ciscoatmSigSSCOPConEvents
ciscoatmSigSSCOPConEvents
Module: CISCO-ATM2-MIB
OID (symbolic): CISCO-ATM2-MIB::ciscoatmSigSSCOPConEvents
OID (numeric): 1.3.6.1.4.1.9.10.23.1.1.1.5
Node type: OBJECT-TYPE
Type: Counter32
Access: read-only
Description: 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 P. See ITU-T Q.2110 [13].)
2) SSCOP Connection Initiation Failure
This condition indicates the inability to establish an SSCOP connection. This event occurs whenever the number of expiries of the connection control timer (Timer_CC) exceeds the MaxCC or upon receipt of a connection reject message BGREJ PDU. (This event is communicated to layer management with MAA-ERROR code O. See ITU-T Q.2110.)
3) SSCOP Connection Re-Establ/Resynch
This event occurs upon receipt of a BGN PDU or RESYNC PDU.
What is ciscoatmSigSSCOPConEvents?
This counter sums several distinct SSCOP connection-layer error events, including connection disconnects from an expired no-response timer and connection initiation failures, per ITU-T Q.2110. Because SSCOP is the reliable signaling transport underneath ATM call control, similar in role to TCP for signaling messages, this counter climbing means the signaling channel itself is having connectivity problems, separate from and more fundamental than any single call failing, which can explain a wave of unrelated call setup failures on this interface all at once. A burst of SSCOP connection events right before every SVC on the interface starts failing to establish would point to the underlying signaling link, not the individual calls, as the root cause.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.10.23.1.1.1.5 snmpwalk -v2c -c public <target> CISCO-ATM2-MIB::ciscoatmSigSSCOPConEvents
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.9.10.23.1.1.1.5.1 snmpget -v2c -c public <target> CISCO-ATM2-MIB::ciscoatmSigSSCOPConEvents.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::ciscoatmSigSSCOPConEvents 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.5 | ciscoatmSigSSCOPConEvents | CISCO-ATM2-MIB |