The “Hosts disconnected from VC” alarm in vSAN Health Test is triggered when one or more hosts in a vSAN cluster are disconnected from the vCenter Server. This can happen for a variety of reasons, including network connectivity issues, vCenter Server or host failures, or maintenance activities.
When this alarm is triggered, the vSAN cluster will not be able to properly function and some of the features may not be available. This can also lead to data availability issues, and in case of a host failure, data loss.
To resolve the issue, you will need to identify the cause of the disconnection and take appropriate action.
Here are some steps you can take:
- Check the vCenter Server and host logs for any error messages or warnings that may indicate the cause of the disconnection.
- Verify that the host is powered on and that the vCenter Server and host can communicate with each other over the network.
- Check for any network or firewall issues that may be preventing communication between the vCenter Server and host.
- If the host has been rebooted or taken offline for maintenance, ensure that it has been properly added back to the vCenter Server and vSAN cluster.
- If the host has failed, check the vSAN health status and consider replacing the host if necessary.
It’s important to address this alarm as soon as possible in order to prevent any data loss or availability issues that can occur as a result of the hosts being disconnected from the vCenter Server.
Why am I receiving this alarm “Alarm alarm.vsan.health.test.network.hostdisconnected”?
The “alarm.vsan.health.test.network.hostdisconnected” alarm in vSAN is triggered when one or more hosts in the vSAN cluster are disconnected from the vCenter Server. This can happen for a variety of reasons, such as:
Network connectivity issues: The host may not be able to communicate with the vCenter Server due to a network or firewall problem.
vCenter Server or host failures: If the vCenter Server or host is down, it will not be able to communicate with the other hosts in the cluster.
Maintenance activities: If the host is taken offline for maintenance or rebooted, it may not be able to reconnect to the vCenter Server and the alarm may be triggered.
Incorrect configuration: If there is an issue with the host’s network configuration, it may not be able to connect to the vCenter Server.
Insufficient resources: If the host is running low on resources, it may not be able to communicate with the vCenter Server and the alarm may be triggered.
It’s important to troubleshoot and resolve the issue as soon as possible, in order to prevent any data loss or availability issues that can occur as a result of the hosts being disconnected from the vCenter Server.
You should check the vCenter Server and host logs for any error messages or warnings that may indicate the cause of the disconnection. Also verify that the host is powered on and that the vCenter Server and host can communicate with each other over the network.
Check for any network or firewall issues that may be preventing communication between the vCenter Server and host. If the host has been rebooted or taken offline for maintenance, ensure that it has been properly added back to the vCenter Server and vSAN cluster.
If the host has failed, check the vSAN health status and consider replacing the host if necessary.