OPERATIONAL DEFECT DATABASE
...
...
Cannot connect directly to the ESXi host or manage under vCenter server.vCenter Server displays the error: Virtual machine creation may fail because agent is unable to retrieve VM creation options from the host.
For troubleshooting ESXi connectivity issue, restart the management agents on your ESXi host. Warning: If LACP is configured on the vSAN network, do not restart management agents on ESXi hosts running vSAN. Restarting the management agents may impact any tasks that are running on the ESXi host at the time of the restart.Check for any storage issues before restarting the Host deamon hostd service or services.sh
Restart Management agents in ESXi Using Direct Console User Interface (DCUI): Connect to the console of your ESXi host.Press F2 to customize the system.Log in as root.Use the Up/Down arrows to navigate to Troubleshooting Options > Restart Management Agents.Press Enter.Press F11 to restart the services.When the service restarts, press Enter.Press Esc to log out. Note: You can also restart services using the Host Client. In Host Client, select Host >> Manage >> Services and select the service to restart. Restart Management agents in ESXi Using ESXi Shell or Secure Shell (SSH): Log in to ESXi Shell or SSH as root. For Enabling ESXi Shell or SSH, see Using ESXi Shell in ESXi 5.x and 6.x (2004746). Restart the ESXi host daemon and vCenter Agent services using these commands: /etc/init.d/hostd restart /etc/init.d/vpxa restart Alternatively: To reset the management network on a specific VMkernel interface, by default vmk0, run the command: esxcli network ip interface set -e false -i vmk0; esxcli network ip interface set -e true -i vmk0 Note: Using a semicolon (;) between the two commands ensures the VMkernel interface is disabled and then re-enabled in succession. If the management interface is not running on vmk0, change the above command according to the VMkernel interface used. To restart all management agents on the host, run the command: services.sh restart Caution: If LACP is enabled and configured, do not restart management services using services.sh command. Instead restart independent services using the /etc/init.d/module restart command.If the issue is not resolved, and you are restarting all the services that are a part of the services.sh script, take a downtime before proceeding to the script.If NSX is configured in the environment, do not run the /sbin/services.sh restart command because this will restart all services on the ESXi host. If you need to restart the management agents on the ESXi host, restart vpxa, host.d, and fdm individually. If you also need to run the /sbin/services.sh restart command because restarting each management agent does not work, then migrate all the VMs off the ESXi host and put the host in maintenance mode if possible.If you are unsure that NSX for vSphere is installed on an ESXi host, run this command to verify: esxcli software vib list --rebooting-image | grep esx-* Look for the following VIBs to determine if NSX is installed on the ESX host: vsip-esx esx-vxlan If using shared graphics in a View environment (VGPU, vDGA, vSGA), do not use services.sh. This will shut down the xorg service which is responsible for graphics at the guest OS level. By ripping the graphics out of the guest OS you will in term cause the crash of your VDI workload using the shared graphics. Ensure you are using shared graphics to only restart hostd, and vpxa if you are not in maintenance mode.
For translated versions of this article, see: Español: Reiniciando los agentes de administración en un Servidor ESX o ESXi (1029041)Português: Como reiniciar os agentes de gerenciamento em um host ESXi ou ESX (2045125)日本語: ESX および ESXi のマネジメント エージェントの再起動について (1037058)Deutsch: Neustarten der Management Dienste auf einem ESX oder ESXi Server (2000987)简体中文: 在 ESXi 或 ESX 主机上重新启动管理代理 (2048205) VMware Skyline Health Diagnostics for vSphere - FAQDetermining whether virtual machines are configured to autostartTroubleshooting vmware-hostd service if it fails or stops responding on an ESX/ESXi hostRestarting hostd (mgmt-vmware) on ESX hosts restarts hosted virtual machines where virtual machine Startup/Shutdown is enabledService mgmt-vmware restart may not restart hostd in ESX/ESXiTroubleshooting the vCenter Server Agent when it does not start“vm-support” command in ESX/ESXi to collect diagnostic informationCollecting information about tasks in VMware ESXi/ESXReiniciar los agentes de administración en ESXiESXi の管理エージェントの再起動Neustarten der Management Dienste auf einem ESX oder ESXi ServerUsing ESXi Shell in ESXi 5.x and 6.xPerforming a Reconfigure for VMware HA operation on a master node causes an unexpected virtual machine failoverReiniciando os agentes de gerenciamento em um ESXi在 ESXi 中重新启动管理代理NULL 値の serial0.fileName をマッピングを試みているときに ESXi hostd サービスが応答しなくなるVMware vCenter Server 上でホストまたは仮想マシンにアラートアイコンがついているにもかかわらず、該当するアラームが発報されていないiLO ファームウェアをアップデートすると HP Proliant Gen8 サーバから誤ったアラームが通知されるNFS データストアのアンマウントが次のエラーで失敗する： Sysinfo set operation VSI_MODULE_NODE_mnt_umount failed with error status BusyNeustart der Management-Agents auf einem ESXi- oder ESX-HostCollecting diagnostic information for VMware ESX/ESXiPowering off an unresponsive virtual machine on an ESXi host
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
