CISCO-RPMS-MIB :: crpmsCpAttemptedCalls

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CISCO-RPMS-MIB › crpmsCpAttemptedCalls

crpmsCpAttemptedCalls

Module: CISCO-RPMS-MIB

OID (symbolic): CISCO-RPMS-MIB::crpmsCpAttemptedCalls

OID (numeric): 1.3.6.1.4.1.9.10.84.1.2.1.1.6

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Total number of attempted calls (both successful and failed) for this customer profile.

What is crpmsCpAttemptedCalls?

Reports the cumulative total of calls attempted, whether successful or failed, for a given customer profile.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.10.84.1.2.1.1.6
snmpwalk -v2c -c public <target> CISCO-RPMS-MIB::crpmsCpAttemptedCalls

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.10.84.1.2.1.1.6.1
snmpget -v2c -c public <target> CISCO-RPMS-MIB::crpmsCpAttemptedCalls.1

Start monitoring Cisco RPMS server (Resource Policy Management System) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-RPMS-MIB::crpmsCpAttemptedCalls OID value, configure state conditions and alerts, and monitor any Cisco RPMS server (Resource Policy Management System) from a single console.

How to Use in IPNetwork Monitor

Select a Cisco RPMS server (Resource Policy Management System) 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 crpmsCpAttemptedCalls 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 total number of attempted calls (both successful and failed) for this customer profile. 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.10ciscoExperimentCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.10.84ciscoRpmsMIBCISCO-RPMS-MIB
1.3.6.1.4.1.9.10.84.1ciscoRpmsMIBObjectsCISCO-RPMS-MIB
1.3.6.1.4.1.9.10.84.1.2crpmsCustomerProfileCISCO-RPMS-MIB
1.3.6.1.4.1.9.10.84.1.2.1crpmsCpTableCISCO-RPMS-MIB
1.3.6.1.4.1.9.10.84.1.2.1.1crpmsCpEntryCISCO-RPMS-MIB
1.3.6.1.4.1.9.10.84.1.2.1.1.6crpmsCpAttemptedCallsCISCO-RPMS-MIB