All MIBs › CISCO-WAN-3G-MIB › c3gGsmCurrentServiceError
c3gGsmCurrentServiceError
Module: CISCO-WAN-3G-MIB
OID (symbolic): CISCO-WAN-3G-MIB::c3gGsmCurrentServiceError
OID (numeric): 1.3.6.1.4.1.9.9.661.1.3.2.1.3
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: Current service error: unknown(1) - Unknown none(2) - None imsiUnknownInHlr(3) - IMSI unknown in HLR (Home Location Register) illegalMs(4) - Illegal MS (Mobile Station) imsiUnknownInVlr(5) - IMSI unknown in VLR (Visitor Location Register) imeiNotAccepted(6) - IMEI not accepted illegalMe(7) - Illegal ME (Mobile Entity) gprsServNotAllowed(8) - GPRS services not allowed gprsNonGprsServNotAllow(9) - GPRS and non-GPRS services not allowed msIdentUnknown(10) - MS identity unknown implicitlyDetached(11) - Implicitly detached plmnNotAllowed(12) - PLMN not allowed lacNotAllowed(13) - LAC not allowed roamingNotAllowed(14) - Roaming not allowed gprsServNotAllowInPlmn(15) - GPRS services not allowed in this PLMN noSuitableCellInLa(16) - No suitable cells in LA (Location Area) mscTempNotReachable(17) - MSC (Mobile Switching Center) temporarily not reachable networkFailure(18) - Network failure macFailure(19) - MAC failure synchFailure(20) - Synch failure congestion(21) - Congestion gsmAuthenNotAccept(22) - GSM/LTE Authentication not accepted servOptionNotSupport(23) - Service option not supported reqServOptionNotSub(24) - Requested service option not subscribed servOptionOutOfOrder(25) - Service option out of order callCannotIdentified(26) - Call cannot be identified noPdpContextActivated(27) - No PDP context activated invalidMandatInfo(28) - Invalid mandatory info unpsecProtErr(29) - Unspecified protocol error
What is c3gGsmCurrentServiceError?
This read-only enumeration reports the specific reason GSM service is impaired, distinguishing causes like imsiUnknownInHlr(3) (the SIM isn't recognized by the home network's Home Location Register), illegalMs(4), imsiUnknownInVlr(5), or imeiNotAccepted(6). An admin uses this to turn a vague "no GSM service" complaint into an actionable root cause, for instance an imsiUnknownInHlr error clearly points to a carrier-side provisioning problem rather than anything wrong with the router. For example, seeing imeiNotAccepted(6) here would tell the admin the specific modem hardware itself is being rejected by the network, possibly due to an IMEI blacklist entry, rather than a SIM issue.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.661.1.3.2.1.3 snmpwalk -v2c -c public <target> CISCO-WAN-3G-MIB::c3gGsmCurrentServiceError
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.661.1.3.2.1.3.1 snmpget -v2c -c public <target> CISCO-WAN-3G-MIB::c3gGsmCurrentServiceError.1
Start monitoring Cisco routers with 3G/4G LTE WAN interface modules with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-WAN-3G-MIB::c3gGsmCurrentServiceError OID value, configure state conditions and alerts, and monitor any Cisco routers with 3G/4G LTE WAN interface modules 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.9 | ciscoMgmt | CISCO-SMI |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.9.9.661 | ciscoWan3gMIB | CISCO-WAN-3G-MIB |
| 1.3.6.1.4.1.9.9.661.1 | ciscoWan3gMIBObjects | CISCO-WAN-3G-MIB |
| 1.3.6.1.4.1.9.9.661.1.3 | c3gWanGsm | CISCO-WAN-3G-MIB |
| 1.3.6.1.4.1.9.9.661.1.3.2 | c3gGsmNetworkTable | CISCO-WAN-3G-MIB |
| 1.3.6.1.4.1.9.9.661.1.3.2.1 | c3gGsmNetworkEntry | CISCO-WAN-3G-MIB |
| 1.3.6.1.4.1.9.9.661.1.3.2.1.3 | c3gGsmCurrentServiceError | CISCO-WAN-3G-MIB |