MIB Browser

VMWARE-VCHA-MIB

VMware Inc.
This MIB module describes the vCenter High Availability Service (VCHA).
 A VCHA cluster consists of three VMs identified by a single instance UUID.
 One is the Active vCenter VM that serves client requests. Second is the
 Passive VM that is identical to the Active vCenter VM in terms of database
 and filesystem state. Passive VM constantly receives updates from Active
 VM and takes over the role of Active vCenter VM in the event of a
 failover. Third is the Witness VM that acts as a quorum VM in a VCHA
 cluster. The sole purpose of Witness VM is to avoid classic split-brain
 problem in a VCHA cluster.

                         client
                            +
                            |
                            |
           +----------------v---+       +--------------------+
           |            Public IP       |                    |
           |                    |       |                    |
           |   Active vCenter   |       |  Passive vCenter   |
           |                    |       |                    |
           +---Private-IP+------+       +------+Private-IP---+
                    ^ <--------------------------> ^
                    |    DB & File replication     |
                     +                            +
                      +                          +
                       +                        +
                        +------>    <----------+
                          +----Private-IP----+
                          |                  |
                          |  Witness vCenter |
                          |     (Quorum)     |
                          |                  |
                          +------------------+

All events will not be repeated for the duration of a given state entered.

It is highly recommended that the administrator links the SNMP trap receiver
to both public network and vCenter HA cluster network, so that the
monitoring system is able to get notified as long as one of the
networks is up.
Organization
VMware, Inc
Root OID
1.3.6.1.4.1.6876.53.1
Last updated
Objects
38
Source
Show full MIB
snmptranslate -m VMWARE-VCHA-MIB -Tp
snmpwalk -v2c -c <community> -m VMWARE-VCHA-MIB <host> 1.3.6.1.4.1.6876.53.1

Imports

INET-ADDRESS-MIBInetAddress, InetAddressType
SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP
SNMPv2-SMIBits, Integer32, IpAddress, MODULE-IDENTITY, MibIdentifier, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, TimeTicks, Unsigned32, iso
SNMPv2-TCDisplayString, PhysAddress, TEXTUAL-CONVENTION, TruthValue
VMWARE-ROOT-MIBvmwVCHA

OID tree

NameOIDTypeAccessStatus
NvmwVCHANotifications1.3.6.1.4.1.6876.53.0
!vmwVchaNodeJoined1.3.6.1.4.1.6876.53.0.100
!vmwVchaNodeLeft1.3.6.1.4.1.6876.53.0.105
!vmwVchaNodeIsolated1.3.6.1.4.1.6876.53.0.110
!vmwVchaClusterStateChanged1.3.6.1.4.1.6876.53.0.130
!vmwVchaClusterModeChanged1.3.6.1.4.1.6876.53.0.150
!vmwVchaPublicIpUp1.3.6.1.4.1.6876.53.0.205
!vmwVchaPublicIpDown1.3.6.1.4.1.6876.53.0.206
!vmwVchaFailoverTriggered1.3.6.1.4.1.6876.53.0.210
!vmwVchaFailoverSucceeded1.3.6.1.4.1.6876.53.0.220
!vmwVchaFailoverFailedDisabledMode1.3.6.1.4.1.6876.53.0.225
!vmwVchaFailoverFailedNodeLost1.3.6.1.4.1.6876.53.0.226
!vmwVchaFailoverFailedPassiveNotReady1.3.6.1.4.1.6876.53.0.227
!vmwVchaContinueAsActive1.3.6.1.4.1.6876.53.0.230
!vmwVchaDbReplicationStateChanged1.3.6.1.4.1.6876.53.0.300
!vmwVchaFileReplicationStateChanged1.3.6.1.4.1.6876.53.0.350
IvmwVchaMIB1.3.6.1.4.1.6876.53.1
NvmwVchaMIBConformance1.3.6.1.4.1.6876.53.1.2
NvmwVchaMIBCompliances1.3.6.1.4.1.6876.53.1.2.1
MvmwVchaMIBBasicComplianceRev21.3.6.1.4.1.6876.53.1.2.1.3
NvmwVchaMIBGroups1.3.6.1.4.1.6876.53.1.2.2
GvmwVchaNotificationInfoGroup1.3.6.1.4.1.6876.53.1.2.2.1
GvmwVchaNotificationGroup1.3.6.1.4.1.6876.53.1.2.2.2
SvmwVchaInstanceUuid1.3.6.1.4.1.6876.53.5OCTET STRINGAN
SvmwVchaPrivateAddressType1.3.6.1.4.1.6876.53.11InetAddressTypeAN
SvmwVchaPublicAddressType1.3.6.1.4.1.6876.53.12InetAddressTypeAN
SvmwVchaPrivateAddressAddr1.3.6.1.4.1.6876.53.15InetAddressAN
SvmwVchaPublicAddressAddr1.3.6.1.4.1.6876.53.16InetAddressAN
SvmwVchaTargetNodeRole1.3.6.1.4.1.6876.53.20VmwVchaNodeRoleTypeAN
SvmwVchaClusterState1.3.6.1.4.1.6876.53.25VmwVchaClusterStateTypeAN
SvmwVchaClusterMode1.3.6.1.4.1.6876.53.30VmwVchaClusterModeTypeAN
SvmwVchaIsPlannedFailover1.3.6.1.4.1.6876.53.40TruthValueAN
SvmwVchaDbReplicationState1.3.6.1.4.1.6876.53.50VmwVchaDbReplicationStateTypeAN
SvmwVchaIsFileProviderInSync1.3.6.1.4.1.6876.53.55TruthValueAN
SvmwVchaFileReplicationProvider1.3.6.1.4.1.6876.53.60VmwVchaFileReplicationProviderTypeAN
NvmwVchaActive1.3.6.1.4.1.6876.53.250
NvmwVchaPassive1.3.6.1.4.1.6876.53.255
NvmwVchaWitness1.3.6.1.4.1.6876.53.260

Textual conventions

VmwVchaClusterModeType INTEGER

disabled(2) enabled(1) maintenance(3)

Represent VCHA cluster modes: enabled, disabled or maintenance:

enabled (1)     State replication between Active and Passive nodes
                is enabled and automatic failover happens if the
                Active node fails while the VCHA cluster is healthy.

disabled (2)    All three nodes are part of VCHA cluster but the
                state replication and automatic failover are
                disabled.

maintenance (3) All three nodes are part of VCHA cluster but
                automatic failover is disabled while state
                replication continues. The Active node continues to
                serve client requests even if Passive and Witness
                nodes are lost.
VmwVchaClusterStateType INTEGER

degraded(2) healthy(1) isolated(3)

Represent the health state of the vCenter HA cluster.

healthy (1)     All three nodes in a VCHA cluster are healthy and
                connected. State replication between the Active and
                Passive nodes is working and both nodes are in-sync.

degraded (2)    A VCHA cluster is said to be in degraded state when
                it has lost one of the three nodes. Node loss can
                be due to various reasons and as a result, the lost
                node is not visible to other two nodes. If the
                Active node is lost, the Passive node will take the
                role of the Active node. If the Passive or Witness
                node is lost, the Active node will continue to serve
                requests. A VCHA cluster can also be in degraded
                state if state replication fails between the Active
                and Passive nodes.

isolated (3)    All three nodes are isolated from each other. If
                this happens when VCHA cluster is in enabled mode,
                the Active node stops serving client requests. If
                nodes are isolated in a disabled VCHA cluster mode,
                the Active node continues to serve client requests.
VmwVchaDbReplicationStateType INTEGER

async(4) noReplication(1) sync(3)

Represent DB replication states: sync, async or no replication.

noReplication (1)   There is no DB replication between the Active
                    and Passive nodes. This could happen when
                    vPostgres is not running on the Passive node.

sync (3)            In sync state, the Passive vCenter keeps the
                    up-to-date state with the Active vCenter.

async (4)           Async state replication makes the state of
                    Passive node fall behind the Active vCenter.
                    This causes a data loss when an automatic
                    failover happens.
VmwVchaFileReplicationProviderType INTEGER

serviceConfig(1) serviceState(2)

Represent the file replication providers.

serviceConfig (1)   This provider maintains the replication of
                    service configuration files, which are small in
                    size.

serviceState (2)    This provider maintains the replication of
                    service state files, which are large in size.
VmwVchaNodeRoleType INTEGER

active(1) passive(2) unknown(4) witness(3)

Represent the role each node in the cluster is running as.
active (1)      Active vCenter serves client requests.

passive (2)     Passive node is identical to the Active node in
                terms of database and filesystem state. Passive
                node constantly receives updates from the Active
                node and takes over the role of Active node in the
                event of a failover.

witness (3)     Witness node acts as a quorum node in a vCenter HA
                cluster. Sole purpose of Witness VM is to avoid
                the classic split-brain problem in a VCHA cluster.

unknown (4)     Node without any role assigned.

Traps / Notifications

Groups and compliance