Thank you very much.
I was able to resolve the score issue. Turns out there were multiple static routes on this first host, including to a gateway address that I had temporarily setup right when I built the new network in the new datacenter for testing purposes.
The symptoms were weird. I was able to dig and resolve public DNS perfectly fine. I was also able to ping public IP addresses perfectly fine. But I was not able to ping or access any content using DNS (i.e. yum couldn't download, for example).
Once I identified the faulty route, fixed it, and re-synchronized the Network settings inside the oVirt UI, the score immediately jumped back up to 3400.
I was also able to (successfully) test my high availability storage this morning, and confirmed that everything still worked when that host was completely rebooted.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, October 15th, 2021 at 12:25 AM, Strahil Nikolov via Users <users@ovirt.org> wrote:
For the score issue you can check https://www.google.com/url?sa=t&source=web&rct=j&url=https://www.ovirt.org/images/Hosted-Engine-4.3-deep-dive.pdf&ved=2ahUKEwiWlZu5yMvzAhX0hf0HHaDACzQQFnoECAQQAQ&usg=AOvVaw2SJWnH5ghQoZq7CV_f-9hs and then identify your problem and fix it.
For the he_local, you can use hosted-engine --set-shared-config mnt_options
backup-volfile-servers=<server2>:<server3>
But most probably you will need to set each host in maintenance and reboot it (there are other ways but that's the simplest) to take effect.
Best Regards,
Strahil Nikolov
On Wed, Oct 13, 2021 at 2:49, David White via Users