A cluster shows as Noncompliant on the Cluster Compliance tab

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• After attaching a host profile to a cluster, the reference host shows as Noncompliant on the Cluster Compliance tab.
• You see the following error if you initiate a Cluster Compliance check when you are using host profiles:

FT logging is not enabled

Environment

VMware vCenter Server 4.1.x
VMware vCenter Server 5.1.x
VMware vCenter Server 5.0.x
VMware vCenter Server 4.0.x

Resolution

Cluster Compliance is checked against a pre-defined set of requirements. These requirements vary depending on whether you have VMware High Availability (HA), VMware Distributed Resource Scheduler (DRS), or both enabled on your cluster. For example, you see the error FT logging is not enabled if Fault Tolerance (FT) is enabled, but FT logging is not.

You can view the set of requirements by clicking Description in the Profile Compliance tab in vCenter Server.

If both HA and DRS are enabled, ensure that:

• FT logging NIC speed is at least 1000 Mbps.
• At least one shared datastore exists.
• FT logging is enabled.
• VMotion NIC speed is at least 1000 Mbps.
• All the hosts in the cluster have the same build for Fault Tolerance.
• The host hardware supports Fault Tolerance.
• VMotion is enabled.

If only DRS is enabled, ensure that:

• VMotion NIC speed is at least 1000 Mbps.
• VMotion is enabled.
• At least one shared datastore exists.

If only HA is enabled, ensure that:

• FT logging NIC speed is at least 1000 Mbps.
• At least one shared datastore exists.
• FT logging is enabled.
• VMotion NIC speed is at least 1000 Mbps.
• All the hosts in the cluster have the same build for Fault Tolerance.
• The host hardware supports Fault Tolerance.
• VMotion is enabled.

The host profile that you attach for the cluster is only used for checking Host Profile Compliance and has no bearing on Cluster Requirement Compliance. If your ESX host is showing as Noncompliant for Cluster Requirement Compliance, ensure that it meets the above requirements.

Note: Host Profile may also show non-compliant for other components and can be deselected.

For more information on Fault Tolerance and Fault Tolerance logging, see the vSphere Availability Guide.

Additional Information

If the Fault Tolerance feature is not being used and you are encountering this error, it is possible to disable the Fault Tolerance compliance check on the cluster. For further details, see Disabling Fault Tolerance compliance checks on a cluster (1017714).

Note: if in the future you plan on using Fault Tolerance you should re-enable the Fault Tolerance compliance checks.
Enabling vMotion and Fault tolerance logging