CISCO-ITP-DSMR-UCP-MIB :: cdsmrUcpDestSentRequests

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CISCO-ITP-DSMR-UCP-MIB › cdsmrUcpDestSentRequests

cdsmrUcpDestSentRequests

Module: CISCO-ITP-DSMR-UCP-MIB

OID (symbolic): CISCO-ITP-DSMR-UCP-MIB::cdsmrUcpDestSentRequests

OID (numeric): 1.3.6.1.4.1.9.9.1302.1.7.1.11

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Number of SMS requests sent to destination.

What is cdsmrUcpDestSentRequests?

Counts the number of SMS requests sent to this destination, useful for monitoring outbound message traffic.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.1302.1.7.1.11
snmpwalk -v2c -c public <target> CISCO-ITP-DSMR-UCP-MIB::cdsmrUcpDestSentRequests

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.1302.1.7.1.11.1
snmpget -v2c -c public <target> CISCO-ITP-DSMR-UCP-MIB::cdsmrUcpDestSentRequests.1

Start monitoring Cisco IP Transfer Point (ITP) SS7 signaling gateway (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-ITP-DSMR-UCP-MIB::cdsmrUcpDestSentRequests OID value, configure state conditions and alerts, and monitor any Cisco IP Transfer Point (ITP) SS7 signaling gateway (legacy) from a single console.

How to Use in IPNetwork Monitor

Select a Cisco IP Transfer Point (ITP) SS7 signaling gateway (legacy) 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 cdsmrUcpDestSentRequests into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. It reports the number of SMS requests sent to destination. 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 requests), 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.1302ciscoItpDsmrUcpMIBCISCO-ITP-DSMR-UCP-MIB
1.3.6.1.4.1.9.9.1302.1ciscoItpDsmrUcpMIBObjectsCISCO-ITP-DSMR-UCP-MIB
1.3.6.1.4.1.9.9.1302.1.7cdsmrUcpDestTableCISCO-ITP-DSMR-UCP-MIB
1.3.6.1.4.1.9.9.1302.1.7.1cdsmrUcpDestTableEntryCISCO-ITP-DSMR-UCP-MIB
1.3.6.1.4.1.9.9.1302.1.7.1.11cdsmrUcpDestSentRequestsCISCO-ITP-DSMR-UCP-MIB