Enable Host Monitoring feature for vSphere HA enabled cluster may set to disabled during FDM reconfigure
search cancel

Enable Host Monitoring feature for vSphere HA enabled cluster may set to disabled during FDM reconfigure

book

Article ID: 421534

calendar_today

Updated On:

Products

VMware vCenter Server VMware vCenter Server 8.0 VMware vSphere ESXi 8.0

Issue/Introduction

  • Enable Host Monitoring under cluster may be set to disabled post upgrade/update of vCenter Server Appliance (VCSA) during vSphere HA (FDM) reconfigure

  • Executing journalctl -b 0 on VCSA reports repeated attempts to enable host monitoring

YYYY-MM-DDTHH:MM:SS info vpxd[PID] [Originator@6876 sub=ResMgr opID=dasConfig.cpp:<>] Changing host monitoring state for cluster [vim.ClusterComputeResource:domain-<cluster ID>,<Cluster Name>]: (disabled) -> (enabled)
YYYY-MM-DDTHH:MM:SS info vpxd[PID] [Originator@6876 sub=ResMgr opID=dasConfig.cpp:<>] Changing host monitoring state for cluster [vim.ClusterComputeResource:domain-<cluster ID>,<Cluster Name>]: (enabled) -> (disabled)
YYYY-MM-DDTHH:MM:SS info vpxd[PID] [Originator@6876 sub=ResMgr opID=dasConfig.cpp:<>] Changing host monitoring state for cluster [vim.ClusterComputeResource:domain-<cluster ID>,<Cluster Name>]: (disabled) -> (enabled)
YYYY-MM-DDTHH:MM:SS info vpxd[PID] [Originator@6876 sub=ResMgr opID=dasConfig.cpp:<>] Changing host monitoring state for cluster [vim.ClusterComputeResource:domain-<cluster ID>,<Cluster Name>]: (enabled) -> (disabled)

  • /var/log/vmware/vpxd/vpxd.log: (on VCSA)

YYYY-MM-DDTHH:MM:SS info vpxd[PID] [Originator@6876 sub=DAS opID=dasConfig.cpp:<>] Getting image spec for solution com.vmware.vsphere-ha in cluster domain-<cluster ID>
YYYY-MM-DDTHH:MM:SS info vpxd[PID] [Originator@6876 sub=DAS opID=dasConfig.cpp:<>] Updating image spec to version <vCenter Server Version-Build number> for solution com.vmware.vsphere-ha in cluster domain-<cluster ID>
YYYY-MM-DDTHH:MM:SS info vpxd[PID] [Originator@6876 sub=ResMgr opID=dasConfig.cpp:<>] Updating cluster state for [vim.ClusterComputeResource:domain-<cluster ID>,<Cluster Name>]: 1 -> 0
YYYY-MM-DDTHH:MM:SS info vpxd[PID] [Originator@6876 sub=ResMgr opID=dasConfig.cpp:<>] Changing host monitoring state for cluster [vim.ClusterComputeResource:domain-<cluster ID>,<Cluster Name>]: (disabled) -> (enabled)
YYYY-MM-DDTHH:MM:SS info vpxd[PID] [Originator@6876 sub=ResMgr opID=dasConfig.cpp:<>] Updating cluster state for [vim.ClusterComputeResource:domain-<cluster ID>,<Cluster Name>]: 0 -> 1
YYYY-MM-DDTHH:MM:SS info vpxd[PID] [Originator@6876 sub=ResMgr opID=dasConfig.cpp:<>] Changing host monitoring state for cluster [vim.ClusterComputeResource:domain-<cluster ID>,<Cluster Name>]: (enabled) -> (disabled)

YYYY-MM-DDTHH:MM:SS error vpxd[06734] [Originator@6876 sub=Default opID=dasConfig.cpp:<>] [VpxLRO] -- ERROR task-<Task ID> --  -- <ESXi host name> -- DasConfig.ConfigureHost: :vim.fault.Timedout

Cause

This issue can be seen if any/all host(s) in the cluster is reported as "UNKNOWN_FDM_HSTATE" during the vSphere HA reconfigure

/var/log/vmware/vpxd/vpxd.log: (on VCSA)

YYYY-MM-DDTHH:MM:SS info vpxd[PID] [Originator@6876 sub=MoHost opID=dasConfig.cpp:<>] VC state for host host-<Host ID> (retry -> uninitialized), FDM state (UNKNOWN_FDM_HSTATE -> UNKNOWN_FDM_HSTATE), src of state (null -> null)
YYYY-MM-DDTHH:MM:SS info vpxd[PID] [Originator@6876 sub=MoHost opID=dasConfig.cpp:<>] VC state for host host-<Host ID> (retry -> uninitialized), FDM state (UNKNOWN_FDM_HSTATE -> UNKNOWN_FDM_HSTATE), src of state (null -> null)
YYYY-MM-DDTHH:MM:SS info vpxd[PID] [Originator@6876 sub=MoHost opID=dasConfig.cpp:<>] VC state for host host-<Host ID> (uninitialized -> retry), FDM state (UNKNOWN_FDM_HSTATE -> UNKNOWN_FDM_HSTATE), src of state (null -> null)

Resolution

The parameter for "Enable Host Monitoring" will eventually result as enabled post the retry timeout is complete and host is marked as vim.fault.Timedout

Powered by Wolken Software