RecoverPoint for VMs：vRPAの追加操作が「RPAの詳細を取得できませんでした」というエラーで失敗します。

新しいvRPAノードをRecoverPointクラスターに追加できません。

新しいvRPAノードをRecoverPointクラスタに追加すると、次のエラーが報告されます。

ERROR - could not get RPA details.

別の考えられるエラー:

Failed to verify Vc credentials

RecoverPoint for VMsのclusterLogicログ:

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.

追加されているvRPAは、vCenter Serverと通信できません。

ユーザーは、新しいvRPAとvCenter Server間の接続を確認する必要があります。ファイアウォールでポート(443)がブロックされているか、ルーティングに問題があることが原因である可能性があります

RecoverPoint for VMs CLIコマンドの使用 update_vcenter_server_registration -f 認証情報と証明書をアップデートし、それらが機能していることを確認するには、次の手順を実行します。

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.