Getting VMware ESXi ready for Avaya SDM client

Prerequisites

  • Server with vSphere ESXi installed
  • ESXi License with vSphere API enabled (the free one doesn’t work)
  • Avaya SDM client on Windows
  • Local DNS Services

ESXi

The VMware Installer will generate a self signed certificate for the hostname of the ESXi host, this hostname needs to be resolvable later by the SDM client.

If you have already installed your host you can see the certificate via your browser.

The certificate on the left was issued when I first installed the host, this is just a hostname and not an FQDN so this will not work, the one on the right is the newly generated one. The SDM client does not work with IP Addresses so you have to have the certificate issued to the FQDN.

Add the FQDN to your DNS Resolver so it does go to the appropriate address.

pfsense DNS Resolver

Once everything is neat and tidy the SDM will show us the certificate and we can hit Accept Certificate and go on to deploy some VMs.

Successfully added the host to the SDM client.

Windows SDM client

Install SDM client on the PC you are going to deploy the OVAs from, the client should have the same release as your System Manager. You can find the SDM client on support.avaya.com under System Manager.

If you put all OVAs and Patches here
C:\Program Files\Avaya\AvayaSDMClient\Default_Artifacts
the OVA will be loaded to the hypervisor on hitting “deploy”, the other option is to “browse” for them when selecting the OVA file, but this way you will have to wait until the file is “loaded”.

Error messages

Retrieving host certificate info is failed: The certificate received from x.x.x.x was issued for a different server. Secure communication cannot be established from Solution Deployment Manager to systems where the host IP/FQDN does not match the details in the security certificate. You may need to re-generate the certificate on your system to correctly match the host details or connect with the FQDN of the system rather than the IP address.

This is the error message you get if this is not done correctly.

Professionally change the FQDN of your ESXi host or use the quick and dirty method which should under no circumstances be used in a production environment:
Go into the CLI of the ESXi, verify the
/etc/hosts
files has the correct hostname/FQDN information, edit the file
/etc/vmware/esx.conf
the row
/adv/Misc/HostName = "labmachine"
should contain the FQDN of the server. Reboot and run
/sbin/generate-certificates
reboot, now you should have the correct hostname/FQDN and certificate.

Error Code-UNABLE_TO_CREATE_VM:: Unable to create new VM. The license on the host does not support VMWare API which is required by SDM. Please contact VMware for appropriate licenses.

You get this one if you do not have the licenses for vSphere API and try to deploy a VM.

Are you using the free VMware ESXi license? It will not work, you need a license with the feature vSphere API.
I have VMware vSphere 6 Essentials Plus and can confirm that it does work with that, I am quite sure it also works with VMware vSphere Essentials.

Retrieving host certificate info is failed: The server https://vcenter.lab.lab/sdk does not exist. Please check the IP addresss / FQDN.

Are you trying to add a Vcenter? If so you have to do that on the lower left, Map vCenter.

Hardware resources

Keep in mind that Avaya not only specifies how much of every resource is needed (RAM, CPU, Donkeystrength…) but also what the minimum vCPU speed is. The SDM client will reserve these resources from the start and if they are not available it will not even let you deploy the VM. Of course you can later remove the reservations in your actual vmware ESXi manager.

To quickly get the Hardware requirements for an Avaya product get the deployment guide and search for “Supported footprints”

Date: 19.08.2019

Leave a Reply

Your email address will not be published. Required fields are marked *