cRFStatusFailoverTime

CISCO-RF-MIB · .1.3.6.1.4.1.9.9.176.1.1.9
Commands MIB view Table view

Object

scalar SNMPv2-TCTimeStamp 
The value of sysUpTime when the primary redundant unit took over
as active. The value of this object will be 0 till the first
switchover.

Context

MIB
CISCO-RF-MIB
OID
.1.3.6.1.4.1.9.9.176.1.1.9
Type
scalar
Access
readonly
Status
current
Parent
cRFStatus
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 'CISCO-RF-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-RF-MIB::cRFStatusFailoverTime.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::cRFStatusFailoverTime'

Syntax

SNMPv2-TCTimeStamp
Source
SNMPv2-TCTimeStamp
Base type
Unsigned32
Based on
SNMPv2-SMITimeTicks
Type Description
The value of the sysUpTime object at which a specific
occurrence happened.  The specific occurrence must be
          
defined in the description of any object defined using this
type.
          
If sysUpTime is reset to zero as a result of a re-
initialization of the network management (sub)system, then
the values of all TimeStamp objects are also reset.
However, after approximately 497 days without a re-
initialization, the sysUpTime object will reach 2^^32-1 and
then increment around to zero; in this case, existing values
of TimeStamp objects do not change.  This can lead to
ambiguities in the value of TimeStamp objects.

Values & Constraints

No enumerated values or constraints recorded.

Conformance

Member of
ciscoRFStatusGroupRev1