gpsHP5071AQuesNibble1Data

MERIDIAN2-MIB · .1.3.6.1.4.1.13827.14.2.79

Object

scalar Bits

This is a bit string contained in one character representing the second
nibble of the optional HP5071A Cesium Questionable Data word.  Unfortunately, 
SNMP numbers the bits in the reverse order, so that the enumerated values are 
backwards from the description contained in the HP5071A User's Manual for the 
Questionable status register.  Each bit indicates a Questionable state when set.  
Currently defined states encoded in this value:
          
Bit 3:    Not Used.
Bit 2:    HP5071A Frequency is unlocked.
Bit 1:    HP5071A Phase has perturbations.
Bit 0:    Not Used.

Context

MIB: MERIDIAN2-MIB
OID: .1.3.6.1.4.1.13827.14.2.79
Type: scalar
Access: readonly
Status: current
Parent: gps

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 'MERIDIAN2-MIB' -M '/opt/observium/mibs/endrun:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'MERIDIAN2-MIB::gpsHP5071AQuesNibble1Data.0'

More examples

Translate to a numeric OID

/usr/bin/snmptranslate -Pud -Ir -On -m 'MERIDIAN2-MIB' -M '/opt/observium/mibs/endrun:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'MERIDIAN2-MIB::gpsHP5071AQuesNibble1Data'

Syntax

Bits

Values & Constraints

Enumerated Values

`0`	csNotUsed0
`1`	csPhase
`2`	csFrequency
`3`	csNotUsed3