4.5 ClusterStatus

Use this Knowledge Script to monitor the configuration status of the cluster. This script raises an event if the state of the cluster changes to one of the following states:

  • Inconsistent - The number of virtual machines powered on exceeds the requirements of strict failover. The current failover capacity is smaller than the configured failover capacity, and can no longer guarantee failover for the specified number of hosts, but it continues performing failover. If a host fails, VMware first fails over the virtual machines of one host in order of priority, and then fails over the virtual machines of the second host in order of priority, and so on.

  • Overcommitted - When capacity is removed from the cluster, such as when a host fails or is removed, and there are no longer enough resources to support all requirements.

  • Undercommitted - Available resources can meet all reservations and support all running virtual machines. In addition, at least one host has enough resources to run.

This script generates data streams for undercommitted state, overcommitted state, and inconsistent state.

4.5.1 Resource Object

vSphere cluster

4.5.2 Default Schedule

By default, this script runs every 15 minutes.

4.5.3 Setting Parameter Values

Set the following parameters as needed:

Parameter

How to Set It

Event Notification

Raise event when cluster state changes?

Select Yes to raise an event if the state of the cluster changes. The default is Yes.

Event severity when cluster state is inconsistent

Set the event severity level, from 1 to 40, to indicate the importance of an event in which the cluster state changes to inconsistent. The default is 5.

Event severity when cluster state is overcommitted

Set the event severity level, from 1 to 40, to indicate the importance of an event in which the cluster state changes to overcommitted. The default is 15.

Event severity when cluster state is undercommitted

Set the event severity level, from 1 to 40, to indicate the importance of an event in which the cluster state changes to undercommitted. The default is 25.

Raise event when status information is not available?

Select Yes to raise an event if the status information is not available. The default is unselected.

Event severity when status information is not available.

Set the event severity level, from 1 to 40, to indicate the importance of an event in which status information is not available. The default is 15.

Event severity when AppManager failed to get metrics

Set the event severity level, from 1 to 40, to indicate the importance of an event in which AppManager failed to retrieve metrics from vCenter. The default is 15.

Event severity when AppManager failed to log in

Set the event severity level, from 1 to 40, to indicate the importance of an event in which AppManager failed to log in to vCenter. The default is 5.

Event severity when ClusterStatus job fails unexpectedly

Set the event severity level, from 1 to 40, to indicate the importance of an event in which the ClusterStatus job fails unexpectedly. The default is 5.

Data Collection

Collect data for status change?

Select Yes to collect data about cluster status for charts and reports. The default is unselected.

NOTE:If enabled, data collection returns the following data: 100 for undercommitted state, 50 for overcommitted state, and 0 for inconsistent state.