VMWARE-VCHA-MIB
43 objects
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 + | | + | Public IP | | | | | | | Active vCenter | | Passive vCenter | | | | | + ^ < | DB & File replication | + + + + + + + + | | | 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.
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 |
| OID | Name | Access | Status | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.6876.53.0 | NodevmwVCHANotifications | |||
| 1.3.6.1.4.1.6876.53.0.100 | NotificationvmwVchaNodeJoined | current | This informative notification is sent from the Active node when it notices a peer node rejoin the cluster. It is sent only once. | |
| 1.3.6.1.4.1.6876.53.0.105 | NotificationvmwVchaNodeLeft | current | 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 live… | |
| 1.3.6.1.4.1.6876.53.0.110 | NotificationvmwVchaNodeIsolated | current | 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 nod… | |
| 1.3.6.1.4.1.6876.53.0.130 | NotificationvmwVchaClusterStateChanged | current | This notification is sent only once from the Active node when vCenter HA cluster state changes to either healthy, degraded or isolated. Please see VmwVchaClust… | |
| 1.3.6.1.4.1.6876.53.0.150 | NotificationvmwVchaClusterModeChanged | current | This notification is sent only once from the Active node when vCenter HA cluster mode changes to either enabled, maintenance or disabled. | |
| 1.3.6.1.4.1.6876.53.0.205 | NotificationvmwVchaPublicIpUp | current | 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 th… | |
| 1.3.6.1.4.1.6876.53.0.206 | NotificationvmwVchaPublicIpDown | current | 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 … | |
| 1.3.6.1.4.1.6876.53.0.210 | NotificationvmwVchaFailoverTriggered | current | 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 rol… | |
| 1.3.6.1.4.1.6876.53.0.220 | NotificationvmwVchaFailoverSucceeded | current | This informative notification is sent only once when the Passive node takes over the Active role and brings up the public network interface. | |
| 1.3.6.1.4.1.6876.53.0.225 | NotificationvmwVchaFailoverFailedDisabledMode | current | This warning notification is sent only once when the Active node fails to initiate a failover because the cluster is in disabled mode. | |
| 1.3.6.1.4.1.6876.53.0.226 | NotificationvmwVchaFailoverFailedNodeLost | current | 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. | |
| 1.3.6.1.4.1.6876.53.0.227 | NotificationvmwVchaFailoverFailedPassiveNotReady | current | 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 tak… | |
| 1.3.6.1.4.1.6876.53.0.230 | NotificationvmwVchaContinueAsActive | current | 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 scena… | |
| 1.3.6.1.4.1.6876.53.0.300 | NotificationvmwVchaDbReplicationStateChanged | current | This informative notification is sent only once from the Active node when database replication state changes to sync, async or no replication. Database replica… | |
| 1.3.6.1.4.1.6876.53.0.350 | NotificationvmwVchaFileReplicationStateChanged | current | 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 o… | |
| 1.3.6.1.4.1.6876.53.1 | IdentityvmwVchaMIB | 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 A… | ||
| 1.3.6.1.4.1.6876.53.1.2 | NodevmwVchaMIBConformance | |||
| 1.3.6.1.4.1.6876.53.1.2.1 | NodevmwVchaMIBCompliances | |||
| 1.3.6.1.4.1.6876.53.1.2.1.3 | CompliancevmwVchaMIBBasicComplianceRev2 | current | The compliance statement for entities which implement VMWARE-VCHA-MIB. | |
| 1.3.6.1.4.1.6876.53.1.2.2 | NodevmwVchaMIBGroups | |||
| 1.3.6.1.4.1.6876.53.1.2.2.1 | GroupvmwVchaNotificationInfoGroup | current | These objects provide notification details. | |
| 1.3.6.1.4.1.6876.53.1.2.2.2 | GroupvmwVchaNotificationGroup | current | Group of objects describing notifications (traps). | |
| 1.3.6.1.4.1.6876.53.5 | ScalarvmwVchaInstanceUuid | accessible-for-notify | current | A string that uniquely identify the vCenter HA cluster. This is the same as instance UUID of the active vCenter Server. |
| 1.3.6.1.4.1.6876.53.11 | ScalarvmwVchaPrivateAddressType | accessible-for-notify | current | The type of cluster network interface: ipv4 or ipv6. |
| 1.3.6.1.4.1.6876.53.12 | ScalarvmwVchaPublicAddressType | accessible-for-notify | current | The type of public network interface: ipv4 or ipv6. |
| 1.3.6.1.4.1.6876.53.15 | ScalarvmwVchaPrivateAddressAddr | accessible-for-notify | current | 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 an… |
| 1.3.6.1.4.1.6876.53.16 | ScalarvmwVchaPublicAddressAddr | accessible-for-notify | current | The IP address of a node in public network that serves client's request. |
| 1.3.6.1.4.1.6876.53.20 | ScalarvmwVchaTargetNodeRole | accessible-for-notify | current | Represents the role of node being affected by the given event. See MIB module general description for detailed expalanation for each role. |
| 1.3.6.1.4.1.6876.53.25 | ScalarvmwVchaClusterState | accessible-for-notify | current | vCenter HA cluster states: healthy, degraded or isolated. |
| 1.3.6.1.4.1.6876.53.30 | ScalarvmwVchaClusterMode | accessible-for-notify | current | vCenter HA cluster modes: enabled, maintenance or disabled. |
| 1.3.6.1.4.1.6876.53.40 | ScalarvmwVchaIsPlannedFailover | accessible-for-notify | current | 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,… |
| 1.3.6.1.4.1.6876.53.50 | ScalarvmwVchaDbReplicationState | accessible-for-notify | current | Database replication states: sync, async or no replication. |
| 1.3.6.1.4.1.6876.53.55 | ScalarvmwVchaIsFileProviderInSync | accessible-for-notify | current | 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 a… |
| 1.3.6.1.4.1.6876.53.60 | ScalarvmwVchaFileReplicationProvider | accessible-for-notify | current | File replication providers: service-config or service-state. |
| 1.3.6.1.4.1.6876.53.250 | NodevmwVchaActive | |||
| 1.3.6.1.4.1.6876.53.255 | NodevmwVchaPassive | |||
| 1.3.6.1.4.1.6876.53.260 | NodevmwVchaWitness |
Type Definitions
| Name | Syntax | Status | Description |
|---|---|---|---|
| VmwVchaClusterModeType | INTEGER { enabled(1), disabled(2), maintenance(3) } | current | 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… |
| VmwVchaClusterStateType | INTEGER { healthy(1), degraded(2), isolated(3) } | current | 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… |
| VmwVchaDbReplicationStateType | INTEGER { noReplication(1), sync(3), async(4) } | current | 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. syn… |
| VmwVchaFileReplicationProviderType | INTEGER { serviceConfig(1), serviceState(2) } | current | 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 se… |
| VmwVchaNodeRoleType | INTEGER { active(1), passive(2), witness(3), unknown(4) } | current | 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 no… |