RecoverPoint for VMs: Falha na operação de adição do vRPA com o erro "Não foi possível obter detalhes do RPA".
Summary: O erro do RecoverPoint for Virtual Machines (VMs) ocorre ao adicionar um novo vRPA (Virtual RecoverPoint Appliance) a um cluster do RecoverPoint.
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
Falha ao adicionar um novo nó do vRPA a um cluster do RecoverPoint.
O seguinte erro é relatado ao adicionar um novo nó do vRPA a um cluster do RecoverPoint:
ERROR - could not get RPA details.
Outro possível erro:
Failed to verify Vc credentials
Os logs do clusterLogic do RecoverPoint for VMs:
2024/03/26 15:34:44.461 [pool-214-thread-72] (BaseInstallationServerAdapter.java:310) ERROR - errorType: OPERATION_FAILED , userMSG: Operation failed. Failed to verify Vc credentials. 2024/03/26 15:34:44.461 [pool-214-thread-72] (BaseInstallationServerAdapter.java:317) ERROR - Transaction failed. transactionId=21, timeoutInSeconds=350, errorMSG=Operation failed. Failed to verify Vc credentials., errorType=OPERATION_FAILED, value=null 2024/03/26 15:34:44.461 [pool-214-thread-72] (BaseRpaCall.java:52) ERROR - GetRpaDetailsCall failed. java.lang.RuntimeException: Operation failed. Failed to verify Vc credentials. at com.emc.recoverpoint.cluster_logic.proxy.BaseInstallationServerAdapter.getResultFromTransaction(BaseInstallationServerAdapter.java:318) at com.emc.recoverpoint.cluster_logic.proxy.BaseInstallationServerAdapter.getTransactionResult(BaseInstallationServerAdapter.java:244) at com.emc.recoverpoint.cluster_logic.proxy.BaseInstallationServerAdapter.getTransactionResult(BaseInstallationServerAdapter.java:185) at com.emc.recoverpoint.cluster_logic.proxy.BaseInstallationServerAdapter.getTransactionResult(BaseInstallationServerAdapter.java:181) at com.emc.recoverpoint.cluster_logic.proxy.InstallationServerClientImpl.getRPADetails(InstallationServerClientImpl.java:110) at com.emc.recoverpoint.cluster_logic.cl_rpa_adapter_core.calls.GetRpaDetailsCall.innerCall(GetRpaDetailsCall.java:18) at com.emc.recoverpoint.cluster_logic.cl_rpa_adapter_core.calls.GetRpaDetailsCall.innerCall(GetRpaDetailsCall.java:8) at com.emc.recoverpoint.cluster_logic.cl_rpa_adapter_core.calls.BaseRpaCall.call(BaseRpaCall.java:37) at com.emc.recoverpoint.cluster_logic.cl_rpa_adapter_core.RpaAdapterImpl.getRpaDetails(RpaAdapterImpl.java:39) at com.emc.recoverpoint.deployment.validation.tasks.BuildRPADetailsTask.getRPADetailsOneCall(BuildRPADetailsTask.java:58) at com.emc.recoverpoint.deployment.validation.tasks.BuildRPADetailsTask.perform(BuildRPADetailsTask.java:43) at com.emc.recoverpoint.deployment.validation.tasks.BuildRPADetailsTask.perform(BuildRPADetailsTask.java:21) at com.emc.recoverpoint.utils.javainfra.status.tasks.Task.executeSync(Task.java:91) at com.emc.recoverpoint.utils.javainfra.status.tasks.Task.call(Task.java:142) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:823) 2024/03/26 15:34:44.462 [pool-214-thread-72] (GeneralUtils.java:75) ERROR - could not get RPA details.
Cause
O vRPA que está sendo adicionado não pode se comunicar com o vCenter Server.
Resolution
O usuário deve examinar a conectividade entre o novo vRPA e o vCenter Server. Isso pode ocorrer devido a uma porta bloqueada (443) em um firewall ou a um problema de roteamento.
Usar o comando da CLI do RecoverPoint for VMs update_vcenter_server_registration -f Para atualizar credenciais e certificados e verificar se funcionam:
Site1> update_vcenter_server_registration -f Enter RPA cluster name: Site1 Enter vCenter Server name: VCSA-Site1.lab.com Enter new vCenter Server name, or press 'Enter': Whould you like to change the connection paramters and credentials?(y/n)y Enter new vCenter Server IP address: (Default: Keep current value of xx.xx.xx.xx) Enter new vCenter Server port: (Default: Keep current value of 443) Enter new username: (Default: Keep current value of administrator@vsphere.local) Enter password: Validate credentials? (Default is 'yes') 1) yes 2) no Select, or press 'ENTER' 1 Here is the retrieved array certificate. Issuer: O=VCSA-Site1.lab.com, ST=California, C=US, DC=local, DC=vsphere, CN=VCSA-Site1 Subject: O=VMware, L=Palo Alto, ST=California, C=US, CN=VCSA-Site1.lab.com Not before: Fri Mar 01 16:51:38 UTC 2024 Not after: Sun Mar 01 16:51:38 UTC 2026 MD5: xxxxxxxxc718d4e1fa5c822xxxxxxxx SHA1: xxxxxxxxfe82c1c91fee70b4cf805a3xxxxxxxx SHA512: xxxxxxxxa27aea9ad28be80c7338d48ab8fddfbcf2xxxx955076215xxxxf5ee922a9e10080a71f382367b062d47d2118dc00c58c64c7xxxxxxxxxxxxxxxx vCenter Server registration updated successfully.
Affected Products
RecoverPoint for Virtual MachinesArticle Properties
Article Number: 000223733
Article Type: Solution
Last Modified: 02 Apr 2025
Version: 3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.