Multiple ESXi servers, IPs and templates

ESXi records and settings profiles

Define your VMware ESXi servers under Products → Hosting & Servers → Server Settings. In each record, check that the API address, user, connection details, datastore and network selection match the target ESXi.

On the management page, edit the provisioning method, template access and network values under Settings Profiles. Restrict the connection details to authorised administrators; you can also restrict ESXi API access to the address of the WISECP server.

IPv4 pools

Check the IP ranges, gateway, netmask and DNS values together. Exclude the network, broadcast and gateway addresses, and any addresses used elsewhere, from allocation.

Several ESXi servers can use the same pool, provided the servers are compatible with the same network routing. Do not add the same address to separate pools that know nothing of each other. In the pool view, review the free, assigned, externally used and excluded addresses. Addresses of services that have been cancelled but whose virtual machine has not been deleted count as assigned.

Operating system templates

On the management page, the Templates screen shows each operating system together with its ready / source status on every ESXi. Powered-off VMs with the default tpl- prefix, or VMs registered as templates, are detected. An OVA library and shared templates from another ESXi are supported.

The template’s VMware Tools status, firmware, disk controller, network card and first-boot method must be correct. Linux can use cloud-init; Windows can use cloudbase-init or the supported VMware Tools method. The plan disk must not be smaller than the template disk.

Capacity and product mapping

Review the CPU, RAM, datastore and capacity warnings on the Overview tab. In the VPS / VDS product, select the target server, profile, vCPU, RAM, disk, IP and snapshot limits. Make sure the right template is accessible on every target.