Setting up HDvM 7.0.0.01 or greater to work with VMware.

1. Download the vMA The vMA can be either downloaded or deployed remotely via OVF from vCenter. Visit http://www.vmware.com/support/developer/vima/ for instructions.

2. Power the vMA and run through the standard setup wizard which requires: IP address Subtnet Mask Default Gateway DNS servers New password for the admin account (vi-admin)

3. At the welcome screen press ALT+F2:

4. When presented with the login screen, login with the user vi-admin and the newly set password:

5. Use the vifp command to add the vCenter Server, then check it was added successfully:

6. Ensure that the open source web services service is stopped

(IF YOU GET A FAIL HERE, see troubleshooting below before moving to step 7)

7. Use VMwares SMI-S script to finish the installation. Populate the vSphere hostname with the FQDN or IP address of vCenter and answer yes to starting both cimserver and OpenwsMan as below:

8. Check all required services are running by checking the output of the following command: ps -ef | egrep -i cim|open

9. Login to HCS

10.Click on Administration -> Host -> Add Host. When the dialog box appears select List of IP addresses and populate the IP address allocated to the vMA in step 2. Select the OS type as VMware and the username as vi-admin and the password as configured in step 2. Then hit ok.

11.Go to the Data collection task and wait a few seconds. If something is wrong, Failed will under the status. If everything is ok, the status will be in progress. This can take a while depending on the number of ESX hosts that vCenter manages

12.Wait until the task completes

13.Check the hosts have been added under Resources-> Hosts

Troubleshooting

You only need to read this, if the wsmanservice failed to stop in step 6.

On occasion, things go wrong. I suspect this is because the wsmanwas services forcibly stopped before the OVF was released in some version (the vMA 4.1 doesnt appear to have this problem). This causes the process to die, but leaves behind the persistent copy of the process identifier (a PID file). If you come across this, you wont be able to stop or start the wsman service, all attempts result in a FAIL. This is because the script which starts this service looks checks for the watchdog process by looking for the PID file.

You can identify this is the case by checking the status of the service. Run the command: sudo /etc/init.d/wsman status (sorry no screen for the output). If the service reports as stopped and the watchdog is running:

If it is, we need to remove the PID files for both cimserver and openwsmand watchdogs.

At this point you should go to step 7.