Reference record for OID 1.3.6.1.4.1.2.6.144.1.2.1.6.4



parent
1.3.6.1.4.1.2.6.144.1.2.1.6 (indHiAvailStatObjects)
node code
4
node name
hasSubState
dot oid
1.3.6.1.4.1.2.6.144.1.2.1.6.4
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ibm(2) ibmProd(6) ibmENetDispatcher(144) dispatcherMib(1) indSrvrGoneDown(2) indStatus(1) indHiAvailStatObjects(6) hasSubState(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ibm(2) ibmProd(6) ibmENetDispatcher(144) dispatcherMib(1) dispatcherMibObjects(2) indStatus(1) indHiAvailStatObjects(6) hasSubState(4)}
  • ...skipped...
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) ibm(2) prod(6) ibmENetDispatcher(144) dispatcherMib(1) indSrvrGoneDown(2) indStatus(1) indHiAvailStatObjects(6) hasSubState(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) ibm(2) prod(6) ibmENetDispatcher(144) dispatcherMib(1) dispatcherMibObjects(2) indStatus(1) indHiAvailStatObjects(6) hasSubState(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) ibm(2) ibmProd(6) ibmENetDispatcher(144) dispatcherMib(1) indSrvrGoneDown(2) indStatus(1) indHiAvailStatObjects(6) hasSubState(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) ibm(2) ibmProd(6) ibmENetDispatcher(144) dispatcherMib(1) dispatcherMibObjects(2) indStatus(1) indHiAvailStatObjects(6) hasSubState(4)}
  • ...skipped...
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ibm(2) prod(6) ibmENetDispatcher(144) dispatcherMib(1) indSrvrGoneDown(2) indStatus(1) indHiAvailStatObjects(6) hasSubState(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ibm(2) prod(6) ibmENetDispatcher(144) dispatcherMib(1) dispatcherMibObjects(2) indStatus(1) indHiAvailStatObjects(6) hasSubState(4)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/ibm/ibmProd/ibmENetDispatcher/dispatcherMib/indSrvrGoneDown/indStatus/indHiAvailStatObjects/hasSubState
  • /iso/identified-organization/dod/internet/private/enterprise/ibm/ibmProd/ibmENetDispatcher/dispatcherMib/dispatcherMibObjects/indStatus/indHiAvailStatObjects/hasSubState
  • ...skipped...
  • /iso/org/dod/internet/private/enterprise/ibm/prod/ibmENetDispatcher/dispatcherMib/indSrvrGoneDown/indStatus/indHiAvailStatObjects/hasSubState
  • /iso/org/dod/internet/private/enterprise/ibm/prod/ibmENetDispatcher/dispatcherMib/dispatcherMibObjects/indStatus/indHiAvailStatObjects/hasSubState
  • /iso/org/dod/internet/private/enterprises/ibm/ibmProd/ibmENetDispatcher/dispatcherMib/indSrvrGoneDown/indStatus/indHiAvailStatObjects/hasSubState
  • /iso/org/dod/internet/private/enterprises/ibm/ibmProd/ibmENetDispatcher/dispatcherMib/dispatcherMibObjects/indStatus/indHiAvailStatObjects/hasSubState
  • ...skipped...
  • /iso/iso-identified-organization/dod/internet/private/enterprises/ibm/prod/ibmENetDispatcher/dispatcherMib/indSrvrGoneDown/indStatus/indHiAvailStatObjects/hasSubState
  • /iso/iso-identified-organization/dod/internet/private/enterprises/ibm/prod/ibmENetDispatcher/dispatcherMib/dispatcherMibObjects/indStatus/indHiAvailStatObjects/hasSubState
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/2/6/144/1/2/1/6/4

    Description by mibdepot

    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

    Parsed from file ibmenetd.mib.txt
    Company: None
    Module: IBM-ENETDISPATCHER-MIB

    Description by circitor

    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

    Parsed from file IBM-ENETDISPATCHER-MIB.mib
    Module: IBM-ENETDISPATCHER-MIB

    Information by oid_info

    Vendor: IBM
    Module: IBM-ENETDISPATCHER-MIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    hasSubState OBJECT-TYPE SYNTAX INTEGER { notSynchronized(0), synchronized(1), syncIn(2), syncOut(3) } ACCESS read-only STATUS mandatory DESCRIPTION "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" ::= { indHiAvailStatObjects 4 }

    Information by circitor

    hasSubState OBJECT-TYPE SYNTAX INTEGER { notSynchronized(0), synchronized(1), syncIn(2), syncOut(3) } ACCESS read-only STATUS mandatory DESCRIPTION "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" ::= { indHiAvailStatObjects 4 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.2)

    Bob Moore

    Children (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.2.6.144.1.2.1.6.4.0 hasSubState 0 0 None

    Brothers (3)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.2.6.144.1.2.1.6.1 hasPrimary 1 1 Indicates whether this machine is the primary or backup machine.
    -primary (0)
    -backup (1)
    1.3.6.1.4.1.2.6.144.1.2.1.6.2 hasPort 1 1 Port used by both primary and backup Network Dispatcher machines for
    heartbeat messages.
    1.3.6.1.4.1.2.6.144.1.2.1.6.3 hasState 1 1 Status of this Network Dispatcher machine.
    -idle, (0) this machine is routing packets and is not trying
    to establish contact wi…