All MIBs › CASCADE-MIB › cktSvcCause
cktSvcCause
Module: CASCADE-MIB
OID (symbolic): CASCADE-MIB::cktSvcCause
OID (numeric): 1.3.6.1.4.1.277.1.6.1.1.79
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: SVC cause number. The index will be 0.0 and should be disregarded.
The following cause numbers maybe returned by stdx:
1 - unassigned number, callee is not assigned 2 - no route to specified transit network 3 - no route to destination 6 - channel unacceptable 16 - normal clearing 17 - user busy 18 - no user responding 21 - call rejected by whoever is sending this cause 22 - number changed, called party has changed its number 27 - destination out of order (the interface to called user) 28 - called party number is invalid 29 - facility requested can't be provided by network 30 - included in STATUS message to indicate it is responding to a STATUS ENQUIRY 31 - unspecified, used if no other cause is appropriate 34 - no circuit or channel available to handle the call 38 - network is out of order 41 - tempprary failure, i.e., caller may try again 42 - network congestion 43 - access information (user-to-user) discarded 44 - requested circuit unavailable 58 - bearer capability not available 63 - requested service unavailable 65 - requested bearer capability is not implemented 81 - call reference is unknown 95 - invalid message 96 - mandatory information element is missing 97 - message type is unknown 98 - message not compatible with call state 99 - information element is unknown or not implemented 100 - invalid information element contents 101 - message not compatible with call state
What is cktSvcCause?
This provides the specific ITU-style cause code explaining why this SVC ended or failed, such as 17 (user busy), 18 (no user responding), or 16 (normal clearing), letting the admin distinguish a routine call teardown from an actual dialing or network problem without guessing from generic symptoms. For example, seeing cktSvcCause consistently return 2 (no route to specified transit network) for a customer's repeated SVC attempts points to a network addressing or routing configuration problem, whereas a value of 17 simply means the far end was already occupied on another call.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.277.1.6.1.1.79 snmpwalk -v2c -c public <target> CASCADE-MIB::cktSvcCause
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.277.1.6.1.1.79.1 snmpget -v2c -c public <target> CASCADE-MIB::cktSvcCause.1
Start monitoring Cascade Communications ATM/Frame Relay switches (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CASCADE-MIB::cktSvcCause OID value, configure state conditions and alerts, and monitor any Cascade Communications ATM/Frame Relay switches (legacy) from a single console.
OID Breakdown
Upper-level ancestors (6 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 |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.277 | cascade | CASCADE-MIB |
| 1.3.6.1.4.1.277.1 | cascfr | CASCADE-MIB |
| 1.3.6.1.4.1.277.1.6 | ckt | CASCADE-MIB |
| 1.3.6.1.4.1.277.1.6.1 | cktTable | CASCADE-MIB |
| 1.3.6.1.4.1.277.1.6.1.1 | cktEntry | CASCADE-MIB |
| 1.3.6.1.4.1.277.1.6.1.1.79 | cktSvcCause | CASCADE-MIB |