This behavior is expected with the current design.
To avoid such VM migrations:
Set DRS to manual mode before restarting vCenter Server or enabling Proactive HA on a cluster.
Set it back to Fully Automated after all hosts receive at least one health update (host no longer has the “unknown health state” config issue).
To clear the message from 'All Issues':
- Disable and re-enable Proactive HA on the cluster.
If using Cisco Intersight Plugin for VMware vSphere Client:
- Temporarily set vSphere DRS to Manual mode. This prevents DRS from migrating VMs off hosts that report an unknown state during the provider reset.
- Toggle the Provider (Cluster Level):
- Navigate to the Cluster > Configure tab.
- Under Services, edit Proactive HA.
- Navigate to the Providers tab.
- Deselect/disable the Cisco Intersight Provider and click OK.
- Edit Proactive HA again, return to the Providers tab, and re-enable the Cisco Intersight Provider.
- Monitor the hosts to verify if the health state updates.
If the above steps are not sufficient, unregister via the Plugin (If Step 2 Fails):
- If toggling the provider does not push the update, the plugin registration must be reset directly.
- In the vSphere Client, go to Menu > Cisco Intersight Plugin.
- Select the Proactive HA Registration tab.
- Click Unregister to remove the stale Proactive HA provider connection.
- Re-register the provider and verify that all alarms are actively mapped.
- Restore Automation: Once the ESXi hosts receive the health update and the "Unknown health state" clears, restore vSphere DRS to Fully Automated.
Reference:
https://intersight.com/help/saas/resources/plugin_vsphere