COPS-CLIENT-MIB

All MIBs › COPS-CLIENT-MIB

Organization: IETF RSVP Admission Policy Working Group

Last Updated: 2000-09-28

Category: RADIUS and AAA

Description: Defines managed objects for managing a client of the Common Open Policy Service (COPS) protocol, used for network policy control and provisioning.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring COPS-CLIENT-MIB with a free 30-day trial of IPNetwork Monitor.

What Is COPS-CLIENT-MIB?

COPS-CLIENT-MIB is a vendor-neutral IETF standards MIB that defines managed objects for a client implementation of the Common Open Policy Service (COPS) protocol, used for centralized network policy control and provisioning (e.g. QoS or RSVP policy decisions pushed from a Policy Decision Point to network devices). It exposes configuration and status data about the COPS client's connection(s) to policy servers, including server address, port, authentication type, connection state, and keepalive timing. Its monitoring focus is squarely on software/protocol service status rather than hardware: administrators use it to verify whether the COPS client is successfully connected and authenticated to its policy server, track the client's overall state, and watch for failed or stale connection attempts that would leave the device without current policy. It is designed to be used alongside other policy-related standards (the COPS protocol itself, and often paired with RSVP or QoS device MIBs on the same box). It is typically deployed on routers or other network devices that receive dynamic policy provisioning from a centralized COPS policy server in service-provider or large enterprise networks. Engineers implementing or auditing this functionality typically reference the COPS-CLIENT-MIB RFC/standard documentation for the authoritative specification.

IPNetwork Monitor allows you to monitor SNMP objects defined in COPS-CLIENT-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

vendor-neutral, standards-based MIB, not tied to a specific manufacturer; applies to routers and network devices acting as COPS policy clients

Monitoring Examples

An administrator would poll copsClientServerCurrentTable/copsClientServerCurrentEntry to read copsClientServerAddress, copsClientServerTcpPort, copsClientServerAuthType, and copsClientServerLastConnAttempt for the active policy server connection, alongside the overall copsClientState. A copsClientState indicating a disconnected or failed state combined with a recent copsClientServerLastConnAttempt would reveal that the device has lost contact with its policy server and may be running on stale or default policy. copsClientServerKeepaliveTime helps confirm whether keepalive timing is configured aggressively enough to detect such failures quickly.

What Can Be Monitored

COPS policy server connection state
policy server address and port
authentication type
last connection attempt time
keepalive interval
client capabilities

Imported Objects

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32
mib-2

From SNMPv2-TC

RowStatus
TEXTUAL-CONVENTION
TimeInterval
TimeStamp

How to Use in IPNetwork Monitor

Example using copsClientInPkts OID:

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.

OIDs

OID symbolic	OID numeric	Type	Access	Description
copsClientMIB	1.3.6.1.2.1.89			The COPS Client MIB module
copsClientMIBObjects	1.3.6.1.2.1.89.1
copsClientCapabilitiesGroup	1.3.6.1.2.1.89.1.1
BIT copsClientCapabilities	1.3.6.1.2.1.89.1.1.1	Bits	read-only	A list of the optional capabilities that this COPS client supports.
copsClientStatusGroup	1.3.6.1.2.1.89.1.2
copsClientServerCurrentTable	1.3.6.1.2.1.89.1.2.1		not-accessible	A table of information regarding COPS servers as seen from the point of view of a COPS client. This table contains entries for both statically-configured and dynamically-learned servers (from a PDP Redirect operation). One entry exists in this table for each COPS Client-Type served by the COPS server. In addition, an entry will exist with copsClientServerClientType 0 (zero) representing information about the underlying connection itself: this is consistent with the COPS specification which reserves this value for this purpose.
copsClientServerCurrentEntry	1.3.6.1.2.1.89.1.2.1.1		not-accessible	A set of information regarding a single COPS server serving a single COPS Client-Type from the point of view of a COPS client.
IPt copsClientServerAddressType	1.3.6.1.2.1.89.1.2.1.1.1	InetAddressType	not-accessible	The type of address in copsClientServerAddress.
IP copsClientServerAddress	1.3.6.1.2.1.89.1.2.1.1.2	InetAddress	not-accessible	The IPv4, IPv6 or DNS address of a COPS Server. Note that, since this is an index to the table, the DNS name must be short enough to fit into the maximum length of indices allowed by the management protocol in use.
INT copsClientServerClientType	1.3.6.1.2.1.89.1.2.1.1.3	INTEGER	not-accessible	The COPS protocol Client-Type for which this entry applies. Multiple Client-Types can be served by a single COPS server. The value 0 (zero) indicates that this entry contains information about the underlying connection itself.
COP copsClientServerTcpPort	1.3.6.1.2.1.89.1.2.1.1.4	CopsTcpPort	read-only	The TCP port number on the COPS server to which the client should connect/is connected.
COP copsClientServerType	1.3.6.1.2.1.89.1.2.1.1.5	CopsServerEntryType	read-only	Indicator of the source of this COPS server information. COPS servers may be configured by network management into copsClientServerConfigTable and appear in this entry with type copsServerStatic(1). Alternatively, the may be notified from another COPS server by means of the COPS PDP-Redirect mechanism and appear as copsServerRedirect(2).
COP copsClientServerAuthType	1.3.6.1.2.1.89.1.2.1.1.6	CopsAuthType	read-only	Indicator of the current security mode in use between client and this COPS server.
TIM copsClientServerLastConnAttempt	1.3.6.1.2.1.89.1.2.1.1.7	TimeStamp	read-only	Timestamp of the last time that this client attempted to connect to this COPS server.
COP copsClientState	1.3.6.1.2.1.89.1.2.1.1.8	CopsClientState	read-only	The state of the connection and COPS protocol with respect to this COPS server.
NUM copsClientServerKeepaliveTime	1.3.6.1.2.1.89.1.2.1.1.9	TimeInterval	read-only	The value of the COPS protocol Keepalive timeout, in centiseconds, currently in use by this client, as specified by this COPS server in the Client-Accept operation. A value of zero indicates no keepalive activity is expected.
NUM copsClientServerAccountingTime	1.3.6.1.2.1.89.1.2.1.1.10	TimeInterval	read-only	The value of the COPS protocol Accounting timeout, in centiseconds, currently in use by this client, as specified by the COPS server in the Client-Accept operation. A value of zero indicates no accounting activity is to be performed.
C32 copsClientInPktsEx	1.3.6.1.2.1.89.1.2.1.1.11	Counter32	read-only	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.
C32 copsClientOutPkts	1.3.6.1.2.1.89.1.2.1.1.12	Counter32	read-only	A count of the total number of COPS messages that this client has sent to this COPS server marked for this Client-Type. This value is cumulative since agent restart and is not zeroed on new connections.
C32 copsClientInErrs	1.3.6.1.2.1.89.1.2.1.1.13	Counter32	read-only	A count of the total number of COPS messages that this client has received from this COPS server marked for this Client-Type that contained errors in syntax. This value is cumulative since agent restart and is not zeroed on new connections.
COP copsClientLastError	1.3.6.1.2.1.89.1.2.1.1.14	CopsErrorCode	read-only	The code contained in the last COPS protocol Error Object received by this client from this COPS server marked for this Client-Type. This value is not zeroed on COPS Client-Open operations.
C32 copsClientTcpConnectAttempts	1.3.6.1.2.1.89.1.2.1.1.15	Counter32	read-only	A count of the number of times that this COPS client has tried (successfully or otherwise) to open an TCP connection to a COPS server. This value is cumulative since agent restart and is not zeroed on new connections. This value is not incremented for entries representing a non-zero Client-Type.
C32 copsClientTcpConnectFailures	1.3.6.1.2.1.89.1.2.1.1.16	Counter32	read-only	A count of the number of times that this COPS client has failed to open an TCP connection to a COPS server. This value is cumulative since agent restart and is not zeroed on new connections. This value is not incremented for entries representing a non-zero Client-Type.
C32 copsClientOpenAttempts	1.3.6.1.2.1.89.1.2.1.1.17	Counter32	read-only	A count of the number of times that this COPS client has tried to perform a COPS Client-Open to a COPS server for this Client-Type. This value is cumulative since agent restart and is not zeroed on new connections.
C32 copsClientOpenFailures	1.3.6.1.2.1.89.1.2.1.1.18	Counter32	read-only	A count of the number of times that this COPS client has failed to perform a COPS Client-Open to a COPS server for this Client-Type. This value is cumulative since agent restart and is not zeroed on new connections.
C32 copsClientErrUnsupportClienttype	1.3.6.1.2.1.89.1.2.1.1.19	Counter32	read-only	A count of the total number of COPS messages that this client has received from COPS servers that referred to Client-Types that are unsupported by this client. This value is cumulative since agent restart and is not zeroed on new connections. This value is not incremented for entries representing a non-zero Client-Type.
C32 copsClientErrUnsupportedVersion	1.3.6.1.2.1.89.1.2.1.1.20	Counter32	read-only	A count of the total number of COPS messages that this client has received from COPS servers marked for this Client-Type that had a COPS protocol Version number that is unsupported by this client. This value is cumulative since agent restart and is not zeroed on new connections.
C32 copsClientErrLengthMismatch	1.3.6.1.2.1.89.1.2.1.1.21	Counter32	read-only	A count of the total number of COPS messages that this client has received from COPS servers marked for this Client-Type that had a COPS protocol Message Length that did not match the actual received message. This value is cumulative since agent restart and is not zeroed on new connections.
C32 copsClientErrUnknownOpcode	1.3.6.1.2.1.89.1.2.1.1.22	Counter32	read-only	A count of the total number of COPS messages that this client has received from COPS servers marked for this Client-Type that had a COPS protocol Op Code that was unrecognised by this client. This value is cumulative since agent restart and is not zeroed on new connections.
C32 copsClientErrUnknownCnum	1.3.6.1.2.1.89.1.2.1.1.23	Counter32	read-only	A count of the total number of COPS messages that this client has received from COPS servers marked for this Client-Type that contained a COPS protocol object C-Num that was unrecognised by this client. This value is cumulative since agent restart and is not zeroed on new connections.
C32 copsClientErrBadCtype	1.3.6.1.2.1.89.1.2.1.1.24	Counter32	read-only	A count of the total number of COPS messages that this client has received from COPS servers marked for this Client-Type that contained a COPS protocol object C-Type that was not defined for the C-Nums known by this client. This value is cumulative since agent restart and is not zeroed on new connections.
C32 copsClientErrBadSends	1.3.6.1.2.1.89.1.2.1.1.25	Counter32	read-only	A count of the total number of COPS messages that this client attempted to send to COPS servers marked for this Client-Type that resulted in a transmit error. This value is cumulative since agent restart and is not zeroed on new connections.
C32 copsClientErrWrongObjects	1.3.6.1.2.1.89.1.2.1.1.26	Counter32	read-only	A count of the total number of COPS messages that this client has received from COPS servers marked for this Client-Type that did not contain a permitted set of COPS protocol objects. This value is cumulative since agent restart and is not zeroed on new connections.
C32 copsClientErrWrongOpcode	1.3.6.1.2.1.89.1.2.1.1.27	Counter32	read-only	A count of the total number of COPS messages that this client has received from COPS servers marked for this Client-Type that had a COPS protocol Op Code that should not have been sent to a COPS client e.g. Open-Requests. This value is cumulative since agent restart and is not zeroed on new connections.
C32 copsClientKaTimedoutClients	1.3.6.1.2.1.89.1.2.1.1.28	Counter32	read-only	A count of the total number of times that this client has been shut down for this Client-Type by COPS servers that had detected a COPS protocol Keepalive timeout. This value is cumulative since agent restart and is not zeroed on new connections.
C32 copsClientErrAuthFailures	1.3.6.1.2.1.89.1.2.1.1.29	Counter32	read-only	A count of the total number of times that this client has received a COPS message marked for this Client-Type which could not be authenticated using the authentication mechanism used by this client.
C32 copsClientErrAuthMissing	1.3.6.1.2.1.89.1.2.1.1.30	Counter32	read-only	A count of the total number of times that this client has received a COPS message marked for this Client-Type which did not contain authentication information.
copsClientConfigGroup	1.3.6.1.2.1.89.1.3
copsClientServerConfigTable	1.3.6.1.2.1.89.1.3.1		not-accessible	Table of possible COPS servers to try to connect to in order of copsClientServerConfigPriority. There may be multiple entries in this table for the same server and client-type which specify different security mechanisms: these mechanisms will be attempted by the client in the priority order given. Note that a server learned by means of PDPRedirect always takes priority over any of these configured entries.
copsClientServerConfigEntry	1.3.6.1.2.1.89.1.3.1.1		not-accessible	A set of configuration information regarding a single COPS server from the point of view of a COPS client.
IPt copsClientServerConfigAddrType	1.3.6.1.2.1.89.1.3.1.1.1	InetAddressType	not-accessible	The type of address in copsClientServerConfigAddress.
IP copsClientServerConfigAddress	1.3.6.1.2.1.89.1.3.1.1.2	InetAddress	not-accessible	The IPv4, IPv6 or DNS address of a COPS Server. Note that, since this is an index to the table, the DNS name must be short enough to fit into the maximum length of indices allowed by the management protocol in use.
INT copsClientServerConfigClientType	1.3.6.1.2.1.89.1.3.1.1.3	INTEGER	not-accessible	The COPS protocol Client-Type for which this entry applies and for which this COPS server is capable of serving. Multiple Client-Types can be served by a single COPS server.
COP copsClientServerConfigAuthType	1.3.6.1.2.1.89.1.3.1.1.4	CopsAuthType	not-accessible	The type of authentication mechanism for this COPS client to request when negotiating security at the start of a connection to a COPS server.
COP copsClientServerConfigTcpPort	1.3.6.1.2.1.89.1.3.1.1.5	CopsTcpPort	read-create	The TCP port number on the COPS server to which the client should connect.
I32 copsClientServerConfigPriority	1.3.6.1.2.1.89.1.3.1.1.6	Integer32	read-create	The priority of this entry relative to other entries. COPS client will attempt to contact COPS servers for the appropriate Client-Type. Higher numbers are tried first. The order to be used amongst server entries with the same priority is undefined. COPS servers that are notified to the client using the COPS protocol PDP-Redirect mechanism are always used in preference to any entries in this table.
ROW copsClientServerConfigRowStatus	1.3.6.1.2.1.89.1.3.1.1.7	RowStatus	read-create	State of this entry in the table.
INT copsClientServerConfigRetryAlgrm	1.3.6.1.2.1.89.1.3.2	INTEGER	read-write	The algorithm by which the client should retry when it fails to connect to a COPS server.
U32 copsClientServerConfigRetryCount	1.3.6.1.2.1.89.1.3.3	Unsigned32	read-write	A retry count for use by the retry algorithm. Each retry algorithm needs to specify how it uses this value. For the 'sequential(2)' algorithm, this value is the number of times the client should retry to connect to one COPS server before moving on to another. For the 'roundRobin(3)' algorithm, this value is not used.
NUM copsClientServerConfigRetryIntvl	1.3.6.1.2.1.89.1.3.4	TimeInterval	read-write	A retry interval for use by the retry algorithm. Each retry algorithm needs to specify how it uses this value. For the 'sequential(2)' algorithm, this value is the time to wait between retries of a connection to the same COPS server. For the 'roundRobin(3)' algorithm, the client always attempts to connect to each Server in turn, until one succeeds or they all fail; if they all fail, then the client waits for the value of this interval before restarting the algorithm.
copsClientConformance	1.3.6.1.2.1.89.2
copsClientGroups	1.3.6.1.2.1.89.2.1
copsDeviceStatusGroup	1.3.6.1.2.1.89.2.1.1			A collection of objects for monitoring the status of connections to COPS servers and statistics for a COPS client.
copsDeviceConfigGroup	1.3.6.1.2.1.89.2.1.2			A collection of objects for configuring COPS server information.
copsClientCompliances	1.3.6.1.2.1.89.2.2
copsClientCompliance	1.3.6.1.2.1.89.2.2.1			The compliance statement for device support of management of the COPS client.

RFC description

SNMP management of COPS (Common Open Policy Service) client protocol connections and policy enforcement.

Start monitoring Vendor-neutral COPS policy client (router/network device) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download COPS-CLIENT-MIB