Peer connections not established if hosts in a cluster have different VirtuCache build number

If VirtuCache driver build numbers on hosts in the same ESXi cluster are different, then VirtuCache doesn’t create peer connections between hosts with mismatched build numbers, and hence any VirtuCache tasks that require such a connection over the replication network, don’t happen. So read directs in case of write-through caching and write replication in case of write-back caching will not happen. Also, vmotions for VMs doing high IO might get aborted.

These problems will also happen if one or more hosts in the cluster have a different VirtuCache build number and other hosts had different build numbers installed before, but VirtuCache is now uninstalled on those hosts.