AD | Application | AWS | Azure | Cloud | Database | Enterprise | Environmental | Event Log | File System | Infra | IoT | IT Service | Linux | Network/System | Performance | Protocol | SaaS | Security | Service Level | SNMP | Storage | VMware | VoIP | Web | Wireless

Crumbtrail

MonitorTools.com » Technical documentation » SNMP » MIB » RFC » COPS-CLIENT-MIB » Objects

COPS-CLIENT-MIB.mib object view, vendor RFC

Introduction

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

ActiveXperts Network Monitor 2024 can import MIB file COPS-CLIENT-MIB and use it to monitor vendor specific OID's.

COPS-CLIENT-MIB file content

Object view of COPS-CLIENT-MIB:

Scalar Object
copsClientCapabilities .1.3.6.1.2.1.89.1.1.1
A list of the optional capabilities that this COPS client supports.
copsClientServerCurrentEntry .1.3.6.1.2.1.89.1.2.1.1
A set of information regarding a single COPS server serving a single COPS Client-Type from the point of view of a COPS client.
copsClientServerConfigEntry .1.3.6.1.2.1.89.1.3.1.1
A set of configuration information regarding a single COPS server from the point of view of a COPS client.
copsClientServerConfigRetryAlgrm .1.3.6.1.2.1.89.1.3.2
The algorithm by which the client should retry when it fails to connect to a COPS server.
copsClientServerConfigRetryCount .1.3.6.1.2.1.89.1.3.3
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.
copsClientServerConfigRetryIntvl .1.3.6.1.2.1.89.1.3.4
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.
Tabular Object
copsClientServerAddressType .1.3.6.1.2.1.89.1.2.1.1.1
The type of address in copsClientServerAddress.
copsClientServerAddress .1.3.6.1.2.1.89.1.2.1.1.2
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.
copsClientServerClientType .1.3.6.1.2.1.89.1.2.1.1.3
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.
copsClientServerTcpPort .1.3.6.1.2.1.89.1.2.1.1.4
The TCP port number on the COPS server to which the client should connect/is connected.
copsClientServerType .1.3.6.1.2.1.89.1.2.1.1.5
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).
copsClientServerAuthType .1.3.6.1.2.1.89.1.2.1.1.6
Indicator of the current security mode in use between client and this COPS server.
copsClientServerLastConnAttempt .1.3.6.1.2.1.89.1.2.1.1.7
Timestamp of the last time that this client attempted to connect to this COPS server.
copsClientState .1.3.6.1.2.1.89.1.2.1.1.8
The state of the connection and COPS protocol with respect to this COPS server.
copsClientServerKeepaliveTime .1.3.6.1.2.1.89.1.2.1.1.9
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.
copsClientServerAccountingTime .1.3.6.1.2.1.89.1.2.1.1.10
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.
copsClientInPkts .1.3.6.1.2.1.89.1.2.1.1.11
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.
copsClientOutPkts .1.3.6.1.2.1.89.1.2.1.1.12
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.
copsClientInErrs .1.3.6.1.2.1.89.1.2.1.1.13
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.
copsClientLastError .1.3.6.1.2.1.89.1.2.1.1.14
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.
copsClientTcpConnectAttempts .1.3.6.1.2.1.89.1.2.1.1.15
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.
copsClientTcpConnectFailures .1.3.6.1.2.1.89.1.2.1.1.16
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.
copsClientOpenAttempts .1.3.6.1.2.1.89.1.2.1.1.17
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.
copsClientOpenFailures .1.3.6.1.2.1.89.1.2.1.1.18
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.
copsClientErrUnsupportClienttype .1.3.6.1.2.1.89.1.2.1.1.19
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.
copsClientErrUnsupportedVersion .1.3.6.1.2.1.89.1.2.1.1.20
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.
copsClientErrLengthMismatch .1.3.6.1.2.1.89.1.2.1.1.21
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.
copsClientErrUnknownOpcode .1.3.6.1.2.1.89.1.2.1.1.22
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.
copsClientErrUnknownCnum .1.3.6.1.2.1.89.1.2.1.1.23
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.
copsClientErrBadCtype .1.3.6.1.2.1.89.1.2.1.1.24
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.
copsClientErrBadSends .1.3.6.1.2.1.89.1.2.1.1.25
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.
copsClientErrWrongObjects .1.3.6.1.2.1.89.1.2.1.1.26
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.
copsClientErrWrongOpcode .1.3.6.1.2.1.89.1.2.1.1.27
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.
copsClientKaTimedoutClients .1.3.6.1.2.1.89.1.2.1.1.28
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.
copsClientErrAuthFailures .1.3.6.1.2.1.89.1.2.1.1.29
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.
copsClientErrAuthMissing .1.3.6.1.2.1.89.1.2.1.1.30
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.
copsClientServerConfigAddrType .1.3.6.1.2.1.89.1.3.1.1.1
The type of address in copsClientServerConfigAddress.
copsClientServerConfigAddress .1.3.6.1.2.1.89.1.3.1.1.2
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.
copsClientServerConfigClientType .1.3.6.1.2.1.89.1.3.1.1.3
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.
copsClientServerConfigAuthType .1.3.6.1.2.1.89.1.3.1.1.4
The type of authentication mechanism for this COPS client to request when negotiating security at the start of a connection to a COPS server.
copsClientServerConfigTcpPort .1.3.6.1.2.1.89.1.3.1.1.5
The TCP port number on the COPS server to which the client should connect.
copsClientServerConfigPriority .1.3.6.1.2.1.89.1.3.1.1.6
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.
copsClientServerConfigRowStatus .1.3.6.1.2.1.89.1.3.1.1.7
State of this entry in the table.
Table
copsClientServerCurrentTable .1.3.6.1.2.1.89.1.2.1
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.
copsClientServerConfigTable .1.3.6.1.2.1.89.1.3.1
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.
Object Identifier
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
copsClientStatusGroup .1.3.6.1.2.1.89.1.2
copsClientConfigGroup .1.3.6.1.2.1.89.1.3
copsClientConformance .1.3.6.1.2.1.89.2
copsClientGroups .1.3.6.1.2.1.89.2.1
copsClientCompliances .1.3.6.1.2.1.89.2.2
Group
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.