All MIBs › COPS-CLIENT-MIB › copsClientServerConfigRetryIntvl
copsClientServerConfigRetryIntvl
Module: COPS-CLIENT-MIB
OID (symbolic): COPS-CLIENT-MIB::copsClientServerConfigRetryIntvl
OID (numeric): 1.3.6.1.2.1.89.1.3.4
Node type: OBJECT-TYPE
Type: TimeInterval
Access: read-write
Description: 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.
What is copsClientServerConfigRetryIntvl?
This read-write TimeInterval, in centiseconds, sets a retry interval whose meaning depends on the algorithm: under sequential it is the wait time between retries to the same server, and under roundRobin it is the wait time after cycling through all servers unsuccessfully before starting over. An admin tunes it to control how aggressively or gently the client retries connecting to its COPS servers. For example, an admin increases copsClientServerConfigRetryIntvl to avoid hammering every configured PDP with connection attempts during a broader network outage.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.89.1.3.4 snmpwalk -v2c -c public <target> COPS-CLIENT-MIB::copsClientServerConfigRetryIntvl
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.89.1.3.4.1 snmpget -v2c -c public <target> COPS-CLIENT-MIB::copsClientServerConfigRetryIntvl.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.2.1.89.1.3.4.1 s <value>
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::copsClientServerConfigRetryIntvl OID value, configure state conditions and alerts, and monitor any Vendor-neutral COPS policy client (router/network device) from a single console.
OID Breakdown
Upper-level ancestors (6 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.2 | mgmt | APERTUS-NPG-MIB |
| 1.3.6.1.2.1 | mib_2 | AXON-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.2.1.89 | copsClientMIB | COPS-CLIENT-MIB |
| 1.3.6.1.2.1.89.1 | copsClientMIBObjects | COPS-CLIENT-MIB |
| 1.3.6.1.2.1.89.1.3 | copsClientConfigGroup | COPS-CLIENT-MIB |
| 1.3.6.1.2.1.89.1.3.4 | copsClientServerConfigRetryIntvl | COPS-CLIENT-MIB |