Answer: This alert may not have anything to do with High Availability. Foxhound uses any runtime change in the server name to trigger this alert, and that can happen if you manually stop and restart the target database with a different server name.

If you are not using HA, you can disable Alert #11 to avoid this message.