CISCO-GGSN-MIB :: cGgsnSentSigMessages

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-GGSN-MIBcGgsnSentSigMessages

cGgsnSentSigMessages

Module: CISCO-GGSN-MIB

OID (symbolic): CISCO-GGSN-MIB::cGgsnSentSigMessages

OID (numeric): 1.3.6.1.4.1.9.9.240.1.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of GTPv0 and GTPv1 signalling messages sent.

Trigger Condition: This counter is updated whenever a GTPv0 and GTPv1 signalling messages is sent out, including retries.

What is cGgsnSentSigMessages?

Counts the number of GTPv0 and GTPv1 signalling messages sent by the GGSN, including retries; increments each time such a message is transmitted.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.240.1.1.1
snmpwalk -v2c -c public <target> CISCO-GGSN-MIB::cGgsnSentSigMessages

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.240.1.1.1.1
snmpget -v2c -c public <target> CISCO-GGSN-MIB::cGgsnSentSigMessages.1

Start monitoring Cisco GGSN (Gateway GPRS Support Node) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-GGSN-MIB::cGgsnSentSigMessages OID value, configure state conditions and alerts, and monitor any Cisco GGSN (Gateway GPRS Support Node) from a single console.

How to Use in IPNetwork Monitor

Select a Cisco GGSN (Gateway GPRS Support Node) 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 cGgsnSentSigMessages into the Find box to locate it in the OID tree, then select it and click OK. The number of GTPv0 and GTPv1 signalling messages sent. 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 sharply between polls relative to its normal baseline (in packets), since an unexpected spike often reflects a real change in traffic or activity. 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.240cGgsnMIBCISCO-GGSN-MIB
1.3.6.1.4.1.9.9.240.1cGgsnMIBObjectsCISCO-GGSN-MIB
1.3.6.1.4.1.9.9.240.1.1cGgsnStatisticsCISCO-GGSN-MIB
1.3.6.1.4.1.9.9.240.1.1.1cGgsnSentSigMessagesCISCO-GGSN-MIB