I have a new cluster that I am implementing vFRC on. The cluster runs great and the vFRC looks to be working without issue. Unfortunately when my VCenter is restarted the hosts in the cluster all still show that they have vFRC installed, but show 0mb available. The only way to clear this is to place the host in maintenance mode.
This of course is challenging since it happens to all host on the cluster at the same time. Requiring me to either shutdown all the VM's on a host or disable vFRC on the vm's from a host to get it to maintenance mode.
Does any one know if this is expected behavior?
or if there is kb/known issue that I am not finding?
or a good direction to go to diagnose why this is happening?
I am running
vCenter 6 3018524 on windows 2012R2 fully patched
ESXi 6 u1 3380124
Dell Servers R730
vFRC on intel P3600 (NVMe interface)
How is your vCenter licensed? EntPlus?
What type of shared storage do you have? Is it a SAN with a Flash option?
I have been looking for KB's and found this one. Did you see this one yet? http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=213686...
Otherwise, I found the list of best practices in the vFRC 5.5 guide, which still applies to v6, and I would verify that these are met before proceeding.
https://www.vmware.com/files/pdf/techpaper/vfrc-perf-vsphere55.pdf
How is your vCenter licensed? EntPlus?
What type of shared storage do you have? Is it a SAN with a Flash option?
I have been looking for KB's and found this one. Did you see this one yet? http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=213686...
Otherwise, I found the list of best practices in the vFRC 5.5 guide, which still applies to v6, and I would verify that these are met before proceeding.
https://www.vmware.com/files/pdf/techpaper/vfrc-perf-vsphere55.pdf
I was not able to find the first KB in my searches. Thank you for pointing me to it, I believe this is a direct match for my issue. I will test the work around in the morning to verify that it resolves the issue.