ccopsInitialTimeout
CISCO-COPS-CLIENT-MIB ·
.1.3.6.1.4.1.9.9.140.1.1.5
Object
scalar r/w
secondsUnsigned32
If the device can not connect to the last connected COPS
server, it uses this value for the initial retry time-out
and then retries to connect after this time-out period.
This value is re-used for the first retry after every
successful connection.
When the device is connecting to COPS server the first
time or the last connected COPS server is no longer
available, it will attempt to contact COPS servers existing
in ccopsServerConfigTable for the appropriate Client-Type
in the order of their priority values.
Context
- MIB
- CISCO-COPS-CLIENT-MIB
- OID
.1.3.6.1.4.1.9.9.140.1.1.5- Type
- scalar
- Access
- readwrite
- Status
- current
- Units
- seconds
- Parent
- ccopsGlobalObjects
- Groups
- 2
Net-SNMP examples
How SNMP and these commands workScalars have one instance, identified by the .0 suffix.
Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'CISCO-COPS-CLIENT-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-COPS-CLIENT-MIB::ccopsInitialTimeout.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-COPS-CLIENT-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-COPS-CLIENT-MIB::ccopsInitialTimeout'
Syntax
secondsUnsigned32
Values & Constraints
Object Constraints
range: 0-65535
Conformance
Member of