VMWARE-VCHA-MIB

File: VMWARE-VCHA-MIB.mib (24685 bytes)

Imported modules

SNMPv2-SMI SNMPv2-CONF INET-ADDRESS-MIB
VMWARE-ROOT-MIB SNMPv2-TC

Imported symbols

MODULE-IDENTITY OBJECT-TYPE NOTIFICATION-TYPE
MODULE-COMPLIANCE OBJECT-GROUP NOTIFICATION-GROUP
InetAddress InetAddressType vmwVCHA
TEXTUAL-CONVENTION TruthValue

Defined Types

VmwVchaNodeRoleType  
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.
TEXTUAL-CONVENTION    
  INTEGER active(1), passive(2), witness(3), unknown(4)  

VmwVchaClusterModeType  
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.
TEXTUAL-CONVENTION    
  INTEGER enabled(1), disabled(2), maintenance(3)  

VmwVchaClusterStateType  
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.
TEXTUAL-CONVENTION    
  INTEGER healthy(1), degraded(2), isolated(3)  

VmwVchaDbReplicationStateType  
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.
TEXTUAL-CONVENTION    
  INTEGER noReplication(1), sync(3), async(4)  

VmwVchaFileReplicationProviderType  
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.
TEXTUAL-CONVENTION    
  INTEGER serviceConfig(1), serviceState(2)  

Defined Values

vmwVchaMIB 1.3.6.1.4.1.6876.53.1
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.
MODULE-IDENTITY    

vmwVCHANotifications 1.3.6.1.4.1.6876.53.0
OBJECT IDENTIFIER    

vmwVchaActive 1.3.6.1.4.1.6876.53.250
OBJECT IDENTIFIER    

vmwVchaPassive 1.3.6.1.4.1.6876.53.255
OBJECT IDENTIFIER    

vmwVchaWitness 1.3.6.1.4.1.6876.53.260
OBJECT IDENTIFIER    

vmwVchaNodeJoined 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

vmwVchaNodeLeft 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

vmwVchaNodeIsolated 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

vmwVchaClusterStateChanged 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

vmwVchaClusterModeChanged 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

vmwVchaPublicIpUp 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

vmwVchaPublicIpDown 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

vmwVchaFailoverTriggered 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

vmwVchaFailoverSucceeded 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

vmwVchaFailoverFailedDisabledMode 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

vmwVchaFailoverFailedNodeLost 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

vmwVchaFailoverFailedPassiveNotReady 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

vmwVchaContinueAsActive 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

vmwVchaDbReplicationStateChanged 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

vmwVchaFileReplicationStateChanged 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

vmwVchaInstanceUuid 1.3.6.1.4.1.6876.53.5
A string that uniquely identify the vCenter HA cluster. This is the same as instance UUID of the active vCenter Server.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  OCTET STRING  

vmwVchaPrivateAddressType 1.3.6.1.4.1.6876.53.11
The type of cluster network interface: ipv4 or ipv6.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  InetAddressType  

vmwVchaPublicAddressType 1.3.6.1.4.1.6876.53.12
The type of public network interface: ipv4 or ipv6.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  InetAddressType  

vmwVchaPrivateAddressAddr 1.3.6.1.4.1.6876.53.15
This is the IP address of each node in cluster network that is used to communicate with other nodes in the cluster and transfer data between the Active node and the Passive node.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  InetAddress  

vmwVchaPublicAddressAddr 1.3.6.1.4.1.6876.53.16
The IP address of a node in public network that serves client's request.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  InetAddress  

vmwVchaTargetNodeRole 1.3.6.1.4.1.6876.53.20
Represents the role of node being affected by the given event. See MIB module general description for detailed expalanation for each role.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  VmwVchaNodeRoleType  

vmwVchaClusterState 1.3.6.1.4.1.6876.53.25
vCenter HA cluster states: healthy, degraded or isolated.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  VmwVchaClusterStateType  

vmwVchaClusterMode 1.3.6.1.4.1.6876.53.30
vCenter HA cluster modes: enabled, maintenance or disabled.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  VmwVchaClusterModeType  

vmwVchaIsPlannedFailover 1.3.6.1.4.1.6876.53.40
For planned failover, the Active node flushes all the state to the Passive node, waits for the flush to complete before causing a failover. After the failover, the Passive node starts without any data loss. For unplanned failover, the failover is initiated immediately and may result in data loss.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  TruthValue  

vmwVchaDbReplicationState 1.3.6.1.4.1.6876.53.50
Database replication states: sync, async or no replication.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  VmwVchaDbReplicationStateType  

vmwVchaIsFileProviderInSync 1.3.6.1.4.1.6876.53.55
This variable represents the file replication provider state. When it is false, the service configuration and state files are out of sync between the Passive and Active nodes. This could result from file replication failures.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  TruthValue  

vmwVchaFileReplicationProvider 1.3.6.1.4.1.6876.53.60
File replication providers: service-config or service-state.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  VmwVchaFileReplicationProviderType  

vmwVchaMIBConformance 1.3.6.1.4.1.6876.53.1.2
OBJECT IDENTIFIER    

vmwVchaMIBCompliances 1.3.6.1.4.1.6876.53.1.2.1
OBJECT IDENTIFIER    

vmwVchaMIBGroups 1.3.6.1.4.1.6876.53.1.2.2
OBJECT IDENTIFIER    

vmwVchaMIBBasicComplianceRev2 1.3.6.1.4.1.6876.53.1.2.1.3
The compliance statement for entities which implement VMWARE-VCHA-MIB.
Status: current Access: accessible-for-notify
MODULE-COMPLIANCE    

vmwVchaNotificationInfoGroup 1.3.6.1.4.1.6876.53.1.2.2.1
These objects provide notification details.
Status: current Access: accessible-for-notify
OBJECT-GROUP    

vmwVchaNotificationGroup 1.3.6.1.4.1.6876.53.1.2.2.2
Group of objects describing notifications (traps).
Status: current Access: accessible-for-notify
NOTIFICATION-GROUP