- Login to vSphere Web Client.
- Browse to Home, System Configuration and select Nodes on the top left-hand corner of the UI.
- One of your PSC appliances or vCSA instances does not appear in the node list. You may see this after you have upgraded your vCSA infrastructure from 6.0 to 6.5.
- Or, the instance is listed with the message “The appliance management service on <object> is not running.”
- SSH to the PSC appliance or vCenter Server Appliance in question and login with the root credentials. Make sure SSH has been enabled from the VAMI on Port 5480.
- Execute the command “service-control –list” for the vCSA service list. You will see “applmgmt” is present.
- Execute the command “service-control –stop applmgmt” to stop the service.
- Execute the command “service-control –start applmgmt” to start the service.
- In the vSphere Web Client, browse to Home, System Configuration and check that the issue with the Node has cleared.
- Note: an external PSC has 9 services (all active), a dedicated vCSA has 25 services (normally 19 active, 6 disabled) and a combination PSC/vCSA has 27 services (normally 21 active, 6 disabled). The disabled services vary depending upon which advanced services have been enabled (eg. Auto-Deploy, vCenter HA, etc.).
In vCenter Server for Windows, an administrator will use the Services MMC to manipulate vCenter Server services, however with vCSA, they are administered via CLI. vCSA service manipulation is also documented in VMware KB 2109887.