LoadMaster Profiles are deployed by opening the Configuration Management > LoadMaster Deployment > Create LoadMaster page. Selecting a profile that is in the Ready or Downloaded states, and clicking the Deploy button. You can deploy a LoadMaster either automatically or manually.

Automatic Deployment enables you to provide the parameters required to instantiate a VLM using a specific deployment profile on a specific hypervisor platform (IP address, credentials, and so on). In addition, Kemp 360 Central manages the VLM instantiation directly with the hypervisor platform.

Note: Automatic deployment is currently supported for VMware vCenter, VMware ESXi, and KVM hypervisors only.

Manual Deployment of a LoadMaster profile enables you to download a pre-configured VLM image (or pair of LoadMaster VLMs configured into HA) that you can then manually install on a wider range of hypervisor platforms. VLM images can be manually deployed to:

  • VMware (vCenter or ESXi)
  • Hyper-V (Gen1 image only)
  • VirtualBox
  • KVM
  • Xen

As with automated deployment, the manual deployment process can be entered at the end of the deployment profile creation process; it can also be entered by going to the LoadMaster Virtual Machines screen, selecting a Ready or Downloaded profile from the list, and clicking Deploy.

General Deployment Notes

An SSL certificate validation error may be observed in the Kemp 360 Central log during either a manual or automatic deployment, and a similar error may be observed in the hypervisor log. This may be caused by a difference between the date and time settings on Kemp 360 Central and on the target hypervisor environment. The deployment will still succeed, but the result is that Kemp 360 Central will not be able to communicate with the LoadMaster using certificate authentication until the time on the hypervisor is later than the time that the LoadMaster image was created on Kemp 360 Central. If this happens, you can temporarily go back to Basic Authentication by editing the device definition on Kemp 360 Central. In general, ensure that all hypervisor environments being used for automatic and manual LoadMaster deployments have their date and time set properly (ideally using NTP) to avoid SSL certificate validation errors when deploying a profile.