Unified Communications

I am feeling like a complete idiot in that I cannot get SDM to work regardless of SMGR/SDM or SDM Client. I am able to get some of the VM's to re-establish Connection, but others hang up with the "Get Trust Status      FAIL".

Also, I am using my own vMware credentials for each Host but have asked our server team to establish a service login instead of a user login and our server team has the following question which Avaya has not yet responded to:

In preparation for this meeting, please provide the Avaya tech's responses to the questions I asked previously:
1) What is the avaya appliance logging in to the host directly to do

2) Why does it not do this action through vcenter Also, given that you had 2 hosts working without a local / direct host SSH login I would like to add a third question:

3) Is a local SSH login actually needed when the avaya appliance is talking to / through vcenter Please email or call me with answers to the questions above.

I am feeling like a complete idiot in that I cannot get SDM to work regardless of SMGR/SDM or SDM Client. I am able to get some of the VM's to re-establish Connection, but others hang up with the "Get Trust Status      FAIL".

Also, I am using my own vMware credentials for each Host but have asked our server team to establish a service login instead of a user login and our server team has the following question which Avaya has not yet responded to:

In preparation for this meeting, please provide the Avaya tech's responses to the questions I asked previously:
1) What is the avaya appliance logging in to the host directly to do

2) Why does it not do this action through vcenter Also, given that you had 2 hosts working without a local / direct host SSH login I would like to add a third question:

3) Is a local SSH login actually needed when the avaya appliance is talking to / through vcenter Please email or call me with answers to the questions above.

This is what i discovered when I was having problems with SDM and VMWare. When SDM communicates with vCenter and/or the ESXi hypervisor (directly), it uses API and not traditional scripting. Because of this, SDM will connect using TLS. You'll need to add your company's VMWare's SSL CA cert to SDM certificate store so that it will trust the connection.

SDM will use traditional scripting (SSH) when connecting to many of the Avaya guests within the virtual environment to download, execute, and apply the patches.

I don't know if this is the problem you are experiencing but, this fixed me up.