Aura 7: Virtual Machine built on AVAYA Aura Virtual Platform (AVP) fails to deploy with CONNECTION_NOT_ESTABLISHED error

Doc ID		SOLN284833
Version:		2.0
Status:		Published
Published date:		01 Mar 2017
Created Date:		01 Mar 2016

Author:

Charles Kuhn

Details

AVP 7.0.0.0.0.21, Avaya_SDMClient_win64_7.0.0.0.16886_116, failure seen on Application Enablement Services (AES) vm, and Utility Services (VUS) vm. Installer also trying to repurpose older HP DL 360 G7s.

Problem Clarification

AVP installs without error but when using SDM or vSphere to install a virtual machine (VM) like US-7.0.0.0.0.12-e55-01_OVF10.ova (Utility Services) the VM fails to deploy in a late stage with CONNECTION_NOT_ESTABLISHED

Cause

Typically VMs need to spin an embedded cdrom and this step has been seen to not fully access the values input for network configuration. This has been quite rare, and thus, the RC behind the failure is not fully understood. Older hardware like HP DL 360s originally purposed for single core, low memory or that might have failed RAID controller batteries might contribute to the occurrence of this error, CONNECTION_NOT_ESTABLISHED.

Solution

It has been seen that in this late-stage failure the VM can be redeployed and then the VM can be accessed from the console, prior to the failure and the installer will notice from the console of that VM there will be network parameters that can be input. Once input the VM will deploy successfully.

Installer should double check hardware requirements and health too however.

Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy