IDPA Deployment Stuck at 6%


   Article Number:     529644                                   Article Version: 2     Article Type:    Break Fix 




DP5800 Appliance,Integrated Data Protection Appliance Family,Integrated Data Protection Appliance Software,Integrated Data Protection Appliance





During Deployment of Integrated data protection appliance it reports errors with being able to deploy the AVproxy.    
    Seeing Errors as follows on the /usr/local/dataprotection/var/configmgr/server_data/logs/server.log file   

Line 10519: 2019-01-22 22:34:09,746 INFO  [pool-5-thread-14]-avadapter.AvamarMcsdkUtil: getDomain() looking for domain name dpappliance-vcsa.idpa.local    Line 10536: 2019-01-22 22:34:09,849 ERROR [pool-5-thread-14]-avadapter.AvamarMcsdkUtil: getDomain()Failed to get domain from Avamar. McsFaultMsgException    Line 10567: 2019-01-22 22:34:19,873 INFO  [pool-5-thread-14]-avadapter.AvamarMcsdkUtil: getDomain() looking for domain name idpa-vcenter.emc.local    
    Other errors may include   
Line 12337: 2019-01-22 22:35:20,072 INFO  [pool-5-thread-14]-avadapter.AvamarMcsdkUtil: getClient() looking for client name idpa-vcenter.emc.local/dpappliance-vcsa.idpa.local    Line 12354: 2019-01-22 22:35:20,122 ERROR [pool-5-thread-14]-avadapter.AvamarMcsdkUtil: getClient()Failed to get client from Avamar. McsFaultMsgException    






    caused by a duplicate or incorrect entry of the vCenter in the DNS or host file of the ACM.   
    if you perform a nslookup on the IP address you will see a name different from the actual vCenter hostname. it is possible that the implementations/Professional services engineer has added the dpappliance-vcsa.idpa.local entry in the DNS early because of the errors seen in KB article: 516540    






a change to the DNS entries or host files on the ACM                                                           






correct the DNS entries or host file for incorrect vCenter hostname.