cRFCfgNotifTimer

CISCO-RF-MIB · .1.3.6.1.4.1.9.9.176.1.2.8

Object

scalar r/w millisecondsSNMPv2-SMIUnsigned32

Note that the term 'notification' here refers to an RF
notification and not an SNMP notification.
          
As the standby unit progresses to the 'standbyHot' state,
asynchronous messages are sent from the active unit to the
standby unit which must then be acknowledged by the standby
unit. If the active unit receives the acknowledgement during
the time period specified by this object, progression proceeds
as normal. If the timer expires and an acknowledgement was not
received by the active unit, a switch of activity occurs.

Context

MIB: CISCO-RF-MIB
OID: .1.3.6.1.4.1.9.9.176.1.2.8
Type: scalar
Access: readwrite
Status: current
Units: milliseconds
Parent: cRFCfg
Groups: 2

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 'CISCO-RF-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-RF-MIB::cRFCfgNotifTimer.0'

More examples

Translate to a numeric OID

/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-RF-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-RF-MIB::cRFCfgNotifTimer'

Syntax

millisecondsSNMPv2-SMIUnsigned32

Source: SNMPv2-SMIUnsigned32
Base type: Unsigned32

Values & Constraints

Type Constraints

range: 0..4294967295