Standard view Table view

VMWARE-VCHA-MIB

        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.
Source file
VMWARE-VCHA-MIB
Last revised
Identity
vmwVchaMIB
Base OID
1.3.6.1.4.1.6876.53.1
Imported Objects
INET-ADDRESS-MIB InetAddress InetAddressType
SNMPv2-CONF MODULE-COMPLIANCE NOTIFICATION-GROUP OBJECT-GROUP
SNMPv2-SMI MODULE-IDENTITY NOTIFICATION-TYPE OBJECT-TYPE
SNMPv2-TC TEXTUAL-CONVENTION TruthValue
VMWARE-ROOT-MIB vmwVCHA
Net-SNMP examples using the vmware MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'VMWARE-VCHA-MIB' -M '/opt/observium/mibs/vmware:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'VMWARE-VCHA-MIB::vmwVchaMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'VMWARE-VCHA-MIB' -M '/opt/observium/mibs/vmware:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'VMWARE-VCHA-MIB::vmwVchaMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (20)
vmwVCHANotifications
.1.3.6.1.4.1.6876.53.0
vmwVchaMIB
.1.3.6.1.4.1.6876.53.1
vmwVchaMIBConformance
.1.3.6.1.4.1.6876.53.1.2
vmwVchaMIBCompliances
.1.3.6.1.4.1.6876.53.1.2.1
vmwVchaMIBGroups
.1.3.6.1.4.1.6876.53.1.2.2
vmwVchaPrivateAddressType
INET-ADDRESS-MIBInetAddressType
 .1.3.6.1.4.1.6876.53.11
vmwVchaPublicAddressType
INET-ADDRESS-MIBInetAddressType
 .1.3.6.1.4.1.6876.53.12
vmwVchaPrivateAddressAddr
INET-ADDRESS-MIBInetAddress
 .1.3.6.1.4.1.6876.53.15
vmwVchaPublicAddressAddr
INET-ADDRESS-MIBInetAddress
 .1.3.6.1.4.1.6876.53.16
vmwVchaTargetNodeRole
VmwVchaNodeRoleType
 .1.3.6.1.4.1.6876.53.20
vmwVchaClusterState
VmwVchaClusterStateType
 .1.3.6.1.4.1.6876.53.25
vmwVchaActive
.1.3.6.1.4.1.6876.53.250
vmwVchaPassive
.1.3.6.1.4.1.6876.53.255
vmwVchaWitness
.1.3.6.1.4.1.6876.53.260
vmwVchaClusterMode
VmwVchaClusterModeType
 .1.3.6.1.4.1.6876.53.30
vmwVchaIsPlannedFailover
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.6876.53.40
vmwVchaInstanceUuid
OctetString
 .1.3.6.1.4.1.6876.53.5
vmwVchaDbReplicationState
VmwVchaDbReplicationStateType
 .1.3.6.1.4.1.6876.53.50
vmwVchaIsFileProviderInSync
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.6876.53.55
vmwVchaFileReplicationProvider
VmwVchaFileReplicationProviderType
 .1.3.6.1.4.1.6876.53.60
Dependencies (5) 5 direct Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. SNMPv2-TCrfc
  3. INET-ADDRESS-MIBrfc
  4. SNMPv2-CONFrfc
  5. VMWARE-ROOT-MIBvmware
  6. VMWARE-VCHA-MIBvmwareselected
Type Definitions (5)
VmwVchaClusterModeType
Enumeration
enabled(1)
disabled(2)
maintenance(3)
VmwVchaClusterStateType
Enumeration
healthy(1)
degraded(2)
isolated(3)
VmwVchaDbReplicationStateType
Enumeration
noReplication(1)
sync(3)
async(4)
VmwVchaFileReplicationProviderType
Enumeration
serviceConfig(1)
serviceState(2)
VmwVchaNodeRoleType
Enumeration
active(1)
passive(2)
witness(3)
unknown(4)
Conformance Groups (2)
vmwVchaNotificationInfoGroup
vmwVchaInstanceUuid vmwVchaPrivateAddressAddr vmwVchaPrivateAddressType vmwVchaPublicAddressAddr vmwVchaPublicAddressType vmwVchaTargetNodeRole vmwVchaClusterState vmwVchaClusterMode vmwVchaIsPlannedFailover vmwVchaDbReplicationState vmwVchaIsFileProviderInSync vmwVchaFileReplicationProvider
These objects provide notification details.
 .1.3.6.1.4.1.6876.53.1.2.2.1
vmwVchaNotificationGroup
vmwVchaNodeJoined vmwVchaNodeLeft vmwVchaNodeIsolated vmwVchaClusterStateChanged vmwVchaClusterModeChanged vmwVchaPublicIpUp vmwVchaPublicIpDown vmwVchaFailoverTriggered vmwVchaFailoverSucceeded vmwVchaFailoverFailedDisabledMode vmwVchaFailoverFailedNodeLost vmwVchaFailoverFailedPassiveNotReady vmwVchaContinueAsActive vmwVchaDbReplicationStateChanged vmwVchaFileReplicationStateChanged
Group of objects describing notifications (traps).
 .1.3.6.1.4.1.6876.53.1.2.2.2
Compliance Statements (1)

OID .1.3.6.1.4.1.6876.53.1.2.1.3
The compliance statement for entities which implement VMWARE-VCHA-MIB.
Required groups
mandatory vmwVchaNotificationInfoGroup
mandatory vmwVchaNotificationGroup
Notifications / Traps (15)
NameOIDDescription
vmwVchaNodeJoined
vmwVchaInstanceUuid vmwVchaPrivateAddressType vmwVchaPrivateAddressAddr vmwVchaTargetNodeRole
.1.3.6.1.4.1.6876.53.0.100
This informative notification is sent from the Active node when it
notices a peer node rejoin the cluster. It is sent only once.
vmwVchaNodeLeft
vmwVchaInstanceUuid vmwVchaPrivateAddressType vmwVchaPrivateAddressAddr vmwVchaTargetNodeRole
.1.3.6.1.4.1.6876.53.0.105
This warning notification is sent from the Active node when it notices
a peer node has left the cluster. This is sent only once. Operator
should check the liveness and connectivity of the departed node and try
to bring it back by either rebooting the appliance or resolving the
network problem.
vmwVchaNodeIsolated
vmwVchaInstanceUuid vmwVchaPrivateAddressType vmwVchaPrivateAddressAddr vmwVchaTargetNodeRole
.1.3.6.1.4.1.6876.53.0.110
This warning notification is sent when a node is network isolated from
the cluster. This notification can only be sent from the isolated node,
not by other nodes in the cluster. After being isolated, the node will
reboot itself trigging coldStart notification. In case of Active node
failure, the cluster will trigger a reelection and every slave node will
be declared as isolated temporarily before the cluster re-election
completes.
vmwVchaClusterStateChanged
vmwVchaInstanceUuid vmwVchaClusterState
.1.3.6.1.4.1.6876.53.0.130
This notification is sent only once from the Active node when vCenter
HA cluster state changes to either healthy, degraded or isolated. Please
see VmwVchaClusterStateType for detailed description of each state. And
administrator should receive another notification describing the state
change of cluster subsystem (cluster membership, DB replication or file
replication) which is trigger of cluster state change.
vmwVchaClusterModeChanged
vmwVchaInstanceUuid vmwVchaClusterMode
.1.3.6.1.4.1.6876.53.0.150
This notification is sent only once from the Active node when vCenter
HA cluster mode changes to either enabled, maintenance or disabled.
vmwVchaPublicIpUp
vmwVchaInstanceUuid vmwVchaPublicAddressType vmwVchaPublicAddressAddr
.1.3.6.1.4.1.6876.53.0.205
This informative notification is sent only once when the public IP
address is brought up on the Active node. At this time, the Active node
is reachable from the client and will be able to serve client requests
when services are up and running.
vmwVchaPublicIpDown
vmwVchaInstanceUuid vmwVchaPublicAddressType vmwVchaPublicAddressAddr
.1.3.6.1.4.1.6876.53.0.206
This informative notification is sent only once when the public
network interface is brought down on the Active node. This can happen
when InitiateFailover is invoked on the Active node or vcha process
gracefully shuts down resulting in a reboot of the appliance (triggered
by network isolation). During this time, clients cannot connect to
vCenter Server and users will experience downtime until the public
network interface is brought up. In either case, users should not
expect more than five minutes of downtime. If VCHA cluster is still not
connectable, the operator should verify the reachability of each node
through the cluster network.
vmwVchaFailoverTriggered
vmwVchaInstanceUuid vmwVchaIsPlannedFailover
.1.3.6.1.4.1.6876.53.0.210
This informative notification is sent only once when a failover is
triggered from the Active node to Passive node. Passive node should
take over the Active role if the cluster is in healthy state.
vmwVchaFailoverSucceeded
vmwVchaInstanceUuid
.1.3.6.1.4.1.6876.53.0.220
This informative notification is sent only once when the Passive node
takes over the Active role and brings up the public network interface.
vmwVchaFailoverFailedDisabledMode
vmwVchaInstanceUuid
.1.3.6.1.4.1.6876.53.0.225
This warning notification is sent only once when the Active node fails
to initiate a failover because the cluster is in disabled mode.
vmwVchaFailoverFailedNodeLost
vmwVchaInstanceUuid
.1.3.6.1.4.1.6876.53.0.226
This warning notification is sent only once when the Active node fails
to initiate a failover because the cluster does not have all three
nodes connected.
vmwVchaFailoverFailedPassiveNotReady
vmwVchaInstanceUuid
.1.3.6.1.4.1.6876.53.0.227
This warning notification is sent only once when the Active node fails
to initiate a failover because vPostgres service on the Passive node is
not ready to take over.
vmwVchaContinueAsActive
vmwVchaInstanceUuid
.1.3.6.1.4.1.6876.53.0.230
This informative notification is sent only once when the last Active
node continue as the Active node to servce client's request. This can
happen in many scenarios:
1. After triggering a planned failover, DB or file replicator failed to
flush data to the Passive node and failover didn't proceed because of
data loss.
2. After triggering a planned or forced failover, Passive node failed to
pick up the Active role for reasons like: auto failover cannot happen in
maintenance mode or cluster is in disabled mode.
vmwVchaDbReplicationStateChanged
vmwVchaInstanceUuid vmwVchaDbReplicationState
.1.3.6.1.4.1.6876.53.0.300
This informative notification is sent only once from the Active node
when database replication state changes to sync, async or no
replication. Database replication is not healthy when it is in async or
no replication state. Reasons include large network delays or vPostgres
service becoming unresponsive on the Passive node.
vmwVchaFileReplicationStateChanged
vmwVchaInstanceUuid vmwVchaFileReplicationProvider vmwVchaIsFileProviderInSync
.1.3.6.1.4.1.6876.53.0.350
This informative notification is sent only once from the Active node
when file replication state changes to in-sync or out-of-sync. File
replication state is out-of-sync when VCHA fails to set a watch on a
file at the Active node or fails to replicate a file from the Active
node to Passive. Administrators should check the corresponding KB
article for recovery action.