copsClientServerConfigRetryCount

COPS-CLIENT-MIB · .1.3.6.1.2.1.89.1.3.3
Commands MIB view Table view

Object

scalar r/w SNMPv2-SMIUnsigned32 
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.

Context

MIB
COPS-CLIENT-MIB
OID
.1.3.6.1.2.1.89.1.3.3
Type
scalar
Access
readwrite
Status
current
Parent
copsClientConfigGroup
Groups
1

Net-SNMP examples

How SNMP and these commands work

Scalars have one instance, identified by the .0 suffix.

Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'COPS-CLIENT-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'COPS-CLIENT-MIB::copsClientServerConfigRetryCount.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'COPS-CLIENT-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'COPS-CLIENT-MIB::copsClientServerConfigRetryCount'

Syntax

SNMPv2-SMIUnsigned32
Source
SNMPv2-SMIUnsigned32
Base type
Unsigned32

Values & Constraints

Type Constraints
range: 0..4294967295

Conformance

Member of
copsDeviceConfigGroup
Compliance refinements
copsClientCompliance readonly
Write access is required only if the device supports the
configuration of COPS server information.