hasSubState – IBM-ENETDISPATCHER-MIB

Object

scalar mandatory Enumeration

High Availability sub state:
          
Synchronized and notSynchronized are normal, synchIn and synchOut are
transitory.  If the Network Dispatcher machine appears to be stuck
(for more than a minute), in a transitory state then that indicates
a problem.
          
If HighAvailability should be running and the substate is notSynchronized,
then that indicates a problem.
          
If High Availability is not running and the hasState is idle, then
all subState data is meaningless and should be ignored.
          
   notSynchronized (0), network dispatcher is not in conact with partner machine
   synchronized    (1), network dispatcher is in contact with partner machine
   sync-in         (2), network dispatcher is going into standby state
   sync-out        (3), network dispatcher is going into active state

Context

MIB: IBM-ENETDISPATCHER-MIB
OID: .1.3.6.1.4.1.2.6.144.1.2.1.6.4
Type: scalar
Access: readonly
Status: mandatory
Parent: indHiAvailStatObjects

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 'IBM-ENETDISPATCHER-MIB' -M '/opt/observium/mibs/ibm:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'IBM-ENETDISPATCHER-MIB::hasSubState.0'

More examples

Translate to a numeric OID

/usr/bin/snmptranslate -Pud -Ir -On -m 'IBM-ENETDISPATCHER-MIB' -M '/opt/observium/mibs/ibm:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'IBM-ENETDISPATCHER-MIB::hasSubState'

Syntax

Enumeration

Values & Constraints

Enumerated Values

`0`	notSynchronized
`1`	synchronized
`2`	syncIn
`3`	syncOut