Not all Fault Tolerance Properties in vCenter Server MOB VirtualMachineQuickStats Report Information

Products

• VMware vCenter Server

Issue/Introduction

Fault Tolerance is configured correctly on ESXi Hosts and Virtual Machines.

ftSecondaryLatency is showing a value of "0"

ftLatencyStatus is showing a value of "gray"

Virtual machines with Fault Tolerance enabled are functioning as expected

Environment

VMware vCenter Server

Cause

This is the expected behavior.This latency is not visible to the customer because the secondary virtual machine is a live-standby  and will not respond to an external ping.

Resolution

The product is functioning as designed.

If you would like to know the Fault Tolerance network latency, there are two options for analysis:

1) Use vmkping in the esxcli. See KB 344313: Testing VMkernel network connectivity with the vmkping command for more information.

2) Check vmkernel logs. Fault Tolerance will measure and print the RTT when Fault Tolerance connection btween primary and secondary is created. An example of these events will appear as follows:

vmkernel: cpu30:1001390962)FTCpt: RTTHandshake:1728: (1394946416917888328 pri) socket 0x43254858ac10 rtt = 300 US

vmkernel: cpu52:1001556633)FTCpt: RTTHandshake:1728: (433290718433 snd) socket 0x432547702390 rtt = 300 US