VCP550 · Question #80
An ESXi 5.x host is unable to connect to a vCenter 5.x server. Which commands should an administrator use to restart the management agents on the host?
The correct answer is A. SSH to the host and execute the commands - /etc/init.d/hostd restart and /etc/init.d/vpxa restart. On ESXi 5.x, the two management agent services are hostd (Host Agent) and vpxa (vCenter Agent), both restarted via /etc/init.d/ to restore vCenter connectivity.
Question
An ESXi 5.x host is unable to connect to a vCenter 5.x server. Which commands should an administrator use to restart the management agents on the host?
Options
- ASSH to the host and execute the commands - /etc/init.d/hostd restart and /etc/init.d/vpxa restart
- BSSH to the host and execute the commands - /etc/init.d/vpxd restart and /etc/init.d/vpxa restart
- CSSH to the host and execute the commands - /etc/init.d/vmware-hostd restart and
- DSSH to the host and execute the commands - /etc/init.d/vmware-hostd restart and /etc/init.d/vpxd restart
How the community answered
(37 responses)- A86% (32)
- B3% (1)
- C3% (1)
- D8% (3)
Why each option
On ESXi 5.x, the two management agent services are hostd (Host Agent) and vpxa (vCenter Agent), both restarted via /etc/init.d/ to restore vCenter connectivity.
The hostd daemon is the ESXi Host Agent responsible for managing local host operations and exposing the API consumed by vCenter, while vpxa is the vCenter Agent that runs on the ESXi host and maintains the communication channel to vCenter Server. Restarting both services via /etc/init.d/hostd restart and /etc/init.d/vpxa restart refreshes the management plane without requiring a full host reboot.
vpxd is the vCenter Server daemon that runs on the vCenter Server itself, not on ESXi hosts; this command does not exist on an ESXi host and would not resolve host-side connectivity issues.
vmware-hostd is not the correct init.d service script name used in ESXi 5.x; the proper service name is simply hostd, making this command fail.
vpxd runs on the vCenter Server appliance or Windows host, not on ESXi nodes, so issuing this command from an ESXi SSH session is invalid and would not fix the agent connectivity problem.
Concept tested: Restarting ESXi management agents via SSH
Source: https://docs.vmware.com/en/VMware-vSphere/5.5/com.vmware.vsphere.troubleshooting.doc/GUID-BD659F1D-0A5A-4075-9CC5-E2DBAB9DD7C6.html
Topics
Community Discussion
No community discussion yet for this question.