Synchronization and connectivity errors occur on an ESXi host, and the host becomes disconnected from vCenter Server.
You can find the following messages in journalctl log.MM DD 10:20:46 <vCenter Server> vpxd[#####]: Event [#####:] [1-1] [YYYY-MM-DDT10:20:46.011772Z] [vim.event.TaskEvent] [info] [<USER>] [<Cluster>] [####] [Task: Disconnect host]MM DD 10:20:47 <vCenter Server> vpxd[#####]: Event [#####:] [1-1] [YYYY-MM-DDT10:20:47.024461Z] [vim.event.HostConnectionLostEvent] [error] [] [<Cluster>] [####] [Host <ESXi> in <Cluster> is not responding]MM DD 10:20:47 <vCenter Server> vpxd[#####]: Event [#####:] [1-1] [YYYY-MM-DDT10:20:47.030655Z] [vim.event.HostDisconnectedEvent] [info] [<USER>] [<Cluster>] [####] [Disconnected from <ESXi> in <Cluster>. Reason: User request]MM DD 10:20:47 <vCenter Server> vpxd[#####]: Event [#####:] [1-1] [YYYY-MM-DDT10:20:47.034068Z] [vim.event.EventEx] [info] [] [<Cluster>] [####] [Alarm 'Host connection failure' on <ESXi> triggered by event #### 'Host <ESXi> in <Cluster> is not responding']
VMware vSphere ESXi
ESXi host was intentionally disconnected from vCenter Server by user action.
This behavior is expected when a host is manually disconnected by a user.
Please review the operational records or recent maintenance activities to confirm whether any user intentionally executed a host disconnect task around the reported time.