CISCO-GTPV2-MIB :: cGtpv2DroppedSigMsgs

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-GTPV2-MIBcGtpv2DroppedSigMsgs

cGtpv2DroppedSigMsgs

Module: CISCO-GTPV2-MIB

OID (symbolic): CISCO-GTPV2-MIB::cGtpv2DroppedSigMsgs

OID (numeric): 1.3.6.1.4.1.9.9.734.1.1.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: This object represents the total number of GTPv2 control plane messages dropped by the gateway.

What is cGtpv2DroppedSigMsgs?

Reports the total number of GTPv2 control-plane (signalling) messages dropped by the gateway, useful for spotting GTPv2 signalling processing issues.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.734.1.1.1.1
snmpwalk -v2c -c public <target> CISCO-GTPV2-MIB::cGtpv2DroppedSigMsgs

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.734.1.1.1.1.1
snmpget -v2c -c public <target> CISCO-GTPV2-MIB::cGtpv2DroppedSigMsgs.1

Start monitoring Cisco SGW/PGW LTE/EPC mobile gateway platforms with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-GTPV2-MIB::cGtpv2DroppedSigMsgs OID value, configure state conditions and alerts, and monitor any Cisco SGW/PGW LTE/EPC mobile gateway platforms from a single console.

How to Use in IPNetwork Monitor

Select a Cisco SGW/PGW LTE/EPC mobile gateway platform as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type cGtpv2DroppedSigMsgs into the Find box to locate it in the OID tree, then select it and click OK. This object represents the total number of GTPv2 control plane messages dropped by the gateway. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.

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.9ciscoMgmtCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.9.734ciscoGtpv2MIBCISCO-GTPV2-MIB
1.3.6.1.4.1.9.9.734.1cGtpv2MIBObjectsCISCO-GTPV2-MIB
1.3.6.1.4.1.9.9.734.1.1cGtpv2StatisticsCISCO-GTPV2-MIB
1.3.6.1.4.1.9.9.734.1.1.1cGtpv2SystemStatisticsCISCO-GTPV2-MIB
1.3.6.1.4.1.9.9.734.1.1.1.1cGtpv2DroppedSigMsgsCISCO-GTPV2-MIB