Skip to main content
Sign Out
Welcome to Dell
My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us
Your Dell.com Carts
Some article numbers may have changed. If this isn't what you're looking for, try searching all articles. Search articles

Article Number: 000055975

IDPA Deployment Stuck at 6%

Summary: during deployment of IDPA it reports error with deploying the AVproxy at 6%

Article Content

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

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. Reason:com.avamar.mc.sdk20.McsFaultMsgException: 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. Reason:com.avamar.mc.sdk20.McsFaultMsgException: McsFaultMsgException

 
Cause

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 



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

Article Properties

Affected Product

Integrated Data Protection Appliance Family

Product

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

Last Published Date

20 Nov 2020

Version

2

Article Type

Solution

Back to Top