COPS-CLIENT-MIB :: copsClientInPkts

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › COPS-CLIENT-MIB › copsClientInPkts

copsClientInPkts

Module: COPS-CLIENT-MIB

OID (symbolic): COPS-CLIENT-MIB::copsClientInPkts

OID (numeric): 1.3.6.1.2.1.89.1.2.1.1.11

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: A count of the total number of COPS messages that this client has received from this COPS server marked for this Client-Type. This value is cumulative since agent restart and is not zeroed on new connections.

What is copsClientInPkts?

This read-only Counter32, cumulative since agent restart, counts total COPS messages this client has received from a specific server for this Client-Type. An admin watches it to confirm two-way COPS protocol traffic is actively flowing from the policy server. For example, copsClientInPkts staying flat while copsClientOutPkts keeps climbing suggests the server has stopped responding to this client.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.89.1.2.1.1.11
snmpwalk -v2c -c public <target> COPS-CLIENT-MIB::copsClientInPkts

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.89.1.2.1.1.11.1
snmpget -v2c -c public <target> COPS-CLIENT-MIB::copsClientInPkts.1

Start monitoring Vendor-neutral COPS policy client (router/network device) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the COPS-CLIENT-MIB::copsClientInPkts OID value, configure state conditions and alerts, and monitor any Vendor-neutral COPS policy client (router/network device) from a single console.

How to Use in IPNetwork Monitor

Select a device implementing COPS-CLIENT-MIB 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 copsClientInPkts 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 a count of the total number of COPS messages that this client has received from this COPS server marked for this Client-Type. 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, 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 (6 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.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.89copsClientMIBCOPS-CLIENT-MIB
1.3.6.1.2.1.89.1copsClientMIBObjectsCOPS-CLIENT-MIB
1.3.6.1.2.1.89.1.2copsClientStatusGroupCOPS-CLIENT-MIB
1.3.6.1.2.1.89.1.2.1copsClientServerCurrentTableCOPS-CLIENT-MIB
1.3.6.1.2.1.89.1.2.1.1copsClientServerCurrentEntryCOPS-CLIENT-MIB
1.3.6.1.2.1.89.1.2.1.1.11copsClientInPktsCOPS-CLIENT-MIB